Libraries. If you had to write everything from scratch, nothing would ever get done. You pick a UI library/framework that meets your needs and is supported in the language you’re using, and go from there.

You can use a Web interface, it’s absolutely hideous but it gets the job done. I hear QT is pretty easy to develop for and it’s cross-platform.

The docs directory literally has a stub on getting the repo up and serving and also a note that they are cleaning up and working on the documentation https://github.com/ente-io/ente/tree/main/docs

Yeah, ensuring availability over time requires dedicated infra. That’s basically what it comes down to. Torrents for the most part lack dedicated providers ensuring file availability. Web seeds exist, but the uploader or the tracker needs to have the resources to back their torrents with bandwidth and storage. Other decentralized solutions, like say IPFS, don’t solve the resources problem, because it’s not technical, so although you can pay to have content “pinned” in place on IPFS, or you can pin it yourself, that “pinning” requires a server, running off electricity, using someone else’s uplink to serve the content, all of which costs. If you don’t have your own server, and don’t pay someone else to pin it for you, it could easily fall off IPFS.

Syncthing could honestly help, I’ve thought about this a fair amount, although you’d still have the resources issues. Availability of content over syncthing or something like it would likely still be tied to popularity (how long are uploaders going to keep their syncthing folders full of specific content? how long will downloaders? In order for it to really work people would have to get in the habit of building out NAS’s and putting their libraries on syncthing forever, basically). It still has some of the same basic issues with torrent, but the dynamicness is cool for sure.

deleted by creator

Unless the dependencies they compile in have reproducible builds set up, then you literally cannot expect binaries to compile the same bit-for-bit between different build environments. This is a known problem for tons of reasons, etc etc. Progress has been made on improving build practices, but there are still tons of projects that aren’t reproducible. Also, the checksums not matching could easily be caused by Ventoy developers enabling different compile-time flags on their builds than upstream builds, which is near the top of the list of reasons why you’d bother to provide your own builds to start with. There are literally like 500 legitimate reasons why their builds might have different checksums than upstream’s builds. Your accusation is nonsense unless you can do some more digging and prove there are unpublished modifications to their dependencies.