<?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 (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://mastodon.social/@matthewskelton/113208937897993101"/>
	<rdf:li rdf:resource="https://dannorth.net/how-simple-is-too-simple/"/>
	<rdf:li rdf:resource="https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/"/>
	<rdf:li rdf:resource="https://apichangelog.substack.com/p/how-breaking-changes-affect-api-documentation?publication_id=26957&amp;post_id=142648936&amp;triggerShare=true&amp;isFreemail=true&amp;r=7vo67&amp;triedRedirect=true"/>
	<rdf:li rdf:resource="https://observablehq.com/@simonw/download-github-repo"/>
	<rdf:li rdf:resource="https://github.com/Kong/insomnia/discussions/6626#discussioncomment-7299800"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/bitemporal-history.html"/>
	<rdf:li rdf:resource="https://www.outlookindia.com/business/apple-vs-facebook-how-a-small-change-in-apple-iphone-s-privacy-feature-is-threatening-business-model-of-social-media-companies-news-236802"/>
	<rdf:li rdf:resource="https://medium.com/criteo-engineering/introducing-openapi-comparator-an-open-source-tool-to-detect-breaking-changes-in-your-api-7f705bb972b0"/>
	<rdf:li rdf:resource="https://www.somebits.com/fiskmap/#9.00/31.0768/-91.5979"/>
	<rdf:li rdf:resource="https://docs.microsoft.com/en-us/microsoft-365/admin/manage/release-options-in-office-365?view=o365-worldwide#how-it-works---release-validation"/>
	<rdf:li rdf:resource="https://vimeo.com/671743693"/>
	<rdf:li rdf:resource="https://apihandyman.io/handle-api-gateway-and-backend-differences-in-api-documentation-with-openapi-specification/"/>
	<rdf:li rdf:resource="https://apihandyman.io/apidays-interface-doing-apis-right-and-doing-right-apis/#versioning-handling-changes"/>
	<rdf:li rdf:resource="https://nordicapis.com/whats-new-in-openapi-3-1-0/"/>
	<rdf:li rdf:resource="https://useoptic.com/blog/launching-the-optic-gitbot/"/>
	<rdf:li rdf:resource="https://developer.github.com/v4/breaking_changes/"/>
	<rdf:li rdf:resource="https://www.bennadel.com/blog/3501-when-is-a-change-a-breaking-change-for-an-api.htm"/>
	<rdf:li rdf:resource="https://lauren.vortex.com/archive/001112.html"/>
	<rdf:li rdf:resource="http://www.cepro.com/article/new_sonos_api_disrupts_home_automation_integration_but_lays_solid_foundatio"/>
	<rdf:li rdf:resource="https://medium.com/@anildash/the-end-of-thinkup-e600bc46cc56#.9dhazj3vf"/>
	<rdf:li rdf:resource="http://liveresource.org/"/>
	<rdf:li rdf:resource="https://blog.pinboard.in/2016/03/my_heroic_and_lazy_stand_against_ifttt/"/>
	<rdf:li rdf:resource="https://tools.ietf.org/html/rfc7089"/>
	<rdf:li rdf:resource="https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp?hl=en"/>
	<rdf:li rdf:resource="https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp"/>
	<rdf:li rdf:resource="http://en.m.wikipedia.org/wiki/Levenshtein_distance"/>
	<rdf:li rdf:resource="https://developers.facebook.com/roadmap/change-policy/"/>
	<rdf:li rdf:resource="http://www.cindyalvarez.com/communication/announcing-change-without-inducing-panic"/>
	<rdf:li rdf:resource="http://www.donationcoders.com/kubicle/watcher/"/>
	<rdf:li rdf:resource="http://drupal.org/project/subscriptions"/>
	<rdf:li rdf:resource="http://drupal.org/project/recent_changes"/>
	<rdf:li rdf:resource="http://sourcegear.com/diffmerge/index.html"/>
	<rdf:li rdf:resource="http://www.markwell.btinternet.co.uk/webmon/"/>
	<rdf:li rdf:resource="http://www.changenotes.com/index.php?r=website+monitoring"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://mastodon.social/@matthewskelton/113208937897993101">
    <title>Bookmarked toot from matthewskelton</title>
    <dc:date>2024-09-28T07:42:04+00:00</dc:date>
    <link>https://mastodon.social/@matthewskelton/113208937897993101</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Rob Lazzurs explaining the value of code-driven changes: it provides an audit
trail of **intent** behind changes. 💡

[#DevOpsDays](https://mastodon.social/tags/DevOpsDays)
[#FastFlow](https://mastodon.social/tags/FastFlow)


mast-id:113208937990297551]]></description>
<dc:subject>masto-bmarks auditing audits yaml changes</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1688a26f8749/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:masto-bmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:auditing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:audits"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:yaml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dannorth.net/how-simple-is-too-simple/">
    <title>How simple is too simple? - Dan North &amp; Associates Limited</title>
    <dc:date>2024-09-04T16:30:33+00:00</dc:date>
    <link>https://dannorth.net/how-simple-is-too-simple/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>This led us to the notion of a Change Event Horizon, which is the amount of time before you can undo the effect of a decision. For a programming language the change event horizon is huge. It can take years to repair a bogus language decision, and involve complex processes such as deprecation. For an internally-deployed enterprise app you are only as far away as your next release date.</blockquote>]]></description>
<dc:subject>changes time flexibility tradeoffs horizons apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3c052416f283/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:flexibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tradeoffs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:horizons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/">
    <title>Software Licensing Changes and Their Impact on Financial Outcomes – Alt + E S V</title>
    <dc:date>2024-08-26T18:53:11+00:00</dc:date>
    <link>https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>While in our sample we see revenue grow post-license change, we don’t see a notable change in the rate of growth. We also see very mixed results in company valuation, and there does not seem to be a clear link between moving from an open source to proprietary license and increasing the company’s value.</blockquote>]]></description>
<dc:subject>licensing oss opensource changes revenue business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a9df8aa73d4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:oss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:revenue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apichangelog.substack.com/p/how-breaking-changes-affect-api-documentation?publication_id=26957&amp;post_id=142648936&amp;triggerShare=true&amp;isFreemail=true&amp;r=7vo67&amp;triedRedirect=true">
    <title>How Breaking Changes Affect API Documentation</title>
    <dc:date>2024-03-15T17:47:37+00:00</dc:date>
    <link>https://apichangelog.substack.com/p/how-breaking-changes-affect-api-documentation?publication_id=26957&amp;post_id=142648936&amp;triggerShare=true&amp;isFreemail=true&amp;r=7vo67&amp;triedRedirect=true</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>An API breaking change is something you want to avoid at all costs. At least that's what most of you would agree with. If any breaking change introduces a functional obstruction how does it also affect the API documentation?</blockquote>
Why not write tests? Or have LLMs generate tests from docs?]]></description>
<dc:subject>apis changes documentation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9f0c3877f6d0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://observablehq.com/@simonw/download-github-repo">
    <title>URL to download a GitHub repository as a zip file / Simon Willison | Observable</title>
    <dc:date>2024-01-29T21:38:14+00:00</dc:date>
    <link>https://observablehq.com/@simonw/download-github-repo</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[See: https://fedi.simonwillison.net/@simon/111841303732052620

need to look nito Observable as a scripting tool. Same with val.town]]></description>
<dc:subject>github changes tools sites</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cca020c9887e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sites"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Kong/insomnia/discussions/6626#discussioncomment-7299800">
    <title>Local-only projects are back in Insomnia 8.3 (GA). · Kong/insomnia · Discussion #6626 · GitHub</title>
    <dc:date>2023-10-19T03:02:33+00:00</dc:date>
    <link>https://github.com/Kong/insomnia/discussions/6626#discussioncomment-7299800</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apis kong changes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c299e88440ef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kong"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/bitemporal-history.html">
    <title>Bitemporal History</title>
    <dc:date>2023-09-27T23:00:24+00:00</dc:date>
    <link>https://martinfowler.com/articles/bitemporal-history.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>It's often necessary to access the historical values of some property. But sometimes this history itself needs to be modified in response to retroactive updates. Bitemporal history treats time as two dimensions: actual history records what history should be given perfect transmission of information, while record history captures how our knowledge of history changes.</blockquote>]]></description>
