Given that your key has expired.
$ gpg --list-keys
$ gpg --edit-key KEYID
Use the expire command to set a new expire date:
| # send logs for all traffic (including non-html) to google analytics | |
| # | |
| # in server block: | |
| # set $google_analytics_id "UA-THECORRECT-ID"; | |
| # include /srv/nginx/google_analytics; | |
| # | |
| # in location blocks: | |
| # post_action @ga; | |
| # | |
| # notes: post_action has been referred to by nginx devs as a "dirty hack" and this approach may stop working one day. |
| <head> | |
| ... | |
| <!-- to fix FOUC (Flash of Unstyled Content) --> | |
| <script type="text/javascript"> | |
| var elm=document.documentElement; | |
| elm.style.display="none"; | |
| document.addEventListener("DOMContentLoaded",function(event) { elm.style.display="block"; }); | |
| </script> |
For a more detailed version of the steps below visit: https://developers.google.com/admin-sdk/directory/v1/guides/delegation
| /* | |
| * This script will create base62_encode() and base62_decode() in the current schema of a postgresql database. | |
| * Give it a star if you find it useful. | |
| */ | |
| CREATE OR REPLACE FUNCTION base62_encode( long_number bigint ) | |
| RETURNS text | |
| AS $BODY$ | |
| /* | |
| * base62_encode() |
Network views tend to be the view of the network from a single node, or small selection of nodes. They are not complete views of the network. This is impossible to achieve. Even if many node views were combined, it would still be incomplete.
These network views, or network maps, have been termed 'visualisers' by the LN community.
Screenshots may reflect older visual styles, and are dated accordingly.
I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/
It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.
Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>A simple clock</title> | |
| </head> | |
| <body translate="no" > |
| #include "audiorenderer.h" | |
| #include "videorenderer.h" | |
| #include "audiocapturemodule.h" | |
| #include "yuvframecapture.h" | |
| #include "conductor.h" | |
| #include "webrtc/api/test/fakeconstraints.h" | |
| #include "webrtc/video_encoder.h" | |
| #include "webrtc/modules/video_coding/codecs/vp8/simulcast_encoder_adapter.h" |
Enable developer console in browser and navigate to:
Look for the response of POST request in the network tab of developer console: https://www.facebook.com/v2.6/dialog/oauth/confirm?dpr=1 it contains the access token parameter. Just search for 'access_token' in the response. For the lazy people (like myself) i made a small helper that parses the token from response https://taseppa.github.io/tokenparser.github.io/