This is less about the practicalities of "what currency are they charging me?", which is rarely if ever a legitimate concern of a customer. This relates more to the presentation of the menu itself, where excluding the dollar sign is something posh restaurants do, and many others imitate. As for why they do so, I don't know of a reason beyond the appeal of minimalism

A teacher read us this book in elementary school and I've unsuccessfully been trying to track this book for years. Such an interesting way to think about the world around us, how it will be perceived, and the degree to which we cannot be sure of the accuracy of our perceptions of the past.

Here ya go: https://www.amazon.com/Motel-Mysteries-David-Macaulay/dp/039...

David Macaulay's illustrations are fantastic.

His books and TV series have been a nice part of this years home school curriculum. Roman City is my favorite.

My favorite will always be "Unbuilding"

High fees and lack of a fiat on ramp are two big reasons

Only that it would have been way more profitable

Not completely mistaken, I think you're confusing blurring with "blending", where pixels are displaced in tight irregular spirals. These images have been successfully unscrambled as part of criminal investigations into child exploitation cases.

Something like consumer trust only makes sense if compared relatively to competitors, otherwise you're making a statement about the general public rather than about Amazon.

Networked applications like this really expose the real money drain in AWS and other cloud services, network charges particularly network egress rates.

This is also how it works in Clojurescript (through Reagent/Re-frame). I don't have too much JS react experience, but I often read this kind of article and marvel at how huge the mental load is working on react projects in native JS.

You use a global db atom in re-frame for global state, but there's nothing stopping you from using a reagent atom local to a component, is there?

I never thought of the existence of the global db as the thing that ALL state should go in., or is that a community best practice?

Edit: after digging through the re-frame docs themselves, you can see here that local reagent atoms are used for local state even with the global app db: https://github.com/day8/re-frame/blob/69a3fcd411369fff65404e...

> estimating hacker provenance consists purely of modifiable and/or spoofable circumstantial evidence, including IP addresses, malware signature, and possibly timestamps/localizations within the binaries.

There's more to it than that, and often attribution is the result of the "bigger picture" of multiple clues, rather than a single smoking gun. Group operations develop patterns over time that are much greater than just a timestamp somewhere. Also, identifying a 0-day exploit somewhere often allows you to discover previous deployments of the same exploit, which have their own blast radius of evidence, contributing to these patterns that are identified over time.

>but surely a competent hacker could pull of a hack and trivially modify the evidence to implicate any nation/state who's modus operandi are known in hacking circles, no?

>Deliberately engineering your attack to mimic one from another group is an excellent way to keep people off your trail...

Yes, misdirection is the name of the game here, all bets are off and nothing is off limits. But covering your tracks leaves tracks of its own, and again, even when an attacker thinks all their bases are covered, they will never be sure there wasn't something somewhere they left behind that points back to them.

> and these are hackers we're talking about, after all.

Who do you think "hacker-hunters" are, if not hackers themselves?

It doesn't mean you shouldn't, either. There's nuance to every situation, particularly when we're discussing the means by which some people quite literally survive, vs. luxury or leisure goods and services.