| [tool.poetry] | |
| name = "remove_duo_friends" | |
| version = "0.1.0" | |
| description = "" | |
| authors = ["Felix Sargent <felix.sargent@gmail.com>"] | |
| readme = "README.md" | |
| [tool.poetry.dependencies] | |
| python = "^3.8" | |
| requests = "^2.31.0" |
Kong is pretty cool. Auth0 is pretty cool. They should work together. This guide details the fastest way to get your APIs protected using JWT tokens issued by Auth0.
Pre-requisites:
| [ | |
| { | |
| "name": "SofleKeyboard", | |
| "author": "Felix Sargent", | |
| "switchMount": "cherry" | |
| }, | |
| [ | |
| { | |
| "y": 0.2, | |
| "x": 3, |
| Amendments | 1st | 2nd | 3rd | |
|---|---|---|---|---|
| New Hampshire | 5 | 4 | 4 | |
| Massachusetts | 16 | 14 | 15 | |
| Vermont | 3 | 2 | 2 | |
| Rhode Island | 2 | 2 | 2 | |
| Connetticutt | 8 | 7 | 7 | |
| New York | 11 | 10 | 11 | |
| New Jersey | 7 | 5 | 5 | |
| Pennsylvania | 14 | 13 | 14 | |
| Delaware | 2 | 1 | 1 |
Answer
{
"actions": [
{
"say": "Hello! Who would you like to call?"
},
{
"listen": true
| const app = new (require('express'))(); | |
| const wt = require('webtask-tools'); | |
| const crypto = require('crypto'); | |
| // Be sure to specify your SDK key for your environment! | |
| app.get('/', (req, res) => { | |
| const hmac = crypto.createHmac('sha256', req.webtaskContext.secrets.LD_SDK_KEY); | |
| hmac.update(req.user.email); | |
| req.user.ld_hash = hmac.digest('hex'); |
| # some more ls aliases | |
| alias ll='ls -alF' | |
| alias la='ls -A' | |
| alias l='ls -CF' | |
| # enable color support of ls and also add handy aliases | |
| if [ -x /usr/bin/dircolors ]; then | |
| test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" | |
| alias ls='ls --color=auto' | |
| #alias dir='dir --color=auto' | |
| #alias vdir='vdir --color=auto' |
| $ middleman build | |
| create build/apple-touch-icon-precomposed.png | |
| create build/img/logo.png | |
| create build/img/social-sa760cfa992.png | |
| create build/img/cards/card1.png | |
| create build/img/cards/card5.png | |
| create build/img/social/blog.png | |
| create build/img/social/facebook.png | |
| create build/img/social/twitter.png | |
| create build/img/cards/card2.png |
| C:\NS2>Server.exe -map ns2_tram -limit 8 -lan false | |
| Changing setting 'lanGame' to: 'false'... | |
| Changing setting 'mapName' to: 'ns2_tram'... | |
| Changing setting 'playerLimit' to: '8'... | |
| Press Tab to open the console window | |
| Press Ctrl-C to exit | |
| -------------------------------------------------------------------------------- | |
| Build 204 | |
| Starting Natural Selection 2 |
Cut your backlog.
Your backlog is too long. You know it, your team knows it. There are things in there from two years ago, collecting dust, feeling neglected. Issues that may or may not have been fixed, long forgotten festering in the unprioritized dungeon of your backlog. Delete them.
"As a database, I would like to support Acme Standard ZXY 2.17-3" No value, no stakeholder. What does ZXY 2.17-3 do? What does that even mean? Delete it.
Product Managers often use the Backlog as a notepad. A place to jot down tasks before they slip from consciousness into a vaguely nagging feeling of necessity as you grab a soda. Stop. Realize that every item in your backlog has to be sorted, and you are a human bubblesort - so inefficient your primary purpose is to show computer science students how not to sort lists. The fewer stories you have, the more meaningful they can be.