Finally we know why Threads doesn't federate with metalhead.club: We are "violating the community guidelines or terms of use!"
-
Finally we know why Threads doesn't federate with metalhead.club: We are "violating the community guidelines or terms of use!"
I can't do it anymore! I CAN'T DO IT ANYMORE! *hysterical laughter*
Well that ends the issue. I haven't gotten a response even after many good-natured attempts to contact threads/meta and I'm tired of begging. If they don't like it, let them be without us. Too bad (because one or the other user would probably have read threads), but that's not going to happen.
-
@thomas where do you see the full list of servers they ban?
-
Are they blocking Mastodon instances that have Authorized Fetch enabled. I nearly recall that violates their policy. My recall could be wrong. If so, and you have it enabled, that could be a reason.
-
I'm pretty sure they're not blocking all instances with Authorized Fetch -- indieweb.social has AF enabled and it's not on their list.
@[email protected] @[email protected] -
@jdp23 @thomas @paul doesnβt authorized fetch have 2 different levels? like one is where there is still a public timeline, posts can still be looked at on their own page (like my instance has) and the other level is where these things are no longer possible and you can only access posts through a fedi interface. since threads clearly blocks instances for not having a publicly visible feeds, that would mean they automatically have to block every instance that has this level of authorized fetch active
-
Good points. Threads does indeed block everybody who doesn't have a public timeline accessible (although they include that in their description, so that's not what's going on with metalhead.club).
@[email protected] @[email protected]