●● IRC: #techbytes @ Techrights IRC Network: Sunday, December 31, 2023 ●● ● Dec 31 [00:15] schestowitz https://webcache.googleusercontent.com/search?q=cache:NvG5L9IRl8wJ:https://keingerede.eu/reply-to-brodies-stallman-flatpak-video.html&hl=en&gl=uk [00:15] -TechBytesBot/#techbytes- ( status 404 @ https://consent.googleusercontent.com/ml?continue=https://webcache.googleusercontent.com/search%3Fq%3Dcache:NvG5L9IRl8wJ:https://keingerede.eu/reply-to-brodies-stallman-flatpak-video.html%26hl%3Den%26gl%3Duk&gl=GB&m=0&pc=srp&uxe=none&cm=2&hl=en&src=1 ) [00:15] schestowitz "My reply to Brodie's video about Stallmans take on Flatpaks [00:15] schestowitz In his video "In reply to "Stallman's Bizarre Take On Flatpaks & Snaps" Brodie talks about an interview Stallman gave to Wikinews and more specifically about some things he said about Flatpak, Snap, etc. [00:15] schestowitz Stallman made a "bad" argument. As you said yourself, not everyone is correct all of the time. [00:15] schestowitz But if you go into it, it's not that bad or wrong. Because Snaps and Flatpaks (and I want to include Docker as well) can be used to easily include non-free software, while packages, that are disributed via the distributions package managers have to have certain standards and all the used dependencies must be clear. With Debian (and Fedora) they even have to be Free Software. So for the user it's much more clear from the beginning, what [00:15] schestowitz he was getting into, if he uses a "traditional" package manager. [00:15] schestowitz You know and instead of (for lack of a better word) "making fun" of Stallman for his "bizarre" take, why not invite him and him to see how much he actually knows and maybe use the chance to educate him and your viewers more about the issue. Because Flatpaks, Snaps and Dockers (FSDs) come wit a lot of problems more social than technial which is why it's even more important to discuss them. [00:15] schestowitz Free Software (not) included [00:15] schestowitz You were saying, that you don't (currently) want to use 100% Freedom-Giving (Free) Software, which is your good right. The point is, that the user always should have the choice, whether he wants to install and use freedom-denying (non-free) software. And that's Stallmans point, when he says: "So a free operating system always permits you to install non-free programs." It's not so much about, whether the distribution (in the case of GNU+ [00:15] schestowitz Linux) includes proprietary drivers from the beginning. If someone doesn't want to have those drivers preinstalled, that's his good right and if someone does, that's fine as well. The big difference to, let's say Windows users, is, that we have the choice, how much non-free software we want or need (or if we have to have it at all). This is one of those points where Stallman and the FSF actually have changed their stance over the last y [00:15] schestowitz ears. If you go back to talks of Stallman from, let's say 10, 15 years ago Stallman was often refering to the free-distro page you showed. [00:15] schestowitz And even though, they've accepted, that not everyone can run Free Software to the same degree they do, I think it's good and necessery, that the FSF always kept their position, that Free Software is prerequisite for a "free society". I mean, how else should we know, what the goal is? How should we get a glimpse at a possible utopia, if no one talks about it and doesn't show us, what's possible? [00:15] schestowitz Flatpak, Snap and Docker [00:15] schestowitz The security issues [00:15] schestowitz While, I agree with you, that a lot of packaging work is wasted time, FSD are not the solution. Consider this, if there is a security-related bug in OpenSSL or cURL. With FSD every maintainer, that uses the affected library has to update his individual package. Then every user would have to update every single container in the hopes, that the issue got fixed. With the distributions "traditional" package management only the one depencenc [00:15] schestowitz y, that needs to be updated gets updated. All the other maintainers don't need to do a thing. The latest real world example was "libwebp", where some Debian(?) maintainer was writing on the Fediverse, how the whole communtiy beneftied, because only the dependency (libwebp) needed to be udpated. Which also probably saved a lot of redudant work. ;-) [00:15] schestowitz The big social issues [00:15] schestowitz The point Stallman is trying to make, when he says "Nobody's building it" is again not so much a technical, but a social one. Because, of course, most people also don't build the packages, they get from their distros, but there is a community of maintainers, that does. And that is in contrast to all the individual developers and projects, that build and distribute their software by themselfs. This distributions have communities of maint [00:15] schestowitz ainers, devs and users, that meet and have discussions, how they want software packaged, what should be in them and how it can benefit everybody. Flatpak, Snap and Co. are attacking those communities by indiviualising the developers and the users. FSD are probably not even that with bad intention, but they are not healthy for a Free Software (and even "Open Source") community. [00:15] schestowitz Finishing words [00:15] schestowitz In my opinion Flatpak, Snap and Co. are nice tools for developers to quickly setup and test their software, but in the end projects, if they want to be part of a community, should get their projects published via the different package managers. [00:15] schestowitz I also want to recommend you this blog post "Flatpak Is Not The Future", which goes into more technical details." [00:20] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [00:24] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Dec 31 [01:37] *psydruid has quit (connection closed) ● Dec 31 [02:00] *Disconnected (Connection timed out). [02:00] *Disconnected (Connection timed out). [02:00] *Now talking on #techbytes [02:00] *schestowitz[TR2] (~schestowi@freenode/user/schestowitz) has joined #techbytes [02:00] *Now talking on #techbytes ● Dec 31 [03:57] schestowitz
  • [03:57] schestowitz
    Creating an OpenBSD Wireguard VPN Gateway
    [03:57] schestowitz
    [03:57] schestowitz

    A couple of years ago I published a blog post about creating an OpenBSD VPN gateway using OpenVPN.

    [03:57] schestowitz

    I've recently switched from an OpenVPN-based VPN provider to one that uses Wireguard. As a result I've had to redo my VPN gateway.

    [03:57] schestowitz

    I'll only be highlighting the things I've changed since the last setup in this post, so please refer to the previous post for more details.

    [03:57] schestowitz
    [03:57] schestowitz
    • [03:57] -TechBytesBot/#techbytes-blog.lambda.cx | Creating an OpenBSD Wireguard VPN Gateway - lambda.cx blog [03:58] schestowitz
  • [03:58] schestowitz
    Gentoo goes Binary!
    [03:58] schestowitz
    [03:58] schestowitz

    You probably all know Gentoo Linux as your favourite source-based distribution. Did you know that our package manager, Portage, already for years also has support for binary packages, and that source- and binary-based package installations can be freely mixed?

    [03:58] schestowitz

    To speed up working with slow hardware and for overall convenience, were now also offering binary packages for download and direct installation! For most architectures, this is limited to the core system and weekly updates - not so for amd64 and arm64 however. There weve got a stunning >20 GByte of packages on our mirrors, from LibreOffice to KDE Plasma and from Gnome to Docker. Gentoo s [03:58] schestowitz table, updated daily. Enjoy! And read on for more details!

    [03:58] schestowitz
    [03:58] schestowitz
    • [03:58] -TechBytesBot/#techbytes-www.gentoo.org | Gentoo goes Binary! Gentoo Linux [03:59] schestowitz
  • [03:59] schestowitz
    Transform your coffee table into a piece of kinetic sand art
    [03:59] schestowitz
    [03:59] schestowitz

    An Arduino UNO Rev3 board controls those stepper motors through a CNC Shield V3 with two TMC2209 drivers. The sketch is very simple and doesnt run G-code directly. Instead, the user must extract a series of coordinates from a G-code file and copy them into the sketch. But because this is a coffee table, most users will only need to do that one time to program a series of patterns to cycle th [03:59] schestowitz rough.

    [03:59] schestowitz
    [03:59] schestowitz
    • [03:59] schestowitz [03:59] -TechBytesBot/#techbytes-blog.arduino.cc | Transform your coffee table into a piece of kinetic sand art | Arduino Blog [03:59] schestowitz
  • [03:59] schestowitz
    Ordering my first nylon 3D printed part
    [03:59] schestowitz
    [03:59] schestowitz

    NOTE: Posting about 3D printing is an exercise fraught with peril; youll always be told you used the wrong materials or hardware, that you bought it from the wrong place, that you should have done something else, and/or youll be lectured by an armchair chemist about formulations they read on Wikipedia. This post shows something that worked amazingly well for me in this specific use case, [03:59] schestowitz but its up to you to do research if you attempt one of these yourself.

    [03:59] schestowitz
    [03:59] schestowitz
    • [03:59] -TechBytesBot/#techbytes-Rubenerd: Ordering my first nylon 3D printed part ● Dec 31 [04:23] schestowitz
  • [04:23] schestowitz
    Continuous Integration and Workflow Improvement
    [04:23] schestowitz
    [04:23] schestowitz

    As part of our continued support of the FreeBSD Project, we have a full-time staff member dedicated to improving the Projects continuous integration system and the test infrastructure. In 2023, we added more testing jobs for ARM64 architectures like testing with Kernel Address Sanitizer and building test for non-standard compilers like GCC 12 and 13.

    [04:23] schestowitz

    We have also made great progress running the workflow working group, designing and implementing systems to support the pull-request based workflow. Pre-commit CI is on the horizon as well.

    [04:23] schestowitz
    [04:23] schestowitz
    • [04:23] schestowitz [04:23] -TechBytesBot/#techbytes-freebsdfoundation.org | Continuous Integration and Workflow Improvement FreeBSD Foundation ● Dec 31 [05:53] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Dec 31 [06:37] *u-amarsh04 has quit (Ping timeout: 2m30s) ● Dec 31 [07:55] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [07:56] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Dec 31 [08:29] *u-amarsh04 (~amarsh04@dc77dxzcmjmaq.irc) has joined #techbytes ● Dec 31 [09:42] *u-amarsh04 has quit (Quit: Konversation terminated!) [09:48] *u-amarsh04 (~amarsh04@dc77dxzcmjmaq.irc) has joined #techbytes [09:53] *u-amarsh04 has quit (Quit: Konversation terminated!) [09:57] *u-amarsh04 (~amarsh04@dc77dxzcmjmaq.irc) has joined #techbytes ● Dec 31 [10:23] *jacobk (~quassel@kgjtzp9sreehi.irc) has joined #techbytes [10:26] *jacobk has quit (Ping timeout: 2m30s) ● Dec 31 [11:31] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [11:33] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [11:49] *Righty (~Username@eu6xsuxgxtzea.irc) has joined #techbytes [11:52] *Righty (~Username@eu6xsuxgxtzea.irc) has left #techbytes [11:59] schestowitz > There are some further significant changes I'll have to make. [11:59] schestowitz > [11:59] schestowitz > I'm also thinking of making a series of posts out of it, because it got [11:59] schestowitz > so long. [11:59] schestowitz Definitely. [11:59] schestowitz Beat me to it. ● Dec 31 [14:13] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [14:13] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [14:18] *psydroid2 (~psydroid@u8ftxtfux23wk.irc) has joined #techbytes ● Dec 31 [18:30] *SaphirJD (~SaphirJD@8dh7gmy6ps5fy.irc) has joined #techbytes ● Dec 31 [23:01] *psydroid2 has quit (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/) [23:20] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [23:20] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes