Kevin Cox

Hmm, a manhole check for `bridge.az.ready` returns `True` though, implying that we are reaching https://github.com/mautrix/python/blob/v0.10.6/mautrix/bridge/bridge.py#L170.

Hmm, it just appears that logging for `bridge.matrix.e2ee` just isn't working because even manually making a critical log from a manhole isn't appearing.

I managed to work around this by clearing the `crypto_account` table and restarting mautrix-facebook. This lead to it generating and registering a new session. It didn't clear the old sessions...

I just saw this too: 

Restarting the bot appears to have fixed it.

This would be awesome, assuming that your hdfs user is the same as your local user is a pretty strong assumption.

Seems to come from here based on the `` text: https://github.com/repology/repology-webapp/blob/2672c9acc1861dff12743ffc8f4305dd306a367b/repologyapp/templates/repository-feed-atom.xml#L48-L53

Thanks, the `` should definitely stay. Although I think the hardcoded value is actually a lie. However IDK if it is worth doing more work to make it correct.

Well in my case there were events which got dropped off. So if the time that those events were removed was recorded it would be correct. But I don't think...

I think the current situation is fine. The problem for me was that when I subscribed there were events. Eventually the events expired (which was fine) but then this "new"...