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.
No, that’s not the topic. The topic is ads being placed in the fediverse in a way only defederation could block. Even if Meta silently making posts in the name of my favorite organic orange juice advertising Coca-Cola was legal (it’s not), it would be easily solved by simply not following any Threads accounts. Also, Lemmy cannot interact with Threads anyway, so Lemmy servers defederating from Threads is completely pointless.
about them impersonating their own users and using that to push ads through federation.
No, that’s not legal. That would violate copyright, consumer protection, competition laws, and whatnot, at least in the USA and the EU. Mastodon users (!!) must be explicitly aware that a post is an ad, not the brands ticking off an EULA on Threads. Therefore Mastodon users could decide to follow a brand account were products are promoted (just as they can right now if that brand has a regular Mastodon page) but Threads cannot legally impersonate one account on Threads to advertise another account. That’s not a grey area.
I didn’t set a timer but it took me at most a single-digit number of minutes to find documents and announcements about the FTC tightening the rules about deceptive advertising several times throughout the years.
The topic is ads being placed in the fediverse in a way only defederation could block. Even if Meta silently making posts in the name of my favorite organic orange juice advertising Coca-Cola was legal (it’s not), it would be easily solved by simply not following any Threads accounts.
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.
Also, Lemmy cannot interact with Threads anyway, so Lemmy servers defederating from Threads is completely pointless.
Irrelevant to what I’m saying.
That would violate copyright, consumer protection, competition laws, and whatnot, at least in the USA and the EU.
Copyright to what? A person’s name? A small string of characters that is a “handle”? None of that is copyrightable.
That would violate copyright, consumer protection, competition laws, and whatnot, at least in the USA and the EU.
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. –
That would violate copyright, vonsumer protection, competition laws, and whatnot, at least in the USA and the EU.
As I previously mentioned, corporate accounts can be excluded to remove running afoul of competition laws.
Mastodon users (!!) must be explicitly aware that a post is an ad, not the brands ticking off an EULA on Threads.
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.
Threads cannot legally impersonate one account on Threads to advertise another account.
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.
Let’s go with your idea of what the topic is for a second
Considering that I’ve replied to another person with my explanation and got very positive feedback, I certainly know better than you. You’re not the person I’ve replied to. You interjected and then tried to educate to me what my comments are about.
have you considered how advertisement posts could appear in search results, hashtags, or the explore section?
Any brand account on a regular Mastodon instance would be the very same.
Or what if they decide to screw with the normal process and artificially inflate the number of boosts and favorites for advertisement posts?
Mastodon doesn’t have an algorithmic timeline, so that would lead to absolutely nothing.
Also, Lemmy cannot interact with Threads anyway, so Lemmy servers defederating from Threads is completely pointless.
Irrelevant to what I’m saying.
Relevant to the comment I’ve initially replied to.
What copyright? Threads users gave it away when they signed up.
Nope.
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.
No, I made several good arguments, you just moved goalposts and declared they don’t matter.
You interjected and then tried to educate to me what my comments are about.
My original comment was a comment. The only reason it continued is because neither of us seem to be content with letting other people be confidently wrong.
Any brand account on a regular Mastodon instance would be the very same.
Now imagine that it comes from a non-brand account that you follow. You have an ad. On your Mastodon instance. Federated by Threads.
Mastodon doesn’t have an algorithmic timeline, so that would lead to absolutely nothing.
Let’s address the elephant in the room: the parts of Mastodon that I previously mentioned but were deemed to be out-of-place goalposts. Here, I even did the research:
Trends use both the boosts and favorites count for calculating scores.
Although it doesn’t solve the issue of ads being propagated in the first place, I will admit that having the option for manual admin approval is a nice mitigation, though.
Relevant to the comment I’ve initially replied to.
After coming back and fully re-reading this thread again, I’ll give you that.
What copyright? Threads users gave it away when they signed up.
Nope.
Let me rephrase that without hyperbole: you gave them the ability to do what they want to do with your copyright.
“Very broad copyright license on your content.”
“You maintain ownership of your content.”
No, I made several good arguments, you just moved goalposts and declared they don’t matter.
Let’s see…
Still no reason to defederate, huh?
You:
No, it’s not. Ads can’t federate. Threads has no control over my Mastodon feed and Lemmy can’t interact with Threads at all. Following Threads accounts from Mastodon is effectively an ad blocker.
Neither of us:
How do you know that Threads won’t inject ads as posts?
You:
Ads in Instagram are posts from accounts you don’t follow. Threads can’t make you follow promotion accounts you don’t want to follow.
Me:
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.
You are correct that ads on Instagram are posts.
You are also correct that the federation protocol can’t force you to follow users, and that ads won’t show up in your feed unless you are subscribed to the user. You did not answer the user’s question asking if you knew that “threads won’t inject ads as posts.”
You are not correct in that “ads can’t federate”. I pointed out that the federation protocol doesn’t prevent an instance owner (Threads) from sending out ads as posts under any account hosted under their domain.
That was a technical argument for how they could actually federate ads if they wanted to. The discussion should have ended there while it was about the extent of what they could do to overreach in the fediverse. You were the one who decided to move the goalposts by bringing copyright and advertising standards into it.
My follow-up comments with shoddily-explained examples of how Meta could try weaseling out of consequences by abusing terms of services and pedantically following the letter of the law over of the spirit evidently isn’t a successful way to communicate a point. All of that crap was to say that Meta does not respect the law when money is to be made. They have been fined for prioritizing ad money over data collection laws and even antitrust laws. They even got away with blaming their advertising platform approving and nearly publishing COVID-19 misinformation ads on automation. If they were to consider the potential profits to outweigh the risks from getting fined, they would do it and try to lawyer their way out of being held accountable.
If the direction of our discussion were to continue, you’re going to disagree with me, I’m going to disagree with you, and we’ll both come out of this wasting more time. I would prefer that neither of us waste more time on this, though.
As long as you are, I’m more than happy to call this a misunderstanding over whether Theads “can” or “will” use ActivityPub to distribute ads turned petty disagreement and move on. Agreed?
From my previous comment:
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.
No, that’s not the topic. The topic is ads being placed in the fediverse in a way only defederation could block. Even if Meta silently making posts in the name of my favorite organic orange juice advertising Coca-Cola was legal (it’s not), it would be easily solved by simply not following any Threads accounts. Also, Lemmy cannot interact with Threads anyway, so Lemmy servers defederating from Threads is completely pointless.
No, that’s not legal. That would violate copyright, consumer protection, competition laws, and whatnot, at least in the USA and the EU. Mastodon users (!!) must be explicitly aware that a post is an ad, not the brands ticking off an EULA on Threads. Therefore Mastodon users could decide to follow a brand account were products are promoted (just as they can right now if that brand has a regular Mastodon page) but Threads cannot legally impersonate one account on Threads to advertise another account. That’s not a grey area.
I didn’t set a timer but it took me at most a single-digit number of minutes to find documents and announcements about the FTC tightening the rules about deceptive advertising several times throughout the years.
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.
Considering that I’ve replied to another person with my explanation and got very positive feedback, I certainly know better than you. You’re not the person I’ve replied to. You interjected and then tried to educate to me what my comments are about.
Any brand account on a regular Mastodon instance would be the very same.
Mastodon doesn’t have an algorithmic timeline, so that would lead to absolutely nothing.
Relevant to the comment I’ve initially replied to.
Nope.
No, I made several good arguments, you just moved goalposts and declared they don’t matter.
My original comment was a comment. The only reason it continued is because neither of us seem to be content with letting other people be confidently wrong.
Now imagine that it comes from a non-brand account that you follow. You have an ad. On your Mastodon instance. Federated by Threads.
Let’s address the elephant in the room: the parts of Mastodon that I previously mentioned but were deemed to be out-of-place goalposts. Here, I even did the research:
https://github.com/mastodon/mastodon/blob/27965ce5edff20db2de1dd233c88f8393bb0da0b/app/models/trends/statuses.rb#L103
Trends use both the boosts and favorites count for calculating scores.
Although it doesn’t solve the issue of ads being propagated in the first place, I will admit that having the option for manual admin approval is a nice mitigation, though.
After coming back and fully re-reading this thread again, I’ll give you that.
Let me rephrase that without hyperbole: you gave them the ability to do what they want to do with your copyright.
https://edit.tosdr.org/services/219
“Very broad copyright license on your content.” “You maintain ownership of your content.”
Let’s see…
You are correct that ads on Instagram are posts.
You are also correct that the federation protocol can’t force you to follow users, and that ads won’t show up in your feed unless you are subscribed to the user. You did not answer the user’s question asking if you knew that “threads won’t inject ads as posts.”
You are not correct in that “ads can’t federate”. I pointed out that the federation protocol doesn’t prevent an instance owner (Threads) from sending out ads as posts under any account hosted under their domain.
That was a technical argument for how they could actually federate ads if they wanted to. The discussion should have ended there while it was about the extent of what they could do to overreach in the fediverse. You were the one who decided to move the goalposts by bringing copyright and advertising standards into it.
My follow-up comments with shoddily-explained examples of how Meta could try weaseling out of consequences by abusing terms of services and pedantically following the letter of the law over of the spirit evidently isn’t a successful way to communicate a point. All of that crap was to say that Meta does not respect the law when money is to be made. They have been fined for prioritizing ad money over data collection laws and even antitrust laws. They even got away with blaming their advertising platform approving and nearly publishing COVID-19 misinformation ads on automation. If they were to consider the potential profits to outweigh the risks from getting fined, they would do it and try to lawyer their way out of being held accountable.
If the direction of our discussion were to continue, you’re going to disagree with me, I’m going to disagree with you, and we’ll both come out of this wasting more time. I would prefer that neither of us waste more time on this, though.
As long as you are, I’m more than happy to call this a misunderstanding over whether Theads “can” or “will” use ActivityPub to distribute ads turned petty disagreement and move on. Agreed?