• elscallr@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    1 year ago

    That’s because you don’t know what an “internet service provider” is. Twitter is not one.

      • elscallr@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        5
        ·
        edit-2
        1 year ago

        Twitter isn’t, and shouldn’t be under any obligation to respond to you proxying your requests through their url tracker with any service level.

        Is it unethical? Yeah. Does it violate the letter of proposed NN laws? No. Does it violate the spirit of proposed NN laws? Also no. Those laws don’t cover what happens while a request is inside a parties network, only the traffic that travels in and out of it, of which Twitter was manipulating neither.

        Well, I suppose they could deliver a few packets with a couple microseconds of latency when they delivered the HTTP response payload but they would have to literally modify their OS’s TCP stack to do so and the entirety of that actual throttling would be literally milliseconds of difference.