The concord spec changed a month ago to deal with those limitations. So the communities you join are now sharded on armada and vector. At the time you did not want to update amethyst. Now that means pretty frequently people wonder why their communities from Armada do not sync correctly. And we have to explain its because Amethyst never updated itself to the newer spec.
So amethyst not only doesn't get the proper channel sync, it also is subject to the limitation issues that change solved to begin with.
Once you implement the sharding kínd 33302 instead of sticking to 13302 you are in line with the spec again so people dont miss channels and dont risk issues with their community list.
https://github.com/concord-protocol/concord/commit/759448ab637abd2ccabe1026b8f8ad80569cfea5
:H::e::n::k::y:!!
npub160…x889v
2026-09-29 12:26:44 UTC
in reply to nevent1q…y0xv
Author Public Key
npub1600yr4qg5vcfp7svf6ysj0008tn7aphnu0gjs6lw5hjn74n0laasjx889vPublished at
2026-09-29 12:26:44 UTCEvent JSON
{
"id": "a8f83666dc513833a9a4d87db6630da089fd3f9734d7a30d7b7358a20f84896d",
"pubkey": "d3de41d408a33090fa0c4e89093def3ae7ee86f3e3d1286beea5e53f566fff7b",
"created_at": 1790684804,
"kind": 1,
"tags": [
[
"alt",
"A short note: The concord spec changed a month ago to deal with ..."
],
[
"e",
"dd50c4582599e6868ca5da887b74b97740f7d906b29eef8e021d8286f59a8c07",
"wss://nos.lol/",
"root",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef"
],
[
"e",
"a74ec4ebd5864d1d5cb6a93e7028aef6169a1713544628ea0b788ac4362b9a4c",
"wss://relay.primal.net/",
"",
"d3de41d408a33090fa0c4e89093def3ae7ee86f3e3d1286beea5e53f566fff7b"
],
[
"e",
"000000587b1f5284c27427dea26f971a7e3093a1956f3ac34904aecd336e17f2",
"wss://nostr.mom/",
"reply",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"75d737c3472471029c44876b330d2284288a42779b591a2ed4daa1c6c07efaf7",
"wss://relay.primal.net/"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef",
"wss://nos.lol/"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"wss://vitor.nostr1.com/"
],
[
"p",
"d3de41d408a33090fa0c4e89093def3ae7ee86f3e3d1286beea5e53f566fff7b",
"wss://theforest.nostr1.com/"
],
[
"r",
"https://github.com/concord-protocol/concord/commit/759448ab637abd2ccabe1026b8f8ad80569cfea5"
],
[
"client",
"Amethyst"
]
],
"content": "The concord spec changed a month ago to deal with those limitations. So the communities you join are now sharded on armada and vector. At the time you did not want to update amethyst. Now that means pretty frequently people wonder why their communities from Armada do not sync correctly. And we have to explain its because Amethyst never updated itself to the newer spec.\n\nSo amethyst not only doesn't get the proper channel sync, it also is subject to the limitation issues that change solved to begin with.\n\nOnce you implement the sharding kínd 33302 instead of sticking to 13302 you are in line with the spec again so people dont miss channels and dont risk issues with their community list.\n\nhttps://github.com/concord-protocol/concord/commit/759448ab637abd2ccabe1026b8f8ad80569cfea5",
"sig": "54a9cc3854e7e04eb8a0b0338471f9164afd72a1b39f47aa27f811d0f8bc41b05500e08530d39114fa6a62b2eb71cbb2c34db4d98c158f8910d31a95f8f0a4e1"
}