Just installed coop on my laptop via Flatpak. Timed out with my Amber bunker URL, so I yolo'd my nsec. Then timed out loading DMs.
It looks promising, and it's not on Reya, but nostr DMs are one big dumpster fire.
I dont proclaim the DM problem solved just yet.
That said Coop might be the best today.
nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 takes feedback seriously, and addresses it promptly.
Discussion
100%
I just need to DM to share my signal invite
Absolute shitshow
nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 see amber sign in problem.
https://github.com/lumehq/coop/issues/124
Regarding the DMs loading timeout I thought you fixed this one??
nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 is deep diving
https://github.com/lumehq/coop/issues/104#issuecomment-3226351684
Thank you for your report. I've identified the problem with Amber. Regarding the timeout when loading DMs, the issue might be that Coop failed to connect to your NIP-17 relays, or the user hasn't authenticated yet.
Currently, there are no logs that show users the status of relay connections. I will work on this immediately after I finish other fixes. This is my detailed plan to improve this:
- 1: Coop will fetch the user's NIP-65 relays. If not found, it will ask the user to create them (currently, Coop will time out)
- 2: Coop will fetch the user's NIP-17 relays from their NIP-65 relays. If not found, it will ask the user to create them.
- 3: Fetch all gift wrap events from the user's NIP-17 relays.
- 4 (optional): If NIP-17 relays require AUTH, Coop will show a popup to require the user's action instead of silently processing (current behavior).
cc nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5