order @order@nerdculture.de

Dear users on https://nerdculture.de,

this is the new account that will be used to spread information regarding the server itself, like upgrades, issues, maintenance, etc...

So please keep this account in your contact list.

PS: Welcome to all new users!

Reboot finished, everything should be back to normal.

Starting the reboot process...

Today (late afternoon/early evening CEST) there will be a server reboot to install some security updates.

Expect some downtime (maybe 30 mins or so).
There will be short notice some minutes before the reboot, though...

We're back on track... service is restored with more storage space... sorry for the long downtime...

There wil be some downtime today, because I need to extend the storage for Mastodon.

There were some maintenance work over the weekend that resulted in >125k backlogged jobs.

I've increased the number of database connections from 25 to 100. The backlog is now clearing up step by step.

Reboot done, everything should be back to normal. If not, please report...

(except that the timeline might be empty. this is a known issue)

Will start to reboot in about 5 min...

This evenening I'll reboot the server. Expect some downtime.

There will be a short notice right before going down...

Ok, this was weird...

After the upgrade something went wrong and Mastodon didn't work any more over here.

It took me a while fiddling around with errors, reinstalling ruby, bundle install and such things.

It looked similar to https://github.com/mastodon/mastodon/issues/15751 but I'm still unsure if I hit that issue.

However, Mastodon seems to run again now and I'm sorry for the downtime.

I'm currently upgrading the server and virtual machines to the new Debian Bullseye.

During the upgrade services might be unavailable for some time, because the service will be stopped by the package management.

Stay tuned!

Some users reported that logging in to XMPP with their username (camelCaseUsername) didn't work. I've updated the authentication script to the current version that includes some checks regarding non-lowercase usernames.

Basically for the XMPP server it doesn't matter, but for the authentication script looking up your usernames it might. So, please report back if you try to use XMPP with your nerdculture.de account, but get authentication errors.

FYI: this week 92 inactive users got deleted. We are now down to 513 users (from >1.1k).

From the-federation.info (yesterday, before deletion):
Users: 604
Last 6 months active users: 604
Last month active users: 396

So, we have now like 80% users being active in past 6 months and 60% monthly active users.

That's quite good. Keep posting! Stay active! :)

FYI: Today about 220 inactive user accounts got deleted by the script. Many more received a notification mail...

From now on the script will run on every Thursday at 8:20 local time (CET/CEST).

The next run will warn users between 6 and 18 months inactivity and will delete all accounts with more than >18 months inactivity.

Ah, I see I need to change the mail text a little bit.. will do that for the next run in about a week...

I've activated a cleanup script that is checking your last login time.
If you haven't logged into Nerdculture.de for more than 6 months, you'll receive a mail.

Accounts that haven't logged in for 24 months will be deleted.

In the end the deletion will be lowered to 7 months so that you'll have 4 weeks to react to the weekly reminder mails.

Deleting unused accounts is a matter of digital hygiene and data protection.

Reminder:

Every Nerdculture user can use XMPP chat with the same credentials - now even with audio/video calls when the client supports this feature, e.g. Conversations on Android.
You can find more information here: https://hookipa.net/nerdculture-xmpp-server/

So get a XMPP client and start communication via XMPP! You can find more information on https://hookipa.net

Reboot finished, everything should work again. If not, please open a ticket at https://support.windfluechter.net/

There are some security updates necessary. This will require a restart of the server.
Hopefully this will take about 15 mins for reboot when initiated...