18 digit Twitter user IDs behaving differently in statuses/filter

[agency]

I’m streaming 11 user IDs in statuses/filter follow parameter. 4 of the IDs are the newer 18 digit user IDs, the remaining 7 are older, shorter user IDs.

The four newer 18 digit Twitter user IDs are being completely ignored by the stream, while all of the shorter user IDs are consistently returning new statuses.

Does this make any sense to anyone?

[agency]

no matter, tracking their screen names instead works fine:

    const stream = T0.stream('statuses/filter', {
      track: [
        'BTS_Billboard',
        'BTS_ARMY_I',
        'btsanalytics',
        'BT21_'
      ],
      follow: [
        335141638,
        1409798257,
        573299587,
        // 806179924407107585,
        221390506,
        // 817052056125108224,
        // 864525927438536707,
        975000510,
        // 894537112225067008,
        165033159,
        343918695
      ]
    });

[b_lw]

It looks like you’re developing in Javascript and handling the IDs as integers.
Twitter IDs are now 64-bit unsigned integers whereas JavaScript is only able to handle integers up to 53 bits.
Therefore you’re losing accuracy for your 18-digits IDs.

Try sending your comma separated list of IDs as a string instead of an array of integers, it should work.

Also, when reading the data returned by the API you should use the id_str field instead of id.

[agency]

you rock. awesome. thank you.

(off topic: please see my faces about how app passwords haven’t worked for a year to log into iOS Twtr)

[QuantumDecay]