<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[RSS Feed]]></title><description><![CDATA[RSS Feed]]></description><link>http://direct.ecency.com</link><image><url>http://direct.ecency.com/logo512.png</url><title>RSS Feed</title><link>http://direct.ecency.com</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 13 May 2026 08:21:26 GMT</lastBuildDate><atom:link href="http://direct.ecency.com/@thebluefish/rss" rel="self" type="application/rss+xml"/><item><title><![CDATA[Using Express middleware for authentication]]></title><description><![CDATA[For the longest time, my bot platform was secured by a simple hard-coded password check on the client-side. This was OK for a placeholder, but isn't security by any means. In the recent rewrite, I implemented]]></description><link>http://direct.ecency.com/nodejs/@thebluefish/using-express-middleware-for-authentication</link><guid isPermaLink="true">http://direct.ecency.com/nodejs/@thebluefish/using-express-middleware-for-authentication</guid><category><![CDATA[nodejs]]></category><dc:creator><![CDATA[thebluefish]]></dc:creator><pubDate>Wed, 21 Mar 2018 17:27:24 GMT</pubDate></item><item><title><![CDATA[Crypto platform update - Refactoring the backend service]]></title><description><![CDATA[As I briefly touched in my original post, my platform is roughly separated into a front-end webapp and a back-end set of node services. For my original tests, this served its purpose well enough. I was]]></description><link>http://direct.ecency.com/crypto/@thebluefish/crypto-platform-update-refactoring-the-backend-service</link><guid isPermaLink="true">http://direct.ecency.com/crypto/@thebluefish/crypto-platform-update-refactoring-the-backend-service</guid><category><![CDATA[crypto]]></category><dc:creator><![CDATA[thebluefish]]></dc:creator><pubDate>Tue, 18 Jul 2017 22:36:48 GMT</pubDate></item><item><title><![CDATA[Progress update on crypto trade app - Exchange Health]]></title><description><![CDATA[One of the important aspects of any trade platform is quick, reliable information. My goal when building my app is to stay as informed as possible about the current climate of crypto-currencies. My progress]]></description><link>http://direct.ecency.com/crypto/@thebluefish/progress-update-on-crypto-trade-app-exchange-health</link><guid isPermaLink="true">http://direct.ecency.com/crypto/@thebluefish/progress-update-on-crypto-trade-app-exchange-health</guid><category><![CDATA[crypto]]></category><dc:creator><![CDATA[thebluefish]]></dc:creator><pubDate>Sun, 16 Jul 2017 00:54:24 GMT</pubDate><enclosure url="https://images.ecency.com/p/2gsjgna1uruvUuS7ndh9YqVwYGPLVszbFLwwpAYXZoapUbwEAexuKbGj9cAoGJoP36qwQMSr14CZCqoAanmLFS36A3H56mP5Qc35KgqoAccFJhprY6?format=match&amp;mode=fit" length="0" type="false"/></item><item><title><![CDATA[Extending Vue components for services]]></title><description><![CDATA[I have begun rewriting a basic app to handle all of my needs in trading crypto-currencies. I am working in nodejs, wrapping it in Electron + Webpack, with a SPA built on vue + vuex + vue-router + vue-loader.]]></description><link>http://direct.ecency.com/nodejs/@thebluefish/extending-vue-components-for-services</link><guid isPermaLink="true">http://direct.ecency.com/nodejs/@thebluefish/extending-vue-components-for-services</guid><category><![CDATA[nodejs]]></category><dc:creator><![CDATA[thebluefish]]></dc:creator><pubDate>Fri, 30 Jun 2017 22:34:42 GMT</pubDate></item></channel></rss>