zhashtoshi_
Zhash

https://relay.hivescope.xyz

₿ Bitcoin, Nostr and Hive. I build decentralized stuff:
chat.hivescope.xyz
quill.hivescope.xyz
and run a small open Nostr relay. @rzazo24 on Hive.
https://github.com/rzazo24

Public Key

npub1v7nf76fh474q4dnqfjpnkyqsmg439n5uw9x9jdpvzmmgczvrwhcsuhvl8a

NIP-05 Address

zhash@rizful.com

Profile Code

nprofile1qqsx0f5ldym6l2s2kesyeqemzqgd52cje6w8znzexskpda5vpxphtugpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpz3mhxue69uhkummnw3ezummcw3ezuer9wc4y2u5g

Publishing to

nostr.bitcoiner.social

Author Public Key

npub1v7nf76fh474q4dnqfjpnkyqsmg439n5uw9x9jdpvzmmgczvrwhcsuhvl8a

Show more details

Last Notes

2026-10-13 22:29:51 UTC

- reply

Sorry to hear that. It's a good reminder of why code hosting shouldn't depend on one company: git over Nostr (NIP-34, e.g. ngit) lets you keep your repos and issues under your own key, with a mirror wherever you like. Keep building! 🫡

2026-10-13 20:16:31 UTC

- reply

Thanks, I'll take a look! A "restore a previous version of my follow or mute list" option would fit well next to the checks Quill already does before signing a list change. If I add something like it, I'll make sure to credit Lazarus.

2026-10-13 07:36:50 UTC

- reply

I think mostly yes, the same way you'd be responsible for an employee you handed your keys to without any rules. Not telling it to do something isn't the same as not letting it.
That's why my own agent setup can't publish without my confirmation, is capped at a few posts an hour, and my signer refuses any kind I didn't allow. The guardrails are the part I'm accountable for.

2026-10-12 22:40:03 UTC

- reply

PWA is the best option. Lightweight and more private.

2026-10-12 21:41:36 UTC

- reply

I think the clear panel is better so you can see inside. It would also be important to have access to images and videos of the wallet teardown to better assess whether it was tampered with.

2026-10-12 20:41:58 UTC

- reply

One more: a Highlights view, next to Follows, Network and Popular.
It looks for substance, not likes. Over the last two days it takes notes with something to say (40+ words of their own) by the people you follow, plus notes by anyone that they replied to, quoted, or that at least two of them shared. One repost alone doesn't bring a stranger in.
Talk weighs most and a like little. Two notes per author at most, never yours, and each one says who of your follows talked about it.
It's a rule, not an editor: it can't read, so now and then something light slips in. But it surfaces far more than a like count does.

2026-10-12 19:40:56 UTC

- reply

Follow-up on relay.damus.io: today, publishing one note, damus first answered "rate-limited: you are noting too much", and on a retry "banned: too many rate-limit violations, try again later". The same note was accepted by every other relay I use.
Since I added it to my list on Oct 11, damus kept 30 of my 41 events. I don't post much, but my key also signs through my own NIP-46 bunker, which talks over damus, so I guess it all adds up against one limit.
So I've replaced it as a publishing relay with nostr.bitcoiner.social. I chose it by looking at which relays the people I follow and who follow me actually read from (16 of 82 lists), and which ones accept and return my notes.
Not a complaint: damus carries a huge load, and my signer still uses it to talk to my bunker.

2026-10-12 19:11:35 UTC

A few more things in Quill, the text-first Nostr client that tells you why it hides things:
• Send zaps with your own wallet through Nostr Wallet Connect. The connection string stays only on that device, with a clear warning that it can spend, and Quill pays only if the invoice asks for exactly the amount you chose.
• Other people's notes now show their zaps, and who sent them. Only zaps: Quill never shows how many likes or reposts a note got, so a count doesn't decide what looks important.
• Notes that arrive from people's own relays while you are reading further down no longer move the page: a button at the top says how many came.
• Optional real profile pictures, off by default and only for people you follow. Everyone else keeps a drawn avatar, so no spam account can put a picture in front of you.
https://quill.hivescope.xyz

2026-10-12 17:16:40 UTC

More news in Quill, the text-first Nostr client that tells you why it hides things:
• Zaps: your notes show the sats they got and who sent them, checked against the zap receipt.
• Drafts: what you write is kept if you leave the page.
• You can edit your profile description and delete your own notes.
• Two new filter rules: notes made of mentions (used to flood someone's notifications), and notes that are not text (an app's JSON or a long base64 blob posted as a note). Both say why; you can open them anyway.
• The trust score now weighs your own network: an account vouched for by people you follow counts more, and one muted by them counts less.
• Search has Filters: show all, people or notes, and search in what is loaded or, only if you choose it, in the network.
• People are also read where they write (NIP-65): if someone you follow publishes only on relays that are not yours, Quill asks a few of theirs, just for them. A switch in Settings turns it off.
https://quill.hivescope.xyz

