<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #services</title>
    <link>/tags/services/</link>
    <description>Recent bookmarks tagged #services</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:48 +0000</lastBuildDate>
    <item>
      <title>Micro Service Architecture</title>
      <link>http://yobriefca.se/blog/2013/04/29/micro-service-architecture</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #Unread #imported:pinboard #microservices #msa #services #soa&lt;/p&gt;</description>
      <pubDate>Tue, 18 Mar 2014 03:05:18 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:24607</guid>
      <category>Unread</category>
      <category>imported:pinboard</category>
      <category>microservices</category>
      <category>msa</category>
      <category>services</category>
      <category>soa</category>
    </item>
    <item>
      <title>Secure Your REST API... The Right Way | Stormpath</title>
      <link>http://www.stormpath.com/blog/secure-your-rest-api-right-way</link>
      <description>We already showed you how to build a Beautiful REST+JSON API, but how do you secure your API?  At Stormpath we spent 18 months researching best practices, implementing them in the Stormpath API, and figuring out what works. Here’s our playbook on how to secure a REST API.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #auth #gluecon #imported:pinboard #rest #security #services&lt;/p&gt;</description>
      <pubDate>Thu, 23 May 2013 00:21:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23678</guid>
      <category>apis</category>
      <category>auth</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>rest</category>
      <category>security</category>
      <category>services</category>
    </item>
    <item>
      <title>Stormpath | Authentication and User Management for Developers</title>
      <link>http://www.stormpath.com/</link>
      <description>User Management and Authentication for Developers&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #authentication #authorization #gluecon #imported:pinboard #services #stormpath&lt;/p&gt;</description>
      <pubDate>Thu, 23 May 2013 00:11:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32311</guid>
      <category>apis</category>
      <category>authentication</category>
      <category>authorization</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>services</category>
      <category>stormpath</category>
    </item>
    <item>
      <title>Stormpath | Authentication and User Management for Developers</title>
      <link>http://www.stormpath.com</link>
      <description>User Management and Authentication for Developers&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #authentication #authorization #gluecon #services #stormpath&lt;/p&gt;</description>
      <pubDate>Thu, 23 May 2013 00:11:25 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23675</guid>
      <category>apis</category>
      <category>authentication</category>
      <category>authorization</category>
      <category>gluecon</category>
      <category>services</category>
      <category>stormpath</category>
    </item>
    <item>
      <title>Mashape - The Cloud API Hub</title>
      <link>https://www.mashape.com/</link>
      <description>Consume and distribute software in the cloud on the largest API hub in the universe.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #cloud #gluecon #imported:pinboard #services&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 20:30:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32320</guid>
      <category>apis</category>
      <category>cloud</category>
      <category>gluecon</category>
      <category>imported:pinboard</category>
      <category>services</category>
    </item>
    <item>
      <title>Mashape - The Cloud API Hub</title>
      <link>https://www.mashape.com</link>
      <description>Consume and distribute software in the cloud on the largest API hub in the universe.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apis #cloud #gluecon #services&lt;/p&gt;</description>
      <pubDate>Wed, 22 May 2013 20:30:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23659</guid>
      <category>apis</category>
      <category>cloud</category>
      <category>gluecon</category>
      <category>services</category>
    </item>
    <item>
      <title>InLinkz. Blogging tools for link-ups, blog hops and product lists</title>
      <link>http://www.inlinkz.com/?refId=13210</link>
      <description>It is a widget that is inserted in your blog and allows you to receive link submissions from your readers&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #imported:pinboard #links #services #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 09 Jan 2013 13:55:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23025</guid>
      <category>imported:pinboard</category>
      <category>links</category>
      <category>services</category>
      <category>webdev</category>
    </item>
    <item>
      <title>baudehlo/Haraka · GitHub</title>
      <link>https://github.com/baudehlo/Haraka</link>
      <description>Haraka is an SMTP server which uses a plugin architecture to implement most of its functionality. It uses a highly scalable event model to be able to cope with thousands of concurrent connections. Plugins are written in Javascript using Node.js, and as such perform extremely quickly. The core Haraka framework is capable of processing thousands of messages per second on the right hardware.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #email #haraka #imported:pinboard #js #mail #node #nodejs #services&lt;/p&gt;</description>
      <pubDate>Fri, 14 Dec 2012 20:46:06 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:22852</guid>
      <category>email</category>
      <category>haraka</category>
      <category>imported:pinboard</category>
      <category>js</category>
      <category>mail</category>
      <category>node</category>
      <category>nodejs</category>
      <category>services</category>
    </item>
    <item>
      <title>Proposed standards for the care and feeding of user generated content – Jeffrey Zeldman Presents The Daily Report</title>
      <link>http://www.zeldman.com/2012/07/25/proposed-standards-for-the-care-and-feeding-of-user-generated-content/</link>
      <description>Treat our data like it matters. Keep it secure and protect our privacy, of course—but also maintain serious backups and respect our choice to delete any information we’ve contributed.&#xD;&#xA;No upload without download. Build in export capabilities from day one.&#xD;&#xA;If you close a system, support data rescue. Provide one financial quarter’s notice between announcing the shutdown and destroying any user-contributed content, public or private, and offer data export during this period. And beyond that three months? Make user-contributed content available for media-cost purchase for one year after shutdown.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #cloud #data #imported:pinboard #services #to:fb&lt;/p&gt;</description>
      <pubDate>Thu, 26 Jul 2012 05:20:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32714</guid>
      <category>cloud</category>
      <category>data</category>
      <category>imported:pinboard</category>
      <category>services</category>
      <category>to:fb</category>
    </item>
    <item>
      <title>Proposed standards for the care and feeding of user generated content – Jeffrey Zeldman Presents The Daily Report</title>
      <link>http://www.zeldman.com/2012/07/25/proposed-standards-for-the-care-and-feeding-of-user-generated-content</link>
      <description>Treat our data like it matters. Keep it secure and protect our privacy, of course—but also maintain serious backups and respect our choice to delete any information we’ve contributed.&#xD;&#xA;No upload without download. Build in export capabilities from day one.&#xD;&#xA;If you close a system, support data rescue. Provide one financial quarter’s notice between announcing the shutdown and destroying any user-contributed content, public or private, and offer data export during this period. And beyond that three months? Make user-contributed content available for media-cost purchase for one year after shutdown.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #cloud #data #services #to:fb&lt;/p&gt;</description>
      <pubDate>Thu, 26 Jul 2012 05:20:27 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:22373</guid>
      <category>cloud</category>
      <category>data</category>
      <category>services</category>
      <category>to:fb</category>
    </item>
    <item>
      <title>Don&#39;t Be A Free User (Pinboard Blog)</title>
      <link>http://blog.pinboard.in/2011/12/don_t_be_a_free_user</link>
      <description>These projects are all very different, but the dynamic is the same. Someone builds a cool, free product, it gets popular, and that popularity attracts a buyer. The new owner shuts the product down and the founders issue a glowing press release about how excited they are about synergies going forward. They are never heard from again.&#xD;&#xA;&#xD;&#xA;Whether or not this is done in good faith, in practice this kind of &#39;exit event&#39; is a pump-and-dump scheme. The very popularity that attracts a buyer also makes the project financially unsustainable. The owners cash out, the acquirer gets some good engineers, and the users get screwed.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #business #economics #free #fuckthecloud #pinboard #services #shutupandtakemymoney #web #web20&lt;/p&gt;</description>
      <pubDate>Tue, 06 Dec 2011 22:25:16 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:20158</guid>
      <category>business</category>
      <category>economics</category>
      <category>free</category>
      <category>fuckthecloud</category>
      <category>pinboard</category>
      <category>services</category>
      <category>shutupandtakemymoney</category>
      <category>web</category>
      <category>web20</category>
    </item>
    <item>
      <title>Calepin</title>
      <link>http://calepin.co</link>
      <description>Publishing for writers who love Markdown and Dropbox&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #blogging #calepin #dropbox #markdown #services #tech #writing&lt;/p&gt;</description>
      <pubDate>Fri, 25 Nov 2011 05:18:11 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:19928</guid>
      <category>blogging</category>
      <category>calepin</category>
      <category>dropbox</category>
      <category>markdown</category>
      <category>services</category>
      <category>tech</category>
      <category>writing</category>
    </item>
    <item>
      <title>Packrati.us = Twitter + Delicious</title>
      <link>http://packrati.us</link>
      <description>This is what I wish Delicious had done with Twitter.  pinboard.in has this built-in, by the way. &#34;This site provides a simple bookmarking service. We follow your twitter feed, and whenever one of your tweets contains URLs, we add them to your delicious.com bookmarks. Optionally, bookmark URLs in @replies to you. We&#39;ll even add a delicious tag identifying the sender if you like.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #bookmarking #delicious #services #twitter&lt;/p&gt;</description>
      <pubDate>Wed, 10 Mar 2010 16:09:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12968</guid>
      <category>bookmarking</category>
      <category>delicious</category>
      <category>services</category>
      <category>twitter</category>
    </item>
    <item>
      <title>Sterling Editing</title>
      <link>http://www.sterlingediting.com</link>
      <description>&#34;Editing, mentoring and coaching for writers&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #editing #services #writing&lt;/p&gt;</description>
      <pubDate>Tue, 02 Mar 2010 18:03:13 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12940</guid>
      <category>editing</category>
      <category>services</category>
      <category>writing</category>
    </item>
    <item>
      <title>Public Open Source Services / FrontPage</title>
      <link>http://poss.gliderlab.com</link>
      <description>&#34;You use the same Google Merchant account that App Engine debits as the one that accepts donations. This way no bank account is involved. Then you track the money that goes into the account (using the Google Merchant IPN equivalent). Then you look at your usage stats from the App Engine panel and predicate future usage trends. Then calculate the cost per month. Then divide the cash in the account by that and you have how long the service will run. You make this visible on all pages (at the bottom, say) that this service will run for X months, &#34;Pay now to keep it running.&#34; You accept any amount, but you are completely clear about what the costs are. And this is all automated.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #api #appengine #cloud #opensource #saas #services #webhooks&lt;/p&gt;</description>
      <pubDate>Tue, 26 Jan 2010 22:48:48 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12756</guid>
      <category>api</category>
      <category>appengine</category>
      <category>cloud</category>
      <category>opensource</category>
      <category>saas</category>
      <category>services</category>
      <category>webhooks</category>
    </item>
  </channel>
</rss>
