# large\_files Published articles for large\_files. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## HTTP 206 Partial Content Explained DevFeed: [HTTP 206 Partial Content Explained]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-26T11:37:15Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [HTTP](), [client](), [browser](), [file](), [servers](), [Cache]() Tags: [browser](), [cache](), [cdn](), [client](), [file](), [http](), [http-206](), [http-codes](), [internet-architecture](), [large-files](), [range](), [request](), [server](), [video](), [web-servers](), [web-troubleshooting]() ### AI overview This tutorial explains HTTP 206 Partial Content, a successful response used when a client requests only part of a file or other resource. It describes byte-range requests, the Range and Content-Range headers, and uses such as video playback, resumable downloads, and cache or CDN handling. ### Source excerpt A browser does not always need the whole file at once. Sometimes it only needs a slice of the file. That slice might be the next part of a video or a chunk of a large object sitting behind a CDN. When that happens, the client can request a byte range instead of requesting the ... Read more The post HTTP 206 Partial Content Explained appeared first on Justin Wilson (j2sw). ## Transfer many large files from Android DevFeed: [Transfer many large files from Android]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2022-12-17T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [adb](), [Command-line interface](), [Shell]() Tags: [adb](), [android](), [backup](), [blogs](), [disk-space](), [dry-run](), [files](), [large-files](), [storage]() ### AI overview A tutorial on using ADB to transfer many large files from an Android phone when Android File Transfer is unreliable or disk space is limited. It explains pulling files in batches and safely deleting only files that were synchronized. ### Source excerpt Trying to get a large number of files from your Android phone, but Android File Transfer freezing up? Here's what I learned trying to pull ~170 Gb from my Pixel phone. ## send.firefox.com rocks DevFeed: [send.firefox.com rocks]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-28T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [Firefox]() Tags: [firefox](), [https](), [large-files](), [simple]() ### AI overview The article recommends Mozilla's send.firefox.com for sending large files to individuals, describing it as simple, easy to use, and powerful. ### Source excerpt If you have to send a large file to an individual, use: https://send.firefox.com/ It is brilliantly simple, easy to use and powerful. Recommended. ## A Warning About Git LFS and Large Machine Learning Models and Automated Deployments DevFeed: [A Warning About Git LFS and Large Machine Learning Models and Automated Deployments]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2019-11-14T00:00:00Z Content type: article Language: en Sources: [Scott Johnson]() Topics: [Git](), [Ansible](), [Ubuntu]() Tags: [ansible](), [automated](), [git](), [git-lfs](), [large-files](), [machine-learning](), [models](), [ubuntu]() ### AI overview The author reports that an automated Ubuntu 18 and Ansible deployment installed Git LFS after cloning a repository, but a subsequent git pull did not download a large machine learning model. Deleting the repository and performing a manual clone downloaded the full model, raising concerns about Git LFS in automated deployments. ### Source excerpt Github has a maximum size of 50 mb per file under management. And that normally works just fine - until the age of machine learning. Machine learning models are big, staggeringly big. I'm currently working on a project where the underlying model is like 830 + mb. Now when you have large files, git has a facility called "Git LFS" (large file support) and they purport that it is the solution but, well, it really, really isn't. Here's what I just ran across (platform is Ubuntu 18 and Ansible): I have a playbook that handles git clone / git update. When you initially install, the git clone only brings down the non lfs files. I then remembered the lfs issue and modified the playbook to install lfs and run the per repository installation command (cd into your repo directory and then git lfs install). The next stage in the playbook did a git pull and my expectation was that the pull would bring in the large model. Unfortunately it did not so I had a real wtf moment. I then logged into the machine manually and deleted the repo and cloned it manually. And, voila, I got the full model coming down. Before Git LFS Install du -hcs hate-language-modeling/ 16K 0hate-language-modeling/ 16K total After Git LFS Install Using Manual Git Clone du -hcs hate-language-modeling/ 836M hate-language-modeling/ 836M total Conclusion Given the importance of automated deploys, this really makes me concerned about using git lfs moving forward. Yes it is wonderful that I can run the per repository installation command and have it work even after the directory is installed but the git pull, after that command was run, should have brought down the entire model.