Stories
Slash Boxes
Comments

SoylentNews is people

posted by Woods on Thursday May 15 2014, @11:11PM   Printer-friendly
from the content-of-this-article-is-SFW dept.

In the beginning, pop culture wiki TV Tropes licensed its content with the Creative Commons Attribution-Share Alike license for free content.

When Google pulled out its AdSense revenue because of... let's call it NSFW fan fiction, TV Tropes changed its guidelines to forbid tropes about mature content. In response to this move, two forks were eventually created. The admins disliked this move so much that they changed its license notice to the Attribution-Noncommercial-ShareAlike version, despite their site not having requested copyright rights from their users. Only later they added a clause to their Terms of use page requiring all contributors to grant the site irrevocable, exclusive ownership of their edits.

I suppose the morale of the story is, if you contributed to TV Tropes before summer 2012, you should know they're distributing your content under a license that you didn't give them permission to use.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by tdk on Friday May 16 2014, @09:16PM

    by tdk (346) on Friday May 16 2014, @09:16PM (#44443) Homepage Journal

    I've tinkered with the idea of creating a Slash->NNTP protocol,

    If you do this, you have to decide whether to import Usenet posts back to SN.

    If you do, there's going to be a lot of spam and you may have to beef up your moderation - eg allow anyone to moderate at any time.

    If you don't, you'll get a lot of flak from Usenetters and will be missing out on a lot of useful posts.

    If you followed [squte.com] the threads [squte.com] on slashdot vs usenet [squte.com]
    you'll know I think it's better to build a new backend instead of usenet, but meanwhile the more web sites mirror to usenet the more likely it is to last as a kind of open database/protocol for distributed web forums.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by NCommander on Friday May 16 2014, @09:31PM

    by NCommander (2) Subscriber Badge <michael@casadevall.pro> on Friday May 16 2014, @09:31PM (#44450) Homepage Journal

    In my very rough ideas on how we'd do this, users who are logged into our NNTP server (using the slash username/password) would be auto-posted to the site as a logged in user, while everyone else will come in as AC (we'd import headers and display them as well).

    My thought here is to write the site out as a series of UUCP USENET batchfiles (the fileformat is simple), and just import straight into INN which means that slashcode would essentially operate as a second server to INN which in turn can be fed to the rest of USENET in a predictable matter.

    In USENET terms, the SN feeds would be moderated, so every post would turn into an email which slashd can process one by one, and run them through spam-assassin; unautheticated posts from USENET that fail spamassassin will just be discarded silently; posts that pass will be passed back into slashd, and installed into the database, then echoed back into INN as described above. Our posts will have plenty of metadata allowing people to re-create the database from scratch if we ever have to close our doors (we could probably use some control message magic to make moderation scores appear as X-Headers, and then cancel out the old posts in the feed. This might cause issues w/ some news readers as not many of them implement Replaces/Supersedes very well).

    --
    Still always moving