Hacker News new | ask | show | jobs
by dingo_bat 3188 days ago
> Why do I have to fetch jQuery from fricking California when it's sitting on my girlfriend's phone in the other room?

Because your girlfriend probably values her battery life and data usage? I doubt we'll ever see phones hosting any ipfs content for the reasons.

3 comments

Funny you should say that. Just hours ago I released an app that helps you pin your most important IPFS hashes to your phone[0]. Works well together with IPFSDroid[1].

Battery usage is definitely noticable, but my phone has a good battery life overall, and IPFS on the phone is a priority for me.

Data usage would be a problem, but I use it only when connected to a portable WIFI hotspot I am carrying with me.

[0]: https://play.google.com/store/apps/details?id=com.hobofan.ip...

[1]: https://play.google.com/store/apps/details?id=org.ligi.ipfsd...

In a post-carrier world, she would be paid with tokens that she could use to buy faster network access later in the day or sell any surplus to heavy network users (probably indirectly through a brokerage, perhaps even run by a company that used to be a carrier). The tokens might even buy electricity from the neighbor's solar panel to charge the phone.
If data isn't embarrassingly cheap before mid-century we did something terribly wrong. Ditto electricity / battery life by the end of century.

(and again: content-addressing could drastically reduce data usage anyway.)

If I understand correctly, the argument isn't against content addressing but against sharing the content with anyone. While you have an incentive to store it locally and reach for that first, you (currently) have a negative incentive (=cost of data/electricity) to share it with someone.