- Ploum.net En - listes.ploum.net

My colleague Julius
by Ploum.net (English posts only) 23 Dec '24

23 Dec '24

MY COLLEAGUE JULIUS by Ploum on 2024-12-23 https://ploum.net/2024-12-23-julius-en.html Traduction en français https://ploum.net/2024-12-23-julius-fr.html Do you know Julius? You certainly know who I’m talking about! I met Julius at university. A measured, friendly young man. He always wore a smile on his face. What struck me about Julius, aside from his always perfectly ironed clothes, was his ability to listen. He never interrupted me. He accepted gratefully when he was wrong. He answered questions without hesitation. He attended all the classes and often asked for our notes to "compare with his own" as he said. Then came the infamous computer project. As a team of students, we had to code a fairly complex system software using the C language. Julius took part in all our meetings but I don’t remember witnessing him write a single line of code. In the end, I think he did the report formatting. Which, to his credit, was very well done. Because of his charisma and elegance, Julius was the obvious choice to give the final presentation. He was so self-confident during the presentation that the professors didn’t immediately notice the problem. He had started talking about the C virtual machine used in our project. He even showed a slide with an unknown logo and several random screenshots which had nothing to do with anything known in computing. For those who don’t know about computing, C is a compiled language. It doesn’t need a virtual machine. Talking about a C virtual machine is like talking about the carburettor of an electric vehicle. It doesn’t make sense. I stood up, interrupted Julius and improvised by saying it was just a joke. “Of course!” said Julius, looking at me with a big smile. The jury was perplexed. But I saved the day. Throughout our studies, I’ve heard several professors discuss the “Julius case.” Some thought he was very good. Others said he was lacking a fundamental understanding. Despite failing some classes, he ended up graduating with me. After that, our paths went apart for several years. I’ve been working for nearly a decade at a large company where I had significant responsibilities. One day, my boss announced that recruiters had found a rare gem for our team. An extraordinary resume, he told me. From the perfect cut of his suit, I recognised Julius before seeing his face. Julius! My old classmate! If I had aged, he had matured. Still charismatic and self-assured. He now sported a slightly graying three-day beard that gave him an air of wise authority. He genuinely seemed happy to see me. We talked about the past and about our respective careers. Unlike me, Julius had never stayed very long in the same company. He usually left after a year, sometimes less. His resume was impressive: he had gained various experiences, touched on all areas of computing. Each time, he moved up in skills and salary. I would later discover that, while we held similar positions, he had been hired at twice my salary. He also got bonuses I didn’t even know existed. But I wasn’t aware of this aspect when we started working together. At first, I tried to train him on our projects and internal processes. I assigned him tasks on which he would ask me questions. Many questions, not always very relevant ones. With his characteristic calm and his signature smile. He took initiatives. Wrote code or documentation. He had answers to all the questions we could ask, regardless of the field. Sometimes it was very good, often mediocre or, in some cases, complete nonsense. It took us some time to understand that each of Julius’s contributions needed to be completely reviewed and corrected by another team member. If it was not our field of expertise, it had to be checked externally. We quickly had a non-written rule stating that no document from Julius should leave the team before being proofread by two of us. But Julius excelled in formatting, presentation, and meeting management. Regularly, my boss would come up to me and say, “We’re really lucky to have this Julius! What talent! What a contribution to the team!” I tried, without success, to explain that Julius understood nothing of what we were doing. That we had reached the point where we sent him to useless meetings to get rid of him for a few hours. But even that strategy had its limits. It took us a week of crisis management meetings to calm down a customer disappointed by an update of our software. We had to explain that, if Julius had promised that the interface would be simplified to have only one button that would do exactly what the client wanted, there was a misunderstanding. That aside from developing a machine that read minds, it was impossible to meet his complex needs with just one button. We decided to act when I heard Julius claim to a customer, panicked at the idea of being "hacked", that, for security reasons, our servers connected to the Internet had no IP address. We had to forbid him from meeting a client alone. For those who don’t know about computing, the "I" in IP address stands for Internet. The very definition of the Internet is the network of interconnected computers that have an IP address. Being on the Internet without an IP address is like claiming to be reachable by phone without having a phone number. The team was reorganised so that one of us was always responsible for keeping Julius occupied. I never wanted to speak ill of him because he was my friend. An exasperated programmer had no such restraint and exposed the problem to my boss. Who responded by accusing her of jealousy, as he was very satisfied with Julius’s work. She was reprimanded and resigned shortly after. Fortunately, Julius announced that he was leaving because he had received an offer he couldn’t refuse. He brought cakes to celebrate his last day with us. My boss and the entire human resources department were genuinely sad to see him go. I said goodbye to Julius and never saw him again. On his LinkedIn account, which is very active and receives hundreds of comments, the year he spent with us became an incredible experience. He hasn’t exaggerated anything. Everything is true. But his way of turning words and a kind of poorly concealed modesty gives the impression that he really contributed a lot to the team. He later became the deputy CEO then interim CEO of a startup that had just been acquired by a multinational. An economic newspaper wrote an article about him. After that episode, he joined the team of a secretary of state. A meteoric career! On my side, I tried to forget Julius. But, recently, my boss came to me with a huge smile. He had met the salesperson from a company that had amazed him with its products. Artificial intelligence software that would, I quote, boost our productivity! I now have an artificial intelligence software that helps me code. Another that helps me search for information. A third one that summarises and writes my emails. I am not allowed to disable them. At every moment, every second, I feel surrounded by Julius. By dozens of Juliuses. I have to work in a mist of Juliuses. Every click on my computer, every notification on my phone seems to come from Julius. My life is hell paved with Juliuses. My boss came to see me. He told me that the team’s productivity was dangerously declining. That we should use artificial intelligence more effectively. That we risked being overtaken by competitors who, without a doubt, were using the very latest artificial intelligence. That he had hired a consultant to install a new time and productivity management artificial intelligence. I started to cry. “Another Julius!” I sobbed. My boss sighed. He patted my shoulder and said, “I understand. I miss Julius too. He would certainly have helped us get through this difficult time.” Picture by Max Gruber/Better Images of AI https://betterimagesofai.org/images?artist=MaxGruber&title=Clickworker3d-pr…

1 0

20 years of Linux on the Desktop (part 2)
by Ploum.net (English posts only) 16 Dec '24

16 Dec '24

