RT @simonw: Wow, Inbox Zero for GitHub issues - I can only dream of this for any of my larger projects
My friend @aaronareed’s book on “50 Years of Text Games” is on its last day on Kickstarter. If you have some personal history with text games, are a fan of interactive fiction in the past or are still building them today, you owe yourself to order a copy! https://www.kickstarter.com/projects/aaronareed/50-years-of-text-games
RT @aaronareed: $30K to go until IF fans everywhere can brag indefinitely about that time an interactive fiction history book raised half a…
RT @Brent_Shambaugh: Yep. People like @kimdhamilton @csuwildcat @ChristopherA @JoeAndrieu … have worked in here. It is where the sausage…
Replying to @noUpside
In addition to the DID/VC work others have mentioned, you might want to look at the W3C Amira Engagement Model, which is based on a user story I wrote about how can we protect an engineer working on advocacy software from threats to her career or family. https://w3c-ccg.github.io/amira/
Replying to @noUpside and @noUpside
I’ve you’d like to talk about pseudonymity and efforts at Blockchain Commons and @RWOTEvents to support it, DM me or send me your contact info. https://github.com/BlockchainCommons/Pseudonymity-Guide
Replying to @kate_sills
It is a relatively mature tech, but is a double-edged sword. Microsoft. Google and others have been using image identification perceptual tech like this for child porn: https://en.wikipedia.org/wiki/PhotoDNA
Replying to @kate_sills
Apple proposed a version where this scanning was done on your phone, which became quite controversial: https://eclecticlight.co/2021/08/09/how-apple-intends-checking-images-for-csam/
Replying to @kate_sills
Replying to @kate_sills
So although you could use this same tech for provenance of art, then someone will propose having your phone censor or DRM, and someone else will trick giving your phone an innocent looking image that fails the algorithm and causes ISP to drop you.
The newest quarterly report for @BlockchainComns was just released. If it is TL;DR, here is my summary 🧵: [1/9] https://twitter.com/BlockchainComns/status/1547710602071511042
For #SmartCustody, we completed our draft of our multisig scenario. One of our final additions was a set of illustrations, because leveraging Bitcoin’s multisig is still harder than it should be! [5/9] https://github.com/BlockchainCommons/SmartCustody/blob/master/Docs/Scenario-Multisig.md
We also continue to evolve our wallet interoperability reference apps, which provide examples of our specifications and the Gordian Principles. Our biggest release this quarter was for Gordian Seed Tool 1.5. [4/9] https://github.com/BlockchainCommons/GordianSeedTool-iOS/releases/tag/releases%2Funiversal%2F1.5
The Silicon Salon showed the strength of the Commons. We’ve now got enough diverse experience that we can share our knowledge and our requirements and really innovate for the future! More to come in Q3 on this topic. [3/9] https://github.com/BlockchainCommons/Airgapped-Wallet-Community/discussions/90
Our most notable event was the #SiliconSalon, where we brought together several different Blockchain Commons members to talk about the future of silicon design for cryptography. [2/9] https://www.siliconsalon.info/
Take a look at our full quarterly report for all the specifics, and also for info on our big three future projects for this summer & fall: CSR (Collaborative Seed Recovery), a unified hardware API, and more wallet interoperability reference upgrades. [8/9] https://www.blockchaincommons.com/quarterlies/Q2-2022/
The eResidency testimony was supported by our new coterie of summer interns, which now include pre-law students, in addition to engineers who are also working on projects such as BIP-322, Spotbit, and updating Learning Bitcoin for taproot. [7/9] https://docs.google.com/presentation/d/1rNs2yO2b4n4m0dFIzGUOcW1k7utMlsG6/edit#slide=id.p1
We also did extensive work with the Wyoming legislature on e-residency, private key protection, and a new idea called WRDAS, which are registered digital assets. [6/9] https://docs.google.com/presentation/d/1HeeriDG834w-BaczqbioKYioaMQhD5F4m2goYhS5ih0/edit#slide=id.p
If these various projects are important to you, please become a Blockchain Commons monthly sponsor to continue our advocacy & interoperability efforts! Thank you! [9/9] https://github.com/sponsors/BlockchainCommons
RT @evacide: Breaking up is hard to do. Digitally disentangling yourself from your former partner is harder. Avast and Refuge have written…
We don’t do this out of the goodness of our hearts, but because offering these papers well in advance makes for a better, more impactful event. They offer a “sense of the community” such that is worth it for us to give that large a discount as an incentive to share early.
For our @RWOTEvents we give a large discount for submitting an “Advance Reading” paper before our collaborative event. Combined with the “Early Bird” ticket (ending tomorrow June 19th) this can be a discount as much as 45-70%! Why do we do this?🧵
An Advance Reading does not need to be a large multi-page document with academic rigor, but can just be a 2-3 page survey with good open questions in an emerging topic area of your interest. https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/advance-reading-primer.md
The first of these are arriving now, on topics ranging from the large scope like multi-dimensional reputation systems to the small scope, like how to render a Verifiable Claim for the deaf or blind. See https://github.com/WebOfTrustInfo/rwot11-the-hague/tree/master/advance-readings
They also allow people to share their own unique perspectives, interests and motivations for participation, and to join efforts. RWOT is all about integrating these into shared, collaborative artifacts — 50+ papers to date! Advance Readings are an important part of this process.
I will also be holding open office hours about these Advance Readings this Thursday, July 21st & again on August 18th from 9-10am PDT. Participation is open to all who are considering attending. https://us02web.zoom.us/j/83914783118?pwd=aGFuREY1VDFPWmcreldIc0RsYUdzZz09
For the greatest discount and the biggest impact of your ideas on the community, sign up now for our September 26-30th collaborative workshop at https://rwot11.eventbrite.com.
Just outline a problem related to decentralized identity or trust; offer a specific critique of an existing system; survey a specific topic to advance our understanding; or detail a specific solution; or share an open question about decentralized identity and web of trust.
I wrote a bit today at @BlockchainComns on the long path that DID has followed over the last 7 years. [2/9] https://www.blockchaincommons.com/specifications/DIDs-Ratified/
Congratulation to @W3C, the Decentralized Identifier Working Group, the Credentials Community Group @w3c_ccg, and the larger Decentralized Identity ecosystem for ratification of the DID 1.0 spec as a W3C Recommendation — an international standard! [1/9] https://www.w3.org/2022/07/pressrelease-did-rec.html.en
Early on, with support from a US Department of Homeland Security grant run by @aniltj, The Respect Network (later acquired by Evernym) brought DID Requirements to RWOT2 scheduled with ID2020 at the United Nations. [5/9] https://github.com/WebOfTrustInfo/rwot2-id2020/blob/master/final-documents/requirements-for-dids.pdf
DIDs really took off with Rebooting Web of Trust @RWOTEvents. The idea of decentralized identifiers was in the air, as shown by the massive DPKI paper at #RWOT1 in San Francisco. [4/9] https://github.com/WebOfTrustInfo/rwot1-sf/blob/master/final-documents/dpki.pdf
My own work began in late 2014-2015 with some exploration of how to use the Bitcoin blockchain to decentralize the revocation of X.509 certs. [3/9] https://github.com/ChristopherA/revocable-self-signed-tls-certificates-hack
These successful collaborative efforts toward DIDs at RWOT were an inspiration for the creation of @BlockchainComns, and DIDs continue to be a touchstone in our architecture. [8/9]
Congrats to DID Working Group chairs @DanielCBurnett & @brent_zundel, and to the DID editors @manusporny , @rhiaro, @peacekeeper & @drummondreed, for shepherding us the final release as W3C Recommended standard! [7/9] https://www.w3.org/TR/did-core/
With the help of @drummondreed @manusporny, @JoeAndrieu @csuwildcat @kimdhamilton & many, MANY others, we were able to incubate DIDs at @RWOTEvents, onward to the W3C Credentials Community Group (CCG), and then for approval as a chartered official W3C Working Group in 2019! [6/9]
You can help us celebrate the ratification of DID 1.0 this September in the Hague at #RWOT11! [9/9] https://rebootthehague.com/
RT @kimdhamilton: Reflecting on the first time I learned about DIDs 5 years ago, at @RWOTEvents 4 in Paris. It was my first time meeting th…
RT @kimdhamilton: And what if the issuer goes out of business? It was at @RWOTEvents that I met a community of folks who had been obsessing…
RT @kimdhamilton: And we did that soon after https://w3c-ccg.github.io/didm-btcr/. Even if it’s not your go-to DID method, its properties and simplicity…
Crypto-envelopes containing SSKR shares allow for the encryption of encapsulated data such that it can be reconstructed by combining multiple envelopes, saved in multiple places, or by multiple services or people. This is the essence of CSR (Collaborative Seed Recovery). [3/8]
Crypto-envelope itself is fairly simple: a well-specified way to encapsulate content. But it’s part of a larger architecture, as the final video on using crypto-envelopes with SSKR (Sharded Secret Key Reconstruction) reveals. [2/8] https://youtu.be/ERRhMDSEFm8
We (@BlockchainComns) recently published a playlist of three videos to kickoff off our new CSR (Collaborative Seed Recovery) effort for digital asset & identity wallets, and in particular, we have details about our new crypto-envelope specification. [1/8] https://www.youtube.com/playlist?list=PLCkrqxOY1Fbp-P1Yv-7gmu75i2QS2Z6vk
We have multiple companies already involved, all collaborating to ensure interoperability between very different wallets. We’re still in the design phase, so if you’re interested in this project, please drop me a line or comment via GitHub: https://github.com/BlockchainCommons/Community/issues/149 [6/8]
CSR is one way to ensure the resilience of your crypto-seed (or other vital digital data), but not the only one. We also are working on multisig scenarios and distributed key generation tech. But CSR allows us to offer resilience for your digital assets and identity today [5/8].
CSR is not just for social key recovery. It is part of a new architecture from @BlockchainComns that empowers a web of share servers, any one of which can be used to hold your sharded secrets. That means you can use it for self-sovereign custody of keys. [4/8]
Support our continued efforts for wallet interoperability, reference apps & specifications, all with independence, privacy, resilience, privacy & openness, by becoming a monthly sponsor via Github! [8/8] https://github.com/sponsors/BlockchainCommons
This project is only possible because of the support of @BlockchainComns sustaining sponsors: Bitmark, Blockchain Bird, Chia, Crossbar, Foundation Devices, Proxy & Unchained Capital, and these Github sponsors: https://www.blockchaincommons.com/sponsors [7/8]