6,820 karma · joined January 7, 2015
Also working on a surveillance machine should have a proven system of values to be aware where boundaries are being overstepped ... Oh wait, maybe that's the point.
A Mail, even with just a subject takes a lot more space and leads somebody to answer to it which messes up the thread.
The big new power lines are needed to get electricity from offshore Windparks in the Northern and Baltic Sea to industrial zones south. The conflicts are with villagers in probably nice but not as special areas as the Alps.
By default it directly runs code as part of the download.
By isolation there is at least a chance to do some form of review/inspection
Then there are ideological reasons: Purposly trying to make the open source version sustainable.
And then reduced lockin etc. by not using Enterprise only features by accident/convenience, which leaves the door open to leave the contract.
I can share clipboard contentents, can send files, send web page urls from phone to desktop to open a browser there, can control media playback between devices (switch to next track/pause desktop from phone and vice versa) etc also I get phone notifications on desktop
(All optional)
Binary size however is less of an issue for most users.
It can make sense if you have very differing load, with few notable spikes or on an all in on managed services, where serverless things are event collectors from other services ("new file in object store" - trigger function to update some index)
As example: my late grandfather of 100 years took records of his stamp collection in Excel. He used the computer for Wikipedia as well, but we didn't upgrade ist as he was comfortable, but upgrading to later Windows to ruin newer browser would have been too much of a change and rather made him stop doing what brought him fun. The router etc blocked worst places frequent backups allowed restore, thus actual risk low.
Anecdote aside: there are tons of those machines all over.
And then another big one: bots claiming to be something which they aren't.
(And then two more, Deutschlandradio and Deutsche Welle)
(*) From state's perspective there is still a problem: tax audits, bad if everybody avoids them by "accidental" data loss
Alternative is some generic phishing with a complete fake invoice, which somebody assumed to be true.
Now if it is serious and an invoice was changed (independently from transport considerations) that alone is quite some effort: the original message has to be held back and analyzed, then it has to be manipulated (replaced) and then the message has to be sent on.
If you get to that level of sophistication it's a lot more likely the source was hacked.
There are a few other scenarios, like invoice being sent wrongly and some random person manipulating it before sending on, but if you aren't prepared by having a bank account for that purpose it's quite a risky thing to do. My private account can be traced to me ...
Well, E-Mail is inherently async and allows a sequence of relays with no back channel to confirm delivery.
With other protocols (except snail mail) I get a confirmation that recipient was valid and the message for delivered. With some I even get a marker it was read.
With e-mail, with luck, I get a cryptic not standardized response mail, if something went wrong. Sometimes even only a lot later as delivery is retried for a few days in some cases.
That's true for some forms of communication, but for social chitchat in an ongoing conversation there isn't much relevance.
Subject becomes especially ridiculous when Mail clients are localized and you get some "Re: AW: RE: Re: AW: fun stuff" as subject.
At work subject tis key. Allows me to ignore 90% of the mails immediately.
That sounds like a quite sophisticated attack. By far most Mail these days should be transport encrypted. The attacker thus must have control (legal or illegal, at least to fake a wrong MX DNS record) over either side and then manipulate the invoice and then need a bank account which can receive the payment, while hiding their traces. Seems quite sophisticated and targeted as an attack.
> Nobody uses GPG, sadly.
User experience there was never good. Signal/WhatsApp probably are the most userfiendly e2ee systems around: automatic key exchange with ability to verify. (While proprietary clients require trusting those, which is a big ask especially with Whatsapp/meta)
Doing this in a digital system requires first some computing device (be it phone or laptop or whatever) then check the account value, read it correctly, then do some arithmetics and then interpret the result. That's a year or two older.
However it isn't trivial. First problem coming to my mind:
module a importing first somelib>=1.2.0 and then b and b then requiring somelib>1.2.1 and both being available, will it be the same or will I have a mess from combining?