How does this work? How do you host pixelfed.domain.com and mastodon.domain.com together in the same domain, with queries for “@user@domain.com” to the webfinger host path?
I’m other words, how does the querying application know which resource it needs? How do you know that a pixelfed instance will get the pixelfed resource versus the mastodon resource?
I think what they mean is a service to provide the webfinger response in a customizable manner. I know for me right now, I’m just using wildcards in nginx to handle it for the ActivityPub path, but it’s not really ideal because it won’t work for other activitypub services as far as I can tell.
I’ve thought about doing this. It seems simple enough, though it would need a front end to be user friendly. I could build the rest api pretty quickly.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I’ve thought that if some dev created a webfinger reverse proxy they would be the hero of the fediverse.
Can you eli5?
I don’t think I understand what you mean.
What would the reverse proxy do in this situation?
I think what they mean is a service to provide the webfinger response in a customizable manner. I know for me right now, I’m just using wildcards in nginx to handle it for the ActivityPub path, but it’s not really ideal because it won’t work for other activitypub services as far as I can tell.
I’ve thought about doing this. It seems simple enough, though it would need a front end to be user friendly. I could build the rest api pretty quickly.