I've also use Keepass[0] for what feels like nearly a decade at this point. I use google Drive or just very dumb shuffling of files to get the database where I need it.
I keep feeling like I should upgrade to something with better native support... but it's worked for me so long and still fits my workflow.
> I was recently out for a walk when I saw a small package fall off a truck ahead of me. As I got closer, the dull enterprise typeface slowly came into focus: Cellebrite.
While I'm skeptical of the method of acquisition, would be interesting if they actually got the hardware and could publish details.
Update : other news outlets reporting with more details, but not confirmation [0]
I've never heard of micro.blog before now, but after reading the article, I'm still not sure what the "problem" is.
I read three major points: Ownership, curation, and diversity. As the latter two, I feel, require hands-on experience, I'll focus on the first.
For Ownership, the author / OP appear to suggest that content ownership is about where the content is hosted. From the article (again, never heard of the service before now), it seems that preserving redirects and letting you create whatever URIs you want, and therefore move / control content, would suffice. Am I just missing something?
Meltdown doesn't _directly_ allow modification of code. However, a guest VM could run userspace code that accesses ring 0 / kernel memory of the hypervisor / physical machine.
This would mean that security certificates, passwords, etc of the hypervisor could be exposed, which could then allow compromise.
I keep feeling like I should upgrade to something with better native support... but it's worked for me so long and still fits my workflow.
[0]https://keepass.info/