Currently Origin repositories are private to members of a Cursor team. Over time we plan to expand access, but wanted to start with a limited beta of the underlying git tech.
ultimately, folks need to stop writing massive YAML files to define their builds. CI should schedule jobs, your build system should define them. my workflow files look like this:
steps:
name: Do the thing
run: nix build .#
at any point, if my CI is down or i need to switch or i need to run builds locally, i can do so trivially.
It's worked great for hosting my smaller personal projects so far, and I've already received a few helpful pull requests from the community.
Tangled.org really been working to ensure all their features work from data hosted on your personal data server (it's based on ATproto) which means should their performance, reliability, or monetization ever get you down it's easy to switch to a competitor since you're not locked in.
this is simply false: bluesky moderating your account will have no effect on what happens with it on tangled. on the off-chance that your account is hosted by bluesky's PDS AND your account gets deleted for violating their terms, yes, you will lose complete access to that account. you can avoid this by either following their TOS or hosting your own PDS or joining the tangled PDS instead.
you can selfhost all components of tangled, takes about 200mb of memory and zero disk at the moment (api.tangled.org is completely stateless!): https://blog.tangled.org/bobbin/
> 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