home.social

#linuxconfau — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #linuxconfau, aggregated by home.social.

  1. tridge has written a post about the recent #rsync issues:

    rsync and outrage

    medium.com/@tridge60/rsync-and

    pls at least read his post before commenting on this toot
     
     
    like most non-trivial things in life, tech, & especially security, my thoughts on this are… “it’s complicated”
     
     
    I’m only tenuously connected to tridge via the #LinuxConfAU / #EverythingOpen community, but his reputation is the stuff of F/LOSS nerd legend – I was in the room for his #LCA2015 talk in Auckland, Flying with Linux, where he did a live demo of #ArduPilot controlling an RC aircraft in Canberra (AU) with real-time telemetry from the aircraft that was also compiling the Linux kernel while in-flight… 🤯

    YouTube: youtu.be/2Twl2mQAh6g

    LA mirror: mirror.linux.org.au/pub/linux.

    in the post, tridge argues that he is able to bring his (undisputed) expertise in software design & development to find ways use LLMs (relatively) safely to assist with specific coding tasks. I think that’s probably true, even given the regression bugs introduced in the most recent version of rsync – and it may even be the pragmatic least-worst way for open source maintainers to try to deal with the current deluge of LLM-assisted (or entirely LLM-generated) security reports currently overwhelming many open source projects

    but most software devs are not on tridge’s level, and are already using #LLMs as coding assistants in unsafe and unpredictable ways (or just wholesale vibe-coding things without regard for building guardrails at all)

    tridge also points out that he is technically retired and would rather be out sailing than working on maintaining rsync. a very possible outcome from all this might be that he decides to just… walk away and let others pick up the slack (he did note that the silver lining is that a couple of other experienced devs are – at least for now – working on the project)
     
     
    but even if everyone using LLMs to generate code was supervising it closely with very-experienced-software-design-and-development-level skills (they’re definitely not), I still don’t think that would justify or offset the enormous ethical, environmental, & social issues with the creation & use of LLMs

    like I said, #ItsComplicated 💁‍♀️

  2. tridge has written a post about the recent #rsync issues:

    rsync and outrage

    medium.com/@tridge60/rsync-and

    pls at least read his post before commenting on this toot
     
     
    like most non-trivial things in life, tech, & especially security, my thoughts on this are… “it’s complicated”
     
     
    I’m only tenuously connected to tridge via the #LinuxConfAU / #EverythingOpen community, but his reputation is the stuff of F/LOSS nerd legend – I was in the room for his #LCA2015 talk in Auckland, Flying with Linux, where he did a live demo of #ArduPilot controlling an RC aircraft in Canberra (AU) with real-time telemetry from the aircraft that was also compiling the Linux kernel while in-flight… 🤯

    YouTube: youtu.be/2Twl2mQAh6g

    LA mirror: mirror.linux.org.au/pub/linux.

    in the post, tridge argues that he is able to bring his (undisputed) expertise in software design & development to find ways use LLMs (relatively) safely to assist with specific coding tasks. I think that’s probably true, even given the regression bugs introduced in the most recent version of rsync – and it may even be the pragmatic least-worst way for open source maintainers to try to deal with the current deluge of LLM-assisted (or entirely LLM-generated) security reports currently overwhelming many open source projects

    but most software devs are not on tridge’s level, and are already using #LLMs as coding assistants in unsafe and unpredictable ways (or just wholesale vibe-coding things without regard for building guardrails at all)

    tridge also points out that he is technically retired and would rather be out sailing than working on maintaining rsync. a very possible outcome from all this might be that he decides to just… walk away and let others pick up the slack (he did note that the silver lining is that a couple of other experienced devs are – at least for now – working on the project)
     
     
    but even if everyone using LLMs to generate code was supervising it closely with very-experienced-software-design-and-development-level skills (they’re definitely not), I still don’t think that would justify or offset the enormous ethical, environmental, & social issues with the creation & use of LLMs

    like I said, #ItsComplicated 💁‍♀️

  3. tridge has written a post about the recent #rsync issues:

    rsync and outrage

    medium.com/@tridge60/rsync-and

    pls at least read his post before commenting on this toot
     
     
    like most non-trivial things in life, tech, & especially security, my thoughts on this are… “it’s complicated”
     
     
    I’m only tenuously connected to tridge via the #LinuxConfAU / #EverythingOpen community, but his reputation is the stuff of F/LOSS nerd legend – I was in the room for his #LCA2015 talk in Auckland, Flying with Linux, where he did a live demo of #ArduPilot controlling an RC aircraft in Canberra (AU) with real-time telemetry from the aircraft that was also compiling the Linux kernel while in-flight… 🤯

    YouTube: youtu.be/2Twl2mQAh6g

    LA mirror: mirror.linux.org.au/pub/linux.

    in the post, tridge argues that he is able to bring his (undisputed) expertise in software design & development to find ways use LLMs (relatively) safely to assist with specific coding tasks. I think that’s probably true, even given the regression bugs introduced in the most recent version of rsync – and it may even be the pragmatic least-worst way for open source maintainers to try to deal with the current deluge of LLM-assisted (or entirely LLM-generated) security reports currently overwhelming many open source projects

    but most software devs are not on tridge’s level, and are already using #LLMs as coding assistants in unsafe and unpredictable ways (or just wholesale vibe-coding things without regard for building guardrails at all)

    tridge also points out that he is technically retired and would rather be out sailing than working on maintaining rsync. a very possible outcome from all this might be that he decides to just… walk away and let others pick up the slack (he did note that the silver lining is that a couple of other experienced devs are – at least for now – working on the project)
     
     
    but even if everyone using LLMs to generate code was supervising it closely with very-experienced-software-design-and-development-level skills (they’re definitely not), I still don’t think that would justify or offset the enormous ethical, environmental, & social issues with the creation & use of LLMs

    like I said, #ItsComplicated 💁‍♀️

  4. tridge has written a post about the recent #rsync issues:

    rsync and outrage

    medium.com/@tridge60/rsync-and

    pls at least read his post before commenting on this toot
     
     
    like most non-trivial things in life, tech, & especially security, my thoughts on this are… “it’s complicated”
     
     
    I’m only tenuously connected to tridge via the #LinuxConfAU / #EverythingOpen community, but his reputation is the stuff of F/LOSS nerd legend – I was in the room for his #LCA2015 talk in Auckland, Flying with Linux, where he did a live demo of #ArduPilot controlling an RC aircraft in Canberra (AU) with real-time telemetry from the aircraft that was also compiling the Linux kernel while in-flight… 🤯

    YouTube: youtu.be/2Twl2mQAh6g

    LA mirror: mirror.linux.org.au/pub/linux.

    in the post, tridge argues that he is able to bring his (undisputed) expertise in software design & development to find ways use LLMs (relatively) safely to assist with specific coding tasks. I think that’s probably true, even given the regression bugs introduced in the most recent version of rsync – and it may even be the pragmatic least-worst way for open source maintainers to try to deal with the current deluge of LLM-assisted (or entirely LLM-generated) security reports currently overwhelming many open source projects

    but most software devs are not on tridge’s level, and are already using #LLMs as coding assistants in unsafe and unpredictable ways (or just wholesale vibe-coding things without regard for building guardrails at all)

    tridge also points out that he is technically retired and would rather be out sailing than working on maintaining rsync. a very possible outcome from all this might be that he decides to just… walk away and let others pick up the slack (he did note that the silver lining is that a couple of other experienced devs are – at least for now – working on the project)
     
     
    but even if everyone using LLMs to generate code was supervising it closely with very-experienced-software-design-and-development-level skills (they’re definitely not), I still don’t think that would justify or offset the enormous ethical, environmental, & social issues with the creation & use of LLMs

    like I said, #ItsComplicated 💁‍♀️

  5. tridge has written a post about the recent #rsync issues:

    rsync and outrage

    medium.com/@tridge60/rsync-and

    pls at least read his post before commenting on this toot
     
     
    like most non-trivial things in life, tech, & especially security, my thoughts on this are… “it’s complicated”
     
     
    I’m only tenuously connected to tridge via the #LinuxConfAU / #EverythingOpen community, but his reputation is the stuff of F/LOSS nerd legend – I was in the room for his #LCA2015 talk in Auckland, Flying with Linux, where he did a live demo of #ArduPilot controlling an RC aircraft in Canberra (AU) with real-time telemetry from the aircraft that was also compiling the Linux kernel while in-flight… 🤯

    YouTube: youtu.be/2Twl2mQAh6g

    LA mirror: mirror.linux.org.au/pub/linux.

    in the post, tridge argues that he is able to bring his (undisputed) expertise in software design & development to find ways use LLMs (relatively) safely to assist with specific coding tasks. I think that’s probably true, even given the regression bugs introduced in the most recent version of rsync – and it may even be the pragmatic least-worst way for open source maintainers to try to deal with the current deluge of LLM-assisted (or entirely LLM-generated) security reports currently overwhelming many open source projects

    but most software devs are not on tridge’s level, and are already using #LLMs as coding assistants in unsafe and unpredictable ways (or just wholesale vibe-coding things without regard for building guardrails at all)

    tridge also points out that he is technically retired and would rather be out sailing than working on maintaining rsync. a very possible outcome from all this might be that he decides to just… walk away and let others pick up the slack (he did note that the silver lining is that a couple of other experienced devs are – at least for now – working on the project)
     
     
    but even if everyone using LLMs to generate code was supervising it closely with very-experienced-software-design-and-development-level skills (they’re definitely not), I still don’t think that would justify or offset the enormous ethical, environmental, & social issues with the creation & use of LLMs

    like I said, #ItsComplicated 💁‍♀️

  6. Who says Linux people have no sense of humour? This was from the Linux.Conf.AU introduction keynote in 2007. (No, didn't attend that year… but for some reason I grabbed a few videos from it.) #Linux #Humour #LCA2007 #LinuxConfAu #SuSE #RedHat #Debian #Ubuntu #Gentoo

  7. Who says Linux people have no sense of humour? This was from the Linux.Conf.AU introduction keynote in 2007. (No, didn't attend that year… but for some reason I grabbed a few videos from it.) #Linux #Humour #LCA2007 #LinuxConfAu #SuSE #RedHat #Debian #Ubuntu #Gentoo

  8. Who says Linux people have no sense of humour? This was from the Linux.Conf.AU introduction keynote in 2007. (No, didn't attend that year… but for some reason I grabbed a few videos from it.) #Linux #Humour #LCA2007 #LinuxConfAu #SuSE #RedHat #Debian #Ubuntu #Gentoo

  9. Who says Linux people have no sense of humour? This was from the Linux.Conf.AU introduction keynote in 2007. (No, didn't attend that year… but for some reason I grabbed a few videos from it.) #Linux #Humour #LCA2007 #LinuxConfAu #SuSE #RedHat #Debian #Ubuntu #Gentoo

  10. Who says Linux people have no sense of humour? This was from the Linux.Conf.AU introduction keynote in 2007. (No, didn't attend that year… but for some reason I grabbed a few videos from it.) #Linux #Humour #LCA2007 #LinuxConfAu #SuSE #RedHat #Debian #Ubuntu #Gentoo

  11. #EverythingOpen 2024 welcomes #RedHat as a Royal Penguin #sponsor

    Red Hat has a long history with Everything Open and formerly with #linuxconfau

    Red Hat, the first billion US$ #OpenSource company, showed that open source as a model could not only pay the bills, but enabled organisations to see the advantages.

    There would be few enterprises world wide that do not use Red Hat Enterprise Linux #RHEL

    Thank you, Red Hat!

  12. 2024 welcomes as a Royal Penguin

    Red Hat has a long history with Everything Open and formerly with

    Red Hat, the first billion US$ company, showed that open source as a model could not only pay the bills, but enabled organisations to see the advantages.

    There would be few enterprises world wide that do not use Red Hat Enterprise Linux

    Thank you, Red Hat!

  13. #EverythingOpen 2024 welcomes #RedHat as a Royal Penguin #sponsor

    Red Hat has a long history with Everything Open and formerly with #linuxconfau

    Red Hat, the first billion US$ #OpenSource company, showed that open source as a model could not only pay the bills, but enabled organisations to see the advantages.

    There would be few enterprises world wide that do not use Red Hat Enterprise Linux #RHEL

    Thank you, Red Hat!

  14. #EverythingOpen 2024 welcomes #RedHat as a Royal Penguin #sponsor

    Red Hat has a long history with Everything Open and formerly with #linuxconfau

    Red Hat, the first billion US$ #OpenSource company, showed that open source as a model could not only pay the bills, but enabled organisations to see the advantages.

    There would be few enterprises world wide that do not use Red Hat Enterprise Linux #RHEL

    Thank you, Red Hat!

  15. #EverythingOpen 2024 welcomes #RedHat as a Royal Penguin #sponsor

    Red Hat has a long history with Everything Open and formerly with #linuxconfau

    Red Hat, the first billion US$ #OpenSource company, showed that open source as a model could not only pay the bills, but enabled organisations to see the advantages.

    There would be few enterprises world wide that do not use Red Hat Enterprise Linux #RHEL

    Thank you, Red Hat!

  16. #Google are long-term supporters of #EverythingOpen and, previously, #linuxconfau, and jumped at the chance to again #sponsor us this year in #Gladstone #Queensland. We're super grateful for their support.

    #Google has been contributing to the #OpenSource #ecosystem from the start, with projects like #Android, based on the #Linux kernel, and #Chrome, based on the open source #Chromium.

    Thank you, Google!

  17. are long-term supporters of and, previously, , and jumped at the chance to again us this year in . We're super grateful for their support.

    has been contributing to the from the start, with projects like , based on the kernel, and , based on the open source .

    Thank you, Google!

  18. #Google are long-term supporters of #EverythingOpen and, previously, #linuxconfau, and jumped at the chance to again #sponsor us this year in #Gladstone #Queensland. We're super grateful for their support.

    #Google has been contributing to the #OpenSource #ecosystem from the start, with projects like #Android, based on the #Linux kernel, and #Chrome, based on the open source #Chromium.

    Thank you, Google!

  19. #Google are long-term supporters of #EverythingOpen and, previously, #linuxconfau, and jumped at the chance to again #sponsor us this year in #Gladstone #Queensland. We're super grateful for their support.

    #Google has been contributing to the #OpenSource #ecosystem from the start, with projects like #Android, based on the #Linux kernel, and #Chrome, based on the open source #Chromium.

    Thank you, Google!

  20. #Google are long-term supporters of #EverythingOpen and, previously, #linuxconfau, and jumped at the chance to again #sponsor us this year in #Gladstone #Queensland. We're super grateful for their support.

    #Google has been contributing to the #OpenSource #ecosystem from the start, with projects like #Android, based on the #Linux kernel, and #Chrome, based on the open source #Chromium.

    Thank you, Google!

  21. I'm a bit disappointed to be missing #EverythingOpen this year, but I just can't justify attending a conference of that size without it having a strong health & safety policy. (While I haven't signed the @phpledge, I am aligned with its expectations in most cases. And I really don't want to catch #COVID again!)
    It'll be the first #LinuxConfAU-shaped conference I've missed since I started attending in 2012. 😢

  22. I'm a bit disappointed to be missing #EverythingOpen this year, but I just can't justify attending a conference of that size without it having a strong health & safety policy. (While I haven't signed the @phpledge, I am aligned with its expectations in most cases. And I really don't want to catch #COVID again!)
    It'll be the first #LinuxConfAU-shaped conference I've missed since I started attending in 2012. 😢

  23. I'm a bit disappointed to be missing #EverythingOpen this year, but I just can't justify attending a conference of that size without it having a strong health & safety policy. (While I haven't signed the @phpledge, I am aligned with its expectations in most cases. And I really don't want to catch #COVID again!)
    It'll be the first #LinuxConfAU-shaped conference I've missed since I started attending in 2012. 😢

  24. I'm a bit disappointed to be missing #EverythingOpen this year, but I just can't justify attending a conference of that size without it having a strong health & safety policy. (While I haven't signed the @phpledge, I am aligned with its expectations in most cases. And I really don't want to catch #COVID again!)
    It'll be the first #LinuxConfAU-shaped conference I've missed since I started attending in 2012. 😢

  25. I'm a bit disappointed to be missing #EverythingOpen this year, but I just can't justify attending a conference of that size without it having a strong health & safety policy. (While I haven't signed the @phpledge, I am aligned with its expectations in most cases. And I really don't want to catch #COVID again!)
    It'll be the first #LinuxConfAU-shaped conference I've missed since I started attending in 2012. 😢

  26. In an effort to encourage myself to start writing #blog posts again, I’m sharing some of my old posts with a new audience here on mastodon 🙃

    Next one:
    Radia Perlman at #LinuxConfAU 2013 (2013)

    itgrrl.com/2013/03/06/radia-pe

  27. In an effort to encourage myself to start writing #blog posts again, I’m sharing some of my old posts with a new audience here on mastodon 🙃

    Next one:
    Radia Perlman at #LinuxConfAU 2013 (2013)

    itgrrl.com/2013/03/06/radia-pe

  28. In an effort to encourage myself to start writing #blog posts again, I’m sharing some of my old posts with a new audience here on mastodon 🙃

    Next one:
    Radia Perlman at #LinuxConfAU 2013 (2013)

    itgrrl.com/2013/03/06/radia-pe

  29. In an effort to encourage myself to start writing #blog posts again, I’m sharing some of my old posts with a new audience here on mastodon 🙃

    Next one:
    Radia Perlman at #LinuxConfAU 2013 (2013)

    itgrrl.com/2013/03/06/radia-pe

  30. In an effort to encourage myself to start writing #blog posts again, I’m sharing some of my old posts with a new audience here on mastodon 🙃

    Next one:
    Radia Perlman at #LinuxConfAU 2013 (2013)

    itgrrl.com/2013/03/06/radia-pe

  31. By heck, I'd like to go to a LinuxConfAu.

  32. Folks, particularly those of an @everythingopen #OpenSource or #linuxconfau persuasion, please give @nnye a warm welcome to the #Fediverse :fediverse: - great to have her here!

    Edit: Fixed typo

  33. Folks, particularly those of an @everythingopen #OpenSource or #linuxconfau persuasion, please give @nnye a warm welcome to the #Fediverse :fediverse: - great to have her here!

    Edit: Fixed typo

  34. Folks, particularly those of an @everythingopen #OpenSource or #linuxconfau persuasion, please give @nnye a warm welcome to the #Fediverse :fediverse: - great to have her here!

    Edit: Fixed typo

  35. Folks, particularly those of an @everythingopen #OpenSource or #linuxconfau persuasion, please give @nnye a warm welcome to the #Fediverse :fediverse: - great to have her here!

    Edit: Fixed typo

  36. Folks, particularly those of an @everythingopen #OpenSource or #linuxconfau persuasion, please give @nnye a warm welcome to the #Fediverse :fediverse: - great to have her here!

    Edit: Fixed typo

  37. Organiser @saera answers the question "why #EverythingOpen?" - it invites more diverse people, more diverse fields, more diverse attendees together - creating more paths, more opportunities for connections and more opportunities to connect.

    A third of attendees have never been to #linuxconfau before!

  38. Organiser @saera answers the question "why ?" - it invites more diverse people, more diverse fields, more diverse attendees together - creating more paths, more opportunities for connections and more opportunities to connect.

    A third of attendees have never been to before!

  39. Organiser @saera answers the question "why #EverythingOpen?" - it invites more diverse people, more diverse fields, more diverse attendees together - creating more paths, more opportunities for connections and more opportunities to connect.

    A third of attendees have never been to #linuxconfau before!

  40. Organiser @saera answers the question "why #EverythingOpen?" - it invites more diverse people, more diverse fields, more diverse attendees together - creating more paths, more opportunities for connections and more opportunities to connect.

    A third of attendees have never been to #linuxconfau before!

  41. Organiser @saera answers the question "why #EverythingOpen?" - it invites more diverse people, more diverse fields, more diverse attendees together - creating more paths, more opportunities for connections and more opportunities to connect.

    A third of attendees have never been to #linuxconfau before!

  42. The phones are ALMOST alive at #EverythingOpen! These are the old phone numbers from #linuxconfau 2020 on the Gold Coast. "Honest" Rob's Used Car (and VoIP) Emporium has assigned a new number which will be on the website soon.

  43. The phones are ALMOST alive at #EverythingOpen! These are the old phone numbers from #linuxconfau 2020 on the Gold Coast. "Honest" Rob's Used Car (and VoIP) Emporium has assigned a new number which will be on the website soon.

  44. The phones are ALMOST alive at #EverythingOpen! These are the old phone numbers from #linuxconfau 2020 on the Gold Coast. "Honest" Rob's Used Car (and VoIP) Emporium has assigned a new number which will be on the website soon.

  45. The phones are ALMOST alive at #EverythingOpen! These are the old phone numbers from #linuxconfau 2020 on the Gold Coast. "Honest" Rob's Used Car (and VoIP) Emporium has assigned a new number which will be on the website soon.

  46. Today's event is focused on #OpenHardware - folks who have the #linuxconfau #lca2022 #OHMC #SwagBadge #Rockling #FPGA invited to #HackMelbourne , 5 Kent Street, Hawthorn.

    Take a Metro train - fr Southern Cross or Flinders to Glenferrie Stn - Alamein, Belgrave or Lilydale lines.