<dc:subject>data history programming time changes techniques</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:8cf5eb274293/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:techniques"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.outlookindia.com/business/apple-vs-facebook-how-a-small-change-in-apple-iphone-s-privacy-feature-is-threatening-business-model-of-social-media-companies-news-236802">
    <title>How A Small Change In Apple iPhone’s Privacy Feature Is Threatening Business Model Of Social Media Companies</title>
    <dc:date>2023-07-02T16:40:12+00:00</dc:date>
    <link>https://www.outlookindia.com/business/apple-vs-facebook-how-a-small-change-in-apple-iphone-s-privacy-feature-is-threatening-business-model-of-social-media-companies-news-236802</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apple ads tracking changes impact anticompetitive</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:fd160978ea8e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apple"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ads"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tracking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:impact"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:anticompetitive"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/criteo-engineering/introducing-openapi-comparator-an-open-source-tool-to-detect-breaking-changes-in-your-api-7f705bb972b0">
    <title>Introducing OpenAPI Comparator: an open-source tool to detect breaking changes in your API | by Paul Mathon | Criteo R&amp;D Blog | Feb, 2023 | Medium</title>
    <dc:date>2023-02-20T22:20:12+00:00</dc:date>
    <link>https://medium.com/criteo-engineering/introducing-openapi-comparator-an-open-source-tool-to-detect-breaking-changes-in-your-api-7f705bb972b0</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>openapi told changes comparison</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b19be0d496f2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:told"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.somebits.com/fiskmap/#9.00/31.0768/-91.5979">
    <title>1944 map of former courses of the Mississippi River</title>
    <dc:date>2022-12-06T20:07:14+00:00</dc:date>
    <link>https://www.somebits.com/fiskmap/#9.00/31.0768/-91.5979</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[nice, imposed over the actual river map, so clever!]]></description>
<dc:subject>mississippi rivers changes change visualization time maps</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:78c3164973dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mississippi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rivers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maps"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.microsoft.com/en-us/microsoft-365/admin/manage/release-options-in-office-365?view=o365-worldwide#how-it-works---release-validation">
    <title>Set up the Standard or Targeted release options - Microsoft 365 admin | Microsoft Docs</title>
    <dc:date>2022-03-21T18:22:18+00:00</dc:date>
    <link>https://docs.microsoft.com/en-us/microsoft-365/admin/manage/release-options-in-office-365?view=o365-worldwide#how-it-works---release-validation</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["How it works - release validation
Any new release is first tested and validated by the feature team, then by the entire Microsoft 365 feature team, followed by all of Microsoft. After internal testing and validation, the next step is a Targeted release (formerly known as First release) to customers who opt in. At each release ring, Microsoft collects feedback and further validates quality by monitoring key usage metrics. This series of progressive validation is in place to make sure the worldwide-release is as robust as possible. The releases are pictured in the following figure.



For significant updates, customers are initially notified by the Microsoft 365 Roadmap. As an update gets closer to rolling out, it is communicated through your Microsoft 365 Message center"]]></description>
<dc:subject>releases changes channels features productmanagement microsoft</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dbe0a36757a6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:releases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:channels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:features"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:microsoft"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://vimeo.com/671743693">
    <title>API Review with Optic on Vimeo</title>
    <dc:date>2022-02-08T22:00:40+00:00</dc:date>
    <link>https://vimeo.com/671743693</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[nice CI job to ensure changes are caught and meaning is given context of the changes as a comment on the change. clever!]]></description>
