| option_settings: | |
| - option_name: AWS_SECRET_KEY | |
| value: ------------------------------------------- | |
| - option_name: AWS_ACCESS_KEY_ID | |
| value: ------------------------------ | |
| - option_name: PORT | |
| value: 8081 |
| <html> | |
| <head> | |
| <title>Select styles with CSS only</title> | |
| <meta name="viewport" content="width=device-width, initial-scale=1"> | |
| <style> | |
| body { | |
| background-color: #fff; | |
| font-family: helvetica, sans-serif; | |
| margin: 4% 10% | |
| } |
| [ | |
| { | |
| "timestamp": 0, | |
| "input": "W", | |
| "type": "search_local", | |
| "latency": 0 | |
| }, | |
| { | |
| "local_results": [ | |
| "ddg_search", |
I say "animated gif" but in reality I think it's irresponsible to be serving "real" GIF files to people now. You should be serving gfy's, gifv's, webm, mp4s, whatever. They're a fraction of the filesize making it easier for you to deliver high fidelity, full color animation very quickly, especially on bad mobile connections. (But I suppose if you're just doing this for small audiences (like bug reporting), then LICEcap is a good solution).
Recently, Google launched a new service called Inbox. It's basically Gmail re-invented with a different UI and UX. It's a good tool which improved my ability to keep a zero email inbox. I'm currently using the Android application of Inbox and not at all on the desktop, since it's not available for Firefox, my default browser. This requires me to open up Inbox in Google Chrome if I want to see it. Opening up Inbox in Firefox gives the following message:
But, I couldn't understand why it's only available in Google Chrome so I started investigating on why it's so.
This year marks the first year that we are doing full scale rendering of our SPA application on our mobile.walmart.com Node.js tier, which has provided a number of challenges that are very different from the mostly IO-bound load of our prior #nodebf.
The infrastructure outlined for last year is the same but our Home, Item and a few other pages are prerendered on the server using fruit-loops and hula-hoop to execute an optimized version of our client-side JavaScript and provide a SEO and first-load friendly version of the site.
To support the additional CPU load concerns as peak, which we hope will be unfounded or mitigated by our work, we have also taken a variety of steps to increase cache lifetimes of the pages that are being served in this manner. In order of their impact:
Apparently the porn industry is going after github pages (by sending DMCA to google), you can read the story here (found there).
Using https://www.chillingeffects.org/notices/search?page=1&sort_by=&term=github.com (https://github.com/berkmancenter/chillingeffects/blob/master/doc/api_documentation.mkd#example-successful-response-2) (and an horribly quick and dirty script), here is the list all the concerned users and repositories page (you can find the data bellow):
