-
apollonexpectus
govanify =zosch@jabber.ru?
-
apollonexpectus
Zash =zosch@jabber.ru
-
apollonexpectus
?
-
apollonexpectus
I started out as a 14 year old lesbian 10 years ago marginalized by society and bullied in school, the daughter of two diplomats i was well travelled and read at an early age and taught by some of the best minds in the world in the intricacies of bank account cashouts.*fraud boss of international crime see PGP for details look on masterlist ahmia.fi > masterlist ExpectUs Fraud Fullz Cashout Crime Boss Hansa WSM apollon nightmare
-
apollonexpectus
none of this was a bot i type fast and i cashout fast
-
apollonexpectus
π
-
apollonexpectus
π
-
apollonexpectus
tftp 10.1.1.1
-
apollonexpectus
lol
-
apollonexpectus
--
-
apollonexpectus
'
-
apollonexpectus
select * from CASH where 'my bank account ' == > 1,000,000,000,000
-
apollonexpectus
π
-
apollonexpectus
select * from big_titty_bitches
-
apollonexpectus
select * from lesbians who love buttsex just like me
-
tom
Are there any working implementations of Jingle?
-
Neustradamus
rion: ^^
-
Daniel
tom: yes. What specifically are you looking for?
-
tom
Videocalls
-
tom
On linux
-
tom
Without a web browser
-
tom
https://upload.nuegia.net/adde0e10-bf17-487b-be96-afb7fc6ec6dc/qsbti5vpk9841.jpg
-
Holger
tom: https://desktop.jitsi.org
-
Mr.eslamo
Hi, is anyone has a book for xmpp starters ?
-
Kev
http://shop.oreilly.com/product/9780596521271.do is still the best option, I believe (author).
-
edhelas
β β β "Must Read" The Daily XMPP - 2009
-
Zash
Kev, not time for a n++th edition yet? :)
-
Kev
Zash: There are definitely interesting new things to say, although it feels like we're on the cusp of there being pretty much a whole new story about how one works with XMPP, and doing anything before that would be premature (even if we and O'Reilly were motivated to do another edition - I hate writing ;)).
-
Mr.eslamo
Thank you all, I hope if you have any advice in this technology i'm new here in this field and I hope to make good things with it
-
Zash
I remember http://shop.oreilly.com/product/9780470540718.do being pretty good, but not sure how well it has aged, with how fast the web has moved
-
edhelas
Mr.eslamo maybe https://xmpp.org/about/ could help
-
Zash
MattJ: Modern XMPP - The Book? ποΈ
-
MattJ
When "Modern XMPP" exists, I think that would be sensible
-
edhelas
if you want to understand the basics, I think the best is to open a XMPP console and start to play with it :)
-
MattJ
flow, you wrote on the list that you would review MAM (thanks for the diffs btw) - do you plan to give any feedback?
-
MattJ
otherwise I plan to request merging soon after addressing the existing feedback
-
Mr.eslamo
Zash: Thank you, I will purchase this book and I'll start using it because I have ZERO knowledge about this technology π
-
Daniel
> if you want to understand the basics, I think the best is to open a XMPP console and start to play with it :) And read the rfc
-
Daniel
People always under estimate rfcs
-
Kev
Zash: I think the issue with that one is that stanza.io is mostly unmaintaned now, isn't it?
-
Kev
Now that Jack The Moffit doesn't XMPP anymore.
-
Zash
Wasn't it using Strophe.js?
-
Zash
That's still around afaik
-
MattJ
I think you mean strophe.js? And that's maintained
-
Kev
Sorry, yes, I'm getting names muddles.
-
flow
MattJ, I plan(ed) to. But I think you can take the silence as "mosly lack of disagreement" on the proposed changes✎ -
Zash
I could check if I just reached like an inch further up my bookshelf
- MattJ reacts to flow's message with :thumbs_up:
-
flow
MattJ, I plan(ed) to. But I think you can take the silence as "mostly lack of disagreement" on the proposed changes ✏
-
Zash
Yup, Strophe.js and jQuery.
-
Zash
> Re: [Standards] OMEMO:2 Spec Sprint I read "OAuth2 Spec Sprint". :/
-
MattJ
Not yet
-
MattJ
Daniel, XEP-0333 in MUC: https://github.com/xsf/xeps/pull/927
-
MattJ
and whoever was in the conversation about 333 status code in MUC: https://github.com/xsf/xeps/pull/926
-
MattJ
(333 is purely a confusing coincidence)
-
Zash
It says status code 307?
-
MattJ
307 is what has been removed (from the examples)
-
Zash
Nice ellipsis Github, thanks
-
MattJ
The examples were suggesting that a server would send 307 + 333 together
-
MattJ
But it only makes sense to send one or the other
-
MattJ
Unless you want legacy clients to make it look like people keep getting kicked from the room
-
jonasβ
I wanted that :>
-
MattJ
I assumed it would be pep. ;)
-
pep.
Saying things on me while I'm away!!
-
pep.
I'll have to look into poezio code again, not sure how I did that
-
Daniel
MattJ: when parsing a marker do I have to check both - if the ID matches stanza-id and normal. Or do I switch over depending on the availability of the stanza id namesapce on the room
-
flow
depending in the stanza-id feature availability, i'd say
-
flow
as you can only trust <stanza-id/> it a 'by' value of the MUC's bare JID, if that JID announces the stanza-id feature, and hence announces that the MUC will prevent stanza-id spoofing
-
Daniel
Yes I agree
-
Daniel
The same goes for adding it imho
-
Daniel
Currently the text says if there is a stanza id
-
Daniel
I think that should be changed to read if the feature is announced
-
Daniel
Then you can follow the same rule for sending and receiving
-
MattJ
Sounds sensible
-
MattJ
> Therefore, if a MUC announces support for &xep0359; and a <stanza-id> element is present within a markable stanza with a 'by' attribute matching the MUC's bare JID, this is the id that MUST be used when returning chat marker updates.
-
MattJ
?
-
MattJ
Daniel, not sure if I understand your point about sending vs. receiving (do you mean sending == adding <markable>, receiving == responding with <received/>?)
-
Daniel
MattJ: no I mean the decision on whether or not to use the stanza id (over the message ID) is the same on all sides
-
MattJ
Hmm, right
-
Daniel
The one who sends out the displayed and the one who receives it
-
MattJ
Should usage within a MUC that doesn't advertise stanza-id be discouraged?
-
Daniel
Maybe
-
Daniel
I think reactions will do that
-
MattJ
Also what if a client adds <markable> to a message that the MUC doesn't archive?
-
Daniel
I'd be OK with it not working in those cases
-
MattJ
<p>Therefore, if a MUC announces support for &xep0359; then clients MUST always use the MUC-assigned id for Chat Markers. The id will be contained in a <stanza-id> element inserted into the stanza with a 'by' attribute matching the MUC's own JID.</p>
-
MattJ
<p>As per XEP-0359 security considerations, clients MUST only trust a <stanza-id> element with a 'by' attribute that matches the MUC's own JID, and MUST ignore any such element in MUCs that do not announce XEP-0359 support.</p>
-
Daniel
That sounds reasonable
-
MattJ
Updated the PR
-
flow
Daniel> I think that should be changed to read if the feature is announced that would be redundant to what the stanza-id xep already says
-
MattJ
Not really
-
flow
I am usually against XEPs repeating what other XEPs already say, but I see that there could be exceptions to that rule
-
flow
MattJ, how not really?
-
MattJ
Of the two paragraphs above, the first one applies to Markers only ("if the feature is present, the behaviour of your Markers implementation changes like this:")
-
MattJ
The second paragraph is duplicating what XEP-0359 says, but I chose to do that as it's calling out security stuff
-
MattJ
There is a high chance that someone implementing Markers would accidentally overlook that
-
flow
yep, hence I said that there could be exceptions to that rule
-
flow
but those really should be scarse
-
flow
MattJ, "MUST only trust" does not sound right, you could trust other <stanza-id/>'s too
-
MattJ
Alternative suggestions welcome, I changed that several times
-
flow
that is nitpicking, but I think that paragraph could become a blueprint for other <stanza-id/> using XEPs
-
flow
and we usually write empty elements, so instead of <stanza-id> XEPs typically use <stanza-id/>
-
flow
MattJ: As per XEP-0359 security considerations, clients MUST only trust a <stanza-id/> element with a 'by' attribute that matches the MUC's own JID, if the MUC's own JID announces XEP-0359 support.
-
MattJ
I had something like that, but didn't want it to sound like "If the MUC's JID announces support, you most only trust 'by' with the MUC's JID"
-
MattJ
i.e. if the MUC doesn't announce support, trust any
-
flow
hmm, maybe additionally specify that the stanza-id shouldn't be trusted if the support is not annouced?
-
flow
"If XEP-0359 support is not annoucned, then <stanza-id/> elements with a 'by' attribute that matches the MUC's own JID should be considered spoofed and be ignored✎ -
flow
"If XEP-0359 support is not annoucned, then <stanza-id/> elements with a 'by' attribute that matches the MUC's own JID should be considered spoofed and be ignored" ✏
-
flow
something like that
-
MattJ
Yep, that sounds better
-
MattJ
How's this?
-
MattJ
<p>As per XEP-0359 security considerations, if XEP-0359 support is not announced then <stanza-id/> elements with a 'by' attribute that matches the MUC's own JID should be considered spoofed and MUST be ignored.</p>
-
MattJ
s/matches/match/
-
flow
like it
-
flow
ahh, hmm, maybe specifiy where the xep359 support is announced?
-
flow
just to make it bullet proof
-
flow
"is not annoucned on the MUC room's bare JID"
-
flow
i'd probably s/MUC's own JID/MUC room's JID/, but that could just be me
-
MattJ
Pushed
-
sss
Hey all
-
sss
any one online here ?
-
tom
Anything other than Jitsi that can do videocalls?
-
Zash
There's a bunch actually. Telepathy based things, Pidgin(β½), Gajim, a few others. Atalk I heard.
-
Zash
I had a phone running Linux 10 making voice/video calls over XMPP 10 years ago.✎ -
Zash
I had a phone running Linux making voice/video calls over XMPP 10 years ago. ✏
-
Maranda
Gajim not on Windows right?
-
pep.
Movim also
-
pep.
Gajim I don't think so no. Audio might work though