Yes, I am more than aware that the fediverse can see Threads profiles and posts. However, adding to what T said:
Federation is an optional feature, and does not account for profiles which have it disabled. So those simply won't pop up on Mastodon.
Threads has not been received well by a huge chunk of the fediverse, including myself, due to Meta essentially collecting data from users outside of Threads without their explicit consent. As such, many instances have defederated from Threads.
Federation on Threads is only available in certain regions. To be exact, if you're a Threads user, you cannot enable federation unless you live in the US, Canada, or Japan.
It may be an option for you, but it really depends on the instance your account is in, and who do you want to follow. Shoelace, on the other hand, would only be limited by the capabilities from unauthenticated API endpoints Meta provides, but any public post or profile can be opened.
I'm prepared to receive intimidation letters at my door! Thankfully I live in a country (Chile. Can't really hide it, since you can geolocate my server and see that indeed it's hosted there) where it wouldn't be very much valuable for [m3t4] to sue me, since they haven't signed with a law firm here from what I can see. It would be much easier for them to just try and keep their platform closed off, which would mean they kill the open aspect of the platform. It would also be a win for the Fediverse, who has not received it well. Heck, I don't like it as well.
It's not. This essentially proxies content from Threads. These kinds of websites are generally nicknamed alternative frontends. It's basically the equivalent of Invidious, Bibliogram, or Libreddit (RIP), but for Threads.
The primary use case is seeing content from the platform in a privacy-respecting way. As in, no Facebook trackers, no heavy JavaScript, plain HTML and CSS. For example, you can use it if someone sends you a post in Threads.
Unfortunately no :(, and it's hard there'll be one soon. Facebook is much more closed off than Instagram or Threads. They really beg for you to have an account, and if someone were to start an alternative frontend which uses burner accounts, they would get blocked immediately AND lose in court, since that bleeds into computer fraud and abuse laws, similar to how Barinsta got taken down.
I think you're much better off getting an account with an aliased email address and using a plugin like Facebook Container to access those groups. Add a good proxy/VPN to this, and it'll be virtually impossible to link it back to anything else you do online. That's what I've done, since I use Facebook Marketplace to buy things from time to time, and it has worked well, with me only getting suggestions from Facebook pages I've already visited within that account, and not from any other website I visit outside of it.
However, with Mastodon you have to deal with Meta collecting data from your profile, including any relations such as likes and follows. Furthermore, not all accounts from Threads have Fediverse integration enabled, and those who do are limited to the US, Canada, and Japan. This is more anonymous and functional than that. I also plan to add RSS support soon, to have an equivalent to following someone.
I know that. I think the problem is, specifically as it pertains to Threads, is that "alternative frontend" can mean different things. Moshidon is an "alternative frontend" for Mastodon. The backend is all the same. So if I were to be advertising this project, I would be making sure to make that distinction somehow. Probably by including "private" somewhere in the title.
Regardless, does this allow you to generate a personal feed or is it just supposed to be a redirect like Nitter?
You're right. I was calling it a private frontend when referring to it beforehand, and the repo description states it, but I looked at other projects and they used the phrase "alternative", so I switched to it, since that's the common term.
For now it doesn't have personal feed functionality, but if a lot of people want that I may be able to implement it similarly to how CloudTube does. As in, generate a secret, store it in a cookie, and from there save user data. For now though, I want to prioritize RSS subscriptions.
sr.ht
Hot