> Lower end devices will take more time to meet our requirements since the updates and security features aren't as good. It's mostly due to how Qualcomm handles it. The latest Snapdragon flagships have the best security features. We'll also need Motorola to start paying them for longer updates below flagships

Since you are here, do you have any updates about the issue of issues and PRs living in the author's PDSs and not on the knot ? (Which also acts as the repository's PDS if I am not mistaken)

    >  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.

I am just thinking you do not like tangled because you don't use the social features of github and so don't see the point here. I can understand that, but then tangled is just not for you ?

And yeah ATProto is not the next thing, but IMO having a portable identity and services that can act as "one big single app" are requirements for a modern social protocol to do applications like Twitter,Instagram, and github's social features for example, ATProto is just the one that does it better imo for now.

But again since you are always bringing on private repos, I think tangled is just not for you since the ATProto model is for open data and so fits open source projects really nicely I think.

But after looking a bit more into it, they are still following the same model as Bluesky in that the author of an issue or comment or PR is the owner of the resource, and it lives on their PDS, but they are considering changing that (and I hope they do it soon) by having the record be created on the repo PDS (so the knot basically) and a pointer record on the user's PDS proving they are the author.

ATProto has all that's required to do so, so I hope they do it soon, they are still in alpha after all but I find the interoperability very promising because you can have independent code hosting regardless of the opinions of forge X (which I think is the main reason why people move away from GitHub), but still be a part of an interoperable ecosystem that acts just like it is a single platform.

Your GitHub Enterprise comparison is wrong, because with an onprem github entreprise you don't have the social github features (and that's the whole point of tangled, use something else if you want a private forge for your company, it's not for this purpose)

My point is, Tangled being on ATProto, you can still access all of the repos, PRs and issues of other people by looking through your self-hosted appview even if the official appview is down, because an appview, is just that, an "app *view*" It's the view layer in your traditional app, and ATProto is the database.

It's a view of the data on the ATProto network, it is not the data holder, everyone can be their own data holder that is visible through any appview.

> downtime and self-hosting is not a reason most people are convinced to move forges, it takes a lot to get someone there

Yes, I agree, but I personally think tangled is great because of the interoperability

People on codeberg, on gitlab, on github, on self-hosted gitea instances, on self hosted gitlab instances, and so on, all control their issues, PRs, and git repos (they run on their own infra) but they are also more independent, are not subject to a central platform's policies (or are subject to the one they prefer) and so on, and they also introduce contributor friction, you need separate accounts, it can be difficult to cross reference issues and PRs accross projects on different forges, users can't easily have a central feed of project they starred.

On tangled you get to have the first part (freedom) while not having the second downside (unique account, cross-references work seamlessly, etc...)

Give me reasons open source projects moved forges away from github, and I am pretty sure if tangled did exist when they did so it would fit more boxes of "why they left" than their target forge.

If you want to build an alternative Knot implementation (git Hosting) you can use anything as long as the API is compatible ?

Same for all of the parts of Tangled really

Also, even if it's down, unlike GitHub you can self host your own AppView so it's never down for you

You get:

   - Self hosting your git hosting (if you want)

   - Self hosting your issues/PRs (if you want)

   - Self hosting your CI (if you want)

   - Github-like social features (I have one account, I can follow, star, add issues and PRs to any repo on tangled)

Right now there are many providers providing different tradeoffs, for different usages.

Would "winning" mean releasing an all-purpose better model that will outperform every other companies for all kind of tasks ? Something like AGI but cost effective ?

Or is it winning the consumer-side AI race ? Like making a kind of "super personal AI assistant" the likes you would see in movies and TVs ?

I'm not arguing, I am just struggling to understand what it usually means when somebody says that, it's not like competitors will go bankrupt the second OpenAI/Anthropic/Whatever does something specific.

It's a social network with github-like social features and git hosting, but you can still self host your git and have all the features like issues, PRs and so on just like GitHub.

And it's built on ATProto so you can also have your issues PRs and so on hosted on your infra, but everything interconnects nicely with your single account, just like using GitHub.

They even added a vouching system for users, to know who to trust based on who you already trusted.

I admit they are done pretty well, it took 2-3 different calls (accross months) for me to notice I wasn't talking to a real person !

I hope it will make people who argue that "there are no instances in ATProto" is wrong, understand that it is actually true and not just a naming debate.

Comments URL: https://news.ycombinator.com/item?id=49202912

Points: 141

# Comments: 30

https://www.microsoft.com/en-us/research/blog/everparse-hard...

https://lwn.net/Articles/770750/

https://project-everest.github.io/

Is this used in the industry ? And for what kind of software ?

Having a scripting language as a tool is powerfull, and can help remove unnecessary stuff from the LLM's context.

You are saying the chicken came first and they are saying the egg came first.

So from image generators up to agents.