it should prompt you unless you are using private browser. it always prompts me when i run on localhost.
thank you for your understanding and patience! welcome to nostr!
next version will not use indexeddb which should be much better
i would love for as many people to run locally as possible. my prod server is also debian based and not having any issues. but also building from remote context.
I think the big problem is indexeddb (used currently) takes forever once it gets too large. I am going to switch to using session storage instead which is way faster, but not persistent.
will leave using indexeddb as an option incase anyone wants persistence.
yes should work on firefox. last time I checked firefox seemed worse but haven't check again since cleaning up some UI lag. this person seems to feel that firefox is better than chrome rn #[3]
yes, if you click on the 'not seen' icon in the relay list it will attempt to publish that event to the relay. however this does not guarantee that the relay will successfully save it.
opposite for me, but got an old pixel and new mac. both mobile and desktop need much improvement though really. I have an idea, hopefully it will work.
and after you set your color preferences you are sure to hit the save button at the top of the preferences section? if you key is getting saved there shouldn't be a problem with the colors
this is weird, shouldn't get wiped. is your key getting wiped every time too (aka do you have to login every time you load astral)?
yes. but also astral is much worse than the average chrome tab processing wise
no i don't recommend it for mobile browsers rn. still working to make mobile actually usable.
am working on solutions to both these things. gif one may take a little longer.
hey its really weird you are getting this error, I run it locally all the time and there were no fixes for this error (bc i've never seen it). whats on github was run in prod no problem. will take a look and get back to you. debian seems to be common thread
local may be a bit faster.
it depends on how the client handles content parsing. it renders as an image on astral
no, but also haven't gone looking for them. any caching issues in particular I should be on the lookout for?
thank you! it was suggested by someone on nostr and thought it was a good idea. but cant remember who 😞
damn til about bold unicode char. was baffled by lack of markdown in content.
hahahah this identifies which tag of the post is being mentioned. if client doesn't support parsing it will look like that. this is the NIP about that convention: https://github.com/nostr-protocol/nips/blob/master/08.md