XSF Discussion - 2018-03-07

{xep 155}

jonasw: Stanza Session Negotiation (Standards Track, Draft, 2016-01-20) See: https://xmpp.org/extensions/xep-0155.html

Are we devs going to drown in CFEs now?

Yes, you are!

Zash, first the editors are going to drown in CFEs ;-)

Yay, I've got another change into XEP-0045! Two more and I've fixed it sufficiently to not need MIX any more! 🙌

I'm not convinced :)

Well, I guess if you switch it to work on bare JIDs, make occupancy persistent, synched with the user's server, and then add pubsub nodes you'd be most of the way there. You'd also have MIX.

Kev, MIX doesn’t really sync with the users server or does it?

IIRC MIX does not handle s2s link downtimes

The state of which rooms you're in does.

jonasw: MIX contains strong words about ensuring consistency over s2s failures, but no hints for implementations on how to actually achieve that.

something something s2s SM

I'm really curious to see that play out in the wild.

I've got popcorn and spectator seats.

I might not even veto MIX in case it comes in fast enough

Ge0rG: that popcorn will be pretty stale by the time mix gets implemented

daniel: touché

well played…

Servers MUST NOT include the <stanza-id/> element in messages addressed to JIDs that do not have permissions to access the archive, such as a users’s outgoing messages to their contacts. However servers SHOULD include the element as a child of the forwarded message when using Message Carbons (XEP-0280) [3]

why is this a SHOULD?

this makes the whole reason we have mam:2 useless

how do we go from "I made this strange but useful-to-me thing by tying 3 different proprietary silos together" to "I made this strange but useful-to-me thing with XMPP" ?

https://www.twilio.com/blog/2018/03/iot-poop-button-python-twilio-aws.html

is it that they don't know about XMPP or is it just shinier to use proprietary silos?

moparisthebest: it's because there are more people who know http than xmpp, and because xmpp just lacks the right abstraction layer for IoT

No, it's because it's infinitely easier to use proprietary silos that have good support and nice HTTP APIs.

(too late; what Ge0rG said)

all that looks way harder than how I'd probably do it, but meh

all xmpp needs is lots of dev advocates who write about poop buttons...

how will the poop button developers get paid?

true story; fippo ++

💩

Zash, shitty

💸

I've done similar things but I guess they just aren't fancy and I don't blog about them

I'm curious about how well emojis work in non-desktop XMPP clients

moparisthebest: Do things and talk about them.

waqas, mobile you mean? pretty well

I'd think they would work better than on the desktop ones, no?

waqas, in console it just works, if you have a recent enough glibc and a font.

like when the amazon buttons came out, when you pushed it it sent out an ARP request, and I called sendxmpp

waqas: Better than on desktop probably

but it's trivial, does that stuff require writing about?

On the more tightly controlled mobile system you presumably have nice built-in fonts for it and support in the application platform.

need to figure out how to load my own font into QWebEngineView >.>

Zash: I was also thinking of CLI clients, do those actually show emojis well? I'd expect font issues

waqas, yes.

moparisthebest: the problem with that statement is two fold: 1) it's probably not trivial for most people, 2) it's not about things being difficult, we don't need people to blog about difficult or complex things as much, we want to show that you can do things simply, so if it is actually trivial (or at least simple), blog away!

waqas, https://sotecware.net/images/dont-puush-me/KmzOKUa0WA5-e_lLWT5Bx0s9lYxOaSOtqLcl1_tTv18.png

Interesting, simple projects are what attract people who will spend a weekend doing it. If it's not trivial, most likely no one wants to waste too much time on it.

waqas: https://www.zash.se/upload/3sakjSXMvw0y.png

waqas, https://linkmauve.fr/files/wayland-screenshot-2018-03-07_21-39-01.png

Ah, too late.

I have a blog, but my last blog post was about new blog software on april 24th 2013 lol

Tho my screenshot has Ge0rGs plugin

and the last one before that was a guest blog poster in 2006

super active, in other words

my terminal is not that fancy :( https://i.imgur.com/SF16kJf.png

fippo: what we need is a compelling abstraction layer with appropriate libraries. Something where you define your sensors and actors in a human readable way, eg. "button, two-state", "230V relais", and then those objects automatically log into your private server and you can define rules like "button DEADBEEF triggers relais FOOBAR"

that sounds like a tool you build using something like xmpp in the background

That seems a bit specific to IoT (I don't disagree, but I'd start with decent, well-documented libraries in a number of popular languages that hide the XMPP specifics from you as much as possible…)

in general I'd say that's too much overhead and too restrictive

but it seems like what all these proprietary APIs do, so maybe it's what people want

fippo: what we need is a compelling abstraction layer with appropriate libraries. Something where you define your sensors and actors in a human readable way, eg. "button, two-state", "230V relais", and then those objects automatically log into your private server and you can define rules like "button DEADBEEF triggers relais FOOBAR"

SamWhited: yes, that's very specific to IoT, but it's something that we need to differentiate over MQTT, CoAP and other contenders

this call to experience

should only people answer that implemented the xep fully?

It's kinda like Last Calls

or is it in general of interest what parts are used for which use case in clients?

lovetox: why you didn't implement it or why you only partially did would be useful too.

use cases are great

k thanks

If you feel that you can answer any of the questions then that's surely useful info.

https://news.ycombinator.com/item?id=16536254 'Slack' turning off their irc and XMPP gateways :p

whu

Or how walled gardens first expose standard protocols to get the nerd crowds to root for them, and once they obtain some critical mass stop with that.

who needs/use slack anyway...

matrix otoh is somewhat useful.

still <3 XMPP.

ThurahT, a few millions of users, at least.

The answer to "who needs/use slack" is a fairly large set of organizations :)

inconceivable!

I’ve had to use it for a client.

waqas: You gon' have fun now?

My company uses it. There's quite a bit in the UX that I wish XMPP clients had.