735 karma · joined April 23, 2007
"It seems that the 'victim' had opened an account using an email address of mine, with extra characters thrown in, which Gmail ignores and accepts as the same email address, so it was gmail which uncorrupted the email address and sent the emails to me, not Paypal. I had previously reported an account set-up with fraudulent email address to Paypal many times in the past, but only yesterday noticed that the email address was different to mine, in a way which on any other email system in the world would be a different email address."
From http://namesake.com/conversation/mattlangley/i-just-accident...
However I also HATE God of War for its violence and misogyny. quite strange.
I suspect this may be the real cause of their lack of interest.
1) HTTP GET http://twitter.com/some_account [~500ms for me]
2) 302 redirect -> HTTP GET http://twitter.com/ [~600ms for me]
3) HTML tells browser to download some JS -> HTTP GET bundle.js [~500ms for me] (concurrently here we start getting CSS)
4) JS reads hashbang & request actual data -> HTTP GET data.json [~500ms for me]
... only after about 2 seconds can we start(!) rendering data. Now there's about another 2 seconds for all json data & CSS calls to complete. It takes upwards of 4 seconds for a twitter page to render for me (the Load event lies as it fires well before actual data shows. Try it yourself with your favourite browser inspector).
When not using hashbangs, a single HTTP request can get all the data for the page and start rendering it. One blocking CSS call (possibly cached) is all that's needed for styling.
Hence when I see an external link with a hashbang it frustrates me (barely perceptively) because I know that when I load the page it's going to take a longer than a normal HTTP request. Significantly longer. While subsequent page loads are faster, it's not these you want to optimise for if you care about bounce rates. This issue affects every new link you click into a website, so it affects an even larger number of requests than normal bounces.
Hashbangs are a good solution to an important problem, but I don't see them as a tool to build entire websites upon. Fortunately I see the performance issue as one which will result in people voting with their browsers and choosing sites which only use hashbangs when they genuinely improve the user experience - especially since they're easily visible in the url.
If Google is looking for how useful a page is, they're better off just looking at whether people go back to their search results and click on another site after a short delay.
People are pretty good at recognising "scams", but you need to tell them that's what they're looking for, not just how the content makes them feel. It seems like the report spam button was a large factor behind gmail's spam filtering success. Would love to see the same approach applied here. I know I'd be hitting my report spam button in chrome pretty often :)
While Wikileaks may not survive in the mid term, I believe what it represents may have far reaching, long term consequences. The internet has democratised information to the point that an unhappy individual with mid level trust in an organisation can expose the organisation's "sensitive" information globally with very little effort and thought.
Before the internet an individual could expose this information, but the barriers were much higher. To be a whistle blower you could only influence people immediately near you socially. To reach higher you had to filter your information through news organisations. While there are cases of this happening, the information was still continually at risk of being censored. Would this cable information have been released if a whistle blower took it directly to the NYT, or even a collection of newspapers?
With our current online structure of Twitter, Blogs and peer file sharing it makes sensitive information immediately accessible to millions with no chance of it being censored. To me Wikileaks represents the start of something hugely disruptive to our way of life. It's not possible to scale an organisation beyond several people while maintaining complete trust in each of them. When every piece of information is at risk of being exposed, what position does this place governments in? Is it possible for the current structure of the us government with its extensive lobby groups, international secrets and security through obscurity to continue?
I think its still too hard to see how the bits will fall here, but I do think we're in for an interesting decade :)
If you're under high traffic and you try to resize the server the operation time hugely blows out. There's no way to block this TCP traffic other than changing DNS settings which is obviously undesirable and you might as well just manually setup a new server if you're going to do this (which is what I now tend to do). This process should be automated. It's an obvious bottleneck and fixing would dramatically improve their offering.
I didn't really mind Rackspace having all these issues at the beginning, but after 2 years I see no progress anywhere. Unlike AWS there's very little apparent investment in the infrastructure tools. Other cloud services have matured, but Rackspace hasn't. While the support at Rackspace is awesome, there's only so often I can hear someone apologizing. I'd rather the issues just got fixed and all this friction was reduced. Incredibly disappointed.
Rackspace Cloud does one thing well - small instances have great value CPU & local IO performance. If your app is CPU or local IO bound, splitting it across multiple 256MB instances on Rackspace Cloud will get you huge performance relative to price. I've been worried that this would degrade as the service grew, but that hasn't been the case.
Unfortunately many other 'features' of Rackspace Cloud have been poor to awful recently. Some anecdotal stories;
1) We haven't been able to make images of our server or restore ANY backup of our servers for months. There is a bug in the backup service where if you have spaces in the names of your Cloud Files containers (completely unrelated to the backup service) then all images fail to be able to be restored. We can't remove the spaces in the containers because you can't rename containers (only delete) and there's too much data tied to different parts of our infrastructure in there.
2) In relation to the issue above, we have had a ticket open for over 2 months which we continually post updates with new information & asking for issue resolution. We never receive updates to the ticket itself and only receive information when contacting their live chat. The response is always "we're working on it". I could live with it if this was a short period, or not an absolutely vital part of their service, but come on - all backups broken for 2 months! No timelines on resolution. No ticket responses. No happy.
3) While CPU value is great on small instances you get the other end of the stick on large instances as other posters here have said. You don't get significantly improved performance above the 2GB servers. CPU capacity certainly does not double as their documents say.
4) Cloud Files latency is awful. Individual read/writes take 300-1000ms. Fine for a small number of large files. Impossible for a large number of small files. (Having said that, being able to upload files and publish to CDN in a click has saved me lots of time for static files I need to quickly publish).
5) Resizing mid to large instances is impossible. We recently tried to resize a 1GB (40GB disc) server to a 2GB (80GB disc) and it took OVER 3 DAYS. No really. It didn't complete. The resize process takes the server down towards the end. We had to get Rackspace to cancel the resize and manually spin up another server and transfer the files ourselves. To make it worse, we couldn't act on this issue initially because Rackspace insisted that the process was "almost complete" from 12 hours onwards. 2.5 days later we just gave up. We managed to do the manual transfer ourselves in a couple of hours. Even worse Rackspace seemed to not think that it was unusual for the process to take 3 days or express any desire to investigate further.
6) The web interface has awful performance at scale. Once you go above 20 cloud servers every single page load takes 10+ seconds. As the original poster says, the number of errors it spits out about not being able to complete operations is insane. It's rare I can go in there planning on doing something and not have to contact support to fix something broken on their end.
7) They're taking the entire web interface and API offline for 12 hours this week! You won't be able to spin up or take down any of your servers. Why? So they can fix a billing issue related to Cloud Sites (a service we don't use).
I've always been a champion of Rackspace Cloud and Rackspace in general, but sadly I would no longer recommend them to people. I'm starting to make contingency plans and looking for other providers again.
Is this because prediction has been "solved" or because characterization is currently more commercially useful?
There's definitely a need for a 'great' PHP ORM. I've been rolling my own for a couple of years since I've never been satisfied with what's out there. Here's the kind of syntax/style I use on mine (that class definition is the entire code I need to write to get working abstraction).
class Person extends Model {
const TABLE_NAME = 'people';
const TABLE_KEY = 'id';
}
$person = Model::find("Person", 1234);
$person->name = "James";
$person->save();
$persons_named_james = Model::find("Person", array("name" => "James"));
foreach($persons_named_james as $person) {
print $person->age;
}
$person = new Person();
$person->age = 26;
$person->save();
I should really upgrade to 5.3 so I could write Person::find(1234); instead.
The pattern of diggs from the suspect accounts stopped not long after digg was notified of the blog post and before it was made public.
I have filevault turned on. Moving the binary out of my home folder (and adding a symbolic link) solved the problem.
I have filevault turned on. Moving the binary out of my home folder (and adding a symbolic link) solved the problem.
It's frustrating.
However, if you then found out I had been going into a different casino only betting 3 times and walking away every hour of my life you would understand that it was just by chance that you happened to be there on the day that I won three times in a row. There is nothing to explain - no divine powers.
This is what Hawkings is arguing for the multiverse. Because there are many possible universes, the fact that ours has all the right qualities to sustain life is an inevitability. It's inevitable that one would be created and because we exist, we must inhabit one.
I knew there was an incarceration problem in the US, but I didn't realise it was this bad.
It's always been like this.
Like any social news site, you can never get content that perfectly suits what you want. When you start looking for content you think doesn't suit your tastes, you will find always find it.
Nothing has changed.
Vote up posts you think suit HN and ignore ones you don't.
They had a special deal for $99 when I got it, but that was very limited and they haven't done it since. Still I'd say if you hold out for a year that price will be halved. I generally recommend people to wait unless they're really interested in these things. The industry is still in its infancy. Cost is going down quickly and quality is going up just as fast.