MD87
That would actually fix some ugly CSS I have. The demo works. Neat.
Except... the demo doesn't use either the old syntax or the new syntax. The browser support is wrong (Firefox doesn't support it, the site says Firefox 16+; it says Chrome 43+ but in reality it's much newer: Chrome 148+). It says "Since 2018" but the spec was introduced in 2024.
So maybe an interesting overview of things that might be available or might not, but the filtering and data on the site doesn't seem to be useful.
> ... licensed to use source code to create compiled versions ...
Why's it calling out compiling specifically? Are they trying to imply you can't modify/distribute/etc the source? Presumably that would be a "further restriction" per the AGPL and hence ignorable, but it's sloppy at best and misleading at worse, which isn't great for a license document...
The entire "Gradual recovery" part of the post makes absolutely no sense, and is presumably an LLM fabrication. That's just... not how anything works. And deploying three different weird little mitigations flies in the face of the earlier "We couldn't just restart production. Too many active users."
We trust strangers' open source more than our colleagues'
Nothing specifies what a binary called `sl` does. The user didn't "overwrite" anything. They just had an `sl` binary that was not the `sl` binary Jest expects. Arguably they had the more commonly known binary with that name.
e.g. https://bsky.app/profile/did:plc:dbipwza2663x6hfp2purbn7i/fe...
I also found the scoreboards surprising. I wouldn't expect a Gameboy-like device to be reporting things back to a server. I don't have any particular privacy concerns about it myself, but it is surprising, and I can see why people might object.
It also seems to contradict their privacy policy (https://panic.com/privacy/):
Panic apps and products _do not_ send out _any_ private information. This includes
...
Usernames
...
But the scoreboard API seems like it's tied to usernames...Yes, with some more varied clues I can see how it could be very fun. Maybe an extra type of clue could be associating suspects with potential murder weapons (e.g. "Alice said she never touched the rope" or "Forensic testing found traces of Bob's DNA on the poison bottle").
Or maybe another type could be like: "Alice heard someone in the bedroom when she was in the kitchen at 09:30". In the right circumstances that could give you _just_ enough information to deduce something.
I'm looking forward to see where you take it! :)
> However, it's important to note that every clue you view will have an impact on your overall score. Exercise caution and strategic thinking as you navigate through the evidence and interrogate the suspects to piece together the ultimate solution.
That sounds great! But what actually happened was I clicked through clue after clue about person X being in room Y at time Z until I eventually got told what the murder weapon wasn't three times in a row. I didn't feel like I could exercise any caution or strategic thinking; it was just "Nope, this isn't enough information" over and over until "Yes, this is now enough information".
At the point where I thought I had enough information, I realised I hadn't been consistent in how exactly I was using the notebook: does a tick in the "9:15" box means "They entered at 9:15" or "They left at 9:15"? The boxes really need to correspond to the times they're in the rooms, rather than the instants they move between (so either labelled with a range: 9:00-9:15, 9:15-9:30, or move the labels so they sit in the gaps in between).
Also the "How to Play" link isn't openable in a new tab (because it's handled by javascript), and if you open it normally and go back to the main page you lose all your progress
Midday and midnight are the points at which AM/PM change and you can't logically differentiate them by appending AM or PM. You just have to know the arbitrary cultural convention that midday is PM.
I'm sure these are just oversights but it leaves a very bad taste in my mouth!
Buildah from Red Hat has an argument to set this programmatically instead of using the current date, but AFAIK there's no way to do that with plain old docker build.
TypeError: e is null
P App.tsx:36
React 2
Fn App.tsx:31A new way of blogging about Golang
"Fraud by false representation" happens when someone dishonestly makes a false representation with the intent to make a gain for themselves or another. Making up a news story to flip NFTs would almost certainly amount to a crime of fraud by false representation.
Learning something tends to be a gradual uphill climb: through practice and repetition you slowly become better. There are very few inherent concrete goals or thresholds, and it's generally fairly difficult to notice yourself improving because it takes place over a longer time period.
I struggle with perfectionism, which means while I enjoy learning I'm never hugely satisfied with the outcome. You can always bake a better cake, write better code, or whatever. But when you get that 'ding' of an achievement there's nothing even the most annoying bit of my head can argue about: I did the thing; there's no way to improve on it further. Annoyingly, that's far more satisfying for me.