I got your DMs. Just haven't gone through them all yet. Working on a big update. I'll get to it.
Ok it's either cached in NG or loading an old record. I'm looking into it.
Ok I'll take a look and see if it's caching the old badges list. Thanks for letting me know. But if you're not seeing the badge at badges.page then it's gone and it's just a caching thing.
Ah ok. When you click 'Reject' in NostrGram it removes the badge from your badge list. If you refresh the page does the badge disappear? If so then there's a bug where it's not removing it immediately from your list of badges even though it's been rejected.
Haha ok. I know Brave has some quirky issues with NostrGram but that's one I can't duplicate. So I'm not sure what's up.
Gotcha. I'm not able to duplicate the issue in Brave. Can you confirm that it happens with every thread and not just certain ones?
Are you on the Notifications page? If so, when you click Reject does it not put the "Rejected" label on the notification? If so, are you saying when the page reloads the notification is still there? If so, that's a known issue lol. There's no official way to "reject" a badge so I'm working out how best to hide the ones you've rejected.
Gotcha. Very odd, especially since it's persisting after a refresh. I can't duplicate that issue and haven't pushed any updates (working on a big one atm). Same result in other browsers?
Are you saying that the scrollbar is gone from the right side of the page?
Unless something has changed Umbrel doesn't use a secure socket (wss://) but an insecure one (ws://). Web browsers won't let a sight running on a secure connection (https:) connect to an insecure socket.
I'm not able to duplicate the issue using Brave. Does it still persist if you refresh the page? If not some combination of some actions must have triggered something. If you remember what you were doing at the time (or if refreshing fixes it and it happens again) let me know what you did right before it stopped scrolling and I'll try to troubleshoot it.
I haven't pushed any updates. Screenshot?
Happy birthday! ⚡
Ok I believe I found the issue. Should be fixed in the next update coming out later.
Ok I'll look into it. Thanks for the bug report!
NostrGram uses a caching server for performance (and bandwidth saving) that indexes 150+ relays. So it's serving the cached data. By default it uses a web socket for this, but some configurations seem to have an issue with that so there's a fallback to the rest api. A few devices aren't falling back though (not sure why yet), so I added a way to force it to use the rest api.
Have you tried using NostrGram without web sockets? Use this link:
For the folks that have had issues it's usually been the web sockets.