Given my plan to set up a database for storing raw input to Scaffold, something on my mind has been what legal red-tape I may eventually run into.
To be perfectly honest, I am not sure what the legal implications are of storing published content that I do not own on a server whose contents I manage. On one hand, this is a not-for-profit open source application. On the other hand, this could definitely present issues if I were interested in the eventual implementation of accounts that could store and access previously Scaffold-ed content. Which, for the record, I am interested in since I believe it would be exceptionally helpful for users conducting research and information compilation across multiple sessions.
As a bonus thought exercise: if I were to use a corpus containing copy-righted documents to train an ML model what are the resulting limitations on my use of the model?
Down the line, I'll certainly revisit investigating the legality of article storage and access for users before embarking on the development of any features that would suck to have to immediately roll back due to litigation. To be clear, I also seriously care about not screwing over the content providers, even if unintentionally.
For now, I think I am safe being primarily concerned with first getting to the point where Scaffold is useful and well-liked enough to be worth suing over.
Subscribe to:
Post Comments (Atom)
Late January Updates
Nothing too big, this time, just wanted to pop over here for a check-in. My eagerness to move forward with my work on Scaffold has been mom...
-
In the interests of testing, standardizing input, and improving ease of use my next work item is to transition Scaffold from taking in plain...
-
The incredibly basic front-end of my dreams has been integrated with my back-end logic. I might remember to post screenshots or a bitty demo...
-
Scaffold will now take in a local file name or URL as input, verify which one of those two input types it has been given, and open and read ...
No comments:
Post a Comment