My brain is currently entirely into steemd and SDS development, as I want to finally finish this version over the next few weeks. I guess I would still tend more to a complete/clean solution (adding a community field in the json_metadata) instead of a workaround, but I need to give it more thoughts when I find some more time for this...
RE: Communities vs. Blogs
You are viewing a single comment's thread from:
Communities vs. Blogs
No problem, there's no rush - I will test if the idea's feasible.
I don't think this idea is a work around. It's essentially returning the URL back to how it was before communities existed - where the first tag defines the internal (and therefore external) link.
Instead of the internal link being:
/(hive-xxxxxx)/(username)/(permlink)
It's
/(1st-tag)/(username)/(permlink)
If the community makes more sense, it could probably be:
/(communityName)/(username)/(permlink)
without too much effort.
It feels like a fairly elegant and straightforward solution.
A question for me is what happens to the SEO value of these posts if a community decides to change name. Which makes my current preference using the 1st tag (non hive-xxxx).
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
@remlaps
This works:
This is the feeds code.
Instead of always using the category, if it starts with 'hive-xxxxxx', it replaces this with the 1st tag.
Returning Steemit to the old SEO URL value in 4 new and 1 edited lines of code (+ 1 comment + 3 empty lines for readability).
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit