ecaron

Most interesting point: http://www.thefancy.com/ (the promo site in the video) ISN'T EVEN USING THE SERVICE!!!

I'm anxious to know if http://www.crashie.com/ brings it down, it doesn't in Win8 but I suspect Win7 is still vulnerable...

And the follow-up to that even-better article (http://ventspace.wordpress.com/2013/01/31/follow-up-on-direc...):

    The message said “DirectX is no longer evolving as a technology.”
    That is definitely not true in any way, shape or form. 
    Microsoft is actively investing in DirectX as the unified
    graphics foundation for our key platforms, including Xbox
    360, Windows Phone and Windows. DirectX is evolving and 
    will continue to evolve. For instance, right now we’re 
    investing in some very cool graphics code authorizing 
    [sic] technology in Visual Studio. We have absolutely no 
    intention of stopping innovation with DirectX,
    and you can quote me on that.

> When Ralph Nader does this sort of thing he is lauded, I don't think Musk's criticisms should be viewed in any different light.

Just as a point of fact, Ralph Nader was hardly universally lauded when he entered the arena of public critiques: http://en.wikipedia.org/wiki/Unsafe_at_Any_Speed#Criticisms

For anyone making a shift from 1.7/1.8 to this, please don't overlook the jquery-migrate plugin (https://github.com/jquery/jquery-migrate/).

You/we don't have to suffer the headaches of "what the heck changed since the version I was using...", the jQuery overlords have really done us a great service in offering this cool migration checker - so let's use it!

The guys at Smarty did some pretty good analysis on the @ operator - specifically in cases where implementing it improved performance: http://blog.rodneyrehm.de/archives/12-Improving-Disk-IO-in-P...

I would have liked it the jQuery API documentation would be closer to the PHP.net documentation. For instance, I want to know the options for $.post - going to http://api.jquery.com/post/ would sure be nice (and even if it didn't exist, it could do a search for "you might have meant...")

For people unfamiliar with PHP.net's configuration, going to php.net/<function or whatever name> will go to the function if its known or search if it isn't (like http://php.net/strapos)

Yet another great example of the problem with Twitter and not having any policy/business-plan for dealing with squatter accounts.

They should, if account is unusued for 3 months, send an email saying "are you still using this" and just ask the person to login to verify they are. If that email (and multiple subsequent) aren't answered within 3 months, the person initiating the "claim unusued handle" request gets the handle.

How is this better than the decentralized Persona Identify solution that Mozilla's promoting: https://developer.mozilla.org/en-US/docs/Persona/Identity_Pr...

I'm encountering something similar this Christmas. We'd given my wife's grandma a Chromebook - and it has died of its own accord after just 14 months.

After talking about the replacement, she nearly begged for a Windows or a Mac. By name. This same woman that doesn't think she can run the microwave while being on the cordless phone.

We (Linux, and I'm lumping ChromeOS into this albeit a different beast) aren't going to win the marketing battle. With sites like Netflix not working on Linux and "you'll get it if you try it for two weeks" UX mentality (looking at you Unity), we're not going to win the experience battle - the only one where we stood a shot. Short of a product that thoroughly feels superior we just can't expect consumers to cope with a product just to "fight the [men]". And until that happens, I (and I suspect many fellow nerds) are following this round of the cycle and moving our families away from Linux (again, for now.)

This "bug" has been resolved since 01-Mar-2012 when 5.4 was released, and there's a very straight-forward explanation of it if people would just RTFM.

This is the worst part of the PHP community - all the in-fighting when the core developers don't bend over backwards to accommodate short-sighted programmers who know their conflicting demand is the one that should be heard.

Interesting they call this "live" now, TechCrunch has been running on WordPress.com's "VIP" platform since early 2010.

I didn't. I nuked my personal stuff, and then worked hard to put the machine in a state that my replacements would find useful to reproduce my processes.

I think they get changed by the server itself, without human intervention.

If the poster has enough karma, I think the HN code should trust the user's title over the <h1>.

Which gets you close, but not close enough to say "I've testing in IEX." Although the DOM modelling is very close, the CSS and JS quirks between different versions aren't emulated enough in F12 to catch the problems that using the actual version would expose.

The biggest problem with these is that they all have an expiration date - and Microsoft frequently forgets to update them. And getting through to Microsoft to tell them it is out of date... forget about it.

Solr's docs also leave a lot to be desired. The wikis are a mess and knowing what is still relevant (e.g. not deprecated) is frequently a crap shoot.

It'd be great if their docs had versioning (like the Apache HTTP Server Project), but I suspect that isn't on anyone's roadmap.

After the 3rd thing that was wrong about Solr, I stopped caring to write anything more than this comment.

You can learn a lot about a community, a product, and a company based on how they respond to bug reports. Promptness, formality, details and politeness are all incredible indicators about what's going on under the hood.

After being with Dyn for 8+ years, this last week I moved from them to Amazon. The Dyn interface is chaotic - so bad I contemplated just reverting to hosting DNS myself in PowerDNS/Poweradmin (https://www.poweradmin.org/trac/).

I never had downtime issues with Dyn, and the performance was satisfactory. But I tried talking a coworker through updating our TXT/SPF record and told him he'd have to "stumble around until he found the right interface" - at that point I realized we deserved better.

There's an interesting story here about Google's strategy to retain Windows 8 users, and maybe some forecasting about what other websites might have to do if Win8 gets traction.

Unfortunately this post's title is so bad this conversation will never take off.

In fairness to Replicator 2, the output versatility looks scores more impressive than Panda's: http://www.youtube.com/watch?v=3o6pcbhylmQ. I suppose it all depends on the hobbyist.

This thread would be infinitely more interesting, and worthy of discussion, if the poster on 37signals wasn't anonymous.

Except this would only work if you:

1) Forced all users in your system, who already had email/password based accounts, to abandon their existing accounts and adopt Persona

2) Became fluent in quickly explaining to users how to reset their Persona password when they forget it

3) Don't mind losing all the users who say "I trust you, but not this company I haven't heard of before." Some users, especially jobseekers, won't let their circle of trust grow - and forcing adoption of a 3rd party causes abandonment. But so does a complicated sign-in process, so you just need to figure out if group A or group B is larger because you can't make everyone happy.

Thank you so much for the thorough details. I squashed this bug. Can you ping me at eric@linkup.com so I can send you a Starbucks giftcard for your help?

98% in agreement.

I think the "built by a nonprofit" is a fantastic point that they should keep pushing, though.

Yahoo! login bug has been fixed.

Teaches me to try and get Yahoo! to behave with https. If anyone wants a great example of why to use Persona, try using Yahoo's developer apps interface...

Let's agree to disagree on this point and let this thread end.

Thanks for the feedback. We're still working on nailing the design - we need a way that all the buttons look uniform, and want a way to explain what they are (namely Persona, as I said, still working on it.) And fitting the multiple options in the small space is no easy feat. Fortunately hover isn't necessary for interaction, so the touch screen device point is moot. And the "moving target" is the same reaction as people gave Apple's dock. But you're right - this design isn't perfect yet.

Once a user's source authenticity is verified, we give the option to merge accounts once we detect overlaps. So if you login via Twitter, verify your Yahoo! email address through the profile, and then login through Yahoo!, you'll be in the same account as you were in the 1st login. We have ~20 scenarios that we maintain for logins, and have heard 0 complaints on the assumptions we have in practice.

Thanks for the screenshot - we'll get that fixed today. Would you like an email once it is resolved?

I did OpenID early on in the site (nobody understood it), RPXNow/JanRain (more than we could afford for fewer features than we needed), and finally our own solution that does OAuth* for the various providers and Persona.

I love Persona. I want a Persona shirt and tattoo. OpenID was just a bit harder, but had nowhere near the payout that using Persona offers. The only burden of Persona is the auto-login/logout handling, which is a good thing in the long-run but in the short-run involves tracking down all your login/logout methods and making sure they all react properly.

*OAuth integration is a nasty mess of nastiness that I can't bring up w/o derailing this entire conversation. If you want to chat about that train-wreck, email me.