twtxt VS textual

GitHub repo

> there really oughta be a text-only implementation of mastodon or one of the other fediverse ecosystems

Something like this that I know of, in a very simplified form.

> twtxt is a decentralised, minimalist microblogging service for hackers.

> So you want to get some thoughts out on the internet in a convenient and slick way while also following the gibberish of others? Instead of signing up at a closed and/or regulated microblogging platform, getting your status updates out with twtxt is as easy as putting them in a publicly accessible text file. The URL pointing to this file is your identity, your account. twtxt then tracks these text files, like a feedreader, and builds your unique timeline out of them, depending on which files you track. The format is simple, human readable, and integrates well with UNIX command line utilities.

https://github.com/buckket/twtxt

I will note that indieweb folks sometimes get a little dogmatic about POSSE being better than PESOS (Publish Elsewhere, Syndicate to your Own Site). Because POSSE necessarily entails write-permissions, it's titchier to set up than PESOS-ing your public content elsewhere back to your own site. I had a lot of stuff PESOSed from Lemmy (https://lemmy.ml/post/47757) to my own site (https://maya.land/responses/2021/01/14/recyclable-plastic-is...) because I could just scrape the content out of the Lemmy RSS feed and reformat. Similarly I pull over Hypothes.is annotations (https://via.hypothes.is/https://theprepared.org/features-fee...) to a personal wiki where I clean them up into posts for my site (https://maya.land/responses/2021/07/29/geofoam-giant-styrofo...). Sure, if I wanted to update in two places it'd get titchy, but because I'm mainly using these other sites as front-ends to get a canonical personal copy I then mess with, it works pretty well. Hell, I even take Mastodon (https://occult.institute/@maya) and shove it into a twtxt (https://github.com/buckket/twtxt) file on my site (https://maya.land/assets/twtxt.txt). Once you start thinking about stuff with these approaches you can always find a convenient way to duct tape things together.

The Textual project has a lot of screenshots in its documentation. These screenshots are built with the docs, so they are always up to date.

https://textual.textualize.io/

Textual[0] does this for CLI apps. That’s not for full GUI apps, but it’s very DOM-like, uses CSS selectors, etc. and a cool option when it meets your needs.

[0] https://github.com/Textualize/textual

For future projects that need a TUI beyond normal printing to a terminal, I'd recommend taking a look at Textual.

https://jupyterbook.org/en/stable/content/code-outputs.html#...

`less -R` is not the default.

FWIW, textual (and urwid) does ANSII escape codes well: https://github.com/Textualize/textual

  touch file$'\n'name

After installing logmerger, you can run a self-contained demo by running logmerger --demo, to view two log files before and after they are merged, and to play with the user-interface features provided by textual.

I think it just survived naturally, filling in the cracks left by Java / C++.

And not the era of Textual (https://textual.textualize.io/) is here, python may get the spotlight even more.