companies are capable of operating under different rules in different jurisdictions, they do it all the time. just look at how they handle data in EU due to GDPR vs how they do it everywhere else. I don’t see why this case would be much different.

ok but I’m not in the EU nor is my instance so that doesn’t really apply to me.

deleted by creator

yeah, I see them being posted into their DB (and therefore federated as) a post as if they are a user. they can earmark that post as an ad and properly present it as such in their own platform but anyone federated would see the post as-is.

they could either obfuscate how they mark it as an ad or just not provide that information at all to federating instances.

then I can totally see them claiming they don’t control other instances and can’t be responsible for whether or not the federated ads are presented as such.

they technically could do this by representing ads with posts.

the problem occurs when most of the content comes from Meta (they will likely have the vast majority of Fediverse users). especially if major communities exist on their instance. when meta decides to no longer support fedi integration, those in the fedi are forced to decide between staying with their communities by ditching the fedi and moving to threads or having many of their communities ripped away.

meta will do this at some point as a play to draw users to them, but we can decide if we want to be affected when that comes to pass.

Facebook could just create fake users that post ads as content