I will pay 1M sats to anyone who fixes this bug:

## Fix Flotilla network bug

Here's the [github issue](https://github.com/coracle-social/flotilla/issues/118) of the bug.

Make an offer on this URL:

https://satshoot.com/nostr:naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqsuamnwvaz7tmwdaejumr0dshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsq86xd9uz63nvda6xjmrvvykkuet5wahhy6edvf6kwtt2wgm8z7t203ytjg

#satshoot #asknostr #flotilla #welshman #bugfix #networking

Reply to this note

Please Login to reply.

Discussion

The URL returns a 404

Thanks, will fix that shortly

In the meantime, just remove the "nostr:" prefix from the url

What files handle:

Relay connections

Subscription management

Any connection retry/recovery logic

Event handling code

Any cashing/indexedDB implementation

[Welshman](https://github.com/coracle-social/welshman) lib, that flotilla is based on

And what files exactly in flotilla are handling these things:

1) Your app may not be resubscribing after a refresh or session timeout. Try explicitly closing old subscriptions and re-opening them

2) If relays become unresponsive, you might need a retry mechanism

3) Relays may be timing out too soon. Try increasing the connection timeout

4) If old events load from IndexedDB but not the relay, try forcing a fetch

I could not fix the issue in the time frame I could dedicate to this.

Now I'm paying others to figure out the details.

404 error on deployment.

What ever is going on I'm wishing you the best of luck!

Thank you!