Important announcement, especially for BSD Cafe friends who don’t have a local account.
-
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
@announcements Careful, considered admin work, transparently explained.
I love it, even though I’m not affected. This is one of the things that make the Fedi special.
-
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
@announcements Plus, the wording makes it look like instances are complicit to the "other servers| postings, at least by one your users following such accounts...
"These are the most recent public posts from people on the fediverse that people on oldfriends.live follow."
#Mastodon really needs to change the wording on this because this is not true. These are posts from Fediverse servers that my instance knows about. 99.9999999999999% of the people posting in "other servers" are not followed by anyone on my self-hosted instance.
-
R AodeRelay shared this topic on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login