nostr:nprofile1qqst03hkj9w04xnzllm2rupxqn0g3s3ud3kx6xu0vtrucyr5nuc8aqgpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgewaehxw309a5xzan9dch8xmrfv3jhxarj9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uhtjwuq when there's any error (404 in this case) all syncing stops. I'd assume that bouquet sync would just continue and sync what it can? 
Discussion
Yeah, it’s quite buggy … I’ll need to look into it
nostr:nprofile1qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyphydppzm7m554ecwq4gsgaek2qk32atse2l4t9ks57dpms4mmhfx5ltf6v I have fixed the error handling. It looks like primal.net keeps blobs in the listing even after they have been deleted. I also have some 404 entries.
I also listened to the No Solutions with Hrzd episode. I agree that an offline archive tool would be great. Since blossom servers usually require upload authentication the process will at least require a bunker for signatures or a separate NSEC for the archival tool. That's where bouquet's browser approach is limited in terms of background operations.
Yay! CC nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uq35amnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6tc4uevew and also nostr:nprofile1qqsypwwgtll74lqu4huvxzjwtjyxvrlkujt35rw8y026ke6ttesmg5gpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7qg5waehxw309amk7apwdehhxarj9ehx2ap0dxsk92 because he is actually working on the nostr pacemaker thing
On it 🫡