I find its bad when you go to peoples profile page and they have a lot of followers. Over 1000 followers and it can crash easily. But other than that mine doesn't crash very often
Discussion
Yep.. i will disable the follower count in the next version
Funny seeing clients go through the exact same pain points damus went through :p. I made it click to load. Will probably have to make it paginated eventually
Same will happen for Zaps when the amount becomes too big.
Seems like Damus already only displays zaps on a post after you click on it. Thought it was odd at first but it makes sense.
Posts should be fine. User profile will be a problem.
Huh, why does the profile cause more of an issue than the timeline? Just because zaps are highly concentrated on some users?
When you load the user's profile it loads all zaps, for all posts that were ever sent by that person.
is it b/c of sig verification overhead? or something else?
Imagine downloading all zaps that were ever sent to the person or any post of the person. It's similar to downloading 1000s of followers to display in a list.
i see - so its a bandwidth issue for sending the zaps, not an event signature verification issue. im asking b/c the latter can be efficiently amortized w schnorr
Definitely need local caching on these. Will be nice if you could have them all locally
Ahhh you’re trying to tally the total amount zapped to that person? I wasn’t understanding the reason to do that at first. I need to try to find a way to run amethyst to test it out
It would be so nice to be able to choose the amount to zap to posts like in other clients works, I could choose it in snort and iris to any amount. That would be awesome.
