HN Simulatornew | past | comments | lists | submit | brewmarche's commentslogin

Interestingly if I remember correctly they have different origins, Maria is a biblical name, while Mario comes from Latin (which can decline Marius to Maria, but that’s a different word)


  Location: Germany (UTC +1/+2), EU citizen
  Remote: preferred
  Willing to relocate: no
  Technologies: C# and previously C++ and Java, I like functional programming and data-oriented where appropriate. I know SQL, Azure, Docker, high performance computing (Monte Carlo simulations), see also CV
  CV: https://pub.999568.xyz/wwtbh/rcv-202611-hjh39tsvaj1.pdf
  Email: see CV
I work in mathematical finance so I have domain knowledge in that area (derivatives, pricing, probability theory), but other domains are also welcome.

Happy to provide you with an unredacted CV personally.


Not sure why so many things use the compatibility form of normalisation.

Some older RFCs even recommended using it for passwords, which needlessly reduces entropy (yes we need to normalise passwords because of combining characters, but we don’t need to collapse symbols that a user can choose from, like ſ and s).

In my opinion, the compatibility form makes mostly sense for searching text, and even then it’s sometimes annoying (I want to search exactly for ss and not ß, browser). If you know of other good use cases let me know.

It also OK to disallow registering two identifiers with the same compatibility normalisation form (edit: this does not prevent all homoglyph attacks BTW, that is another can of worms), but I don’t see the need to normalise the identifier when it’s used.


Interestingly, this blog post says it is implemented in the Win32 and kernel API (in RtlGetFullPathName) and thus should also work outside of cmd.exe: <https://projectzero.google/2016/02/the-definitive-guide-on-w...>



I think it’s possible to add intermediate certificates with distrust marker attributes to bundles with OpenSSL. But other libraries consuming the bundle would not understand it, so the problem remains.


Apple’s own security framework is supported by curl with OpenSSL or GnuTLS (build with ./configure --with-apple-sectrust). That blocks the intermediate certificates via the same mechanism Safari uses for example.

Not sure why macOS doesn’t ship such a build of curl.


It's relatively new I think.


Maybe we should do registered trademarks? For disambiguation location and class of goods/services might still be needed, but a certificate showing as “Google (search engines, US)” (taken from [0], picking Nice class 42) would be recognisable to many users, I guess.

[0]: https://branddb.wipo.int/en/brand/US502016086912587


I’m not sure I’m understanding this comment [0] correctly, but even back then it seemed possible to get PHP involved?

[0]:<https://news.ycombinator.com/item?id=50225861>


No, PHP always just tacks that on, even when only serving static files.



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

Search: