normalocity

On what planet is there a tradition of paying for the time spent in an interview? The writer of the article knew it was an interview, and presumably knew approximately how long the interview would be.

Anyone else in this thread think that this blog post covers a painfully trivial calculation problem? What's next - someone's going to write a full blog post to explain to me how to perfectly toast my toast using these visual sensor things that seem to be built into my head (eyes)?

In terms of privacy I see two categories of data on a network: (1) data that leaked/has been copied to other people and (2) data that hasn't yet leaked.

The thing is you can never know with certainly when a piece of data has changed from "not leaked" to "leaked", so effectively you have to act as if all data is leaked in all circumstances as soon as you put it on the network.

I like how the name "Shuttle" implies that this is going to make your SSHing experience "take off", but anyone with an SSH config file is like:

"You mean you weren't doing this years ago? Why do I need a UI to get to a shell command? I'm already in the shell!"

For anyone reading this that is interested in news on how this goes, but doesn't have sysadmin skills, nor access to a building, I added a simple newsletter signup field to the page.

I suppose this also doesn't require roof access in many cases. If someone is willing (and your building super isn't going to get angry at you), you could put an antenna on a balcony the same way people would put up a satellite dish, and we get could get line-of-sight going at least in one direction from a given building.

What about TJ Hooker? http://www.imdb.com/title/tt0083486/

I can only imagine someone trying to explain the logic on this one in some ad copy somewhere. "TSO" is the kind of name that requires its own FAQ entry just to explain, and even then it doesn't make sense.

I should also say that the requirements aren't an all-or-nothing deal. For every node we setup we'll need people to use the network, support it, talk about it, and help maintain it. So really, no one here should be discouraged if you don't happen to have access to a semi-tall building. Please - join up and be part of the group - don't let the building access issue stop you.

Thanks for the front page love, HN. Really wasn't expecting that. :)

The idea here would also be to reduce the cost of network access to near zero, or am I missing something about where the costs come from maintaining the network?

Any chance the administration of nodes for this kind of technology could be crowdsourced to the people in the neighborhood as well, giving not only access but useful knowledge and a learning experience? I know when I was young I didn't need new or expensive technology to hack on - just needed something I had regular access to.

Sounds good to me. We'll take what we can get.

Sounds awesome. By all means reach out and let's get something going.

I'm totally from this era but I don't quite have the nostalgia for it that you do. I definitely remember the joy of getting mail when the idea of spam was nonexistent, but I'm not sure I'd want to go back. That said, the protocols people want to run on top of this would be whatever people want, I would think, so if you can find enough people who wanted to do this I don't see what's stopping you. :)

Got a link to any information? Sounds interesting - would love to read up.

Not sure - there's only a couple of cjdns nodes on the atlas

I will, thanks.

Has simply ignoring the trolls stopped working? ;)

Unlike the other link I saw about this, this one links directly to the article containing the list, rather than the reblog.

Really internet - are we re-blogging lists at this point? WTF - some people just aren't trying anymore.

3:14 - Pi time in Jan. 2038.

Get a Pi(e) and enjoy eating it as the world collapses...or when the world is just fine you will have just enjoyed a delicious pie.

DB username and password. Fuck - was pretty much waiting for something like this to happen. Just got one of these emails a few minutes ago myself. Luckily I was only using this for a toy app.

If an idea was so easily cloned, then it wasn't that valuable in the first place. This is the primary driving force behind all things that drop in price with economies of scale, lack of scarcity, and/or increasing ease of access.

Besides, ideas often aren't cloned because someone talked - they're cloned because (a) multiple people/groups often co-create very similar ideas because we're all feeding off the same pool of inspiration, and (b) your idea probably isn't as unique as you think it is, and the "brilliant stroke of insight" you experienced to create this thing was probably obvious to a lot of people.

You're right, I left that portion about, but it's also important.

Hm, hard to say. I don't know Linus personally. If I had to guess, I'd say he was one fire about it, and is obviously passionate about it. People are people, and they get exciting about stuff they care about.

The deficiency basically has to do with git being primarily a command-line tool, and as such, it's most powerful/native tools are built to be perfect for viewing plain text/in the command line (which are also mono-spaced). As such, when you view commit messages that are too long in the command line, the formatting gets screwed up as text is wrapped, and it's more difficult to read. In my interpretation, Linus believes this results in lost efficiency, which gets worse the more commit messages you have to read/handle on larger/more active projects.

If you work within GitHub's UI only (and rarely look at your shortlog / git log on the command line), you'll never know about this because the web UI hides this fact. That seems to be what Linus is getting at - that the tool (git itself) was built to be awesome on *nix platforms, and GitHub effectively ignores this aspect of git.

Finally, since the web UI doesn't enforce the proposed standard, you effectively create two groups of people: people who work through the web UI (or other UI-based tools), and people who work from the command line. Only the command-line people really suffer. However, if everyone (even people who work in the web UI) would conform to the standard, not only is everyone happy, but it encourages people who write commit messages to be more succinct, effective, and precise in their messages.

That's pretty much what I took from it.

Indeed, very intense; especially when Linus was throwing out statements like, "The truth shouldn't be sugarcoated." I had to believe there was something concrete behind it, however, and I was glad to see that there was.

The Seattle (or Portland? can't remember which) airport has a self-driving train that shuttles people between terminals. Of course, there's no competing "traffic" to deal with in those cases, just a handful of trains all heading around a closed loop in the same direction, moving people from place to place.

I think this is a lame minority view. I don't know anyone who actually loves driving in traffic, for example, even if it is to take their kids to school or to go to the gas station. WTF?

I guess they came from the ChinaBang conference?