You are viewing a single comment's thread from:
RE: Steem improvement proposal : Canonical links.
In my view, this is one of the fundamental issues that really needs resolving for 3rd party app success.
A standard that everyone (including and most importantly, steemit.com) needs to follow.
I think too, and with steem success growing we'll see more and more dapps hence why I think it' so important to remove this problem that slows down adoption.
great catch @howo, was going to say this needs to be in Steemit GitHub submission & an Utopia post but with all the comments below, looks like this will be worked out the with all the dev here
just letting you know I'm following you now
I like the utility of the
canonicalproperty.The
apptag is not particularly scaleable, and adds several brittle complexity obligations to all clients.I'd suggest we start with both a
canonicaland anapp_account(that is an account associated with only the app that assisted in creating the post).At some point in the future we can either:
app_accountto publish a configuration set for in a special tx; so that all clients can generate the correct urls by pulling the most recent tx for that app_account.If we get sufficient community support, and add in the concept of trusted app_accounts (with some additional complexity) any of the above would get the job done 'well enough'.
Oh, I agree this really does need to happen. For all our sakes.
Nice to meet you @jesta
You are the best steemians
I think so
I agree with your approach 110%.
It will only help improve efficiency on the chain as well as avoid potential duplicate content issues. There are many On-Page SEO issues Steem has, many of the most critical I have outlined here...
https://steemit.com/steemit/@sf2/9-things-steemit-can-do-to-improve-on-page-seo-for-all-users
The more we can improve these technical SEO and accessibility issues, the more adoption and awareness we will create for Steem and the community.
Everybody wins.
What is the fundamental issue?