I take packaging requests (for Guix packages)

If you lack the time to work on a package and you have no specific deadline for it,
you can message me with your requests.
Please mark the email with accordingly so that I can filter them later on, I suggest starting the subject line with “[packaging request]”.
If you do this, please support me on either flattr or patreon (more platforms will eventually be added).

Currently I work on an 1:1 port of torbrowser for Guix (longterm fun project), and completion of the mailman3 packages. Other work in progress packages can be found here.

Flattr this!

opinion: misconceptions about non-commercial federated networks in the press (draft)

This is a response to mashable.com – mastodon-wont-survive. It’s an early public draft, later versions will go more into depth of explaining certain concepts of networks which I do imply knowing here.

As a personal information, I’m neither involved with mastodon development nor do I speak for the project. In fact I’m advocating methods to make the majority of server based networks obsolete in the long run.

Shel Raphen, one of the people who are actively contributing to Mastodon’s codebase wrote an essay here. It was so obvious that I failed to include in this text the fixation of “killing networks” and “financial support” in the press.

This news post reads like a mixture of misunderstanding of federation and just mocking.

Let’s look at everything Mastodon gets wrong.

1) Terrible name

Mastodon implies large, slow, frozen, and dead for thousands of years. The logo is cute, but the service right now stinks almost as badly as a thawing woolly mammoth.

What’s in a name anyway? Softwareprojects and companies don’t have a record for original names (look at twitter, facebook, diaspora), and when they do have original names they tend to be way over the top with too much rocket gear added to the name finding process.

2) There is no single Mastodon

In trying to satisfy a spike of new users, Mastodon broke the cardinal rule of social media: it separated them into silos and made it hard if not impossible for them to all socialize. This unfortunate design makes Mastodon feel more like a bunch of chat rooms rather than a cohesive, growing social network. The Federated Timeline helps, but it’s not the default view.

And I get that having a decentralized social media platform, Mastodon creator Eugen Rochko’s big idea, helps create safe zones from groups and topics, but it’s really a terrible approach that will lead to a stagnant growth and way more opinion bubbles, which is the last thing we need.

(Growth for the growth deity.)
But my dear author, it is federation by design. Let me first introduce this with a picture:
network types in a picture: centralized, decentralized, distributed. copyright or copyleft unknown, assumed to be public domain.

Socialmedia networks do not have to re-use models we currently know as succesful as they get rich by making money of your metadata. Twitter, Facebook, and GooglePlus all are corporate networks with a centralized structure. Mastodon is not the first federated network. Other kinds of networks exists and are in the making (distributed ones). The overall concept of the internet and its earliest usecases was a federation. Email as we know it today is federation. Fidonet, started in 1984, still has 3,652 active nodes and it is federated. Diaspora, even if there might be no longer that much coverage in the press, is federated, has 328 active nodes and around 17.000 users.

To present a more precise usecase of federation you can experience, here’s a diagram by @vhf I am allowed to use (click to see the full size):
diagram: federation of toots in mastodon. created by https://techn.ical.ist/@vhf

3) Toots

In trying to be the anti-twitter, Mastodon’s Rochko chose the dumbest and most ridiculous post name possible: Toots. This too-cute take-off on Tweets literally hurts me every time I say and do it on Mastodon.

See above, regarding names. It’s a personal opinion, I think toots are as random as tweets.

4) Handles are meaningless

User handles do show up in Toots (blech!) but not in the URLs for users’ Mastodon homepages. Giving users numbers (mine is 995) instead of identifiable website addresses makes Mastodon feel amateurish.

Actually they do: @vhf has the handle vhf and the public URL https:// techn.ical.ist/@vhf. What precisely is amateur when it comes to how you format URLs for profiles? In the end you do not interact with the URLs, you interact with the people. I did not see the issue the author of the post raised, so I suppose this is just mocking.

5) Where is everyone?

If you can’t find people by name, then how can you follow them on Mastodon? Someone in one local Mastodon timeline may not appear in another (Sorry, Mr. Shatner). To see everyone (at least I think you see everyone), you have to troll the Federated timeline, open a Toot (blech!) and add them there. Twitter and other social networks already have this stuff figured out. Why is Mastodon better? It’s not!

It’s not as obvious as it is, and should be explained better. You know that for software project bugs can be reported. This is a known (?) documentation bug, for a current explanation take a look at the 2nd image here.

6) Apps feel like a science project

I started using Mastodon in Safari. It was not a good experience. At least there’s an app…or apps.

There is no one app called Mastodon. Instead, you can find a Github list of apps for the open-source project. Apps like the iOS-based Amaroq let you log into any of the many Mastodon “instances” by typing in the name. Nope, there’s no list of instances because I don’t think anyone knows just how many Mastodon instances are out there.

One app per child!
Why is having no centralization of client applications considered bad? It’s about the freedom to create an application and choosing one of many compatible clients, and not being forced to use THE mastodon app.
There is a list of instances and it is being advertised on most instances sign up pages:
https://mastodon.social/about displays a link to this https://instances.mastodon.xyz/ public listing of instances which chose to be displayed.

The Internet is a big place — universe-big — so there’s room for another social media platform, but the Internet can also feel like a very small place, one that targets the weak and consumes them quickly.

Mastodon cannot live on hype alone.

Mastodon has potential. It can be easy to use and there are clearly a lot of people trying it right now. But its weaknesses are glaring. It’s more project than product. Unless someone buys the code off Rochko today and consolidates this mess ASAP, it can’t survive.

This implies that succees can only be achieved if you are throwing money at a project. You have facebook. Companies and other investors have decided to throw money at it, yet it is a threat to democratic systems and human rights. Still people use it. You an throw money at it, but what makes a good project is passion and community interaction. I don’t see a future where facebook opens up contributions to its core code by volunteers with no hidden intentions.

And, no, Mastodon cannot live on hype alone.

I fully agree. But does it have to grow that much? Federated social networks do not scale to world population sizes. Forms of distributed networks can achieve this. Federation still features the same trust issues (points of authority) as centralized networks. The advantage of federation is that you can be transparent about what you publicly state you do, don’t do and if people don’t agree they can move on. I would not say we are at the point where anyone can run a server. Among SysOps knowledge this requires skills and time to debug software, failures etc which normally happen in operation of any software on any network. A small step in the right direction would be a Guix package for Mastodon and system services for it on GuixSD, so that it can be as easy as putting a couple of configuration lines into your local system configuration, run guix system reconfigure, reboot and have a a functional Mastodon node!

Remember Peach? It, too, was a fun social network that let you keep track of friends and share funny images. It was a crappy version of Snapchat without all the sexting.

Peach enjoyed a solid two weeks of being the hottest thing on the social media planet. Then, as I predicted, it fizzled. The last time we talked about Peaches and technology was when Apple changed the peach emoji so it no longer looked like a butt (and then changed it back). No one even mentioned the now mostly forgotten Peach social network.

Late last night on Twitter, we quickly reached the same conclusion: Mastodon is more Peach than Twitter, Less Snapchat than Path.

I was already ready to move on. So was Shatner.

I suspect thousands of other Tooters (blech!) will soon do the same and Mastodon will lay down beside all other other fossilized social media platforms and fade from existence.

Flattr this!

announcing pragmatique – call for participation

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/]

Flattr this!


Long time no update.
I’m busy with documentation about https://pragmatique.xyz currently, and in the process of writing lots of texts I’ve written a page for patreon.

If you want to and follow this page (I have no way of telling how many people read this anyway, as I’m not even remotely interested in tracking the behavior of people and gathering their data), you can visit the profile at https://www.patreon.com/ng0

Stay tuned for the update/launch of the project website.


Flattr this!

the live-system is now named pragmaOS

This week I had another evaluation of my work, and for the live-system this means:

I picked the name pragmaOS.
I’ve decided against a bugtracker. Currently there is one (on our secushare community server), but as a meta-project this is not necessary unless I diverge too much.
I’ve listed some details here, which I hope don’t leave too many questions open.

uclibc-ng is optional, but “nice to have” which is why I’m working on it.

edit 2017-03-19: This post is due for change and reworked. Expect updates on the system in 2 – 3 weeks.

Flattr this!

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…

Flattr this!

guix: 0ad – almost there?

I started working on 0ad in August, the commits I’m working with are dated to the beginning of September.

When you are not focusing 110% on one package it takes some time, especially when the distributed source code base is big.
At first I was stuck on trying to unbundle nvidia-texture-tools, moved it on to a TODO task. Some days ago I started working on it again, and right now it seems as if fixing mozjs-38 is the only major obstacle between the current state and the point where you can play 0ad on Guix and GuixSD.

I hope someone else will take on packaging Xonotic.

Update: Thanks Clément!

Flattr this!

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

Flattr this!