

Not really. I haven’t worked with a TI mcu for a while so I can’t talk about their mcu docs, but their sections describing data exchanges between the IC and your mcu usually has a lot of ambiguity that needs to be clarified through trial and error.
Not really. I haven’t worked with a TI mcu for a while so I can’t talk about their mcu docs, but their sections describing data exchanges between the IC and your mcu usually has a lot of ambiguity that needs to be clarified through trial and error.
I am not sure if you are agreeing with me or not, but DOB and location where you were born are additional informations as I mentioned in my replie before.
You can guess a phone number as well by changing the last number, but that information has 0 value unless it is coupled with other informations.
I am not familiar with MacOS, but that seems like a nightmare. What is the purpose of these files?
I don’t even have to click the link to know what it is.
I haven’t laughed like that from a cartoon for a while. The guy is funny as fuck.
For me it’s 2 things :
Making a deck that works so well that it crushes everything.
Getting shit cards and making it works.
The first one gets me hooked, the second one keeps me going. It takes a long time to figure it out, as you put it.
I mostly play indie games, but I sometimes play AAA games (Ghost of Tsushima right now) and I am glad that I have my rig that can get 90 fps @ 4k (with fsr).
It’s not because you don’t use it every single time that you play a game that it is a waste of money.
//Todo: fix this bug in prod
Never realized that Etcher was an Electron app and it makes a lot of sense.
Yeah that was the issue. I though I had switched to my LTE network connection from my phone, but my phone was still on my local network.
Thanks for the answer
You are right and I should have been more precise.
I understand why docker was created and became popular because it abstracts a lot of the setup and make deployment a lot easier.
I hate how docker made it so that a lot of projects only have docker as the official way to install the software.
This is my tinfoil opinion, but to me, docker seems to enable the “phone-ification” ( for a lack of better term) of softwares. The upside is that it is more accessible to spin services on a home server. The downside is that we are losing the knowledge of how the different parts of the software work together.
I really like the Turnkey Linux projects. It’s like the best of both worlds. You deploy a container and a script setups the container for you, but after that, you have the full control over the software like when you install the binaries
I edited the post. Since it’s all local it’s fine to show the IP. It’s just a reflex to hide my ips.
I use IP directly as I don’t have a local domain configured properly.
The outpost ip in my configuration file is the same provided in the outpost on Authentik.
I am trying to get it to work still, but I am pretty sure that the issue is between Authentik and Firefly.
I don’t see any of the headers (x-authentik-email more specifically) specified in the caddy file when Authentik is sending the request to Firefly. The only header I see is x-authentik-auth-callback.
I am not sure how I can specify which headers are sent in Authentik.
Thanks for the suggestion
I am open to paid SMTP service if you have any suggestion. I was not planning on running my own instance.
Otherwise, what would be my options to have a functional SMTP server for Authelia?
Trump doesn’t give a fuck. He just want to stay out of prison for all the terrible things he did.
And greasy pepperoni
Just killed a man…
Not every domain though. I still see master/slave in every relevant datasheets that I read, and I’ve never seen primary/secondary in newer datasheets.
I work as an embedded developer and when a new board is produced and half tested, every one expects fully functional code off the bat, right away.
Motherfucker, you didn’t even qualify your hardware and you expect my code, that hasn’t hit the new board, to be 100% functional, based on your mind map? We will find hardware issues that will inevitably be blamed on the code and spend hours “debugging” the code to eventually find out the hardware is shit.