Slashdot

Usenet had groups that didn't have *.sex.* or *.beastiality.* in it? Man, I missed a LOT during the 90's...

Kibo seems to know how find stuff on usenet.

Usenet is more or less dead with respect to technical discussions. They have all moved to disparate Web forums, the most offensive of which put freely-given advice from volunteers behind a paywall [expertsexchange.com].

There actually are a couple of good forums for Win32 advice, such as CodeProject [codeproject.com], and Google is still the best way by far to search MSDN, by adding site:microsoft.com to your query.

But Google's handling of Usenet, including (but not limited to) their unauthorized alteration of message content by mangling email addresses, has not been healthy for the venue.

hi, you must be noob to the internets. this usenet thing went the way of horse drawn buggies and panning for gold. I would suggest you use the web that is world wide (www). this will help you significantly. thank you sir.

Nobody really reads much usenet anymore, and during the decline earlier in this decade, the problem was that the poster would post but the replies would come in private email. So yes, the question might get answered, but the answer never got shared.

The reason? Spam. Usenet posts became the #1 source of email addresses to spam because anybody could easily and cheaply hook up to a usenet feed and just gobble them up. So nobody posted anymore 'cause nobody wanted their address to end up on a spam list from hell.

Eventually with little proof online that anybody was reading the questions, people just stopped posting them.

Usenet was a wonderful thing when it was needed. Today, while the idea of a central yet open (re: infinitely cloned) repository of all topics of conversation may seem nice, it'll never happen again so long as spam is a problem.

If you think about it, most google apps have a few really cool and flashy features (which is why I like to use them), but then tend to have lots of UI bugs. Also, it's pretty much impossible to actually report bugs to google. At best you'll find some google group on the product that no engineer ever looks at.

Aside from the one mentioned google groops had lots of basic bugs. Until recently reading comp.lang.c++.moderated on google groups caused all sorts of problems because they weren't properly handling the escape of the ++ characters in the url (every time I clicked on a link I'd have to edit the url manually to get it to work). It took them years to find out about that and fix it. Although it was a daily annoyance to me, I had no way to get it into any kind of bug tracking system.

Even worse I've *never* been able to use google gears or google docs without major bugs and error messages, no matter what browser I used (including chrome).

Gmail, google reader, and basic search are probably the only google web apps I've seen that don't have lots of bugs. I actually have a higher opinion of their desktop apps.

Reader, which is awesome and you should check out btw, used to be very bug ridden, but it's massively improved over the last year and a half.

Search actually is kind of problematic in that the basic search works fine, but lots of the extensions are broken. Last time I tried subscribed links was broken. As in, it didn't work *at all* and there was no workaround.

I think honestly that while they obviously have high quality engineers, they just have sucky QA. I think that they focus too much on unit tests, and have forgotten that a lot of basic bugs can only be detected by someone hammering on the interface of the production system and logging bugs.

Also, I think they've basically destroyed their ability to have beta software, by making all of their software beta. Now, user have no way of distinguishing what is truly production ready software from stuff that clearly isn't, except by trying it and getting burned.

Google has pretty completely fucked up in their handling of usenet archives. Some examples:

1. I was searching for a particular post by message ID. It was a post from someone who used Google to post the damn thing, for God's sake, and Google still could not find it. It was definitely there, because if I went into that newsgroup in Google's usenet reader, and manually found the thread, and expanded it, I could see it. It just could not be found by a message ID search.
2. I wanted to search for a post of mine. I did a search for my name, in quotes. It returned something like 6 posts. It used to return tens of thousands (I've been on usenet since 1984). I then searched for "bill gates". That returned a whopping 9 hits. I then tried some random troll's name, and got thousands of hits. It took several weeks before they fixed this, and "bill gates" and myself were back to a large number of hits.
3. Now it's broken again. I get about 2000 results for myself, 3000 for Bill Gates, 3000 for Linux. I haven't found anything that gives more than 3200 now.
4. The search display is almost completely worthless. They seem to be in the midst of changing this, so I will complain about both the old results and the new results. Old results first. Say a long thread has several posts that match. It shows one of the posts, and then shows indented other matches after that. Good. Except that it seems to do this for each matching posts. Net result is that many posts are displayed multiple times. I've seen cases where the first 10 pages of results are all from one thread, and there's no good way to skip that.
5. Lately, it's been just showing one result for the whole thread, which you can click on to get the thread. That's better, but there doesn't seem to be any good way to go to the specific posts that match. When you open the thread, it will have highlighted a particular post, but there's no apparent way to then repeat the search in the thread to find other matching posts.
6. If I find a post of mine, select options, and click the link to find more posts by this author, it is now only finding about 1000 posts. Similar results when I try this for other people's posts.
7. They've fucked up dealing with their authentication server. If you are logged into your Google account when you go to groups, it sometimes takes up to 20 seconds or so for the page to appear. If you aren't logged in, it appears instantaneously.
8. When you view the headers of a post, and click the "..." to expand the from address, it takes you to a page where you have to solve a CAPTCHA to get the full address. That used to work. Now after solving it, it just takes me back to where I was, without expanding the address.
9. They are very inconsistent. I've asked other people about some of the above problems, and the usual result is that some people will be getting them, and some will not. As the problems go away for some, they start for others. It looks like they have multiple servers, and some are working better than others.

We really need some competition for Google in this area. There's some very valuable stuff in the usenet archives, and that needs to be in competent hands.