seldo

129 ms·

1171.
by seldo 18y ago
That's kind of the point of the article though -- they're just getting by with the bare minimum, because they don't really care about the web. The consumer doesn't care, but a web company should care.
1172.
by seldo 18y ago
Of the many pieces of evidence that Microsoft doesn't get the web, the fact that they suffer under download spikes is one of the least persuasive. For example: they think that buying Yahoo, the slowly sinking grandaddy of the web, is someho
1173.
by seldo 18y ago
Oh god, not again. Will these bastards ever give up?
1174.
by seldo 18y ago
A separate layer for semantics is a really excellent idea; something like "cascading semantics sheets"* -- instead of cluttering your markup with tons of extra semantic information, frequently duplicated, just use existing CLASS and ID and
1175.
by seldo 18y ago
I'm really glad they point out that implementing OAuth would have done nothing to prevent either the phishing attack earlier or this breach. People keep waving OAuth around like it's some kind of panacea for security.
1176.
by seldo 18y ago
Climate-change denialists will of course look at this and say "see? no problem!" when actually massive and unexpected fluctuations -- both colder and warmer -- of exactly this kind are what you'd expect from dangerous climate change.
1177.
by seldo 18y ago
Jokes aside, this is a huge deal for Twitter. Unless they can prove that these guys did something like get phished, their professed monetization strategy of corporate twitter accounts could run into real trouble.
1178.
by seldo 18y ago
I've been thinking a lot about this issue recently. Hometown is a relatively small site, but what if for some reason Google decided to shut down Blogger tomorrow? There's huge swathes of the useful internet on that domain, and no legal reco
1179.
by seldo 18y ago
It's no problem at all. What the fuck is anybody going to do with 5000 twitter passwords? Post something profane pretending to be you? Create link spam, when everything in twitter is rel=nofollow anyway? There's no way to make money by stea
1180.
by seldo 18y ago
I dunno if you've tried using and implementing OAuth, but it is a gigantic pain in the ass. A big factor driving the bewilderingly huge number of twitter mashups is how easy it is to use their API. Not implementing OAuth was a great move.
1181.
by seldo 18y ago
It's a good thing that stuff like this doesn't happen too often, or people would be more wary of trusting all their data to web services. I mean, we assume Google has a really amazing backup strategy for Gmail. We hope they do, because,
1182.
Application autodiscovery via website metadata(laaker.com)
2 points by seldo 18y ago|0 comments
1183.
by seldo 18y ago
The number of servers you have to buy is totally property-dependent. It can be anywhere from 2 to several hundred, but is usually less than 20 in total for the median-sized Yahoo property. Could you clarify what you mean by database inconsi
1184.
by seldo 18y ago
Widgets, Profiles, YDN and Mobile, in the last 2 years. And those are just the ones that I know about because I worked on them. YAP was also new hardware but it was also a new product.
1185.
by seldo 18y ago
Exactly right. As I said at the beginning of my post, the "new boxes" method is only used for major platform upgrades, of a magnitude that would happen once a year or less for most properties. For the really huge properties, the cross-col
1186.
by seldo 18y ago
At least one other: http://blogs.guardian.co.uk/inside/authors/matt_mcalister/in... (although theirs seems to have no published APIs or documentation that I can find, yet)
1187.
by seldo 18y ago
For a moderate-sized upgrade, the description given by gaius is pretty accurate. Working at Yahoo, I've been around for a couple pretty huge property changes, and then the deployment process is very different. Basically, hardware is much ch
1188.
by seldo 18y ago
At Yahoo we drop columns from the previous version the next time we upgrade the database, e.g. if you stopped using a 1.0 column in version 1.1, then you drop that column as part of the upgrade going to 1.2. The key thing is always being
1189.
by seldo 18y ago
There's been a ton of interest in this chart, so I turned it into a poster :-) Thanks for visiting, folks!