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.
-
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
Thanks for the heads-up, and for keeping this a welcoming & safe place!
-
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 sounds like a sensible move. 👍
-
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
@stefano This sounds like a very tricky issue to handle. I'm glad I'm the only person on my server, so I don't have to worry about these problems, but I guess a larger instance would have to communicate with the other instances that are the source of the NSFW posts and make sure they remove such content or at least enforce a CW policy, ban accounts, etc., or face defederation from your instance.
-
@stefano This sounds like a very tricky issue to handle. I'm glad I'm the only person on my server, so I don't have to worry about these problems, but I guess a larger instance would have to communicate with the other instances that are the source of the NSFW posts and make sure they remove such content or at least enforce a CW policy, ban accounts, etc., or face defederation from your instance.
@stefano Maybe there's also such a thing as instance-wide blocking of remote accounts, come to think of it, but you might want to just get rid of those users on your own server that subscribe to such things, as the others mentioned.
-
@stefano Maybe there's also such a thing as instance-wide blocking of remote accounts, come to think of it, but you might want to just get rid of those users on your own server that subscribe to such things, as the others mentioned.
@ben sometimes they come in because of boosts. Or legit remote accounts that are hacked and used for malicious activities.
It's impossible to (totally) stop this, unless you stop federating with the bigger instances and lots of smaller ones.
Ciao! Sembra che tu sia interessato a questa conversazione, ma non hai ancora un account.
Stanco di dover scorrere gli stessi post a ogni visita? Quando registri un account, tornerai sempre esattamente dove eri rimasto e potrai scegliere di essere avvisato delle nuove risposte (tramite email o notifica push). Potrai anche salvare segnalibri e votare i post per mostrare il tuo apprezzamento agli altri membri della comunità.
Con il tuo contributo, questo post potrebbe essere ancora migliore 💗
Registrati Accedi