https://trending.knowyourmeme.com/editorials/guides/what-is-...
- ask you for an email
- send you an email
- ask you for a username
- except you cant actually log in with this username directly
- im being forced to learn some new social url protocol
- why does the auth flow pass me through a new ui/url that seems owned by the project but visually disconnected (eg, different branding/colors for the form)
- my password manager couldnt bridge the gap
I'm notoriously fickle about dealing with signup/login friction, but the project sounds cool so hopefully my feedback is more actionable than curmudgeony.
>Failed to complete sign up. Try again later.
I expect that's the... more optimized flow at this point in this forge's life.
> - why does the auth flow pass me through a new ui/url that seems owned by the project but visually disconnected (eg, different branding/colors for the form)
Probably because of the above, identity isn't tightly associated with the app you're using here so they've stood up their own infra for it but probably not spent too much time on making it good.
> - except you cant actually log in with this username directly
Really? That's strange... I haven't made a native account... what do you need to login with then?
The main issue is that even though I had the knot with IPv6 connectivity, it only really reliably worked once I enabled lots of IPv4 NAT'ing and also created a dummy A record for the Knot.
This is a known issue - https://tangled.org/tangled.org/core/issues/494
Doesn't really fit the 'friendly language' claim IMO
And please explain how it's not a choice when they are still on GitHub.
I remember back in early GitHub days this used to happen too, as the repository was asynchronously created but the redirect was immediate, then after a few seconds you refreshed the page and it was there. At one point they added the interstitial that I think is still there, that basically does the "waiting then redirect" for you.
Now they're trying to reinvent a worse GitHub (not off to a great start)
Abandon AT proto - dumb idea, all empty ego on the part of the creators, no utility for the masses
My experience with Bluesky Vs Mastodon really showed that the friction of federation in the latter can really kill the experience for me. I think we need something like Signal is to WhatsApp but for GitHub and my impression is that the ATProto world is the only one with the potential to deliver this.
It could be a better solution for agents that don’t bounce off such mundane complexity. It could be better for private repo federation (eg private collective or agent swarm.)
I’m interested in Tangled for the OSS/community aspect, it seems to have an advantage there with the richer identity layer for humans.
Similar groups to Bluesky (bain capital crypto) and some notable CEOs
GitHub's moat is not code hosting, they will need to build out the equivalent of Actions and figure out what private repos look like. Unclear how they intend to IAP with corporate identity systems, I have a hard time seeing ATProto break into that category.
- Charging to bypass the (admittedly very reasonable) rate limits on the main appview
- Providing paid hosting tiers for private git knots, high traffic git knots, git LOP knots, CI runners/spindles, web page hosting (via their github pages equivalent), etc
- Introducing a paid-for and permissioned nix binary cache platform since their CI spindle system is already nix-first.
- providing paid PDS hosting for corporate/business customers with SSO integration etc.
- SLAs and support contracts
There's enough options here that they have a pretty flexible path towards profitability.
Of course not, it’s the number of people who are already signed up.
Instagram’s moat also most certainly isn’t a scrollable photo timeline.
Actions, GitHub apps/external integrations, identity/permission management
The most significant, near-term, non-moaty gap is still private repos, which isn't all that big of a feature on the surface, but will have major work under the surface because of how bluesky is designing private spaces.
I also think being primarily nix/jj focussed turns a lot of people away. Those techs are not my cup of tea, so I don't see myself using tangled.
I'd be curious to hear tangled's thoughts on the path to financial sustainability. Without something that sounds plausible, I'm unwilling to migrate my code forge, for risk of going away / obsolescence.
Nix is as simple as it gets, even better than docker. Just 'nix run' whatever flake file someone gives you and everything works magically.
This codeforge going away can't happen for me because I self-host it.
Just because ATProto vibes?
- tangled federates: https://blog.tangled.org/federation
- native stacked PRs: https://blog.tangled.org/stacking
- tangled implements mitchell's vouch system: https://blog.tangled.org/vouching
People have been talking about federation across forges for a couple of years and seems like its finally at least close to being a real thing!? That's absolutely amazing!!
see knot2[0] for some initial experiments: https://tangled.org/oyster.cafe/knot2
> As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs
Codeberg's git hosting is a Forgejo instance, actually.
I was using Codeberg this morning, now I'm on Tangled. All I had to do was switch remote origin.
I'm not sure of the link on the post though... I didn't see anything at all that jumped out as pertinent to this "Tangled" thing. I get that many posts on HN just aren't meant for me... but this seems to take that to an extreme.
Edit: yes I see the URL is Tangled... But that is a very subtle cue that I didn't notice until the third time I clicked through to see if the landing page really said nothing about Tangled.
Idk if I can give you toooo much about migration, since I haven't used any CICD kind of stuff; just having repos to push to is super simple if you use their hosted knots. Also not too complicated to host a knot yourself; I'm hosting my own knot, and I like that I own at least one of the servers that I'm pushing code to.
[0]: https://tangled.org/mitchellh.com/tack
[1]: tangled.org/evan.jarrett.net/loom
https://blog.tangled.org/spindle-microvm/
Curiously the link to the spec is broken: https://tangled.sh/@tangled.sh/core/blob/master/docs/spindle...