HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
shawwn
llama-dl
Shell2023–2024
shawwn / llama-dl

llama-dl

High-speed download of LLaMA, Facebook's 65B parameter GPT model

7Distinct people
8Mentions
0Explicit recommenders
4.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

High-speed download of LLaMA, Facebook's 65B parameter GPT model

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month8 dated mentions

Observed mentions: 2023-03-05 04:28:45 UTC to 2024-03-22 08:09:47 UTC.

02462023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 commentsMar 20232023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 20232023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC624
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC101
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC000
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC101

What Hacker News says

8 sources
There seems to be some confusion here. Let me step in as someone who has gone through this. My repo https://github.com/shawwn/llama-dl was taken down last March by Facebook. They asserted copyright over LLaMA, which is obviously bogus since it was trained on data they do not own the copyright to. I was bummed about this, but after I mentioned on HN that I was willing to fight Meta, an anonymous person named L contacted me and sent $20k of Monero to cover legal fees. I was also contacted by an amazing lawyer who wanted to represent me in this. I was absurdly fortunate on both counts. He drafted a counternotice, we sent it, and then my repo was restored within a week or so. GitHub had no choice in the matter. Legally this is a required process. Ditto for GitLab. Both are US companies. When YouTube-dl was taken down some time ago by a DMCA,
Read the rest
Nat went to bat and got it restored, and GitHub made some sort of pledge to cover legal fees associated with bogus takedown requests. Here’s the shitty part for this particular situation. A case can be made that the emulator is for the purpose of circumventing copyright protection mechanisms. This, sadly, is a solid legal basis for issuing a lawful takedown, as much as we all absolutely despise that idea. It’s pretty clear cut; Nintendo doesn’t want Switch games to be run on non-Nintendo platforms, and the emulator seeks to enable Switch games to be run on any platform. Therefore, the intent of the emulator is to circumvent Nintendo’s protection mechanisms. So where does this leave us? Well, the team can file a counternotice. GitLab will restore the repo. But that opens up the team to a lawsuit by Nintendo. And as much as I want to stand up to bullies, there’s a difference between standing up to a guy shoving a kid in a locker vs standing up to a Silverback gorilla charging at you. Nintendo’s legal history implies the latter. Welcome to Nintendo pain. The Smash community has been dealing with Nintendo’s BS for decades now. They shut down tournaments that use emulators for Smash Melee. And no one can do anything, because it’s their legal right to do so. EDIT: It’s horrible that GitLab disabled the accounts of the developers, though. My GitHub account was fine. This should be the focus of the outrage here.
In Gitlab confirms it's removed Suyu, a fork of Nintendo Switch emulator Yuzu
Your philosophical argument is interesting, but what the op was saying was one of the linked repos used in this repo is inaccessible due to DMCA: https://github.com/shawwn/llama-dl So while what you say may be true the DMCA seems to have worth for these orgs because they can get code removed by the host, who is uninterested in litigating, and the repo owner likely is even less capable of litigating the DMCA. Unfortunately as a tool of fear and legal gridlock DMCA has shown itself to be very useful to those with ill intent.
In Run LLaMA and Alpaca on your computer
>> The leak appears to be essentially just weights. The copyrightability of weights is the central and perhaps only issue. You’re wrong, there’s a material and significant amount of copyrighted material related to LLaMa which is critical to running it. If you’re so confident it’s legal, feel free to link to a guide on how to LLaMa that uses the only materials originally provided by Facebook so it’s possible to assess the system’s dependencies on legally protected materials. Next, feel free to link to build that is not bound to any property claims by Facebook. >> If you didn't sign the contract or induce the breach then it isn't relevant Again, this is not true, that’s property laundering; see above comments, repeating points I have already made will not add to this discussion. If anything is unclear, let me know, but claim that party is n
Read the rest
ot bound to an agreement related to legally protected property (not referring to the weights) if they launder it is obviously invalid, since if it was, no property for which the terms of use were separable from the property itself would be enforced; again, party would receive a cease and desist with a copy of the terms of use. >> That's a non-argument. Everything is ultimately up to the courts despite the letter of the law. No, if a legally it’s material. There is a massive difference between clean-room reverse engineering a systems from property that’s free from any claims — and referencing materials that are subject to claims to build a new system. Further, it is my position it is impossible to do a clean-room build in this situation. As a result, the only way anyone would have any confidence that a new system was free from material claims is as a result of a ruling. ____ Beyond the prior points above, worth noting Facebook has already begun taking legal actions against developers related to LLaMa leak, so it’s clear they have no intention of releasing the weight for commercial use. Here’s an example: https://github.com/shawwn/llama-dl
In Show HN: ChatLLaMA – A ChatGPT style chatbot for Facebook's LLaMA
What's the best way to download and get setup with this stuff atm? Ie lets say i want to run currently available variations of LLaMA -- 7B, 13B, and 30B [1] -- is there a current summary of how to acquire them, possibly quantize them, etc? Would i download a quantized version or do it myself? etc I ran Alpaca 7B Q4 almost instantly because they provided Curl's to download it. Super simple. But it seems most aren't doing that because it's prone to getting Facebook's gaze. So.. what's recommended? I happened to find this[2], but i think that's the non-quantized raw models? Not sure yet. [1]: Won't bother with 65B, can't fit in memory i believe? [2]: https://github.com/shawwn/llama-dl/blob/main/llama.sh edit: I forgot about https://github.com/cocktailpeanut/dalai - i suspect this is best in breed atm? Though a Docker container would be nice
Read the rest
to wrangle all the dependencies
In Load LLaMA Models Instantly
Quick steps I did to get it working 1. Download the models from here https://github.com/shawwn/llama-dl/blob/main/llama.sh (you'll need to edit the script to make it work in bash) 2. Follow the instructions here. 3. Create an interesting prompt for the AI and put your question at the end. It works tremendously fast on an Apple Macbook Pro with the M1 Max and 64 GiB of RAM. I only downloaded the 7B model because I wanted a quick run through. I'll try the rest later. Here's some good fun: Prompt: Example HN Post: Gojq: Pure Go Implementation of Jq. Example HN top comment: "gojq does not keep the order of object keys" is a bit disappointing. I care about key order purely for cosmetic reasons: when Im designing JSON APIs I like to put things like the "id" key first in an object layout, and when Im manipulating JSON using jq or similar I like
Read the rest
to maintain those aesthetic choices. HN Post:"Llama.cpp - C/C++ implementation of Facebook LLama model". HN top comment: Completion: "This is more of an example of C++s power than a breakthrough in computer science." Example HN Post: "The Moral Case for Software Patents". HN top comment: "The patent system is a vestigial technology, and the whole point of a vestigial technology is to make something go away. Its like a dinosaur that no one is using anymore. Its served its purpose." Example HN Post: "Benchmark: The Mystery of Gauss Summation". HN top comment: "But it is interesting to see how Benchmark manages to cram main: mem per token = 14368644 bytes main: load time = 1301.14 ms main: sample time = 273.73 ms main: predict time = 20970.29 ms / 82.89 ms per token main: total time = 22939.82 ms
In Llama.cpp: Port of Facebook's LLaMA model in C/C++, with Apple Silicon support

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.