Show newer
Forest boosted

#GoToSocial 0.3.0 aka Stimky Sloth is out now

github.com/superseriousbusines

This release includes pubic profile pages at last! Migration to the new version is pretty easy, see the release for details.

Have fun with your new profile pages!

Current status: resisting the human instinct to write new database software from scratch

I started making these silly images for mainstream social media platforms when I announce my streams because my friend told me that text-only posts (especially containing links) will be buried automatically by them and its much better to post an image and then post the link as a comment. IDK if this is still true, I think its silly but whatever, when in rome....

stream.sequentialread.com/

Implementing support for serial console access to vms in capsul-flask

🙎🏼‍♂️👨🏿‍🦲 Fracus and Darwin 💿🎚️🎛️💿

I liked the idea of golang's module system (every module is just a url) because it seemed to invite more decentralization in packaging, welp, today I discovered firsthand just how wrong I was: github.com/golang/go/issues/51

Ok, article is updated with several factual accuracy fixes and additional info, and I'm publishing it wider now.

I was looking for an easy-to-read page w/ info on what common features processes have on Mac, Windows, and Linux. I **COULD NOT FIND ANY** on the web.

How the heck did this happen!? At any rate, here's the missing article, just had to write it first.

sequentialread.com/what-is-a-p

I could not find any concise but useful single page descriptions of what a process is and what you can do with a process, so I decided to write my own:

sequentialread.com/what-is-a-p

AHHHH I was wrong turns out it was a typo bug in the matrix version we were using. Updating to matrix-synapse v1.50.2 fixes it.

Show thread

cyberia.club matrix server outage RCA

RCA is that a cyberia.club user was in a 4chan-associated room on matrix.org which was experiencing an extreme volume of hate message spam from a common "chud" server.

Since we had an incomplete block on the offending server / since matrix-synapse's block feature is buggy, this resulted in what appeared to be an ` O(n*m)` number of error messages in our log file, where `n` is the # of spam messages and `m` is the average number of times that federation was attempted for each message. This log spam filled our disk and caused matrix to crash.

insight was gained by creating a histogram of bytes-per-minute in the log file, and by examining the rooms related to those high-volume error messages.

The issue was resolved by "purging" the room via the matrix administration API, (kick all local users, delete, & block) and then manually deleting all `federation_inbound_events_staging` rows associated with that room from the database.

Show older
Pixietown

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