I’ve previously mentioned having trouble managing BlendIT, but I’m going to give it another try.

Tomorrow, 5th February, I’ll be running an experimental update.

I managed to compile everything in my test jail, but we’ll have to see if the actual upgrade succeeds.

I will be taking the service down for a few hours - exact timing depends on my schedule - but since usage is low, it shouldn't be an issue.

I will post updates here and on https://status.bsd.cafe.

#BSDCafe #BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements #BlendIT

I’ve previously mentioned having trouble managing BlendIT, but I’m going to give it another try.

Tomorrow, 5th February, I’ll be running an experimental update.

I managed to compile everything in my test jail, but we’ll have to see if the actual upgrade succeeds.

I will be taking the service down for a few hours - exact timing depends on my schedule - but since usage is low, it shouldn't be an issue.

I will post updates here and on https://status.bsd.cafe.

#BSDCafe #BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements #BlendIT

The #BSDCafe #Mastodon instance has been upgraded to v.4.5.6

#BSDCafeUpdates #BSDCafeServices #BSDCafeAnnouncements #BSDCafeInstance

The #BSDCafe #Mastodon instance has been upgraded to v.4.5.6

#BSDCafeUpdates #BSDCafeServices #BSDCafeAnnouncements #BSDCafeInstance

Important announcement, especially for BSD Cafe friends who don’t have a local account.

Over the past few days I noticed that, when browsing some public pages on our Mastodon server (especially the federated timeline, meaning posts coming from other instances as well), certain content could appear without a CW and in some cases it was pornographic, illegal, or generally not suitable for a general audience.
The problem is that this was visible even to users who were not logged in, which effectively made BSD Cafe a gateway to that content. Also, some media files are cached on our server, so it could look like BSD Cafe is the source of it.

For this reason I had to make a decision: I have disabled the ability for non-logged-in visitors to view posts coming from other instances.
This way, anyone visiting BSD Cafe without an account will only see BSD Cafe local content, helping us avoid potential issues, including legal ones.
Some of you (from other instances) thought you had been blocked because you could no longer see your posts here, but that is not the case: your posts are still fully visible to local users, as usual.

I have also re-enabled (at least for now) hashtag browsing, since BSD Cafe is one of the most well federated instances for BSD-related content and it would be a shame to lose that. However, I may reconsider this decision if it leads to problems.

Let me know if you notice anything unusual.

#BSDCafe #BSDCafeUpdates #BSDCafeAnnouncements #BSDCafeServices #Mastodon #Fediverse

Important announcement, especially for BSD Cafe friends who don’t have a local account.

Over the past few days I noticed that, when browsing some public pages on our Mastodon server (especially the federated timeline, meaning posts coming from other instances as well), certain content could appear without a CW and in some cases it was pornographic, illegal, or generally not suitable for a general audience.
The problem is that this was visible even to users who were not logged in, which effectively made BSD Cafe a gateway to that content. Also, some media files are cached on our server, so it could look like BSD Cafe is the source of it.

For this reason I had to make a decision: I have disabled the ability for non-logged-in visitors to view posts coming from other instances.
This way, anyone visiting BSD Cafe without an account will only see BSD Cafe local content, helping us avoid potential issues, including legal ones.
Some of you (from other instances) thought you had been blocked because you could no longer see your posts here, but that is not the case: your posts are still fully visible to local users, as usual.

I have also re-enabled (at least for now) hashtag browsing, since BSD Cafe is one of the most well federated instances for BSD-related content and it would be a shame to lose that. However, I may reconsider this decision if it leads to problems.

Let me know if you notice anything unusual.

#BSDCafe #BSDCafeUpdates #BSDCafeAnnouncements #BSDCafeServices #Mastodon #Fediverse

The #BSDCafe #snac instance has been upgraded to 2.89

#BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #snac instance has been upgraded to 2.89

#BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Mastodon instances have been upgraded to v4.5.5

#BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Mastodon instances have been upgraded to v4.5.5

#BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Mastodon instances have been upgraded to v4.5.3

#BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Mastodon instances have been upgraded to v4.5.3

#BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #snac instance has been upgraded to 2.85

#BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #snac instance has been upgraded to 2.85

#BSDCafeServices #BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Forgejo instance (brew) has been upgraded to v11.0.8

#BSDCafeUpdates #BSDCafeServices #BSDCafeAnnouncements

The #BSDCafe #Forgejo instance (brew) has been upgraded to v11.0.8

#BSDCafeUpdates #BSDCafeServices #BSDCafeAnnouncements

The #BSDCafe #Forgejo instance ("brew") is constantly under "attack" by scrapers. It was killing the performance and making the entire BSD Cafe slower.

I've added some limits and workarounds - but you could see, from time to time, some 429 errors.

#BSDCafeUpdates #BSDCafeAnnouncements

The #BSDCafe #Forgejo instance ("brew") is constantly under "attack" by scrapers. It was killing the performance and making the entire BSD Cafe slower.

I've added some limits and workarounds - but you could see, from time to time, some 429 errors.

#BSDCafeUpdates #BSDCafeAnnouncements

I've just incremented the number of streaming and puma processes so Mastodon should be more responsive and show less 500 errors.

It was already quite fast and the 500 errors were rare, but this won't harm

#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #Mastodon

I've just incremented the number of streaming and puma processes so Mastodon should be more responsive and show less 500 errors.

It was already quite fast and the 500 errors were rare, but this won't harm

#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #Mastodon