To Blygger discord this hopes to turn into a thread

From Blygger

To Blygger discord this hopes to turn into a thread

A few random thoughts

(1) the technical design values of Blygger seem very old-school, Web 1.0 (not meant as criticism or praise, just an observation). No more centralized platforms, everybody acts as their own publisher of static content, the way Tim B-L would have wanted it.

(2) the user level design values are explicitly biased towards a particular model of communication. I'm not sure I share those biases, but it's your design so not going to argue about that (unless you want to). But it raises a kind of meta-question about protocol design, should something at this level be as general as possible (which probably would help adoption) or tuned to particular use cases?

(3) The [tk] stuff is neat but seems mostly orthogonal to the rest of the protocol. It could be split out as a general markdown/html extension.

(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.

Created Oct 1, 2026 · updated Oct 1, 2026 · v2

JSON · Blyg