HackerTrans
トップ新着トレンドコメント過去質問紹介求人

intangible

no profile record

投稿

Using a Shelly 1 as a garage door opener with Home Assistant

trstn.com
1 ポイント·投稿者 intangible·3 年前·0 コメント

コメント

intangible
·5 か月前·議論
Hey, you were the one who said you were confused - it sounds more like you've already made up your mind and don't want to hear otherwise.
intangible
·5 か月前·議論
If you were already experienced and productive, it does very little for you beyond summaries, a little boilerplate, and possibly search help.

If you were unproductive, it allows you to be more "productive" while stalling or reversing your learning and growth.

Of course, person number 2's newfound "productivity" comes at the expense of leeching productivity away from the experienced and productive people by overloading them with reviewing and validating their non-deterministic generated spaghetti.

It amazes people who think pumping out code is the hard part of a project, when in fact that's the easiest part...

We've apparently collectively forgotten that lines of code is one of the worst metrics for measuring productivity.
intangible
·5 か月前·議論
Google ripped away the functionality to access your original Google Photos files via any programmatic method vs the manual Google takeout.

This was the biggest reason I also had to move away from Google Photos when all I really wanted was protection from getting my account accidentally G-structed with zero way to contact a human to get my files back.
intangible
·6 か月前·議論
If only Trump had 4 years to do anything other than kick the can down to road yet again like every prior president.

Biden took the political hit by doing the right thing and ending the war - No prior president did that.
intangible
·3 年前·議論
I think Mercedes is the only company willing to take liability for their self-driving features. https://www.theverge.com/2023/9/27/23892154/mercedes-benz-dr...

If your Tesla crashes while using FSD, it's completely your fault, according to them.
intangible
·3 年前·議論
It's difficult to say if the person is recoverable, but as long as you continue chest compressions without major interruptions, some blood will continue to circulate and should mostly stave off irreversible brain damage. Even without rescue breaths, there's a massive benefit https://hsi.com/blog/are-rescue-breaths-necessary-during-cpr
intangible
·3 年前·議論
I wouldn't really treat it as a replacement for a NAS, mostly only for the container workloads running on kubernetes itself... Ideally, any apps you develop should use something more sane like object storage (Minio etc) for their data.

I push it pretty minimally right now, so no great performance testing myself, and I do run it in synchronous mode, so that means its write performance is likely going to be limited to the 1gbps network it syncs over.
intangible
·3 年前·議論
I've been using a 3 nuc (actually Ryzen devices) k3s on SuSE MicroOS https://microos.opensuse.org/ for my homelab for a while, and I really like it. They made some really nice decisions on which parts of k8s to trim down and which Networking / LB / Ingress to use.

The option to use sqlite in place of etcd on an even lighter single node setup makes it super interesting for even lighter weight homelab container environment setups.

I even use it with Longhorn https://longhorn.io/ for shared block storage on the mini cluster.

If anyone uses it with MicroOS, just make sure you switch to kured https://kured.dev/ for the transactional-updates reboot method.

I'd love to compare it against Talos https://www.talos.dev/ but Talos's lack of support for a persistent storage partition (only separate storage device https://github.com/siderolabs/talos/issues/4041 ) really hurts most small home / office usage I'd want to try.
intangible
·3 年前·議論
Another really nice Immutable Linux system that I'm using is VyOS.. It's targeted primarily at a router OS, but you can run containers on it now to make it pretty versatile.

Basically, it's an image based OS that configures everything from a single config file on boot. https://docs.vyos.io/en/latest/introducing/about.html