For 3rd party ads, that is sometimes correct. What blocking js does is prevent cookie stitching, ie the joining of the first party id with the 3rd party cookie id. This is necessary for external ad networks.

Twitter runs mostly their own ads afaik, so they don't face this problem.