this post was submitted on 03 Mar 2025
848 points (98.2% liked)
Lemmy Shitpost
29005 readers
3406 users here now
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When I handled these, I always checked for poor taste collisions. If found, granted an immediate exception.
She would be Megan.finger@.
Fuck the old systems with hard character limits.
Firstname.lastname@address is pretty much a universal standard, why would you use anything else?
My work does first initial last name, which even internally results in tons of jsmith2@company.com.
I don't really get why I can't just choose from a list of accepted combinations or something.
This is just supposition but I presume the resmasoning is they want to programatically "calculate" your email address.
I mean that's a dumb constraint but it does explain the requirement.
You'd think that every place should do this, but for whatever reason a lot of them do weird shit like in the OP. Not sure why that is. Maybe they are afraid of the characters running too long or something like that for people with long names?
Edit: Wow just reading through some of the real generated emails in this post is wild lol!!
They are probably just trying to keep consistency between an AD instance and Exchange or something like that. Or just laziness.
When we generate new user accounts we run a script that generates an email (so we don't have to manually do it). It gets generated with the username of the individual which in our case would be first initial, last name. Then another alias gets generates to first.last@x.whatever and is set as primary. While the username@x.whatever is left as an alias, but would still technically work if you emailed it.
If a username already exists we will use the first and second letter of the first name and then the last name, etc.
In the above I mentioned consistency and laziness, but there is also another side, and that is your user base. If you are servicing hundreds of thousands of people or just a ton in general, consistency is very much preferred. Try having to explain to an end user that their login is simply "username" for their computer, but their email is "first.last@x.whatever" oh and let's go ahead and loop in Azure SSO so now their software license login and login for all these other portals is "username@x.whatever".
You end up with a mass of confusion. Sometimes simplicity is best when it's possible.