Hey fedifolks! I was hoping to get some bikeshedding feedback on a new #FEP we're working on at #DistributedPress.
tl;dr we want #ActivityPub objects to link to #P2P URLs for alternate ways to load them. Right now I'm debating between putting them in `alsoKnownAs` or into the `url` field. e.g. `"alsoKnownAs": ["ipns://staticpub.mauve.moe"]` for @mauve@staticpub.mauve.moe
I worry that field is already in use and that it could cause trouble. Would a new field name be better? Maybe `alternateURL`?
@mauve@mastodon.mauve.moe @mauve@staticpub.mauve.moe Maybe these addresses could be plainly considered as IRIs? Then it may even more make sense to assume them as plural, because that's what happens when resources are available via different transports and addressing schemes, and to have a list as type, using a fitting plural identifier: "iris": [ ].
Et voilà! Problem solved ;)
@mauve@mastodon.mauve.moe @mauve@staticpub.mauve.moe I'll now have to build a P2P network called *Iris*, obviously.
@silverpill These are great. I didn't know I could place anything but a string under URL. Setting it as alternate with the AP mime type seems like a good solution
@mauve@staticpub.mauve.moe In case anyone is interested, I've made a PR that adds an initial attempt using the `url` field with `rel=alternate`.
https://github.com/RangerMauve/staticpub.mauve.moe/pull/2/files