[Feature Request]: Decentralize, one gitea account, involve in the activities amoung the gitea instance all over the world. #7862

New Issue

GiteaMirror · 2025-11-02T07:39:35-06:00

GiteaMirror commented

2025-11-02 07:39:35 -06:00

Originally created by @evan0greenup on GitHub (Sep 19, 2021).

Feature Description

Just inspired by Matrix Protocol, https://matrix.org/

Each server hold a bunch of accounts, but the accounts in different server can also interact each other.

Currently, Github is the center of git-based open source development. But itself is not open source at all. Github might be influenced by politics or other non-tech related issue.

Gitea is completely open source, and the gitea instance is distributed all over the world.

It might be a large list about what exactly the feature in details include.

But it would be nice to make exist gitea instance form a large network. And make users of those instance feel that they are in a gap-less Gitea decentralized network.

All the activities in a single server can be done between servers.

For example, user A @A@gitea.hello.world might clone a project gitea.nice.peace:/B/project_sample from @B@gitea.nice.peace. A's fork will display the original repo position, and he can easily submit new merge request back.

If a user on gitea.nice.peace [at] A, the server gitea.nice.peace will send a request to server gitea.hello.world, and A will receive the notification. While this is just an example, more inter-server communication should be included.

Screenshots

No response

Originally created by @evan0greenup on GitHub (Sep 19, 2021). ### Feature Description Just inspired by Matrix Protocol, https://matrix.org/ Each server hold a bunch of accounts, but the accounts in different server can also interact each other. Currently, Github is the center of git-based open source development. But itself is not open source at all. Github might be influenced by politics or other non-tech related issue. Gitea is completely open source, and the gitea instance is distributed all over the world. It might be a large list about what exactly the feature in details include. But it would be nice to make exist gitea instance form a large network. And make users of those instance feel that they are in a gap-less Gitea decentralized network. All the activities in a single server can be done between servers. For example, user A `@A@gitea.hello.world` might clone a project `gitea.nice.peace:/B/project_sample` from `@B@gitea.nice.peace`. A's fork will display the original repo position, and he can easily submit new merge request back. If a user on `gitea.nice.peace` [at] A, the server `gitea.nice.peace` will send a request to server `gitea.hello.world`, and A will receive the notification. While this is just an example, more inter-server communication should be included. ### Screenshots _No response_

GiteaMirror added the issue/duplicate label 2025-11-02 07:39:35 -06:00

GiteaMirror closed this issue

2025-11-02 07:39:35 -06:00

GiteaMirror commented

2025-11-02 07:39:36 -06:00

@evan0greenup commented on GitHub (Sep 19, 2021):

With the power of decentralization, it have potential to become the large ecosystem just as Github has done.

This feature may be appeared in gitea v2.0.0

@evan0greenup commented on GitHub (Sep 19, 2021): With the power of decentralization, it have potential to become the large ecosystem just as Github has done. This feature may be appeared in `gitea v2.0.0`

GiteaMirror commented

2025-11-02 07:39:36 -06:00

@evan0greenup commented on GitHub (Sep 19, 2021):

@lunny @zeripath what is your opinion?

@evan0greenup commented on GitHub (Sep 19, 2021): @lunny @zeripath what is your opinion?

GiteaMirror commented

2025-11-02 07:39:37 -06:00

@evan0greenup commented on GitHub (Sep 19, 2021):

By the way, the feature of real-time cross-server mirroring could be added.

This is not just git-mirroring, but include all the activities, issues, merge request, milestone, and wiki. It is not sync at specific time,

When ever new activities take place, the mirroring server will sync each other, and make all the nodes always up to date.

The open source development won't be affected if one of those server down.

It can make open source software development always available to every one in the world without affected by politics and situation.

@evan0greenup commented on GitHub (Sep 19, 2021): By the way, the feature of real-time cross-server mirroring could be added. This is not just git-mirroring, but include all the activities, issues, merge request, milestone, and wiki. It is not sync at specific time, When ever new activities take place, the mirroring server will sync each other, and make all the nodes always up to date. The open source development won't be affected if one of those server down. It can make open source software development always available to every one in the world without affected by politics and situation.

GiteaMirror commented

2025-11-02 07:39:37 -06:00

@mscherer commented on GitHub (Sep 19, 2021):

You might be interested in the work around FedeProxy and forgefed, as well as all tickets tagged federation.

@mscherer commented on GitHub (Sep 19, 2021): You might be interested in the work around [FedeProxy](https://fedeproxy.eu/) and [forgefed](https://forgefed.peers.community/), as well as all tickets tagged [federation](https://github.com/go-gitea/gitea/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Ffederation).

GiteaMirror commented

2025-11-02 07:39:37 -06:00

@delvh commented on GitHub (Sep 19, 2021):

Please have a look at https://github.com/go-gitea/gitea/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Ffederation.
I think your proposal is already known.
If I understood the conversation correctly, one of the main features for Gitea 1.16 or 1.17 that are currently in development is exactly enabling federation between different (Gitea) instances.
Especially interesting for that might be #16827.

@delvh commented on GitHub (Sep 19, 2021): Please have a look at https://github.com/go-gitea/gitea/issues?q=is%3Aopen+is%3Aissue+label%3Atheme%2Ffederation. I think your proposal is already known. If I understood the conversation correctly, one of the main features for Gitea 1.16 or 1.17 that are currently in development is exactly enabling federation between different (Gitea) instances. Especially interesting for that might be #16827.

GiteaMirror commented

2025-11-02 07:39:38 -06:00

@lunny commented on GitHub (Sep 19, 2021):

Please go to known issues to discuss further.

@lunny commented on GitHub (Sep 19, 2021): Please go to known issues to discuss further.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7862