ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    New.net in financial trouble? | Log in/Create an Account | Top | 47 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re: Wrong
    by fnord (groy2kNO@SPAMyahoo.com) on Wednesday April 10 2002, @10:55PM (#5802)
    User #2810 Info
    Assuming there have been millions of downloads of new.net's plugin when bundled with other apps, and assuming that many thousands of those plugins were installed (some certainly were as not all these other apps have been above board about the bundling) plus how many times have you installed a free download and just agreed with a bunch of clickwrap agreements, then if you go to CNET here and see that to date there have been 1,669 downloads of the freestanding plugin in over seven months, what does that tell you? There have been less than 2,000 people who actually want the plugin. New.net pays for it to get bundled so that many thousands, probably even millions, get it installed with or without their informed consent. That is why new.net is providing it via its download partners (most all of whom BTW also have other proggies packaged with them in similar fashion, not just the new.net plugin). If you want to learn more about this practice, do a google on foistware.

    FWIW, ZDNet is a little (actually a lot) slow on this story, as I've pointed out here on ICANNWatch that new.net was being bundled in this fashion, and with these problems, since the day they first did this many months ago, and I've pointed it out numerous times since. Also FWIW I installed the plugin on a machine the day they went live just to test it (due to privacy/security concerns). My testing showed that I needn't have had such concerns (though as it autoupdates without asking one can never be sure). The plugin also worked properly and was well behaved, which is more than I can say about a lot of downloads, particularily the often buggy first version. However, when the download was first offered on CNET I downloaded it on the same machine and installed it. It didn't tell me whether or not to uninstall the earlier version, so I didn't. It also didn't tell me much of anything when I did the install (of what was presumably a different version than I had). Once installed I couldn't access the net at all, either by dialup or cablemodem (via a hub). So I uninstalled it, got connection back, and haven't used the plugin since. As I've never seen or heard of a new.net site I'd want to visit, this was no great loss.

    I used to be of the opinion that new.net and alt roots and XTNS and all the rest are free to do as they please (which isn't to say I'm not free to point out their shortcomings if I find them). While I still think they can do as they please, I don't think they're particularily healthy for the namespace. I've thought about registering .info domains, and know others who want .biz domains, but I think both will be a hardsell with the public. There has now been so much negative press about some repurposed ccTLDs, and new.net, and one .usa, and etc. that the public, both end-users and many of those looking to register one or a few domains for actual use, are shying away from using .biz and .info (and the 5 other new ICANN TLDs will also be affected to some degree).

    I don't blame new.net or the others for this (as long as they are open and upfront and above board with what they are doing, new.net has been, as has ORSC, some others less so, all the way to outright scams). I blame ICANN for being so slow in rolling out new TLDs, and then making a horrid mess of things when they did (certainly .biz and .info have had more bad press, most of it well-deserved, than all the alt roots and overlays combined). The internet is seeing ICANN as damage and routing around it. Depending on whom you trust to do your routing, some of them aren't above causing damage either. Things could be worse, if you install Morpheus instead of Kazaa, you might wind up with another problem. Type in amazon.com and instead you're taken to one of their partner sites. This is arguably worse than new.net et al as most all of them add to the ICANN root, they don't mess with it. I expect this redirect exploit to become much more of a problem in the near future. Caveat emptor, and if it's a 'free' download, ditto. -g

    [ Reply to This | Parent ]
    Re: Wrong by fnord
    Re: Wrong
    by RFassett on Thursday April 11 2002, @03:00AM (#5804)
    User #3226 Info | http://www.enum.info
    fnord writes: "I blame ICANN for being so slow in rolling out new TLDs, and then making a horrid mess of things when they did (certainly .biz and .info have had more bad press, most of it well-deserved, than all the alt roots and overlays combined). The internet is seeing ICANN as damage and routing around it."

    Well said. ICANN's role is to fulfill its technical mission towards influencing a unique and global namespace that includes competition. It seems to me that if the situation evolved where half the world exclusively use the legacy root and the other half something different, ICANN will believe its mission to be fulfilled in that the legacy root will still be a unique and global namespace. I think this is a statement certain current members of ICANN would endorse, but is just my own conjencture. Whether you view the legacy root as a U.S. resource or a world resource, the bottom line is that ICANN is allowing it to be butchered by implementing artificial restraints outside of its technical mission. We'll see how far this evolves in terms of its global impact upon end-users.
    [ Reply to This | Parent ]


    Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com