skysight-inc/HackerNews huggingface dataset:
There should be a way to define an async executor API that works like Crossbeam's scoped threads API, so that the executor lives inside a fixed scope and is guaranteed to clean up any outstanding tasks before the end of that scope. Then it would be safe to accept references to longer-lived values on the stack. My guess is that there's not much demand for such an API outside of toy examples, though. (Does anyone use `crossbeam::scope` in production? It's a beautiful and important concept, but it seems to occupy an awkward performance point of "I care enough to worry about heap allocations, but not enough to use a thread pool.") EDIT: Ah, just saw GolDDranks' similar comment.
>because it's fun

Naaah not really, but hey tastes are different.
I get that things like proper kerning are probably doable with CSS.

LaTeX still does a better job out of the box, which goes a long way for my understanding of its typical use cases (resumes or long form reports).
And to be clear, I don’t blame her lawyers for doing this. It’s their job to zealously defend her, as distasteful as I find her behavior to have been, and the defense is what the defense must be.

But yeah, they must not have much else available if they’re going for the insanity plea.
This guy was 5'3" (though, granted, that's the record and a significant outlier): https://en.wikipedia.org/wiki/Muggsy_Bogues
To be fair, Bob Ludwig did a lot of work to get it onto a record.
At current exchange rates, that's $255K USD, per year. I manage a team of 11 people at a large US tech company. Level of experience ranges from 2-7 years. The lowest paid person on my team makes just under that amount. The highest paid makes about twice that amount.
It sounds like you didn't intend it as a personal attack, but inserting rhetorical questions like "Do you know anything about $foo" in an argument about $foo definitely comes across that way on the internet, and isn't allowed here. The fact that you repeated it twice makes it much worse—this is an attempt to expose the other commenter as "someone who doesn't know anything", which is needlessly personal.

If you know more than someone else, that's great, but please just share some of what you know so the rest of us can learn. Putting others down (even implicitly) doesn't serve learning, it's just distracting and builds up toxins in the ecosystem. Consider how much better your comment would read without those bits. The best way to react to bad information is respectfully with better information.
Honestly, the modern JavaScript toolchain is better at giving reverse engineers a headache than 80% of binary obfuscators.
They clearly thought there was some benefit to doing it with C++. I will say I generally agree with you on the consistency point.

Then again I spent none of my time working on this project so I refuse to criticize the result. That would be obnoxious.
If intelligence is ‘extremely resilient’ then we will find it everywhere in our universe.

If you use the cellular automata analogy that is being alluded to, ‘intelligence’ is being essentially equated to some limit of ‘complexity’

This is all very hand-wavey so it doesn’t appear to add much to the discussion?
> In this post, I will raise my objection against the idea of “Security by obscurity is bad”.

I think this article's fundamental flaw is that it conflates the concepts of obscurity and a secret.

To start with, a definition: a system is secure if an attacker has no reasonable chance of unauthorized access over a relevant period unless they are in possession of necessary secrets.

SSH with public-key authentication is secure by this definition, since the (remote) attacker has no realistic chance of guessing the proper secret key within a human lifetime and there is no better-than-chance way to obtain the secret key. Likewise, a strong, high-entropy password is impractical to guess.

Running on nonstandard ports, however? It doesn't add practical security because guessing is so trivial. The author's twitter reach had a 50/50 split on whether they scanned all ports for pen-testing, so that implies that using a nonstandard port increases the time-to-compromise from either (lifetime of the universe) or (about an hour) to twice that, depending on whether the second (real) layer of security is vulnerable. In neither case does the obscure port provide meaningful protection.

Some activities like port-knocking can add security, but only if the practitioner thinks of the knocking as a secret from the start. That requires:

* Limiting who has knowledge of the secret (i.e.: a port knocking routine known only to you is secret; one distributed in a public client for access to a production service is not),
* Having plans in place to change the secret if it is ever compromised (DeCSS) or found to be flawed, and
* Ideally ensuring that the secret cannot be guessed / confirmed independently of other secrets.

Other suggestions in the article ignore this difference:

* Database encryption requires an attacker to possess two secrets for extraction (internal access to the database plus the key) rather than just one. It's not obscurity.
* Randomizing variable names or obfuscating code is not a secret because an interested attacker can reverse the obfuscation with ordinary human levels of effort. The confidence here is strictly false, since it "secures" against low-effort attackers and not high-effort ones. The "secret" is distributed publicly, so it is no secret at all.
* The convoy example is again a secret; the point is that a would-be attacker does not know which car contains the target and has no reasonable ability to guess with better-than-chance success.

