nostrnests / nests Goto Github PK

When joining another room from the profile flyout, the room audio doesn't connect to the new room instead it stays connected to the current room.

The flyout also doesn't close.

This may be because we use navigate with state object. I assume there is a react hook dependency

It would be cool If users could connect their lightning wallets and zap directly on Nostr Nest!

Bitcoin Connect is an easy to implement web component that allows it through WebLN (and NWC).
When implemented could easily connect their Alby, Mutiny, Umbrel, lnbits and some other wallets (and list is growing) to do payments directly from their own wallet (without confirmations or QR codes). And all that without the need to install WebLN browser extension

More about Bitcoin Connect on Github and website.

• Spacebar toggle mute
• Spaceber PTT
• More?

Sometimes mic volumes are adjusted automatically on the OS when using nests even though AGC is disabled, not sure why..

When zapping another user, the zap window doesnt automatically close.

This is because we dont know if the invoice is paid.

Using the zaps feed we COULD detect a payment is complete my comparing the zaps paymentHash to the paymentHash of the invoice displayed and automatically close it.

Cant leave the stage when mic permissions is denied

When you reload the page while in a room, it uses the (probably) expired token.

2 options:

1. Use the latest token which is being refreshed in the background
2. Get a new token if we get auth issue

Ref: #17

On the room list page the presence events should be queried from the relays listed in the relays tag of each room instead of the default relay list

Add chat moderation features the same as zap.stream

• Mute user
• Hide muted users from own mute list
• Hide muted users from room host

Similar to the profile flyout, create another flyout on the left which will display the room list (lobby)

I've identified two significant issues with nostrnests that need attention: room access and high latency

Room Access Issue:

Users encounter difficulties joining rooms, preventing them from participating effectively

The problem persists across different browsers, such as Firefox and Microsoft Edge, Opera

High Latency:

Latency during conversations is unacceptably high, ranging from 2-20 seconds
This delay impedes smooth communication, causing inconvenience for users

The current implementation looks like this:
and is confusing for users. This should be changed to show scheduled Nests in chronological order. We also previously discussed hiding Nests that were scheduled far out into the future as well. Maybe this would be a good time to implement that as well? By default show scheduled Nests in chronological order for Nests scheduled in the nest 7 days. Anything else can be viewed 'View All Scheduled' in an overflow / toggle button.

When updating profile, use a blaster relay or push to a larger set of relays.

The current implementation will broadcast to the current relay list, which may be a restricted relay set.

Add an option to add a planned room to calendar using OS features or iCal event format

On some devices the chat section is cut off because of browser bars

Support swipe gestures to open/close the chat window on mobile,

The same should be supported for the profile flyout

Add controls to the room audio level (playback)

Sometimes you may need to do something else while keeping the room open so adjusting the room audio volume or muting the room audio can be useful.

Create a BackgroundWorker on the NestsBackend to delete recordings after 72 hrs

A screen sharing function for the host in the nest would be great.

I've mentioned this topic before, but I thought I'd just write it as a feature request in your issue tracker.

I love the new nostr nests anyway

Support raiding other rooms using the raid event

https://git.v0l.io/Kieran/stream/src/commit/364d2c272f327d3572b6884e7f7cab0573f98abd/src/element/raid-menu.tsx#L25-L33

Reactions currently show for a short time on the avatars.

Its easy to miss people reacting so reactions should be more obvious, maybe animate them as rising from the avatar like smoke.

If a user (self) is moved to the stage and has their hand raised, they should automatically have their hand lowered if they are moved to the stage.

Nostr nests is not accepting a valid bunker token.

nsec.app produces tokens that look like this:

bunker://<key>?relay=wss://relay.nsec.app&secret=<secret>

However when pasting this into the "Nostr Address" field and attempting to log in, I get the error: "Not a valid nostr address".

Removing the query parameters did not fix this.

Inspired by Twitch: raiding other nests

how about forwarding visitors of your nest to other nests once you shut down your nest?

I think that's something people would appreciate.