#YunoHost devs are testing#Prosody as #xmpp#jabber replacement for metronome to get better integration with the system and better compliance with jabber standards. Also new default features as A/V calls.
For instance to send an announcement for servers supporting XEP-0133:
li ad-hoc run "<http://jabber.org/protocol/admin#announce>" -f subject "Maintenance in 30 min" -f announcement "$(<~/announces/maintenance_30.txt)" -S
Check the doc linked above, it's explained there. Ask me if you have questions.
Curious how none of the coverage of this launch mention that the app isn’t actually open-source (though they pretend to be an open-source project), which makes all of their claims of “end-to-end encryption” worthless...
@Samsy@arbocenc#XMPP can run bridges (called "Transports" or "Gateways" in XMPP terms) since the early ages. And nowadays, there are modern ones with tight integrations: #Slidge being a flagship (including a #Matrix gateway), and I'm myself working on ActivityPub gateway and soon a email one with #Libervia. #Cheogram is also working on SMTP gateway. And #Biboumi is the flagship #IRC gateway.
#Libervia now supports SCRAM-SHA authentication. Previously relying on outdated Twisted #XMPP mechanisms, we experienced incompatibilities with recent servers like #Snikket. This issue is resolved, and Libervia can now operate with up-to-date Snikket instances.
First blog post about the work I've done so far on the #moxxy UI! I'd like to do one every month if possible, like Thunderbird does with K-9 Mail. Please feel free to send me feedback! #xmpp
Hmm, after having #nextcloud run on my #rpi for a bit I noticed I really don't need it. (Because the video chat just doesnt work as it should).
Maybe I'll just reset the rpi again and focus on some leaner system.
Maybe I'll try with #xmpp this time. Have to check if that has good voice and screenshare options right now. And maybe a web interface.
I haven't really done anything with that for a decade.
🚀 Just pushed the #WebRTC Data Channel Signaling implementation to #Libervia! In this case, it features a different workflow compared to usual Jingle File Transfer methods, with separate browser and #GStreamer implementations 💻
It's a great addition, allowing direct P2P file sending (where possible) from any device to any other one (like a CLI/Desktop frontend sending files directly to a remote browser). I look forward to enhancing the UI/UX! #NLnet#XMPP#PeerToPeer 🌐
I was about to start a poll asking if #Conversations_im should add a fallback STUN server (stun.conversations.im) for the ~40% of #XMPP servers that don’t offer one via XEP-0215 External Service Discovery.
And then the network of our hosting provider went out for ~5 minutes acting as a good reminder of why the app doesn’t rely on centralized infrastructure…
Access to the #XMPP server and the #Matrix server are currently limited because the primary IPv4 address was blocked by the provider due to #DDoS. Checking the server revealed no abnormalities and we have applied for unblocking.
@erlend I've spent 2 hours of this rainy day to read your blog and #CommuneApp design discussions. I will definitely keep an eye on it and hope you'll deliver something in 2024.
@erlend it's a protocol and all implementations are open-source.
It's a simple API (few JS functions) to implement over a chat protocol to allow "widgets" or "apps" to run and sync between members of a chatroom (existing impl run on @delta and #XMPP). You could think about matrix widgets but simpler and not requiring to host anything.
We have moved our chat room from #Matrix to be hosted on #XMPP. The new home is motoristic@conference.motoristic.org.
Hope to see you there! If you have any problems, or need help connecting, let us know.
We know it's not ideal to have to download a client to interact with the project - in the long term, we would like to offer a hosted webpage (likely using #ConverseJs) to make it easier to interact with us.
Ich hoste mit #Yunohost meine eigenen Dienste. Darunter z.b. #invidious#searxng und #xmpp. Nun wollte ich gerne mal nachfragen, wie sicher das ganze ist, wenn ich z.b. Die Suchmaschine und auch XMPP öffentlich ins Netz stellen würde; was muss beachtet werden? Oder sollte ich davon ganz absehen?
> What do you think the future of XMPP will be like? I think it might be the protocol I enjoy using the most
Interesting, and refreshing, to see optimistic XMPP thoughts on, I guess, adoption? After 25 years?
People have been proclaiming the death of Jabber/XMPP for many a moon, yet its utility and existence just below the surface of mainstream awareness remains healthy. Yes, it is sometimes thought of as long forgotten, and no, it's not losing any um, ... Market share, so to speak.
For most things, and especially as a chat/communications platform between people, I migrated away and onto other solutions, leaving it alone and largely dormant for nearly two decades; yet it has always been part of my infra - mostly just between me and machines I've managed (notifications mostly).
I think part of the reason for it being so summarily dismissed was due to the rise of things like AIM, YIM, etc., and its perceived 'death knells', following Google's choice to (at least publicly) migrate away from it in the course of killing some of their public services.
More significantly however, IMO, were the abhorrently ugly and unintuitive UIs most chat clients sported - I'll call that era the time when XMPP clients mostly appeared like something you'd see on Angelfire or GeoCities web pages - before the MySpace and subsequent early Faceplant years following the breakage of the Pimp my Myspace page phenomina.
Like Samuel Clemens, once stated, ... "The report of my death was an exaggeration." If XMPP were itself able to express such sentiment, I believe it certainly would, lolz.
XMPP is simple to use, fast, secure (not by default), and by creating a situation where the user is transparently ignoring the JID + "/resource" and numerical priority that served to constantly confuse laypersons with multiple devices, the neo-adoption of XMPP and the introduction of 'pretty' clients has to a large degree, made it seem as if XMPP is something that is rather novel in the communications (chat) sector.
Clients like Conversations, at least on the #Android platform, have enabled this renaissance. There's also more desktop clients that sport a good look (pretty), offering an intuitive UX.
Is it going to be the next great thang? Doubtful. As @silverpill stated:
> I think It will remain a small network, unless something really bad happens to matrix (its main competitor).
... There's that elephant in the room.
On the other hand, for those of us who were early adopters of the hopeful #Matrix protocol, the promise hasn't quite been realized as expected, and further, it's been rife with disappointments - How many times have I myself integrated Matrix into system monitoring infrastructure only to feel that dissapointment?
XMPP doesn't offer me that - it works, every fucking time, fast, and I need it fast. I need to be able to call my customers and tell them that there's a problem and that I'm working on a fix before they even know there's a problem. I can plugin Zabbix, Observium, Nagios, Cacti, #NetFlow, etc., and when I hear that cacaphony of an alarm in the middle of the night, know that I need to get out of bed and start putting out fires.
I use Matrix - daily, all the time. But when people close to me ask which one of my non-email contact methods is best (besides actually calling me on the phone), I let them in on a little secret - "If you really need to get a hold of me, like, right now, and want my undivided attention when some IM pings me, then use my Jabber address". It's the first thing I check when I wake up, and I don't even usually check Matrix (it's mostly just for discussions and private chats nowadays anyway in my work flow).
Do I care if it's going to be the next great thing? Well, I prolly, when thinking about it, would prefer that it not be - Here's why:
Mass adoption by my friends and colleagues who I converse with would only serve to dilute the priority to which I assign my #XMPP communications
Migrating from Matrix (or something else) to XMPP for my virtual social interactions would prolly spur me towards wishing I had a dumb beeper again on my belt, lolz.
Sure, I can take advantage of different JIDs/resources, and even install separate XMPP clients if I wished, but managing different alert sounds, etc., and, ... Basically just complicating something that is so simple and effective the way I use it now kinda defeats the purpose of having a (mostly) dedicated interface between me and my boxes :p
Well, that's my 2 cents ;) and of course, my XMPP addy is in my profile if someone wants a priority chan to rattle my cage - but please do use #OMEMO as a matter of practice, even untrusted e2ee is better than clear text and I believe that we should, whenever practical, use encryption by default....... because. Just because :)
Automattic buys Beeper for $125MM, launches closed-source "privacy" app (techcrunch.com)
Curious how none of the coverage of this launch mention that the app isn’t actually open-source (though they pretend to be an open-source project), which makes all of their claims of “end-to-end encryption” worthless...