Even if you need Id/scanner. If the check is at the elevator on the ground floor it may often as well not exist.
Even if you need Id/scanner. If the check is at the elevator on the ground floor it may often as well not exist.
I just carry my laptop with me while walking around during meetings.
The amount of reference material it has is also a big influence. I’ve had to pick up PLC programming a while ago (codesys/structured text, which is kinda based on pascal). While chatgpt understands the syntax it has absolutely no clue about libraries and platform limitations so it keeps hallucinating those based on popular ones in other languages.
Still a great tool to have it fill out things like I/O mappings and the sorts. Just need to give it some examples to work with first.
Those are some peak water polo nails.
I don’t think I’ve ever seen someone wearing cycling specific clothes for normal commuter trips. Other than maybe putting on a rain coat/pants over their normal clothing.
If it’s only you (or your household) that is accessing the services then something like hosting a tailscale VPN is a relatively user friendly and safe way to set-up remote access.
If not, then you’d probably want to either use the aforementioned Cloudflare tunnels, or set up a reverse proxy container (nginx proxy manager is quite nice for this as it also handles certs and stuff for you). Then port forward ports 80 and 443 to the server (or container if you give it a separate IP). This can be done in your router.
In terms of domain set-up. I’ve always found subdomains (homeassistant.domain.com) to be way less of a hassle compared to directories (domain.com/homeassistant) since the latter may need additional config on the application end.
Get a cheap domain at like Cloudflare and use CNAME records that point domain.com and *.domain.com to your dyndns host. Iirc there’s also some routers/containers that can do ddns with Cloudflare directly, so that might be worth a quick check too.
There’s a couple SD-WAN solutions out there that you can do this with. Essentially route all your traffic through one or more VPSes while still keeping things like port forwards and STUN working properly.
I’ve had to use it to enable proper video feeds to and from people that had Spectrum as their ISP.
There’s actually an HAI video on that. Those names were actually a direct result of an attempt by Amazon to curate their products better. https://youtu.be/_Bq-6GeRhys?si=ih1eyBLJwo7KAVuS
Chiming in a bit further on this. Quite a few (Google) devices and apps have started using DNS over Https servers to circumvent things like pihole. Blocking known IP’s on my firewall has helped effectiveness quite a bit.
Modding used to be extremely easy and detection systems weren’t implemented yet back in the day. I have an account with billions in cash just for being in the same lobby as one.
These days you’re still free to ruin everyone’s day with all sorts of griefing mods, but once you try and spawn in cash daddy rockstar gets angry at you.
Unfortunately that works less and less as "AI" continues to be more important in gathering results. Luckily there are other tricks like searching for pdfs only, exclude the 'corrected' words , or simply trying multiple search engines.
As someone that has to search for obscure hardware and part numbers on a regular basis Google's 'did you mean' is the bane of my existence.
I definitely rely on documentation more than copilot, since I've noticed that the code it writes is only ever as good as your own codebase.
Most of the stuff I code is API wrappers to get arbitrary data into a format our broadcast graphics system can understand. Once all the data structures are properly defined copilot is extremely useful in populating all the API endpoints.
The actual problem solving is getting the data in the first place and morphing it into the correct format.
I'm very much a novice coder, but I often find myself doing the opposite. Write a good comment and let copilot write the actual code.
For some reason every registrars dns panel has its own weird restrictions, bugs and interface quirks. Pointing the nameservers to Cloudflare at least makes for a consistent experience.
Linux is where a lot of the actually interesting stuff is, so I highly doubt they don’t have a bag of exploits for that.
Also fire departments, hospitals and other medical services. They’re extremely reliable, last a very long time on a charge and don’t shatter when you accidentally drop it.