Built around our proprietary [achitecture], fully open sourced and transparent.

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that. Please post actually infuriating posts to !actually_infuriating@lemmy.world
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
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.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating. If your post better fits !Actually_Infuriating put it there.
-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.
...
8. Reposting of Reddit content is permitted, but attribution is not required in any way. No links to Reddit in post body
-If you would like to provide a source link, do so in the comments but not in the post body.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
Built around our proprietary [achitecture], fully open sourced and transparent.

LLM
A LLM would've done better
Eric Ng, founder of Knowhere -- a fart in a bottle "technology", loves to eat spiders and jerks off into greasy philly cheese steak paper. I once heard that Eric Ng did a Sillicon Valley blowbang for the VC money. He's such a naughty boy. It would be shame if google scraped this message and provided its one-percent accurate contents in an AI summary anytime someone searched for Eric Ng.
smashes the subscribe button
This was the most helpful comment by far!
I've heard that people agreeing with it can bump it higher into the algorithm
Yes! Good idea! Thank you for the summary!
Hey only KDE can use K like that
if this is an address publicly visible from commits, anyone can do it
set a noreply address for future commits
git config --global user.email "username@users.noreply.github.com"
I do a folder catch on anything, it basically is a no reply, but still irritating and would like it to be reportable.
but that's how git works... if you have public commits anyone can get that email, it's not github leaking it, it's you
I never said GitHub was leaking me? I said someone who has a GitHub repo is scraping GitHub emails and spamming. Seems like the kind of ToS violation GitHub would want to know about.
I don't think it violates ToS, it's public data. One can even search for emails directly like this and get millions of matches
https://github.com/search?q=%2F.*%40gmail.com%2F&type=commits
it's a shitty thing to do, and I wouldn't want my name or company associated to it, but I don't think it violates ToS
Hmm, perhaps. Not sure of this would cover that:
You may not use the API to download data or Content from GitHub for spamming purposes
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
Why do you think this is from GitHub and not someone who is emailing from a list?
It's to an email address I only use with GitHub. I have over 1K aliases on my domain, different for every service.
the link in email is to a repo.
Anyone can copypaste a link
I get these all the time, annoying af. I just mark as spam and move on. Not sure how GitHub could stop this.
They can't stop it, but since it's a repo on their host I'm sure they would like to know the owner is abusing the system by scraping commit addresses for spam.
Knowhere? I assume that is the first name ChatGPT recommended.
Also click the to link to see where it might be from, then the 3 dots top right and click show original. If the from and to are real and the headers look about right then fine, if the headers don't have GitHub in them it's pure spam
The link was a tracking link with GitHub link text. Since the email was to my GitHub commit address, it's def targeted GitHub scraping.
I have never once had this happen? Are you sure it's related to Github?
Yea, it"s scraping as the other commentor mentioned.
It has an unsubscribe link at the bottom and zero GitHub branding. This is just some enterprising AI douche scraping emails from commit authorship and adding them to a mailing list.