HayadSont

joined 3 weeks ago
[–] HayadSont@discuss.online 1 points 1 day ago (1 children)

Your reply is much appreciated, fam! Unfortunately, I wasn't able to return right away. I thank you for your patience! Btw, I'm not native. So, if I misuse any terms/words/phrases or whatnot; my apologies. Usually, I put in some significant effort to alleviate this. Sadly, I didn't quite have the chance to do so this time. Thank you for your understanding!

Firstly, I'm glad we can have a civil discourse on this topic rather than resorting to personal attacks and namecalling. I also appreciate the fact that you seem like someone who actually wants to get to the truth rather than defending your stance no matter what.

Thanks fam for the compliments! Your engagement is (I think) (at least) equally commendable!

You're right. The people in the video are in fact publicly celebrating the 9/11 attacks which took the lives of thousands of innocent people. As you can see, it's not just grown ass men who are celebrating, but children and women too. If this is the level of hatred they have towards the United States, do I really need to explain how severe their hatred for Israel would be?

Btw, I understood the implied context of the footage. But, it would be intellectually dishonest if I didn't take into account the framing at hand. Cuz, if we were to be very critical of the footage itself (so without AP's provided text as guidance), then there's nothing explicitly there that connects those celebrations to the 9/11 killings; no burning of American flags or anything that would imply it. Granted, I assume neither of us speak Arabic. So that doesn't help either πŸ˜….

Just to be clear, I'm well aware that this story is pretty much uncontested^[I did find this, but it seems to be a biased take.]. So I'm not actually disputing it. But, with the benefit of hindsight^[That is, the eventual wars in Iraq and Afghanistan.], it's hard to completely deny any ulterior motives for broadcasting said celebrations.

And to push back: is it sociologically-speaking strange for them to be glad that the biggest support of their rivals has received a retribution?

That's an easy question to answer. There would be one country and it would be called Palestine.

History has indeed taught us that that^[Nation states only exist since relatively recently. So, there has never been a Palestinian state or something. However, Muslim rule has dictated over those lands. My reading of history informs me that while Jews definitely weren't first-class citizens, they were fortunately not persecuted like we saw in other parts of the world.]'s a pretty likely outcome. But, I was also curious to hear your take on the other question. Namely, "What would become of the Israeli people?".

But they will be celebrating.

Likely indeed.

And they will want the whole world to see them celebrating. That's for sure.

For this, I'm not so sure. But it could be.

https://en.m.wikipedia.org/wiki/Dolphinarium_discotheque_bombing#Aftermath

Ah, another celebration. I'm starting to notice a pattern :P .

https://www.youtube.com/watch?v=cWOw7YI7vzo

Another one.

https://www.youtube.com/watch?v=0xPNTbtUHVc

This video I didn't pay a lot of attention to as the media outlet didn't seem to be as reliable as I'd like.

https://www.youtube.com/watch?v=c-wyW-7iJwU

I think I got the message by now :P .

Again I want to be very clear that I'm not an Israeli sympathizer. I'm just trying to make a point that the Palestinians aren't the saints that the liberals (btw I'm a liberal myself) often portray them to be.

If sainthood is achieved through suffering alone, then I'd argue they would make a good chance. But yeah, I get where you're hinting at.

[–] HayadSont@discuss.online 1 points 1 day ago (1 children)

While that’s a good read for someone more technical

I would perhaps put more importance to eagerness to learn. But (I think) I understand where you're hinting at.

the distro chooser brings it to people of lower technical prowess.

While the distrochooser definitely has a lower entry barrier, I'd argue that if one isn't willing to read the above guide, then they might as well roll a die and choose between Bazzite, Fedora, Linux Mint, Pop!_OS, TUXEDO OS and Zorin OS accordingly.

[–] HayadSont@discuss.online 1 points 4 days ago* (last edited 4 days ago) (4 children)

