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.

[0]https://keepass.info/

For Direct Connect, they still charge for egress.

> For Direct Connect, they still charge for egress.

They do for both Snowball and Direct Connect, but it's 2 cents per GB, which is what I used to give the 3k estimate.

> 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]

[0] https://arstechnica.com/information-technology/2021/04/in-ep...

It's a tongue-in-cheek English saying which implies that the item was stolen.

I long for the day when security is the default state. I wonder if legislation could help address the never ending stream of things like this.

How bizarre. I wonder how heavily the micro-tasked and bot-driven fake-reviews will factor into (now) literal product placement?

Again, I haven't heard of this place before, but from the article, it appears like they offer that through control of domain names?

Certainly there's an argument about the manually-curated feed, but don't know if that's what you're talking about?

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?

The model is exactly as you say. The whole idea is to be sort of like Wordpress.com. Pay for hosting if you want it, but if you just want to participate in a social layer on top of your own RSS feed, all of the social features are free and you just import an RSS feed.

If you leave micro.blog hosting, you can just submit your new RSS feed wherever you're hosting the same content and it'll be pretty seamless, I think.

Curation and diversity, in this post, feel like expressing the same problem in some ways-- too few people with insufficient diversity are currently using the service. Curation _may_ fail at scale the way they are doing it, but we don't know that. And if the diversity isn't there to curate, I'm not surprised curation hasn't surfaced diversity. But micro.blog is super young. Maybe it'll be a useful social place, maybe not. For me, it's a pretty good blog host right now.

I also didn't know anything about micro.blog before now, but based on the article I assumed from the features offered that "creators own the content" actually means "creators own the relationship with the user" which seems pretty important. Worst case you could copy-and-paste your content to a different service, as long as you own the domain.

Same here, never heard of micro.blog but the concept and business model seem sound.

Owning the things you post and having to host them yourself are two different things. The content is yours, the domains is yours, you pay for someone serving it for you. Hosting is not free and maintaining it is always a hassle a lot of savvy people will pay for a service in order to avoid.

Micro.blog seems to be open source, if at some point you don't want to pay any more, you can always get your data out, setup a server or a rpi, and restore your data. Nothing lost other than some quality time with some readmes.

While I agree with the spirit of what you’re saying, micro.blog is not open source.

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 would also assume this means exploits on a machine provisioned with multiple VMs from different customers would allow a malicious customer to leak data from another customer's VM located on the same machine.

I have a bunch of unused CPU time on my virtualization cluster. I wonder how the power delta for full-utilization would work with the pay...