<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://unraid.net/blog/ultimate-energy-efficient-build"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/PleX/comments/1hgr0ao/would_either_of_these_be_a_good_option_for_a_plex/"/>
	<rdf:li rdf:resource="https://byroot.github.io/ruby/performance/2025/03/04/the-pitchfork-story.html"/>
	<rdf:li rdf:resource="https://www.hardkernel.com/shop/odroid-h4/"/>
	<rdf:li rdf:resource="https://ounapuu.ee/posts/2023/10/09/zimaboard/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=34612277&amp;s=03"/>
	<rdf:li rdf:resource="https://fediverse.randomfoo.net/notice/ARAAtsSHL6jVTe4JBA"/>
	<rdf:li rdf:resource="https://www.hannahtech.co/post/turn-your-old-cracked-android-phone-into-a-backup-server-urbackup-linux-deploy-tutorial-part-i"/>
	<rdf:li rdf:resource="https://talawah.io/blog/extreme-http-performance-tuning-one-point-two-million/"/>
	<rdf:li rdf:resource="https://blog.cloudflare.com/a-free-argo-tunnel-for-your-next-project/"/>
	<rdf:li rdf:resource="https://console.cloud.google.com/cloudshell/editor?pli=1&amp;supportedpurview=project&amp;shellonly=true"/>
	<rdf:li rdf:resource="https://medium.com/@mubarak.seyed/netty-at-layer-powering-client-api-2a6ca3617d48#.91mjjdwh2"/>
	<rdf:li rdf:resource="https://github.com/amscanne/huptime"/>
	<rdf:li rdf:resource="https://code.facebook.com/posts/1503205539947302/introducing-proxygen-facebook-s-c-http-framework/"/>
	<rdf:li rdf:resource="http://webrtchacks.com/coturn/"/>
	<rdf:li rdf:resource="http://arstechnica.com/tech-policy/2014/07/obama-administration-says-the-worlds-servers-are-ours/"/>
	<rdf:li rdf:resource="http://blog.phusion.nl/2013/11/11/duplicity-s3-easy-cheap-encrypted-automated-full-disk-backups-for-your-servers/"/>
	<rdf:li rdf:resource="http://www.wired.com/threatlevel/2014/01/tormail/"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work"/>
	<rdf:li rdf:resource="http://www.scribd.com/doc/56651812/kreitz-spotify-kth11"/>
	<rdf:li rdf:resource="https://www.ssllabs.com/ssldb/index.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://unraid.net/blog/ultimate-energy-efficient-build">
    <title>The Ultimate Energy-Efficient Unraid Server Build</title>
    <dc:date>2025-04-01T10:37:52+00:00</dc:date>
    <link>https://unraid.net/blog/ultimate-energy-efficient-build</link>
    <dc:creator>jm</dc:creator><description><![CDATA["The goal of this build was to create a powerful 90TB server that idles at just 20-25 watts, proving that substantial storage capacity doesn’t have to come with massive power consumption." -- Extremely relevant to my current interests!

"At the core of this build is an N100-based motherboard, featuring six SATA ports and two NVMe slots. Priced at around $150-180, it provides excellent value for those looking to build energy-conscious storage solutions. To maximize storage connectivity, an NVMe to SATA adapter was used along with 32 GB of DDR5 RAM."]]></description>
<dc:subject>ssd hard-disks nas storage disks hardware n100 servers home low-power power sata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:be133e2c0dfb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hard-disks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:n100"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:low-power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:power"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/PleX/comments/1hgr0ao/would_either_of_these_be_a_good_option_for_a_plex/">
    <title>Would either of these be a good option for a Plex server? : r/PleX</title>
    <dc:date>2025-03-27T10:42:32+00:00</dc:date>
    <link>https://www.reddit.com/r/PleX/comments/1hgr0ao/would_either_of_these_be_a_good_option_for_a_plex/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A thread of hardware tips for low-cost home servers, optimising for Plex transcodes.

tl;dr: 7th gen Intel CPUs are minimum for hardware transcoding; 8th gen better.   8500T are apparently a great 8th gen CPU; 6 cores vs 4 cores for an N100, and an 8500T based system will run with 35 watt max load, idling at 7-10 watts.]]></description>
<dc:subject>hardware shopping home servers intel to-get</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ce9cb3103a93/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:shopping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:intel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:to-get"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://byroot.github.io/ruby/performance/2025/03/04/the-pitchfork-story.html">
    <title>Pitchfork</title>
    <dc:date>2025-03-21T10:30:41+00:00</dc:date>
    <link>https://byroot.github.io/ruby/performance/2025/03/04/the-pitchfork-story.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[An amazing journey through Ruby heap memory optimization, from one of the experts at Shopify, who are heavy users of Rails.  Using cleverly-timed fork(2) usage, it's possible to optimize memory usage in a Rails app and discard a lot of performance/heap overhead caused by lazy loading and poorly-timed in-memory caching.

This very much reminds me of optimising similar issues in Perl-land, back in the day -- and really helps me appreciate how easy the modern JVM world has it, in comparison.  There's a lot of complaints to be made about the complexity of optimising JVM garbage collection settings, but this kind of problem is malleable there without a fundamental architectural rewrite like this approach.]]></description>
<dc:subject>ruby performance optimisation optimization heap memory fork forking http services servers monolith rails gc</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2839524a8511/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:optimisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:heap"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:memory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fork"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:forking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:monolith"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gc"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.hardkernel.com/shop/odroid-h4/">
    <title>ODROID-H4+</title>
    <dc:date>2025-01-28T18:13:00+00:00</dc:date>
    <link>https://www.hardkernel.com/shop/odroid-h4/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The next generation of the excellent ODROID SBCs; based on Intel's N97 architecture, AVX2 extensions, faster DRAM, 4 SATA ports, and up to 48GB of RAM. 

Significantly beefier in general, reportedly around the EUR180 mark in price.]]></description>
<dc:subject>odroid sbcs n97 hardware home devices servers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f3284ed9dc84/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:odroid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sbcs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:n97"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ounapuu.ee/posts/2023/10/09/zimaboard/">
    <title>Zimaboard: the closest thing to my dream home server setup</title>
    <dc:date>2023-10-10T08:42:23+00:00</dc:date>
    <link>https://ounapuu.ee/posts/2023/10/09/zimaboard/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Helpful review of this new single-board computer. 8GB of RAM, 32GB of eMMC storage and a quad-core Intel Celeron N3450 CPU; built-in heatsink for totally silent operation; low power usage (2-15W typical power usage); 2x SATA or NVMe for SSDs.

Ideal profile for a home server, in my opinion; I've already gone for an ODroid-HC4, but possibly on the next rev I may take a look at the Zimaboards as an alternative. (ODroids are pretty great though.)]]></description>
<dc:subject>hardware home servers sbc zimaboard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:02638a659783/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sbc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:zimaboard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=34612277&amp;s=03">
    <title>Raspberry Pi alternatives</title>
    <dc:date>2023-02-02T10:58:47+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=34612277&amp;s=03</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Interesting thread on the current state of low-cost/low-power server hardware; I didn't realise thin client boxes were so viable for this use case, these days.  (I've just replaced my current home server with an ODROID HC4, and I'm absolutely delighted with it, though...)]]></description>
<dc:subject>servers home gadgets hardware linux raspberry-pi</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7ed216cab297/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gadgets"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:raspberry-pi"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://fediverse.randomfoo.net/notice/ARAAtsSHL6jVTe4JBA">
    <title>Caddy</title>
    <dc:date>2023-01-04T11:42:53+00:00</dc:date>
    <link>https://fediverse.randomfoo.net/notice/ARAAtsSHL6jVTe4JBA</link>
    <dc:creator>jm</dc:creator><description><![CDATA[lhl likes Caddy:

<blockquote>Caddy https://caddyserver.com/ came up in conversation earlier today. It's been my favorite reverse proxy/web server for the past few years because of how simple it is to setup and for it's automagic LetsEncrypt setup. (This post is actually being pushed through Caddy on my fediverse server, and was basically the easiest part of the setup). For those interested, it performs pretty competitively with nginx: https://blog.tjll.net/reverse-proxy-hot-dog-eating-contest-caddy-vs-nginx/ but IMO the main selling point (why I first installed it) was the automagic HTTPS setup: https://caddyserver.com/docs/automatic-https</blockquote>

]]></description>
<dc:subject>caddy reverse-proxies ops http https lets-encrypt servers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:dbcc32a62424/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:caddy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:reverse-proxies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lets-encrypt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.hannahtech.co/post/turn-your-old-cracked-android-phone-into-a-backup-server-urbackup-linux-deploy-tutorial-part-i">
    <title>Turn Your Old, Cracked Android Phone Into a Backup Server</title>
    <dc:date>2021-06-21T16:34:16+00:00</dc:date>
    <link>https://www.hannahtech.co/post/turn-your-old-cracked-android-phone-into-a-backup-server-urbackup-linux-deploy-tutorial-part-i</link>
    <dc:creator>jm</dc:creator><description><![CDATA[It's gratifying to see that an apk called 'Linux Deploy' will run a chrooted Debian install on a rooted Android phone -- that's a great way to reuse and recycle old, nearly-dead hardware]]></description>
<dc:subject>backup android servers linux ops home</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3813f67ce138/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:home"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://talawah.io/blog/extreme-http-performance-tuning-one-point-two-million/">
    <title>Extreme HTTP Performance Tuning: 1.2M API req/s on a 4 vCPU EC2 Instance | talawah.io</title>
    <dc:date>2021-05-21T08:54:01+00:00</dc:date>
    <link>https://talawah.io/blog/extreme-http-performance-tuning-one-point-two-million/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is very cool. Updating the old "C10K" problem space to C1.2M -- the current state of Linux userspace networking -- using libreactor and a whole load of up-to-date tweaks.

Interesting to note that this scale is feasible to run in Docker (using --network=host, of course).
]]></description>
<dc:subject>http servers c10k linux performance scalability ops tuning libreactor networking tcp</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:022774113a4b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:c10k"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tuning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:libreactor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tcp"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.cloudflare.com/a-free-argo-tunnel-for-your-next-project/">
    <title>A free Argo Tunnel for your next project</title>
    <dc:date>2019-06-18T11:27:34+00:00</dc:date>
    <link>https://blog.cloudflare.com/a-free-argo-tunnel-for-your-next-project/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Argo Tunnel lets you expose a server to the Internet without opening any ports. The service runs a lightweight process on your server that creates outbound tunnels to the Cloudflare network. Instead of managing DNS, network, and firewall complexity, Argo Tunnel helps administrators serve traffic from their origin through Cloudflare with a single command. [....]

Starting today, any user, even those without a Cloudflare account, can try this new method of connecting their server to the Internet. Argo Tunnel can now be used in a free model that will create a new URL, known only to you, that will proxy traffic to your server. We’re excited to make connecting a server to the Internet more accessible for everyone.</blockquote>

]]></description>
<dc:subject>cloudflare internet tunnel servers ports tunnelling ops free</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:151704816f99/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cloudflare"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tunnel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ports"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tunnelling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:free"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://console.cloud.google.com/cloudshell/editor?pli=1&amp;supportedpurview=project&amp;shellonly=true">
    <title>Cloud Shell - Google Cloud Platform</title>
    <dc:date>2019-03-25T21:42:53+00:00</dc:date>
    <link>https://console.cloud.google.com/cloudshell/editor?pli=1&amp;supportedpurview=project&amp;shellonly=true</link>
    <dc:creator>jm</dc:creator><description><![CDATA[I had no idea about this -- every google user has instant in-browser shell access to a Linux VM with 1.7GB of RAM]]></description>
<dc:subject>shell servers linux google gcp cloudshell</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:b1154a01a4bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:shell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gcp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cloudshell"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@mubarak.seyed/netty-at-layer-powering-client-api-2a6ca3617d48#.91mjjdwh2">
    <title>How Netty is used at Layer</title>
    <dc:date>2015-10-22T08:26:14+00:00</dc:date>
    <link>https://medium.com/@mubarak.seyed/netty-at-layer-powering-client-api-2a6ca3617d48#.91mjjdwh2</link>
    <dc:creator>jm</dc:creator><description><![CDATA[pretty conventional HTTP/1.1, WebSockets and HTTP/2 front-end services with modern Netty practices]]></description>
