mastodon.uno è uno dei tanti server Mastodon indipendenti che puoi usare per partecipare al fediverso.
Mastodon.Uno è la principale comunità mastodon italiana. Con 77.000 iscritti è il più grande nodo Mastodon italiano: anima ambientalista a supporto della privacy e del mondo Open Source.

Statistiche del server:

6,2K
utenti attivi

#eol

6 post5 partecipanti1 post oggi

Nitrocid 0.1.1 is no longer supported

We are announcing that the end of support for the first minor release after the 0.1.0 version, the 0.1.1 version that was released on July 23rd, 2024, has officially commenced as of today. It added new features, such as The Nitrocid Homepage, while improving existing features to make them more reliable.

The final mod API version for this version series was v3.0.26.60, and the final version of this release series was v0.1.1.36. Starting from today, we will no longer:

  • provide further new versions under that version series
  • provide support for users that continue to use this version series
  • provide any security and features improvements across different components

In addition to that, the warning message will be displayed upon trying to start this version series up, reminding you of this series’ support. In Debian builds, you’ll be notified in the command line that you’re installing the version series that is no longer supported.

In order to continue getting new features and security updates, and to continue receiving support from us, please either use the latest LTS version, which is v0.1.0.x, or use the latest short-term supported version, such as v0.1.2.x.

@ChrisLAS @ironicbadger really sad to hear about the #selfhosted #podcast reaching #EOL, I've been with you since the single-digit episodes, was an #SRE supporter then Jupiter.party, it was SelfHosted that brought me to #JupiterBroadcasting all those years ago.

Will be really sad to see it go, the cadence was great, and you two made wonderful hosts.

Sorry about the #AdWinter, afraid that is what is doing in so many JB shows like SH and Coder Radio.

Old Nitrocid PPA EOL Reminder

The old Nitrocid PPA (kernel-sim) has been officially marked as deprecated as of the 0.1.2.0 release on February 27th, 2025. The reason was that because we wanted to get rid of a PPA that hosted very old versions of Nitrocid KS, such as 0.0.15.8 for Groovy Gorilla uploaded on April 14th, 2021, and because the most recent versions that were released had libc6 issues on Jammy Jellyfish and older.

We have only added the deprecation notice to the old PPA mentioned above, but we’ve recently updated the notice. We will permanently disable the kernel-sim PPA starting July 1st, 2025, as we get closer to the second half of the year.

To disable the kernel-sim PPA and to enable the newer Nitrocid PPA, nitrocid, follow these steps:

  1. Uninstalling all Nitrocid-related packages from the old PPA
    1. Open the terminal emulator
    2. Run sudo apt purge kernel-simulator
  2. Replacing the kernel-sim PPA with the nitrocid PPA
    1. Run sudo add-apt-repository --remove ppa:eofla/kernel-sim
    2. Run sudo add-apt-repository ppa:eofla/nitrocid
  3. Installing the newer Nitrocid packages
    1. Execute sudo apt update
    2. Follow the instructions by running sudo apt install nitrocid

Once you follow the above steps, you’re now using the new nitrocid PPA instead of the older one. If you failed to remove the kernel-sim PPA from your system before the abovementioned deadline, the apt update command will fail with error messages about said PPA.

Nitrocid 0.1.1 EOL Reminder

We are approaching the end of support for the first minor release after the 0.1.0 version, the 0.1.1 version that was released on July 23rd, 2024. It added new features, such as The Nitrocid Homepage, while improving existing features to make them more reliable.

The final mod API version for this version series is v3.0.26.60, and the final version of this release series is v0.1.1.36 that was released today to fix some small bugs.

The end of support date was assigned as April 23rd, 2025. This means that, starting from that day, we will no longer:

  • provide further new versions under that version series
  • provide support for users that continue to use this version series
  • provide any security and features improvements across different components

In addition to that, the warning message will be displayed upon trying to start this version series up, reminding you of this series’ support. In Debian builds, you’ll be notified in the command line that you’re installing the version series that is no longer supported.

In order to continue getting new features and security updates, and to continue receiving support from us, please either use the latest LTS version, which is v0.1.0.x, or use the latest short-term supported version, such as v0.1.2.x.

In the upcoming service pack for v0.1.0.x, we’ll push all v0.1.1.x features to the long-term version series to make sure that further bugs in those features get fixed across releases.

The Python version diagram has been updated to show the bugfix/security split for each release. (Before, the bars were either completely green or yellow.)

devguide.python.org/versions/

It's also zoomed in and shows fewer releases than before. There's another chart further down the page showing all of 2.6 to 3.14. And the wording in the status key has been refreshed to make it clearer.

Thanks to @nedbat and @encukou for updating it!

#Python#CPython#EOL

When buying your #network #connected #devices, make sure that vendors #support matches your #expectations. Devices might be #EoL ⚰️ even thought they are still being sold 💰. #Maintenance is hard - our decade old Turris 1.0 still receives #updates (contrary to the industry standards) and it is not easy 💪. Sometimes you can #reflash the device with your own #firmware to fix the #security issues, so prefer devices from vendor that pushes their #hardware support #upstream. vulncheck.com/blog/zyxel-telne

VulnCheckZyxel Telnet Vulnerabilities - Blog - VulnCheckVulnCheck and partner GreyNoise discovered Zyxel-related vulnerabilities being targeted in the wild. In this blog, VulnCheck describes the vulnerabilities CVE-2024-40891 and CVE-2025-0890.