Nuts and Bolts Moves to a New Time

"Hey everybody.. we're moving the twice-weekly developer videochats up by an hour, to make life easier for folks in europe. (the google calendar entry that zooko managed was tied to UTC, and the transition to daylight savings time pushed it an hour later for everybody).

We do these Tuesdays and Fridays (mornings in the US, evenings in Europe).

The new time is:

• 0900 (9am) San Francisco (PDT)
• 1600 UTC
• 1700 (5pm) London (BST)
• 1800 (6pm) Berlin (CEST)
• 2130 (930pm) Mumbai (IST)
• 0400 (4am) Auckland (NZST) (sorry)

In the (northern-hemisphere) "winter", we'll move it forward to 1700 UTC to keep local times the same. To honor the arbitraryness of time zones, we'll make the transition on a randomly-selected date using a weighted average of the local DST rules of the participants. For a long-term fix, please see https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1934 .

We're using talky.io for the hangouts these days (instead of google).. seems to work pretty well. The URL is:

• https://talky.io/tahoe-lafs" [0]

Gmail Classifying TWN as Spam

It turns out Gmail is classifying some TWN emails as spam. Patrick created #2772 to deal with this issue. If your Gmail account classifies TWN as spam, please provide the why is this spam reasoning to the ticket. Thank you to our users who already provided this information. We hope to have this resolved soon.

Tuesday, 04/19

Attendees: Brian Warner, Daira Hopwood, meejah, Patrick R McDonald, Leif Ryge, David Stainton

Patrick broached the idea of reproducible builds. As a first step, Brian suggests we use requirements.txt and hashes

Daira added a "python -m allmydata.scripts.runner" -style mode and also changed tests that use subprocess(bin/tahoe) to use subprocess(sys.executable, -m, allmydata.scripts.runner). The next step is to remove 'setup.py make_executable' and remove bin/tahoe

David brought up the excellent point that we could use a packager for BSD systems.

In regards to magic-folder, meejah will rebase for landing next week (some pieces were landed on master, and no longer need to be in the branch).

Below is the Tor/multiintroducer plan.

• land 2491-sync next week

• then land the Tor foolscap client connection handler plugin somewhere: either in Tahoe itself, or a 3rd package (but not in foolscap)

• multi-introducer / introducerless / tor-client branch may be ready to land next week too, will enable client-side

• Tor server-side:

  • meejah will work on a txtorcon function that: starts Tor with --no-network, creates ephemeral HS, retrieves private key and onion address, shuts down Tor
  • tahoe create-server will use that function to compute the tub.location, store private key into NODEDIR/private/ somewhere
  • tahoe start will (synchronously) call Tub.setLocation(), (synchronously) use txtorcon to create endpoint, pass endpoint to Tub.listenOn()
  • still need to decide about CLI arguments. "tahoe create-server --tor"? --listen-tor?
  • foolscap needs a test to see if startTLS works over unix-domain sockets
  • ideally SOCKs, Tor-oubound, and Tor-HS-inbound should all use unix-domain sockets locally, rather than TCP/localhost

The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS

The Tahoe-LAFS Weekly News is published once a week by The Tahoe-LAFS Software Foundation, President and Treasurer: Peter Secor . Scribes: Patrick "marlowe" McDonald , Zooko Wilcox-O'Hearn , Editor Emeritus: . Send your news stories to marlowe@antagonism.org - submission deadline: Monday night.