Obscurity goes from marginally effective (or outright ineffective) to counterproductive when its implementation makes it harder for the designer to reason about their own system. Someone who rolls their totally unique cryptosystem is relying in part on algorithmic obscurity for their security, but in doing so they give up on established (and battle-tested) best practices in favour of their own limited analysis.

Ultimately, the "Swiss cheese" model of security is a poor analogy because a big number for a human is a small number for a computer. To take the convoy analogy again, a would-be attacker is only going to get one shot, but a computer can try billions.
I wonder if it's the technology or if it's just getting older. Not a musician, but I used to do all sorts of creative stuff as a bored 13 year old. Programming, painting, coming up with board games, experimenting in the basement. Now that I'm an adult, I blow 1/2 my waking hours at work, then there's the family that wants to go hiking next weekend, and a kid to play with, and paying bills, and doing taxes, and cleaning the house, and mowing the lawn, and fixing the leaking sink, and being on boards and committees in the community, and on and on. I can maybe carve out an hour a week to do something creative, and by that time I just want to down a six pack and catch up on sleep.
Learn some basic stats, get knowledgeable in another domain, mix it with your coding knowledge, and BAM! Data Scientist.

No, but seriously, you don't need to be a rock star dev. to succeed in the world of tech. Usually, it's when you're good enough in skill A, and good enough in skill B, and combine those, that you get some interesting opportunities.
Many serious real-world scenarios do use obscurity as an additional layer

It works for the military, for spy agencies, and governments.

If obscurity didn't have any benefit, then the military's latest weapons wouldn't be tested in the Nevada desert, or some remote island; they'd be tested in Illinois, or off the coast of Long Island.
You don't.

Maybe to edit such a complex program that you're using to convert your equations to some other pretty format you should.
It is a similar story for aluminum. It takes much less energy to re-use recycled aluminum than to manufacture new. [0, about 2/3 of the way down the page].

[0] https://www.aluminum.org/aluminum-advantage/facts-glance

Also the aluminum association is a trade organization so they are obviously promoting the use of aluminum. But still some of the facts are quite interesting.
Why must the PDF encapsulate all requirements? My understanding of accessibility requirements it that you must have a version that is amenable to automatic speech, not that all versions must be.
Congratulations on all your success - hope it makes you feel good. You also happen to be in the right place at the right time. This to make me feel good.
The noise is that everybody's trying to extract money out of computing.

The whimsy is in just enjoying it and exploring within it for its own sake, which is the willingness to simply put time & money _into_ it without that noise.
I ran a world-writable off-the-shelf wiki for years. Trivially tweaked the edit url, visible on every page. But that was enough to break automated spam tooling defaults, so the spamming human might get to see a note, pointing out that robots.txt was blocking indexing, so there was really no reason to waste both our times. The dominant threat wasn't the spammer, but their dumb automation.
Or, you know, actual garbage collection (generational, JVM-style)
> I had a realization a while back, that in my opinion LaTeX isnt really needed anymore

Am I correct in assuming that you are not working in academia/on research? In that case, I would argue that from your point of view latex was never needed. On the other hand, if you are working on math/cs/physics research latex is indispensable...
NYSE exchanges to prepare for potential move from New Jersey datacenter [pdf]
Rust is a very clean and powerful language with several use cases. It's super easy to be productive in Rust and I'll predict Rust is going to dominate.
People who are actually bad at what they do rarely realize it! I think that's the difference between an imposter and "imposter syndrome".
notacoward is not an HN moderator. I'm the only HN moderator who currently posts moderation comments.
NASA wants to buy moon dirt from private companies
We have a few technologies in play in the world that operate on obscurity. Shared industry passwords like the DVD encryption key:

https://en.wikipedia.org/wiki/AACS_encryption_key_controvers...

Even if it was technically a password, it's really obscurity because the password was literally available in billions of devices worldwide - it's just hard to read. Then someone figured it out (specifically in WinDVD).

So, when someone says obscurity is fine, it's fun to remind them that all DVDs are cracked because someone thought so. (Not that I think that's a bad thing)
Couldn't agree more with this statement.

Also, professionally, if you find yourself in this environment: GTFO yesterday. It's toxic, and will take it's emotional toll over time. Especially if you're technically talented there's always a market for your skill... keep bouncing until you find a place that respects you as a professional/person.
It wasn’t because mathematicians were reluctant to change that math in HTML didn't take off. Rather, it was because browser developers were loathe to implement and maintain the enormous and complex pile of code that is MathML, and they said "Why should we, if you mathematicians already have LaTeX?" [0]

