HN user

velshin

67 karma
Posts2
Comments39
View on HN

Proxies like unotelly may send more of your traffic through their service than you would like. You can protect your traffic but still use the tunnel if you only send bbc.co.uk DNS lookups to unotelly.

Here's how to do this in Ubuntu 12.04. The DNS has changed in 12.04 to use NetworkManager, which makes the process more convoluted than it should be. The below instructions could be improved but it'll get you some BBC Olympics coverage.

# https://gist.github.com/3202101

Ubuntu 12.04

$ nslookup bbc.co.uk # you should see a UK IP e.g. 212.58.241.131

$ vi /etc/NetworkManager/NetworkManager.conf # comment out dnsmasq #dns=dnsmasq

# save+quit

$ vi /etc/dhcp/dhclient.conf

prepend domain-name-servers 127.0.0.1;

$ service network-manager restart

# create a new dnsmasq.conf with unotelly California DNS 184.169.139.227 206.214.214.28 # note that server=192.168.11.1 is my router (which handles my upstream DNS) and you'll need to change that IP. $ vi /etc/dnsmasq.conf

server=/bbc.co.uk/206.214.214.28212.58.241.131 server=/co.uk/206.214.214.28 server=/bbchdsodsecure-f.akamaihd.net/206.214.214.28 server=/bbchdsodsecure-a.akamaihd.net/206.214.214.28 server=/bbchdsodsecure-b.akamaihd.net/206.214.214.28 server=/bbchdsodsecure-c.akamaihd.net/206.214.214.28 server=/bbchdsodsecure-d.akamaihd.net/206.214.214.28 server=/bbchdsodsecure-e.akamaihd.net/206.214.214.28 server=/bbc.co.uk.edgesuite.net/206.214.214.28 server=/bbcfmhds.vo.llnwd.net/206.214.214.28 server=192.168.11.1

# save+quit

$ nohup /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.0.1 --conf-file=/etc/dnsmasq.conf --cache-size=0 --proxy-dnssec &

$ tail -f /var/log/syslog

$ nslookup bbc.co.uk # you should see unotelly proxy servers e.g. uk-cluster.unostructure.com

Hopefully you change your employer more frequently than your spouse, hobbies, family, or friends. :)

The vast majority of people in the world do not have the luxury of loving their work. For those, 25% of their lives working for someone else in a job they tolerate but do not necessarily enjoy is a means to an end. Maybe it's 20 years of comfortable retirement, or the relative security of a regular paycheck to support their spouse and children.

Most of us on HN are lucky enough to enjoy coding and are well compensated for it. We get caught in the feedback loop of tech chatter and forget that the majority of our friends and family, outside the blissful tech world, do not enjoy their work.

Is it really that easy to hack someones gmail account?

I realize phishing and key loggers are easy ways to grab a password, but if you avoid typing your gmail password at public internet kiosks and the like, is it really that easy for someone to get at? Assuming you use a reasonably long and impossible to guess password, the captchas would prevent brute forcing.

An attack targeted specifically at you will inevitably succeed but most of us are not that special.

The article's advice seems far too easy to lock yourself out (losing my wallet with my magic paper codes and my phone could do it). The additional inconvenience does not seem worth it.

Most of us have used physical 2 factor authentication (like RSA SecurID) for banking and work related VPN access. This works well because the provider (your office, your bank) has a vested interest in getting you back into your account if you get locked out. Google, Yahoo, MS, etc. have no such obligation.

I've lived in SF and Tokyo and spent time in NYC. @potatolicious is spot on with this post. NYC streets and subway cars are, generally, cleaner than the equivalent in SF. Crime's lower (per capita, not totals) in NYC than SF too. You also don't witness as much derelicts and gang bangers on an evening stroll down a NYC street as you do in SF.

@cletus was right about the job scene though. Most tech companies HQ are in SF and there's a wealth of jobs. NYC's tech scene is still up and coming. As we've seen with Austin , Seattle, and NC/Research Triangle, "up and coming" can last for a long, long time.

