Instructions to use Altworld/Hemmingway-1 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.

Libraries

How to use Altworld/Hemmingway-1 with Transformers:

# Use a pipeline as a high-level helper
from transformers import pipeline

pipe = pipeline("text-generation", model="Altworld/Hemmingway-1")
messages = [
    {"role": "user", "content": "Who are you?"},
]
pipe(messages)

# Load model directly
from transformers import AutoTokenizer, AutoModelForCausalLM

tokenizer = AutoTokenizer.from_pretrained("Altworld/Hemmingway-1")
model = AutoModelForCausalLM.from_pretrained("Altworld/Hemmingway-1", device_map="auto")
messages = [
    {"role": "user", "content": "Who are you?"},
]
inputs = tokenizer.apply_chat_template(
	messages,
	add_generation_prompt=True,
	tokenize=True,
	return_dict=True,
	return_tensors="pt",
).to(model.device)

outputs = model.generate(**inputs, max_new_tokens=40)
print(tokenizer.decode(outputs[0][inputs["input_ids"].shape[-1]:]))

Notebooks
Google Colab
Kaggle
Local Apps Settings

vLLM

How to use Altworld/Hemmingway-1 with vLLM:

Install from pip and serve model

# Install vLLM from pip:
pip install vllm
# Start the vLLM server:
vllm serve "Altworld/Hemmingway-1"
# Call the server using curl (OpenAI-compatible API):
curl -X POST "http://localhost:8000/v1/chat/completions" \
	-H "Content-Type: application/json" \
	--data '{
		"model": "Altworld/Hemmingway-1",
		"messages": [
			{
				"role": "user",
				"content": "What is the capital of France?"
			}
		]
	}'

Use Docker

docker model run hf.co/Altworld/Hemmingway-1

SGLang

How to use Altworld/Hemmingway-1 with SGLang:

Install from pip and serve model

# Install SGLang from pip:
pip install sglang
# Start the SGLang server:
python3 -m sglang.launch_server \
    --model-path "Altworld/Hemmingway-1" \
    --host 0.0.0.0 \
    --port 30000
# Call the server using curl (OpenAI-compatible API):
curl -X POST "http://localhost:30000/v1/chat/completions" \
	-H "Content-Type: application/json" \
	--data '{
		"model": "Altworld/Hemmingway-1",
		"messages": [
			{
				"role": "user",
				"content": "What is the capital of France?"
			}
		]
	}'

Use Docker images

docker run --gpus all \
    --shm-size 32g \
    -p 30000:30000 \
    -v ~/.cache/huggingface:/root/.cache/huggingface \
    --env "HF_TOKEN=<secret>" \
    --ipc=host \
    lmsysorg/sglang:latest \
    python3 -m sglang.launch_server \
        --model-path "Altworld/Hemmingway-1" \
        --host 0.0.0.0 \
        --port 30000
# Call the server using curl (OpenAI-compatible API):
curl -X POST "http://localhost:30000/v1/chat/completions" \
	-H "Content-Type: application/json" \
	--data '{
		"model": "Altworld/Hemmingway-1",
		"messages": [
			{
				"role": "user",
				"content": "What is the capital of France?"
			}
		]
	}'

Docker Model Runner
How to use Altworld/Hemmingway-1 with Docker Model Runner:
```
docker model run hf.co/Altworld/Hemmingway-1
```

Complaint Regarding Improper License Change on Derivative Model "Hemmingway-1"

#10

by JLouisBiz - opened 9 days ago

Discussion

JLouisBiz

9 days ago

Subject: Unauthorized License Restriction on Hemmingway-1 — Derivative of Qwen/Qwen3.8-27B (Apache 2.0)

Complaint Regarding Improper License Change on Derivative Model "Hemmingway-1"

To: luka@hemmingway.io
Subject: Unauthorized License Restriction on Hemmingway-1 — Derivative of Qwen/Qwen3.8-27B (Apache 2.0)

Dear Luka / Altworld Team,

