Ive seen that pixelfed and peertube have the ability to add a licence to content. I think this would be great for everyone so we can get ahead of threads and have collective bargaining power when they inevitable put our content between ads.
Heres the pixelfed duscyssion on the issue: https://github.com/pixelfed/pixelfed/issues/13 Here is mastadons discussion: https://github.com/mastodon/mastodon/issues/20079
Im not sure if lemmy has a discussion yet i may create one later if one doesnt already exist.
Removed by mod
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- it’s simply a voluntary intermediary for a user to access their own account with their own content feed.
That said, any client apps that run ads are 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.
So we need something more than a ccbync to prevent ads being put next to content?
deleted by creator
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.
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)
Exactly the implementation i was invisioning.