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

How to handle user/content discovery #296

Closed
davidrichard23 opened this issue Dec 31, 2017 · 2 comments
Closed

How to handle user/content discovery #296

davidrichard23 opened this issue Dec 31, 2017 · 2 comments

Comments

@davidrichard23
Copy link

each user would have their own database for their tweets. To follow a user, a peer would subscribe to a user's feed, ie. replicate their feed database.

How would a user discover a feed to subscribe to? From what I understand, only database level write permissions are available so I couldn't create a public database that allows users to add their profiles because any user would be able to edit/delete any other user's profile.

I could use a Log Database but then the profile wouldn't be editable or searchable.

Is there something I'm missing or is this just a current limitation?

@fazo96
Copy link

fazo96 commented Jan 3, 2018

I think discovering new database is just not currently in the scope of OrbitDB.

However you can solve that problem by opening a pubsub topic where the client advertises the address of their databases

@aphelionz
Copy link
Member

@fazo96 is correct! This is currently on the application developer to do. However, we cover this in Chapter 5 of the tutorial section of the new OrbitDB Field Manual. People should check that out and open issues there if they have more questions or if something doesn't make sense.

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

No branches or pull requests

3 participants