Fucking psychotic. These people have an actual mental illness, and they’re trying hard as hell to normalize it.

Nah, it’s not that risky if your tooling and process is solid. I have thousands of edge devices out in the field doing firmware updates on carrier boards from a specific manufacturer and have never had one fail or brick in update. Why? Because their tooling is absolutely fantastic and pretty bulletproof.

Even a simple {checksum>transfer>checksum>write>checksum} is pretty safe, UNLESS…you know the carrier you’re flashing doesnt have the ability to do so, in which case, you definitely put a warning like this on your product because you know it has a penchant for failure.

When they do this, they know they have a problem with their flash utils and process 🤣

I’d leave it alone.

Never seen that, and I build with hundreds of variants from all the big manufacturers. Haven’t seen that once in a PC, Laptop, or SFF.

Yeah, but it’s almost pointless to give an “if, then, elsif, elsif” scenario if just removing the battery does the same thing, and all motherboards have a battery for the CMOS.

Did you read that I was saying containers are bad somewhere? You have misread.

Flatpak for one: https://github.com/flathub/com.google.AndroidStudio

Android Studio isn’t just a simple app, nor a single executable, AND it maps out to a bunch of local sockets to your already running host to provide various services. Certainly not going to be easy or stable in a container, especially since they are asking about emulation as well.

Edited to a bit more. See my other comment.

We can’t see your house, to it’s hard to give you very many options except the simplest.

You will more than likely need more hardware though.

Repeaters don’t work, especially on newer Wifi clients. You need a proper Mesh system to cover a larger area. Probably going to run you $300-$500USD for a 3 AP kit.

You’ll need to put that junky AP they sent you from the ISP into Passthrough Mode, hook up the new AP from the Mesh system as your new router, then just place the other new APs in mesh mode as you want them.

If you have multiple other APs and some wires Ethernet ports in the house, you could switch those into AP Mode, plug them into Ethernet, and they’ll act as extensions of your main router as a hacky mesh as well. The problem with this route is that if they are all different WiFi versions and standards, you’ll get a bit of wonky behavior here and there, but it will work.

I’m confused by your question. Why would you need a container for this? There are other packages downloads for Android Studio. Container would be the most convoluted way of running it.

That’s just the difference between an LTS and everything else though. Debian is meant to be slow to release, battle tested, and focused on stability.

They’ve about a half dozen stupid decisions just in the past decade that has garnered the tarnish on their reputation. Trying to rationalize it won’t make the issues go away.

Note that this same hate sure isn’t going towards Debian.

Many in Urban areas will be fine for quite some time. Others with more space have already started adding EV charging, and increasing the presence of their convenience operations since EV charging customers will be at the properties a bit longer than normal gas fueling customers.

It’s just a pivot on their profit model and focus.

Most of the Linux support community is all handled in forums, though there are some development oriented chat spaces. If you’re looking for a place to just hang out and get live help, youre probably not going to find that.

That being said, the documentation for all distros is massive, and about as complete as you can get. That should be enough for most people, but I understand that not everyone is so technically inclined. I’ll hit some key points:

Most active: Probably Fedora or Arch Best Wiki: Arch first, Fedora second, Debian third, with others usually referring to the above Most active: Arch first, Debian second, Fedora third, with most Fedora comms happening in dev channels and issue tickets

In order to get help though, you need to get familiar with figuring out if your issue is with the actual distribution (it almost never is), the specific software you’re having an issue with, or a combo of both where the software has a configuration issue with the specific distro you’re running.

If you’re having a problem with Audacity on Fedora for instance, don’t go looking to the Fedora community for help, because it likely has nothing to do with Fedora. Go to the Audacity GitHub and search issues first, then start looking for specific information to your issue (error messages, logs…etc) next.

This sounds like you have beef with the developer.

What’s this post about?

Well, for the exact reason I said. Google ignores reference to anything without other corroboration. Hard or anchor links are necessary.

Fediverse content requires fluidity, and the same content is available at dozens of places. If they scrape the same post at different endpoint URIs, it will be discarded as spam.

This isn’t even news, it’s a known thing, and Google themselves described this in their SEO docs. No Fediverse instance is going to be spending money with Google to get a higher ranking, so it’s just kind of not going to show up.

Fediverse content is generally not indexed by Google because it’s doesn’t have predictable landing pages or site indexes. It moves and changes.

If something is shared enough on enough places and has enough anchor/hard links backs to something, it will probably show up.

To be real…kind of all of them. All the “smart” locks you see for sale are WILDLY insecure at the consumer level.

You are correct that almost all of them focus on the deadbolt, but look at something like this. I kind of hate this company, but they make components as well as entire lock systems.

I have no idea if they work with HA or not, just giving you a jumping off point to familiarize yourself with the options and terminology to have a deeper search.

Great episode, tho