Avatar
ThatWhichisNotSeen
cf8f07ebffbdce4976ea8ab830cfd6036ffb6203e67ba8eb7a9a448a742a6eaa
Bastiat already explained all of this to us, but here we go again...

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn im testing latest flotilla. Trying to get the new notifications to work with my nip 42 relay. I think im not getting them because i dont have an invite code for my space, perhaps? How do i generate an invite code for my space as the owner of the relay ( relay.tools relay) ?

nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 Hey, couple observations:

I am testing Keychat with using various relay setups. If I have the default relays in my setup, I get notifications on my phone. However, If I add just my relay.tools relay, the message sends successfully but I no longer get notifictions (If I have nip-42 set to yes, the message does not go through at all which I think I understand why). I then played around with the combos and found that notifications seemed to need having wss://nos.lol as a connected relay.

Also - I downloaded the linux desktop appimage, but so far have not been able to successfully open the client. I have it set as an executable program, not sure if this is known as I know the desktop app is new, but fyi. I'll keep trying to troubleshoot on my end too with the desktop app - easily could be user error on my end.

Keep up the great work!

I was testing on my graphene OS pixel 7, latest version of Keychat available in zapstore

Update, I got the .deb package to install successfully!

nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 Hey, couple observations:

I am testing Keychat with using various relay setups. If I have the default relays in my setup, I get notifications on my phone. However, If I add just my relay.tools relay, the message sends successfully but I no longer get notifictions (If I have nip-42 set to yes, the message does not go through at all which I think I understand why). I then played around with the combos and found that notifications seemed to need having wss://nos.lol as a connected relay.

Also - I downloaded the linux desktop appimage, but so far have not been able to successfully open the client. I have it set as an executable program, not sure if this is known as I know the desktop app is new, but fyi. I'll keep trying to troubleshoot on my end too with the desktop app - easily could be user error on my end.

Keep up the great work!

I was testing on my graphene OS pixel 7, latest version of Keychat available in zapstore

Looks like the very fabric of reality is breaking apart behind them due to this meeting šŸ˜…

Replying to Avatar Keychat

Keet uses the Holepunch stack—not WebRTC—for its real-time voice calls. In a one-to-one call the connection likewise falls into three logical stages:

1 Ā· Peer-discovery exchange

Each endpoint relies on HyperDHT ( Distributed Hash Table) to locate the other party:

The caller joins the network with the callee’s 32-byte Ed25519 public key.

Nearby DHT nodes return the latest announce record published by that key—essentially ā€œI’m online at 203.0.113.7:54567ā€.

A short-lived, signed invitation token proves the request really comes from the owner of the calling key, preventing spam.

No central signaling server is involved; the DHT itself is the rendez-vous layer.

2 Ā· Distributed hole-punch — DHP → direct connection

The two devices attempt to break through their NATs with DHP (Distributed Hole Punching) and then talk over UDX (Ultra-Datagram eXchange):

Each side enlists several random DHT peers as hole-punch helpers—they play the same role that STUN servers do in WebRTC but are fully decentralized.

Both endpoints fire simultaneous UDX probes at every candidate (IP:port) they learn.

As soon as one path succeeds, a one-round-trip Noise_XX handshake derives a session key, and encrypted audio frames start flowing directly between devices.

In residential or mobile networks this succeeds ~70 %–80 % of the time, giving a pure P2P (peer-to-peer) path with minimal latency—no relay, no bandwidth fees.

3 Ā· Volunteer relay fallback

If symmetric NAT (Network Address Translation), CGNAT (Carrier-Grade NAT), or a strict firewall blocks every hole-punch attempt:

Keet asks nearby peers whether any is willing to act as a relay for this call.

If at least one agrees, the audio stream is tunneled through that peer—still encrypted end-to-end by Noise—so neither relay nor network can eavesdrop.

When no volunteer relay is available, the call fails; Keet has no equivalent to TURN (Traversal Using Relays around NAT) hosted in a central data-center.

nostr:nevent1qvzqqqqqqypzpwleyw4fy3sxt7yvgrran0mpenxqlululur94r9jlax0hd3q3rc7qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqypvwqh84uq76vdjhaa9ekn4tt0trwuw2kkc5htsxz2jasezmmcht60p280p

Excited to try this out in the app!

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl What is the best way to delete a single note from nostr relay tray? I see a filter option for event ID, but it wants it in 'hex' format? How would you go about deleting a single note using the dashboard? Thanks!

I uninstalled amethyst and i am using keychat now...and discovered my phone does have decent battery life still apparently šŸ˜‚

A client that bootstraps in the community relay, and stays in the community relay without having to follow 12 steps to set it up. Should literally be: user copy the wss://examplerelay.name into first field upon opening app, then they.name nsec / sign in from amber, then they are in that relay and not exposed to all the other communities on nostr.

Like im thinking keychat where it serves as a signer for mini apps, but you are silo'd in your community relay by design.

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl i have a test accoubt i am trying to add read/write relays to, but after several attempts to add the relay the process wheel was just spinning after i clicked save. Now, when i return to the page to add relays ( ive force closed and cleared cache), it is stuck like this:

I cant figure out a way to fix it. I am using jumble via the keychat browser on an android LG phone ( running android OS 15). This issue does not happen for my every day phone / npub that I am,posting this from. May be a bug so letting you know. Have a great day!

Replying to Avatar Dikaios1517

Well... nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9g84ctjf is out. Though it is now easy to set up a wallet to receive zaps with Zeus's new eCash feature, you still cannot easily connect your Zeus wallet to a Nostr client via Nostr Wallet Connect for sending zaps.

So it's looking like nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rg20d4vz might be the way to go, unless others have suggestions.

Criteria:

- No KYC needed.

- No channel management needed.

- Lightning address for receiving zaps.

- Nostr Wallet Connect for sending zaps.

- NIP-57 support for zap receipts.

Keychat ecash wallet, set up with minibits relay and generate nwc string to use in other apps...then use npub.cash ln address for receiving, can then make ecash withdrawals to the keychat wallet.

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl i think it'd be cool in jumble if there were a way to mark a relay as a 'trusted' relay, where if marked as such, all comment counts, reaction counts are shown before you click on the note and web of trust filtering client-side is turned off at least when viewing that relay's feed.

You are welcome, dont hesitate to message me for more info, i enjoy helping however i can

nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 ive been testing making large groups. When i make the group and invite another test account i made on diff phone, the invite for the invite receiver doesnt appear as an invite link, but instead seems to be some encryped message.

nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 whats the maximum users ( more or less) for this group chat option?