Anyone else notice Amethyst is pretty crashy in the latest release?

Reply to this note

Please Login to reply.

Discussion

#[2]

Disable public relays for Global and Public Chats. There are tons of spam circulating and amethyst downloads it all if you don't filter out.

Guide for this, please?

Top right corner (stars), put in gray the peoples and global icons for each public relay, then post.

Ok yep that made a big difference

Gotta figure out how to teach people about relays and data usage via UI... 🫤

Can that be made default?

It is for new users. We can't change a user's existing setup, though.

True. Video explaining? Screen recording. Sats paid to those who repost?

To me, I assumed nothing global would load if I don't actually click on global?

Public chats always load because of the notifications icon. Even if you hide/report spammers, events still come.

Would love to have a relay filter to download things that have not been reported/hidden.

It’s a tough challenge. This tweet from #[7] is very relevant to the problem too as we think about keeping people through onboarding. https://twitter.com/anitaposch/status/1626567637575647233?s=46&t=u_05-74uc8hM1IgFMT64NA

True. Without massive simplification and tons of local cache optimizations, it will be hard to use in places with broken connections.

#[8]

Another relay… on it #[8]

Thanks for the h/u Vítor. Any fixes directly from Amethyst on the road map? Damus defaults to only showing paid relays for example

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

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.

Same as bitcoin, we are still early 🤙🏻

I haven't even started :)

Is it normal that one cannot un-like a post?

Yup, there are no take backs on Nostr

But posts can be deleted?

Nope they can't

There's a button for that and there is NIP-09.

It's not a true delete, basically just a delete request as a new event. The relays still have your posts. Not all clients and relays will honor deletes or offer the option.