Artem Savkov
Artem Savkov
Makes sense, c4f3426 does that.
Hey there, @lethal-click. The support status is "maintenance only" but I'd be glad to merge this if you can create a pull-request with your changes and we can ask someone...
Yes, there is no support for permissions whatsoever in bitlbee-discord. Issue #34 discusses a possible solution for the problem with joining unwanted channels. Implementing permission support is something I've been...
Are you sure unicode has anything to do with it and it's not the same issue as https://github.com/sm00th/bitlbee-discord/issues/47? Can you try bitlbee's develop branch that has a fix for #47...
> From that API call (sent once per server on connect) the plugin could build a hash/map of emoji names to IDs on each joined Discord server for outbound translation....
> I did just think of a UX consideration though. If the user tries to send an emoji that they don't have access to (assuming it's not in the plugin's...
Try using bitlbee's `save` command right after you configured all the auto_join channels. This should forcefully dump the config onto disk.
If you can get the debug logs (see "Debugging" section in README) that should give an idea on what is going on. How reproducible is this?
I merged a pull-request that **might** (so not closing the issue yet) be solving this issue. Please update your bitlbee-discord (don't forget to restart bitlbee) and see if the situation...
> All I have to do is ac dc off, wait, then ac dc on, and everything connects and joins up just fine. If you are using autojoin - have...