Skip to content
This repository has been archived by the owner on Oct 14, 2022. It is now read-only.

Working on the social side of Hashbase #93

Open
kodedninja opened this issue Apr 6, 2018 · 4 comments
Open

Working on the social side of Hashbase #93

kodedninja opened this issue Apr 6, 2018 · 4 comments

Comments

@kodedninja
Copy link
Contributor

As I see, currently the center of peer-to-peer sites are Github and Twitter, at least most of us publish new projects there.

Hashbase is already a hidden center for these projects, because they're mostly seeded by it, so I was thinking about making Hashbase the new center and moving away (partially) from Twitter, in example.

Focusing on the "social-networky" side of Hashbase would help in finding new projects and meeting other p2p fellas. I think about a feed and profile similar to Github's.

Would here your opinions... 😄

@pfrazee
Copy link
Member

pfrazee commented Apr 6, 2018

I'm a little concerned about Hashbase consolidating functions like discovery or social networking into its core pinning service. It makes obvious sense! But it could have a centralizing effect. We want Hashbase to be highly generic background infrastructure.

It's kind of like separation of powers, right? Just like how the president can't write laws: Hashbase can't do discovery. That way Hashbase has less power to abuse.

What are some alternatives? Maybe a service on zeit or glitch?

@kodedninja
Copy link
Contributor Author

I only thought that most of the time you upload a project to Hashbase and then you don't have upload it elsewhere. But I do understand your concerns.

Github is a good place for discovery but p2p projects fade away in that huge amount of projects.

Another thing that came to my mind is an external site that uses some kind of Hashbase API to access sites there.

Does the community need this at all? I really don't know why I feel like this is important.

@pfrazee
Copy link
Member

pfrazee commented Apr 6, 2018

Well you definitely shouldn't need to upload the content to another location. The point of Hashbase is to keep the data online. The idea is that discovery services can point to the Dat data without having to host it. Hashbase keeps the data online; discovery services make the data easy to find.

We also have APIs for seeing what's pinned. Stuff like https://github.com/beakerbrowser/hashbase/blob/master/docs/webapis.md#get-v1usersusername. Also https://github.com/beakerbrowser/hashbase/blob/master/docs/webapis.md#get-v1explore.

@kodedninja
Copy link
Contributor Author

Didn't knew about the API, thanks.

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

No branches or pull requests

2 participants