[GH-ISSUE #119] Add Keyword Filter for Tweets #29

New issue

TheLovinator · 2026-09-02T13:09:00+02:00

TheLovinator commented

2026-09-02 13:09:00 +02:00

Originally created by @EthanC on GitHub (Jul 16, 2023).
Original GitHub issue: https://github.com/TheLovinator1/discord-twitter-webhooks/issues/119

In the previous version, we could filter for Tweets containing specific keywords in the search query. For example, the following query would only post Tweets to the webhook if the words "sale", "discount" or "deal" were in the Tweet body.

(sale OR discount OR deal) from:Steam

This functionality could be re-implemented in the rewrite by adding a text field containing the required keywords for a feed.

Originally created by @EthanC on GitHub (Jul 16, 2023). Original GitHub issue: https://github.com/TheLovinator1/discord-twitter-webhooks/issues/119 In the previous version, we could filter for Tweets containing specific keywords in the search query. For example, the following query would only post Tweets to the webhook if the words "sale", "discount" or "deal" were in the Tweet body. - `(sale OR discount OR deal) from:Steam` This functionality could be re-implemented in the rewrite by adding a text field containing the required keywords for a feed.

TheLovinator closed this issue

2026-09-02 13:09:00 +02:00

TheLovinator commented

2026-09-02 13:09:00 +02:00

@EthanC commented on GitHub (Jul 16, 2023):

On the opposite end of the OR search operator, there's AND. This functionality would be appreciated as well. For example, the following query would only post Tweets to the webhook if the words "rust" and "deal" were in the Tweet body.

(rust AND deal) from:Steam

@EthanC commented on GitHub (Jul 16, 2023): On the opposite end of the `OR` search operator, there's `AND`. This functionality would be appreciated as well. For example, the following query would only post Tweets to the webhook if the words "rust" and "deal" were in the Tweet body. - `(rust AND deal) from:Steam`

TheLovinator commented

2026-09-02 13:09:00 +02:00

@dziban303 commented on GitHub (Jul 19, 2023):

This is really the most important feature addition for our use case. We like to track events like earthquakes, volcanic activity, tornadoes, and raspberry pi deals (one of these things is not like the other, lol); but filtering is necessary because minor quakes, EF0 tornadoes, and Pi Zeros aren't all that interesting.

@dziban303 commented on GitHub (Jul 19, 2023): This is really the most important feature addition for our use case. We like to track events like earthquakes, volcanic activity, tornadoes, and raspberry pi deals (one of these things is not like the other, lol); but filtering is necessary because minor quakes, EF0 tornadoes, and Pi Zeros aren't all that interesting.

TheLovinator commented

2026-09-02 13:09:00 +02:00

@TheLovinator1 commented on GitHub (Jul 25, 2023):

Hi, sorry for not being faster with this.

I added two ways to whitelist/blacklist tweets. The first one is just checking if the string is in the tweet and the other one is using regex. I have to add a way to see what tweets gets blocked/allowed but this should be a start.

Right now I am just doing:

If not whitelisted:
    continue
If blacklisted:
    continue

Should it be like this instead?

If not whitelisted:
    continue
If blacklisted:
    If whitelisted:
        send_even_if_blacklisted()
    continue

@TheLovinator1 commented on GitHub (Jul 25, 2023): Hi, sorry for not being faster with this. I added two ways to whitelist/blacklist tweets. The first one is just checking if the string is in the tweet and the other one is using regex. I have to add a way to see what tweets gets blocked/allowed but this should be a start. Right now I am just doing: ``` If not whitelisted: continue If blacklisted: continue ``` Should it be like this instead? ``` If not whitelisted: continue If blacklisted: If whitelisted: send_even_if_blacklisted() continue ```

TheLovinator commented

2026-09-02 13:09:00 +02:00

@dziban303 commented on GitHub (Jul 25, 2023):

For my purposes, the current implementation is best. I currently only have one feed configured with both white and blacklists: I want the tweets with whitelisted strings posted, unless the one blacklist word appears. If I understand correctly, the second option you mention would break that functionality and post it anyway. I can see situations where that would be useful, but I'd say leave it as-is unless someone requests it :)

We really appreciate your work on this!

@dziban303 commented on GitHub (Jul 25, 2023): For my purposes, the current implementation is best. I currently only have one feed configured with both white and blacklists: I want the tweets with whitelisted strings posted, unless the one blacklist word appears. If I understand correctly, the second option you mention would break that functionality and post it anyway. I can see situations where that would be useful, but I'd say leave it as-is unless someone requests it :) We really appreciate your work on this!

TheLovinator commented

2026-09-02 13:09:00 +02:00

@EthanC commented on GitHub (Jul 25, 2023):

The current implementation is probably best as it's simpler for the user and less work for you. Much appreciated!

@EthanC commented on GitHub (Jul 25, 2023): The current implementation is probably best as it's simpler for the user and less work for you. Much appreciated!

TheLovinator referenced this issue

2026-09-02 13:09:14 +02:00

[PR #29] [MERGED] Bump types-requests from 2.27.9 to 2.27.10 #73

Sign in to join this conversation.