#photography note (a few people asked): One of the reasons I include a flickr link to most of the photos I post here is so you can download the full res version easily (for printing, etc).
#photography note (a few people asked): One of the reasons I include a flickr link to most of the photos I post here is so you can download the full res version easily (for printing, etc).
Another reason is that clarifies the CC license on most of my photos. For non-commercial straight up use, such as illustrating a personal web page, just attribute it or link to the flickr page; no need to ask or wait for permission (though it's always nice to let me know).
Yep, you identified one of the fails of most fedi-softwares.
ALL of this is supported by the underlying #ActivityPub protocol:
The image property can have multiple url with width and size.
If nothing comes with rel="" we assume the largest to be fullsize
All licences can be embedde via rel="" but it would even be enough to Questionfor the well known licenses and put it in attributedTo as you described with flickr.
For Pros any client could read the IPTC or AdobeXMP caption and use it as default alt.
@[email protected] I'm not sure what you're suggesting. I post a lower resolution version (to not clobber my instance), and a link to the full version, which contains licensing information. That seems OK.
I am suggesting any dev to become ActivityPub conformant.
The problem is if the software receives an image with multiple urls, some can't deal with it, some show the first image.
This is important to many upcoming projects as described yesterday at https://berlinfedi.day/ or in the Key Talk at Public Spaces or in the book (pinned) and Talks at the official Confs https://redaktor.me/#home