I wonder if it would be a bad idea to ban html-only mails on standards@. It breaks display of quoting badly on text-only MUAs
jonasw
markup discussions \o/
jonasw
we haven’t had any for over a week
Ge0rG
meta-markup.
Ge0rG
or markup-meta?
Ge0rG
I'm actually catching up the Styling thread from three weeks ago.
jonasw
ah, so maybe using html-only there was an act of irony? :)
Ge0rG
So far, the html-only mails I've read didn't contribute anything positive to the discussion. If it wasn't for my Council hat, I'd have blacklisted them already.
marchas joined
sonnyhas joined
Ge0rG
I'm actually glad that we are getting XEPs that define the visual format of things.
danielhas left
danielhas joined
Tobiashas joined
ThurahThas left
Guushas joined
ThurahThas joined
blablahas joined
moparisthebesthas left
Ge0rGhas joined
moparisthebesthas joined
zinid
yeah, this is very important now, when basic things are borked
intosihas joined
Ge0rGhas left
Tobias
jonasw, using the Nickname as source of coloring would have other issues, like when somebody else joins a room with the same nick they'll get the same color, suggesting to the user that they are the same
zinidhas left
zinidhas joined
Ge0rG
hey marc, any news from your XEP?
Ge0rG
zinid: why don't you volunteer some time and actually improve the protocols, then? :P
zinid
Ge0rG, typical open-source nerd detected 🙂 If you don't have the feature: write it!
jonasw
Tobias, we have that problem with anonymous MUCs in any case
zinid
while you can act like this (many do) you will end up with no users of your standards eventually
Tobias
true..so maybe in that case they should be all colored the same?
sonnyhas joined
jonasw
Tobias, that’s what is specified now
Tobias
great
daniel
zinid: I didn't think much about any namespace issues with the retry element. I guess I can move it around.
Guus
https://motherboard.vice.com/en_us/article/595zg5/sopranica-jmp-wom-cell-network-diy-anonymous seems to be xmpp based.
zinid
daniel, I'm concerned because ejabberd has validation mode now, and I don't know how to validate unknown elements or attributes
zinid
the mode is optional
daniel
zinid: yes I'll add it beneath the iq then. I just didn't think about validation. In fact this can probably cause issues in other implementations as well. (just due to a lack of a getExtension method for the error class)
zinid
right
Ge0rG
"the web address in your Jabber ID will be different—for example, motherboard@jabber.ccc.de or motherboard@xmpp.jp." That made my eyes bleed.
marc
Ge0rG: no not yet (XEP)
Ge0rG
marc: I'd really like to tear it apa.. eh.. I mean.. provide some constructive feedback
marc
Ge0rG: let me check if I have Git access at the moment
Ge0rG
Guus: that's an interesting article about an interesting tech. I remember there was an announcement of the JMP service on one of our MLs two months ago or so
Ge0rG
But I didn't realize it's more than just a VoIP bridging service.
Guus
Ge0rG: I kind of had the same experience
Guus
also: be nice to marc.
Ge0rG
I'm interested in adhoc 3G infrastructure for a completely different project, but now I forgot the MUC JID :(
Guus
bookmarks! :D
tuxhas joined
Ge0rG
Guus: I've stored it in PEP, but then it was gone after a server upgrade!!!!1!
Guus
oh no! you did a _server upgrade_ ?!
jonasw
s/upgrade/restart/?
Ge0rG
Guus: I did a _server_ _upgrade_!
jonasw
Guus, we’ll be nice to marc :)
danielhas left
danielhas joined
Guus
I see we're back to the markup fun :)
Guus
thanks Jonas :)
goffihas joined
Ge0rG
jonasw: I'm not sure whom you mean by "we"
Guustakes out his trusty smelly trout and eyes Ge0rG...
Guus
(mIRC references are one step down from bash.org quotes, right? :) )
Ge0rG
Guus: you may only swing the trout from mIRC32.exe
Ge0rG
Guus: unless you have screenshots of connecting to this MUC from mIRC, I won't take any damage.
moparisthebesthas joined
Guus
Ge0rG: although that does sound like fun, I really should stop procrastinating :)
waqashas left
waqashas joined
Ge0rG
So I found some references to jmp.chat on the archives, but only from Denver's "signature"
waqashas left
daniel
> https://motherboard.vice.com/en_us/article/595zg5/sopranica-jmp-wom-cell-network-diy-anonymous seems to be xmpp based.
Are the Americans reinventing freifunk?
Ge0rG
daniel: it rather looks like SIP and picocells
SouL
You can join discuss@conference.soprani.ca if interested on that
daniel
picocells as in 4G? are you allowed to run those in the US?
daniel: if you are a telco and have the frequencies, then yes.
daniel
ok. i'll put it into my not gonna happen box
Guus
Is anyone going to the Paris Open Source Summit this week? https://wiki.xmpp.org/web/POSS_2017
Steve Killehas left
Ge0rG
SouL: that's what I was looking for, thanks
Ge0rG
> fatal: unable to access 'https://git.zapb.de/xeps.git/': server certificate verification failed.
Meh.
Steve Killehas left
Ge0rGhas left
jonasw
Ge0rG, pluralis majestatis
jonasw
or so? ;-)
Ge0rG
jonasw: I didn't dare to suggest that. But it's probably better than personality disorder.
Ge0rGhas left
jonasw
:P
Steve Killehas joined
jonasw
no, you’ll also be nice to marc *waves hand*
Ge0rGhas left
marc
Ge0rG: it works, it uses LE
marc
Must be a problem on your side ;)
Guushas left
Ge0rGhas left
ralphmhas left
Ge0rG
marc: did you forget to add the cross-signed "root" cert to the chain?
Ge0rG
Chain of trust NOT ok (chain incomplete)
marc
Ge0rG: not that I'm aware of. It works on all clients for me
Ge0rG
marc: it's apparently not in the Root CA list on my old-ish Debian box
moparisthebesthas joined
archas left
archas joined
marc
Ge0rG: oh you're right 😬
marc
Remove the 's' for now then ;)
moparisthebesthas joined
Ge0rG
marc: https://git.zapb.de/xep.git/? 😀
Ge0rG
marc: I'm not removing the _other_ s.
marc
😀
marc
You have to wait with your "feedback" then ;)
Alexhas joined
Ge0rG
jonasw: I consider it nice to think through what another person suggests and to make constructive feedback. I also consider it nice to not steal people's time by adding large amounts of boilerplate text that simulates politeness, instead just jumping to the point. For reasons beyond my comprehension, people call me blunt and negativistic.
SouL
Haha
Zashhas left
Zashhas left
Zashhas joined
Steve Killehas left
Ge0rG
marc: the git:// URL is also a lie :(
Guushas left
Ge0rG
daniel: oh, no 3G... "WOM is XMPP over chibiArduino (thin messaging on IEEE 802.15.4)"
marc
Ge0rG: fixed
marc
Sorry
Ge0rG
marc: thanks very much :)
archas left
archas joined
jcbrandhas joined
archas left
archas joined
archas left
archas joined
archas left
archas joined
Guushas left
Ge0rG
Meh. How do you build html from an xeps/inbox/ file?
jonasw
Ge0rG, make build/inbox/foo.html
jonasw
or make inbox-html to build them all
Ge0rG
jonasw: ah, thanks. That actually makes sense
danielhas left
sonnyhas joined
Guushas left
Ge0rG
And once again, I forgot to sql-extract from my backup phone the self-messages I wrote on MIX. :sad:
tim@boese-ban.dehas joined
lumihas joined
Guushas left
Ge0rGhas left
danielhas left
efrithas joined
moparisthebesthas joined
moparisthebesthas joined
xnyhpshas joined
danielhas left
jubalhhas joined
lskdjfhas joined
moparisthebesthas joined
moparisthebesthas joined
Ge0rGhas joined
jerehas joined
jerehas left
jerehas joined
Syndacehas left
jcbrandhas left
Steve Killehas left
Steve Killehas joined
ralphmhas joined
jerehas left
jerehas joined
jonasw
zinid, FWIW, RFC 6120 schemas are incorrect, so I wonder how much pain you’ll be having with validation.
jonasw
at least afaict, the schemas do not allow for application-defined-condition in the error element, despite the text explicitly allowing that
jonasw
also, the text allows for the use of the "code" attribute for compatibility, but the schema does not
zinid
jonasw, I can leave with this and fix the validator accordingly
zinid
what I don't want is doing this constantly
jonasw
you may also be in violation of RFC 6120, because servers must simply route traffic addressed to clients (independent of their understanding), but I don’t have a quote for that right now
zinid
yeah, and in another place the RFC says you MAY validate, go figure
jonasw
I understand your general concern, but ignoring undefined attributes and elements is essentially how extensibility in XMPP works.
Guushas left
zinid
no
zinid
this is not how it should work, because there simply can be tag names collisions if we allow adding whatever anyone wants
jonasw
no, that’s why we have namespaces
jonasw
a namespace is defined in a single document
jonasw
(roughly)
Guus
for what it's worth, people in here repeatedly repeat that "schema's in XEPs are not normative" - Best beware to depend on them to much.
zinid
what's the point in this namespace if anyone can extend it?
jonasw
zinid, define "anyone"
Zash
Pretty sure our equivalent to the robustness principle is "ignore what you don't understand"
jonasw
the author and maintainer of the namespace can.
nycohas left
zinid
jonasw, you or me for example, can I use <foo xmlns='jabber:client'> for my extension?
jonasw
no
jonasw
well, you can, but that’d be stupid and asking for trouble
zinid
and <retry xmlns='http:upload:0'>?
jonasw
and nobody would approve of that
jonasw
same
jonasw
unless you’re doing this in context of a XEP-0363 update
I don’t think that the XSF would approve of a XEP update to any XEP *but* XEP-0363 which extends the http:upload:0 namespace
intosi
Only the IETF can introduce elements and attributes in the jabber:client xmlns through a replacement RFC, I think.
zinid
so, that means XSF can add whatever they want, but not others?
jonasw
zinid, sure, the XSF "owns" the urn:xmpp namespace. that’s the whole point of having a standards organization?
Zash
It's all in our heads anyways
zinid
well, of course it's up to you, but I won't change ejabberd validation style
zinid
as I disagree
moparisthebesthas joined
daniel
Zash, namespaces exists only because people believe in them?
jonasw
zinid, what would you prefer?
zinid
bumping namespace obviously
daniel
and if people stop believe the whole system will collapse?
Zash
daniel: pretty much
jonasw
zinid, that’s insanity.
jonasw
bumping the namespace is a major breakage
jonasw
also, this is an experimental XEP
zinid
jonasw, then wait for major breakage and add it in that revision
jonasw
don’t expect any type of stability in there
zinid
if this is an experimental xep I don't see a problem in bumping at all
jonasw
unnecssary namespace bumps are a bunch of the reason why "basic" things like MAM are troublesome.
zinid
but what do you expect from experimental xep?
Guushas left
Kevhas left
Flow
what I expect from any XEP: no namespace bumps for backwards compatible changes
zinid
what I expect: the protocol should be formally verified
zinid
we can debate to death, really
Guus
This touches on a comment made by Jonasw on list - it's probably not the best of ideas to apply a change when the XEP is in last-call.
danielhas left
Flow
Then we should write down that rule in xep1
zinid
yes, the rules are:
1) schemas are meaningless
2) the protocol cannot be formally verified
3) only XSF can add new elements within the same namespace
zinid
now, implement!
danielhas left
Guus
Flow: I don't mind clarifying that in XEP-0001, but perhaps we can also simply try to avoid this from occurring, and save the red tape.
Guus
As the author of the XEP is also on Council, I'm interested in how this plays out though :)
daniel
zinid: I don't understand why you would want to add new elements with the official namespace. Just use your own
archas left
archas joined
zinid
daniel, not me, but I see this quite frequently among customer's code
daniel
Is there anything stopping them from using their own namespace besides lack of knowledge (that they should do this)
zinid
because they don't want to create a namespace with a single element, I think that's their logic
daniel
i see
daniel
but you can hardly blame the system or the xsf for that
zinid
I can use validator to prevent such behaviour among customers
zinid
which works ideally, they don't even create tickets 😛
Alexhas left
danielhas left
valohas left
danielhas left
tim@boese-ban.dehas left
moparisthebesthas joined
lskdjfhas left
lskdjfhas joined
Alexhas joined
danielhas left
Alexhas left
la|r|mahas joined
ralphmhas joined
nycohas joined
Alexhas left
moparisthebesthas joined
jerehas joined
jerehas joined
moparisthebesthas joined
lskdjfhas joined
lskdjfhas joined
sonnyhas joined
jerehas left
jerehas joined
danielhas left
danielhas left
ralphmhas joined
la|r|mahas left
danielhas left
lskdjfhas joined
lskdjfhas joined
Alexhas left
nycohas left
nycohas joined
valohas joined
Syndacehas joined
Syndacehas left
Syndacehas joined
moparisthebesthas joined
moparisthebesthas joined
efrithas left
zinidhas left
jabberatdemohas joined
marchas left
nycohas left
danielhas left
Guushas left
Alexhas joined
marchas left
nycohas joined
jabberatdemohas left
vanitasvitaehas joined
vanitasvitaehas joined
Tobiashas joined
lovetoxhas joined
waqashas joined
zinidhas left
nycohas left
Guushas left
danielhas left
nycohas joined
Kev
It's only worth bumping the namespace when interop that wouldn't work without it will work with it.
marchas joined
nycohas left
nycohas joined
jcbrandhas left
Guushas left
dwd
I think it comes down to whether you see XML and XMLNS as a pragmatic solution to permissionless innovation, or as a stick with which to beat people.
dwd
Not that I'm biased here of course. ;-)
lskdjfhas left
lskdjfhas left
Guushas left
daniel
MattJ, jonasw: would you feel more comfortable if retry is a direct child of the iq?
jonasw
daniel, NO
jonasw
that violates RFC 6120
MattJ
iq can only have one child
jonasw
please don’t do that
jonasw
what you’re doing now is fine with RFC 6120, albeit weird usage of the "condition"
MattJ
daniel, do you have an objection to just using the error type for this information?
daniel
MattJ: yes. I want to know _when_ I can retry
daniel
This could be seconds or hours
jonasw
daniel, hm, how would the server know when the client can retry?
daniel
Depending on implementation
jonasw
quota cleanup cronjob something?
dwd
MattJ, Well. Errors can have two, actually. Sort of.
Zash
Could this not be in a custom element next to the error?
MattJ
dwd, ?
daniel
jonasw: we are taking about quotas like only x MiB an hour
dwd
MattJ, Error + original request.
jonasw
daniel, well, actually, you could in fact make this a child of <iq/>, but I would consider that abuse. normally an error IQ only returns the original data, if anything
Zash
I haven't looked at whatever this <retry> thing is closely enough yet
daniel
Jabber.at is doing this
Guushas left
SamWhitedhas left
Zash
a "application-specific condition element" ala retry-after t=x
Guushas joined
jonasw
daniel, FWIW, I’m fine-ish with this being a child of <error/>. I find it a bit weird, though. Maybe wrap it in a <quota-exceeded xmlns="http-upload"/> thing first? Then there would be an actual condition, with additional information on when to re-try. It also allows to re-use the <retry/> for other possible conditions (like <ebusy/> or so)
daniel
then i have to define every possible error condition instead of relying on normal errors + text
jonasw
daniel, good point
MattJ
It seems like this is a specific case though, not something that could be combined with every other error
pep.
I'm curious what's wrong with defining errors and not just dumping text
jonasw
pep., you need to foresee every possible condition
pep.
Can you not extent it later?
daniel
pep., we already have a huge bunch of 'predefined' errors
jonasw
pep., maybe first read up on the context; in this case, it’s about annotating errors with a time at which the client may re-try
pep.
jonasw, yeah I need to read stuff
daniel
jonasw, if anything i could wrap it in something like <temporal-error><retry/></temporal-error> (working title)
jonasw
daniel, as I said, I’m fine-ish with <retry/> as child of error. it feels weird, but I’m fine-ish with that.
jonasw
well, that’s not usefull at all, leave it as child of <retry/> in that case, because that’s realyl just saying "this is *really* a type='wait' error, no kidding" :)
jonasw
I have a larger problem with making substantial changes after last call begun :/
Zash
<error type='wait'><resource-constraint/><text>You exceeded the quota, try again in an hour or so</text><retry-after stamp="YYYY-MM-DDTHH:MM:SSZ"/></error> ?
jerehas left
jerehas joined
daniel
i disagree with that being a substantial change
jonasw
daniel, in hindsight, it probably was. see the amount o fdiscussion it caused.
jonasw
I also probably meant "non-editorial changes" instead of "substantial changes"
marchas left
stefandxmhas left
stefandxmhas joined
pep.
hmm, https://xmpp.org/community/mailing-lists.html, there's a members@ somewhere?
pep.
Also https://xmpp.org/about/xsf/members.html doesn't seem up-to-date, anybody knows since when? So I can PR (if I find out who's been accepted and who hasn't)
mathieui
you’re automatically subscribed if you become a member afaik
pep.
Ok. Can you give me a header I can filter on? I usually use List-ID
Guushas left
jonasw
pep., haven’t you been subscribed already?
jonasw
List-Id: XSF Members <members.xmpp.org>
jonasw
or wait, your election is still upcoming? I don’t konw
pep.
I have no email coming from members@
pep.
Maybe it's still not done yet, we'll see
mathieui
pep., it’s not done yet
pep.
cool
mathieui
it’s finalized on the 7th I think
jonasw
2017-12-06 is the meeting
moparisthebesthas joined
Guushas left
moparisthebesthas left
moparisthebesthas joined
danielhas left
ralphmhas left
danielhas left
Alexhas left
marchas joined
Neustradamushas joined
Guushas left
la|r|mahas joined
pep.has left
pep.has left
Alexhas joined
Guushas left
edhelas
daniel would it be possible to see if we can figure out the usage of SIMS in Conversations https://github.com/siacs/Conversations/issues/2637 ?
daniel
What particular feature do you need edhelas?
edhelas
basically that when Conversations upload a file it embed it using SIMS to the message, and not only OOB
edhelas
this allow other clients like Movim to have a bit more metadata about the file and create a nice thumbnail
SamWhited
I think I've asked like three times (sorry, I promise to write it down this time) but what was lacking from SIMS that OOB has that conversations uses?
Kevhas left
lovetox
nothing
lovetox
it was just there before
daniel
edhelas, mind giving me an full example of a message stanza you want me to create?
Zash
Is this going to be another one of those times where the better solution dies because an okayish method already existed?
lovetox
edhelas, i would also implement this in gajim
edhelas
that would be awesome
pep.
Zash: first come first served
lovetox
but only for httpupload in short term
edhelas
daniel I can if you want, maybe tonight, but basically everything is done here in Movim https://github.com/movim/moxl/blob/master/src/Moxl/Stanza/Message.php#L101
SamWhited
OOB/SIMS is on my list of "things to deprecate one of", so if everyone wants to go implement SIMS that would make things much easier…
edhelas
I'm doing SIMS and OOB when publishing and only SIMS when receiving
daniel
edhelas, so you put the url in the body and then set no begin and end attributes in the reference?
daniel
and you ignore the XEP MUST implement Jingle File Transfer (XEP-0234)?
edhelas
that's true, I'll put this begin and end tags
lovetox
daniel
pep.
Jingle-FT in movim when? :-°
lovetox
i think the xep means OR
lovetox
i dont see a reason why we have to implement jingle AND httpupload
edhelas
> This XEP delegates actual transport of the media data to one of the existing file-transfer XEPs. Thus a client supporting this XEP MUST implement Jingle File Transfer (XEP-0234) [2] and HTTP File Upload (XEP-0363) [4].
daniel
lovetox, are you sure? the <file> element is even in the jingle namespace
daniel
for what ever reason
edhelas
so how does it work if I want to embed a file that was just uploaded by HTTP Upload ?
edhelas
the file is not in my machine, I just have some metadata and a URL
daniel
edhelas, you tell me. you wanted me to implement the XEP :-)
lovetox
ah i think the xep just builds up on jingle file transfer negotiation
lovetox
so you have to implement the negotiation part
SamWhited
That whole section doesn't make much sense to me, I think it just needs to be reworded.
lovetox
but do not have to offer the actual jingle transport
lovetox
instead you put in httpupload
edhelas
daniel that's all valid questions :) thanks for raising them
daniel
you also need bob for thumbnails which i find very weird
daniel
i'm not gonna implement bob
edhelas
so we need to upaded SIMS, do HTTP Upload AND/OR Jingle FT
daniel
has *anyone* ever implemented bob?
edhelas
I do
daniel
weird
lovetox
no edhelas this xep builds up on jingle FT
edhelas
to do stickers sharing, the files are small enough to be shared using base64
lovetox
that does not mean you have to provide a jingle transport like socks5 or whatever
daniel
well yes. but the counterpart has to be online
daniel
which doesn't go well with the 'stateless' premise of the xep
pep.
I know a few people were talking of a jingle component (so server-side), any discussion started on this already?
edhelas
so we have to tackle again this "file sharing" discussion
daniel
edhelas, i mean I can totally implement what you are doing in that PHP script you linked earlier. that's like 10 minutes work
daniel
but i'm really not sure that has anything to do with implementing the XEP
edhelas
yeah I understand
edhelas
to br frank I'm using SIMS to pass the metadata of HTTP File Upload to the other JID, that's mostly it
daniel
edhelas, what meta data are you interested in? mime type and size mostly i would assume?
daniel
maybe file name
Guushas left
daniel
by the way I personally also regard resolution (width * height) as a nice to have because that would could allow me to allocate space for this in the UI. which this XEP is not doing.
edhelas
yup, mime and size as well, I'm not trusting them 100% but they tells me if I need to resolve the HTTP HEADER if I'm interested to build an attachement block to the message
daniel
so for me SIMS is just not doing the right thing. because i would ignore vast parts of the XEP and couldn't even but some information in there I want to put in there
daniel
*put
lovetox
sims is just not trying to be a better OOB
daniel
Sure.
lovetox
thats why it reuses jingle stuff
daniel
It's doing something completely different
edhelas
if we are improving OOB to add those tags I'd be happy
lovetox
i dont think so edhelas
lovetox
or at least i dont know how easy we can extend a xep years long in draft
lovetox
and if its good
SamWhited
I don't understand what SIMS is trying to be if not a better OOB; I agree that the XEPs focus seems a bit off, but that's fixable
lovetox
oob has a clear use case, and does it well, you can communicated a uri with a description
lovetox
really SamWhited ?
lovetox
you dont see what it trys to do beside adding metadata?
SamWhited
No, as far as I can tell it's a better OOB except that it focuses on file transfer for some reason
lovetox
you can share a file with multiple connection points for the receiver
lovetox
he can choose if he wants to request it via jingle
lovetox
or httpupload
SamWhited
Right, and that's all just sharing some metadata about the file
lovetox
or any other FT method invented in the future
Tobiashas joined
SamWhited
And basically what OOB does except in a more general way
SamWhited
It's OOB but with arbitrary URIs and some other random metadata
lovetox
what is the argument? you can add a shittone of stuff to OOB xep then its the same?
SamWhited
Can you? I don't see definitions for anything like eg. different resolutions of the same file or other things SIMS has
lovetox
i think we going in circles
lovetox
frist you tell that you dont understand what sims trys to do
lovetox
now you tell me oob does not have definitions about file resolutions
daniel
neither has sims though?
ralphmhas left
SamWhited
It doesn't, and I don't see how these two things are related; you said that SIMS doesn't do the same thing as OOB, and if that's true I don't understand what it does differently. To me it seems like it's just an improved OOB.
lovetox
daniel i think you can just add more file tags
lovetox
with different images
SamWhited
I thought SIMS specifically had that? Maybe I need to read it again
daniel
within the same reference?
daniel
how do i match a source and a file then?
lovetox
nah i think im confusing this
lovetox
this was 0084 with different avatar sizes or
SamWhited
Ah yah, this one is just thumbnail. Regardless, it was just an example. "more metadata than OOB" was the point.
lovetox
yeah ok, but whats bad about this?!
Zash
It's a pointer.
lovetox
it tries to be more general and have more info then oob
lovetox
not just a bit more, WAY more
SamWhited
I don't really care if we have more or less metadata, I just think we don't need two XEPs that do more or less the same thing
lovetox
so thats what i asked you 4 minutes ago
lovetox
18:07:50] lovetox: what is the argument? you can add a shittone of stuff to OOB xep then its the same?
tuxhas left
Guushas left
Zash
SamWhited: You are giving me the impression that we can never improve on things that already exist, since that would require overlaping protocols for some time.
lovetox
oob is a easy small xep that lets you share a description and a uri
lovetox
let it be what it is
Holgerhas left
daniel
yes. wouldn't touch oob. if anything we would create a new XEP that is a more streamlined 'here is an uri and here is some meta data'
daniel
or SIMS can move into that direction
jonasw
I’d prefer the latter
jonasw
SIMS seems like nice framework to extend
SamWhited
I agree
jonasw
the MUST support Jingle-FT is weird though
jonasw
I didn’t know about that, maybe ask Tobias what that is about?
Zash
jonasw: Why is that weird?
daniel
and the bob thumbnails are even more weird
jonasw
Zash, Jingle-FT is a rather complex beast, isn’t it?
Zash
jonasw: If it's basically a pointer to a thing available over Jingle-FT?
jonasw
it’s not necessarily Jingle-FT, or doesn’t necessarily need to be Jingle-FT
SamWhited
Jingle-FT and SIMS are completely orthogonal; SIMS isn't a pointer to a Jingle URI, it also lets you have a pointer to an HTTP Upload API, and as far as I can tell could also provide a pointer to "my proprietary thing" URI.
jonasw
or BOB
daniel
expect that it says must support jingle ft
nycohas left
daniel
and it's at least unclear how to do thumbnails without bob
SamWhited
That seems like it either means "must support using the Jingle FT metadata XML" or "must usupport Jingle FT *or* something else" and it was just poorly worded, but I guess we'd have to ask Tobias
jonasw
maybe post that to the list, daniel?
SamWhited
That and the paragraph after it confuse me though, so I suspect we just need section 5.1 reworded for clarity.
lovetox
im sure tobias just wanted to reuse already definied tags in another xep
lovetox
instead of reinventing the same tags under a new namespace
daniel
jonasw, no. i have bigger fish to fry to be honest. things I actually need for Conversations. not saying that i won't implement SIMS but let other people figure out the details
lovetox
either way i think its no problem to make this jingle agnostic
jonasw
daniel, but spark the discussion maybe?
daniel
jonasw, that's gonna get ignored anyway
jonasw
gotta love your optimism
daniel
like the one about MAM or the problems I raised with jingle-ft
daniel
and those are things i actually care about
SamWhited
MAM is being addressed isn't it? I thought Kev and Matthew responded to that and said they'd get a revision out
Kev
Hmm? Not reading context, but a MAM update is <> close to the top of my stack.
daniel
👍
Holgerhas left
nycohas joined
lovetox
i will post the questions to the list :)
lovetox
i care about sims :)
Steve Killehas left
Steve Killehas left
jubalhhas left
jjrhhas left
Steve Killehas joined
lovetox
do we really need thumbnails?
edhelas
what I'd also like to see is a way to embed URLs in general to messages
lovetox
with the metadata i can display some placeholder
edhelas
like many other messaging solutions are doing now
edhelas
having a littke thumbnail, description, title (the client will have to resolve thoses)
daniel
edhelas, isn't that what references is doing?
lovetox
edhelas thats what the end and begin is for
lovetox
so you can embed it in a message
edhelas
let me rephrase that :)
Alexhas left
Alexhas joined
edhelas
XEP-0372: reference just gives a pointer to an URI, without metadata
edhelas
XEP-0066: OOB gives a pointer to a URL with just a description
lovetox
no, it also tells you where in the text the reference is to be places✎
lovetox
no, it also tells you where in the text the reference is to be placed ✏
lovetox
with beginn and end
edhelas
XEP-0385: gives all the metadata, but doesn'yt fit well with my usage (URL only)
daniel
gf
daniel
you probably need a og extension to references
daniel
like sims but with og data
edhelas
og ?
daniel
http://ogp.me/
daniel
which if you have that you don't need sims anymore to cover your usecase
daniel
because you can put all that into og
edhelas
kind of yes
edhelas
also if I could have one generic way to attach thoses things to XMPP messages and/or Pubsub publications (that are actually Atom items as well) that would be nice
pep.
rrr heroku apps and their lack of tls :(
pep.
Or people failing to set it up correctly
archas left
archas joined
edhelas
daniel is it something that you'd like to have in Conversations ? URL/file embeding ?
isn't that exatcly would you would og and references for?
daniel
you'd have a reference that spans the entire url in this case
daniel
and the og:tile, og:description and og:image
edhelas
yup, but would you like to implement it in Conversations as well ?
daniel
in general yes. but i have the blocker not having stanza content encryption
daniel
and that's not going to be resolved any time soon tbh
daniel
it's easier for me at this point to generate that information on the receiving end
daniel
(opt in)
edhelas
yes I understand
daniel
also ironically - generating the content on might have some privacy related down sides; but to properly circumvent this you'd have to mirror the image on the sender or else you will be at least leaking the image url
vanitasvitaehas left
jjrhhas left
Lancehas joined
Alexhas left
Lancehas left
nycohas left
jubalhhas joined
nycohas joined
vanitasvitaehas joined
lskdjfhas joined
ralphmhas joined
Ge0rGhas joined
jerehas joined
Ge0rGhas left
Ge0rGhas left
archas left
archas joined
lskdjfhas joined
lskdjfhas left
lskdjfhas left
lskdjfhas left
ralphmhas left
lskdjfhas left
archas left
archas joined
lskdjfhas left
lskdjfhas left
lskdjfhas joined
jubalhhas joined
lskdjfhas joined
SamWhitedhas joined
jubalhhas joined
jubalhhas left
jubalhhas joined
danielhas left
lskdjfhas left
ralphmhas left
la|r|mahas joined
lskdjfhas left
sonnyhas joined
lskdjfhas left
zinidhas left
la|r|mahas joined
danielhas left
marchas left
jerehas joined
danielhas left
Ge0rGhas joined
jubalhhas joined
uchas left
lskdjfhas left
Holgerhas left
lskdjfhas left
lskdjfhas left
danielhas left
ralphmhas left
danielhas left
danielhas joined
archas left
archas joined
lskdjfhas joined
Guushas left
intosihas left
danielhas left
zinidhas left
Guushas left
ralphmhas left
nycohas left
nycohas joined
danielhas joined
jerehas left
jerehas joined
nycohas left
nycohas joined
jerehas left
jerehas joined
ralphmhas left
marchas left
Alexhas left
Ge0rGhas left
archas left
archas joined
Zashhas left
la|r|mahas joined
jabberatdemohas joined
jabberatdemohas left
ralphmhas left
archas left
lskdjfhas left
archas joined
archas left
archas joined
archas left
archas joined
archas left
archas joined
jubalhhas joined
archas left
archas joined
la|r|mahas left
zinidhas left
jubalhhas left
blablahas joined
edhelas
what is the standard URI format fur Pubsub nodes and items ?