Investigate Clipboard Pickling APIs

[lidel]

Web Custom formats let websites read and write arbitrary unsanitized payloads using a standardized web custom format, as well as read and write a limited subset of OS-specific formats (for supporting legacy apps).

The name of the clipboard format is mangled by the browser in a standardized way to indicate that the content is from the web, which allows native applications to opt-in to accepting the unsanitized content.
– https://chromestatus.com/feature/5649558757441536

Use in IPFS

It opens an interesting option for passing bytes on the web

Depending on low level limitations and permissions, this might be something we can leverage for:

• signaling for things like exchanging SDP in WebRTC (Alternative to QR codes and ultrasound hacks)
• light transport for exchanging IPFS blocks across tabs and apps
• exchanging access tokens: IPFS Companion's access to Kubo RPC (if we add tokens), pinning services, maybe even user onboarding around UCAN use cases (extremely handwavey, just noting areas to explore)

References

• https://chromestatus.com/feature/5649558757441536
  • https://github.com/w3c/editing/blob/gh-pages/docs/clipboard-pickling/explainer.md#web-custom-formats-for-async-clipboard-api
  • https://docs.google.com/document/d/1afc45MQuwxEWgoUeJCO-sOWRSzs31V4JS-kKXJNMTXw/edit