| export ORG_NAME="Some Company" #change that to your company's name | |
| export SLACK_TOKEN="xoxb-**************************" #Your slack token | |
| curl -L -v -H "Authorization: Bearer $SLACK_TOKEN" "https://slack.com/api/users.list" > contacts.json | |
| cat contacts.json | jq '.members[]?.profile|select(.phone != "")| .real_name+"-"+.phone'| sed 's/\"//g'| while IFS= read -r item; do echo "BEGIN:VCARD\nVERSION:3.0\nFN:${item%-*}\nTEL;TYPE=CELL:${item#*-}\nN:`echo ${item%-*}| awk '{if ($3){ print $3";"$1";"$2} else {print $2";"$1}}'`;;;\nitem1.ORG:${ORG_NAME}\nitem1.X-ABLabel:unknown\nCATEGORIES:myContacts\nEND:VCARD" ; done> contacts.vcf |
| /** | |
| * Wrapper around terragrunt to display output succinctly on Atlantis. | |
| * | |
| * Terragrunt is notoriously verbose, which can cause Atlantis to output | |
| * hundreds of comments on single PRs, which can be annoying. | |
| * | |
| * This script will output just the final plan for resources to update on | |
| * successful terragrunt runs, but will output all terragrunt output on | |
| * errors. | |
| */ |
In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:
http://techcrunch.com/2007/08/11/facebook-source-code-leaked/
It became a big deal:
http://www.techmeme.com/070812/p1#a070812p1
The two files are index.php (the homepage) and search.php (the search page)
