This article is also pretty interesting: https://www.frontiersin.org/articles/10.3389/fpsyg.2022.9555...

Not really. It also supports keeping the symmetric decryption key encrypted with the GPG key of each added user (and handles this automatically). This is the default behavior.

What you're saying also works (quoting from readme, emphasis mine: "Alternatively, you can export a symmetric secret key, which you must securely convey to collaborators."), but feels worse from a security point of view.

I'm not taking Sonos' part here though: like other people here pointed out, I'm pretty sure they patented some very obvious things which they should imo never have gotten a patent for in the first place.

edited to add this link for reference: https://www.androidpolice.com/2020/12/10/the-forced-switch-t...

Lies, damn lies and benchmarks? I don't believe that for a second.

shouldn't that read "...Chrome's default search engine"?

Comments URL: https://news.ycombinator.com/item?id=21905521

Points: 1

# Comments: 0

Anyway, I'm sure there are some compilation phases that won't benefit from more cores, but the bulk of the compilation seems to do so. Even though Elixir has incremental compilation, due to use of metaprogramming in the Phoenix framework sometimes even changes to a single file will trigger recompilation of hundreds of others, so I was thinking these new AMD CPUs with lots of cores could be very helpful here.

On the project I currently work on the codebase is _littered_ with workarounds and hacks to get stuff to work on Safari.