I've written a little something on why I use a web...
# share-your-work
a
I've written a little something on why I use a web browser as my terminal emulator: https://blog.pomdtr.me/posts/tweety-v1/
e
Absolutely smitten! Thanks for sharing this! I just made a tiny pull request to tweety to make the font size year configurable.
Also, curious if you’ve tried TabFS!?
a
Yeah, I love the idea of mapping abstract concepts to the filesystem and managing them using standard unix commands. It was one of the inspirations behind one of my other project: https://smallweb.run
e
I maybe went overboard @Achille Lacoin — I’ve added some very basic optional auth to tweety to make it a tad be more usable/safe. Here’s the commit on my fork — if it is your jam I can create a PR for you.
k
This is using the browser in the same way that many people, including myself, use Emacs: as a flexible user interface to lots of other programs. A thin client. In the abstract, I really like this. In practice, I find it too risky on today's browser oligarchy. In particular for a terminal. I see the terminal as the lowest-level UI on my computer. When everything else fails, for whatever reason, I still have the terminal. Making the browser a dependency of the terminal feels very wrong. Yes, I know, using a Web terminal doesn't take the native terminal away. But it still feels as if an earthquake had messed up the software stack.
That said, I will definitely test this and I may end up using it. Not to replace the terminal, nor Emacs (my default command line interface), but as a way to integrate command line tools into browser workflows.
a
@Eli Mellen I added basic auth support in the latest release !
I'm also trying to rework Tweety as a chrome extension. It would remove the requirement to register tweety as a service, and add support for some interesting features (ex: managing tabs from the
tweety
cli)
image.png