Project ideas from Hacker News discussions.

Lore – Open source version control system designed for scalability

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

4 PrevalentThemes in the Discussion

Theme	Summary & Supporting Quotes
1. Skepticism toward Epic’s “free‑game” narrative	Many users dismiss the idea that Epic’s free titles are truly free, pointing out the hidden costs of installing Epic’s client and the company’s broader practices. “It’s a mischaracterization to call the games free, if they require you to install unrelated third‑party software you’d rather not install…” — argee
2. Interest in Lore as a game‑focused VCS	The new “Lore” system from Epic is repeatedly praised for tackling the specific pain points of game development—large binary assets, permission control, and chunked storage—while acknowledging its early stage. “Lore is meant for situations where your repository is going to contain gigabytes of binary files, such as art assets for games.” — pushcx
3. Critique of Git’s usability, especially for binaries	Several commenters argue that Git’s CLI is opaque and that it struggles with binary files, pushing for simpler, purpose‑built tools. “Git as a CLI is atrocious. The output is just gobbledegook for most people.” — archerx
4. Anti‑Epic sentiment and ethical concerns	A recurring thread is distrust of Epic’s business moves—anti‑Linux stance, past studio acquisitions, and perceived exploitation—making some reluctant to adopt any Epic‑related tooling. “They stole from me and many others.” — superkuh

All quotations are taken verbatim from the discussion and attributed to the respective user.

🚀 Project Ideas

Generating project ideas…

LoreStudio – GUI Client for Game Asset Version Control

Summary

A cross‑platform desktop GUI built on top of the Lore CLI that lets artists and designers version binary assets without touching the command line.
Provides visual diffing for textures/models, file locking, and one‑click integration with Unity and Unreal Engine.

Details

Key	Value
Target Audience	Game artists, technical artists, and indie developers using Lore for binary assets
Core Feature	Drag‑and‑drop asset management with visual diff, asset locking, and engine‑specific plugins
Tech Stack	Tauri (Rust + Web UI), React, Lore CLI bindings
Difficulty	Medium
Monetization	Revenue-ready: $9/mo per seat (free tier for <2 users)

Notes

HN commenters complained about Git’s “gobbledegook” output and the lack of a good GUI for binary VCS (Snafuh, niek_pas); a polished GUI would directly address that pain.
Integrating with UE/Unity solves the “first‑class support inside the engine” desire expressed by tlahtinen and akurilin, making adoption frictionless for studios already using Lore.

LoreHost – Managed Lore Service with CI/CD & Asset Caching

Summary

A hosted platform that provides Lore repositories as a service, complete with built‑in asset caching, automated CI pipelines for game builds, and fine‑grained permission controls.
Teams get instant scalability without self‑hosting a Lore server.

Details

Key	Value
Target Audience	Mid‑size to large game studios and publishing teams needing reliable, centralized VCS for huge asset repos
Core Feature	Managed Lore servers with geo‑distributed cache, webhook‑triggered CI, and role‑based access control
Tech Stack	Go (API), Rust (Lore core), PostgreSQL, S3‑compatible storage, Kubernetes
Difficulty	High
Monetization	Revenue-ready: Usage‑based pricing ($0.02/GB‑month storage + $0.10/build minute)

Notes

Commenters highlighted the need for centralized locking, permissions, and better server‑side performance (regnerba, akurilin); a managed service removes the ops burden while providing those features.
The desire for “full‑surface API” and web client/code‑review tools (kardianos) can be offered as part of the hosted platform, encouraging discussion around CI/CD improvements for game asset pipelines.

AssetSync – Engine Plugin for On‑Demand Asset Hydration

Summary

A plugin for Unity and Unreal Engine that automatically interacts with Lore to perform sparse checkouts and hydrate only the assets needed for the currently open scene or level.
Reduces clone times and disk usage by fetching assets lazily as they are referenced.

Details

Key	Value
Target Audience	Level designers, environment artists, and programmers working on large‑scale game projects
Core Feature	Automatic Lore sparse‑checkout + on‑demand hydration triggered by asset imports or scene loads
Tech Stack	C# (Unity), C++ (Unreal), Lore Rust bindings via FFI
Difficulty	Medium
Monetization	Hobby (open‑source MIT) with optional paid support contracts

Notes

Users such as danudey praised Lore’s on‑demand hydration and sparse checkout potential but noted the manual setup is cumbersome; this plugin automates it, directly addressing that friction.
By integrating with the editor, AssetSync satisfies the request for “editor support” and “first‑class VCS support inside the engine” mentioned by tlahtinen and akurilin, likely sparking discussion on workflow improvements.

LoreLite – Five‑Command CLI Wrapper for Simple Binary VCS

Summary

A thin wrapper around the Lore CLI that reduces the command set to five easy‑to‑remember verbs (init, add, commit, push, pull) while handling binary chunking, locking, and conflict resolution automatically.
Aimed at developers frustrated with Git’s complexity and those wanting a “git with five commands” experience.

Details

Key	Value
Target Audience	Programmers and technical leads who want a simple VCS for binary‑heavy repos without learning Lore’s full CLI
Core Feature	Five‑command interface with intelligent auto‑lock, automatic binary diff/chunk handling, and helpful progress output
Tech Stack	Rust (binary), uses Lore library as dependency
Difficulty	Low
Monetization	Hobby (MIT license) – can be sponsored via GitHub Sponsors

Notes

Multiple commenters (glouwbug, gritzko, pushcx) expressed a wish for a VCS with only five simple commands; LoreLite directly fulfills that desire while leveraging Lore’s powerful binary handling.
By hiding the underlying complexity, it lowers the barrier for teams transitioning from Perforce or Git LFS, likely generating discussion on usability vs. power trade‑offs in game‑dev VCS tools.