Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #998
| From | no.top.post@gmail.com |
|---|---|
| Newsgroups | comp.os.linux.networking, news.software.readers |
| Subject | Could converting blogs to USEnet work? |
| Date | 2012-01-21 18:00 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <jfeuf6$cc0$1@dont-email.me> (permalink) |
Cross-posted to 2 groups.
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.
Back to comp.os.linux.networking | Previous | Next — Next in thread | Find similar | Unroll thread
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
csiph-web