Show newer

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

nlnet.nl/project/current.html

Forest boosted

Can I get some voluntary load testing from #fediverse users lol, please boost/interact with this post.

Forest boosted

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

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
```

Show thread

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

Show thread

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 🧨🍺

stream.sequentialread.com/

Forest boosted

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!

Show thread
Forest boosted
Forest boosted

wow, blocking a list of bad instance is super easy with gotosocial.

Forest boosted

re: dota2 

oops ran out of disk space , back up now

Show thread
Forest boosted

@nolan @shadowfacts

Sorry about my super long winded, poorly written posts before, the sort of silly analogy I can make goes like this:

In the nation of Mastodon Server #42069, there is a postal service. All outgoing mail goes to the postal outbox. Postal workers drive to the outbox, pick up One (1) message, then read the URL address on it and drive to that server to deliver it. Then they drive back to the outbox & repeat. There are only 12 postal workers. Problem is that when folks follower counts start rising they start getting followers from thousands of different servers, and every time they do anything, it puts thousands of messages in that outbox. Poor 12 workers can't deliver them all 1 at a time even if they were superhuman HTTP client machines.

My opinion: remove the limit on # of postal workers completely, or, if you absolutely can't do that, then try to make more than 1 message per mail truck.

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.