Changes between Version 28 and Version 29 of WeeklyMeeting


Ignore:
Timestamp:
2012-11-15T18:21:13Z (12 years ago)
Author:
zooko
Comment:

archive today's agenda, post next week's

Legend:

Unmodified
Added
Removed
Modified

  • WeeklyMeeting

    v28 v29  
    1818== Agenda ==
    1919
    20 URL: https://plus.google.com/hangouts/_/748b6f70b1845e6bbede00fd399a7ce7f8ef3a7f
     20URL:
    2121
    22 Upcoming: 2012-11-15
     22Upcoming: 2012-11-22
    2323
    2424This will be a ''TESLA COILS AND CORPSES'' meeting: science, big new features, writing papers about our work, etc. If you're more into ''NUTS AND BOLTS'' then stay tuned for a future meeting about engineering, debugging, making stable releases, etc.
    2525
    26 Agenda: async notifications
    27 
    28 What a ''lot'' of people really want is an alternative to Dropbox — something that functions very like Dropbox but without exposing your plaintext to spying and corruption. David-Sarah implemented a part of this with the drop-upload feature. It seems to me that the blocker which prevents Tahoe-LAFS from doing the rest of it is that LAFS clients have no way to get an asynchronous notification that a file has changed (i.e., so that they don't have to poll to find out if the file has changed). So: could we add that? Why not just define a remote interface offered by LAFS clients to LAFS servers. The remove interface is "hey_you_this_file_has_changed(storageindex)".
    29 
    30 Another approach would be to embrace a standard mechanism like !PubSubHubBub. That might help with our long-term goal of moving from foolscap to HTTP, and it might let us benefit from the work others do on issues around this such as DoS and scalability.
     26Agenda: Proof-of-Retrievability
    3127
    3228== Proposed Future Topics ==
    3329
    3430* **Tahoe-LAFS v1.10** What can we do to move Tahoe-LAFS v1.10 along? Is David-Sarah too busy with !LeastAuthority.com to be Release Manager for Tahoe-LAFS v1.10? Should Tahoe-LAFS v1.10 contain only patches that are already on trunk?
    35 
    36 * **Proof-of-Retrievability** review of a paper draft Zooko will distribute. (was scheduled: ~~2012-10-30~~)
    3731
    3832* **Rainhill design review** which David-Sarah will distribute; call for outside crypto expert reviewers. (was scheduled: ~~2012-11-06~~)
    … …  
    4135
    4236== Notes / Archives ==
     37
     38=== 2012-11-15 ===
     39
     40* async notifications
     41
     42What a ''lot'' of people really want is an alternative to Dropbox — something that functions very like Dropbox but without exposing your plaintext to spying and corruption. David-Sarah implemented a part of this with the drop-upload feature. It seems to me that the blocker which prevents Tahoe-LAFS from doing the rest of it is that LAFS clients have no way to get an asynchronous notification that a file has changed (i.e., so that they don't have to poll to find out if the file has changed). So: could we add that? Why not just define a remote interface offered by LAFS clients to LAFS servers. The remove interface is "hey_you_this_file_has_changed(storageindex)".
    4343
    4444=== 2012-11-08 ===