Editor-Box VS edn

I have an idea to replace posting on Facebook/Twitter where you sell your and your readers privacy with posting on your own blog.

To achieve this, blogging platforms (I am aiming to WordPress right now) must remove the obstacles in user experience: people stopped blogging and switched to Facebook because posting on FB has more profits: it is easier (just visit front page of FB instead of logging to wp-admin and doing next steps), you have all content in one place (FB wall shows your posts and your friends posts etc) and tickles your ego (you immediately get likes and shares while on your blog barely anyone comment your post)

I am working on plugins and tools to remove this distance: front-end editor box for your blog ( https://github.com/kkarpieszuk/Editor-Box ), plugin to subscribe to other blogs and see their content as part of your blog, plugin to give local likes for posts, broadcast your content to other blogs...

Everyone will have kind of their own Facebook on their own WordPress blog.

I am WP plugin developer as my main job but all above I am doing in my free time as a hobby.

If anyone is interested in collaborating to make the network a bit less occupied by big techs, please reach me here https://github.com/kkarpieszuk/Editor-Box (create an issue or pull request if you have an idea how to extend this plugin) or find my email address at https://muzungu.pl/o-mnie/ (in Polish but you will easily find the address)

> was utterly surprised how no one ever apparently has thought to create a configuration/templating system that's basically a fancy library on top of Scheme.

There's Clojure's extensible data notation: https://github.com/edn-format/edn

A thin language layer around edn/datalog, the query language

EDN (Extensible Data Notation) is a subset of Clojure: https://github.com/edn-format/edn

It is:

- Streamable

- Extensible

- Whitespace-insensitive, but there are formatting conventions for readability

To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.

Alien is not a reason something is bad, just that's it's unusual. JSON was a bit alien when it first arrived as well, as everyone was used to XML at the time.

`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.

Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.

I just checked out the spec, and it gets pretty ugly in the Table section. A lot of the json examples are both shorter and IMO more precise. Stuff that’s not allowed with [table] is allowed with [[table]], and it’s confusing to understand what level of depth I’m at.

I’ll take edn over any of “em. https://github.com/edn-format/edn

As XT is written in Clojure and it natively supports Clojure’s data types, we were not satisfied with available JSON types and decided to give EDN a try - that way we would have way more supported types:

Compare the nightmare that is pickling with how simple it is to serialize pure data with edn in clojure. What ends up happening is people passing around JSONs or whatever and writing parsing/encoding code at each end, which makes things unnecessarily more complex, and dangerous, and error prone, and boring, etc...