111–120 of 302 posts
Earlier quoted context omitted.
WTF. These are some of the first things I clicked through on that page: - https://www.mail-archive.com/devl@freenetproject.org/msg5534... - https://www.mail-archive.com/devl@freenetproject.org/msg5534... Gee, I can't imagine how that mailing list could ever be toxic.
Lol. It's like Linus but crunchier
Imagine an application where an authorized group of users can create and vote in polls, using cryptographic signatures and public/private keys for user verification.
What prevents me from connecting and saying that "everybody's state is wrong, that poll in 2024 which didn't reach quorum actually did, because I voted in it, here's my vote." How can the state merger know that the existing state has been valid for two years, and that the vote shouldn't be retroactively applied?
Blockchains solve this by having state get more authoritative as blocks age. To undo the `poll_didnt_reach_quorum` state transition from 2024, one would have to rewind all blocks that have been created since, and PoW / PoS ensures that this is incredibly costly to do.
On a related note, how does your design prevent sybil attacks, where one participant floods the network with many large contracts and large state updates?
Notably this project was conceived by a backroom decision to dump the original Freenet development team's work, in favor of a rewrite from different developers, without asking anyone on the original team. It was an ivory tower decision which was announced on the mailing list without prior discussion. The old team did not agree, yet it was forced through by a decision of the "board". The "board" was a group of people…
Well, that name pretty much dooms the project to a slow death in obscurity.
Earlier quoted context omitted.
Yeah, I'm not a fan. Feels like this project is trying to get popular off of Freenet's name recognition rather than its own merits.
The submitter is the creator of the original Freenet. If anybody gets to decide what we will call Freenet, it’s him.
Can this be used to sync the data of an app from mobile to desktop without a server ? And vice-versa.
In principle but we don't yet support mobile except experimentally, in part due to mobile OS restrictions (eg. iOS apps can't embed webassembly).
Ed: I guess you'd need a way to run wasm in wasm, and a way to author wasm contracts - and there's not yet a wasm-hosted rust compiler?
Ed2: I'm not up to date on the state of self-hosted wasm compiler/languages... But I did come across:
https://github.com/remko/waforth
I guess it's time to dig out the thesis[t] again and look at movable code and p2p classifications again ...
[t] https://ics.uci.edu/~fielding/pubs/dissertation/net_arch_sty...
It feels like the state merging approach just pushes the hard problems onto the user, without giving them the tools to solve those problems properly. Imagine an application where an authorized group of users can create and vote in polls, using cryptographic signatures and public/private keys for user verification. What prevents me from connecting and saying that "everybody's state is wrong, that poll in 2024 which di…
> It feels like the state merging approach just pushes the hard problems onto the user, without giving them the tools to solve those problems properly.
We've created many of these tools, and have used them to implement practical applications like group chat, a CMS, and a social network, and we and others will build many more tools over time. Designing applications for Freenet can require some creative problem solving, but each problem only needs to be solved once.
> What prevents me from connecting and saying that "everybody's state is wrong, that poll in 2024 which didn't reach quorum actually did, because I voted in it, here's my vote." How can the state merger know that the existing state has been valid for two years, and that the vote shouldn't be retroactively applied?
You could solve this similarly to Bitcoin by having a mechanism that "locks" poll results at a particular point in time to prevent subsequent additions, analogous to how mining repeatedly locks in the blockchain.
> On a related note, how does your design prevent sybil attacks, where one participant floods the network with many large contracts and large state updates?
Peers in the network track cost/benefit of each connected peer, so if a peer starts to consume a lot more resources than it provides then its neighbors will disconnect, a kind of immune response.
I'm sure that once the network is big enough to attract large-scale attacks we'll need to adapt our approach, but I think we have a solid starting point.
Earlier quoted context omitted.
WTF. These are some of the first things I clicked through on that page: - https://www.mail-archive.com/devl@freenetproject.org/msg5534... - https://www.mail-archive.com/devl@freenetproject.org/msg5534... Gee, I can't imagine how that mailing list could ever be toxic.
Not sure what you mean but I stand by every word I said in that thread.
"The woke mind virus" really? You used that non-ironically? This is not something a serious or sane person would say for real.
Earlier quoted context omitted.
Extremely depraved things are not the only thing to use freedom of speech for, and freely speaking can result in all kinds of repressions. And even without agreeing on whether people should be anonymous on the Internet, it could be agreed that replacing a software which guards against a certain threat model (repressions) with one which does not, without changing the name, is not exactly a wise decision.
The new Freenet will support the creation of anonymity systems as services on top of it, which is much better architecturally than tying the platform to one approach to anonymity as I did when I designed the original Freenet. We will also have a decentralized reputation system that will protect people from being exposed to unsavory or illegal content, a common criticism of the old Freenet architecture.
I know you designed the thing, and that was a great effort, but what a miss when compared to the vast majority of freenet users priorities.