A lot of the comments here seem to be missing the point and presumably come from people that didn't actually install the program and try it out, or hell even read the README.
This thing is extremely minimalist. A little bit silly to be talking about adding Markdown, antispam or privacy support when it uses $EDITOR for viewing/authoring posts, and the DB is world writeable...
Personally I think this is a lot of fun, it's the first project that has actually motivated me to install IPFS (which I thought would be much harder). It is in the vein of something like SDF where the retro interface might attract the right kind of people. I hope the author keeps working on it and if I knew Go I might contribute :)
IPFS is one of those things that shows up on my radar every year or so recently, I drool over it from afar, then I download it and install it and try to use it for a real use case and... it doesnt work.
I've went thru what I thought were the default tutorials and... nothing. Made me feel like the docs were leaving something out.
On paper it would be a useful tool to add to my toolbox. Someday...
Let's say I have ten hard drives where no more than two are the same size, so at least 5 pairs or maybe 10 different sizes. For this, zfs cannot be used to expose a single mountpoint.
Perhaps with something like ipfs a single mountpoint could be exposed and allow replicated data to be retained?
The key word here is "replicated" - as in a certainty that the data exists on more than one physical storage device.
I'm spitballing and this isn't necessarily directed at the parent of this comment.
Just an idea: What if instead of writing a client that uses a new protocol we did that on the server? That is, implementing something like this project, but into a local news server, so that users can connect with whatever client they wish to localhost:119, while the server maintains the groups and messages pool in sync through IPFS or any similar mean.
Discoverability has always been the #1 issue for me, so if someone can figure out how to establish any kind of namespace for IPFS I'm willing to apply a few more braincells to it.
This thing is extremely minimalist. A little bit silly to be talking about adding Markdown, antispam or privacy support when it uses $EDITOR for viewing/authoring posts, and the DB is world writeable...
Personally I think this is a lot of fun, it's the first project that has actually motivated me to install IPFS (which I thought would be much harder). It is in the vein of something like SDF where the retro interface might attract the right kind of people. I hope the author keeps working on it and if I knew Go I might contribute :)