Earlier quoted context omitted.
Having wifi on all day is one thing, actually using it is totally different. Just activate your wifi hotspot on your phone and start using it from your computer. See how fast the battery depletes. No matter what incentive scheme you device , it's not going to help you with your battery.
Seeding when phone is actually in use would be net positive. And everyone is on their phones all the time nowadays anyway.
IPFS is the Distributed Web
251–260 of 286 posts
Re: IPFS is the Distributed Web
#252Earlier quoted context omitted.
IPFS needs to protect its users, if it is to have any users. The creators of IPFS may not have any liability, but they open up its users to severe issues of liability due to the way it operates. IPFS will become toxic real quick, if it becomes know that IPFS can make you an unintentional distributor of kiddy porn and pirated content. The core problem is that IPFS' default mode of operation is actively user hostile. T…
> IPFS will become toxic real quick, if it becomes know that IPFS can make you an unintentional distributor of kiddy porn and pirated content. Yea, this is where you're mistaken. It cannot make you distribute anything! You only distribute what you download. Don't download kiddy porn, and you won't distribute kiddy porn. > All it takes for you to commit a crime and/or copyright infringement, not only as a consumer but…
Oh, really?
"In some cases, nodes must work for their blocks. In the case that a node has nothing that its peers want (or nothing at all), it seeks the pieces its peers want, with lower priority than what the node wants itself. This incentivizes nodes to cache and disseminate rare pieces, even if they are not interested in them directly."
https://github.com/ipfs/papers/blob/master/ipfs-cap2pfs/ipfs...
What's to say BitSwap won't proactively decide to download and start seeding some rare pieces of kiddy porn?
> You only distribute what you download.
As if that wasn't bad enough.
> Don't download kiddy porn, and you won't distribute kiddy porn.
How are you to know if a hash contains kiddy porn or not?
You need to know if the hash contains kiddy porn before you download it, but to know if it contains kiddy porn you have to download it. Classic Catch-22.
The only rational response to a system like this is not to use it.
> How does BitTorrent protect me from unknowingly downloading kiddy porn?
By not randomly downloading stuff from the Internet. By only downloading torrents, I have explicitly chosen to retrieve (hopefully from vetted and reputable sources). By giving me complete control and feedback on what I'm seeding.
Obviously not ideal, but far better than what IPFS does.
I also don't get how this central censorship authority is going to work. I very much doubt IPFS wants to become the Internet Police for Saudi Arabia.
The whole thing is a futile attempt to appease lawmakers and dictators, since any filtering will be done clientside. Nothing is stopping the client from ignoring any blacklists.
Any great or small firewall will just find it easier to block the whole thing than do some silly whack-a-mole deep packet inspection.
How is IPFS not going to become a haven for kiddy porn aficionados?
If the censorship authority publishes a list of blacklisted hashes, that's the same as publishing a directory of all the available kiddy porn. Oops!
If the censorship authority requires each hash to be queried individually, it becomes a real honeypot for the state surveillance machinery.
Not exactly great choices.
Re: IPFS is the Distributed Web
#253Earlier quoted context omitted.
The difference is IPFS (or similar) would distribute content . Currently communication is distributed, but content is not. IPFS is like https, but where every page is a bittorrent. There are challenges for security in distributing services and monetization. However, the key is that content would be distributed. YouTube probably would not switch to ipfs, but DNS (what was targeted recently) would make sense. A DNS hos…
The internet may run on content (storage) and communication, but both those things run on computation . Until computation can be safely distributed real changes can't happen
Or why the current model (SaaS with Javascript apps literally shipped to every browser) isn't distributed computation.
(The long digression on takedowns doesn't illuminate this at all either.)
Re: IPFS is the Distributed Web
#254Earlier quoted context omitted.
The difference is IPFS (or similar) would distribute content . Currently communication is distributed, but content is not. IPFS is like https, but where every page is a bittorrent. There are challenges for security in distributing services and monetization. However, the key is that content would be distributed. YouTube probably would not switch to ipfs, but DNS (what was targeted recently) would make sense. A DNS hos…
With the web going more mobile with less storage space. Why would anyone would want to be a node in such a network where you have to cache content for others.
Non-mobile devices start at $5. A considerable server is <$100. Even only modest amounts of server persistence allow for a powerful distributed net.
Re: IPFS is the Distributed Web
#255Earlier quoted context omitted.
I am a novice, but I'll do my best to answer. IPFS isn't a replacement for the existing web like many of its predecessors, for the purposes of your question, it really works more like a drop-in shared caching system. The site host doesn't have to participate in IPFS for this to work. As an example: You host a blog. As an IPFS user, I surf to the blog and store your content in my cache. When another IPFS user attempts…
How would you prevent fraud? Say I have a site that sells Awesome Products. L337Hacker mirrors my site, does a DDOS on the original and lets IPFS take over, redirecting the shopping cart to his own site. Is this a potential scenario? If so, is there any way to prevent it?
First: publishing the catalog isn't the same as processing the shopping request. Online commerce is largely an update to catalog + mail-order shopping as it existed from ~1880 - 1990. If someone else wants to print and deliver your (PKI-authenticated, tamper-resistant) catalog, that's fine.
Second: The catalog isn't the transaction interface, it's the communications about product availability. The present e-commerce world is hugely hamstrung on numerous points, but one of these is the idea separating the catalog and product presentation itself from ordering. So long as you're controlling the order-request interface, you're good. A payment processing system which authorised payments via the bank rather than from the vendor would be helpful. Also a move away from account-info sharing.
The key is in knowing who the valid merchant is, and in establishing that the fraudulent merchant has misrepresented themselves as the valid merchant. Perhaps authentication within the payment system would help.
Taking the shopping cart's payment mechanism out of the shopping cart would help.
Re: IPFS is the Distributed Web
#256Earlier quoted context omitted.
> I worry that this is another example of throwing technology at a social and political problem. [...] I would rather we do the hard work of fixing the web we've got There are multiple flaws in your reasoning: for one, the web was also a technical solution to a social problem; also, IPFS is someone's hard work aimed at fixing the web we've got.
The web was a technical solution to an information management problem at a physics lab.
Re: IPFS is the Distributed Web
#257I worry that this is another example of throwing technology at a social and political problem. That the current web is centralized has little to do with its technical design, and everything to do with economic and structural incentives that have made it that way. It's tempting to say "start afresh", but we'll just be trading our current problems for a new set of problems IPFS introduces. It's a law of nature that pro…
> I worry that this is another example of throwing technology at a social and political problem. And here i was just listening to Adam Curtis talk about his latest creation, Hypernormalisation, where he touched on the issue of thinking one can solve social issues with engineering.
Re: IPFS is the Distributed Web
#258I worry that this is another example of throwing technology at a social and political problem. That the current web is centralized has little to do with its technical design, and everything to do with economic and structural incentives that have made it that way. It's tempting to say "start afresh", but we'll just be trading our current problems for a new set of problems IPFS introduces. It's a law of nature that pro…
The key is economic. The cloud and SaaS have taken over largely because the cloud is DRM and because centralization creates opportunities for ad and ad-driven surveillance business models. There is merit in doing the technical work to make a decentralized paradigm easier, but the lack of an economic model is the tougher of the two problems.
One is discoverability. It's tough to find a bunch of scattered systems all over the place. That's a problem Facebook, Reddit, and HN address.
Another is identity. Tracking who's doing what (and what their permissions/authorities are) over a bunch of sites is ... a pain. I'm still mulling over a comment a few days back on HN that a user had 770 different password-based identities in their accounts-management storage (personal).
Search (related to the first) is a third -- spiders suck a lot of bandwidth. Unless there's some way to distribute search or allow nodes to self-report search elements (which will probably require some form of auditing).
And there's administration. It's really easy create systems any idiot can use, but then, any idiot will, and DDoS Brian Krebs and Dyn. Bulletproof administration is a real pain point.
Re: IPFS is the Distributed Web
#259Earlier quoted context omitted.
> IPFS will become toxic real quick, if it becomes know that IPFS can make you an unintentional distributor of kiddy porn and pirated content. Yea, this is where you're mistaken. It cannot make you distribute anything! You only distribute what you download. Don't download kiddy porn, and you won't distribute kiddy porn. > All it takes for you to commit a crime and/or copyright infringement, not only as a consumer but…
> Yea, this is where you're mistaken. It cannot make you distribute anything! Oh, really? "In some cases, nodes must work for their blocks. In the case that a node has nothing that its peers want (or nothing at all), it seeks the pieces its peers want, with lower priority than what the node wants itself. This incentivizes nodes to cache and disseminate rare pieces, even if they are not interested in them directly." h…
Nice catch, that is interesting. Granted, i feel like this could be tweaked as it is simply a mechanic to attempt to reduce leeching on the network.
> You need to know if the hash contains kiddy porn before you download it, but to know if it contains kiddy porn you have to download it. Classic Catch-22.
How do you know if that link to a pdf from a friend contains kiddy porn? You need to download it to check the md5 / contents.
I'm really lost on how this is any different than HTTP/BitTorrent/etc. Any link on the web can be kiddy. Any bittorrent link can be kiddy. Any IPFS link can be kiddy. They're all equally dangerous on that front as i see it.
The only argument i feel like can be made on this front, is that the hash can make for a hard to visually decipher file. Ie, `foo.com/bar.pdf` is inherently more "trust worthy" than `/ipfs/d3b07384d113edec49eaa6238ad5ff00`. With that said though, that's a better reason to not use `/ipfs/d3b07384d113edec49eaa6238ad5ff00` than it is to use `/ipns/foo.com/bar.pdf` (fake domain/example for easy discussion).
Again, stay away from random hashes just like you stay away from sketchy torrents and random http files.
Re: IPFS is the Distributed Web
#260Earlier quoted context omitted.
What do you suggest?
There's the million-dollar question. I've been bashing my head against it for a few years now. I think an important thing is to give everyone a say in how these large computer networks affect their lives. How to do that in the context of a broken political system isn't clear to me at all.
I'm slowly realising a fundamental truth of economics: whatever it is you're making cheaper, you're going to have one hell of a lot more of.
And as you increase the quantity, you'll start bumping into limiting factors elsewhere. E.g., cheaper transport => far more congestion. Cheaper communications => more advertising. Cheaper storage => vastly more surveillance and monitoring. Cheaper telecoms => vastly more phone solicitations and scams.
There's the question of what people really need to access -- and here I think it's key to go back to Maslow's Hierarchy. And to acknowledge our human limitations of information capacity per day. Several sources I've seen (Stephen Wolfram, Walt Mossberg) suggest about 150 - 300 email messages/day, and something less than even a cursory glance at 800 comments (The New York Times's comments moderation team). How do you provide a manageable and significant set of information to people?
I've also started noting that our-so-called discussion systems themselves (Slashdot, Facebook, Reddit, even HN) are pretty poor at self-supporting useful user feedback. Almost as if that's not their true function.