Since the outset of Matrix, our aim has always been to provide a protocol that lets you build open, decentralised, secure communication apps which outperform the mainstream centralised alternatives. It’s been a twisty journey - first focusing on making Matrix work at all (back in 2014), and then getting it out of beta with Matrix 1.0 in 2019, and now focusing on making Matrix fast, usable and mainstream-ready with Matrix 2.0.

Crossposted from [email protected]: https://lemmy.ml/post/21473941

Hello and thanks for making this community!

I would like to ask a question, I'm the creator of the Tenfingers sharing protocol, and a decentralised FOSS implementation of it.

You can basically have a decentralised web site or share data with anyone.

Would it be appropriate to post asking for help here? Testing and ideas for the future mostly I guess.

Cheers

New features coming to the future of self-hosting internet archives: a full plugin ecosystem, P2P sharing between instances, Cloudflare/CAPTCHA solving, auto-logins, and more….

This page is intended to collect information, ideas and comments related to adding BitTorrent functionality to the downloading of package files by Apt.

Brave's IPFS local node support has a cost to Brave in terms of support and maintenance, distribution of binaries, and node updates. For each Kubo node update we need to sometimes change things in code, get it QA'd and get release management to release it.

It is nice to support things, but we do need to also acknowledge that doing so takes away from other things we could be doing. P3A data is showing we have 0.1% local node and 0% gateway setting. 99.9% of people are on an Ask setting which means they’ve never used IPFS.

It also opens up a larger attack surface because there's more code and things running on a users's machine for those that opt into it. 

This issue is to track deprecating and removing the local node support.