RackConnect was intermittently flaky when we used it. We moved off their public cloud in favor of a pure private cloud footprint.
If you can't get your issue addressed and if you've already tried escalating through your AM on the dedicated side, start tweeting @Rackspace. They have a social media team that monitors these things closely and will escalate for you.
Spamford Wallace! A blast from the past. I remember the epic Slashdot articles following the story of the vigilantes that hunted him down. He was easily one of the most-hated villains of the late 1990s Internet.
Mark Bittman (NYT Food columnist) has had an iOS app  out for a while, "How to Cook Everything". I can't remember why but this app was put on sale some time ago for $0.99 and I snapped it up. It's great--I've never had a bad meal from a Bittman recipe.
Wow. I remember watching this fifteen years ago and seeing that young kid (Stuart Parmenter) join Netscape right out of high school and thinking, "Don't do it!". I, too, joined the industry early and by 2000, I'd pissed away the first half of my twenties pulling all-nighters working at tech startups while the rest of my friends were partying at college or backpacking around Europe.
Recently, I'd read something about Mozilla and wonder whatever happened to that kid. Well, looks like he's all grown up now. I'm impressed to see that he spent so many years with Mozilla. I wonder if he has any regrets at starting so young.
No regrets at all. I've been very fortunate to work with many amazing people throughout my career and have learned more than I could have ever imagined back then. The tech world is always evolving and never boring. Those early years, including all the ups and downs of the industry taught me things that would be very difficult to learn these days.
People should step back and think about all the things they do in browsers today. Without the hard work of thousands of people from Netscape and Mozilla, you probably wouldn't be doing most of those things. I'm proud to have been able to play a small role in that.
I wrote jwz a fan email back then because I was afraid I'd have to give up who I am to work in computers. I'm not much of a goth anymore, but it was exciting to see someone like me in such a prominent position.
Unreal. I've been looking at his maps for months in /r/syriancivilwar but had no idea that they were produced by a 19 year-old. I assumed that they were produced by a journalist in the region or an aid group.
They absolutely notice it. I'm a father of two, ages 3 and 12 weeks. When I'm gone, my oldest acts out in a big way. Toddlers are naturally very selfish. They know that the remaining parent is stressed and they'll use this to get their way. It's incredibly stressful for both the kid and parent left behind.
I would love to someday participate in an incubator such as YC but I just can't imagine how my family would handle it--we're dual-income and my wife is active duty military.
I'm curious if the author ever looked into HamWan. 
They provide non-commercial internet access for hobbyists who have their amateur radio licenses (very easy to get) and buy some basic equipment. They cover a number of places in the Puget Sound region. The author would have to build a tower to get above the trees but I can't imagine that this would run more than $4-5k (on the high end).
I am not actually a user of HamWAN--I'm down in Tacoma and my line-of-sight is impeded by terrain and building a tower in my dense urban neighborhood isn't an option. Also, I have biz-class Comcast.
I'm not so sure. I have a large backyard garden and I'm surrounded by neighbors who also garden. I was chatting with some of them the other day and we've all noticed a significant drop in fertilization amongst our plants this year. My tomato plants are typically overloaded with fruit by this time of year but now only have four or five tomatoes each. Same story with the tomatillos, the squashes, the cukes and the watermelons. Production is less than half of a typical year.
My neighbor kept bees but lost his colony last year. I can't say for sure that CCD is the root of our problems--home gardens are more popular around here than ever and perhaps the bees have an overabundance of food--but it certainly feels like something is wrong. Obviously home gardeners and beekeepers don't have the funds to bolster the bee population like a large commercial grower might.
Indeed. Who you consider "toxic" and "angry" depends mostly on what side you take. It's best to keep all politics out of work-related places like Github. Unfortunately, their new Code of Conduct seems to encourage such stances.
Interesting. It relies on a central service that's polling Reddit, though. Why not a distributed, peer-to-peer system instead? By combining the power of hundreds of individual nodes polling the site, you could have fast visibility of new content without being too obvious to the site being monitored.
I made a proof of concept like this some years ago.
It was only synchronising the scores, and was was running as a Chrome extension.
The idea is that each user sees the scores updated in realtime when he display a Reddit page, but he also broadcasts the updated scores back to the server every time he loads a page.
That way no polling is involved, and it doesn't generate any additional load on Reddit servers since the updated data comes from people who were loading tbose pages anyway. This means im not bound to any API restriction (it's basically distributed scrapping).
That's a very cool idea. An unintended side-effect of rockets could be that it reduces the load on reddit's server. My theory is that there are N bots that rely on monitoring new content, and they're all polling for the same data. If those bots just hook into something like this, that's N less requests per second sent to reddit.com.
There's of course a side effect of data being untrusted. While an individual couldn't game this if the system would depend on multiple sources, an organized group (like 4chan) could likely make the system show whatever they want.
It's not against the rules of reddit, and the allowed request rate is enough to grab everything even during busy periods.
You're right that it relies on a central service that's polling reddit. I've done all I can to make it as stable and scalable as possible. I've been running, monitoring and testing it for a week and it's been keeping up just fine.
Given that many people have bots doing the exact same thing, I don't think you'd have any trouble. Hell, total load on reddit would decrease because people would use your service. I don't know why reddit didn't implement something like this themselves.
Given the small amount of people that would use it (relative to the entire userbase), I don't think it would ever be on their roadmap. It would take many developer hours and constant maintenance, which wouldn't be worth it for them as a company. They have more important things to build and fix.
Achieving consensus using browsers as nodes is unpractical for many reasons. Firstly, there are hard limits on localStorage, then there is the issue that nodes go offline really often (whenever someone closes their browser/tab) and therefore it's highly volatile - You would have to replicate data across nodes like crazy to reduce the odds of data loss (the bandwidth use would be massive with loads of duplicate data all over the place). Plus you still need a server to do the signaling to coordinate consensus across all the nodes. Also, there are security implications when storing data inside other peoples' browsers (though this isn't relevant in this specific case).
There has been some hype around using WebRTC for storing data only on the client-side using consensus algorithms like RAFT, but given the constraints which most browsers have and the massive amount of complexity required to get this working, it's really not worthwhile.
I don't think these browser constraints will be lifted anytime soon - There are some very good reasons for having them in the first place - For one, most people don't want their computers' CPU, memory and their internet bandwidth to be used up to process other people's stuff.