> prime audience for the use of end to end encryption (drug addicts) [...]
Sad how scared of authorities he seems to be :(
Flowhas joined
Flowhas joined
jonasw
I think in russia it’s a bit healthy to be scared of authorities......
mathieui
in western countries too, tbh
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
jonasw
mathieui, I think there it’s healthy to have respect of authorities. Scared is another level.
mathieui
well, not "scared", but "expecting the worse of them at all times"
mimi89999has left
Guushas left
jubalhhas joined
Guushas joined
Alexhas left
edhelashas left
la|r|mahas joined
Guushas left
Guushas joined
Guushas left
Guushas joined
jubalhhas joined
Zashhas joined
edhelashas joined
uchas joined
edhelashas left
edhelashas joined
Guushas left
ralphmhas joined
mark.erdhas left
uchas joined
Guushas joined
mimi89999has left
Guushas left
Guushas joined
tim@boese-ban.dehas left
tim@boese-ban.dehas joined
Guushas left
Guushas joined
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
lumihas joined
ralphmhas left
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
tim@boese-ban.dehas joined
winfriedhas left
winfriedhas joined
winfriedhas left
vanitasvitaehas left
winfriedhas joined
winfriedhas left
winfriedhas joined
jubalhhas joined
ralphmhas left
jubalhhas left
jubalhhas joined
uchas joined
intosihas left
Zashhas left
Zashhas joined
vanitasvitaehas left
jubalhhas joined
zinidhas left
intosihas joined
zinidhas left
ralphmhas joined
Guushas left
Zashhas left
Zashhas left
Flow
Is there a way to retrieve all newer PubSub items after the item with ID X?
jonasw
Flow, with RSM possibly
jonasw
Result Set Management, it’s a XEP
jonasw
apparently some pubsub services support that
Flow
I don't found anything in xep59, xep60 and xep313
jonasw
wouldn’t you give the item ID as minimum and then query everything after that?
Flow
RSM appears to be more about "paging through the resulting set"
Flow
not about that particular query
Flow
it is not necessarly clear that the RSM IDs are the same as PubSub item IDs.
jonasw
yeah
jonasw
I’ve seen them differing, too
MattJ
I think that's what https://xmpp.org/extensions/xep-0313.html#sect-idm139955456388768 was for
intosi
MAM ids != PubSub item IDs. If only because those are not guaranteed to be unique.
Flow
too many IDs ;/
Ge0rG
Flow: that's what I said, recently.
Holger
Flow: https://xmpp.org/extensions/xep-0312.html
Ge0rG
Flow: but you didn't like it :(
Flow
Ge0rG: out of context
Holger
Flow: Not sure (where) that's implemented, though.
intosi
On any given service, only (node id, item id) needs to uniquely point to an item. But you can republish an item with the same ID, which would defeat the purpose of the id in MAM.
Ge0rG
Flow: "too many IDs" is true irregardless of context.
Holger
Flow: Ah nonsense, that only works with a timestamp.
Flow
So there is no way to catch up on pubsub items while offline, presuambly because the assumption is that you will get the notifications about new items also while offline?
valohas joined
Holger
Hmm well 0312 does somewhat try to provide that, no?
Flow
I really start to dislike xep0060. Not only is there no way to reliable get the publisher's JID, you also can't do the simplest queries…
valohas joined
Kev
That's why someone at the Summit was suggesting using 313 for 60 queries.
Holger
goffi's PubSub component does MAM, I think.
vanitasvitae
jonasw, If I want to make changes to JET, shall I make these changes in xep-0391, or inbox/jet?
Ge0rG
vanitasvitae: inbox/jet should cease to be a thing as soon as it's got a number
vanitasvitae
okay :)
jonasw
Ge0rG, no, it still exists for historical purposes
jonasw
vanitasvitae, updates against xep-0391.xml
Ge0rG
maybe we could get rid of that, we've got git history after all.
jonasw
Ge0rG, I think the purpose is to have it on the webserver too
vanitasvitae
jonasw, I noticed, that the XEP mentions a dependency on 234 (jingle file transfer). Is this necessary? JET should work for other Jingle usecases too, even when a client does not implement 234.
vanitasvitae
Looks like I added that dependency, when the document was still titled "Jingle Encrypted Transfers"
alacerhas joined
jonasw
vanitasvitae, I didn’t add that depedency :)
jonasw
feel free to modify that
vanitasvitae
okay
jonasw
in Experimental, you can as author basically everything✎
jonasw
in Experimental, you can do basically everything as author ✏
jonasw
you just need to preserve compatibility
vanitasvitae
okay. I should also add revisions, right?
jonasw
vanitasvitae, you SHOULD, yes. An editor will do that if you don’t.
jonasw
when you do it, you have the chance to make the revision text as meaningful as possible :)
vanitasvitae
:D I'll do you the favor :)
jonasw
if you would follow the spirit of semantic versioning when choosing the next version number, that’d be great
Zashhas left
vanitasvitaehas left
pep.has left
lovetoxhas joined
alacerhas joined
intosihas left
intosihas joined
alacerhas joined
Valerianhas joined
Kevhas left
vanitasvitaehas left
valohas left
edhelashas left
waqashas joined
Kevhas left
uchas joined
Kevhas joined
mimi89999has left
mimi89999has left
uchas left
Kevhas left
lskdjfhas left
lskdjfhas joined
Kevhas joined
mimi89999has joined
uchas joined
vanitasvitaehas left
waqashas left
waqashas joined
Flow
So MAM with PubSub only improvement are the query conditions 'start', 'end' and 'with'. But we could specify a PubSub specific (after|before)-pubsub-item-id?
Zash
Does mam+pubsub mean mam-rsm ids are pubsub ids or?
Flow
Zash: intosi says no
Zash
Altho with pubsub ids being user-controlled ... and sometimes always "current", glhf
Flow
For the same reason I had to invent a new "value" for the "Atomically Compare-And-Publish PubSub Items" XEP
Tobiashas left
Flow
(Of course the reasoning is not false, I just think that it is a design flaw that IDs may point to different content, instead of having an <item-retracted/> marker)
Flow
Zash "always "current""?
jonasw
Flow, maybe you could first specify your new ID for re-use by different things and then build CAP on top of that?
tuxhas left
Flow
jonasw: I'm not sure if it's of any use
Zash
Flow: In a bunch of PEP things, the item ID is always the string "current"
Flow
besides of the compare-and-publish case
Zash
this https://xmpp.org/extensions/xep-0060.html#impl-singleton
intosi
Zash: indeed. And just the fact that the Item ID is something the publisher can provide, instead of letting the server guarantee its uniqueness across the service, is enough to invalidate it for MAM id.
Zash
Yeah
Zash
Like with message@id
Zash
Hm, does that mean thaw MAM+PubSub is doomed?
Flow
Zash: You can still use 'start', 'end' and 'with'
jerehas joined
jerehas joined
Zash
Yes
Flow
And specify further fields for MAM+PubSub like after-pubsub-item-id
Zash
Does the pubsub service have final say over the item id?
ralphmhas left
intosi
MAM with Pubsub has semantics that differ from Pubsub retrieval anyway, as you're likely to get the same itemid more than once in some use cases.
MattJ
I was never convinced about MAM+pubsub
Zash
MattJ: Weren't you the one who said "Just use MAM?" back then?
MattJ
niirc :)
Zash
I REMEMBER EVERYTHING .. almost
intosi
I use MAM instead of remembering everything.
Ge0rG
I use a server-side client with logging.
MattJ
^
Ge0rG
MAM is too bumpy.
Zash
Or you can just forget everything the instant it scrolls off the screen. If it was important then they shouldn't have written it over an ephemeral instant messaging thing! :)
Flowhas left
Flowhas joined
uchas joined
mimi89999has left
mimi89999has left
uchas left
mimi89999has joined
uchas joined
Valerianhas left
Valerianhas joined
edhelashas joined
tim@boese-ban.dehas joined
uchas joined
Flowhas joined
Valerianhas left
uchas left
alacerhas joined
alacerhas joined
danielhas left
Kevhas left
xnyhpshas left
danielhas joined
nycohas left
xnyhpshas left
Wiktorhas joined
uchas joined
mathieuihas left
danielhas left
mathieuihas joined
mathieuihas left
mathieuihas joined
Guushas left
ralphmhas left
Guushas left
ralphmhas left
valohas joined
alacerhas joined
Guushas left
winfriedhas joined
mathieuihas left
mathieuihas joined
edhelashas left
edhelashas left
edhelashas left
Valerianhas joined
ralphmhas left
sonnyhas joined
uchas left
alacerhas joined
Guushas left
Guushas left
valohas left
winfriedhas joined
Steve Killehas left
valohas joined
tim@boese-ban.dehas joined
pep.has left
Steve Killehas joined
jonaswhas left
jjrhhas left
jjrhhas left
Guushas left
ralphmhas left
jjrhhas left
sonnyhas joined
sonnyhas left
sonnyhas joined
Neustradamushas left
Neustradamushas joined
stefandxmhas left
efrithas joined
stefandxmhas joined
jjrhhas left
waqashas left
tim@boese-ban.dehas joined
vanitasvitaehas left
ralphmhas left
stefandxmhas left
Valerianhas left
sonnyhas joined
tim@boese-ban.dehas joined
alacerhas joined
pep.has left
jubalhhas joined
Valerianhas joined
sonnyhas joined
alacerhas left
alacerhas joined
Tobiashas joined
stefandxmhas joined
alacerhas joined
ralphmhas joined
Neustradamushas left
Neustradamushas joined
alacerhas joined
la|r|mahas joined
la|r|mahas joined
uchas joined
ralphmhas left
waqashas joined
sonnyhas joined
jerehas left
jerehas joined
lskdjfhas joined
Valerianhas left
Valerianhas joined
goffihas left
Ge0rGhas left
Ge0rGhas left
mimi89999has left
xnyhpshas left
Valerianhas left
sonnyhas joined
jubalhhas joined
xnyhpshas left
Nathanhas joined
Nathanhas left
Nathanhas joined
Nathanhas left
danielhas joined
Alexhas left
waqashas left
waqashas joined
tim@boese-ban.dehas left
jubalhhas left
Valerianhas joined
danielhas left
jubalhhas left
jubalhhas joined
alacerhas joined
ralphmhas left
alacerhas joined
lovetoxhas left
sonnyhas joined
Nathanhas joined
Nathanhas left
Nathanhas joined
zinidhas left
edhelashas left
edhelashas joined
Nathan
...
jubalhhas left
zinidhas left
edhelas
we can change the 0060
Nathanhas left
edhelas
it's not like we have many Pubsub + MAM implementation in the wild :p