From: gtr on
On 2010-06-15 09:39:26 -0700, Wes Groleau said:

> Of course, Usenet has its own share of stupidity …

Oh well now you're just being silly...
--
If God didn't want us to eat animals, why did he make them out of meat?

From: erilar on
In article <hv8ac6$d4i$1(a)news.eternal-september.org>,
Wes Groleau <Groleau+news(a)FreeShell.org> wrote:

> Of course, Usenet has its own share of stupidity …

Killfiles 8-)

--
Erilar, biblioholic medievalist


http://www.mosaictelecom.com/~erilarlo
From: Leonard Blaisdell on
In article <droleary.usenet-45566F.12225015062010(a)news.twtelecom.net>,
Doc O'Leary <droleary.usenet(a)2q2010.subsume.com> wrote:

> That may well be the case, but I also happen to think pretty abstractly
> about things. To me, Usenet is just another transport layer for
> messages, and arguably one much more worthy of attention than the likes
> of Twitter. It may be possible to make a business case to create an
> NNTP.framework that is *indirectly* the basis for some other social
> networking software (or even something mundane like backups). There may
> be a retro renaissance for Usenet in the future if privacy concerns
> continue to plague web sites like Facebook.

NNTP is in decline. You're a developer that pays attention to it. The
protocol is begging for something new. There is money to be made. I'm
trying to think abstractly. What would I do with your skills?

leo
From: Doc O'Leary on
In article <leoblaisdell-DB0B05.23560518062010(a)News.Individual.NET>,
Leonard Blaisdell <leoblaisdell(a)sbcglobal.net> wrote:

> In article <droleary.usenet-45566F.12225015062010(a)news.twtelecom.net>,
> Doc O'Leary <droleary.usenet(a)2q2010.subsume.com> wrote:
>
> > That may well be the case, but I also happen to think pretty abstractly
> > about things. To me, Usenet is just another transport layer for
> > messages, and arguably one much more worthy of attention than the likes
> > of Twitter. It may be possible to make a business case to create an
> > NNTP.framework that is *indirectly* the basis for some other social
> > networking software (or even something mundane like backups). There may
> > be a retro renaissance for Usenet in the future if privacy concerns
> > continue to plague web sites like Facebook.
>
> NNTP is in decline. You're a developer that pays attention to it. The
> protocol is begging for something new. There is money to be made. I'm
> trying to think abstractly. What would I do with your skills?

NNTP provides a caching distribution network. What you would do with my
skills is make software that is even easier to use for content providers
and content consumers to take advantage of that. The added win for ISPs
is that continuing to support Usenet for that kind of popular,
legitimate, broadcast content will reduce upstream traffic.

One good example: I've seen more than a number of podcasts, especially
video podcasts, that have become popular only to get crushed under the
weight of bandwidth costs. Most downloads of new podcasts, or any
popular serialized content, happen well within the retention times of
most Usenet servers.

--
My personal UDP list: 127.0.0.1, localhost, googlegroups.com, astraweb.com,
and probably your server, too.
From: Leonard Blaisdell on
In article <200620100750057057%HP(a)snotmail.com>,
High Priest <HP(a)snotmail.com> wrote:

> I've read that opinion before. But I think it's a concept that is
> resistant to proper analysis, testing and verification. Why, for
> example, do you believe it?

That's easy. When I connected to Usenet (1994), nearly all ISPs offered
the service. It was a going concern. I've only had two ISPs. One was
local and it dropped Usenet. One was national (AT&T) and it dropped
Usenet. Rest assured that Usenet ain't what it used to be. I'm
comfortable here because I'm used to the protocol and the user base is
aging just like me. Kids don't have a clue what Usenet is and they're
the future.
Usenet readers don't get updated - no viable audience.
ISPs drop rather than add NNTP - no loss of customers.
I'm susceptible to proper analysis rather than my experience if you'll
provide a link.

leo