#Amethyst v1.09.0: We are going crazy
- Go live on audio spaces (Nests)
- Marmot Group chats (WhiteNoise)
- Voice and Video calls (Noscall)
- PDF reader
- Favorite algo feeds
- HLS Video Uploads
- Sc...
I am testing Nostr Nests rooms in Amethyst and they stay permanently on “Reconnecting.”
I tested both the public Nostr Nests audio server and my own self-hosted server.
For my own server:
- the room event has the correct tags:
["auth","https://talk-auth.letsfo.com"]
["streaming","https://talk.letsfo.com:4443"]
- Amethyst successfully authenticates repeatedly against my auth server
- my server receives UDP traffic from Amethyst on port 4443
- my MoQ relay replies to Amethyst over UDP
- but Amethyst never finishes connecting and stays on “Reconnecting”
The same reconnecting behavior happens with the public Nostr Nests server too.
Is there a known issue with the current Nests/MoQ room implementation in Amethyst, or any debug logging I can enable on Android to see why the connection does not complete?
I tested both the public Nostr Nests audio server and my own self-hosted server.
For my own server:
- the room event has the correct tags:
["auth","https://talk-auth.letsfo.com"]
["streaming","https://talk.letsfo.com:4443"]
- Amethyst successfully authenticates repeatedly against my auth server
- my server receives UDP traffic from Amethyst on port 4443
- my MoQ relay replies to Amethyst over UDP
- but Amethyst never finishes connecting and stays on “Reconnecting”
The same reconnecting behavior happens with the public Nostr Nests server too.
Is there a known issue with the current Nests/MoQ room implementation in Amethyst, or any debug logging I can enable on Android to see why the connection does not complete?
👀1