this post was submitted on 02 Sep 2024
3 points (100.0% liked)

Decentralization

146 readers
1 users here now

All things and everything about decentralization: news, announcements, proposals, and discussions about decentralized apps, protocols and communities.

Rules

  1. Be polite and follow the rules of our instance lemmy.world.
  2. "Follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others."
  3. With respect to peer-to-peer and file-sharing technologies, refrain from posting illegal content (piracy) or links to it.
  4. With respect to cryptocurrencies, refrain from
    1. posting initial coin offerings (ICOs) and giveaways
    2. posting referral and promo links/codes

founded 2 months ago
MODERATORS
boramalper@lemmy.world
3
Brave Deprecates IPFS Support (github.com)
submitted 2 months ago by boramalper@lemmy.world to c/decentralization@lemmy.world
1 comments fedilink hide all child comments
 

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.

top 1 comments
sorted by: hot top controversial new old
[–] slazer2au@lemmy.world 1 points 2 months ago

We do use local node support for NFT pinning. So that would be 1 feature that would need to be removed.

Say no more.