Robin
Robin
It looks like this bug is caused as the result of Discord's search API including messages that were sent as replies to a user's slash commands. The issue is fixed...
@JayBoom line 314 seems to be the correct place? I'm not the author- you definitely could know better than me but github displays it as line 314 for me. Somewhere...
@JayBoom the fix you describe is certainly possible. Discord's search API returns, along with the list of messages, threads that are referenced by them. I wrote a quick implementation of...
You need to install the dependency. Using `npm i` should work, or using `npm i colors --save`.
I'm pretty sure Discord uses WebRTC for voice calls, which is uses udp packets and may not ever work with plain http/https/websockets.
@sealsrock12 Have you considered using the 1.1.1.3 dns resolver? As far as I know it should block anything malicious, right?
Inside the `http` directive, just below where the `server` directive starts, in `nginx.conf` there is a line `listen 80;`. This tells nginx which port to listen on. However, in `docker-entrypoint.sh`,...