Custom Nitter Instance Not Working about discord-twitter-webhooks HOT 7 OPEN

Please do not use public instances for your bots and operate your own. We will probably have to rate limit you, or straight up block bots due to how brittle the current rate limit situation from twitter is. There is a high chance you are already blocked due to cloud providers being the biggest source of scrapers.

from discord-twitter-webhooks.

OK, yes, creating a new feed after changing the default instance will apparently use the new instance. @TheLovinator1 given the present circumstances I think it'd be better if the currently selected default Nitter instance was used for all feeds instead of whatever instance was in use when the feed was originally created, and/or, allow changing the instance used for individual feeds.

Ethan I think we've annoyed him too much, lol.

from discord-twitter-webhooks.

@TheLovinator1 any chance you have time to look into this? It'd be great to be able to workaround the current Nitter issues!

from discord-twitter-webhooks.

After changing the Nitter instance, I noticed many URLs to the old instance in the database. I assume there's some kind of comparison happening here after the instance change that causes this issue.

Knowing this, I found a less-than-ideal workaround.

1. Delete discord_twitter_webhooks.db (this will reset everything to defaults)
2. Set the Nitter instance in Settings
3. Re-add all of your Feeds

Feeds will then function as expected, using the newly-set, non-default Nitter instance.

from discord-twitter-webhooks.

I noticed this too, I thought it just saved the currently selected instance when creating a feed. Does it not use the new instance when you create a new feed? I can't remember if I tested it or not @EthanC

from discord-twitter-webhooks.

Hm, I didn't test creating a new feed without first deleting the db. But I can confirm that deleting the db, setting the new instance, and then creating a new feed will in fact use the new instance.

from discord-twitter-webhooks.

Ah it's just a SQL database, might be able to just change the instance for the feeds with sed or something

from discord-twitter-webhooks.