@[email protected]

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

For example, if Public Broadcasters worldwide federate highres https://www.publicmediaalliance.org/public-broadcasters-create-public-spaces-incubator/ to millions, it would be nice that it shows in any client as they give you the bandwith in this example.

@[email protected]
#photography #fediverse

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.

I stop here ;)

@[email protected] :fediverse:

💖