20 YEARS OF LINUX ON THE DESKTOP (PART 2) by Ploum on 2024-12-16 https://ploum.net/2024-12-16-linux_desktop2.html > Previously in "20 years of Linux on the Deskop" : Looking to make the perfect desktop with GNOME and Debian, a young Ploum finds himself joining a stealth project called "no-name-yet". The project is later published under the name "Ubuntu". 20 years of Linux on the Desktop (part 1) https://ploum.net/2024-10-20-20years-linux-desktop-part1.html Flooded with Ubuntu CD-ROMs =========================== The first official Ubuntu release was 4.10. At that time, I happened to be the president of my University LUG: LouvainLiNux. LouvainLiNux was founded a few years before by Fabien Pinckaers, Anthony Lesuisse and Benjamin Henrion as an informal group of friends. After they graduated and left university, Fabien handled me all the archives, all the information and told me do continue the work while he was running his company that would, much later, becomes Odoo. With my friend Bertrand Rousseau, we decided to make Louvain-Li-Nux a formal and enduring organisation known as "KAP" (Kot-à-Projet). Frédéric Minne designed the logo by putting the student hat ("calotte") of Fabien on a penguin clipart. Louvain-Li-Nux https://www.louvainlinux.org/ In 2005 and 2006, we worked really hard to organise multiple install parties and conferences. We were also offering resources and support. At a time where broadband Internet was not really common, the best resource to install GNU/Linux was an installation CD-ROM. Thanks to Mark Shuttleworth’s money, Ubuntu was doing something unprecedented: sending free CD-ROMs of Ubuntu to anyone requesting them. Best of all: the box contained two CD-ROMs. A live image and an installation CD. Exactly how I dreamed it (I’m not sure if the free CD- ROMs started with 4.10, 5.04 or even 5.10). I managed to get Louvain-Li-Nux recognised as an official Ubuntu distributor and we started to receive boxes full of hundreds of CD-ROMs with small cardboard dispensers. We had entire crates of Ubuntu CD-ROMs. It was the easiest to install. It was the one I knew the best and I had converted Bertrand (before Fabien taught me about Debian, Bertrand tried to convert me to Mandrake, which he was using himself. He nevertheless spent the whole night with me when I installed Debian for the first time, not managing to configure the network because the chipset of my ethernet card was not the same as the one listed on the box of said card. At the time, you had to manually choose which module to load. It was another era, kids these days don’t know what they are missing). With Louvain-Li-Nux, we literally distributed hundreds of CD-ROMs. I’ve myself installed Ubuntu on tenths of computers. It was not always easy as the market was pivoting from desktop computers to laptops. Laptops were starting to be affordable and powerful enough. But laptops came with exotic hardware, wifi, Bluetooth, power management, sleep, hibernate, strange keyboard keys and lots of very complex stuff that you don’t need to handle on a desktop computer with a RJ-45 hole. Sound was a hard problem. I remember spending hours on a laptop before realising there was a hardware switch. To play multiple sounds at the same time, you needed to launch a daemon called ESD. Our frustration with ESD would lead Bertrand and I to trap Lennart Poetering in a cave in Brussels to spend the whole night drinking beers with him while swearing we would wear a "we love Lennart" t-shirt during FOSDEM in order to support is new Polypaudio project that was heavily criticised at the time. Spoiler: we never did the t-shirt thing but Polypaudio was renamed Pulseaudio and succeeded without our support. Besides offering beers to developers, I reported all the bugs I experienced and worked hard with Ubuntu developers. If I remember correctly, I would, at some point, even become the head of the "bug triaging team" (if such a position ever existed. It might be that someone called me like that to flatter my ego). Selected as a student for the Google Summer of Code, I created a python client for Launchpad called "Conseil". Launchpad had just replaced Bugzilla but, as I found out after starting Conseil, was not open source and had no API. I learned web scrapping and was forced to update Conseil each time something changed on Launchpad side. The most important point about Bugzilla and Launchpad was the famous bug #1. Bug #1, reported by sabdfl himself, was about breaking Microsoft monopoly. It could be closed once it would be considered that any computer user could freely choose which operating system to use on a newly bought computer. The very first book about Ubuntu ================================ Meanwhile, I was contacted by a French publisher who stumbled upon my newly created blog that I mainly used to profess my love of Ubuntu and Free Software. Yes, the very blog you are currently reading. That French publisher had contracted two authors to write a book about Ubuntu and wanted my feedback about the manuscript. I didn’t really like what I read and said it bluntly. Agreeing with me, the editor asked me to write a new book, using the existing material if I wanted. But the two other authors would remain credited and the title could not be changed. I naively agreed and did the work, immersing myself even more in Ubuntu. The result was « Ubuntu, une distribution facile à installer », the very first book about Ubuntu. I hated the title. But, as I have always dreamed of becoming a published author, I was proud of my first book. And it had a foreword by Mark Shuttleworth himself. I updated and rewrote a lot of it in 2006, changing its name to "Ubuntu Efficace". A later version was published in 2009 as "Ubuntu Efficace, 3ème édition". During those years, I was wearing Ubuntu t-shirts. In my room, I had a collection of CD-ROMs with each Ubuntu version (I would later throw them, something I still regret). I bootstrapped "Ubuntu- belgium" at FOSDEM. I had ploum(a)ubuntu.com as my primary email on my business card and used it to look for jobs, hoping to set the tone. You could say that I was an Ubuntu fanatic. The very first Ubuntu-be meeting. I took the picture and gimped a quick logo. https://ploum.net/files/old/ubuntube_fosdem.jpg Ironically, I was never paid by Canonical and never landed a job there. The only money I received for that work was from my books or from Google through the Summer of Code (remember: Google was still seen as a good guy). I would later work for Lanedo and be paid to contribute to GNOME and LibreOffice. But never to contribute to Ubuntu nor Debian. In the Ubuntu and GNOME community with Jeff Waugh ================================================= Something which was quite new to me was that Ubuntu had a "community manager". At the time, it was not the title of someone posting on Twitter (which didn’t exist). It was someone tasked with putting the community together, with being the public face of the project. Jeff Waugh is the first Ubuntu community manager I remember and I was blown away by his charism. Jeff came from the GNOME project and one of his pet issues was to make computers easier. He started a trend that would, way later, gives birth to the infamous GNOME 3 design. You have to remember that the very first fully integrated desktop on Linux was KDE. And KDE had a very important problem: it was relying on the Qt toolkit which, at the time, was under a non-free license. You could not use Qt in a commercial product without paying Trolltech, the author of Qt. GNOME was born as an attempt by Miguel de Icaza and Federico Mena to create a KDE-like desktop using the free toolkit created for the Gimp image editor: Gtk. This is why I liked to make the joke that the G in GNOME stands for Gtk, that the G in Gtk stands for Gimp, that the G in Gimp stands for GNU and that the G in GNU stands for GNU. This is not accurate as the G in GNOME stands for GNU but this makes the joke funnier. We, free software geeks, like to have fun. Like its KDE counterpart, GNOME 1 was full of knobs and whistles. Everything could be customised to the pixel and to the milliseconds. Jeff Waugh often made fun of it by showing the preferences boxes and asking the audience who wanted to customise a menu animation to the millisecond. GNOME 1 was less polished than KDE and heavier than very simple window managers like Fvwm95 or Fvwm2 (my WM of choice before I started my quest for the perfect desktop). Screenshot from my FVWM2 config which is still featured on fvwm.org, 21 years later https://ploum.net/files/fvwm.jpg With GNOME 2, GNOME introduced its own paradigm and philosophy: GNOME would be different from KDE by being less customisable but more intuitive. GNOME 2 opened a new niche in the Linux world: a fully integrated desktop for those who don’t want to tweak it. KDE was for those wanting to customise everything. The most popular distributions featured KDE: Mandrake, Red Hat, Suse. The RPM world. There was no real GNOME centric distribution. And there was no desktop distribution based on Debian. As Debian was focused on freedom, there was no KDE in Debian. Which explains why GNOME + Debian made a lot of sense in my mind. As Jeff Waugh had been the GNOME release manager for GNOME 2 and was director of the GNOME board, having him as the first Ubuntu community manager set the tone: Ubuntu would be very close to GNOME. And it is exactly what happened. There was a huge overlap between GNOME and Ubuntu enthusiasts. As GNOME 2 would thrive and get better with each release, Ubuntu would follow. But some people were not happy. While some Debian developers had been hired by Canonical to make Ubuntu, some others feared that Ubuntu was a kind of Debian fork that would weaken Debian. Similarly, Red Hat had been investing lot of time and money in GNOME. I’ve never understood why, as Qt was released under the GPL in 2000, making KDE free, but Red Hat wanted to offer both KDE and GNOME. It went as far as tweaking both of them so they would look perfectly identical when used on Red Hat Linux. Red Hat employees were the biggest pool of contributors to GNOME. There was a strong feeling in the atmosphere that Ubuntu was piggybacking on the work of Debian and Red Hat. I didn’t really agree as I thought that Ubuntu was doing a lot of thankless polishing and marketing work. I liked the Ubuntu community and was really impressed by Jeff Waugh. Thanks to him, I entered the GNOME community and started to pay attention to user experience. He was inspiring and full of energy. Drinking a beer with Jeff Waugh and lots of hackers at FOSDEM. I’m the one with the red sweater. https://ploum.net/files/old/fosdem_jdub.jpg Benjamin Mako Hill ================== What I didn’t realise at the time was that Jeff Waugh’s energy was not in infinite supply. Mostly burned out by his dedication, he had to step down and was replaced by Benjamin Mako Hill. That’s, at least, how I remember it. A quick look at Wikipedia told me that Jeff Waugh and Benjamin Mako Hill were, in fact, working in parallel and that Jeff Waugh was not the community manager but an evangelist. It looks like I’ve been wrong all those years. But I choose to stay true to my own experience as I don’t want to write a definitive and exhaustive history. Benjamin Mako Hill was not a GNOME guy. He was a Debian and FSF guy. He was focused on the philosophical aspects of free software. His intellectual influence would prove to have a long-lasting effect on my own work. I remember fondly that he introduced the concept of "anti- features" to describe the fact that developers are sometimes working to do something against their own users. They spend energy to make the product worse. Examples include advertisement in apps or limited-version software. But it is not limited to software: Benjamin Mako Hill took the example of benches designed so you can’t sleep on them, to prevent homeless person to take a nap. It is obviously more work to design a bench that prevents napping. The whole anti-feature concept would be extended and popularised twenty years later by Cory Doctorow under the term "enshitification". Benjamin Mako Hill introduced a code of conduct in the Ubuntu community and made the community very aware of the freedom and philosophical aspects. While I never met him, I admired and still admire Benjamin. I felt that, with him at the helm, the community would always stay true to its ethical value. Bug #1 was the leading beacon: offering choice to users, breaking monopolies. Jono Bacon ========== But the one that would have the greatest influence on the Ubuntu community is probably Jono Bacon who replaced Benjamin Mako Hill. Unlike Jeff Waugh and Benjamin Mako Hill, Jono Bacon had no Debian nor GNOME background. As far as I remember, he was mostly unknown in those communities. But he was committed to communities in general and had very great taste in music. I’m forever grateful for introducing me to Airbourne. With what feels like an immediate effect but probably lasted months or years, the community mood switched from engineering/geek discussions to a cheerful, all-inclusive community. It may look great on the surface but I hated it. The GNOME, Debian and early Ubuntu communities were shared-interest communities. You joined the community because you liked the project. The communities were focused on making the project better. With Jono Bacon, the opposite became true. The community was great and people joined the project because they liked the community, the sense of belonging. Ubuntu felt each day more like a church. The project was seen as less important than the people. Some aspects would not be discussed openly not to hurt the community. I felt every day less and less at home in the Ubuntu community. Decisions about the project were taken behind closed doors by Canonical employees and the community transformed from contributors to unpaid cheerleaders. The project to which I contributed so much was every day further away from Debian, from freedom, from openness and from its technical roots. But people were happy because Jono Bacon was such a good entertainer. Something was about to break… (to be continued) > Subscribe by email or by rss to get the next episodes of "20 years of Linux on the Desktop". > > I’m currently turning this story into a book. I’m looking for an agent or a publisher interested to work with me on this book and on an English translation of "Bikepunk", my new post-apocalyptic-cyclist typewritten novel which sold out in three weeks in France and Belgium.

