Interesting, why there is still no chat-on-blockchain thing. Sounds like an obvious idea for an ICO.
I hate this mindset
21–30 of 90 posts
Interesting, why there is still no chat-on-blockchain thing. Sounds like an obvious idea for an ICO.
I hate this mindset
Interesting, why there is still no chat-on-blockchain thing. Sounds like an obvious idea for an ICO.
Earlier quoted context omitted.
I don't know man, when we say "defenseless", we mean it has no defense. "Useless", it has no use. We don't mean "it has so many uses that you can't really pick one". That would be "useful", I guess, which is pretty much the opposite.
serverful, then?
Couldn't they serve [js-ipfs](https://github.com/ipfs/js-ipfs)?
AFAIK that would make every user of the web app run an IPFS node.
Earlier quoted context omitted.
It's still a stupid name.
It's used now as official term on AWS and probably other clouds as well. Its the new hot thing since you don't need to provision any servers or infrastructure. All you do is write code and deploy it to a cloud platform. And it's much much cheaper as well. So yeah it's a dumb term but it's here to stay. :)
Interesting, why there is still no chat-on-blockchain thing. Sounds like an obvious idea for an ICO.
> That means the "servers" hosting it are distributed across a wide network. This is a strange way of saying "you're looking at this site through one centralised server hosted at ipfs.io". Don't get me wrong, IPFS is great. I have released an application that works over IPFS. But I don't think obscuring the difference between a gateway and a node is beneficial. I think the difference needs to be highlighted front and…
No, your rephrasing is completely orthogonal to what they're saying. Both are true. Seems like dishonest nitpicking to me to say that they obscure the difference between a gateway and a node.