russjr08

No worries at all! I battled with that choice for a while when I was self hosting. I had already been so deep into using GitLab CI that it would’ve been a pain to migrate to Forgejo Actions, though to be fair when I had setup GitLab the Actions system didn’t actually exist yet.

And if you plan to expose it to the Internet, GitLab being a much larger project has more potential security issues to keep up with which is another important note.

(Though as always when publicly exposing services to the Internet, keep up with patches either way and stay safe!)

Depending on what your needs and available resources are, GitLab is fairly heavy especially in comparison to Forgejo.

Well, someone is certainly not having a Happy New Year heh.

Meanwhile others are absolutely over the moon celebrating 🎉

I’ve been using Google Fi for the last few Pixel phones I’ve been on. Each time I’ve switched, during setup I just get asked if I’d like to activate the phone (with a warning that my old one will be deactivated) and I click yes. It’s then active before I can even complete the phone’s OOBE setup.

Android also does apparently have a “copy to another device” function mentioned here, but they hint to what you said regarding carrier limitations applying. Though Apple’s quick eSIM transfer has a similar note as well.

Definitely seems like a “When it all lines up, it can be convenient, but when it doesn’t you’re fucked” situation.

I very rarely used to, and now I absolutely don’t ever since I pre-ordered Anthem…

Supposedly the compatibility is via a Wi-Fi spec that Apple was forced to switch AirDrop to which likely means that support for the spec needs to be implemented on the actual chipset.

This is a bit out of my realm of knowledge, but that would be my assumption. Kind of like BLE when that first became a thing.

Do you mean the call screening feature that Pixels have? When my Pixel does a call screen, it does announce to the other user that the call is being recorded.