[–] 38 points 11 months ago (2 children)

It means you're not a man, you pussy!

...it also implies that "being a man" is not determined by your birth, but rather by your decisions and lifestyle, and that everyone is in fact gender fluid and able to change their gender at any time.

So basically, toxic masculinity is actually woke as fuck

  • source
  • parent
  • context
  • [–] 3 points 11 months ago

    I don't like this. Flatpaks are a huge step forward, but Fedora Flatpaks are two steps back. I'm not at all convinced by his arguments here or in the rejected proposal.

    The only potential benefit that might make sense is that they will contain the same Fedora-specific patches found in the fedora RPMs... Except that is exactly the type of thing Flatpaks were supposed to prevent! Neither users nor developers want a middle man adding or removing features for their software. It has historically been one of the biggest pain points for migrating to Linux as a user, or supporting it as a developer. It was necessary in the past for compatibility reasons, but Flatpaks fixed that. Now, developers can publish one Flatpak that will work on all distros, and users don't have to wonder if they'll be able to use some app or not, or whether it will work... Unless they're on Fedora

    But I don't like this post nor the wording in the proposal. He doesn't actually outline why he wants this to go through. I'm not claiming any tinfoil hat conspiracy behind the scenes, it's just his argument is not well articulated. If someone wants to use an app with Fedora-specific patches for some reason, they can layer the RPM on top of their Atomic distro. There's no reason to add uncertainty and confuse users by turning those into flatpaks.

  • source
  • [–] 8 points 11 months ago

    If you already know cron and are too lazy to learn something new, then use cron with the knowledge that it's a personal failure and not a real technical decision... Otherwise, use systemd timers.

  • source
  • [–] 15 points 11 months ago (3 children)

    I know nothing about what it takes to develop a laptop. Are these issues (BIOS updates, virtualization support, USB4 support, etc) something the laptop manufacturer needs to develop solutions for in-house? Wouldn't that be the job of Qualcomm? Or are Tuxedo saying that these things aren't supported on the Linux side yet? Qualcomm claimed to be contributing to the kernel last year, so idk if that just hasn't happened yet or if they just lied.

    Either way this is disappointing, but understandable. There's no sense in working to release a laptop with previous-gen hardware that's not going to be competitive.

  • source
  • [–] 5 points 1 year ago (1 child)

    More devs need to start doing AGPL with other licenses available for a licensing fee. Or better yet, price it based on revenue with the LGPL/GPL/Apache version free for orgs under $1bn annual revenue, and everyone else has to pay up.

    The OSI was a mistake. They were wrong, Stallman was right. How long until open source devs finally accept this?

  • source
  • [–] 1 point 1 year ago

    It doesn't matter. It's a rumor that one US president sucked off another US president, except there's a sliver of credibility in it. It's one of the least likely things imaginable, yet here it is showing up in a context where you can't just completely dismiss it as an obvious shitty joke. This is probably going to become one of the most iconic and significant memes in American history, even if it turns out to be false. Our great grandkids will be joking about it in their locker rooms.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago

    Damn those headphones you have are from the pre-enshitiffication era. Cherish them!

    The headphones work without the app fortunately, but you need it to control EQ settings, isolation settings, and install firmware updates. They're kinda like the shitty software that PC gaming peripherals ship to control LED colors or whatever.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (2 children)

    I'm using "Bose QuietComfort Ultra Headphones" manufactured in 2024, according to the app. I can't find any model number, but I just looked up the order in my email and it turns out I've actually only had it for a little over a year, and the price was a ridiculous $380. Luckily, I only ended up paying around $200 because I had reward points with the vendor, but I would definitely not recommend these to anyone at $400. At $200? Maybe, but I wouldn't buy it again at that lower price.

    My ears fit in the cups, but they still get tired sometimes after wearing them the entire day. Idk what to tell you, I guess my ears are too big and brush up against the inside of the cups? It's not a real issue for me, and doesn't happen often, which is why I didn't even mention comfort as being a problem.

    Do you really not experience any of the software issues I mentioned? The Bose app even says I'm on the latest firmware version.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (4 children)

    I actually have been using those Bose QC over the ear ones for a few years now (and I already had to replace the pads once), and they're not great. IIRC I paid like $300, and they're definitely not worth that much. I'm not that picky about sound quality, but the UX is terrible. Powering it on is a crap shoot. Sometimes you press the button, and 5 seconds later it plays a sound to indicate it turned on. Sometimes it takes 10 seconds, sometimes more. Sometimes it doesn't even turn on, and you just sit there doing nothing waiting to see if it decided to turn on this time, or if you have to hold the button for ~30 seconds to get it unstuck. Sometimes that sound that plays when powering on even gets interrupted by the bluetooth connection notice. Sometimes, it gets stuck in a loop switching between sound isolation modes, just endlessly saying "Aware. Immersion. Quiet." until you intervene.

    It's also hard to simply wear them around your neck when your ears get tired and you just want to use them as tiny speakers. This is for two reasons. First, the placement of the physical buttons on the side of the cups means that they will accidentally get pressed when the cups collide (which will happen when you wear them around your neck). Second, they will constantly pause whenever they get close to your chin, as they'll think you took them off your head. That part is overly sensitive, and they were too cheap/lazy to add a simple sensor to detect the rotation of the cups to know when they're not being used over-ear.

    And finally, the battery life is not good enough to last an entire work day, so you'll have to connect them to power... except, for some reason, connecting a usb cable to charge causes it to shutdown immediately. You can use them while charging, but you have to power them back on/reconnect them after connecting the cable, which means you have to play the annoying waiting/guessing game again with the power button!

    I have other complaints, but whatever. When they're working, they're fine, but I'm probably done with Bose. These little issues on such an expensive product left a bad taste in my mouth. I don't know how Sony's over the ear headphones compare, but the in-ear ones I have are amazing simply because they work as intended 99% of the time without any of this kind of bullshit.

  • source
  • parent
  • context
  • view more: ‹ prev next ›