/u/[email protected] and /c/[email protected] are better because they work automatically, no need for special handling if you’re using the web frontend. and also the same should be done for posts so it automatically opens the post on your own instance instead of redirecting you to another website.
Nevermind “it looks wrong”, it works less well! Using !comm@instance, you can directly go to a comm and subscribe to it or block it (plus it’s automatically displayed in dark mode if that’s your preference), which is quite a bit harder to do with a /u/comm@instance link.
I always get confused with these!
Even the Lemmy devs used to get it wrong, there was multiple times way back in the past where they’d link something and a bot would reply that they’re doing it wrong.
Yeah, I basically stopped tagging stuff because I never got used to the formatting.
And also because I never remember which instance it’s on.
In the web UI it should automatically start suggesting things as soon as you type @ or ! - no need to remember
Also in the Voyager client.
deleted by creator
I mean so does Lemmy in the default interface (WebUI)
I seemingly have a rverse take - I much prefer the latter. i just do not use threadiverse, i use places where !/@ means something totally else (for example in programming ! is not and @ can be used for different purposes, but in my shell, @ sigil is used for arrays). the latter is very clear to me - /c/ is comm and /u/ is user. a bit more verbose (3 characters vs 1) but not that much but much more readable for someone comming from outside or who context switches.
Missed an opportunity to use IAM style principals, e.g. user:[name]@[instance] and comm:[name]@[instance].
ew. This is your brain on AWS
This is my brain liking self-documenting strings, instead of having to remember which symbol means what. I’m using a communications platform, not playing nethack.
