471 karma · joined July 24, 2024
Except, it makes the user experience worse: I can certainly make it infinitely more tedious to open the document exchange site of $superimportantcompany on superimportantcompany.co (or was it .com? or .co.uk? or important-company-le.ai?), and spread out "my" inbox across 30 different sites and spend additional time navigating their unique interfaces to not just read, but also add each document into the appropriate local archive. But what have I gained in making it more likely that each correspondence is kept confidential between the only parties that should read it? Nothing beyond what I started with. Could have stayed with email, no?
I can see the appeal of mitigating part of the usability problem by pivoting straight to bundling up all thematically related messages into centralized repositories to limit the number of pseudo-mailboxes one has to maintain simultaneously, as done in the recent "everything medical related" cases. But someone would grab a full copy in the inevitable compromise, and that is a risk that should rather stay scoped to smaller groups of senders and/or recipients. It seems like a bad tradeoff to force every blood test of everyone into the danger zone for that, given that one could have instead spent 3% of the budget on.. merely policing away the DNS warts in public authorities (or, in the medical example, insurance companies) while keeping data custody unchanged.
(The way I know it: Local court or police officer shows up at our office later that day and hands over a printout matching the request that we had been unable to confirm, on request of federal authority, in turn on request of the authority demanding we hand over some customers data. Those two requests utilizing government agency-internal auth mechanisms we do not need to know or care about.)
If you can afford to keep fines in litigation/appeals/formal-defect limbo for a sufficient number of years, you can grow out of even once-threatening fines and delay compliance until the law that you finally bow down to is so old that its signs of old age will in the meantime become popular arguments for undermining or retracting it.
SCT is not contingent on EU or Euro participation - SEPA membership is distinct from those. That is how Iceland, Norway and Switzerland can reap the benefits (the latter not even EEA member, though effective treaties are now somewhat similar). As long as an US bank has a correspondent branch/account/partnership/whatever inside SEPA, they can make it almost free to receive money via SEPA, and then possibly still save on currency conversion and transaction cost as they clear in bulk across the pond.
You're missing out! Try a few of the apple varieties that are not available year-rounds, that are not optimized for insecticide compatibility and tons per square kilometer (well, more likely bathtubs per football fields or something). Yes, even and especially the small & ugly ones that never ever have that flawless smooth skin that makes you wonder which ones are plastic props and which ones are fresh fruits. After dumbing down the basic supermarket apples to just a few that look presentable and can be made to work in a wide range of climates, it has lost the refined tastes of most of the other varieties they out-priced.
Unless providers do insane things (e.g. accept then discard), it is much safer than snail mail, where messages may not arrive and not cause the sender to be notified of non-delivery either. With email, the sender gets explicit per-recipient-and-message feedback on what the recipient provider has accepted responsibility (to not lose them) for.
.. incidentally, OpenBSD also provides one of the clearest examples of how the excuse "calling system() is fine in my case, its totally not arbitrary user input" is deluded just the same, see CVE-2020-8794.
Sounds risky, unless paired with strong policy about what a verifier should do. e.g. if the verifier just grants network access to the buildbot that then checks what the result should look like, then compromise could remain invisible while the label silently downgrade to "independently downloaded by". And I do not expect there are many parties that would be willing to provide such service beyond their own needs, while simultaneously not already providing that service in places where the infrastructure and policies are already set (such as Debian). Or at least they would already contribute towards build dependencies that do not break reproducibility on every other version bump.
That way you would be forced to keep it personal.. or suffer reduced sale price, as the new owner would need to backpay the minimums you were exempt from, or take on some risk merely leasing from you until the lock eventually expires - as you remain the true owner and all the payments and paperwork must cross your desk.