To be fair, they supported two different git backends, one of them being go-git which was the one corrupting repositories. However, it was never enabled by default, you specifically had to build Forgejo with a specific tag to instead use that as the backend. If you just built normally or pulled ready-made containers or bins then it was always the default git backend.

I’m just confused why this has annoyed users just NOW since the button has always existed. It was just a down-pointing chevron before it got changed to a new icon so it’s not like it suddenly popped up and took space away

Just in case somebody only reads the title and wants to ready their pitchforks:

And to reiterate a couple important points we’ve communicated in our previous updates published in March and May:

• The webRequest API is not on a deprecation path in Firefox
• Mozilla has no plans to deprecate MV2

Agreed! On a Lenovo Yoga Slim 7 X, I also had a big, big boost of battery life. It’s really great how far it came in comparison to a few months ago!

That’s the solution if you immediately tried to login and it didn’t work.

Twitch login has in general very misleading error messages. The exact same message with unsupported browser also appears if you take too long to login

As far as I know, since 2019 the Hue bulbs or lights are Zigbee + Bluetooth. I haven’t heard of a Bluetooth-only bulb yet

Since the Hue bulbs are using the Zigbee standard, you can still safely buy them in the foreseeable future and just connect it with something like SkyConnect, zzh!, Conbee, etc. and use it with Home Assistant

Linux can be run on an Nintendo 64. Mainline Kernel support has been added in v5.12

What you could do is have one of the HAs install the custom integration remote-homeassistant. However, even then it would mean that you have to somehow make your instance available outside e.g. VPN, port forwarding, cloud service, …

This one connects with the instance directly via a long-lived token and allows you to control and read date from the other instance. The good thing though: The configuration.yaml way allows you to specificially include or exclude entities. So with that you could technically only send the entities from slimmelezer+ without having to pass the other info.

I would say the only caveat would be that because the long-lived token is somewhere on the other house’s instance, they could technically take it and send commands randomly to your instance :P Maybe with an extra user you could maybe limit the permissions or something similar and create the long-lived token there - haven’t tried it though, just a thought.