gtkcord3

README

gtkcord

A lightweight Discord client which uses GTK3 for the user interface.

This is a modified derivative of gtkcord3, please don't contact the original author about issues with this project.

Gtkcord3 Node JS rewrite

There is a new project I have started which is a full rewrite of this app in typescript with node-gtk gtkcord3-js. If that interests you please feel free to contribute to the gktcord3-js conversion project.

It's time to ditch the Discord Electron application (soon).

• Lighter than the official Discord application
• Faster than the official Discord application
• Uses less system resources than the official Discord application
• Is just as easy to use as the official Discord application
• Uses your preferred GTK theme

Build gtkcord

Required: go (1.13+ & <1.16), gtk, libhandy0, pkgconfig (refer to shell.nix)

go get github.com/TheBlueOompaLoompa/gtkcord3 # auto updates
~/go/bin/gtkcord3 # $GOPATH/bin/gtkcord3 or $GOBIN/gtkcord3

Logging in

Using DiscordLogin (recommended)

1. Click the DiscordLogin button.
2. Install DiscordLogin if you have to.
3. Login normally.

Manually

1. Press F12 in when Discord is open (to open the Inspector).
2. Go to the Network tab then press F5 to refresh the page.
3. Search api library then look for the "Authorization" header in the right column.
4. Copy this token into the Token field, then click Login.

(Missing) features

• See the messages of the selected channel
  • Message reactions
• Send messages
  • Emojis
    • Show normal emojis
    • Show custom emojis
  • Message reactions
    • Show a menu when clicked
    • Add reaction from clipboard
• Graphical login
  • Graphical logout
• Hamburger menu
  • Change the visibility of your online state
    • Custom Rich Presence
    • Rich Presence IPC server
  • About dialog

Low priority

• Options menu with the same options which Discord has
• Voice chat support

Known Bugs/Limitations

• Random crashes (very rare)
  • Might crash on channel switch because glib.PixbufLoader sucks
• Rapid recursive ack bug
  • High priority, might count as API abuse