Package Details: betterdiscord-installer 1.3.0-1

Git Clone URL: https://aur.archlinux.org/betterdiscord-installer.git (read-only, click to copy)
Package Base: betterdiscord-installer
Description: Installer for BetterDiscord
Upstream URL: https://github.com/BetterDiscord/Installer
Keywords: betterdiscord discord
Licenses: MIT
Replaces: betterdiscord
Submitter: ObserverOfTime
Maintainer: elektrikfisch
Last Packager: ObserverOfTime
Votes: 51
Popularity: 1.53
First Submitted: 2021-04-08 09:45 (UTC)
Last Updated: 2023-06-02 11:21 (UTC)

Pinned Comments

ObserverOfTime commented on 2021-04-01 07:57 (UTC) (edited on 2021-04-26 09:51 (UTC) by ObserverOfTime)

I've adopted and rewritten this package for the new BD installer.

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Moire commented on 2020-08-12 18:34 (UTC)

Hello, I am the maintainer of the discord-development package, and I just wanted to let everyone here know that betterdiscord does not currently work with discord development, so if you want to use betterdiscord you'll have to use a different channel.

(Also, I do not condone breaking of the TOS, I am simply posting this here so I don't get complaints from people whose install failed because they are using discord development.)

neneal commented on 2019-03-09 05:13 (UTC)

BetterDiscord is essentially deprecated. I recommend you move on to the enhanceddiscord-git package on the AUR. Same features as BD, and more, really

bb010g commented on 2018-01-10 11:03 (UTC)

https://aur.archlinux.org/packages/betterdiscord-rauenzi-git/ works on the new stable release thanks to Zerebos's excellent BandagedBD fork.

FichteFoll commented on 2017-11-07 12:52 (UTC) (edited on 2017-11-07 12:53 (UTC) by FichteFoll)

Does this still work for anyone? According to samogot, the commit 9ab77a82 broke Linux support and has still not been reverted[1]. Since about a week (probably when I updated the package), "betterdiscord" does nothing for me, while "betterdiscord-git" prevents discord from starting at all. I normally use canary, but this happens across all versions. [1]: https://github.com/Jiiks/BetterDiscordApp/issues/585

Stitchless commented on 2017-10-18 14:27 (UTC) (edited on 2017-10-18 14:27 (UTC) by Stitchless)

No, worries. It's a really messy repo. Jiiks is a bit... er... yea. Apparently (so I have been told) v2 is already dead, dp3 is the next one. Go figure.

MakaryGo commented on 2017-10-18 14:19 (UTC)

@HanFox my bad, didn't notice.

Stitchless commented on 2017-10-18 14:17 (UTC)

@MakaryGo, but that v2 branch also states it's not ready for production and you should use the old branch for now.

Lahvuun commented on 2017-10-18 09:06 (UTC)

Alright, let's just get this out of the way: BetterDiscord is garbage. At least, it is managed in a way that makes me think so. There's no sane versioning whatsoever, and package files that are in the very same commit expect different versions of stuff, thus sometimes things break and Jiiks fixes that with simply commiting and not releasing a new version. The revision number means there was a staggering amount of _450_ commits between 0.2.82 and latest master commit, which just calls for a version bump, yet Jiiks just doesn't care. Anyway, I'm going to switch this package to revision-based releases. Now it won't differ much from the cloned betterdiscord-git by samogot, except that I'm only going to bump it when the upstream is actually working properly. Things should be okay now, and working for every discord-*. Have a good day, everyone.

Lahvuun commented on 2017-10-18 07:56 (UTC)

Sounds like an issue with upstream. I think that's the reason I had an older commit as source previously. Gonna look into that now.

« First ‹ Previous 1 2 3 4 Next › Last »