you should no longer need to nuke astral browser data as I removed the indexeddb (which was the issue). however if images are broken you will need to clear cache storage get the browser to display the images. should be the last time this is needed.
its mostly for my own troubleshooting. main views to use are nostr_events and nostr_users which can be joined by pubkey column (the base nostr table is very hard to use). basic query might be
`select u.name, e.*
from nostr_events e
join nostr_users u on e.pubkey = u.pubkey
where e.kind = 1
and e.content like '%randomstring%'
`
its live. but you need to clear your cache storage for images to get served correctly.
astral images are broken because the cors headers are not getting refreshed!! please clear your cache storage! #[1]
#3 is also in this update actually haha. #2 is definitely coming soon. and prob not doing #1 anytime soon, see here #[6]
hmm sure, not a bad idea.
non persistent browser memory. so loads all your stuff every time. really wanted to make persistent indexeddb work but its too slow.
haha i'm releasing an update rn that trashes indexeddb
any particular areas I should focus on improving implementation? always appreciate feedback
i'm going to allow this for astral eventually and let you filter feed by pow (and other stuff)
thanks pleb world!
the ln metadata fields are on my radar
actually this was exactly my goal!
working on it
many things. currently trying to get rid of indexeddb so that astral is much faster.
no not right now
can you try using http://localhost:8080/ instead? cantillion effect seemed to say this fixed it.
yes bootstrap relays will be overwritten with your previously set relays. bootstrap relays only remain when no relay config can be found for the user (aka new user).