-
• #2
Why not?
-
• #3
VB steals some of your soul every time this happens..
-
• #4
Why not?
i find it irritating when sites do this because i just wanted to see the image, not the content it is in, and plus the image wasn't even hosted on lfgss, so hotlinking it wouldn't steal any bandwidth.
its your site though.
-
• #5
http://www.evanscycles.com/product_image/image/5c5/7f7/0f6/29567/product_page/campagnolo-veloce-bottom-bracket.jpg
right click show image?
and if it goes to a page like that it'll usually come up in its max resolution anyway, like it did. -
• #6
I'm going to start a facebook group about this link-stealing..
The people have a right to KNOW!!!!
-
• #7
i find it irritating when sites do this because i just wanted to see the image, not the content it is in, and plus the image wasn't even hosted on lfgss, so hotlinking it wouldn't steal any bandwidth.
its your site though.
When you click the view by default you see a frame at the top showing the thumbnail, and a frame at the bottom showing them image in context... which of course is that web page that it appears on... so it does indeed load a whole page.
I don't regard bandwidth use as stealing. Stealing requires depriving someone of some property, and bandwidth is not property... I still have bandwidth, so it's not theft.
What I do have in place is a framebusting script... so why would I want to do that? Because I'd already seen a fair amount of places ages ago that took the "view post" page and embedded it in their site. An analysis at the time suggested that they were doing this for silly reasons... basically to increase their search engine standing and at the same time look like they had content on their site. It was silly, but as I didn't want a spammer benefiting from creating a cost (server session) for me, I add the script.
The script simply says: If someone calls this site in a frameset... break the frameset.
It works against Facebook wrapping external sites, it works against Digg wrapping external sites, and it works against Google wrapping external sites... it works everywhere that someone wraps the site with content.
It's not about bandwidth theft which is a silly notion... it's about ensuring that the content on this site wasn't being used by spammers, and later when Facebook started their external site wrappers I was pleased it also stopped that rubbish.
Of course, if you don't like this argument, then try this one: I changed it years ago to spite you personally. I knew you'd come here years later, and so I purposefully did it to piss you off.
Now, which of those sounds more likely?
-
• #8
hehe, i'm not pissed off, just mildly irritated that my usual routine of clicking "see full size image" was disrupted. good reasons.
/thread
-
• #9
Josh dear, you're easily offended by everything!
-
• #10
Beware the Soul Stealer!!!!
-
• #11
same thing happens when you use google images to look for porn and it redirects you to a different site
..ive been told
-
• #12
Josh dear, you're easily offended by everything!
what else?!
-
• #13
What I do have in place is a framebusting script... so why would I want to do that? Because I'd already seen a fair amount of places ages ago that took the "view post" page and embedded it in their site. An analysis at the time suggested that they were doing this for silly reasons... basically to increase their search engine standing and at the same time look like they had content on their site. It was silly, but as I didn't want a spammer benefiting from creating a cost (server session) for me, I add the script.
The script simply says: If someone calls this site in a frameset... break the frameset.
It works against Facebook wrapping external sites, it works against Digg wrapping external sites, and it works against Google wrapping external sites... it works everywhere that someone wraps the site with content.
Heh, I like that a lot. DIE FRAMES!!! >:<
googling for a pic of a campagnolo bb tool i was on this link
seeing the lfgss pic (second row, far right) i clicked it, and instead of doing the google frame thing it just takes me straight to the thread its in.
why?