Forgot your password?
Close
typodupeerror

Comment Re:So i can just post 30TB and get it later? (Score 5, Informative) 66

No. Trying to push 30TB into Freenet will be interpreted as an attack on the network by other peers and they'll disconnect from your peer.

Freenet is better viewed as a communication medium than a storage medium. Data is prioritized according to demand, somewhat like an LRU cache. You can't upload 30TB and expect the network to preserve it for you.

On liability, running a Freenet peer is more like running network infrastructure that automatically routes and caches other people's traffic than intentionally publishing it. US law explicitly recognizes this distinction in the DMCA's provisions for transitory network communications and system caching. We discuss this in more detail in the FAQ.

Comment Re:Just a heads up, decentralized platforms... (Score 4, Informative) 66

You obviously haven't tried Freenet. You can join our room on River and you'll see no spam, no fraud, no hate speech, none of that.

Decentralized doesn't mean unmoderated. Systems built on Freenet can be moderated however their creators and communities want. River is moderated.

The difference is that nobody running one service gets to decide what everyone else is allowed to run.

Submission + - Freenet: Apps Without Platforms

Submitted by Sanity
Sanity writes: Earlier this year Slashdot covered the launch of the completely redesigned Freenet. I recently gave a talk about what we've been building since then. Unlike traditional web applications, apps on Freenet have no central server or database, with application state instead distributed across the network. These now include decentralized group chat, publishing, search, and fully decentralized Git hosting. The talk also gets into some of Freenet's internals, including how we use machine learning for network routing.

Comment Re:Where does the data live? (Score 4, Informative) 26

by Sanity (#66042712) Attached to: New Freenet Network Launches, Along With 'River' Group Chat

Thanks for your questions, Freenet caches data but it isn’t meant to be a long-term storage network. It’s better to think of it as a communication system. Data persists as long as at least one node remains subscribed to it. If nobody subscribes (including the author), it will eventually disappear from the network. So yes, if only your node subscribes then the data will only exist there and won’t be available when your machine is offline. But if other nodes subscribe it will be replicated automatically and remain available even if your node goes offline.

Submission + - New Freenet Network Launches With River Group Chat (freenet.org)

Submitted by Sanity
Sanity writes: Freenet’s new generation peer-to-peer network is now operational, along with the first application built on the network: a decentralized group chat system called River.

The new version is a complete redesign of the original project, focusing on real-time decentralized applications rather than static content distribution. Applications run as WebAssembly-based contracts across a small-world peer network, allowing software to operate directly on the network without centralized infrastructure.

An introductory video demonstrating the system is available on YouTube.

Slashdot previously covered the reboot of Freenet in 2023 in this article.

Submission + - 'Just Because Linus Torvalds Vibe Codes Doesn't Mean it's a Good Idea' (theregister.com)

Submitted by Anonymous Coward
An anonymous reader writes: Vibe coding got a big boost when everyone's favorite open source programmer, Linux's Linus Torvalds, said he'd been using Google's Antigravity LLM on his toy program AudioNoise, which he uses to create "random digital audio effects" using his "random guitar pedal board design." This is not exactly Linux or even Git, his other famous project, in terms of the level of work. Still, many people reacted to Torvalds' vibe coding as "wow!" It's certainly noteworthy, but has the case for vibe coding really changed? [...] It's fun, and for small projects, it's productive. However, today's programs are complex and call upon numerous frameworks and resources. Even if your vibe code works, how do you maintain it? Do you know what's going on inside the code? Chances are you don't. Besides, the LLM you used two weeks ago has been replaced with a new version. The exact same prompts that worked then yield different results today. Come to think of it, it's an LLM. The same prompts and the same LLM will give you different results every time you run it. This is asking for disaster.

Just ask Jason Lemkin. He was the guy who used the vibe coding platform Replit, which went "rogue during a code freeze, shut down, and deleted our entire database." Whoops! Yes, Replit and other dedicated vibe programming AIs, such as Cursor and Windsurf, are improving. I'm not at all sure, though, that they've been able to help with those fundamental problems of being fragile and still cannot scale successfully to the demands of production software. It's much worse than that. Just because a program runs doesn't mean it's good. As Ruth Suehle, President of the Apache Software Foundation, commented recently on LinkedIn, naive vibe coders "only know whether the output works or doesn't and don't have the skills to evaluate it past that. The potential results are horrifying."

Why? In another LinkedIn post, Craig McLuckie, co-founder and CEO of Stacklok, wrote: "Today, when we file something as 'good first issue' and in less than 24 hours get absolutely inundated with low-quality vibe-coded slop that takes time away from doing real work. This pattern of 'turning slop into quality code' through the review process hurts productivity and hurts morale." McLuckie continued: "Code volume is going up, but tensions rise as engineers do the fun work with AI, then push responsibilities onto their team to turn slop into production code through structured review."

Slashdot Top Deals

Often statistics are used as a drunken man uses lampposts -- for support rather than illumination.

Close