attack i/o

I'm a huge fan of JavaScript, and I love how it's been evolving over the years, however some new features are questionable from my point of view.

Changing the Promise spec to add a method which is already possible by the design of Promise is borderline insane.

Promise.finally() will allow you to do try/catch/finally with async functions, which sounds awesome and if you never use higher order functions it is awesome; however it's not an problem if you don't intend to use async functions!

Let me demonstrate:

Promise.reject(new Error('omgad')).catch(e => console.warn(e.message)).then(() => console.log('finally?'));

I made this module after noticing bugs in my stack due to a lack of coverage afforded by every test framework I looked at. It handles the annoying things like capturing & reusing cookies, headers & etags (special case).

I released a sample tenso API on github as a starting point for new API gateways that are powered by node.js & want to be OWASP compliant with minimal developer effort.

It's hard when you have to say goodbye to beloved "pet", which is a poor word to describe the type of bond & companionship you can have. Halo, my "therapy" cat of 18+ years was put to sleep last night. I can't describe the type of loss and pain this has inflicted my family with; however, I can gladly say that those 18 years started near the lowest point, the death of my father, and continued well into the highest point, my marriage. It was one hell of a ride with much love and laughter. Goodbye my mostly silent friend, you will be greatly missed.

https://www.ssllabs.com/ssltest/analyze.html?d=api.ottawa.ski

This was as simple as generating a 4096 bit key, i.e. openssl dhparam -out dhparam.pem 4096 and running the following config for nginx:

I'm glad to say this API has finally gone pseudo 'live', with weather data provided from the OpenData initiative of the Canadian Government & my nodejs module canada-weather.

The API gateway is very simple in design. It's running tenso 4.0 which I released earlier this week, which is based on an effort to clean up the underlying turtle.io server.

Behind the API is a cron job which executes every 30 minutes to scrape weather data, and write to specific files on disk. This allows me to have the API gateway map requests to data without adding complexity; a file watcher is registered on startup, which updates the in RAM representation after a change is detected; if the file is erased the current representation is served until the server is stopped. The data sits in a Map>Map>Object structure for quick validation/retrieval/serialization.

I plan to use a similar method for the other API collections, but with a shorter polling interval.

The tenso server is kept alive with systemd, and the stdout & stderr are routed to syslog for me.

Done with AFINN sentiment analysis:

stinkfist: 4, 0.02 comparative

eulogy: -15, -0.06 comparative

h: -33, -0.13 comparative

useful idiot: N/A

forty-six & 2: -18, -0.07 comparative

message to harry manback: -56, -0.32 comparative

hooker with a penis: -36, -0.15 comparative

intermission: N/A

jimmy: -14, -0.07 comparative

die eier von satan (english): -9, -0.08 comparative

pushit: -4, -0.02 comparative

cesaro summability: N/A

ænema: -83, -0.21 comparative

(-)ions: N/A

Done with AFINN sentiment analysis.

intolerance: 2, 0.12 comparative

prison sex: 1, 0.00 comparative

sober: -7, -0.05 comparative

bottom: -51, -0.28 comparative

crawl away: 3, 0.03 comparative

swamp song: -15, -0.16 comparative

undertow: -3, -0.01 comparative

4 degrees: 6, 0.03 comparative

flood: 0, 0.00 comparative

Done with AFINN sentiment analysis.

sweat: 14, 0.10 comparative

hush: -19, -0.37 comparative

part of me: 10, 0.11 comparative

cold & ugly: -18, -0.3 comparative

jerk off: -22, -0.18 comparative

opiate: 3, 0.22 comparative