Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #998 > unrolled thread

Could converting blogs to USEnet work?

Back to article view | Back to comp.os.linux.networking

Contents

  Could converting blogs to USEnet work? no.top.post@gmail.com - 2012-01-21 18:00 +0000
    Re: Could converting blogs to USEnet work? Richard Kettlewell <rjk@greenend.org.uk> - 2012-01-21 18:06 +0000
    Re: Could converting blogs to USEnet work? Stefan Monnier <monnier@iro.umontreal.ca> - 2012-01-22 16:31 -0500

#998 — Could converting blogs to USEnet work?

We all know how blogs have degenerated USEnet,
mainly by the absurdity that you need to d/l the whole thread
to see *IF* there's a reply to your comment/query.

Which results in few multi-stage dialogs.
So the result is that 'contributors' all rush to have their
once-off shout.  And it's degenerated to a Friday night
bar-shout.

Isn't it also problematic to 'hold' 8 blogs open on your
'browser' at the same time as using it for other http-fetches ?

What would happen if 10 blogs which were likely to be read
by a cluster of inetters, were 'harvested' and NNTP-served.

Let's consider the NNTP fields:
From=ok; Date=ok; Subject=ok; ... seems ok.

The threading would initially be weak/lacking because
the bloggers normally find it difficult to put that info in
their message; but as they became aware of threading 
capabilities they would use it.

Probably the biggest problem would be legally, from
the owner of the harvested blogs?

Personally, I never use a full 'browser' for blog-reading.
`lynx` gets me the text, without that crap-in-ya-face.

I've never used RSS. Perhaps that already fixes the problems?

What do you think?

== TIA.

[toc] | [next] | [standalone]

#999

no.top.post@gmail.com writes:
> We all know how blogs have degenerated USEnet,
> mainly by the absurdity that you need to d/l the whole thread
> to see *IF* there's a reply to your comment/query.
>
> Which results in few multi-stage dialogs.
> So the result is that 'contributors' all rush to have their
> once-off shout.  And it's degenerated to a Friday night
> bar-shout.
>
> Isn't it also problematic to 'hold' 8 blogs open on your
> 'browser' at the same time as using it for other http-fetches ?

That's why people use RSS aggregators.

> What would happen if 10 blogs which were likely to be read
> by a cluster of inetters, were 'harvested' and NNTP-served.
>
> Let's consider the NNTP fields:
> From=ok; Date=ok; Subject=ok; ... seems ok.
>
> The threading would initially be weak/lacking because
> the bloggers normally find it difficult to put that info in
> their message; but as they became aware of threading 
> capabilities they would use it.
>
> Probably the biggest problem would be legally, from
> the owner of the harvested blogs?
>
> Personally, I never use a full 'browser' for blog-reading.
> `lynx` gets me the text, without that crap-in-ya-face.
>
> I've never used RSS. Perhaps that already fixes the problems?

The limited RSS->NNTP gateway in
http://www.greenend.org.uk/rjk/2006/newstools.html is designed with LJ's
RSS in mind, but should be readily adaptable to anyone else's.

-- 
http://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#1003

> What would happen if 10 blogs which were likely to be read
> by a cluster of inetters, were 'harvested' and NNTP-served.

I think gwene.org is a possible answer.


        Stefan

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web