Jumble is more stable and with less bugs than Iris, so make sense use Jumble codebase.
nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk please fork nostr:npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9 code and add the features you like on Iris that doesn't exist on Jumble, like the custom feed and other things. I think make more sense.
Discussion
If jumble’s nostr system is better than ndk, one-off fork could make sense. But probably Iris & Jumble philosophy and UI direction are so different that the forks would not be kept in sync.
Yes, but the basics features of Jumble are almost complete developed and working very well. Maybe you could fork and just start customizing according to your desires? But I don't know, I'm not a developer. I'm just suggesting things that make sense for me.
The core of Jumble is pretty messy, it just happens to work :FLASHBANG:
i think it's because it's small so it hasn't got overwhelmed with complexity but maybe you need to have a look at organising it before new features because this last week i've noticed a few bugs creeping in. feeds not loading, some events not publishing (even to only two relays), and a few other quirks.
you would have a good excuse to tell all the feature requesters to shush for a while also :)
yeah, so call this a feature request:
move all of the nostr relay communication code into one directory
It’s all in `/src/services/client.service.ts`, but it’s a bit messy.
I agree of not having new features for a while and focus on bug fixes and usability.
That's exactly what I've been focusing on for the past half year. That’s also why I’ve been putting off some new features.
this_is_the_way.gif
Was this gif to load nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl ?
