README
¶
Concrnt: Makes social media accounts your internet identities.
What is Concrnt:
Concrnt is a distributed microblogging platform.
Why Concrnt:
Using a social media account as a user identity, it's untenable to rely on centralized social media platforms that are prone to third-party censorship and irreversible account suspension. It's unacceptable for a carefully nurtured account to be suddenly frozen and rendered irrecoverable.
However, as long as servers physically exist, their operators must abide by the laws of the countries they are located in. Since operators are human, it's unrealistic to expect that accounts can never be frozen.
Concrnt resolves this dilemma. It uses a unique protocol designed to allow account migration. This means that even if your account is frozen on the server where it was initially created, you can move your account to another server and resume using it there, maintaining all past posts and friend connections just as before the freeze.
How Concrnt solves the problem:
Concrnt uses public-key cryptography to verify user identities. It doesn't share any confidential information with servers, and users are responsible for managing the security of their own accounts.
Cool! Where can I join?
You can experience the world of Concrnt through one of its web client implementations, available at concrnt.world!
Comparison
Centralized (Twitter):
There's a fear of unjust suspension, and if an account is suspended, it signifies the death of that internet identity.
Activitypub (Mastodon, Misskey):
While there is an account migration feature, if your account is suspended before migration, you're out of options. Additionally, major ActivityPub-supported social media platforms have a concept known as local timelines, which are not accessible or joinable by external users, ultimately forcing users to create new accounts on each server. Concrnt, however, allows for the creation of any number of topic-based community timelines on each server, which can be viewed and joined by users from other servers.
nostr:
Nostr is a fantastic mechanism for proving one's identity using a private key, but it requires careful selection of relay servers. There is no guarantee that a relay server will retain or delete your data. (It works very well for use cases that do not require such assurances.) Due to its fundamentally decentralized nature, it seems unlikely to implement non-essential but convenient features (such as visibility control for non-encrypted messages).
Bluesky:
Bluesky is a project that has become more active recently, so details are still emerging, but it seems to share many similarities with Concrnt. Bluesky appears to be created with a mission similar to Twitter's, aimed at "making all the information in the world shareable." In contrast, Concrnt's mission focuses on "centering around communities and loosely connecting with the world." This difference in mission leads Bluesky to adopt an architecture that builds a massive index server and generates feeds, whereas Concrnt uses a single server to lightly and in real-time collect information from nearby sources.
The problem of the Concrnt?:
The architectural strategy adopted by Concrnt may not scale to an ultra-large system where countless users can follow as many others as they like, similar to Twitter. This is because, rather than constructing a single, massive home timeline, it is designed with the assumption that users will create and switch between several moderately sized lists.
This approach is because Concrnt does not primarily aim to intensely connect with the world but to build relationships based on community timelines, optimizing for this purpose. This allows each domain to control information independently without the need for a massive server like an index server.
Furthermore, Concrnt embraces the concept of "protecting one's identity by oneself." However, in reality, this requires a certain level of knowledge and expertise, meaning there is an inherent complexity and difficulty in use.
In this sense, centralized social networks, where one relies on others for protection while trying to stay in the good graces of the administration to avoid being frozen, might be more reassuring for the average person.
For geeks
How to launch own server
look at detailed documentation: concrnt square
Contributing
When creating a PR, we generally recommend creating an issue first and reaching a consensus on whether or not to proceed. (Concrnt is currently being heavily developed, and there may be changes that cannot be made due to its policy.)
Upgrading Steps
v1.3.3 CheckPoint
これ以下のバージョンから上のバージョンにアップデートする際、このバージョンを経由する必要があります
v1.3.0 CheckPoint
これ以下のバージョンから上のバージョンにアップデートする際、このバージョンを経由する必要があります
v1.2.1
v1.2.0
v1.1.3
v1.1.1
v1.1.0
v1.0.13
v1.0.12
v1.0.9
v1.0.3
Documentation
¶
Index ¶
- Constants
- func GetDefaultGlobalPolicy() core.Policy
- func SetupAckService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.AckService
- func SetupAssociationService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, keeper timeline.Keeper, ...) core.AssociationService
- func SetupAuthService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.AuthService
- func SetupDomainService(db *gorm.DB, client2 client.Client, config core.Config) core.DomainService
- func SetupEntityService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.EntityService
- func SetupJobService(db *gorm.DB) core.JobService
- func SetupJwtService(rdb *redis.Client) jwt.Service
- func SetupKeyService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.KeyService
- func SetupMessageService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, keeper timeline.Keeper, ...) core.MessageService
- func SetupNotificationService(db *gorm.DB) core.NotificationService
- func SetupPolicyService(rdb *redis.Client, globalPolicy core.Policy, config core.Config) core.PolicyService
- func SetupProfileService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.ProfileService
- func SetupSchemaService(db *gorm.DB) core.SchemaService
- func SetupSemanticidService(db *gorm.DB) core.SemanticIDService
- func SetupStoreService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, keeper timeline.Keeper, ...) core.StoreService
- func SetupSubscriptionService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, client2 client.Client, ...) core.SubscriptionService
- func SetupTimelineService(db *gorm.DB, rdb *redis.Client, mc *memcache.Client, keeper timeline.Keeper, ...) core.TimelineService
- func SetupUserkvService(db *gorm.DB) userkv.Service
Constants ¶
const Banner = `` /* 211-byte string literal not displayed */
Variables ¶
This section is empty.
Functions ¶
func GetDefaultGlobalPolicy ¶
func SetupAckService ¶
func SetupAssociationService ¶
func SetupAuthService ¶
func SetupDomainService ¶
func SetupEntityService ¶
func SetupJobService ¶
func SetupJobService(db *gorm.DB) core.JobService
func SetupJwtService ¶
func SetupKeyService ¶
func SetupMessageService ¶
func SetupNotificationService ¶
func SetupNotificationService(db *gorm.DB) core.NotificationService
func SetupPolicyService ¶
func SetupProfileService ¶
func SetupSchemaService ¶
func SetupSchemaService(db *gorm.DB) core.SchemaService
func SetupSemanticidService ¶
func SetupSemanticidService(db *gorm.DB) core.SemanticIDService
func SetupStoreService ¶
func SetupTimelineService ¶
Types ¶
This section is empty.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
mock
Package mock_client is a generated GoMock package.
|
Package mock_client is a generated GoMock package. |
|
cmd
|
|
|
mock
Package mock_core is a generated GoMock package.
|
Package mock_core is a generated GoMock package. |
|
internal
|
|
|
x
|
|
|
association
Package association is handles concurrent Association objects
|
Package association is handles concurrent Association objects |
|
auth
Package auth handles sever-side and client-side authentication
|
Package auth handles sever-side and client-side authentication |
|
entity
Package entity is handles concurrent message objects
|
Package entity is handles concurrent message objects |
|
message
Package message is handles concurrent message objects
|
Package message is handles concurrent message objects |
|
profile
Package profile is handling concurrent Profile object
|
Package profile is handling concurrent Profile object |
|
timeline
Package timeline is for handling concurrent timeline object
|
Package timeline is for handling concurrent timeline object |
|
timeline/mock
Package mock_timeline is a generated GoMock package.
|
Package mock_timeline is a generated GoMock package. |
|
userkv
Package userkv provides a simple key-value store for users.
|
Package userkv provides a simple key-value store for users. |
|
userkv/mock
Package mock_userkv is a generated GoMock package.
|
Package mock_userkv is a generated GoMock package. |