silverpill@silverpill@mitra.social: @steve @benpate Bring Your Own Domain is when you use your own domain for IDs/WebFinger while someone else hosts an instance (software). This means an instance will have more than one domain attached to it.<br><br>>I've brought my own domain to my self-hosted Mastodon server instance, but that doesn't make it an implementation (or instance) with multi-tenant capability.<br><br>Yes, it's your instance and your domain. No "multi".

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @silverpill@mitra.social
Steve Bate@steve@social.technoetic.com (2026-04-24 21:53:17)
@silverpill @benpate I don't understand your point. Can you share your definition of "BYOD"? As we've discussed previously, I've brought my own domain to my self-hosted Mastodon server instance, but that doesn't make it an implementation (or instance) with multi-tenant capability.
---Reply---
silverpill@silverpill@mitra.social (2026-04-24 22:21:00)
@steve @benpate Bring Your Own Domain is when you use your own domain for IDs/WebFinger while someone else hosts an instance (software). This means an instance will have more than one domain attached to it.

>I've brought my own domain to my self-hosted Mastodon server instance, but that doesn't make it an implementation (or instance) with multi-tenant capability.

Yes, it's your instance and your domain. No "multi".


---Replies---

Steve Bate@steve@social.technoetic.com (2026-04-24 23:18:10)
@silverpill @benpate For this specific BYODomain use case, the WebFinger service is not the host for  any AP tenants and their associated users/actors. Therefore, it's not related to the multitenancy topic. It's more like a fediHandle-to-URI "redirect". In the related concepts discussion, the FEP is referring to BYODomain in the context of ActivityPub actor ids.