mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

16K
active users

I THINK THE MATRIX CHAT PROTOCOL SUCKS

@esm indeed it does - espechally compared to & !

@kkarhan xmpp has almost no good clients and yet the ux is still better with it compared to element or any other matrix client

@esm @kkarhan meanwhile, good lucking finding a good web xmpp client. I tried. didn't go well.

@hexaheximal @esm Why would anyone want that anyway?

There are native + client for literally any relevant platform!
mstdn.social/@kkarhan/11140494

@kkarhan @esm Most people (including me) prefer using those kinds of things in a web browser.

Also, obvious counter-argument for the any platform thing: chromeos

@hexaheximal @esm

Any with of all Keys should be considered security-sensitive and thus should not he used as a .

Also supports -Apps and if you don't have administrative privilegues on a machine then consider it insecure and nit trustworthy for yourself as a user!

@kkarhan @esm Not all chromeos devices do. (e.g. ones where apps are restricted by management), and there are still other scenarios where a web app is the best/only way to do it. #ArgumentValid

@hexaheximal @kkarhan @esm I also forgot about the most obvious thing...

Back in the 90s, Bill Gates infamously decided to kill Netscape. He did it because he knew that web apps would make the operating system irrelevant.

While his solution was wrong, he correctly predicted that web apps were going to take over.

Look at all of the desktop apps which are just Electron wrappers now too. It's very common. (and before you say that electron is bad and discard it, which is likely, https://github.com/nukeop/nuclear/blob/master/docs/electron.md)

> Any #E2EE #Messenger with #SelfCustody of all Keys should be considered security-sensitive and thus should not he used as a #WebApp.

This is irrelevant too. Browsers have really good sandboxing nowadays, and on chromium you can even create multiple profiles within the UI. The reality is that, as long as the client-side code can be trusted (reminder that you can self-host element and/or cinny if you don't trust it - I've done that before) as well as the browser itself, it's about the same in terms of security.

You are fighting against reality.
GitHubnuclear/docs/electron.md at master · nukeop/nuclearStreaming music player that finds free music for you - nukeop/nuclear

@hexaheximal@blob.cat @esm @hexaheximal@wetdry.world
You may call me a evangelist but

everytime something that could've been barely Megabytes as an , , or Kilobytes as a tool instead shoves yet another entire half gig copy of the - that is onto the Desktop despite using not even 0,1% of it's featureset

I call this a systemic failure in Software Architecture.

Browsers are the most attacked applications on beyond CMSes and Webservers...

@hexaheximal@blob.cat @esm @hexaheximal@wetdry.world ...and even if we think local are a legitimate way to handle sensitive comms - they ain't but let's just assume they are for the sake of argument - WHY would you do anything beyond a .desktop file that includes startup parameters for (or even if you're that kind of Cyber-Masochist!) that specify the browser, and the file to load.

Because any good should be reduceable as + + and measured in kB or maybe a few MB.

@hexaheximal@blob.cat @esm @hexaheximal@wetdry.world

So yeah, don't trust any where it's trivial to siphon away credentials.

And don't trust any , because they WILL LIE TO YOU just like the of and @protonmail did/still do.

Keep your keys in self-custody and encryption as well as decryption locally or don't even bother at all!

And I'd certainly not do critical comms from an insecure device where I don't have full control!

dreadytofatroptsdj6io7l3xptbet