Post B5S5ipj7zIC2ltcYZU by mczachurski@mastodon.social
(DIR) More posts by mczachurski@mastodon.social
(DIR) Post #B5ORh8zKp9HmI1xfrE by mczachurski@mastodon.social
1 likes, 1 repeats
I’m looking for input from ActivityPub experts. Vernissage supports reading and exchanging EXIF metadata from photos (currently visible only in supporting systems). Would it be reasonable (if explicitly enabled by the user) to automatically embed this metadata as HTML in outgoing ActivityPub posts, so other platforms could render it within the status content? This could eliminate the need for manual copying. Curious whether this is considered a good practice or an anti-pattern. 🤔
(DIR) Post #B5ORh9Bk51D6uVlaCG by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski I am more of a fan of the Activity Extension (your FEP). Adding meta data to HTML might be a noisy and with JSON meta, every platform can decide if and how itt wants to show them.
(DIR) Post #B5OT2wNOUmJDV2Ak6a by mczachurski@mastodon.social
0 likes, 0 repeats
@pfefferle Yes, but I don’t think Mastodon, Fredrica, or GoToSocial will ever do that. 🥺
(DIR) Post #B5Q3l0HP8QVDr5dmng by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski which is fine! But if you add these without the possibility for readers to opt out, you have to expect complains!
(DIR) Post #B5Q3xwhhk04gWu778i by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski I implemented the FEP btw ☺️
(DIR) Post #B5QG98ISB8gn7SP5Iu by mczachurski@mastodon.social
0 likes, 0 repeats
@pfefferle Could you send a link to a photo from Vernissage that’s visible in WordPress? I’d really like to see what it looks like 🤩
(DIR) Post #B5QSgKCW8fDd2uDjwe by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski I started with publishing. The reader is not quite ready yet.https://github.com/Automattic/wordpress-activitypub/pull/2751
(DIR) Post #B5QU5aeaCmCDGaxXmq by mczachurski@mastodon.social
0 likes, 0 repeats
@pfefferle I understand. I’ll implement FEP once it gets approved. For now, I’m only using the extension. It would be great if it gets approved soon - then more platforms might adopt it.
(DIR) Post #B5RpBYa17VVSlhTCYi by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski I think implementing it is part of the process. The more implementers, the easier to discuss possible glitches and improve the spec. I am not even sure if a FEP will be published as final without any known implementations… any suggestions @silverpill ?
(DIR) Post #B5S5ipj7zIC2ltcYZU by mczachurski@mastodon.social
0 likes, 0 repeats
@pfefferle @silverpill I understand your point, but it feels unusual to implement something that is not yet approved - especially in a system that already works and exchanges this information. Any change would require me to release new versions and ensure backward compatibility each time, which is quite a lot of work. I would prefer to wait for a finalized FEP and implement something stable and clearly justified.
(DIR) Post #B5UG0oS0rH2tsskORc by silverpill@mitra.social
0 likes, 0 repeats
@mczachurski @pfefferle FEP-ee3a was approved. It is now stored in the FEP repository with the DRAFT status, you can update it with another PR if you want.At some point it should be finalized, but usually this happens after an author incorporates feedback from a discussion thread and convinces at least one other developer to implement the proposal.
(DIR) Post #B5UG0omvbVmAvkX62q by mczachurski@mastodon.social
0 likes, 0 repeats
@silverpill Okay, I understand. I implemented this FEP, and it has already been deployed to production.I also added a section to the FEP with information about the services that have implemented it so far - currently only Vernissage. It would be great if you could also add your WordPress implementation there, @pfefferle.Thanks for the information. PR: https://codeberg.org/fediverse/fep/pulls/826
(DIR) Post #B5UG0oyyshPvX8Aipc by pfefferle@mastodon.social
0 likes, 0 repeats
@mczachurski @silverpill https://codeberg.org/fediverse/fep/pulls/827/ ✅