awesome-ipfs

awesome-ipfs copied to clipboard

What kind of PR is this?

Select only one to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.

• [x] Adding something new to awesome-ipfs

Pre-submit checklist

Please confirm ALL of the following before submitting your PR.

• [x] This PR includes only one addition, removal, or edit.
• [x] I edited the /data directory instead of the README.md.
• [x] I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
• [x] I have followed the CONTRIBUTING.md guidelines.

For new additions: How critical is IPFS to your project?

• [x] Essential

For new additions: What core goal(s) does your project address?

• [x] Freedom from corporate/government interference
• [x] Data integrity
• [x] Disaster resilience/recovery
• [x] File storage/retrieval
• [x] File streaming
• [x] Permanent archiving
• [x] Self-sovereign identity

Thank you for submitting this PR! A maintainer will be here shortly to review it. We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the rest) and in its best form. Follow the code contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment. Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. We are very grateful for your contribution!

	Fails
:no_entry_sign:	Found 7 link issues

	Warnings
:warning:	Changes were made to the src folder.

	Messages
:book:	YAML data files were edited.

Link issues by awesome_bot

Line	Status	Link
58	Error	http://ethlance.com Failed to open TCP connection to ethlance.com:80 (getaddrinfo: Temporary failure in name resolution)
65	Error	https://infinitebooru.com Failed to open TCP connection to infinitebooru.com:443 (Connection timed out - connect(2) for 99.83.154.118:443)
89	503	https://ipjot.herokuapp.com/
140	404	https://pascalprecht.github.io/posts/content-identifiers-in-ipfs/
141	404	https://pascalprecht.github.io/posts/future-proofed-hashes-with-multihash/
204	404	https://github.com/aanupam23/go-stellar-ipfs
242	Error	https://orion.siderus.io Failed to open TCP connection to orion.siderus.io:443 (getaddrinfo: No address associated with hostname)

Generated by :no_entry_sign: dangerJS against 1257cf786fa89fb0ad570ec489f713d72bab4af0