-
Notifications
You must be signed in to change notification settings - Fork 96
Create a Public IPFS User Registry #626
Comments
I have a draft User Registry Entry Form ready for review. It's based on the notes document. Here's the edit view and the preview If you want to suggest changes, please comment on the notes document |
I'm getting permission errors on these.
|
The IPFS User Registry on https://airtable.com/tblLf5K7YnbosxJIl/viwwgIMk4kq5veXte only has 8 users, is this correct? I believe I saw a more up to date one at the Dev Meetings |
@parkan - saw this and thought of our collab discussions. Some useful content and format here as we attempt to systematize information collection from folks we know building on IPFS. |
I was thinking of creating a user registry with a focus on global-remote IPFS freelancers. I even bought interplanetary.dev so that people could have branded profiles like interplanetary.dev/@agentofuser or maybe a subdomain. It would be pretty much a static website generated from data a bit like https://github.com/ipfs/awesome-ipfs. I guess there is no harm in making it not exclusive for freelancers, although having a way to filter based on that kind of property would be nice. I have other things further up my priority list though, so if PLabs is interested I can transfer the domain. |
Don’t let us lick your cookie - I think we’re still shaking out the best way to do this that fits nicely with other tools like awesome.ipfs. It’d also likely be more focused on project over person (since many awesome projects have teams of people contributing) |
yep consolidating this is definitely in the queue! |
All the relevant design notes are in Creating an Public IPFS+libp2p User Registry
Why Create a User Registry
As maintainers of the IPFS project and coordinators of its surrounding ecosystem, we have a view into the huge array of people who are building tools, libraries and products on our protocols. We have not done enough to feature those people, the projects they’ve launched, the software they’ve created, and the communities of users who they’re serving. We intend to change that, giving everyone a view into the ever-growing and continually-evolving ecosystem of people using IPFS, libp2p, IPLD, multiformity, etc. To do this, we are creating an IPFS User Registry which anyone can submit their projects to and, once submitted, can update the registry as their projects evolve.
We hope that this will help people to make crosswise connections, find new tools to use, people to collaborate with, inspiring ideas, etc.
Background
In early 2017 @mishmosh created an IPFS User Registry that she and @flyingzumwalt have used for their own planning. The list is incomplete (lots of glaring holes) but it has proven very useful. We have accumulated about 80 entries in there, but that’s only a fraction of our known users. Our intention was to make that registry’s content public, but it quickly accumulated info that we couldn’t make public without permission from all the people in the registry. To address this, we’re starting over and letting people opt into having their projects & info listed.
cc @mgoelzer @diasdavid
The text was updated successfully, but these errors were encountered: