I host my own instance and use the Creative Commons Non-Commerical license on my content. The idea is that this makes federation with other non-commercial instances no problem, but as soon as an instance mixes in ads in the feed, they (technically) can't show my posts alongside it.

I know Pixelfed has a license field for every post/picture so you get fine grained control, but I don't believe this is the case for the Mastodon API yet, so I have added the license information in my bio. It would be nice to attach license information to individual posts, and to assign a default license.

My hope is that this will make it more difficult for Meta and the like to mix in ads with my content. Time will tell if it works 😆

[–] [email protected] 4 points 11 months ago

Thanks for sharing. I honestly was wondering how people were thinking about this. I was wondering why not include a license specified per post in the client UI as that seemed quite explicit. Yet, I was wondering how this might prohibit federation from being controlled at the server level.

I had considered ads in clients and llm training. Both of which, people in need should be paid for if it is using content they generated if at all possible.