Khatru doesn't have any restrictions on by default so it depends on the relay operator.
But wait, what is the size of these a-tags? An a-tag should generally never be bigger than 5+1+32+1+16=55 characters, so 80 is a pretty reasonable limit, no?
khathru NIP-29 relays are rejecting events that have a-tags due to a very strict "large tags" policy: https://github.com/fiatjaf/khatru/blob/d4334ac2bb863503cc6348894027461b6d8d4088/README.md?plain=1#L76 one use case I had in mind was to be able to share groups in chats by referencing their metadata event which is replaceable but this prevents me from doing it.
could we relax this nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7 nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl or should I only include text references on the content?
Khatru doesn't have any restrictions on by default so it depends on the relay operator.
But wait, what is the size of these a-tags? An a-tag should generally never be bigger than 5+1+32+1+16=55 characters, so 80 is a pretty reasonable limit, no?
I see, but aren't hex pubkeys 64 characters long instead of 32? If so only 9 char remain for group id. 0xchat relay seems to be generating some big ass group ID's that are 64 characters long, groups.fiatjaf.com and relay.groups.nip29.com generate 10 char IDs so I can't a-tag those either.