Gopher can serve html pages and still <img src=“tacking.pixel.com”> and this is what bad actors would continue to do. Switching underlying protocols won’t fix the problem. Even without html the companies that want that data could still do stuff like getting data out of server logs, or using other unique identifiers in gopher url paths. I dunno, technology probably won’t be able to fix this problem.
Gopher can serve html pages and still and this is what bad actors would continue to do
That’s a really good point. Unlike the web, Gopher has a chance to be saved from these things. It could be a really good time to draft and RFC or some kind of document about blocking tracking pixels from gopher html pages.
As for the server logs, accessing gophers through tor could help with that.
And yeah we need to also consider jamming the things that incentivize tracking. Good reminder that these problems aren’t solved only by technical means.
spot on! I definitely find myself sticking to spartan sites more often.
I agree!
That’s why I made a GUI gopher client, https://notabug.org/rain1/gopher
Gopher can serve html pages and still <img src=“tacking.pixel.com”> and this is what bad actors would continue to do. Switching underlying protocols won’t fix the problem. Even without html the companies that want that data could still do stuff like getting data out of server logs, or using other unique identifiers in gopher url paths. I dunno, technology probably won’t be able to fix this problem.
That’s a really good point. Unlike the web, Gopher has a chance to be saved from these things. It could be a really good time to draft and RFC or some kind of document about blocking tracking pixels from gopher html pages.
As for the server logs, accessing gophers through tor could help with that.
And yeah we need to also consider jamming the things that incentivize tracking. Good reminder that these problems aren’t solved only by technical means.
In order to deliver a tracking pixel, the user would have to select it, purposefully.