mckinley

twtxt.net

A guy on the internet. https://mckinley.cc/

Recent twts from mckinley
In-reply-to » @mckinley absolute rubbish.

  • (3) Does Nostr require clients to download much more data than, say, Twitter? I can see it being a little more because of signatures, etc. However, text compresses well and clients should cache previous posts, anyway.

  • (4) NIP-96 does HTTP file upload, XMPP style. There are some other advanced features like tipping on posts, custom emojis, and at least three conventions for selling goods and services.

Of course, not everything is available with every client and some of the specs are still being worked out. It looks promising to me, though. I like its distributed model with dumb servers and smart clients. The software will get better over time.

⤋ Read More
In-reply-to » @mckinley absolute rubbish.

All three of your points on usability are definitely true, especially #3. I haven’t been able to find a good TUI client.

Regarding the technical points, it seems like there are mechanisms to address each of them. Please tell me if I’m wrong on any one of these. I have only been learning about Nostr for a short time.

  1. Relays aren’t a single point of failure because a user can (and should) post to many of them. The attacker in a censorship or sabotage scenario would have to take down every one of your relays at once. If they were taken down gradually, you could replace the bad relay with a new one and advertise that one on all the other relays your followers already use. It’s much more resilient compared to twtxt.

  2. Every event contains a signature from your private key, so it’s hard to spoof. NIP-10 provides a method for marking a note as a reply to another note.

⤋ Read More
In-reply-to » QOTD: What are your thoughts on nostr?

Something I’ve noticed about the Nostr people is that they aren’t the same as the software minimalism people. It seems like it’s all JavaScript, Go, and Rust with dependency counts in the hundreds.

⤋ Read More
In-reply-to » QOTD: What are your thoughts on nostr?

@lyse@lyse.isobeef.org

I fear it’s a rather complicated protocol.

The core protocol looks very simple but I’m sure you can get in the weeds with extensions.

you can’t really change your keys without losing your identity

I think you’re right but that seems reasonable to me. Your public key is your identity, similar to certain cryptocurrencies or Tor hidden services. Why would you want to change your key without changing your identity?

⤋ Read More

PSA: If you’re on Arch Linux and you want to use some of your own scripts on multiple machines, it is incredibly easy to write a PKGBUILD. Then, you can scp the built package around and install it with pacman -U. Let Pacman handle your dependencies so they can easily be removed later and only when they’re no longer required.

⤋ Read More
In-reply-to » Pro tip: Don't run out of space on Btrfs.

@movq@www.uninformativ.de Yeah, it seems like that should never happen under any circumstances but that’s the best explanation I can come up with for what happened and once I fixed the space issue the other problems went away. That particular filesystem is on a LUKS device on a disk image served with NBD. The machine in question and the NBD server are both on Arch Linux so it has potentially unstable versions of all the software involved.

It’s a real house of cards and I’m not surprised something like this happened. I’m keeping lots of backups. My setup is pretty unique but I stand by my original post. Running out of space on Btrfs isn’t fun, even when it’s functioning properly.

⤋ Read More