He he he 😈 I got my first statically published blog to load! Still need to work on the inbox server and get post resolving wired up but I'm happy with the progress so far. @mauve@staticpub.mauve.moe

This is also being published on protocols on ipns://staticpub.mauve.moe/abo

One limitation is you can only one account per domain.

This is being published using and is part of our upcoming integration.

@mauve
can you @ an empty string? (while offsetting user into subdomain)

@mauve.staticpub.mauve.moe

Follow

@dym not sure. I would love that as an option though! The way mastodon and other fedi instances treat webfinger might vary accross the board. Hypothetically any username @staticpub.mauve.moe should resolve to the same thing

@mauve
ok, hold on, can you make a file with symbols ?:= in it on your server, or similar nginx rewrite rule to make

https://staticpub.mauve.moe/.well-known/webfinger?resource=acct:USER1@staticpub.mauve.moe // file webfinger?resource=acct:USER1@staticpub.mauve.moe and https://staticpub.mauve.moe/.well-known/webfinger?resource=acct:USER2@staticpub.mauve.moe // file webfinger?resource=acct:USER2@staticpub.mauve.moe

to have their own ["links"][0]["href"] pointing to
https://staticpub.mauve.moe/USER[1,2].jsonld

@dym that's probably possible with a custom gateway or http server. one limitation I'm dealing with however is publicly run Ipfs gateways which have very simple logic so I think the most I could do is convince them to adopt some new mime types. ideally I would like to make it possible to resolve an identity from any gateway.

another approach that I have been thinking about is that we could focus less on web finger and more linking directly to the profiles page

Sign in to participate in the conversation
Mauvestodon

Escape ship from centralized social media run by Mauve.