#random (2020-09)

Non-work banter and water cooler conversation

A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you’d prefer to keep out of more focused work-related channels. Archive: https://archive.sweetops.com/random/


rms1000watt avatar

Pretty interesting: https://www.socialcooling.com

Social Cooling - big data's unintended side effect attachment image

Thousands of hidden scores influence your chance to get a job, a loan, insurance or even a date. Social Cooling describes how this increases pressure to conform, and asks how this will change society.

Joe Niland avatar
Joe Niland
The Salt Journey Continues with VMWare | SaltStack attachment image

On February 20th, 2011, I started on a journey. I wrote and committed my first lines of code to the Salt open source project. I was alone in my basement at the time, motivated by a desire to solve some technical problems and improve my resume. By April of 2011, I had cut the first […]


jason einon avatar
jason einon

great resource for pattern cards if going through digital transformations: https://www.cnpatterns.org/patterns-library

rei avatar

Nice ressource! Thx


Majan Paul avatar
Majan Paul
GitHub on LinkedIn: GitHub CLI 1.0 is here :tada: Take GitHub to the command line and interact | 155 comments attachment image

GitHub CLI 1.0 is here Take GitHub to the command line and interact with repositories, issues, pull requests, releases, and more. ✓ Free and open … 155 comments on LinkedIn



sheldonh avatar

If I’m part of an organization…. rather than setting the email address of the commit to my work email, what is the negative of just using my standard [users.noreply.com](http://users.noreply.com) github email associated to my user. Since the commits are all private in the org, I’m wondering why I bother setting it to my work email in the commit history in the first place. Any reason to do this?

Note, I just figured out mailmap, which I found interested. It got me to thinking that it’s all mixed up mostly with folks anyway, so why not just use the exact same one regardless of org or not?

RB avatar

i use @users.noreply.github.com at work and there are no issues

sheldonh avatar

got you. i’ve set a separate one per profile in each repo, but now just thinking why do I bother

Jonathan Marcus avatar
Jonathan Marcus
Don’t use [noreply.com>. See Brian [Krebs>’ <http://voices.washingtonpost.com/securityfix/2008/03/they_told_you_not_to_reply.html stories](https://krebsonsecurity.com/2020/09/the-joys-of-owning-an-og-email-account/) of why you shouldn’t use emails like that. He just wrote about this yesterday actually. But someone owns <http://donotreply.com|donotreply.com](http://noreply.com) and they happen to be friendly but you can’t count on that.
The Joys of Owning an ‘OG’ Email Account

When you own a short email address at a popular email provider, you are bound to get gobs of spam, and more than a few alerts about random people trying to seize control over the account. If your account name is short and desirable enough, this kind of activity can make the account less reliable…

sheldonh avatar

Sorry that’s not what we are talking about

sheldonh avatar

This is a subdomain for github, to protect email privacy being mapped directly in the commit history

Jonathan Marcus avatar
Jonathan Marcus

Gotcha. Yeah I saw the [users.noreply.github.com> and saw that was okay; I saw the bare <http://users.noreply.com|users.noreply.com](http://users.noreply.github.com) and was worried for you