Vesktop: Difference between revisions

From Discord Client Modding Wiki
Jump to navigation Jump to search
m (Grammarly)
(Update latest release and limitations)
Line 9: Line 9:


| label2  = Latest release
| label2  = Latest release
|  data2  = 1.5.1
|  data2  = 1.5.3


| label3  = License
| label3  = License
Line 36: Line 36:


However, Vesktop does have some limitations that come with the base of this app: Discord Web.
However, Vesktop does have some limitations that come with the base of this app: Discord Web.
* No VC volumes over 100
* No VC volumes over 100 (soon to be fixed in Vencord<ref>https://github.com/Vendicated/Vencord/pull/2730</ref>)
* No game detection (games sending their presence still work, but process scanning doesn't)
* No game detection using the Flatpak (games sending their presence still work with a workaround<ref>https://github.com/flathub/dev.vencord.Vesktop?tab=readme-ov-file#discord-rich-presence</ref>, but process scanning doesn't)
* Ask to Join on some activities (arRPC limitation)
* Ask to Join on some activities (arRPC limitation)

Revision as of 09:11, 9 August 2024

Vesktop
Screenshot of the Vesktop settings page
Development statusActive
Latest release1.5.3
LicenseGNU General Public License v3.0
RepositoryVencord/Vesktop

Vesktop is an alternative Discord client that loads Vencord on top of the Discord browser client.

Features

Vesktop has:

  • Full support for audio screensharing on Wayland
  • Snappier than the official Discord app
  • Comes with Vencord pre-installed (gone are the days of constantly repatching!)

Backstory

Vendicated initially made this app as Vencord Desktop with no intention of supporting it further. After they noticed that people actually used it, they decided to take the project seriously and rebrand it to Vesktop.

Limitations

However, Vesktop does have some limitations that come with the base of this app: Discord Web.

  • No VC volumes over 100 (soon to be fixed in Vencord[1])
  • No game detection using the Flatpak (games sending their presence still work with a workaround[2], but process scanning doesn't)
  • Ask to Join on some activities (arRPC limitation)