Would Media captioning make a good FEP?

So there is much code written inbetween which could then help.
A main problem when developing all the @redaktor widgets were hearing impaired because the major browsers do not support WebVTT for the Audio Element which is sad.
So, for the as Audio type widget, we have an overlay of a video element doing WebVTT if there are any tracks.
There is a topic with screenshots (early stage) Seeking opinions on time-based content but now for time based “extra content”, it’s most easy is to supply WebVTT Metadata as ActivityPub markup to add time based ActivityPub content.

Then I wrote the image proxy and put it in a gist but just sent it to @datatitian for quick review cause it could be a simple plugin router for https://github.com/immers-space/activitypub-express and I want to prevent any bugs before …

Will let you know about progress …

[edit/addendum:]
Forgot to mention about the proxy (can send the gist link via DM), it is currently handling all Namespaces and Vocabulary in https://developer.adobe.com/xmp/docs/XMPNamespaces/
and converting it to ActivityStreams Vocab.
You can simply chain multiple image operations from sharp and /withMetadata
Then via content-negotiation and Accept-header outputs either the image with metadata embedded or plain json or ld+json

Privacy is important to me.
The thing should never be used by bots automatically creating ActivityPub objects.
It should be used by the Actor as an opt-in template for posting.
In any case the posting interface should proactively notify the Actor about missing captions or the minimal a11y needs and further guidelines.
In general, metadata should fall into 3 categories:

Critical Metadata – what should always be deleted …

  • EXIF Maker Notes
    they contain often encrypted very private and forensic data, like the temperature of the camera or the encrypted email/Account data where “encyrypted” is relative, the forementioned examples (temperature/email) are possible to read for a beginner after 2 days playing and other hacks are known by search engines :wink:

Metadata which was not produced by the author

  • EXIF
  • TIFF
    in my code, the users can opt-in but data is filtered and lands in the instrument property of ActivityStreams

Metadata which was produced by the author

  • IPTC
  • DC
  • photoshop
    [which is just a namespace to bridge IPTC/DC and photoshop or other apps (e.g. iView) specific values]