Replying to Avatar Laeserin

nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn what do you think about those changes? Do they seem intuitive? And did you notice anything weird?

I mean, weird, other than the fact that the filter boxes are the wrong color. 🙈

I haven't tried them out yet 😬. Been focused on the ToC.

Reply to this note

Please Login to reply.

Discussion

No, I mean what I described in this thread, as changes to the state in the video.

* Mutliselection in the drop-downs

* Add a relay filter drop-down

* Add more fields to the search (authors, tags, etc.)

* Remove empty lists from the drop-downs

* Move more-popular tags up the list, and fix the length and add a scrollbar

* Have the drop-down color match the theme

* Shift blank/unknown authors to the bottom of the sort, so that it always starts from A or Z.

And then move it out of the page.svelte into a component, and we can use it on other pages.

Oh yeah those should definitely be on a component rather than the raw +page.svelte.

That will both make it reusable and leave our +page.svelte files focused on routing and loading logic, rather than UI internals.

Same component would be useful on the social feed. That's a one-card, chronological feed, but the controls allow you to sort and filter and search that feed, completely changing the way you can interact with it.

I'd make the table look like Reddit, maybe.

Also useful for article page, of course.

Events page is a narrow specialty, but uses the same search bar component.

And the Wiki page will be the SEARCH AND FIND ABSOLUTELY EVERYTHING ABOUT EVERYTHING FROM EVERYBODY page, where we can throw everything and the kitchen sink at the search bar. 😂 That'll be fun.

Yes I want Alexandria to be the place people go to search Nostr. Like the Google of Nostr.

Actually, now that I think of it, we could set up a search URL such that people can add Alexandria to their browsers as a search engine.

I just wrote up a user story for this in our OneDev. Threw it in the Euler release backlog for now.

I just wrote up a user story for this in our OneDev. Threw it in the Euler release backlog for now.

Reddit-style table is just using relay/community grouping, and allowing upvoting/downvoting ⬆️⬇️ reactions to change the display order within a group, right?

I vibe-coded a prototype for that, a while back, to think through how it would work.

Grouping by list is another idea. A sort of impromptu community.

Group by list and maybe group by relay, in addition to the others.

Then some items would appear mutliple times, but that's okay.

Yeah I think that is acceptable.

Yep! With each entry in the table showing the title, author, and part of the OP.

We could do title, author, and a brief summary, all grabbed from event tags.

Yes, grouping gives us more room for the summary.

* like *

The main difference is that the social feed would use the filters as weights, rather than limiters. So, if you selected Follows or Favorites or whatever from the list, it would pull those to the top, rather than getting rid of non-matches.