1 0

20 years of Linux on the Desktop (part 1)
by Ploum.net (English posts only) 20 Oct '24

20 Oct '24

20 YEARS OF LINUX ON THE DESKTOP (PART 1) by Ploum on 2024-10-20 https://ploum.net/2024-10-20-20years-linux-desktop-part1.html Twenty years ago, I had an epiphany: Linux was ready for the desktop. (*audience laughs*) I had been one of those teenagers invited everywhere to "fix" the computer. Neighbours, friends, family. Yes, that kind of nerdy teenager. You probably know what I mean. But I was tired of installing cracked antivirus and cleaning infested Microsoft Windows computers, their RAM full of malware, their CPU slowing to a crawl, with their little power LED begging me to alleviate their suffering. Tired of being an unpaid Microsoft support technician, I offered people to install Linux on their computer, with my full support, or to never talk with me about their computer any more. To my surprise, some accepted the Linux offer. I started to always have two CD-ROMs with me: the latest Knoppix and Debian Woody. I would first launch Knoppix, the first Live CD Linux, make a demonstration to my future victims and, more importantly, save the autogenerated XFree86 config file. I would then install Debian. When X would fail to start after installation, which was a given, I would copy the X config file from Knoppix, install GNOME 2 and OpenOffice from the testing repository and start working on what needed to be done. Like installing and launching ESD by default to allow multiple sounds. Configuring the network which was, most of the time, a USB ADSL modem requiring some proprietary firmware that I would have downloaded beforehand. I would also create some shell scripts for common operations: connect to Internet, mount the USB camera, etc. I put those scripts on the GNOME desktop so people could simply click to launch them. In some cases, I would make a quick Zenity interface. It was a lot of work upfront but, after that, it worked. People were using their computer for months or years without messing or breaking anything. Most of my complains were about running some windows software (like those on CD-ROM founds in cereal boxes). With GNOME 2.0, I felt that Linux was ready for the desktop. It was just really hard to install. And that could be fixed. The Perfect Desktop =================== I had my own public wiki (called the FriWiki) with a few regular contributors. On it, I wrote a long text called: "Debian+GNOME=The Perfect Desktop?". It explained my observations and all the problems that needed to be fixed. As I wanted to improve the situation, I described how the installation should autodetect everything, like Knoppix did. I also suggested to have a LiveCD and an Installation CD that would be totally mirroring each other so you could test then install. In a perfect world, you could install directly from the LiveCD but I didn’t know if it was technically possible. That installation should also offer standard partitions schemes, autodetect and preserve the Windows partition so people would not be afraid of messing their system. Installation was not everything. I suggested that the user created during installation should automatically have root rights. I had learned that two passwords were really too high of a bar for most if not for all people. I don’t remember anyone understanding the "root" concept. Systems with multiple users were too complex to teach so I ended in every case with a single whole family account. The fact that this single account was prevented from doing some stuff on the computer was baffling. Especially for trivial things such as mounting a CD-ROM or a USB key. Speaking of root: installing software could be really more friendly. I imagined a synaptic-like interface which would only display main applications (not all packages) with screenshots, descriptions and reviews. I did some mockups and noted that the hardest parts would probably be the selection and the translation. I’ve lost those mockups but, in my souvenirs, they were incredibly close of what app stores would become years later. I, of course, insisted on installing ESD by default to multiplex sound, to include all the multimedia codecs, lbdvdcss and all possible firmware (called "drivers" at the time) in case hardware is added later. I had pages and pages of detailed analysis of every single aspect I wanted to be improved to make Linux ready for the desktop. With 2.0, GNOME switched to a bi-yearly release. Every six months, a new GNOME desktop would be released, no matter what. I thought it would be a nice idea to have the underlying OS released just after, to be kept in sync. But every six months was probably a bit too much work and people I knew would not upgrade as often anyway. So I advocated for a yearly release where the version number would be the full year. This would greatly help people to understand what version they were running. Like in "I’m running Linux Desktop 2003". UserLinux ========= When you have a good idea, it’s probably because this idea is already in the zeitgeist of the time. I don’t believe in "ownership" or even "stealing" when it’s about ideas. Bruce Perens himself was thinking about the subject. He decided to launch UserLinux, an initiative that had the goal of doing exactly what I had in mind. I immediately joined the project and started to be a very vocal member, always referring to my "Perfect Desktop" essay. I wanted UserLinux to succeed. If Bruce Perens was behind it, it could not not succeed, right? A mockup of the UserLinux desktop (GNOME 2.0 with a custom theme) https://ploum.net/files/userlinux.jpg Unfortunately, most of UserLinux people were, like me, talking a lot but not doing much. The only active member was an artist who designed a logo and started to create multiple GNOME themes. It was great. And lots of discussions about how to make the theme even better ensued. This is how I learned about "bike shedding". UserLinux was the ultimate bikeshedded project. To my knowledge, no code was ever written. In fact, it was not even clear what code should be written at all. After launching the initial idea, Bruce Perens was mostly discussing with us, everybody waiting for someone to "do something". No-name-yet =========== At the start of 2004, I was contacted by Sébastien Bacher, a Debian developer who told me that he had read my "Perfect Desktop" essay months ago and forwarded it to someone who had very similar ideas. And lots of money. So much money that they were already secretly working on it and, now that it was starting to take shape, they were interested in my feedback about the very alpha version. I, of course, agreed and was excited. This is how I joined a mysterious project called "no-name-yet" with a nonameyet.com website and an IRC channel. While discussing about the project and learning it in great depth, my greatest fear was that it would become a fork of Debian. I felt strongly that one should not fork Debian lightly. Instead, it should be more a few packages and metapackages that would sit on top of Debian. Multiple people in the team assured me that the goal was to cooperate with Debian, not to fork it. At one point, I strongly argued with someone on IRC whose nick was "sabdfl". Someone else asked me in private if I knew who it was. I didn’t. That’s how I learned that the project was funded by Mark Shuttleworth himself. Dreaming of being an astronaut, I was a huge fan of Mark Shuttleworth. The guy was an astronaut but was also a free software supporter. I knew him from the days when he tried to offer bounties to improve free software like Thunderbird. Without much success. But I was surprised to learn that Mark had also been a Debian developer. This guy was my hero (and still kinda is). He represented all of my dreams: an astronaut, a debian developer and a billionaire (in my order of importance). Years later, I would meet him once in the hall of an Ubuntu Summit. He was typing on his laptop, looked at me and I could not say anything other than "Hello". And that was it. But I’m proud to say that his hackergothi on planet.ubuntu.com is still the one I designed for him as a way to celebrate his space flight. sabdfl’s hackergotchi, designed by yours, truly https://ploum.net/files/sabdfl.png During the spring or early summer of 2004, I received a link to the very first alpha version of no-name-yet. Which, suddenly, had a real name. And I liked it: Ubuntu. I installed Ubuntu on a partition to test. Quickly, I found myself using it daily, forgetting about my Debian partition. It was brown. Very brown at first. A bit later, it even got naked people on the login screen (and I defended sabdfl for this controversial decision). Instead of studying for my exams, I started to do lengthy reports about what could be improved, about bugs I found, etc. The first Ubuntu login picture with three half-naked people looking toward the sky. Some alpha versions were with even fewer clothes. https://ploum.net/files/old/login.png This makes me one of the very few people on earth who started to use Ubuntu with 4.04 (it was not named like that, of course). Wanting to promote Ubuntu and inspired by Tristan Nitot, I decided to start a blog. A blog which, coincidentally, was started the very same day the first public Ubuntu was released, exactly twenty years ago. A blog you are reading right now. And this was just the beginning… (to be continued) > Subscribe by email or by rss to get the next episodes of "20 years of Linux on the Desktop". > > I’m currently turning this story into a book. I’m looking for an agent or a publisher interested to work with me on this book and on an English translation of "Bikepunk", my new post-apocalyptic-cyclist typewritten novel.

