Aaron D Goldman
@aarondgoldman.bsky.social
Computer Philosopher, Distributed Systems builder
I had intended it to map to int64 format
i = timestamp * 1024 + ClockID.
1970 + 2^53 microsecond = 2255
1970 - 2^53 microsecond = 1685
I think 1685 CE - 2255 CE is a pretty good range for computer events 🤷♂️
i = timestamp * 1024 + ClockID.
1970 + 2^53 microsecond = 2255
1970 - 2^53 microsecond = 1685
I think 1685 CE - 2255 CE is a pretty good range for computer events 🤷♂️
August 21, 2024 at 9:22 PM
I had intended it to map to int64 format
i = timestamp * 1024 + ClockID.
1970 + 2^53 microsecond = 2255
1970 - 2^53 microsecond = 1685
I think 1685 CE - 2255 CE is a pretty good range for computer events 🤷♂️
i = timestamp * 1024 + ClockID.
1970 + 2^53 microsecond = 2255
1970 - 2^53 microsecond = 1685
I think 1685 CE - 2255 CE is a pretty good range for computer events 🤷♂️
Have you asked on
discord.com/invite/4T2ep...
discord.com/invite/4T2ep...
January 5, 2024 at 7:24 AM
Have you asked on
discord.com/invite/4T2ep...
discord.com/invite/4T2ep...
hur.st/bloomfilter/... sounds right.
January 2, 2024 at 4:31 AM
hur.st/bloomfilter/... sounds right.
We have lots of wheels invented for lots of use cases. Some Authenticated Data eXchange protocol will win.
December 1, 2023 at 8:20 PM
We have lots of wheels invented for lots of use cases. Some Authenticated Data eXchange protocol will win.
There's only one writer now. If writes move to the user agent it could pull down just the path to their new record.
Create the path back to create a new signed root.
The b#tree gives efficient client side signing without losing non-existence proofs. No keys on the server is a real use case.
Create the path back to create a new signed root.
The b#tree gives efficient client side signing without losing non-existence proofs. No keys on the server is a real use case.
June 22, 2023 at 6:01 PM
There's only one writer now. If writes move to the user agent it could pull down just the path to their new record.
Create the path back to create a new signed root.
The b#tree gives efficient client side signing without losing non-existence proofs. No keys on the server is a real use case.
Create the path back to create a new signed root.
The b#tree gives efficient client side signing without losing non-existence proofs. No keys on the server is a real use case.
Not responsible for every action of an AI, but if you know it causes harm and don't move to mitigate then yes.
June 17, 2023 at 6:13 PM
Not responsible for every action of an AI, but if you know it causes harm and don't move to mitigate then yes.
So that repo can have control transferred.
Start with the PDS managing the keys and finally irrevocably transfer control to the user.
There are use cases where one repo controller may want to transfer a repo to a different controler with finality.
Start with the PDS managing the keys and finally irrevocably transfer control to the user.
There are use cases where one repo controller may want to transfer a repo to a different controler with finality.
June 12, 2023 at 11:35 PM
So that repo can have control transferred.
Start with the PDS managing the keys and finally irrevocably transfer control to the user.
There are use cases where one repo controller may want to transfer a repo to a different controler with finality.
Start with the PDS managing the keys and finally irrevocably transfer control to the user.
There are use cases where one repo controller may want to transfer a repo to a different controler with finality.
did:plc needed to make a choice between consistent or available. By having a consensus group DIDs don't fork. If we just had delta gossip then a controller could fork their DID to two different states.
June 9, 2023 at 9:45 PM
did:plc needed to make a choice between consistent or available. By having a consensus group DIDs don't fork. If we just had delta gossip then a controller could fork their DID to two different states.
https://youtu.be/BCksQYqU5ok
https://youtu.be/BsV-4aj7PTo
https://youtu.be/O3QENUHs7yY
Not your keys, not your repo ... mostly just that you need control of the top rotation key.
That said, I would like to control the repo keys so that the PDS literally couldn't sign a commit without my user agent.
https://youtu.be/BsV-4aj7PTo
https://youtu.be/O3QENUHs7yY
Not your keys, not your repo ... mostly just that you need control of the top rotation key.
That said, I would like to control the repo keys so that the PDS literally couldn't sign a commit without my user agent.
Building decentralized systems using DHTs - Part 1
Decentralized systems based on distributed hash tables (DHTs) have received a lot of attention during the past decade, and systems based on this technology a...
youtu.be
June 8, 2023 at 10:06 PM
https://youtu.be/BCksQYqU5ok
https://youtu.be/BsV-4aj7PTo
https://youtu.be/O3QENUHs7yY
Not your keys, not your repo ... mostly just that you need control of the top rotation key.
That said, I would like to control the repo keys so that the PDS literally couldn't sign a commit without my user agent.
https://youtu.be/BsV-4aj7PTo
https://youtu.be/O3QENUHs7yY
Not your keys, not your repo ... mostly just that you need control of the top rotation key.
That said, I would like to control the repo keys so that the PDS literally couldn't sign a commit without my user agent.
June 7, 2023 at 4:44 AM
I would also like to know what this DID's use case is
https://plc.directory/did:plc:m2o63tpnlwrfj43nrqzxyrry
https://plc.directory/did:plc:m2o63tpnlwrfj43nrqzxyrry
June 3, 2023 at 5:56 PM
I would also like to know what this DID's use case is
https://plc.directory/did:plc:m2o63tpnlwrfj43nrqzxyrry
https://plc.directory/did:plc:m2o63tpnlwrfj43nrqzxyrry
still time to nullify the delta if you don't want to mutate the immutable log
```
"cid": "bafyreidaxmtdx6pb3up6tznwdbdse53uytfl7laql4cdlig22zhktkhfjy",
"createdAt": "2023-06-01T04:27:23.090Z",
"did": "did:plc:z72i7hdynmk6r22z27h6tvur",
"nullified": false,
```
```
"cid": "bafyreidaxmtdx6pb3up6tznwdbdse53uytfl7laql4cdlig22zhktkhfjy",
"createdAt": "2023-06-01T04:27:23.090Z",
"did": "did:plc:z72i7hdynmk6r22z27h6tvur",
"nullified": false,
```
June 3, 2023 at 5:50 PM
still time to nullify the delta if you don't want to mutate the immutable log
```
"cid": "bafyreidaxmtdx6pb3up6tznwdbdse53uytfl7laql4cdlig22zhktkhfjy",
"createdAt": "2023-06-01T04:27:23.090Z",
"did": "did:plc:z72i7hdynmk6r22z27h6tvur",
"nullified": false,
```
```
"cid": "bafyreidaxmtdx6pb3up6tznwdbdse53uytfl7laql4cdlig22zhktkhfjy",
"createdAt": "2023-06-01T04:27:23.090Z",
"did": "did:plc:z72i7hdynmk6r22z27h6tvur",
"nullified": false,
```
Seems more like a bug in the PDS then the DID Directory. Being willing to sign an update where the DID String does not match the DID String for the account. Also the poor practice of reusing key material.
As long as the rotation key holder signs things they shouldn't the directory can't help you.
As long as the rotation key holder signs things they shouldn't the directory can't help you.
June 3, 2023 at 5:24 PM
Seems more like a bug in the PDS then the DID Directory. Being willing to sign an update where the DID String does not match the DID String for the account. Also the poor practice of reusing key material.
As long as the rotation key holder signs things they shouldn't the directory can't help you.
As long as the rotation key holder signs things they shouldn't the directory can't help you.
The Repo is a tree. If a PDS wanted to do a narrow checkout that only pulled some paths it could. e.g. Pull posts leave the long videos. Once you pull the root CID of the repo you can sync the rest at your leisure.
May 10, 2023 at 4:48 PM
The Repo is a tree. If a PDS wanted to do a narrow checkout that only pulled some paths it could. e.g. Pull posts leave the long videos. Once you pull the root CID of the repo you can sync the rest at your leisure.
Feels like the lexicons should be more related to the records. I like it though.
May 2, 2023 at 2:42 AM
Feels like the lexicons should be more related to the records. I like it though.
ipfs://bafybeiddeohylecumwkpbhnyejtkt3rhnnpcbgqwjmlyqejuqok74ghrtq
April 24, 2023 at 10:20 PM
ipfs://bafybeiddeohylecumwkpbhnyejtkt3rhnnpcbgqwjmlyqejuqok74ghrtq