Balisage Paper: Fat Markup: Trimming the Fat Markup Myth one calorie at a time

https://www.balisage.net/Proceedings/vol10/html/Lee01/BalisageVol10-Lee01.html

XML is a fine format in comparison to JSON.

Movim is another web UX option (comes with posts + feeds that can easily be crawled as well so you don’t have everything stuck in the black hole of chat).

It is the exact opposite. Ligatures were created to help deal with the lack of clarity when symbols overlap. fi, ff, fl, ffi, have historically (like print press historical) been common ligatures where others are stylistic, where others are downright questionable & make things harder to read. The first category should almost always be supported, & the others can usually be disabled if not commonly off by default where you opt in for some design, not for general body copy.

What you are referring to about ‘programming ligatures’ is an outright abuse of open type features full of false positives, ambiguities, & lack of clarity for outsiders to understand what your code means. What you want is Unicode supported in your language so you can precisely what you mean than using ASCII abominations—like meaning → but typing ->, dash + greater, than which isn’t at all what you mean which is a rightward arrow. (with a non-exhaustive languages with decent Unicode support: Raku, Julia, Agda, PureScript, Haskell with Unicode pragma, & all APL dialects).

They still exist in the malls of Asia

It’s hard to take a project seriously for championing our privacy if the only communication options are Discord & Microsoft Github

I wish we could stop with smart TVs. I want a dumb TV with a nice screen & my own hardware without worrying about the data collection

So long as you aren’t giving Adobe money, keep doing you

No need when you have free software Mumble + Murmur :)

ASUS removed the ability to unlock or root their most recent phones. Not letting users run what they want on the device they own is a hard pass from me.

Signal is pretty broken. A chat app shouldn’t require a SIM card & an iOS/Android device just to create & maintain an account (too bad Linux or KaiOS users or folks that otherwise don’t want a smart phone). Multi-devdice setups seem to have issues. The desktop app being Electron is a waste of resources. They still don’t want to support UnifiedPush while highly encouraging you download the app from the Google Play Store & send notification data thru Google-controlled FSM. There’s also the missing history of the server code which is probably has something to do with US intelligence injecting code.

Is it better than a lot of things, sure, but it should be put on a pedestal nor seen as exemplary for private chat in UI or philosophy.

Depends on the use case but XML is good for markup—especially if you need extensibility.

For config, Nickel & Dhall take the cake for being typed & having LSPs so the configuration writer can get immediate feedback about possible options (while eliminating invalid states) without requiring the manual—with configuration readers not needing to mess around with marshaling their types. Both these configuration languages let you import files & write little loops to make your config more DRY & makes maintaining large files (like say Kubernetes) easier.

Wat. Conversations is on F-Droid… and it’s the basis for Blabber, Cheogram, Monocles, etc. It’s the most influential XMPP application in the Android space.