2 ms·
Those FCC registration records would then be public information. Would you feel comfortable with your name, address and MAC + SSID of your wireless AP(s) being
by alyandon 5y ago
Those FCC registration records would then be public information.
Would you feel comfortable with your name, address and MAC + SSID of your wireless AP(s) being registered in a public database and the onus on you to keep that registration information up to date every time you changed the SSID or swapped in something with a different MAC address?
I'm not sure I would be.
The ethics around Google's behavior aside - this is a tricky problem to solve.
Edit: Why the downvotes? I'd really like for people that disagree to engage and tell me where I am either wrong or not arguing in good faith. If you believe this is a Google specific problem or somehow an easy problem to solve under the current FCC regulatory regime I'd be happy to hear about it.
- ratww 5y agoThere's no need for a database. Just add the suffix "_optin" to your SSDI and you're opted in. This is what they're currently requiring for the opt-out, I can't see why the same solution can't be used for opt-in...
- alyandon 5y agoI just don't see either approach (opt-in vs opt-out) being workable in practice though. Taking it to a bit of a silly extreme - what happens when 100 different companies want to use public SSID data? 100 different opt-in codes? 1 code for all? What if I want to allow 5 companies out of that 100 to use that data and exclude the other 95?
- shkkmo 5y agoDoesn't the exact same argument apply to using an opt-out approach, but much worse? If two companies use different suffixes, that makes it impossible to opt out of both. Edit: The only reason this isn't already an issue is because Microsoft made their opt-out work anywhere in the SSID