<dc:subject>apis reviews changes tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:866bc9e9b96b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:reviews"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apihandyman.io/handle-api-gateway-and-backend-differences-in-api-documentation-with-openapi-specification/">
    <title>API Handyman | Handle API gateway and backend differences in API documentation with OpenAPI Specification</title>
    <dc:date>2022-02-08T02:31:05+00:00</dc:date>
    <link>https://apihandyman.io/handle-api-gateway-and-backend-differences-in-api-documentation-with-openapi-specification/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["I got yet another interesting question from my social networks: how to deal with the fact that an API contract can be different at gateway and implementation levels, and more precisely how to manage that when describing that contract with an OpenAPI file used as specification targeting API’s implementation’s developer and documentation targeting API’s consumers?"

Whatever the way of doing the modifications, they would be:

Replace backend servers by gateway one
Replace backend securityDefinitions by gateway one
Replace backend operation securityby gateway one
Add gateway specific responses
Add gateway specific headers in responses
Remove backend specific operations if needed (see In case of backend specific operations)
]]></description>
<dc:subject>apis transformation openapi gateways changes descriptions</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6d9e74c3b8bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:transformation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gateways"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:descriptions"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://apihandyman.io/apidays-interface-doing-apis-right-and-doing-right-apis/#versioning-handling-changes">
    <title>API Handyman | Doing APIs right and doing right APIs</title>
    <dc:date>2021-06-18T15:51:39+00:00</dc:date>
    <link>https://apihandyman.io/apidays-interface-doing-apis-right-and-doing-right-apis/#versioning-handling-changes</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Sam Newman gave a deep dive into versioning during his session. He especially explained that versioning is not the real problem. It’s not about version 1 and version 2. The real problem is how to handle change, how to handle backward compatibility and incompatibility. And this is even more true when doing microservices which are supposed to be independently deployable: maintaining backward compabitibility is key.

He gave 4 concrete tips to do so.]]></description>
<dc:subject>apis versioning changes microservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:66081b830d86/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:microservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nordicapis.com/whats-new-in-openapi-3-1-0/">
    <title>What’s New in OpenAPI 3.1.0? | Nordic APIs |</title>
    <dc:date>2021-04-08T00:09:24+00:00</dc:date>
    <link>https://nordicapis.com/whats-new-in-openapi-3-1-0/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Just over a year after OAS 3.0.3’s release — and five months after OAS 3.1.0 RC1’s — OAS 3.1.0 has finally hit the airwaves. This is the OpenAPI Initiative’s newest major revision to the OAS 3.0 branch. Despite this, the specification’s developers want the upgrade to feel incremental for new users. Corporate users reliant on OAS should feel more comfortable with swift adoption. While semantic naming conventions dictate the jump to OAS 4.0, the leap would discourage quick embracement of critical changes.

While the consortium is always advancing development, releases tend to be spaced apart over months or years. Adopters should get comfortable with this latest build. Thankfully, there are plenty of updated goodies for developers to unpack. What exactly has changed?"]]></description>
<dc:subject>openapi blog post changes updates</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ec3060c0b7e4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:blog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:post"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:updates"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://useoptic.com/blog/launching-the-optic-gitbot/">
    <title>An API Changelog on Every Commit -- Optic Blog</title>
    <dc:date>2019-09-23T22:28:40+00:00</dc:date>
    <link>https://useoptic.com/blog/launching-the-optic-gitbot/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""
see: https://www.useoptic.com]]></description>
<dc:subject>apis changes changelog github</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:df80bf6c60fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changelog"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:github"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.github.com/v4/breaking_changes/">
    <title>Breaking Changes | GitHub Developer Guide</title>
    <dc:date>2018-10-17T19:33:42+00:00</dc:date>
    <link>https://developer.github.com/v4/breaking_changes/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Breaking changes are any changes that might require action from our integrators. We divide these changes into two categories:

Breaking: Changes that will break existing queries to the GraphQL API. For example, removing a field would be a breaking change.
Dangerous: Changes that won't break existing queries but could affect the runtime behavior of clients. Adding an enum value is an example of a dangerous change.
We strive to provide stable APIs for our integrators. When a new feature is still evolving, we release it behind a schema preview.

