Entries Tagged 'gnunet' ↓

Status Update: gnurl

I have released gnurl 7.53.1 on 2017-02-24: https://gnunet.org/node/2645 and gnurl 7.54.0 on 2017-04-20: https://gnunet.org/node/2647

status update

I’ve had my ~2 months break to recollect thoughts, reflect on what I have already achieved and now the time to plan new things.
Breaks are good. You are mostly in it for life, and often work as a volunteer is not being payed you do it because you care. To grow tired of the project because of frustration is not good.
Take a break if you do. Rest, find your inner calm, if you have enough money to travel and couchsurfing do that. Start some other hobbies or pick them up again, but balance is important.

It will probably be another 1 – 3 weeks until all the base for pragmatique is covered:
move to ikiwiki, mailserver, put every thought I have gathered about the micro aspects of communities from whiteboard, paper and brain into the new website, etc.
I was also told that the current explanation of the project is still fuzzy and unclear, I’ll fix that too.

Afterwards I will get back to where I was originally complaining about working with an outdated version of GNUnet to create a service for an outdated version of GNUnet. With GNUnet roadmap goals for the next version release at 99%, 2 real bugs left to solve I hope a release happens so I can work with a real test case.

announcing infotropique – call for participation

The content here is kept for reasons, it is just inaccurate at this point. The name has been changed to infotropique, and infotropique OS.

Today I’m announcing pragmatique, a new project.

Its primary focus is to open up the efforts I’ve been working on for some time to other people, to provide space as a community, and to work on more than just software.

Our main project is pragmaOS, an on-going project to build a live-system for applications around GNUnet and further software solutions which make use of GNUnet, based on GuixSD.

We are currently setting up our new development server, so there’s no immediate fancy environment to sign up at and start hacking.

Our software page shows an early road map without the targeted versions.

You can read more about our project at pragmatique.xyz – be aware that this is an early version of the web site.

Let me know what you think and join the fun!

[edit, 2017-04-24 00:01. Official news around pragmatique are now announced at https://pragmatique.noblogs.org/]

Guix and gnunet-fs (a draft)

This article is a public draft, expect it to change. At this point it mostly originates from chats with some minor edits.

At secushare we already collected some notes about certain aspects of GNUnet and why we picked it over other existing networks and technologies.

As it has been an topic since the start of Guix (search archives of guix-devel for “binary distribution through gnunet”), a couple of people have been working on this, but if I remember correctly no one has mentioned in detail why we should use gnunet-fs and not ipfs, torrents, and the like.

On our page titled anonymity[onion|clearnet] we explain why it is of fundamental importance that we use one single technology for anonymization of all use cases and not several technologies like ipfs, freenet, tor, and others side by side.

Compared to freenet, gnunet-fs has extensive censorship resistance and sibyl attack protection.

Ipfs does not gossip (proactively disseminate some information that may be useful later), so if nobody cares for what you publish it will disappear.
It (ipfs) depends on getting attention for your content (attention economy), which can be bad if for example a whistleblower publishes information but needs to disconnect before announcing it to the public.

It is foundational for gnunet to make padding actually useful, whereas in some of tor’s bridge protocols it is just thrown away bandwidth.

Ipfs has the advantage of being fast and simple, but it can never be anonymous, not even when you combine it with tor.

Freenet is working alright, but is has the disadvantage of not being very good for real-time applications and that the attacks descibed in the paper of Christian Grothoff aren’t fixed yet as far as I know at this point.

So, gnunet would be good in this case (distributing binary substitutes for Guix), to not just serve one technology.

So far we don’t know of any flaws in the architectural design of gnunet which would leave it open to attacks on that level.

In addition to the pure distribution purpose, I want to go beyond just publishing binaries. More on that later.

to be edited and continued…

status update: gnurl

December saw two releases of gnurl (should it be stylized as `gnURL`?), version 7.52.0 and 7.52.1.  Both releases suffered (as the previous release) from my change of the release system.

Previously I used Gentoo and GuixSD, built on both in parallel and prepared the release tarball on Gentoo and signed over on GuixSD.
Artifacts of `/gnu/store…` references remained, but with the help I received in help-guix: 2016-12: Seeking advice: preparing releases on GuixSD
the next release should only have such a reference in ltmain.sh (which is a minor bug in the Guix package). It just need a minor fix to rename the resulting directory and tarball for `make dist` in addition to the ltmain.sh issue.

Changes for the Guix package of gnurl are covered in