-
zinid
RFCs like 7564 make me cry
-
zinid
instead of providing a simple pseudo-code there are 40 pages of stupid definitions
-
fippo
feel free to submit a draft doing so.
-
edhelas
lskdjf no, please no, it's like saying that you don't need proper validation in HTML/JS because the database can handle that
-
edhelas
SamWhited that would be nice yes :)
-
jonasw
pep., XEP-0392 offers a way to adapt the colors to a given background.
-
jonasw
or overall theme tint
-
Syndace
Is "Remko" here, the dude that wrote a mail about OMEMO key agreement recently?
-
jonasw
Syndace, sometimes
-
jonasw
yesterday or on saturday he was
-
jonasw
why are you asking?
-
Syndace
I read a lot about OMEMO recently and I want to discuss his question a little while not spamming the mailing list with probably unqualified comments :D
-
Syndace
is his nick in here remko aswell?
-
jonasw
yupp
-
jonasw
Syndace, there’s always the option of replying only to him
-
pep.
jonasw: re color generation, nice
-
Syndace
jonasw, I decided to risk it and answered the list ^^
-
Flow
Syndace, good question you posted :)
-
SamWhited
edhelas: the little tool I use isn't actually on this machine, but here's a quick one that just checks if the first argument is a valid JID: https://gist.github.com/SamWhited/faaa24d72e06903122152a5a17984fe7
-
SamWhited
Note that by default that will be using the newer version of PRECIS from RFC 8264 and Unicode 10, but there shouldn't be any major differences.
-
pep.
https://xmpp.org/extensions/inbox/bmh.html Is that Flow? What happens if a client doesn't announce any supported markup? will the other client send non-formatted plaintext? Or the same but untagged?
-
jonasw
MattJ, lovetox is having issues joining the channel, possibly the stalled s2s bug. he’s in jdev. Care to debug?
-
Flow
pep.,: what do you think would be best?
-
pep.
Is there a need for the XEP?
-
Flow
pep I obviously think so, as otherwhise I wouldn't have go through the effort writting it
-
pep.
Well the example I showed above kind of defeats the point
-
Flow
pep., your question?
-
pep.
yes
-
Flow
pep., I don't see how it defates the point
-
pep.
The markup is going to make it _as is_ to the other side in any case
-
Zash
With MAM, carbons and whatever, you have no way of knowing if all the clients that receive it supports it.
-
Flow
Ok, so maybe it's time to provide some motivation for BMH
-
Flow
I was going to wait until the offical editor annoucement, but it looks like people get into the wrong direction about what it's about
-
Zash
It would let those who understand it know for sure that it is what the sender intended.
-
Flow
Zash, that!
-
pep.
And why not xhtml-im?
-
pep.
You're assuming it's already out, right?
-
Flow
So BMH does not try to be a successor of XHTML-IM
-
Flow
It's not even meant as intermediate solution
-
Flow
The case for BMH is bridges which take Markup formated text, and send it via XMPP to an XMPP client
-
Flow
For example a Stackoverflow bot, which sends you an question and a answer
-
Flow
Or a discourse interface
-
Zash
Thing could in theory have serverside translation into XHTML-IM or XEP-future-markup-thing
-
Flow
Or a Bot which sends you status information with headings and sections and stuff
-
pep.
well the gateway/bridge would know markups the other side sends, and could translate it into XHTML-IM
-
pep.
I'm not sure more is needed
-
Flow
If you client doesn't know the markup language, fine, it will still display the text more or less nicely
-
Flow
If it does understand the markup hinted markup language, it can throw it into a converter and show it in a richful way
-
Zash
So it's equivalent to the Content-Type header in email
-
Flow
pep., Not every client supports XHTML-IM
-
Zash
Which is fine.
-
pep.
Flow, the more reasons to implement it
-
pep.
Not every client supports $MARKUP
-
Zash
Flow: pep.s point of the discovery section being fairly pointless stands tho
-
Zash
OTOH it is mandatory in XEPs
-
Flow
Zash, yep, the discovery was just a goodie I wanted to take along
-
pep.
I'm still not sure I see the point. This can be totally covered with xhtml-im
-
pep.
Flow, please do add some more details on the XEP so we can comment on it before it's accepted
-
pep.
:)
-
Flow
pep: I've responded on the editor announcement
-
Flow
Also the latest snapshot of the xep may contains more backstory: http://geekplace.eu/xeps/xep-bmh/xep-bmh.html
-
Flow
Meh, a 2 week last call for so important cornerstones like MAM feels a little bit to short
-
pep.
thanks
-
pep.
I'd like to make motivation the first requirement of a protoXEP :x
-
Zash
Isn't that usually supposed to be covered in the first section?
-
pep.
Well apparently not enough
-
Zash
Like, a problem statement or somesuch
-
pep.
"Why is this needed", "Are there existing XEPs trying to solve the same issue or similar/related ones", "How does that compare to these XEPs", etc.
-
Flow
please direct blame to the lazy me :)
-
pep.
Flow, I can see a point for your XEP here, just that it doesn't really come at a good time, with the latest events around XHTML-IM and people trying to kill it
-
pep.
Also I fear people are going to abuse it
-
pep.
And give up on xhtml-im for this
-
Zash
Was there an easy way to get schemas out of XEPs?
-
waqas
Zash: Ctrl+C, Ctrl+V.
-
waqas
Zash: You can probably use one of the xpath CLI tools to grab this: https://github.com/xsf/xeps/blob/master/xep-0016.xml#L856
-
waqas
No idea if this stuff is consistent across XEPs
-
Zash
In this specific instance I'm interested in getting schemas out of XEP60
-
Zash
And I seem to have repressed^W forgotten how XPath works
-
waqas
https://github.com/xsf/xeps/blob/master/xep-0060.xml#L6522
-
waqas
Copy paste, and split on the CDATA sections
-
waqas
Oh, it uses <xs:import /> to reference an external 'http://xmpp.org/schemas/x-data.xsd' too
-
Zash
Hm, I have this strange memory of fighting xpath or xml search tools in order to get them to spit out bare text, and giving up beacuse it's impossible.
-
Zash
Why is {pubsub#errors}unsupported a MUST?
-
Zash
Why does the implementation need to know all the things it doesn't do?
-
Zash
And isn't this the job of disco#info?