From 3ed7ae3bfea161545e7eda901859a0dc65899104 Mon Sep 17 00:00:00 2001 From: Simon Date: Mon, 14 Oct 2024 17:30:36 +0200 Subject: [PATCH 1/7] draft --- README.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/README.md b/README.md index ece2c27..aa7529b 100644 --- a/README.md +++ b/README.md @@ -87,3 +87,38 @@ It would be great to at some point connect with BW and Couchers over Nostr. If you see "nostr token", run away, it is a scam. There's no nostr token. There was no nostr ICO, nostr is not a DAO, there is no blockchain. Nostr makes it easy to integrate bitcoin lightning, which may at some point be helpful to for example keep out spammers. But this is not something we are interested in for the foreseeable future. + +## Roadmap + +Goal: 70% of active Trustroots users are on Nostroots by middle of 2026 +- active trustroots users: around 5K active within last month, 70% is around 3.5K ([Trustroots statistics](https://www.trustroots.org/statistics)) +- "are on Nostroots": Have had a Nostroots experience means have some feature use that went well and is associated with Nostroots. The users don't need to recognize Nostr as the protocol, just that something is possible that wasn't before. This could be logging into a different site, transporting some of their network, or interacting with content from a different platform. + +First step: Trial this in Berlin. Largest userbase, close to some of the developers. + +200 users in Berlin, likely around 30 active within the last 6 months. Probably around 5 people requesting hosting every week. + + +The technical side of things are manageable as long as we just care about Trustroots functionality. There are two big challenges for migrating our users. +- telling the story +- finding partners in the ecosystem. + +### Telling the story +Trustroots users skew hippie, alternative, vanguard, experimental, left, gifting. The Nostr userbase is generally cryptocurrency and privacy focused. + +As far as our users are concerned, Trustroots is fine and nothing is broken. So a degradation of their experience will likely only lead to frustration. At best, we can justify inconvenience through appealing to the values of the community. The community also won't care that much about the admins' wish to make Trustroots more maintainable. + +Trustroots users interact with the app when they're looking for something in a new city. That is the moment they're engaged and ready to be excited and we should find a story that works for them. + +Story: +- Trustroots was never meant to be just for hosting. It's meant to enable gifting and sharing based on trust and shared values. +- In a world of companies owning your identity online, Trustroots wants to empower you to own your own identity. +- There's more cool stuff like Trustroots in the world. + + +### Partners in the ecosystem +There are no good partner organisations in the ecosystem. + +"Log in with trustroots" – forward. + +What's the simplest login-with functionality we can implement? \ No newline at end of file From a5f33cfc5875d3a3a348c5bb7e23397733bbe63f Mon Sep 17 00:00:00 2001 From: Simon Date: Tue, 15 Oct 2024 11:53:00 +0200 Subject: [PATCH 2/7] update numbers --- README.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index aa7529b..a34a0b5 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ Goal: 70% of active Trustroots users are on Nostroots by middle of 2026 First step: Trial this in Berlin. Largest userbase, close to some of the developers. -200 users in Berlin, likely around 30 active within the last 6 months. Probably around 5 people requesting hosting every week. +200 hosts/maybe hosts in Berlin. Probably around 5 people requesting hosting every week. The technical side of things are manageable as long as we just care about Trustroots functionality. There are two big challenges for migrating our users. @@ -116,8 +116,18 @@ Story: - There's more cool stuff like Trustroots in the world. -### Partners in the ecosystem -There are no good partner organisations in the ecosystem. +### Partners in the ecosystem +We need space-focused organisations in Berlin we can work with: +- Bike Surf Berlin +- Geocaching? +- Party groups? + +There are no good partner organisations in the current Nostr ecosystem. Our best bet will be supportive interested other groups that we build the tech for. So we need to build a good DX for adding logging in. + + +Who will the first 5 users be? + +Log "Log in with trustroots" – forward. From b821f5db6afa2eed38d4e667dea26dfc2ecafecc Mon Sep 17 00:00:00 2001 From: Simon Date: Tue, 15 Oct 2024 13:49:50 +0200 Subject: [PATCH 3/7] finished draft --- README.md | 65 ++++++++++++++++++++++++++++++++++++++++--------------- 1 file changed, 47 insertions(+), 18 deletions(-) diff --git a/README.md b/README.md index a34a0b5..c73526e 100644 --- a/README.md +++ b/README.md @@ -96,7 +96,7 @@ Goal: 70% of active Trustroots users are on Nostroots by middle of 2026 First step: Trial this in Berlin. Largest userbase, close to some of the developers. -200 hosts/maybe hosts in Berlin. Probably around 5 people requesting hosting every week. +200 yes/maybe hosts in Berlin. Around 1000 users. Estimate 5-10 people requesting hosting every week. The technical side of things are manageable as long as we just care about Trustroots functionality. There are two big challenges for migrating our users. @@ -108,27 +108,56 @@ Trustroots users skew hippie, alternative, vanguard, experimental, left, gifting As far as our users are concerned, Trustroots is fine and nothing is broken. So a degradation of their experience will likely only lead to frustration. At best, we can justify inconvenience through appealing to the values of the community. The community also won't care that much about the admins' wish to make Trustroots more maintainable. -Trustroots users interact with the app when they're looking for something in a new city. That is the moment they're engaged and ready to be excited and we should find a story that works for them. - -Story: +Trustroots users interact with the app when they're looking for something in a new city. That is the moment they're engaged and ready to be excited and we should find a story that works for them. The core elements of this story should be: - Trustroots was never meant to be just for hosting. It's meant to enable gifting and sharing based on trust and shared values. - In a world of companies owning your identity online, Trustroots wants to empower you to own your own identity. - There's more cool stuff like Trustroots in the world. ### Partners in the ecosystem -We need space-focused organisations in Berlin we can work with: -- Bike Surf Berlin -- Geocaching? -- Party groups? - -There are no good partner organisations in the current Nostr ecosystem. Our best bet will be supportive interested other groups that we build the tech for. So we need to build a good DX for adding logging in. - +We need platforms and communities that work in Berlin, are not money-focused, are valuable to travellers, and encourage personal connection and sharing. There are no good partner organisations in the current Nostr ecosystem. Our best bet will be supportive interested other groups that we build the tech for. So we need to build a good DX for adding logging in. -Who will the first 5 users be? - -Log - -"Log in with trustroots" – forward. - -What's the simplest login-with functionality we can implement? \ No newline at end of file +Possible groups and communities: +- [Bike Surf Berlin](bikesurf.org) +- Geocaching? +- Semi-legal rave groups +- [Couchers](couchers.org) and other hospex platforms + +### Timeline +**Q4 2024:** +- Add functionality on main trustroots site to display and link recommended organisations in Berlin + - at most 3, possibly rotating + - maybe also based on Circles? + - track what gets clicked on + - solicit experience reports and recs for other groups to display +- Build out Trustroots app + - full notes functionality + - "login-with-trustroots" functionality + +**Q1 2025:** +- Add login-with functionality to most promising one partner org +- Add more recommended orgs +- Solicit for some Berlin community management role? + + + + + +### Log in with Nostr/Trustroots +#### User flow +- People search for something in Berlin +- A little sidebar informs them of other services in Berlin they might be interested in + - it includes a mention of the app and ease of using them via the app. +- User downloads app. +- They're onboarded onto Nostr + - private key generated and saved + - public key NIP-5 verified + - profile information published on the Nostr ecosystem (do we need extra consent here?) +- In the app, they can click on a link to an app and get taken straight to the service onto the "edit account" page to fill in missing information. + +#### Technical Flow: +- user clicks a "login with trustroots" button +- it redirects to a trustroots-controlled domain with the redirect url as query param that gets handled by the trustroots app +- client-side, we find the relevant profile event, the NIP-5 verification URL, and any other events we might need for vouching +- all are sent together to a mynewservice.org/nostr-callback URL with the stringified events as request params or data body +- service verfies the events are appropriately signed and that trustroots verified the user, checks if the corresponding public key is already associated with an account, and then signs up/logs in the user. \ No newline at end of file From 92b7d90c20f87f1cc4f5a3fc5559f9bdba46c4f0 Mon Sep 17 00:00:00 2001 From: Simon Date: Tue, 15 Oct 2024 17:39:20 +0200 Subject: [PATCH 4/7] more updates --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index c73526e..2c0c658 100644 --- a/README.md +++ b/README.md @@ -132,15 +132,18 @@ Possible groups and communities: - solicit experience reports and recs for other groups to display - Build out Trustroots app - full notes functionality - - "login-with-trustroots" functionality + - ["login-with-trustroots" functionality](https://nips.nostr.com/46) + - putting more profile data onto Nostr with opt-in **Q1 2025:** - Add login-with functionality to most promising one partner org - Add more recommended orgs - Solicit for some Berlin community management role? +- feed more data into the map - - +**Q2 2025:** +- add nip-46 login to Trustroots app and begin encouraging users to store their nsec outside of the Trustroots app +- add login-with functionality to another partner org ### Log in with Nostr/Trustroots @@ -156,8 +159,9 @@ Possible groups and communities: - In the app, they can click on a link to an app and get taken straight to the service onto the "edit account" page to fill in missing information. #### Technical Flow: -- user clicks a "login with trustroots" button -- it redirects to a trustroots-controlled domain with the redirect url as query param that gets handled by the trustroots app -- client-side, we find the relevant profile event, the NIP-5 verification URL, and any other events we might need for vouching -- all are sent together to a mynewservice.org/nostr-callback URL with the stringified events as request params or data body -- service verfies the events are appropriately signed and that trustroots verified the user, checks if the corresponding public key is already associated with an account, and then signs up/logs in the user. \ No newline at end of file +- partner site embeds javascript we provide on their website +- partner site adds `login-with-nostr` endpoint to their API +- user clicks a "login with trustroots" button on +- nip-46 flow is initiated +- browser sends a signed-by-user event with all user data to `login-with-nostr` api endpoint +- endpoint verifies event is properly signed and logs in the user and updates their user fields, creating their account first if necessary \ No newline at end of file From 963b13af8be5dc05a0c40abcc171e624b41ab47d Mon Sep 17 00:00:00 2001 From: Simon Date: Tue, 15 Oct 2024 17:47:57 +0200 Subject: [PATCH 5/7] more draft --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2c0c658..94f6d87 100644 --- a/README.md +++ b/README.md @@ -133,13 +133,13 @@ Possible groups and communities: - Build out Trustroots app - full notes functionality - ["login-with-trustroots" functionality](https://nips.nostr.com/46) - - putting more profile data onto Nostr with opt-in + - putting more profile data onto Nostr with opt-in, starting with Circles **Q1 2025:** - Add login-with functionality to most promising one partner org - Add more recommended orgs - Solicit for some Berlin community management role? -- feed more data into the map +- feed more data into the map and filter by Circles **Q2 2025:** - add nip-46 login to Trustroots app and begin encouraging users to store their nsec outside of the Trustroots app @@ -155,7 +155,7 @@ Possible groups and communities: - They're onboarded onto Nostr - private key generated and saved - public key NIP-5 verified - - profile information published on the Nostr ecosystem (do we need extra consent here?) + - profile information published on the Nostr ecosystem (do we need extra consent here?). - In the app, they can click on a link to an app and get taken straight to the service onto the "edit account" page to fill in missing information. #### Technical Flow: From 5aac4d1576e92c0fbeaf81f9bfb0af945bad8c25 Mon Sep 17 00:00:00 2001 From: guaka Date: Wed, 16 Oct 2024 13:23:18 +0000 Subject: [PATCH 6/7] Update README.md: roadmap edits links to tr circles, thought about tool to help communities (that are now often on telegram, facebook, whatsapp) --- README.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index bf3c435..e09f5ec 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ The technical side of things are manageable as long as we just care about Trustr - finding partners in the ecosystem. ### Telling the story -Trustroots users skew hippie, alternative, vanguard, experimental, left, gifting. The Nostr userbase is generally cryptocurrency and privacy focused. +Trustroots [circles](https://www.trustroots.org/circles) around hippie, alternative, vanguard, experimental, left, gifting. The 2024 Nostr userbase is generally cryptocurrency and privacy focused. As far as our users are concerned, Trustroots is fine and nothing is broken. So a degradation of their experience will likely only lead to frustration. At best, we can justify inconvenience through appealing to the values of the community. The community also won't care that much about the admins' wish to make Trustroots more maintainable. @@ -70,6 +70,8 @@ Trustroots users interact with the app when they're looking for something in a n - In a world of companies owning your identity online, Trustroots wants to empower you to own your own identity. - There's more cool stuff like Trustroots in the world. +A lot of coordination around events and groups occurs on telegram, whatsapp and facebook, we think a nostr geo tool can do better. + ### Partners in the ecosystem We need platforms and communities that work in Berlin, are not money-focused, are valuable to travellers, and encourage personal connection and sharing. There are no good partner organisations in the current Nostr ecosystem. Our best bet will be supportive interested other groups that we build the tech for. So we need to build a good DX for adding logging in. @@ -77,8 +79,13 @@ We need platforms and communities that work in Berlin, are not money-focused, ar Possible groups and communities: - [Bike Surf Berlin](bikesurf.org) - Geocaching? -- Semi-legal rave groups - [Couchers](couchers.org) and other hospex platforms +- related to [circles](https://www.trustroots.org/circles): + - Semi-legal rave groups [circle](https://www.trustroots.org/circles/ravers) + - foodsharing.de, [circle](https://www.trustroots.org/circles/foodsharing) + - [acroyoga circle](https://www.trustroots.org/circles/acroyoga) + - [lindyhop circle](https://www.trustroots.org/circles/lindyhoppers) + ### Timeline **Q4 2024:** From c9dd15898cbb880e392100979957a8e398c80991 Mon Sep 17 00:00:00 2001 From: guaka Date: Wed, 16 Oct 2024 13:27:10 +0000 Subject: [PATCH 7/7] Update README.md burners circle --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index e09f5ec..6281df4 100644 --- a/README.md +++ b/README.md @@ -82,6 +82,7 @@ Possible groups and communities: - [Couchers](couchers.org) and other hospex platforms - related to [circles](https://www.trustroots.org/circles): - Semi-legal rave groups [circle](https://www.trustroots.org/circles/ravers) + - [burners circle](https://www.trustroots.org/circles/burners) - foodsharing.de, [circle](https://www.trustroots.org/circles/foodsharing) - [acroyoga circle](https://www.trustroots.org/circles/acroyoga) - [lindyhop circle](https://www.trustroots.org/circles/lindyhoppers)