<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Myows Blog &#187; team</title>
	<atom:link href="http://myows.com/blog/tag/team/feed/" rel="self" type="application/rss+xml" />
	<link>http://myows.com/blog</link>
	<description>It&#039;s about online copyright protection</description>
	<lastBuildDate>Wed, 01 Feb 2012 23:22:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Free Copyright Protection and Management: Just Add Trust</title>
		<link>http://myows.com/blog/trust-us-to-protect-your-copyrights-online/</link>
		<comments>http://myows.com/blog/trust-us-to-protect-your-copyrights-online/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 11:27:33 +0000</pubDate>
		<dc:creator>Chris Human</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[article]]></category>
		<category><![CDATA[dev]]></category>
		<category><![CDATA[protection]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[team]]></category>

		<guid isPermaLink="false">http://myows.com/blog/?p=1370</guid>
		<description><![CDATA[The issue of whether Myows is trustworthy is an interesting one. Okay, to be honest, it’s a little frustrating. But then I guess it’s always annoying to be faced with trust barriers when you’ve started a positive initiative and all you want to do is go out there and nail bad guys. Of course, these [...]]]></description>
			<content:encoded><![CDATA[<p><img class="fr" title="Tandem Skydive" src="http://myows.com/blog/wp-content/uploads/2010/02/skydive-270x201.jpg" alt="Tandem Skydive" width="270" height="201" /><strong>The issue of whether <a href="http://myows.com">Myows</a> is trustworthy is an interesting one. </strong></p>
<p>Okay, to be honest, it’s a little frustrating. But then I guess it’s always annoying to be faced with trust barriers when you’ve started a positive initiative and all you want to do is go out there and nail bad guys. Of course, these questions are only natural at the end of the day. So here is our response.</p>
<p><span id="more-1370"></span></p>
<h4>We realise that there will always be skeptics and conspiracy theorists, but as for the rational majority &#8211; here’s what we’ve done to ensure that you can trust us with your work:</h4>
<p><strong>1. </strong>Each file is stored and backed-up on two remote, independently operated and maintained servers on opposite sides of the world. If both these servers are simultaneously and cataclysmically destroyed, the safety of your OWs will cease to be your priority.</p>
<p><strong>2. </strong>A unique <a href="http://en.wikipedia.org/wiki/Hash_function">hash value</a> is generated for each work at the time of upload. This is permanently linked with the file to form your OW. Basically each file is packing its own fingerprint/retinal ID, proving that it is who it claims and that it was born when it was born.</p>
<p><strong>3</strong><strong>.</strong> All databases (including hash values) are periodically filed (as recorded data) at <a href="http://nicciferguson.com/meettheteam">our lawyer’s offices</a> in a large steel safe that may even survive the cataclysm mentioned in 1 above. </p>
<p><strong>4</strong><strong>.</strong> All the leading web security standards (including SSL encryption) have been thoroughly and conscientiously applied across our app to ensure safe transfer of data and reliable verification where required. <small>(<a href="http://gmail.com">Gmail </a> and <a href="http://basecamphq.com/">Basecamp</a> only recently switched to this approach, and <a href="http://facebook.com">Facebook</a> or<a href="http://twitter.com"> Twitter</a> have yet to follow our lead in terms of site-wide SSL security.)</small></p>
<p><strong>5</strong><a href="http://myows.com/blog/info/about-us/"> Dave, Max, Steve and I</a> are all really good-natured people with solid middle-class upbringings, decent (not decadent) tertiary education and friendly dispositions.</p>
<p><strong>What else can we do to help you believe we’re on your side?</strong> </p>
<p>Plenty. But right now our focus is on getting a great service and product to people that do believe us in light of the above. Time will provide the best evidence of our intentions. </p>
<p>Suffice to say that we’ve gone the extra mile in building <strong>a brand that stands for integrity, safety and solidarity amongst the creative community</strong>. Ergo: there’d be little point in allowing anything or anyone to jeopardise all that.</p>
<p>As far as l running off into the night with our members’ work is concerned&#8230; what would we do with your OWs if we were to steal them? Would we print them all out and fold them into origami paper hats?… perhaps. Would we secretly sell them on to the highest bidder? Now that would be ridiculous. </p>
<p>Stealing our member’s OWs (or allowing them to be stolen) is really not a sustainable business model. If this ever happened, you can bet your cotton socks (it&#8217;s an English thing) that somebody would find out and spread the word fast. We are talking about the net after all. </p>
<p><strong>We would prefer to keep our business and personal reputations in tact thank you very much</strong>.</p>
<p>Bear in mind that, if we breached fellow-members’ trust, we’d go down in history, not only as evil idiots, but also as irony personified. <a href="http://myows.com">Myows</a> would be stuffed. What a waste… even if we were the bad guys.</p>
<p>Which. Of course. We’re not.</p>
]]></content:encoded>
			<wfw:commentRss>http://myows.com/blog/trust-us-to-protect-your-copyrights-online/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
