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

interesting, YouTube channel Veritasium just published a video on how Enigma was broken during WWII. at the very end they also give message that has yet to be decoded, although apparently they're different.

https://www.youtube.com/watch?v=JsBZOcqZerk


WRT the timing, Veritasium maybe looked at the last few weeks and decided there's a fast-closing window in which to report on any famous messages yet to be solved.

It is a private equity channel, so this is surely the reason. They have a team whose job is finding the most engaging content topics.

I just finished watching that video, and thought to myself "I'm sure someone else with Chat GPT tokens to burn has already done that"

And then I come to hackernews and well, not quite, but I'm sure that one will be done shortly too.


Maybe both watched Tom Scott a month ago about Bletchley Park?

"not an expert in zig" but you can't even look at the documentation to find the `@tagName` builtin to do exactly the problem posed?: https://ziglang.org/documentation/0.16.0/#tagName

i can literally google "zig enum to string" and the first result is a reddit post where the given solution is `@tagName`. i'm ready to write this post off as a low-effort ad for C3


Agree, the post was extremely low effort.

from en.action.md:

> Redirect or block "Cloudflare Warp" users from accessing your website. And provide a reason if you can.

come on, really? what does this achieve? only thing i can think of is trying to get the user off of WARP, but i can pretty confidently say that before doing that i'll just not use the website. or if i really care about the content i'll turn it off until i'm done and back on it goes


Tangentially related, the archive.is / archive.today / etc site host used to block anyone using 1.1.1.1 DNS because 1.1.1.1 doesn't send an eDNS subnet to the authoritative DNS server. It accomplishes nothing except annoying actual users.

just sort of a general complaint about how much the internet relies on cloudflare and what that means. massive point of failure, erratic browser checks & outright blocking, surveillance

seemingly hugged, unless they're doing overzealous IP blocking

There's also an alert on the MIT emergency page, though it doesn't mention the substance by name: https://emergency.mit.net/


Latest update reads in part:

"Emerging information calls into question whether this compound was in fact synthesized. We are also able to disclose, with the student’s permission, that while the student remains under medical supervision, their initial blood test result, which was received today, shows no sign of exposure to mercury."


can people publish blog posts (and other things) literally anywhere else? especially now with nitter/xcancel/etc getting taken down


Seriously, posting to the same site owned by the Creator of DOGE, who is ethically responsible for mass death now and future deaths too.

Using the site supports him and his efforts.


nitrotype?


that seems unrelated to the security problem to me


once again, i will ask: why do people care so much about only having one
element open at a time? let me see what i want to see!


Yes, absolutely, and UX experts such as those at the Nielsen-Norman group have for years been advising against auto-closing the already-opened options when opening another. For good reason - user frustration in their research.

If I clicked it to open it, then if I want to close it, I'll click it again. Don't hide content I might still be reading!


When a form has two sets of mutually exclusive options it might be appropriate? But I find the user experience confusing. It's hard to tell what happened when all the elements moved around, at least without animations.


Skimming/scanning. For a couple of items, it is not an issue, but say for a long list of FAQ, being able to scroll past fast is nice.


but then just close the elements yourself if you need that? don't force one behavior onto everyone


Most people are lazy, so it is designed for most, including myself.


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

Search: