Closed kikuomax closed 1 year ago
Mastodon's user endpoint supports both application/activity+json
and text/html
MIME types, though, it is difficult for API Gateway to efficiently implement it. I do not think we have to provide a profile page from the same endpoint as the API. I am thinking to serve profile pages under something like /viewer/users/{user-id}
.
Maybe we should to associate the profile page with the WebFinger output.
Maybe we should to associate the profile page with the WebFinger output.
We can use http://webfinger.net/rel/#profile-page
for rel
like:
{
"rel": "http://webfinger.net/rel/profile-page",
"type": "text/html",
"href": "https://mumble.codemonger.io/viewer/users/kemoto"
},
Thanks to cdk-qwik-bundle
, we can bundle a Qwik app in a CDK stack.
If we can view a profile page as an HTML page, it will make invitation easier.