A candid update on the new nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 app:

The entire thing was rewritten from scratch to address various issues, this time with a sound architecture. On this new foundation, I was able to develop some very requested features which are basically finished.

Last week I was ready to announce an alpha version for testers, excited as this would start the culmination of months of work. Then, I detected an anomaly during relay reconnections. Turns out the websocket pool implementation had several major flaws, in short, it was a mess. So the LLM agent and I decided to rewrite it. Unfortunately I am still having trouble, as it can't really figure this stuff out and my motivation is to debug websocket connections is at an all-time low.

Between my own internal pressure and constant user demands pulling me in all directions, I need to balance things not to approach burnout territory. Running a project like Zapstore is not for a solo developer, much less for me at a point where low-level coding literally feels like a waste of life.

That said, I'm incredibly bullish on Zapstore. With big tech closing it claws, the world needs an open bitcoin-based app marketplace more than ever.

Two options moving forward: finish frying my brain on an isolated downspiral, or move toward a place that rekindles my motivation: making Zapstore grow. I will surely find a team and a way to sustain it long term.

While time is our scarcest asset, I know this can't happen overnight. But eyes on the prize. Thank you for your attention to this matter, if you'll excuse me I now have some websocket logic to take care of.