* additional caller id for calls coming from outside the country
* salary ranges for an open position is a good start. I would also like to see age of opening, number of people interviewed or evaluated, number of applications submitted. Many times job postings just feel false, like a data grab
* DNS block lists built into home routers by default.
a tool that actually shows what third party SDKs in your own apps are phoning home to would be huge, most people have no idea what their own dependencies are sending out. everyone builds network level tools but that app level visibility is missing.
Oh, now this is important. I'm not too familiar with app security, especially telemetry, but I will look into the process of making something like this.
* Strong barriers against caller id spoofing
* additional caller id for calls coming from outside the country
* salary ranges for an open position is a good start. I would also like to see age of opening, number of people interviewed or evaluated, number of applications submitted. Many times job postings just feel false, like a data grab
* DNS block lists built into home routers by default.
* vpn points built into home routers by default
a tool that actually shows what third party SDKs in your own apps are phoning home to would be huge, most people have no idea what their own dependencies are sending out. everyone builds network level tools but that app level visibility is missing.
Oh, now this is important. I'm not too familiar with app security, especially telemetry, but I will look into the process of making something like this.
google drive where you don’t see the files, but you see the people who you shared to, and if you click you can see which files.
I want residential proxy IPs.
That sounds interesting, could you explain how that would work?
What do you think are the biggest privacy and security challenges users face at scale? Determine the problem, work back to the solution.
https://ssd.eff.org/