• woke up with a [[headache]] again, a bit worried -- not overly, I've got three vaccines and it's still a week+ until we have to travel.

  • work was hard as I was tired (didn't sleep well either, I usually sleep well as of the last few months), and as I had two symptoms I decided to tell the team I would take it easy and work in low energy mode (no meetings after lunch, taking rest/naps).
  • just pressed [[g t]] in logseq and it sent me to tomorrow's note, [[2022-01-26]]. Nice.
  • I wanted [[g j]] for go [[journal]] :)
  • asked on [[twitter]]:
    • @tiensonqin @andotvu is it too late to change the defaults? ;)
    • IMHO [[iso 8601]] / [[rfc 3339]] make sense as defaults in general (pending overriding factors). And these settings, I believe, might make [[logseq]] compatible out of the box with extra editors.

• I'm happy about [[logseq]] managing images sensibly out of the box -- I could never make that work well with [[foam]], perhaps because of some interaction with some other extension.

• #push [[2022-02]]

  • LATER make [[agora]] and [[stoa]] run from scratch in a new server using [[docker]]

    --[2022-01-25 Tue 21:08:04] => 00:00:01

• [[yoga with x]]

  • had fun with [[fractal yoga]] again

2022-01-25

• [[1.3 million people, or 2% of the population, are estimated to be living with long Covid]]. That's a hell of a lot.

• [[Covid-19 will not just disappear]].

• [[Platform socialism]]

  • "the organisation of the [[digital economy]] through the social ownership of digital assets"
  • "and democratic control over the infrastructure and systems that govern our digital lives."

I don't really care at all about [[gemini]] but I love love love all the stuff that shows up around [[m15o's']] projects (link). the newest is [[vpub]] (source) and it's real cute, makes me want [[cinni]] to do a UI theme. Also apparently there's a feature in [[atom]] to specify emails where replies to posts can go, which is nice. :)

my annotations look much cuter on lindylearn.

I'm not really adding notes about the things on which I'm doing my most focused research. That's because I'm hoping they'll lead up to a project that -- well, I'm a little obsessive about wanting to keep it cleanly [[pseudonymous]] and not to be traced back to me. This is a strange concern when I'm pretty sure there are fewer than six people who will ever pay attention to it... but oh well.

[[2022-01-25]]

• [[Health]]
  • Had a really nast episode of [[depersonalization]] during the early morning. I'm still not 100% fully recovered from it, but I'm better.
    • Talking with my partner helped a lot. Sleeping too.
    • I think this is a sign that I should reinstate my [[meditation]] routine. It helped me a lot when these episodes were more frequent in [[2017]].
• [[Lightweight markup language]]
  • I'm trying to find an alternative for [[Markdown]] for writing the content of my site.
    • What I need in a [[lightweight markup language]] for my site:
      • As much compatibility with [[HTML]] as possible.
      • Syntax for adding anchor, semantic and arbitrary atributes to [[HTML element]]s.
      • Extensibility.
    • My options so far:

      • [[kramdown]]

          argdown
          [kramdown]: Should I use kramdown for the content of my site?
          	+ kramdown is a Markdown flavor, and Markdown is *de facto* the lightweight markup language *franca* on the internet.
          		+ I'm already used to Markdown, especially the GFM flavor.
          		- Markdown flavors' differences aren't always incremental. Sometimes their syntax for the same elements differ.
          		+ Regular textual elements are fairly easy to copy-and-paste from one Markdown flavor to another.
          			+ This is even more important when working with copying-and-pasting from one app that uses Markdown to another.
          	+ Readable.
          	+ First-class citizen on GitHub and GitLab.
          	+ First-class citizen in the Agora.
          	- Extensibility is mostly parser-dependant.
          		+ But being able to add attributes to HTML elements partially circumvents this. 
          	+ More compatible with HTML than regular Markdown.
          		- But could be better.
          	+ Jekyll supports it.  
          	+ Syntax for adding anchor, semantic and arbitrary elements to HTML elements.
          		+ <li> elements can have attributes added to them.
          		- No syntax for adding attributes to <ul> elements, which is essential for my atomic/transclusion dependant workflow.
        

      • [[AsciiDoc]] + [[AsciiDoctor]]

          argdown
          [AsciiDoc + AsciiDoctor]: Should I use AsciiDoc + AsciiDoctor for the content of my site?
          + Extensible.
          + Popular, widely used, with a rich ecossystem.
          	-  Markdown still surpasses it on the use and popularity aspect.
          + Readable. 
          + First-class citizen on GitHub and GitLab.
          + Great compatibility with HTML.
          - Not a first-class citizen in the Agora.
          	- However, there are many ways to convert AsciiDoc to Markdown.
          - Jekyll does not support it.
          	- A jekyll-asciidoc gem exists.
          		- It hasn't been updated for months.
          	- There are ways to import HTML (to which AsciiDoc can be exported) into Jekyll.
          + Syntax for adding anchor, semantic and arbitrary elements to HTML elements.
          	+ <li> elements can have id attributes added to them.
          		- Support for semantic and arbitrary attributes is yet to be implemented.
          			- There's an active discussion about implementing it however.
          	+ <ul> elements can have attributes added to them.
        

      • [[org-mode]]

          argdown
          [org-mode]: Should I use AsciiDoc + AsciiDoctor for the content of my site?
          + Extensible.
          	+ org-babel makes org-mode *really* extensible.
          + Popular and widely used desktop-wise, and part of the rich GNU Emacs ecossystem.
          	- Non-existent as an Internet lightweight markup language (it was never its purpose).
          	+ Direct integration between my private and public digital gardens.
          	- I'm a Neovim user. I don't use GNU Emacs, neither I'm really interested in using it.
          		- There are ways to use org-mode files in Neovim.
          			- However, this makes the GNU Emacs ecossystem useless.
          + Readable.
          + First-class citizen on GitHub and GitLab.
          - Not a first-class citizen in the Agora.
          	- However, there are many ways to conver org-mode to Markdown.
          - Jekyll does not support it.
          	- jekyll-org and jekyll-org-to-html exist.
          		- Both haven't been updated for years.
          	- There are ways to import HTML (to which AsciiDoc can be exported) into Jekyll.
          + Natively supported by Logseq.
          + Great compatibility with HTML.
          - Slightly more convoluted syntax than the other options.
          	- However, not in a crazy way
          + Syntax for adding anchor, semantic and arbitrary elements to HTML elements.