True but Amethyst is the worst for me

I’ve been working on optimizing my apps resources and it’s easier said than done. The architecture is the issue and not so much the developer. No matter how you slice it, backfilling locally cached events triggers high memory usage and strains the battery.

In Amy's case, because of some odiities in how it fetches notes. Like I can have all media off and it'll randomly use a gig of metered data. I can't open it out of the house.

As much as they criticize Primal for their cache relays, I suspect that it helps lower bandwidth. One major problem with folks who have tight bandwidth plans complained about Nymchat using too much was due to all the simultaneous relays connected. It wasn’t until I built out a relay proxy (sort of similar to what Primal uses) where it could then dedupe events server-side, did the high bandwidth use drop. And then even more, I rolled out a low bandwidth feature to cap the maximum connected relays by the proxy. And still, the bandwidth use could be high for someone in a disenfranchised part of the world where they may only have access to ~1GB data for their plan each month. It has been an interesting challenge.

I would love better SVG support in the clients for things like charts - it’s a very space-efficient vector format View quoted note →