Not receiving the signup code on email for tangled.org
Tangled, a Git collaboration platform built on atproto
61–70 of 88 posts
Re: Tangled, a Git collaboration platform built on atproto
#62This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
This!!
It is trivial to set up a VPS with a git remote. Access it with ssh. Done. Git clone fred@fooda.com:/hubs/frog gets you hopping instantly.
I think the issue behind the curtain (attempt at an obscure reference to the wizard of oz) is lock in. And why is lock in such an issue all around us? Why is github so completely focused on lock in rather than service? Behind the curtain of lockin is funding. Paying for it. A business model.
Maybe centralization => lockin => money? Like gmail. Like github. Etc.
If you have no business model for service => money (and we do not!) then this is what you get.
[Edit: "funding" => "is funding"]
Re: Tangled, a Git collaboration platform built on atproto
#63Github is no longer a trusted nor a reliable platform. Moving at least the oss stack to atproto (or any other open network) is an excellent way to safeguard it against Big Tech, Government censorship etc. Love to see this.
But nobody will pay for his own servers. Big OSS orgs might, but you cannot even provide PR's other than by email.
Re: Tangled, a Git collaboration platform built on atproto
#64This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
> I don’t see why these necessarily need to be bundled together.
They don't need to be, but it's very convenient.
Re: Tangled, a Git collaboration platform built on atproto
#65Earlier quoted context omitted.
I see you hand waved people who pay money so that forges can operate. If you have a company you don’t want to pay 20 invoices to different vendors. If you have a company you don’t want to deal with debugging integration between your CI/CD and web view and git providers, you want to make a ticket and have it fixed. When you are developing a project you don’t want to spend time figuring out which task management will i…
Inevitably someone will end up paying for Tangled. Their architecture demands an infrastructure piece that actually hosts the forges and PDSs through BlueSky won't always be free. They're also non-trivial to run.
A PDS is just a docker image of a TS node app w/ sqlite that can run on effectively no hardware at all (someone got one running on a microwave once upon a time).
A relay is also fairly trivial to set up and can be orchestrated via docker I believe. You can run them on a raspberry pi as long as you have a half decent internet connection.
The tangled appview runs on a single machine w/ like 4 cores and a few gigs of ram.
You can run a knot (git host for tangled) on pretty much any hardware.
And a spindle (CI runner for tangled) on anything that meets the requirements for your CI ops.
It's multiple moving parts which increases complexity but IIRC they also all have nix flake support as well so orchestrating all of the moving parts together via nix is increasingly trivial.
Re: Tangled, a Git collaboration platform built on atproto
#66Hey HN, co-founder of Tangled here! We recently shipped a change to switch out our OAuth library—which introduced a regression, preventing new users from being added to the default knot and spindle (the git hosting server & CI runner). We just discovered this and pushed a fix—please log out and log back in again and you should be able to create repositories! Otherwise, happy to answer any questions!
First Question: is it possible to change your handle or delete your account on the tngl.sh PDS instance?
Second Question: how much resource does creating and hosting a new AppView entail? For example let's say I make an appview that's essentially the PDS-hosted equivalent of Cloudflare Pages, where a user upload a folder of a static website and the appview just forwards it verbatim at a hypothetical https://atprotocities.org/@cool.guy/... , would you need to bear the brunt of the traffic cost as an AppView host?
Re: Tangled, a Git collaboration platform built on atproto
#67This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
While there may be no technical reasons why these functions need to be bundled together in a forge, there may still be economic reasons (can’t support development as a standalone function) and usability reasons (people want it to arrive “batteries included”). The counter might be “open source proves this can work because people ignore the economics there, too,” but remember that most open source projects die with a single maintainer and the most successful ones have some sort of corporate patrons contributing sponsorship money, engineers, etc.
Re: Tangled, a Git collaboration platform built on atproto
#68This is a really cool project and I’ve been following it for awhile. I’m also keen on breaking up the code forges monopolies. I’ve been dipping my toes into this space mainly because I think code forges as they exist are trying to solve multiple problems at the same time. I think there’s value in splitting this functionality up into discrete services. For example, most forges: host your git repo, web view, collab too…
"Git is already decentralized" Decentralized is a big word. Git never tackled the decentralized aspect, being served over a master-slave protocol like HTTP means you have a tendency to centralize it again.
Git was really useful because it allowed decentralization but didn’t require it like CVS or SVN. It catered to the “just clone the repo and create a new branch when you hop on the airline and push updates to origin when you land” model. But it’s really unusual that people really want a hugely distributed model. Typically, people want to go to The Blessed Repo and get The Blessed Code. For example, Linus’s got kernel tree is more important than everyone else’s clone.
Re: Tangled, a Git collaboration platform built on atproto
#69Github is no longer a trusted nor a reliable platform. Moving at least the oss stack to atproto (or any other open network) is an excellent way to safeguard it against Big Tech, Government censorship etc. Love to see this.
But nobody will pay for his own servers. Big OSS orgs might, but you cannot even provide PR's other than by email.
That was the right way from the start
Re: Tangled, a Git collaboration platform built on atproto
#70I'm not touching anything related to atproto with a ten foot pole