That's the npub derived from the hex when it's interpreted as a secret key. There's also the npub of the hex interpreted as a public key in the output.

In the inbox commands it will read from the target's "read" relays automatically or what?

Yes, but prettier.

Thank you, you are right. Although I'm sure I had the -O flag there at some point, but obviously not in the version of the script I pasted here.

Unfortunately no because djot is really great.

Weird, I always browse relays and never seen that issue. Is that on desktop or on a phone? If it's on a desktop please try https://jumble.social/ and see if the issue also appears there and let me know, please. If it's on a phone then abandon the web and try the native app (install from app stores) as it has a very nice relay browsing capabilities.

blurhash: thumbhash:

https://fevela.me/ now supports https://github.com/dtonon/fevela/pull/40, which is better than blurhash. https://evanw.github.io/thumbhash/ You can see it in action on if your eyes are faster than your internet. (Or throttle the connection speed in your browser devtools network panel, this was a good idea.) Actually after browsing through a feed of blurhashes (on Jumble) and a feed of thumbhashes I've changed my mind, I think the difference is absurd and thumbhash is not only slightly better, it's astronomically better. would you add it to Jumble? please jump in the bandwagon too! ? ? ? ?

#pyramid has had some updates with bugfixes since the v1.0.0 release, but there was no easy way to update the version you had running in your server that was as easy as the installation process. Now we have the easiest thing possible, a button: You click and it will update your server in place. The only catch is that you have to update manually once to get the button. If you've installed pyramid using the easy.sh script you can do that by opening your server terminal and pasting this: systemctl stop pyramid cd pyramid wget https://github.com/fiatjaf/pyramid/releases/download/v1.0.5/pyramid-exe chmod +x pyramid-exe systemctl restart pyramid

Crowdsourcing doesn't mean just users clicking, by the way (although that could be possible too), it means a bunch of machines competing: https://leaderboard.sbstats.uk/

What happens? Can you send a screenshot?

What is that?

I didn't benchmark, but it should get pretty close to strfry for query operations, it's very inspired by it and also uses LMDB. It also does a noveau thing with direct memory mapping of a huge file with encoded events that I came up with and may be completely broken but may also end up saving some milliseconds. The most important part is that events are deduplicated across the main relay and all the subrelays.

Here's a demo of how you can setup a pyramid relay for you in very few steps:

I think redundant coordinators will work, you just have to have more than one in your bunker URI. Also I don't want to run this coordinator forever, this was just a prototype until someone made one in Rust. But for now I think the signers are the biggest problem. There may be something wrong with nostrlib that causes it to not reconnect to the relay after a connectivity glitch, so they stop reacting to messages. Or at least that is something that seems to be happening with `nak bunker` too and it uses the same approach, but I can't figure out what the exact cause is. If someone can help find the bug that will be much appreciated. Or rewrite it in Rust.

Can you voice your criticism in a clearer way? How does Nostr AUTH help with a git server? Or how is ssh better in any way than authorizing with Nostr then pushing with http? No, hosting git objects on blossom is not easier than running a normal git server over HTTP, it would be ridiculously more complicated. I don't understand what you're thinking.

https://gitworkshop.dev/danconwaydev.com/grasp/tree/master/01.md But I think it's still a work-in-progress. If you have some good ideas about how to best handle the pull request flow or other things let know.

Grasp is Blossom for git repositories. You can host your repositories in multiple servers and their state is attested by Nostr events you publish that tells people where to fetch from and what is the latest head and branches, so the servers don't have to be trusted and it's easy to switch servers while keeping your repository identifiers immutable (they're essentially your pubkey + an arbitrary identifier). Grasp servers can be self-hosted, paid, or ran for free by some community benefactor, and you can mix and use all these at the same time. The existence of grasp servers also makes it easy for people to clone repositories, create branches and make them available to be merged by others, all without leaving the terminal (but of course there can also be all kinds of clients), which is the GitHub "pull request" UX people are familiar with.

I was conflicted about adding it, but finally made my mind. I had enough of my own decoding learning experiences too. Oh, it also support nip05 addresses. Please report bugs (just replying in this thread is ok).

Do you listen to podcasts in a browser?