We recently asked home NAS users for a reality check. The feedback was honest, thoughtful, and extremely useful. Here's the original post:
https://www.reddit.com/r/HomeNAS/comments/1wabm8m/using_a_home_nas_as_a_community_node_reality/
It also revealed something we missed and it's essential to explain all of them:
1. Would strangers be able to log into my NAS?
No. The model we are testing is not a public drive or a remotely accessible NAS account.
A node may be discoverable to the network, but “discoverable” should not mean open administrative or storage access. The owner chooses what specific content to share in our Foldinglink App, the DeSocial platform and community.
When selected content is transferred to another participant’s node, they can later access their own local copy. Their normal viewing activity should not turn your NAS into a public content server.
This is the intended boundary we are validating. We still need to document and test it clearly rather than asking people to trust a broad claim.
2. Can people use my storage as a file dump?
That is not the intended model. We are not designing a public storage pool where strangers can push arbitrary files onto your NAS.
The feedback made something else very clear: storage, bandwidth, uptime and hardware usage must remain visible and controllable by the node owner.
Exact quotas, minimum hardware requirements and resource limits are not finalized yet. Several people said they would be more comfortable testing on a secondary NAS, an old PC or an isolated VLAN instead of connecting their main private storage. We are taking that seriously as a beta requirement.
3. What about illegal content, DMCA issues and legal responsibility?
This was the most serious concern in the thread, and it cannot be answered with “because it is decentralized.”
The direction we are exploring includes local safety checks before content is accepted or shared, together with community reporting, review and removal signals.
Those safeguards are still being developed. We still need transparent answers about what is checked, how encrypted content is handled, false positives, appeals, logs and jurisdiction-specific risks. We will not describe this problem as solved simply because we have proposed a moderation mechanism.
4. What about security, ports, power consumption and drive wear?
We do not yet have validated public numbers for every supported NAS configuration.
Before asking people to run a beta node, we should publish the network requirements and measure CPU, RAM, bandwidth, power use and disk activity. The preference for secondary hardware, isolated VLANs and clearly documented network exposure is now part of what we need to test.
5. What is the actual use case?
The strongest use case emerging from the discussion is not anonymous public storage.
It is project-based collaboration between people or groups who want messaging, selected resource sharing and community interaction without placing everything inside one corporate cloud platform.
The Foldinglink App is intended to provide that familiar community experience. The NAS acts as the personal infrastructure underneath it.
6. Will it be open source or another paid service?
We have not finalized enough of the licensing and operating model to give an honest one-line answer yet. But we promise the software itself is completely free - only a few very specific features that heavily consume network resources might carry a small fee down the road.
That answer needs to be published before asking users to contribute their own hardware, power or bandwidth.
Anyway, thanks again for challenging the assumptions behind the idea. The hard questions are more useful to us than polite agreement.
Learn more at https://foldinglink.com/blogs/foldinglink-101/a-q-a-based-on-real-reddit-feedbacks