3 ms·

The Indie Web movement is a very interesting one, I personally support some of their goals, however, the protocols they design seem a bit... too uncomplicated a

by tscs37 9y ago

The Indie Web movement is a very interesting one, I personally support some of their goals, however, the protocols they design seem a bit... too uncomplicated at times (Microformats2 is impossible to properly parse in JSON form and you need that for their Micropub protocol. And Micropub has a few stinks of it's own)

epeus 9y ago
That makes no sense. Microformats 2 defines how to parse html into json form, and there are multiple implementations in different programming languages. http://microformats.org/wiki/microformats-2-parsing http://microformats.org/wiki/microformats-2-parsing If you have problems with micropub, file issues with the spec. https://github.com/w3c/Micropub/issues https://github.com/w3c/Micropub/issues
- tscs37 9y ago
  When you write a Micropub implementation the primary spec involves an unholy JSON format. About 80% of the code I wrote was just dedicated to finding out whether or not I'm updating an article, creating a new one, deleting the article entirely and which attributes need updating. The JSON format has an immense amount of issues relating to irregularity, some fields have html and text sub-attributes but this doesn't seem documented properly anywhere, not even the MF2 page, everything is an array even where it makes 0 sense to do so and as an implementer I'm somehow expected to then process and store this mess as a coherent article. Part of the spec validation involves storing a publication which contains almost no text and some user defined elements for some reason. And I'm expected to understand and properly update these custom elements if requested.
humanrebar 9y ago
I'm not familiar with the protocols. Can you expand on this? Or are there articles that explore these concerns?
- tscs37 9y ago
  I've written a bit of a rant on a sibling comment but the TL;DR is that the IndieWeb movement has spawned some protocols which feel more like "what we happened to use is standard" instead of developing a sane standard. My favorite nitpick is that it's rather difficult to tell if a Micropub POST request is an create, read, update or delete operation. They could have used POST, PUT, DELETE HTTP methods but apparently that's too complicated.

by tscs37 9y ago

epeus 9y ago

That makes no sense. Microformats 2 defines how to parse html into json form, and there are multiple implementations in different programming languages. http://microformats.org/wiki/microformats-2-parsing http://microformats.org/wiki/microformats-2-parsing If you have problems with micropub, file issues with the spec. https://github.com/w3c/Micropub/issues https://github.com/w3c/Micropub/issues

tscs37 9y ago
When you write a Micropub implementation the primary spec involves an unholy JSON format. About 80% of the code I wrote was just dedicated to finding out whether or not I'm updating an article, creating a new one, deleting the article entirely and which attributes need updating. The JSON format has an immense amount of issues relating to irregularity, some fields have html and text sub-attributes but this doesn't seem documented properly anywhere, not even the MF2 page, everything is an array even where it makes 0 sense to do so and as an implementer I'm somehow expected to then process and store this mess as a coherent article. Part of the spec validation involves storing a publication which contains almost no text and some user defined elements for some reason. And I'm expected to understand and properly update these custom elements if requested.

humanrebar 9y ago

I'm not familiar with the protocols. Can you expand on this? Or are there articles that explore these concerns?

tscs37 9y ago
I've written a bit of a rant on a sibling comment but the TL;DR is that the IndieWeb movement has spawned some protocols which feel more like "what we happened to use is standard" instead of developing a sane standard. My favorite nitpick is that it's rather difficult to tell if a Micropub POST request is an create, read, update or delete operation. They could have used POST, PUT, DELETE HTTP methods but apparently that's too complicated.