2,215 karma · joined October 29, 2008
C/C++, baremetal/cloud, nginx/openresty/nchan, LuaJIT, PHP, Redis, statsd/rrd
None of your suggestions are going to do anything but aggravate the offender further, which is the entire point of the post you've replied to.
It's like suggesting Snapchat monitor and deny underaged teens from from taking suggestive photos.
> Sidenote: So despite media reports to the contrary, Blizzard and Riot appear unaffected.
Battle.net was hit all weekend; the effects were obvious for anyone trying to authenticate. It was not a hardcore DDoS; it just took a long line to get auth'd, at which point other Blizzard services seemed mostly OK -- some games were still affected, regardless of the auth services.It seemed to get better by Sunday, where I can only recall one or two times having timeouts.
I don't know that this extension purports to "fix" reply. I don't recall Gmail's reply ever working much differently than it does -- an inline textarea under the thread. Unclear what you are gaining from shift-click replying. Anything but inane... and hardly anything near one of the worst UIs... very revisionist.
* Have shortcuts on and hit "d" -- open a new compose [browser] tab
* Hold Shift and hit "c" (or click "Compose") -- open compose in a popup
* Hold Shift+Ctrl and click "Compose" -- open a compose that fills 90% of the viewport
As well, Netflix will do the same -- literally stick a disk array of videos inside Verizon's network.
Report, using the "command" module, free memory on all "nyc-web" hosts in our "prod-hosts":
ansible -i prod-hosts nyc-web -m command -a 'free -m'
More often, we'll want to have Ansible playbooks [2] that take our hosts and assign roles. Briefly on the topic, we might have a "common" role that deals with updating our package manager, checking/upgrading packages that every machine should have (eg. ssh, ntp, etc), and ensuring certain processes are running. Second, we might have a "web" role that is similar to "common" but dealing with web-server specific packages, configs, etc. As to keep it brief, we'll skip how the roles are setup, but here's our "web" playbook (web.yml), and find that we've defined the hosts [group] to execute against -- all hosts under our "web" group in the hosts inventory. ---
- hosts: web
remote_user: web-user
roles:
- common
- web
Which we'll execute with: ansible-playbook -i prod-hosts web.yml
Maybe you only want to hit nyc-web and not all web hosts? The following will take the intersection of the playbook's hosts "web" and the "limit" hosts "nyc". ansible-playbook -i prod-hosts web.yml --limit nyc
Or maybe you know the one IP you want to hit. The ":&" syntax is a logic AND to find only the nyc 10.0.2.21, because we also have one in LAX. If your IP layout, then simply a "--limit 10.0.2.21" would do. ansible-playbook -i prod-hosts web.yml --limit 'nyc:&10.0.2.21'
[0] http://docs.ansible.com/intro_adhoc.html/etc/ansible/{dev,test,stage,prod}-hosts
[nyc-dns]
10.0.1.1
10.0.2.1
[nyc-web]
10.0.1.21
10.0.2.21
[nyc-db]
10.0.1.201
10.0.2.201
[nyc:children]
nyc-dns
nyc-web
nyc-db
[lax-dns]
10.0.1.1
10.0.2.1
[lax-web]
10.0.1.21
10.0.2.21
[lax-db]
10.0.1.201
10.0.2.201
[lax:children]
lax-dns
lax-web
lax-db
[dns:children]
nyc-dns
lax-dns
[web:children]
nyc-web
lax-web
[db:children]
nyc-db
lax-dbAlso, Flask was created as a joke; it obviously took off; but there's something there about not taking it super super serious.
$blah = "hi $_GET[hello]";https://www.google.com/intl/en/chrome/devices/chromecast/app...
NOTE: I have no opinion on their involvement in the goto fail;