Category Archives: Internet
Wish I could go, but SF is a long way away from Miami.
Must read: Kieren McCarthy, ICANN’s leaving the nest, so when will it grow up? The org that will run the internet still acts like a teenager.
Protected by its important father, the US government, ICANN has become a surly, entitled, and vain figure. It will want for nothing. It will listen to no one. It is always right. …
Unfortunately, the real ICANN has a visceral loathing of anything decided by its “community” – the people it is supposed to be serving. …
Despite ostensibly being a community organization, at its thrice-yearly conferences ICANN corporate tightly controls the agenda. There are no “unconferences” or even community-led sessions. All sessions – and frequently panelists – are chosen and controlled by the staff. Sessions are added and removed according to whim.
Just as ICANN was showing real signs of maturity, it lapsed. Rather than using its greater autonomy to step up to the plate, the prevailing atmosphere within the organization was that it couldn’t believe its luck. And then, with the arrival of a new CEO and the approval of the money-minting new gTLD program, ICANN more than quadrupled its own budget. It’s now a child with both fewer constraints and more money to spend.
Now in 2016, with the transitioning of the IANA contract, ICANN is finally coming of age and the US government can no longer expect to keep it in its house. Rather than sending forth a well-prepared and mature young adult, however, we’re letting loose a know-it-all teenager with a chip on its shoulder and a determined belief that it doesn’t have to listen to anyone.
Milton Mueller’s ICANN Accountability – Present, Future and Past is good too, but more polite. (Which, if you know Milton, is quite an amazing thing to be writing!)
There’s this company that calls my office over and over. And over. And leaves messages asking me to go on their site and ‘claim my profile” that they have already concocted for me. It’s been going on for weeks, always at times I happened to be out. Note that it never sounded like robo-calling, but rather like call-center humans.
Finally, I happened to be in the office recently and answered a call from them (it was a human). I asked, begged, pleaded, to be put on their Do Not Call list.1
Begging didn’t work. There’s a message from them on my voice mail again today.
So far, I’m standing strong, not giving in, not registering on their web site. Even if would shut them up. But I’m also a bit afraid to name them here, because it seems to me that that given their less-than-perfect authentication methods–which include linking to social media on which I do not have accounts–there is a substantial impersonation risk.
Should I just give in and ‘claim my profile’?
This leaves aside the question whether the calls violate state or federal ‘do not call’ rules; I’m signed up for both, but since they are not actually selling anything or asking for money, they might be off the hook? ↩
- In the Location bar, type about:config and press Enter.
- The about:config “This might void your warranty!” warning page may appear. Click I’ll be careful, I promise! to continue to the about:config page.
- Search for privacy.trackingprotection.enabled.
- Double-click privacy.trackingprotection.enabled to toggle its value to true.
This will turn on Tracking Protection. If you later want to turn it back off, repeat the above steps to toggle the preference back to false.
As The Wall Street Journal recently reported, “There’s an Uber for everything now. Washio is for having someone do your laundry, Sprig and SpoonRocket cook your dinner and Shyp will mail things out so you don’t have to brave the post office. Zeel delivers a massage therapist (complete with table). Heal sends a doctor on a house call, while Saucey will rush over alcohol. And by Jeeves — cutesy names are part of the schtick — Dufl will pack your suitcase and Eaze will reup a medical marijuana supply.”
I thought MoDo had been played, but it’s all true, even if some of them only serve Seattle and Silicon Valley.
In order to get box.com to work on my computer, I had to enable TLS 1.0, 1.1, and 1.2 in Internet Explorer, even though I almost never use IE.
I had turned off all three versions of TLS on security grounds. As a result, I kept getting an error message when I tried to log into Box Sync on my computer (“Cannot connect”).
Box.com help desk’s explanation for the requirement — amazingly — is that SSL 3.0 is not secure so they don’t use it. It’s true there have been issues with SSL 3.0, but TLS, as I understand it, has the same issues plus much worse. [UPDATE: Dan Riley explains why I have it all backwards in the comments.]
On the positive side, I only figured out the source of the problem thanks to efficient and friendly work from ‘Ashley’ at the box.com help desk, so they are doing something right.