3 ms·

if anyone is curious, the link data is the following in base64: 1;1|fig:MemLink;5;2;c|h2:In-memory micro web pages;5;3;c|p:MemLinks are self-contained, mic

if anyone is curious, the link data is the following in base64: 1;1|fig:MemLink;5;2;c|h2:In-memory micro web pages;5;3;c|p:MemLinks are self-contained, micro websites that are fully generated at the edge.|p:Use a MemLink to easily share lists of links, contact details, project overviews, and so much more.|h3:The link is the web page.;1;3|p:Memlink pages are composed of blocks that can be added, removed, and rearranged to make unique and creative content.|p:Create your own Memlink now by clicking Edit this page below. is this a bespoke markup format or just something i don't recognize?

throwaway413 4y ago
Haha thanks for posting this! It is a custom templating syntax I came up with to store the document data as compact as possible before encoding. You have: <doc_config> | <block_data> Where doc config is: <palette_index> ; <background_index> And block data is a list of blocks separated by | that have the following structure: <block_type> : <block_value> ; <block_config> And block_config is an additional set of characters separated by semicolon. Right now each block reads its metadata differently, so the order of the metadata options depends on the block they’re used for. I’d like to standardize them eventually. Most start with: <background_color_index> ; <text_color_index> The color indexes map to the index position of the given document palette selected. Every palette’s first two colors are white, and black.
Cloudef 4y ago
Probably could make this shorter by applying compression optimized for text. Also I wonder what happens if you enter | into the custom text field, can user input break this or will the special characters be escaped / handled some way?
- hombre_fatal 4y ago
  It's percent-encoded.
  - throwaway413 4y ago
    Yep exactly - individual components of the string are encoded at different stages to prevent pipes and other characters from breaking the parser. Clearly though all the kinks are not worked out as others here have reported breaking it with some characters. Work in progress for sure!
- sgtnoodle 4y ago
  I'd imagine LZW would do a pretty good job without being too complicated.

throwaway413 4y ago

Haha thanks for posting this! It is a custom templating syntax I came up with to store the document data as compact as possible before encoding. You have: <doc_config> | <block_data> Where doc config is: <palette_index> ; <background_index> And block data is a list of blocks separated by | that have the following structure: <block_type> : <block_value> ; <block_config> And block_config is an additional set of characters separated by semicolon. Right now each block reads its metadata differently, so the order of the metadata options depends on the block they’re used for. I’d like to standardize them eventually. Most start with: <background_color_index> ; <text_color_index> The color indexes map to the index position of the given document palette selected. Every palette’s first two colors are white, and black.

Cloudef 4y ago

Probably could make this shorter by applying compression optimized for text. Also I wonder what happens if you enter | into the custom text field, can user input break this or will the special characters be escaped / handled some way?

hombre_fatal 4y ago
It's percent-encoded.
- throwaway413 4y ago
  Yep exactly - individual components of the string are encoded at different stages to prevent pipes and other characters from breaking the parser. Clearly though all the kinks are not worked out as others here have reported breaking it with some characters. Work in progress for sure!
sgtnoodle 4y ago
I'd imagine LZW would do a pretty good job without being too complicated.