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.
    Bugtoaster Calls New.net Plugin Defective | Log in/Create an Account | Top | 35 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: Bugtoaster Calls New.net Plugin Defective
    by steve@new.net (SteveC) on Monday November 26 2001, @02:25PM (#3861)
    User #2430 Info | www.new.net
    I want to correct some inaccurate and/or incomplete information that someone culled from BugToaster.com regarding our client software. We were notified of this particular problem on November 8 and responded the same day. Thanks to their detailed reports, we have determined the cause of the bug and fixed the code, and it is in QA. We will release a new version of the client as soon as it passes through final testing (which includes, by the way, BugToaster's software).

    There are actually two separate bugs that account for nearly all of the incidents reported by BugToaster. The reason these particular bugs have gone undetected for so long is that the situations under which they would cause a problem are quite unusual. The only time they appear to occur is when either an install or uninstall of the plug-in has been interrupted. Given that our software typically takes only a few seconds to download, it doesn't seem unusual that we haven't seen this before now. One other situation under which we occasionally see problems is when our files have been corrupted by the subsequent installation of other plug-in software. We can't control what users install on their PCs, but we can diligently follow up on any reported problems. Regardless of the source, we take every bug seriously, and we've worked quickly to fix every problem we know about.

    As for the assertion that our uninstall doesn't completely remove all files, while literally true, is a bit misleading. The only file we leave behind is an Active X remnant that has no effect on the operation of the PC and is similar to the residue of many other programs. In addition, if someone does not reboot after the uninstall as instructed, it may appear that a .dll file is still there, but this will disappear the next time the user reboots. No matter that these are harmless situations, they do create misunderstandings. Accordingly, we are working on changes to the uninstall program to remove these files and will release this functionality in a future build.

    Like every other software product, despite rigorous testing, some bugs creep through. Given the tens of millions of copies of our plug-in that are out there, we are quite pleased at the low volume of support calls and emails we get. And when we do get complaints, we respond immediately, and we have the benefit of being able to update the clients automatically when fixes are available.

    I trust this clears up several misconceptions that perhaps lack of factual information has fueled. Please feel free to email me directly if you have any further questions or concerns.

    Steve Chadima
    New.net
    [ Reply to This | Parent ]
    Re: Bugtoaster Calls New.net Plugin Defective
    by Anonymous on Monday November 26 2001, @04:24PM (#3863)
    Who cares? Why would anybody modify the way their address bar works anyway. I have heard that some of your download partners are seemlessly installing your plugin without the users knowledge. Any comments Steve?
    [ Reply to This | Parent ]
    Re: Sorry Steve,
    by Anonymous on Monday November 26 2001, @11:47PM (#3865)
    Sorry Steve,

    No matter what you do, New.net is still not a recognized registry by ICANN. There are enough groups opposed to New.net to ensure that New.net will never be given any real tlds to operate. I would venture to say that IOD would be given .web by ICANN before New.net would be allowed to participate in any meaningful way within ICANN.

    The BugToaster issue only highlights what many have known for some time- that New.net is not operating a real registry, only passing off third and fourth level domains as tlds. Of the "75 million" or so "potential users" of New.net, how many domain names have been purchased? And of those domain names, how many DO NOT correspond to the names of famous marks that speculators/domain scammers have purchased with the false hope that sometime, someday New.net would catch on with the general public.

    Sorry Steve, you wish you were NeuLevel.
    [ 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