Because of what? Event size? We don't operate relays. I am confused..
Login to reply
Replies (5)
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.

GitHub
CORD-02 §8: shard the Community List, and shrink what it carries · concord-protocol/concord@759448a
A real 43-membership List serialized to 50,113 B and encoded to a 76,868 B
event, past the ~64KB most relays accept. §8's guard measured NIP-4...
But that was just for community lists, right? Are people having more than 64KB of community headers already? That sounds crazy. What do you do in messages that are bigger than 64kb?
Some people indeed hit community lists that big which was why they did the sharded one. Point remains that even if you dont find it neccesary you being behind on the spec still causes issues. I don't know what armada does when it encounters a changed 13302. But it doesnt actively update its 13302 anymore so amethyst is left out on any community list updates.
That the same issue for follow lists and people lists in nostr.. I will implement the sharing, but to me that doesn't solve anything since messages cannot be big. I have seen more people losing messages than losing lists, by far.
Which other clients are active these days that I can test with?