I'd like to ask some of the less-technical folks that follow me to read this and tell me if it makes sense to you?
https://github.com/fedi-e2ee/public-key-directory-specification
(I'm trying to make it less intimidating to newcomers)
I'd like to ask some of the less-technical folks that follow me to read this and tell me if it makes sense to you?
https://github.com/fedi-e2ee/public-key-directory-specification
(I'm trying to make it less intimidating to newcomers)
What does "less-technical" mean here?
If you recognize the term "kASLR" or "Frobenius trace" or can type a valid flag for the tar command from memory, you're probably technical.
@soatok does does tar -?
or tar --version count?
@soatok The link to The Verge is paywalled
@CraigStuntz God fucking dammit
@foxyloon Thanks, I appreciate you taking the time to look at it and answer honestly <3
@soatok I have some technical knowledge/experience, insofar as being a junior sysadmin for a few years. The minutia of encryption stuff is definitely not one of my strengths, let alone being able to write a shell script without lots of research first.
In short, I can comprehend high level technical concepts but lack the skills to utilize or implement them in any meaningful way.
Your write-up seems to do a good job of explaining the high level concepts and goals of the project, which is a great starting point to do further research. Also, I very much appreciate the embedded links that provide added context to certain talking points.
@andreu If you can remember any valid tar flags for any reason that counts
@soatok I can only remember tar -xzf because of the "xtract ze files" mnemonic, does that count?
@soatok I only skimmed through it, but this looks pretty good.
The section "How Does This Help Non-Technical Users?" does not actually answer the heading question, though.
There's also a minor language issue in "We want to build a system, which [...]". No need for comma and using "that" is preferred.
@herzenschein How's this? https://github.com/fedi-e2ee/public-key-directory-specification/pull/109
@soatok I thought you were only technical if you had a mounted machine gun installed in the back of a pickup truck
@soatok I can reply later on Github
@soatok I wouldn't mind a little elaboration on why/how key transparency helps the trust issue. All the pieces are there but it's left a bit implicit to connect the dots. Maybe it's best to leave that in the subsequent docs but it felt missing to me in this overview
@ferrix Do the blog posts linked at the bottom cover it adequately?
@ferrix Also, https://github.com/fedi-e2ee/public-key-directory-specification/blob/752477be93b3889709170999b0f478fc3ccc0557/README.md#how-does-key-transparency-help-the-trust-issue
@soatok came for this xkcd lol
@davepolaschek Yes, it does! :3
@soatok It makes sense, but where it says, “it only gets more technical from here on,” it wasn’t kidding.
So I’m interested, but already have so many projects, I can’t spend the time to dig into any of the other docs. But I’m still interested. So I think you’ve succeeded in your goal of making it readable. And I like the sound of the general idea.
Does that help?
OK I pushed a bunch of changes:
https://github.com/fedi-e2ee/public-key-directory-specification
If you want to compare with what was there before, https://github.com/fedi-e2ee/public-key-directory-specification/tree/c639fe7625133701def55763e4c3ed9712c5cd07 is the main branch before everyone's feedback was collected
@peritia There's actually very little for them to implement.
The PKD server is a separate piece of software.
Most of the other code lives client-side.
The only pieces the server needs to support are IETF RFC 9421 and FEP-521a (for Ed25519 support, since almost everyone uses RSA for the publicKey attribute on each actor).
If they want to support BurnDown (for privileged admins to issue to help people who lose their keys regain access), that will be a bit more work, but not much.
Starred
I hope glitch soc will implement this
(i dont think mastodon will implement that soon)
@FurryBeta Blockchains are built atop Merkle trees.
@soatok Am I correct in thinking that a Merkle tree is some what analogous to a block chain? I don’t know a lot about cryptography, but from what I picked up about crypto currency over the years is the block chain is what keeps everyone honest, by providing a method where everyone who was so inclined, could audit the chain and verify the transactions. Sounds similar but using the public keys rather than an crypto coin amount
@herzenschein Yeah I had a bunch of other changes I wanted to merge in. (I'm also moving very fast.)
@soatok Replied there, though it was merged already.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.