I am writing to formally object to the licensing terms you have applied to Hemmingway-1, which you publicly describe as being "Built on Qwen3.8-27B" and list your base model as Qwen/Qwen3.8-27B.

The Problem

The upstream base model — Qwen/Qwen3.8-27B — is released under the Apache License 2.0. That license is irrevocable and binding on all derivative works. You cannot relicense a derivative of Apache-2.0 software under a more restrictive license.

You have published Hemmingway-1 under CC BY-NC 4.0, which:

Adds a non-commercial restriction that does not exist in Apache 2.0.
Imposes attribution requirements different from Apache 2.0's terms.
Purports to require a separate commercial agreement with you for uses that Apache 2.0 expressly permits royalty-free.

This is not a valid license for Hemmingway-1. Under Apache 2.0 Section 4, you may add your own copyright terms to modifications you make, but you must still comply with the Apache 2.0 license for the underlying work, and you cannot impose additional restrictions on the combined/derivative work that conflict with the rights Apache 2.0 grants to downstream recipients.

Why Your License Is Invalid

Apache 2.0 Section 2 grants every recipient a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

Apache 2.0 Section 4 states that you may add your own copyright statement and may provide additional or different license terms for your modifications, provided that your use, reproduction, and distribution of the Work otherwise complies with the License.

It does not permit you to:

Replace Apache 2.0 with CC BY-NC 4.0 on the derivative as a whole.
Add a non-commercial restriction on top of Apache 2.0.
Require a separate commercial agreement for rights Apache 2.0 already grants.

CC BY-NC 4.0 explicitly states it is not a license suitable for software and its non-commercial clause directly conflicts with Apache 2.0's royalty-free commercial-use grant. A downstream user who received Hemmingway-1 under Apache 2.0 (via the base model) has rights you cannot unilaterally revoke.

What You Must Do

Correct the license on the Hemmingway-1 model card to reflect that the derivative work is governed by Apache 2.0, or at minimum that Apache 2.0 rights apply to the base model and all derivatives.
Remove the CC BY-NC 4.0 designation and the requirement for a separate commercial agreement, as these are unenforceable against the Apache 2.0 grant.
Retain the Apache 2.0 license text, NOTICE file, and attribution to Qwen as required by Section 4.
Clarify that any additional terms you apply to your own modifications do not restrict rights granted by Apache 2.0 on the base model.

You are of course free to license your own original contributions under additional terms, but you cannot use those terms to restrict the Apache 2.0 rights attached to Qwen3.8-27B and its derivatives. Such is also not practical and difficult to prove who used what tensor parts in case of a LLM model.

Requested Action

Please update the Hemmingway-1 model card and distribution terms within 7 days to comply with Apache 2.0. If you believe your CC BY-NC 4.0 licensing is valid, please provide the specific legal basis under Apache 2.0 that permits adding a non-commercial restriction to a derivative of an Apache-2.0 work.

I look forward to your prompt correction.

Sincerely,
Jean Louis

Cc: Qwen Team / Alibaba Cloud

FemGrlLvr

7 days ago

Jean Louis is the truth!

ReingeFallen

about 1 hour ago

The letter gets the main legal point wrong, but the conclusion is partly right for another reason.

Apache 2.0 isn't copyleft. Section 4 explicitly allows "different license terms [...] for any such Derivative Works as a whole". So a Qwen finetune can be CC BY-NC.

The real issue is that Hemmingway-1 was first published here under Apache 2.0 (commit "Apache-2.0", card said "yours to use, including commercially"). That grant is perpetual and irrevocable. Anyone who got those weights keeps Apache rights to them and can redistribute them under Apache. Relicensing only binds newly released weights, not the ones already out.

Separately, the current LICENSE only links to Apache instead of including a copy (4a), and the Alibaba Cloud copyright notice is missing (4c). That part of the complaint is valid and easy to fix.

Upload images, audio, and videos by dragging in the text input, pasting, or clicking here.

Tap or paste here to upload images

· Sign up or log in to comment