#jabber — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jabber, aggregated by home.social.
-
You might take a look into #UWPX, a once promising, but later abandoned #Jabber/#XMPP client by #FabianSauter a.k.a. #COM8 (not on #fediverse?):
https://github.com/UWPX/UWPX-Client
Maybe you can even take over his work instead of starting from scratch?
IIRC, it does have #OMEMO, but no A/V calls, no message reactions, maybe #MAM, not sure.
-
You might take a look into #UWPX, a once promising, but later abandoned #Jabber/#XMPP client by #FabianSauter a.k.a. #COM8 (not on #fediverse?):
https://github.com/UWPX/UWPX-Client
Maybe you can even take over his work instead of starting from scratch?
IIRC, it does have #OMEMO, but no A/V calls, no message reactions, maybe #MAM, not sure.
-
I was surprised and a little bit disappointed that (almost?) nobody got my pop-cultural #reference in a #Jabber/#XMPP talk I gave at #DebConf26.
Who knows this #fractal #fish from their #childhood?
Don't ask #AI! -
I was surprised and a little bit disappointed that (almost?) nobody got my pop-cultural #reference in a #Jabber/#XMPP talk I gave at #DebConf26.
Who knows this #fractal #fish from their #childhood?
Don't ask #AI! -
I was surprised and a little bit disappointed that (almost?) nobody got my pop-cultural #reference in a #Jabber/#XMPP talk I gave at #DebConf26.
Who knows this #fractal #fish from their #childhood?
Don't ask #AI! -
I was surprised and a little bit disappointed that (almost?) nobody got my pop-cultural #reference in a #Jabber/#XMPP talk I gave at #DebConf26.
Who knows this #fractal #fish from their #childhood?
Don't ask #AI! -
I was surprised and a little bit disappointed that (almost?) nobody got my pop-cultural #reference in a #Jabber/#XMPP talk I gave at #DebConf26.
Who knows this #fractal #fish from their #childhood?
Don't ask #AI! -
So far only the #Jabber/#XMPP and #keysigning ones, but more will be uploaded:
https://salsa.debian.org/debconf-team/public/share/debconf26/-/tree/main/slides
-
So far only the #Jabber/#XMPP and #keysigning ones, but more will be uploaded:
https://salsa.debian.org/debconf-team/public/share/debconf26/-/tree/main/slides
-
So far only the #Jabber/#XMPP and #keysigning ones, but more will be uploaded:
https://salsa.debian.org/debconf-team/public/share/debconf26/-/tree/main/slides
-
So far only the #Jabber/#XMPP and #keysigning ones, but more will be uploaded:
https://salsa.debian.org/debconf-team/public/share/debconf26/-/tree/main/slides
-
So far only the #Jabber/#XMPP and #keysigning ones, but more will be uploaded:
https://salsa.debian.org/debconf-team/public/share/debconf26/-/tree/main/slides
-
"Abgesehen von diesen grundlegenden Bedenken wären mit der Umsetzung von Interoperabilität erhebliche technische Herausforderungen verbunden, die uns unverhältnismässig viel Ressourcen kosten würden. Denn WhatsApp gibt alle Protokolle vor, und Drittanbieter müssen quasi eine Light-Version von Metas Chat-App in ihr bestehendes System integrieren."
Sehr schade, daß die @EUCommission die Umsetzung nicht auf #IETF #RFC 6120 festgelegt hat.
-
"Abgesehen von diesen grundlegenden Bedenken wären mit der Umsetzung von Interoperabilität erhebliche technische Herausforderungen verbunden, die uns unverhältnismässig viel Ressourcen kosten würden. Denn WhatsApp gibt alle Protokolle vor, und Drittanbieter müssen quasi eine Light-Version von Metas Chat-App in ihr bestehendes System integrieren."
Sehr schade, daß die @EUCommission die Umsetzung nicht auf #IETF #RFC 6120 festgelegt hat.
-
"Abgesehen von diesen grundlegenden Bedenken wären mit der Umsetzung von Interoperabilität erhebliche technische Herausforderungen verbunden, die uns unverhältnismässig viel Ressourcen kosten würden. Denn WhatsApp gibt alle Protokolle vor, und Drittanbieter müssen quasi eine Light-Version von Metas Chat-App in ihr bestehendes System integrieren."
Sehr schade, daß die @EUCommission die Umsetzung nicht auf #IETF #RFC 6120 festgelegt hat.
-
"Abgesehen von diesen grundlegenden Bedenken wären mit der Umsetzung von Interoperabilität erhebliche technische Herausforderungen verbunden, die uns unverhältnismässig viel Ressourcen kosten würden. Denn WhatsApp gibt alle Protokolle vor, und Drittanbieter müssen quasi eine Light-Version von Metas Chat-App in ihr bestehendes System integrieren."
Sehr schade, daß die @EUCommission die Umsetzung nicht auf #IETF #RFC 6120 festgelegt hat.
-
"Abgesehen von diesen grundlegenden Bedenken wären mit der Umsetzung von Interoperabilität erhebliche technische Herausforderungen verbunden, die uns unverhältnismässig viel Ressourcen kosten würden. Denn WhatsApp gibt alle Protokolle vor, und Drittanbieter müssen quasi eine Light-Version von Metas Chat-App in ihr bestehendes System integrieren."
Sehr schade, daß die @EUCommission die Umsetzung nicht auf #IETF #RFC 6120 festgelegt hat.
-
Yes, if I can't trust the server, I have to assume, that it copied all messages anyway before I read them.
For #dataHygiene a simple way to flush the #MAM would be nice, though. Needs a new #XEP or an addition to "XEP-0313: Message Archive Management", I guess.
-
Yes, if I can't trust the server, I have to assume, that it copied all messages anyway before I read them.
For #dataHygiene a simple way to flush the #MAM would be nice, though. Needs a new #XEP or an addition to "XEP-0313: Message Archive Management", I guess.
-
Yes, if I can't trust the server, I have to assume, that it copied all messages anyway before I read them.
For #dataHygiene a simple way to flush the #MAM would be nice, though. Needs a new #XEP or an addition to "XEP-0313: Message Archive Management", I guess.
-
Yes, if I can't trust the server, I have to assume, that it copied all messages anyway before I read them.
For #dataHygiene a simple way to flush the #MAM would be nice, though. Needs a new #XEP or an addition to "XEP-0313: Message Archive Management", I guess.
-
Yes, if I can't trust the server, I have to assume, that it copied all messages anyway before I read them.
For #dataHygiene a simple way to flush the #MAM would be nice, though. Needs a new #XEP or an addition to "XEP-0313: Message Archive Management", I guess.
-
CW: tech, xmpp, parenting
LGTM, but maybe ask here?
(Reminder so myself: Add mod_block_s2s_subscriptions, mod_block_subscribes, mod_muc_access_control, mod_muc_block_pm, and mod_s2s_whitelist to the #Debian prosody-modules package.)
-
CW: tech, xmpp, parenting
LGTM, but maybe ask here?
(Reminder so myself: Add mod_block_s2s_subscriptions, mod_block_subscribes, mod_muc_access_control, mod_muc_block_pm, and mod_s2s_whitelist to the #Debian prosody-modules package.)
-
CW: tech, xmpp, parenting
LGTM, but maybe ask here?
(Reminder so myself: Add mod_block_s2s_subscriptions, mod_block_subscribes, mod_muc_access_control, mod_muc_block_pm, and mod_s2s_whitelist to the #Debian prosody-modules package.)
-
CW: tech, xmpp, parenting
LGTM, but maybe ask here?
(Reminder so myself: Add mod_block_s2s_subscriptions, mod_block_subscribes, mod_muc_access_control, mod_muc_block_pm, and mod_s2s_whitelist to the #Debian prosody-modules package.)
-
CW: tech, xmpp, parenting
LGTM, but maybe ask here?
(Reminder so myself: Add mod_block_s2s_subscriptions, mod_block_subscribes, mod_muc_access_control, mod_muc_block_pm, and mod_s2s_whitelist to the #Debian prosody-modules package.)
-
I'm on #XMPP again! This time using @ejabberd
#jabber #ejabberd #selfHosted #selfhosting #selfhost #homelab
-
I'm on #XMPP again! This time using @ejabberd
#jabber #ejabberd #selfHosted #selfhosting #selfhost #homelab
-
I'm on #XMPP again! This time using @ejabberd
#jabber #ejabberd #selfHosted #selfhosting #selfhost #homelab
-
I'm on #XMPP again! This time using @ejabberd
#jabber #ejabberd #selfHosted #selfhosting #selfhost #homelab
-
I'm on #XMPP again! This time using @ejabberd
#jabber #ejabberd #selfHosted #selfhosting #selfhost #homelab
-
@markus @threemaapp @protonprivacy
Which is federated, an #IETF #openStandard, exists since 1999, is in active use and development by a diverse community, and — of course! — the best option 😉
-
@markus @threemaapp @protonprivacy
Which is federated, an #IETF #openStandard, exists since 1999, is in active use and development by a diverse community, and — of course! — the best option 😉
-
@markus @threemaapp @protonprivacy
Which is federated, an #IETF #openStandard, exists since 1999, is in active use and development by a diverse community, and — of course! — the best option 😉
-
@markus @threemaapp @protonprivacy
Which is federated, an #IETF #openStandard, exists since 1999, is in active use and development by a diverse community, and — of course! — the best option 😉
-
@markus @threemaapp @protonprivacy
Which is federated, an #IETF #openStandard, exists since 1999, is in active use and development by a diverse community, and — of course! — the best option 😉
-
IETF125 Hackathon: XEP-0490: Message Displayed Synchronization
-
IETF125 Hackathon: XEP-0490: Message Displayed Synchronization
-
IETF125 Hackathon: XEP-0490: Message Displayed Synchronization
-
IETF125 Hackathon: XEP-0490: Message Displayed Synchronization
-
IETF125 Hackathon: XEP-0490: Message Displayed Synchronization
-
It is one thing to convince your friends to use XMPP, it is another to have them easily be able to sign up their friends too.
https://txw.ca/mod-signup-keyword/
This is a mod for ejabberd which allows in-band registration with a fixed pre-shared key. It replaces the standard mod_register.
So your friends can pass this PSK to their trusted friends, and they can sign up for an account, and pass it to their trusted friends.
An XMPP Client needs to surface a UI element for the PSK to be entered, and returned to the ejabberd server. I’ve tested it with my hobby client, Mach.
