Between the ticker and the plans to auto-share even more activity on the timeline, I’m beginning to think that Facebook should call itself Firehose instead.
I’m tempted to ask, “Who the hell wants this?” but based on past experience, that usually means I’m just not in the target audience.
TechCrunch | Share Buttons? Ha. Facebook Just Schooled The Internet. Again.
(Originally posted on Google+)
Firefox has been testing a new release that detects and closes crashed plugins (instead of letting them crash Firefox entirely) for several months, carefully making sure everything was working before they released Firefox 3.6.4 last week.
Within days, they released an update. I couldn’t imagine what they might have missed in all the beta testing. Katie wondered if the beta testers hadn’t been testing the limits.
You want to know what convinced Mozilla to issue an update so quickly?
Farmville.
Apparently Firefox was detecting Farmville as frozen and closing it. It turns out that on many computers, Farmville regularly freezes up the browser for longer than 10 seconds, and its players just deal with it and wait for it to come back. Mozilla decided that the simplest thing to do would be to increase the time limit.
What this tells me is that the type of person willing to beta-test a web browser these days is not likely to be playing Farmville — or if they are, it’s likely to be on a bleeding-edge computer that can handle it without 10-second freezes.
In more practical terms: Mozilla needs to convince a wider variety of users to help test their software!
An experiment: I’ve modified* Twitter Tools to create digest posts as drafts instead of publishing immediately. That gives me a chance to edit a week’s worth of random thoughts and links down to the interesting stuff, clean things up a bit, expand things that could use more detail, and remind myself of items that I wanted to write more about later.
If it works out, and if the plugin still offers digests after it’s rewritten to use OAuth, I’ll probably use this same setup to make sure I keep on top of linkblogging at Speed Force.
*It was pretty simple. I just looked for the function that creates digests, then changed the post_status from publish to draft.
Facebook polls need a “This is BS” option. Too many are based on false premises or are of the “Threat or Menace?” variety. 🙄
Amazing how many “people” are sending Facebook messages to the postmaster account, offering helpful links to resources for *ahem* improving uptime.
On a related note:
Google’s Social Graph thinks I own Cute Overload. It seems to treat all LiveJournal syndication feeds as one profile, and I linked to K2R’s LJ feed with XFN.
Forget Ashton Kutcher and Oprah, forget #unfollowfriday, forget 25 Random Evil Things about Twitter — the key problems with the social media / microblogging / broadcast IM / whatever you want to call it service boil down to two problems:
Twitter’s prompt is not something general like “What’s on your mind?” It’s “What are you doing?” That encourages people to post things like “I’m eating lunch” or “Just got into work,” or “Posting on Twitter.” Presumably what they mean is “What are you doing that you think people would find interesting?” but of course that’s too long a prompt from a usability standpoint.
The thing is, there’s no reason to broadcast the mundane to the world. Don’t tell me “I’m eating soup.” Tell me, “Just learned that gazpacho soup is best served cold. I wonder if they eat it in space?”
Unfortunately, that means the signal-to-noise ratio can get pretty bad at times.
Twitter posts are limited to 140 characters of plain text so that the your name and comments can fit in a standard SMS message. Now, this is great if you use Twitter via text messages on your mobile phone. It’s not so great if you use Twitter on the web, or through a smartphone app like Twitterific on iPhone or Twidroid on Android, or through any of the zillions of desktop apps.
I don’t have a problem with the 140-character limit itself (it can actually be liberating in a way), though it would be nice to have some formatting options beyond all-caps and *asterisk bolding*.
The real problem is that links have to share that limit. URL-shortening services have exploded lately as people try to squeeze links into the tiniest space possible to save room for their precious text. Even if you use something as short as is.gd, just including one link means you’re down to 122 characters.
Plus URL shorteners come with a host of problems, in particular the fact that they hide the destination. That’s no big deal if the target matches the description, or if it’s a harmless prank like a Rick Roll, but it’s all too easy to disguise something malicious.
Seriously, if you got an email that said something like this:
Look at this! http://example.com/asdjh
Would you click on that link? Even if it appeared to be from someone you know? That’s just asking to get your computer infected by a virus, trojan horse or other piece of malware. Or to see something you wish you could unsee.
I hesitate to bring up Facebook as a good example of anything, and I know the current layout is largely reviled by its users, but they really got posting links right.
When you want to post a link to your Facebook profile, you paste in the full URL. Facebook reads the page and extracts the title, a short summary, and possible thumbnail images. Then you have the normal amount of space to write your comment. Continue reading
