Tweetscout API: 403 Forbidden

[Lezek123]

The problem

Requests to tweetscout API fail with 403 Forbidden and a message: 'api key not payed'.

We're using this API to get:

• number of @JoystreamDAO followers on X
• @JoystreamDAO's tweetscoutScore (unique for tweetscout)
• @JoystreamDAO's "topFollowers" (Featured followers on https://www.joystream.org) on X

Because the API doesn't work anymore and we're missing this data, we get validation errors in this status server, ie.:

ZodError: [
  {
    "code": "invalid_type",
    "expected": "number",
    "received": "null",
    "path": [
      "community",
      "twitterFollowerCount"
    ],
    "message": "Expected number, received null"
  },
  // ...

This prevents ALL dashboard data from being updated, resulting in stale data being displayed on https://www.joystream.org/

Possible solutions

1. Pay for tweetscout API access ($49 / 10k requests according to https://app.tweetscout.io/developer)
2. Use free tier of X.com API to retrieve the number of followers (https://api.twitter.com/2/users/by/username/JoystreamDAO?user.fields=public_metrics), remove other statistics like Tweetscout score and Featured followers from joystream.org.

Additionally, the validation issue should be addressed separately (see #54)

[bedeho]

Thanks for doing this analysis.

I wonder perhaps the least overhead here is just to use static data for the time being?

Happy to pay the API access also, but how long would this last? is it one request per visit? if so I guess perhaps doing some sort of caching could make sense, as this data likely very rarely changes materially.

Ill leave it for you to decide, we go with whatever you think is best.

[Lezek123]

Happy to pay the API access also, but how long would this last? is it one request per visit? if so I guess perhaps doing some sort of caching could make sense, as this data likely very rarely changes materially.

It's queried every 4 hours with cron and cached, so theoretically it's only ~2190 requests / year, excluding queries being made for testing purposes etc.

[bedeho]

oh, so why dont we just stick with it then? Just pay for more access?