add follow packs to nip51 #1898
Conversation
|
how about having a I'd like to have "Olas starter packs"
cc @callebtc |
What does the |
|
I think it's better use another kind instead of the We could easily have new list kinds for "multimedia follow lists", "multimedia follow packs" for apps like Olas, "short-form video follow lists/packs", "photo-sharing follow lists/packs" etc. I think these categories can be generic enough to encompass different kinds and still specific enough to not be confused with a microblogging app or a recipe-sharing app (for recipes we can have still other lists, once that time comes). |
|
Something is very off with both: the idea of putting Almost all lists right now are based on what people are, not on what or where (which clients) they are posting things. These lists look more like badges than lists of useful posts inside their topics. For instance, I made an Amethyst Devs list. But those guys rarely post about Amethyst, or even development in general. My MedNostr list has all the MDs I know on nostr, but they rarely post about health care. So, if a user wants to hear about health care, it wouldn't make sense to follow MedNostr. I think we need a measure of how good the list is when used in each client for what the user is looking for. That is how we should rank them. Not by whatever the author wrote or which kinds he/she used. |
|
I agree, but I don't see what we can do about it. Most of these packs are useless even when they're made with good intentions like your examples. It's effectively spam and we need someone to curate what lists are actually useful for newcomers -- but notice that the lists themselves are already curations, so we need someone to curate the curations and then someone to curate the curations of curations. |
|
I hereby nominate @fiatjaf to tell each new comer who to follow and why. |
So this iterates back to the content that is shared by the npubs of a follow lists right? So it might be topic (or multiple) related... |
| @@ -57,6 +59,8 @@ Aside from their main identifier, the `"d"` tag, sets can optionally have a `"ti | |||
| | Emoji sets | 30030 | categorized emoji groups | `"emoji"` (see [NIP-30](30.md)) | | |||
| | Release artifact sets | 30063 | group of artifacts of a software release | `"e"` (kind:1063 [file metadata](94.md) events), `"a"` (software application event) | | |||
| | App curation sets | 30267 | references to multiple software applications | `"a"` (software application event) | | |||
| | Starter packs | 39089 | a named set of profiles to be shared around with the goal of being followed together | `"p"` (pubkeys) 8000 | | |||
There was a problem hiding this comment.
Why would these need to be enumerated in nip51 when not all other lists/sets are ?
No description provided.