Home About News

Recent News Atom feed

The state of infotropique OS

ng0 — August 18, 2017

As you can see[0] I have tried to improve the website for infotropique a bit (help with the website is still wanted though).

So what has changed sine the last "the state of infotropique OS" post? Many things, apparently:

  • We now have a git host (in the community of GNUnet, but addressable with

    • master is still with no pushed commits though
  • The documentation is now largely outdated and needs to be rewritten
  • Goals are better defined in public presentation, or at least it is assumed that they are
  • You will not be able to just point your guill pull --url at our repository, more on that later in the documentation
  • Most notes are still on paper and in local systems
  • Almost all of the work still happens with direct target to Guix directly, so the master repository will only be useful with Guix, not on its own

    • However there will be a mechanism to make it work without a pre-existing Guix

Now I just need to find the time to write the documentation.


In music - GNUnet and its potential for artists

ng0 — August 5, 2017

krosos started at some time around 2000 or 2002 with myself (ng0) doing live rehearsals with other people. The line-up changed many times, leading to the conclusion that krosos can't exist as a group formation. With the last line-up I produced one EP ("Journey through Darkness") and one Album ("I"), both never saw the light of day until today and instead krosos went on hiatus.

This hiatus lasted about 6 years (or more? or less? a damn long time). In the meantime I got more involved with other creative projects, some of them were a continuation of projects started before the hiatus.

Most of the ideas and projects around them are connected. I need a little more of a reference to the past until I can get to the point of this post: In the last 15 years people approached me about websites for their bands, with simple and common goals and ideas. Of course the work on the websites never happened because there was one thing I could never fulfill: They should be easy to use and maintain for people who are not interested in staying up to date with technology and don't have much time to learn or care for security. Furthermore some (not all) big festivals, bands and record labels moved entirely to Facebook and LastFM to announce their concerts and changes to them. If it would've been just an addition to their websites that would've been no problem, but some even abandoned their independent websites. We as artists have a huge problem when we start to rely exclusively on corporate infrastructures. For myself this meant: What we have is not working anymore. And what we could have is not there yet and no technology has managed to be easy to use and respect your freedom. This can be applied to many technologies, but I'm mainly interested in supporting DIY music, events, political groups, activists, artists and oppressed groups of people in society.

When I found GNUnet back in 2014 (or '15?) one of my initial thoughts was that this could be used for artist of any trade when you write an application (or many) around it. Even in early stages you could simply use the filesharing part. Because it's unlikely that the sheer mass of ideas I have will all be executed by myself alone: GNUnet and artists. Let's just focus on artists who work with sound. I envision a use of the network where you cut down the need for a middle party (record labels) and you can offer your work directly, exchanged peer-to-peer. Payment (I didn't see this one coming back in 2014) could be arranged via TALER once it is ready. This is based on the same principle as todays agreements: if people like your work the majority who can will support you and don't leak your work. Taking this a step further, we would provide one last middle-party which is providing software that provides a platform for artists and their fans and customers. This middle-party has some servers which can be used to publish data faster (think of it as an express offload into the filesharing subsystem of GNUnet). The software offers an easy interface for returning functions: you can upload works or pictures of it, you create a "website", people have options to contact you and you can do all the things you'd do to present yourself. As far as I understand secushare, this could very well be realized as a later extension of it. Middle-parties can continue to exist if you must or wish to remain anonymous, you like to let other people do your PR work, etc.

I had more notes on this, but this is the very basic of how I imagine it could work. Maybe I will realize it, maybe someone else. The point is, we have the power in our hands to take down unfair conditions of how payments for our work are made. If this is put from thought to code and people start using it, we as artists and as society can renegotiate living conditions for those who do art for their living.

The state of infotropique OS

ng0 — June 22, 2017

This is not suited for the official outlet, so it will be posted here.

My main activity in the last weeks has been thinking about order, structure, organization, expansion and start of infrastructure, and the many aspects of the system including how to maintain this the best way so that relevant parts of code can be shared with GuixSD.

Nothing is really "static" and fixed to what I wrote in the Email many weeks ago, the only fixed fact is that the goal is to make GNUnet universal usable.

At the moment I am writing a documentation handbook. I could simply develop on my own and wait for more people to ask where they could contribute, but infotropique maintenance and development will soon run on shared time.

Development is just a one person job at the moment, so I can't really calculate any deadlines for first releases.

We are still discussing the source code repository location and workflow, so I'm sitting on some unreleased material, specifically the master repository.

Within the next months you should be able to:

  • read the handbook, intended for contributors and those who want to become contributors (later it will be expanded, I just need to make a start for developers)
  • point your guix pull to an URL which represents first individual pieces of this system
  • and more

a temporary place: github pages

ng0 — June 22, 2017

I wanted to avoid this, but cutting down on costs and time spent with server administration has driven me back to use Github for this website.

There's a '' in the title, but the page so far makes use of only.

It's okay, one day I will have either GuixSD or infotropique OS running on a shared or dedicated server.

edit: and the experiment has ended. No github.

release: fish-guix 0.1.1

ng0 — April 29, 2017

I have released version 0.1.1 of fish-guix (completions for Guix for the FISH shell) yesterday with no release message/details.

release: fish-guix 0.1.0

ng0 — April 27, 2017

I have released version 0.1.0 of fish-guix (completions for Guix for the FISH shell) today: release message

release: gnurl 7.53.1 and 7.54.0

ng0 — April 26, 2017

I have released gnurl 7.53.1 on 2017-02-24 and gnurl 7.54.0 on 2017-04-20.


ng0 — April 26, 2017

Every year I repeat:

"every mail client sucks"

I hope I won't write my own set of Email tools, but it is on my list of things to write.


ng0 — April 21, 2017

I plan to integrate smu (a simple markup) into ([Haunt]. I also consider to re-implement or write bindings to prep (a small preprocessor with multilanguage support written in perl).

This weekend I learned:

  • The fact that the maildir to mh/nnml converter of Gnus in Emacs runs with just one thread is very unfortunate if you do this with more than 700.000 messages.

I will either improve this in Emacs or write my own converter.

The other way around with the nml2md converter I have is blazing fast.

hello again

ng0 — April 20, 2017

I decided to keep this domain name for constructing an online showcase of my work and a simple web log. And it will serve as a platform for music once I get to finish the albums.

It used to be written at the time of writing this post in yet another version and language of my own website compiler, but it is now compiled with haunt.

release: gnurl 7.52.0, 7.52.1

ng0 — December 26, 2016

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 the next release should only have such a reference in (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 issue.

Changes for the Guix package of gnurl are covered in