Chaos Computer Club - archive feed

Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. Org mode is an extension to the Emacs text editor. The talk will introduce a trusted system to manage your daily life and keep track of all the stuff that matters to you. The mein difference to other personal productivity apps is: - **You** have control over your files. - Files are in plain text, you can even read them without org mode. - The application is Open Source, so no risk that is discontinued because the business plan didnt work. - The user can customize it for his own needs and is not forced to adapt to the needs of a tool. **About me:** Software Engineer, 25+ years on Linux, using Org mode daily for at least 12 years now. about this event: https://c3voc.de

This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. This talk focuses on effective communication with the openSUSE community. Many workgroups have formed around the new Adaptable Linux Platform. However, not all of them are reporting the public yet. [ALP Community Work Group ](https://en.opensuse.org/openSUSE:ALP/Workgroups/Community)would like to encourage workgroup drivers to increase transparency by sharing our recommendations on how to communicate with the openSUSE community. about this event: https://c3voc.de

A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ A traditional Linux file system tree in the root file system has quite a number of directories with special purpose, documented in the Filesystem Hierarchy Standard (FHS). An operating system installation by default populates most of those directories with different kinds of files, e.g. by means of a package manager. When looking closer this theoretical order is quite a mess in practice. Alternative approaches to manage and update software components of the operating system such as MicroOS reveal the inconsistencies and require stricter separation of different types of files. This talk analyzes where we're coming from, how the tree looks today and where we're heading. The talk will be based on https://lnussel.github.io/2020/12/16/fslayout/ about this event: https://c3voc.de

How we got onto YouTube as Makers and a realistic look at what it's like to be content creators including some of the pitfalls, with examples of 'how going viral can be a curse'. Participants are: James Bruton Matt Denton Ruth Amos about this event: https://c3voc.de

Ru Callender has been a self proclaimed, self taught Radical undertaker for the past 23 years, and draws upon a diverse range of influences in his work, such as rave culture, punk DIY, crop circles and performance art and ritual magic. He had written an account of this time in a book entitled “What remains? Life death and the human art of undertaking” for the progressive US publishers Chelsea Green. Ru will be in conversation with Sophie Lovejoy, funeral celebrant and life coach and EMF favourite. Trigger warning: We die. about this event: https://c3voc.de

Placeholder for the second Lightning Talks session about this event: https://c3voc.de

The Apollo Guidance Computer (AGC) was a critical element in the success of the Apollo Moon landing programme, and was one of the first digital computers to use the then new technology of integrated circuits. By modern standards, its design has many unusual aspects, such as: - The logic circuits were made entirely from 3 input NOR gates. - Design was split into 24 logic modules, but due to limits on gate/chip count per module, individual gates were sometimes 'borrowed' from unrelated modules. - Shift and rotate operations existed, but were not available during interrupts. - Numerical overflows disabled interrupts. - There was no stack. - Limited memory addressing range, combined with a need for ever more memory lead to a complex memory banking system. - Word length was 15 bits, ones-complement (mostly). - No floating point - everything done in integer - programmer responsible for avoiding overflows. - Single bit 'Up/Down' Analog to Digital conversion (kind of) throughout, with the curious side-effect that the faster the spacecraft was rotating, the slower the computer would run... On top of the limited hardware was built an impressive realtime system supporting cooperative multitasking, a virtual machine running interpreted commands, a powerful fault detection and restart system, and an innovative VERB NOUN user interface. This talk aims to describe the architecture, with particular focus on aspects which are unusual by modern standards. about this event: https://c3voc.de

simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. simpledrm is a fbdev replacement implemented in the DRM kernel subsystem. It allows for smoother handover from the early boot phase to when a "real" DRM driver is loaded. In addition it allows for Wayland support on simple display adapters that do not have their own DRM driver. It has already been mainlined for a while but is not in active use by major linux distributions. In this talk I will briefly introduce you to the project and show you how you can test it on your machines. I have recently learned about this effort and started looking at DRM. This talk is held by a kernel newbie. about this event: https://c3voc.de

This talk will go over the history of the openSUSE Bar. How it started and what it has done. This talk will go over the history of the openSUSE Bar. How it started and what it has done. about this event: https://c3voc.de

Keysmashes are way of expressing emotions through spamming random letters on a keyboard but what do they actually mean? How random is a keysmash? Where do keysmashes come from? What can we learn about a person from their keysmashes? This talk is a beginners guide to the world of keysmashes and what they tell us about modern communications and online communities. about this event: https://c3voc.de

I am an engineer, so when my partner died when I was 24 and I found myself in the midst of grief, I discovered that the best way of dealing with it was to use the engineering approach that was already ingrained in me. “An engineer's guide to grief” if you will. Some bits worked (some less so!) and that’s what I want to share with you, ahead of a honest, open conversation exploring how we can get all get better at dealing with, and talking about, death. Trigger warnings: Death, dying, cancer, middle-aged lady probably wearing too much leopard-print about this event: https://c3voc.de

Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. Business processes evolve continuously, customer expectations and requirements change even faster. Process management and workflow support systems have a tendency to grow organically into fearsomely complex monolithic beasts while piling up technical debt in the process. Data migrations come at high cost, changing systems almost always require data to be converted into the new systems particular data model, which makes doing data migration verification both complex as well as costly. Using the open source/free software SQL database engine PostgreSQL, one of the leading Relational Database Management Systems, and in recent years the most popular database engine used in startups and scaleups, takes away the concern of future accessibility and integrity of the data itself. A middleware layer/REST API built with Symfony framework and a ReactJS based frontend ensure a fully responsive modern UX. Furthermore we use GitLab and Ansible for project management and automating our CI/CD environment. At OpenNovations we’ve created a solution called Aranei built with standard open source tools which generates a state of the art, open web standards based, user interface on top of any existing SQL data structure. Keep the same schema/structure between source system and archiving solution, or to use the notion of a controlled copy, is a much less cumbersome approach, as a one on one data verification can be performed. Not just the UI components themselves are generated by the metadata app modeling engine, also automated test scripts and a data dictionary are generated as part of the data verification process. about this event: https://c3voc.de

Trains are one of the safest ways to travel, but it hasn't always been like that. In this talk I will introduce the basics of railway signalling, and look at how it has evolved over time - often in response to accidents and near-misses. You will find out how a single stray wire caused an accident that killed 35 people, why leaves on the line cause such a problem for the railways, and how signalling systems are designed to deal with the inevitable human error. Working from the early days of the railway to the present (and future), the talk will take you through a number of accidents, their causes and the improvements that were made after the accidents. This talk is suitable for any level of knowledge about railways - it aims to be understandable for complete beginners, and still have some interesting parts even for railway geeks. about this event: https://c3voc.de

The SEGA Dreamcast was released nearly 25 years ago, but was discontinued after only 18 months on sale in the west, and was such a commercial failure that SEGA never made another console. Despite this short lifetime, a homebrew community formed, has not gone away, and has only become more passionate since. The most tangible demonstrations of this passion are the extensive hardware modifications that have been developed by hobbyists to drag the Dreamcast kicking and screaming in to the 21st century. Users can restore internet connectivity, replace the PSU or the commonly-failing disk drive (originally based on bespoke optical media), and even enable true digital video output. I will talk about the origins of the Dreamcast homebrew scene, and the development and implementation of the most popular of these mods that ensure the Dreamcast will live on for many years to come. about this event: https://c3voc.de

We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. We have several ways to install and update openSUSE distributions, standard with zypper, atomic with transactional-update or using disk images created with kiwi or similar tools. But this are all RPM based. In some scenarios, it would be good to have an image based installation and update mechanism (image means /usr, not a full disk image). A PoC is MicroOS TIU (https://github.com/thkukuk/tiu), which allows to use either btrfs snapshots or several partitions (usrAB) for installation and update. This talk will give some insight into it. The current status, the problems, what it means for packaging, etc. about this event: https://c3voc.de

Exploring data ethics through creative immersive tools with brainwave, and motion capture data. Is there a difference in sense of self (identity) between the human and the virtual? How does sharing your personal biometric data make you feel? How can biometric and immersive development tools be used in the computing classroom and dance studios to raise awareness of data ethics and immersive performance tools? We created 3D motion capture data from 2D RGB video sources using AI software. We recorded and visualised EEG using cheaply available equipment. We are currently producing a performance in Augmented Reality, using game development tools for animation data visualisation, particle systems, fragment shaders, etc. And data sonification with Python and Sonic PI. We will give a video demonstration of work in progress augmented reality ballet using the concepts we have developed. It is cool and awesome. about this event: https://c3voc.de

Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. Default community distributions are running in the same issues for special architectures. Every Linux distribution has got mostly separate maintainers and hardware distributors are handling these communities really often disconnected. That has been identified also for the architecture s390x. Therefore, openSUSE, Fedora, Debian, SUSE, Canonical (Ubuntu) and Red Hat have established together with IBM a Linux Distributions Working Group for a better collaboration together and with the goal to achieve better support. In this presentation, you should receive an overview of a good collaboration between Linux distributions and what you can achieve together with such a Working Group. about this event: https://c3voc.de

D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. D-Installer is the code-name of a experimental project for creating a new YAST-based installer designed to offer reusability, better integration with third-party tools and the possibility of building rich user interfaces over it. In this talk, we will explain the motivation of the YaST Team for creating a new installer and what possibilities this new idea brings. There will be time for diving into some technical details about the project architecture and we will show a live demo! You will hear about D-Bus, web interfaces, YaST and Cockpit. If you are interested in how all those pieces play together, do not hesitate to join us. about this event: https://c3voc.de

Margate, Kent is a phoenix rising from the ashes of Britain's great seaside institutions. This one-time jewel had been abandoned to decay and deprivation. The last 6 or 7 years have seen green shoots of regeneration begun by Turner Contemporary Gallery and is now rich in galleries, media consultants, music and film producers. Its High Street is an exemplar for retail re-purposing. Unfortunately, there remains a lot of deprivation and a widening digital divide. This talk is an engineer’s tale of moving to Margate from London. The opportunities, experiences and challenges had so far, and an ambition to bring more joy of tech to the area. I will talk about Margate's Maker community as context, and tell tales of working with artists and involvement with several community activities. I even mange to squeeze in a bit of IDEF0 modelling! about this event: https://c3voc.de

Fire has been a ubiquitous technology for countless millennia, finding applications across many problem domains. This talk describes the development of a new product that brings fire into the wearable technology arena. Wearable technology is often limited to daily practicalities like reading emails on your wrist or tracking your fitness goals. In this talk you will witness large plumes of burning gas that can be a thoroughly impractical, but hilarious, addition to your wardrobe. about this event: https://c3voc.de

Unfortunately, you cannot pop magic Limitless style pills to improve your memory. But with a bit of understanding about how our memory works, we can introduce techniques that will help us remember important and even unimportant information. In this talk, I will talk a bit about the structure of memory and then discuss some techniques that anyone can use to improve their memory (when you want to). about this event: https://c3voc.de

Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. Sourcery is a program that builds root file systems consisting mostly of Go source code: of the 90,000 files in a typical sourcery root, there are only 12 or so programs. Other programs are compiled on demand to a ramfs-backed file system. Compilation takes a fraction of a second for most programs, and never more than 2 seconds. Once the program is compiled to a statically-linked, tmpfs-based binary, invocation is instantaneous. Because these images are mostly source, they can also be multi-architecture. Binaries present on boot have a path formed from the target os and architecture, e.g. /$OS_$ARCH/bin/init for init. Dynamically compiled binaries are placed in the tmpfs-backed /bin, since these binaries vanish on boot, the path can be simpler. The file system includes the full Go toolchain as well as all source code. Constructing the root file system, including the git clone steps and Go toolchain build, takes under 4 minutes; each additional architecture takes another 90 seconds (to ensure reproducible builds, the Go toolchain builds itself 3 times). Sourcery root file systems are designed for VFAT, a standard for firmware for x86, ARM, and RISC-V. A typical USB stick for sourcery would include a syslinux bootstrap for x86, required for those platforms; a kernel Image file for ARM; and a kernel file for RISC-V: the firmware for ARM and RISC-V is able to find boot kernels without using an on-stick bootstrap. Sourcery may be found at github.com:u-root/sourcery. about this event: https://c3voc.de

**transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. **transactional-update** is the openSUSE way of a **Transactional Operating System update** and a core component of _openSUSE MicroOS_ / _Kubic_ and _SLE Micro_, making sure updates can be applied safely without affecting the currently running system. It's also supposed to play an important component in the future ALP. At lot of things have changed internally since the last talk at oSC19: The core functionality has been **rewritten in C++** (formerly Bash), including a **C++ and C API** and a **D-Bus interface**. From a user's perspective the transactional-update command line interface still looks the same, but we now have **Cockpit** and **dnf integration**. This talk will - give a **short overview of transactional-update** for those new to the concept. - introduce `tukit`, the command line interface for the API functionality. - present the new **Cockpit** interface for transactional-update. - present the **dnf** integration. - give an overview over other changes (SELinux support, Kernel Live Patching). - and we should also have some minutes left for questions and discussions. about this event: https://c3voc.de

Suzie is the creator of Two Tin Cans, a printmaking studio in a telephone box which will be at EMF! Two Tin Cans is a K6 style phonebox... with a difference! Inside the phonebox is a tiny printmaking studio includes printing blocks created by Suzie Devey. Every person who enters the box can make a unique work of art to keep, for free. New artwork is created for every event making the work highly collectable! Established as a way to tackle loneliness across the North York Moors the phonebox is in high demand as a way to make creative conversations happen. Funded by Arts Council England, Suzie worked with Teesside Hackspace to test ideas and make the magic happen! This talk tells the story of my journey as an artist and how I encouraged people from all walks of life to get in touch with their local hackspaces as part of the creative engagement. about this event: https://c3voc.de

Advances in NLP and machine learning are allowing automatic processing of knowledge. An untapped potential of this revolution is the ability to change how people come up with ideas and solve problems. People tend to solve problems in linear ways. If my horse is too slow, I want a way to make it faster. It wasn't clear to many people of the 1800s that changes in industrialisation would lead to an entirely new way of going fast! So what happens when you do have all of the information, and when you can find subtle patterns occurring in vast swathes of data? What happens when an engineer's Alexa can tell you not just the answer to your question, but the answer to the question that you didn’t know you were asking? I would like to explore how AI may fundamentally change the human’s ability to think and invent, and the changes that this may lead to in society, drawing on my experience as the head of the world’s first AI augmented invention team with example patents and progress that has been made so far. about this event: https://c3voc.de