@carlnewton
Awesome. It seems that you and @benpate and me are basically working on the same things.
I would be more than happy to meet in an audio call. Our funded menschys project allowed me to work on fedigeo fulltime the past weeks. It might help anyone.
Also if we could establish a standard for federated geohash Collections which is our base for federated regions, geocoding and routing (federated routing uses openroute humanitarian/collaborative plan in the beginning). Would be happy to tell you more.
Carl FYI;
am also elected Policy Lead of Social CG, worked much towards consulting EU for DMA/DSA and co-org the official ActivityPub Conf https://conf.tube/c/apconf/_channel/videos
For mastodon you need to delete anything after the last '/' and put the
"https://lemmy.world/post/31535735/" in the search box and you get the fedi-object instead of the url. Then you can share that. Not saying this is intended, just saying, it works :)
then delete the last path segment of the lemmy post.
The canonical url for your example is https://lemmy.world/post/31535735
and that works.
I am not sure what the "/17725147" is good for.
It might either has to do with redirects or lemmys Content-Negotiation.
They should figure out.
@pepper0
For mastodon, you make em visible by putting the whole url in the mastodon search box and enter, tried with https://lemmy.ca/post/50437467 [from posted lemmy group]
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
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.
@elettrona
yes, only Pros, see the ActivityPub Spec. which has exactly the same "addressing" fileds like mail …
E.g. https://www.w3.org/TR/activitypub/#client-addressing
@selfhosted
@carlnewton
Awesome. It seems that you and @benpate and me are basically working on the same things.
I would be more than happy to meet in an audio call. Our funded menschys project allowed me to work on fedigeo fulltime the past weeks. It might help anyone.
Also if we could establish a standard for federated geohash Collections which is our base for federated regions, geocoding and routing (federated routing uses openroute humanitarian/collaborative plan in the beginning). Would be happy to tell you more.
Carl FYI;
am also elected Policy Lead of Social CG, worked much towards consulting EU for DMA/DSA and co-org the official ActivityPub Conf https://conf.tube/c/apconf/_channel/videos
@pepper0 @aussocialadmin @lemmy_ca_support
summing up:
Lemmy posts have different URLs to the same Object.
Your example was
https://lemmy.world/post/31535735/17725147
which is
https://lemmy.world/post/31535735/
For mastodon you need to delete anything after the last '/' and put the
"https://lemmy.world/post/31535735/" in the search box and you get the fedi-object instead of the url. Then you can share that. Not saying this is intended, just saying, it works :)
@pepper0 @aussocialadmin @lemmy_ca_support
then delete the last path segment of the lemmy post.
The canonical url for your example is
https://lemmy.world/post/31535735
and that works.
I am not sure what the "/17725147" is good for.
It might either has to do with redirects or lemmys Content-Negotiation.
They should figure out.
@pepper0
For mastodon, you make em visible by putting the whole url in the mastodon search box and enter, tried with https://lemmy.ca/post/50437467 [from posted lemmy group]
@aussocialadmin @admin @lemmy_ca_support
@mattblaze@federate.social
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.
@mattblaze@federate.social
#photography #fediverse
Yep, you identified one of the fails of most fedi-softwares.
ALL of this is supported by the underlying #ActivityPub protocol:
The
imageproperty can have multipleurlwith 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 inattributedToas you described with flickr.For Pros any client could read the IPTC or AdobeXMP caption and use it as default alt.
I stop here ;)
@BeAware@social.beaware.live :fediverse:
💖