Project Directory cleanup #116
Conversation
| * [go-ipfs-api](https://github.com/ipfs/go-ipfs-api) | ||
| An unofficial go interface to IPFS's http API. | ||
|
|
||
| * [java-ipfs-api](https://github.com/ipfs/java-ipfs-api) | ||
| A Java implementation of the HTTP IPFS API. | ||
|
|
||
| * [js-ipfs-api](https://github.com/ipfs/js-ipfs-api) | ||
| A node client library for the IPFS API. |
There was a problem hiding this comment.
"A JavaScript client library"*
There was a problem hiding this comment.
Updated description on repo.
|
This all LGTM. thanks for keeping it in order. |
|
I guess just:
|
| DMCA takedown notices | ||
|
|
||
| * [gateway-dmca-denylist](https://github.com/ipfs/gateway-dmca-denylist) | ||
| API for IPFS keys to which access should be denied. |
There was a problem hiding this comment.
maybe:
list of IPFS paths for which we have received DMCA notices.
There was a problem hiding this comment.
This has been changed to:
DMCA notices, and tools for publishing them https://ipfs.io/refs/lists/denylists/dmca
This reflects the new ipfs/refs description.
RichardLitt
force-pushed
the
feature/dir-cleanup
branch
2 times, most recently
from
f32a8f2
to
8304a92
Compare
This follows ipfs/js-ipfs#32.
RichardLitt
force-pushed
the
feature/dir-cleanup
branch
from
cbf496d
to
7169d85
Compare
|
I can't change the descriptions of the API client implementations on their GitHub repository descriptions without write access. Should I deviate from them, here, or open PRs to those repos asking for the contribs to change them? |
This is mostly following ipfs/js-ipfs#32 by renaming and linking all changed repositories, but I also cleaned up the repo by alphabetizing everything and conforming to capitalizing the first letter of each description.