Slashdot Mirror
Open Source, Closed Talk
Internet users who "post" articles using USENET or mailing lists are inherently granting third parties the right to repackage and retransmit their words into various formats. For example, Deja and Remarq take the legal position that they have the right to rate, sort, emphasize and discard USENET posted content, and retransmit what they consider "best", without obtaining any license or permission from the authors of the content. Seems perfectly reasonable, even to their legal departments and investors!
So long as Linux related discussions take place in such open forums, third parties have wide latitude to do the same, potentially adding a lot of value -- identifying highly relevent and instructive postings, questions asked and answered, tips for new users, a record of new ideas and suggestions and more. Enter a site like VA Sourceforge. True, they are providing all sorts of value added services. An open source project conducted there has certain advantages. The general discussion forums there too, may be useful. However, in each case, the participants are asked (in the legal "terms and conditions") to grant the Web site permission to use the forum content, but no permission is requested or accepted on behalf of third parties.
The bottom of every page says "Forum comments are owned by the poster. The rest is copyright VA Linux Systems." Remember that the GPL may apply to code, but it's irrelevent to talk. If I see an insightful discussion taking place on the Web site, or in the site's archives months after the fact, I can't take it, package it, sort or filter it, and retransmit this in another form or medium. Not unless I go back and obtain permission and a license from *each and every participant* in the discussions in question. So, in an important sense, VA is taking ownership of the content; no one else will be able practically to get the rights to reproduce, recycle and extend the content. Open source, but "closed talk".
Is there a solution? Yes. A quick and direct solution would be for a site like VA Sourceforge to permit users to obtain any and all contributed content an automated mailing list facility. Just asking users who are posting content for the right to retransmit, if done properly, could move us back to the status quo ante. However, I suspect they won't, because they want the site traffic. There is potentially a lesson here for Slashdot as well. I suspect that I can't take what's posted at Slashdot and retransmit what I might consider "best" like I could, for example, with the Linux kernel mailing list, can I? This whole trend toward Web site forums and facilities is leaving significant, valuable intellectual property rights in the hands of companies valued in the billions of U.S. dollars, and rendering it uneconomical for others of us to get the rights ourselves. Potentially, this is denying the Linux community valuable future resources.
To provide copies of useful information I'd seen at these sites, I'd practically have to construct an elaborate Auctionwatch or Bidders Edge system, and point people to links at VA Sourceforge or Slashdot. (And then what, will the sites respond with lawsuits like eBay?) Until these sites establish new policies of collecting intellectual property rights for the whole community, instead of just for themselves, some of the most exciting and important content in this "new era" for Linux is no longer open to all -- certainly not the way we all mean when we say "open". "
The US copyright law is very clear in this regard. The author of the post holds the copyright. Reuse of the material (in documentation, for example), requires permission from the author. The author does not give away his copyright on the material by posting it to USENET. Thus, the problem of ownership of content does not change by going to web based forums. Unless the site explicitly states that submitted posts become the property of the site, the author retains ownership.
I think the gripe originates from the fact that when a post is made on a web site rather than via USENET, the post remains located on a single server which has an owner and the right to drop the post if they want to. In USENET, once the article makes it to your NNTP server, you can choose to archive it and process it for as long as you want. (e.g, Deja.com) Holding the post and displaying it in the context under which it was posted does not violate the authors copyright since it was he who put it there to begin with. This is why Deja.com isn't in trouble. (Their choice to filter out posts is no different than an individual setting up a killfile.)
If anything, I would argue that the web gives us the opportunity to change the rules on what can be done with a post. It gives the web site owner the chance to tell the poster who owns what and for what purpose BEFORE the post is made (unlike USENET).
Some Anonymous Coward writes a moving, compelling manifesto against the MPAA-- concise, easy to comprehend, with easy steps one might take to fight them.
If only the general public would read this post from Anonymous Coward-- why, they'd undestand the issue, their hearts would melt, and public sentiment rally against the dictatorial Valenti and his ilk.
Now, let's say everyone wants to repost this moving article on their web site. Can they do it, legally? Do they have to ask the original poster for permission to print it in its entirety?
And if the author was an Anonymous Coward, how could they ever get permission? What then? Maybe the open content (http://www.opencontent.org) license could be applied to all postings or something (?)
This whole debate is very interesting,
and I am watching with some worry.
In USENET, ppl contribute, their help
, ideas, flames etc, without any sort of
monetary reward for doing so.
The news server you use does not generate
revenue per article read or anything like
that for the company or individual who ran it
either.
Slashdot however generates moey for the ppl
running it, or their company whatever, by
every page impression/view that happens.
Every time someone reads a discussion,
the hits go up, and in this new wacky economy
you read the ad, you might generate some
revenue.
If Slashdot, starts mirroring the discussions
on NNTP, its my true hope that they will
NOT add stupid ads etc to the disussions but
sticking true to the old school USENET style,
and ONLY replicating content.
However, how will Slashdots admins, or their
parent company feel about loosing perhaps
30% (over estimate I am sure) of the page
impressions if the discussion are bidirectionally
replicated to NNTP. That means less ads seen
less revenue.
Slashdot a while back started publishing their
headers via XML, for some reason they update
it very rarly compared to their frontpage.
This is natural since they want ppl, they want
you, to look at their front page, and earn them
money.
They dont really want to give you the content
without having to go through it.
I will be pleasantly suprised if Slashdot sets
up a bidirectional real time replication to
NNTP without any banners though I doubt it
will happen.
I would like a fresh bowl of Slashgrits poured down my pants.
Thanks you.
While pushing /. discussions out to NNTP is a fine and worthy goal, I hope they don't replicate NNTP posts back.
The signal-to-NataliePorter ratio is bad enough already - adding the volume of USENET spam would be a bad move...
This sig left unintentionally blank.
The idea of getting /. discussions mirrored on to an NNTP server is the greatest idea I've heard in a long time. I sure hope this improvement makes it.
/. in mid-1998, which puts me fairly near the start of the usage curve. My user # is certainly in the top 10%, and by now maybe in the top 1% (this is hardly to brag: I only contribute to threads occassionally, and have only a moderate karma thereby).
/. at the beginning was that the discussion capabilities were *SO FAR* behind the Usenet in terms of speed, usability (in my favorite news client), archivability, searchability, and in all the other things that make NNTP great. Over the last year, /. has added some nice features (the moderation, for a big one). But even still, it doesn't come anywhere close to Usenet in terms of convenience. (slashdot is still occassionally way too slow, and there is no way to browse discussion, respond, etc. offline).
/. style boards are not. And it is an open standard that allows everyone to have their favorite newsreader that encorporates all the features they find most useful (again unlike a web-board). News feeds are easily searchable plain-ASCII, which is wonderful (which web-boards are not, even for comments posted as ASCII).
/.. But all else pales next to NNTP.
I first started reading
Anyway, one of the main hesitations I had in spending much time on
This was discussed recently in the "death of Usenet" thread, and I guess a lot of correct points were made there. But I really think the *open* and distributed format of NNTP is the very best thing the internet has created. It is open in a lot of ways, too. The discussion is inherently public (if not unambiguously "public-domain") in a way even
A distant second here would be a majordomo or listserv type mirror of
Buy Text Processing in Python
Bruce
Bruce Perens.
Thanks
Bruce
Bruce Perens.
To do this I used a rather unusual publication policy, as far as I know I've invented it:
By submitting this article you grant Technocrat.net a separate and independent copyright to your posting, and you keep your own copyright. That means that you can do anything you wish with your posting, and so can we.
That allows us to apply a license to the postings after the fact.
However, this doesn't address the complaint, which is that Usenet sites seem to have a more liberal copyright policy that allows them to be filtered and presented differently by various web sites, and weblogs like Slashdot and Technocrat do not. I'm not sure that stands, legally. The Usenet doesn't demand a particular copyright and the default if you don't copyright your posting would be All Rights Reserved.
Thanks
Bruce
Bruce Perens.
It seems to me that every OSS license has this sort of provision already.
Here in the US, any form of publication (email, books, pictures) is considered the property of the originial publisher, whether this is stated or not.
The copyright can be given up, or changed to the copyleft, but only at the discretion of the originial publisher.
In the strictest sense, this also applies to USENET. It has never been legal to use another person's writing without crediting/reimbursing them.
Never let your fears overcome your dreams.
There are many, many methods of moderation on Usenet.
/. moderation would be "nocem". nocem messages are advisories in which any reader of Usenet can list message-IDs that they either consider a must-read, or that they think should be immediately trashed.
./ moderation. Choosing between standard discussion, or Natalie Portman posts would simply be a matter of choosing which moderators you trust. Moderators can mark as many posts as they want, even their own, in discussions they're taking part in. If you find the moderator is moderating badly, all you have to do is remove their key from your trust file.
Scoring killfiles are a God-send. Once you've read a newsfroup for a few months, you can tell who is most likely to produce content, and score them up, and score down those more likely to produce noise. Don't have enough time to read the entire group today? Doesn't matter, the cream should have floated to the top of your newsreader. Just read down the list as far as you want, then bin the rest.
The other "plus" of this method is that you know when you load the group and there's nothing with a positive score, it's time to move on and find somewhere else to amuse you.
The most similar to
The difference is that you can verify the source of a nocem using PGP, and you can choose which moderators you trust.
This would dispose of most of the complaints about
This is also something that couldn't be implemented on a web-based forum. Dealing with such fine-grained moderation preferences would bring the site to its knees. The beauty of Usenet is that aside from the spam-filtering, the rest of the work is done by the client, so you can set up your own moderation to your own preferences.
Usenet isn't dead. It's not even dying. Web based forums are incredibly clumsy in comparison, and only good for short-lived discussions.
Look at slashdot for an example. Unless you get in the first hour or two after a topic is posted, the chances of having your post read, or responded to is minimal. The chance of carrying on a discussion that lasts more than a few hours is almost non-existant - everyone will have moved on to the next topic.
On Usenet, on the other hand, discussions can go on for days, weeks, months, years, or occasionally forever. Those who are interested in the thread will continue to read it, those who aren't will just score it down or killfile it, and move on to something new.
I'd like to see how a slashdot/NNTP gateway would deal with this obvious change in mentality would be interesting. Expiring posts after 24 hours would be the obvious, if brutal solution.
Charles Miller
--
The more I learn about the Internet, the more amazed I am that it works at all.
In both USENET and the various discussion Web sites, the comment poster owns the copyright, so, technically, you should have to get permission to redistribute in either case.
Due to the nature of USENET, it can reasonably be assumed that the poster allows redistribution freely. However, there definately is untested waters for services that "package" USENET postings and then resell them, since they are using the original copyrighted material in methods that could be argued are different from the implied "license to distribute". Now, no one has challenged this in court, and hopefully, no one will, since it seems to be a good arrangement for both sides, and it would hurt everyone involved. Everything I just said about USENET seems to apply to mailing lists, too.
The major problem with Web sites is the lack of easy-to-access archives of material, not the legality of redistribution. Yes, technically, you should ask for permission to redistribute, but that's the same as under USENET. It's a matter of perceptions. The problem sited here is that 3rd-parties can't get at the archives in an efficient method to do repackaging. This is a problem, and one I'm not sure is easy to solve.
However, it's also a problem with mailing-lists: if the list maintainer doesn't make a digest or archive available, it's not easy to get back articles. Sure, you can subscribe and get everything from that moment on, but you don't get "back issues".
I don't really know what the answer is, but at least it doesn't seem to be a legal problem.
:-)
-Erik
There are always four sides to every story: your side, their side, the truth, and what really happened.
Here's a way around the problem (for all those that still view .sigs)...
It seems as soon as any discussion moves beyond "a few friends and I" it always degenerates into a form that requires moderation... thus the rise in easy-to-moderate web bulletin board type systems and moderated mailing lists.
The most difficult part of the new moderated discussion world is to find moderators who don't abuse their powers.
I'm surprised to see no one has commented on this already. I'm sure there are many SF project admins on /., aren't there?
"Internet users who "post" articles using USENET or mailing lists are inherently granting third parties the right to repackage and retransmit their words into various formats. [snip] So long as Linux related discussions take place in such open forums, third parties have wide latitude to do the same, [snip] Enter a site like VA Sourceforge. True, they are providing all sorts of value added services. An open source project conducted there has certain advantages. [snip]"
From the admin area "help" for one of my lists there... ("formatting" courtesy of lynx-ssl)
If pre and /pre tags were supported on /., that would have come out okay. Hint, Rob.
The point here is, the NNTP gatewaying mechanism is already in place,) as well as the archiving of past messages in with a public or private method,) if the project admin chooses to take advantage of it. And the gatewaying can be configured to go in either direction or both, if desired.
There are several problems in the implementation of mailinglists and newsgroups that can be worked around on the web that makes those "old" services less desirable when it comes to using them.
;). But sponsorship without control. Don't count on this happening though. With Linux being the new bandwagin to jump on, corporations want a flauntable piece of the pie, something that they can control and do whatever they want with. Until the need for greed wears of in a couple of years, expect open-source collaboration to be very rocky, with the buisnesses that contribute the least to be making the most noise and stirring up the most bullshit.
Yes, it's nice that VA sponsors that soundforge work, but when it comes down to it, VA does like to keep a good deal of control over the work of it's sponsored projects, because when it comes down to legal liability, they don't want to be stuck in a corner, as do any other company that sponsors these projects.
What do I see as a solution? Not the abandonment of web forums, because they tend to be much more effective when implemented correctly (admittedly, most of them suck right now
(Slashdot does not condone the use of it's users saying the word "bullshit")
I am proposing that Slashdot and VA Sourceforge immediately make available their web hosted forums via a majordomo style mailing list, with every participant at the web site giving up as many legal rights as any participant in any mailing list. Permit users access to the full ascii content of whatever is posted to forums via e-mail, without ever having to visit the site (except maybe to sign up).
Different 3rd party "mailing list archiving" sites, which use html interfaces (ugh), already take the position they have the inherent right to be one more manner of the redistribution contemplated by the mailing list method of moving content around.
One can squabble about whether this would hold up in court, but let's move back to status quo ante: put web hosted forums on the same playing field as majordomo mailing lists.
This is a much more direct solution than writing a new GPL something or other licence, although maybe that would be useful in the longer term.
Ummm...paraphrasing is still considered plagiarism. Whether or not this form of plagiarism can be proved to be a flagrant copyright violation is up to the lawyers.
FWIW, the fine print says that the posts are owned by the original posters, which means that they (Andover.net) are divesting themselves of all copyrights to the posts.
Oh yeah...IANAL.
My journal has hot
The "fine print" in the green bar above the comments states that "The following comments are owned by whoever posted them."
This means that Andover.net is divesting itself of all copyright to the comments. Since the original posters own the comments, copyright release would have to come from the original posters.
Now, I believe that I have read somewhere that it was either USENET or bulletin board postings were ruled by the courts to be "reasonably assumed that redistribution is granted" due to the nature of such. I would assume that this would also apply to Slashdot postings, but there is really precedent for it, since Web postings aren't actually redistributed by several different sources the way USENET postings are.
Of course, it makes matters worse if I do something like this:
Now can you redistribute this post or not? This is left as an exercise to the reader.
My journal has hot
How about changing the default license 'all comments are copyright of the author' to: All comments are in the public domain, unless otherwise is stated in the comment?
/. terribly slow today?
BTW, is it me or is
If Slash is getting a gateway, does that mean we are going to get killfiles for reading the pages? To be clear, will I be able to add usernames of other people to a list, and then never see their comments again? That would be nice.
Nerd rage is the funniest rage.
Duh!
Bruce Perens' site, techoncrat.net has packaged all last's years content & comments and made them available (somewhere - I couln't find a URL)
Bruce, if you are reading - what's the licence, and do you require permission of the comment posters to make their comments available for redistribution?
I'm sorry I have to be the one to say this, but USENET sucks. I've used it to varying degrees of success, and certainly obtained and published my meager knowledge of Linux, but by and large, USENET is spam and porn.
/. my inane Linux questions), but /. does provide a publicly moderated forum for discussion. In many ways, /. is better than USENET, one, because it is moderated by the members of /. and therefore not subject to the whim of a single USENET moderator, and two, /. ACTUALLY GETS MODERATED. Many usenet groups I've seen cannot keep up with the garbage that is posted there. /. moderators eliminate the Natalie Portman troll posts almost as quickly as they are posted.
/. moderation scheme, the moderated messages are not actually removed, they are just lowered to an ignorable level. The burden of the moderation is on the /. community, and I have to say that the /. community has gone above and beyond the call of duty on this one! Good show, give yourselves a pat on the back!
/. community to moderate the moderators. I occasionally find a comment moderated down that shouldn't be, and have the priviledge of being able to do something about it.
/., so don't make it out to be an evil that it isn't.
I've recently become interested in distributed computing, and looked on USENET for a dist comp group. I did find ONE, with about a dozen messages in it. About three of those messages were valid. The other 80% was divided equally betwixt spam and porn.
Sites like Slashdot, while not providing the same forum as USENET, (i.e. I cannot just post on
Also, with the
And let's not forget the ability of the
I've never seen a better public forum than
While I agree that copyright laws are necessary to protect the interests of authors, and comments are technically covered under this, the original intent of copyright laws are to protect the profits of the author so he/she can make a living from writing.
Is anyone here making a living by posting comments to slashdot, and need their livelyhood protected?
Do we need to introduce a "not for profit" clause allowing redistribution? (so as to protect sites like slashdot from being plundered for their comments?)
hmmm.
I think this is a technical issue. It /would/ definately be great to backend weblog-like frontends with traditional "open" communications mediums like USENET. I wouldn't get on VA's case too much. They /do/ have mailing lists. I don't think anybody is intentionally attempting to appropriate or make it difficult for others to access discussions. It is just a technical matter of /how/ to "open" it up.
I think it is just a matter of integrating communications mediums. I think XML has a great potential for facilitating this.
Jazilla.org - the Java Mozilla
It's 10 PM. Do you know if you're un-American?
Regardless of whether my comment is my copyright or the public's, I wish new sites would focus on creating their own content, rather than recycling old comments from another source.
Don't get me wrong, I do like the idea of a user checking a box next to his/her comment, which would make it available to the public. It would then be useful to allow developers the option to download all "public comments" in one click. Either a CSV file or XML would allow easy integration into whatever database system is being used.
However, I just hope that future web projects will focus more on the creation of their own, new content, rather than re-hashing and re-filtering material from another site. Just as we don't need a links page pointing to another links page, we don't really need comments from comments.
There's plenty of code out there to easily build your own Slashdot. So hopefully developers will think "new content" first, and "import content" second.
I just got wind of this. It seems a web service for reading Usenet will be highlighting keywords within the articles displayed through their site with links to advertisers who have purchased that service. The press release from the service itself is here. It is high time to start digitally signing everything with either PGP or GPG and licensing it only for unaltered redistribution.
This comment is licensed under the OpenContent License (OPL) Version 1.0, July 14, 1998. The relevant paragraphs concerning modification are as follows:
2. You may modify your copy or copies of the OpenContent or any portion of it, thus forming works based on the Content, and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified content to carry prominent notices stating that you changed it, the exact nature and content of the changes, and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the OC or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License, unless otherwise permitted under applicable Fair Use law.
The net will not be what we demand, but what we make it. Build it well.
Circa 1991 or so, he was like the king of internet porn on usenet.
I can't either confirm or deny that. Until about a year ago, my Usenet feed was somewhat filtered. All I know is that he was a regular poster to a number of newsgroups, and that he made the suggestion that I posted a link to.
The net will not be what we demand, but what we make it. Build it well.
Elf Sternberg, an long-time personality on Usenet, anticipated some of the growing problems with it and has put this proposal on his web site for a distributed solution. It is worth reading, especially in light of the idea for a Slashdot/NNTP gateway.
This article may be copied and distributed under the terms of the OpenContent License (OPL) Version 1.0, July 14, 1998.
The net will not be what we demand, but what we make it. Build it well.
Awww jeez...
Here we go again. This guy isn't Roblimo.
He's RobLimo_ User #146994
The Roblimo we know and love is user # 357
Keep this in mind when you respond to him...
Here's my copy of DeCSS. Where's yours?
censorship is a form of noise, which actively seeks to drown out content with silence - Crash Culligan
"with every participant at the web site giving up as many legal rights as any participant in any mailing list."
/. as an AC, so should you have tha ability to decide what is done with the comment you just submitted.
So you would ask that several hundred thousand users give up their rights to their comments, just to participate?
I, for one, would not participate if I did not have that choice avaliable to me. I would also resent it if ever Rob did such a thing.
"This is a much more direct solution than writing a new GPL something or other licence"
We probably wouldn't need to write a new GPL something. In my original comment, I suggested something HTTP specific (called it the SlashComment Public License). It would appear that the open content license could be easily modified to serve this purpose.
"put web hosted forums on the same playing field as majordomo mailing lists."
I would argue that there's enough of a difference between the two to call for a different license/redistribution structure. The biggest difference, IMHO, is that web forums allow you to be totally anonymous. With a maling list, you aren't totally guaranteed anonymity by virtue of having to have an email address to participate. If I wanted to badly enough, I could probably trace your email address back to you. With Slashdot, I have no such ablility.
Therefore, I would propose a slightly different structure. Just as you have the ability to pop in and post to
Am I making sense here?
Here's my copy of DeCSS. Where's yours?
censorship is a form of noise, which actively seeks to drown out content with silence - Crash Culligan
...those `GPL for Books' kind of licenses?
Combine that with an option below the Comment window (like Slashdot's) to `Include comment in SCPL (SlashComment Public License)'. That way, the poster still owns the comment *and* gives permission for others to use it in a manner consistant with the SCPL.
This would also allow people to opt in and out, legally, and at will. Make the option avaliable to all (AC and those with accounts) and, voila! Problem solved.
This would also make things easier for posters. Remember the _Jane's_ happening? There were people who were quoted and not given credit (at first. IIRC, all of those problems got sorted out). With something like the SCPL, the license writers could include a clause that made it mandatory to give due credit.
The best part about this is that it's a vouluntary system. Since it's a contract that you knowingly enter into, there's no problems with comments beig `stolen', taken out of context, or abused.
Comments?
Here's my copy of DeCSS. Where's yours?
censorship is a form of noise, which actively seeks to drown out content with silence - Crash Culligan
Well if I want something from slashdot I do the following. .. "99.txt etc)
1. Get a number of floppy disks. Usually even with maxium stories displayed on the main page and even with things like perhaps Linux goes commercial and abandons the GPL I can get all of slashdot's extended stories on 5 or so floppies at max.
2. Save the context via a decent browser (Netscape and IE both have their faults for overall indention and including of ^M characters and other bad things and lynx dosn't allow for the typical indention of comments via nested mode)
IE 5 is actually good for the aboive because it automatically includes the title of the page for easy index. Spill over and the next page problem is solved with a simple appending of a numberal that is the same as the page in question (ie Slashdot News Linux goes commercil and abandon's the GPL1.txt "2.txt "3.txt
3. Filter this through a program similar to col with cat blah1.txt | col -b >newfile-without-control-characters.txt
4. Read the comments.
Now this dosn't allow for the use of responding to various comments and such but if I want an archive of all of the ranting and raving on slashdot it is a very nice thing.
Now how di I solve the problem of citations and such? Simple if you paraphrase something it usually works well enough.
Now I actually think that from an access point of view that the use and collection of info using a web browser is actually more fail safe and better than usenet. Usenet is something that is not guaranteed from a services offered perspective from each and every ISP. Some ISPs have a bigger spool some only keep stuff for 24hrs. I know of some ISPs that only provide a simple IP address and you do everything else (even without mail). I most of the time don't use USENET because of it's inherent lack of accessibility and uneven resource distribution. You can flame me all you want but even slashdot partly agrees with me as there was posted a little sotry a couple of days ago about usenet dieing because people don't care. This type of a forum is quite nice.
Now I pose a question to all of you. Suppose I did take information from slashdot and paraphrase each and every comment (no I really don't think that many people care about post the first or dousing heated grits down my trousers or a fossilized version of Natalie Portman would be interesting). Would anyone be able to honestly say that slashdot-terminal or anyone else didn't actually know all that stuff?
Slashdot social engineering at it's finest
USENET has a number of problems, starting with the picky nature of its users. While it can do HTML to present an opinion in rich text, it is frowned upon.
If you have a newbie/basic question for a newsgroup, there's a chicken and egg problem. If you have a basic question for alt.foo.foobar, how do you find the FAQ? You're stuck with the choice of two stupid threads: "Where's the FAQ?", or "My foobar is broken". The former is the best choice of course, but it kind of lessens the usefulness of a FAQ, because someone still has to reply, and hopefully they won't flame you with RTFM's, too. The latter is also likely to get you the link, though it may get you a few extra flames. While I haven't seen it implemented, the web interface can preemptively point someone in the right direction before they start a "junk" thread.
Forums based on Slash or UBB feel more like communities. If you're interested in the person who made such-and-such a comment, there's an easy way to find out who/what they are -- you just click the link to their user information, and if they want to share anything, they've put it into their forum profile directly or by a link.
Usenet is moving to the Web because the interface, content, and interactivity can be done better there.
--
E2 IN2 IE?
Hmm it seems to me that all this is.. is a well...rant. He trying to make some play on Free speech when there isnt even an issue.
Take for isntance documentaries, like on the Discovery channel. I they just piped out the data recorded raw right into the audience it wouldnt make for a good, or even informative show. If a comapany is going to spend the time to moderate and filter out the crap from public domain speech and put the data they feel important on their media then more power to them. Anyway that is what people have done for years, the media never correctly portrays the full scope of any particular subject, just what people want to hear.
Hell even Slasdot does it. So again I ask what is the point of this article..... none really, its just some guy blowing crap out his mouth trying to sound pretentious and just, when he is probably just out for personal glory....
By the way, there has been some discourse at SourceForge on uniformly gatewaying the hosted mailing lists to a newsgroup hierarchy, similar to what Debian does with their mailing lists. No response on this idea yet from SourceForge personnel.
The whole point of posting to a forum is to release your memes on the collective consciousness. Anyone who would stop posting because of a public release isn't really interested in the discussion anyway.
/. moderation structure?
So the answer is simple - a public release and redistribution license accepted by hitting the "submit" button. Part of it could be the user id attached in any redistribution.
On another point - anyone know of a political discussion board using the
Slashdot is great news site, but (IMO) it's forums are a bad usenet wannabe. I can choose my newsreader. I can even write my own (or find someone else to do it) if I can't find one I like. I can tailor a newsreader to my likes and set up the most complex filtering criteria. If slashdot breaks, no discussion. If one usenet server breaks, the rest of the world can continue. How about turning the slashdot discussion board programs into a news reader pointing at one particular thread in an appropiate newsgroup? (I'll help!) Bill, likes usenet, lots.
It's the next version of Internet Relay Chat (IRC). Starting with IRC v2.3, (being released in March), the product will known as Intelligent Internet Relay Chat, or IIRC, due to its next-generation chatroom features. Look for it to be bundled with Windows 2000.
***
Back around 1989, I wrote a short history of USENET and made fun of all the people who kept predicting for years that it would soon die. I ended up coining the phrase "imminent death of the net predicted" in the history.
/. and others as the place to go for online conferences.
/., compared to a good newsreader. I rarely read the boards here. It's too slow, too cumbersome, even over a fast link. My newsreader is an order of magnitude faster.
But today I've joined the doomsayers. The net won't die, but it's already in decline, finally for real, but for a long time simply compared to the web. You see USENET was growing, but it wasn't growing nearly as the net itself. During the 80s it grew faster. Now all the mindshare belongs to the web, and more and more people think of web boards like
Too bad because frankly they suck in most ways, including
So much better yet it manages to die, while Andover gets valued at 800 million dollars (or whatever) of VA Linux Stock. Why?
Many reasons, but prime among them resistance to change. USENET is the example of open source at its worst. To change and evolve, it needs the cooperation of *everybody*. It's hard to lead, and no matter what you do, there will be more people who will think it's a bad idea. Every new suggestion is met with "Go to the web to do that" or "Go start your own hierarchy."
Well, I did start my own hierarchy once. It's not easy, and it's stupid it should be necessary to do something new.
I helped start the usenet-format IETF working group to help improve the USENET standard. It's been going for over 2 years and gotten nowhere. There are perhaps 2 or 3 new features in it, all because I pushed for them, but frankly nothing. Because of the need for too much agreement there is no change.
USENET people fear the web and the internet as the enemy when they should embrace them. Slashdot works because doing it on USENET would be hard. USENET still lacks real support (other than robo-moderation) for the idea of short-term, moderator-created topics that are within themselves unmoderated, or retro-moderated. That's how almost every online service and BBS has worked for a long time now.
USENET people fear the web because of the things that are wrong with the web -- it's too pretty, to inefficient, requires permanent connectivity -- but in turn they reject all the good it has to offer.
The last new feature in newsreaders was MIME, which is almost 10 years ago, before the web. One new feature in 10 years? 10 Internet Centuries they would now call that.
Even though over 50% of users now read with Netscape or Outlook Express and can do full MIME and HTML, even good uses that don't involve the feared abuses of the web are shouted down if people try them. Even somebody like myself, a reasonably respected old hand and moderator, has trouble suggesting new things. If I can't do it, I don't know who can.
I've about given up on the usenet-format working group as a means to improvement. My battle cry at the end was that we bring USENET into the 90s before they were over. Start-of-Decade-debates notwithstanding, I lost.
Has it been over a year since you last donated to the Electronic Frontier Foundation