Hardening aside, I like that LibreWolf actually lets you turn on JPEG XL.

If you want a rush, try gyukuro. Flavor of an umami green tea with the caffeine level of a cup of coffee & high L-thiamine to cut the jitters.

I lived it the UK briefly & my roommate never understood my fascination generally preferring his Yorkshire tea (trash). One day he asked about it so I made him a mug (we used coffee mugs). He said it tasted like yard clippings like other green teas before walking off continuing to sip to not waste it. He comes back in 15–20 minutes later over halfway finished, “Did you put drugs in this‽”. “Nope.” “I feel like I want to run a marathon. Okay, I see the appeal for your mornings, but this is the worst high ever.”

Gerrit is probably the poster child for branchless, stack-based diffs in Git. It takes some get getting used to, but once adjust your thruput is really ramps up. In some sense tho, this is a hack by tagging changelist values in the commit message to help reconstruct what the heck is going on due to Git limitations, but it’s old & robust enough to trust that system & many of its users absolutely swear by it (I have limited exposure but have used it more recently I can feel the appeal). You should be able to slap it in front of any Git server—even just straight host HTTP if not something lightweight like cgit, gitweb, or Ayllu. (Jujutsu is the same commit hackery in a different package & I don’t think it moves the needle as much as folks think being ultimately shackled to Git’s design decisions).

If you look outside of snapshot-based tools like Git, Mercurial, & so on, patch-theory-based options offer refuge. Darcs & Pijul are the leading (D)VCSs in the space. Darcs is very mature & shows its age in many ways (but is still developed & works good enough). Pijul is largely based on Darcs but meant be faster (& is), but it is immature; some features are missing on purpose to avoid the swell of Git commands, but I am personally surprised theres no good story for sending patches nor rebase. That said its identity system is how VCS should do it. Both VCSs have a lot less tooling built around them. Darcs is still supported by tools like Nix (but not Flakes) as well as Opam for OCaml with darcs hub & Smederee for maintained public forges. Pijul isn’t supported by much at all unfortunately & while Nest is a public forge, its lacking in features & basic usability like being able to fetch a tarball (despite pijul archive). All the latter negativity may sound bad, but all tooling requires momentum. They would be prime candidates for the Gerrit workflow--just without the hacks needed. With the two being similar, I hope we see more tooling pop up to support them & just like trying a new paradigm of programming gives you insight on the ones you know, a new way to do VCS will teach you about version control. Do recommend.

client or server that doesn’t support the same encryption protocols

Outside of TLS which most any server uses by default, XMPP or not, the server is not responsible for E2EE. Conversations Compliance & Are We OMEMO Yet have existed for a long while & I never see anyone recommending a client not on these lists so while certain features may be fragmented, the communication essentials have been more or less established for years now. XMPP is an extensible format, and some applications that aren’t for chatting with your friends/family, don’t need many of these features which allows the protocol to morph into something stripped down for the task… which is why the base spec is basically barren, & community XEPs are what folks get behind for adding new features for different use cases.

This isn’t speaking, but writing (or typing). Using ‘correct’ spelling & grammar helps ESL speakers read the language as well as those relying on text translation software. Some folks make typos & it’s fine to make mistakes but it’s also strange to act like it’s just as easy to understand. Apostrophes have a specific meaning & many folks rely on them for understanding.

I’m learning a foreign language now & I can tell you it is a massive stumbling block when you run into what you think is a new word, but is ‘just’ a misspelling.

My issue with this account is not its corrections, but if you want to be the correction bot, at least get the typography right too. ' is as ASCII holdover & it should be ’.

If you want the messaging to be resilient, this makes sense as a server can go down but anyone else connected has the whole history on their server.

But I think that is better suited for a forum where copying Slack/Discord’s lead & trying to preserve all history in a chat isn’t worth it as I see this sort of thing as better tasked for ephemeral communication. However, there is something communal & intuitive about chat apps that make folks interact pretty well so they can make decisions. This is a ‘good thing’ where forums don’t get the same engagement—but at the cost of you had to be there or worse, you need an account to see the discussion for that decision.

I made the mistake of getting my family to switch to Signal. It works great for messaging, but it has other issues—beyond the typical SIM-required complaint. I hate that you have to register with a ‘primary’ device on either iOS or Android fueling that duopoly (SoL if you are on a postmarketOS or KaiOS or Capyloon phone… or just don’t want a internet-capable phone). Notifications are sent thru Google’s FSM (news 1–2 months ago that of course Apple & Google send all the metadata to the feds) & refuse to support UnifiedPush (thank goodness the Molly fork does). They’re also not too happy to support alternative clients meaning you are stuck with the shitty, resource-sucking Electron client while not having a web client or native or TUI client. And the worst cherry on top is shipping those iOS emoji to Android & Linux …eww.

This is why you should install an adblocker on the network as well as your machine + browser & browse with JavaScript in allowlisted mode (enable remote code execution if & only if it is required—which it often is for web apps, but web pages should work without via progressive enhancement).

70% is the happiest middle ground for me: still have function row so less modifier-holding required (vertical space was never the issue) & tighter than tenkeyless while not giving up keys. Luckily these are readily sold & the default laptop keyboard setup. Numpads IMO are a niche peripheral that are rarely used & add stress to mouse usage since that numpad has to be crossed over every time for the average user; separate numpads can be bought and located somewhere more ergonomic.

I don’t like Microsoft Windows at all, but you are absolutely right about doing a good job with backwards compatibility.

Linux isn’t so backwards compatible, but with much of it having open source code, you can often compile it again yourself—tho having been written in a language that offers good backwards compatibility also helps.

Seeing how the dumb community feels trapped now that Meta stopped supporting KaiOS, I can tell there are a lot of people that wish they could leave the service. A lot of spaces make you feel like you have to use it, not want to use it. I used a few months while I was in the UK, but after that I’ve been lucky enough to delete my account as the service was useless elsewhere where other places I lived, no one used it.

…That said, I now have issues with LINE as a defacto chat option locally that gets in the way. My account was crushed after they canceled LINE Lite which was 10× smaller with no bloat or trackers & I refused to “upgrade” (where like WhatsApp & Signal, one is forced to have a mobile device as a primary device). Largely I can inconvenience everyone by making them choose a different means of communication (with email be largely the only common denominator) but if I were dating again, I would inevitably be forced to use the unsafe app putting myself in the position a lot of WhatsApp users feel they are without effective choice.

I also have a Shanling DAP (many files in FLAC, Opus, Ogg, AAC, not just MP3s). Just 9 more comments to a dozen.