x/m8sh
1
0
Fork 0
forked from x/gitea
Code Issues Pull Requests 1 Packages Releases Activity

updated home page, typo corrections, refinements

Browse Source
This commit is contained in:
d
2026-06-10 23:22:05 +03:00
parent f914c4fade
commit dfcf6d733e
1 changed files with 11 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/home.tmpl
+9 -11
View File
@@ -10,7 +10,8 @@
Work in progress
</p>
<p style="font-size: 1.15rem; color: var(--color-text-secondary); margin: 0;">
A heavily extended Gitea fork - integrated VPN, email, messenger, media streaming, GPG-based auth, and more.
A heavily extended Gitea fork with integrated GPG-based auth, email, messenger, media streaming, VPN, and later —
clients for secure interaction with the network.
</p>
</div>
@@ -19,16 +20,13 @@
M8SH is what email should have evolved into, but didn't.
</p>
<p style="line-height: 1.8; margin-bottom: 1rem; color: var(--color-text-secondary);">
The naming convention stays - <code>name@example.com</code> - because that part was always right.
What email got right was federation: anyone could run a server and communicate freely, without depending on proprietary software.
What it got catastrophically wrong was everything else - cryptography, security, protocols, user experience.
Ray Tomlinson's invention served its purpose in the 70s. Then corporations arrived, offered convenience in exchange for privacy,
and the protocol was effectively abandoned. GPG extensions were proposed and ignored, because they were inconvenient for the corps.
What email got right was simplicity alongside decentralization: anyone could run a server and communicate freely, without a
central controlling institution. What it got catastrophically wrong was everything else — cryptography, security, protocols, user experience.
</p>
<p style="line-height: 1.8; color: var(--color-text-secondary);">
M8SH turns Gitea from a development platform into a complete content exchange and distribution system —
decentralized, no dozen separate accounts, no walled gardens. The one thing email got right —
<code>user@domain</code> — stays as the identity primitive, rebuilt on modern protocols and cryptography.
<p style="line-height: 1.8; margin-bottom: 1rem; color: var(--color-text-secondary);">
In M8SH the naming convention stays the same — <code>name@example.com</code> — but it provides a full-fledged modernized API for different
forms of interaction between users on the network: sharing music, videos, subscribing to each other, posting articles, sending private
messages, all reusing that simple email naming — <code>neo@m8sh.su</code>.
</p>
</div>
@@ -55,7 +53,7 @@
</li>
<li style="display: flex; gap: 1rem; align-items: baseline;">
<span style="font-size: 0.75rem; color: var(--color-text-secondary); min-width: 1.5rem; font-variant-numeric: tabular-nums;">05</span>
<span>Posts, articles, videos, reels, music</span>
<span>Posts, articles, videos, reels, music, reactions, comments</span>
</li>
<li style="display: flex; gap: 1rem; align-items: baseline;">
<span style="font-size: 0.75rem; color: var(--color-text-secondary); min-width: 1.5rem; font-variant-numeric: tabular-nums;">06</span>