```
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/ 👀
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://github.com/mastodon/mastodon/issues/20820
> **USABILITY: init db before configuration is completed causes silent failures / broken instance #20820 **
IMO this is usability bug in mastodon or in the specific mastodon docker container you are using. A configuration issue of this magnitude should trigger massive highly visible error messages, it should trigger the app failing to start.
Querying the db showed:
```
# SELECT username FROM accounts WHERE id=-99;
username
----------------
localhost:3000
```
Which corresponded with the value in the curl
```
"preferredUsername": "localhost:3000",
```
So a quick fix was to connect to psql and run the following update: UPDATE accounts SET username = 'destituent.social' WHERE id=-99;
Now I can toot at my friends over on pixie.town!
Hopefully I didn't burn too many of your CPU cycles @f0x and @forestjohnson thanks!
streaming again today https://stream.sequentialread.com/
music: 🧪🏠 Goop House 🪴👽
dota2
live right now https://stream.sequentialread.com/
@firewally 👀 can I make an account for our dogs
@ashfurrow@masto.ashfurrow.com @nolan
I wish you the best and I hope that in the future you will have time for it, or whatever else you wanna do. I saw a lot of posts from mastodon.technology so thanks for hosting it :)
@nolan @shadowfacts Ok, reading more:
> While fibers provide a delightful interface to work with concurrency the real drawback of Ruby and other GIL (global interpreter lock) based languages is that the execution of threads is limited to only one native thread (per process) at a time.
It sounds like it's similar to Node.js, where one can make multiple-process copies of the application which collaborate.. Not unlike the signup table at a large event where you go to a different queue depending on the first letter of your last name, a-f, line 1 g-o line 2, and p-z line 3, something like that
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero