They will try. This is about OS-level APIs. In order for a browser to to install and run PWAs, it needs certain OS APIs for e.g. home screen installation, storage and notifications. iOS currently has these APIs but Safari severely limits what you can do with it. Now the DMA will force Apple to accept other browsers, which have no such limitations. So, Apple now wants to remove these APIs altogether and kill PWA support outright, before that portion of the DMA takes effect.

There probably will be a lawsuit and Apple will probably lose, but it will take years to resolve that. And in the mean time PWAs remain dead and the only way on the iOS home screen in paying the 30% app store cut.

Yeah, I wondered about the ninth kid and how (s)he’s doing.

The people saying that are just pushing some other product in you.

Yup, I remember that 😄

43 years old here. I can still hear it. I think I put about 10-15 chargers in the bin because of the noise. I also really hate those anti-mosquito ultrasone emittors people put in their yards. I can hear them whenever I walk around the neighborhood.

I have a small collection of Lego sets. I mainly collect the minifigure-scale Star Wars space ships (yes, I have the crazy big Millenium Falcon), but only original trilogy ships. My wife collects the big Lego Creator cars.

Why not allow anyone to see the votes? Anyone already can by using kbin or spinning up their own instance.

That’s harder, but perhaps the new wifi 7 sensing can help in the near future.

Home Assistant can do that. Put a Shelly smart plug in the stove outlet to see if it’s using power (or do you have an old fasioned gas stove?). It can also track what time you turned off your lights last night.

I put a Shelly smart plug in my washing machine outlet. If it detects the machine using power for 30 seconds and then stop using power for 5 minutes, then it sends a signal to Home Assistant, and HA send a notification to my phone. It’s easy.

Home Assistant has a really good basic presence detection: wifi. If you phone is connected to your home wifi network, then you’re home. Else you’re away. Simple. Works. Local only. No extra sensors.

It’s not about clicks, it’s about attribution. That is also why they all want to track you. It’s not just about targeting ads. If you buy something in a webshop and the advertiser can show that you saw a (related) ad for that somewhere in the last X days/weeks then the sale is attributed to the advertiser and they get paid a fee. That is why they want to track anything and everything. The more data they collect, the higher the chance they can show attribution. No clicks required.

My guess is that you have Docker configured incorrectly. Its internal IP range probably overlaps with your real network, so all requests are routed to Docker. Uninstall docker and reboot the server. If that works, reinstall docker and properly configure its internal networking.

deleted by creator

Distro maintainers are a lot better about keeping libraries up-to-date than random application developers. They will even patch applications to work on newer libraries, even when the app developers do not.

There’s also auditability. If e.g. OpenSSL (or some other library) gets a high rated CVE and Debian ships a same-day patch, I know I am safe. I can verify that I have installed the patched version, and I know my applications use that patched version. Not with flatpak. Now I’m at the mercy of a dozen app developers, many of which probably value security less than the Debian Security team.

IMHO it’s a mistake for Fedora to drop its own packages for flatpak. But Fedora appears just to be a RedHat experiments playground these days, not a user focussed distro.

Don’t get me wrong, Flatpak is fine if you want to install stuff from Joe Random Developer off the internet, but I trust the Debian maintainers a whole lot more. If they ship it, i can trust it.

deleted by creator

Distro native packages are:

• Better integrated into the base system
• No maintenance for the devs (they are usually maintained by distro package maintainers)
• Better interoperability with other packages and dependencies, thanks to the package maintainers
• No duplicate or outdated dependencies
• More space efficient because they use system dependencies instead of packaging their own
• Launch even quicker since they don’t go through flatpak
• No missing or broken features due to flatpack limitations or sandbox issues (e.g. inter-process communication)

If an application is new or niche or small then flatpak is definitely a good option. But if there’s a distro native package then that one is almost always the better option. Flatpak is nice for when there is no native package.

Only install flatpacks if the distro repository doesn’t have the application in question. But I agree about snaps. Never ever use snap packages.

Accessibility

There’s a11y and l10n. What else is there?