you misunderstand me – firefox is helpful in this respect, but there’s only so much it can do.
and i engage in anti-tracking practices and extensions when i learn of them and the point of my comment is that the the developers on the server side inevitably keep finding ways to circumvent each iteration eventually.
i’ll always continue to do my best, but it’s clear they’re the better supplied side in this arms race
to answer your question: my comment was spurred on my instagram recognizing who i was on a device that i had never used before, on a sim/phone plan that i had never used before, using firefox in private mode.
i’m best guess so far is that some sort of 3rd party tracker was part of a different service that i had used the device earlier in the day clued in instagram into who i was.
you misunderstand me – firefox is helpful in this respect, but there’s only so much it can do.
and i engage in anti-tracking practices and extensions when i learn of them and the point of my comment is that the the developers on the server side inevitably keep finding ways to circumvent each iteration eventually.
i’ll always continue to do my best, but it’s clear they’re the better supplied side in this arms race
Actually the implementation of tracking methods and data collection is much more easier than implementing methods to prevent them.
Can you please point out which service you specifically talking about?
i suspected that @spectre@hexbear.net was up to no good. loledit: whoops, wrong post. lol
to answer your question: my comment was spurred on my instagram recognizing who i was on a device that i had never used before, on a sim/phone plan that i had never used before, using firefox in private mode.
i’m best guess so far is that some sort of 3rd party tracker was part of a different service that i had used the device earlier in the day clued in instagram into who i was.