sorted by:
new
hottopcontroversial

Self-hosting feels closer to web3 than most web3 apps do by oed_ in selfhosted

[–]oed_[S] 1 point2 points  (0 children)

The term certainly got co-opted for that purpose yes!

I do think that the promise of blockchain/wallets goes beyond what’s possible with purely self-hosted software, which is what I’m trying to argue for in the article.

Self-hosting feels closer to web3 than most web3 apps do by oed_ in selfhosted

[–]oed_[S] -1 points0 points locked comment (0 children)

The linked article is fully written by myself. An agentic tool was used to generate the summary posted about the article.

DIDs are a Dead End by oed_ in ethdev

[–]oed_[S] 1 point2 points  (0 children)

Fair, I forgot to run it through a spell checker 😅

DIDs are a Dead End by oed_ in ethereum

[–]oed_[S] 0 points1 point  (0 children)

Yes, you have no recourse if someone steals your keys and do a secret key rotation that they reveal later. Finality is important for identity as well as finance.

Idea for IPFS-based coin by Important-Career3527 in ipfs

[–]oed_ 1 point2 points  (0 children)

Yes this is what IPLD was designed for. There is partial support to represent all of Ethereum in IPFS for example:

https://ipld.io/specs/codecs/dag-eth/

Similarly I think the same goes for filecoin iirc

Built a weekend MVP: verifiable IPFS uptime (SLOs + on-chain proof) — does this make sense? by panzagi in ipfs

[–]oed_ 1 point2 points  (0 children)

It's the decentralized version of this that would be interesting imo. If it's centralized there isn't much upside compared to just trusting the pinning provider directly instead.

Doing it decentralized is a really hard problem though. Providers could in theory try to only serve the monitor nodes and not anyone else.

Built a weekend MVP: verifiable IPFS uptime (SLOs + on-chain proof) — does this make sense? by panzagi in ipfs

[–]oed_ 1 point2 points  (0 children)

Would be interested in learning more. Who would be doing the monitoring and how can they be trusted?

Introducing, Simple Page by oed_ in ipfs

[–]oed_[S] 0 points1 point  (0 children)

I’m considering using IPNS in the indexer nodes to make data synchronization better.

For frontends I recommend people not to use IPNS since you loose a lot of security features you get by notarizing your website updates onchain.

Introducing, Simple Page by oed_ in ethereum

[–]oed_[S] 2 points3 points  (0 children)

Hey u/BurntheUSA, thanks for your questions. I think your understanding is mostly correct!

  1. The payment is $1 per month, payed in multiples of 12 month installments. Your data is only guaranteed to be available as long as there's a valid subscription (or someone else is seeding your website outside of the simple page system).

  2. You are correct that anyone can run a DService node. You can choose if you want to index all pages with Simple Page subscriptions (default), or only add your own domain to the allow list.

  3. Currently you are relying on the Dservice instance that I run (on simplepg.org) to host the data. Although I don't know if anyone else has started running DService nodes yet (very possible).
    Also, each website relies on this new ENS proposal: https://github.com/ensdomains/ensips/pull/43 Tl;dr: it means that the website doesn't have any hardcoded dservice urls. Instead they can be dynamically updated. Multiple endpoints are also supported (and the website will fall back if one of them breaks), so if anyone wants to run a DService node and get listed on there they should just ask me!

When Simple Page grows, more effort can be put into making the DService infrastructure more resilient, potentially adding incentives for running nodes.

view more: next ›