this post was submitted on 14 Jun 2023
70 points (100.0% liked)
Technology
37746 readers
333 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I am not sure I agree entirely with this, while I do think there should be third party clients, we have entered the age where allowing API access is giving free reign to very valuable LLMs to train on your data, which also IMO violates your users privacy. I think it's better to have it be gratis but not libre, perhaps some kind of app approval process or some such.
I think it's possible to have a middle ground, just by putting properly formed license terms like foss projects. Ie. Specify that the AI/bot must be following certain rules(ie, fetch the comments but not the user IDs), because if we don't provide data for open and free alternative, there will be no good AI tools for common folks. And the top dogs are all hoarding data with sneaky ToS.
That was wild, yeah. Social media sites shouldn't lock down APIs because it's all user generated and LLMs should be given free reign to harvest user content for their own proprietary ends?
I guess I can agree that these two ideas aren't fully contradictory, but there's a lot of friction between these two conceptions of user's rights to their content/data.