If they’re still allowed on the platform to speak their mind amongst their ilk, doesn’t that just create an echo chamber of idiots? Assuming they stay instead of leaving after their fe-fes get hurt, of course.
If they’re still allowed on the platform to speak their mind amongst their ilk, doesn’t that just create an echo chamber of idiots? Assuming they stay instead of leaving after their fe-fes get hurt, of course.
I would say quitting twitter to join bluesky is more like quitting
mentholsPCP to smoke regular cigarettes
Fixed that for you.
For those who are unfamiliar,
PCP may cause hallucinations, distorted perceptions of sounds, and violent behavior.
From my previous comment:
selecting threads-hosted accounts
ActivityPub literally will not let them impersonate accounts from other instances. That much should be obvious. The topic is about them impersonating their own users and using that to push ads through federation.
identity fraud
I’m sure they could find some way to have the terms of service agreement include a paragraph on how a handle is the property of Meta and not a user identity.
My favorite fair trade drink endorsing Coca-Cola.
Business accounts can be exempted from injected advertising.
Without the ads being clearly separated as required by many jurisdictions.
Post the ad as an image attachment and put the advertising disclaimer within the image? There’s a lot of ways they can make an ad disguised as a post, and not all of them are as easy to filter out as a quick text search.
Not targeted advertising in any way.
If @OutdoorsyOdin posts content about hiking and mountain climbing, you can make a reasonable guess that the subscribers are going to be interested in that kind of activity. It’s not targeted to a specific user, but it’s good enough to serve ads targeted at specific lifestyles or hobbies.
Users could just opt not to follow Threads accounts.
Exactly.
Anyways, this whole thing is to show that they could try to enshittify their fediverse integration if they really wanted to. There’s no technological barrier preventing them from sending ads through ActivityPub.
Depending on where they want to sit in the scumbag chart, there’s no technical barrier stopping them from selecting threads-hosted accounts with high metrics and injecting advertisement posts under their handles.
TypeScript isn’t terrible. It’s extra work to set up, but it makes JavaScript codebases somewhat more maintainable.
And at least garbage let you make international calls with the money you put into it. Nitro-saturated sewer water gives you what—a bit of extra bandwidth utilization, 2 free tokens to prove you’re above the poverty line, and discounts on paid cosmetics?
Let’s go with your idea of what the topic is for a second: have you considered how advertisement posts could appear in search results, hashtags, or the explore section? Or what if they decide to screw with the normal process and artificially inflate the number of boosts and favorites for advertisement posts? Okay, the solution is to simply have your instance users refrain from following any Threads accounts so the posts don’t show up anywhere—which is effectively defederation.
Irrelevant to what I’m saying.
Copyright to what? A person’s name? A small string of characters that is a “handle”? None of that is copyrightable.
Doot Doot @SomePerson@example — 4h
Looking for gifts in time for the holiday season? Head on down to Best Buy to pick up some amazing deals on Black Friday!
– This is an advertisement shown to you by Meta. Click here for more info. –
As I previously mentioned, corporate accounts can be excluded to remove running afoul of competition laws.
As with my example toot above, that took all of 15 words. They don’t need to be deceptive about what is or isn’t an advertisement to push that shit through the ActivityPub protocol.
Your whole argument is predicated on the idea that a (personal) account on Threads is either owned by its creator, or is associated with a trademark. Furthermore, there are a number of different approaches they could take to argue that the ActivityPub support provides access to a feed of content, and not an individual identity.
In any case, you’re repeatedly glossing over the fact that my original point was to say there isn’t a way to prevent it AT THE PROTOCOL LEVEL.