Package Details: slack-libpurple-git r375.ee43d55-1

Git Clone URL: https://aur.archlinux.org/slack-libpurple-git.git (read-only, click to copy)
Package Base: slack-libpurple-git
Description: A purple-based (Pidgin) plugin for Slack.
Upstream URL: https://github.com/dylex/slack-libpurple.git
Licenses: GPL3
Provides: libslack.so
Submitter: sergej
Maintainer: richedge39
Last Packager: richedge39
Votes: 17
Popularity: 0.000000
First Submitted: 2017-08-11 17:01 (UTC)
Last Updated: 2024-11-15 15:01 (UTC)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

richedge39 commented on 2023-04-25 18:52 (UTC) (edited on 2023-05-17 16:18 (UTC) by richedge39)

The following issue is now resolved. Removed references to the finduserhack branch. * https://github.com/dylex/slack-libpurple/issues/173

To login to certain workspaces, you can now use your "USERID." This is a string that can be found after logging in via the web ui: https://app.slack.com/

Then pop open your browser's developer console find local storage for app.slack.com. Look for a jsonblob under the key "localConfig_v2." This will include teams> team id > user_id. The string inside the user_id key should be used in place of your username. For the password box, use your actual password.

Also, if you haven't already tried, please clean build this. To do so using makepkg:

makepkg --clean -f

makepkg --install

Strykar commented on 2023-03-28 08:31 (UTC) (edited on 2023-03-28 08:31 (UTC) by Strykar)

Build fails, log - https://gist.github.com/Strykar/af7041b70753a336361cac2746256751

warning: remote HEAD refers to nonexistent ref, unable to checkout
==> Starting pkgver()...
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: Needed a single revision
==> Updated version: slack-libpurple-git r.-1
==> Starting build()...
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: A failure occurred in build().

vasya commented on 2023-03-26 20:10 (UTC)

@loki7990, oops, somehow I've missed this comment on time. I've removed the dependency now.

@all: Please report if anything's broken.

loki7990 commented on 2021-05-21 22:25 (UTC) (edited on 2021-05-21 22:31 (UTC) by loki7990)

Is json-parser necessary? It seems to not be mentioned at all in the README of the repo.

EDIT: Indeed, it was removed a long time ago

vasya commented on 2020-01-21 18:12 (UTC) (edited on 2020-01-21 18:14 (UTC) by vasya)

@CyberShadow, understood now. The patch still changes the code, but the change itself is meaningless now. Removed the patch and pushed the new (cleaner) version (along with version dump). Thanks!

CyberShadow commented on 2020-01-21 17:57 (UTC) (edited on 2020-01-21 17:58 (UTC) by CyberShadow)

Probably it was sent upstream at the same time as added to this package. Now that upstream applied it, it's no longer needed here. Thanks!

vasya commented on 2020-01-21 17:56 (UTC)

Hi. The package was disowned by sergej right now, and I've just adopted it. If you have any improvement ideas, please share.

Does anybody know why we had the "patch" in the first place, what does it do?

CyberShadow commented on 2018-11-08 15:22 (UTC)

@vasya Your proposed "patch" is almost exactly what's already in the current code:

https://github.com/dylex/slack-libpurple/blob/master/slack.c#L128-L131

api-token-in-passwd.patch is currently completely unnecessary. @sergej should have removed it in commit 437d7a03a9ba instead of "updating" it.

vasya commented on 2018-11-08 13:44 (UTC)

I wonder, can the patch be reduced to?: + if (!token || !*token) { + token = purple_account_get_password(account); + } One indentation less than currently, placed before the current already-existing "if".

CyberShadow commented on 2018-07-22 02:46 (UTC)

Why is api-token-in-passwd.patch needed? There is code which does exactly what the patch adds directly above the added code. In fact, you can even see the purple_account_get_password in the original code in the patch's context.

1 2 Next › Last »