@@ 4,7 4,7 @@ gwit is a minimalist system for a Web of replicated, host-neutral, lightweight s
- [gwit project home](https://gwit.site/)
-Drawing inspiration from an article by Solderpunk (creator of the Gemini protocol), gwit tries to be way more simple, lightweight and future-proof than other "decentralized Web" efforts. For that, it relies on the mature and ubiquitous Git distributed VCS and its support of PGP signatures; minimal additions turn Git repositories into hyperlinked sites.
+Drawing inspiration from an article by Solderpunk (creator of the Gemini protocol), gwit tries to be way more simple, lightweight and future-proof than other "decentralized Web" efforts. For that, it relies on the mature and ubiquitous Git distributed VCS and its support of PGP signatures; minimal additions turn plain Git repositories into a Web of hyperlinked sites.
- [Low budget P2P content distribution with git (Solderpunk)](gemini://gemini.circumlunar.space/~solderpunk/gemlog/low-budget-p2p-content-distribution-with-git.gmi);
[Web version](https://portal.mozz.us/gemini/gemini.circumlunar.space/~solderpunk/gemlog/low-budget-p2p-content-distribution-with-git.gmi "Low budget P2P content distribution with git (Gemini Portal)")
@@ 13,6 13,7 @@ Drawing inspiration from an article by Solderpunk (creator of the Gemini protoco
Features and usage:
- **Fit for lightweight sites:** personal blogs, books and documentation, reference works (like Wikipedia), and other text-centric, static but frequently updated sites.
+- **Turn any Git repo into a site:** link to its content regardless of where the repo is hosted.
- **Obstacle-less site creation:** no need to pay for a domain, certificate or server, just create a new PGP key for the site repo.
- **Opportunistic hosting:** make any gwit site available online by hosting its repo on Git forges or dumb HTTP servers (one or many, all at once).
- **Content replication and availability:** readers clone the whole site (with history), clones can be re-published and used safely by others, forever.
@@ 55,7 56,7 @@ The design of gwit tries to fulfil the goals in each list below, as much as they
Functional goals:
-- Clear target: lightweight, static sites (mostly text) with internal and external hyperlinks.
+- Clear target: lightweight, static sites (mostly text) with internal and external hyperlinks, and arbitrary Git repositories.
- Content authentication: it should be possible to verify content authorship and integrity.
- Hosting independence: sites should not be bound to a specific host or location.
- Content replication: sites should be easy to copy in their entirety.