Eleven percent of those under the age of 25 would interrupt sex for a message, and 24 percent under 25 would answer a message in the bathroom.

…is a bit silly.  But really, it seems to me almost like it’s a restructuring of social norms.  Is it a problem, or is it just an evolving expectation that we have with the immediacy in communication and relationships?

Although, if you’re interrupting sex for a message you’re just not doing it right.

“Considering the amount of content on the Web that uses Flash — not allowing your consumers to access that content isn’t showing off the Web in all its glory.”

And,

“Apple’s business model is more trying to maintain a proprietary lock.”

And,

“the 10.1 version will do what Jobs wants it to do.”

I can hear the canned laugh-track as I read it.

I’m also not saying that Adobe is a shining star when it comes to some of the choices they’ve made but overall, I’d say they’ve done a pretty good job at holding up the bar in the design world (even if they’re responsible for making drop-shadowed text ubiquitous).

It takes a lot of guts for Emmy Huang, the Project Manager for Flash Player, to write this post.  It displays a humanity, although I’m sure Jobs wasn’t implying they’re lazy robots.  It also highlights problems in their process.  But I do wonder about this:

“I want to reiterate that it is our policy that crashes are serious “A” priority bugs, and it is a tenet of the Flash Player team that ActionScript developers should never be able to crash Flash Player. If a crash occurs, it is by definition a bug, and one that Adobe takes very seriously. When they happen, it can be the result of something going on purely within Flash Player, something in the browser, or even at the OS level. Depending on where an issue occurs we work to resolve the crash internally or with our partners.”

She then goes on to outline the timeline of how the wheels fell off the wagon.

Some points:

• crashing bugs should be fixed and released immediately, i.e. the day they fixed it.  Telling me that it was fixed 3 months ago and we’re only going to see it with the next release which is…when?…only makes me froth.
• it’s not as if Flash 10 is the first version where the player has had serious issues and caused crashing.  It’s almost a defining characteristic of the platform since version 1.

No amount of denials from upper management is going to make the existence of problems untrue and no amount of apologies from the developer level is going to change the fact that if it’s not in our hands, it’s not fixed.

Adobe needs to fix their process, like a decade ago.  I know it’s complicated, and I know the software’s a crazy rat’s nest.

For what it’s worth, I don’t think Flash will ever completely go away.  Flash as a video delivery vehicle always kind of bother me as over-engineered and overkill.  But as a platform for other things I think it will still have a place, albeit with a much lesser presence.  Nonetheless, Adobe, I don’t think it had to be this way.

Saving a local draft fails. Not iust fails, but completely doesn’t happen at all. Writing a post of any length goes into /dev/null. Seems it’s not an exactly uncommon issue as this forums post shows but for some reason isn’t reproduceable.

Saving as a draft to the server is fine, though.

It’s true, though: if you’re a witch, you won’t drown.

In the same spirit, I’m going to start a company called Apple. I think they’ll understand when my legal team demands they change their name. Not that big of a deal.

I did a bit of digging around the site’s help pages and I’m sure it’s no surprise to anyone that it’s pretty much impossible to contact an actual person to help you out.  I do have to credit the CEO Mark Zuckerberg’s enormous ego with creating what is possibly one of the most successful sites with the paradoxically worst support system ever.  The customer forum is composed of an unbelievably byzantine interface link structure that rivals Microsoft’s.  It’s pretty much impossible to find the answer to a problem which they don’t deem to be an official “issue”, nevermind one they do.

Anyway, I did eventually find a solution (without input, of course, from any Facebook staff, possibly from Google).  For some reason, they’ve started scanning their database for contact emails that they deem “generic” (e.g. “mail@…” and “info@…”).  At their request, I changed mine to something else, something equally generic but not what they’re flagging and then set it on my email server side to forward to the address I had previously given Facebook.  This seemed to satisfy it.

I did notice in the “help” pages that some customers had tried to follow Facebook’s instructions but on doing so, became locked out of their accounts.  They’re now stuck in purgatory.  I won’t dwell on this too long, since it’s only a matter of time until I too, am banished with all my contacts, groups and fan pages blown to dust.

Seriously, Facebook:  F.O.

Also, anecdotally (from the “help” pages), more than one customer had reported finding a help page in there somewhere that directed them to contact Facebook support at the following address: “info@facebook.com”.

I’m very, very crankie right now.  I swear to god, I hope they’re quick about fixing it.  Safari is feeling mighty close…