Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make trustroots forkable #2669

Open
4 tasks
guaka opened this issue Jan 26, 2024 · 2 comments
Open
4 tasks

make trustroots forkable #2669

guaka opened this issue Jan 26, 2024 · 2 comments

Comments

@guaka
Copy link
Contributor

guaka commented Jan 26, 2024

Make the trustroots network forkable. If someone decides to run a fork, it should be easy for users to

@guaka
Copy link
Contributor Author

guaka commented Feb 2, 2024

We chose to go with nostr (nostroots) but support for ActivityPub in trustroots seems nice, supposedly instantly connectable to sleepybike. Possibly through https://gitlab.com/soapbox-pub/mostr

@guaka
Copy link
Contributor Author

guaka commented Feb 3, 2024

Nostr and ActivityPub handle user identities differently, particularly in terms of portability and control. In Nostr, users maintain a consistent identity across different applications through a public/private key pair. This system allows for greater portability, as the same identity and social graph can be used in any app implementing the Nostr protocol, with the private key being central to access and identity control.

ActivityPub, used by platforms like Mastodon, links user identities to domain names and is controlled by server operators. This structure results in identities being more server-dependent. While it offers a degree of decentralization, server administrators have control over aspects like bans and server-to-server interactions. User migration between servers in the ActivityPub network can be challenging and requires cooperation between the servers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant