6 months of Tangled
59 points by icy
59 points by icy
Curious what Tangled’s deal is wrt governance. Migrated to Codeberg this year and fell in love with getting a democratic say in the platform’s evolution. Tangled seems to have a couple of cool concepts on a pure tech level but what’s the strategy for the human stuff?
This addressed a big question I had about governance with respect to "requiring" a blue sky account. Thanks for adding your own PDS.
I apologize if this should be obvious to me, but is it possible to use Tangled without the social aspect? That is, I like the look of it so far as a forge, but I have no interest in being on a social-media-style timeline every time I work with a repository. Is it possible to use Tangled in that way, or is the social aspect entirely baked into the site?
I once talked to one of the guys involved about being able to host private repositories for e.g. business purposes on there. They weren't completely dismissive, but I never got around to following up with them. That said, I would pay for a replacement to GitHub that allows me to use jujutsu and a stacking workflow with single commits as the unit of review in private a private organization.
Huh, they use a thing I wrote (Nixery) for CI. Might serve as motivation to check this out 🤔
The ToS grants some rather expansive IP rights to Tangled, no?:
By uploading content, you grant us a non-exclusive, worldwide, royalty-free license to use, reproduce, modify, and distribute your content as necessary to provide the Service.
GitHub, by contrast, qualifies what is considered necessary:
This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program.
Not a lawyer, not legal advice, haven't read the surrounding context, but apart from "This license does not grant GitHub the right to sell Your Content" the GitHub qualification you quote seems seems roughly equivalent to "as necessary to provide the service"?
The last part of the ToS limits the scope: "as necessary to provide the Service". So they can't distribte or sell the content unless that is a required part of the service. If public hosting is a required part of the service, then worldwide distribution is a required part of it.
Huh… interesting. I somehow assumed they run their own network to not carry all that social cruft around and make running app views / relays less of an economical problem.
I guess my question is: can you prune/filter an app views to just generate indexes for specific data types / apps?
Yes, you can. You can use Jetstream to filter any relay down to specific record types and/or specific owning users.