While your endorsement is definitely well-intentioned, I'm unsure if it correctly reflects the project's health^[Unsure if I'd be able to word my criticisms better than this.]. I'd argue we've got (a lot) better resources on the fediverse. Like, e.g. this excellent guide: Understanding Linux and choosing your first Linux distro, v2.0

[–] HayadSont@discuss.online 2 points 4 days ago* (last edited 4 days ago) (3 children)

Thank you for providing that video!

I hadn't seen it before, and I can definitely understand why its content is disturbing.

Granted, as I'm unable to understand the context beyond what AP themselves have provided, I'll (for the sake of the argument) accept this as Palestinians celebrating an attack on the US.

Then, my initial intention was to dissect the argument and explain why I can't agree with your extrapolation^[That is, "But if Palestine had the kind of military backing Israel does, Israel would simply not exist on the map today. And the Palestinians would be openly celebrating over the dead bodies of Israeli people."]. However, to my surprise, your extrapolation might not be as far-fetched as I initially thought πŸ˜…. But, this ultimately depends on what you mean precisely. So, please allow me to ask further clarifications:

  • With "Israel would simply not exist on the map today.", what do you mean exactly? Like, what would come in its place? What would become of the Israeli people?
  • With "And the Palestinians would be openly celebrating over the dead bodies of Israeli people.", do you mean something similar like we see on the footage? Or something more grandiose? (And perhaps more sinister?)

Let me know if you still aren’t convinced.

Please allow me to take you up on that offer 😜.

[–] HayadSont@discuss.online 1 points 4 days ago (1 children)

they’ve been apparently working on its replacement for quite some time, so the β€œnews” of its retirement actually comes because of the discovery of its replacement and the chatter around it.

Are you referring to the combination of Agama, Ansible and Cockpit?

[–] HayadSont@discuss.online 3 points 4 days ago

Thanks for posting.

It has been my pleasure!

I was worried that it might have been forgotten about

The XZ utils supply chain attack has actually made the community more wary of blobs. Some projects were even prompted to come clean on this matter.

Fedora has also recently made a push towards reproducible builds. In the lwn.net article that discussed that push, one of Fedora's spokespeople explicitly said that it would help combat supply chain attacks.

So, all in all, I can confidently say that it did leave a mark on the Linux landscape. Hopefully, this specific attack vector will not be as viable in the foreseeable future.

[–] HayadSont@discuss.online 9 points 4 days ago (5 children)

But if Palestine had the kind of military backing Israel does, Israel would simply not exist on the map today. And the Palestinians would be openly celebrating over the dead bodies of Israeli people.

What is this based on? Like, could you (by any means) back up this claim?

[–] HayadSont@discuss.online 3 points 5 days ago (3 children)

Please correct me if I'm wrong, but my understanding is that we didn't get any alternative in return. Right?

 

A video by SavvyNik that covers some of the highlights from the following recently published scientific article - Wolves in the Repository: A Software Engineering Analysis of the XZ Utils Supply Chain Attack

 

A video by SavvyNik that covers some of the highlights from the following recently published scientific article - Wolves in the Repository: A Software Engineering Analysis of the XZ Utils Supply Chain Attack

[–] HayadSont@discuss.online 3 points 5 days ago

Thank you for the answer! Much appreciated.

Mint has a common issue of destroying itself on updates.

Could you be more explicit? Like, I don't think it literally deletes itself from your drive. Right? So, what is it then?

[–] HayadSont@discuss.online 2 points 5 days ago

It has been my pleasure! Hope it'll work out for ya!

[–] HayadSont@discuss.online 3 points 5 days ago (2 children)

With no Adobe CC on Linux

How's this?

[–] HayadSont@discuss.online 2 points 5 days ago* (last edited 5 days ago) (2 children)

Mint has far too many issues to be a serious suggestion.

Would you mind elaborating on that?

Edit: Note that I've been a Linux^[Including the likes of: EndeavourOS, Fedora Atomic, Nobara and Zorin OS] user for a couple of years now, so no need to dumb down the answer for me. Just a heads-up*.

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects β€” those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects β€” those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects β€” those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

While this is an especially great development for the Fedora Atomic aficionados among us, I wouldn't be surprised if we'll be hearing a lot more from sysexts as (yet another) avenue for installing software, particularly on other atomic/immutable distros. The concept itself isn't new - Flatcar has been utilizing this approach for some time (and has been a significant influence on this Fedora initiative).

The gist would be that it basically allows installing software natively without the traditional rpm-ostree layering method. This approach eliminates both the lengthy installation times and reboot requirements typically associated with that process. Though, it doesn't seem to completely replace the conventional method as it comes with certain limitations (as per the developer):

They can not be used to:

  • install another kernel
  • install kernel modules
  • make changes to the initrd
  • make changes to /etc
  • add udev rules

For those wondering what is actually envisioned to be installed using this method, the software that's already available may shed some light πŸ˜‰.

In any case, note that this is FAR from its final form. The (relative) complexity currently involved in installing and updating software reflects this clearly; don't expect shiny wrappers that will make all of us blissfully ignorant of the underlying complexity right away 😜.

 

While this is an especially great development for the Fedora Atomic aficionados among us, I wouldn't be surprised if we'll be hearing a lot more from sysexts as (yet another) avenue for installing software, particularly on other atomic/immutable distros. The concept itself isn't new - Flatcar has been utilizing this approach for some time (and has been a significant influence on this Fedora initiative).

The gist would be that it basically allows installing software natively without the traditional rpm-ostree layering method. This approach eliminates both the lengthy installation times and reboot requirements typically associated with that process. Though, it doesn't seem to completely replace the conventional method as it comes with certain limitations (as per the developer):

They can not be used to:

  • install another kernel
  • install kernel modules
  • make changes to the initrd
  • make changes to /etc
  • add udev rules

For those wondering what is actually envisioned to be installed using this method, the software that's already available may shed some light πŸ˜‰.

In any case, note that this is FAR from its final form. The (relative) complexity currently involved in installing and updating software reflects this clearly; don't expect shiny wrappers that will make all of us blissfully ignorant of the underlying complexity right away 😜.

 

While this is an especially great development for the Fedora Atomic aficionados among us, I wouldn't be surprised if we'll be hearing a lot more from sysexts as (yet another) avenue for installing software, particularly on other atomic/immutable distros. The concept itself isn't new - Flatcar has been utilizing this approach for some time (and has been a significant influence on this Fedora initiative).

The gist would be that it basically allows installing software natively without the traditional rpm-ostree layering method. This approach eliminates both the lengthy installation times and reboot requirements typically associated with that process. Though, it doesn't seem to completely replace the conventional method as it comes with certain limitations (as per the developer):

They can not be used to:

  • install another kernel
  • install kernel modules
  • make changes to the initrd
  • make changes to /etc
  • add udev rules

For those wondering what is actually envisioned to be installed using this method, the software that's already available may shed some light πŸ˜‰.

In any case, note that this is FAR from its final form. The (relative) complexity currently involved in installing and updating software reflects this clearly; don't expect shiny wrappers that will make all of us blissfully ignorant of the underlying complexity right away 😜.

 

Look, I've only been a Linux user for a couple of years, but if there's one thing I've learned, it's that we're not afraid to tinker. Most of us came from Windows or macOS at some point, ditching the mainstream for better control, privacy, or just to escape the corporate BS. We're the people who choose the harder path when we think it's worth it.

Which is why I find it so damn interesting that atomic distros haven't caught on more. The landscape is incredibly diverse now - from gaming-focused Bazzite to the purely functional philosophy of Guix System. These distros couldn't be more different in their approaches, but they all share this core atomic DNA.

These systems offer some seriously compelling stuff - updates that either work 100% or roll back automatically, no more "oops I bricked my system" moments, better security through immutability, and way fewer update headaches.

So what gives? Why aren't more of us jumping on board? From my conversations and personal experience, I think it boils down to a few things:

Our current setups already work fine. Let's be honest - when you've spent years perfecting your Arch or Debian setup, the thought of learning a whole new paradigm feels exhausting. Why fix what isn't broken, right?

The learning curve seems steep. Yes, you can do pretty much everything on atomic distros that you can on traditional ones, but the how is different. Instead of apt install whatever and editing config files directly, you're suddenly dealing with containers, layering, or declarative configs. It's not necessarily harder, just... different.

The docs can be sparse. Traditional distros have decades of guides, forum posts, and StackExchange answers. Atomic systems? Not nearly as much. When something breaks at 2am, knowing there's a million Google results for your error message is comforting.

I've been thinking about this because Linux has overcome similar hurdles before. Remember when gaming on Linux was basically impossible? Now we have the Steam Deck running an immutable SteamOS (of all things!) and my non-Linux friends are buying them without even realizing they're using Linux. It just works.

So I'm genuinely curious - what's keeping YOU from switching to an atomic distro? Is it specific software you need? Concerns about customization? Just can't be bothered to learn new tricks?

Your answers might actually help developers focus on the right pain points. The atomic approach makes so much sense on paper that I'm convinced it's the future - we just need to figure out what's stopping people from making the jump today.

So what would it actually take to get you to switch? I'm all ears.

 

Look, I've only been a Linux user for a couple of years, but if there's one thing I've learned, it's that we're not afraid to tinker. Most of us came from Windows or macOS at some point, ditching the mainstream for better control, privacy, or just to escape the corporate BS. We're the people who choose the harder path when we think it's worth it.

Which is why I find it so damn interesting that atomic distros haven't caught on more. The landscape is incredibly diverse now - from gaming-focused Bazzite to the purely functional philosophy of Guix System. These distros couldn't be more different in their approaches, but they all share this core atomic DNA.

These systems offer some seriously compelling stuff - updates that either work 100% or roll back automatically, no more "oops I bricked my system" moments, better security through immutability, and way fewer update headaches.

So what gives? Why aren't more of us jumping on board? From my conversations and personal experience, I think it boils down to a few things:

Our current setups already work fine. Let's be honest - when you've spent years perfecting your Arch or Debian setup, the thought of learning a whole new paradigm feels exhausting. Why fix what isn't broken, right?

The learning curve seems steep. Yes, you can do pretty much everything on atomic distros that you can on traditional ones, but the how is different. Instead of apt install whatever and editing config files directly, you're suddenly dealing with containers, layering, or declarative configs. It's not necessarily harder, just... different.

The docs can be sparse. Traditional distros have decades of guides, forum posts, and StackExchange answers. Atomic systems? Not nearly as much. When something breaks at 2am, knowing there's a million Google results for your error message is comforting.

I've been thinking about this because Linux has overcome similar hurdles before. Remember when gaming on Linux was basically impossible? Now we have the Steam Deck running an immutable SteamOS (of all things!) and my non-Linux friends are buying them without even realizing they're using Linux. It just works.

So I'm genuinely curious - what's keeping YOU from switching to an atomic distro? Is it specific software you need? Concerns about customization? Just can't be bothered to learn new tricks?

Your answers might actually help developers focus on the right pain points. The atomic approach makes so much sense on paper that I'm convinced it's the future - we just need to figure out what's stopping people from making the jump today.

So what would it actually take to get you to switch? I'm all ears.

 

Look, I've only been a Linux user for a couple of years, but if there's one thing I've learned, it's that we're not afraid to tinker. Most of us came from Windows or macOS at some point, ditching the mainstream for better control, privacy, or just to escape the corporate BS. We're the people who choose the harder path when we think it's worth it.

Which is why I find it so damn interesting that atomic distros haven't caught on more. The landscape is incredibly diverse now - from gaming-focused Bazzite to the purely functional philosophy of Guix System. These distros couldn't be more different in their approaches, but they all share this core atomic DNA.

These systems offer some seriously compelling stuff - updates that either work 100% or roll back automatically, no more "oops I bricked my system" moments, better security through immutability, and way fewer update headaches.

So what gives? Why aren't more of us jumping on board? From my conversations and personal experience, I think it boils down to a few things:

Our current setups already work fine. Let's be honest - when you've spent years perfecting your Arch or Debian setup, the thought of learning a whole new paradigm feels exhausting. Why fix what isn't broken, right?

The learning curve seems steep. Yes, you can do pretty much everything on atomic distros that you can on traditional ones, but the how is different. Instead of apt install whatever and editing config files directly, you're suddenly dealing with containers, layering, or declarative configs. It's not necessarily harder, just... different.

The docs can be sparse. Traditional distros have decades of guides, forum posts, and StackExchange answers. Atomic systems? Not nearly as much. When something breaks at 2am, knowing there's a million Google results for your error message is comforting.

I've been thinking about this because Linux has overcome similar hurdles before. Remember when gaming on Linux was basically impossible? Now we have the Steam Deck running an immutable SteamOS (of all things!) and my non-Linux friends are buying them without even realizing they're using Linux. It just works.

So I'm genuinely curious - what's keeping YOU from switching to an atomic distro? Is it specific software you need? Concerns about customization? Just can't be bothered to learn new tricks?

Your answers might actually help developers focus on the right pain points. The atomic approach makes so much sense on paper that I'm convinced it's the future - we just need to figure out what's stopping people from making the jump today.

So what would it actually take to get you to switch? I'm all ears.

view more: next β€Ί