Some drives are worse than others and higher capacities get worse and worse, in my experience, Seagate drives are extremely loud.
If you get helium drives (like wd red plus > 8TB i think),or 2nd hand hgst/ WD enterprise drives) they are significantly quieter.
But, having an ssd is cheaper probably. I have an SSD for the boot drive and all databases, configuration folders, etc... In docker so general IO is fast, then media, documents, pictures, etc... On the big HDDs.
I'm sorry. There are people who go to an adult hardcore porn site and then type in "Suitable for work"??? Like do you think the site wouldn't get flagged at your work?
KNX.
Everything is decentrally programmed, and you can do extra automations and stuff from home assistant, but KNX devices are wired (generally) and will always Just Work™. More expensive that the cheaper retrofit options, but if you factor in manual overrides or getting the "better" wireless smart devices it is comparable. They generally also have a manual override at the panel. For core functions like lights, HVAC, roll shutters or blinds, etc... That is honestly the best option (unless you want every light to be an RGB light for some reason, then you still need smart bulbs)
You can also look at the MKBHD 2024 smartphone camera comparison test with the FP5. I would suggest taking the test yourself if that is still possible.
I would guess that the camera will be comparable. (Everything below if FP5 assuming about the same performance with the FP6)
For me, daylight pics were after all of the pixels but before anything else. I like the more neutral not supremely over-saturated over-sharpened/smoothed pictures that many phones take nowadays.
For me, it was middle of the pack for dimly lit photos.
For the overall ELO with everyone, FP5 was on the mid-lower end (of a comparison of all flagships + pixel A series), but perfectly usable for people who aren't doing social media as a job.
This is similar to what I do.
I have a USB drive with the whole bootloader + decryption keyfiles on it. I remove it while it is running as everything is stored in RAM and already booted.
Downside being it has to be plugged in to update the boot partition during an upgrade.
And you are often paying 140-200 for a pi nowadays to make it have the same usability as a laptop (pi, power supply, sata hat, data drive because SD cards simply fail after a while under server IO) while you can get cheap used laptops for 0-100.
So unless you are running it for more than half a decade (which rarely happens with selfhosters for a main server), you are probably spending more in total on the pi.
Yep, you can get an m.2 NVMe to USB3 converter very cheap and stick any m.2 nvme drive in it. (Also sata versions exist for m.2 sata)
Much safer solution for your data.
I had the same thing on Bazzite just with the local network, not a VPN.
I believe it has to do with the firewall. You have to open the port both incoming and outgoing for 53317.
But you literally have to be on the same network, so for example if both devices are on the same local network (hence local in the name) and your phone is on a VPN but your computer is not on a VPN, then it won't work.
It should work if you VPN into your local network remotely so that both devices are on the same LAN, however, then that won't work anyway because you have to have physical access to the device to accept the transfer (you could probably use a remote desktop to do that, but then it is getting complicated)
LocalSend.
No more USBs ever (outside of install media). So so simple, fast, and works on all devices and FOSS.
It is really the best UX of any file sharing app I have experienced (outside of airdrop I guess, but obvious problems there)
Okular is also a favorite of mine.
There is also leantime.io that I have been hosting for 5 years or so. It is a bit more than planka or tarallo as far as scope I think, but it has integrated kanban, gannt charts, and hour logging which is all I need for my personal projects.
The few things I don't like about flatpaks (which become a problem on atomic distros that use almost all flatpak by design):
Some types of embedded development is essentially impossible with flatpaks. Try getting the J-link software connected with nrftools and then everything linked to VScodium/codeoss
Digital signing simply doesn't work, won't work for the foreseeable future, and is not planned to get working,
Flatpaks sometimes have bugs for no reasons when their package-manager counterparts don't (e.g. in KiCAD 8.0, the upper 20% or so of dialog boxes were unclickable with the mouse, but I could select and modify them with the keyboard, only the flatpak version)
The status on whether it is still being actively developed or not (at least I hear a fair amount of drama surrounding it)
But besides those small things, it seem great to me.