> To be very honest here, you risk having KeePassXC blocked by relying parties

This threat, because someone dared to give users control, is completely unacceptable to me.

I believe this refers to switching to high-efficiency electric heaters like reverse-cycle AC units (also known as "heat pumps"), rather than oil heaters or ducted gas heating.

The version taught in Australian first aid classes is DRSABCD: check for (D)anger, check for patient (R)esponse, (S)end for help, (A)irway, (B)reathing, (C)irculation.

†Untrustworthy, because it will either double down on its own output in its context, or will flip-flop to whatever the user said .

> In addition, charging an exchange fee would allow the central bank to implement negative interest rates, if deemed necessary. The central bank could also impose a conversion limit per customer for AML/CFT (“cash” limits) or financial stability reasons (to prevent hoarding or bank runs), if desired.

Well goody.

The idea of blind signatures is cool, as is the fact that the merchant doesn't need to identify the customer, as is the fact that you could deploy neat local currencies with something like this, but AFAIK you still can't give 20€ to your friend without the exchange knowing and approving, or it becoming a race to see who spends the tokens corresponding to the 20€. And that's not very privacy-preserving.

Also, the font used for the monospace examples in the post is a great kick to the nostalgia. Which one is it? It reminds me of https://int10h.org/oldschool-pc-fonts/fontlist/font?ibm_vga_...

    make :: forall symbol -> (IsNonEmptySymbol symbol) => NonEmptyText

    type family IsNonEmptySymbol symbol :: Constraint where
      IsNonEmptySymbol "" = Unsatisfiable (Text "Expected a non-empty string")
      IsNonEmptySymbol _ = (()::Constraint) -- empty constraint is always satisfied

The big problem preventing this approach from working for numbers is that it's just so cumbersome there. Most of this is because all the arithmetic operators are bundled into a single Num typeclass, and `fromInteger :: Num a => Integer -> a` has a type that's impossible for a "non-zero number" wrapper to satisfy.

https://www.apple.com/legal/warranty/docs/statutory_warranty... (Page 2):

> Without limiting consumers rights, Apple will provide its own remedies equivalent to those remedies in the consumer guarantee provisions of the Australian Consumer Law at any time within 24 months of the date of purchase. For the avoidance of doubt, Apple acknowledges that the Australian Consumer Law may provide for remedies beyond 24 months for a number of its products.