Radioactive Butthole

If the keys have been lost then so has Satoshi. Otherwise any random idiot can say they’re satoshi. Sucks to suck.

Then it would be trivial to sign a message using his known wallet address that could be cryptographicly verified. But he is lying so he can’t.

I don’t think it will be that fast but yes I think there will be no other outcome.

Thank god

That’s kind of my point though. For being made specifically for the purpose of being machine readable, its kind of a pain in the ass to work with.

I want a command line utility where I can just

xmlquery --query 'some/query' --file foo.xml --output foo-out.xml

or in python

import xml

with open("foo.xml", "r") as file:
    data = xml.load(file.read())

That’s the amount of effort I want to put into parsing a data storage format.

Meh. I just wish XML was easier to parse. I have to shuttle a lot of XML data back and forth. As far as I can tell, the only way to query the data is to download a whole engine to run a special query language, and that doesn’t really integrate into any of my workflows. JSON retains the hierarchy and is trivially parsed in almost any programming language. I bet a JSON file containing the exact same data would be much smaller also, since you don’t list each tag twice.

That will pay for like an hour. The dude is screwed.

Training an AI to kill humans on sight is a horrifying prospect

I was talking to my cousin (journalist) a while ago and she told me how she was supposed to interview a whistleblower for Anaheim PD. I snarkily commented something like, “yeah but let me guess he shot himself twice in the back of the head” and she alarmingly said “…yeah, how did you know?”

kbin died?

Felony slander of a corporation charges inc.

I’d donate to his OF 🥵

deleted by creator

Almost all of those are for the database release, not the production release.

Even if they are for the current production release was last April. Considering the buggy mess their product is, that’s kind of unacceptable for an app that is supposed to hold your entire lifes data.

Brother delet this

The selling point is that it is immutable, not that it uses snaps (which it does). Fedora does the same thing with Silverblue and IoT. You don’t install rpms, you install flatpaks. You can install rpms, but you’re not really meant to.

Since Canonical refuses to get onboard with flatpak (for now) they use snaps instead of debs, but snaps aren’t the direct appeal.

The whole idea is that you have a core system in a known configuration. Updating the system just means using a different image. If an update fails, then you just roll back to the last good configuration. Bazzite uses this to nice effect too.

There are a lot of advantages to end users and enterprise admins with systems in this configuration.

As best I can tell, no such thing happened. Feel free to provide some credible sources to back that up though.

Can’t put the genie back in the bottle. Would probably be a different story if China released this years ago.

https://discuss.logseq.com/t/why-the-database-version-and-how-its-going/26744

I get it. And I don’t necessarily disagree with them, but it gives me concerns over the long term viability of the project. If obsidian did blocks the same way logseq did I’d probably jump ship and use that, but you can’t really brain dump in obsidian the same way you can in logseq.

There’s lots of examples. Mir, Unity, Snap, PPAs, and more.

I think Ubuntu Core is a bad example. Immutable distros is where the industry is headed for a lot of good reasons, and it makes sense for Canonical to jump on that train. Snaps are bad (although honestly I do like that they can package server apps unlike flatpak, that’s cool), but the concept for the distro is not.