flexibility when relinking renamed tiddlers
TiddlyWiki Drag and Drop, Jeremy Ruston
Relicensing with AI-assisted rewrite
Exploring the chardet v7.0.0 controversy: Can an AI rewrite legally 'launder' a library from LGPL to MIT?
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.).
An Ode to Links
A URL is a technical thing: a hostname, a path, a port, an origin, some query parameters, etc. But a link is a cultural thing: an invitation, a citation, a…
Connected Places - Links Collections
rel-me
Using rel=me on a hyperlink indicates that its destination represents the same person or entity as the current page, which is a key building-block of web-sign-in, IndieAuth, and ✅ distributed identity verification.
ewancroft.uk/linkat-directory
[READ-ONLY] Mirror of https://github.com/ewanc26/linkat-directory. a Linkat frontend
going with single ‘.’ for link-in-rkey, like sh.tangled.graph.vouch:. thanks @thoth.ptnote.dev for the suggestion! indexing in constellation is working, will try to roll out to prod tomorrow with all the backlogged tangled vouches!
fig (aka:[phil])
Constellation "link sources" are currently(ish): `<NSID>:<RecordPath>` like "app.bsky.feed.like:subject" soooo `<NSID>^rkey` like "sh.tangled.graph.vouch^rkey"? or just "sh.tangled.graph.vouch^"?
i made linkring.lol. it's a place to put your links in lists, because they sure weren't going to organize themselves in my 47 open tabs. on the atmosphere, with stickers.
If somebody else would like to easily and quickly save all Tangled Stars to Semble, using the *permalink* (so the link won't break if the account changes handle or if the repo name changes) I gotchu airglow.run/u/vicwalker.dev.br/3ml5ixicbo… You can easily change the collection or get rid of the last step
Starred Tangled Repo to Semble Collection | @vicwalker.dev.br | Airglow
airglow.runworking on this today 😎. we chose veryyyyy different formats for storing information semble & margin make sense the direction they've chosen. you can organize links into multiple buckets, where on linkring there is a single link<>list relationship. should show up at the very least soon tho!
