The new Freenet is written in Rust.

lol - same thing with pilots ;)

Thank you!

You're very welcome :)

When the new Freenet is up and running, I think it will be the first system of any kind that could host something like wikipedia, not just the data but the wiki CMS system it's built on. An editable wikipedia, entirely decentralized and very scalable.

I think when the history of the last decade is written, it will be about - in part - the terrible social damage caused by opaque and biased social media algorithms manipulating the public discourse.

Locutus is primarily designed for decentralization, not anonymity - which will make it less suited to IP theft than various other technologies that are already pervasive, the same is true of a lot of the other "people you don't want to be your early adopters" that you mention. It's definitely a risk for systems like Freenet, but it's a manageable risk.

Most of the negative comments so far are from people who I doubt spent 20 seconds looking at our site, so I hope they don't color your judgement. Read through our user manual and form your own opinion.

Once there are viable alternatives on Freenet we'll use them.

I think the time is right, which is exactly why I'm doing what I'm doing :)

Totally agree about the importance of naming, and Freenet has the advantage of literally describing what we're building - a free network.

We've already had interest from everyone from video game developers who want to build a decentralized MMORPG, to political advocacy groups across the political spectrum. Plenty of people value freedom.

You're being surprisingly judgmental when it doesn't seem like you even read the first few paragraphs on the website about it, let alone the other available documentation.

We're still early but we already have a user manual that goes into quite a bit of detail, if you'd like to take a look and if you still have questions I'd be happy to answer.

Minor correction; the amount is $30,000; http://www.taxplanningguide.ca... ... doesn't change your point (which I agree with btw).

1. If you're doing a shed, then the windows and door should be secured; get keypad/key lock, self-locking, that saves you a lot of "did I lock the door", and "where's the key" questions. Get some security bars for the windows without making it feel like jail. Consider shatter-proof windows, or a nice steel mesh if you want to open the windows in good weather. Google some options. Get a steel door and steel door jambs if you won't want someone to kick in the door.
2. Put in some sturdier material on the walls other than half-inch plywood. Insulate, vapor barrier, etc. Make sure you have a solid foundation and water-proof where the wood may be in contact. Keep the shed 1-2 inches off the ground.
3. Get some proper electrical wiring and a shut off switch, or a sub-panel. If you want backup batteries, a consumer UPS won't do the trick especially if you want a rack of servers.
4. If you run cable from the house to the shed, do it undergound, use pvc piping and go at least 2 feet undergound. Run at least two cables and a string/wire to fish more in the future.
5. Get a good view without being distracted and bothered by glare.
6. Splurge on good flooring.
7. Figure out what your ideal desk arrangement is and build the shed accordingly (U-desk, L-desk,
8. Get cable locks
9. Backup to a location inside the house or "cloud"
10. Build a quality roof.
11. Sound-proof, especially the roof.
12. Have a security camera pointed a the shed and inside it if you can

That's exactly what I thought when I read the summary; you can just reference page elements from other sites. Been doing the "http_referer" check for a few years on a basically any web site I deploy or work with..