You're linking to commercial services touting them as examples of Amazon being more open than Google? Services linked to are: MapReduce, S3, EC2, SQS, SES and MechTurk.
OK kids, here's what you need to know. There are three levels of your relationship with Godaddy:
Level 1: You're in balls deep. You register your domains with GoDaddy, use their DNS servers and host your shit on their servers. You also get your SSL certs from them. That's what the OP was doing.
Level 2: You're in up to the balls, but that's where it stops. You register with them, host your DNS with them but your website lives on another providers servers and you get your SSL elsewhere.
Level 3: You wearing a condom and don't give them their own key or underwear drawer. In other words, you register your domain with GoDaddy but you host the DNS somewhere else like DNSMadeEasy which costs, but is reliable. You also host your site somewhere else like Linode for example. And your SSL cert is something that costs more but is reliable. I have an EV cert from Verisign which costs but you get better conversions.
Level 3 is the only place you want to be. Pay them the bare minimum, immediately delegate the DNS hosting to a reliable rock solid provider that doesn't black-list DNS servers and use that provider to point your A record to whatever web host you're using. You get cheap domains and the only time you have to wade through GD's cluster fuck interface is when you change DNS providers or want to register another domain.
My primary domain did over 27 million DNS requests last month via DNS Made Easy with a 12 hour TTL and it's been registered with godaddy for over 4 years now with no problems at all.
You've failed to take into account the opportunity cost of your time spent working on the business. Lets assume your labor costs $120,000 a year and the company is not paying you. So it's costing you $120,000 a year.
Sell that "property" as you call it, to someone else and it'll cost them $120k a year to replace you or pay you.
The investment isn't paying for itself, there is no capital gain and the reality is that you would have to pay a buyer to take it off your hands so they could lose money at a rate of $120k a year.
At this point in a businesses evolution you're losing money at a terrifying rate and unable to feed your family because you're working for free, but hey you are profitable because you've managed to pay your $20 a month Linode hosting bill.
Dude, I don't want to crap all over your parade or the OP's. But unless we know what we're all working towards and what the definition of success is, we're lying to ourselves and each other and there's no way to measure whether we're making true progress towards meaningful goals or not.
A dire misunderstanding of business cashflow like this poster has demonstrated makes me worry for all the starry eyed kids on HN starting businesses. They read shit like this and gobble it up as gospel. Then they dedicate years of their lives to working their asses off for very little pay, thinking they've achieved meaningful milestones on the way to generating wealth and creating jobs, but the reality is they're wasting their time, wasting investment capital and are a distraction from truly productive endeavors and truly talented entrepreneurs.
What perpetuates this cluster fuck is the monthly talent acquisitions that Google, Facebook and other heavyweights make getting conflated with job creation, innovation and the creation of new cashflow. Building an entity that attracts top talent into a single room and selling that room full of new-hires to google for $2 million an engineer has nothing to do with entrepreneurship. Are you hearing me Levchin?
I've heard of 3 out of 10 of these highly successful startups. I think we call ourselves successes prematurely to try to accelerate the arrival of true success. Again today a very good friend who runs a startup with great potential trumpeted the fact that he is profitable. Looking deeper, turns out he's no longer pouring cash into the company, but unable to pay himself a salary.
Lets cut the bullshit guys. You're "highly successful" when you're able to pay yourself and your employees above market rate salaries and retain profit for growth.
Edit: ...as well as being able to start making a dent in the debt you may have accumulated during the cash burning phase of your startup. If you want a really fucking scary exercise, plot your cashflows to date and do a NPV or IRR calculation on the flows. You'll have quite the come-to-jesus moment and will realize how deep the hole is you need to climb out of before you can call yourself successful.
Delivering cryptographic software via a network, having it run in a "maleable" runtime and creating a user expectation that it will be secure, is not new.
We've been doing this on the desktop for years.
I'd like to pose a question to the authors:
Don't all the premises you've based "Javascript Cryptography Considered Harmful" on apply equally to downloaded desktop software?
-A chicken egg problem
-A malleable runtime for apps with admin access
-Code verification being defeated by other hostile apps on the system
-Inability to trust the secure keystore because of the chicken-egg problem and other hostile apps installed prior to the crypto app's installation.
This is right on - particularly the part about you screwing up the hiring process, not the exec being at fault. I made assumptions about a level of professionalism that I never assessed properly. I went through this a year+ ago and I hired the wrong guy. Unfortunately he took the legal language in emails during the termination process personally - another symptom of the root cause for which he was fired.
The nurse "called the emergency room doctor, who told him that I was dead and that they should walk away," says Snitzer. "And he hung up and he said to the rest of the people in the room, 'Is anyone else here uncomfortable with walking away from this?' And they all said yes. And it was at that point that he called Dr. White."
"Drink coffee and then take a 15 minute nap.". Advice like this makes it hard to take this article seriously. It's also a little thin on the data. Sure, it's an article on caffeine, so it'll rank on the geek sites, but do you feel richer or empowered after reading it?
I used to drink about 5 cups of coffee a day. I stopped cold turkey and life didn't seem worth living. So I scaled back to one cup of really really FUCKING good coffee every day. Jamaican Blue Mountain roasted beans, $40 a pound. That's right bitches. The only thing more expensive has passed through the asshole of a small cat-like creature. You already know what it's called because you're a geek and you're smart. Hey, I like pussy, but that's taking it a little too far.
So I take my one cup of blue mountain black, no sugar, milk or other evil pollutants. Fresh ground, French pressed. And then it's tea for the rest of the day to segway from my morning caffeine kick in the ass to a righteous l-theanine zen buzz.
Hey. Genius. Some of us send over a million emails a week as a free service to users who are happy to hear from us. We just can't afford to check the damn inbox for that many people, so noreply makes it clear. Don't fucking reply because if we had to pay an agony auntie on the other end to feel your pain, the service wouldn't be free.
I think the spirit of your idea of a per transaction tax on financial products is a good one. I would balance the increase in government revenue with a reduction in tax on capital gains held more than 5 years as Cuban suggests.
So keep an eye on treasury bonds on monday morning. Rate goes up, people still believe the US is safe, regardless of S&P. Rate goes down, market sentiment mirrors S&P's rating, and that's very very bad.
Netscape 6 is (or was) the oft quoted example of why not to do this. All that old code may seem old and boring, but it has a huge amount of knowledge, wisdoms, learnings, fixed mistakes, performance improvements, great ideas, deleted bad ideas and security fixes built into it.
When you throw out your code you're throwing out all that knowledge on the assumption that you can build it all back with improvements.
Evolving an application from a known good state to a known better state is usually the best approach unless your codebase is small or your app has no traction.
Rewriting your app from the ground up is like getting divorced and dating a new girlfriend. The first few months are a lot of fun until you figure out how much you lost.
You could also "cat /usr/local/wordpress/wp-config.php" and see the plaintext mysql username/password and inject malicious data into the DB, create/drop tables or databases depending on access level.
Problem is that then you can't auto install themes, auto update wordpress - and the script causing this vulnerability requires a writable cache directory under the wordpress root.
Sam, you've certainly made an enemy out of every member of the Perl community with this sarcastic and incomplete post.
Once you've gotten through OReilly's beginner Perl books and "Programming Perl", if you truly want to learn how to scale Perl in the enterprise, read Damian Conway's Object Oriented Perl. Once you can write solid consistent OO Perl, read "Apache modules with Perl and C".
sigh