I can't find the profiles of threads users here on masto.ai, while I can on mastodon.social.
Is that a problem with masto.ai?
I can't find the profiles of threads users here on masto.ai, while I can on mastodon.social.
Is that a problem with masto.ai?
@mg admins probably blocked Threads on the instance. When this happens, it's like the blocked instance doesn't exist.
@mg yes, but it's up to the admins to show or hide the list. Masto.ai's hide. It should be in the bottom of this page: https://masto.ai/about
That's the reason I prefer the main instance (mastodon.social). They are more neutral regarding instance blocking (AFAIK, they only block explicity illegal/toxic ones)
@manualdousuario Wow, that sounds bad. Is there a public blacklist that an instance uses, so I can see what is blocked?
@mg I'm almost sure there are domains blocked by email providers. Fastmail, for instance, blocks new registered domains for clearance (had an issue with a new endeavour in December). They also frown upon .info domains (commonly used for spam). But they are way more careful than Mastodon admins
Btw, users can block instances themselves, on top of admin blocks (which impacts everyone in the instance)
@manualdousuario I'm surprised domain level blocking is a thing at all.
The way I think of ActivityPub is that it is like email. Email is for 1:1 communication and ActivityPub is for n:n communication.
In the email world, I have never encountered domain based blocks. Just user level defaults. So while a mail from domain xzy might go to spam by default, the user can still see it in their spam folder. And decide to move it to their main folder.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.