exciting day for @tangled.org@bsky.brid.gy and every other git host except for one
all that combined makes me lean against adding collection filtering.
it's a painful no because a bunch of people ask and it would be trivial to implement, but I think it is worth thinking it all through and things coherent.
and, we want to keep the sync interface (aka, firehose API) consistent across services. so anything we add to interoperable relay API needs to be added to PDS, and hypothetical future services which support sync API.
I said "attacker" there pointing out the adversarial case, but even a well-intentioned dev would cause a ton of load. and also have a bad time because filtering the past 24 hours of full backfill will take the relay a long time (for example).
I think there are some arguments for a middle path which retain CBOR and signatures and just have filtering.
but there are big operational costs to filtering: namely that you can easily ask the relay to scan hundreds of GByte from disk with ~zero attacker resource cost
it is also possible to do an "adversarial" PDS migration. this currently requires setting things up ahead of time, and some tech skills, but over time we hope to make this more accessible and automatic/default
www.da.vidbuchanan.co.uk/blog/adversa...
one ambiguity would be "who are the comments intended for". should they be visible only to lexicon designers? if that is the case, i'd do a pre-compilation step.
if they are expected to be visible to app devs, then it feels like they need to be in the schema files themselves, eg using "description"
there has always been interest in having a full-on DSL for lexicon schemas, and if that existed it could probably support comments. I'd estimate that being off in 2027 / AT v2.0 territory, but folks could get hacking/experimenting sooner
I think that from first principles you are maybe correct and we should maybe change it, just sharing history and that it has gone through iteration previously
as a seattlite and unicode appreciator, can't believe I didn't know about 🇱🇸