Avatar
hacktheplanet
640b1fe1dc17b3d1261e245b892a2796dd7dd9b99d4d2f89c0af477536e32da5
I'd like to hear your story.

I think he is now Mister Papa Edward who will be very very careful to not piss off the one country he and his family reside in.

If we are hoping for a whistleblowing hero about russian internals we'll have to look somewhere else I guess.

I cannot imagine what you are going through right now Anton.

Buut I am not sure if Assange is allowed to have russian cock right now.

Maybe nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9 can elaborate why he chose Russia.

I guess it's less about his cocksucking preferences and more about every other country being scared...

Darktable all the way if you want a Lightroom-esque experience.

Do you supplement?

1. Which wallet did you use with your coldcard?

2. Which wallet did you use to try to restore?

3. Did you try to be smart: mixing the words, using passphrase and writing down only half of it (because thieves) or something like that?

4. Does the coldcard still hold the keys it generated?

5. Is the watch-only-wallet still on the sd card?

6. Did you use an additional passphrase on the cold card?

7. Are you able to unlock the coldcard with the pin?

There are two last resorts to try to get your sats back.

>>>First:

Using your seed+password and then cracking the variation you introduced without knowing.

The only service here I would remotely trust is this one

https://www.walletrecoveryservices.com/

I did not use them myself as I have trust issues and I cobbled something together myself to crack my wallet passphrase.

>>>Second:

Using your hardware wallet.

Security soft/hardware does not age well. Your hardware wallet might be secure now, but flaws will be found in the future. You'll maybe have to wait 1 years. Or 100.

DO NOT send your seed phrase off to me or anyone else in your DMs. Even using walletrecoveryservices might be an elaborate scam running for 11 years, just waiting for that one juicy wallet.

First you could try to get your mind back into the same state: get aggravated and eat ze meds. Then think through the same process you used and maybe your brain will come up with the same genius method of fucking up and you'll notice.

Buy a second coldcard and try tp repeat the process.

DO NOT reset your existing coldcard, as it might still hold the secret to your coin.

I relied on a snippet of code I wrote to do that.

Slept many times like a baby while it ran. And once it grinded through all of history it's easy to keep up. Needed the list of all addresses owning bitcoin for a bloom filter because brainwallets.

Verifying supply was a side effect to be honest

I know every utxo and every address. It checks out

I'll audit the supply of monero! Oh wait...

If unsure how hard you fucked up it is not over yet.

Nostr is a giant shit show. The fact that our software interoperates at all is a miracle and probably just a temporary anomaly. Given enough time, the relentless breaking changes being made to published NIPs will eventually break everything.

Linux succeeded because "WE DO NOT BREAK USERSPACE". For nostr to succeed, changes must "NOT BREAK EXISTING IMPLEMENTATIONS". There shouldn't be any exceptions to that EVEN IF THE IMPLEMENTATION WAS NON-COMPLIANT.

Pay close attention to Linus right here:

> Are you saying that pulseaudio is entering on some weird loop if the

> returned value is not -EINVAL? That seems a bug at pulseaudio.

Mauro, SHUT THE FUCK UP!

It's a bug alright - in the kernel. How long have you been a

maintainer? And you *still* haven't learnt the first rule of kernel

maintenance?

If a change results in user programs breaking, it's a bug in the

kernel. We never EVER blame the user programs. How hard can this be to

understand?

Linus doesn't want to break pulseaudio EVEN THOUGH pulseaudio was doing the wrong thing.

It seems like every week I find a NIP that I've coded for has changed. This last week I think it happened three times already. Sometimes it's a small change and I quickly update my code. But I can't read all the PRs, and I'm afraid dozens of small changes have slipped past my notice. Gossip is probably now incompatible with multiple other implementations which happen to have implemented different versions of the same NIPs (some older, some newer).

Even if we didn't have any breaking changes, the simple fact that different software implements different optional NIPs itself presents to end users like broken software. Why does it work in Damus but not Amethyst? Why does it work in Amethyst but not Coracle? That is an even harder problem to solve.

But let's at least solve the easier problem and stop changing NIPs. If you don't like a NIP make a new one, don't break the current one. Even if you think the current one sucks balls and should have never happened. Even if you think there aren't many implementations out there.

Developer burnout factory?

Why do I think of lightning. The fact it was/is a moving target for so long did upset some devs to the point they ripped it out of theirs apps after a few years of following and fixing breaking changes.

We simply need an open source phone with open source decentralized reproducible kernel. That's it!