> Your message could not be delivered for more than 4 hour(s).
> It will be retried until it is 5 day(s) old.
Zash
> <standards@xmpp.org>: connect to atlas.jabber.org[208.68.163.215]:25: No route to host
Ge0rG
That's quite unfortunate, given tonight's election
Zash
Ehm
Zash
Only port 25? Does this ISP block port 25 out?
Zash
Or is my firewall confused?
jonas’
wfm
adiaholichas left
Ge0rG
Zash: tcptraceroute will tell you
Zash
Looks like
Zash
I find our lack of IPv6 ... disturbing
Zash
From laptop: Ends in router, as expected.
From server: Ends far away with some ISP-named thing.
Lancehas joined
Lancehas left
Zash
I guess I'll have to call them and tell them I know why but please open the port
SouLhas joined
vaulorhas joined
adiaholichas joined
Bhas left
adiaholichas left
daniel
theThedd you agree with #1001, right?
daniel
because then I'll just trust the 'long and productive conversation' you two had and vote +1 instead of trying to understand all the side effects
Zash
I read the 'long and productive conversation' and I got the impression that it did not end with a conclusion or consensus. It just ended.
flow
I wonder why nobody asked what CommonMark would do :)
Bhas joined
Zash
One could ask why there were only two participants in that thread
Lancehas joined
daniel
because it's a bad combination of too complex and not interesting
Kev
I was following the discussion but didn't disagree with anything Tedd said.
Kev
Especially what was said about look-ahead. I started implementing a 393 parser for Swift and gave up in the end. I started thinking it should be trivial, and it wasn't.
jonas’
how am I not surprised
flow
Zash, for me, it's probably that I would simply re-use CommonMark and exploit its existing ecosystem of libraries
Zash
Just bring back XHTML-IM
Kev
jonas’: There are many things you could be not surprised about there. That I agree with Tedd, that I misestimated how easy it was, that it wasn't easy, ...
jonas’
Kev, the fact that it isn’t as trivial as it looks on the outside
Lancehas left
adiaholichas joined
Kev
I wonder how many people have implemented it successfully. I guess we found that out during LC, but I don't remember.
jonas’
no, during LC, we found at best out how many people *thought* they implemented it successfully
Kev
Well, yes.
Kev
I don't remember how many that was either, though :)
adiaholichas left
adiaholichas joined
Ge0rG
The implementation in yaxim is good enough™
Ge0rG
Also it's shamelessly stolen from another client. Should have created a pluggable android library.
Ge0rG
That was the one part that doesn't depend on the underlying XML stream parser, so could really be its own useful standalone component
adiaholichas left
Bhas left
adiaholichas joined
Bhas joined
moparisthebesthas left
Bhas left
moparisthebesthas joined
Bhas joined
jonas’
ehhh
jonas’
> Unless noted otherwise by the XMPP Extensions Editor when announcing a Council vote, the voting period shall be ten (10) days.
dwd, you sent a mail on Stickers to the mailing list, but in a separate thread and your statement "none of these are blocking though" may be read as a +1 evote ✎
jonas’
dwd, you sent a mail on Stickers to the mailing list, but in a separate thread and your statement "none of these are blocking though" may be read as a +1 vote ✏
jonas’
but I’m not 100% sure -- is this a +1 vote?
Zash
jonas’, +0 on 1001 fwiw, haven't worked up the nerve to call and get port 25 unblocked yet
jonas’
Zash, k
theTeddhas joined
theTedd
daniel, #1001 is acceptable to me; it's a minor change to clarify the implementation based on an obscure edge case, so it will mostly go unnoticed anyway
theTedd
jonas’, Dave did vote on stickers, but on council for some reason - https://mail.jabber.org/pipermail/council/2020-November/004444.html