Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

There's a huge difference. In one case, the car is displacing all of that air; in the other, you are. Now, sure, an aerodynamic shell helps with that, but you still have to be the one to displace that air mass, while with a car you have a powered source doing so.


I wouldn't say that you should expect to get fucked over.

You should treat the favor as a gift, and not expect a quid pro quo. You shouldn't do more than you can afford as a gift for them; you shouldn't spend years of your life, or a large fraction of your salary, or anything of the sort. It's just a gift for a friend or family member.

That way, you aren't left hanging, expecting something from them, and having that poison your relationship. Be very careful about letting some kind of debt or obligation hang over the head of a relationship that you care about.


Exactly.


It's called the EFF.

The problem is, it's mostly supported by individuals, not the industry. And there are a lot more individuals interested in gun rights than electronic rights. It has a budget that's a tiny fraction of the NRA's.


In the sense that they're defending our rights, yes you could say it's EFF.

But I'm a little worried about the idea of EFF having to lobby Congress the way NRA does (by paying them). I wouldn't want EFF to become a corrupted organization because it starts receiving a ton of money from the industry instead of the users.


> I wouldn't want EFF to become a corrupted organization

I don't think any NRA member thinks they are corrupted. They are doing the exact job they are supposed to given the rules of Washington DC. Like the ACLU and other rights organization they know to defend the extremes because the first compromise will not be the last. Sadly, there is no room for reasonable where rights are concerned.

I don't think any House or Senate member fears the EFF during election time. If we want the 4th amendment to be defended, then we need an organization they do fear.


This is politics, if you want to win you have to play the game.


