HN user

ClassicFarris

36 karma
Posts3
Comments29
View on HN

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.

Go in Go 11 years ago

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?

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?

… We also know that kill switches are effective…

Do you have a source to back up the stats in this section?

This would be an ineffective way to accomplish that. They'd first have to make a list of all the phones in the target area, and then they'd have to send the lock commands to them, one by one.

This doesn't seem to hard, if you have all of the phones connecting to one or two towers (Or you set up your own "Stingray" tower).

Now the standard line before a protest speech will be, "Please turn your phones to silent, and turn off the kill switch please..."

Your comment about the bool, got me thinking. This would have been better implemented if it was thought of along the lines of movie rating system.

http://en.wikipedia.org/wiki/Motion_picture_rating_system

However, this got me thinking that across cultural lines there are a lot of shades to what is "safe". So a website based in Austria might want to restrict different content than a website based in Australia, and who knows where the "browser" is based.

Of course your comments about the site actually implementing anything/correctly still apply.

At first I thought something along these lines, then I remembered:

1. Google has "trends" when things happen, and "Earthquake" was most certainly googled near/at the time it happened. 2. The phone company has records, which many people texted/called near/at the time it happened. 3. 911 has records and calls were made near/at the time it happened.

and so on…

So there are private entities and government that have data around the event that can correlate behavior and situations, so it shouldn't seem scary to me… it's just should I have better access to the data? And if I do, what can I tell from the correlation?

I'm surprised nothing about functional tests were explicitly mentioned in the article. There were some hints about "engineering the heck out of your migration scripts" (paraphrased) which could be taken as setting up functional tests.

If there is a good tests infrastructure re-writes can be done with a heck of a lot of confidence. Plus there is the benefit of breaking the re-write project up along test lines which helps in not creating the pressure for a, "huge one-time switchover".

For Machine <-> Machine we have several that don't use HTTP, such as Thrift, ProtocolBuffers, etc.

For browser to Machine, I'm not sure we need that. The reason is, for example, we can use JSON which is very easily consumable by a machine over HTTP. HTTP provides all of the transport niceties like headers, verbs (which translate fairly well to CRUD), etc. So the combination of a fairly well featured transport layer combined with fairly well machine consumable data document format makes a pretty good protocol.

Which parts can change for the better in specific relationship to a machine-centric API protocol.

Combined with being a bike friendly city, (googling "best bike cities usa" brought up the city in the top 10 of every list). It seems like Minneapolis is doing commuting right. I wonder if there are any studies around the "quality" of the different commutes a city can have? Meaning does it matter that people can Drive, Bus or Bike to work in some very good conditions… or it doesn't matter; because most people think any commute sucks?

Now about those winters...

Unfortunately becoming a problem would most-likely just land him in jail; with a longer record, and conveniently out of sight for much longer. Not to mention that in jail there could be the possibly of a rougher crowd than the shelter that had the stabbing he witnessed. It's truly a vicious cycle.

Hey, I'm interested in my you have Redis, MySQL and Couchbase? That's three database technologies for this project? I can see Redis being used like Memcache… but how are you using MySQL and Couchbase together. I'm interested in that interaction.