We'll announce upcoming breaking changes at least three months before making changes to the GraphQL schema, to give integrators time to make the necessary adjustments. Changes go into effect on the first day of a quarter (January 1st, April 1st, July 1st, or October 1st). For example, if we announce a change on January 15th, it will be made on July 1st."]]></description>
<dc:subject>github changes apis breaking versioning graphql omgwtf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5833b86183f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:breaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graphql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:omgwtf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.bennadel.com/blog/3501-when-is-a-change-a-breaking-change-for-an-api.htm">
    <title>When Is A Change A Breaking Change For An API</title>
    <dc:date>2018-10-02T00:48:22+00:00</dc:date>
    <link>https://www.bennadel.com/blog/3501-when-is-a-change-a-breaking-change-for-an-api.htm</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[how can I break thee? let me count the ways.]]></description>
<dc:subject>apis contracts changes breaking versions versioning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:419c1ecf3289/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:contracts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:breaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versioning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lauren.vortex.com/archive/001112.html">
    <title>Lauren Weinstein's Blog: UI Fail: How Our User Interfaces Help to Ruin Lives</title>
    <dc:date>2017-05-04T21:12:01+00:00</dc:date>
    <link>https://lauren.vortex.com/archive/001112.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["For a user with fading memory (another attribute that begins to surface relatively early in life) the sudden change of an icon from a wrench to a gear, or a change in a commonly used icon's position, can trigger such frustration that users who could most benefit from these systems -- especially for basic communications -- become embarrassed and, not wanting to ask for help, give up and withdraw back into deadly isolation."]]></description>
<dc:subject>ux design interface changes ui costs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4a7b4b3040c0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:costs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cepro.com/article/new_sonos_api_disrupts_home_automation_integration_but_lays_solid_foundatio">
    <title>New Sonos API Disrupts Home Automation Integration, But Lays Solid Foundation - CE Pro</title>
    <dc:date>2017-01-26T17:00:17+00:00</dc:date>
    <link>http://www.cepro.com/article/new_sonos_api_disrupts_home_automation_integration_but_lays_solid_foundatio</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apis partners Sonos changes change communication deprecation</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bd4e3b34b965/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:partners"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Sonos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deprecation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@anildash/the-end-of-thinkup-e600bc46cc56#.9dhazj3vf">
    <title>The end of ThinkUp — Medium</title>
    <dc:date>2016-08-07T05:12:44+00:00</dc:date>
    <link>https://medium.com/@anildash/the-end-of-thinkup-e600bc46cc56#.9dhazj3vf</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apis changes business thinkup</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cfaf4c37b0d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:thinkup"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://liveresource.org/">
    <title>LiveResource</title>
    <dc:date>2016-04-08T18:14:28+00:00</dc:date>
    <link>http://liveresource.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["We all work with web resources. What if we had a nice way to know when they change?

LiveResource is a protocol specification and JavaScript reference library for receiving live updates of web resources. It has the following principles:

Blend naturally with RESTful API design.
Optionally support WebSockets, but do so without abandoning established API principles.
Keep it simple. It should be possible to curl for updates.
"]]></description>
<dc:subject>web resources notifications change changes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:595760089dac/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notifications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.pinboard.in/2016/03/my_heroic_and_lazy_stand_against_ifttt/">
    <title>My Heroic and Lazy Stand Against IFTTT (Pinboard Blog)</title>
    <dc:date>2016-04-01T01:23:56+00:00</dc:date>
    <link>https://blog.pinboard.in/2016/03/my_heroic_and_lazy_stand_against_ifttt/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>pinboard ifttt legal terms platforms challenges changes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0d25eb09bcbd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pinboard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ifttt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:terms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:challenges"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tools.ietf.org/html/rfc7089">
    <title>RFC 7089 - HTTP Framework for Time-Based Access to Resource States -- Memento</title>
    <dc:date>2015-12-16T18:11:17+00:00</dc:date>
    <link>https://tools.ietf.org/html/rfc7089</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[" The HTTP-based Memento framework bridges the present and past Web.
   It facilitates obtaining representations of prior states of a given
   resource by introducing datetime negotiation and TimeMaps.  Datetime
   negotiation is a variation on content negotiation that leverages the
   given resource's URI and a user agent's preferred datetime.  TimeMaps
   are lists that enumerate URIs of resources that encapsulate prior
   states of the given resource.  The framework also facilitates
   recognizing a resource that encapsulates a frozen prior state of
   another resource."]]></description>