2026-10-12 09:56:36 UTC

- reply

It looks interesting 🤔

2026-10-12 00:21:32 UTC

But this note got blocked by the Damus relay again. It definitely looks like intermittent rate limiting 👇🏻
#nevent1q…hxsy

2026-10-12 00:16:37 UTC

What's new in Quill, the text-first Nostr client that tells you why it hides things:
• Quoted notes show inside the note that quotes them, judged by the filter like any other.
• Pictures and videos: a "Show image · site" button loads them straight from their site, only when you tap. Quill keeps no copy. Optionally, pictures from people you follow load by themselves.
• A Popular feed: notes by anyone that the people you follow reacted to or reposted in the last day, each saying who.
• Search: instant, on your device, in what Quill has loaded; a hashtag also asks your relays; a button asks two search relays only if you want.
• Mute from an account page or a note's menu, with the same care as following: one account changes, the rest of your list (private part included) stays.
• Each account page shows how much the network vouches for it, with the reason for every point.
• A light theme.
https://quill.hivescope.xyz

2026-10-12 00:13:56 UTC

- reply

Update: this very note went through on damus at the first try, along with the other five. So it looks intermittent rather than something about my key.

2026-10-12 00:12:59 UTC

Has anyone else seen relay.damus.io turn notes away lately?
Twice in two days, publishing a single note from my own key, damus first answered HTTP 503, and a retry a few seconds later got "rate-limited: you are noting too much". The same signed note was accepted by the other five relays I publish to. I don't post much.
Not a complaint, damus carries a huge load. Just curious whether it is a new limit, something about my key, or a bad moment. #nostr #relays

2026-10-12 00:06:34 UTC

- reply

Congrats on the launch! Lazarus is a great idea: overwritten lists are one of the scariest things in Nostr. I just added muting to my own client, Quill, and went the cautious way: it reads your newest mute list right before signing, changes only that one account, keeps the private part untouched, and refuses if the list looks smaller than expected. Nice to know there's a safety net if something slips through anyway.

2026-10-11 15:24:31 UTC

- reply

The idea is really good. It would be nice to be able to select content from the global feed, to discover interesting posts selected by the AI. It would also be good to improve the interface in the PWA.

2026-10-11 15:07:40 UTC

- reply

Now I’m testing it. Very interesting proyect 👌🏻

2026-10-11 11:59:13 UTC

Heads-up for anyone using relay.nostr.net: today it refused most connections from my side (HTTP 500 on 4 of 5 attempts; the relay info page itself answers fine), so my notes kept landing on 5 of 6 relays.
I swapped it for relay.damus.io in Quill's defaults and in my own relay list. relay.snort.social was the fastest I tried, but it only keeps events in memory; nostr.bitcoiner.social and offchain.pub reject events from keys outside their web of trust.
If you run it and want details, happy to share what I saw. #nostr #relays

2026-10-11 00:28:31 UTC

- reply

Thanks, that makes sense: that round trip through Clave's relay is the weak spot. In my case it kept failing even with good coverage, so I ended up running my own signer on a VPS for my other apps, and I'm keeping Vault with Clave for now. Good to know about the NIP-49 option, a locally encrypted key sounds like the most reliable setup on a phone.

2026-10-10 23:00:19 UTC

- reply

Great update. Now it works much more smoothly and the new features are great 👌🏻. Although sometimes it's hard for them to connect with Clave (Probably because of iOS).

2026-10-10 21:02:48 UTC

The bunker connection with Clave worked fine until this afternoon. From then on it started giving me various types of connection problems, I guess because of iOS. So in the end I had no choice but to create my own bunker hosted on a VPS.
#nevent1q…avak

2026-10-10 20:48:01 UTC

Why I built my own Nostr signer
My phone signer kept failing when I needed it. iOS suspends apps, its background wake-ups were unreliable for me, and after I deleted one connection I could not pair it again. Quill, my relay's admin panel and my MCP assistant all stopped signing in the same day.
So I wrote hivescope-bunker, a NIP-46 remote signer for one account that runs on my own server:
• The key is encrypted on disk (NIP-49) and the bunker starts locked: I unlock it by hand after a restart
• Each app has its own connection that can sign only the kinds of event it needs, with an hourly limit
• The relay panel's connection signs only logins for its own address
• No open ports: it only connects out to relays
The trade-off is real: my key now lives, encrypted, on a server instead of in a phone keychain. Open source, MIT, written in Go:
https://github.com/rzazo24/hivescope-bunker
#nostr #nip46

