Amazing write-up. Owing to your data, a standardized protocol (such as the AT Protocol) is so great! It's like markdown, everything is basically built on files (but cleverly architected so that it works decentralized across the web too!).
not sure if you understood the article, isn't the whole point to own your data as "it's just a filesystem". Reddit, Instagram, etc. are the total opposite.
Yes, I should have been clearer. Reddit and Instagram do not operate this way today, but open social alternatives to them could. The idea is that people create personal websites where posting, commenting, and other social actions live, and that becomes the filesystem they own.
Open social networks would simply index or pull from those sites using agreed-upon lexicons and protocols. Existing platforms could either adopt the open social model, or, more realistically in the short term, be treated as syndication targets where posts are pushed via their APIs when someone publishes on their own site.
Yes I'm loving the growth in this space. I'd also throw Standard.site[0] into the mix, it seems to be the lexicons Leaflet and some other apps are using.
I moved from 15 years of macOS to Linux (Omarchy in my case). I was mostly using the terminal and am therefore super happy with my choice now. I wrote more at https://www.ssp.sh/blog/macbook-to-arch-linux-omarchy/, in case of interest.
This is the story of how (Neo)Vim and Markdown unified my data engineering and writing workflow.
As CEO of Obsidian says:
> Obsidian will not exist forever, no app will. However, the files you create in Obsidian are yours, and can hopefully last for generations.
Plaintext files as the foundation, Markdown as the format, and Neovim as the editor. Combined, they will last until the end of days of computers.
I really like how he automates his newsletter off of his blog, notes, TIL, etc., but it's also amazing how complicated it is. Imagine the blog would be on Markdown, nothing of this is needed as the "content" would just be locally for a Claude to read, it could do the SQL-query with a cmd-line instead, or you could build a small wrapper around if you want. Plus if the Newsletter supports Markdown, too (I use Listmonk), then the conversion would be straight forward too, also with no bugs.
This inspires me to automate one day more of my newsletter too, maybe as I have everything in place for it. And I automate blog post to send out automatically, but not a collection of notes and blogs.
I found Presenterm [1] to be optimal for me. Simple and works in the terminal, yet powerful to export to PDF and HTML. It supports Mermaid and images. I'm also collecting a list [2] with other Markdown-first presentation tools, and according to the git stars, reveal.js seems to be the most popular. Tough for me, it was too heavy.
i made a toolset i call "mdslides" for making pure HTML+CSS (no JavaScript) presentations in Markdown. it's just a CSS stylesheet and an 8 line Awk preprocessor for a slide delimiter, adding just enough HTML wrapping to work with the stylesheet. the stylesheet adds page breaks at each slide so you can get a PDF by asking your browser to print/save-as-PDF. it should work with any CommonMark Markdown formatter (i use "md2html" from the MD4C project).
I tried to use pandoc+revealJS, then tried presenterm (which was really nice but didn't give me enough control over font sizes), and then settled on Marp, which worked great.
I wrote a little along the same lines on «Well Being in Times of Algorithms» at https://www.ssp.sh/blog/well-being-algorithms/ (or HN: https://news.ycombinator.com/item?id=46352747).
reply