having a hardware configuration that is easily repeatable, with software that is standardized, and apps that require no additional configuration after installation on known hardware, should push past a friction threshold for some that want privacy, but can’t manage the full hardware and software stack themselves.
Eventually, this should have multitudes of apps, including home assistant apps, although today, it’s more of a demonstration of an end-to-end pipeline that enshrines the users interests above all else.
I’m building something to give away I hope others will replicate, and contribute.
if you are going to use insets to show close-ups they should at least be real close-ups. the way they are now they are barely any bigger than they are with you in the shot. the focus should be the close-up not you.
you should also provide a link to the video somewhere else since I needed to pause the video halfway thru (after the way too long portion of assembling the enclosure) and then when I tried to restart it something failed and now I can’t watch the rest of it. So that first 25 minutes was a complete waste of time since it never even got into the potentially more useful/interesting software portion of the video.
is there somewhere else besides the embedded video here that I can watch it and I can scroll thru so I don’t need to rewatch the first half again?
other than that I can’t comment on the rest of your concept.
As said earlier the videos of the device should be full screen and then you can be in a smal window instead, if there should be window with you at all.
You need to rehearse the video a lot more, so you know what you do and what you need to say and why.
I do not think you ever said why you suddenly stood with a RPi5.
I would say half the video could be cut out and the rest could be compressed 5 minutes more.
You need to be sure of your knowledge and level of your audience.
You jump back and forth on the knowledge ledger, like explaining what a hard drive is to just saying console and terminal.
You should also make sure the viewer can actually see what you do, like when you add something to the home screen. you press something, but it is impossible to see what.
All in all it should have a big disclaimer in the beginning.
First a RPi is a tinker computer and the viewer might be in trouble with its power designs, where RPi is know for a very restricted power setup.
Also a RPi require a good PSU or it will cause issues, which needs to be addressed too.
There should also be a disclaimer that this setup will not be able to replace one of the many apps on the phone, because it is not internet connected, so once you leave the house, then the connection is lost and it is somewhat tricky to get it available on the internet and even more to do it securely.
Portforwarding can be tricky enough to explain, but a VPN is probably required, so you do not need to spend so much time on trying to explain hardening of the server. It will not be well taken if you guide was leaking information to malicious users on the internet, due to your inability to secure the server.
Secondly get your terms right and make sure you get all explained that is important.
A hat is a circuit board you connect to the row of GPIO pins on the RPi, which the Argon One case is not. It is allowing a hat to be used at the same time.
When you recommend a piece of hardware, like the Argon One, then make sure to mention what keys of M.2 medias are accepted.
When doing educational videos you should really put on the stupid hat and watch it before posting it. The hard part with this is to actually hear and see what is being said and shown and not what you THINK is being said and shown.
You need to linger with every technical term and ponder if it should be explained or maybe replaced with a more common one.
The hard part here is to discover the things that are not being said or shown, but should have, like the key of the M.2 storage accepted by the Argon One case.