EdJoPaTo

The idea behind sessions is to keep some state for the current user without needing to care about its userID, chatID or stuff like that. So the sessions are designed...

I removed my `#![allow(clippy::useless_transmute)]` and it does no longer seem to be an issue.

Not sure if this is only related to the `SessionStore` or if that is more general. telegraf-session-local for example does not even use that. https://github.com/RealSpeaker/telegraf-session-local/blob/f91470d8aab9e80a5518b0dba1490456fa8b454b/lib/session.js#L164-L167

> as I understood (_and I might have understood wrong_), the problem is in parallel handling messages that were sent to bot while bot was OFF, right? This should affect...

Can this ever be a problem for different users? If one user / chat is spamming like hell and change the session all the time I personally wouldn't care if...

Personally I tend to move away from session for persistent data. If I have a bunch of lets say movies they are managed in their own way and ctx.session is...

I copied the not working stuff out of my project and simplified it for this bug report. Today I tested the code provided here and everything worked fine. After stripping...

[@typescript-eslint/no-confusing-void-expression](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-confusing-void-expression.md)

my mqttui tool was added in 90d8cb65261247d87fe5f096c32635c1b2049d9c so only my tree widget is added in this Pull Request.

I assume sindresorhus/got@6ae3b345e8108decba768c181ed7792f2da74f6a answers the linter question: use xo with eslint-config-xo-typescript. Also the question about xo supporting TypeScript by default is answered [here](https://github.com/xojs/xo/issues/373) (WIP).