Usage ideas #205
Usage ideas #205
Conversation
Next step: Organize into a table (most items should be in several categories)
Still needs to become a table
|
This is a great first start @bertrandfalguiere! I've got a couple of pointers that might help your writing:
I'm looking forward to seeing this page complete! |
|
Thanks! |
|
Ok. I took a lighter tone than the rest of the docs, because it's not instructions or real explanations about IPFS internals. I chose not to put illustrations because it is already very long. I would love some feedback at this point @johnnymatthews @jessicaschilling |
|
Great, thanks for this @bertrandfalguiere! I'll review this in the next few days. |
|
Nice work @bertrandfalguiere! You've put a lot of research into these projects, and there's a lot to look at here. I'd like to re-organize the page before merging into |
|
Sure! Let me know if there's anything I can do in the meantime. |
|
|
||
| Textile.io is building the [Powergate](https://blog.textile.io/filecoin-developer-tools-concepts/) tool for your app to interact with Filecoin once the main net is launched. | ||
|
|
||
| ### Reconcile IoT and privacy |
There was a problem hiding this comment.
IOTA is not about privacy. They want to entice devices into sharing data via micro-transactions, on the contrary.
There was a problem hiding this comment.
Could you expand on this section a bit further then? Looks like I've missed the point.
There was a problem hiding this comment.
I think there is confusion because there are 2 different companies: Iotex who wants to sell hardware and provide a platform for clients to keep their data safe. IOTA is a distributed ledger, but technically it's not a blockchain, but something else that they call the Tangle.
I'll clarify.
|
|
||
| The [Iotex](https://www.iotex.io/) blockchain wants to build an ecosystem where Internet-of-Things (IoT) data is owned by the owners of those devices. Data from hardware devices such as cameras can be stored on local hardware, backed up to cloud, or to IPFS. Future integration with Filecoin will further reinforce the ownership of data by the users. | ||
|
|
||
| Tangle is a distributed ledger of the [IOTA](https://www.iota.org/) network, and it supports hosting IoT data on IPFS. You can find out more [on GitHub](https://github.com/iotaledger/poc-ipfs). |
There was a problem hiding this comment.
IOTA uses "the Tangle", not "Tangle". The Tangle is another form of distributed ledger, just like a blockchain. So I think the Tangle should be used like the (Bitcoin) blockchain.
There was a problem hiding this comment.
I see, again looks like I've misunderstood. Can you please expand on The Tangle and what it's for.
|
|
||
| ### Efficient network factories | ||
|
|
||
| [Actyx](https://www.actyx.com/) is helping the manufacturers to fast forward to what they're calling _Industry 4.0_: the industry of connected machines. Actyx built a custom operating system on top of IPFS to ensures all machines and monitors receive the orders, information, and parameters they need to function properly. |
There was a problem hiding this comment.
Industry 4.0 concept is not Actyx's invention, it's a known concept in the manufacturing game. Maybe linking to Wikipedia? https://en.wikipedia.org/wiki/Industry_4.0
There was a problem hiding this comment.
The term Industry 4.0 isn't particularly common place. Maybe you could expand upon what Industry 4.0 is before this paragraph.
| ### Co-host large datasets | ||
|
|
||
| [Qri](https://qri.io/) is an open-source tool for the management of large datasets. Qri users enjoy reduced hosting costs, traceability of changes in the data, rollback to previous versions, and easier collaboration when updating data. De-duplication across datasets also helps to keep physical storage usage as small as possible, along with reducing sync times. | ||
|
|
There was a problem hiding this comment.
I'm surprised about the removing of "#### Heavily parallelize Big Data processing"(https://www.cse.unsw.edu.au/~hpaik/thesis/showcases/16s2/scott_brisbane.pdf). I find it a very attractive use-case. But it's your call in the end of course.
There was a problem hiding this comment.
It looked to me like a duplication of a previous heading. If you think it's an important and separate point, then give it another go.
|
|
||
| ### Deploy your GitHub website on IPFS | ||
|
|
||
| [Fleek.co](https://fleek.co/) allows you to effortlessly build sites & apps on IPFS. The workflow is similar to that of Netlify: developers can link their GitHub project to Fleek and have it automatically built and deployed on IPFS whenever a change is made to a specific branch. Fleek also comes with ENS and domain name integration. |
There was a problem hiding this comment.
People from Fleek says they will support deploying several more methods of deploying website (https://discuss.ipfs.io/t/publish-website-on-ipfs/7957/5) apart from Github, and I believe them (they are moving fast). I don't know if it's worth mentioning or not.
There was a problem hiding this comment.
In that case it's probably worth mentioning what Fleek are intending to support in the future.
|
Looks good on my end @bertrandfalguiere! Thanks for your hard work here. I'll merge this in shortly. To get started on your bounty payment, please email me at johnny@protocol.ai. |
Here is a pull request for the ideas of usage in the docs.
Fixes ipfs-inactive/docs#387
It is still heavy WIP, but I gathered all the resources I need. Now it's just a work of writing, formating and cleaning.
I will work more all day tomorrow.