Re: Google and blogspot.com copyright infrigement



sobriquet wrote:
On 29 aug, 10:05, "Ryan Robbins" <redbird...@xxxxxxxxxxx> wrote:
"sobriquet" <dohduh...@xxxxxxxxx> wrote in message

news:ec407b27-cc6d-4de7-b519-fd84e39a8e70@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On 28 aug, 08:29, "Ryan Robbins" <redbird...@xxxxxxxxxxx> wrote:
"sobriquet" <dohduh...@xxxxxxxxx> wrote in message
news:c5fdb15e-32b5-4183-8d4e-d798dd7740a4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
However it was intended, in a way the public domain means what as been
published (as opposed
to things people keep to themselves). Once things have been published,
in practice there is very little
you can do to prevent people from reproducing and distributing such
creations.
Sure there is: sue them.
Sure, if you put a picture on your website you run some risk, but
share the picture on piratebay and the
risk becomes negligible. So if you like to exchange pictures and you
don't really care if the photographer objects to people exchanging
their pictures, there is not much a photographer can do in practice to
prevent this.
Sure there is: sue.
How would you prevent people from sharing and distributing a picture
you have published (either offline or online)?
You prevent it by going after those who do it.

If big corporations like adobe can't effectively prevent people from
sharing software packages on p2p
that costs thousands of dollars, how can you seriously expect to be
successful at that?

How would you even know
people are doing this, when they do it in semi-private p2p networks
(like bittorrent sites where you need an invitation from a member to
access the site)?
The same way the music and movie industries are cracking down on thieves who
use such systems.

The real criminals are the publishing and recording industry
themselves who think
they can impose their outdated business model by force if necessary,
regardless of technological
developments that render their services (reproducing and distributing
content) redundant.

There are so many ways people can share and exchange your pictures
once you've published them, so there is very little you can do about
that.
Continuing to say that isn't going to make it true.

Same goes for demonizing p2p users as thieves, which is the
perpetually repeated mantra of the IP mafia.

The only thing you can somewhat prevent is when people have a
website where they have your work on display, so you can obtain their
ip and harass their isp.
The ISP has nothing to do with it. You go after the Web site's owner.

It doesn't have to be on a website. But talk is cheap. Want to see if
you can actually
prevent me from publishing a picture that you have published before?
I'm very curious to see how effective you are in actually trying to
prevent people from sharing
and exchanging a picture (or something similar) that you have
published, where you think you
are able to dictate the terms of reproduction and distribution and
effectively able to prevent others
from sharing and exchanging your work in ways you do not approve of.


Will you sue people in countries like Rusia or China who share your
pictures, like in an archive of pictures harvested from various photo
websites, on bittorrent?
If need be.

Ok, so lets see if we can actually validate your claims and establish
you are actually able
to prevent people from sharing/exchanging something you have published
previously.
Show me one of your pictures and I will show you alternative places
where to obtain your picture
that have not been authorized by you and then you can show me how
effective copyright is in helping
you preventing such unauthorized sharing.

I think you miss Ryan's point. In creating a web site we are sharing our pictures with the world. What we are not doing is allowing other people to benefit from our efforts without paying us for it. I have no issue at all with you providing links to my photos to your friends or whoever you like.

I certainly will (as Ryan would too) sue you regardless of the cost to me, if you try to gain (financially or otherwise) from using my pictures. You simply cannot steal them. "Look but do not touch" I think the sign in the gallery reads.

Many people once-upon-a-time used to "hotlink" to my photos without my permission or (for a while) knowledge. This was seen by the court as illegally benefiting from the use of my Intellectual property and found to be in breach of Copyright.

You can't do that now because I've closed that hole but it does demonstrate that no photographer in the world can afford to let bloody minded idiots who think just because they object to not being able to have anything they see without payment, it's OK to just take them. It's not. No one is going to gain from the use of my photos without paying for it.

Steal my photos and you will pay considerably more than if you had asked and bought in the first place. I created them, I shared them and that wasn't enough for some people, they wanted to use them to make money without paying me for them. Not on now and never will be in the future.
.



Relevant Pages

  • Re: Google and blogspot.com copyright infrigement
    ... So if you like to exchange pictures and you ... How would you prevent people from sharing and distributing a picture ... prevent me from publishing a picture that you have published before? ... No one is going to gain from the use of my photos without paying ...
    (rec.photo.digital)
  • Re: picture no showing
    ... >>to review the proper way of publishing your site. ... >>Also read the article about compressing your pictures. ... >>HTH DavidF ... >>> for me that is what most of the website is. ...
    (microsoft.public.publisher.webdesign)
  • Re: picture no showing
    ... Did it occur to any of the bright folks at M$ that many folks are still stuck ... creates websites that work so slowly with dialup connections and which is not ... >to review the proper way of publishing your site. ... >Also read the article about compressing your pictures. ...
    (microsoft.public.publisher.webdesign)
  • Re: Extreme Porn - Hiding your Stash ?
    ... c++ etc, if all you need to hide is text its simple, pictures less so. ... The thing to watch with that is leaving your source code lying around. ... the bulk of the code is for an image viewer, and it would not be hard to bulk that out at all so the bits you want to hide are well hidden, if you don't comment it too well frankly it will never be found unless someone has a reasont o throw real resource at you. ... the idea of publishing a different version is interesting, depending how you do it hiding several images within one would be easy.. ...
    (uk.legal)
  • Re: Extreme Porn - Hiding your Stash ?
    ... c++ etc, if all you need to hide is text its simple, pictures less so. ... jpg inside an uncompressed tiff. ... with a lot else so your custom picture viewer normally shows tiff files, but given the right start up parameter shows the hidden jpg. ... the idea of publishing a different version is interesting, depending how you do it hiding several images within one would be easy.. ...
    (uk.legal)