Who owns what we post?
im to lazy to check my instance
Well, let’s see what the ToS says. sh.itjust.works here.
Legal:
TBD
Oh.
To add to this, can we “disown” what we post? If it can be used against me but isn’t “mine”, it just seems like I’m always getting the short end of the stick.
As far as any legal liability, no, unless you’re successfully anonymous (VPN, tor, etc)
So shouldn’t some of the legal repercussions be shared with whomever “owns” what I post?
Generally you own what you post, but you have given a license to the site to display and use it. In the US, social media sites are protected by something called Section 230. This allows sites to display user-generated content without being liable for legal issues related to it, as long as they do a decent job of trying to moderate clearly illegal content.
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 😆
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.
“I made this…”
