[colug-432] Ping

[Rick Hornsby]

There are multiple ways to measure the "speed" of your link, and dozens of factors involved.  Ping really just tells you the latency (how long a single packet takes to travel round trip) to your target destination.

It sounds like they tried to detect your connection speed, found that it was slow, and served up lower resolution (and smaller file size) images.

Sent from my iPhone

> On Dec 7, 2013, at 14:20, tom <thomas.w.cranston at gmail.com> wrote:
> 
>> On 12/07/2013 01:02 PM, Bill Baker wrote:
>> The first instance is because you have http:// before the domain name.
>> The second is because you have a / after it.
>> 
>>> On 12/07/2013 01:36 PM, tom wrote:
>>> Why can't I ping http://www.newyorker.com/?
>>> 
>>> I can bring it up in my browser, but can not ping it.
>>> 
>>> tom at tom-Inspiron-1520 ~ $ ping -c5 http://www.newyorker.com/
>>> ping: unknown host http://www.newyorker.com/
>>> 
>>> 
>>> tom at tom-Inspiron-1520 ~ $ ping -c5 www.newyorker.com/
>>> ping: unknown host www.newyorker.com/
>>> 
>>> Tom
>>> 
>>> _______________________________________________
>>> colug-432 mailing list
>>> colug-432 at colug.net
>>> http://lists.colug.net/mailman/listinfo/colug-432
>> _______________________________________________
>> colug-432 mailing list
>> colug-432 at colug.net
>> http://lists.colug.net/mailman/listinfo/colug-432
> Thanks.
> 
> ping -c5 www.newyorker.com
> 
> That works.
> 
> I asked their tech support why archives came up blurred. They told me it 
> was because I had a slow connection. So ran ping to see what speed I was 
> getting. My providers tower fell down. They put up a temporary tower. I 
> was getting speeds in the range of 40. ms. Looks like they have improved.
> 
> Tom
> _______________________________________________
> colug-432 mailing list
> colug-432 at colug.net
> http://lists.colug.net/mailman/listinfo/colug-432