Yes, but there is a big difference (at least in my mind). While the notion of the right to bear arms is conceptual, what it aims to protect is actually tangible (Iron and Lead) and people would feel impacted (can't go hunting, or could not 'protect themselves', the latter being less tangible.)

So it would have to appeal to people differently. Psychologically, 'privacy' is higher up the hierarchy than 'security' and 'food'. I think that's one of the main hurdles.


Is gun industry bigger than Google, Microsoft, Amazon, Apple, eBay, Rackspace, Godaddy, etc. combined? The latter are directly affected by the government policies regarding privacy and certainly their clients would appreciate their companies standing up for their rights. The users should just be more vocal in expressing it. Maybe if you're just a hobbyist who nobody knows your voice won't be heard, but if you're a known person in tech would, people would take notice.


The total revenue of the gun industry (which doesn't count a lot of ancillary things like hunting lodges) is 1/8th of Google's---which points out one way this analogy isn't useful. We gun owners are powerful because they're are a lot of us, we're organized, and we vote.

Getting Google et. al. to resist this requires an entirely different approach.

Ah, one good analogy: while it was owned by some Brits, Smith and Wesson was the only company to play ball with the Clinton Administration in 2000 and it got crushed by a boycott: http://en.wikipedia.org/wiki/Smith_and_Wesson#Agreement_of_2...

But, then again, it's only because we're politically organized, and had to do so in self-defense starting in the '70s, that this came about. But if a prominent Internet company lost 40% of its business due to privacy issues that would get serious attention.


Maybe this will cause people that value privacy to organize.


A bicycle actually consists of two inverted pendulums (the frame and the fork) joined by a hinge. And the bike that was stable with no trail and no gyroscopic effects used this to provide stability; the stability was provided because the fork, with the lower center of gravity, would fall faster than the frame (taller inverted pendulums fall slower than shorter ones, which you can easily demonstrate by how much easier it is to balance a long object like a shovel than a short object like a spoon on your hand). This provided the necessary feedback that caused it to steer into a turn in a way that stabilized.

The takeaway is that there are several factors which influence the stability of a bike. We know of certain designs which utilize one or more of these factors to achieve self-stability (and the conventional bike has all of these factors, hence why it tends to work so well), but we don't know the exact set of conditions on the combination of factors which would allow you to characterize which designs are stable versus unstable, without simply trying out any given design and simulating it.


> Having a rake angle on the front wheel makes a bicycle self correcting (if the c.g. is on the right side of where the wheels contact the ground, then a right turn is induced in the front wheel by the rank angle)

No. If you actually read the paper linked (and the Supplementary Online Materials, which contains a lot of the actual information), it is shown that rake angle is not necessary for the bike to be self correcting. You can build a bike with a negative or zero rake angle that is still self-stable (at least, according to the bicycle dynamics modelling software they were using, JBike6; they didn't actually build this particular bike, but did build one that had small negative trail and no gyroscopic effects that was still stable).

As they demonstrate in the paper, none of rake angle, trail, or gyroscopic forces are either necessary or sufficient for self-stability. All of them can influence stability, so saying the gyroscopic theory has been proven wrong is not entirely right either; it is a part of the dynamics that adds stability, it is simply not necessary or sufficient on its own. In fact, the paper shows that on the "benchmark bicycle", removing the gyroscopic force makes it unstable, so on that particular design, the gyroscopic force is necessary for its stability (thus explaining why it was believed for so long that gyroscopic force is what provided stability).

What we know is that gyroscopic forces, trail, rake angle, and distribution of the center of mass of the fork and body of the bicycle all influence stability (in particular, the center of mass of the body of the bike being substantially higher than that of the fork); none of them alone are sufficient to provide stability, and likewise none of them alone are necessary as we can build bikes without them that are still self-stable.


  > > Having a rake angle on the front wheel makes a bicycle self correcting ..
  > No. If you actually read the paper linked ...
Please don't start replies with a "no", especially when you don't disagree! You reply that it "is not necessary" which does not negate your interlocutor's point!

(probably going to regret going meta, but the initial 'no' in forums and irc really bothers me)


If you read the actual paper referenced, we know some of how it works, but not all.

Two of the proposed theories (that it has to do with gyroscopic effects, and that it has to do with trail), have been disproven by creating a self-stable bike with no gyroscopic effects and (slightly) negative trail. The paper introduces one additional factor, the difference in center of mass between the steering assembly and the rigid body of the bike; the steering assembly having a lower center of mass causes it to fall faster, providing the necessary corrective steering to achieve self-stability.

So, there are several factors we know about, which can increase stability. We know how to locally optimize stability for certain designs. But we don't yet have a full set of necessary and sufficient conditions for a bike to be self-stable. We haven't even proven, analytically, the intuitive notion that a bicycle must lean toward a fall, though given our intuition it is believed to be true.

Here are the two necessary conditions that the paper provides:

> To hold a self-stable bicycle in a right steady turn requires a left torque on the handlebars. Equivalently, if the hands are suddenly released from holding a self-stable bicycle in a steady turn to the right, the immediate first motion of the handlebars will be a turn further to the right. This is a rigorous version of the more general, as-yet-unproved claim that a stable bicycle must turn toward a fall.

> Another simple necessary condition for self-stability is that at least one factor coupling lean to steer must be present [at least one of Mδϕ, Cδϕ, or Kδϕ must be nonzero (SOM text S3)]. These coupling terms arise from combinations of trail, spin momentum, steer axis tilt, and center of mass locations and products of inertia of the front and rear assemblies.

That's what is meant when people say "we don't know how bicycles work." We do know some of how they work; we know that the designs that we create steer into a fall, and do so in such a way that damps the wobbles and eventually goes straight again. And we do know some necessary conditions for a self-stable bicycle, like a requirement that something that couples lean and steering must be present; but we don't know if the steering into the fall is absolutely necessary, or if you could build a bike that managed to achieve self-stability without it.

So, I would say that a more accurate summary is "we know how current bicycle designs work, but we don't know exactly what aspects of them are necessary, or how to completely characterize the sets of designs that work or don't work." But that's a bit more of a mouthful than "we don't know how bicycles work", so that's what gets repeated.


So we do know how the bikes that actually are 'bikes' work at least to a very large degree (engineering vs math), but we don't know all the possible physics which can enable an arbitrary two wheeled construct to be selfstablize when perturbed while in forward motion.

I completely understand the point your making. However, at when making a technical argument and then generalizing the end results, we can end up in a situation where the truth of the technical argument no longer strictly implies the truth of the generalized/summarized result. I feel the statement 'we do not know how bikes work' has crossed that line.


I suppose it depends on how you look at it, or perhaps on whether you're interested in how a bike works versus why a bike works. How is relatively easily answered; as the bike tilts it steers into the tilt, moving its base back under its center of gravity, in a way which damps itself thus getting back to upright without oscillating repeatedly or falling over.

Why it works is the open question. We know that it's some combination of gyroscopic effects, rake, trail, and the different centers of gravity of the frame and fork, but we don't know the precise relationship between them that allows it to work.


You could build a bike with no gyroscopic effects, slightly negative rake AND the steering column center of mass at the same height as the rest of the bike. So you could cancel out and test the influence of the last effect.


If that failed to be stable, all that would prove is that particular design was unstable, not that there is no design with those features that is stable. This is a problem of finding a general rule, not just a particular design that is stable or unstable.

The issue is that no one has found a way to characterize all possible designs (within certain constraints, such as two wheels each attached to a rigid frame, the frames joined by a hinge) which are self-stable. They know some conditions that are necessary, such as at least one factor linking lean to steering and the design needing a steering force applied to turn in a steady turn. They have not yet characterized what conditions are sufficient for a stable design.

What you want, to say that you fully undertsand how a bicycle works, is a set of conditions which are both necessary and sufficient for a bicycle to be self-stable. If you build a bicycle which meets those conditions, then it will be self-stable (at some speed; certain designs may be self-stable over a wider range of speeds while some may only be self-stable at a narrow range of speeds); if you build a bicycle which does not meet those conditions, it will not be self-stable at any speed.

We've gotten closer over the last century; initially it was believed that gyroscopic force was necessary, but that was disproved. Later it was believed that trail was necessary (or either gyroscopic force or trail was necessary; I haven't read the older paper), but that has now been disproved. We now know a couple of necessary conditions (listed above), but they are somewhat weak necessary conditions, and we don't yet have (as far as I know) a set of sufficient conditions (conditions which, if they hold true, will guarantee that the bicycle will be stable, regardless of other changes to the design), beyond a few known designs which are demonstrably stable.

In fact, if you follow from the paper in Science to the "Supplementary Online Materials" (which is actually the full-length paper; what's published in Science is really an extended abstract), you will see that they prove that "no combination of positive gyroscopic action, positive trail, or positive steer axis tilt are either necessary or sufficient for self-stability over at least a small range of speeds." They construct models of bicycles that lack each of these things but are stable, and have all of these things but are unstable.


Why do you think they have poor reading skills? Perhaps they wanted to throw in a little extra, but not the next tier up at $10,000.

Remember, you can donate at any level you want. If someone donated $1000, they would probably chose the $830 option to give more people a chance to get the $600 option.

Remember, you shouldn't think of Kickstarter or Indiegogo projects as a pre-order. It's a donation to a project that you think is worthy; where you may get a substantial reward if that project goes well.


Yes, but it doesn't take more than a day to know that an intruder had accessed the system in a way that may have compromised your personal information.

Basically, once the problem was serious enough that they felt like they needed to take the site down, I'm pretty sure they knew which machines had been accessed (or at least may have been accessed). They knew that some of those machines had developer's personal information. They could have posted as much up front, rather than waiting 3 days to do so.


"I'm pretty sure."

No, they likely took the portal down as soon as they knew there was a breach. Highly unlikely they left it up while they investigated, and it takes time to figure out what happened and how much information was taken.

What motivation would there be to wait anyways?


> No, they likely took the portal down as soon as they knew there was a breach. Highly unlikely they left it up while they investigated, and it takes time to figure out what happened and how much information was taken.

They still haven't said anything about how much had been taken.

My point is they knew how much could have been taken. They knew what machines were at risk; hence taking them down. If those machines that were at risk had sensitive personal information, they should have notified the people affected right away, not three days later.

Taking the site down, with no indication of why, and waiting three days to tell people that their personal information may be at risk (and remember, the possibly compromised information includes credit card numbers, as there are a number of things you need to pay for in your developer account) is just crazy.

You should be upfront and transparent when the breach first occurs. Of course you don't know exactly what has been compromised; but they are still being plenty vague even three days later. If they had posted three days ago what they posted today, it would be a lot more reassuring.


Meh. A lot of these sound like those ideas that any programmer comes up with, about what would be great, without ever actually putting the sweat in to turn a vague idea into something that actually works.

I have probably as many half-baked schemes in the back of my mind. We probably all do. Why is this list particularly interesting?

Heck, lots of these ideas sound downright bad. Adding operations for "put in new folder" and "pull out of folder"? Don't we already have plenty of ways to do this? A basic set of primitives (create new folder, move files to folder, whether done through the UI or on the command line), allows you to compose those simple actions into the more complex ones, rather than having some giant menu of everything you could ever possibly want to do with files that you need to navigate through.

I'm just not sure what the value of long lists of vague, half-baked features ideas for random software is. Why not actually build one or two of these? That would be far more interesting.


A lot of ideas start out half-baked, in brainstorming sessions, etc. Even if you don't like the ideas here, judging from other comments it's at least thought-provoking. And this person basically opened up their private journal of ideas for anyone to look at.


That's sad. I was never a regular reader of the H, but when I did come across their articles, I found them very well written and informative.

I'm surprised they haven't tried a subscription model like LWN. LWN has encountered similar problems, and been on the brink of shutdown before, but every time they have announced this they have subsequently managed to increase subscriptions enough to stay afloat. The nice thing about subscriptions as opposed to a one-time donation drive is that it becomes a sustainable revenue stream that they can depend on, rather than a one-time injection of cash that dries up quickly.

LWN's subscription model seems to work really well. A subscription just means you get access to subscriber's only articles a week before everyone else; so if you don't need to stay absolutely on top of every development, you can read for free. There are different levels of subscriptions, ranging from $3.50/month to $50/month, so it's close to a "pay what you want" model (there are some slight differences in features you get at the different levels, but they are mostly equivalent). And subscribers are allowed to generate links that they can share with other people to content that is still subscriber-only, so you can still discuss an article if you feel like, submit it to HN, or the like; they just ask that people don't abuse it by providing a feed of all subscriber-only articles or something of the sort.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: