<?xml version="1.0" encoding="UTF-8" ?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
       <title>PublicNTP Blog</title>
       <link>https://publicntp.org/blog.html</link>
       <description>PublicNTP updates and initiatives</description>
       <atom:link href="https://publicntp.org/blog/posts/rss.xml" rel="self" type="application/rss+xml" />
       <item>
           <title>Global NTP Server Monitoring</title>
           <link>https://publicntp.org/blog/posts/global-ntp-server-monitoring.html</link>
           <description>PublicNTP has consistently grown its global deployment footprint since the day the company formed. While that’s excellent news for us, it comes with a number of unforeseen issues as a matter of scale. With 30+ servers across the globe, it’s not enough to just make sure the server and operating system are both up and running.</description>
           <guid>https://publicntp.org/blog/posts/global-ntp-server-monitoring.html</guid>
       </item>

       <item>
           <title>The “Why” Question, the Network Time Community, and You!</title>
           <link>https://publicntp.org/blog/posts/network-time-community-and-you.html</link>
           <description>While Network Time Protocol (NTP) has been in development for 34 years, time refinement has been a global cause for nearly a century.</description>
           <guid>https://publicntp.org/blog/posts/network-time-community-and-you.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Fleet Servers and Maintenance</title>
           <link>https://publicntp.org/blog/posts/publicntps-fleet-servers-and-maintenance.html</link>
           <description>In the second half of 2017, a few months after PublicNTP officially became a company, we had anywhere from five to ten servers providing time. We found that our servers needed occasional maintenance but were reliable enough that we could “safely” ignore them most of the time. Our service, supported by many other surrounding stratum one/two providers, could be relied on while working and covered when down.</description>
           <guid>https://publicntp.org/blog/posts/publicntps-fleet-servers-and-maintenance.html</guid>
       </item>

       <item>
           <title>PublicNTP JAM</title>
           <link>https://publicntp.org/blog/posts/publicntp-jam.html</link>
           <description>Little while back (let’s face it, a long while back), I had another opportunity to visit the team out in Salt Lake. Scott and our developers are always pleasant company when working on PublicNTP’s objectives.</description>
           <guid>https://publicntp.org/blog/posts/publicntp-jam.html</guid>
       </item>

       <item>
           <title>Groundbreaking: Africa and the Middle East!</title>
           <link>https://publicntp.org/blog/posts/groundbreaking-africa-and-the-middle-east.html</link>
           <description>We’ve mentioned a few times that our cloud servers hit a speedbump around Africa due to a lack of developed infrastructure. Project: Ikenga is one of our attempts to work around that with a physical deployment.</description>
           <guid>https://publicntp.org/blog/posts/groundbreaking-africa-and-the-middle-east.html</guid>
       </item>

       <item>
           <title>PublicNTP July Board Meeting</title>
           <link>https://publicntp.org/blog/posts/publicntp-july-board-meeting.html</link>
           <description>PublicNTP’s board members once again met up to talk about the company’s accomplishments since our meeting last November, and make sure we all agreed on the company’s vision for the future.</description>
           <guid>https://publicntp.org/blog/posts/publicntp-july-board-meeting.html</guid>
       </item>

       <item>
           <title>GPS Generation Three Has Launched!</title>
           <link>https://publicntp.org/blog/posts/gps-generation-three-has-launched.html</link>
           <description>November 26th, 2018 saw NASA land the Mars InSight rover—an achievement that required a thousand different, precise steps to all happen perfectly in order to succeed.</description>
           <guid>https://publicntp.org/blog/posts/gps-generation-three-has-launched.html</guid>
       </item>

       <item>
           <title>F2F in Mountain Time!</title>
           <link>https://publicntp.org/blog/posts/f2f-in-mountain-time.html</link>
           <description>PublicNTP, like many companies, is geographically distributed; the company’s four board members live in four different states.</description>
           <guid>https://publicntp.org/blog/posts/f2f-in-mountain-time.html</guid>
       </item>

       <item>
           <title>Touching Bases With The Team (African Expansion and More!)</title>
           <link>https://publicntp.org/blog/posts/touching-bases-with-the-team-african-expansion-and-more.html</link>
           <description>PublicNTP has been working to improve our footprint in Africa since before the company was legally incorporated in the state of Virginia. The company has dubbed the search for improved company presence in Africa Project Ikenga, named after an African god of time.</description>
           <guid>https://publicntp.org/blog/posts/touching-bases-with-the-team-african-expansion-and-more.html</guid>
       </item>

       <item>
           <title>PNTP Open Architecture Stratum One Part 5/5: Future Investigations</title>
           <link>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-5-future-investigations.html</link>
           <description>In this final entry in the series about our open architecture stratum one server, we call out some of the future investigations we noted that may be worth looking into during the exploration so far.</description>
           <guid>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-5-future-investigations.html</guid>
       </item>

       <item>
           <title>PublicNTP Open Architecture Stratum One Part 4: Step By Step Blueprint</title>
           <link>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-4-step-by-step-blueprint.html</link>
           <description>This next ‘article’ is for those tech-heads and time-nerds who are interested in setting up their own time server.</description>
           <guid>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-4-step-by-step-blueprint.html</guid>
       </item>

       <item>
           <title>PNTP Open Architecture Stratum One Part 3: Technical Overview</title>
           <link>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-3-technical-overview.html</link>
           <description>In this third entry in the series, we get into the technical decisions we made, and the decision points we encountered along the way to the current iteration.</description>
           <guid>https://publicntp.org/blog/posts/pntp-open-architecture-stratum-one-part-3-technical-overview.html</guid>
       </item>

       <item>
           <title>PublicNTP Open Architecture Stratum One Server Part 2: Rationale</title>
           <link>https://publicntp.org/blog/posts/open-stratum-one-server-part-2-rationale.html</link>
           <description>As posted in PublicNTP’s previous blog article, our team has spent many hours and meetings over the past months identifying the advantages and disadvantages of our own open architecture. We’ve looked hard at utilizing tried and true NTP servers in tandem with our own established network of stratum two and, more recently, stratum one servers.</description>
           <guid>https://publicntp.org/blog/posts/open-stratum-one-server-part-2-rationale.html</guid>
       </item>

       <item>
           <title>Open Stratum One - The Meinberg Solution</title>
           <link>https://publicntp.org/blog/posts/open-stratum-one-the-meinberg-solution.html</link>
           <description>Since PublicNTP started in the summer of 2017, all but one of the servers we have deployed have been stratum two servers according to the Network Time Protocol.</description>
           <guid>https://publicntp.org/blog/posts/open-stratum-one-the-meinberg-solution.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Stratum One Deployment Checklist</title>
           <link>https://publicntp.org/blog/posts/publicntps-stratum-one-deployment-checklist.html</link>
           <description>Much in the same way we dove into virtual servers, we figured it would be fairly easy to find an underserved country and find a company who would lease us some power, space, and network bandwidth.</description>
           <guid>https://publicntp.org/blog/posts/publicntps-stratum-one-deployment-checklist.html</guid>
       </item>

       <item>
           <title>What Goes Into Deployment?</title>
           <link>https://publicntp.org/blog/posts/What-Goes-Into-Deployment.html</link>
           <description>As of this writing, all of PublicNTP’s deployed time servers are virtual (i.e., running in the cloud) -- except for Salt Lake City, because Scott is a  fan of turning things up to 11. This approach has served us well so far. It’s becoming clear that we’re reaching the point of diminishing returns for cloud deployments. In the underserved countries we’re now trying to target, cloud just won’t be an option.</description>
           <guid>https://publicntp.org/blog/posts/What-Goes-Into-Deployment.html</guid>
       </item>

       <item>
           <title>Project Ikenga - Connecting Africa</title>
           <link>https://publicntp.org/blog/posts/Project-Ikenga.html</link>
           <description>When PublicNTP originally targeted Africa for a deployment campaign we knew that there were going to be a few challenges.</description>
           <guid>https://publicntp.org/blog/posts/Project-Ikenga.html</guid>
       </item>

       <item>
           <title>2018 PublicNTP Board Meeting - Upcoming Year</title>
           <link>https://publicntp.org/blog/posts/2018-board-meeting.html</link>
           <description>Board members look forward to what 2019 holds for PublicNTP</description>
           <guid>https://publicntp.org/blog/posts/2018-board-meeting.html</guid>
       </item>

       <item>
           <title>Year in review</title>
           <link>https://publicntp.org/blog/posts/2018-year-in-review.html</link>
           <description>PublicNTP has its annual board meeting in November, where the directors review the changes, achievements, and progress made in the previous twelve months. As always, it was a delight to get all four board members face to face to discuss what has happened.</description>
           <guid>https://publicntp.org/blog/posts/2018-year-in-review.html</guid>
       </item>

       <item>
           <title>The Time Server App Has Launched!</title>
           <link>https://publicntp.org/blog/posts/bring-time-to-the-world.html</link>
           <description>The Time Server app is a reflection of both PublicNTP’s vision for the future and a sizeable portion of our concerted efforts in the last two years. With Time Server, you’ll be able to have and redistribute some of the most accurate time on the planet.</description>
           <guid>https://publicntp.org/blog/posts/bring-time-to-the-world.html</guid>
       </item>

       <item>
           <title>A Tale of Two Meetings</title>
           <link>https://publicntp.org/blog/posts/keeping-company-pointed.html</link>
           <description>A big part of keeping any company pointed in the right direction is making sure the leadership team is communicating regularly.</description>
           <guid>https://publicntp.org/blog/posts/keeping-company-pointed.html</guid>
       </item>

       <item>
           <title>PublicNTP partners with Network Time Foundation</title>
           <link>https://publicntp.org/blog/posts/publicntp-partners-network-time-foundation.html</link>
           <description>Network Time Protocol (NTP) remains one of the oldest and most fundamental internet protocols in use. It has provided a bedrock of reliable time for us since 1985. NTP started out rough, as all innovations do</description>
           <guid>https://publicntp.org/blog/posts/publicntp-partners-network-time-foundation.html</guid>
       </item>

       <item>
           <title>Donating Time</title>
           <link>https://publicntp.org/blog/posts/donating-time.html</link>
           <description>PublicNTP receives federal public charity status</description>
           <guid>https://publicntp.org/blog/posts/donating-time.html</guid>
       </item>

       <item>
           <title>PublicNTP&#x27;s Paperwork Puzzle</title>
           <link>https://publicntp.org/blog/posts/paperwork-puzzle.html</link>
           <description>Part 4: Our 15 step checklist</description>
           <guid>https://publicntp.org/blog/posts/paperwork-puzzle.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Financial Structure</title>
           <link>https://publicntp.org/blog/posts/financial-structure.html</link>
           <description>Part 3: When considering the public charity path, make sure you know how you’re reconciling your finances and how often</description>
           <guid>https://publicntp.org/blog/posts/financial-structure.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Organizational Structure</title>
           <link>https://publicntp.org/blog/posts/organizational-structure.html</link>
           <description>Part 2: We needed to establish some structure to the corporation</description>
           <guid>https://publicntp.org/blog/posts/organizational-structure.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Dizzying Terminology</title>
           <link>https://publicntp.org/blog/posts/dizzying-terminology.html</link>
           <description>Part 1: The first steps to becoming tax-exempt</description>
           <guid>https://publicntp.org/blog/posts/dizzying-terminology.html</guid>
       </item>

       <item>
           <title>PublicNTP’s Journey to Tax-Exempt Status</title>
           <link>https://publicntp.org/blog/posts/pntp-introduction.html</link>
           <description>The first steps to becoming tax-exempt</description>
           <guid>https://publicntp.org/blog/posts/pntp-introduction.html</guid>
       </item>

       <item>
           <title>Global expansion and a facelift</title>
           <link>https://publicntp.org/blog/posts/global-expansion-and-a-facelift.html</link>
           <description>When I first launched PublicNTP with a single NTP server in Chicago, Illinois, I had grand plans for rapid expansion, first across the US, to be quickly followed by exotic locations around the globe I’d always wanted to visit.</description>
           <guid>https://publicntp.org/blog/posts/global-expansion-and-a-facelift.html</guid>
       </item>

   </channel>
</rss>
