Tigase @tigase@mastodon.technology

The XMPP universe is going at full speed this month!

Checkout the newsletter, with lots of software updates and specifications progress... Including a tiny summary of the XMPP Summit!

https://xmpp.org/2020/02/newsletter-04-february/

#xmpp #jabber #decentralised #federated

What I learned this #FOSDEM and at the #summit:
The #xmpp situation on #ios is far better than I imagined :)

#siskinim

It seems that Push Notifications do work on SiskinIM from @tigase
, Monal and ChatSecure

@tagomago @tigase I'm still so wasted that I didn't even realize that you were mentioning me directly :P

@tigase is also present at the @xmpp booth in case you are at #fosdem :)

@tagomago check out @tigase, they have a client called SiskinIM!

@tigase a friend wants to let you know that since the latest release #BeagleIM on Mac is a complete joy to use, he completely replaced #imessage with it now
#xmpp #omemo

Topic 7: Why Push Notifications are not enough?

Push on iOS sucks and appears to be unreliably. Additionally the Push XEP-0357 lacks support for different types of priorities. Therefore spam messages from strangers will always alert the user as there are no silent notifications.

Tigase proposes some very interesting solutions to current push issues, like using encryption to hide message contexts inside push notifications from the push service itself.

@Photor @farhan Yeah, I know... every client has its downsides... You can improve situation by reporting issues to the developers and give them some feedback. Tigase can be found on Mastodon and is quite responsive, but they prefer issues reported on Github of course.
Same applies to Monal as well.
In both cases you can also join the MUC (monal@chat.yax.im or tigase@muc.tigase.org).

Happy new XMPP year!
The XMPP newsletter is out, although late... Sorry for this.
Read it online:
https://xmpp.org/2020/01/newsletter-14-january/
Subscribe:
https://xmpp.org/newsletter.html

@tigase - in the last hour I did some debugging with Zash from Prosody and we seem to have solved the issue...
In the end it was a typo in the config: "legcacy_ssl" instead of "legacy_ssl" setting....

Ohmy... *sigh*

Siskin is now happy as well... :)

@tigase

I agree that XEP-0384 needs an upgrade. For a start, its discovery mechanism (§ 4.2) is non-standard. It should advertise itself via XEP-0030 instead, and then it could also inform peers of whether out of band data is also encrypted (and how) or not.

@Muto @vecna @stevenroose