Artem Savkov

I have a rough sketch of how it might fit: https://gist.github.com/sm00th/eb65efcc10059782bf8db9fac1a84c34 It doesn't generate proper code though as src part of the call instruction needs to be set to BPF_PSEUDO_KFUNC_CALL...

I think something like this can be better handled on irc-client/bouncer level

It does not, I assumed that by "channel which has no unread messages" you meant that you join a channel you already received unread messages for, that means your bouncer...

> That is the weirdest thing ever. Would still warrant an update to the README, IMHO... Barely touching this project, but feel free to open a PR, I'd gladly merge...

Might be cloudfare being suspicious of your bitlbee host's ip address. Could you try tunneling through that machine (`ssh -D`) and trying to log into discord with it's ip via...

I see. To be honest I've been neglecting this project for a while and I currently don't even have anything set up to properly test this issue and I am...

You can try running bitlbee in [debug mode](https://github.com/sm00th/bitlbee-discord#debugging) and see if the messages are comming. If they don't there also might be clues in the logs during chanel join/sync.

I guess that is caused by discords recent 'unique username' vs 'shown username' update. So we now either need to save the latter as our uname [here](https://github.com/sm00th/bitlbee-discord/blob/master/src/discord-handlers.c#L901), or check both...

just checked and I do receive messages, you can try running in debug mode (https://github.com/sm00th/bitlbee-discord#debugging) and see if you do receive them but they are not shown for some reason...

ok, so if you see them in debug output the problem is probably the way you join them, please make sure they are properly added the way described in readme's...