Open jblachly opened 1 year ago
Right now this portion is kind of is in development; in that it combines two or three types of rooms:
a) public channel of kind 4x, which is what the Heidelberg room is b) #t tags like #work etc, which are actually kind 1 messages with that particular tags, shown as 'rooms' c) #location tags with values such as usa, india, which are also given their own rooms.
So over time this can and will be improved, but right now I am not focusing on this; in that I am still waiting for some ideas about how to show or do this. Want to change code only after some idea about how useful these tags rooms are.
Also note that all these rooms ARE sorted - by the latest event in each. So rooms with a later event will be at top.
As I use it, if you know a room, you can just type its first four letters of id, or few words in name, and you will get into it. Also shortcuts to public rooms can be created ( on linux in this case) using this.
As I use it, if you know a room, you can just type its first four letters of id, or few words in name, and you will get into it. Also shortcuts to public rooms can be created ( on linux in this case) using this.
Thanks -- one current usability issue with above is that partial match overrides exact match. Namely, if you try to join "Nostr" (the largest channel, in my list above), it fails because that partially matches other names. It can only be joined by id. Substring matching will become a bigger problem the more channels are created with common terms.
Preferably, total number of messages, but optionally, by some other field such as name or timestamp of latest message.
Example below in which lots of the spam single-message groups obscure larger groups like "Bitcoin Heidelberg"