Slashdot discussion re: Verizon Fios customer's experience:
"However, his Netflix video streams were limping along at just
375kbps (0.375mbps), equivalent to 0.5 percent of the speed he's
paying for. On a hunch, he decided to connect to a VPN service,
which in theory should actually make thing
Begin forwarded message:
> From: "A. Richard Miller"
> Date: July 23, 2014, 9:21:42 PM EDT
> To: "Boston Linux Unix User Group/John Abreau, Ex.Dir." ,
> Boston Linux and Unix Users Group/Jerry Feldman , "Boston Linux
> Unix User Group/Will Rico, Beginners Group" , Boston User
> Groups/John R
When: Wednesday, Aug 6, 2014 6:30PM
Location: Akamai, 8 Cambridge Center, Cambridge, MA
Directions
http://www.akamai.com/html/about/driving_directions.html
Also easily accessibly by T.
Notes
1) Please note the location is different from BLU's
standard MIT meeting location.
2) Akam
Hi All,
I've recently been asked to work with a team of PHP developers on a
pretty large and complex project. The code they have submitted works,
but it has a bunch of warnings and notices in the logs. I personally
think this is sloppy coding. My question is, how strong a stand should
I ta
On 7/26/2014 5:56 PM, Eric Chadbourne wrote:
Hi All,
I've recently been asked to work with a team of PHP developers on a
pretty large and complex project. The code they have submitted works,
but it has a bunch of warnings and notices in the logs. I personally
think this is sloppy coding. M
I've had too many experiences where some sloppy coder was flooding the logs
with pointless warnings to the point that the logs were useless for
diagnosing actual problems. The clues I needed in order to diagnose a real
problem were lost in all the noise.
Sloppy coding has a high maintenance cost,
Web development is a ghetto or even, still, the wild wild west. A properly
configured and developed web site with no warning would probably only
serve static web pages. If you log nothing, you miss important errors and
warnings, if you log more, you will get stupid errors and warnings.
The real is
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss-
> bounces+blu=nedharvey@blu.org] On Behalf Of Stephen Ronan
>
> Slashdot discussion re: Verizon Fios customer's experience:
> "However, his Netflix video streams were limping along at just
> 375kbps (0.375mbps), equivalent to 0
On 7/26/2014 10:57 PM, Edward Ned Harvey (blu) wrote:
> Yup, but remember there are two possible explanations why:
Neither of which are at all relevant. All Netflix traffic is encrypted
but this did not prevent Comcast from intentionally degrading Netflix
traffic throughput. All Netflix traffic is
