Compare commits

..

No commits in common. "05ac85af41b3e156b0489d77405ce743b2e5035f" and "6c9f6c9bfbfe291942d18f3836f14d9d499887b9" have entirely different histories.

View file

@ -22,7 +22,7 @@ Thats when I realized that I prefer protocols over services.
I didnt have much success back then,
but fortunately, XMPP (and I hope I have too)
has continued moving forward over the past two decades.
It has developed slowly, sometimes awkwardly, but steadily.
It has developed slowly, sometimes awkwardly, but still.
Here I wont talk about why XMPP is great or how to use it.
You can check
@ -67,7 +67,7 @@ arent available on desktop at all,
and so on.
All commercial so-called "secure" messengers, like Signal or WhatsApp,
end up with pretty similar limitations,
end up with pretty much the same limitations,
because it's tricky to make end-to-end encrypted chats
work the way users expect.
@ -76,17 +76,16 @@ convenience or user expectations.
Many XMPP clients let you do almost anything youre trying to do.
Sometimes its clunky and unintuitive,
sometimes its the kind of freedom that lets you shoot yourself in the foot.
At the end of the day, youd better understand what youre doing.
It might sound messy, but for that price, XMPP actually
gives you a lot of handy features:
your chats are secured with Signal-grade end-to-end encryption,
It might sound messy, but XMPP actually
gives you a lot of handy features.
Your chats are secured with Signal-grade end-to-end encryption,
and you can use as many devices as you want,
all at the same time,
without being tied to any proprietary service.
without being tied to any single service.
This post is here to show how to use it intentionally and safely.
In general, the XMPP experience today
could be described as a "WhatsApp with benefits and frictions".
It's kinda ironic, considering that WhatsApps protocol
It's kinda funny, considering that WhatsApps protocol
is actually based on XMPP, but incompatibly altered and defederated.