I'm trying to switch the wallet setup in my phone's Nostr client to use a local relay (specifically @Citrine) and @zeus for fast responsiveness, but it doesn't work properly in almost all clients.

I suspect it's because they automatically block WS connections instead of WSS. Only amethyst allows zaps, but even there, balance and history checks don't work.

Blocking WS is fine, but localhost should be whitelisted as an exception.

@ZEUS Apps connected via NWC are extending beyond a single page, but scrolling isn't working, so the initially registered ones are not visible.

@PayPerQ How do I get rid of the red inquiry button floating on the screen? It's really annoying.

Am I the only one who thinks it's weird that the playback bar, play/pause button, or settings button cover the video when watching? Isn't this way too annoying?

https://zapstore.dev/apps/com.hoppe.cliprelay

I had Claude build me a clipboard sync tool using Nostr. I've always found it extremely cumbersome to copy something on one device and paste it on another by having to open a messenger app, find the chat-with-self room, paste it there, then on the other device open the same messenger, go to that chat room, tap on the message, and copy it again.

Sure, similar tools probably exist out there, but these days with Claude around, it's so quick to just ask an AI to build it—so I went ahead and made one.

Here are the app's key features:

- Supports only NIP-46 login (direct use of private keys is not supported. Aside from security concerns, the problem remains of how to transfer that private key to another device. Isn't it ridiculous if you still have to use a messenger just that one initial time to send it over?).
- Tracks in real-time the relays and Blossom server specified by the user, and transmits data through those servers.
- Text is encrypted using NIP-44 self-encryption; images are encrypted with an AES-GCM one-time key, then the encrypted binary is uploaded to Blossom, while the SHA-256 hash and decryption key are sent via NIP-44 encryption. General file types (beyond images) are not currently supported.
- Supported on Windows, Linux, Mac, and Android; iPhone is not supported.
- Usage: On desktops, after installation and login, there’s nothing else to do—copy on one device, and it automatically appears on the other's clipboard. On mobile, there is a persistent notification—after copying, tap the persistent notification to send it to the other device. When receiving, a separate incoming notification appears (distinct from the persistent one), and tapping it copies the content to the clipboard.
- Currently free. I'm considering a payment system for the future—specifically when large file support is added, I'm thinking of passing charges directly through the Blossom server (not that I intend to collect payment directly). Enabling economic incentives for Blossom server operators was actually one of my motivations for building this app. I plan to support it once a smoother payment standard emerges.
- On mobile, the app attempts to stay running continuously unless explicitly closed by the user (though this cannot be guaranteed).
- Care has been taken to ensure plaintext is never stored outside the app’s own storage (e.g., in notification systems), though this cannot be fully guaranteed.
- Clipboard history is stored plaintext on the device itself.
- Logging out deletes authentication data along with the history.
- The NIP-46 communication private key is stored in the OS-specific secure key storage.

I’ve put effort into encryption, but given my own technical limitations, I can't be certain there are no data leaks somewhere. I do not recommend using this app for highly sensitive or critical information. It’s intended only for everyday, routine use—something that replaces the kind of casual content you’d previously share over messenger apps.