Microsoft, Lay Off Yahoo!
This is not a business analysis. I am not using any fancy tools or statistical programs to calculate what might happen if Microsoft acquires Yahoo!. All I'm writing is straight opinion, with some links to other posts I've read on the subject.
First, I'll cut to the chase: I do not want Yahoo! bought by Microsoft. Ever. End of story.
Obviously not really, or else I would have just tweeted about this.
I used to use only Microsoft products several years ago, back when the Internet was a new thing to me. At twelve, I didn't really care what I used as long as it worked. I searched using MSN Search in Internet Explorer 6, while my mom used Google. I used Outlook Express (and later Outlook) for my email.
Strange, isn't it, that a hardcore Google fan and Firefox user like myself once surfed on Microsoft's terms? Let's just say I saw the light. It was actually i80and who told me about Firefox in the first place and got me to install it. I eventually used some program (I forget what) to alter the Windows Registry and change "Microsoft Internet Explorer" to "Microsoft Big Security Hazard" in the IE title bar. That was before I came up with Suckernet Exploder, but I digress.
Fast-forward to my first hard disk crash (or not -- the disk was still working -- but it gave me a scare anyway and I ditched that computer for a school laptop the next year). I had switched to Firefox for browsing, but still used Outlook for email. After the crash, I quickly switched to Gmail full-time, telling everyone I emailed I was switching addresses. (Gmail did not have Mail Fetcher at that time.)
Once using Firefox and Gmail, I branched out to other places and services, using Google to search the Web for instance. I realized that all the other sites were just easier to use and better than Microsoft's offerings, not that I could quantify or qualify the differences.
At this point, it should be known that I started blogging on MSN Spaces, which became Windows Live Spaces, which became horrible in my opinion (the whole Windows Live thing was stupid, I think). I moved here to Blogger and have been much happier.
Now, while I am certainly not a super-fan of Yahoo!, I have a gut feeling that, should Microsoft acquire them, Yahoo! will go down the tubes. Look at the new Hotmail, for instance. It barely functions in Firefox.
I've seen what happened with Windows Vista, and I don't want the playing field of Internet services narrowed to two major players. Three is fine. Yahoo! and Google keep each other on their toes (I naturally think Google is doing better
and Microsoft sits there playing catch-up to everyone else.
Yahoo! has actually done some good things. They have suggestions in their search box, for instance, which I still have to get on Google via a browser extension. Microsoft's search products are just annoying to me, perhaps because they're still so limited. And the visual design doesn't help.
So aside from the product implications, let me take a look at how Microsoft has been trying to conduct the acquisition. Back on February 1, Microsoft first offered Yahoo! $44.6 billion. They were turned down. They've since sent a letter to Yahoo!, earlier this month, which basically threatened a hostile takeover if Yahoo! didn't cooperate in the next three weeks (now down to a little over two weeks).
Yahoo! again turned them down.
What have we learned? Bullying doesn't work. I hope that when Microsoft takes their discussion to the Yahoo! shareholders in two weeks' time, they also fail to come to an agreement and the deal falls through. (I don't see Yahoo! agreeing to sell in the next couple of weeks, so I'm figuring they'll just keep shut until the deadline.)
In short, my opinion on a "Microhoo!" (as the proposed merger has been called) is, "Nnnnnnnnoooooooo!!!!!!!!" I hope it doesn't come to pass. Ever.
If you're hungry for other opinions or more facts, here are some good articles and blog posts I've read on this subject in the past:
- Microsoft puts Yahoo in a headlock and applies noogies. Wants lunch money in 3 weeks — or else (VentureBeat)
- Microsoft Sends Letter to Yahoo! Board of Directors (Microsoft.com)
- Yahoo Again Rebuffs Microsoft (PC World)
- Microsoft, Just Walk on By (Mini-Microsoft)
My Recent Posting Frequency
I know it's been a week since I last posted here, and that I've been really low on post volume for the last month or two. I'm just getting busier with school and have also been getting distracted by Wikipedia (up to over 16,500 contributions as of right now). Also, there hasn't been as much going on that's really stirred an opinion in me, which is really why I blog. I considered blogging about Microsoft's recent bid to acquire Yahoo!, but found I didn't really have a strong opinion to write about. Blogging without an opinion to generate the words doesn't really make good use of the readers' time.
I apologize for the out-of-context post, and if you think this entry is a waste of your time, don't feel obligated to read it. I certainly don't expect every reader to read every post I write; I don't treat other blogs that way.
When something happens that I really want to talk about, know that I will take a break from school (heh, more like reverting vandalism on Wikipedia) to blog about it. As I said, I just haven't been terribly moved by any of the recent announcements made by Google or anyone else. The Microsoft-Yahoo! thing was lacking substance; plenty of other people made comments, and anything I would have said would have just been repetitive. (Yahoo! turned down Microsoft anyway.) I'll blog about a Y! acquisition when something concrete happens. Meanwhile, my posting frequency is going to be lower for the time being. Perhaps all you readers can get useful stuff done for a change instead of reading my random rants.
Blogger as OpenID Provider
Hot on the heels of last month's release of OpenID commenting, Blogger is now testing support for using blog URLs as OpenID logins. Now not only can other people log in with their OpenIDs from elsewhere, but Blogger users can use their Blogger blog URLs as OpenIDs to log into other sites. I have now deleted the delegation code from my template (which has been working for a while; I just never updated my previous post), as I enabled the beta feature from Blogger in Draft. For now, it's only available from Draft, through a checkbox on the Edit Profile page (rather than in the blog control panel), but Google will probably push it through to everyone by the end of the month.
There are a couple things missing at the moment, like revoking trust from a site you choose to trust "Yes, Always", but it's nearly feature-complete. I'm switching to it. Now I probably won't care as much about Yahoo!'s upcoming OpenID support, but oh well. If Blogger's integrating it, why should I care about Yahoo!'s effort? Granted, that's a large user base they have, and it will probably lift OpenID into the public view, but for my purposes it's useless now.
Yahoo! Launching OpenID?
PC World says Yahoo! is testing OpenID support. I'd say, from the evidence presented (the content of the domain https://me.yahoo.com/, for example), that they're probably right. The page title is currently "OpenID Provider 2.0 -- User's page", with "The user's OpenID provider is https://open.login.yahooapis.com/openid/op/auth" in the body. It seems primed to have nice, simple identity URLs like https://me.yahoo.com/voyagerfan5761. Of course, I delegate my OpenID from this domain (the delegation meta tags redirect requests to AOL), so a simple configuration change on my end can get me using Yahoo!'s system. And when Google eventually support OpenID from Blogger URLs natively (which would be a natural extension of the OpenID commenting launched last month), I can just remove the delegation tags (unless I like my current provider better, in which case I shouldn't have to touch anything).
As more major providers support OpenID, I think that will be a great impetus to start supporting OpenID logins in more places. I certainly hope this Yahoo! thing is true; I'd really like to use them instead of AOL.
Oh, before I go sort pictures from tonight's robotics club meeting, let me say more about the evidence. Aside from the above-mentioned domains, there is also code on Flickr.com photostream pages that would allow users to login with their Flickr identity elsewhere. The code is: <link rel="openid2.provider" href="https://open.login.yahooapis.com/openid/op/auth" /> I hope this is formally launched soon; PC World couldn't reach Yahoo! for a comment, but given all this already-placed code, it seems unlikely that they'd abandon the project now. I can't wait!
Update (01/17): About a week later, there's been an official announcement. Yahoo! OpenID support goes into public beta on January 30, 2008. Looks like they'll be using the Yahoo! homepage as everyone's identity URL, though. Boo! In that case, I'll stick with AOL. But things can change a lot in two weeks... Never mind that. After I found the press release, I saw that users can use a personalized URL at me.yahoo.com or just type in "www.yahoo.com" or "www.flickr.com". So I'll probably be able to delegate after all. Phew!
School Email Sucks
Today's generation of Web servers can do a lot of things: Run a store, provide static information, publish random writings (like mine), host sites anyone can edit (Wikipedia, specifically, and wikis in general), bring news updates instantly (RSS/Atom), and run schools. That's right, run schools. Built on the Apache Tomcat server base, the Blackboard Learning System has been adopted by many schools, including Augsburg College (which has since switched to Moodle, mentioned below) and the notorious Houston, MN, School District, better known as MCoOL (those are the ones I know). Other platforms like Moodle don't seem to be as popular, though Moodle, at least, runs in PHP.
I won't go into specifics -- that's a topic for another day -- but with schools like MCoOL built entirely upon Web-based activities, with no physical attendance, teachers and students need a way to communicate. Fortunately, we don't need to rely on forum-style communication within the software (though such systems are present). Email was invented years ago, before most people even used the Internet, and we can use it for this purpose. Have an assignment to send in? No problem; just attach it to an email and send it to your teacher. Need help? Ask questions via email. It's so convenient, especially with massive systems like Gmail, Yahoo! Mail, and Hotmail to support students with free, feature-rich (some more than others) email accounts.
When we get into proprietary systems, however, problems arise. MCoOL, for instance, started their own Moodle server (to provide home-brew and non-Blackboard courses), with a webmail interface on another port (port 8000). This is OK, and it's great for students just getting involved in the online world. They get an email address (admittedly, one that purges itself every year) and an easy way to get connected with their teachers, without exposing personal information to one of the giants of the Web.
When the administration tries to force geeks like me, however, into using their underpowered system, all that happens is either 1) a frustrated, begrudging geek using a horrible system or 2) an intense email war that goes on for days and eventually will probably result in 1). The situation can be exacerbated when administrators and "IT" staff (who probably have pictures of Adolf Hitler above their desks and on their computer desktops and likely wouldn't know Linus Torvalds from 50 Cent) insist upon closing the system, disabling email from non-organizational addresses, preventing filters, blocking settings pages, and generally making the system (even more) difficult. And all this under the umbrella of "It's more secure for our system."
A school that has AVG Antivirus installed on all its office computers, and uses that system's Outlook add-on vigorously, wants to attribute the "necessity" of a closed system to preventing viruses from outside emails that may probably have better virus filtering than their own. When I send a message from Gmail, for instance, the attachment is scanned for viruses on upload, and will be blocked if it's infected. You can't even send EXE files, not even within ZIP archives (though there is at least one workaround). This, combined with the scanning on the other end (evidenced by AVG taglines in the messages they send), should be enough to prevent viruses.
Gmail's not the only service with virus detection, either. Yahoo! Mail has integrated Norton Antivirus software that scans attachments, too. On every message open, just like Gmail. Even Hotmail has Trend Micro scanning (they used to use McAfee). With this plethora of free services offering antivirus scanning by default in their accounts, why insist that emails from external sources could be tainted?
Freenigma: Free PGP Encryption for Webmail
At the beginning of the month, I blogged about an Internet radio service called Pandora. Now, I'm going to blog about something completely different. I discovered a service called Freenigma, and it provides free PGP encryption for anyone with a webmail account from a major provider (Hotmail, Gmail, Yahoo!, etc.). All you need is an account, one of these email addresses, and Mozilla Firefox (because Freenigma uses a browser extension to display the toolbar; IE support is under development).
So, you sign up for an invitation at www.freenigma.com. You wait for a while, up to a few days. They'll send you an invite code via email, and you then complete the signup process by following a link. Then you install the extension and restart Firefox. Log in to the webmail account you signed up to use Freenigma with and voila, you have encryption.
I won't detail the instructions here; the help files on the Freenigma website are pretty detailed. But your contacts must also use Freenigma, have Firefox, and have a supported webmail account. Aside from that, it's great! Though you have to invite people to your contacts list and then trust them before Freenigma will work. But that's minor.
Anyway, I tested the software (is it really?) and it worked. Both encryption and decryption take place locally on your computer so there's no data floating back and forth to the Freenigma servers. And it doesn't support encrypting attachments yet. But both processes were smooth (though Firefox did slow down for a bit, a result of the intense calculations) and the messages never turned out garbled.
The service is based in Germany, and the site is rather slow. Especially the HTTPS profile management part. It takes me, on cable, more than 5 seconds to select or deselect email addresses in the profile section, search for existing Freenigma users, or do anything else. The fact that the site is in Germany, coupled with the HTTPS encryption/decryption calculations, slows the site down quite a bit. But this doesn't affect the encryption and decryption of messages, fortunately.
The final caveat is the fact that each computer you want to check your email on must have a Freenigma-enabled copy of Firefox configured with your primary email address before you can encrypt or decrypt messages. But for those with a webmail account that's just on the web because they don't want to deal with a software program and check their email from only one or two computers anyway, it works.
So, sign up for the service and try it out. As far as I know, it works with Gmail, Yahoo! Mail, Hotmail, and some others, like maybe AIM Mail (unconfirmed). Get your friends to sign up. Enjoy simple, encrypted communication that no one without a password associated with one of the accounts involved in the message will be able to read. Even if someone hacks into your webmail account, your email will be nicely PGPed and unreadable. Have fun!



