How to link in pictures without stealing bandwidth!

[benburch]

This works for most pictures. 

Say you have a picture you want to use in a posting; 

http://foobar.com/JulieNewmar.jpg 

Now, if you just link it to your LJ posting, you immediately
start stealing bandwidth from foobar.com.

This is simply not a nice thing to do as some websites pay for
every byte they transfer. 

If you change that URL a little; 

http://foobar.com.nyud.net:8090/JulieNewmar.jpg 

It then uses a free public caching service. It gets fetched
ONCE from foobar.com, and they are not made bankrupt as each
of LJ's horny guys look at your Catwoman picture. 

It helps to preview the posting before you hit post as this
gets the caching service to do the initial fetch of the
picture, which can be slow, before your posting appears to the
public. Sometimes you need to wait a few minutes and
re-preview it before everything will appear as it should, and
some web servers will not play ball with the cache, and this
is how you weed those out. 

ENJOY!

[derby378]

1. So, do you use that same tag on each image?

If so, I'll be sure to keep it in mind.

[benburch]

2. Yes.

Just add .nyud.net:8090 to the end of address part of the URL

[SoCalDem]

8. testing...(on preview, it did not work.)

http://socaldem.smugmug.com/photos/54727462-L.jpg.nyud.net:8090

[benburch]

9. This thread seems to be frozen in plain text mode.

Uncheck the little "Message Format" box  above the
Subject bar in the message editor and re-post this.

Correct syntax is

http://socaldem.smugmug.com.nyud.net:8090/photos/54727462-L.jpg

[benburch]

10. Thus...

http://socaldem.smugmug.com.nyud.net:8090/photos/54727462-L.jpg

[SoCalDem]

13. I took you literally when you said "at the end of the url"

:)

and deliberately checked the box :)

[hootinholler]

19. Ah, there's the rub, he said address part...

A URL (which is very similar to a URI) consists of these bits: <protocol>://<address>/<path to resource>?<query> of which, the protocol and address are mandatory. Refer to the nice example in your address bar above ;)

<protocol>: How the 2 computers will 'negotiate' the return of the thingie to be fetched. (ex: http: ftp: {there should be a BitTorrent protocol})

<address>: the FQDN (fully qualified domain name) of the host providing the resource and the port number that protocol is answered on. HTTP by default is port 80

<path>: where on the hard drives the resource lives.

<query>: additional parameres that the server may need to identify the resource, often name:value pairs used by programs, like this forum. (?az=view_all&...)

So, now that your eyes are good and glazed, what's happening here is that the machine named nyud.net is running an HTTP server on port 8090. When it gets a request for something, it strips out its own name and port from the URI and then it checks to see if it got it already, and if not, it goes and gets one copy that it keeps hanging around for a while to send back to anyone else that wants it.

I haven't looked at it yet. Theoretically it should be able to handle requests for any http server thingie served, meaning entire web pages. Crafting URLs to pass through several of these services would make it a real PITA to track someone down for looking at say a dissenting website.

The results for dynamic pages like DU, would be dissapointing at best, but possibly could be used to store a snapshot of a thread if something interesting happens.

-Hoot

[KarenS]

3. ThankYou for this information =) N/T

[Steve A Play]

4. The Coral Content Distribution Network

Only fair to give credit where credit is due!

http://www.coralcdn.org/

What is Coral?

Coral is peer-to-peer content distribution network, comprised
of a world-wide network of web proxies and nameservers. It
allows a user to run a web site that offers high performance
and meets huge demand, all for the price of a $50/month cable
modem.

Publishing through Coral is as simple as appending a short
string to the hostname of objects' URLs; a peer-to-peer DNS
layer transparently redirects browsers to participating
caching proxies, which in turn cooperate to minimize load on
the source web server. Sites that run Coral automatically
replicate content as a side effect of users accessing it,
improving its availability. Using modern peer-to-peer indexing
techniques, Coral will efficiently find a cached object if it
exists anywhere in the network, requiring that it use the
origin server only to initially fetch the object once.

One of Coral's key goals is to avoid ever creating hot spots
in its infrastructure. It achieves this through a novel
indexing abstraction we introduce called a distributed sloppy
hash table (DSHT), and it creates self-organizing clusters of
nodes that fetch information from each other to avoid
communicating with more distant or heavily-loaded servers.

A preliminary deployment of CoralCDN has been online since
March 2004, running on the PlanetLab testbed. As of November
2005, it receives almost 20 million requests per day from over
1 million unique clients.

Steven P. :kick:

[benburch]

5. Thanks!

I was trying to keep the information simple to digest and
remember, but when I repost it in the future I will include
the URL.

[hootinholler]

16. I hate it when my hash table is sloppy

I tend to loose hash that way :evilgrin:

Seriously, I need to have a look at this, thanks for the
pointer.

-Hoot

Hmmm. did we loose smilies?

[Steve A Play]

21. Looks like the new server still has a few bugs

It appears that it's holding the option choice checked in the
OP and forcing it on the rest of the thread. Fascist software!


Steven P.

[emulatorloo]

6. kick and nominating n/t

[ET Awful]

7. One thing to keep in mind though . . . the :8090 is a port number and it

may be blocked by many firewalls.  8080 is default for HTTP if
I'm not mistaken, 8090 is not a common port, so many firewalls
may block it by default.  So, those viewing from work may be
SOL.

It's still better than stealing other folks bandwidth :)

[benburch]

11. Right... But the coral cache is becoming well-known.

And I expect more and more rule sets to have it enabled for
that address only.

[Jose Diablo]

12. Gonzales told us today it's ok to steal

just as long as it's for a good cause. So, don't feel so
guilty about stealing bandwidth. Everyone is doing it:
advertisers, the government, everyone. Go ahead.

[Renew Deal]

15. 80 is the default port.

Not 8080.

http://www.iana.org/assignments/port-numbers

http-alt 8080/tcp HTTP Alternate (see port 80)
http-alt 8080/udp HTTP Alternate (see port 80)

[ET Awful]

18. 8080 is the alternate HTTP port it would appear.

That's why I put the "if I'm not mistaken" disclaimer in :P

[hootinholler]

20. Http default is port 80..

80xx are common ports used for application servers. 

-Hoot

[Renew Deal]

14. Thanks

But you realize that people behind firewalls will probably not
be able to see them.  Either way, this is much needed. 
Thanks!  :yourock:

[EFerrari]

17. Thanks from the clueless, Ben!

:)

[bud E. holly]

22. Is there any way to

paste an image from your own hard drive into a post?

[chat_noir]

23. Image Shack - great photo resource

http://www.imageshack.us/

You can upload from your hard drive or an URL.  The post the
image here - choice of full size or thumbnail.


Another option is signing up for a free Photobucket account:

http://www.photobucket.com/

[bud E. holly]

24. Thank-you!

I knew there had to be a way, since I've seen a lot images
around here that had to be personal photos.
Many thanks:)