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.
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?
>Failed to complete sign up. Try again later.
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
https://discourse.ubuntu.com/t/gleam-and-the-value-of-small/...
Doesn't really fit the 'friendly language' claim IMO
the beauty of atproto means that you are in no way tied to the VC funded company behind the web app available at tangled.org. you merely publish your git repository using a protocol that this app will pick up and present with a nice UI
any other app that speaks atproto and looks at those same sh.tangled.* records will be able to access everything in the same way
and even the git repository itself doesn't need to be hosted by tangled the company, you can host your repository yourself. all you need is a server that can speak git, ssh, http and websocket
This is false: you’re tied to both tangled (unless you want to self host a forge, which if you did you wouldn’t have picked tabgled) and Bluesky for your login to keep working (unless you want to self host a complex constellation of social media components).
this is true today only because nobody has made an alternative "frontend". but the data is there, public, for anybody to see. they can't take it from you even if they really wanted to. in fact, tangled has been working on making it easier for such third-party "frontends" to exist: https://blog.tangled.org/bobbin/
> and Bluesky for your login to keep working
you seem to be misinformed. "your login" is handled by your PDS, whichever it is. self-hosting a PDS doesn't require you to host anything beyond a sqlite database and a websocket connection. they are easy and very cheap to host, nothing like a "complex constellation of social media components"
today you can already 100% use atproto apps without having any ties whatsoever to bluesky:
- data: non-bluesky-hosted pds (either your own or some other host) for your data
- identity: the did:plc directory is managed by an independent swiss association, but you can even use did:web if you really want to
- relays/apps: blacksky is an example of a fully independent stack
And please explain how it's not a choice when they are still on GitHub.
They mirrored their repo somewhere else. An additional location does not make it less friendly.
If anyone would like to give me a large amount of money in exchange for my publishing a mirror on your git forge, please get in touch ;)
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.
Gleam has had many dozens of front page posts here.
Tangled is a niche GitHub alternative, but has also had previous history.
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.
Yes, code is largely about communication as well - with others as well as our future selves. That doesn’t mean it’s a social media experience. There are lots of ways to communicate that aren’t that.
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.