Updated the web site again to make it more man-ish. https://mkws.sh/

@adi@twtxt.net Looks good :) I will give mkws a go soon

@adi@twtxt.net It will be a basic social profile site similar to examples listed on mkws, and with at least a yarn pod :)

I’m a dummy, so I might need some help when I get around to it!

@prologic@twtxt.net @movq How can you specify your handle? Do other sites recognise it depending where the twtxt.txt is located?

e.g. Can I host a pod publicly at yarn.domain.tld but have the yarn handle just as
@username@domain.tld instead of @username@yarn.domain.tld

I mean, from the perspective of everyone else.
I realise the profile will still be viewable at yarn.domain.tld/user/username

@prologic@twtxt.net So it works for @lyse@lyse.isobeef.org and @movq because they are just hosting a twtxt file and not a pod? They can still have landing page for their website and have their handle at the domain.tld level this way.

It’s not a big issue for me, was just wondering if it were possible to make use of a .well-known in nginx.

@lyse@lyse.isobeef.org @prologic@twtxt.net For example I have currently running a Matrix server here https://ix.social/ with the following

`server {

    server_name ix.social;
...
    location /.well-known/matrix/server {
            return 200 '{ "m.server": "syn.ix.social:443"}';
...
    }
    location /.well-known/matrix/client {
            return 200 '{"m.homeserver": {"base_url": "https://syn.ix.social:443"}}';
    	...`

This allows the user handle to be username@ix.social instead of username@syn.ix.social where Synapse is running.