Friendly post urls
-
Rather than a format like piefed.social/post/long_number, posts how have a url that includes the community name and title in it.
This improves readability, helps people differentiate between multiple links in a list and is better for SEO.
The old style of url still works too and there may be occasions when you get taken to a url like https://piefed.social/post/1382987 but we'll be working to remove those over time.
-
Rather than a format like piefed.social/post/long_number, posts how have a url that includes the community name and title in it.
This improves readability, helps people differentiate between multiple links in a list and is better for SEO.
The old style of url still works too and there may be occasions when you get taken to a url like https://piefed.social/post/1382987 but we'll be working to remove those over time.
@rimu this is awesome! -
Rather than a format like piefed.social/post/long_number, posts how have a url that includes the community name and title in it.
This improves readability, helps people differentiate between multiple links in a list and is better for SEO.
The old style of url still works too and there may be occasions when you get taken to a url like https://piefed.social/post/1382987 but we'll be working to remove those over time.
@rimu It can be any community name and title though
E.g., https://piefed.social/c/anything/p/1382987/anything resolves to the same content as your original link.
That feels like a risk - you could give someone a URL that looks like it's for one community/title, but goes to a completely different one.
Trivial example - https://piefed.social/c/piefed_meta@piefed.social/p/1220635/friendly-post-urls - looks trustworthy, but is completely different. That could be NSFW content, and you won't know until you click.
It isn't NSFW, you can trust me.
Or can you...?
-
Rather than a format like piefed.social/post/long_number, posts how have a url that includes the community name and title in it.
This improves readability, helps people differentiate between multiple links in a list and is better for SEO.
The old style of url still works too and there may be occasions when you get taken to a url like https://piefed.social/post/1382987 but we'll be working to remove those over time.
Cool tweak!
-
@rimu It can be any community name and title though
E.g., https://piefed.social/c/anything/p/1382987/anything resolves to the same content as your original link.
That feels like a risk - you could give someone a URL that looks like it's for one community/title, but goes to a completely different one.
Trivial example - https://piefed.social/c/piefed_meta@piefed.social/p/1220635/friendly-post-urls - looks trustworthy, but is completely different. That could be NSFW content, and you won't know until you click.
It isn't NSFW, you can trust me.
Or can you...?
Yes, the /p/number bit is the only functional part of the url. I'll make it check for tampering!
-
Yes, the /p/number bit is the only functional part of the url. I'll make it check for tampering!
rimu@piefed.social for what it's worth, we had this discussion a decade ago too.
We ended up being very simplistic and not tying anything to anything else.
So posts are not tied to topics (theoretically you could have a post in multiple topics... we don't do that, but you can)
And topics aren't tied to categories (same deal, and we also don't have topics in multiple categories... yet!!, cross-posting will change that.
So when you have a direct url to a post it's just
/post/
. A friendly URL uses a post index, but we can do that because we order posts linearly. Piefed doesn't have that advantage unfortunately.