Hacker News new | past | comments | ask | show | jobs | submit | qqii's comments login

I'd argue that false data doesn't achieve this, it just confuses everything. Using an analogy in programming terms, it would be like `job_title <- Maybe "NULL"` whereas they really ment `job_title <- Nothing`.


I do agree with this. If they stick with this policy it would be better if they use some unambiguous title like “Former Employee”.


Exactly, or expulge and refuse to provide job titles? That begs the question, why do they provide this information to third parties anyway?


If it is for secrecy then why not delete the information and inform those who ask they do not hold such information? The issue was the discrepancy when a third party tried to verify, and I'm sure third parties would quickly learn to work around the fact?

Instead making everyone associates is like an error propagating far from it's call site until an exception (this article) is raised.


There is a follow up, where he get another popup: https://nitter.42l.fr/linusgsebastian/status/148185562555858...


> Challenge: How would you go about writing a function that reverses a string while leaving symbols encoded as sequences of code points intact? Can you do it from scratch? Is there a package available in your language that can do it for you? How did that package solve the problem?

So are there any good libraries that can deal with code points that are merged together into a single pictographic and reverse them "as expected"?


If you're using Python, check out grapheme: https://github.com/alvinlindstam/grapheme


From the threat it looks like Linus' threat model for git is simply different from the common use today. Of course a judgement under a different threat model would make it seem like a bad tradeoff!


It's more that Linus:

1. Didn't understand the attack

2. Doesn't understand security

3. Doesn't care

He's shown this repeatedly for decades.


There's no reason you cannot construct a token that can be frozen and reversed - USDT (other issues as side) being an example. Accounts as we know them don't have to be at the level of public address-private key but rather a smart contract as seen by Loopring.

The difference is what was centralised is now decentralised, what was implicit and required trust is now explicit and requires formal verification.


USDC has a blacklist feature too. I don't think funds are reversed though, just frozen (my rough understanding)


I find it very strange that this HN thread is full of people taking the website name hyper literally.

The about page mentions that this is a UI for the subreddit of the same name, which is focused on "Post quirky and niche words/phrases from foreign languages that can't easily be translated."

Personally the discussion for possible translations is far more interesting than the slightly misleading subreddit and site name.


Having seen the English translations for my native tongue a lot of these translations are only surface level and quite lossy.

Even if the mapping between languages is surjective, certain ideas and phrases are difficult to translate whilst maintaining the succinctness of dialogue and are practically difficult to translate.

Considering translatability as a spectrum obviously "does not translate" is a hyperbole, and shouldn't be taken literally at face value. Hopefully you'd agree that most words on this list are at least on the difficult end of the spectrum.


Having checked my own language I'd describe the list not as being unable to translated outright, but of susinct ideas that are not normally expressed in English.

A literal or detailed and contextful translation does not express the same "feeling" as in the native tongue, which you could argue as a what is impossible to translate.


Also, taking the website name literally leads to a very boring time. If we define translatable as having a surjection between languages then many commenters have shown examples of even the most difficult to translate phrases explained in a blog or article.

Instead the subreddit's description[0] is a far better description, and the discussion on each phrase about possible translations or similar ideas in different languages is a lot of fun!

[0]: Post quirky and niche words/phrases from foreign languages that can't easily be translated.



Thank you.


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

Search: