Linux desktop stuff is such a mystery to me. This honestly seems batshit insane, but in GTK3, it appears that if you use a FilePicker, something like (Rust here but w/e): rfd::FileDialog::new().set_directory(&my_specific_dir).pick_folder() ... it refuses to open the file picker in your specified directory. It just flat out ignores you, and *always* opens the dialog in its "Recent Items". So not complaining about a default (though it's a terrible one honestly), but the baffling decision to just ignore the developer's setting. I would love to find any justification of this anywhere, but I can't. This "documentation" (

Gtk.FileChooser.set_current_folder

) just points at a non-existent other documentation section to justify why you shouldn't use the function (Not "deprecated" but "warning, you'd better not use this function, but we won't tell you why!"). The code itself basically defaults to recent items, and that can *only* be overwritten with a GTK setting, outside of the developer's control, and here's the best bit: if you somehow get your user to override it, they can *only* change the location the FilePicker opens in, to $HOME! Your directory setting will still get ignored! Btw this restriction did not exist in the previous GTK version; they actively added it as an improvement. #linux

I did this. It worked. Cool software! View quoted note →

If you plan on creating a new tech/wallet/project in bitcoin, be sure to set aside several days to choose a name that isn't already taken by some altcoin or token.

Gave a presentation last week on "purecoin", showing basically how ~ 50% embedding rate in "pure" bitcoin transactions with no scripts is inevitable *even if* you force the outputs to prove they are not "fake". 'Fraid the audience had no idea what I was talking about, so I'll post the pdf here: https://files.catbox.moe/tpfc4x.pdf I must apologize for calling it a "very hard fork" because you could actually do it as a soft fork (thanks @npub1au23...t53j ) but it's hardly relevant. The point is that there is no version of Bitcoin, even a 99% crippled version of it that doesn't allow L2s, that does not allow data embedding, *except* one in which we completely change the cryptography to BLS (any deterministic signature scheme could in theory do it, but nobody is going to seriously suggest hash-based signatures or RSA FDH I think) (thanks @Zero-Knowledge Goof for thoughts on this), *and* totally cripple any programmability. And since quantum is coming (so they tell me!) I see basically no chance of this happening. #bitcoin #cryptography

Wtf! (also not working here) View quoted note →