nice!! I need to do this as well... are you gonna attempt to move your channels too or just starting fresh?
yeah nothing. just saying we shouldn't cut off an account from its followers after revocation, on the chance that revocation was not done by the user. but don't really have a better solution to offer atm...
we need to make sure that a user still has options if an imposter marks their account as revoked though, right?
maybe favs go in kind 3 and the lists are a new kind? tbh I still don't know how the relay in the tag is used
thats a relief to hear, thank you! next version will be more stable. and hopefully speed improvements with next next version.
then again fav follows could be in kind 3 and other lists are a new kind. might make more sense?
I like this. are you envisioning just using kind 3 or a new kind? I kinda like a new kind as you could use it for other lists, not just favorite lists. then people can make a single fav follows list or multiple lists of follows for different topics
extremely weird, will keep an eye out for that. initial load/reload are slow for any page that queries db (like follows feed). if you can manage to not reload astral is fairly usable, but current version of astral has some errors that kinda force reload (fixed for next release)
https://stackoverflow.com/questions/61865890/run-websocket-in-web-worker-or-service-worker-javascript comments on the issue of multiple tabs with same WSs.
thanks! bookmarked. will be attempting to optimize the db worker for astral in next round of updates
#nip12
hey there, I'm very sorry about ruining the commit history between branle and astral. astral is 100% a fork of branle. this is my first project and I didn't fully think through the git strategy. I will not do this in the future.
branle also uses _@ for NIP05 (it just obscures the _@ when displaying the name to the user). for example the astral.ninja account uses _@astral.ninja
lol i did a lot of interpretations. will have to watch how you implement it
no it won't but again holding off on new kinds in general. even if kind 6=reposts, i still want to be able to render kind 1 events nicely first. not as a standard, just my personal pref. as long as all the same content is available between clients that should be compatible enough