Reposted by jess
pluribus is really good but it’s gonna be god-mode good when carol and pirate lady finally bang okay now i’m going to bed gnight
November 18, 2025 at 7:35 AM
pluribus is really good but it’s gonna be god-mode good when carol and pirate lady finally bang okay now i’m going to bed gnight
i love my Pentaxes but i picked up an OM-1 one time in a used camera shop and it was a perfect little gem. the platonic ideal, sitting directly above the MX, of what a 35mm SLR should be.
November 22, 2025 at 5:38 PM
i love my Pentaxes but i picked up an OM-1 one time in a used camera shop and it was a perfect little gem. the platonic ideal, sitting directly above the MX, of what a 35mm SLR should be.
anyway this is a very security-adjacent question that i have spent a lot of time on; disambiguating identifiers and not-identifiers from different sources is the heart of my work.
November 17, 2025 at 1:29 AM
anyway this is a very security-adjacent question that i have spent a lot of time on; disambiguating identifiers and not-identifiers from different sources is the heart of my work.
yeah—calling the client thing an "idempotency key", treating it as an opaque string, and saying "you can give us whatever you want for this but you have to make sure it's unique among all such keys or we'll reject" is valid. refusing it expose it in your own API protects against misinterpretation.
November 17, 2025 at 1:25 AM
yeah—calling the client thing an "idempotency key", treating it as an opaque string, and saying "you can give us whatever you want for this but you have to make sure it's unique among all such keys or we'll reject" is valid. refusing it expose it in your own API protects against misinterpretation.
For a fully noncentralized system, you have to let go of the ability to prevent collisions from happening; you have to create a structure whereby consumers of the data can perceive and ignore semantically-invalid collisions. That's what the UUID5 does—define the permitted semantics of the ID
collisions.is
November 17, 2025 at 1:21 AM
For a fully noncentralized system, you have to let go of the ability to prevent collisions from happening; you have to create a structure whereby consumers of the data can perceive and ignore semantically-invalid collisions. That's what the UUID5 does—define the permitted semantics of the ID
If partial centralization is OK, I'd have a dual-PK on the record pairing a received client ID (the first time it's received) with a self-generated ID, rejecting repeated requests that aren't canonically-identical replays.
November 17, 2025 at 1:18 AM
If partial centralization is OK, I'd have a dual-PK on the record pairing a received client ID (the first time it's received) with a self-generated ID, rejecting repeated requests that aren't canonically-identical replays.
Is non-centralization a core goal? If so, I'd suggest some sort of content-based ID like a UUIDv5 paired with a shared canonicalization scheme to feed the hash. That would provide idempotency over repeated submissions.
November 17, 2025 at 1:16 AM
Is non-centralization a core goal? If so, I'd suggest some sort of content-based ID like a UUIDv5 paired with a shared canonicalization scheme to feed the hash. That would provide idempotency over repeated submissions.