Slashdot Mirror


Google Flips Back to Groups Beta (Again)

afabbro writes "Google backed off its beta of Google Groups within 24 hours of making it mandatory for all users. You may recall that its lack of features (date searches), unwanted features (e-mail masking), and clunky user interface met with a very chilly reception here. Unfortunately, as of December 5th, Google Groups Beta is back and you can't get to the original (wonderful) Google Groups anymore. Be sure to share your opinion with Google."

9 of 363 comments (clear)

  1. Email masking... by JPriest · · Score: 5, Insightful

    What would be so bad about Email masking?

    --
    Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
    1. Re:Email masking... by Lxy · · Score: 4, Insightful

      What would be so bad about Email masking?

      Every so often I need info a thread that has gone dormant. Since a reply to the thread won't get a response, it sometimes makes sense to e-mail the author(s) directly. I have done this a few times, and even though sometimes the thread is almost 2 years old, I still get useful replies.

      I agree that public listings of e-mail addresses is a good way to get spam, but it is useful enough that I hate to see it completely removed.

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    2. Re:Email masking... by HeghmoH · · Score: 4, Insightful
      It's bad for two reasons. First, you're changing the contents of the post without notification and without the consent of the author. Second, e-mail masking can cause problems with false positives. For example, in Objective-C, there are several keywords that start with @, such as @interface. Some archives of Objective-C mailing lists have e-mail blockers, and so you see weird stuff like:
      <E-MAIL REMOVED> MyClass : NSObject { .... }
      I doubt if Google's e-mail blocker will be that stupid, but you never know what kinds of false positives it could find.

      There is also no purpose to it. Every single post ever made to usenet has already been harvested by spammers, so what's the issue with making them public?
      --
      Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    3. Re:Email masking... by Anonymous Coward · · Score: 5, Insightful

      The bad thing about e-mail masking is that it makes it hard to send mail to an author who has put an unmunged email address on their messages. These authors have put their mail addresses on a public forum (or decided to mung their addresses themselves, or put an invalid address) so why should Google go out of their way to "protect" people that don't want to be protected?

      I've received mail before from people who have found a post of mine on Google groups and wanted to ask me a quick question and I've always been happy to respond.... Why should google stop those people from mailing me in the future?

  2. Re:boo by BillyBlaze · · Score: 3, Insightful

    I think it's clear that when you post something to Usenet, you understand that it will be copied, without any further permission requested from you, onto news servers and to news clients around the world. If someone doesn't like that, they shouldn't have posted - they have no right to tell Google whether or not they can charge people for their interface (one of many) to access the newsgroups. (Obviously, one can only licence their own copyrights, so I'm not saying you can share other people's copyrighted stuff.)

  3. Threaded view? by Malc · · Score: 3, Insightful

    Am I blind, or is there really no way to get a threaded view of the headers? The flat view useless.

  4. Ugly fonts! by ZorinLynx · · Score: 4, Insightful

    I hate the new proportional font they adopted for messages. Usenet is meant to be looked at in a fixed-width font! Proportional fonts totally screw up lovingly crafted sigs, ascii art, and so on.

    Who was the nutcase at Google that thought Groups needed a facelift? It was FINE AS IT WAS. I don't know what they're smoking over there.

    I'm going to use the Canadian Google Groups (google.ca) in defiance for now, but I bet it will go away soon as well.

    Arrrgh. Companies can't just leave a good thing alone.

    -Z

  5. More Important Than The Human Genome Project by paranerd · · Score: 4, Insightful

    Warning: I go off the deep end on this subject. But I'm sincere for all of that.

    DejaNews is more important for our society than the Human Genome Project. Just because only Slashdot-types (mostly) understand that doesn't make it less factual. It's wrong to leave it in the hands of one company.

  6. Modifying articles is a copyright violation by Anders+Andersson · · Score: 4, Insightful

    I recently retrieved all articles in Google Groups posted using either of the four e-mail addresses I remember having used for Usenet (there were 429 such articles, posted between 1985 and 1997). I never mangled my e-mail address on purpose, but I had mostly stopped posting to Usenet when spamming took off in the mid 90's. Those four addresses have since all been disabled, although I tried to keep them alive as long as possible, as a matter of principle (I preferred using blacklists to silence annoying senders rather than give up my freedom to express myself in public for the convenience of spammers).

    Google not only masks the address of each poster, but also anything in the article itself that merely looks like an e-mail address, including Message IDs. When I quote somebody else, referring to the author of that quote by name and e-mail address, Google sees fit to remove that identifying information. I did not approve of them mangling my articles in this way; that was not part of the understanding of how my postings were to be processed when I made them.

    Since I retain the copyright to my articles, I have the right to control in what way they may be disseminated by others. I'm perfectly happy with Google or anyone else archiving my articles for future readers, as long as they don't modify what I have written. If someone wants to quote a significant portion of an article rather than all of it, that's fine too, as long as they attribute it to the original author, but that's not an archive, and that's not what Google is doing. Instead, Google is systematically erasing information detailing exactly who wrote what part of each article. What if an e-mail address is used as the sole identifier of the author in an explicit copyright notice, will Google destroy that information too?

    As for Google allowing individual authors to opt out from having their articles archived at all, that's fine but it's no excuse for systematic copyright infringement, however small. To make a rough analogy, that's like Napster allowing copyright holders to request their own titles to be removed from Napster's database on an individual basis, while continuing to distribute anything the copyright holders haven't complained about (maybe because they haven't found out about it). For distribution to be legal, copyright requires authors to opt in to it, not fail to opt out. If authors want to opt out from enforcing their rights, they do so by neglecting to sue.

    I want to tell Google: You can continue distributing my 429 articles if you like, as long as you distribute them verbatim, without any modifications of what I once wrote. Google however does not provide me with that option. Should I really have to send Google 429 removal requests, and then submit my articles to some other public archive, just to make that point? What a waste.