jdev - 2024-08-26

@marcan@treehouse.systems 🔗 https://social.treehouse.systems/users/marcan/statuses/113027398881744258 - Say what you want about Telegram, but it has one of the best data export/backup features I've ever seen. Fully client-driven, with real-time progress display (and even the ability to manually skip large file downloads on-the-fly). The output is a bunch of plain HTML pages with just 200 lines of pure JS (no frameworks) for some minor interactivity features, that loads instantly and looks roughly like the Telegram client itself, easy to browse and search. The JSON is one big blob with all the same data in a trivial format. The text encoding is interesting: Telegram supports rich text, but instead of in-line HTML-style markup, in the JSON it's encoded as JSON objects representing the different spans of text with different format. Very clean. Something like this might also be nice in xmpp.

> representing the different spans of text with different format. hey, that' s XEP-0394 ;) ✏

nicoco__: Slidge is not using XEP-0100 (Gateway Interaction), is it? It seems to be using a "register" command with XEP-0050 instead, any reason for that?

goffi: yes. the reason is 0077 is single step, single form

when that's enough, it uses it

but sometimes, we need a 2FA code by email, SMS, or official apps…

This is one of the reasons I _have_ to write "XEP-xxxx Gateway Interaction of the future" one day…

Slidge also does not respect the part of XEP-0100 where you're supposed to log out from the bridged network when you go offline - this just does not make sense with mobile devices, and think about everyone expects gateways to act as bouncers…

nicoco__: If I'm not mistaken, you can use arbitrary data form with XEP-0077, which can use several steps.

nicoco__: oh, yes the log-out part is clearly outdated.

A data form cannot have several steps

That is the reason to use XEP-0050 with nodes like jabber:iq:register to mimick this

haha I was about to ping you singpolyma

Oh right I'm confusing with ad-hoc commands.

I tried to write a XEP to extend IBR to multi step once, but that was soundly hated. I think 0050 is a better solution anyway

So XEP-0050 with a "register" node is the recommended way nowadays? Is there any standardisation of this or it's just de-facto standard?

I use the node "jabber:iq:register" and treat it specially in UI sometimes. But no I haven't XEP'd it, it's just documented in my wiki right now

I'm asking because I've started work on my email gateway, and I was going the XEP-0100 way.

If one step is sufficient for you then using IBR is fine

Are you going to need registration at all for an email gateway?

for IMAP/SMTP credentials yes.

Ah interesting, you're going that way. I understand