<dc:subject>resources spec changes specifications specs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:27f067b73ee4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:spec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:specifications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:specs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp?hl=en">
    <title>Chrome Web Store - Track Changes</title>
    <dc:date>2014-03-21T04:41:02+00:00</dc:date>
    <link>https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp?hl=en</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>track changes Google:docs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f45ea430d73e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:track"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Google:docs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp">
    <title>Chrome Web Store - Track Changes</title>
    <dc:date>2014-03-12T15:11:18+00:00</dc:date>
    <link>https://chrome.google.com/webstore/detail/track-changes/pgjeblaieehjmmahlikmifaggjckpcnp</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Makes it work like word]]></description>
<dc:subject>Google:docs addons track changes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a4d0f9be2003/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Google:docs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:addons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:track"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.m.wikipedia.org/wiki/Levenshtein_distance">
    <title>Levenshtein distance - Wikipedia, the free encyclopedia</title>
    <dc:date>2013-03-15T04:04:40+00:00</dc:date>
    <link>http://en.m.wikipedia.org/wiki/Levenshtein_distance</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>Information theory language letters differences changes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6525c4e9a81a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:theory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:letters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:differences"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.facebook.com/roadmap/change-policy/">
    <title>Breaking Change Policy - Facebook Developers</title>
    <dc:date>2013-02-04T07:18:25+00:00</dc:date>
    <link>https://developers.facebook.com/roadmap/change-policy/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["We are committed to a 90-day breaking change policy. This means Platform changes that would require a code change from developers (security and privacy changes excluded) will be announced at least 90 days before the change goes into effect.

Starting with the April 2013 breaking change, we will bundle all breaking changes (security and privacy changes excluded) into quarterly updates.

To clarify what's covered by this policy, here are some examples of changes we might make.

Change/removal of major functionality
We may decide to change or remove existing major functionality, such as removing FBML, the REST API, an SDK or requiring SSL. These types of changes will always be announced 90 days prior to the change going into full effect.

Backwards compatibility
We will continue to enhance our existing APIs and reserve the right to add new parameters, return fields, etc. (such as adding new Page functionality or the ability to get the list of people a user is subscribed to). These changes shouldn't break any existing apps. Please ensure your apps properly handle these scenarios.

Facebook product changes
Facebook products will continue to evolve and we'll communicate these changes when they launch, but not always beforehand. For example, we might improve the Login Dialog or add/move discovery points. We'll strive to minimize disruption.

Privacy and security-related changes
We are committed to fixing privacy and security-related vulnerabilities as fast as possible even if this might mean introducing a breaking change. In these situations, which we strive to avoid, we will work with developers to quickly provide workarounds so they can fix their apps as soon as possible. However, due to the nature of these issues, timeliness is key and there's no way to pre-announce the changes.

To stay up to date on all upcoming changes, be sure to subscribe to our Developer Blog where all breaking changes will be announced. You can also check out the Developer Roadmap to see a full list of all upcoming breaking changes. To test out breaking changes in advance, you can use Migrations. If you ever notice a breaking change that falls out of our 90-day commitment, please file a bug and tag it with the "breaking change" tag to help keep us true to our commitment."]]></description>
<dc:subject>facebook api apis breaking changes deprecation policy community management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a3a237cd9d3f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:breaking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deprecation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:policy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cindyalvarez.com/communication/announcing-change-without-inducing-panic">
    <title>» Announcing Change without Inducing Panic</title>
    <dc:date>2012-02-22T17:12:01+00:00</dc:date>
    <link>http://www.cindyalvarez.com/communication/announcing-change-without-inducing-panic</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["You need to communicate these 5 things within 10 seconds / 1 screen of text:
