XMR registers 2.5-year high of $218 after ~31% surge
Monero (XMR/USD1) bulls have managed to essentially wipe all bear progress since May 2022 with an impressive under 9-hour ~31% surge yesterday from $166 to ~$218.

As I am writing this report, the reds are trying to force the price back under the 200 psychological level.

Provided bulls manage to reinforce the 175-185 support zone, we could see another attempt to break the local top. This could leave the next resistance around … ⌘ Read more

How to Instantly Write a Business Plan with AI on Mac, iPhone, iPad
While there are plenty of paid options to get a business plan, from business plan software, to books, to working with a consultant, or even outsourcing the entire thing, another option is available for iPhone, iPad, and Mac users, and it uses the magic of Apple Intelligence features and ChatGPT to instantly create a business … Read More ⌘ Read more

How to Find a Lost Apple Pencil
The Apple Pencil is a great accessory for iPad users, but obviously you can’t use an Apple Pencil if it’s lost, and it’s not particularly useful if it’s missing. Fortunately there are a few tricks that you can employ to help you find a lost Apple Pencil, so you can be back to your writing, … Read More ⌘ Read more

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

Beta 2 of iOS 18.2, MacOS Sequoia 15.2, & iPadOS 18.2 Available for Testing
The second beta versions of iOS 18.2, MacOS Sequoia 15.2, and iPadOS 18.2 are now available for users participating in the beta testing programs for Apple system software. The new betas continue to focus on additional Apple Intelligence features, expanding beyond the writing tools, smart replies, and summary features what was initially introduced in iOS … [Read More](https://osxdail … ⌘ Read more

@quark@ferengi.one Yeah i’m in deep red here. the governor race is getting split between a red and a maga that is running a write in.. but even if they split the vote 50-50% they will still be greater than what the blue will get.

@bender@twtxt.net I try to avoid editing. I guess I would write 5/4, 6/4, etc, and hopefully my audience would be sympathetic to my failing.

Anyway, I don’t think my eccentric decision to number my twts in the style of other social media platforms is the only context where someone might write ¼ not meaning a quarter. E.g. January 4, to Americans.

I’m happy to keep overthinking this for as long as you are :-P

@bender@twtxt.net @prologic@twtxt.net I’m not exactly asking yarnd to change. If you are okay with the way it displayed my twts, then by all means, leave it as is. I hope you won’t mind if I continue to write things like 1/4 to mean “first out of four”.

What has text/markdown got to do with this? I don’t think Markdown says anything about replacing 1/4 with ¼, or other similar transformations. It’s not needed, because ¼ is already a unicode character that can simply be directly inserted into the text file.

What’s wrong with my original suggestion of doing the transformation before the text hits the twtxt.txt file? @prologic@twtxt.net, I think it would achieve what you are trying to achieve with this content-type thing: if someone writes 1/4 on a yarnd instance or any other client that wants to do this, it would get transformed, and other clients simply wouldn’t do the transformation. Every client that supports displaying unicode characters, including Jenny, would then display ¼ as ¼.

Alternatively, if you prefer yarnd to pretty-print all twts nicely, even ones from simpler clients, that’s fine too and you don’t need to change anything. My 1/4 -> ¼ thing is nothing more than a minor irritation which probably isn’t worth overthinking.

iOS 18.1 with Apple Intelligence Now Available to Download
Apple has released iOS 18.1 and iPadOS 18.1 to bring Apple Intelligence features to iPhone and iPad. The initial set of Apple Intelligence AI features include writing tools, summaries for messages and emails, and other handy capabilities. Apple Intelligence has strict system requirements however and is not available on all devices. Aside from Apple Intelligence, … [Read More](https://osxdaily.com/2024/10/28/ios-18-1- … ⌘ Read more

Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

1. It’s a text file, so you must be able to write it by hand (ie. no app logic) and read by eye. If you edit a post you change the content not the timestamp. Otherwise it will be considered a new post.

2. The order of lines in a twtxt.txt must not hold any significant. The file is a container and each line an atomic piece of information. You should be able to run sort on a twtxt.txt and it should still work.

3. Transport protocol should not matter, as long as the file served is the same. Http and https are preferred, so it is suggested that feed served via Gopher or Gemini also provide http(s).

4. Do we need more commandments?

Release Candidates of iOS 18.1, MacOS Sequoia 15.1, & iPadOS 18.1 Available
Apple has issued release candidate builds of iOS 18.1, macOS Sequoia 15.1, and iPadOS 18.1, making them available for users enrolled in the beta testing programs for Apple system software. These versions are the first to include Apple Intelligence support on compatible devices. Initial Apple Intelligence features include functionality for summarizing data, writing tools, and … [Read … ⌘ Read more

Minix Z300 0DB Fanless Mini PC with 2.5GbE LAN and Dual 4K Display Support
The Minix Z300-0dB delivers efficient, quiet performance with a fanless passive cooling design that eliminates the need for traditional fans. Powered by the Intel Alder Lake-N N300 octa-core processor, it features Kimtigo premium RAM and a PCIe 3.0 x4 NVMe SSD for fast read and write speeds, enhancing productivity and response times. According to the […] ⌘ 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

escapethe3RA: Looking for funding to maintain Monero Observer until 2026

Funding goal (24Q4+2025): 240 XMR

11 successful CCS proposals, 3500+ work hours, thousands of reports in over 3 years of thinking about, writing about, and dreaming about Monero.

That has been my sometimes rough yet always exciting secret life since 2021 and I wouldn’t change it for anything. More importantly, I owe it all to you. Thank you for supporting me since day 1 via the CCS.

Now, I am ready to skip the system and seek dire … ⌘ Read more

Honestly… not much. Have abandon two projects (both private) on Golang and one related to cryptography. My mostly languages are Python and Javascript (also can PHP). After writing code on Go i spend same time on fixing dumb errors

I share I did write up an algorithm for it at some point I think it is lost in a git comment someplace. I’ll put together a pseudo/go code this week.

Super simple:

Making a reply:

1. If yarn has one use that. (Maybe do collision check?)
   
2. Make hash of twt raw no truncation.
   
3. Check local cache for shortest without collision
   
   • in SQL: select len(subject) where head_full_hash like subject || '%'
     

Threading:

1. Get full hash of head twt
   
2. Search for twts
   
   • in SQL: head_full_hash like subject || '%' and created_on > head_timestamp
     

The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.

Recent #fiction #scifi #reading:

• The Memory Police by Yōko Ogawa. Lovely writing. Very understated; reminded me of Kazuo Ishiguro. Sort of like Nineteen Eighty-Four but not. (I first heard it recommended in comparison to that work.)

• Subcutanean by Aaron Reed; https://subcutanean.textories.com/ . Every copy of the book is different, which is a cool idea. I read two of them (one from the library, actually not different from the other printed copies, and one personalized e-book). I don’t read much horror so managed to be a little creeped out by it, which was fun.

• The Wind from Nowhere, a 1962 novel by J. G. Ballard. A random pick from the sci-fi section; I think I picked it up because it made me imagine some weird 4-dimensional effect (“from nowhere” meaning not in a normal direction) but actually (spoiler) it was just about a lot of wind for no reason. The book was moderately entertaining but there was nothing special about it.

Currently reading Scale by Greg Egan and Inversion by Aric McBay.

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.

https://stephanearnier.com/2024/09/27/ecrire-a-la-premiere-personne-les-essentiels/ #writing

why can we both have a format that you can write by hand and better clients?

5th Beta of iOS 18.1, MacOS Sequoia 15.1, iPadOS 18.1 with Apple Intelligence, Available for Testing
Apple has released the 5th beta versions of iOS 18.1, macOS Sequoia 15.1, and iPadOS 18.1, with Apple Intelligence support. The Apple Intelligence features that are included with these releases are mostly Writing Tools, summaries, and new Siri features, which allow you to do things like summarize emails, offer Smart Replies in Mail and Mes … ⌘ Read more

@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.

I wrote some code to try out non-hash reply subjects formatted as (replyto ), while keeping the ability to use the existing hash style.

I don’t think we need to decide all at once. If clients add support for a new method then people can use it if they like. The downside of course is that this costs developer time, so I decided to invest a few hours of my own time into a proof of concept.

With apologies to @movq@www.uninformativ.de for corrupting jenny’s beautiful code. I don’t write this expecting you to incorporate the patch, because it does complicate things and might not be a direction you want to go in. But if you like any part of this approach feel free to use bits of it; I release the patch under jenny’s current LICENCE.

Supporting both kinds of reply in jenny was complicated because each email can only have one Message-Id, and because it’s possible the target twt will not be seen until after the twt referencing it. The following patch uses an sqlite database to keep track of known (url, timestamp) pairs, as well as a separate table of (url, timestamp) pairs that haven’t been seen yet but are wanted. When one of those “wanted” twts is finally seen, the mail file gets rewritten to include the appropriate In-Reply-To header.

Patch based on jenny commit 73a5ea81.

https://www.falsifian.org/a/oDtr/patch0.txt

Not implemented:

• Composing twts using the (replyto …) format.
  
• Probably other important things I’m forgetting.

@prologic@twtxt.net Wikipedia claims sha1 is vulnerable to a “chosen-prefix attack”, which I gather means I can write any two twts I like, and then cause them to have the exact same sha1 hash by appending something. I guess a twt ending in random junk might look suspcious, but perhaps the junk could be worked into an image URL like

Image

git only uses sha1 because they’re stuck with it: migrating is very hard. There was an effort to move git to sha256 but I don’t know its status. I think there is progress being made with Game Of Trees, a git clone that uses the same on-disk format.

I can’t imagine any benefit to using sha1, except that maybe some very old software might support sha1 but not sha256.

@movq@www.uninformativ.de

Maybe I’m being a bit too purist/minimalistic here. As I said before (in one of the 1372739 posts on this topic – or maybe I didn’t even send that twt, I don’t remember 😅), I never really liked hashes to begin with. They aren’t super hard to implement but they are kind of against the beauty of the original twtxt – because you need special client support for them. It’s not something that you could write manually in your twtxt.txt file. With @sorenpeter@darch.dk’s proposal, though, that would be possible.

Tangentially related, I was a bit disappointed to learn that the twt subject extension is now never used except with hashes. Manually-written subjects sounded so beautifully ad-hoc and organic as a way to disambiguate replies. Maybe I’ll try it some time just for fun.

@prologic@twtxt.net Brute force. I just hashed a bunch of versions of both tweets until I found a collision.

I mostly just wanted an excuse to write the program. I don’t know how I feel about actually using super-long hashes; could make the twts annoying to read if you prefer to view them untransformed.

💻 Issue 433 - Writing an Android app with Scala.js ⌘ Read more

** Constants, variable assignment, and pointers **
After reading my last post, a friend asked an interesting question that I thought would also be fun to write about!

They noted that in the reshape function I declared the variable result as a constant. They asked if this was a mistake? Because I was resigning the value iteratively, shouldn’t it be declared using let?

What is happening there is that the constant is being declared as an array, so the reference … ⌘ Read more

iOS 18 is Compatible with These iPhone Models
iOS 18 for iPhone includes a variety of new features that many users are excited about, from all new Dark Mode icons and widgets, to color hued icons/widgets, customizable Control Center, Apple Intelligence AI features that will write emails and texts for you and summarize data or generate images, a confusing Photos redesign, Game Mode … Read More ⌘ 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

Exam Numbers
⌘ Read more

Exam Numbers
⌘ Read more

@movq@www.uninformativ.de Somewhere or another, I think in a William Byrd talk, I heard it suggested that the best ideas in computer science should fit on an index card (ah yes it’s this one: https://paperswelove.org/2017/video/will-byrd-most-beautiful-program/ ). He was referring to the basic principles of LISP/the lambda calculus, which have sometimes been called the Maxwell’s equations of computer programming (by Alan Kay). Simple, short, elegant, but very densely packed with meaning–generations of people have spent their whole careers unpacking what those simple rules can do.

Much of modern software feels like the polar opposite of that. Not only can you not write it on an index card, you never will be able to because people who write software don’t seem to aspire to try. I wish more people thought this way though!

It seems like I finally fixed a memory leak in GoBlog yesterday, that sometimes made my blog crashing. How? I used Anthropic’s new Claude 3.5 Sonnet to write me a new HTTP compression middleware that compresses HTTP responses using zstd or gzip when possible. I needed to instruct a few changes and modify some code lines as the initial implementation was wrong, but thereafter, it finally seems to work better than my original implementation that probably leaked some objects anywhere. Claude also helped me to write uni … ⌘ Read more

Last week at The Lunduke Journal (June 23 - June 29, 2024)
Microsoft Write! Computers in 1961! Ridiculous Amounts of RAM! Socialism! ⌘ Read more

There is JavaScript, but not everything is implemented (properly). They’re writing everything including the JavaScript engine from scratch.

A huge effort 😲

Experiment in Digital minimalism
I recently read Cal Newport’s book Digital Minimalism. It really
resonated with me, despite (or because of?) being glued to my computer
many hours of the day.

Cal suggests a month of digital decluttering, at first cutting off
everything that your job and other obligations don’t depend on. At the
end of the month you evaluate what, if anything, is to be let back
inside.

I did a decluttering plan for April. It ended up being an ongoing
project when I’m writing this in June.

Fire-proof safes are generally designed so the internal temperature stays at or below ~350°F. Is there a computer medium I can write that’s likely to survive an extended stay around that temperature? Storage size doesn’t matter too much; a CD would be plenty (although an actual CD would presumably turn to soup).

https://stephanearnier.com/2024/05/31/creation-de-personnages-trois-tamis/ #writing personnages

Best way to write programs: turn off the computer.

Started writing something from scratch yesterday using thread(3) and wow do I miss writing in Limbo instead. :-/ #plan9

Just over here writing my Senator’s office to see if we can get a new Federally Funded R&D Center created. 😳🤞

Generating Kubernetes ValidatingAdmissionPolicies from Kyverno policies
Project post originally published on Kyverno’s blog by Mariam Fahmy In the previous blog post, we discussed writing Common Expression Language (CEL) expressions in Kyverno policies for resource validation. CEL was first introduced to Kubernetes for the Validation rules for CustomResourceDefinitions,… ⌘ Read more

Whenever I write O_RDWR it makes me think of Martin Crane

Did another write up on #webfinger and DIDs for twtxt/yarn that you can read and edit/comment in: User lookup for twtxt/yarn - Webfinger or Decentralized Identifiers (DIDs) - HedgeDoc

How to Mount & Copy HFS Classic Mac Drives on MacOS
Modern versions of MacOS no longer support HFS, meaning that new Macs can no longer read, mount, or write to classic HFS drives. But a fair amount of longtime Mac users continue to have older Macs and old Mac hard drives that are in HFS format, way back from the days of Mac OS 8, … Read More ⌘ Read more

Keyboard layouts
I’ve updated my article about keyboard layouts with XKB after 13
years!

https://hack.org/mc/writings/xkb.html

I’ve edited it so the focus is on the layouts if you just want to grab
them and don’t need any handholding. Also added Thinkpad layouts along
with the original HHKB layouts.

It now also includes instructions for use with the River and Sway
Wayland compositors as well as X11.

I will probably update it soon with some images of different Thinkpad
keyboards. ⌘ Read more

Status 2024-01-29
Friday is my day off from work, as usual. So when I’m typing this I’m
in front of the hackstation (not a battlestation, obviously) with my
third cup of coffee, writing an update again.

I’ve been doing these status updates on my Gemini log, but I’m
increasingly aware of the dropping amounts of traffic, so I’m thinking
about doing them on the blog instead, but see below for some thoughts
on Gemini.

In which I speak about an intense week, feeling good(?), spending … ⌘ Read more

💻 Issue 401 - How to Write a Full-Stack Scala Application with the Typelevel Stack ⌘ Read more

** Arkady Martine and Virginia Woolf **
As an undergrad and a grad student I was obsessed with Virginia Woolf. Woolf’s writings appeared in my citations pretty much regardless of the class or subject area I was writing on.

I have recently finished reading an engaging and lovely novel by Arkady Martine,“A Memory Called Empire.” Of course, I was excited to pick up the sequel, but, also, I had this feeling, this Woolf’s scent — I’ve always felt that Woolf’s nonfiction was more lucid and p … ⌘ Read more