Gossip / Default theme users: the new indentation's design helps you to visually follow long/deep discussions?
Any request/suggestion about this?
However this is a middle-step, the final version should have a more "continuous" thread style.

Gossip / Default theme users: the new indentation's design helps you to visually follow long/deep discussions?
Any request/suggestion about this?
However this is a middle-step, the final version should have a more "continuous" thread style.

Thread style would be better. I hate how Amethyst renders replies for example. It makes it hard to follow a conversation.
Treading design on mobile is hard.
I think the best mitigation could be the possibility to collapse sub-treads; this way you can easily skip to the next one. /cc #[0]
But what about Gossip? :)
Haven't tried it? Does it run on Android? Right now I'm using Iris on PC and occasionally Amethyst on Android. Not at all impressed with Amethyst TBH. Iris in web browser is great though.
Gossip is a native desktop-only client.
Check it: https://github.com/mikedilger/gossip
Prebuils releases a bit outdated (2/3 weeks ago) and the development is quite active, so the best option is to compile it from source (quite easy on a *nix OSes, using cargo).
Iris is great but I don't like very much the not-nested thread visualization; it can be a necessity on mobile but on desktop there is plenty of space to have a more structured navigation style, like Gossip is trying to achieve.
How do I impress you?
Please don't change Amethyst thread lines... Many users are used to it because of Reddit.
I agree #[0]. Amethyst have a nice threading design, despite the limited screen estate.
I hate it.
I prefer the way Iris does threads Twitter style.

It definitely helps! Following threads on most clients is a nightmare.
π Clients will take care of this as soon the conversations will grow, and this will happen fast :)
It looks good. I like the numbers.
I just wish that Gossip could reliably find the threads. Very often I click on on of @jacks' conversations and I cannot see the source. Is this a relay problem or a protocol problem?
Thanks.
What you refer happens when you don't read the user's writing relays. Gossip use a particular approach instead of reading casual or as many as possible relays. It doesn't always work perfectly currently, but seems the best one approach in the long run.
Read this interesting article by #[0], the Gossip author: https://mikedilger.com/gossip-model/
Quick and dirty solution: search the user note on nostr.band, and use the "Seen on relays" to find out where it is currently present; do the same with some historycal notes and find out if he is posting on some relays that you don't have in your Gossip list, then add them.
When you access the user profile in Gossip you can see the commons relays.
Thanks for explaining. It seems like a problem that needs to be fixed eventually.
Ngl I fw it gonna give it a try π«‘π
Yes! I love Reddit-style threading.