Comments on: Microsoft: We’re not going to fix the bug, we’re going to remove functionality http://tntluoma.com/web/microsoft-were-not-going-to-fix-the-bug-were-going-to-remove-functionality/ Stuff I've Written Down Thu, 04 Mar 2010 19:19:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Olaf Slater http://tntluoma.com/web/microsoft-were-not-going-to-fix-the-bug-were-going-to-remove-functionality/comment-page-1/#comment-1124 Olaf Slater Tue, 10 Feb 2004 14:30:51 +0000 http://tntluoma.com/?p=363#comment-1124 <p>...and for me they have with that killed one of our most important domains and affiliate programs.</p> <p>our Domain www.tr@vel.de, www.tr@vel.ca and www.tr@vel.cn including the affiliate versions like www.michael.tr@el.de or www.single.tr@vel.de are seemingly now obsolete...who is going to reimburse all of the marketing we have done in the past 6 years??? We can't even rely on having the people reaching our site, to even inform them to change something, because the bookmarks and search engine links don't even work locally!</p> …and for me they have with that killed one of our most important domains and affiliate programs.

our Domain http://www.tr@vel.de, http://www.tr@vel.ca and http://www.tr@vel.cn including the affiliate versions like http://www.michael.tr@el.de or http://www.single.tr@vel.de are seemingly now obsolete…who is going to reimburse all of the marketing we have done in the past 6 years??? We can’t even rely on having the people reaching our site, to even inform them to change something, because the bookmarks and search engine links don’t even work locally!

]]> By: JohnP http://tntluoma.com/web/microsoft-were-not-going-to-fix-the-bug-were-going-to-remove-functionality/comment-page-1/#comment-1123 JohnP Thu, 05 Feb 2004 17:26:14 +0000 http://tntluoma.com/?p=363#comment-1123 <p>Couldn't agree with you more!!!! Getting rid of the problem is not a fix.</p> <p>Thank goodness they enabled a reg edit to bypass the fix.</p> Couldn’t agree with you more!!!! Getting rid of the problem is not a fix.

Thank goodness they enabled a reg edit to bypass the fix.

]]>