fazo96/ipfs-boards
1
0
Fork 0
mirror of https://github.com/fazo96/ipfs-boards synced 2025-03-12 21:48:39 +01:00
Code Issues Releases Wiki Activity

update README

Browse Source
This commit is contained in:
Enrico Fasoli 2015-12-11 16:13:56 +01:00
parent 63830bb129
commit d50c61bb79
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@ -86,11 +86,11 @@ very inefficient, slow, etc. You're welcome to help in any way though!
Also, remember that __it doesn't have__: Also, remember that __it doesn't have__:
- Ability to post and create a profile from the web app (it's read only for now) - Ability to post and create a profile from the web app (it's read only for now)
- Aggregation (only the admin can post, for now) - Aggregation (it's quite limited for now)
- Advanced customization, control, user profile customization - Advanced customization, control, user profile customization
- Media support - Media support
- Votes - Votes
- Ability to run without a full IPFS node. That would require either a backend or the (currently not done) js implementation of IPFS - Ability to run without a full IPFS node. That would require either a Backend or the (currently not done) js implementation of IPFS
Ability to publish stuff in the browser won't be implemented until go-ipfs 0.4 Ability to publish stuff in the browser won't be implemented until go-ipfs 0.4
is ready. It will maybe be ready before the new year. is ready. It will maybe be ready before the new year.
@ -112,24 +112,24 @@ See `CONTRIBUTING.md`
- __Client__ - __Client__
- a static web application to access IPFS Boards - a static web application to access IPFS Boards
- maybe a desktop version (which would be a wrapped web application) - work in progress, some features are already done, see above
- will be able to do everything in a simple browser - maybe a desktop version (which would be the wrapped web application, using Electron)
- __Server__ - will be able to do everything in any modern browser
- __Completely Optional__ (not right now, but it will be) - __Cache Server and/or Backend__
- can cache content so that it doesn't get lost - __Not started yet__: no code has been written yet!
- fully configurable - __Completely Optional__: you don't need this to be able to use the App
- can serve the Client - automagically caches content 24/7 so that it's always available
- fully configurable, for example only cache content from users you want to support.
- can serve data via HTTP API
- can render the client application so that search engines can index content - can render the client application so that search engines can index content
- can provide content over an HTTP API or web sockets so that devices can save bandwidth - can provide content over an HTTP API or web sockets so that devices can save bandwidth
- __[go-ipfs](https://github.com/ipfs/go-ipfs)__
- needed to use the app until [js-ipfs](https://github.com/ipfs/js-ipfs) is ready!
__Note:__ until the __IPFS Javascript Implementation__ is done: __Note:__ until the __IPFS Javascript Implementation__ is done:
- the client (a static web application) requires a full IPFS node because it needs to be able to discover content via the IPFS API. - the client (a static web application) requires a full IPFS node because it needs to be able to discover content via the IPFS API.
- the cache server (written in node) requires a full IPFS node. - the cache server (written in node) requires go-ipfs.
__Note:__ if you want to write data, your __IPNS__ needs to be taken over
by the application. This problem will be solved after go-ipfs 0.4 with the files
API is released.
### License ### License