HNHacker News
TopNewBestAskShowJobs

Nadya

4,139 karma · joined April 7, 2015

nadyanay.me - U+26A5

Democracy is totalitarianism. Freedom is oppression. Censorship is freedom.

[ my public key: https://keybase.io/nadya; my proof: https://keybase.io/nadya/si gs/lklP5B4B7JREUYCzdbw60w0u3esviheCxECPU0D9TgU ]

submissionscomments
Nadya··on Teens are rewriting what is possible in the world of competitive Tetris
Dvorak does not evenly use all fingers - it is especially more right-hand dominant and that trait was actually why I hated it as a left-handed dominant person. The amount of finger travelling the right hand has to do for Dvorak is insane. Almost all improvements of typing speed in Dvorak are attributed to the learner finally learning how to type in the first place. The main draw to learning Dvorak should for the ergonomics - which are strictly inferior to Colemak. While Colemak is nearly as right-hand dominant it doesn't require nearly as much finger travel making it more ergonomic for left-hand dominant people as well.

Also - as someone who has learned both - I adamantly believe Dvorak is inferior to Colemak in almost every single way. From difficulty learning the layout to the ergonomics once learned to having to rebind or relearn hotkeys - especially common ones like cut/copy/paste. I only wish I had discovered Colemak prior to wasting time learning Dvorak all those many years ago.

Colemak heatmap: https://zhangshenjia.com/wp-content/uploads/2012/04/8.jpg

Qwerty & Dvorak heatmap: https://whyfiles.org/wp-content/uploads/2012/02/dvorak3.jpg

(And as Bradwood pointed out in the response below - definitely biased towards typing English and not other languages. So people who primarily type a language that is not English may have drastically different experiences.)

Nadya··on Some Thoughts on Zig
I'm keeping an eye on Vale [0] but will continue to use Rust for hobby projects because the community/tooling that has built around it has made it much easier over a few years than when I first gave it a try in 2018 and especially as support for development on Windows grew. I went from absolutely struggling to get so much as a win32 GUI window to open [1] to writing a basic counting app [2] for a game I play to completely rewriting that app to not suck [3] (even though the code is still awful).

Zig looks nice to read and understand. However at my skill level (more or less a skript kiddie) I don't trust myself to not cause major memory-related bugs. In fact, I can't help but wonder if it's hubris or what when extremely intelligent, college educated, programmers with more than my lifetime of experience who still manage to write programs riddled with memory safety issues and in the very next breathe say memory safety isn't an issue just write safe code. I wonder what skill/knowledge thresholds are where "I don't trust myself to not make those mistakes" turns into "I won't make those mistakes."? Honestly it reminds me of the low IQ/high IQ meme [4].

[0] https://vale.dev/

[1] https://gitlab.com/NadyaNayme/rusty-eyes

[2] https://github.com/NadyaNayme/Dorothy

[3] https://github.com/NadyaNayme/Dorothy-egui

[4] https://kimiwo.aishitei.ru/i/sZaEWnY3NvfXecLm.png

Nadya··on Advice for the next dozen Rust GUIs
What's funny is that it pisses off a large number of those 1% of users who swap OSs frequently as well. So it isn't even for the benefit of that 1% either.

When operating a Mac I expect Mac-specific behaviors. When operating a Windows PC I expect Windows-specific behaviors. I LOATHE programs that decide to do away with OS-isms that I am accustomed to and require me to learn how to "do things their way" because they wanted cross-OS consistency. Sometimes this means conforming everything to a single platform which is partially evil but just as often it means conforming to _none of them_ which is pure evil.

But I understand this - as a web developer I've experienced pressure from Project Managers and the "decision makers" to make things consistent across browsers/devices even if doing so goes against how the users of said browsers/devices would expect things to operate - breaking user expectations and creating a worse UX for many users. I fight against it when I can but I'm not always successful.

Nadya··on Using a catch-all domain is a mistake
I'm going to mirror most of the other commenters in saying - I've been doing this for nearly a decade and have basically never had an issue with it and have absolutely prevented some spam because of it. The "social awkwardness" problem of using "Company@example.com" can be solved by using "PineappleBanana@example.com" instead or random characters or my personal favorite throwaway "[Company]SentMeSpam@example.com". Yea, you might have to use a password manager to know which random string of nouns is tied to what account - but no more "social awkwardness" of using the company name in your email (can't say I've ever had that experience either...)

In fact the only issues I've ever had with a "non-standard" email address (aka: not @gmail, @yahoo, @hotmail, etc.) is that one of my domains is a .ru address and even before the modern-day issues surrounding Russia .ru addresses get blocked in many places. My fallback email is an email hosted by https://cock.li which being chan-adjacent also gets blocked so occasionally I simply have to accept that I am not wanted as a user because my email isn't good enough.

Nadya··on “Shuwa-Shuwa” is an illustrated book of Japanese onomatopoeia
Onomatopoeia are commonly equated to phonomimes but can also include phenomimes and psychomimes. Phonomimes are meant to imitate an actual sound - like "bark" for a Dog (wanwan in Japanese). Most Japanese onomatopoeic expressions come in the double form (the sound repeated twice). There are of course っと and り forms of onomatopoeia but the double form is probably the most common and among the most known ones.

Phenomimes are onomatopoeia that depict something closer to an action than a sound - for example "powering up" (can't recall this one sorry) or "to be spinning around" (guruguru).

Doubled base onomatopoeia are not unique to Japanese either. Think of "bam-bam", "pop-pop", "click-click", "chirp-chirp", "oink-oink" or a bit less strictly "rattattat". I believe the technical linguistic term for this is called reduplication.

Nadya··on There Is No CD Revival
1. This presumes Spotify will still be in business in the next 10, 30, 50+ years.

2. This presumes 100% of the music collection is on Spotify. Personally speaking, 60%~ of the music I listen to ISN'T on Spotify.

3. This presumes music is only desired to be listened to when an available internet connection is available.

Having to shuffle my media collections around whenever a third party went out of business or pivoted was such a massive headache that it was the inspiration for just managing my own media collections locally.

Nadya··on Alphabet Announces First Quarter 2022 Results
Depending on the popularity of the content you consume you can use https://sponsor.ajay.app/ which is a crowdsourced way of skipping the in-video sponsorship ads. I've had it work for some relatively obscure channels and it reliably works for most any popular/large channels as well.

I have a zero-tolerance ad policy. If there isn't a way for me to reliably skip ads I will stop consuming the content. I'm willing to pay but all too often you end up paying for an ad-free experience and eventually ads get re-introduced anyway or the ads take on another form.

Pardon the language but fuck advertisements. If it isn't a dry, boring information-based ad I don't care for it. I have no tolerance for the emotional manipulation and psychological warfare committed by modern advertisements. I'm sick of seeing [attractive people enjoying time spent together while <using/eating/drinking> <product> during a <meal/activity/social gathering>] or [commercial designed to make you laugh or smile so you associate being happy at some level with <product>]. I was sick of those commercials 20 years ago because they're all the same and I'm even more sick of them now that I'm old enough to see how they're designed to be manipulative.

Nadya··on U+237C ⍼ Right Angle with Downwards Zigzag Arrow
https://en.wiktionary.org/wiki/%E2%8B%9A

> If the function f is differentiable and concave, then f′(x1)⋚f′(x2) as x1⋛x2. That is f′(x1) and f′(x2) have the opposite relation as x1 and x2.

Nadya··on Ask HN: What does 12:00 AM mean?
And then you have Japan where that could be March 24 at 25:00.

https://kimiwo.aishitei.ru/i/ytPbouZ21iYnNXi7.png

Not all too uncommon to see bars and bookstores open until 27:00 or 28:00 and it's surprisingly intuitive when you consider when the bar is open. ie 19:00 ~ 29:00. (7pm - 5am)

Nadya··on API-0.core.keybaseapi.com has expired certificate
> I never found the identity/distributed-account thing on keybase useful, as I explicitly DO NOT want my accounts linked, but if that's your thing, definitely worth checking out.

The funny thing is that is the only reason I wanted to use Keybase and what I found most useful was that I DO want my accounts linked (at least ones with related identities) so that it is easier to verify my identity across platforms in a still-pseudonymous but user friendly way.

I used to be in a position where it mattered more but it's still nice to have.

Nadya··on ReVanced
If the signal you are picking up from downvotes is that the channel must be hated in some way you should watch fewer outrage-bait/drama channels and more learning/tutorial channels. Some tutorial videos are made so confusingly and poorly, or worse teach incorrect information altogether, that the only signal for people to know "This video is absolute bollocks and you shouldn't waste your time watching it" is when he gets downvote bombed by anyone watching it. It's a single to then check the comments section where you'll probably see some comment explaining all the problems/incorrect parts of the video with more likes than the video itself has often with a recommendation to a better video on the topic.

Sure - channels absolutely used to be downvote bombed because people were mad at the content creator for whatever reason they may have had. But for a good section of videos the downvotes only spoke about the quality of the video itself and nothing about the content creator.

Nadya··on So, you want to be a darknet drug lord
> I'd say if you are doing it long term then you are doing it wrong.

I agree entirely but it also depends on your threat model. When making my post I didn't have DNM's in mind (though that's the context...) and was actually thinking about the abysmal opsec of many private tracker admins.

Nadya··on So, you want to be a darknet drug lord
Opsec is incredibly difficult to get correct - especially in the long term. Many of the people who need to be getting it correct do not and the only reason they are not in front of a judge or serving time is simply because their government hasn't given a shit to so much as glance their way. Because if their government actually gave a crap to investigate they'd be found almost instantly. From doing stupid things like sharing photos of their pets to more mundane things like having very obvious hours of activity and using vocabulary that varies spelling regionally (eg: how you spell color/colour suddenly matters) or even worse using regional slang like a bunch of Australian slang.

If you want to be a darknet drug lord my advice is of a different flavor: Don't let yourself become too big. Once a (or multiple) governments are after you it is very likely only a matter of time before you get caught. Not because the government is particularly good at tracking people down or somehow nearly omniscient but simply because you likely had or have terrible opsec and finding you is more trivial than you've led yourself to believe. If you believe they are already looking for you it's time to abandon everything and disappear. Live your life like it never happened and whatever you do don't pass on the torch. Let your work die and be buried and someone else build on top of the grave.

Nadya··on My boundaries as an open source developer
The big misconception you speak of is being that the requirement is met if a <compiled binary> is released under a FOSS license but that isn't at all what I said. I said the licensing of the <source code> - not of any compiled binaries - is what matters. Swapping <source code> for <compiled binary> of course entirely changes the claim being made. The freedoms afforded by FLOSS licenses necessitate the availability of the source code as a pre-requisite to being met. So one does not meet the terms of the license of the source code if users cannot study/modify it and cannot distribute modified versions of it on account of not being able to modify it due to not being able to access it. Access to the source code in FLOSS licenses is intentional but also a side effect of the freedoms already afforded. There is no 5th freedom requiring the source code to be available because it already must be available in order to meet the requirements of freedoms 2 and 4.

But I'm still entirely wrong.

I'm completely and unequivocally wrong due to two other requirements - both of which actually pertain to the source code and not its licensing. There are in fact two requirements placed upon the source code itself to be considered open source under the OSD or even as free software as the FSF defines it. (1) It may not be deliberately obfuscated. Which makes me wonder if programs written to be deliberately obfuscated are technically not allowed to be considered free-libre or open source software? Such as programs written to compete in IOCCC or if the intent here matters and it's more about releasing obfuscated versions of source code that was not already written to be obfuscated and was made obfuscated with the intent being to prevent others from studying/modifying it. That one I think is a bit of a technicality. (2) The other being that the source code, if not released with the program, must be available in a well-publicized manner at no more than a reasonable cost of distribution/reproduction (ie no charging $1,000 for access to the source code to claim it's "technically available").

Nadya··on Christopher Alexander has died
Software Engineer.
Nadya··on My boundaries as an open source developer
The problem with "free software" definitely exists as well but the intended meaning is still a plain English meaning of the word "free" but not the first one that comes to mind. Making it easier to correct "Free as in freedom, not as in beer." than "Please read the OSI definition of what 'open source' means." or still a bit confusingly "It's actually about the licensing of the source code and not the source code itself."

I agree it is still a problem - which is why "gratis" and "libre" see use to prevent the confusion and why I prefer the term "FLOSS".

Nadya··on UK Online Safety Bill will censor some “legal but harmful” content
You've been to the domain before then. - it sets a value in localStorage to make it a banner at the top instead. First time visitors and Incognito browsers see this on page load: https://kimiwo.aishitei.ru/i/q6P9wN2OBQSDI0n2.png

If "popup_71227_times" is 0 you get the fullscreen popup asking for email with a "Let me read first >" link underneath.

Nadya··on My boundaries as an open source developer
I made my point incredibly poorly as I was a bit pressed for time. My bringing up other initiatives misled you as to the point I was poorly trying to make. My point was that laypersons know what the words mean - there is no "aha, it actually means <an entirely unrelated definition of the words used>!" in the words "childhood cancer data". If one knows the words "childhood", "cancer", and "data" they can accurately guess what "childhood cancer data" means and that is not the case for "open source" which has an obvious meaning in plain English which is also not what it means at all.

How people use words matters almost as much as what those words mean - and meaning can change because of how people use words over the course of years, decades, or centuries. Pointing at a dictionary is only useful when clarifying which meaning is being used.

> That's not what's at issue.

Then what is the issue, if you don't mind me asking? The issue as I understand it was what was meant by "open source" and my not already prescribing to the OSI's definition of it. Pointing to the OSI's definition cleared the air about which definition was being used but did not resolve the issue that the phrasing is easily misunderstood outside of the OSS community and is the reason the term "FLOSS" exists to circumvent the issue. The fact they had to specify the definition as defined by OSI and not "source available" is part of the issue. That this misperception exists at all is part of the issue. That the OSI has had to plea with people to please use the branding how they want it to be used [0] is part of the issue. That it is not totally uncommon to see "open source" to only mean "source available" is part of the issue. That "open source" has an obvious plain-English meaning separate from it's "intended meaning" is part of the issue. This is an issue that has existed in the community for the entirety of its 23 years of existence, been spoken about at length by both the OSI and FSF as being an issue, and some people are acting like it's the first time they've ever heard about this being an issue or even denying that it is an existing issue at all.

I'm not sure how many articles from community leaders and the very people who defined the words in the first place speaking about the issue being an issue I need to cite before people go "OK maybe it is an existing issue and not just Nadya saying it's an existing issue when it isn't."

To actually and intentionally move the goalposts this time: It still isn't even logically sound that because you're able to fork and send a PR on Github that the project is "open source" to begin with and it especially doesn't follow that the project is compliant with OSI's definition of "open source". Per my understanding of the Github Terms of Service Section D Parts 4-7 the license given to other users only extends so far as to their using Github's functionality (including "forking") - which I'm reading as not providing any license to compile or redistribute modified source code compiled into an executable. Making sending a PR possibly the only reasonable method of ensuring that a fix or feature makes it to end users.

[0] https://opensource.org/node/163

Nadya··on My boundaries as an open source developer
Does similar confusion exist when asking people what the Childhood Cancer Data Initiative or Sustainable Energy Initiatives are about? Do you think there is a similar level of misperception among laypersons about the meaning of those initiatives? The common misperception regarding "Free Software" is that people think it means "gratis" rather than "libre". The common misperception with "Open Source" is that people think it means "source-code publicly available". But if the argument about common misperceptions being muddied water is not entirely convincing for you we can take another look at how the terms are defined.

The Free Software Foundation disagrees that "Open Source" and "Free Software" are the same thing. The discussion about whether they are the same thing should end there if we are to accept that the authority defining "Open Source" are correct in their definition of "Open Source". The same credence should be given to the authority defining "Free Software" providing the correct definition of "Free Software". If we are to accept both of these definitions as given by the authorities defining the terms - then they are necessarily different because the authority defining one of the terms says so despite any attempts of another authority who did not define the term at claiming otherwise.

In other words: X defines X and says X = X and X != Y. Y defines Y and says Y = Y and Y = X. Since X defines X and Y does not define X we must accept that X != Y per X's definition of X despite Y's attempt at redefining X such that Y = X.

It's uncharitable to point to OSI's definition of "Open Source" and OSI's claims that they are one and the same while completely ignoring FSF's definition of "Free Software" and FSF's claims that they are different.

Nadya··on My boundaries as an open source developer
Ask anyone who is not already heavily involved in open source software development. They can still be technical users - hell they can even still be programmers - just not already entrenched ones. You're going to have to correct them and go "No I mean this" in the same way that the Free Software movement has to correct people with "Free as in freedom, not as in beer."

See the "Common Misunderstandings of “Free Software” and “Open Source”" section of the article I previously provided. This is a known issue by both OSI and FSF.

Nadya··on My boundaries as an open source developer
Those who sit on the Open Source side of things constantly muddy the waters and claim they are one in the same. Those who sit on the Free Software side of things are adamant that they are related but different.

https://www.gnu.org/philosophy/open-source-misses-the-point....

The important bit is here:

> “Free” and “open” are rivals for mindshare. Free software and open source are different ideas but, in most people's way of looking at software, they compete for the same conceptual slot. When people become habituated to saying and thinking “open source,” that is an obstacle to their grasping the free software movement's philosophy and thinking about it.

Nadya··on My boundaries as an open source developer
It doesn't use the term directly, no. Because to hackers, especially back in 1999, Free and Open Source were one in the same. It was just a difference of branding. However Bruce differentiates between "Open Source" and "Free Software" in writing and he only does so because public perception of what "Open Source" actually means had already been muddied in the year since OSI's founding and the freedoms afforded by FLOSS were already being de-emphasized and put on the back burner.

To quote Bruce:

> Most hackers know that Free Software and Open Source are just two words for the same thing. Unfortunately, though, Open Source has de-emphasized the importance of the freedoms involved in Free Software.....

> ......Sadly, as I've tended toward promotion of Free Software rather than Open Source, Eric Raymond seems to be losing his free software focus. The Open Source certification mark has already been abused in ways I find unconscionable and that I will not abide. I fear that the Open Source Initiative is drifting away from the Free Sofware values with which we originally created it.

There would be no need to make any kind of distinction between Free Software and Open Source if Open Source was being perceived as Free Software.

OSI was and always will be a marketing gimmick [0] created to sell the idea of open source to commercially interested parties.

> We realized that the Netscape announcement had created a precious window of time within which we might finally be able to get the corporate world to listen to what we have to teach about the superiority of an open development process. We realized it was time to dump the confrontational attitude that has been associated with `free software' in the past and sell the idea strictly on the same pragmatic, business-case grounds that motivated Netscape. We brainstormed about tactics and a new label. Open source, contributed by Chris Peterson, was the best thing we came up with.

Not to downplay OSI at all. It was extremely important and widely influential in Netscape's journey to becoming Firefox and I'd even argue is still important today. But the issue centered around what "Free" means ("Free" as in freedom - not beer - which is why the term "libre" is often used as well) and that "Free Software" already had a poor reputation in the business world and so it needed to be rebranded. Eric Raymond made it very clear that he places importance on phrasing and branding and attributes the tactics used by OSI to its success and why the Free Software movement failed. [1]

Honestly a comment by Havoc Pennington on that very post, dated Jun 28, 1999, sums up the issue perfectly.

>I think Eric's analysis of the facts is basically right. i.e. the "open source as business" stuff has gotten us a lot of popularity. The danger is that we fall for our own marketing program. That is, new community members join, and we have to say "we didn't really mean that. Really we meant freedom. The business stuff is for the suits." An increasing number of new members just don't understand freedom, or copyright, or anything like that; they joined "Linux," not "GNU."

[0] http://web.archive.org/web/19981206185148/http://www.opensou...

[1] https://web.archive.org/web/20170630183629/http://www.linuxt...

Nadya··on My boundaries as an open source developer
There is a reason FLOSS exists as a term to differentiate itself from OSS and I think the ideological differences between the two are important. So does Bruce Perens, the co-founder of OSI and the author of the Debian Social Contract of which the OSI definition was based off: https://web.archive.org/web/20140716055445/https://lists.deb...

This was back in 1999 - it's been over 20 years and "OSS" has only been muddied further and further to mean "source available" since.

Pedantry aside tremon's response sums it up well: "Feature branch hosted in a separate repository."

Nadya··on My boundaries as an open source developer
Maintaining a fork and maintaining a single feature of a project are two different levels of commitment and you can want to do one without doing the other although all too often people want to contribute a feature and then not provide support for it and expect the project maintainer to now maintain the contributed code. But that's a different issue (and why many maintainers sometimes don't accept random PR's even if the code itself is fine).

> You don't need to push to the original repo because open source allows you to make your fork available to others.

This is simply not true - not all open source software is copyleft. You can have restrictive licensing regarding use and/or distribution and still be open source.

Nadya··on AVIF has landed (2020)
See also: https://news.ycombinator.com/item?id=25706284

Personally I'm trying to push for JXL (for high fidelity) and AVIF (for when lower fidelity is acceptable) adoption at work. With absolutely no success yet but as it matures I'm sure things will turn around.

Nadya··on What's the problem with old but excellent Mac apps?
But you don't actually feel those differences unless you (a) measure it or (b) have such an absurdly large project or file as to actually encounter these problems. Many people aren't working on supermassive/monolothic projects and VS Code works just fine for my little 100-500 lines-per-file projects. I don't really care if it takes 0.0002 seconds instead of 0.00009 seconds because the end result is that it feels instantaneous either way. Sure if my files were 1,000,000 - 5,000,000 lines of code per file and I was working on massive projects the 8 seconds vs 0.004 seconds would begin to make a massive difference. I don't though and so it doesn't matter.

I sped up the RegEx in my application earlier by an astounding 99.92% on average. I run several dozen various RegEx on a string once every few seconds - sometimes even slower. Execution for the end users already _appeared_ near instant and after the improvements it... doesn't feel any faster for the end users. Because the efficiency of my RegEx doesn't really matter at the rate strings are being parsed and for the small size of the strings (<150 characters often in the 30-50 range).

Nadya··on It's always been you, Canvas2D
Same thing with gradients in forum design. The moment we could use CSS instead of a gradient handcrafted with a pirated version of Photoshop - gradients stopped being commonly used in forum skins.
Nadya··on What makes writing more readable?
That excerpt reads to me much like explaining how a guidance system works on a missile: https://www.youtube.com/watch?v=bZe5J8SVCYQ

> The missile knows where it is at all times. It knows this because it knows where it isn't. By subtracting where it is from where it isn't, or where it isn't from where it is (whichever is greater), it obtains a difference, or deviation. The guidance subsystem uses deviations to generate corrective commands to drive the missile from a position where it is to a position where it isn't, and arriving at a position where it wasn't, it now is. Consequently, the position where it is, is now the position that it wasn't, and it follows that the position that it was, is now the position that it isn't.

Very simple words, with 3 or 4 exceptions, but it short-circuits the brain a bit if you aren't following along carefully enough.

Nadya··on Show HN: CSS Speedrun – A small game to test and improve your CSS knowledge
4:22 - I got stuck on the ID one because I felt like I was meant to do something than select each one individually. I also got stuck on :enabled and ended up writing something dumb in retrospect. Some of my selectors were quite hacky in the name of speed though.

It would have been nice to see what the intended solutions after because otherwise I have no way of finding out that using :enabled was the intended way and not input:not(disabled), button:not(disabled). Realized after I could have used an :is there but I don't use :is often in work due to browser support for IE so it didn't cross my mind at the time. It would also be nice to see that #one, #three, #five, #nine (or whatever the ID's where for that puzzle) was indeed the "intended" answer as a kind of trick question.

Without reading HN I would not have learned I was meant to use :enabled.

Nadya··on California moves to recommend delaying algebra to 9th grade statewide
Yes, but often times the army of scientists had already done their work. Even in the late 90's a lot of what I was learning was already known to be false but the updates hadn't yet hit by textbooks published in 1982. The teachers even sometimes already knew it to be wrong but had to teach it anyway because it was still considered part of the state curriculum. But the more common and larger issue was the partial truths/mostly lies - even if some of the lies are arguably justified to make learning easier for some kids. The better teachers wouldn't lie but would simply say "You'll be taught about that later in a higher grade".
← PreviousPage 5 of 34Next →