Nostr Web Client

One year ago I proposed a "stacked users" design/UX (note mentioned at the bottom of this note). It was appreciated but I didn't see any real implementation of it, so I finally decided to build it on my own, but instead of creating yet another nostr client, I picked Jumble and added it as a new "Grouped notes" mode:

Main features:

- Pick a custom timeframe (default 24 hours)

- Filter out users that posted more than X notes; useful to surface users that post rarely

- Switch to compact mode to have a RSS-like feeling, to the delight of nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

- See how many other notes the author published in the selected timeframe

- Compatible with the built-in filters

- Works also when browsing specific relays

I've been using this mode in the last few days, and I really like it, especially the compact version, since it offers a clean interface without any doom scrolling temptation. It also is letting me discover interesting content and users I forgot I followed that, for a long time, remauned hidden behind the more active ones on my list.

Try it yourself at https://grouped-notes.dtonon.com

And give back any feedback, thanks!

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl should I open a PR? :)

nostr:nevent1qqs0v4t44mw794pajrzzsmrlleu08x9q69akvg6ccwhygga542cz40cprfmhxue69uhkx6rjdahxjcmvv5hxgar0dehkutnrdakszrthwden5te0dehhxtnvdakqzyrhwden5te0dehhxarj9e3xzmny39ygr8

idsera 3mo ago

Great idea, I really liked it. Some suggestions:

1- Add an option on users profile menu to prioritize showing some users on top of the feed. These profiles could have some signal on feed indicating that they are "important".

2- If I choose 24 hous and the user have posted like 8 notes, when I click on 8, should show only the 8 notes or show the 8 notes as unread. Would be great to have an option to mark all as read, so this user on feed will be hidden until the user write a new note.

cc nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl

Reply to this note

Please Login to reply.

Discussion

fiatjaf 3mo ago

Great ideas.

idsera 3mo ago

And I think it's time to have custom feeds instead of this grouped thing that works like a filter. So we could create a new feed for grouped one with custom options and that doesn't disappear when we refresh the page, something like what Iris client does.

idsera 3mo ago

* doesn't reset when we refresh the page,

daniele 3mo ago

This is a completely different topic. I also want lists (kind 30000).

Cody 3mo ago

We first need to address the performance issue, right now this mode becomes very laggy when browsing relays with lots of content or when a longer time limit is set. Since it loads all notes within the time window, it can even trigger the relay’s rate limiting. I think we may need to remove the time limit and instead load a few hundred notes at a time and group them.

Laeserin 3mo ago

Time is the essential factor, tho. It's a time-span group, rather than a continuous timeline.

daniele 3mo ago

I also thought this initially, but actually the time-span group is browsed in sequential chunks, so we can lazy loading them.

The only cons of this i approach seems that you cannot have the real total count for every user of all the published events.

Silberengel 3mo ago

Wait, I'm confused. I thought you were fetching all follows from last X hours into a map in cache and displaying that, with lazy-loading in the rendering step, when someone clicks on an entry.

How does this work?

daniele 3mo ago

It's like that, but for long ranges, e.g. 5-30 days, I actually can load only the events necessary to fill the viewport and permit some scrolling. So I have to query all follows, but for a limited time-span, and then load more in chunks.

Silberengel 3mo ago

Ah, okay. I see.

Silberengel 3mo ago

This is really good, by the way. I'll host it on my https://jumble.imwald.eu .

Silberengel 3mo ago

An AUTH aggregator like aggr.nostr.land really shines with this view nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj as you can deliver big data fast without triggering rate-limiting.

Silberengel 3mo ago

This actually helps frequent posters, too, as you can filter them out, temporarily, instead of muting them. Even if you only used this view, they'd reappear during times when they were quieter.

Laeserin 3mo ago

Just query them all in parallel and populate the map, as the results come in, with a 30-second timeout.

Laeserin 3mo ago

And have most kinds deselected, by default. Limit it to kind 1, with a "see all results" toggle.

Most people who post infrequently, use kind 1.

Cody 3mo ago

According to nostr.band’s stats, there were 20,670,324 kind 1 events in the past 24 hours.

Laeserin 3mo ago

But what are the chances that they all came from someone's followers?

Cody 3mo ago

This feature isn’t limited to the following feed.

Silberengel 3mo ago

Ah, I oversaw that. Thought it was for following. 🤔

It would work well on TheForest 🌲, but if you did it on band, it'd be a bunch of garbage.

Cody 3mo ago

Yeah, for now TheForest should be fine. But once it grows bigger, problems might show up.

daniele 3mo ago

1. Favorite/sticky users is an interesting idea; Jumble already has public/encrypted mute lists, so it should be pretty easy to implement.

2. I was already thinking about a read status, but the implementation is a little trickier, you should save a timestamp for every follows.