When the change is coming
How this affects you (or “This does not affect you unless X”)
What action you need to take (or “You do not need to do anything”)
Why this decision was made (can be high-level/’spun’)
You can complain here"]]></description>
<dc:subject>cindy_alvarez change changes communication migration messaging customers happiness</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:18326ea9a1c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cindy_alvarez"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:migration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:customers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:happiness"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.donationcoders.com/kubicle/watcher/">
    <title>Tiny Watcher: keep your Windows clean</title>
    <dc:date>2008-10-23T12:10:13+00:00</dc:date>
    <link>http://www.donationcoders.com/kubicle/watcher/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["monitors your system for changes to your registry, drivers, and first-time programs and provides you with options to undo any unwanted changes. The application's site judiciously provides a list of pros and cons that are spot on. Pros: It's lightweight and only runs when you need it, it detects most important changes that can happen on your system, and it's configurable. Cons: It's not a real-time monitor, so you'll only be alerted of changes after the fact, and it doesn't automatically clean up messes for you—you still have to identify and tell it what you want to reverse." via:lifehacker]]></description>
<dc:subject>software Windows freeware Utilities tools monitor registry changes sysadmin</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e4f421d68701/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freeware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Utilities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monitor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:registry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sysadmin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drupal.org/project/subscriptions">
    <title>Subscriptions | drupal.org</title>
    <dc:date>2008-05-13T20:27:47+00:00</dc:date>
    <link>http://drupal.org/project/subscriptions</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[enables users to subscribe to be notified of changes to nodes or taxonomies, such as new comments in specific forums, or additions to some category of blog. Once enabled, all nodes will have an additional link that allows the user to change their subscrip]]></description>
<dc:subject>drupal module subscriptions email notification monitor changes</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:17acab9fb7bf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:module"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:subscriptions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monitor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://drupal.org/project/recent_changes">
    <title>Recent Changes | drupal.org</title>
    <dc:date>2008-02-07T15:24:00+00:00</dc:date>
    <link>http://drupal.org/project/recent_changes</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[track all editing on your site. A page is provided with a list of all revisions and comments in chronological order.]]></description>
<dc:subject>changes content diff drupal revisions compare rss module wiki</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a56ce9e7e072/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:content"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:diff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:revisions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:compare"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:module"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:wiki"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sourcegear.com/diffmerge/index.html">
    <title>SourceGear | DiffMerge</title>
    <dc:date>2007-06-05T20:32:46+00:00</dc:date>
    <link>http://sourcegear.com/diffmerge/index.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[a cross-platform application to visually compare and merge files for Windows, Mac OS X and Unix]]></description>
<dc:subject>diff tools software windows freeware linux OSX merge compare comparison changes document text free</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f4c36a4cb984/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:diff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freeware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:OSX"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:merge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:compare"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:document"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:free"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.markwell.btinternet.co.uk/webmon/">
    <title>WebMon</title>
    <dc:date>2007-04-09T16:12:58+00:00</dc:date>
    <link>http://www.markwell.btinternet.co.uk/webmon/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[a freeware web page update monitoring program - it saves you time and keeps you updated by automatically checking web pages to see if they have changed.]]></description>
<dc:subject>website web monitor changes change checker notify page</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:29875e6f68b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:website"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monitor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:checker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:page"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.changenotes.com/index.php?r=website+monitoring">
    <title>ChangeNotes.com - Monitor web site changes</title>
    <dc:date>2006-03-31T18:50:05+00:00</dc:date>
    <link>http://www.changenotes.com/index.php?r=website+monitoring</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[This free service monitors the web pages that interest you and notifies you by email when they change. You might like to monitor the web pages of your work or former work, clients, customers, industry groups, competitors, friends and family, hobby sites,]]></description>
<dc:subject>web tools services changes internet email website</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:11a1459260ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:website"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>