Repository Behavior-hash by pardy.at on Tangled.
Robustness of Practical Perceptual Hashing Algorithms to...
Perceptual hashing algorithms (PHAs) are widely used for identifying illegal online content and are thus integral to various sensitive applications. However, due to their hasty deployment in...
graydon (@graydon@types.pl)
@mhoye@mastodon.social To be more constructive here, I'll tell you a funnier story: a million years ago I worked on this git-predecessor called monotone (this is where the uniform merklized history idea emerged) and we *agonized* over the hashes-as-versions UI question. We were convinced it'd be the dealbreaker for almost everyone. Almost all the feedback we got was on that "nice ideas, but nobody is ever going to specify a version via a hash". We came up with all these different ways you could avoid it, all these UI affordances to use tags and local linear histories or abbreviations or whatever. And ultimately none of it mattered. The features (no central clocks, no locking or blocked commits, trivial branching, trivial full-repo replication, offline work) meant people just said "oh, well, fine" and used hashes. Basically all subsequent systems (mercurial, git, fossil) were built the same way. It became so normal that people even made systems with non-hash UUIDs present UI that _looks_ like hashes (eg. docker) just to meet the newly-reoriented UI expectation that "a version of a thing is a ~40 char string of hex noise". (IMO this is also why all the web3 stuff as well as secure p2p messaging like SSB and nostr had their moments when they did: elliptic curve crypto finally meant a public signing key could be "a ~32 char string of hex noise", which is actually a psychologically tolerable threshold in UI we hadn't previously identified, but is real. Dropping below the "full page of hex" RSA/DSA key-size mattered.)
/fujo-snippets/ao3-loader at main · fujocoded.bsky.social/fujo-snippets
A repository on Tangled
Lessons From The History Of Attacks On Secure Hash Functions
This document is a work-in-progress. Please contact the author if you see errors or omissions. Most of the secure hash functions ever designed have turned out to be vulnerable to collision attacks.
proposal: ingest repo records #282
`sh.tangled.repo` records are one of the last few records that need atprotation (2-way sync between appview/pds). this one is tricky because we want consistency between knot state, appview state and PDS state. the path forward is described below: - migration to did/rkey syntax universally: in several places, we utilize `did/repo-name` as a globally unique identifier for a repository, we should migrate this to `did/rkey`: * for the tangled appview: this means reworking our ACLs, routers and DB to use `did/rkey` or ATURI as a globally unique identifier for a repo * for knots: this means changing paths on disk to be `did/rkey`, allowing git ops to `host:did/rkey` , updating ACLs, and XRPC endpoints * for spindles: this means updating ACLs and XRPC endpoints - once this is done, we can define ingestion logic for all services in the network to pull sh.tangled.repo records * for the tangled appview, this should create/delete/update a repo pointer record * for knots: this should create-or-ignore/delete-or-ignore/update-or-ignore a repo on disk. migration of repos needs to be thought out here. * for spindles: as above - define edge-case behaviors: * when referring to repos by rkey, it is possible for clever users to create duplicate records with the same repo-name, appview routers must handle this ambiguity with a new interstitial page that offers a redirect, knots must return an error upon push/pull on ambiguous git URLs * the `knot` cli can introduce a command `backfill` or `sync` to bring knot state up to sync with the rest of the world (repos, collaborators, pubkeys, ACLs etc.).
good-first-issue bot (@hacktober.tngl.sh)
Announcing good-first-issue tags added on @tangled.sh issues this October! Find them all at https://tangled.org/goodfirstissues source: https://tangled.org/@bad-example.com/hacktober-bot by @bad-example.com (not affiliated with tangled)
Bobbin
Bobbin is an API appview for Tangled records. It serves XRPC endpoints for sh.tangled.*, with it you can get repos, issues, pulls, comments, follows, stars, labels, pipelines, and profiles. It is read-only, there is no auth, since that should all be handled direct-to-PDS and knot respectively.
Hash Functions for GPU Rendering – Nathan Reed’s coding blog
Pixels and polygons and shaders, oh my!
Spaces explainers
Search terms: AT Protocol Spaces, ATProto Spaces, permissioned data, buckets
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
The Atproto Spaces Alpha is Live - AT Protocol
Reintroducing Spaces - Daniel's Leaflets
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
