pep., re https://github.com/xsf/xeps/pull/986 I wonder if the type thing should also be mentioned under https://xmpp.org/extensions/xep-0277.html#node_config
looks good to me, i'm just wondering how I can migrate to that
j.rhas joined
pep.
yeah.. migration is always "fun". Setting the type on creation for a start (to eventually stop creating type-empty nodes), then set the type on type-empty nodes when writing to them? or if you can detect signs of microblog such as presence of id='0' etc.
debaclehas left
pep.
I also need to mandate that for comment nodes right
goffihas left
DebXWoodyhas joined
sonnyhas joined
sonnyhas left
sonnyhas joined
sonnyhas left
adityaborikarhas left
adityaborikarhas joined
neshtaxmpphas joined
sonnyhas joined
adityaborikarhas left
adityaborikarhas joined
Marandahas left
Marandahas joined
j.rhas left
j.rhas joined
debaclehas joined
adityaborikarhas left
adityaborikarhas joined
xeckshas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
j.rhas left
pep.
Zash, pushed! Thanks
pep.
Re comment nodes I'm not entirely sure.
pep.
I guess whether it's on PEP or PubSub doesn't change the fact that the node will be named urn:xmpp:microblog:0:comments/ID. But it might be good for consistency
pep.
Also I was gonna add a "MAY" set pubsub#type on PEP (anyway). For consistency always, even though it's also obvious here
pep.
It's probably the same code that's gonna be used here so at least saying that it's a thing may be good
Zash
I wonder if MUST is a bit strong (for the other thing). Is #type even widely supported?
Zash
The field
pep.
I find the XEP a bit useless without MUST tbh
pep.
Well, this change, rather. But the XEP becomes unusable without the MUST the second another spec uses pubsub + atom
j.rhas joined
Zash
That's already a thing that's done, e.g. fetching rss/atom feeds and pushing into pubsub, or our commit (etc) notifications
pep.
Here you go
pep.
I'm not saying I don't want a tool reading "generic" pubsub+atom (whatever that means), but I definitely don't want a tool editing my pubsub+atom extension labelled "not-microblog" with microblog rules
krauqhas left
krauqhas joined
mukt2has joined
Zash
Hm. I've got a thing that derives a <body> for pubsub notifications, but it seems it bases it on the payload xmlns, not the #type
Steve Killehas left
Steve Killehas joined
goffihas joined
mukt2has left
krauqhas left
krauqhas joined
papatutuwawahas left
Syndacehas left
LNJhas joined
krauqhas left
krauqhas joined
antranigvhas joined
alameyohas left
alameyohas joined
sonnyhas left
sonnyhas joined
papatutuwawahas joined
stpeterhas joined
stpeterhas left
alameyohas left
alameyohas joined
neshtaxmpphas left
moparisthebesthas joined
sonnyhas left
sonnyhas joined
sonnyhas left
antranigvhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
krauqhas left
sonnyhas left
krauqhas joined
sonnyhas joined
sonnyhas left
neshtaxmpphas joined
sonnyhas joined
sonnyhas left
alameyohas left
alameyohas joined
sonnyhas joined
Shellhas left
sonnyhas left
andrey.ghas joined
Nano4BeingYouhas joined
sonnyhas joined
Shellhas joined
Syndacehas joined
Andrzejhas left
sonnyhas left
Andrzejhas joined
krauqhas left
krauqhas joined
Shellhas left
antranigvhas joined
antranigvhas left
sonnyhas joined
edhelas
https://xkcd.com/2365/
mdosch
It's two days now and I still don't understand Jabber + TLS = e2e²…
florettahas joined
flow
Am I the only one who finds it remarkably that xkcd #2365 does not mention Matrix?
https://xkcd.com/1810/ didn't mention neither jabber nor xmpp.
mdosch
> Jabber.org (based on XMPP) is a communications protocol based on XML that was developed in 1999. The Jabber protocol could be used with Transport Layer Security (TLS) to have a secure communications service.
https://www.explainxkcd.com/wiki/index.php/2365:_Messaging_Systems
mdosch
Never saw that wiki before. 😂
LNJhas left
LNJhas joined
sonnyhas left
sonnyhas joined
adityaborikarhas left
adityaborikarhas joined
j.rhas left
j.rhas joined
Andrzejhas left
sonnyhas left
sonnyhas joined
j.rhas left
j.rhas joined
sonnyhas left
adityaborikarhas left
Andrzejhas joined
sonnyhas joined
eevvoorhas joined
stpeterhas joined
stpeterhas left
sonnyhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
pasdesushihas joined
Andrzejhas left
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
alameyohas left
alameyohas joined
krauqhas left
krauqhas joined
Andrzejhas joined
Nano4BeingYouhas left
Shellhas left
pasdesushihas left
pasdesushihas joined
Andrzejhas left
andrey.ghas left
adityaborikarhas joined
Shellhas joined
Wojtekhas joined
Steve Killehas left
Steve Killehas joined
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
Andrzejhas joined
Neustradamus
Mistake, it is XMPP since 2004, the original name was Jabber in 1998.
Jabber.org is an XMPP service.
archas left
archas joined
j.rhas left
pasdesushihas left
pep.
Neustradamus, maybe you should propose a change on that wiki?
pasdesushihas joined
j.rhas joined
krauqhas left
krauqhas joined
pasdesushihas left
Shellhas left
florettahas left
florettahas joined
pasdesushihas joined
Andrzejhas left
Zash
TOPIC: Another episode of the never-ending XHTML-IM vs Message Styling story
Daniel
Anyway I think what ever proper solution comes out of xhtml-im2 or out of body markup or what ever is independent of what we do with 393
eta
Daniel: agreed
pep.
Yeah I didn't like the proposal made during summit either tbh..
jonas’
(for anyone who wants context, start here: https://logs.xmpp.org/council/2020-09-30#2020-09-30-0b1875408a3ee1bb )
Andrzejhas joined
Zash
Random comment: I like the way that SVG has attributes mirroring CSS properties, which seems somehow easier to deal with.
Daniel
I mean the point raised during summit (remember summits?) of not wanting two truth is also valid and should be taken into consideration
pep.
Daniel, sure. Which makes me say again "What pains me most is devs thinking this is actually a good solution"
jonas’
Zash, but then SVG still has CSS to make things more confusing
Daniel
But again independent of 393
Zash
sum-mit???
Kev
I think that is right in principle. Although I think that if you added <strippable/> (which, as noted in https://mail.jabber.org/pipermail/standards/2020-June/037514.html is going to be a huge benefit to Accessibility) 393 would actually be Good Enough, rather than needing immediate replacing.
jonas’
strippable, which would be a SHOULD or MUST to add? being equivalent to the opt-in I’ve been asking for all the time?
Kev
jonas’: I think you SHOULD add it if you determine(wave hands) that the user intended the markup - e.g. because you rendered it that way on the text input.
pep.
And poezio will never add the flag unfortunatley, so receivers will never know
Kev
Things continue to render it without the strippable, but they have to render the control characters.
pep.
Fortunately for receivers, poezio is not the most widely used clients out there
Kev
So I don't claim that by adding this 393 would be the perfect solution (to what I think is an impossible problem), merely that it makes 393 better.
jcbrandhas left
jcbrandhas joined
Shellhas joined
Neustradamus
pep.: XMPP + TLS or XMPP or other?
jcbrandhas left
jcbrandhas joined
pep.
I don't know, whatever you think is best. Maybe you can be nice with them. XMPP was after all called "Jabber" at the beginning, and the author does still use IRC so I wouldn't be surprised if they still think of XMPP as something from that time
pep.
Wasn't it called Jabber still when OTR came up? :P
pasdesushihas left
eevvoorhas left
pep.
arf, stpeter replies to #986 and possibly swipes all the +1 I was gonna get :(
It will be really good if we can plan a migration of mail.jabber.org to mail.xmpp.org...
debaclehas left
j.rhas left
j.rhas joined
APachhas joined
j.rhas left
j.rhas joined
mukt2has joined
werdanhas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
Andrzejhas joined
j.rhas left
j.rhas joined
archas left
archas joined
archas left
archas joined
j.rhas left
j.rhas joined
APachhas left
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
archas left
archas joined
eevvoorhas joined
Andrzejhas left
APachhas joined
sonnyhas left
sonnyhas joined
disgyzehas left
disgyzehas joined
Daniel
pep.: if the goal is to find all mircoblogs. Doesn't it matter to what value the type is set to as long as its known and agreed upon?
pep.
To “Here the payload is Atom, right?” I was gonna reply “I'm saying I wouldn't define the payload as Atom, no.”.
pep.
The goal is..
Alexhas left
pep.
to be able to distinguish what kind of payload that is. Now it seems peter and I are disagreeing on what payload means..
pep.
Not especially microblog
archas left
archas joined
archas left
archas joined
pep.
Say I publish my new spec also using pubsub + atom with different but very specific rules about how to handle Atom stuff that is also different from how the Atom spec defines things, I can, right? It's my spec.
pep.
Now I don't want microblog clients coming on my stuff and doing non-compliant things
pep.
And I guess they also wouldn't want that from me
mukt2has left
mukt2has joined
flow
IMHO pubsub#type should not define the pubsub node's payload type, but the node's type. and the node's type defines which payload(s) you may find in the node's items
flow
Neustradamus, did it occur to you that explainxkcd.com may be not related to xkcd? because it looks that way
sonnyhas left
sonnyhas joined
Andrzejhas joined
pasdesushihas joined
sonnyhas left
waqashas joined
pasdesushihas left
goffihas left
archas left
archas joined
archas left
archas joined
sonnyhas joined
Lancehas joined
Yagizahas left
Yagizahas joined
sonnyhas left
sonnyhas joined
sonnyhas left
mukt2has left
sonnyhas joined
sonnyhas left
APachhas left
Shellhas left
Shellhas joined
archas left
sonnyhas joined
APachhas joined
werdanhas left
Yagizahas left
Alexhas joined
mukt2has joined
sonnyhas left
eevvoorhas left
debaclehas joined
mukt2has left
Andrzejhas left
waqashas left
pasdesushihas joined
sonnyhas joined
pasdesushihas left
lovetoxhas left
sonnyhas left
sonnyhas joined
sonnyhas left
Neustradamus
flow: Have you looked the source?
- https://xkcd.com/2365/
Neustradamus
The problem is here
Neustradamus
After the update, the picture will be updated in explainxkcd.com