And with #Jabber you even have first class clients (i.e. not Electron) on systems which are neither Google Android nor Apple iOS (e.g. my mobile runs #Mobian).
Just set up my own instant messaging server through @snikket_im, the process was very easy and non-technical 👍 Was especially pleased with how they handle the domain name, you can use your own (with lots of help given including an interactive settings tester) or choose a subdomain of snikket.org.
Snikket runs on #XMPP / #Jabber and is compatible with non-Snikket servers and apps.
If you're interested in this topic, are there any particular things you would like me to test on Snikket?
Note, that not everyone limits the use of the term #fediverse to the AP protocol. Many apply it to AP, Diaspora, Matrix, #XMPP, etc. After all, communication between the "sub-federations" is possible.
The lesson of the XMPP story is that the community shouldn't get complacent just because a big corp is now backing them, support their own smaller #FOSS developers through any means they can (whether financial or code), put out a unique thing every now and then, and make sure the UX is not horrible for new users. I think #Misskey, #Sharkey, and #Catodon got those lessons right (especially the very latter, UX was really horrible in XMPP back then and I think that's what "killed" it if you can even call it that). Not sure about #Mastodon though. Maybe that's what why almost all of the worry I'm hearing about #Threads comes predominantly from Mastodon and Mastodon-compatible (in the sense they try to be as compatible with Masto as possible in terms of API) instances. :seija_coffee:
An important distinction is slowly being uncovered about the definition of the term "fediverse." Who is it that gets to decide what this place is? How are we being represented? These are not easy questions to answer and if we don't do a better job describing ourselves, then the job will get done for us by people who don't understand the underlying values we hold. #fediverse#meta#threads
@liaizon Personally, and the way the term was used, since it was first coined, was any software with #OStatus support (later #ActivityPub).
When there were discussions of having a new name, I ran suggestion threads and polls about it, and one suggestion/choice was mycelial, mycelium. I like it so I started using it myself.
W nowym dużym wydaniu eJabberD 24.02 udostępniono możliwość logowania do serwerów Matrix. Tak oto nieco starszy świat otwartej zdecentralizowanej komunikacji spotyka się z tym młodszym:
"🌐 Matrix #Federation Unleashed: Wyobraź sobie płynne łączenie się z serwerami Matrix – teraz jest to możliwe! #ejabberd otwiera nowe możliwości w komunikacji międzyplatformowej, wspierając bardziej połączony świat wiadomości. Mamy jeszcze trochę do nadrobienia i w tym celu czekamy na Twoją opinię."
The account below is a discussion group. Follow it to see its discussions in your timeline, mention it to post to the group. (More info on how to use Fediverse groups: https://fedi.tips/how-to-use-groups-on-the-fediverse/)
A few months ago, I persuaded a client to abandon an external cloud system and use Nextcloud on their own server instead. Powered by FreeBSD and ZFS, it has already demonstrated its strengths on a couple of occasions (such as in the case of a snapshot rollback). This morning, they expressed the desire to abandon the various WhatsApp groups they use for coordination and to use a solution "all on their servers." I was inspired and quickly installed both an ejabberd and a Matrix server (Synapse) - which they will probably prefer, according to the latest news they sent me - on two FreeBSD jails.
Today, we have the awareness and experience of what it means to give our data to large companies, completely losing control over it. We have the tools, so why not use them?
And I'm really happy when someone like them, thanks to their willingness to try "new" solutions, realizes the alternatives to the colorful, advertised, warmly recommended (by salespeople) "proprietary" solutions.
Interesting, just discovered an XMPP based alternative chat client - recommended by a new acquaintance in my local LUG for snikket.
federated, decentralized XMPP with a standard set of XEP's (if you ever got that deep into xmpp, xeps are the service modules that enable features - think of them as protocol plugins/extensions)
Not sure I'd throw back in with XMPP right now but interesting all the same.
Wenn ihr auf das Jahr 2023 zurückblickt, welche Maßnahme im Bereich IT-Sicherheit und/oder Datenschutz hat euch besonders positive Ergebnisse gebracht - sei es ein Projekt, eine Entscheidung, eine Anpassung oder eine Veränderung?
Bei all den negativen Entwicklungen, insbesondere #AppZwang bei #DeutscheBahn und auf niedrigem Niveau steigende Zahl von Läden und Restaurants, in denen man nicht mehr #datensparsam mit #Bargeld zahlen kann, ist es nicht leicht Positives zu finden.
Immerhin das: Bei #Jabber gibt es spannende Entwicklungen bzgl. Gateways: Einerseits #Libervia AP gateway (#XMPP ⇔ #ActivityPub) von @Goffi, andererseits #Slidge (⇔ Matrix, Signal, Telegram, Whatsapp und mehr) von @nicoco.
I had an interaction today that was quite revelatory: I was chatting about a friend on mastodon and got asked "On which mastodon" he was. I really think that we, as a community, are explaining this instance thing quite poorly indeed... #fediverse
@m_artigiani Personally, it's not that it's being explained poorly, rather, people are too used to siloed / closed-garden #SNS that they find it hard to get their heads around it.
For example, in the #messenger / #InstantMessenger space, we've had #federation since the late 90s, thanks to #XMPP (formerly known as #Jabber). We didn't encounter this issue, people simply understood it like how people understood email.
Then later, there's #Matrix, which is also a federation. But I haven't heard anyone ask or got confused how it works.
However, when it comes to SNS, majority of people were never exposed to interoperable SNS. Since #Friendster#MySpace#Hi5 came out, there never was a federated SNS until 2008 when the #Fediverse was born (then called #Identiverse).
The #ATproto / #BlueSky federation is coming in 2024, so we'll see if they'll encounter the same challenges in explaining instances. If they do, or do not (as the BlueSky team are saying they won't have that issue), then we'll know better since we'll have a comparison by then.
For me, I think we've done everything that we can to explain it.
One of the more limiting things about Signal is you have to give out your mobile number to everyone. Even if it is a burner, I still don't want to advertise to the world that it's mine.
Was happy to read today that Signal is now beta testing a new username feature.
#Streams galaxy
-- note 1: communication with the Fediverse is standard practice in this universe.
#Hubzilla galaxy
-- note 1: developed a way to communicate across the Mycelial Web (a.k.a. the multiverse). Can also communicate with BlueSky and diaspora.
#Friendica galaxy
-- note 1: developed a way to communicate across the Mycelial Web (a.k.a. the multiverse). Can also communicate with BlueSky and diaspora.
#X#Twitter Mycelium (closed borders; isolated; have not discovered there are other mycelium/universes besides their own)
#Tumblr Mycelium (closed borders; isolated; rumours has it their government decided against connecting with the other mycelium/universes, but they are aware)
#Flickr Mycelium (closed borders; isolated; aware of other mycelium/universes)