MySpace is preparing to add Facebook Connect features to its main service, we’ve confirmed from a source within MySpace. This will be the first time MySpace will publicly conceded defeat to Facebook over ownership of the social graph, and it’s more than a touchy subject internally.

So touchy, in fact, that my source tells me that by simply breaking the news early the whole rollout might be ditched or delayed. A key part of the launch is apparently a serious amount of message massaging by MySpace PR on what this means for MySpace.

Earlier this year the MySpace UK team added Facebook Connect features to a fan video without, apparently, the knowledge of upper management at MySpace. MySpace also quietly (silently actually) rolled out sharing on Facebook for MySpace videos recently. This new Facebook Connect rollout is being done very quietly as well, we’ve heard. Some very senior MySpace execs seem to have no idea it’s happening.

So what does all this mean? In the next week or two we’ll see at least a limited rollout of Facebook Connect on MySpace. Or, we won’t. Ah, the joys of having co-presidents to take your company to the next level.

Earlier today, Adobe and Google announced a partnership that integrates Flash right into future builds of Chrome. At a time when Flash is under fire from both Apple and HTML5 advocates, this is a huge win for the technology. But one thing that wasn’t clear from Google’s post on the matter (and Adobe’s comment to us) is what this means for the upcoming Chrome OS. So I asked.

“We plan to bring these benefits to Chrome users across all platforms, including Windows, Mac, Linux, and Google Chrome OS,” a Google spokesperson tells me. In other words, yes, this deep Flash is coming to Chrome OS.

Here’s why this is significant: when Chrome OS-based netbooks launch later this year they will not only compete with Windows-based netbooks, they will also compete with the iPad. The iPad, of course, will not run Flash. This could be a major differentiating factor when people are deciding which machine to buy this holiday season. Especially if those people are addicted to Farmville (which is, of course, Flash-based).

“Netbooks aren’t better at anything,” Apple CEO Steve Jobs said while unveiling the iPad back in January. This deep Flash integration may give some users reason to disagree.

And don’t forget, eventually, there will be Chrome OS-based tablets as well. That Apple/Google rivalry keeps getting more interesting.

What this means is that anytime someone in your tweet stream sends out a tweet from Foursquare (which, to the annoyance of some users, happens automatically at times), that Foursquare link (shown as a 4sq.com URL) will be able to be opened in Tweetie in a way that displays the location information in a nice format. When a tweet is eligible for this feature, you’ll see a purple square logo in the upper right hand corner of the tweet in Tweetie.

When you click on a Foursquare link, you’ll be taken to a page that shows the venue’s address and phone number as well as the Foursquare mayor of the place. If you click on the address you’ll load a Google Map showing you exactly where it is. If you click on the phone number, you’ll be able to call the place right from the iPhone. Below all of that, there is a button to open the venue in Foursquare, which launches the Foursquare iPhone app.

A couple other new features in Tweetie 2 include Vodpod video uploads and the ability to attach messages along with your TwitPics to that service.

Look for this Tweetie 2 update soon in the App Store (it will be version 2.1.1). Meanwhile, Tweetie Two for Mac should be released in a private beta in about a month, according to new info shared on MacHeist today. Tweetie for Mac will soon be added to the nanoBundle 2, and in anticipation, they’ve added this message:

As a MacHeist customer, you’re not only receiving a free upgrade to the upcoming, highly anticipated Tweetie 2 – we’ve also arranged exclusive access to the pre-public beta for you guys!

Have fun using the best Mac Twitter client for now… and stay tuned for an email from us in about a month with your invite to the future of Mac tweeting.

While digging through the Chromium forums back in November looking for clues about the then-unreleased Chrome for Mac beta, we stumbled on an interesting bit of information: Google was moving away from supporting Gears going forward. While this move was obvious for some given Google’s heavy investment in HTML5, Google hadn’t talked much about what would happen to their plug-in that allowed for things such as offline access to Gmail. They’re talking now.

In a post yesterday on the Gears API blog, Ian Fette from the Gears team comes right out and says it in his title: “Hello HTML5.” Fette notes that the reason there haven’t been many updates to Gears in the past several months is because the team has shifted its focus towards implementing the same features into Chrome through HTML5. So far, this includes Database API, workers, local storage, and web sockets. And soon, LocalServer API and Geolocation will be a part of Chrome as well, Fette notes. In essence, all of these features make Gears unnecessary — well, at least in Chrome, which Google obviously wants you to use.

Because of this shift of focus, Fette notes that support for Gears will be increasingly “constrained in scope.” What this means is that beginning immediately, they will no longer be supporting Gears on OS X Snow Leopard (and later). Meanwhile, Gears support in Firefox and Internet Explorer will continue in limited form for now. But both of those too will eventually be killed off. “We will not be investing resources in active development of new features,” Fette writes.

Really, all Google is waiting for is an effective way to migrate Gears-enabled apps (and their users) over to HTML5. While there is currently no good way to do this, it seems as if Google just may wait for developers to drink the HTML5 kool-aid and then kill of Gears support entirely — even if there are still some who are using it.

I’m all for this. As I wrote back in December, I’m of the opinion that plug-ins are perhaps the biggest inhibitor of a unified web. That is, a web where everyone sees the same content the same way, no matter what browser or which OS they’re using. It doesn’t matter if those plug-ins are made by Google (Gears), Microsoft (Silverlight), Adobe (Flash), or anyone else.