I found from hard way that lemmy community urls are bit problematic. Here is the story, which contains bit NSFW material.
I was trying to figure out in Jerboa how to subscribe to community in another instance. First one that I came across, that i was not subscribed to was !hairypussy@pornlemmy. com. (I know, I know, I am a perv)
I copy pasted the community path to my android clipboard, and tried few ways in the app, and eventually gave up.
Some time passes, until I went to do some shopping. My wife and I use a shared shopping list. From this shopping list I found this beatiful community path.
My wife had a laugh, but I was worried that If she would have been bit more jelous side, she could have made a assumption from the structure of the path.
The thing is that !hairypussy @ pornlemmy. com looks like email address. This could have been misunderstood quuuite badly.
I am a coder also, so @ is sensible separator, and serves the same purpose as in email. Probably it should not change, but the structure can cause misunderstandings with some communities and lemmy instance urls. Of course here main issue is user error, and any link to some bad site can be issue, but people understand what website URL is.
Please let me know if this needs NSFW tag.
OP’s wife: welp I guess I can stop shaving this thing
OP’s cat: finally.
I’m dead. You and the poster you replied to just murdered me. 🤣
deleted by creator
I found it amusing when, in response to an issue, the admin asked someone to open a ticket by sending it to support@lemmy.world. At first I thought he meant to DM the account, but then I was like Ohhh, you mean actually send an e-mail to that address. I can totally see people confusing the two concepts.
That’s true, and in addition it could even be confusing whether support@lemmy.world refers to a community or a user!
I think for ideal clarity using !community@instance.adress and @user@instance.adress would be best to differentiate from e-mail addresses. Though that would tag users for mention notifications more often I guess.
I feel like it should be community#instance.domain. The @ is already internet common for email addresses. It should be avoided to reference communities.
Sadly # is reserved URL particle for page anchors i.e. to refer to an HTML element by its ID.
I would maybe say that c/community@instance.com and u/user@instance.com could be better. / is not legal character on email address, but so is of course ! in the front. c/ and u/ would make sense because that is the actual url that is fetched (c/community@instance.com is located in https://instance.com/c/community), so in code just combining these two paths together would generate the actual URL. Also external communities are handled by https://homeinstance/c/community@instance.com, so it would make sense here also, because c/ is already part of the path.
Of course changing it at this point in time of the life cycle is probably a no-go.
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !community@instance.com
Sure about that “not a legal email character” part?
Ok, it seems that I was wrong, standard seems to allow it. So both ! and / are allowed in email
but these solutions would not have saved my clumsy ass in the original case.
If instance would have been fictional furryporn.com and community is called worldnews, and I sent to my grandmother a message containing community url !worldnews@furryporn.com, it would not really matter is it in form of c/worldnews@furryporn.com or with !
From one hairy situation to another, in time.
Pornlemmy, You say? I’ll be right back.
