jdev - 2020-09-26

Hey I think you people are ll

Looking for me

No

Yeah man

66,000 tokens to Victoria a couple yrs ago

I'm the anonymous tipper

Whats up you

The first time I was on the site I used emojis to send a code

Y'all going to talk to me or what

⚓

And a bunch of blocks that had letters on them

Kev, MattJ, ralphm: spammy guy ^

Look how else would I know what all that geek talk up the log means

Yo talk to me and tell me what you need from me or ima double up on the server and encryption

Do y'all know what the X is for?

Let me spell this out for you its just like Christmas only its Xmas its shorter to write down

Wtf y'all scared to talk . dont be I'm cool as fuck

It dont make a fuck you cant kill.me I'm bullet proof and surrounded by angels

we *really* need that message moderation feature

Whats up if y'all cant talk to me then dont talk aboit me it is fucking rude

Hello

Someone get the cobra

She isnt scared to talk

Bye

lovetox: yeah

also a bulk moderate feature

he moved to xsf@

(cc ralphm)

Yo what's reallly going on in he

In here

MattJ what is up with this tracking my every move.

ralphm,

Eta what can you tell me about this code

It's x: simple, if you continue bothering people with off topic messages in these channels, you're banned.

Kev is there any way I can get my other 2 accounts unlocked ?

Why would we do that?

I have tokens on one and I would like to use them

This site seems to have an interest in me that I didnt know about

Its understandable

Just ban it. It'll spam it's gibberish again.

This is all coming in through our website

when implementing XEP-0313, do the <first> and <last> elements returned as part of the RSM <set> in the <fin> element need to be the archive IDs, or can they be arbitrary?

Pretty sure they need to be archive IDs when used in XEP-0313

bollocks!

How so?

because archive IDs aren't sortable

Correct

so I'll need to do an extra step to translate the archive ID to the integer primary key of the database table storing all the history

and then do a "where id >"...

Tell me about it :)

was hoping I could get away with hackily just shoving the primary key in there >_>

This is what Prosodys SQL backend does

eta: Are you implementing a server?

surely that means the before-id and after-id things are redundant?

Zash, nah, this is for whatsxmpp

eta: Are youe implementing a XEP-0313 as a server or a client?

as a server

So it's up to you what format archive ids has

You could make it the numeric primary key if you wanted

well not really, given this transport also has to work without persistent history

so I've been handing out archive IDs in another format since the thing started existing

but anyway, surely if you can specify any arbitrary archive IDs via RSM, the before-id and after-id parts of XEP-0313 are redundant?

Not exactly

Those define the messages matched by the query

The RSM stuff does paging within that set

I'm struggling to think of an implementation usecase where the difference between those 2 is significant

MAM → SQL WHERE RSM → SQL LIMIT / OFFSET

especially given the spec mandates you can't have any conception of an "open query"

hrm, I guess

oh wait, can you not specify both <after> and <before> in RSM?

Nope.

ah! okay, that works then

thanks Zash :)

:)

eta, this is an important detail when learning about RSM

RSM is not meant to be a filter

you filter a database with other means (after-id, start, end, before-id)

and then page through that filter result with RSM

lovetox, yeah, got it :)