Sure, I can make some tradeoffs because a bunch of threads will not overwhelm local storage like a general purpose social client would. But I never understood why Primal made the design choice of removing a locally authored message just to show it when it hears back from relays. It could've been done with some other form of UI indicator nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jsppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgmwaehxw309ahx7um5wghx7unpdenk2urfd3kzuer9wchss7kzrc 

 If I had to guess I would say it made it easier to get a prototype out where the main focus was consolidating relays into a proxy backend that gave Primal an edge to clients that were forced to interface with N relays. 

 Layering both approaches makes total sense, but it will take some finesse to balance. Def makes for a more complex implementation.