[0] https://en.wikipedia.org/wiki/MathML#Browser_support
How Will This Code Fail
Personal attacks and flamewar comments like this will get you banned on HN. We've had to ask you about this kind of thing more than once before.

If you're involved in a tit-for-tat exchange that's activating to this degree, please just step away for a while. The internet does it to all of us, but the purpose of this site is to practice something different together.

https://news.ycombinator.com/newsguidelines.html
Arbol, a parametric weather risk platform built on IPFS
Lets do this. Maybe this comment thread will spark the creation of an actual app. How do we get in touch?
Syringes, urine cups, stool sample collection cups, catheters, condoms - these days nobody wants to go through the hassle of washing and sanitizing certain items for reuse. A single-use plastic ban would make dealing with biohazards an energy and chemically intensive cleaning nightmare.
> - protocol exceptions like duplicated key

> - query exceptions

Even that is just barely scratching the surface. Postgres has ~250 error codes, and while not all of them can be triggered by all operations or statements, there's way more granularity in there than there is in just two piddly exceptions.
It's a step up on the CV for higher paid private sector work and yet the calibre required would be those already in high paid private sector work at the level of stock options that would pale this remuneration.

The type who would want this, would be those who want the kudos of working in that environment.

Now to get somebody good and also keen - that's very few people indeed.

Also working in government environments can be mixed, I've dealt with ministers with more common sense and ability to grasp the gravitas of a potential issue instantly and others who will kick any such can down roads of paperwork. Navigating all that is a skill that is needed on-par with the ability to tech. Knowing when to be blunt about an issue or when to pre-navigate the land mines of doubts. I can think of very few people who I've worked with who would be close to handling that. I know a fair few who could do the tech side, but the political/management navigation in government is a whole level of skill-set that you just can't get out of a book and whilst I know some good at that - both, a rare commodity indeed.
Moved to Go after being frustrated with Python and I couldn't be happier. I know there are complaints with the language but I'm not that picky, I can get in and hack features together really quickly. Deployment is awesome and easy. Edit: I'm specifically referring to cloud development.
It appears to be a similar problem akin to facebook, twitter etc. which promote "every" content no matter how bad (e.g. trolling etc.) it is for as long as the underlying metrics (e.g. click rates, revenue) appear to go up.
However, they don't see the second order effect, namely that customers lose interest in engaging with the sites over the long run and start looking for alternatives.
As someone who is not very good at JavaScript reverse engineering, I would tend to agree that minifiers are pretty annoying.
`Result<T, dyn Error>` from Rust (since I'm not a Haskeler) is a result that can contain any error. Which is exactly what unchecked exceptions are.

Rust developers can fluently switch and convert between conrete `Result<T, SomeErrorEnumeration>` and `Result<T, dyn Error>`. It works beautifully. Libraries usually enumerate their errors (leafs), applications usually just throw everything to one universal error bag.
Indeed, overly broad denunciations of 'security by obscurity' come up as a point of confusion often on HN, and this post provides a good, coherent summary of a proper response.

A defense mechanism that only partially mitigates an attack vector could be considered 'security through obscurity' if deployed on its own, but that same mechanism could be considered 'defense in depth' if deployed alongside other defense layers as part of a more comprehensive security model.
You are looking from the point of view of our very limited technological level.

To understand the problem you need to look at physical limitations of a civilization. A civilization that has an ability to wipe off another civilisation in another remote star system will definitely be at least hitting some physical limitations if not pushing them (if our understanding of physics is wrong).

We already have plans to image other planets by use of gravitational lensing with something like 25km per pixel resolution.

If we can image planet surface with this resolution remember, radio signals are also being amplified by gravitational lensing. While it seems it is more complicated I don't see any technical limitation to receiving even very weak radio signals this way.

I mean, if we can almost do it now it is naive to think they can't do it.

Our current biggest to getting this level of image is putting drones in right, remote place in space many AUs from us. If we are talking about a civilisation that has means and time to wipe off other star system then they definitely don't have that problem.
Not even considering the math formatting, Html is still lacking good footnotes, bibliographies, glossary generation, index generation, and table of context generation. Browsers also render things atrociously compared to a latex pdf.
The problem with heavily focusing on Arabs while paying less attention to other threats is that Arab Islamist terrorists aren't the only problem aviation security needs to deal with.

Focusing most of the security effort on Arabs is a good way to fight the war of 19 years ago, but it leaves the air travel system vulnerable to upstart terrorist movements that see the lack of universal security as an exploitable vulnerability.

For example, there's nothing to say that America's right wing terrorist groups won't decide to switch from shootings and vehicle ramming attacks to attacks on air travel. The TSA ought to be prepared for this, or any other, emerging threat.
Five Online Advertising Events to RSVP in Q3 and Q4 2020
I recently read that YAML has a way of specifying a "sequence of sequences" which could work for tabular data like that in your example. i.e

- [Server,Subnet,IP]
- [db01,databases,10.1.2.3]
- [db02,databases,10.1.2.4]
- [user01,filers,10.3.10.1]
- [user02,filers,10.3.10.2]

That being said, the CSV does seem more straightforward.
We would like to support React Native in the future which both support Android & iOS
For a reporter at znet, that mush seem like a fortune. But yeah, for someone who might be qualified for that position, it would be a pittance.

Governments really just need to be competitive with their pay if they’re going be successful in their missions. Though, for a lot of people, a successful government is undesirable...
It does seem that the OP constructs a bit of a strawman by claiming TeX's source code is too complicated for an average computer science graduate. I doubt even the top 5% of computer graduates could more readily understand the source code of most common programs.
Agreed. The maxim warning against "security from obscurity" is often reduced to an irrational comprehensive avoidance of obscurity. It's similar to the irrational avoidance of all performance optimization because Knuth warned of premature optimization.

Both reductions lose practical utility by omitting nuance.

* Avoid wasting your time doing performance optimization until tuning is necessary. But definitely take obvious and easy measures to ensure your software is fast, such as choosing a high-performance language or framework with which you can be productive.

* Don't exclusively rely on obscurity. But definitely take obvious and easy measures that leverage obscurity to add another layer of defense, such as changing default ports, port-knocking, or whatever.

To use the same art of reduction to counter the common interpretation: A complex password is, in a manner of thinking, security from obscurity. Your highly complex password is very obscure, hence it's better than a common (low obscurity) password from a dictionary.
React Native use Yoga which use most of CSS Flexbox syntax. So it's similiar to React with FlexBox
It's more than that.

I read more than one or two IT papers which donated variable types by using a different font between A and A and that difference was essential for reasonable understanding the papers.

Then the notation is overloaded.

Brackets are not even necessary enclosing something or are not necessary well balanced.

"Bar" based brackets and bars used for non bracket purpose are not necessary differentiate by noon visual clues. Etc.

It's already often confusing for people which can read the formula so I'm not surprised that really annoying for people which can't normally read the formula.

A super simple example is that [a;b[ is that "German"/(EU?) still to write an range with inclusive start and exclusive end. In the US [a;b) is used instead. But let's be honest something like rangeIE(a, b) or similar (Latex range_{ie}) is much better for a screen reader I thing and that's a trivial example not one of the really bad ones.

I think all formula should be written in a way which represents semantics not visuals and then be compiler to a classical visual representation (maybe using some additional non-semantic style annotation block).
Whilst this is recent enough knowledge to not be included in what most people here would have learned in high school, we have found many genes that have been transplanted laterally. We are technically not sure this was by viruses (perhaps it was by bacteria or even somehow directly).

Genes do spread without procreation. This is a certainty at this point.
Yeah, that's what I was trying to get at with my "in the age of automation" comment. If you go to a period in history without automation, then obscurity is going to be a lot more effective. And that's why I think people still want to go back to it. Obscurity is much easier to wrap your mind around than RSA, et al.

However, the psychological warfare video does make me think that there's still a place for obscurity after you've already used actual security measures. If you can find any technique that makes your attacker work harder vs some other target, then it feels like there's an economic value to doing it as long as the cost to you is relatively low.
> You seem to be thinking in terms of security mechanisms either perfectly blocking attacks or being useless.

Ours is an industry with a lot of people "on the spectrum".

https://thesilentwaveblog.wordpress.com/2017/03/08/aspergers...
Rust is a very clean language with several use cases. It gives a lot of power to the programmer and it's super easier to be productive compared. Rust will win over Go much like React.js won over Angular. I'd predict that the Rust language will dominate and become a must-know in a couple years time.
> The US movie industry already censors itself from anything that can remotely offend China.

I wonder how that could be changed. Could the US just pass a law banning exports of movies to China or banning cooperation with their censorship process? It's not like the censored movies are going to do much good, the censorship plus profit-seeking has a pernicious effect on the US domestic market.