@thelonelyghost

thelonelyghost ( thelonelyghost@infosec.pub ) · 3 years ago

That’s hilarious because for automated access to the API, without tying to a single specific user account (for attrition purposes), my company was advised by Microsoft Support to create a service account for that API access. The process was the exact same as any other user account because… it WAS like any other user account.

thelonelyghost ( thelonelyghost@infosec.pub ) · 3 years ago

Like what?

OCI registry? GitLab.
pull request model? Every one of the competing services
CI/CD system based on YAML definitions? Most every competitor.
static site hosting? Most competitors
protected branches? Most competitors

I’m not saying there isn’t vendor lock-in, but I am saying it likely isn’t the features of GitHub that are limiting that. Third party integrations will follow wherever the foot traffic goes.

thelonelyghost ( thelonelyghost@infosec.pub ) · 3 years ago

Incoming job board spam:

… just to name a few

thelonelyghost ( thelonelyghost@infosec.pub ) · 3 years ago

direnv
nixpkgs (with flakes enabled)
committed flake.nix and flake.lock
Makefile or several shell scripts in bin/ for common tasks

(explainer)

thelonelyghost ( thelonelyghost@infosec.pub ) · edit-2 3 years ago

This reads the same as “hi, my friend saw my {dating app} date’s photo up at the post office with the note that they were wanted for the murder of 16 different {my demographic}. Should I still go on a date with them to that remote cabin in the woods?”