how will the fix work?

cool, i’m glad to hear you’re amenable to this change!

maybe a good reason for me to finally start learning rust :)

(i’m not going to in the immediate future, however, so if someone else wants to do it please do!)

You memorize lemmy post IDs?! They’re currently six digits here, and I can’t imagine why you would need to memorize one. It is sort of nice that they can be communicated verbally, though I doubt that actually happens very often. But, in any case, my proposal still allows for that because the title part can always still be omitted when entering the URL. Do you ever receive lemmy URLs in chat? I do, as I imagine many people do, and that is the case I would like to see improved.

I think the only URLs containing data_type that I’ve seen were 404 URLs from a bug in the inbox, sometimes triggered by reloading immediately after clicking “mark all as read”.

I like the current model.

I’d rather have the URLs be self-describing.

Automatically formatting issue numbers on sites like github is nice, but I think doing it with freeform titles mid sentence like that would be jarring more often than not.

https://www.cryptovoxels.com/ might be the closest thing today, but, it relies on the ethereum blockchain and is very NFT oriented.

You can enter their virtual world without a login, in a web browser, without using any cryptocurrency, however (i did it once).

I don’t know much about it but my understanding is that the long-term game state (eg, who has what items, and what virtual real estate (unreal estate?)) is all kept on-chain, which is rather absurdly expensive, but the minute-to-minute state must be just on their centralized server. However, I think that (in theory at least) if the people operating the centralized infrastructure disappeared today that others could run gateways to the same gameworld state tomorrow. Maybe.

My investment advice is to not invest in this.

yeah, that seems reasonable.

That is a nice URL, but it omits any database ID, which means that you couldn’t have two posts with the same title. Also, you would need a more expensive database lookup to serve the URL. For wikis and blogs, I think using the post title as the unique key makes sense, but I don’t think that actually makes sense for lemmy.

On github I see @nutomic@lemmy.ml said “If we make this change, we should do it before releasing federation. After that it will get much harder to change the URLs.” - I haven’t looked closely at the data model but I’m optimistic that a graceful upgrade to a better URL format should not be a problem. Eg, this post is currently https://lemmy.ml/post/152773 and in my ideal world in the future that old-format URL would continue working but become a redirect to a canonical URL such as https://lemmy.ml/post/152773/lemmy/Lemmy_URLs_should_be_human_meaningful or https://lemmy.ml/c/lemmy/152773/Lemmy_URLs_should_be_human_meaningful

Really the /c/ and/or /post/ parts shouldn’t be necessary; could just be https://lemmy.ml/lemmy/152773/Lemmy_URLs_should_be_human_meaningful

Human readable URLs! The URL is a very important part of a site’s user interface, and lemmy’s URLs currently just have a post number - there is no title, or even the name of the sub-community. Compare this to reddit: when I paste a friend a reddit URL in chat they get two hints about what it is about: the subreddit name, and the post’s title, both embedded in the URL itself. This lets them decide if they want to click it now, or later, or never, or to recognize if they’ve already seen it. Lemmy links should be like that.