Or, really, people build on this pile of sand because it's more valuable than not doing so. There is enough money to be had in the iOS ecosystem that even when you take into account the risk of being dinged for something stupid like this, it's still an expected net gain for many people to release an iOS app.
The person answering emails for abuse@... shouldn't be the CIO or other management type. It should be a tech support person who has a modicum of clue, and knows who to forward the email to who can deal with and respond to it appropriately.
You are paying for 0 web dynos. They happen to be giving you one for free, but the free one comes with limitations.
Yes, you are paying for a bunch of other services; but, well, those services aren't the actual web dyno that processes the actual request.
Perhaps they could phrase their offerings better, but my impression was that the 1 free dyno with idling is intended for development and testing, not for production use. Once you actually need to use it in production, you need to pay for a dyno.
Yes, that was my impression also, especially since there's no limit on the number of free dynos you can have (for different projects). I was actually surprised to learn that when I looked into setting up a separate staging server for my current project -- I'd thought the free dyno was one to a customer. Nope. The staging dyno is free; I just have to wait a few seconds for it to spin up if I haven't been working with it for a while.
So now I have 3 dynos (2 production, one staging) for $35/month, I can scale up or down at will, deployment is dirt simple, and I don't have to do the sysadmin crap myself.
It's an extreme bargain, IMO.
Now if the project takes off to the point where I need dozens of dynos all the time, that will be different, but ideally in that case I could hire a sysadmin. :-)
Of course, all of these other cases are ridiculous as well. And there have been protests about many of them. Should we not protest one injustice because another has been committed?
> Look at the lot of it in this blokes name, not just one tiny insignificant part of it.
Do you believe that everyone here cares only about Aaron Swartz, and not the rest of these issues?
The death of Aaron Swartz is a particularly painful wake-up call, but it doesn't mean that people care only about him. It helps that he was a particularly sympathetic character, and that many people in this community knew him personally or were directly involved in his work and writing. Kim Dotcom is a international millionaire, who was violating copyright for substantial personal profit, and who had a mansion with a built-in bunker for just this sort of problem; and has been able to use his wealth and power to much more successfully defend himself. Bradley Manning is more sympathetic, but he did violate his duty to his country by revealing many secret documents that he had access to, without being particularly selective about anything that really showed abuses.
Aaron, on the other hand, was merely trying to preserve access to a large body of academic and scientific work. Nothing he did ever indicated that he intended to profit from his downloading. Heck, he never even distributed any of it. And while he used some techniques that were further into the grey-zone than many of us would try, the prosecution was so clearly out of proportion with the "crime" as to make the absurdity apparent to almost anyone (and the fact that it's treated as a crime rather than a civil matter is patently absurd as well).
It has always been the case that martyrs, or particular example of people persecuted by a system, are far more effective than general complaints about entire populations. There were millions of black people who had been treated unfairly, made to use separate bathrooms, drinking fountains, sit in the back of the bus, before Rosa Parks decided one day that she wouldn't take it any more and refused to move, leading to her arrest, and subsequently leading to bus boycotts and the case that eventually worked its way to the Supreme Court ruling that segregation on the bus system was illegal.
Putting a face on injustice is so much more effective than simply talking about it in the abstract. And when that face is a brilliant and well loved young man, who had many influential connections in the tech industry, who was working in the interests of knowledge and social justice, rather than some kid downloading the latest Hollywood blockbuster or an international millionaire trying to make a buck, it will be much more effective.
The stakes have been raised. We cannot sacrifice our future, and our freedom, in the interests of failing business models.
The more magic, unexpected behavior you have when parsing untrusted input, the more likely you are to have security holes.
Instead of building up some complex object based on untrusted input, the author of the application should specify the values and types expected, and the parser should parse those and nothing more. This would lead to much simpler code paths, as the user never has an object that has unexpected keys, values, behaviors, etc. Don't parse the object using complex, general purpose code, then hand the user an object that they have to treat specially; if their form only expects 5 values of given types, then parse only those values and those types.
The problem is, all of this kind of magic is at the very heart of what Rails is. I don't know if you could eliminate it all and still have Rails be Rails.
> Specifying what item(s) should be targeted in a pool of possibly millions, with endless possible combinations is bound to require some kind of precise pointer.
Since you're using base 64 there, let's think for a minute. How many characters would you need to uniquely identify over a million objects? log_64(1,000,000) is about 3.3. With 4 characters, you could represent over 16 million objects. If you just store all of the objects that you need to reference along with an incrementing primary key, you wouldn't have to use more than 4 characters until you had more than 16 million objects in your database.
Have a billion objects? That's just five characters. Still not enough? With 7 characters, you could index more than 4 trillion.
But let's say that you can't actually keep a single database, with an incrementing primary key. You have multiple independent processes or people generating objects that need identifiers that will always be stable, you can't rely on manually picked names, and so on. So just use a secure hash: a SHA-2 or SHA-3 hash of the objects. If you use a 256 bit secure hash (44 characters in Base64, including the padding), and had 500 octillion items in your set, you would have about one in a quintillion chance of having an accidental collision. I'll give you a hint; you are never going to have that many items in your data set.
Now, you might object "what if SHA-2 is broken". Well, that may happen, though it's fairly unlikely. Most of the ways of breaking a secure hash involve making it a few orders of magnitude easier to compute a collision. But at 256 bits, you have a substantial safety margin; it would have to be pretty thoroughly broken before anyone would be able to find meaningful collisions. Heck, Git uses SHA-1 still, which uses 160 bit hashes, and is much closer to being broken.
Anyhow, the point of all of this is that a URL is supposed to be an identifier. It doesn't take that many characters to create an identifier that could uniquely identify each quark in the whole universe. You absolutely don't need long URLs to guarantee uniqueness; if your URLs are long, it's because you're including a lot of redundant information in the URL, or you are actually trying to store a description of the object in the URL, rather than an identifier.
Interesting. I'm reticent to implement any of this. Why? Because it adds a bunch of complexity where none is required. As I said before, I might add a URL shortener if the need arises.
If my goal was to get the smallest possible URL, you would be correct (well, you still are...) However, for the same reason people prefers a website named "ycombinator" over "zgrrc", even if the url would be shorter, I don't mind not being concise.
If I can check my url and without any database see that it's project X, device Y, object Z, it makes debugging easier.
But you are absolutely right: there are ways to make short, unique urls. I just don't want to use them.
Consuming large amounts of them can cause you to have temporary bursts of pleasure, which then cause you to crave them more when they are missing. Have you never had the experience of eating something salty, and realizing that you craved more, to the point where you ate too much salt? Or had some sugar, and then had a sugar crash a little while later, where you got grumpy until you could have something to eat?
That does not make salt or corn syrup a "drug", which is what brador asked about.
Your definition is so broad as to make the term "drug" meaningless, as it means that even water is a drug. Yes, after swimming in the ocean waves for an hour, cold freshwater is pure pleasure, and if I haven't had enough water for a while I start to suffer from dehydration.
A friend of mine has to eat a small amount every few others, else she becomes irritable. I've sometimes forgotten to eat until the afternoon, with little effect on my personality. Does that mean that food is a drug to her, or that she's more addicted to food than I am?
Obviously not.
Can you come up with a better definition of "drug" which makes makes sense? That is, one where "water" and "food" are not drugs, but for which salt and corn syrup is a drug?
I don't really know. I was explaining the above comment, not agreeing with it.
One of the problems is that we have this value judgement associated with the word "drug." Once you label something a "drug", it acquires a negative connotation.
One thing that distinguishes a drug from something like water is that you actually, physically depend on water; you cannot live without it. You can, however, live without sugar (though of course, your body will break down complex carbs into sugar). You can't live without salt, though there's a wide range between how much you need and how much many people eat.
I hope that "drug" also acquires a positive connotation. Aspirin is a drug. Insulin is a drug. Penicillin is a drug. During pollen season, I reach for my loratadine.
Your definition is one characteristic between a drug and a non-drug, but it doesn't suffice. Meat is not essential, as the various vegetarians and vegans on this planet confirm. Does that make meat a drug? A Google search says that a few dozen people have asked, and answered that in the affirmative.
While Vilhjálmur Stefánsson and others showed that people can survive on just meat and entrails; are vegetables drugs?
I read that. It's one of the worse Wikipedia pages I've come across. Did you see that it cites the same paper twice, with different style for each one?
Anyway, I read the paper. It concludes "we suggest that sugar, as common as it is, nonetheless meets the criteria for a substance of abuse and may be “addictive” for some individuals when consumed in a “binge-like” manner. This conclusion is reinforced by the changes in limbic system neurochemistry that are similar for the drugs and for sugar. The effects we observe are smaller in magnitude than those produced by drug of abuse such as cocaine or morphine; however, the fact that these behaviors and neurochemical changes can be elicited with a natural reinforcer is interesting. _It is not clear from this animal model if intermittent sugar access can result in neglect of social activities as required by the definition of dependency in the DSM-IV-TR_ (American Psychiatric Association, 2000). Nor is it known whether rats will continue to self-administer sugar despite physical obstacles, such as enduring pain to obtain sugar, as some rats do for cocaine (Deroche-Gamonet et al., 2004). Nonetheless, the extensive series of experiments revealing similarities between sugar-induced and drug-induced behavior and neurochemistry, as chronicled in Sections 4 and 5, lends credence to the concept of “sugar addiction”, gives precision to its definition, and provides a testable model."
As you can see (assuming my HN markup-foo is strong), sugar has not been shown to (or shown not to) lead to the definition of "dependency" for humans, which is a neglect of social activities. So this remains a conjecture with some supporting evidence, but not enough to make the statement that sugar is or even can be an addictive substance.
I've been addicted to coffee before, quit it for a couple of years, then chose to start drinking it again. It wasn't nearly as bad for me as described here. Sure, it's a week in which your life sucks more than usual, and you have a kind of constant nagging headache. But then it's over, and you're fine. It's really nothing like a heroin addict going cold turkey; though I've never tried heroin, from what I've heard of going cold turkey on heroin, it's far more harrowing. Perhaps the OP is exaggerating slightly, or perhaps he had a stronger reaction than I did. Given other people I've talked to who have quit caffeine, their experience is about like mine; a week or so of nagging headaches and just feeling kind of lousy (like a low-grade flu), and then you're fine.
I decided later on that I really liked the regularity of coffee; something hot and stimulating every morning, that I would be able to look forward to. I also like the taste of coffee (once I acquired a taste for it). And caffeine does improve productivity; the additional wakefulness and concentration are helpful. Now, when you get addicted, you lose that benefit; the same amount of caffeine puts you back at your baseline performance. But I can, on occasion, have a second cup of coffee when I need a little boost; it's a lot easier for me to do that when I'm drinking coffee regularly, since if I have caffeine when I'm not drinking it regularly, I find it makes me a little too jittery and anxious. Being used to it helps smooth out its effects.
Now, that's not to say that caffeine isn't without its downsides. That week of withdrawal symptoms did suck; and if I need to quit again, or don't have access to caffeine for a few days, it sucks all over again (especially if I'm too sick to drink coffee, I now wind up with withdrawal symptoms on top of my existing problem). And for some people coffee is too hard on the stomach, or can cause other problems like anxiety; whether that's the case for you depends on your body.
Caffeine can be either helpful or harmful, depending on the person and how you use it. The harm generally is fairly mild. I started drinking it this time around consciously, knowing full well what it's like to quit, and knowing what the advantages are, and I decided that the advantages outweighed the disadvantages, at least for myself.
I doubt the author's experience was actually as bad as going cold turkey off heroin, but he does describe a caffeine intake amount that is nearly unbelievable to me and I'm someone who probably drinks way too much caffeine myself.