search

ayn2op / discordo

A lightweight, secure, and feature-rich Discord terminal client.
MIT License
2.02k stars 63 forks source link

Will not start for the last 1-2 weeks #342

Open r3k2 opened 6 months ago

r3k2 commented 6 months ago

I like to come back sometimes to test and see if finally is stable, but now is worse than ever, I start it, add my credentials and crashes! Do not even have time to use it. Do you guys actually test this on GNU/Linux? I am using Arch and something broke in the last 2 weeks that I test it. I did remove ~/.cache/discordo and reinstalled no luck, also deleted the config.

ghost commented 6 months ago

Have you ever tried to see the log files, Arch user?

StandingPadAnimations commented 6 months ago

(Fellow Arch user here, might be able to help)

I did remove ~/.cache/discordo and reinstalled no luck, also deleted the config.

~/.cache/discordo contains the logs that discordo outputs. Can you post them here so we have something to work with?

r3k2 commented 6 months ago

@jumps-are-op smart ass you? don't you think I already had check that?

swappy-20240208-070112

oh and in case someone thinks since I saw the hostility of the first msg by @jumps-are-op that I deleted it and created an empty file. Here is the timestamp from when I posted the issue swappy-20240208-070425

I just wanted to know if this is happening just to me or to all Linux users, @StandingPadAnimations response makes me believe is working well for him, so must be something on my side, Ill run it after work with strace and see what I get.

ghost commented 6 months ago

@r3k2 You never said you checked the logs, I thought you didn't check it. No need for that kind of bad language here, Arch user.

apprehensions commented 6 months ago

There is no reason for @r3k2 to open an issue for a project that the maintainer is making completely out of his free time, being impolite and having higher standards that is provided purely out of patience.

You said discordo crashes, where is the crash information? If you get a completely empty output, run strace discordo and paste the contents here.

Please be polite when opening issues on open source projects.

gruelingpine185 commented 6 months ago

I also experienced this issue on mac. The log files are also empty. Since then I stopped using Discordo and ended up deleting it some time after. I'm glad someone posted an an issue about it, but I do agree that this is no place for that kind of response.

satheevrin commented 6 months ago

I can also confirm that this is broken on Arch. But for me, it's simply not opening. I have a log file:

2024/02/18 01:44:42 ws.go:16: Gateway error: websocket: close sent 2024/02/18 01:44:42 main.go:22: websocket closed, reason: 4004 Authentication failed.

Fix, explanation??

apprehensions commented 6 months ago

Probably duplicate of #339

satheevrin commented 6 months ago

So can I fix it somehow then to where discordo works? (Sorry if this is a dumb question, I don't quite understand the link you gave me.)

epetousis commented 5 months ago

@r3k2 so to summarise this issue: an extremely bad attitude from the get-go, no logs and when asked for them, one is called a "smart ass"? Might I suggest you try respecting other people before asking us to "respect hacker ethics" as per your bio?

Token authentication is not hard and really does not warrant this kind of disrespect for a completely free project. For anyone else stumbling upon this and simply wanting to log in:

  1. Browse to https://discord.com/app and sign in (if not already).
  2. Open the dev tools with F12 and click "Console".
  3. Paste (after taking the time to read and understand that it is exposing the getToken() method buried inside Discord's Webpack bundle) (webpackChunkdiscord_app.push([[''],{},e=>{m=[];for(let c in e.c)m.push(e.c[c])}]),m).find(m=>m?.exports?.default?.getToken!==void 0).exports.default.getToken(), then hit Enter.
  4. Copy the token output.
  5. Run discordo --token <the token in question>.
Riddim-GLiTCH commented 3 months ago

Experiencing the same on Windows 11 Enterprise version 23H2 (build 22631.3593) I have tried the above, and it asked me to log in with an email again. I thought maybe it couldn't log in because the token was not stored correctly in the key-ring and deleted the discordo entry as a troubleshooting step and tried logging in again. Still fails.

Not sure how to collect a stack trace on windows, however; /appdata/local/discordo/logs.txt has collected these two lines:

2024/05/21 11:34:58 ws.go:16: Gateway error: websocket: close sent
2024/05/21 11:34:58 main.go:28: websocket closed, reason: 4004 Authentication failed.

Unsure if this is because discord added support for physical 2-step authentication or not. I am NOT using a security key though.