Activity Pub vs. Web Frameworks
I think there is an simple solution to this problem. It does require some changes, but they seem to be pretty straightforward:<p>- When installing any app, user must always specify an arbitrary prefix. It is applied to all pages (and resources) except toplevel one. So you never have &quot;hostname.com&#x2F;posts&#x2F;1234&quot;, instead it is &quot;hostname.com&#x2F;m1&#x2F;posts&#x2F;1234&quot;<p>- When switching to a new software, you use web spider&#x2F;export functionality to convert the entire old prefix to static files. Static files are fast, and you can easily keep 100000 of them on average computer (and if not, you can store them in sqlite or some immutable k-v store). You then expose the static versions, either directly or via some trivial app.<p>- New ActivityPub goes to different prefix, so new posts are &quot;hostname.com&#x2F;m2&#x2F;post&#x2F;1234&quot;<p>- The only thing that _might_ need redirects is users, to get following to work.. Those will need to be set up manually. But there are much fewer users than other objects, so this should be pretty doable.<p>----<p>Does this needs some changes to be feasible? yes. Is it easier than designing all-new scheme? Absolutely.