Hi! Tangled co-founder here. We're super stoked with this launch -- we've stabilized our AT Protocol lexicons, completely overhauled our architecture and UI, and made self-hosting the entire stack (or parts of it!) incredibly easy. We've also shipped support for organizations, and have private repos rolling out in the following couple weeks.

Happy to answer any questions at all.

▲

kstrauser 6 hours ago | parent | next [-]

I’m excited about this direction. I’ve moved most of my own projects onto my own Forgejo, but miss it being easy for remote strangers to open PRs and such without registering in my system, which I have zero desire to allow.

So what’s the state of Tangled today? Say I have a Tangled server (instance? host?) up and running with my repos. Some stranger wants to contribute. What do they have to do before they can open issues or send PRs or whatever?

	▲	icy 6 hours ago \| parent \| next [-]
		That's exactly the problem we want to solve. Of course, they still need identity of some kind -- in this case, they'll need an AT Protocol account -- either by self-hosting a Personal Data Server[0], or signing up with a provider such as Tangled or Bluesky/Blacksky, etc. This is the last ever account they'll need (and it's theirs, and portable!). They can then begin contributing; they'll use this same account for all of Tangled and other AT Protocol services. Your Tangled git server that you'd want to run is a 'knot'[1]. It's not exactly analogous to Forgejo because it's headless, but that makes it super light on resources to run. [0]: https://atproto.com/guides/the-at-stack#pds [1]: https://tangled.org/docs/knots/self-hosting/
	▲	nerdypepper 6 hours ago \| parent \| prev [-]
		all they would need is an atproto account. you can get one of these on Tangled itself, or bring your own. they can then open issues on your repository. soon, repos will be able to declare a contribution policy: presently its open to all (anybody can open an issue), but owners can choose to limit this to just contributors for example.

▲

vaylian 4 hours ago | parent | prev | next [-]

What are your thoughts on https://forgefed.org/?

▲

rapnie 3 hours ago | parent | prev | next [-]

Tangled looks great, and I may consider self-hosting a knot. But what I am curious about, and what I weigh in such decision, is what your business model is. Right now it isn't clear from the website, so I hope you are perhaps willing to share a bit on that here.

▲

HumanOstrich 6 hours ago | parent | prev | next [-]

I wanted to try this but when I signed up for a BlueSky account it was immediately banned by some automation. I appealed but never heard back.

	▲	nerdypepper 6 hours ago \| parent [-]
		don't need to signup for bsky to try out Tangled however, you can directly just signup for an account with Tangled.

▲

0x457 6 hours ago | parent | prev | next [-]

Are there plans to add http(s) support to knot? I was planning on hosting my own knot at home, but didn't want to expose my home IP (I use cloudflared for other services that need to be exposed)

	▲	nerdypepper 5 hours ago \| parent [-]
		already exists :) its undocumented at the moment but you push over https as well. somebody has set up a git credential helper here: https://tangled.org/pds.dad/tangled-core/blob/feature%2Fgit-...

▲

jauntywundrkind 4 hours ago | parent | prev | next [-]

One of my biggest questions about the forged about is what kind of CI (and somewhat CD) do they offer?

What can I expect as a developer using Tangled to build (and deploy) my app? What is the native platform? What are typical other CI systems that have been adapted to work on Tangled (Dagger, Drone, whatnot, especially if there are repos to demonstrate the adaption)? What can I expect as enterprise or lone developer using Tangled or self-hosting or federation?

The system is called Spindle, but what about it? What does it take inspiration from, what are things like it that would help us spool up on this?

	▲	hauleth 4 hours ago \| parent [-]
		Tangled has its own CI named Spindle. However it is not limited to that as there is for example https://tangled.org/mitchellh.com/tack which allows connecting different CIs to Tangled.

▲

embedding-shape 5 hours ago | parent | prev [-]

> made self-hosting the entire stack (or parts of it!) incredibly easy

Back when you first launched, I thought running a knot was already pretty easy :) Could you expand on how it's different now, and what part(s) aren't now easy to self-host, if there is any?

	▲	nerdypepper 5 hours ago \| parent [-]
		self-hosting the appview was a bit trickier back then, but we have worked towards making that trivial. it now runs entirely in-memory, and is completely stateless (rebuilds the state of the network from scratch each time). https://tangled.org/docs/self-hosting/indexer/ we have also stabilized lexicons, so if you are a selfhoster, you can expect to not require a breaking upgrade!