Here's a simple way to think of git as a data structure rather than a magic box (not using any particular syntax):
history: Map<Hash, Commit>
Commit {
changes: Diff,
previous: Hash,
| https://thedefiant.io/feed/ | |
| https://www.coindesk.com/arc/outboundfeeds/rss/?outputType=xml | |
| https://cointelegraph.com/rss | |
| https://cryptopotato.com/feed/ | |
| https://cryptoslate.com/feed/ | |
| https://cryptonews.com/news/feed/ | |
| https://smartliquidity.info/feed/ | |
| https://finance.yahoo.com/news/rssindex | |
| https://www.cnbc.com/id/10000664/device/rss/rss.html | |
| https://time.com/nextadvisor/feed/ |
Inspired by the following exchange on Twitter, in which someone captures and posts a valuable video onto Twitter, but doesn't have the resources to easily transcribe it for the hearing-impaired, I thought it'd be fun to try out Amazon's AWS Transcribe service to help with this problem, and to see if I could do it all from the bash command-line like a Unix dork.
The instructions and code below show how to use command-line tools/scripting and Amazon's Transcribe service to transcribe the audio from online video. tl;dr: AWS Transcribe is a pretty amaz
https://snapchat-example-api.herokuapp.com/api/v1/
/users/authenticate require the X-Api-Token HTTP header| var crypto = require('crypto'); | |
| // larger numbers mean better security, less | |
| var config = { | |
| // size of the generated hash | |
| hashBytes: 32, | |
| // larger salt means hashed passwords are more resistant to rainbow table, but | |
| // you get diminishing returns pretty fast | |
| saltBytes: 16, | |
| // more iterations means an attacker has to take longer to brute force an |
The git command-line utility has plenty of inconsistencies http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
A GUI like http://sourcetreeapp.com is often helpful, but staying on the command line usually quicker. This is a list of the commands I use most frequently, listed by functional category:
git status list which (unstaged) files have changed