3 ms·
Freenet-core itself isn’t stable enough to rely on for something like family chat, and River is still missing some important operational pieces. In particular,
by sanity 9mo ago
Freenet-core itself isn’t stable enough to rely on for something like family chat, and River is still missing some important operational pieces. In particular, there isn’t a smooth or robust way yet to handle things like updating the room contract, which is the decentralized part that defines membership and state. That makes recovery from mistakes or bugs harder than it should be.
That said, a lot of progress has been made recently. Stability has improved noticeably even over the past couple of weeks, and most of the remaining issues are about hardening and ergonomics rather than fundamental design problems.
I’m hesitant to give timelines, but my expectation is weeks rather than months before River is something I’d personally feel comfortable recommending for non-technical use. In the meantime, feedback from people trying it, especially around rough edges or failure cases, is very helpful.
- pamcake 9mo agoThat you don't mention NAT punching or discovery as outstanding is encouraging - that seems to be the hard part where others fall so if that's in a workable state and the project resists the allure of centralizing control ("streamlining" updates for that contract, say), I'm sure the rest will follow! Even if it's months not weeks in the end.
- sanity 9mo agoYes, we have a lot of experience with NAT hole-punching which should work with most (but not all) firewalls, and our plan is that peers which don't require NAT hole-punching can help those that don't support it.