business card
business card
For example reading here: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial
I wasn't considering some scenarios, like multiple accounts for a single domain (See 'How can I set and manage multiple subdomain handles?' in the link above)
For example reading here: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial
I wasn't considering some scenarios, like multiple accounts for a single domain (See 'How can I set and manage multiple subdomain handles?' in the link above)
@nick@nick (Masto/Yarn style)
vs
nick.eapl.me and eapl.me (Bsky style)
I see, for example, that
yarn shows my account as eapl.me@eapl.me which looks 'weird' although it's not wrong since my domain and my nick are the same. Honestly I like more the Bsky approach as in https://bsky.app/profile/eapl.me for eapl.me, as when you look for https://eapl.me, it's my home page.Also, I didn't get it completely if you are also proposing a URL standard using subdomains, like https://nick.domain.tls. I only want to point out that these are more difficult to handle from shared hostings, so I'd prefer to also allow https://domain.tls/nick/
@nick@nick (Masto/Yarn style)
vs
nick.eapl.me and eapl.me (Bsky style)
I see, for example, that
yarn shows my account as eapl.me@eapl.me which looks 'weird' although it's not wrong since my domain and my nick are the same. Honestly I like more the Bsky approach as in https://bsky.app/profile/eapl.me for eapl.me, as when you look for https://eapl.me, it's my home page.Also, I didn't get it completely if you are also proposing a URL standard using subdomains, like https://nick.domain.tls. I only want to point out that these are more difficult to handle from shared hostings, so I'd prefer to also allow https://domain.tls/nick/
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
If NICK = DOMAIN then only show @DOMAINSo instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
If NICK = DOMAIN then only show @DOMAINSo instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
If NICK = DOMAIN then only show @DOMAINSo instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
If NICK = DOMAIN then only show @DOMAINSo instead of **@eapl.me@eapl.me** it will just be **@eapl.me**
And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I've implemented webfinger on my sever for a single user;)
nick@domain is preferred over just @nick in the first place. The twtxt world here is so small (and hopefully will always be) that duplicate nicks are just not an issue from my point of view. And even if there are several feeds with the same nicks, one probably does not follow both of them. Yes, there's the birthday paradox, but I'd guess we have a slightly larger nickname space than days in a year.
I agree on displaying a short
@nick.We could hover on the nick to see the full detail which could be
@nick@domain.tls or the full URLAlso it could be a display option in Preferences in case your account starts showing many collisions.
The disambiguation for collisions is the .txt URL and the nick inside it, right ?
I agree on displaying a short
@nick.We could hover on the nick to see the full detail which could be
@nick@domain.tls or the full URLAlso it could be a display option in Preferences in case your account starts showing many collisions.
The disambiguation for collisions is the .txt URL and the nick inside it, right ?
@nick@domain.tls I think Webfinger is the way to go. It has enough information to know where to find that nick's URL.@prologic does that webfinger fork made by darch work OK with yarn as it is now? (I've never used it, so I'm researching about it)
https://darch.dk/.well-known/webfinger/
@nick@domain.tls I think Webfinger is the way to go. It has enough information to know where to find that nick's URL.@prologic does that webfinger fork made by darch work OK with yarn as it is now? (I've never used it, so I'm researching about it)
https://darch.dk/.well-known/webfinger/
In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or " **nick** _(domain.tld)_ " could also work.
In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or " **nick** _(domain.tld)_ " could also work.
In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or " **nick** _(domain.tld)_ " could also work.
In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or " **nick** _(domain.tld)_ " could also work.