Here is my use-case for a trustless architecture: there are parts of my families digital life which I would prefer to continue working as much as possible, even if I'm temporarily or permanently unavailable. "Pay this amount of money monthly/yearly for this to keep working" is a straight forward concept for 99.999% of the population. "Poke around in docker debugging logs if this stuff stuff" is not.
And, if stuff has to be hosted by third parties for me, I prefer it to be encrypted.
Who knows what the problem could be - if you want to invest time into this, you could try collecting some debug logs to see if it indicates anything. For me and my family it works pretty well (~300G of data across 10s of thousands of photos / videos). Face recognition / AI search works reasonably well. It's not perfect, but I'm happy to keep our photos under our control rather with some big tech company which could decide on a whim to erase all of my data (or even worse, report me to the police and then erase all of my data).
Of course I also dump all of the data about once per week on a NAS, just in case :)
I also worked with japanese, including on site in Tokyo and quickly learned that asking "did you understand it?" is useless. I always had to keep in mind to ask "what did you understand?".
Cool project, but seems to be abandoned. At one point I was a subscriber to their premium version, but then started getting spam to the (unique) email address I used for the subscription. I emailed them to warn that their account database might be compromised but never heard back from them (this was back in '22).
Also, back then, their map tiles loading had a very high failure rate when loading, so I wrote a custom caching proxy to make it tolerable (which had built-in retry and also cached any successful response for a very long time).
No, he was an old man who cared for his wife with dementia until his death, an experience which changed him. And thus he has chosen to go on his own accord.
Spectre was shown to be exploitable from Javascipt: https://www.zdnet.com/article/google-this-spectre-proof-of-c... - making the bet that this won't be shown the same is not a safe wager I would say :) (especially that Javascript also includes stuff like WebAssembly).
To clarify: the PSF did not lose $1.8m on PyCon. It spent $1.8m and made most of that money back in revenue from the event.
Most years the cost is fully covered by tickets and sponsors and the event makes a profit.
When PyCon runs at a loss it’s generally a sponsorship problem. The tech industry has seen a lot of layoffs recently, and companies that sponsor large conferences are often doing so for recruiting. If a company is laying people off they are likely to drop their sponsorship budget.
And, if stuff has to be hosted by third parties for me, I prefer it to be encrypted.