nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

so i have now tested it, with my code working properly, and two things are happening that you might need to look at:

- notification messages don't appear at all with no database mode on and everything coming from the relay - i think the queries are not being made correctly

- messages are also not appearing, again, this seems to be connected to the previous

in general, there is now a minor new bug that the notifications, even in browser cache mode, are not being fetched, except if you reload the app (alt f5/ctrl-R)

i suspect there is a connection between all of them

also, thanks for doing the thing with the database options... not sure i like the layout (don't see why it can't be in the database tab at the top of settings) but it's working and helps with developing relays... when you fix the message/notification queries issue it will be platinum plated epic

nostr:nevent1qvzqqqqqqypzqnyqqft6tz9g9pyaqjvp0s4a4tvcfvj6gkke7mddvmj86w68uwe0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzfmhxue69uhhytndd3jkkafwv3jhvtcqyqgm3lgj0hz5yrjzqt52x00m94gpmc7l4yudhn3njkcyfazl2shnkmajw5p

yeah I've been noticing the issues with notifications and messages. Its not due to the no-cache or in-memory cache options but when you remove the cache it becomes a lot more apparent.

I think its due to how the relay connection and subscripts are handled under the hood. I've been switching out the relay class and it seems to be causing some issues

Reply to this note

Please Login to reply.

Discussion

No replies yet.