2026-10-10 20:01:11 UTC

- reply

I think that's what all clients should do but they don't. That's why I came up with the idea of Quill. It's a modest project that I'm still developing. My idea is for it to be a lightweight client that can give you the features that big clients don't give you.

2026-10-10 13:10:36 UTC

- reply

Thanks for looking into it, and for the screenshots! The notice recommending a bunker address makes sense: pasting it from Clave instead of using the nostrconnect flow worked for me, since Clave only has to approve in the background and iOS suspending it doesn't break anything.

2026-10-09 22:33:41 UTC

Quill: a small, text-only Nostr client that tells you why it hides things.
• Nothing external is loaded: no images, video or link previews. The browser enforces it, not just the code.
• A filter you can read: every hidden note says which rule hid it and what the rule saw. One tap shows it.
• You write through your signer (Clave): Quill never sees your private key.
• Replies, reactions, reposts, a Network view (the people your follows follow), notifications inside the app. Installs as a phone app, no backend.
https://quill.hivescope.xyz
Open source (MIT): https://github.com/rzazo24/quill
#nostr #quill

2026-10-09 21:33:03 UTC

- reply

Following up: I did ask @npub1xy5…3urc in a separate note, and in the end I solved it myself.
The problem was how I had paired Clave with my MCP server: I used a nostrconnect link. Pairing through a bunker address (copied from Clave) fixes it, even from Termius on the same iPhone: with Clave in the background and low trust, the signing request now arrives and I can approve it in about 6 seconds.
Tested only a couple of times, but it works exactly in the setup that failed before. So there is no need for another signer, and no need for full trust.

2026-10-09 21:24:05 UTC

- reply

Update: solved on my side.
The problem was how I had paired Clave with my MCP server: I used a nostrconnect link. Pairing through a bunker address (copied from Clave) instead fixes it, even from Termius on the same iPhone: with Clave in the background and low trust, the connection resumes by itself and the signing request arrives so I can approve it (about 6 seconds).
Tested once so far, but it worked exactly in the setup that failed before. In case it helps @npub1xy5…3urc or anyone with the same setup. @npub1cla…539g

2026-10-08 21:09:07 UTC

- reply

Clarification: that relay rejects my replies too, not only reactions (this thread's reply included). It still accepts my own standalone notes.

2026-10-08 21:02:51 UTC

- reply

A small addition from a real case: it can also be applied by relays when you write, not only by readers. nostr.bitcoiner.social rejected a reaction from my key with "pubkey is not in our web of trust", while accepting my notes.

2026-10-08 12:33:28 UTC

- reply

There are nice people everywhere. Sometimes the hard part is finding them.

2026-10-08 12:30:14 UTC

- reply

Now I get what this is about 👌🏻

2026-10-08 12:28:24 UTC

- reply

What’s WoT? Is there a note that explains it?

2026-10-08 11:53:27 UTC

- reply

What I also notice is that the connection with Clave sometimes fails, so there are events that don't get registered or the relay gives an authentication failure. The problem may be more with Clave than with Nostr.Vault.

2026-10-03 23:44:53 UTC

- reply

Signing in and looking for a group to chat

2026-10-03 22:29:45 UTC

It’s not quite like Bitchat but it gets the job done: chat.hivechat.xyz
#ephemeral #chat
https://npub1v7nf76fh474q4dnqfjpnkyqsmg439n5uw9x9jdpvzmmgczvrwhcsuhvl8a.blossom.band/7095b4f5a5c093fe4296ed6ca3c2a42d478e39fb8cd96594a603076a1c18ef59.jpg

2026-10-03 22:23:57 UTC

- reply

In Spain se say: “no pueden ponerle puertas al campo”
https://npub1v7nf76fh474q4dnqfjpnkyqsmg439n5uw9x9jdpvzmmgczvrwhcsuhvl8a.blossom.band/e896fc6570723b98fe88d6ebe8a6a48757057c97d4819cea26a94e1e38bc581e.jpg

2026-10-01 20:53:35 UTC

- reply

GM Joe! Alive and kicking from Spain 🇪🇸 Building on Hive and lurking here on Nostr too ⚡

2026-10-01 10:06:51 UTC

Learning about #nostr
https://nostr.how/

2026-10-01 10:02:40 UTC

- reply

Very interesting. You can create your own Coursera!!!