Thanks for the comments Greg! Could you expand upon what you mean by "predictable semantics"? I'm not sure what that entirely entails.<div><br></div><div>-Mark Berger<br><div><br></div><div><div>PS: Here are some more comments I left on the ticket.</div>
<div>-------------------</div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Comment (by markberger):</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> * I agree that the feature should be at the protocol level. That was my</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> original idea but I forgot to explicitly state that.</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> * When I was talking about sharing, I had the idea of sharing via a</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> publicly accessible gateway, similarly to how the tiddly wiki works. If a</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> user is running their own client, shortcuts should be able to be used with</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> the WUI, but I agree that it is not the way to share files.</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> * You're right in that there are serious issues with the flat namespace.</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> If accounting were implemented a user could have their own namespace for</span><br style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> their respective shortcuts.</span><br><br><div class="gmail_quote">On Tue, Jul 2, 2013 at 9:54 AM, Greg Troxel <span dir="ltr"><<a href="mailto:gdt@ir.bbn.com" target="_blank">gdt@ir.bbn.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mark,<br>
<br>
I put some thoughts in the ticket. (Perhaps tahoe-dev should get all<br>
ticket updates? It seems better to have the conversation in the ticket,<br>
so it's organized, but it risks leaving out people.)<br>
<br>
From: "tahoe-lafs" <<a href="mailto:trac@tahoe-lafs.org" target="_blank">trac@tahoe-lafs.org</a>><br>
Subject: Re: [tahoe-lafs-trac-stream] [tahoe-lafs] #2010: Implement<br>
shortcuts to caps<br>
Cc: <a href="mailto:tahoe-lafs-trac-stream@tahoe-lafs.org" target="_blank">tahoe-lafs-trac-stream@tahoe-lafs.org</a><br>
Date: Tue, 02 Jul 2013 13:52:27 -0000 (1 minute, 4 seconds ago)<br>
Reply-To: <a href="mailto:tahoe-dev@tahoe-lafs.org" target="_blank">tahoe-dev@tahoe-lafs.org</a><br>
<br>
#2010: Implement shortcuts to caps<br>
-----------------------------+--------------------------------------------<br>
Reporter: markberger | Owner:<br>
Type: enhancement | Status: new<br>
Priority: normal | Milestone: undecided<br>
Component: code | Version: 1.10.0<br>
Resolution: | Keywords: usability, newurls, introducer<br>
Launchpad Bug: |<br>
-----------------------------+--------------------------------------------<br>
<br>
Comment (by gdt):<br>
<br>
This is a major architectural change, to add a new namespace. Before it<br>
happens, I think it needs a a complete written architectural design and<br>
protocol explanation. A few concerns:<br>
<br>
* Absent a really good reason, the feature should be at the protocol/WAPI<br>
level, not at the WUI level. I think you meant that, but I'm not sure.<br>
* This is basically an extension to the aliases file, with a grid-wide<br>
shared namespace. So perhaps having an aliases.public that is published<br>
would make sense.<br>
* One needs to have unpublish if there is publish, probably.<br>
* Synchronization of aliases should have predictable semantics. Re-fetch<br>
on miss does not satisfy this.<br>
* I think sharing by pointing at a foreign WUI is bad practice; that's a<br>
hack for a web server with a tahoe backend filesystem. Sharing by a cap<br>
that allows the reader to find an introducer and speak the protocol is<br>
another matter.<br>
* It seems clear to me from reading your examples that there are serious<br>
issues with a flat namespace in a grid with multiple people.<br>
* The mechanism could be abused to store (small amounts) of data without<br>
write authorization, but perhaps that's not incrementally a bug. Once<br>
there is write authorization in place, this will be a bug.<br>
<br>
--<br>
Ticket URL: <<a href="https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2010#comment:1" target="_blank">https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2010#comment:1</a>><br>
tahoe-lafs <<a href="https://tahoe-lafs.org" target="_blank">https://tahoe-lafs.org</a>><br>
secure decentralized storage<br>
_______________________________________________<br>
tahoe-lafs-trac-stream mailing list<br>
<a href="mailto:tahoe-lafs-trac-stream@tahoe-lafs.org" target="_blank">tahoe-lafs-trac-stream@tahoe-lafs.org</a><br>
<a href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream" target="_blank">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream</a><br>
</blockquote></div><br>
</div></div></div>