Media uploads v1.1 deprecation

[haleyngonadi]

Is your feature request related to a problem? Please describe.
Not exactly.

Describe the solution you'd like
I have just received an email that states: We plan to deprecate the legacy v1.1 media upload endpoints on March 31st 2025 for self serve developers (Free, Basic and Pro tiers). This means the incredible implementation we have currently would likely not work as expected come March 31.

Describe alternatives you've considered
N/A

Additional context
https://docs.x.com/x-api/media/media-upload

[danieldevine]

Hi, am aware of this and will look into the feasibility of addressing it very shortly.

[grenaria]

bird-elephant-issue-67.patch

Here's a patch that works with the new API. It's almost a drop-in replacement, however when initializing the Media object the id field is different:

$media->mediaIds([$mediaUpload->media_id_string]); changes to $media->mediaIds([$mediaUpload->data->id]);

        $be = new BirdElephant([
...auth tokens
        ]);
        $media_info = $be->tweets()->upload($file);
        $media = new Media();
        $media->mediaIds([$media_info->data->id]);
        $tweet = new Tweet();
        $tweet->text = 'Testing media upload';
        $tweet->media($media);
        $be->tweets()->tweet($tweet);

The patch can be added to composer.json like this:

    "extra": {
        "patches": {
            "coderjerk/bird-elephant": {
                "Issue 67 - Support v2 media upload API": "path/to/patchfile/bird-elephant-issue-67.patch"
            }
        },
    }

Here is the PR #69

[danieldevine]

Hey, I'm currently in a round of testing but will most likely merge the above in the next few days, thanks for the PR

[grenaria]

In Twitter's infinite wisdom, they have deprecated part of the new media upload API and added new endpoints.

https://devcommunity.x.com/t/media-upload-endpoints-update-and-extended-migration-deadline/241818

I will be revising my PR to add support for the new API endpoints ASAP.

[grenaria]

The PR has been revised but please note that the new API seems very unstable. A lot of people are reporting issues with it and I had to wait 2 days to get it to not fail with 500 errors so that I could test the changes.

I should also note that I changed the module to be backward compatible with the older API. This was done because I had to work around inconsistencies in the returned objects from the new v2 API endpoints.