1,427 karma · joined July 7, 2015
If it were up to me, housing should also be included in the definition of inflation. That would be a good way to lay bare the downsides with an aggressively expanding monetary policy.
The author of the article customized his environment so opening a file no longer froze his editor.
I wouldn't classify that either as "slightly better ergonomics" nor "tinkering" nor "bike shedding".
He had the discipline to improve his favorite editor. Good for him.
Emacs is obviously a very powerful environment for people who know how to use it. I applaud the author for documenting how he fixed this.
The only difference between emacs and many other open source software is here you can easily solve bugs in your config file, instead of filing a pull request or submitting a patch to some git repo. The first you call "tinkering" and look down upon. The other I assume you approve of? But why the double standard?
"when I was young I used to work out and eat healthy... a couple of decades later, I just fund it all so exhausting".
Customizing your computer environment is good. Eating healthy is good. None of those need to end up in a "rabbit hole".
Everyone can be tired of life and give up due to exhaustion, but greatness requires discipline. This is also true with the craft and art of programming.
When I travel in for example Africa and South America and Asia I bring my yellow vaccination card together with my passport, and this information is used to make entry decisions when I'm at the border of these countries.
I'm not particularly upset at what Spain is doing here. We live in a society where people can travel freely within the European Union (Schengen). If you refuse to be part of societal obligations to combat a dangerous disease, then you shouldn't be upset if your traveling or interactions with other nation states will be impacted in one shape or another.
PII is more or less an American term. In the context of European legislation such as the GDPR, there is no such thing as "PII".
Within Europe and within the context of the GDPR, you do however talk about "Personal Data".
Personal Data and PII are both about data that can identify a person, but Personal Data (Europe) is much broader than PII (US) from a regulatory perspective.
This was a pet peeve of the best GDPR lawyer I ever worked with, and now it's a pet peeve of mine as well. :-)
I have provided a Criticism section of a Wikipedia article that points out light pollution criticism from many authoritative sources, including photographic evidence. You dismiss this photographic evidence, but why should I listen to you when I can listen to the IAU, for example? Or Nature? Or the astronomical community?
Quote International Astronomical Union: "The scientific concerns are twofold. Firstly, the surfaces of these satellites are often made of highly reflective metal, and reflections from the Sun in the hours after sunset and before sunrise make them appear as slow-moving dots in the night sky."
Here's an entire article in Nature Astronomy about the issue https://www.nature.com/articles/s41550-020-01238-3
Here's a quote from a Senior Advisor to the European Space Agency https://twitter.com/markmccaughrean/status/11323943469454213...
Here's an entire discussion at the American Astronomical Society about the issue https://aas.org/posts/advocacy/2020/12/impacts-large-satelli...
Here's an article about how the problem will get workse https://www.scientificamerican.com/article/spacexs-dark-sate...
But sure, you call me an "entitled and dismissive urbanite".
This is light pollution.
Where do you live? In most of Europe and SE Asia you can get gigabit broadband.
I think SpaceX is a cool company and I could see myself work there, but StarLink is, IMHO, a shitty project that ruins the night sky and space for everyone. https://en.wikipedia.org/wiki/Starlink#Criticism
If your (the author) mindset is that "everyone else is an idiot", be it management, or regulators, auditors or some other group that is not your group (engineer?), then unfortunately you have an attitude problem.
If furthermore you maliciously misinterpret the other group, saying "they want us to be compliant, not secure", based on misunderstanding the domain expertise _of your own group_ (!), then you are a liability to your business and should be kept at arms length from external auditors.
Because the author clearly has no clue what he is doing, and based on his technical shortcomings he is speaking down on others who are _actually_ doing their job correctly: the auditors.
Why is the author comparing bcrypt using 32 iterations with sha512crypt with 5000 iterations? Why not increase the sha512crypt iteration count by orders of magnitude if he want the hashcat test to fair equal or better under the testing methodology in use? Why is he using hashcat and basing decisions solely on that tool? Why is he using shacrypt at all and not a a proper KDF, such as PDKDF2, plugging in SHA2?
It still boggles my mind that the same person can:
(1) one hand be that stereotypical designer with the scarfs and the small cups of coffee and the Leica cameras, designing user interfaces and logotypes and brands (Spotify logotype, Spotify green color), designing popular fonts for the Internet ( https://rsms.me/inter/ )
(2) on the other hand be a great low level engineer, creating programming languages, virtual machines ( https://github.com/rsms/sol ), text editors, stuff like GraphQL, etc
A one man army for sure.
So Sappho lived over 2500 years ago.
Obviously we don't have a complete manuscript of everything she wrote in original. What we have instead are various manuscript copies and copies of those manuscripts, many of which are corrupted, partially destroyed, wrong, fake or has other textual issues. Excluding the fake ones (how do you know which are fake?) these manuscripts are corrupt, destroyed or wrong in different places. Some fragments are quotes from other manuscripts which in turn have the potential issues mentioned.
When preparing a critical edition, you basically collect all of these ancient manuscripts and try to figure out how they relate to each other, and based on what you know of the manuscript and the text you can relate them in a tree (imagine a git commit log with branches)... for example if manuscript B is copied from an earlier manuscript A. Then based on your skill and knowledge you use this limited information to try to figure out what the original manuscript said.
Apart from some old papyri, like the ones found at https://en.wikipedia.org/wiki/Oxyrhynchus, for many authors the oldest surviving manuscripts are often from around the 10-12:th centuary. So if you read Homer or stuff like that, it's been like 1700 years before the original and the oldest surviving manuscript used to base the critical editions used today. So who knows what was originally in the manuscript :-)
These critical editions are then what other scholars use when they translate these poems into English.
The fun part about reading the critical editions instead of translations is they show you what the textual issues are: often it's not obvious and controversial what a particular word should be in the text, if there are many possibilities that are equally likely. The translations will have to pick one interpretation of the text and stick with it, to not make it overbearingly complicated for people to read the works.
Edit: Two more things
(1) The most common textual corruption are related to word anticipation when you copy a text by hand. So say you're a 12:th centuary monk and you copy (by pen) a text, you will probably read a sentence, memorize it, and write it down in the copy you are working on. A common problem is if in a previous sentence you had to write down a word that is different but sounds like a word in the sentence you will now write: it's easy to accidentally write down the old word again.
(2) More nefarious: There are many instances when copyists remove or alter text for political or religious reasons.
This reminds me of my favorite typo: https://slashdot.org/comments.pl?sid=406154&cid=21914102
If you don't want people on the internet to connect to your server, then you shouldn't allow network connections to your server. A few connections per minute hardly classify as abuse in any reasonable sense of the word.
The owner of the source network, on the other hand, (compared to the destination server), I think have a more legitimate reason to raise flags. Most cloud providers for example do not allow port scanning from their network (for various reasons). If you're gonna send out millions of packages all over the place I think it's good practice to inform your network provider first.
> Much of the rest of the world takes for granted architectural principles of how to build life-affirming human settlements. These principles evolved over thousands of years, and it’s no accident that so many cultures reached the same conclusions. Urban Europeans, and indeed Armenians, are accustomed to vertical growth, mixed-use development (shops on first floor, apartments above), sidewalks, plazas, public squares and street cafes. These are the fixtures amidst which your halcyon childhood days played out, where you walked hand in hand with your first love, where you met friends for coffee, and hopped the train to work. It’s the corner with the pastry shop, it’s the supermarket down the street, and the bench in between.
> Few people can prepare themselves for the degree to which Americans have, in the last half-century or so, taken this entire corpus of human experience and thrown it completely into the trash, with the exception of a few older cities–not the places where the majority of Americans live. What has replaced it is a surreal moonscape. For those accustomed to the traditional urban civilisation, the primary question in America is: where do I go? What do I do? Looking around leads to an intangible but intense realisation of emptiness. Suburbia is both a cause and an effect of the destruction of civic and community life in America: there’s increasingly little to come home to, and vanishingly little to go out to.