Show newer

@Kilirai Oh that's so cute. I totally expect this to be a whole children's books series!

@dosnostalgic I've never really been fan of those kind of games, but Worms can be kinda fun.

@faticake Gosh. I do consider that a bit pricy, but you do get a very lot for it!

@sergeant@mstdn.social Jeez, that's some detailed fantasy.

@Acer That's right, that word is used the most in combination with the fence.

It does have some more meanings than those wooden stakes for a fence, though.

@lydiaconwell Well, mine's ADHD!

Performed analogously.
Recorded digitally.
Converted to HD format.
Transferred to this digital medium.

@rastinza Okay, I've taken a peek at it now.

The two plugins in question are: Obsidian Columns (OC) and Multi-Column Markdown (MCM).

They have both pros and cons.

OC uses code blocks, and you can nest them to have columns inside columns. I'm not too fond of this approach much because if you have a genuine text or codeblock inside a codeblock, the normal text formatting or syntax highlighting is gone in editing. It's just a bit annoying to work with in editor mode. But hey, nested columns! The output is in divs.

MCM uses `=== keyword` type coding, so not codeblocks. It goes like `=== start-multi-column: name` and then right below it a small codeblock for some config settings, and then stuff like `=== end-column ===` and ending with `=== end-multi-column`. Rendering was a slight bit buggy but ultimately came out right. I likey because formatting of your content stays intact, but no column nesting possible inside them. And yes, this ended up as a div as well.

@rastinza Okay, I've taken a peek at it now.

The two plugins in question are: Obsidian Columns (OC) and Multi-Column Markdown (MCM).

They have both pros and cons.

OC uses code blocks, and you can nest them to have columns inside columns. I'm not too fond of this approach much because if you have a genuine text or codeblock inside a codeblock, the normal text formatting or syntax highlighting is gone in editing. It's just a bit annoying to work with in editor mode. But hey, nested columns! The output is in divs.

MCM uses `=== keyword` type coding, so not codeblocks. It goes like `=== start-multi-column: name` and then right below it a small codeblock for some config settings, and then stuff like `=== end-column ===` and ending with `=== end-multi-column`. Rendering was a slight bit buggy but ultimately came out right. I likey because formatting of your content stays intact, but no column nesting possible inside them. And yes, this ended up as a div as well.

@rastinza No idea, I've not checked the details yet. Maybe nested divs. Because you can nest the columns into columns as well.

I'm seeing 2 different multi-column Obsidian plugins in the plugins list. They both look interesting. I might fiddle with them later today to get a feel which one of them is the more logical/easiest to use. Would be nice to have multiple columns possible in markdown. I wouldn't always need it but it's nice to have an option there!

@sgryphon I'm not sure I understand that comparison. An email service versus federated social media?

@geekmomprojects @oskay @Blenster @gever @oskay@mastodon.technology

Don't feel bad. Thankfully moving between (Mastodon) servers here is reasonably easy. We're not locking you in like those commercial alternatives! 😊

I hope many people decide to stay around on Qoto, though. We like the extra activity!

@Acer Look up 'picket fence' in an image search to get a clear idea.

Show older

Trinsec @Qoto's choices:

CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.