Forest @forestjohnson@pixie.town

This style of client and server application has its roots in things like `inetd` (internet daemon) and CGI (common gateway interface). Benno Rice explains in a section of his excellent presentation covering the history of linux and unix:

https://video.strongthany.cc/watch?v=o_AIw9bGogo&t=4m58s

> [Then things changed...] the internet happened. That inetd model was great when [you were dealing with a small amount of stuff going on], like, [only a few users would have telnet connections] ...The web looked like it would work that way too, and then it became really really popular. And so you end up with situations where forking off a process to handle every single connection doesn't really scale that well.

Many Mastodon server users and admins have mentioned that the load from all the new users is causing a strain on the system -- large outbound queues, delays on messages, slow page load times, etc.

The good news is that these problems don't have to be solved by buying a more powerful computer.

The Mastodon software uses an old (circa 90s and earlier) way of organizing its code, which I like to call "one-thread-per-request with blocking IO"

One of them is GoToSocial, which I see as a dark horse poised to surpass Mastodon and become the best general purpose Fediverse server implementation.

https://nlnet.nl/project/GoToSocial/

Congrats to everyone who has worked incredibly hard to make that project a reality!

Look at all the cool projects that NLNet is funding right now !!! 😮​

https://nlnet.nl/project/current.html

You know what, I'm realizing that maybe the correct implementation for a fedi client has **a freakin <em>URL BAR</em>** at the top o' the page like its its own browser

12k new accounts in the last hour

I created an account for my dogs to try out pixelfed: @fedipugs

So far its been a bit rough (no video support, hyperlinks get broken 🪦)

But if you like cute pet pictures maybe it could be worth a follow, I'll try to post when I can and occasionally maybe repost older stuff from the instagram that my partner made in the past.

```
Updating crates.io index
Fetch [===================> ] 82.56%, (163401/213323) resolving deltas
```

Ok, tinygo is definitely not stable enough for this, moving on to trying rust instead https://docs.rs/age/latest/age/ 👀

my co-streamer is with me today 🙂 🐶​

From yesterday: research into related memory leak here: ​https://github.com/tinygo-org/tinygo/issues/1140#issuecomment-1314608377

Streaming again, getting to work on running FiloSottile/age to run in the web browsa (compile golang to WASM with tinygo compiler)

music rn: 🎸🎺 Less Than Jake 🧨🍺

https://stream.sequentialread.com/

I've no idea what a subtoot is 🐘​

streaming again today https://stream.sequentialread.com/

music: 🧪🏠 Goop House 🪴👽