The problem is that breaking it will also break a lot of Apple devices.
/g
Thanks, though your correction is also incorrect. Display managers, like SDDM, GDM, or LightDM, are the login screen. They’re called “display managers” for historical reasons, but they also run on top of the display server.
Display servers, not window managers. Window managers are built on top of X11 or Wayland.
Wayland is a “display server,” which basically means it manages the way GUIs show on the screen. X (most recently X11/Xorg) was the standard for over 30 years, but it was designed for computers 30 years ago. Modern concepts like scaling and high refresh rate displays need extensions to it, but it’s really complicated and hard to work with, so a lot of improvements that need to be made can’t be made. It’s also fundamentally insecure, as every window has access to both the contents and the input of any other window. Wayland is a modern replacement that focuses on security and expandability, and basically everything is working on switching to it. There are growing pains, but it’s constantly improving, and most distros use it by default now.
Chrome OS makes installing Linux applications way more difficult than it is on most other Linux distros.
Chrome OS makes installing Linux applications way more difficult than it is on most other Linux distros.
Be extremely careful. Plenty of people are really smart and malicious, so you need to isolate it from everything on your network. You’re giving random people remote code execution on your local network, which is like the worst case scenario for security.
If you’re rooted, you can use Pixel Launcher Mods (or Pixel Launcher Extended, which includes Pixel Launcher Mods). It themes all of them but Libro.fm automatically, and you can easily add an icon for anything missing (either making your own or using one from another app).
Of what? A lack of Internet-connected devices? Probably. The universe? Probably not.
Can’t you carry their phone?
That’s not really possible. With such a wide-ranging standard as USB-C, the cable needs to report what it can support. Without E-marker chips, for example, there would be three possible results: no cable can charge quickly, every cable is thick, short, and expensive, or cables catch on fire frequently. Cheap cables that don’t support all of the extra features are just cables, but the good ones need to let the computer know what they are capable of.
iPhones.
So they figured out that a $130 Thunderbolt 4 100W E-marker cable is better designed than a $10 USB 2 60W cable? I think they should have looked at a cheaper high-end cable, like a 240W Thunderbolt 4 cable, to see how a comparable one compares.
In my opinion, phone cameras are usually used to capture a memory, not a moment. Memories are idealistic and inaccurate, so I don’t think it’s a problem that a way of “storing memories” is also inaccurate.
Zigbee, Z-wave, and Matter all should work, but they need special radios that require extra hardware on your server (except sometimes Matter—some devices use WiFi, while others use Thread, which is based on Zigbee). SkyConnect gives you Zigbee and Thread. Homekit usually works too, but at this point it’s better to get a WiFi Matter device. Anything running ESPHome will work automatically. Athom has a lot of products that are preflashed with ESPHome, so the firmware is designed by the same people that make Home Assistant.
What I usually do is tell the Play Store to not update it. Also, I don’t think it’s that involved. Take this with a grain of salt because I’m pretty experienced with phone modification, but I think it’s just downloading the file, opening it, selecting YouTube, choosing what modifications you want, and installing it.
That’s odd. That’s really dumb for those third-party technicians to take that, as (aside from the damage to their reputation and simply not being a good person), it would probably be a degraded battery anyway. Being constantly plugged in is very bad for a battery.
.ovh domains are like $2/year, if that helps.