Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[penguinofhonor]

this is a toddler singing a beatles song

[Dutchling]

this is a toddler singing a beatles song

ohfuckyes

[JoshuaFH]

I'm a little late here, but me and Hipster Girl had a good second date. We had dinner and drove around a bit, though when we get back to her place things got a bit hot and heavy. We tumbled around in her backyard for about an hour just kissing and holding eachother, unfortunately I had to cut our time together short when I had to go to work, as I work night shifts, though I cut it to the last second to maximize our time. I'm just glad that nobody questioned why my nice business casual pants were covered in dirt and grass stains.

We're having our third date Thursday

[Xantalos]

Spoiler (click to show/hide)

[Aklyon]

Spoiler (click to show/hide)

Y'need to find a different image host. Unless anti-hotlinking pictures is a happy?

[Xantalos]

Works for me.
?

[Aklyon]

Works for me.
?

Because its cached for you, since you saw it already.

[Xantalos]

Works for me.
?

Because its cached for you, since you saw it already.

Huh. It was supposed to be Quagmire.

[Devling]

this is a toddler singing a beatles song

ohfuckyes

Your a little to happy about that dutchling... 

[misko27]

Works for me.
?

Because its cached for you, since you saw it already.

What is this magic. But wait, when I post images onto this site, I just copy and paste. Why does that seem to work?

[alway]

Works for me.
?

Because its cached for you, since you saw it already.

What is this magic. But wait, when I post images onto this site, I just copy and paste. Why does that seem to work?

The basics:
When you go to a web page, you tell the site's server "give me this document." That document is the html for the page. From there, your browser parses the html. It uses what it finds to figure out what else it needs. Those other things may be on the server, or they may be on another server. When asking for those other things, it tells the server it is asking where the resource was originally being called from, as per this specification. Usually, a server doesn't care, and just serves the information back, be it images, videos, CSS or scripts.

So, if you they copy the image URL directly, then post the image elsewhere, you are saying "Server A has the web page being accessed. Server B has the image being accessed." That's hotlinking. So you then have someone access the web page on Server A. Their browser then looks at the page, and figures out it needs the image on Server B. Well, in some cases, Server B doesn't like when people use their bandwidth for running someone else's site's images. And so instead of ignoring the referrer, it looks at the referrer, says "this isn't me or anyone I host images for" and so returns incorrect content; an image telling you not to hotlink.

The cache is also something which comes into play. If you visit Server B's website, on which the correct image was stored, that image is downloaded and stored in your browser's cache. When you then go to Server A's website, it skips the step of asking Server B for the image, and instead uses the cached version; saving both time and bandwidth. So as a result, the original hotlinker sees the original image, while anyone else sees the anti-hotlinking message.

[Mego]

Works for me.
?

Because its cached for you, since you saw it already.

What is this magic. But wait, when I post images onto this site, I just copy and paste. Why does that seem to work?

The basics:
When you go to a web page, you tell the site's server "give me this document." That document is the html for the page. From there, your browser parses the html. It uses what it finds to figure out what else it needs. Those other things may be on the server, or they may be on another server. When asking for those other things, it tells the server it is asking where the resource was originally being called from, as per this specification. Usually, a server doesn't care, and just serves the information back, be it images, videos, CSS or scripts.

So, if you they copy the image URL directly, then post the image elsewhere, you are saying "Server A has the web page being accessed. Server B has the image being accessed." That's hotlinking. So you then have someone access the web page on Server A. Their browser then looks at the page, and figures out it needs the image on Server B. Well, in some cases, Server B doesn't like when people use their bandwidth for running someone else's site's images. And so instead of ignoring the referrer, it looks at the referrer, says "this isn't me or anyone I host images for" and so returns incorrect content; an image telling you not to hotlink.

The cache is also something which comes into play. If you visit Server B's website, on which the correct image was stored, that image is downloaded and stored in your browser's cache. When you then go to Server A's website, it skips the step of asking Server B for the image, and instead uses the cached version; saving both time and bandwidth. So as a result, the original hotlinker sees the original image, while anyone else sees the anti-hotlinking message.

Spoiler: tl;dr (click to show/hide)

[Mr Space Cat]

So I picked up some baoding balls at a local mall after a friend recommended them for anything from relieving stress to exercising hand dexterity for tasks like piano or guitar playing.

These things are awesome. Meditating while listening to some ambiance while also twirling the baoding balls inhand is remarkably relaxing. I actually feel positive afterwards, which is nice considering the generally crummy, depressing days I've had lately.

[Xantalos]

Without clicking the link I know exactly what those are.
Sweet.

[Scelly9]

It's 2 AM, I'm blasting dubstep, pop, and mildly shitty music, I just built a capacitor and copper wire bracelet, and I'm now working on a copper wire spider web for a corner of the ceiling. This is absolutely amazingly fun.