If you host your own DB of users and passwords you are a target. Offloading it to as many wide-spread oauth providers as possible is a smart move.

“You’re absolutely right!”

“If you want, I can…”

🚀, 🎯, 📌, ✅

Any images being presented/created/passed then questioned and the same image (use a checksum I guess) is returned.

I’ve read that the double dash (emdash?) is a bit of a giveaway as although correctly used, it’s not very prevalent in current English (although, I do remember Microsoft Outlook used to convert hyphens to that as well). And I think double-space after a full-stop/period?

OMG, this is the internet don’t be posting self-flaws. Jeez. ^kthxlvubai

Yep. I won’t be playing because of this.

Terrible title, I thought it was a vulnerability in git.

I mean, I get it, but that’s also not a thing of git, right? Just because GitHub does something doesn’t mean every other hosting provider needs to. If your code review process is to comment upon specific commits, maybe it’s the code review process that’s wrong?