There is also a rumor that said the OpenAI has changed how the model run, now user input is fed into smaller model first, then if the larger model agree with the initial result from the smaller model, then larger model will continue the calculation passed from the smaller model, which supposedly can cut down GPU time.
How can Apple got this wrong? Pretty much all meteorological data are sourced from the same set of weather forecasting data produced from running weather simulations on weather agencies supercomputers using satellites and ground observation data. The forecasting models will pretty much produce almost similar results when fed with the same data, which is why weather reports are usually pretty similar even though they’re produced by different weather agencies.
Does Apple actually run their own weather simulations here? Probably for their hyper local next-hour weather prediction feature? Or could it be that Apple is using some “AI” for their weather forecasting and the AI conjured some number out of its ass instead of running full physics simulation?
Man, I do miss those old dashboard widgets. Does this means we would get something similar back? If each space can have different widgets, that would be even better.
Oh shoot, I didn’t notice the retina part. On the flip side, the SSD is probably less likely to be water damaged.
Edit: looks like it’s a 2012 retina MBP, which means it has an SSD with property connectors. Check out this ifix guide on how to disassemble them and what enclosure you can use to mount the drive in another computer: https://www.ifixit.com/Guide/MacBook+Pro+13-Inch+Retina+Display+Late+2012+SSD+Replacement/12823
Those 2012 MBPs are using standard 2.5" SATA drives, so you can use any USB3 SATA adapter that supports 2.5" drives. Remember, always use USB3 sata adapter. Somehow there are still USB 2.0 sata adapters sold online right now, probably for legacy stuff so be sure to not accidentally buy them.
The drive itself is usually formatted in APFS partition, so you’ll need to connect the drive to another mac in order to use. If it’s encrypted, the encryption key is probably stored in the apple account associated with the broken macbook.
Your main concern is probably whether the disk got water damage or not. If the disk is damaged and unreadable, you’ll probably can still recover it by paying a data recovery specialist in your area. They’re expensive but can literally revives the drive as long as the platters are not damaged.
Good luck!
Also, need repeater to reach certain room in the corner? Just strategically place some mirrors and you’re golden!
I put my smart IR blaster behind my tv and it still works. It can even reaches the AC unit in my room if the door is open.
If you want some peace of mind, there is nothing wrong to keep your home assistant instance locked up behind your lan. You can still access it externally using a VPN, or zerotier/tailscale. If you need notification support, just configure sms or email notification so HomeAssistant can still send you alert via SMS or email.
If you’re ok with not being able to use HomeAssistant mobile app, then you can add some extra security by putting your home assistant instance behind an authenticating proxy. This means your home assistant will be protected by two login pages when you attempt to access it from outside your network.
Some authenticating proxy options are Cloudflare Access or OAuth2 Proxy.
If you’re already using Cloudflare, then using Cloudflare Access might be no brainer. If you’re already have experience with setting up your own OIDC providers using keycloak, auth0, okta, or Google oauth2 provider, then putting your home assistant instance behind OAuth2 Proxy might be a good option. Those auth providers usually have stricter login pages and you usually can add even stricter rules to the login page (e.g. disallow login from certain countries, rate limit, add captcha in addition to 2fa, etc). How strict your extra login security will be is entirely up to you.
For Google assistant integration, you’ll need to enable the API in your GCP account as mentioned in this page. But it does require your home assistant url to be publicly routable from GCP servers so Google assistant can reach it, which means you can’t put your instance behind an authenticating proxy or keep it behind your lan. You might still be able to whitelist certain path from the authenticating proxy (e.g. the /api/google_assistant endpoint), but I haven’t tried it yet.
I haven’t tried HA with NFC tags yet, but if I tap an NFC tag with my phone, it’ll show a list of app that can be launched to handle the tag. The phone need to be unlocked though.
Tailscale is a virtual lan network. When you enable tailscale, you’ll have an additional network and ip address in your connected devices. It’s not actually redirecting all your traffics there, unless you specifically configure it to do so (if you do so, you can designated a device as an “exit node” for your outbound traffic).
Security is a rabbit hole and you can go very deep depending on your risk model (an ordinary middle class people has different cybersecurity risk than, say, a CEO of a major bank). Let’s say you are an ordinary lemming that don’t have to be worry about being specifically targeted by a hacker group or a nation state, you just don’t want some botnets get into your network and take over your IoT stuff, I think the following is reasonable enough:
You can use Tailscale and Zerotier to access your local HomeAssistant from any devices connected with your Tailscale/Zerotier account.
But if you want to expose your HomeAssistant to public using a custom domain name, one way to do that is by using Cloudflare Tunnel: https://www.makeuseof.com/use-cloudflare-tunnel-expose-local-servers-internet/
It’s written using Symphony framework and seems to be using the latest best practice. Nothing to worry about here. PHP has its warts, which are being addressed since PHP 7.x. Modern frameworks like Symphony go even further by encouraging best practices when developing PHP WebApps, unlike the dark old days of PHP WebApps full of SQL injections and XSS issues (still is though in the WordPress plugins ecosystem).
I’m mostly a Python guy and used to look down on PHP, but changed my tune since the release of PHP 7.x. If Python has JIT half as good as PHP these days, I would die happy.
Investors: shut up and take my money!