Should there be a special Blygger RSS spec?

AMMDI Blyg · quoted from v1

(4) scaling issues. eg index.json is defined to include every item ever published. Should I put my 27K published wiki blocks into it? Probably not! But (a) would be cool if I could and (b) if this is heavily used, in a few years everyone will have the same problem.

I had a similar realization about Blygger. 

I had ChatGPT make me a client for Blygger because I already had a site. I wanted to be able to update it as it is, and then fit Blygger onto it.

I realized somewhere around version 0.6 I think that ChatGPT had given Blygger IDs to every single part of the site. That meant that if I made an update to the page where I explain the site or to do my portfolio, that also got a Blygger ID. All published updates went into my RSS. 

That seemed really spammy, so I had ChatGPT modify that for me and limit which parts of the site have IDs and which changes go into the RSS. 

Then I wondered if Blynger was adding the page for every new fragment to the RSS, as well as the larger thread the fragment appears in? It wasn’t, it turns out, but maybe there’s a world in which that does make sense for people whose RSS is attuned to Blygger?

I don’t know how that would work, just floating the fact that working with this new protocol has raised similar questions for me. 

—Brady Dale
October 01, 2026