Leif Ryge wrote:
I think the idea would be to have a web publishing app which doesn't
necessarily expose Tahoe-LAFS to users directly, but rather just has a
"Publish" button which uploads to it.
That would be really cool =) The URL problem is still a problem, but
for use cases where url mem
I think the idea would be to have a web publishing app which doesn't
necessarily expose Tahoe-LAFS to users directly, but rather just has a
"Publish" button which uploads to it. The only user exposure to Tahoe-LAFS
would be that the URLs contain lengthy cryptographic idenitifers (read
capabilities)
I'm working on a project with the same goals (Stormy), but not sure
what the status is for formalized Torstuff.
For me at least I'm not interested in using Tahoe because it adds
unnecessary complexity. My work with users typically shows that people
have learned or been taught how to use P