1 0

On Open Source and the Sustainability of the Commons
by Ploum.net (English posts only) 01 Jul '24

01 Jul '24

ON OPEN SOURCE AND THE SUSTAINABILITY OF THE COMMONS by Ploum on 2024-07-01 https://ploum.net/2024-07-01-opensource_sustainability.html TL;DR: put your open source code under the AGPL license. Much have been said about the need to pay Open Source developers for their work and the fact that huge corporations use open source software without contributing back. Most articles I’ve been reading on the subject completely miss the mark. Plenty of commentators try to reinvent some kind of "free software but with forced contributions" or "free software but non-commercial". Those are naive and wrong. If you impose limitations, it’s, by definition, not free software anymore. The problem is not about Open Source or Free Software. The problem is everything else. Open Source utopia, as envisioned until the first decade of this millennium, was to create a huge, powerful stack of open-source software that would serve as the foundations of any human endeavour. Including building businesses or, for some, proprietary products. Free Software would be part of the commons, a huge natural pool of resources. Every business would be small in comparison. Just like we allowed private companies to sell water (a common good) thinking the companies would be small compared to the nearly infinite supply of water. We were naive. What we got is more or less the opposite: huge monopolistic corporations and lots of small fragmented free software pieces that connect them. Bottled soda factories pumping so much water that whole populations start to suffer from the lack of fresh water and, as a consequence, being forced to buy bottled water. Technically, Open Source won. Politically, it lost. The reason is simple: it was easier to build consensus around technical solutions, washing away political implications that were seen as out of scope or too hard to agree. Every megacorporation is now built on top of free software. But they managed to make it effectively proprietary by hiding their code behind web interfaces. When publicly distributed, the open-source code is hidden behind layers of indirection bypassing any packaging/integration effort, relying instead on virtualisation and downloading dependencies on the fly. Thanks to those strategies, corporations could benefit from open source code without any consequence. The open source code is, anyway, mostly hosted and developed on proprietary platforms. Even hardcore free software geeks now use some dependencies/plugins mechanisms that are hardcoded to only look at Github. Through nested dependencies, millions of people are running code directly downloaded from Github without even realising it. We need to talk about your Github addiction (ploum.net) https://ploum.net/2023-02-22-leaving-github.html Due to the original open-source utopia paradigm, every time a developer push free code on Github, she feels like she’s contributing to the commons. But, effectively, she’s pushing code into production in hundreds of exploitive corporate projects. When a problem occurs, per corporate tradition, pressure and blame fall on the maintainer. Even if that maintainer is not on the payroll. Paying the Maintainer Makes the Problem Worse ============================================= That will be an extremely unpopular opinion but I’m convinced that paying the contributor/maintainer a dime is not the solution. It worsen the situation. It acknowledges the responsibility of the aforementioned maintainer and legitimises the exploitation. We need to remember that most (if not all) free software is provided, "without liability". That rule should be enforced. We should not care about corporations. If there was no support contract prior hand, let them burn. Trying to force corporations to pay the maintainer is like trying to force landlords to pay firefighters only if their house is burning. Or agreeing that a factory should give a small tip to volunteers cleaning the river it is polluting. Paid and unpaid open source developers are pressed into providing a support they never promised in the first time. So they ask companies for mandatory contributions, something they explicitly refused when they licensed their code. So, what can we do? In the short term, it’s very simple. If you care about the commons, you should put your work under a strong copyleft license like the AGPL. That way, we will get back to building that commons we lost because of web services. If someone ever complains that a web service broke because of your AGPL code, reply that the whole web service should be under the AGPL too. We were tricked into thinking that BSD or MIT licences were "freer" like we were tricked into believing that building a polluting factory next to our local river would be "good for the economy". It is a scam. A lot of unpaid or badly paid developers would probably benefit from switching to a copyleft license but they use BSD/MIT because they see themselves are "temporary embarrassed software millionaires". We should also actively fight against automatic installation of recursive dependencies. No, it is not normal and no sanely engineered system should do this. We should not trust the Microsoft-owned Github to distribute software. A git repository is a development tool, not a distribution mechanism for end users. Something the Great Ancients understood fully when they started projects like BSD, Debian or Red Hat which are called… "distributions". Yes, the "D" in BSD stand for "distribution". It is not by accident that those distributions care a lot about the license of the software they distribute. Get Rid of Monopolies ===================== In the long term, the root causes of most of our problems are the monopolistic corporations. Without them, we would not have this discussion. There’s a generational divide here. Brilliant coders now on the market or in the free software space have never known a world without Google, Facebook and Github. Their definition of software is "something running in the browser". Even email is, for them, a synonym for the proprietary messaging system called "Gmail" or "Outlook". They contribute to FLOSS on Github while chatting on Slack or Discord, sharing specifications on Google Drive and advertising their project on Twitter/X. They also often have an iPhone and a Mac because "shiny". They cannot imagine an alternative world where monopolies would not be everywhere. They feel that having nice Github and Linkedin profiles where they work for free is the only hope they have to escape unemployment. Who can blame them? They cannot imagine a world without monopolies. They don’t search, they Google, they don’t shop online, they go on Amazon, they don’t read a book but a Kindle, they don’t take a coffee but a Starbucks. For them, politics is only a source of conflicts, a naughty word. As they start to understand that they are exploited by those omnipotent deities, they see only one way to make it acceptable: ask, through one of those deities (Twitter, Facebook, LinkedIn), to be paid. They understand that they are two classes of coders in the world: those who are exploited without being paid and those who are paid to be exploited. A bit or even more in some cases. While a few hands keep all the power. What elderly, like myself, should teach them, is that there are many alternatives. We can live without Google, Facebook Microsoft, Apple, Amazon. We can write code which is not on Github, which doesn’t run on an Amazon server and which is not displayed in a Google browser. We should also insist that every piece of technology is, by essence, political. That you cannot understand technology without understanding the people. And you cannot understand people without understanding politics. Every choice you made has an impact on the world. At the turn of the century, the free software community was focused on fighting Microsoft monopoly. We even joined force with Google and Apple to fight Microsoft. We completely failed. We helped build a world where mostly everything is "Microsofted", "Googled" and "Iphonized". All of this made possible thanks to open source and millions of hours worked for free by people who contributed to what we thought was "the commons". The lesson we learned is harsh: we can never trust corporations with anything. They destroyed our oceans, our atmosphere and our politics. There’s no reason to trust them with our software, our privacy and our daily lives. In the long term, our only hope is to build stronger commons. Every day, we must fight to protect and improve the commons while letting corporations have as little power as we can over it and over our lives. If you are a creator or a coder, you can do it today by adopting copyleft licenses and enforcing them as much as you can. Put your open source code under the AGPL license! Photo by Nick Karvounis https://unsplash.com/fr/photos/man-cleaning-shoe-of-another-man-near-white-…

