HN user

aschatten

69 karma
Posts3
Comments72
View on HN

If this model works as expected, then it should take into account those who "would have die very soon" otherwise. It models the deaths that would have happened if it were not for COVID and measures the difference against that number. So the person you mentioned should be counted in the projection.

The choice of headlines does convince me that journalism isn’t getting better.

I think it is a decently chose headline. Moderately sensational, yet eye catching and conveying the premises, that it is going to be about a gloomy prediction that may or may not turn out true.

Ignoring your political reason as completely unrelated to the article.

On the practical side, do you know any language that uses Cyrillic alphabet? If no, then you are not used to it and this is why it looks awkward, blocky, etc. and cursive is not a nightmare and is very readable, much so like cursive text written in English.

If you do know any language that uses Cyrillic, can you provide examples to support your characterizations?

During the initial attack phase, cyber actors scan the internet for SonarQube instances exposed to the open Internet using the default port (9000) and a publicly accessible IP address. Cyber actors then use default administrator credentials (username: admin, password: admin) to attempt to access SonarQube instances.

Given how often this happens, not having a default password and forcing users to set it should be a standard practice these days. Relying on administrators of the instance doing the right thing obviously keeps failing, thus an option to do the wrong thing should be removed completely.

There is nothing wrong with CSV or text base formats. You can even use AWS Athena to query CSV feels stored in S3. It's a good format for data import/export, that many systems can natively understand or have tools to parse, given it's known how to interpret data.

It was a data pipeline issue. Software has little to do with it. If they received data in json and tried to interpret it as CSV, the same could have happened. I believe Excel even warns when you open file that has too many rows.

emacs has plugins that provide all the essential features of an IDE with minimal fuss

I vehemently disagree. There is no such thing as minimal fuss in emacs, especially when it comes down essential IDE features.

for specific languages like Clojure or Common Lisp

Common Lisp is esoteric language at this point, not relevant here, IMO.

(disclaimer: I am an IntelliJ fanboy)

From my experience out of the box you get poor performance and you have to spend a lot of time figuring out how to change configuration to improve it as knowledge is scattered in many places and not always up to date.

I don't know if you are talking about IntelliJ or VCS, but IntelliJ can quickly start an empty project. And you don't to spend time to figure out how things work. I mean, there is literally no entry barrier for a bare bone project.

I wish there was an editor with low latency, smart search, some proper file system database

You are describing an IDE here. Smart search and a proper file system database, it means operating not on a collection of text files but on a project and a code tree, which is the main difference between IDE and Editor.

I think the success of VSCode is because you can easily open it in your current directory from the terminal and it will show you your folder etc.

IntelliJ is adding this functionality slowly: https://blog.jetbrains.com/idea/2020/04/lightedit-mode/ It's not on par with opening a folder in VCS, but it's a matter of time until the close the gap if they choose to.

I am the same way. I use emacs for git, org notes, small adhoc scripts, but for actual project work – IDE, hand down. I have converted a long time emacs user to try PyCharm once. He was skeptical for a long time, then he switched.

Interesting study, but it’s has been suspected for long that vitamin D might have all this effects.

Without being able to see the data, this does not feel right. I would like to see how they did cross-validation, test/train split, assigned weights, proportion of missing values. If you have data, this can be easily reproduced and studied. What if it’s overfitting?

Another "boeing still uses floppy disk" article, but this one reads like an ad for the company mentioned.

They answers their own question:

Emergency response units talked by two-way radio and sent each other text messages with photos of paper maps, said Kenneth Dueker, the director of Palo Alto’s office of emergency services. “Here we are right in the middle of Silicon Valley,” Dueker said. “Why am I using paper and pencil and a two-way radio when I should be using geospatial tools? It’s very 1920s, frankly.”

and few paragraphs later:

"Glitches in software and outdated maps have been reported in the warning systems used to alert people in the path of the flames during several major fires in the last year."

I understand how port knocking can throw off nmap and reduce brute force traffic.

Does it solve anything else?

I believe there are sshd vulns extant that you and I don't know about and port knocking allows me to worry less about them.

Wouldn't you need to worry about vulnerabilities in knockd?

Didn't Telegram challenge this rule as well? > * Never roll your own crypto Afaik, discovered practical vulnerabilities like [1], [2] were patched, and the rest are theoretical, like [3].

  > Using Symmetric Encryption in the Database: When you write data to the database, use a function like encryption_algorithm(data,key). Likewise, when you read data, use a function like decryption_algorithm(data,key). If the attacker can read your backend code, obviously he/she can decrypt your database.
I think the author misclassified this method. An actual encryption is not obscurity. It would be, sort of, if the key is stored in code. But when a proper key management is in place, it's a solid approach.

[1] https://news.ycombinator.com/item?id=6948742

[2] https://web.archive.org/web/20181118154823/https://www.alexr...

[3] https://eprint.iacr.org/2015/1177.pdf