Some of their stories were surprising, and I wonder if women in any CS/IT related field are subject to similar situations."
Link to Original Source
Submission Summary: 0 pending, 4 declined, 0 accepted (4 total, 0.00% accepted)
Instead I asked to be transferred to the sales department and requested the rep show me where I should have seen Verizon stated they block port 80. Sales was less helpful & even more frustrating. The rep was unable to produce where I would have seen this, and was unable to find Verizon's TOS so we could reference it. The icing on the cake was the promised, within 24 hour, callback from a sales supervisor that never occurred.
From my own digging through the TOS, I can confirm Verizon does not mention blocking port 80 on residential accounts. Clearly Verizon does not understand their own policies. The closest I can find is a mention that residential accounts may not use web-servers, yet their own IT department gave me the solution of running my web-server on an alternative port. Additionally some applications blur the line between client and server; I wonder if prohibiting a "server" is reasonable or if many customers are unknowingly breaking this rule now.
Today I'm reading through docs on fcc.gov about network neutrality to find some leverage before I call their sales unit again.
Has anyone else at Slashdot been down this road with Verizon, or a similar ISP and 'won' through reason?
Can anyone else recommend additional (US legal) sources that may help me, and future American geeks with home web-sites, to combat Verizon and its restrictive residential policies."
If you think nobody cares if you're alive, try missing a couple of car payments. -- Earl Wilson