this post was submitted on 18 Oct 2025
13 points (64.4% liked)
Lemmy
14010 readers
31 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It worked in Boost, but on Lemmy UI it doesn't linkify the whole thing
You would think markdown would work, but no, these somehow have the same issue:
https://piefed.social/c/lemmy@lemmy.ml/p/1384152/piefed-finally-fixes-lemmys-ugly-post-urls
https://piefed.social/c/lemmy@lemmy.ml/p/1384152/piefed-finally-fixes-lemmys-ugly-post-urls
Ok we're now generating links like this instead https://piefed.social/c/politics/p/1385905/will-the-supreme-court-hand-government-contractors-blanket-immunity
That does work! What about if it's a remote community? Does it just use the post ID number to determine what instance it's actually from?
The only part of the url that actually does anything is p/1385905 which functions the same way piefed.social/post/1385905 does. So that /c/politics bit has no effect on which post is displayed and it could be any string of gibberish. There are communities called 'politics' on many instances and this url scheme doesn't differentiate between them, but I'm ok with that.
I think that's pretty standard for URL slugs
Oh, interesting. I think having a '@' in the url is going to be a problem for a lot of different software. I'll remove that part.
Maybe the @ could be replaced by "at", just for legibility and transparency? Of course, there's always URL escapes, but that's for clients to do