Thank you.
Actually... do you have a post already (EN) describing @krolestwo and all of its use cases that are Hive related? If so, please share a link, or couple of links.
You are viewing a single comment's thread from:
Thank you.
Actually... do you have a post already (EN) describing @krolestwo and all of its use cases that are Hive related? If so, please share a link, or couple of links.
There is only one published a year ago on @hive.aid. Yeah, we have to write a new one, because a lot has changed over the year.
Thanks, by the way I'll use this example as an opportunity to show the importance of frontend-agnostic links that IMHO should highly recommended.
That's because (1) your link is explicitly redirecting viewer to a PeakD platform, regardless of which frontend user (clicking it) is currently using (logged into).
This might be annoying if your hard-linked fronend is different than my preferred, since I might either need to log in to a different one (which I would rather avoid to) or replace part of the url in my browser.
So instead of using a link that explicitly opens a post in:
PeakD
Ecency
Hive.Blog
etc.
You can just use an (4) universal one in order to open it in a same front end app that the user is reading it in.
Here's how those links looks like in markdown:
1.
[PeakD](https://peakd.com/standwithukraine/@hive.aid/the-last-homely-house-eng)2.
[Ecency](https://ecency.com/standwithukraine/@hive.aid/the-last-homely-house-eng)3.
[Hive.Blog](https://hive.blog/standwithukraine/@hive.aid/the-last-homely-house-eng)4.
[universal one](/@hive.aid/the-last-homely-house-eng)Of course (4) is a preferred way. As you can see it consists of just
/@username/permlinkTesting something new I just learned: universal one
0.0 Oh, that's sexy! I have to remember this.