in reply to Michel 🪱

@Michel 🪱 Fortunately things are named well enough that I can mostly work out what everything does. He has made some... interesting choices though. I want to do a bit of a refactor and have offered to send my changes upstream for review. I know he's not doing feature requests these days, but nothing stops me from implementing changes and fixes, even if only in a private fork.
in reply to Jonathan Lamothe

We're still here. Tornado risk is gone, but we've been wothout power for the past two hours, the server that hosts my usual account is down.

No word on when power will be restored, but we're otherwise okay.

This entry was edited (Thursday, September 3, 2026, 12:38 AM)

It says something about the state of modern browsers that my preferred way for reading things on the web from my tablet is to:

  1. Open termux
  2. ssh into my laptop
  3. Launch Emacs
  4. Browse using eww

Otherwise, I chew through battery in no time flat. As it stands, I've been doing so for many hours straight and still have 88% battery.

Been looking for an iOS compatible #reticulum client for Katy. There seems to be exactly one (Retichat).

Unfortunatrly, it doesn't seem to work properly, and I can't prove it, but I think it's MitM-ing the messages.

Finally found another Android client that's working on an iOS port. I popped over to the project's GitHub page and what's the first thing I see? A .claude directory.

Welp, back to the drawing board.

fedipossible reshared this.



@kbond008@diaspora.glasswings.com:
Former climate scientists from NOAA launched Climate.us after being fired during the Trump administration, aiming to provide accessible and reliable climate information to the public. This new platform serves as a successor to the now-defunct Climate.gov, ensuring continued access to vital climate data and resources.
climate.us/about

#climateinfo



me blabbing on about Reticulum (my current fixation) again

One of the things I really love about #reticulum is its ability to seamlessly route traffic over literally any communication medium that can handle at least 5 bits per second. I'm also reminded of a YouTube video I watched a while ago where a guy was able to send data (at a very slow rate) over a literal tin can phone. Sadly, I can't find the link.

Anyhow, I think you can probably figure out what I am now legally and morally obligated to do.

fedipossible reshared this.

in reply to Hannes Deeken

@Hannes Deeken It wasn't regarding the network itself. I just stumbled across some nodes that were hosting general conspiracy nonsense.

Given how attractive the network would seem to doomsday preppers and so-called "free speech absolutists", I expected that sort of thing to be more prevelant.

Florian Schmidt reshared this.

Woke up this morning to a very large unexpected bill that needed to be addressed immediately. Managed to put the immediate fire out (or at least reduce it to a manageable simmer) but it took several hours of negotiating and it burnt essentially all of my spoons for the day. I should have just written the rest of the day off and done nothing else.

Katy and I decided to go run an errand anyway because we could turn it into a nice relaxing bike ride, which honestly sounded pretty appealing. Unfortunately, the errand went sideways and resulted in me having to spend another hour on the phone putting out another urgent fire.

I've done what needed to be done, but I know I'm going to pay a heavy price for overtaxing my system like that. The spoon tax is real.

Turns out I've been pruning my #BorgBackup archives wrong. There's a second step involved that actually deletes the "removed" data rather than just (presumably) removing the refrences to that data from the index. While I knew about this second step, I assumed that it was like how it works when you delete a file: the data technically remains intact, but gets overwritten by subsequent writes. Apparently I was wrong about this. I've been pruning—but not compacting—my daily backups monthly for years.

Long story short: I just spent an entire day compacting my backups. My backup storage just went from 71% full to 38%.

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.