“You have reached a non-working number at UPS […]” says the recording. If it is a non-working number, it wouldn’t even ring, right? It should have said “You have reached an outgoing calls only number at UPS […]”, or better yet, route outgoing call only numbers to the one we should be calling instead. Problem resolved.

⤋ Read More

Summary of Discussions (as best I can):

  • @lyse@lyse.isobeef.org and @sorenpeter@darch.dk express simplicity. Both Lyse and Sorenpeter support location-based addressing.
  • @falsifian@www.falsifian.org believes we should continue to develop ideas and extensions progressively over time like we’ve always done.
  • @david@collantes.us @quark@ferengi.one and @bender would like a better user experience, especially when threads break due to edits, deletions or feed location changes.
  • @anth@a.9srv.net would like to see utf-8 mandated, and the threading model remain largely the same as it is today, which is primarily based on the convention of a Twt Subject anyway, Twt Hash(es) just make the threading “more precise”. Anth also states that format, client and server specification/recommendations should be kept separate.
  • @movq@www.uninformativ.de @xuu@txt.sour.is sorry you two haven’t said too much really, so I’m not too sure?

Overall, the 22 votes we’ve had on the poll from the community (if you can call it a community?) have clearly shown that:

  • We continue to support content-based addressing. (65/35)
  • We think about formally supporting edits/deletes (60/40)
  • We do not increase the use of cryptography (thworing things like authenticity and identity out the window) (70/30)

And overall the NPS (net promoter score) of “Would I recommend Twtxt to a friend” is a whopping 7/10 (which is crazy! 🤯)

Let’s have our monthly catch up soon™ (1hr) and discuss together. My own take on the direction we should take at this point is as follows:

  • We continue to use hashing for the threading model.
    • We think about changing this to SHA-256 for simplicity.
  • We either adopt @anth@a.9srv.net’s UUID approach or @lyse@lyse.isobeef.org Dynamic URL approach.
  • We continue to incrementally/progressively improve things over time as @falsifian@www.falsifian.org suggested.
  • We think about mandating utf-8 as @anth@a.9srv.net suggests which makes things so much easier for everyone.
  • We further discuss the merits/ideas of supporting formal Edit/Delete requests or other ways to better support this in some way.

⤋ Read More

Diving into mblaze, I think I’ve nearly* reached peek email geek.

Just a bunch of shell commands I can pipe together to search, list, view and reply to email (after syncing it to a local Maildir).

EXAMPLES at https://git.vuxu.org/mblaze/tree/README

So far I’m using most of the tools directly from the command line, but I might take inspiration from https://sr.ht/~rakoo/omail/ to make my workflow a bit more efficient.

*To get any closer, I think I’d have to hand-craft my own SMTP client or something.

⤋ Read More

“First world” countries problem number x:

More than 3,600 chemicals approved for food contact in packaging, kitchenware or food processing equipment have been found in humans, new peer-reviewed research has found, highlighting a little-regulated exposure risk to toxic substances.

⤋ Read More

I passed a mountainbiker with a helmet camera in the forst, saw a four centimeter long black beetle that rolled over its side to change directions and finally spotted three deer on the paddock. An hour well spent I reckon.

⤋ Read More

Some more arguments for a local-based treading model over a content-based one:

  1. The format: (#<DATE URL>) or (@<DATE URL>) both makes sense: # as prefix is for a hashtag like we allredy got with the (#twthash) and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.

  2. Having something like (#<DATE URL>) will also make mentions via webmetions for twtxt easier to implement, since there is no need for looking up the #twthash. This will also make it possible to make 3th part twt-mentions services.

  3. Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don’t follow.

⤋ Read More

Held another “talk” about Git today at work. It was covering some “basics” about what’s going on in the .git directory. Last time I did that was over 11 years ago. 😅 (I often give introductions about Git, but they’re about day to day usage and very high-level.)

I’ve gotta say, Git is one of the very few pieces of software that I love using and teaching. The files on your disk follow a simple enough format/pattern and you can actually teach people how it all works and, for example, why things like rebasing produce a particular result. 👌

⤋ Read More

Can anyone recommend a decent Android ROM that strips out as much of the spyware as possible? Is GrapheneOS a good option? I need to get a new phone anyway so I don’t mind buying within a supported device list as long as I can get one on the used market for $300-$400 or less.

If anyone could recommend some learning resources for this stuff I’d really appreciate it.

⤋ Read More