<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by John Brett on Medium]]></title>
        <description><![CDATA[Stories by John Brett on Medium]]></description>
        <link>https://medium.com/@johnbrett?source=rss-df2bba60649b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*23bXC6E4kMUcEgP9CTniSQ.jpeg</url>
            <title>Stories by John Brett on Medium</title>
            <link>https://medium.com/@johnbrett?source=rss-df2bba60649b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:40:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johnbrett/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Nodejs Remote Server Debugging]]></title>
            <link>https://medium.com/@johnbrett/nodejs-remote-server-debugging-6b67298f1ab9?source=rss-df2bba60649b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b67298f1ab9</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[John Brett]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 10:38:35 GMT</pubDate>
            <atom:updated>2017-06-13T10:38:35.984Z</atom:updated>
            <content:encoded><![CDATA[<p>Trying to debug a remote server with node -inspect is a very handy feature. I had a little trouble getting set up so this is to help anyone who hits the same issue.</p><p>First set up ssh port forwarding:</p><pre>ssh -nNT -L 9229:127.0.0.1:9229 user@remote-server.com</pre><p>On the remote server, launch it with:</p><pre>node --inspect myapp.js</pre><p>In chrome, open:</p><pre>chrome://inspect/#devices</pre><p>and click “Open dedicated Devtools for Node”. And you’re in :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b67298f1ab9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node-gyp rebuild failing on Amazon Linux]]></title>
            <link>https://medium.com/@johnbrett/node-gyp-rebuild-failing-on-amazon-linux-38453b62db95?source=rss-df2bba60649b------2</link>
            <guid isPermaLink="false">https://medium.com/p/38453b62db95</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[John Brett]]></dc:creator>
            <pubDate>Mon, 15 May 2017 14:26:38 GMT</pubDate>
            <atom:updated>2017-05-15T14:26:38.657Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a personal reminder for when I hit this issue again.</p><p>node-gyp rebuild fails to execute on AWS AMI until the necessary packages are installed. Here’s how to install them:</p><p>yum install make glibc-devel gcc patch</p><p>Answer was from here: <a href="https://serverfault.com/questions/204893/aws-ec2-and-build-essential">https://serverfault.com/questions/204893/aws-ec2-and-build-essential</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38453b62db95" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create react app push state nginx config]]></title>
            <link>https://medium.com/@johnbrett/create-react-app-push-state-nginx-config-a9f7530621c1?source=rss-df2bba60649b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9f7530621c1</guid>
            <category><![CDATA[create-react-app]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[John Brett]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 23:08:59 GMT</pubDate>
            <atom:updated>2017-02-07T23:10:01.770Z</atom:updated>
            <content:encoded><![CDATA[<p>I learned today that Create-react-app’s production build needs to sit behind a HTML5 pushstate enabled server (the build script drops a hint recommending the <a href="https://github.com/scottcorgan/pushstate-server"><strong>pushstate-server</strong></a> npm package). The reasoning here is if you make a request for <a href="https://johnbrett.me/"><strong>https://johnbrett.me/user/123</strong></a>, nginx (or most web servers) will look for a file inside your apps root directory, for a <strong>user</strong> directory containing the file <strong>123</strong>.</p><p>Below is the nginx config to replicate <strong>pushstate-server</strong>’s functionality, but through nginx. This cost me some time to figure out, so posting it here so I remember in future and to be of use to anyone else who hit this issue.</p><pre># Default server configuration</pre><pre>server {<br>  listen 80 default_server;</pre><pre>  server_name johnbrett.me;</pre><pre>  root /var/www/app;</pre><pre>  # Routes without file extension e.g. /user/1<br>  location / {<br>    try_files $uri /index.html;<br>  }</pre><pre>  # 404 if a file is requested (so the main app isn&#39;t served)<br>  location ~ ^.+\..+$ {<br>    try_files $uri =404;<br>  }</pre><pre>  # OPTIONAL: For an API server you want to proxy<br>  location /api {<br>    proxy_pass <a href="http://localhost:8081/">http://localhost:8081</a>;<br>    proxy_http_version 1.1;<br>    proxy_set_header Upgrade $http_upgrade;<br>    proxy_set_header Connection ‘upgrade’;<br>    proxy_set_header Host $host;<br>    proxy_cache_bypass $http_upgrade;<br>  }</pre><pre>}</pre><p>You can test the config with the following:</p><pre>$ sudo nginx -t</pre><p>And restart the nginx server with:</p><pre>$ sudo systemctl restart nginx</pre><p>This was useful: <a href="https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04">https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9f7530621c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ads reward clicks and views, sponsorship rewards quality]]></title>
            <link>https://medium.com/sponsorama/ads-reward-clicks-and-views-sponsorship-rewards-quality-a6051ab76984?source=rss-df2bba60649b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6051ab76984</guid>
            <category><![CDATA[monetization]]></category>
            <category><![CDATA[sponsorship]]></category>
            <category><![CDATA[advertising]]></category>
            <category><![CDATA[ad-blocking]]></category>
            <dc:creator><![CDATA[John Brett]]></dc:creator>
            <pubDate>Thu, 06 Oct 2016 16:21:46 GMT</pubDate>
            <atom:updated>2016-10-06T16:35:23.007Z</atom:updated>
            <content:encoded><![CDATA[<p>There is an epidemic of low-quality content on the web today — lets look at <strong>why</strong> and <strong>how</strong> we can fix it.</p><p>Display advertising is the most widely used business model for monetization of content on the web today. Since the advertising industry incentivises clicks and pageviews over quality content and user engagement, publications often sacrifice the quality of their content in order to get as many site visitors as possible. Often via <a href="http://www.bbc.com/news/business-29322578">sleazy techniques like clickbait</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*H8KsU5NqyaLzbE2SdEpCUA.png" /><figcaption>A far too often encounter on the web today</figcaption></figure><p>Combine this with a low cost of publishing and easy access to consumers through channels like Facebook, company blogs, newsletter curation services, we see an explosion of low quality content and publications on the web today. Just as search and social media algorithms are starting to catch up and punish the “You won’t believe what happened next” articles, we see new techniques emerge like leaving out an important detail in a headline, “this celebrity is the latest to endorse…”. Just to spark enough curiosity to “earn” a click. <strong>As much as we try, tweaks to a search engine algorithm won’t change an entire culture of worshipping the page view count</strong>.</p><p>As a result of years of this, much consumer frustration and the ever rising competition for a user’s attention we’re seeing content consumers fight back. Ad blocker usage is on the rise. Non-ad based platforms like Medium are growing in usage. We’re even seeing browsers created to support alternative business models like the Brave Browser which will use micro-payments based on user behaviour and feedback instead of page views. <a href="https://medium.com/sponsorama/why-we-created-the-worlds-first-sponsorfunding-platform-e14ae293b7e0">My cofounder wrote about this last week</a>, but in this post I wanted to talk specifically how this affects publications and how sponsorship can improve content for us consumers.</p><h3>Sponsorship to the rescue</h3><p>One solution that has been available since before the days of the web, which unfortunately hasn’t seen much (if any) innovation, is sponsorship. Sponsorship is often a grey area and confused with ads. So just to clarify; by sponsorship I mean when a brand pays a publication, event or service in exchange for it’s name being associated in some manner, whether it be to contribute for running costs or for profit of the content creator. It’s usually not in an overly commercial or quick reward manner and almost always requires a direct relationship between the sponsor and sponsored party.</p><p>So if we imagine a world where sponsorship was the main source of monetization instead of ads, how would this change the game of advertising, brand building and monetization for publications?</p><h4>Publications would have greater responsibility for what brands they endorse.</h4><p>With most ad networks you provide a “window” or “space”; and you leave it up to the ad network to decide what’s displayed there. Usually, this decision is based on a per-user basis, through invasive user tracking. With sponsorship on the other hand, content producers and publications have to decide what brands are relevant for their readers — and not let a third party make that decision. This would result in users respecting the brands supporting publications they like. They would have greater trust when it comes to clicking links compared to today’s state of affairs which is ad blocking and ignoring ads.</p><p>The benefit of this: brands are more trustworthy and henceforth are marketed more.</p><h4>Brands want to be associated with better content.</h4><p>Just as importantly, brands also need to decide what content they want their logo linked with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*VS_kaIkpvfyiRz_Xg_vO2A.png" /><figcaption>Did this bank know it was going to have it’s logo next to this type of content?</figcaption></figure><p>As a founder of a company looking to build trust and credibility in the world, I don’t want our logo or name associated with questionable content, nor do I want it frustrating users through splash screens or banner ads. I want it recognised for benefitting potential users before we even talk to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*IcESMz0yDhzsTqTCub0VXA.png" /><figcaption>Sponsorship done right: Intercom want to be endorsed by great services like Product Hunt. “We use intercom” is far more effective.</figcaption></figure><p>The benefits of sponsorship as a source of monetization:</p><ul><li>Better quality content gets funded more.</li><li>Trustworthy brands get better marketing and endorsements.</li></ul><h3>The challenges of Sponsorship</h3><p>So if sponsorship is so great, why isn’t it used more? Well there are plenty of reasons:</p><ul><li>Building personal relationships is hard. It’s a traditional sales process both for brands and projects.</li><li>Content producers / service creators often just want to produce content, not deal with the business side. This often leads to using agencies or turning to ads.</li><li>Ad networks have made using advertisements so easy people often just resort to this, as I’ve been told by some content creators. This is even when some ad networks take in the region of 40% of ad revenue!</li><li>It’s much harder to measure how effective a sponsorship campaign has been vs ads. Without stats to back up a campaign, it can often be difficult to justify the spend.</li></ul><h3>Sponsorship simplified</h3><p>I want a better web. A better web means better content and better promotion for the brands that support that too. As part of trying to achieve this goal, I’ve been part of the team building a new platform called <a href="https://sponsorama.com/">Sponsorama, <strong>The Marketplace for Sponsorship</strong></a>. Our goal is to make the entire sponsorship workflow much easier — discovery, discussion, payment, invoicing and planning. It is one of the many ways we want to improve the web as a whole. So far it’s been a fantastic experience talking to awesome brands and projects and helping them connect.</p><p>I believe this will lead to a new age for brands to have a means to build awareness and grow via a method that will improve the web. When I see a service I like, being sponsored by a brand I know, it builds trust, respect and admiration.</p><p>Fortunately Sponsorama isn’t limited to just publications or content creators — digital products, open source, podcasts and newsletters can all grow via sponsorship. Are you a company who wants to grow in a way that can improve the web and establish a brand that customers love? Or how about a project looking to monetize in a manner that’s best for your users? Then you should join our early access program: <a href="https://sponsorama.com/signup">https://sponsorama.com/signup</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*j3IAlNLCjj3FpajrHrHaiQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6051ab76984" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sponsorama/ads-reward-clicks-and-views-sponsorship-rewards-quality-a6051ab76984">Ads reward clicks and views, sponsorship rewards quality</a> was originally published in <a href="https://medium.com/sponsorama">Sponsorama</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>