We must have follow lists for each kind. The kind 1 follow list is different than a blog post follow list. So, all of your options are wrong. :)
Other kinds should never be rendered as root posts on kind 1 clients. But kind 1 clients must render or forward them when they are quoted into a kind 1.
Vitor Pamplona
npub1gc…fnj5z
2024-10-26 21:19:22
in reply to naddr1qq…d9ah
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-10-26 21:19:22Event JSON
{
"id": "68ab92deb6f36febcbaaa9cc1be22819827e6a25f6b1fed23164f87b8ff4be36",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1729977562,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"a",
"30023:3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d:cd8ce2b7",
"",
"root"
]
],
"content": "We must have follow lists for each kind. The kind 1 follow list is different than a blog post follow list. So, all of your options are wrong. :)\n\nOther kinds should never be rendered as root posts on kind 1 clients. But kind 1 clients must render or forward them when they are quoted into a kind 1. ",
"sig": "65b1bb0acd37e64a0f59999f35f6d8d4683e5d63aa651d6ed2e42065c5709bada6b670183a1338d3cec3134464c05e2da1cad5a6901490ac0da566f8a0edaac1"
}