Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Benedikt was thinking about the same, proxies only anonymise you if they are very very busy
-
@epse Yup but I wanted to make something similar, simple as that :)
-
So.. proxy Google services? With all due respect but things like login flow and email traffic and such is not something I'd like to entrust to a proxy, whether that's ran by someone I personally know (such as you), or someone I don't. It's too easy to snoop on it. And that's especially dangerous given that a Google account can be used to access more than half of most users' other accounts. For the purpose of privacy, just limit your exposure to Google to begin with. And for the purpose of IP forwarding, use a VPN. But I don't think that a proxy like this would be a solution, or even a good idea at all.
-
@Condor I'm not sure what you're misunderstanding by static resources? (Googleapis for example, this is just meant to serve up some of those pesky libraries delivered by google (and Facebook and others for that matter) cdn's.
I definitely understand that you wouldn't trust any proxy with login stuff nope. -
@Condor To clarify, while testing I used one of the fonts you can download through googleapis. (Also did some tests with cloudflare)
-
@Condor this would be a similar thing as the add-on Decemtraleyes. Just making sure that stuff hosted with cdn's will be proxied to local resources, in my case to a proxy ran by me.
-
@Wack Possibly, I've never worked with varnish and this does work right now. (My reasoning behind it)
Would uploads and such be done through the same domains? (Again, this is just for static resources) -
@linuxxx depends on what you mean by static ressource. Ex. The static google maps image or the google maps js sdk both require a token in the request url. If they are called from the frontend, then sure, anyone would see them anyway, however if they're called in the backend and processed/stored, then not neccessarily.
-
@Wack I'll give an example when home, good one, might need some advice on this!
Just wrote a (PHP based) proxy which can cache resources being requested and serve them to clients.
The idea is that (I'm going to write a firefox add-on for it too, yes) you can install the add-on and any resource (js/CSS, general web resources which would be downloaded off of googleapi's etc) hosted with Google would be proxied through the server running the proxy, meaning that one wouldn't have to connect to the mass surveillance networks directly anymore as for static resources.
I think checksum verify stuff would still work as the proxy is literally a proxy, the content will be identical to the 'real' resource. (Not sure about this one, enlighten me if this isn't true)
Input appreciated!
rant