And we are back online! The performance will be decreased for a couple of hours while catching up on the fediverse. #mastoadmin
The rule change has mostly been a bit of changed wording, but we have also added a section of "best practices".
You can find the complete instance rules at https://chaos.social/about/more as always, and you can look at the changeset here: https://github.com/chaossocial/about/commit/73d7248006523e98c4affe0fdf37333414c378e7
At the same time, I modified our instance rules a bit to include a separation between rules and "best practices"/behaviour guidelines.
I'll probably merge the changes tomorrow, but you can see the changeset here: https://github.com/chaossocial/about/pull/13
Wir haben aufgeschrieben, wie es derzeit um die Finanzen von chaos.social steht: https://blog.chaos.social/2020/01/26/sparschwein-bericht-2020.html
Kein Grund zur Sorge, das ist nur ein Transparenzpost und ein großes DANKE an alle, die uns so großartig unterstützen! Ihr seid super!
We have published a write-up of the current state of chaos.social, particularly our finances: https://blog.chaos.social/2020/01/26/piggybank-report-2020.html
There's no cause for alarm – this is just a transparency post, and a big THANK YOU to everybody who is supporting us. You're the best!
Oh and here are some metrics. That's the reason why we decided that the problem is less urgent and doesn't need immediate attention.
We are aware that there are some (short) outages over the last weeks. We want to inform you that we are working on the problem.
Currently we observe two kinds of outages. Multiple short outages resulting in 502 errors and two crashes of our hardware.
We had an intense time on congress helping to create a great event, but this also lead to less time to look into problems here. Also we needed some recovery time after congress. So please be patient. We are still doing this in our spare time.
While we are at it: Please consider donating to support chaos.social. Due to the increased demand and declining donations, we are currently covering ~40%-50% of the instance costs ourselves. We're preparing a more detailed report.
There will be a longer downtime (approx. 2-3 hours) of our instance chaos.social this evening starting at 19:00 CET (UTC+1). We need to move the system to a new host with more storage. #mastoadmin
Mastodon v3.0.0 brought us an admin UI option to disable search engine indexing for all accounts that haven't set it manually before. We have enabled this setting on chaos.social.
We think opt-in is better than opt-out so if you want your toots to be indexed by search engine providers in the future please review your settings. #mastoadmin
We as operators of chaos.social also wanted to set a sign for the world wide climate strike and added a custom mastodon art to our instance. The mastodon told us that they know quite well the consequences of climate change. So we gave them a sign to demonstrate together with us :) #FridaysForFuture #ClimateStrike
If you want to add it to your instance too, you could find the SVG here: https://github.com/chaossocial/custom/blob/master/images/mastodon-climate.svg
Hey...sorry for the short downtime since 06:20 this morning. We run out of storage faster than expected. We fixed the problem for the next time and the instance is catching up but we will need another longer downtime in the next few weeks to move the system to a bigger host. We will announce this separately. #mastoadmin
We've just blocked the nazi instances at *.halle-leaks.de
We've decided to silence the instance humblr.social because of a massive amount of not tagged NSFW contend. Silence means you can still follow them but the are not visible in the federated timeline anymore. #mastoadmin