Idea for new nick/URL scheme for pods: nick.domain.tld #671

Right now the url to someone profile on a yarn pod is kinda ugly in my opinon: https://twtxt.net/user/darch/

I would like to suggest to create a subdomain for each user so the url will instead be: https://darch.twtxt.net/ and from this we will have these nicer urls: https://darch.twtxt.net/twtxt.txt and https://darch.twtxt.net/avatar.png

This will also fix the issue with two @-signs in the @nick@pod which I beleave can too easily be mistaken for an e-mail adresse.

I'm away it will break all the current URLs, but I belive this new URL scheme will make it easier to share links to your profile on print and with laymen.

Are you aware of https://twtxt.net/~darch ?

haha, no i was not. It's halfway there indeed, but it would still go after something that looks more clean and less techy. Alto it not easy to type a ~ on a danish keyboard. It's not even printed on any keys on my macbook, so for regular joes this is a big barrier...

The issue with what you're suggesting is that in order to do this you actually end up increasing the work a Pod Operator has to do to set this up. I don't like that ;/ -- I don't think any existing Pod Owner/Operator in the community would really like that either.

Changing URI schemes is also quite hard as it breaks hashes.

There's also a lot of work involved in supporting sub-domains as a "feature".

At an infrastructure level one could just have an instance per user, with their own sub-domain and we could make yarnd support single-user mode.

I'm not really sure what problem we're solving here?

Let me sleep on it :)

We used to have the syntax:

@user@domain

We should bring this back, and we will, see #631

Just thinking about this some more before I go to bed...

This will also fix the issue with two @-signs in the @nick@pod which I beleave can too easily be mistaken for an e-mail adresse.

I don't actually see this as a problem. What's to say that a multi-user pod operator doesn't also integrate yarnd with their email system? This would mean inf act every user of that pod would also get a valid email address too. No reason this can't happen -- We just chose to "not implement" out own to focus on one thing and do that well.

I'm away it will break all the current URLs, but I belive this new URL scheme will make it easier to share links to your profile on print and with laymen.

The way I see it is currently sharing twtxt.net/~prologic is actually super easy. And not that key is on the Mac keyboard (remember I use macOS!)

As I said in some comments above I think we need to bring back and formalize (for example) @prologic@twtxt.net and make this a first-class thing.

I never liked the dobble-@-syntax. and it also giving a wrong implession because you are missing part of the acctual url for the twtxt.txt-file:

@darch@twtxt.net =/ twtxt.net/darch - but: twtxt.net/user/darch that is a yarn-specific URL scheme.

With @darch.twtxt.net there is very little guesswork involved - the URL is the username as vice-versa.

The problem I want to solve is a matter of æstetics and usability.

A service like saved.io uses subdomain in a very dynatic way, when you can create a new list of bookmarks by just typing twtxt.saved.io in the adress bar.

I'm fully aware that this will break a lot of stuff, so maybe it only to be implemented for new pods.

A way to secure backward compabiliy would be to have nick.domain.tld just as a forward to domain.tld/user/nick

Threre is no ~ on a danish macbook keyboard.

I also have a vision that we could offer a complete system with both public twtxt feeds and email or suggest people to use delta.chat for private conversations and groupe chat.

I just wanted to see if this idea was something you would be up for considering:)

Threre is no ~ on a danish macbook keyboard.

Ahh my bad I wasn't aware of that 😅

I also have a vision that we could offer a complete system with both public twtxt feeds and email or suggest people to use delta.chat for private conversations and groupe chat.

I think this can happen but not righ tnow. At a later date when we're in a better position to "integrate" with other systems and platforms like Email for example.

I just wanted to see if this idea was something you would be up for considering:)

Sure all ideas are welcome, just have to go thorugh them to see if they pass the "sniff test" and whether we're going outside our "scope" too much 😉

You can rewrite the URL with the web server of your choice. There is no need to change the current URL scheme for that.

Closed via 085d3a9