And then move it out of the page.svelte into a component, and we can use it on other pages.
Discussion
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.
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.
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.