Pinned toot

We've opened the invite system again – users on chaos.social can generate invites for their friends at chaos.social/invites

To avoid a suden onslaught on the instance – PLEASE only generate invites for ONE PERSON AT A TIME.
Please don't generate invites that allow many or unlimited people to sign up – slow, organic growth works best for a community instance like ours.

Pinned toot

Wir haben aufgeschrieben, wie sich chaos.social bislang finanziert, und wie wir uns die Zukunft vorstellen.
tl;dr: So ihr spenden wollt, tut es vorerst an Leahs PayPal-Account unter paypal.me/leahoswald.

blog.chaos.social/2018/08/20/s
--
We wrote a blog post about how chaos.social finances worked so far, and how we want to handle things in the future:
tl;dr: For now, donations should go to Leah's PayPal at paypal.me/leahoswald

blog.chaos.social/2018/08/20/p

Sorry for the short downtime. We had to do some small maintenance.

We are already in a complicated situation. The situation in the USA is getting even more complicated now. To protect the mental health of all of us, please use CWs or at least the hashtag or if you toot about the ongoing election! Thank you!

FYI: We've just moderated most of the report backlog for the last two weeks. In this case we will not inform you individually about the actions taken.

Normally the nginx should be automatically reloaded properly on a certificate change. This time this mechanism failed. Therefore we where without a valid certificate for the last 3 hours. Sorry for the downtime ;)

We just updated chaos.social to v3.1.3. Sorry for the short downtime.

We could located the error in a driver issue with the Intel network card. We think this issue was also the cause for previous crashes. We have installed a workaround that should mitigate the problem while waiting for a upstream patch in the kernel.

Show thread

We had a system crash and a downtime of 30 minutes. We are currently debugging the cause.

We had an outage of 30 minutes. The host running chaos.social crashed. Manuell reset helped to fix it. We also used the downtime to upgrade the system.

We now know what the cause of the 502 errors was. The backends of the mastodon application bind only to ipv4 by default. We used the name localhost on the nginx reverse proxy to refer to the backend. This, as usual first resolves to ::1 the local ipv6 address. As there is no backend listening under this address we need to fallback to ipv4 and we think this was to slow in some cases leading to the user facing 502 error.

Show thread

We got no feedback on any 502 errors in the last 11 days so it looks like the problem is finally solved 🎉

The only problem is, we changed two things. We might change one back for a short period of time in the next few days to check which of both lead to the problem. So if you experience 502 errors it will only be for a short time but please still report them.

Show thread
@ordnung boosted

Many of you already do it but we want to ask and urge everyone on chaos.social and of course on other instances to add a CW (corona or covid19) to *all* toots in a relation with the corona virus pandemic. Additionally adding the hashtag is also a good idea to filter the toots.

The topic is important but there are a lot of people that are for example in a risk group and really don't want to hear every bad joke or every new headline. Help them and be a nice citizen of this instance.

Many of you already do it but we want to ask and urge everyone on chaos.social and of course on other instances to add a CW (corona or covid19) to *all* toots in a relation with the corona virus pandemic. Additionally adding the hashtag is also a good idea to filter the toots.

The topic is important but there are a lot of people that are for example in a risk group and really don't want to hear every bad joke or every new headline. Help them and be a nice citizen of this instance.

We've changed some parameters regarding the increasing number of 502 errors we see on the instance. We would kindly ask you to report us such 502 errors in the next few days with the exact time you see them.

@ordnung boosted

Some instances on the Fediverse offer full-text search of statuses (not just self-authored ones), and I'm wondering how to deal with that. I'm tempted to block every instance doing so, because the current expectation of our users is that their statuses will not be full-text searchable by strangers.

Opinions? What should we do with instances offering full-text search for all statuses?

@ordnung boosted

⚠️ #Mastodon v3.1.2 is out with an important security fix:

github.com/tootsuite/mastodon/

Likewise, v3.0.2 and v2.9.4 have been released to port this fix to older versions.

We've just upgraded chaos.social to mastodon v3.1.2. This was a security release so there are no functional changes.

And we are back with nearly no downtime and are now running mastodon v3.1.1.

For all the changes see: github.com/tootsuite/mastodon/

Show thread

There will be a short downtime in the next 30 minutes to upgrade chaos.social to mastodon 3.1.1.

Show more
chaos.social

chaos.social – a Fediverse instance for & by the Chaos community