The experiment with feeding Soylent articles: your comments!

by
in ask on (#2QM4)
Well, unless you were holed up with Dick Cheney in the underground security bunker, you probably noticed Pipedot flipped the switch on a new feature that feeds articles from other sites. The idea is, as I understand it, anyone running Pipecode can eventually have a whole series of these feeds, and automatically populate their site with articles.

That led to a rash of new articles here, all of the Soylent comments, and a bit of anger over at Soylent despite NCommander having generously and magnanimously offered the feed of articles to Pipedot.

Nonetheless, this mirthful article suggestion poked up in the Pipe today:
Pipedot caught willfully plagiarizing Soylent News! As noted on https://soylentnews.org/comments.pl?sid=3587&cid=85807 and https://pipedot.org/story/2014-08-26/database-to-track-suspicious-memes-on-twitter and in particular, https://pipedot.org/comment/1409062920_n1_soylent_news_org , the majority of content being posted on pipedot.org is taken without permission from soylentnews.org

Given that the copyright of comments on soylentnews.org is not transferred from the people that posted them, this ongoing action constitutes wilful, mass copyright infringement.

You are hereby given notice on behalf of John Doe and Jane Doe * 4,000 under the US Digital Millennium Copyright Act 1998, as amended, Section 512(c)(3)(A) that:- ...
Glad nerds haven't lost their sense of humor. So, what did you think of the feature? Your comments here about the feed, the pipe, and the future direction of Pipedot.

Re: Alright then, I'll start (Score: 4, Interesting)

by moveonover@pipedot.org on 2014-08-27 14:22 (#2QNE)

I absolutely agree. For Soylent content, I'll go to Soylent. I was hoping Pipedot would remain lower-volume, higher-quality and tech-focused.
If 95% of the content on Pipedot is coming from Soylent, then 95% of the reason for Pipedot to exist is gone.
Post Comment

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Undefined array key 0 in /var/pipedot/include/captcha.php on line 64

Warning: Trying to access array offset on null in /var/pipedot/include/captcha.php on line 64

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/lib/tools/tools.php:2762) in /var/pipedot/lib/tools/tools.php on line 1540

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/lib/tools/tools.php:2762) in /var/pipedot/lib/tools/tools.php on line 1549

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/lib/tools/tools.php:2762) in /var/pipedot/include/common.php on line 80

Warning: Cannot modify header information - headers already sent by (output started at /var/pipedot/lib/tools/tools.php:2762) in /var/pipedot/include/common.php on line 82
Fatal Error - sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.216.9] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null] - Pipedot
Fatal Error
sql [update captcha_challenge set captcha_id = ? where remote_ip = ?] arg [, 216.73.216.9] msg [SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'captcha_id' cannot be null]
Subject
Comment