[@Ellri] It was super easy to avoid autolinking in code-blocks in my experimental editor. Jealous? :lol

[img]https://dl.dropboxusercontent.com/spa/quq37nq1583x0lf/4qkhsmyq.png[/img]

[@NuttsnBolts] The experimental editor has a code representation. Here it is for the post in the screenshot right above this line:

[hider][pre]
{
  "entityMap": {},
  "blocks": [
    {
      "key": "75t1p",
      "text": "Hello",
      "type": "unstyled",
      "depth": 0,
      "inlineStyleRanges": [],
      "entityRanges": [],
      "data": {}
    },
    {
      "key": "1p39a",
      "text": "Inside this code block,\nthis URL should not parse into a link: google.com",
      "type": "code-block",
      "depth": 0,
      "inlineStyleRanges": [],
      "entityRanges": [],
      "data": {}
    },
    {
      "key": "aa5qm",
      "text": "Goodbye google.com foo.com",
      "type": "unstyled",
      "depth": 0,
      "inlineStyleRanges": [],
      "entityRanges": [],
      "data": {}
    },
    {
      "key": "d2u73",
      "text": "Long URL: https://www.roleplayerguild.com/topics/75056-mahzs-dev-journal/ooc?page=199#post-4324425",
      "type": "unstyled",
      "depth": 0,
      "inlineStyleRanges": [],
      "entityRanges": [],
      "data": {}
    }
  ]
}
[/pre][/hider]

You can basically copy it from one editor and load it into another, and the editor will populate itself with the post for editing. Kinda like copying the /raw version of a post (https://www.roleplayerguild.com/posts/4324490/raw) and pasting it into the Guild's current editor.

So that's possible off the bat. Though of course it'd be nicer if that was transformed into something you could actually edit by hand (if you had to) like HTML. The editor can generate HTML, but it takes a little work to tell it how to read it back into its own representation.

Ultimately it'd be cool if it was transformed into BBCode and then you could copy the BBCode representation back into an editor. But that would require more work. It's certainly possible in the long term.

There isn't much difference between BBCode and HTML, really. They are both intermediate representations of media made for human editing that get rendered into something prettier.

You're right that HTML can lead to more security accidents, and that's of course because BBCode doesn't run in the browser, so it's hard to accidentally skip the step where you transform it into a neutered subset of HTML before rendering it. Though that's the same step you have to do with HTML that comes from the user.

I'm not sure if I'm demystifying anything in this essay :lol, but I'm trying to clarify why a WYSIWYG editor is not a limitation.