> > http://127.0.0.1:8888/__USE_DATE_20020817__SSK at
> > rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/TFE//
I think that the user interface should work like this:
1) User goes to TFE, and clicks on a link for a site.
2) After a while, fred says DataNotFound, and fproxy draws a page that
looks like this:
Data Not Found (network error)
Freenet could not find the key you requested (SSK at blahblahblah).
Your node tried to ask 15 other nodes; if you wish, you may try another
request to more nodes:
new HTL: __16__ [ Go ]
Or, since the key you tried to request is a date-based redirect
document, you may attempt to fetch an older version instead:
__1__ days ago [ Go ]
3) Of course, this would only be done for DBR sites. For an edition
site (or an editionless site), the last part would be omitted.
4) The "__1__ days ago" part, and the text before it, would have to be
changed if the request is already in the past. Something like this:
Or, since the key you tried to request is a date-based redirect
document 1 day in the past, you may attempt to fetch an older or
newer version instead:
__2__ days ago [ Go ]
End users should not be expected to convert a date to hexadecimal and
insert it into the middle of a URL, with a hyphen. Nor should they
be expected to put "?date=YYYYMMDD" at the end of a URL, nor should
they be expected to put "__USE_DATE_YYYYMMDD__" in the middle of a
URL. Fproxy should handle this gracefully.
--
Greg Wooledge | "Truth belongs to everybody."
greg at wooledge.org | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20020831/7b5a5b21/attachment.pgp>
