Vesktop: Difference between revisions
Volume Booster works on web based clients including Vesktop now
Vendicated (talk | contribs) m (remove "less memory usage" feature. vesktop makes no attempt to use less memory. doing so isnt possible without rewriting their web app from scratch) |
(Volume Booster works on web based clients including Vesktop now) |
||
(4 intermediate revisions by 4 users not shown) | |||
Line 9: | Line 9: | ||
| label2 = Latest release | | label2 = Latest release | ||
| data2 = 1.5. | | data2 = 1.5.3 | ||
| label3 = License | | label3 = License | ||
Line 31: | Line 31: | ||
== Backstory == | == 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 == | == Limitations == | ||
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 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) | |||
* No game detection (games sending their presence still work, process scanning doesn't | |||
* Ask to Join on some activities (arRPC limitation) | * Ask to Join on some activities (arRPC limitation) |