Link MauveAfter having written a Council application, and subsequently reading the other applicants’, I am hereby not applying this year.
andyhas left
Link MauveI think there are much needed ideas in there, and will be happy to see how they pan out. :)
remkohas left
kokonoehas joined
kokonoehas left
remkohas joined
kokonoehas joined
pdurbinhas joined
Danielhas left
dwdhas joined
Danielhas joined
pdurbinhas left
Danielhas left
remkohas left
Danielhas joined
mukt2has joined
mukt2has left
adiaholichas joined
Danielhas left
adiaholichas left
adiaholichas joined
Danielhas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
pdurbinhas joined
andyhas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
remkohas joined
waqashas left
waqashas joined
mukt2has joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
waqashas left
waqashas joined
adiaholichas left
waqashas left
waqashas joined
kokonoehas left
adiaholichas joined
krauqhas joined
adiaholichas left
adiaholichas joined
kokonoehas joined
kokonoehas left
mukt2has left
krauqhas left
Tobiashas joined
krauqhas joined
kokonoehas joined
Danielhas left
Shellhas left
ralphmhas left
ralphmhas joined
mimi89999has left
mimi89999has joined
remkohas left
Danielhas joined
remkohas joined
lskdjfhas joined
pdurbinhas left
remkohas left
goffihas joined
Danielhas left
Danielhas joined
karoshihas joined
Danielhas left
moparisthebesthas left
moparisthebesthas joined
adiaholichas left
Danielhas joined
adiaholichas joined
mukt2has joined
xalekhas left
wurstsalathas joined
mathijshas left
mathijshas joined
kokonoehas left
kokonoehas joined
kokonoehas left
jonas’oh wow
jonas’a pep
mukt2has left
jonas’I am amazed, this is going to be a fun election
remkohas joined
Ge0rGEspecially with multiple candidates running for both, this guarantees some i interesting vote dynamics. Will we need a second round?
Guushas left
alameyohas left
Guushas joined
kokonoehas joined
mathijshas left
mathijshas joined
alameyohas joined
jonas’reacts with 👍
remkohas left
remkohas joined
debxwoody> Link Mauve: Existing thing already using gloox?
I'm starting to use and understand gloox.✎
Steve Killehas left
Steve Killehas joined
debxwoody> Link Mauve: Existing thing already using gloox?
I'm starting to use and try to understand gloox. ✏
Ge0rGjonas’ [08:58]:
> /me reacts with 👍
/me slaps jonas’ with a large trout
Zashhas left
Zashhas joined
Nekithas left
jubalhhas joined
LNJhas joined
remkohas left
remkohas joined
pdurbinhas joined
remkohas left
remkohas joined
KevIs gloox still maintained? (as opposed to Swiften)
KevAh, looks like it is, yes.
winfriedhas left
winfriedhas joined
flowKev, Swiften is not maintained any more?
KevSwiften is. I thought Gloox wasn't, but it is.
flowahh, got it
debxwoodyI think there is just one developer. So, I will try to have a look into the code. Maybe I can help 🤷♂️
pdurbinhas left
LNJhas left
jubalhhas left
emushas joined
marc_has joined
winfriedhas left
winfriedhas joined
kokonoehas left
kokonoehas joined
Nekithas joined
mathijshas left
mathijshas joined
winfriedhas left
winfriedhas joined
MattJhas left
MattJhas joined
marc_has left
Nekithas left
mukt2has joined
Marandahas left
Marandahas joined
mukt2has left
adiaholichas left
adiaholichas joined
Link Mauvedebxwoody, ah sure, so I pushed my (WIP, still segfaulting) code to https://github.com/linkmauve/bonzomatic/tree/xmpp
Link MauveI might move to Swiften eventually, nothing is set so far.
Link MauveI also don’t implement the Jingle part of SXE yet.
Ge0rGsegfaulting XMPP client. What could go wrong?
Link MauveAlso once it doesn’t segfault anymore, I will probably upstream the SXE StanzaExtension so that other people can benefit from it, even if I end up not using gloox.
Link MauveGe0rG, segfaulting text editor, even worse.
Ge0rGEverybody knows that text editors are turing-complete and you MUST NOT open untrusted documents in them
Link MauveWell, this one is a bit special, it compiles and executes the code the user is typing directly as its background.
Link MauveIt’s completely at the mercy of the OpenGL driver for proper behaviour.
Ge0rGThe things that my imagination draws up in the intersection of XMPP, OpenGL and text editing are... weird
Link Mauve^^
Link MauveI like mine too. :)
ZashOh, bonzomatic!
ZashIt didn't run on my machine 😞
jubalhhas joined
Link MauveZash, it previously was in my plans to lower its OpenGL version for it to run on my netbook, before said netbook stopped booting altogether…
Link MauveBut there is no reason for it not to be able to target e.g. OpenGL 3.3 for snb users.
ZashHm, that was before I bought my new laptop, maybe it works there
Link MauveWhich OpenGL version do you have? It expects at least 4.1.
Link MauveI guess because Apple will never go higher than that.
SeveHey Link Mauve! Is that a collaborative editor? I was looking for an editor to do "pair-programming" sessions. I found Atom + Github, but that requires Github stuff
Kevvscode's sharing stuff for pairing is actually excellent.
ZashThe what now?
KevZash: @me?
Ge0rGsharing is ~caring~ pairing?
marc_has joined
Kev( https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare was what I was talking about )
ZashKev: Yeah, I haven't seen anything like that in vscode. Plugin or whatsitcalled?
kokonoehas left
ZashCool
KevI typically use it by having an external video call on at the same time as a live share just for the code/terminal/debuggerer, although I believe it does have inbuilt audio stuff in a sister extension if you prefer.
flowSeve, https://www.saros-project.org/
kokonoehas joined
pdurbinhas joined
adiaholichas left
LNJhas joined
debaclehas joined
adiaholichas joined
pdurbinhas left
mathijshas left
mathijshas joined
mathijshas left
mathijshas joined
j.rhas left
goffihas left
Link MauveSeve, it’s not, I’m making it into one.
Link Mauve(Sorry, had breakfast with my sister.)
pep.flow: that's only with eclipse?
Link Mauveflow, larma, https://github.com/linkmauve/xeps/tree/xep-0234 contains some changes to fix Jingle-FT which imo will require a namespace bump. My plan is to then request a Last Call.
flowLink Mauve, already tracked/noted at https://wiki.xmpp.org/web/XEP-Remarks/XEP-0234:_Jingle_File_Transfer. Although I didn't see a specific change which would require a namespace bump, but I didn't had a close look
flowpep., there is also an intelliJ plugin IIRC
Seveflow, Kev thanks for sharing
flowSeve, of course there is also gobby
flowhttps://github.com/gobby
Link Mauveflow, the main breaking change is in the current version, the addition of <hash-used/> and making it mandatory.
Link Mauveflow, sadly unmaintained. :(
SeveLink Mauve, what is your motivation? (I did not know that tool but it is great if you are adding support for that :D)
Link MauveBut it may be a good base to build on top of SXE, I haven’t looked into that yet.
flowIIRC the wire protocol of gobby is also unspecified
Link MauveSeve, writing shaders together with a friend. ^^
flowI once tried to compare it with SXE
SeveLink Mauve, super!
LNJhas left
Wojtekhas joined
LNJhas joined
sonnyhas joined
larmahas left
larmahas joined
mukt2has joined
danielepadmonte39has joined
debaclehas left
danielepadmonte39has left
jubalhhas left
jubalhhas joined
mukt2has left
kokonoehas left
kokonoehas joined
Link MauveKev, do you happen to know which protocol they are using? Also the license isn’t one I recognise, and they don’t seem to publish the extension itself in their repository, only some documentation and code samples.
Link MauveSo I guess it is non-free?
Zashhttps://marketplace.visualstudio.com/items/MS-vsliveshare.vsliveshare/license
Doesn't read like an open source license to me
Link MauveYeah.
Link MauveSo not really usable for the purpose of writing a compatible text editor.
remkohas left
larmaLink Mauve, I honestly don't see why your changes require a namespace bump. This is just clarifications IMO
larmaOr "fixes" of where the XEP was inconsistent
pep."Clarification" :(
jonas’larma, problem is, if there previously were two ways to interpret a text, and there’s now only one, the two versions are not always interoperable
ZashCan a thing following the previous version talk to a thing following the new version?
larmajonas’, in this case they are and it's not even a big deal
adiaholichas left
jubalhhas left
larmaFrom the current XEP 234:
> Either a <hash/> or a <hash-used/> element MUST be included when offering a file. [...] One or more <hash/> elements MUST be present when offering a file, but those elements MAY be empty if the hash has not yet been computed. [...] At any time during the lifetime of the file transfer session, the File Sender can communicate the checksum of the file to the File Receiver. This can be done in the session-initiate message [...] After the session-initiate message, this can also be done [...] In such a case however, the session-initiate message MUST contain a <hash-used/> element.
sonnyhas left
remkohas joined
sonnyhas joined
larmaSo according to current XEP the only strictly correct implementation by the text of the XEP of providing the hash later is to have both empty <hash/> and <hash-used/> which obviously makes little sense. The only example covering this usecase, Example 16, only has <hash-used/> and no empty <hash/>. To me it's obvious that the "One or more <hash/> elements MUST be present when offering a file, but those elements MAY be empty" is an artifact from before <hash-used/> was introduced. I don't see why clarifying this needs a namespace bump. As a side note: the introduction of <hash-used /> in 0.18.3 didn't bump the namespace
pdurbinhas joined
larma"have both empty <hash/> and <hash-used/>" -> "have both empty <hash/> and <hash-used/> in session-initiate"
pdurbinhas left
debaclehas joined
flowYep, that potentially could go without a namespace bump (if there are no other changes)
flowAlthough I am happy to hear if someone wants to argue why one is required…
Chobbeshas joined
rionhas left
strypeyhas joined
Link Mauvelarma, it’s not strictly about my changes, the namespace bump should have happened in 0.18.3 which introduced a new <hash-used/> element and made it a MUST where previously only <hash/> was to be there: “Either a <hash/> or a <hash-used/> element MUST be included when offering a file.”
Link MauveThus making it incompatible with previous clients which were requiring a <hash/>.
larma"previous clients requiring a <hash/>" = none?
Link MauveI guess we could also waive it as an incompatible change made to an experimental XEP and not bump anything.
Link MauveI haven’t done a field study about that, but I had an implementation (not used in any public client) which was doing that.
Link MauveClients following a version from before 0.18.3 will entirely ignore <hash-used/> as it wasn’t a thing back then, so these MUST can’t be followed by them.
larmaI agree. But versions before 0.18.3 are not XEP compliant anymore and Experimental XEPs don't provide any notion of backwards compatibility to their previous versions.
Link MauveOk, then perfect. :)
larmaAlso, afaik both Dino and Conversations don't send hash/hash-used in session-initiate at all...
jubalhhas joined
larmaIn case you are wondering, there is also good reason for that: When the file is encrypted using JET, the hash would be the *real* hash of the file, so this would leak information on the file contents to any MITM, which isn't really desirable
larmaSo if you wanted to update that, you could change the requirement of hash/hash-used to SHOULD with a note on that 😉
Link MauveSo it should be made optional?
larmaWell it could also be considered in issue of JET
larmaOr the acutal issue is that we don't have full stanza encryption 😉
Link MauveOr of not using full-stanza encryption for Jingle too.
Link Mauve.
larmaBTW, I added this table https://wiki.xmpp.org/web/XEP-Remarks/XEP-0234:_Jingle_File_Transfer#Current_implementations_checksum_behavior
emushas left
emushas joined
strypeyhas left
waqashas left
waqashas joined
Danielhas left
Danielhas joined
kokonoehas left
Danielhas left
Danielhas joined
mukt2has joined
adiaholichas joined
adiaholichas left
adiaholichas joined
mukt2has left
Shellhas joined
adiaholichas left
adiaholichas joined
kokonoehas joined
eevvoorhas joined
Wojtekhas left
pdurbinhas joined
pdurbinhas left
eevvoorhas left
edhelashas left
Chobbeshas left
nycohas left
edhelashas joined
Wojtekhas joined
nycohas joined
ajhas left
waqashas left
Chobbeshas joined
Chobbeshas left
adiaholichas left
waqashas joined
waqashas left
adiaholichas joined
adiaholichas left
adiaholichas joined
kokonoehas left
kokonoehas joined
Danielhas left
Danielhas joined
waqashas joined
Nekithas joined
adiaholichas left
adiaholichas joined
waqashas left
DebXWoodyhas joined
kokonoehas left
kokonoehas joined
pdurbinhas joined
Marandahas left
Marandahas joined
pdurbinhas left
debxwoodyhas left
lovetoxhas joined
mathijshas left
mathijshas joined
Danielhas left
Danielhas joined
lovetoxhas left
lovetoxhas joined
stpeterhas joined
winfriedhas left
winfriedhas joined
bengosthas joined
bengosthas left
mathijshas left
mathijshas joined
winfriedhas left
debxwoodyhas joined
winfriedhas joined
adiaholichas left
adiaholichas joined
winfriedhas left
winfriedhas joined
winfriedhas left
winfriedhas joined
j.rhas joined
winfriedhas left
winfriedhas joined
j.rhas left
j.rhas joined
j.rhas left
j.rhas joined
mukt2has joined
j.rhas left
j.rhas joined
Steve Killehas left
Steve Killehas joined
Nekithas left
winfriedhas left
winfriedhas joined
mukt2has left
xalekhas joined
Nekithas joined
emushas left
emushas joined
adiaholichas left
Alexgreat list of application for the next board & council