#Tag
Log in
BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp 3 days ago
BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp 3 days ago
Stefano Marinelli
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp last week
BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp last week

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

BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp last week
BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp last week
BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp 2 months ago
Stefano Marinelli
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp 2 months ago

Quick status update regarding usa02.bsd.cafe.

Yesterday, at 16:11 my monitoring reported the server as unreachable.
The provider’s console indicated urgent maintenance on the physical host, and the VM was not manageable. The console could be opened, but the system was entirely unresponsive.

A support ticket was opened at 21:00. There was no reply until the following morning.

After posting an update on Mastodon, I was contacted and asked for the ticket number. Once provided, the server became reachable through the console again, although still disconnected from the network. It appeared to have been running during the outage, just isolated.

Several tests were performed, but network connectivity did not return.

At 10:56 support replied stating that the VM had been relocated to a new node. In practice it remained offline, and I reported this.
Around 11:10 they accessed the console; I joined as well. A hard reboot was performed, leading to a filesystem check.

At 11:15 the server became reachable again. Support then confirmed they had identified and resolved the underlying issue.

It took more effort than it should have to get this resolved, and the whole process was far from smooth. Still, this is the first time anything like this has happened in many years, and my trust remains.

#BSDCafe #BSDCafeUpdates #BSDCafeServices

BSD Cafe Announcements
BSD Cafe Announcements
@announcements@mastodon.bsd.cafe  ·  activity timestamp 2 months ago
Stefano Marinelli
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp 2 months ago

Quick status update regarding usa02.bsd.cafe.

Yesterday, at 16:11 my monitoring reported the server as unreachable.
The provider’s console indicated urgent maintenance on the physical host, and the VM was not manageable. The console could be opened, but the system was entirely unresponsive.

A support ticket was opened at 21:00. There was no reply until the following morning.

After posting an update on Mastodon, I was contacted and asked for the ticket number. Once provided, the server became reachable through the console again, although still disconnected from the network. It appeared to have been running during the outage, just isolated.

Several tests were performed, but network connectivity did not return.

At 10:56 support replied stating that the VM had been relocated to a new node. In practice it remained offline, and I reported this.
Around 11:10 they accessed the console; I joined as well. A hard reboot was performed, leading to a filesystem check.

At 11:15 the server became reachable again. Support then confirmed they had identified and resolved the underlying issue.

It took more effort than it should have to get this resolved, and the whole process was far from smooth. Still, this is the first time anything like this has happened in many years, and my trust remains.

#BSDCafe #BSDCafeUpdates #BSDCafeServices

Stefano Marinelli
Stefano Marinelli
@stefano@mastodon.bsd.cafe  ·  activity timestamp 2 months ago