Did Google open a Milwaukee dev office?

It's irrelevant if the midwest is cheaper. The tech centers have the jobs and the higher rents. (SF, Boston, NYC, Seattle, Austin, NC)

Sign of the tech bubble? Financiers jumping to tech companies?

The chemists and high school teachers turned ninja hax0r can't be far off. Someone please warn me so I can short XLK.

Exercise in the morning, or at least before noon, for 30 minutes or more, and eat a decent meal just after. You'll find that'll give you energy throughout the day, including after a long day at work. Then, pick one thing, focus on it, and achieve clear goals. Refer to what the original article terms success spirals.

[1] How Exercise Fuels the Brain http://goo.gl/RjGe0 [2] Exercise reduces stress http://goo.gl/C6ztV [3] Exercise improves brain function in young people http://goo.gl/NeN0M

As an interviewer, to indicate things are going well, you can smile, nod, give happy words of encouragement, get excited, etc.

When things are going poorly, you can frown, say "not quite", give sour words of encouragement, linger on the same unsolved problem, etc.

While HR / Legal usually have policies prohibiting direct feedback ("You're a 5 of 10 and we have 30 candidates who are all better than you. Also you went to Yale and that's lame."), there are many ways to provide feedback to the interview candidate without opening the company up to legal trouble. There are no laws against being human during an interview.

It's tragic that engineering interviewers extrapolate a candidate's mistakes on a whiteboard during a tense, time pressured interview situation to the calm day coding at a keyboard during a real day at work. It's almost as if we forget what it's like to be an interview candidate when we're the interviewer.

Am I off in thinking it's horrible for the interviewers to not provide feedback during the interview?

I'd also be curious how much throwawayttt probed for feedback during the interview process.

It always hurts to not get something you work hard for -- sorry mate!

There's often a distinction between APIs intended for general consumption (platform APIs) and APIs optimized for JavaScript and/or mobile clients ("private" APIs).

A platform API tends to be stable, versioned, well documented, and "unoptimized" or strongly RESTful. GETing a resource (noun) returns just that one representation. e.g. GET /v1/user/123/profile or GET api.linkedin.com/v1/people/id=123

"Private" APIs tend to return more data in bulk, optimized to reduce the quantity of remote calls and improve page load times. The responses tend to be structured in a way that's easier for the client (browser/mobile app) to render content, usually by including more tangentially related data than a traditional REST resource would contain. e.g. a browser's load of https://github.com/rails/rails does GET github.com/rails/rails/graphs/participation

Twitter uses the platform API in the browser. e.g. GET api.twitter.com/1/trends/1.json

I'd be interested to hear from others leveraging APIs in their browser/mobile clients what they're using for MVC (e.g. backbone.js vs server side) and whether they've "optimized" their APIs for the client.

Deep corporate hierarchies encourage politics and associated power struggles. Part of moving up in that environment is to have others perceive you as an "air-traffic controller" of a segment of the company, a master of your domain. This sometimes results in people in "manager" roles with 1 or 2 direct reports, where the "manager" does no actual work, but spends inordinate amounts of time coordinating with other teams or politicking. Honest work avoided.

I'm not excusing that behaviour but if you've spent enough time at a big company, you'll see motivations for it.

Contrast that to pg's air-traffic controller role in the YC network, providing value to all the startup people he connects.

It will be interesting to see how well pg's positive influence scales as YC continues to grow.

We're professionals paid 6 figures or more. It's reasonable to expect we 'work' (study, learn) outside of the office.

The extra time, 10 - 15 hours a week, keeps you current. Would you want to visit a doctor that only put in 40 hours a week seeing patients, and never studies recent medical advances? Or a lawyer whose case law knowledge did not extend beyond their own experience?

If you work in tech and honestly expect to only put in 40 hour weeks for your profession, as you get older you will end up in a dreary IT department -- not a software company -- and eventually be laid off.