I believe the other platforms do it individualy by post so u as a user can choose. I reccon this is a better implementation than instance wide but i suppose an instance coild have a default.
Comment on [Duscussion] Post licening to kneecap threads putting ads next to our content.
AdamEatsAss@lemmy.world 10 months agoIf they’re trying to profit off of content on instances they don’t have licensing to them yes, they cannot steal that content. We would want instance wide licensing that would be attached to each post that explicitly states the content cannot be used alongside ads to generate revenue. Some instances may choose not to have this licensing so their content could be used with ads, but it would prevent companies from stealing content posted by people who don’t want this. The value in any social media is the user base, the cost of ad space goes up the more people use the social media, to get users you need engaging new content all the time, with the fideverse anyone can pull content and display it on their instance, some users don’t want to create the content that someone else uses to make money.
muntedcrocodile@lemmy.world 10 months ago
otter@lemmy.ca 10 months ago
Instance default makes sense
Most users won’t mess with settings and details. Then if a user wants, they can select from a specific set of licenses (with simple language explanations for what they mean)
muntedcrocodile@lemmy.world 10 months ago
Exactly the implementation i was invisioning.
ethan@lemmy.world 10 months ago
Creating a paid or ad-supported client app for a website isn’t profiting off of content, it’s profiting off of the user’s desire for a better mobile experience. There’s no ‘stealing’, the developer never has access to nor purports to own any of the content themselves.
That said, any client apps that run ads is dumb and will fail miserably. It’s awful for UX. Just so long as client apps can be monetized in other ways I think it’s fine to adopt a license that prohibits specifically ads.
muntedcrocodile@lemmy.world 10 months ago
So we need something more than a ccbync to prevent ads being put next to content?