Hacker Newsnew | past | comments | ask | show | jobs | submit | 1lint's commentslogin

I'm surprised by how much this publication reads like an advocacy piece for a specific viewpoint, rather than an objective review of existing literature. Just from reading the paper, it is clear that there are many experts in the field that take the opposing viewpoint that is being attacked in the paper, especially considering that their hypotheses have been published in widely circulated textbooks.

When it comes to research publications in general, I very much prefer to hear an objective, good faith presentation of the major viewpoints, with the author taking an opinionated but measured take in the conclusion as they review the overall weight of the literature. I'm sure there are issues with this "triune brain" model, but at a certain level every model is inaccurate; the real question is whether a model is useful in its framework, and the answer has a degree of subjectivity such that I do not think it is fair to categorically reject the perspectives of opposing experts in the field.


On a more general note, a human eating a vegetable is a predatorial relationship, and like any prey, the vegetable will evolve defenses against such predation. Obviously the vegetable can't run away, so it produces compounds that are harmful against its human predators. Artificial selection through farming may reduce the harmful compounds, but constitutes a small fraction of their relevant evolutionary history.

On the other hand, we have the opposite relationship with fruits. When our ancestors ate fruits, they played a pivotal role in facilitating the plant's reproductive fitness by dispersing the seeds, at times with the excellent complimentary fertilizer that is human excrement. In this case, the plant has an evolutionary incentive to produce more nutritious fruits to encourage such human consumption.

There are a lot of "vegetables" that are actually botanical fruits such cucumbers, zucchini, tomato, etc. (note they all contain seeds). They are much better alternatives than true vegetables (spinach/kale) for juicing if you are trying to avoid sugar or somehow don't like sweet juice.

It also doesn't sound right to me to refer to liquified vegetables as "juice", when I've long thought the term refers to the liquid produced from squeezing a fruit (not to mention liquified spinach/kale sounds a bit nasty)


I recall someone in a similar situation who was able to convince IT to whitelist a cloud VM for testing website deployments. In addition to the website, this VM also hosted a wireguard server running on ports that happen to be commonly used for databases.


I don't think this article raises an actual issue (if it even exists).

If we take up the author's call to action in the title and introduction to "stop growing alfalfa" (presumably by outlawing it), then the corporations that grew alfalfa would obviously just find some other crop/product through which to effectively export water, albeit less efficiently, in which case the preexisting problems still exist but are even worse.

The real question is why these farmers/corporations are using their water to grow crops in the first place, when they could presumably be selling their water to consumers at much higher retail rates.

An immediately obvious answer would be that the costs of transporting/distributing this water from the source to the consumer is greater than the profit margin, in which case there isn't even a problem to begin with.

If the issue is regulation restricting corporations from selling/distributing their water to consumers, then it should be an obvious win for the politicians to fix: their corporate lobbyists get more money selling water at higher rates, while their voters get to buy water at cheaper rates. Either way, the article doesn't even mention any regulations at issue.


If the justification for criminalizing a drug is its propensity to cause societal damage, then by far the most important drug to ban is alcohol. Heroin addiction may promote theft and property damage, but that doesn't even come close to the mayhem, permanent injury and death caused by drunk driving accidents (as well as the social service costs of managing our country's subpopulation of alcoholics). Because alcohol remains legal, I believe less harmful drugs, including many if not all of the drugs decriminalized by Oregon, should be legal as well.

>> "I guess these things would all be prevented and/or prosecuted, rather than the drugs themselves" I agree with this statement. Criminalizing hard drug use simply because it is associated with behaviour causing societal damage is not only inconsistent with the legality of alcohol use, it is also a slippery slope to justifying far more insidious laws. For example, a similar justification could be used to criminalize violent tv shows/movies/video games if the government believes consumption of such media is associated with societal harm.

The obvious solution is to simply criminalize the acts, such as theft and property damage, that actually harm others/society, rather than indirect upstream actions such as drug use. This "Oregon experiment" involves far more than just decriminalizing drug use, but also (effectively) decriminalizing many other domains of crime such as retail theft, daylight robbery, urban camping, property damage, etc. not unlike what we have here in SF.


Crack, heroine, meth, and opioids are demonstrably more damaging to the individual than alcohol. You're conflating total magnitude (individual harm * number of users) with individual harm.


This brings back memories of first playing civ5, which used a hexagonal grid


Another reason to include commit ids in the url when fetching files from external repos. I think you should do this anyways in case the external repo maintainer makes a change that silently breaks your build script


Just verify the SHA of the tarball a la Bazel?


Remember when git archive changed its format and that affected archives downloaded from github?


That won't help you very much. There's no guarantee the commit belongs to the named repository with e.g. raw links[0].

[0] https://twitter.com/slimsag/status/1672421999698903043


Of course it will, since you'll either get the commit you wanted at the time you wrote the script, or an error.


Unless someone is very good at finding SHA1 collisions.


The collisions need to deliver malicious payload as well, making it extra hard


Those are still very hard to get for a random hash, and GitHub I think warns (or blocks?) you if you try to push a hash with a known vulnerability.


If you clone the repo, it won't be there.


I agree it seems like a disproportionate act to take given the situation as the author described it, but this certainly does seem like the kind of scenario that involves a lot of context that goes unmentioned.

One explanation for this sequence of events is that the conference planners had since found a new compelling topic reflective of the project's direction to be covered in a keynote speech, in which case the natural topic to replace is one that discusses a "possible"/hypothetical idea. I'm sure there was a better way for leadership to handle this, in particular around communicating their intentions, but this shortcoming seems much more likely a case of incompetence rather than malice towards the speaker, given the lack of information to support the latter.


If we don't care about the UX, then it would be more "convenient" for the developer to just not write the program in the first place.

Using string templating makes the DX better without compromising UX, since users just see the rendered output. Implementing bad/nonexistent web security also makes the DX easier since there's simply fewer features to implement, but this obviously has negative consequences on UX when folks have their accounts/credentials easily stolen.


Using string templating for HTML is bad/nonexistent web security, so by your argument it does compromise UX.


By your argument, everyone using string templating for HTML has bad/nonexistent web security. I disagree.


Not everyone, just the people whose pages display untrusted inputs. Which is a huge fraction of the modern web...

(The rest just have brittle websites that might break when someone uses certain punctuation for the first time.)


Ah okay I see now you were referring to failure to sanitize inputs/outputs in the original comment. I don't know if this oversight occurs more often when using string templating, but I'm pretty sure this was already a problem long before string templating came into practice.


It's literally the reason why HTML templating is done with other means than string concatenation, these days.


Isn't that why server side validation exists? What's wrong with letting the user enter whatever they want? It doesn't mean it has to be accepted.


Validation can force usernames to be a-z but it doesn't work on freeform text. Forum comments should be able to state that the HTML open comment syntax is <!--


Not really. Lots of template engines escape and/or sanitize interpolated expressions, according to the context, by default.


Well that goes far beyond what I think of as "string templates", now you're parsing the string into HTML.


What law was he actually charged with breaking? I didn't see this mentioned in the article and it seems like this would be relevant information to include.

Anyways based on the available details, I'm surprised the police were even involved in what should really be a civil case between the rights holder and the YouTuber. I don't know if the Japanese public is safer or better off after this arrest.


Japanese news say 著作権法違反, which is "violation of the copyright act", IOW, copyright infringement.


Thanks, hopefully violating copyright in Japan doesn't come with draconian prison sentences.



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

Search: