I mean, these ain't like in the old days where a few Megabytes got you #Pidgin and other Multi-Protocol Clients of the old days where everyone had to implement bespoke, custom and incompatible and often completely undocumented, proprietary protocols like #ICQ, #AIM, #SIPE, etc.

• Nowadays all these do have some kind of #WebApp or Web Interface one can just login (because none of them do proper #E2EE with #SelfCustody of all the keys!) so this should be way easier these days:
• All they do is do HTTP(S) GET/POST so the most critical part is to attain credentials like a #Login #cookie and to basically run a console on i.e. #Firefox to reverse-engineer the "#API0"...

It just makes me wounder: Are modern messengers these days complicated or do the people who have the talent to write such a #MultiProtocolIM chosen that this is stupid and that like myself they'd never touch that shite in their life and make peace with it?

• And I'm not talking about specific #API limitations like #Discord uses to force people to use their garbage client, but like #WhatsAppWeb and others...

I mean, there are commercial #MultiPlatform #clients for #SocialMedia like #HootSuite and #NUVI [not that I'd like either of those but still...

https://www.hootsuite.com
https://reputation.com/products/social-suite/

And it's not like people and espechally businesses are unwilling to pay for good tools, cuz not only is HootSuite still around, but @tapbots, who made the excellent TweetBot nowadays make @ivory, an excellent #ActivityPub client with focus on #Mastodon that people are willing to pay a #subscription for!

• And from what I could see from users who pay for it, they are not just happy, but it also looks and feels better than #TweetDeck in it's golden days...

https://tapbots.com/ivory/

Like: There's not much of a technical reason something similar to @zulip 's #TUI - based client could exist for the aformentioned platfirms:

• Obviously #proprietary platforms - (just like #Shitter even before #ApartheidEmeraldBoy took over and speedrun it into becoming a #NaziBar) - will try to passive-aggressively stifle such #clients, but still...
  

If people can build #bots for shite like #discord, #Telegram, etc. then why not make an actually good client ???

For those who don't know the size of the problem:

In 2006 I bought a new [entry level] Computer with 256 MB of RAM and a single-core P4 Celeron with 2,8 GHz.

• This thing ran #WindowsXP and #NeedForSpeedMostWanted just fine.

• Nowadays it would crash trying to open #Slack even on a minimalist #Linux distro like @bunsenlabs in @dillo, a lightweight browser ...

And now imagine that some folks have to use #Slack, #MicrosoftTeams, #Telegram, #Signal, #WhatApp, #WeChat, #QQ and #LineMessenger at the same time on their machine, and you can imagine that this will make entry-level desktops already scream harder than if someone were to loop the Lost Coast benchmark on them...

• The #bloat of modern #WebApps is just the socially accepted equivalent to #Cryptojacking desktops and driving some *phat #SuperUselessVehicle just to get less than a kg of groceries at a walking distance supermarket.

Everywhere else we'd not accept such a #bloatware IRL.

• So why should we accept #obscene|ly #WastefulComputing*?

@kkarhan unfortunately the users don't, the server I've been visiting since 2001 is down to like 5 people currently :-\

Everyone moved to discord, which completely sucks. Back in the old days, we'd archive IRC logs and post them on our sites as tutorials. Discord prunes information, sucks it out of rotation like a leech.