So I’ve just put up a website to host links for all of my images that I put out. Also for more devices I work on than just what clockworkpi offers. The old links will still stay there but this is a new way to get to them.
I’m still looking for a decently cheap object storage provider to get the images off of Google drive, so the links are a direct download but still open a Google drive page. I hope to change that soon.
I just hope this makes it easier for some.
The site is mainly vibe coded because I’ve been lazy and depressed lately, but it’s just a simple static page so it don’t matter much.
Have a great weekend everyone!
Not usually how that would work through torrents. His IP would be one in a dozen as many others would be helping to share it.
Considering that you used to be able to get other peers IP via Discord I would consider IP leak already a certain and impact fairly low. And even so, he doesn’t need to be the one to initially serve the data.
I’ve thought about doing torrents. But it’s a lot of hassle when it’s not something that will be static forever like a movie. Plus I have images for a device that’s not even out yet.
I think I’ll end up using cloud flares object storage.
Thanks for all your work for the community! Just bought you a few coffees since my device would never have worked without your Debian Trixie image for my CM 5 UConsole.AIO and Meshtastic were so easy to get working!
The problem with GitHub is that it uses git, which really is not well-suited for storing large files like images, because anyone who clones the repository gets all of the large files in the entire history of the repo.
I previously used to store UF2 files for zeptoforth in the zeptoforth repo on GitHub, but after I got complaints from people in places like India who did not have access to high-bandwidth connections who tried to clone the zeptoforth repo I ended up having to use a special tool to filter my repo and then force-push it to destructively remove the UF2 files from my repo.
At my day job, even though much of our code is in git repos, and we have been slowly transitioning what code remains in Perforce to git, we still use Perforce (and Artifactory) for storing very large files (think at least hundreds of megabytes up to tens of gigabytes each) for this reason and have no plans of moving these files to git.
If you need to distribute large files within your repository, you can create releases on GitHub.com. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit About releases.
We don’t limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than the maximum file size limit for Git LFS on your plan. See About Git Large File Storage.
