i'm going to cap the limit at 10 event mentions per post, and not render nested reposts/quotes. so potentially 10 queries to the db plus 1 query to relays for 10 event ids. not ideal but imo its worth the usability it brings.

yeah just the normal released app (but the type of wallet you create is different I believe). if you go to the connect wallets section of umbrel there are directions for wallets you can integrate with. so far the directions have worked pretty well for me.

err could this break bitcoin

ah yeah i had to make updates to fetch adhoc events when it encounters a repost or quote

kinda in the same boat as you. one thing i did was enable a bluewallet lightening wallet that routes through my node (instead of bluewallet). on chain, a lot of wallets will let you connect your node as the back end so no one can snoop on utxos you query

why not always show preview for quotes and reposts?

this is prob true. but right now generating counts is lower on my priority list. i would also say you can extract all the same info just using kind 1 (even if it isn't very streamlined)

for sending from astral, all event mentions (reposts and quotes) will need a tag anchor in the content. only reply events will not need a tag anchor. for reading, astral assumes first 2 unanchored event tags are reply events, rest are interpreted as event mentions.

this is exactly the logic im using for this. 'reposts' and 'quotes' (what i'm calling them) are the same, except repost's only content is the tag anchor (which I remove on display). kinda janky but works well enough. i'm displaying a preview on all reposts and quotes by default

test mentions still work #[0]

🙌🙌🙌

quote test #[1]

#[1]

hey fyi looks like you tagged my pubkey twice on this one

(yes)

jb! thank you for the amazing test cases!

yeah, still need a better way to insert the newly loaded events though...

reply with unrelated mention #[2]

https://astral.ninja/ has a global timeline which can help. still not easy in early days of nostr.

reply with mention #[0]