<?xml encoding="ISO-8859-1" version="1.0"?>
<!-- OPML generated by OPML Editor v0.75 on 5/19/2013; 5:35:41 PM -->
<opml version="2.0">
	<head>
		<title>8/10/11 by DW</title>
		<ownerName>Dave Winer</ownerName>
		<ownerEmail>dave.winer@gmail.com</ownerEmail>
		<windowTop>200</windowTop>
		<windowLeft>200</windowLeft>
		<windowBottom>600</windowBottom>
		<windowRight>800</windowRight>
		</head>
	<body>
		<outline created="Wed, 10 Aug 2011 18:27:01 GMT" pgfnum="907" text="SLIde time must be in GMT" type="blogpost">
			<outline created="Wed, 10 Aug 2011 18:27:05 GMT" pgfnum="908" text="The time must be in GMT. We were sending it in the local timezone of each machine. It happens to work because both of my test machines are in the same timezone. "></outline>
			<outline created="Wed, 10 Aug 2011 18:39:18 GMT" pgfnum="909" text="This is one of the problems of Unix dates, each app must have a convention about what timezone it's in. The date itself can't say what timezone it's talking about. A comparitive advantage of RFC822 dates."></outline>
			</outline>
		<outline created="Wed, 10 Aug 2011 13:53:48 GMT" pgfnum="892" text="Changes to SLIde" type="blogpost">
			<outline created="Wed, 10 Aug 2011 13:54:05 GMT" pgfnum="893" text="Implemented four of the &lt;a href=&quot;http://worknotes.scripting.com/july2011/72711ByDw/feedbackOnTheSlideProposal&quot;&gt;suggestions&lt;/a&gt; from reviewers."></outline>
			<outline created="Wed, 10 Aug 2011 13:54:18 GMT" pgfnum="894" text="1. Unix timestamp. Used to be RFC822 formatted. A lot of reviewers asked for this, independently. Let the majority rule. :-)"></outline>
			<outline created="Wed, 10 Aug 2011 15:36:23 GMT" pgfnum="896" text="2. Version parameter. Starts off at 0. Might possibly change it to 1 when it's announced on scripting.com. On the other hand a 0-based protocol version is kind of neat (never heard of one before). Current implementation just checks for its presence and that it's a valid integer. Otherwise all versions are (currently) assumed to be compatible with all others. If that should change, it will be noted in the spec."></outline>
			<outline created="Wed, 10 Aug 2011 16:47:23 GMT" pgfnum="897" text="3. Timestamps can only be used once. Since we only allow timestamps to be used for five minutes, this is quite implementable. "></outline>
			<outline created="Wed, 10 Aug 2011 17:43:21 GMT" pgfnum="898" text="4. No longer base64-ing the signature. No need to since it is URL-encoded. "></outline>
			<outline created="Wed, 10 Aug 2011 17:52:50 GMT" pgfnum="901" text="Still have to update the spec, but the code is implemented and changes released."></outline>
			<outline created="Wed, 10 Aug 2011 17:48:17 GMT" pgfnum="899" text="Parts">
				<outline text="idApiSuite.init"></outline>
				<outline text="idApiSuite.getSignature"></outline>
				<outline text="idApiSuite.responder.respond"></outline>
				<outline text="opmlEditor.member.validateRemote"></outline>
				</outline>
			</outline>
		</body>
	</opml>
