-
Notifications
You must be signed in to change notification settings - Fork 17
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
Lets rename this project to a thing that better represents what it is #336
Comments
I am 100% on board with this. It is essentially a DAG Service so something along those lines makes sense. IPDS perhaps? I have not real preferences here, so happy to take suggestions/comments/recommendations from your perspective. |
If I recall correctly @mikeal had a suggestion of: Inter Planetary Dag Persistence (IPDP) I have another one: Inter Planetary Data System (IPDS)
However I'm personally not a big fan of acronyms as they prone to conflicts. And would much rather pick something else here's few
|
/cc @lidel |
|
I also just tough of |
No strong favorite on my end, but I agree we should try to come up with something with "DAG" in the name,
|
IPDP - Interplanetary DAD Persistence? |
hahaha, I had spent so much time reading comments I didn’t see that @Gozala already mentioned this name in the original post, my bad :) |
My reading of this thread seems to indicate that |
Sorry for the late entry, but I just realized that I’ve been calling the commands I create to put dag’s on the IPFS network as “seed” commands and we hadn’t considered that here yet. DagSeed? DagSeeder? |
While I think DagSeeder is actually pretty representative of what this library ultimately will be, I'm not sure its the right name for an end-user. The seed or seeder language (to me anyway) infers something more akin to pinning or providing. But this library could be used in a "client-only" type mode, where it can fetch but doesn't provide. Service seems like the most robust name, so that's still my vote. |
good point, i’m sold. |
As per ipfs/notes#436 I would love to use ipfs-lite as foundation for IPLD with persistence and (IPFS) network. However I think ipfs-lite is a controversial because it sets up wrong expectations for API (compatibility) and inter-op.
I think it would be a good idea to recognize this as a separate layer in the IPFS stack and give it it's own name & attempt to design best API for the DAG storage & replication without being tied to on that IPFS exposes today.
The text was updated successfully, but these errors were encountered: