mailbox-like object type.
(Apparently the answer to your exact question is 'Now someone has'.)
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe
use a specific port, which you don't
need to do unless you're trying to run a public server behind NAT port
forwarding.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-de
e,
http://localhost:/ . It should contain a list of all
the storage server nodes the introducer has seen, which will help with
troubleshooting.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing l
uld prefer Accept over matching and
modifying a URL they receive).
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
nt results if the user later uses a different gateway.)
• collect readcaps and writecaps which can then be used to perform normal
access through non-compromised gateways.
• fail to renew leases, thus eventually allowing a user's files to be actually
deleted from the grid.
--
Kevin Reid
ps://tahoe-lafs.org/trac/tahoe-lafs/ticket/1824
Please check your tahoesvc.log to see if it is the same series of events.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.
com/economics/to-truck-barter-and-exchange-on-the-nature-of-valves-social-economies/>.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
ly
inspired by git having a mechanism to do this (AFAIK primarily used for
replacing ancestry, not replacing subdirectories; I haven't looked at its uses
myself).
> which inspired David-Sarah to announce that they were going to
> implement #954 during Hack Fest.
Perhaps this
On Mar 28, 2012, at 22:06, Brian Warner wrote:
> On 3/28/12 6:13 PM, Kevin Reid wrote:
>
>> LaunchDaemon. A LaunchAgent is per GUI-login session, a LaunchDaemon
>> is global. This goes in
>> /Library/LaunchDaemons/org.tahoe-lafs.tahoe.plist (or other
>> appropriat
#x27;
echo
done
These are the tools I use. I would be pleased if these, equivalents, or
improvements were included with Tahoe instead of being my private tools.
--
Kevin Reid <http://switchb.org/kpreid/>
___
anonical URL root is HTTPS.
Could someone (well, Zooko, according to the Mailman info) look into this?
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
ted and non-full storage servers.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
re-repair: 4 healthy, 1 unhealthy
1 repairs attempted, 1 successful, 0 failed
post-repair: 4 healthy, 1 unhealthy
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
e-existing Tahoe capabilities. I could 'tahoe mkdir' a fresh
directory and cp into it.
Any suggestions on how to do this more cleanly?
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
intended target; if there is a certificate
problem then the link is not succeeding at that job and proceeding
despite that would be a vulnerability.
For this concern, changing the UI doesn't help: the only thing that would be
better than trustworthy CAs would be including
inside a square, has no text) version.
My logo design fails this test as far as I can see.
I forget the reason I thought this was important when I thought of it.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tah
g the lease).
Hm. Perhaps a not-so-short lease expiration but *refuse to allow renewals*: all
files are guaranteed to disappear a certain time after uploading.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe
..]
As many copies of *the read-only version of* your rootcap as possible.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
ed at how nice installing Node.js from source
is.)
Is there a JavaScript-to-Python compiler yet? :-)
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
ir own gateway
(everybody's localhost:whatever). This is not *just* to support the
unhosted-web-app scenario, but also to protect a file-upload-and-download user
working through the WUI (which is one of my current two personal use cases for
Tahoe).
--
Kevin Reid
#1 serves only content
generated by Tahoe-or-Caja; Origin #2 serves only arbitrary uploaded content.
Any comments? Security issues? Do you think this is worth doing?
[Disclosure: I am currently being paid to work on Caja.]
--
Kevin Reid <http://
ducer. In what document did you find the furl
you're using?
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
f complex distributed
> systems.
What does Nilestore do that Tahoe does not? What makes this not a duplication
of effort?
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
d
file or different convergence secret, but it should be sufficient for DMCA
compliance as I understand it (IANAL).
I just *might* be interested in working on implementing this at some point in
the future.
--
Kevin Reid
y see version 1, then version 2, then
3, then 2 again.”
2. Looking at the capability mechanisms, it's not clear to what
extent capabilities are bound to individuals. The standard problem
with key-based capabilities mechanisms is that they can be copied.
That's a fea
-r option, but then claims
that directories will be copied recursively [by default]. Which is it?)
You can then get the data again with a reversed copy command, or view
it on the web via
tahoe webopen my-data:
Tahoe stores your aliases in ~/.tahoe/private/aliases.
--
Kevin Rei
/tahoe-lafs.org/pipermail/tahoe-dev/2011-January/005966.html
This reads to me as non-agreement about "what is a filename" not "what
does Tahoe-LAFS do with filenames-in-sense-a".
--
Kevin Reid <http://switchb.org/kpreid/>
__
ure this!" advice
until non-defaults are set.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
TCP's ordering
guarantees: you want new messages to go through even if they arrive
before old messages do (or can be assumed to have failed to arrive).
(Disclaimer: I have not actually implemented any of the above anywhere.)
--
Kevin Reid
d whatever they want to servers, as long as it's properly
formatted as a share.
Yes, but they can't upload something that looks like a share of file A
but actually contains some other content (unless they find a hash
collision).
--
Kevin Reid
question: What are the advantages of your
protocol over WebDAV? I've implemented WebDAV, and while it does have
a certain amount of architecture bloat, it doesn't seem -- at the
moment -- worth using a different protocol just for that.)
--
Kevin Reid <
ges (I use them myself) ...
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
d of onto their local hard
drive. :-)
But I want the visualizer to visualize what's wrong with my slow,
stumbling grid!
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@t
e find a good
solution) violating this dependency management principle.
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
o.svg
http://tau.rycee.net/tahoe-logo.png
I don't like that the hyphen in the name is gone due to the wrap. I
think that if the name is in the logo, it ought to be spelled the same
way as it conventionally is.
--
Kevin Reid <http://switc
asterizer.html>
(The existing size was chosen to be similar in height to the logo
currently on tahoe-lafs.org.)
* If you render it, make sure you have the Futura font or the layout
will be more or less off depending on font metrics.
--
Kevin Reid
On Aug 19, 2010, at 19:02, Zooko O'Whielacronx wrote:
3. The Tahoe-LAFS logo (ha! trick question! we never finished
designing a logo. I vaguely recall that Kevin Reid had the best
candidate but that I wasn't 100% satisfied with it yet.)
http://switchb.org/kpreid/2009/tahoe/
I thin
swap space -- especially since
it went back on reboot. Next time, check the size of /private/var/vm
before rebooting (if you can).
--
Kevin Reid <http://switchb.org/kpreid/>
___
tahoe-dev mailing list
tahoe-dev
38 matches
Mail list logo