1 0

List check. Please disregard
by Ploum.net (English posts only) 09 Apr '24

09 Apr '24

List check for en(a)listes.ploum.net Please disregard this test message.

1 0

About Freedom and Power
by Ploum.net (English posts only) 08 Apr '24

08 Apr '24

ABOUT FREEDOM AND POWER by Ploum on 2024-04-08 https://ploum.net/2024-04-08-freedom-power.html Freedom is the right to do whatever you want. Power is the right to force others to do what you want. Power is, by definition, being able to restrict others’ freedoms. Copyleft is a tool that gives you freedom but no power. Permissive licenses give freedom and power, allowing already powerful people to restrict the freedoms of others. That’s why powerful people (and those dreaming of being powerful) don’t like copyleft. When you are accustomed to the privilege of power, freedom of others sounds like oppression. Don’t listen to the powerful people. They will tell you that you need to protect powers just in case you become powerful yourself. They will tell you that you need to be against taxation just in case you become rich yourself. That you are a "temporary embarrassed millionaire". Similarly, they’ve told you to use MIT/BSD license because you could later become a "billionaire proprietary software tycoon" with your lines of code. That’s, of course, a lie. They already are the barons. They want to use your own lines of code to restrict your own freedoms. We should not admire powerful people but fight them. You may dream of power but all you need is freedom. We need to protect freedom, not power. We need to respect humans, not bosses nor commercial interests. Offer a little freedom : use copyleft licenses !

1 0

A Society That Lost Focus
by Ploum.net (English posts only) 18 Mar '24

18 Mar '24

