137 Members
A fancy, customizable, keyboard-operable Matrix client ⬩ Latest release: 0.7.1 ⬩ https://github.com/mirukana/mirage/releases/51 Servers

Load older messages

14 Apr 2021
@maze:sorunome.deMazesame computer20:02:09
@sorunome:sorunome.deSorunomeokay, that would explain that, then. nico also mentioned stuff like that happening if two different clients try to set different presences20:02:26

yeah. I'll be careful from now on, I'll only use one at once

@maze:sorunome.deMazeThanks soru!20:07:24

Maze Sorunome: it even happens with only one client sometimes, honestly I have no idea how to fix it

@miruka:matrix.orgmirukawhen Mirage receives a presence update for your account, it updates itself to follow that, but it still manages to glitch out sometimes somehow23:44:06
15 Apr 2021
@sorunome:sorunome.deSorunome @miruka:matrix.org do you set presence on the /syncrequest? 04:55:26
@sorunome:sorunome.deSorunomelike, via the query parameter05:06:04
@sorunome:sorunome.deSorunomedo you have a cooldown for how often to pick up its own presence? maybe a synapse lag can cause it to keep switching05:07:43

I haven't tried that, but what happens exactly if you sync without setting it? Wouldn't it always put you back to online? Especially if you're trying to stay invisible

@sorunome:sorunome.deSorunomesoru thinks it defaults to online, yes05:10:54

or I guess you mean: always /sync with what the user set in mirage for at least x seconds, then we can accept a change

@sorunome:sorunome.deSorunomeand when picking up a change, also stick to that change for at least x seconds before changing again05:21:41

if we pick up a change from a presence event, doesn't that mean the server is up to date? It wouldn't just fallback to a previous state

In reply to @sorunome:sorunome.de
and when picking up a change, also stick to that change for at least x seconds before changing again

This sounds like it would only slow down the problem but not prevent it?


Maze Sorunome: I've done some work in the latest dev commit 2b3f86, if you can try it, please report if the issue keeps happening


this doesn't use the cooldown solution, but rather this:

  • when we set a new presence, it is "locally echoed", i.e. shown to the client has an intermediate state before receiving an actual presence event from the server
  • when we receive a presence event from the server for our account, if we're in a local echo state, but that event doesn't correspond to what we're trying to set (e.g. we're in echo_online but server says unavailable instead of online), ignore that event
  • if it does correspond to what we're trying to set, then switch our state to the non-echo version

I tried with old and new dev version, but I'm not able to reproduce the issue.

@thecatcore:matrix.orgCat Core joined the room.21:07:08
16 Apr 2021
@ameliafloof:matrix.orgAmelia the Floof joined the room.01:17:46
@ameliafloof:matrix.orgAmelia the Floof

Maze that is the heccin most adorable pfp i have seen :0

@maze:sorunome.deMazeyou need to see me for christmas02:29:03
@ameliafloof:matrix.orgAmelia the FloofSend itttt02:29:15
@maze:sorunome.deMazeRedacted or Malformed Event02:30:30
@ameliafloof:matrix.orgAmelia the Floof



Amelia the Floof meow, let's dm, I don't think this room is the right place

@ameliafloof:matrix.orgAmelia the Floofowo02:40:03
17 Apr 2021
@arter:privacytools.io@arter:privacytools.io left the room.13:42:58

There are no newer messages yet.

Back to Room List