@pixiekat if they implement mastodon client interface* and do not do something like registration only in their app** you can use Tusky or whatever as threads.com client and do not install official Threads clients (ergo it's permission irrelevant for you).
But why do so if you can use any client with tech.lgbt or any other instance and still communicate with threads.com users?
* I see no reason for facebook to do it
** I have no idea does Threads require addition registration or you can just use facebook/instagram login and password without additional actions (i doubt)
@paul .net?!! what a terrible choice of tld 🤮
.il would have been great: “i” for the needle and “o” for the hole being threaded
@SkyLander everyone can scrape public data from any activity pub instance without such efforts. Old-good webscraping, fake user subscribed to target everyone, relays…
@paul It's going to push ads into Threads users' feeds. These ads will leak out into the wider Fediverse. In fact, Facebook is intending to pay instance admins to accept these ads - which is probably what the infamous NDAs were about.
I definitely see a problem with that.
@[email protected] Based on this post: https://beach.city/@vantablack/110594120842443355 My understanding is that Meta will be pushing ads to users of its’ app/instance, but other instances that federate with Meta will have the option of whether to allow its’ ads or not (for more compensation to the admin). While I’m not opposed to Meta being on the Fediverse in principle (I’d love to be able to interact with my IRL friends and family from here), I personally draw the line at pushing ads to users of instances that federate with them, more specifically, to anyone who isn’t using Meta’s own instance or software. Any instance that allows Meta’s ads to federate should be defederated.
@jerome @paul The gist is that Facebook intends to pay admins of big instances to carry the Facebook ads from the Threads instance.
@[email protected] Based on this post: https://beach.city/@vantablack/110594120842443355 My understanding is that Meta will be pushing ads to users of its’ app/instance, but other instances that federate with Meta will have the option of whether to allow its’ ads or not (for more compensation to the admin). While I’m not opposed to Meta being on the Fediverse in principle (I’d love to be able to interact with my IRL friends and family from here), I personally draw the line at pushing ads to users of instances that federate with them, more specifically, to anyone who isn’t using Meta’s own instance or software. Any instance that allows Meta’s ads to federate should be defederated.
@thomholwerda @paul youre stating it as a fact while it’s a rumor (a very unlikely one!)
If you think the admin of your instance can be bought that way, what would prevent a spyware company to pay them to inject fake toots with spywares in it? Of course our instance owners could be corrupted, but they would be corrupted by a lot worse. That’s why we have groups or non profit to manage them. And you can easily migrate to other instances, which is what prevent a lot of those behaviours.
@paul I think it’s fears of “embrace, extend, extinguish” and generally feeling gross about a company heavily invested in harvesting the world’s user data getting involved.
I don’t think Meta (or most large tech companies) are good stewards of the web as a free and open place, and they have a huge uphill battle to gain acceptance, let alone trust or respect from the community of people that are already on the fediverse.
Since the Fediverse is already pretty open, I would be surprised if harvesting of user data and content is not already in full operation. Any tech bro can read the whole thing, using bots in slow read-only mode, right? Gotta feed that AI monster in their closet...
@[email protected] not meeting with any client devs though…
@paul I think it all depends on Meta’s moderation. If they went to inject ads into their own mastodon client eh. I guess that’s up to them and if people want to subject themselves to that.
Since it’s just basically masto under the hood at least from what my limited reading shows couldn’t any masto client connect to it?