Developer by day, gamer by night!

🖥️ Stack: #NodeJS #Flutter #Go

🐧Linux: Currently on #Fedora

🎮️ Games: #ApexLegends and #Chess

Fun fact: Built my own custom keyboard, which sometimes doesn’t work and hangs, but hey… it still adds to the charm, right 😂

  • 15 Posts
  • 121 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle










  • oh… it’s a game where every day there’s a 5 letter word you have to guess.

    you start with a random word and it shows you if the letters are in its corect place (green), wrong place (yellow) or they don’t occur at all (gray).

    then you keep on guessing until you find the word or reach the limit.









  • in a nutshell

    This is how the control and information exchange of smart devices work:

    Phone App -> [Server] … [Server] -> Smart Device and vice versa

    There’s no way around this concept.

    Now, Google gives you the phone app and the (public) server part. but these only work with their servers and apps, keeping you locked in.

    HA gives you the same, a server and an app, but allows you to keep the server private (access via vpn for public)

    Also who guarantees that Google Home will be there in the next few years? HA will still keep running even if it ever gets abandoned.




  • Authelia is meant to be an SSO (like Google). In order to use it, you have to create users (and passwords) within the authelia yaml file, or connect it to light-ldap and do it via ldaps web gui.

    You probably have other services running, i.e. immich, etc. These can be configured to use auhelias OIDC to authenticate the user against. you’d still need to create the users within the service, since I doubt they get auto-created.

    Now, you can decide for yourself, whether to put your bitwarden behind authelia or not, and I’m not sure how the mobile apps work in this sense, if at all.

    If you decide to do so, you just give your users their authelia/lightldap creds, if not, you additionally have to give them their bitwarden creds.