{"updated":"2026-10-01T15:33:59Z","content_md":"From [Blygger](https:\/\/ammdi.hyperphor.com\/Blygger#6abbeb5e-9eed-4752-a5bc-ba7bf718873f)\n\nTo Blygger discord  this hopes to turn into a thread\n\n![[773a45yceyqt6xdcsfpengkmbz]]\n\n![[27yv9b5tbv4hkwpw5jvh98z3jx]]\n\n![[6xk6mcjjxc0ewr269fxyx7ypxh]]\n\n![[2mj2ymcsnbxcvcx50e8j6adpdf]]\n\n![[10fdvqqfed8ce0zr7wd5yk90pj]]","changelog":[{"version":1,"at":"2026-10-01T02:51:38Z","note":null},{"version":2,"at":"2026-10-01T15:33:59Z","note":null,"pinned":true}],"transclusions":[{"id":"773a45yceyqt6xdcsfpengkmbz","version":1},{"id":"27yv9b5tbv4hkwpw5jvh98z3jx","version":2},{"id":"6xk6mcjjxc0ewr269fxyx7ypxh","version":2},{"id":"2mj2ymcsnbxcvcx50e8j6adpdf","version":2},{"id":"10fdvqqfed8ce0zr7wd5yk90pj","version":2}],"created":"2026-10-01T02:51:38Z","page":"f\/20wddcba341k7n9qjyb7mqpyn7\/","content_hash":"sha256:9580cbe853decb781dfc73ed6a4fad913600ce9fd6d4b056244d3fca5e598fea","id":"20wddcba341k7n9qjyb7mqpyn7","kind":"thread","origin":"https:\/\/ammdi.hyperphor.com\/blyg\/","content_html":"<div><p class=\"source-page\">From <a href=\"https:\/\/ammdi.hyperphor.com\/Blygger#6abbeb5e-9eed-4752-a5bc-ba7bf718873f\">Blygger<\/a><\/p><div><p><span>To Blygger discord  this hopes to turn into a thread<\/span><\/p><blockquote class=\"blyg-transclusion\" data-blyg-id=\"773a45yceyqt6xdcsfpengkmbz\" data-blyg-version=\"1\"><p>A few random thoughts<\/p><\/blockquote><blockquote class=\"blyg-transclusion\" data-blyg-id=\"27yv9b5tbv4hkwpw5jvh98z3jx\" data-blyg-version=\"2\"><p>(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. <\/p><\/blockquote><blockquote class=\"blyg-transclusion\" data-blyg-id=\"6xk6mcjjxc0ewr269fxyx7ypxh\" data-blyg-version=\"2\"><p>(2) the user level design values are explicitly biased towards a particular model of communication. I&apos;m not sure I share those biases, but it&apos;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? <\/p><\/blockquote><blockquote class=\"blyg-transclusion\" data-blyg-id=\"2mj2ymcsnbxcvcx50e8j6adpdf\" data-blyg-version=\"2\"><p>(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. <\/p><\/blockquote><blockquote class=\"blyg-transclusion\" data-blyg-id=\"10fdvqqfed8ce0zr7wd5yk90pj\" data-blyg-version=\"2\"><p>(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. <\/p><\/blockquote><\/div><\/div>","version":2,"media":[],"blyg":"0.3"}