Damus
verbiricha · 2w
how does this get through QA? are you guys dogfooding it? nostr:npub1whtn0s68y3cs98zysa4nxrfzss5g5snhndv35tk5m2sudsr7ltms48r3ec nostr:nevent1qgst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqp...
J.G.Montoya.Hodl profile picture
It's still in early development, we noticed a bunch of issues and we know there's many improvements still to be made.

Even with that being the case, the last release is better than the one before it, so there's no harm in releasing.

Next release will be better than the current one for sure. Perfect? Of course not, nothing is. But consistent continous improvements beats "not-releasing because there's bugs" in the long run.
3💯1
verbiricha · 2w
I'm not asking for perfect, every software has flaws and improves over time and I'm cheering for you. But this is something so fundamental and the fact it's badly broken is not a good look at all, specially when we are talking about something as sensitive as e2e encrypted comms. That's why I asked i...
Troy · 2w
Releasing critical defects that cause 100% breakage for a significant segment of users is far worse than holding back until those defects are fixed. The "release early and release often, even if it's dogshit" has never been a good paradigm. Give weight to defect classifications, keep track of your...
Max · 2w
We deliver shippable intermediaries.