| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
The script prints usage if you run it with --help, so I don't see a need
for these examples. The examples are likely to get outdated when the
script options are changed, so I rather not have them there.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add support for cookies decryption for Chrome/beta
* Add support for firefox-snap, and multiple default/custom profiles
paths
* If no token can be found, like no key localConfig_v2 in
webappsstore2, try the best to fetch it from leveldb (or online copy
of it, if locked by running browser). When no luck even with that,
suggest the user to fetch it manually from dev console, and pass it
as an extra argument. This way it still saves some extra cycles for
the script users by fetching d/d-s values, and formatting the
ultimate registration command string.
Not tested on Darwin, leaving this as an exercise for you
Adding Chromium support should be straightforward and can be done in
follow-ups.
Signed-off-by: Bohdan Dobrelia <bdobreli@redhat.com>
Co-authored-by: Bogdan Dobrelya <bogdando@mail.ru>
|
| |
|
|
| |
Fixes #888
|
| |
|
|
| |
Fixes #889
|
| |
|
|
|
| |
WeeChat in Debian switched to Python 3 in bullseye (currently
oldstable), so the Python 2 instructions shouldn't be necessary anymore.
|
| |
|
|
|
|
| |
If I understand https://docs.brew.sh/Homebrew-and-Python correctly,
Homebrew Python installs python3 so you can use pip as described for
"Other".
|
| |
|
|
|
| |
Pip recommends using `python3 -m pip` instead of just `pip` (and Python
recommends using `python3` rather than just `python`).
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Automatically set completion_default_template on wee-slack buffers, so
emojis and usergroups can be tab completed without having to set
weechat.completion.default_template manually.
|
| |
|
|
| |
The setup-python action doesn't support Python 2.7 anymore.
|
| |
|
|
|
|
|
|
|
| |
If the line isn't found, line_pointer becomes an empty string which will
crash WeeChat when it's used with hdata_update. This happened when the
history for a channel that contained a reply also posted to the channel
was loaded, because in that case wee-slack tries to modify the parent
message before the channel history is printed, so it couldn't find the
line.
|
| |
|
|
|
|
|
|
|
|
| |
Since WeeChat now has multiline support, the problems with using
prefix_nick_<color> (mainly that it isn't possible to distinguish
between a multiline message and multiple messages when
weechat.look.prefix_same_nick is set) isn't present anymore, so we can
use this tag to properly mark lines as chat messages from a nick. This
also means that we don't have to use prefix_same_nick or
nick_prefix/suffix ourselves anymore.
|
| |
|
|
|
|
|
|
|
| |
Since WeeChat now has multiline support, the whole message is in one
chat line. This means that we don't need to look for all the lines
belonging to a message and modify them, we can just modify the line for
the message directly. This has the benefit of making it possible to
increase and decrease the number of lines for a message, rather than
having to join extra lines or get blank lines.
|
| |
|
|
|
|
| |
Don't insert a prefix at the start of each line of a message so it
renders normally in WeeChat 4.0.0 which supports chat lines with
multiple lines.
|
| |
|
|
|
|
|
|
|
| |
Without spaces, WeeChat will consider all the nicks as one word, which
means that rather than wrapping between nicks, it will fill the whole
line and wrap in the middle of nicks. Additionally, if you have disabled
weechat.look.align_multiline_words it will start from the beginning of
the line when wrapping, rather than after the prefix, which doesn't look
nice.
|
| |
|
|
|
| |
Remove a space before a colon and add a comma after a sentence starting
with if.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The url_private link for Slack posts just downloads a json of the post,
which isn't very useful to click on. The permalink goes to the web view
for a post, which is what we want. The web client adds origin_team and
origin_channel, which makes the post page show info about where the post
is shared, so add that here as well.
We still want to use url_private for images etc., not permalink there as
well, because that links to the Slack client with the image shown in the
sidebar, which is much more inconvenient than just getting the image
directly.
|
| |
|
|
|
|
|
|
| |
If a link preview was added by an app, like GitHub, instead of directly
by Slack, it was not detected by wee-slack as a link preview, so it
would be shown even if link_previews was set to false.
Fixes #834
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
One user experiences receiving a "HTTP/1.1 200 Connection established"
header block before a "HTTP/2 200" header block with the headers. I'm
not sure why specifically this happens, but I know a similar response
will happen if redirects are followed.
This wasn't supported by the http_check_ratelimited function which
splits the header from the body. It now splits out all the header blocks
from the body and uses the status and headers from the last one.
|
| |
|
|
| |
Fixes #871
|
| |
|
|
|
| |
This is only required for WeeChat < 1.5, and we require >= 2.2, so
there's no point in keeping this.
|
| |
|
|
|
|
|
| |
After moving the token in Slack API requests from a query string param
to an Authorization header in commit 2185a58 we require WeeChat >= 2.2
because that was the version which added support for setting HTTP
headers.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We used the response from rtm.start to find which IMs and MPIMs to open,
but after moving away from that we didn't have the information from the
response from conversations.list, so commit 962bbc5 changed to only open
unread ones.
However, it turns out that conversations.info has the information, and
we are already requesting that for each IM/MPIM to check if it's unread,
so we can use that to open the correct ones.
Fixes #875
|
| |
|
|
|
|
|
|
| |
Old type MPIMs (has `is_group: true`) has `is_open`, but not
`unread_count_display` in the response from `conversations.list`, so
they were not marked as unread on start if background_load_all_history
was set to false because we have to request the history, but
`check_should_open` created the buffer, so it wasn't requested here.
|
| |
|
|
|
|
|
|
|
|
| |
Apparently there are some bots which are not listed in users.list and
which sends messages where the only info about the sender is a bot_id.
To fix this properly we will have to look up the bot with bots.info when
we encounter an unknown bot_id, but for now just fall back to using the
id directly like we do with unknown users to make it possible to use
triggers and filters.
|
| |
|
|
|
| |
I've been the maintainer of this script for several years now, and Ryan
isn't involved anymore, so it makes sense to update the script author.
|
| |
|
|
|
| |
The script will use the new methods if the WeeChat version is new
enough, and the old deprecated methods if it's too old for the new ones.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When slack return a button message type and a url field is present we
should output the URL.
Fix: #811 and #810
|
| |\
| |
| |
| | |
Support new session tokens (xoxc tokens) and replace the usage of
rtm.start (which will soon stop working) with other API methods.
|
| | | |
|
| | |
| |
| |
| |
| | |
Limit should be used now, so it seems like count has been renamed to
limit.
|
| | |
| |
| |
| |
| |
| | |
On one of my teams, all the MPIMs have is_shared set to true and the
name is not set correctly if they are created as SlackSharedChannel
instead of SlackMPDMChannel.
|
| | |
| |
| |
| |
| | |
On one of my Slack teams, none of the MPIMs are included in
conversations.list if types include public_channel for some reason.
|
| | | |
|
