Live data from Hacker News

Show HN: I made a site to catalogue 10,000 CC0-licensed stock photos

finda.photo

61–65 of 65 posts

Re: Show HN: I made a site to catalogue 10,000 CC0-licensed stock photos

#61
post #43

Earlier quoted context omitted.

One of the challenges I have with attribution generally--and, to be clear, I try to be very careful with attribution on any CC, etc. photos that I use--is that the attribution is usually detached from the photo. (It may be stored in the metadata--or not.) So, even though I make a point of cutting & pasting the flickr links when I'm putting together a presentation, it's very easy for the attribution text and the photo…

There are fields within the JPEG file itself for this information, called IPTC fields. I know they can be read with photo-specific software like Photo Mechanic or Photoshop, but they seem incredibly under-used by the Internet in general. They're perfect for a use case like persistent attribution, but few image software services seem to know about or expose them.

We're (Creative Commons) writing something up about this right now.

Re: Show HN: I made a site to catalogue 10,000 CC0-licensed stock photos

#63

I like to think I am very conscious of copyright. I might not always adhere to it in my person life (who can claim they do these days?!) but professionally, everything is done strictly legitimately. With that in mind... Am I the only person who is slightly uncomfortable with the phrasing around PD and CC0? With other copyright licenses there is somebody there is saying they own something. I'm particularly uncomfortab…

If you look underneath each photo, there's a link back to each original page, as well as a link to the photographer's URL of choice (depending on the source this might be their profile on Unsplash, or their own website).

When I posted this comment the source link was just the top level page on (eg) Unsplash, not the profile of the user there.

Re: Show HN: I made a site to catalogue 10,000 CC0-licensed stock photos

#64

Earlier quoted context omitted.

If you look underneath each photo, there's a link back to each original page, as well as a link to the photographer's URL of choice (depending on the source this might be their profile on Unsplash, or their own website).

When I posted this comment the source link was just the top level page on (eg) Unsplash, not the profile of the user there.

Do you remember which image you're referring to? I haven't changed either the image data or the site code since your comment, so I'm curious to know which one it is and if I can update it.

Re: Show HN: I made a site to catalogue 10,000 CC0-licensed stock photos

#65

Earlier quoted context omitted.

There are fields within the JPEG file itself for this information, called IPTC fields. I know they can be read with photo-specific software like Photo Mechanic or Photoshop, but they seem incredibly under-used by the Internet in general. They're perfect for a use case like persistent attribution, but few image software services seem to know about or expose them.

I agree these are under-used but they face the same issues as the other methods like putting the data in text near the image on a web page or presentation slide. These fields, same as all Exif metadata, can be overwritten or removed by anyone with access to the file. The data can be faked by someone intending to deceive, or it could disappear when posted to big sites like Facebook or Twitter who routinely remove Exif…

The data can be faked or deleted within IPTC fields, of course.

What IPTC fields have over the typical ways of handling attribution is that they are not left behind when the image file is copied--so they should be more resistant to accidental removal of attribution metadata.

On most websites, the attribution is a line of text that is displayed next to the image. Anyone copying the image, who wishes to preserve attribution, must also separately copy the attribution text. Then they need a way to store that text, and keep it associated with the image. Not easy, actually!

> Once the photo metadata is gone, it is too easy for others to claim it is an 'orphan work' and avoid liability under copyright law.

You cannot avoid liability this way. Under the law, it is the responsibility of the person using an image to know that they have the right to use it. Just claiming "I thought it was orphaned" does not work if you are being sued by the actual image rightsholder.

> I use and rely on Exif tags a lot but they are fragile and you cannot rely on them staying embedded with your images once they hit the web.

Yes, this is my point! They're fragile because web services don't preserve them--but theoretically they could.

The cynical side of me thinks that a lot of web services don't want to know all the rights data for the media they carry. Ignoring rights gets them more traffic and engagement, and under the relevant law (the DMCA), they are allowed to. All they have to do is remove infringing images when the rights holder requests it.

Post reply on HN