Nobody. It's a public forum, anyone can take what you said and use it as their own.
From technical side, instance admins, community moderators, and you have the ability to remove them.
I think some user content may be subject to copyright. Depends on local law.
Might we easily make it more clear that the poster or the server owns them outright?
Hypothetically, a corporation federates and wants to monetize my posts. Can they do this? I’m not personally fixated on ownership (which could easily be viewed as my systemic privilege), but the pathway out of this type of thought in general doesn’t seem to be yielding all power to already powerful growth-based corporations. I didn’t create the current systems, but I do acknowledge their existence.
How would that even fundamentally make sense? Define "own". If you post the comment "lol" does that mean I shouldn't be allowed to post "lol" since you "own" it? How would simply posting something establish ownership? What if you had copied it from a different site?
Anywhere where you're a repeat customer is probably selling your data. Any service you repeatedly use could also sell your data. Unfortunately it's just a way of life these days.
Who says that no-one is sucking up all of the Lemmy data right now and selling it to some entity? There is no way of knowing and there is no way to combat it.
Well, let's see what the ToS says. sh.itjust.works here.
Legal:
TBD
Oh.
They were too busy getting shit to just work.
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.
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.
Others have expanded, but it may be useful to try to break out of the typical idea of ownership.
But everything has to be owned by someone! Otherwise how could it be worth anything?
(I'm being sarcastic, but alas, I expect there really are people with that mindset. I often see people who are absolutely incensed that someone could use their posts to train an AI without them somehow getting the microscopic fraction of a penny that the AI might eventually make, for example)
Nah, spend years and money on something and then give it away? Nope, hard pass. Corporations would love that though, less litigation when they're going to steal it anyway.
Each instance has complete control over what is posted on it. The only way to truly own your posts is to set up your own instance and interact only with communities on it.
An interesting thought. I’m not sure this is entirely true though in many jurisdictions. It is clearly possible to post something on someone else’s server and still maintain ownership of it. Platforms like SoundCloud have you specify a license in the ui client at the time of upload. While this might seem performative, it is explicit.
True, but if server owner pulls the plug, all the content you have there is gone. They can also unilaterally delete your posts.
I guess my point is ownership isn't as important as control.
SoundCloud vapes content and entire accounts all the time.
I think this is something that should be clarified in the terms of service of the instance.
A site's terms of service may state that you grant certain permissions regarding the content you post, but that's typically so that they can display it in other people's feeds. It takes pretty explicit consent to give up or transfer your copyright to another entity. So while you're granting permission to transmit what you post to others, it would be a really difficult case to make that you have given up your ownership of what you post. For example, if you post a photo you took to Lemmy, you're granting your instance permission to distribute it across the fediverse, but you still own the photo.
Disclaimer: not a lawyer but have studied copyright law academically.
"I made this..."
You own your original ideas, technically speaking. Just other people that view the board can use the ideas, copy it, or remix it into their own ideas as well.
As an analogy, say you buy a brand new red car, and you drive it on a public street. People who take a picture of the car don't own the car, you do of course. They, however, own the picture of your car and can sell it, copy it, post it, whatever as they please.
It's a little more nuanced than that. My understanding in the US, if you copyright your building, a person can't sell the picture of your building standing alone, but can sell the picture of the landscape it's in. In your example, If you took a picture of the car and said you designed and manufactured and are trying to sell it, that's absolutely illegal. Litigating it and getting money from it is a different matter.
Yep all valid points. Asserting your rights are another matter entirely, and there are many intricacies and nuances that vary from place to place but boiled down to a basic principle I hope my version was apt.
They, however, own the picture of your car and can sell it, copy it, post it, whatever as they please.
That depends on your jurisdiction.