<dc:subject>netty http api-services coding java servers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2a9e57061ee5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netty"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:api-services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/amscanne/huptime">
    <title>huptime</title>
    <dc:date>2015-01-25T23:50:05+00:00</dc:date>
    <link>https://github.com/amscanne/huptime</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Nice trick -- wrap servers with a libc wrapper to intercept bind(2) and accept(2) calls, so that transparent restarts becode possible]]></description>
<dc:subject>linux ops servers uptime restarting libc bind accept sockets</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:8dc351b013f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:uptime"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:restarting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:libc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bind"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:accept"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sockets"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.facebook.com/posts/1503205539947302/introducing-proxygen-facebook-s-c-http-framework/">
    <title>Introducing Proxygen, Facebook's C++ HTTP framework</title>
    <dc:date>2014-11-07T14:58:54+00:00</dc:date>
    <link>https://code.facebook.com/posts/1503205539947302/introducing-proxygen-facebook-s-c-http-framework/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Facebook's take on libevent, I guess:

<blockquote>We are excited to announce the release of Proxygen, a collection of C++ HTTP libraries, including an easy-to-use HTTP server. In addition to HTTP/1.1, Proxygen (rhymes with "oxygen") supports SPDY/3 and SPDY/3.1. We are also iterating and developing support for HTTP/2.

Proxygen is not designed to replace Apache or nginx — those projects focus on building extremely flexible HTTP servers written in C that offer good performance but almost overwhelming amounts of configurability. Instead, we focused on building a high performance C++ HTTP framework with sensible defaults that includes both server and client code and that's easy to integrate into existing applications. We want to help more people build and deploy high performance C++ HTTP services, and we believe that Proxygen is a great framework to do so.</blockquote>

]]></description>
<dc:subject>c++ facebook http servers libevent https spdy proxygen libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:868926651da2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:c++"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:libevent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spdy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:proxygen"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://webrtchacks.com/coturn/">
    <title>webrtcH4cKS: ~ coTURN: the open-source multi-tenant TURN/STUN server you were looking for</title>
    <dc:date>2014-10-14T16:05:52+00:00</dc:date>
    <link>http://webrtchacks.com/coturn/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Last year we interviewed Oleg Moskalenko and presented the rfc5766-turn-server project, which is a free open source and extremely popular implementation of TURN and STURN server. A few months later we even discovered Amazon is using this project to power its Mayday service. Since then, a number of features beyond the original RFC 5766 have been defined at the IETF and a new open-source project was born: the coTURN project.</blockquote>

]]></description>
<dc:subject>webrtc turn sturn rfc-5766 push nat stun firewalls voip servers internet</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:cb7a2ddf8521/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:webrtc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:turn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sturn"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rfc-5766"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:push"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stun"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:firewalls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:voip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arstechnica.com/tech-policy/2014/07/obama-administration-says-the-worlds-servers-are-ours/">
    <title>Obama administration says the world’s servers are ours | Ars Technica</title>
    <dc:date>2014-07-15T13:02:22+00:00</dc:date>
    <link>http://arstechnica.com/tech-policy/2014/07/obama-administration-says-the-worlds-servers-are-ours/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>In its briefs filed last week, the US government said that content stored online doesn't enjoy the same type of Fourth Amendment protections as data stored in the physical world. The government cited (PDF) the Stored Communications Act (SCA), a President Ronald Reagan-era regulation.</blockquote>

Michael McDowell has filed a declaration in support of MS' position (attached to that article a couple of paras down) suggesting that the MLAT between the US and Ireland is the correct avenue.]]></description>
<dc:subject>privacy eu us-politics microsoft michael-mcdowell law surveillance servers sca internet</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:55822d11b469/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eu"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:us-politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:michael-mcdowell"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:surveillance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sca"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.phusion.nl/2013/11/11/duplicity-s3-easy-cheap-encrypted-automated-full-disk-backups-for-your-servers/">
    <title>Duplicity + S3: easy, cheap, encrypted, automated full-disk backups for your servers</title>
    <dc:date>2014-03-31T13:37:03+00:00</dc:date>
    <link>http://blog.phusion.nl/2013/11/11/duplicity-s3-easy-cheap-encrypted-automated-full-disk-backups-for-your-servers/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[actually sounds quite nice]]></description>
<dc:subject>backups s3 aws servers duplicity ops duply unix linux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:9ae11460371c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:backups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:duplicity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:duply"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.wired.com/threatlevel/2014/01/tormail/">
    <title>If You Used This Secure Webmail Site, the FBI Has Your Inbox</title>
    <dc:date>2014-01-27T12:28:03+00:00</dc:date>
    <link>http://www.wired.com/threatlevel/2014/01/tormail/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[TorMail was a Tor-based webmail system, and apparently its drives have been imaged and seized by the FBI.  More info on the Freedom Hosting seizure:

<blockquote>The connection, if any, between the FBI obtaining Freedom Hosting’s data and apparently launching the malware campaign through TorMail and the other sites isn’t spelled out in the new document. The bureau could have had the cooperation of the French hosting company that Marques leased his servers from. Or it might have set up its own Tor hidden services using the private keys obtained from the seizure, which would allow it to adopt the same .onion addresses used by the original sites.

The French company also hasn’t been identified. But France’s largest hosting company, OVH, announced on July 29, in the middle of the FBI’s then-secret Freedom Hosting seizure, that it would no longer allow Tor software on its servers. A spokesman for the company says he can’t comment on specific cases, and declined to say whether Freedom Hosting was a customer.  “Wherever the data center is located, we conduct our activities in conformity with applicable laws, and as a hosting company, we obey search warrants or disclosure orders,” OVH spokesman Benjamin Bongoat told WIRED. “This is all we can say as we usually don’t make any comments on hot topics.”</blockquote>

]]></description>
<dc:subject>fbi freedom-hosting hosting tor tormail seizures ovh colo servers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:34b91e192bcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fbi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:freedom-hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hosting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tormail"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:seizures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ovh"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:colo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work">
    <title>How does LMAX's disruptor pattern work? - Stack Overflow</title>
    <dc:date>2011-11-23T09:52:35+00:00</dc:date>
    <link>http://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work</link>
    <dc:creator>jm</dc:creator><description><![CDATA[LMAX's "Disruptor" concurrent-server pattern, claiming to be a higher-throughput, lower-latency, and lock-free alternative to the SEDA pattern using a massive ring buffer.  Good discussion here at SO.  (via Filippo)]]></description>
<dc:subject>via:filippo servers seda queueing concurrency disruptor patterns latency trading performance ring-buffers</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:388ee9929e15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:filippo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:seda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:queueing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:disruptor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:latency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ring-buffers"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.scribd.com/doc/56651812/kreitz-spotify-kth11">
    <title>Gunnar Kreitz, _Spotify - Behind The Scenes_</title>
    <dc:date>2011-05-30T23:15:50+00:00</dc:date>
    <link>http://www.scribd.com/doc/56651812/kreitz-spotify-kth11</link>
    <dc:creator>jm</dc:creator><description><![CDATA[the innards of Spotify's client, server fleet, and P2P layer, from the dev team themselves.  good stuff]]></description>
<dc:subject>spotify streaming servers networking music mp3 dns p2p</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:15a9b072fc5c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:spotify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:music"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mp3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:p2p"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.ssllabs.com/ssldb/index.html">
    <title>Public SSL Server Database</title>
    <dc:date>2009-07-22T20:34:25+00:00</dc:date>
    <link>https://www.ssllabs.com/ssldb/index.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA['an online service that enables you to look up the configuration of any public SSL web server. The configuration of known public SSL web servers will be periodically inspected and the results recorded. This service relies on the SSL Server Rating guide for the assessment']]></description>
<dc:subject>ssl grades security tls https servers sysadmin ssl-labs</dc:subject>
<dc:identifier>https://pinboard.in/u:jm/b:57ac4adba12a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:grades"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ssl-labs"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>