Hacker Newsnew | past | comments | ask | show | jobs | submit | nerdypepper's commentslogin

relatedly, i have been using literate haskell to document my advent of code journey this year:

- day 5's solution for example: https://aoc.oppi.li/2.3-day-5.html#day-5

- literate haskell source: https://tangled.org/oppi.li/aoc/blob/main/src/2025/05.lhs

the book/site is "weaved" with pandoc, the code is "tangled" with a custom markdown "unlit" program that is passed to GHC.


how is atuin doing what deltaDB does?


ah not much at all, did too much selective reading on my end. Should have read the entire blog and not the quoted selection.


no AP is not the right protocol for shared/collaborative systems, the creators of forgefed have the same thoughts: https://forgefed.org/blog/actor-programming/.


It doesn't feel to me as if the author of that really get AP.

AP fundamentally rests on exchanging activities, that model operations on objects in collections.

Everything under their "basic concepts" section can map cleanly to an application that speaks AP.

AP has actors. Methods maps to Activities. Making networking transparent is down to wrapping things in a local framework that chooses when to use networking. Their concept of "vats" similarly is down to a lcal framework that calls method if local and posts AP activities otherwise.

AP provides a format for storing both the activities and other objects to disk, but you can choose to use your own, and that includes state that might reference other actors.

I'm working on an app server, in fact (not open source) that is based around those concepts and provides all of the things they're describing, but currently with AP as the main external protocol (that is likely to change - e.g. we're likely to use NATS for communication internally in clusters of these app servers).


https://tangled.sh?

social features via atprotocol, native jujutsu support, stacked PRs, interdiffs, light weight to selfhost, nix-based CI.


amazing


there's https://forgefed.org/ defined by the creators of forgejo. there is no complete implementation of the spec. from the last forgejo changelog, the "star" action has been completely federated. federated PRs and issues are a long way away.

https://tangled.sh is the other contender in this space that I know of. uses atproto (same as bluesky) under the hood.

fundamentally activitypub is insufficient to define these kind of networks. you'd need to have some sort of object-capability representation. the creators of forgefed are also moving in this direction: https://codeberg.org/Playwright/playwright


the only thing I really miss from GitHub is the social bits. it's super easy to stand up cgit etc. but you miss out on actual collab features, discover etc.

I've moved the bulk of my repos from GitHub to cgit first, but now to https://tangled.sh.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: