ClassicFarris

Thanks for the suggestion on the description. That should help in preventing me from conflating the different use-cases of running a VPN. For example: viewing a US Netflix account while in India vs. At public coffee shop vs. Protect myself and my family from persecution.

The login would change as you bring up and down servers. You get a new fresh install of the service on an instance each time you start a new one up. (Although the option to start and stop could be easily implemented.)

You can choose between all of the AWS Cities/Countries that AWS offers which is 9 across Asia, Australia, Europe, The USA and South America. Which hopefully would provide a good mix for a while.

As for expense, this is where the different use cases come in. If you want to secure a coffeeshop connection for a few hours then you'd just pay a few cents for the protection, which I think is reasonable. But if you want a more permanent connection then I may need to think more about the costs, or starting and stoping servers automagically to save costs.

I have a set of scripts that I've compacted into a one-click binary that spin up new AWS instances as a VPN. Would people buy this? (I'm planning on a Show HN: in a week or two, once I get the final debugging and product artwork done.) Even then, I'm really not sure if there is an advantage in having you're own home-grown VPN or using a service like StrongVPN (or any of the other "google: private vpn service" VPN service providers)?

I'd like to think that people would want to "run" their own, but I'm wondering if most even would care.

How is it anonymous if I have to give you my number. Is there a way to text from a web client?

Can some one answer this question. It says that Go1.4 will be needed to compile Go1.5. Does this mean that Go1.4 will always be needed, even for Go1.6 and beyond? So are they essentially locking things to the Go1.4 "C" code, then updating on top of that?

Yeah, I've thought of this too. I was thinking you could just use a normal mobile network, as you'll just be sending the correct color to a full screen (not a ton of data needed for that). I was thinking that a website serving up web socket connections would be the best way to send the data, no clock sync needed.

Just spin up $10K worth of AWS instances for a few hours to handle all of the connections, and done.

I think this is a good idea. There can be a change in the structure of where things are hosted (think moving the images to a CDN as traffic increases) which won't require a new client to find the optimized images.

I agree that it's the overhead carry-ons that cause most of the problems. From 1. people wanting to make sure they get space. 2. People incorrectly placing their luggage taking up more space than needed in a bin.

The solution: Carry-on Valet. Have 3-10 airplane employees (indoor luggage handlers) load the carry-on's to the bin above the seat number the person will be sitting in then leave the plane from the back. (For more speed have people start loading as the bins are filled from front to back)

I think large international flights could be excluded.

The airline would need to only have a few more luggage handlers to do this; as they are already at the gate, just outside, right?

Also Known As: The Sophomore Slump

One thing that your recipe format helps with is timing, which is one of the things that I always found fun about cooking. Which is, how to have everything work to come out about the same time. So how do you prep and cook, and work in a special detail at the same time.

Do you have plans to incorporate full meals on the site, such as a meat dish with two sides and how to cook them all together, to come out at the same time?

We should document life versioning, as in web 1.0 verses web 3.0.

Can I do a pull request to make this change, or is this page so 1.0?

Ahh, the little-known trickle down theory…

An articulated and advocated instance, where it just might work.