SQLite3 or Postgres?: Whatever runs dendrite.matrix.org
Running in Docker?: Whatever runs dendrite.matrix.org
go version: Whatever runs dendrite.matrix.org
Description
After logging in with Nheko on dendrite.matrix.org, I get the following update in every second sync, causing my client to mark those users keys as out of date:
This also includes my own user, @deepbluev7:dendrite.matrix.org, who only has this one device.
I also get 2 times the same sync token, only differing in the last number: s69732_6464.dl-0-9131 and s69737_6464.dl-0-0.
The last number seems to be the same in every second sync. It looks like Nheko is running 2 parallel /sync streams here for some reason, but the sync tokens actually flip flop the last number after each sync, which then causes dendrite to send device_lists for one of those /sync's?
Steps to reproduce
register to dendrite.matrix.org
login with Nheko
join a room
watch your device list
Expected behaviour
Device lists should not change, if they don't actually change.
Background information
go version
: Whatever runs dendrite.matrix.orgDescription
After logging in with Nheko on dendrite.matrix.org, I get the following update in every second sync, causing my client to mark those users keys as out of date:
This also includes my own user, @deepbluev7:dendrite.matrix.org, who only has this one device.
I also get 2 times the same sync token, only differing in the last number: s69732_6464.dl-0-9131 and s69737_6464.dl-0-0.
The last number seems to be the same in every second sync. It looks like Nheko is running 2 parallel /sync streams here for some reason, but the sync tokens actually flip flop the last number after each sync, which then causes dendrite to send device_lists for one of those /sync's?
Steps to reproduce
Expected behaviour
Device lists should not change, if they don't actually change.