[tahoe-lafs-trac-stream] [tahoe-lafs] #70: idea: integrate captcha into some furls

[tahoe-lafs]

#70: idea: integrate captcha into some furls
-------------------------------+-------------------------
     Reporter:  samuelstoller  |      Owner:  nobody
         Type:  enhancement    |     Status:  closed
     Priority:  minor          |  Milestone:  undecided
    Component:  code           |    Version:  0.4.0
   Resolution:  wontfix        |   Keywords:  uri captcha
Launchpad Bug:                 |
-------------------------------+-------------------------

Old description:

> Often when I share data with other people on the internet I do the
> following:
>
>  * Put the data in a directory on my web server.
>  * Add some .htaccess fu to my webserver to get basic auth protection of
> the data
>  * Mail the people a link to the data, I also put on a line following the
> URL the username and password necessary to access the data.
>
> This way if a search engine grabs the link, the data won't be accessible
> to the whole internet. (A human needs to read the email message and
> locate the http auth data necessary to follow the link.)
>
> Furls could emulate this captcha like behavior:
>  * have an 'incomplete' furl type; missing some critical bytes, but
> complete enough that the client can figure out whats going on to prompt
> the user for a key.
>  * the furl would be completed with a 'key' which a user can pass out-of-
> link.

New description:

 Often when I share data with other people on the internet I do the
 following:

  * Put the data in a directory on my web server.
  * Add some .htaccess fu to my webserver to get basic auth protection of
 the data
  * Mail the people a link to the data, I also put on a line following the
 URL the username and password necessary to access the data.

 This way if a search engine grabs the link, the data won't be accessible
 to the whole internet. (A human needs to read the email message and locate
 the http auth data necessary to follow the link.)

 Furls could emulate this captcha like behavior:
  * have an 'incomplete' furl type; missing some critical bytes, but
 complete enough that the client can figure out whats going on to prompt
 the user for a key.
  * the furl would be completed with a 'key' which a user can pass out-of-
 link.

--

Comment (by amontero):

 @samuelstoller: check lafs-rpg at https://bitbucket.org/nejucomo/lafs-rpg
 and/or this use case #2144 in case any can help.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/70#comment:8>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage