the problem with links is that we’re all on different websites, and lemmy vs kbin use different url standards. on lemmy it’s /c/ and kbin it’s /m/. and ofc different host names.
My impression – and I have not gone digging through the tech docs yet – is that the idea is that !magazinename@instancename is supposed to be the syntax for reference, but it isn’t correctly auto-hyperlinked, at least on kbin.
Kbin (and Mastodon, calckey et. al.) don’t know what to do with a bang url. It’s a lemmy thing. @[email protected] should work, but doesn’t because of a kbin bug. It works on those other platforms though.
I wanted to try with the !. yes, doing it without does hyperlink it, however here on kbin it can sometimes lead to a /u/ page and sometimes to an /m/ page and it seems unpredictable which one it does.
Doing the lord’s work, thank you. I’ve genuinely not figured out the link stuff yet, like I’m trying to learn the alphabet over again
the problem with links is that we’re all on different websites, and lemmy vs kbin use different url standards. on lemmy it’s /c/ and kbin it’s /m/. and ofc different host names.
My impression – and I have not gone digging through the tech docs yet – is that the idea is that !magazinename@instancename is supposed to be the syntax for reference, but it isn’t correctly auto-hyperlinked, at least on kbin.
Kbin (and Mastodon, calckey et. al.) don’t know what to do with a bang url. It’s a lemmy thing. @[email protected] should work, but doesn’t because of a kbin bug. It works on those other platforms though.
@tal @damipereira @Beardedsausag3 @Otome-chan Try putting an @ sign before what you just typed. For example, @audiofiction
testing: @!gaming !@gaming @[email protected]
@Otome-chan @damipereira @Beardedsausag3 @tal I’m not sure how it automatically puts the, !, in there, but what about removing the, !, and just having @gaming unless Lemmy requires the !?
I wanted to try with the !. yes, doing it without does hyperlink it, however here on kbin it can sometimes lead to a /u/ page and sometimes to an /m/ page and it seems unpredictable which one it does.