When it comes to adding links to our posts that direct to other peoples content on the chain. Most of don't think about it, you open a new tab maybe, then you copy the link of the thing you want.
Some may drop this in markdown, I prefer to write it out in html and there was a thing which I used to do ontop of that:
I would delete the https://peakd.com or https://domain.io part as we do when changing interfaces.
This essentially then looks like this /@someaccount/somepost
In that way I would then assure that no matter if someone reads my content on Leo, Peakd, Hive.blog, Ecency ... or any one of the tribes, I would ensure they stay on their own interfaces.
Photo by Pixabay: https://www.pexels.com/photo/application-blur-business-code-270408/
To be fair recently I have gotten lazy.
Ok I have always been lazy, but I have forgotten I do that.
Today on twitter I saw 
Why I think I have stopped doing relative urls in my content is because I mainly use Ecency anyway. Ecency does something that others don't do.
They convert any valid Hive content links to point to Ecency itself.
This means that if I wrote a post on Leo, or even Ecency but in my copy paste linking I am taking links from LeoFinance where I am reading said post but I am writing on Ecency, the base HTML will include https://leofinance....
But if I view that post on Ecency it won't take me to Leo it will keep me inside the Ecency Webapp or more importantly the Mobile app.
Absolutely go Relative
This URL rewrite that Ecency does on the interface ensures that users stay in the app they have chosen to use. I personally think this is something which all Hive interfaces should do.
In time a standard can possibly even be achieved, maybe a hover to have a user just choose to say: "You know I think I do want to be absolutely irritated and see this on the linked from interface instead."
Most used feature that? Doubtful.
With more Hive content interfaces arising and some of them being unique and strong enough to warrant a mobile app, the need for relative linking. ie. keeping users on the same domain as they are viewing the content will be something that is rather important.
If not already. Maybe some just never mention it, but I know I Ecency because this is something I like.
Attribute this
As for domain attribution and such things, I think 
Personally I think if you want to attribute a Dapp you are using then add the att, but auto att is a little imposing no?
Who knows possibly each Dapp can at least get custom tags which the interfaces will use to show oh look it a Leo or a Hive.blog post.
Users will use what they use and which has the best experience.
If I get directed to another interface just because the person who wrote the content likes Peakd and Leo but they are writing on Peakd then linking some to Leo and some to whatever Hive interface they happen to have open... I can promise you that is the soonest I learn to not open anymore links on that interface.
To be fair most say hey this is outbound, and you are leaving Peakd to go to Timbuktu...
Why?
Why am I leaving Peakd to go to Timbuktu when it is actually aunt Jenny's post right on the next block?
So I think instead of trying to demonize URL rewriting by interfaces. It is probably good to understand why.
https://twitter.com/FinanceLeo/status/1645444281597927425
- FinanceLeo