| | 20 | |
| | 21 | == April 9, 2024 |
| | 22 | |
| | 23 | attendees: meejah, hacklschorsch, ccx, chris, b3n |
| | 24 | |
| | 25 | hacklschorsch: macbook, trying to ... do haskell stuff? (GHC 8.6 works?) so trying to get Obsidian / Obelisk working on\ |
| | 26 | mac (to be able to build "the mobile GUI" |
| | 27 | |
| | 28 | (meejah provides quick overview of the Haskell Tahoe client stuff we have) |
| | 29 | |
| | 30 | chris / cypher: released Rust library for deterministic RSA keys from BIP32-like words; working towards making one's ow\ |
| | 31 | n mutable RSA key; some future pairing possibly around the Python API etc. |
| | 32 | |
| | 33 | b3n: working towards Trac removal; need the dump of database + content of folder; "just make a tarball of the trac user\ |
| | 34 | folder" (plus database dump) |
| | 35 | |
| | 36 | flo: there's "trac-export.db.bz2" served from tahoe-lafs.org/~trac (which we should _probably_ delete) |
| | 37 | |
| | 38 | b3n: there's "trac-admin auth-copy" which should work |
| | 39 | |
| | 40 | meejah: magic-wormhole release, some haskell magic-wormhole; what about hmac stuff? A not-python version? |
| | 41 | |
| | 42 | |
| | 43 | chris: yeah .. thinking of ways of facilitating different implementations; tahoe libraries? |
| | 44 | |
| | 45 | ccx: ocamljs exists |
| | 46 | |
| | 47 | flo: can we do a read-only browser client to tahoe-lafs? |
| | 48 | |
| | 49 | -> preserves and syndicate -- #preserves channel on Libera |
| | 50 | |
| | 51 | Nim, syndicate -- original impl was in. |
| | 52 | |
| | 53 | Someone is working on a DBUS-like thing on top of PostmarketOS (Alpine with "stuff for phones"). Pub/sub. |
| | 54 | |
| | 55 | ccx: when thinking of a "lightweight" phone client, something like 9p or something to "a node" (i.e. a real tahoe node) |
| | 56 | e.g. do "everything except decryption" on "the node". |
| | 57 | |
| | 58 | |
| | 59 | meejah: sounds interesting! like a "medium-level" API, something like "please assemble this ciphertext, and give it to \ |
| | 60 | me" so that the client doesn't reveal the "full capability", it stays on the phone. |
| | 61 | |
| | 62 | (some discussion of Web browsers etc) |
| | 63 | |
| | 64 | chris: browser extension, maybe? There's also "sub-source reliability" (??) |
| | 65 | |
| | 66 | ccx: can use browser for some stuff (less-sensitive data, across more people) |
| | 67 | |
| | 68 | meejah: just trying to contextualize a bunch of this stuff, and it's important to understand what is possible (and not \ |
| | 69 | possible) these days. Agoric has done some thinking around this. |
| | 70 | |
| | 71 | ccx: also sandstorm.io |
| | 72 | |
| | 73 | (meejah aside: sandstorm doesn't (didn't) have accounts, really, just email address .. wonder if they still have that?) |
| | 74 | |
| | 75 | ccx: still grieving death of CloudABI -- extension of capsicum to make a unix-link system on top of FreeBSD. |
| | 76 | |
