Event JSON
{
"id": "febe3fdcbb9acb95456340649b3da47d628ebfadb9c7d722deca8a9468d0af32",
"pubkey": "6d1a724332a4f8e634d81f856c38c0bb3506fa9af276729031aaa985371f583f",
"created_at": 1735776801,
"kind": 1,
"tags": [
[
"t",
"matrix"
],
[
"proxy",
"https://metroholografix.ca/@sb/113755868434566448",
"web"
],
[
"t",
"mastodon"
],
[
"proxy",
"https://metroholografix.ca/users/sb/statuses/113755868434566448",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://metroholografix.ca/users/sb/statuses/113755868434566448",
"pink.momostr"
],
[
"-"
]
],
"content": "I wonder if it's possible to put a #mastodon instance behind a subdomain like mastodon.mydomain.com while the instance THINKS it is behind mydomain.com by re-routing requests for .well-known to the subdomain.\n\nThe reason for this would be so users could have @myUser@mydomain.com instead of @myUser@mastodon.mydomain.com, leaving mydomain.com free for a landing page or something else.\n\nYou can do this with #matrix, as explained here:\n\nhttps://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/docs/configuring-well-known.md",
"sig": "22e0ca8496932cc837f0f7518122f17f75c954fc0d2b1174f65e97726127038db1377adf4ab6e09baad20629941ac5e4ffba2f848a6ee55c92124d2bcfb56fb6"
}