Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)JE
Posts
0
Comments
130
Joined
2 yr. ago

  • Adding on to a bit from your comment that I missed, it's not affecting the car itself. The article should have used the word "phone" instead of "device".
    All Android Auto is a screen for your phone that also hooks into car buttons. Your phone does all the hard work with projecting data to the screen. If your phone is too old, Android Auto might not work because apps don't work properly with the base framework by Google.
    You can use a new phone on an older car that officially supports Auto/CarPlay. That's never been a problem.

  • If you don't update Android Auto, maybe. Apps still rely on the framework that makes it work, so you are likely to have those break if they use features that Android Auto didn't have at the update freeze.

    The version they're cutting off is really old, relatively speaking. You have to be on Oreo or later (8.0+), which came out in 2017.
    Many apps you would use Android Auto will likely bump up to this break point soon. Waze, for example, is 7.0+. You're bound to run into issues being on Nougat or earlier soon, if not already.

  • Judging by the article and the code snippets found, it's more about updating your phone rather than the car infotainment hub. Nougat is getting the axe, have to be on Oreo or later.
    It would have been better if the headline said "phones" and not "devices", but that's not as panic inducing :P

  • Technology Connections makes very specific, detailed videos on tech stuff, appliances, etc. My recent favorite of his is about incandescent vs LED Christmas lights and his unending rage about LED lights looking like "a computer threw up on your lawn". The first I remember watching was about dishwasher tech and how great they are, but how terrible dish pods are.

  • Definitely listen to this. IP Warming is a very real problem and you have to send thousands of messages at a very gradual rate for most email gateways to 1) mark you as a proper email sender, and 2) classify you as a reputable one that isn't sending spam. Using a public/private cloud IP isn't enough, it should be a service already used for mail sending.

    If you self host sending email and ignore using a service for outbound, make sure it isn't at home. ISPs often block SMTP traffic to keep people from spamming others from their home. A lot of IP blocklists also auto block home IPs so you may not ever get your messages delivered.

    Make sure to set up SPF/DKIM/DMARC. At the very least SPF, DKIM if the platform supports it, and ideally all three or SPF+DMARC. It's not that hard to configure if you do it as you go instead of years down the line after you have a dozen services sending mail as your domain.

  • Turo for sharing cars. It's car rentals but weird since you're borrowing other people's cars.

    Kyte is in a similar vein for on demand cars via app, but it functions similar to a traditional car rental in every other way. Though they're a baby company so they might not be a good Uber comparison yet.
    My personal experience has been pretty good and the prices are very competitive, but we'll see how they survive when the VC money runs out.

  • I use the Outlook app for separating entities before I learned that work profiles were a thing and that my company has them turned on. Gives me different notifications I can control instead of all through Gmail, it's still sandboxed because O365 does the same containerization, and it also does calendar syncing.
    My only complaints are it doesn't handle password changes very well (have to completely re add my profile when it's time), and it is Outlook focused so it misses some Gmail features. This also doesn't solve your Google Meet problem, but at least it's two out of the three.

  • If you use plogons (xivlauncher), you can use IINACT as the parsing plugin and either HUDkit for a separate overlay program, or LMeter (this fork that's still maintained) for a plugin overlay. I use the latter perfectly fine on my Steam Deck and my Linux desktop

  • TSA changes up what they do each day. I just got back from a trip myself. On the way there, they didn't scan boarding passes. On the way back, they did. The guy even said they change things up to keep "the baddies" on their toes. Sometimes you don't take off your shoes, sometimes you do.
    Pre-check helps tremendously to make that the norm. No need to unpack electronics, no shoes off. Only thing they still do occasionally is the full body scan when randomly selected.

  • Our solution that we set up years ago was to connect a Shelly to circuits on a normal, dumb door opener. The Shelly triggers open/closed itself and since the signal comes from the opener, there's no crypto nonsense to figure out. It always works, no matter what MyQ/Chamberlain/LiftMaster do. Bonus, it also works if you have a very old opener.
    We also supplemented this with a tilt sensor so we know the state of the garage door. The door can still be cracked and not registered as opened, but that's a compromise we're okay with since we never leave it intentionally cracked.