Oddbean

I'm ok with that, I decided to work on foundational tech like a new database and a new relay model which should drastically improve damus ios performance. notedeck is a bit of a testbed. it may look like I have shifted focus but all of this tech is meant to be integrated into iOS.

In fact, I have a 116 commit PR that does just that! https://github.com/damus-io/damus/pull/2121 then all of the cool notedeck tech will be available on iOS. the idea that damus ios has been abandoned just because I'm not incrementally adding to it every week is kind of silly. that's just not how engineering works.

That’s fine ! It’s open source environment and you work on whatever you want too and you aren’t obligated to anyone ! Just want you to be a little bit honest to the normies who don’t see it and maybe should start trying other mobile clients that outperform damus

this is actually the lifetime struggle of a backend engineer. it's easy to just slap on lipstick onto a poorly designed engine, but its not going to make it perform better. maybe new bells and whistles every then keeps users happy, but it's not going to ever change the game unless you throw out your original prototype and build it right. this is what I've done with nostrdb and notedeck, and I've designed it in a way so that I can backport it into iOS. it just took a year or so to build a database from scratch and prove out the new model/prototype. feels a bit like building a game engine from scratch... lots of upfront work but it will be so worth it. It will be the foundation for every damus client going into the future. I feel much more confidant building on top of this new tech than the original iOS prototype. I didn't really know what I was doing when I made Damus. damus is one of the oldest clients in active use, and has accumulated lots of cruft. It doesn't even work in the outbox model. The new local relay model makes the outbox model possible in damus, which has been damus' biggest criticism. but yeah, sometimes its hard to explain all this, so I'm ok with people saying I suck in the meantime. it's probably too hard to communicate why I'm doing what I'm doing, but I'll keep trying!

As a backend engineer in the corporate world, I feel this so much. It's so hard to sell to corporate people (non-engineers) stuff that could improve the codebase and thus both efficiency and maintenance cost over a longer time period. I've said it many times before and I'll say it again Will, keep pushing like you've always done. It's easy to notice the hate but try to also notice all the positive feedback you get, because I see alot of it.

doing things properly makes all the difference in the long run even if it seems like the deadline is breathing down your neck every day, every shortcut tends to give you more delays and more bugs, when doing it right would have seemed longer at first but builds momentum nostr:nevent1qvzqqqqqqypzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qqs8cp09j4d2ta9p0yjag9d7n09f3gs7tja6rdcjqueu39g6d5nlt8g4qfd4d

@Compromised There is not a single iOS full time dev, although iOS damus is fortunate to have a most time dev, and a couple intermittent part time devs. PT devs have serious full time jobs elsewhere. One of the reasons @jb55 is tackling non-iOS is that apple throws cold water on any boundary pushing tech (e.g. zaps). There is a ton more to be done to bring freedom money to millions, and relying on how the appstore bureaucrats are feeling on the day of the damus review is foolish based on their 💩 treatment of damus devs (they cant even grant basic functionality outside zaps, and provide no explanation). When team says we hear all the feedback - we do, and we know it painfully well. The reality of limited resources is that we must prioritize, as we dont have a VC funded full time team of half a dozen to a dozen devs. iOS will have to brace for the full nostrdb update as well. This means performance/under the hood upgrades at the cost of everything else to be worked on.