Republish treaties for suggested apps

[jamesacklin]

Since our suggested apps are hardcoded, we may end up suggesting apps whose developers are offline or slow to connect. To improve first time user experience, we should republish featured treaties on reliable, Tlon-owned infrastructure.

For discussion: Is there anything else we’d benefit from republishing? Other popular apps?

[jamesacklin]

Food for thought: we may want to add an endpoint to docket to surface the upstream ship in desk.ship so it doesn't appear as though Tlon is actively developing any of these apps.

[arthyn]

To help the ecosystem and also make it easier on ourselves, we should have an agent which simply mirrors any app identifier given to it through a poke, something like [%mirror [~paldev %pals]]. This would then install the app from that publisher and republish it under its own name. We should potentially only accept pokes from the publisher src themselves as a security precaution, and we could also have a "rescind" type poke which also lets them take down anything mirrored so that they can control it. Would be a very simple agent, likely even stateless since all the state would really be in clay/kiln.

We may want to have some ability to manually curate so that people don't try to post mimics, because if someone posts a "pals" from their own ship, both would show up when the mirror is searched in landscape. Could also end up being a way for us to become a main curator for %portal.

Eventually this could even mirror other things...