Text-Based User Interfaces (TUI; CLI)

92 readers

27 users here now

Forum for advanced users who grok the power of text-based apps, the advantage of tmux/GNU screen, the keyboard and who often find the mouse a hinderance to a fast workflow. A text-based UI is also a decent escape from enshitified resources.

This forum broadly covers tools, hacks, and advocacy of text-based environments.

Slightly marginally kind of related:

founded 6 months ago

MODERATORS

evenwicht

Unmet needs in text environments -- tools we need (self.text_ui)

submitted 3 months ago* (last edited 3 months ago) by evenwicht to c/text_ui

2 comments fedilink hide all child comments

This thread is a whine and winge fest to collect complaints of functionality missing in our world of text UIs. I’ll start off with:

SMS 2.0 (“RCS”): The new standard for SMS (Rich Communcation Services) only has an Android 8.1 app -- nothing for the desktop at all
kbin/mbin
Lemmy: Neonmodem Overdrive seems dysfunctional; some servers have an old. FE which works with links browser because it has a JavaScript engine, but it’s a terrible UX; and nothing works as far as offering offline access.
Mastodon voting and poll creation: (though I have not tested https://brutaldon.org/)

you are viewing a single comment's thread
view the rest of the comments

[–] evenwicht 4 points 3 months ago* (last edited 3 months ago)

I’m not real familiar with RCS either but I got the impression RCS could be used to send an SMS to someone without having mobile phone service yourself. The old way was email gateways where you email $phonenumber@sms.$carrier.net and the msg is sent as an SMS (at no cost) to the recipient at that carrier. But those email-sms gateways are dying off and you need to know which carrier the recipient has.

BTW, I suggest avoiding Signal:

https://github.com/privacytools/privacytools.io/issues/779

The free-world option is XMPP+OMEMO.