It is hard to have much sympathy for someone who complains about seeing a Git commit they never made but presumably clicked "publish" for a blog post that says "a North Korea-aligned group who targets software developers specifically. Not banks. Not hospitals. Devs." Supply chain security is a huge concern nowadays, and JavaScript in config/build-chain files is a sadly long-lived threat vector against a supply chain.
You are a programmer who is all-in on LLM code generation. You get so much written every day! Hundreds of thousand lines of code, and you barely lifted a finger. But... your LLMs are trained on the entirety of Github.
How many repos on there are full of trojans and viruses? How do you know that your super-productive LLM isn't copying those instead of the canonical version of whatever frameworks it's building?
One day you find one. You write a blog post about it. Or, rather, the vague outline of a post. You make an LLM flesh it out, of course. You barely lift a finger.
"I want to be honest about something..." This definitely reads like SLOP. It has got all those unmistakable formulations, patterning of certain phrases and lead in sentences. The signatures of slop.
Before we started doing it this way, the threads would fill up with far more off-topic comments ("why is this 3 day old post on the frontpage?" and so on). That was a much bigger problem. Relativizing the timestamps to reflect the re-up time was our attempt to address that. Overall, it has worked ok—that is, while it does still lead to offtopic confusion and complaints in the threads (boo) there is far less of it than there was before (yay).
I'm open to suggestions of how to do it better! But you also need to consider the cost of adding explicit details to the UI. If we did that every time something like this came up, HN would have become an unreadable mess a long time ago.
I guarantee you've thought more about this than I have, but the first impression I had of the "second chance" pool was that it would essentially be a repost of the top-level post and not the comment threads. I think part of the reason people bring it up is because they see the same post PLUS the same comments with new timestamps and feel disoriented.
maybe just adding something like (revived) to the timestamp, or a [?] link that explains what happened to the date? If you want to avoid adding info to the ui it will inevitably create confusion
That's the status quo ante, which didn't work, plus a UI element which most people wouldn't understand. My guess is this would lead to even more offtopicness.
There have been almost zero visible changes to the HN codebase in over a decade, but the one thing I would love to see them add is a little flag on the heading of the post to say it is 2nd Chance Pool to avoid all these comments every time this happens and everyone is confused :)
Not possible, but it would be possible to reimplement Quake's logic and controls in CSS to have it run without JS. I was considering doing that for my next CSS crime project, though now that CSSQuake has hit the hn frontpage there is little point in doing so.
You cannot close HTML tags that way anyways, <br> and <br/> are the same, as are <div> and <div/>. The spec defines whether an element self-closes, the slash is just ignored.
not only do i think doom in css is possible, but both me and another css person were also planning on actually making it into reality
but it sort of feels demotivating to see js-powered css projects like this hit the frontpage, because if we do eventually make a css-only doom people will think its a repost or nothing special
edit: and to be clear, that demotivation is more of a problem of how the internet, virality, and news cycles work. the actual project here is still pretty cool!
the difference is that knowing 2^8 is generally not useful to people who don't know it
this here is something that's pretty useful to most ssh users, yet seldom spoken of
a better analogy would be comparing it to calling a very good, but not well-known restaurant a secret place - using the word to mean a hidden gem rather than an intentionally hidden secret
