cheers nico! 2022 was a crazy ride, can't wait to see what 2023 brings... thank you to you and all nostr plebs for believing in a better way forward!
yes. this one finally actually tagged the directory.
i think the only chance to prevent this is to go down the pow route
no one planned for email to become centralized, but its what will inevitably happen if there are no alternatives to spam prevention other than coordination
hey this still didn't tag the directory account properly which is the issue. not sure it will when you just past in @pubkeyHexId. try manually tagging the directory user by using @ and selecting from the menu (rather than the #p) or pasting in their npub id
this is fixed now
test
hahah
oof need to handle invalid tags better. thanks.
it loads on brave pixel 3 for me. you do have to give a few seconds to render on initial load, but it should load. after initial load it should be more responsive.
appreciate that! but will prob keep a simple background. trying to keep all astral graphics minimal and clean.
oh duh of course this is what you meant. yes I should def do this. thanks.
my setup is pretty rudimentary so not sure if there is an easy way to enable a splash screen.
this is a great suggestion though. agree this would be nice to have.
I will try to keep an eye out.
sql would definitely be useful relay side, but I think main focus would be around speed as the Nostr event data structure is pretty straightforward.
thank you!! glad updates are having a tangible effect!
free likes aren't coming to astral
paid likes will come but are lower priority than media integration.
yeah. I think there should only be one e tag for root though though (since its a reply to a quote the quote event should be root)
ah well its also a bug in astral.
specific to astral. some of the columns that astral adds are also non-standard per nostr spec (like seen on, first seen, and last updated) but are stored directly on the event in raw nostr table
uhg sorry about the npub key not parsing guess I need to fix that.
two views you should use are nostr_events and nostr_users. you can just select * them to see their columns. they join on pubkey. the base table is nostr but its hard to use bc everything is stored in json.