- if are.na can implement an api endpoint for getting comments from a block, the logic could be: any comment by the block's author is a piece of metadata in a json- or yaml-like format, or maybe some data structure where you have key: value and then can also write key2: key//value2 or something similar; basically a simple syntax for 1) adding a single metadata key, and 2) using metadata keys INSIDE other metadata keys' values so you can build nested data structures
- hm, if that can't work, I think I could do the same thing with block description and/or block title
Second principle of a Marxist design practice: transcend normative aesthetics.
In order to operate within a Capitalist society without inheriting a Capitalist ideology, one must deviate from the aesthetics used to perpetuate the Capitalist ideology.
Prompt: Draw a grid. Now imagine what happens when you enter into that grid? What does its landscape look like? Plot that landscape to create a new grid.
hey! saw you connected hills - i'm trying to hit 1.0 in the next week and am wondering if you were pondering implementing it / what features might make it useful to you over just using the raw are.na api. let's chat in comments or via [email protected] :)