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.
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.
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.
Behavior-based antivirus is extremely difficult, failure-prone, and almost entirely unnecessary because of how secure Linux is, so they don’t exist to my knowledge. Signature-based antivirus is basically useless because any security holes exploited by a virus are patched upstream rather than waiting for an antivirus to block it. ClamAV focuses on Windows viruses, not Linux ones, so it can be a signature-based antivirus, but not many people run an email server accessed by Windows devices or other similar services that require ClamAV, so not many people use it, and nobody made any alternatives.
If you’re worried about security, focus on hardening and updates, not antiviruses.
Heat difference is what you can get energy from, not heat itself. You need something cold to get energy from the heat.
A .ovh domain is more like $3 a year. That’s what I’m using.
EMS doesn’t support bridges unless you pay for the highest tier, but the list you linked is good.
etke.cc does that.
This may not fit your needs, but matrix-docker-ansible-deploy is really good, and it uses Docker and Traefik by default.
At the very least, if Framework dies, many of the parts are standardized, and the ones that aren’t are mostly open source. The SSD, RAM, WiFi card, and screen connector are all standardized. The expansion cards use USB-C and have an open-source shape; many people have already made third-party expansion cards. The motherboard has an open-source layout, and there are open-source CAD files to make custom enclosures (again, people have already done it). There are general schematics with pinouts on their Github, and they’ve provided exact schematics to repair stores. If they die, you end up with a laptop that is more repairable than almost any other, as well as a community with enough information to keep it alive if they want to.
It’s not just a “missing Apple logo” that makes parts not work. If you swap a part from one Apple device to another identical Apple device, it will often not work. For example, the Face ID and Touch ID sensors are paired to the logic board.
Don’t buy HP laptops. They’re terrible. Framework is great, and Lenovo and Dell are generally pretty good. Put Linux on it if you care about privacy.
Correct. What you’d need in that case is a reverse proxy like ngrok, which is a bit more difficult to set up.
.ovh domains are like $2/year, if that helps.