@aarondgoldman.bsky.social
Computer Philosopher, Distributed Systems builder
An image saying 614, and .1%
I feel like this undervalues the work I did before the company was founded.
17.09.2024 15:52 β π 1 π 0 π¬ 0 π 0I 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 π€·ββοΈ
xkcd.com/2867/
25.01.2024 05:02 β π 2 π 0 π¬ 0 π 0Have you asked on
discord.com/invite/4T2ep...
hur.st/bloomfilter/... sounds right.
02.01.2024 04:31 β π 2 π 0 π¬ 0 π 0We have lots of wheels invented for lots of use cases. Some Authenticated Data eXchange protocol will win.
01.12.2023 20:20 β π 1 π 0 π¬ 0 π 0hi
28.07.2023 21:40 β π 0 π 0 π¬ 0 π 0https://www.nist.gov/pml/time-and-frequency-division/time-realization/leap-seconds
27.07.2023 21:48 β π 0 π 0 π¬ 0 π 0One of the upsides of Twitter rebranding to X is that maybe someday Iβll again be able to tell people that I worked at Twitter instead of clarifying that I worked at βpre-Elon Twitter.β
24.07.2023 15:37 β π 67 π 3 π¬ 3 π 0There'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.
Not responsible for every action of an AI, but if you know it causes harm and don't move to mitigate then yes.
17.06.2023 18:13 β π 0 π 0 π¬ 1 π 0So 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.
A triangle showing the trilemma between mutable identifiers. A name can only be two of exclusive, chosen, locally generatable.
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.
09.06.2023 21:45 β π 3 π 0 π¬ 0 π 0https://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.
Image showing the list of PDSs by number of DIDs and the total length of all deltas.
It is just a little spammy.
bsky.social, 139,117 DIDs, 96.7 MB
uwu, 11,170 DIDs, 82.6 MB
I would also like to know what this DID's use case is
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,
```
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.
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.
10.05.2023 16:48 β π 2 π 0 π¬ 0 π 0Feels like the lexicons should be more related to the records. I like it though.
02.05.2023 02:42 β π 1 π 0 π¬ 0 π 0Yup
28.04.2023 02:41 β π 2 π 0 π¬ 0 π 0ipfs://bafybeiddeohylecumwkpbhnyejtkt3rhnnpcbgqwjmlyqejuqok74ghrtq
24.04.2023 22:20 β π 1 π 0 π¬ 0 π 0think of it as an opportunity for those domain names that clutter up the everything drawer
24.04.2023 21:19 β π 1 π 0 π¬ 0 π 0just setting up my bsky
28.02.2023 17:04 β π 15 π 2 π¬ 0 π 0