You are viewing a single comment's thread from:
RE: 👨💻 #Proposal-86: SEO Improvements
In the longer term, I think that entirely replacing the hive-###### in the direct link to the community with the community name or a piece of community-specific metadata is probably still better. I don't think that can be done in condenser, alone, though(?).
I'm not sure. It's possible that the back-end could still store the hive-xxxxxx as the community identifier, but the front end could create a friendly URL that could then be "parsed" to call the correct data from the database.
It feels very messy though. Options 2 and 3 are much simpler.
Shouldn't this be "the downside of option 2" with a fallback to option 3?
It should, thanks for highlighting. I've updated the post.
Another complexity with using community names... I'm not sure, but I don't think that they're guaranteed to be unique. Which means that posts from two different communities could wind up being labeled with the same string... Maybe not a problem, I guess, since there's not really a tree structure - but it's counterintuitive.
That's not a problem since that part of the URL doesn't impace what content gets loaded.
It would even make sense. If 2 communities are doing the same thing, it makes sense that the first hashtag is the same (which is essentially what we're discussing as an abstractoin).
Ideally, communities work together but we've seen with some Country based communities in particular, that there's a divide and they won't work together.
If you want the cats let me know and I come back.
🍀♥️
@ wakeupkitty
I've always preferred dogs 🐶
Hereby
🍀♥️
Baldr
Is he/she good with children?