roberty0979, checking back in before i do some new years activity; however, rust is probably the least 'functional' of the bunch. xmpp (and most other things really) is very pleasant to implement with pattern matching and functional languages tend to be extremely easy to reason about. i used to write a lot of java and currently write a lot of ruby at work but would very seriously like it if the rest of the engineering staff weren't so enamored with go as the 'next step' in scaling. i've become rather sick of having to spend time figuring out just what the hell people were trying to accomplish with some of the wild stuff you see in 'OOP' or procedural/imperative languages. functional programming doesn't stop people from doing it, but it's like giving children the "big legos" so that they can't swallow them or stab each other.
qy
:)
adxhas left
jubalhhas left
spiralhas left
Vaulorhas left
Vaulorhas joined
spiralhas joined
adxhas joined
SouLhas left
spiralhas left
spiralhas joined
Vaulorhas left
Mx2has left
spiralhas left
spiralhas joined
pasdesushihas left
pasdesushihas joined
thomaslewishas joined
thomaslewishas left
pasdesushihas left
adxhas left
spiralhas left
thomaslewishas joined
thomaslewishas left
spiralhas joined
spiralhas left
spiralhas joined
Millesimushas left
wurstsalathas left
Trunghas joined
Millesimushas joined
selurveduhas left
Millesimushas left
Mx2has joined
TheCoffeMakerhas joined
TheCoffeMakerhas left
Millesimushas joined
TheCoffeMakerhas joined
Millesimushas left
TheCoffeMakerhas left
TheCoffeMakerhas joined
qy
what is it that means read state doesnt sync between conv, dino, and gajim? it's chat markers that would do it right, and they all implement that?
qy
or is it that it does, but only at reconnect
Vaulorhas joined
Trunghas left
Trunghas joined
Millesimushas joined
Millesimushas left
paulhas joined
tskhas joined
thomaslewishas joined
Millesimushas joined
thomaslewishas left
thomaslewishas joined
Millesimushas left
Schimon_has joined
qwestionhas joined
qwestionhas left
Millesimushas joined
thomaslewishas left
thomaslewishas joined
Millesimushas left
spiralhas left
Trunghas left
Trunghas joined
spiralhas joined
qwestionhas joined
Millesimushas joined
qwestionhas left
tskhas left
Millesimushas left
Millesimushas joined
spiralhas left
thomaslewishas left
thomaslewishas joined
qwestionhas joined
thomaslewishas left
Millesimushas left
thomaslewishas joined
Millesimushas joined
Trunghas left
Trunghas joined
spiralhas joined
qwestionhas left
miruxhas joined
qwestionhas joined
thomaslewishas left
jubalhhas joined
TheCoffeMakerhas left
qwestionhas left
qwestionhas joined
thomaslewishas joined
MSavoritias (fae,ve)has joined
Vaulorhas left
thomaslewishas left
thomaslewishas joined
Yagizаhas joined
Yagizаhas left
Yagizаhas joined
pep.
qy: there's no protocol for this. Clients generally use a mix of chat markets, chatstates and maybe read receipts to work around this but that's not what they're for
stefanhas left
qwestionhas left
qwestionhas joined
Vaulorhas joined
jubalhhas left
qy
wow a feature that doesn't have an XEP
qy
that's a first
qy
but i feel like chat markers are right to use for this
goffihas joined
menelhas joined
qwestionhas left
SouLhas joined
atomicwatchhas joined
qwestionhas joined
TheCoffeMakerhas joined
goffihas left
moparisthebesthas left
Laurahas joined
moparisthebesthas joined
qwestionhas left
atomicwatchhas left
TheCoffeMakerhas left
qwestionhas joined
atomicwatchhas joined
atomicwatchhas left
qwestionhas left
Alexhas joined
Ingolfhas left
Ingolfhas joined
Vaulorhas left
qwestionhas joined
sponjihas joined
sponjihas left
sponjihas joined
qwestionhas left
SouLhas left
Mario Sabatinohas joined
Vaulorhas joined
atomicwatchhas joined
john-machinehas left
Millesimushas left
john-machinehas joined
pep.
chat markers yeah, not markets :D (autocorrection..)
SouLhas joined
pep.
qy, chat markers are destined to all recipients (your other devices included). I'd rather have something that is explicitely for your clients only.
pep.
Typically chat markers is a feature I disable for privacy reasons. I do want read state sync though
pep.
(Yes I could also hack around it with mod_firewall but not everybody has their own prosody and is knowledgeable enough to do this.)
Millesimushas joined
jubalhhas joined
thomaslewishas left
Vaulorhas left
goffihas joined
goffihas left
goffihas joined
Vaulorhas joined
john-machinehas left
Trunghas left
goffihas left
Trunghas joined
Laurahas left
stefanhas joined
john-machinehas joined
Laurahas joined
Vaulorhas left
Laurahas left
Vaulorhas joined
Marandahas left
Mjolnir Archonhas left
TheCoffeMakerhas joined
wurstsalathas joined
TheCoffeMakerhas left
jubalhhas left
TheCoffeMakerhas joined
TheCoffeMakerhas left
qy
pep.; well ok, chat markers is still experimental, perhaps we can amend it and allow for configurable visibility?
qy
if done at server level, wouldn't require mass updating of clients
qy
just ejd and prosody (who even uses the rest :p)
pep.
I guess so
qy
Zash; Holger; thoughts?
menel
I think it would be important, that they don't spam the server and clients, because it would slow down bigger groups very much. I wonder if that change is to big a change..
A cleaner way would be to store it in a client controlled pep node? And other clients can look it up there?✎
menel
I think it would be important, that they don't spam the server and clients, because it would slow down bigger groups very much. I wonder if that change is to big a change..
A cleaner way would be to store it in an account ~client~ controlled pep node? And other clients of the same account can look it up there? ✏
qy
and subscribe to it
qy
sounds reasonable
stefanhas left
menel
Talking about slow transition to mix...
stefanhas joined
pep.
That's independent of mix anyway. As it should be usable in 1:1 too