A SOCIETY THAT LOST FOCUS by Ploum on 2024-03-18 https://ploum.net/2024-03-18-lost-focus.html Our Mind, the Bottleneck ======================== In the early 90s, after tweaking my MS-DOS computer, I was able to play games. One of those game was called "Battle Chess". A Chess game were pieces were really fighting against each other. It was fun. I was, and still am, a mediocre chess player. I was mate in less than 10 or 15 turns at the easiest level. For the sake of the experiment, I turned the difficulty to the harder level and started playing. Something strange happened: I was still losing but it took a lot more turns. I was able to protect my game, even to manage a few draws. Was it a bug in the game? Even as a young teenager, I quickly understood the reason. With the setting set to "hard", the game would try a lot harder to find a good move. On my 386 processor, without the mathematical coprocessor, this would take time. Several seconds or even one minute by turn. During that time, I was thinking, anticipating. With the easiest setting, computer moves would happen immediately. I knew I had all the time I want but I was compelled to move fast. I could not take the time while the other side was immediately reacting to my moves. The world we are living in is that same chess game on the easiest setting. Everything happens immediately, all the time. White-collar work can now be summarised as trying to reply as fast as possible to every single email until calling it a day and starting again in the morning, a process which essentially prevents any deep thinking, as pointed by Cal Newport in his book "A world without email". As we don’t have the time to think anymore, we masquerade our lack of ideas with behavioural tricks. We replaced documents with PowerPoints because it allowed lack of structure and emptiness to look professional (just copy paste the data of the last PowerPoint you received in a text file and see by yourself how pitiful it is. PowerPoint communications at NASA were even diagnosed by Edward R. Tufte, author of the "The cognitive style of PowerPoint", as one of the causes that led to Space Shuttle Columbia’s disaster). The root problem is that, for the first time in human history, our brain is the bottleneck. For all history, transmitting information was slow. Brains were fasts. After sending a letter, we had days or months to think before receiving an answer. Erasmus wrote his famous "Éloge de la folie" in several days while travelling in Europe. He would never have done it in a couple of hours in a plane while the small screen in the backseat would show him advertisements. In 2012, the French writer Thierry Crouzet had one of the first recorded "online burnout". Being connected all the time with interesting strangers and interesting ideas to which he wanted to reply quickly was too much for his brain. One night, he had a strong panic attack and decided to spend six months without the Internet, an experience he told in his book "J’ai débranché". The Oversold Internet ===================== The instant feedback of permanent connectivity is clearly a bad thing. But the worse had yet to come. After the 2000s bubble popped and told us that Internet was not "magic money", the question became "how do we monetise the Internet?" A few idealistic geeks replied, "You don’t monetise it, it’s a non-commercial world." But geeks, as everyone, wanted or needed to be paid. To earn money, they handled the reins of the whole new world they were creating to marketers. That’s it: hackers sold the Internet in exchange of a salary. Until 2000, marketers played along with the idea of selling the work hackers were doing. With one small problem: they oversold it completely, diving in the geek fantasy that, soon, everybody would be on that Internet buying stuff online. In the 2000s, nobody but geeks wanted to spend their life behind a huge radiating screen. Marketers suddenly waked up to that reality with the dot-com bubble. If not everybody wanted to be on the Internet and nobody would buy anything on the Internet, there were two potential solutions: either monetising the fact that some people were already spending lots of time of the Internet or convincing more people to come on the Internet. Surviving companies such as Google decided for the easiest one: monetising what people were already giving to the Internet: their time and attention. Advertising was, of course, already part of the web (mostly through the infamous "popups") but Google innovated by inventing a whole new way of exploiting attention: trying to learn as much as possible about users to show them the advertising they are more likely to click on. The whole story is told in great details in the book "Surveillance Capitalism", by Soshanna Zuboff. Whether this "personalised advertisement" really work better than traditional one is up to debate. For Tim Hang, author of "Subtime Attention Crisis" and for Cory Doctorow, author of "How to destroy surveillance capitalism", the real impact on sales is negligible but as marketers think it works, they invest massive money in it, making the whole technology a very lucrative bubble. But the real impact is undisputed : as long as someone buys it, it is really lucrative to sell the attention and all the information you could from consumers. As a consequence, the practice has been generalised and nearly every website, every app on the Internet is trying to get both. And they are very scientific about the process. We forgot how not to spy and steal attention ============================================ It is now considered as "normal practice" to try to get the attention and the data of your users, even if it doesn’t make sense from a business perspective. Banking apps send notifications to show you their new shiny logo, good old e-commerce website ask their customers for the number of children they have or their income bracket. Even non-commercial personal blogs or some websites dedicated to privacy contain analytics software to track their users. Not tracking your users is harder than not! Every single vendor from which you shop, even a brick-and-mortar one, will bury you with their mailings. One could assume that buying a new mattress is something you do only every decade and that the prospective market for mattress vendors is those who didn’t buy a mattress in the last five years. So why did anybody think that, right after buying a mattress, I would be interested in receiving news about mattresses every single week of my life? The two consequences of all this are that our privacy is invaded as much as it is technologically possible and that our attention is scientifically captured as much as it is technologically possible. And, in both aspects, technology is "improving" as all the smartest minds in the world are hired to do just that. While working at Google, Tristan Harris realised how much what they were building was in order to get the focus and the attention of people. He left Google to create the "Center for Humane Technology" that tries to raise attention about the fact that… our attention is captured by monopolist technologies. The irony is palpable: Tristan Harris had a very good intuition but can’t imagine doing anything else than either "raising attention" through social networks or building technologies that would notify you that you should be focused. Let’s build yet another layer of complexity above everything else and raise attention so this layer is adopted widely enough to become the foundation of the next complexity paradigm. Worshipping Shallow Ideas ========================= Being distracted all the time prevent us from having any ideas and understanding. We need a catchy slogan. Instead of reading a three-page report, we prefer a 60 slides PowerPoint, containing mostly stock pictures and out-of-context charts. We have valorised the heroic image of the CEO that comes in a meeting and tell engineers, "I have ten minutes left before my next meeting. Tell me everything in five and I’ll take a billion dollar decisions." In retrospect, it is obvious that taking good decisions in that context is nothing more than rolling a dice. Funnily enough, it has been proved multiple times than every high-profile CEO is not better than a random decision algorithm. But, unlike algorithms, CEOs usually have charisma and assurance. They may take a very wrong decision but they can convince everybody that it’s the right one. Which is exactly the definition of a salesman job. In "Deep Work", Cal Newport tries to promote the opposite stance, the art of taking the time to think, to ponder. In "The Ideas Industry", Daniel Drezner observes that long, subtle and complex ideas are more and more replaced by simplistic slogans, the epitome being the famous TED conferences. In 18 minutes, people are sold an idea and, if the speaker is a good salesman, feel like they’ve learned something deep and new. The mere fact that you could learn something deeply enough in 18 minutes is an insult to all the academic world. Without surprise, the same academic world is seen by many as boring old people spending their time writing long articles instead of making a catchy slogan to change the world. Succumbing to Our Addictions ============================ Most monopolies were built by removing choices. You could not buy a computer without Microsoft Windows. You could not visit some websites without Internet Explorer. You can’t find a phone without Google in a shop (Google pay many billions dollars every year to be the default search engine on Apple devices). And if you manage to remove Google from your phone, you will lose the ability to run some apps, including most banking apps. Most apps even check at start if Google services are installed on the phone and refuse to start if it’s not the case. If it’s really hard not to use Google, it’s by definition a forced monopoly. Similarly, it is very hard to avoid Amazon when shopping online. There’s one exception : Facebook. There’s nothing forcing us to go to Facebook or Instagram. There’s nothing forcing us to spend time on it. It’s like we have choice. But it seems we haven’t. Why is this? Why are we playing one hour of what was supposed to be five minutes of a stupid smartphone game instead of reading a book? Why are we spending every minute awake checking our smartphone and replying to mundane chitchat, even if we are in the middle of the conversation with someone else? Why are we compelled to put our life and the lives of our children at risk just to quickly reply while driving? Because of the way the human brain is wired. Evolutionary speaking, we are craving for new experiences. Learning new experiences, good or bad, may help your chromosomes to survive more generations than others. We get that famous "dopamine rush", described in great details by Liberman and Long in "The molecule of more". Each time there’s a notification, each time there’s a red bubble in some part of the screen, the brain acts like it’s a new vital opportunity. We can’t miss it. A study showed that the sole notification sound was enough to distract a driver as much as if he was texting while driving. Yes, even without looking at your phone, you were distracted as much as if you did (which is not an excuse to look at it). The brain has learned that the phone is a random provider of "new experiences". Even in airplane mode, it was demonstrated that having the phone on your desk or in your bag degrades heavily your attention and your thinking performance. Performance went back to normal only when the phone was put in another room. Fighting to Get Our Focus Back ============================== That’s it, the only way to not have any temptation is not to have the phone at arm reach. The aforementioned French writer Thierry Crouzet told me once that it was very difficult to focus on writing when you know you only have to move the word processor window with the mouse to go to the Internet. On the web, writers’ forums are full of discussions about "distraction-less" devices. Some, including your servitor, are going back to old typewriters, a paradigm described as a true resistance by Richard Polt in the excellent book "The Typewriter Revolution". One may even wonder if the epidemic of "electro-sensitivity", feeling bad or being sick when exposed to wifi or similar wireless emissions, may simply be a psychological reaction to the overstimulation. It has been observed that the symptoms are real (people are really feeling bad and are not simulating) but that, in double-blind controlled environment, the symptoms are linked to the belief of wireless emissions (if you simulate a blinking wireless router without emitting anything, people feel bad. If you have wireless emission but tell people it’s disabled, they will feel better). In his landmark book "Digital Minimalism", Cal Newport offers a framework to rethink the way we use digital technologies. The central idea is to balance costs and benefits consciously, highlighting most hidden costs. Facebook might be free in the sense you don’t have to pay for it. But being exposed to advertising, being exposed to angry political rants, feeling compelled to answer, being exposed to picture of people you once knew and who seems to have an extraordinary (even if virtual) life is a very high cost. Simply do the math. If you have 180 friends on Facebook, which seems to be a low amount those days, if your friends take, on average, 10 days of vacation per year, you will have, on average, five friends on vacation every day. Add to this statistic that some people like to re-post pictures of old vacations and it means that you will be bombarded daily by pictures of sunny beaches and beautiful landscapes while you are waiting under neon light for your next boring meeting in a gray office. By design, Facebook makes you feel miserable. That’s not to say that Facebook cannot be useful and have benefits. As Cal Newport highlight, you need to adapt your use to maximise the benefits while trying to avoid costs as much as possible. You have to think consciously about what you really want to achieve. This idea of digital minimalism prompted a revival of the so-called "dumb phones", phones which are not smart and which are able to make phone call and send/receive SMS. Some brands are even starting to innovate in that particular market like Mudita and Lightphone. Ironically, they are advertising mindfulness and being focused. They are trying to catch your attention to sell you back… your own attention. Focus Against Consumerism ========================= One of the consumerist credo is that the market will fix everything. If there’s a problem, someone will quickly sell a solution. As pointed by Evgeny Morozov in "To Save Everything, Click Here", this is not only wrong thinking. This is actually harmful. With public money, we are actually actively funding companies and startups thinking they will both create jobs and sell solutions to every problem. It is implied that every solution should be a technological one, should be sellable and should be intuitive. That’s it: you should not think too much about a problem but instead build blindly whatever solution comes to mind using the currently trending technological stack. French Author Antoine Gouritin wrote a funny and interesting book about that whole philosophy he called "Le Startupisme". The root cause is there: we don’t have any mental framework left other than spying on people and steal their attention. Business schools are teaching how to do catchy PowerPoints while stealing attention from people. Every business is at war with the other to catch your attention and your brain cycles. Even academy is now fighting to get grants based on catchy PowerPoints and raw number of publications. This was the raw observation of David Graeber: even academics have stopped thinking to play the "catch your attention game". There’s no silver bullet. There will not be any technological solution. If we want to claim back our focus and our brain cycles, we will need to walkaway and normalise disconnected times. To recognise and share the work of those who are not seeking attention at all cost, who don’t have catchy slogans nor spectacular conclusions. We need to start to appreciate harder works which don’t offer us immediate short-term profit. Our mind, not the technology, is the bottleneck. We need to care about our minds. To dedicate time to think slowly and deeply. We need to bring back Sapiens in Home Sapiens Sapiens. Picture by Trougnouf https://commons.wikimedia.org/wiki/File:View_through_a_broken_window_from_a…

