On Thu, Feb 12, 2015 at 10:31 AM, Lukas Pirl tahoe-...@lukas-pirl.de wrote:
I just wanted to reply to a ticket but this comment got a 95.19% spam
rating?!
What? Argh.
Hm… I'm not sure, but I think what is happening is that spammers have
started submitting complete English texts that they've
Thanks, Jakob!
Is there any reason why all of that shouldn't happen automatically by
default when a user runs Tahoe-LAFS? If not, then let's create an
issue ticket for it!
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
.. -*- coding: utf-8-with-signature-unix; fill-column: 73; -*-
Tahoe-LAFS Nuts Bolts, 2015-02-10Z
in attendance: Daira, Brian, Zooko (scribe), David
We worked on the upcoming Tahoe-LAFS v1.10.1 release. We reviewed,
refactored, and merged a new contribution
Hi Lukas, thanks for the bug report! I don't immediately know why this
could be happening. I know that a lot of others use Tahoe-LAFS on
FreeBSD, so it isn't something that fails *all* the time on FreeBSD,
but because the only node that has this problem in your setup is your
only FreeBSD node,
in attendance: Zooko, Daira, Brian
We spent about two hours working on filenames support on Windows --
long file names, UNC paths, etc. This is because these issues are
slated to go into the imminent Tahoe-LAFS v1.10.1 release.
It's amazing how much work it is to get such basic normal
Hi Kyle!
Sorry that I didn't see this before now.
I'm sorry that the error message is so frustrating. Fixing that is the
topic of https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2101 (improve
error messages from failed uploads). The best solution would be for it
to just show, visually, a complete
On Sat, Nov 8, 2014 at 9:44 AM, Shu Lin lin...@gmail.com wrote:
Hi,
I like to use Tahoe in an application which I will add new servers
dynamically in new locations (across WAN link). I am wondering how hard and
how to implement a feature to distribute the shares saved in
Folks:
At a Hack Fest, Daira was asking me about something. She mentioned how
our policy requires unit tests to accompany any patches that change
behavior or fix bugs. And, she asked, what if the patch changes the
behavior of the build system, or fixes bugs in the packaging code — do
we make an
On Tue, Sep 9, 2014 at 10:57 AM, 袁盛东 xiao_s_y...@163.com wrote:
Hello everyone,I upload a 50M file to the tahoe system,I want to know is
the cumulative encoding 2.19s means the zfec encoding time ?
It is the time to do both zfec encoding and AES encryption.
I chose the (3,6) as the
What about #2235? It is a pressing issue for LeastAuthority's
Windows-using customers, and there is a patch that is more-or-less
complete. (Owned by Daira at the moment.)
Regards,
Zooko
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2235# Error from 'tahoe
cp' on Windows, due to a long path
On Tue, Sep 2, 2014 at 7:56 PM, Ruben Pollan mes...@sindominio.net wrote:
Is there any chance to get 2045 (Make the paths of the different folders
configurable) in 1.11? Can I do something to speed up the review process,
it's
being a month since we started it.
Will be great if we enter in
On Tue, Sep 2, 2014 at 10:36 PM, Mark Berger mjber...@stanford.edu wrote:
Can someone send me the invite for the next meeting?
Done!
I'm not sure I'll be able to attend but I'll try to if you're all looking at
the happiness stuff.
Great! Delighted to have your help!
I'll try to get the
On Sat, Mar 22, 2014 at 12:54 PM, Greg Troxel g...@ir.bbn.com wrote:
I just rebuilt tahoe-lafs from pkgsrc with updated py-OpenSSL and the
newly vast set of dependencies for it. So far everything seems to be
ok. I ran a deep-check --add-lease over an alias with about 5500
objects (and I
On Wed, Feb 12, 2014 at 10:26 PM, nvw6lxh2yt...@pyramidheadgroup.ca wrote:
Hello,
Hello! Welcome.
unable to execute cc: No such file or directory
It sounds like it is trying to invoke the compiler (which is an
executable named cc) and it can't find it. So this is an occurrence
of
Hi! Welcome.
On Tue, Feb 11, 2014 at 3:22 AM, Gavin King gavinkin...@gmail.com wrote:
[root@vps3 allmydata-tahoe-1.10.0]# python setup.py build
Not found: tahoe-deps
Not found: ../tahoe-deps
twisted/runner/portmap.c:10:20: error: Python.h: No such file or directory
That's:
Dear Lukas Pirl:
Thanks for the data!
On Sat, Dec 28, 2013 at 3:39 PM, Lukas Pirl m...@lukas-pirl.de wrote:
* Timings:
* File Size: 1073741824 bytes
* Total: 7 minutes (2.32MBps)
* Storage Index: 47 seconds (22.84MBps)
* Peer Selection: 6.12s
* Encode And
Hello, Lukas Purl:
Thanks for the note! Could you please look at the timing measurements,
from the Recent Uploads and Downloads page when doing this experiment,
and post here what you learn? Thanks!
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1375# the performance
stats for each upload or
Folks:
(This is a copy of
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/795#comment:13 .)
Here's my rendition of our discussion of add-only sets at the Tahoe-LAFS
Summit today. (As usual, I altered and embellished this story significantly
while writing it down, and people who were present to
Hm, I did a duckduckgo search on how to strip out the DKIM-Signature
header, and found this:
https://bugs.launchpad.net/mailman/+bug/557493
which says it was a bug that GNU Mailman used to strip those out and
that in GNU Mailman 2.1.10 they changed it to leave them in. We
recently upgraded, so
On Thu, Nov 7, 2013 at 4:58 PM, Arthur Breitman
arthur.breit...@gmail.com wrote:
Is there anything of the sort planned or available in Tahoe?
Interesting that you should ask! This is called a Proof-of-Retrievability.
Tahoe-LAFS as it currently exists already has *most* of a
On Fri, Nov 8, 2013 at 2:55 PM, Greg Troxel g...@ir.bbn.com wrote:
(Regardless of DKIM, I am opposed to subject munging. It takes up space and
provides no value for people with adequate mail setups.)
Okay, I just tried to turn off the feature of prepending [tahoe-dev]
to the Subject lines.
On Mon, Oct 21, 2013 at 6:26 AM, Brian Warner war...@lothar.com wrote:
* trac is running, but page rendering is omitting headers and footers,
which means there's no nav bar to find the other pages
This happens every time we upgrade trac:
http://trac.edgewall.org/ticket/7463#comment:15
*
On Mon, Oct 7, 2013 at 6:12 AM, Garonda Rodian deeps...@hotmail.com wrote:
I've been attempting to start a basic menu system to build grids
Cool!
when I try the ConfigParser write method, all of the commented out entries in
the tahoe.cfg are removed...
I would suggest *not* having the menu
On Thu, Oct 17, 2013 at 1:54 AM, Garonda Rodian deeps...@hotmail.com wrote:
Are there any benchmarking modes for tahoe-lafs? I'd like to see the
throughput for the encryption step, and for the zfec step, and the hashing,
etc., to be able to compare setups.
Yes, there is a builtin feature
On Sun, Oct 13, 2013 at 9:09 PM, Callme Whatiwant nejuc...@gmail.com wrote:
Thanks Patrick! Before I accepted this, I was hoping people with more
knowledge of recent TLS vulnerabilities and/or forward secrecy could take a
glance at the cipher list and comment on if it's still Today's Best
Dear Garonda Rodian:
It sounds like you're confusing the authority to access certain
files-and-directories (which ultimately boils down to some
cryptographic keys and/or cryptographic identifiers) with the
authority to upload data. The former is currently controlled by those
caps that you named,
Welcome, Garonda Rodian!
Thanks for the nice user report!
On Wed, Sep 25, 2013 at 2:49 AM, Garonda Rodian deeps...@hotmail.com wrote:
First, let me say the quickstart guide is great;
Thanks for the positive feedback! We get a lot of negative feedback on
the docs for new users, and so I still
Folks:
Tahoe-LAFS is one of the featured projects at the GNU 30th Birthday
Party Hackathon!
https://www.gnu.org/gnu30/celebration
I'm going to be there in person in Cambridge. What I want to do during
the Hackathon is make Tahoe-LAFS work better with Tor and/or I2P. I
know that at least a
Kyle:
Thanks for the good explanation! If I understand correctly, Mark's
#1382 branch will fix this problem, by making it so that a server that
already has a share of a file will not get another share of that same
file assigned. You could help by examining Mark's branch — perhaps you
could look
Dear Kyle:
Could you try Mark Berger's #1382 patch on your home grid and tell us
if it fixes the problem?
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1382# immutable peer
selection refactoring and enhancements
https://github.com/tahoe-lafs/tahoe-lafs/pull/60
Regards,
Zooko
On Wed, Sep 11, 2013 at 9:16 PM, Bodecs Bela bode...@vivanet.hu wrote:
Ok, I will try tomorrow. If I finish, where or how should I put the altered
code?
Well… For now would you just email me a patch? Thanks!
Regards,
Zooko
___
tahoe-dev mailing
Dear Bodecs Bela:
Thank you very much for finding and fixing this bug! Could you please
extend test_zfec.py ¹ so that it will exercise the bug? To do that, I
guess you just need to make sure that _help_test_filefec() gets
invoked with the right parameters and input length to trigger the bug.
Folks:
Here's some recent news:
http://m.washingtonpost.com/world/national-security/us-spy-agencies-mounted-231-offensive-cyber-operations-in-2011-documents-show/2013/08/30/d090a6ae-119e-11e3-b4cb-fd7ce041d814_story.html
That article says that the U.S. espionage agencies have
surreptitiously
Okay, following-up to my own post, now I have kind of a confession to
make: this is part of why I've been pushing so hard on the
source-based distribution of Tahoe-LAFS all these years. The prospect
of malware inserted into binaries that get redistributed is one of the
reasons why I've tried to
On Mon, Aug 19, 2013 at 1:07 PM, Jacob Appelbaum ja...@appelbaum.net wrote:
Are there open bugs and a sketch of what each unit test would look like?
Jeff from the I2P project has added the tag i2p-collab to all of the
tickets that are current blocking their use of Tahoe-LAFS trunk:
Let's move this conversation from the tahoe-dev mailing list to
comments on this bug tracker:
https://bugs.launchpad.net/pyopenssl/+bug/434411/
I believe the file doesn't exist because the unit-test-runner rm -rf's
the test directory after running the tests. You could edit the source
code of:
On Thu, Aug 15, 2013 at 5:41 AM, han zheng z.han0...@gmail.com wrote:
I have done something about this. I have written some code for tahoe to
automatically schedule repair process.
Hooray!
the basic idea like this: run a monitor service when tahoe client runs,
detect file's health'state
http://tny.cz/4c65796a
File
/Users/Frank/allmydata-tahoe-1.10.0/support/lib/python2.7/site-packages/Twisted-13.0.0-py2.7-macosx-10.5-i386.egg/twisted/internet/_sslverify.py,
line 101, in _copyFrom
value = getattr(x509name, name, None)
exceptions.UnicodeDecodeError: 'utf8' codec can't
On Thu, Aug 15, 2013 at 7:43 PM, Frank frankdmarti...@gmail.com wrote:
What is the recommended approach for diagnosing/correcting this issue?
I suspect that it is a problem in the binary build of the pycryptopp
or Twisted libraries (eggs). Do you know where you got those files?
Your logs from
On Fri, Jul 19, 2013 at 6:47 AM, Steven Lee elde...@outlook.com wrote:
I searched on Internet and found no one has ever been interested in this, so
I think there must be some reasons.
The reason nobody has tried it is that just that people don't know
about Tahoe-LAFS, or they haven't thought
On Tue, Jul 16, 2013 at 8:16 PM, Zooko O'Whielacronx zoo...@gmail.com wrote:
Sorry to see you go! Thank you for participating in the Tahoe-LAFS project.
Haha! I'm very amused at myself for accidentally posting to the public
list when I meant it to be a private note to Iantcho.
Anyway, would
On Thu, Jul 18, 2013 at 7:53 PM, Greg Troxel g...@ir.bbn.com wrote:
Can you fix the list to stop adding reply-to, then?
Okay, I've changed this. Now if you reply to a message, and you want
your reply to go to the whole list, you have to manually adjust your
headers before sending your reply.
On Wed, Jul 17, 2013 at 3:05 PM, Mark Berger mjber...@stanford.edu wrote:
I can confirm that 'python setup.py build' wiill not run on OSX 10.8 without
sudo. The error message is error: src/allmydata/_version.py: Permission
denied.
This means that the file ./src/allmydata/_version.py was
Also, apparently the i2p people are maintaining and using their
version of the ticket #68 patch.
As far as I remember, the blocker for merging #68 is simply that we
need someone to volunteer to write a unit test for it. See our
discussion in a Weekly Dev Chat where the core devs agreed to support
Hi there!
I haven't heard of anyone using check_load.py ¹ in a long time, and
there are no automated tests of it, so it has probably bit-rotted.
¹
https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/test/check_load.py?annotate=blamerev=fff237be9a0c4dc5b6c6cdfb596fedc877d748ae
Correct: python setup.py install will not work without sudo or root
privileges. However, python setup.py build *will* work without sudo
or root privileges. The instructions ¹ do not instruct the user to run
python setup.py install!
However, users often run python setup.py install even though the
Folks: I never got around to sending my Weekly Dev Chat report for
last week, so here is last week's followed by this week's.
Tahoe-LAFS Weekly Dev Chat, 2013-07-09
in attendance: Andrew, Brian, Daira, Leif, Amber, Mark, Tariq, Zancas,
Zooko (scribe)
LeastAuthority.com is about to announce a
On Tue, Jul 9, 2013 at 2:12 PM, til til...@yahoo.com wrote:
° Tahoe needs several extra Python Software Packages to be installed. Some
of them need to be compiled for your specific platform (Twisted, pyOpenSSL,
zfec, pycrypto, pycryptopp, zope.interface) some of them dont. Since you
need to
Sorry to see you go! Thank you for participating in the Tahoe-LAFS project.
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Folks:
Mark B has done a great job on his Google Summer of Code project so
far! See his GSoC blog:
http://markjberger.blogspot.com/
And my notes from a Weekly Dev Chat:
https://tahoe-lafs.org/pipermail/tahoe-dev/2013-July/008486.html
Since he has already more or less finished the first two
On Tue, Jul 9, 2013 at 11:39 AM, Greg Troxel g...@ir.bbn.com wrote:
So I think before we add padding as a non-experimental features, we need
a paper analyzing the block-level-crypto vs encrypted files trade
space, and discussing the understand-file-size threat model
I hope such a paper
No, no, we rely on the correctness of our encryption to hide all
information about the plaintext from an attacker who doesn't know the
encryption key. Therefore, the pad bytes are all just zero bytes, and
we believe that this pattern gives nothing useful to the cryptanalyst.
(Our encryption is
On Tue, Jul 9, 2013 at 9:53 AM, Iraklis . leont...@gmail.com wrote:
That would destroy any dedup service if different random bytes are appended.
Even if the same number of random bytes are appended for equivalent
encryption keys. Or i am missing sth?
Hello, Iraklis! Good to hear from you.
Folks:
I think Tahoe-LAFS should automatically pad files when encrypting them
in order to hide the specific length of the file. Avi Freedman just
reminded me of this issue in private email conversation, so I finally
got around to writing up a proposal that has been nagging me for years
(ticket
On Mon, Jul 1, 2013 at 2:18 PM, Daira Hopwood
davidsa...@leastauthority.com wrote:
foolscap sends periodic keepalive messages; an address change should cause
this to fail and the connection to be renegotiated. I don't know the details
well enough to tell why this may not have worked.
Foolscap
On Thu, Jun 6, 2013 at 1:46 PM, Shakuni Gandhaar shak...@ymail.com wrote:
I am trying to run the Tahoe-LAFS code in Kivy to make my Android phone a
node in the grid.
Cool!
I am running to a number of module dependency issues. Has any one tried this
before, are there any instructions to
On Wed, Jul 3, 2013 at 3:36 PM, Mike Nation mnat...@cvt.org wrote:
Just confirming one last time that there aren't any ideas as to why I'm
receiving this error when trying to connect to the testgrid:
c:\allmydata-tahoe-1.10.0bin\tahoe.pyscript start
STARTING
On Tue, Jul 2, 2013 at 2:02 AM, Richard Kiss h...@richardkiss.com wrote:
Erasure coding fascinates me.
I ported the zfec command-line tool to JavaScript. It's a bit rough, but it
seems to work.
Very cool! Thank you!
Next port pycryptopp to JavaScript… ;-)
Regards,
Zooko
Greetings, stig atle.
Welcome! I look forward to seeing what you come up with!
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Folks:
I'm not very satisfied with the current state of the
IP-address-auto-discovery stuff.
Yet another new user just mentioned on IRC that they were blocked by
some kind of problem with the subprocess invocation of ifconfig. It
turned out that in their case ifconfig wasn't on the PATH for
Dear Sameer:
Cool! Thanks for the note and the nice write-up on your blog!
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
I think the Introduction to Algorithms has a succinct description of
Edmonds-Karp:
https://en.wikipedia.org/wiki/Introduction_to_Algorithms
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
On Mon, Jun 10, 2013 at 3:35 AM, Mark Berger mjber...@stanford.edu wrote:
What uploads shares to their designated servers? In upload.py there is a
mention of bucket writers but I can't seem to find anything else about them.
It's awfully hard to see, from looking at the upload.py code [¹],
Hi t.!
How about test the SFTP service directly and make sure that works
before trying to connect ownCloud to it? Run the sftp client and
connect it to the appropriate port, login with the username and
password that you configured into the accounts file (per
On Fri, Jun 7, 2013 at 5:49 AM, Anders Genell anders.gen...@gmail.com wrote:
Hehe, yes, worry is a very human trait :-)
But I can also imagine some slight practical use in having an up to date
list. We plan to invite friends who are not so very computer savvy, and it
would be good to see if
On Thu, Jun 6, 2013 at 1:46 PM, Shakuni Gandhaar shak...@ymail.com wrote:
I am trying to run the Tahoe-LAFS code in Kivy to make my Android phone a
node in the grid.
Cool!
I am running to a number of module dependency issues. Has any one tried this
before, are there any instructions to
It doesn't bother the Tahoe-LAFS clients to know about old servers
that are no longer connected. The main harm from it is it enlarges the
list of known servers and makes humans worry about whether the old
long-gone ones are causing some kind of trouble by still being in that
list.
Regards,
Zooko
This is interesting!
Corruption of shares is pretty rare. It would most likely be caused by
something like the disk being full when a share was being written, or
a program accidentally overwriting parts of the files that contain the
shares, or some such. This report you got says that it found
Hooray! I'm looking forward to working with you, Mark. Could you
kindly tell me again when your classes are finished? This time I'll
write it on my calendar. Also, if you can attend Weekly Dev Chats even
before your classes are finished, that would probably be a good way to
do community bonding
tilllt:
Thanks for the report! I'm glad to hear that it worked.
If anyone reading this wants to help support Tahoe-LAFS on Raspberry
Pi, we need someone to build six binary packages for armv6l: ticket
#1983.
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1983# build binary eggs
for linux-armv6l
On Wed, May 29, 2013 at 5:31 PM, Pierre Abbat p...@bezitopo.org wrote:
The problem turned out to be that I was trying to upload the file with
version 1.8 (on Ubuntu LTS), but my server is running 1.9 (on DragonFly).
When I uploaded the same file from the DragonFly box, it worked. The other
Ah, I see that there is already a trac ticket for this issue: #1707
The patch below ought to fix it for you. I've opened a new ticket
#1988 to talk about another possible solution.
Regards,
Zooko
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1707# iputil cannot get
local IP addresses on newer
On Sun, May 26, 2013 at 4:57 AM, Pierre Abbat p...@bezitopo.org wrote:
Since the last time I tried, I upgraded the kernel, world, and packages. I
have tahoe-lafs-1.9.2 and python 2.7.3nb3 on DragonFly BSD 32-bit. It still
dumps core when I run tahoe start .. I put the core dump where Daira
On Wed, May 15, 2013 at 5:24 AM, Randall Mason clashthebu...@gmail.com wrote:
This discussion addresses the use after the one year of the TGPPL. Could
somebody confirm if this is true:
The period before the one year you can do anything with it, including
releasing complete closed source
Thank you for the notes about the brainstorming of future Tahoe ideas, Tony!
This is the one that most caught my attention at the Users Group Meeting:
- Replace Foolscap with a simplified Tahoe-specific wire protocol
...
In order for tahoe to grow up and be a first-classprotocol, have a
Greg:
Yes, I will continue to distribute zfec under the current terms of
either GPLv2-or-newer or TGPPLv1-or-newer at your option. In addition,
I intend to add the Apache exemption, so that distributing derived
works where the other bits are Apache-licensed is allowed.
In a separate letter, you
On Tue, May 14, 2013 at 10:41 AM, Daira Hopwood (formerly David-Sarah)
davidsa...@leastauthority.com wrote:
1. If we combine TGPPL code with Apache code to create one work derived from
both TGPPL code and Apache code, can we redistribute such work under Apache
license only and permanently?
It's so confusing.
Yuanz's original question was ambiguous: is he asking whether it is
legal to build a derived work out of Apache-licensed (Swift) code
combined with GPL-or-TGPPL-licensed (Zfec) code? Or is he asking
whether it is legal to build a derived work out of Apache-licensed
code,
Hi Mark! I'm sorry it took almost a month to respond to this.
On Sat, Apr 13, 2013 at 3:20 PM, Mark Berger mjber...@stanford.edu wrote:
Response: 550 Requested action not taken: internal server error
...
From tahoe's twisted log:
timed out waiting for DTP connection
Please look
On Thu, May 2, 2013 at 6:27 AM, Jonathan Dill jonat...@nerdsgroup.net wrote:
As an outsider I'd say make a homepage on vhost www separate from Trac that
is simplified with either tabs or menus in the banner including Downloads.
You can embed content from Trac, you just don't want it to be the
Unsure, I'd have to see a more concrete proposal. I don't particularly like
the idea of partitioning what developers do from what users do, since then
developers won't be testing the user packaging in the course of normal
development.
This is a really good point. It is the exact opposite
Yay! Thanks to Brian for being Release Manager this time around!
Until we update trac to point into git history by default instead of
into darcs history, you have to insert a /git/ into these links to
see the current versions:
[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/git/NEWS.rst
[2]
I was wondering if and when ticket #68 is going to land in the trunk?
For a long time we core developers — especially Brian — were sort of
reluctant to move forward with that, because we intend to make a
better, more general thing in the future
* use 1.11 instead of 1.11.0 for the initial release
+1
* rewrite relnotes.txt: it's almost entirely boilerplate, and (being
in the source tree) cannot contain strong identifiers like hashes of
the release tarballs or the git revision id. What I've done for other
projects is: one
Hi Paul Rabahy, thanks for the bug report!
On Fri, Apr 26, 2013 at 7:36 PM, Paul Rabahy prab...@gmail.com wrote:
c:\users\prabahy\downloads\allmydata-tahoe-1.10.0c2\src\allmydata\storag
e\immutable.py, line 52, in __init__
fileutil.make_dirs(os.path.dirname(self.home))
File
Hi, t. Welcome!
What are you trying to do? I'm very interested in making it easier for
people to start using Tahoe-LAFS, but at the moment I don't understand
what is complicated about it or if it _is_ actually complicated, or if
it just seems intimidating until you try it.
Regards,
Zooko
On Tue, Apr 23, 2013 at 8:05 AM, Greg Troxel g...@ir.bbn.com wrote:
I am guessing that he wants file storage space under owncloud (which is among
other things a fileserver) to be backed by tahoe (vs local disk vs some sort
of cloud provider storage).
The natural thing to do would be to
I was pleased about Leif contributing more patches and docs and bug
reports recently, but now look!
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1938#comment:2
Leif is apparently deterred from contributing because of the lack of a
public declaration of the nature of the Tahoe-LAFS Software
Dear Mark:
Yay! Good proposal! I'm excited about the prospect of getting some
focused work on improving repair and rebalancing. There are a lot of
different ways that the functionality could be improved.
I'm not sure, but I have the _feeling_ that the #1382 that Kevan
Carstensen started may be
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/GSoCIdeas
In case any GSoC students are looking for ideas:
Make It Go Faster
Tahoe-LAFS is very slow at downloading files. Potential users have
been looking at this and then deciding not to use Tahoe-LAFS because
they need better performance. Figure
Hi, Dieter! Welcome.
On Tue, Apr 16, 2013 at 11:55 AM, Plaetinck, Dieter die...@vimeo.com wrote:
I'm looking to build a large highly available storage cluster
i'm not really interested in the specific encryption/security features. So
far I've been using openstack swift
for a smaller cluster
2013-04-11
in attendance: Zooko (scribe), ClashTheBunny, Daira, Andrew, Amber, Rohit,
Tariq
The agenda was Nuts and Bolts.
ClashTheBunny has fleshed out MarcusW's IPv6 patches for foolscap and
Tahoe-LAFS. We spent the dev chat working on the tests. It already has
thorough tests, but we want
Are you a student? Want to get paid to hack on Tahoe-LAFS this summer?
Go here!
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/GSoCIdeas
Then write to this mailing list, join the IRC channel, or show up at
next week's Weekly Dev Chat.
Regards,
Zooko
Folks:
I just made a pass through the 1.10 Milestone:
https://tahoe-lafs.org/trac/tahoe-lafs/milestone/1.10.0
I don't see any more tickets that I can directly help with.
So, for this coming Weekly Dev Chat (Thursday), we're going to hack on v1.11!
On Wed, Mar 27, 2013 at 10:56 PM, Daira Hopwood (formerly David-Sarah)
david-sa...@jacaranda.org wrote:
This is ticket #1258. It's a design flaw in setuptools and/or the
Python import mechanism; the cause is explained at
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1246#comment:6 and
On Mon, Mar 11, 2013 at 12:26 PM, Greg Troxel g...@ir.bbn.com wrote:
To me, this seems like needless churn. I don't think the current scheme is
broken.
Noted! Thanks for the feedback.
The advantage of $YEAR.$WHATEVER versioning is that then people who
don't have any memory of Tahoe-LAFS
Dear Paul Rabahy:
That's awesome that you're writing regular reports about the test
grid! Thank you!
Regards,
Zooko
___
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Thanks a lot for the notes, Alex! It does indeed look like the RADOS
layer of Ceph has a lot in common with LAFS and maybe we can learn
from things they've done that we've only imagined. Also, I wonder if
the POSIX↔object-storage layer of Ceph, which I guess is the Ceph MDS
nodes? Could be pressed
I'm looking at this book Producing Open Source Software by Karl
Fogel. I kicked in some money on kickstarter to fund the second
edition of it. This section caught my eye:
http://producingoss.com/en/producingoss.html#bug-tracker-usage
I think we haven't been doing this one. For example, looking
On Fri, Jan 25, 2013 at 12:51 AM, Uncle Zzzen unclezz...@gmail.com wrote:
I've been looking at https://www.filerock.com/ and although I have some
reservations (server isn't open source, reasons to believe they collect
statistics - e.g. web interface has google analytics, etc.) it's still
1 - 100 of 346 matches
Mail list logo
