And it says that SBD is on its way to 100$(optimistic, why not?) and STEEM will soar to 50+bucks(optimistic, why not?) with some time!
Happy new year, Steem! Happy 2018!
Snoop Dogg
And it says that SBD is on its way to 100$(optimistic, why not?) and STEEM will soar to 50+bucks(optimistic, why not?) with some time!
The cake part
This edible masterpiece is made of frozen Belgian chocolate mousse (triple chocolate with a sugar paper print on top).
Another great job by my friend, which was convinced by me to move to STEEM and he has a lot to show and tell about the cake business and travelling. Plus he has a beautiful food art collection in his Instagram. Glad that he made it.
It takes no effort for me to promote Steem or Steepshot, cause they actually do this by themselves. Only a few understand a true potential value of magnificent STEEM+IPFS stack
2018 is going to be special for STEEM+IPFS stack
Thank you, Youtube, for demonetizing videos of a lot of Youtubers, they all are welcome in DTube.
Master Vitalik said that cryptocommunity is immature for its only price concerns. No one wants to solve global problems, and everybody wants easy cryptocash made in 10 hours or less. Ether was one of several revelations of recent years, before STEEM ran in sight.
I agree with this statement so much!
Do you remember how the Internet was decentralized in the early 90s? But not by its will, which was only technological and technical cause. If you wanted to run a website, you've had to buy a specific hardware (server) and upload your site on this server, which was kinda located in your house. You were the only person to control your data. It was a quasi-decentralized WEB-world of the unicorns, until the dotcom boom started. Young and bald entrepreneurs managed to realize that taking money for data hosting is great business!
In my previous post I've mentioned that IT-giants, their being so powerful, starts to be toxic.
Google knows where are you. UBER's Godmode is incredible. Youtube is trying to censor things up to the kindergarten level.
Future of the Web. Permanent Web.
For now there are so much stuff depend on the Internet, it's our basic communication channel plus a whole army of different web-apps that give such amazing capabilities - they do exist only because we've built necessary infrastructure to support them.
What we call "the Web" its just a set of protocols (CCS, JS, HTTP, TCP/IP, TLS,DNS, UDP, IP, SMTP, Browsers, search and etc.) which consist rules of how to transmit data.
A serious major upgrade was made by Tim Berners-Lee, who invented Hypertext transfer protocol or HTTP.
Basically, HTTP is a language used to communicate between web browsers and servers, a client-server.
Your PC can send a request via browser to the eBay and then eBay server will return response message (like a homepage).
It worked well enough, but for now there are some issues, as I think.
Issue#1. Bandwidth
More and more people in the world are coming online and they do it fast. More people means more data demand. Websites crashing all the time, just because they can't handle so much users, who try to access at the same time.
Example:
You've just made a very meaningful photo, and you want to share it with your coworkers. You've uploaded it on Facebook and sent a link to all. Lets assume that total bandwith required for this upload of 1mb photo is 8mb with all routing scheme (from your office to a several servers up to Facebook server). A hundred people trying to see a photo will require 100x8=800mb of bandwitdth usage.
If you made a very meaningful 300mb video and uploaded it, amount of bandwidth required is going to be around of 300mbX100X8=240gb
Just imagine that raw data came out of Google servers with Gangnam style video since it was uploaded - 500+ Petabytes. Thats a lot for a video!
This is horribly inefficient routing scheme since you've just wanted to share something with people sitting next you.
Providing so much bandwidth someday will become no longer profitable.
Issue#2. Latency
The only way to get your data faster to you is to move physically closer. That's why cloud storage services offer servers by regions.
Issue#3. Centralization.Surprise oppression.Censorship
This had happened to Egypt, when all internet providers blocked traffic to interrupt peoples communication during the riot action by the government's request.
Up to 30 services own most of the data and thay don't tell us about how this data is used. These services have unimagineable power just with manipulating large numbers of people with their access to communication. During a riot, for example
Issue#4. Resiliency
If your ISP gets offline - you're out of luck and there is nothing you can do about that.
In case of data permanence - if Wikipedia gets hacked and all the data gets lost - we'd lose that knowledge forever.
HTTP links get broken all the time. You've probably seen this kind of error before. It actually indicates, that content has been deleted or moved. And if data was not copied manually by someone - it is lost forever.
IPFS vs Issues
Interplanetary File System (IPFS) seems to be really underrated, despite it's being the "Upgrade" of the entire WEB! This is a road to a permanent web - a place where links never die, and no one has control of your data.
HTTP is IP addressed, IPFS is content addressed.
When requesting a data from a content based address - you'll receive it faster since it will rout from whoever owns a copy of this content address closest to you. It makes bandwidth usage much more efficient!
Each time you upload a file to IPFS you get back it's immutable hash. Each file in a network is identified by the content using its hash. The hash is cryptographically guarantied to identify this file.
IPFS stack constists of several ideas from computer science:
1. To store the data it uses distributed hash tables (DHT)
DHT is a interface to the data that stored on nodes which are distributed across the network. The node that gets to store a particular key is found by hashing that key. So in effect the hash table buckets are now independent nodes in a network.
2. To exchange the data between this nodes it uses BitSwap mechanism.
Inspired by the popular BitTorrent protocol,which in fact, was a protocol to transfer large data sets across the web. A user can discover nearby peers to share data with, then they can download many small bits of it from many different peers from many different peers all at once. This compensates bottleneck points which makes it more faster than downloading a large file from a single source.
3. To give a structure to DHT and users could find the data they need when they need to, IPFS used data structure called "merkledag". That a topic for additional post.
Money grow on the merkle trees
SUMMARY:
HTTP protocol is a few decades old now and it became slow, impermanent, and centralized.
IPFS is a newer protocol that aims to create a permanent web, where links are content-addressed, not IP-adressed, and it uses a distributed hash tables to store data, a MerkleDAG to give it a structure, and a BitTorrent mechanism to exchange data and maximize bandwidth.