1 0

Announcing Offpunk 2.0
by Ploum.net (English posts only) 25 Nov '23

25 Nov '23

ANNOUNCING OFFPUNK 2.0 by Ploum on 2023-11-25 https://ploum.net/2023-11-25-offpunk2.html I’m happy to announce the release, last week, of Offpunk 2.0. Offpunk is an offline-first command-line browser/RSS reader. You control it by typing command and it maintains a cache of all the networked resources to allow you to access them offline indefinitely. If a non-cached resource is tentatively accessed, the URL is marked as to be fetched later. Running periodically "offpunk --sync" will fetch those resources and add them to your "tour" to remind you that you wanted to access it. Offpunk official website https://sr.ht/~lioploum/offpunk/ Offpunk 2.0 changelog https://git.sr.ht/~lioploum/offpunk/refs/v2.0 List of available offpunk packages https://repology.org/project/offpunk/versions Screenshot ========== Mandatory screenshot showing Offpunk browsing Offpunk’s website. There’s a screenshot of Offpunk in the screenshot. https://ploum.net/files/offpunk2.png Switching the license to AGPLv3 =============================== Offpunk originally started as a branch then a friendly fork of AV-98. It was called AV-98-offline and, as such, shared the same BSD license. AV-98, the first Gemini browser https://tildegit.org/solderpunk/AV-98 During multiple discussions, Solderpunk and I came to the conclusion that AV-98-offline was becoming too different from the initial goal of AV-98. It was thus renamed Offpunk. At the same time, I grew increasingly convinced that we needed more copyleft software and that the AGPL license was better suited to protect the commons. "We need more of Richard Stallman, not less", my take on why copyleft is important https://ploum.net/2023-06-19-more-rms.html As a symbolic move, I’ve thus decided to switch Offpunk license from BSD to AGPLv3 but needed an opportunity to do so. The 2.0 release is such an opportunity. Multiple independent tools ========================== Like AV-98, Offpunk was one single big python file. I liked the simplicity of it. But it really became a mess and I wanted to offer Offpunk’s features as separate command-line tool. With Offpunk 2.0, you will thus have three new command-line tools: - netcache : when given a URL, will download and cache this URL or only access the cache if the "--offline" option is provided. - ansicat : will render an HTML, an RSS, a Gemtext or even a picture in your terminal, with various options. - opnk : universal opener. Will try to render any file or any URL in your terminal. If it fails, it will fallback to xdg-open. Those three commands should come with a man page and a "--help" but they are still quite new. To my own surprise, I found myself using "opnk" all the time. I don’t think anymore about how to handle a file, I simply give it to opnk. Packaging those tools was a lot harder than expected and I want to thank all the contributors to this work, including Austreelis, David Zaslavsky and Jean Abou Samra. Themes ====== The goal of Offpunk, through Ansicat, is to render web, RSS, gemini and gopher pages as coloured ANSI text in your terminal. Until now, those colours were hardcoded. With 2.0, they can be customised. See "help theme". Screenshot of Offpunk customised with the worst possible colours I could find. https://ploum.net/files/offpunk2_theme.png In offpunk, customisation can be made permanent by adding all the commands you want to run at startup in your .config/offpunk/offpunkrc file. Mine contains one single line: "offline", ensuring I use Offpunk only in offline mode. Getting started =============== Using Offpunk daily as your main browsing/rss driver takes some learning. You need to get used to the Offpunk philosophy: adding elements to tour instead of clicking them, creating lists to read later, doing a daily synchronisation. It is not trivial. The "help" command will probably be your best allies. The community also provide support on a user dedicated mailing-list. Offpunk-users mailing list https://lists.sr.ht/~lioploum/offpunk-users If Offpunk becomes useful to you, the community is open. Contributions, documentation, blog post about how you use Offpunk, help to new users and packaging are warmly welcome. Sometimes, simple feedback is all it takes to make a developer happy. So don’t hesitate to contribute in one of our lists. Offpunk-devel mailing list https://lists.sr.ht/~lioploum/offpunk-devel Offpunk-packagers mailing list https://lists.sr.ht/~lioploum/offpunk-packagers I’ve also started an experimental Matrix room on #offpunk:matrix.org. I have the belief that mailing-list is better suited for discussions but I’m giving this the benefit of doubt and willing to explore whether or not direct real-time discussion could help new users. Join the #offpunk:matrix.org room https://matrix.to/#/#offpunk:matrix.org

1 0

The gift of time
by Ploum.net (English posts only) 10 Nov '23

10 Nov '23

THE GIFT OF TIME by Ploum on 2023-11-10 https://ploum.net/2023-11-10-the-gift-of-time.html Maintaining a free software project is spending years of your life to solve a problem that would have taken several hours or even days without the software. Which is, joke aside, an incredible contribution to the common good. The time saved is multiplied by the number of users and quickly compound. They are saving time without the need to exchange their own time. Free software offers free time, free life extension to many human living now and maybe in the future. Instead of contributing to the economy, free software developers contribute to humanity. To the global progress. Free software is about making our short lifetimes a common good instead of an economical product.

1 0

The future of Offpunk: UNIX command-line heaven and packaging hell
by Ploum.net (English posts only) 30 Sep '23

30 Sep '23

