Tangled
@tangled.org
https://tangled.org is a decentralized Git hosting and collaboration platform.
Discord: chat.tangled.org
IRC: #tangled @ libera.chat
Built by @oppi.li & @anirudh.fi
Discord: chat.tangled.org
IRC: #tangled @ libera.chat
Built by @oppi.li & @anirudh.fi
we support `@` free versions too! this is how we do imports in our own source code.
for what its worth, we are going to be removing `@` in URLs very soon!
tangled.org/@tangled.org...
for what its worth, we are going to be removing `@` in URLs very soon!
tangled.org/@tangled.org...
October 29, 2025 at 2:23 PM
we support `@` free versions too! this is how we do imports in our own source code.
for what its worth, we are going to be removing `@` in URLs very soon!
tangled.org/@tangled.org...
for what its worth, we are going to be removing `@` in URLs very soon!
tangled.org/@tangled.org...
this release was made possible by:
- @thecoded.prof
- @5jiji.com
- @camsmith.dev
- @boltless.me
- @hjvt.dev
- @kilroy.bluecanary.dev
- @willdot.net
remember to update your knots to the latest revision, happy tangling!
5/5
- @thecoded.prof
- @5jiji.com
- @camsmith.dev
- @boltless.me
- @hjvt.dev
- @kilroy.bluecanary.dev
- @willdot.net
remember to update your knots to the latest revision, happy tangling!
5/5
October 19, 2025 at 1:11 PM
this release was made possible by:
- @thecoded.prof
- @5jiji.com
- @camsmith.dev
- @boltless.me
- @hjvt.dev
- @kilroy.bluecanary.dev
- @willdot.net
remember to update your knots to the latest revision, happy tangling!
5/5
- @thecoded.prof
- @5jiji.com
- @camsmith.dev
- @boltless.me
- @hjvt.dev
- @kilroy.bluecanary.dev
- @willdot.net
remember to update your knots to the latest revision, happy tangling!
5/5
another quality of life improvement by @thecoded.prof:
1️⃣ push a branch
2️⃣ click on the link returned by the knotserver
3️⃣ open a pull request!
4/5
1️⃣ push a branch
2️⃣ click on the link returned by the knotserver
3️⃣ open a pull request!
4/5
October 19, 2025 at 1:11 PM
another quality of life improvement by @thecoded.prof:
1️⃣ push a branch
2️⃣ click on the link returned by the knotserver
3️⃣ open a pull request!
4/5
1️⃣ push a branch
2️⃣ click on the link returned by the knotserver
3️⃣ open a pull request!
4/5
we've got a few quality of life improvements for #jj-vcs users:
knotservers now write change-ids into commit objects upon pull-request merge!
this means jj is able to delete unreachable change-ids if the branch is deleted on the remote:
3/5
knotservers now write change-ids into commit objects upon pull-request merge!
this means jj is able to delete unreachable change-ids if the branch is deleted on the remote:
3/5
![λ jj git fetch
bookmark: main@origin [updated] tracked
bookmark: push-ymrwkmsxtuoy@origin [deleted] untracked
Abandoned 2 commits that are no longer reachable.
Working copy (@) now at: w 7 (empty) (no description set)
Parent commit (@-) : t 9 w
Added 0 files, modified 2 files, removed 0 files](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:wshs7t2adsemcrrd4snkeqli/bafkreiafpvrwmov4yqftcdscyqlt6ufxpzabhlnnscpqk2xn25u2dwgosm@jpeg)
October 19, 2025 at 1:11 PM
we've got a few quality of life improvements for #jj-vcs users:
knotservers now write change-ids into commit objects upon pull-request merge!
this means jj is able to delete unreachable change-ids if the branch is deleted on the remote:
3/5
knotservers now write change-ids into commit objects upon pull-request merge!
this means jj is able to delete unreachable change-ids if the branch is deleted on the remote:
3/5
we've added support for ⚠️ callouts ⚠️ in markdown!
we presently support GFM syntax, supported types are "note", "tip", "important", "warning" and "caution".
2/5
we presently support GFM syntax, supported types are "note", "tip", "important", "warning" and "caution".
2/5
October 19, 2025 at 1:11 PM
we've added support for ⚠️ callouts ⚠️ in markdown!
we presently support GFM syntax, supported types are "note", "tip", "important", "warning" and "caution".
2/5
we presently support GFM syntax, supported types are "note", "tip", "important", "warning" and "caution".
2/5
you can’t because we don’t have tokens
October 15, 2025 at 4:48 PM
you can’t because we don’t have tokens
roadmap item. not anytime soon tho :)
October 15, 2025 at 6:11 AM
roadmap item. not anytime soon tho :)
we’ve got a robots.txt now. gotta figure out how to SEO maxx this
October 13, 2025 at 8:18 PM
we’ve got a robots.txt now. gotta figure out how to SEO maxx this
migration between knots is planned!
this is very possible in theory.
this is very possible in theory.
October 13, 2025 at 10:07 AM
migration between knots is planned!
this is very possible in theory.
this is very possible in theory.
we saw a lot of traffic over the weekend, and caused k1 to go down intermittently, this should be fixed for good now!
October 13, 2025 at 10:05 AM
we saw a lot of traffic over the weekend, and caused k1 to go down intermittently, this should be fixed for good now!
hey! there's a known issue with PRs: since we store the pull request patch as a string in the AT record, oftentimes the record size exceeds 2MiB and fails to create—resulting in the above error. work is underway to switch it to use blobs instead.
October 13, 2025 at 6:47 AM
hey! there's a known issue with PRs: since we store the pull request patch as a string in the AT record, oftentimes the record size exceeds 2MiB and fails to create—resulting in the above error. work is underway to switch it to use blobs instead.
hey! do you wanna hop in the discord? prob easier :)
October 12, 2025 at 2:05 PM
hey! do you wanna hop in the discord? prob easier :)
there was a teeeny tiny one! knot1 is under a lot of load haha
October 11, 2025 at 12:10 PM
there was a teeeny tiny one! knot1 is under a lot of load haha
this happened when we migrated to the new indigo oauth sdk 😪 timing couldn't have been better—just as we hit the HN frontpage!
October 11, 2025 at 9:20 AM
this happened when we migrated to the new indigo oauth sdk 😪 timing couldn't have been better—just as we hit the HN frontpage!
hey! we have a somewhat aggressive cache which might be causing this. also, bsky had some relay issues which might’ve caused your knot membership to not propagate correctly. i’ve added you now!
and sorry about the delay! missed this notification (way too many)
and sorry about the delay! missed this notification (way too many)
October 11, 2025 at 4:56 AM
hey! we have a somewhat aggressive cache which might be causing this. also, bsky had some relay issues which might’ve caused your knot membership to not propagate correctly. i’ve added you now!
and sorry about the delay! missed this notification (way too many)
and sorry about the delay! missed this notification (way too many)