OP's wife: welp I guess I can stop shaving this thing
Fediverse
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
OP’s cat: finally.
I’m dead. You and the poster you replied to just murdered me. 🤣
I found it amusing when, in response to an issue, the admin asked someone to open a ticket by sending it to [email protected]. 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 [email protected] refers to a community or a user!
I think for ideal clarity using [email protected] and @[email protected] 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/[email protected] and u/[email protected] 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/[email protected] 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/[email protected], 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: [email protected]
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 [email protected], it would not really matter is it in form of c/[email protected] or with !
From one hairy situation to another, in time.
Pornlemmy, You say? I'll be right back.