One thing that really pisses me off personally is the #regression in terms of #Messenger #Apps.

My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal ¹ ², #Telegram, #Discord ³ , #WhatsApp , #Slack, #MicrosoftTeams, #discord etc. aside:

  • WHY is there no #CrossProvider #Messenger to handle that shite?

  • WHY does everyone of these shitty providers think people want to download their #bloated #WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU each of them can??

This problem ain't new and already got solved for corporate social media ages ago! (Not to mention actually good messengers!)

So yeah, consider this a call for a @gajim / #Gajim or @pidgin / #Pidgin for garbage platforms!

  • Cuz back in the day we had way worse messengers yet people actually made #AIM, #ICQ, #MSN, #QQ, #IRC & #XMPP work just fine from one single "phat" client!

  • Can we please get that back? Cuz #WastefulComputing pisses me off!

#api0 #Enshittification

Kevin Karhan :verified: (@[email protected])

Content warning: Rant re: Signal Shills being dangerous Tech Illiterates

Infosec.Space
@kkarhan @gajim @pidgin Because what you're asking for is a Herculean task.

Plattforms like XMPP and IRC were and
are designed to be open. They are made with the intent in mind, that a single developer can read through the specification and build software for and with it.

Plattforms like Discord were never made with this intent in mind. They were started as many people getting paid to be as productive as possible with building something, and "improving" it. They break APIs so rapidly, that to maintain a Discord client library to maintain Discords pace in changes and breakage is no easy feat already, to say the least. Discords HTTP API has 10 versions. And they do not do semantic versioning, nor do they do any kind of active change log keeping, nor do they provide ANY details on the User-Targeted API (only the bot API). In the same version 10:

- Discord completely changed user identifiers from the # based system to @ based usernames
- Discord introduced MLS encrypted voice traffic and implemented that whole system
- Discord changed the client permissions list in a way that affected an existing permission in a backwards-incompatible way, which, I think, was a first for them

In ONE version! In THE SAME version! And they always do this, forever, for every version!

Got that? Okay. Now rinse and repeat, we still got WhatsApp, Signal, Slack, Teams and Telegram to take care of. /hyp

Like, of course, some of these providers, i.E Telegram and Signal, do much better at this than Discord. But still, this is a HUGE task. And you have to keep all of this up-to-date, because they do not care that much about backwards incompatible breakage, unlike your typical IRC enthusiast.

@star sounds more like a "them"-problem to me...

  • Most of these platforms secretly use #XMPP under the hood anyway.

  • Also like #GDPR, the demands per #DMA ain't new nor surprising. They had YEARS to do whatever they need to to to enshure #portability by any means necessary...

#Discord espechally and purposefully works against any 3rd party clients by going out of their way to brick functionality.

  • Them breaking their own shit is - again - their problem, not mine!

@star @kkarhan @gajim @pidgin This Herculean task is exactly what I am attempting to do with Pidgin 3.

Also Pidgin 2 / Purple 2 already has support for most of the protocols mentioned here in some regard. And sure they break, but the plugins get fixed and life goes on.

https://pidgin.im/plugins/?publisher=all&query=&type=Protocol

If you just want to be a doomer, then doomer away but keep us out of it.

Plugins

Pidgin is a universal chat client, allowing you to consolidate all your different messaging apps into a single tool.

@grimmy @star @pidgin exactly that is good, and I assume most of these aim at beingAPI 0 - style reverse-engineering....
Foone🏳️‍⚧️ (@[email protected])

There is always API 0: acting like a human/browser/user. The first API is "fuck you I'm doing it anyway". Any additional API the program provides is merely a helpful shortcut

digipres.club

@kkarhan @star @pidgin Most of them are yes, but the new #Twitch.tv protocol plugin I've been working on uses their API as they're open to third party clients.

It's important that people use those APIs so that others are more pressured to provide them as well.

@grimmy @star @pidgin +9001%

  • Obviously #Twitch needs to offer more open #API|s because they have professional users on their platform that have dedicaded, broadcast-grade gear and staff for chat & moderation.

@kkarhan @star @pidgin Yep and leveraging them with Pidgin gives everyone more options.

I just wish they had a supported way to view streams that wasn't and embedded iframe.

We won't be doing that because I'm not putting a browser engine in Pidgin 3.

@grimmy @star @pidgin +9001%

There are better options.

  • Personally I wished they'd offer an m3u8-Format Stream to just ingest into VLC.
@[email protected] @kkarhan @pidgin grimmy, i am happy i do not have anything to do with you and that i do not federate with your instance

@star @pidgin @grimmy ??

Your account = your decision...

@star @kkarhan @pidgin what are you talking about instance? Pidgin is nearly 28 years old chat client that has been playing this cat and mouse game nearly as long. (It used the officially supported toc protocol to initially connect to aim). It runs on your computer and is not an activity pub or xmpp server.

https://pidgin.im

Pidgin

Pidgin is a universal chat client, allowing you to consolidate all your different messaging apps into a single tool.

@kkarhan @star @pidgin yeah we'll get it. It's just annoying. I assume it's because people want to skip ads, but as a twitch affiliate myself obviously ad revenue is something I would like to keep getting ...

So obviously that means I'll be addIng ad support, but from my initial testing that seems necessary anyways, well at least reporting you saw the ad or something as my test feed just said "ad break" until I gave up and moved to something else.

@grimmy @star @pidgin I wished #Twitch would just provide the streams as shown on their site.

  • I don't think playback for that should be added into #Pidgin but a link that's clickable to said video stream should be handled by the application of choice. May it be @videolan / #VLC or merely the Link to the channel / stream to open in a Browser.
@kkarhan @star @pidgin @videolan Its not going to start the video automatically. But its still awhile before I get that implemented..

@grimmy yeah.

In the meantime just offering a clickable link to the stream/channel would already work great, espechally in cases where Pidgin is beibg used for moderation and interactive cintent production.