THE FUTURE OF OFFPUNK: UNIX COMMAND-LINE HEAVEN AND PACKAGING HELL by Ploum on 2023-10-01 https://ploum.net/2023-10-01-future-of-offpunk-packaging-hell.html > A story about how the UNIX philosophy made me develop tools I’m actually proud of and why packaging is holding me back. Two years ago, I decided that I wanted to be able to browse Gemini while offline. I started to add a permanent cache to Solderpunk’s AV-98, the simplest and first Gemini browser ever. It went surprisingly well. Then, as the excellent forlater.email service went down for a week, I thought that I would add a quick and hackish HTTP support to it. Just a temporary experiment. The same week, I serendipitously stumbled upon chafa, an image rendering tool which was on my computer because of neofetch. I thought it would be funny to have pictures rendered in webpages in my terminal. Just an experiment to take some funny screenshots, nothing more. But something really surprising happened: it was working. It was really useful. I was really using it and, after adding support for RSS, I realised that this experiment was actually working better for me than forlater.email and newsboat. Offpunk was born without really thinking about it and became a real project with its own philosophy. Offpunk, a command line to browse Web, Gemini and Gopher while offline https://sr.ht/~lioploum/offpunk/ Born on Gemini, I wanted Offpunk to keep its minimalistic roots: keeping dependencies under control (making them optional and implementing the underlying feature myself as soon as it makes sense), keeping it simple (one single runnable python script), caring as much as possible about older versions of python, listening to people using it on very minimal systems. I also consciously choose to use only solutions that have been time-trial-tested. I’ve spent too many years of my life falling for the "new-trendy-technology" and learned from those mistakes. The one-file aspect assured that it was really easy to use and to hack on it: open the file, modify something, run it. I’m not a good developer. Anything more complex than that is too much for my taste. Unless forced, I’ve never used an IDE, never understood complex toolchains nor packaging. I modify files with (neo)vim (without any plugin), compile from the command line and run the resulting binary (not even needing the second step with python). Life is too short for making it more complex than that. I like to play with the code, not to learn tools that would do it for me. But offpunk.py was becoming a bit fat. 4500 lines of organic python which have grown over an AV-98 structured to be a test bed for an experimental protocol. The number of people able to understand its code entanglement was varying between 0 and 1, depending on the quality of my morning Earl Grey. I wanted to make life easier for contributors. I also realised that some features I developed might be useful without offpunk. So I stepped into a huge refactorisation and managed to split offpunk into several components. My goal was to separate the code into multiple individual components doing one thing and doing it well. And, to my own surprise, I succeeded. Netcache.py =========== I called the first component "netcache". Think of netcache as a cached version of wget. If possible, netcache will give you a cached version of the URL you are asking. If no cache or too old and if allowed to go online, netcache will download it. It means that if you like Offpunk’s core concept but don’t like the interface and want, for example, a GUI, you could write your own browser that would, using netcache, share the cache with Offpunk. Netcache is currently working just well enough for my needs but could be a lot better. I should, for example, investigate replacing the network code by libcurl and implementing support for multithreaded concurrent downloads. Ansicat.py ========== Coloured output in your terminal is done through a standard called ANSI. As I wrote the first HTML to ANSI renderer for offpunk, I started to understand how awful the HTML standard was. Armed with that experience, I started a second renderer and, to be honest, it is actually not that bad. I’m even proud of it. Ansicat is really useful when in a terminal because it will render HTML and gemtext in a good, readable way. If the optional library python- readability is present, ansicat will try to extract the main content from a web page (and, yes, python-readability is one dependency I would like to reimplement someday). With netcache and ansicat, you can thus already do something like: netcache https://ploum.net | ansicat --format=html Yes, it works. And yes, as a UNIX junkie, I was completely excited the first time it worked. Look mum, I’m Ken Thompson! Making ansicat a separate tool made me think about adding support for other formats. Like PDF or office documents. How cool would it be to have a singe cat command for so many different formats? Opnk.py ======= While netcache and ansicat were clear components I wanted to split from Offpunk’s core since the start of the refactoring, another tool appeared spontaneously: opnk. Opnk (Open-like-a-punk) is basically a wrapper that will run ansicat on any file given. If given a URL, it will ask netcache for the file. Result will be displayed in less (after passing through ansicat, of course). If ansicat cannot open the file, opnk fallbacks on xdg-open. That looks like nothing but it proved to be massively useful in my workflow. I already use opnk every day. Each time I want to open a file, I don’t think about the command, I type "opnk". It even replaced cat for many use cases. I’m even considering renaming it "opn" to save one character. Using opnk also explains why I want to work on supporting PDF/office documents with ansicat. That would be one less opportunity to leave the terminal. Offpunk.py ========== Through this architecture, Offpunk became basically an interface above opnk. And this proved to work well. Many longstanding bugs were fixed, performance and usability were vastly improved. Everything went so well that I dreamed releasing offpunk 2.0, netcache, ansicat and opnk while running naked with talking animals in a flower field under a rainbow. Was it really Earl Grey in the cup that day? Packaging Offpunk.py ==================== Now for the bad news. As expected, the refactoring forced me to break my "one-single-python- file" rule. I felt guilty for those people who told me about using offpunk on very minimal systems, sometimes from a USB key. But I thought that this was not a real problem. Instead of one python script, I had four of them (and a fifth file containing some shared code). That should not be that much of a problem, isn’t it? Well, python packaging systems would like to disagree. Flowers fade, the rainbow disappears behind black and heavy clouds while animals start to look at me with a devilish look and surprisingly sharp teeth. I’ve spent many hours, asked several people on the best way to package multiple python files without making the whole thing a module. Without success. Hopefully, the community is really helpful. David Zaslavsky stepped on the mailing list to give lots of advice and, as I was discouraged, Austreelis started to work really hard to make offpunk both usable directly and packagable. I’m really grateful for their help and their work. But, so far, without clear success. I feel sad about the amount of energy required to address something as simple as "I’ve 5 python files which depend on each other and I want to be able to launch them separately". Austreelis’s branch where she works on making offpunk "packageable". https://gitlab.com/austreelis/offpunk.git The software is working really well. The refactoring allowed me to fix longstanding bugs and to improve a lot of areas while adding new features (colour themes anyone?) On my computer, I added four aliases in my zsh config: offpunk, opnk, ansicat and netcache. Each alias runs the corresponding python file. Nothing fancy and I want to keep it that way. I know for a fact that several users are doing something similar: git clone then run it from an arbitrary location. Keeping things as simple as that is the main philosophical goal behind offpunk. It’s an essential part of the project. If people want to use pip or any other tool to mess up their computer configuration, that’s their choice. But it should never be required. Which means that I’m now in a very frustrating position: Offpunk 2.0 is more than ready from a code point of view. But it cannot be shipped because there’s currently no easy way to package it. The pyproject.toml file had become an obstacle to the whole development process. I’m contemplating putting everything back in one big file. Or removing the pyprojects.toml file from the repository and releasing offpunk "as it is". Some will call me an old conservative fart for refusing to use one of those gazillion shiny packaging system. Others will judge me as a pretty poor programmer if I managed to do 20 years of Python without ever understanding pip nor using an IDE. They are probably right. What would you seriously expect from someone doing a command-line tool to browse Gemini and Gopher? But there’s maybe an easier solution than to change my mind and offpunk’s core philosophy. A simple solution that I missed. If that’s the case, don’t hesitate to drop a word on the devel mailing-list, Austreelis and I will be happy to hear about your opinion and your experience. offpunk-devel mailing list https://lists.sr.ht/~lioploum/offpunk-devel While you are at it, bug reports and feedback are also welcome. I’ve this odd custom of finding embarrassing bugs only hours after a release. I really hope to do better with offpunk 2.0. And after we’ve solved that little packaging anecdote together, I will happily return to my bare neovim to code all the ideas I want to implement for 2.1, 2.2 and many more releases to come.

1 0