Show newer
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.

Forest boosted
@nolan AIUI, it's basically an architectural issue with Sidekiq. Jobs run synchronously, and one worker thread runs one job, so an in-flight network request blocks an entire worker thread. So you have to put a lot more work into tuning Sidekiq to fully utilize the CPU/network resources.

I strongly suspect anything with green threads (Go, Elixir, etc.) would manage it better, because you can just kick off a green thread for every job and when one suspends while waiting for a network request, the OS thread can just switch to running a different job—so there's always forward progress.

I don't know if those languages have facilities for tuning the runtime based on network bandwidth, but they would at least get you a lot closer to CPU saturation.

w3.org/TR/webtransport/#certif

Finally, after 10,000 years I'm able to open a real socket to anywhere I want, from JS in a web browser! Time to Conquer Earth!

Forest boosted
Forest boosted

If your program does this, it's bad and you should feel bad:

Unknown option -h. Use --help for usage information.

@layerzeroevents err, perhaps bad timing to toot this right now as the server is undergoing and upgrade and down at the moment 😅

Show thread

experimental: follow @layerzeroevents ( calendar.layerze.ro ) for updates on events at Layer Zero, the hackerspace, community tech lab & self-proclaimed kewl-est spot in the midwest

but who will help me carry the wheat to run the server??

I just finished writing a HUGE new blog post, this one elaborates on what I wanna work on next instead of greenhouse

sequentialread.com/federation-

Forest boosted

I need every infosec person to understand that surveillance capitalism is structural, not individual, and we are not going to ethically-consume our way out of it please and thank

It's been many months since I've really seriously worked on any of my projects, in the mean time I had some fairly major life upheavals (getting covid, quitting drinking, starting therapy)

But lately I've finally been slowly getting back into it & reorganizing my thoughts. I think I do want to keep working on creating my own homebrew server oriented software project, but I think I'm going to start over at this point. Greenhouse was a bit of a failure and I think I need to completely redesign.

sequentialread.com/greenhouse-

Show older
Pixietown

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