You are viewing a single comment's thread from:
RE: Steem improvement proposal : Canonical links.
A great proposition. It is simple and manageable. And necessary to implement.
But ... hardcoding things is never a good solution in a long run. What we need is a resolver service. You would ask this service, call it a Steem DNS for links :) , with app and other parts of the link as parameters and get back the most recent valid concatenation. Then put this in the header of the html.
I know that this is an additional resource(s) that needs to be maintained and called but it would represent a (fairly) permanent solution. Calls could be cached, for example, to reduce the traffic ...
That would indeed be a good idea ! Although I kinda dislike it because it forces all the dapps to talk to one centralized service. Which is a shame to do when we have a decentralized blockchain.
We can make it decentralized.
A shared resource of apps, an API (in various languages) so that the rules are set and equal across the implementations.
Like this:
https://github.com/busyorg/steemscript/blob/master/apps.json
Lists of apps with names and rules. But you know this better than I do :)
After all, it is an agreement between the parties involved. Or you can put it in the blockchain core code ;)