Skip Navigation

Posts
2
Comments
157
Joined
5 yr. ago

  • Same. I started really using Linux with Ubuntu 6.06 and was drawn in by its "Linux for human beings" goals - the Ubuntu homepage of the era really pushed the ideals of community and openness. Canonical sat in the background paying to send you free CDs in the mail. It was such an idealistic thing back then.

    And then it all changed around 2010. The color scheme shifted to a shitty MacOS lookalike, the human elements were dropped, the logo was reworked, it got bundled with a paid music store, then Amazon ads in the search, and it's been a roller coaster on a downward spiral ever since. I switched to Debian not long after the initial enshittification in the early 2010s and have not looked back, though I moved most of my systems to Arch a few years back because I like life in the fast rolling release lane and Debian wouldn't support my new GPUs.

  • Driver installation is really only a hassle for NVIDIA users. AMD and Intel GPUs simply work out of the box on most Linux distros these days (with the main issues being related to using slow moving distros that lack support for the newest hardware). Use a fast moving distro such as Arch and you likely won't have any issues even with recent GPUs. Hopefully NVK will make the situation for NVIDIA cards better too, been testing it on my laptop and it's starting to be viable for gaming.

  • Any dating app where both people have to "like"/"swipe right" each other should allow either side to initiate tbh or at least opt out of the stupid matchmaking system and accept all incoming matches.

    I was on the dating apps last summer after having been out of the dating pool for 6 years and the current crop of apps are pretty awful for men (amd probably women as well, maybe for difderent reasons). When I used dating sites in the early/mid 2010s most sites let anyone initiate a conversation so you didn't need to worry about the (usually paywalled) "like" system. These days literally everything is a Tinder clone and the only interaction you have with the app is like or dislike. I get why they did it because women receive so much bullshit from unsolicited messages, in my experience it devolved into just mashing the Like button over and over again blindly because it's a shitty numbers game and the odds aren't in your favor. There's no sense reading through detailed profiles and making thoughtful decisions when it's rare to get a match anyways. Easier to like every single profile and then be the one to filter out matches once they come in. If the harassment is going to primarily target women and women are the ones who need to be more selective in their matches, the dating apps should let women be the ones to pick matches, or better yet give each and every user a toggle that lets them accept matches from anyone, because that makes it easier to get over the hurdle of not receiving any matches at all.

    I eventually gave in and paid for the Tinder upgrade that lets you like an unlimited amount of times. I just mindlessly mashed the like button until the queue was empty every day. Before long, matches were actually happening. Two months into that nonsense I actually got a perfect match (she sent the first message) and we've been together for 6 months now. I absolutely love her and I'm glad it worked out, but damn was dating on Tinder, Bumble, OKCupid, and POF a horrible experience all around. All owned by the absolutely dreadful Match.com now of course. The prospect of your perfect match being hidden behind a stupid loot box RNG style gacha system is absolute insanity, because that's what it is. You have a limited number of likes and the profiles you get to see are seemingly picked at random.

  • CentOS good (after they betrayed open source) but Debian bad (even though they remain one of the more independent from corporate influence distros and also serve as the upstream for over half the list)? What even is this nonsense? I agree Ubuntu and its official derivatives maliciously bad and Manjaro completely pointless but that's about all I agree with.

  • How do sodium ion batteries help here? Driving into the wind and running your electric heater at full blast aren't a battery issue, it's just an unavoidable increase in power consumption that you need the extra capacity to deal with.

  • I would say we're beyond the era of PC referencing the classic "x86 IBM Personal Computer compatible" definition. PC could reasonably be considered to include many ARM systems, considering there are now Windows laptops shipping with ARM processors that can run "PC" software. Besides, most new x86 PCs aren't IBM PC compatible anyways as legacy BIOS support has been dropped by a lot of UEFI implementations. I would consider any device that runs a desktop style OS (be it Windows, Linux, or even MacOS) a PC. The distinction in my mind is specifically mobile vs. desktop. Android and iOS are not PC. They're primarily touch driven and apps are restricted to a certain format with a centralized app store where you are expected to get all of your apps. Windows/Linux/MacOS are primarily keyboard and mouse driven and you have a lot more flexibility on acquiring new apps, with their forms of "sideloading" and "rooting/jailbreaking" being things that are just normal and accepted rather than workarounds/hacks to break out of the walled garden. I would also go as far as saying a smartphone can be a PC if you have a PC like OS on it, such as mobile Linux OSes that let you run desktop applications.

  • Range anxiety isn't about your daily commute, it's about the few times a year road trip you make across multiple states to see family on holidays. Having to stop and charge every 150 miles (as I wouldn't trust letting it go below 50) sucks if you're trying to go 500+ miles. Owning a gas car taking up space in your garage and costing you taxes and registration just to use a handful of times a year is wasteful. Renting a car is an option, but it's cumbersome and if you plan to stay a while, expensive. I would not want an EV with less than 300 miles range. You have to factor in worst case scenarios as well, sometimes it gets dreadfully cold and windy in the winter. When it's -10F and the wind is howling you're cranking the (usually resistive) heat and driving head first into the wind kills your efficiency. These are real scenarios I have had to drive in my current car (Volt, so plug in hybrid) and my battery range can be halved (from 35+ miles under 20) in these worst case scenarios, but at least I can fall back on gas. I want to go EV for my next car but if I can't reliably make it to and from my parents' house 300 miles away on a bad winter's Christmas break then it's just not a feasible option yet, even if my drive to work is maybe 15 miles round trip. Also, charging station density is an issue. I would need to go half way to their house, 150 miles, to reach a charging station. You can't just stop anywhere to recharge if you have a low range EV.

  • I want a phone that:

    • Calls - Must support VoLTE, preferably VoWiFi, audio quality has to at least be listenable but I rarely use calls for anything other than authenticators
    • Texts - MMS not super important, I only use texts as a last resort
    • Data
    • Waydroid support (mainly for the Discord app, possibly Teams for work)
    • Browser for most other services
    • Desktop Linux applications on-device
    • Good camera, doesn't have to be the best but it needs to have one
    • Lots of local storage, preferably expandable
    • Connectivity (USB-C with video out support preferably)

    I already have plenty of ways of running desktop applications on big screens. I have a laptop, I have a desktop, I have a Steam Deck. However, my phone is always on me and those devices aren't. Linux phone is awesome because I can always have the applications I need literally in the palm of my hand, and if not they're just an apk or flatpak install away. I've been working on tweaks and utilities to make the experience of using desktop applications easier on mobile Linux, including a virtual mouse using the touchscreen and now working on a Phosh plugin to quickly change screen scaling. A pocket keyboard accessory would make using said desktop applications even easier. I've done quite a bit of coding, compiling, and dabbled in image editing on my mobile devices.

    My daily driver phones at the moment are a OnePlus 6 running stock Android (because Linux isn't quite 100% yet) and a OnePlus 6T running postmarketOS. I got a cheap Mint SIM in both phones. Android phone for my calls, texts, camera, and occasional Google apps (mainly maps) usage. Linux phone for everything else, mainly my pocket computer on the go. I used to carry the PinePhone with keyboard, but even with the keyboard case the battery life was awful and it got super hot and it was slow. The OnePlus 6T with pmOS gets surprisingly good battery life. I can't daily drive the 6T due to the lack of VoLTE, which means calling falls back on the 2G network which they are shutting down very soon. Luckily, someone is working on reverse engineering VoLTE bringup and released a proof of concept daemon to enable it. I've successfully made VoLTE calls but it doesn't always enable and audio sometimes breaks.

  • The domestic social media companies are at the whims of the billionaire class which I would argue is just as bad for voter influence. Neither side wants you to vote in your best interest.

  • I have seen the GPD devices before and if they were a bit smaller (phone sized) and had cell capability maybe that would be a good option. As is, they are not small enough to be in a separate category than the Steam Deck IMO, and I already have a Steam Deck. I also like the idea of the keyboard being detachable as sometimes the phone form factor is desirable, like when holding it up to your ear.

  • While I'm not a fan of advertising or marketing in general, brands having a presence on the Fediverse would be great for Fediverse adoption, and sometimes complaining about a brand on social media is needed to get proper customer service in this world of AI and bot controlled customer service channels. I can see this being a good thing, and there are some brands/companies I would likely follow. I already do follow a few who are on Mastodon, such as Framework, Pine64, and Raspberry Pi.

  • As a user and not as a government agent, why should I care? If anything, having a foreign government hoard my data and spy on me is better than the government that actually has jurisdiction over me. If I were posting things critical of my own government I would rather have a foreign government hoard that data than my own government. There's a lot more of a chance that US data hoarding leads to action against US citizens than Chinese data hoarding.

    I don't see how this benefits average Americans in any way. This helps the government and corporations.

  • I have some of those tiny keyboards, but the PinePhone keyboard case is far more convenient to use as a mini on the go PC than a separate keyboard. If such an all in one option existed for more powerful hardware it would be amazing. I love the idea of a phone that doubles as a true pocket laptop including connectivity options.

  • I would like a phone that has a removable battery, user replaceable screen, and expandable storage. I think Framework would do well to add one or two of their modular slots on the phone since phones already have USB-C support. I would also love to see a phone keyboard similar to the PinePhone keyboard case but using USB-C instead of I2C. Such a case could also incorporate a USB-C dock, providing more Framework module slots or at least additional USB ports, video outputs, an extended capacity battery (using USB-PD to charge itself as well as the phone), and of course also being a tiny keyboard clamshell that fits in your pocket. It could also be nice if the phone could easily detach from said case for taking calls, as the PinePhone keyboard replaces the back cover and does not separate easily when needed.

  • A Framework phone with 2 modular Framework sockets would be amazing. I don't care if it's thick. Make it repairable and support Linux Phone OSes like postmarketOS and I would absolutely buy it.

  • Squeekboard is where it's at. By far my favorite onscreen keyboard for Linux and mainly because you can easily create your own layouts using .yaml files. I'm tired of virtual keyboards that omit keys needed for development and terminal use or shove them off to separate tabs. My custom Squeekboard layout fits my needs exactly and I'm pretty fast at typing on it (typing this on it now). I wish it were usable outside of Phosh, though tbf I haven't tried. Between GNOME Mobile, KDE Plasma Mobile, and Phosh (Squeekboard), I choose Phosh primarily because of how much I like Squeekboard.

  • Except that in the case of VGA (and DVI, HDMI, and DisplayPort) the i2c interface is intended for use over the cable. All of those ports have a pair of i2c pins and corresponding wires in their cables. The i2c interface is used for DDC/EDID which is how the computer can identify the capabilities and specifications of the attached display. DDC even provides some rarely-used control functionality. Probably the most useful of which is being able to control the brightness of the display from software. I use the ddcci module on Linux and it lets me control my desktop monitor brightness the same way a laptop would, which is great. I have no idea why this isn't widely used.

    Edit:

    This i2c interface is widely used to control the lighting on modern graphics cards that have RGB lighting. We've spent a lot of time reverse engineering these chips and their i2c protocols for OpenRGB. GPU chips usually have more i2c buses than the cards have display connectors, so the RGB chip is wired to one of the unused buses. I think AMD GPUs tend to have 8 separate i2c buses but most cards only use 4 or 5 of them for display connectors. There is also an i2c interface present on RAM slots normally used for reading the SPD chip that stores RAM module specifications, timings, etc. This interface is also used for RAM modules with controllable RGB lighting.

  • Yeah, the lack of proper discoverability on i2c truly sucks. You have to just poke random addresses and hope for the best to see if an i2c device exists on the bus. It's a great standard but I wish it would get updated with some sort of plug and play autodetection feature. Standardized device PID/VID system like USB and PCI would be acceptable or a standardized register that returns a part string. Anything other than blindly poking registers and hoping you're not accidentally overvolting the CPU or whatever because the register on your expected device overlaps with the overvolt the CPU register on the same address of a different device.

  • I mean, the open source driver already is out. The nouveau driver has been in the kernel for like a decade now. The userspace part has been in Mesa for just as long, though largely was unused due to nouveau not being able to use high clock speeds. That isn't the case anymore, and since the beginning of the year you've been able to test drive the new NVK Vulkan driver on nouveau with GSP enabled to get actually reasonable performance in several select games. NVIDIA isn't creating a new driver, they're contributing to one that already exists. Since this particular patch set is so huge I don't know it will make it into the next kernel release right away but this guy was the former nouveau maintainer, I expect he knows the necessary standards to get his code accepted.

  • Just fitting objects into the smallest box isn't everything according to the article. This is trying to identify fragile objects and recommend appropriate protective packaging where required to minimize the risk of damage in shipping. If you use a conventional packing algorithm to pack dishes and vases into the smallest box you will receive a box of glass shards on your doorstep. Is AI the best solution? I'm not sure, but using actual statistics of damaged goods and their means of packaging sounds like a worthwhile consideration.