Universal protocols for distributed systems. Includes standardized specifications for backpressure control, distributed tracing, graceful degradation, and failure handling patterns.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Requirements for your pull request
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.
Requirements for your Awesome list
Has been around for at least 30 days.
Run awesome-lint on your list and fix the reported issues.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme.
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
The heading title of your list should be in title case format: # Awesome Name of List.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
Includes a project logo/illustration whenever possible.
Entries have a description, unless the title is descriptive enough by itself.
Includes the Awesome badge.
Has a Table of Contents section.
Has an appropriate license.
Has contribution guidelines.
All non-important but necessary content should be grouped in a Footnotes section at the bottom of the readme.
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI (e.g. GitHub Actions) badge.
Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme.
unicorn
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/3701
**Author:** [@Tryboy869](https://github.com/Tryboy869)
**Created:** 10/18/2025
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `add-nexus-protocols-final-submission`
---
### 📝 Commits (1)
- [`cc2c1bb`](https://github.com/sindresorhus/awesome/commit/cc2c1bbae11941be71052503873157c893fb4921) feat: Add awesome-nexus-protocols
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
https://github.com/Tryboy869/awesome-nexus-protocols
Universal protocols for distributed systems. Includes standardized specifications for backpressure control, distributed tracing, graceful degradation, and failure handling patterns.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
### Requirements for your pull request
- [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
- [x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
- [x] You have to review at least 2 other open pull requests.
Reviewed PRs: #3641, #3688
- [x] You have read and understood the instructions for creating a list.
- [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`.
- [x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
- [x] Your entry should be added at the bottom of the appropriate category.
- [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`.
- [x] No blockchain-related lists.
- [x] The suggested Awesome list complies with the below requirements.
### Requirements for your Awesome list
- [x] Has been around for at least 30 days.
- [x] Run `awesome-lint` on your list and fix the reported issues.
- [x] The default branch should be named `main`, not `master`.
- [x] Includes a succinct description of the project/theme at the top of the readme.
- [x] It's the result of hard work and the best I could possibly produce.
- [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`.
- [x] The heading title of your list should be in title case format: `# Awesome Name of List`.
- [x] Non-generated Markdown file in a GitHub repo.
- [x] The repo should have `awesome-list` & `awesome` as GitHub topics.
- [x] Not a duplicate. Please search for existing submissions.
- [x] Only has awesome items. Awesome lists are curations of the best, not everything.
- [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
- [x] Includes a project logo/illustration whenever possible.
- [x] Entries have a description, unless the title is descriptive enough by itself.
- [x] Includes the Awesome badge.
- [x] Has a Table of Contents section.
- [x] Has an appropriate license.
- [x] Has contribution guidelines.
- [x] All non-important but necessary content should be grouped in a `Footnotes` section at the bottom of the readme.
- [x] Has consistent formatting and proper spelling/grammar.
- [x] Does not use hard-wrapping.
- [x] Does not include a CI (e.g. GitHub Actions) badge.
- [x] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme.
unicorn
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/3701
Author: @Tryboy869
Created: 10/18/2025
Status: ❌ Closed
Base:
main← Head:add-nexus-protocols-final-submission📝 Commits (1)
cc2c1bbfeat: Add awesome-nexus-protocols📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
https://github.com/Tryboy869/awesome-nexus-protocols
Universal protocols for distributed systems. Includes standardized specifications for backpressure control, distributed tracing, graceful degradation, and failure handling patterns.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Requirements for your pull request
Reviewed PRs: #3641, [PR #839] [CLOSED] Add MobX Awesome list (#3688)
Add Name of List. It should not contain the wordAwesome.#readme.Requirements for your Awesome list
awesome-linton your list and fix the reported issues.main, notmaster.awesome-name-of-list.# Awesome Name of List.awesome-list&awesomeas GitHub topics.Footnotessection at the bottom of the readme.Inspired by awesome-fooorInspired by the Awesome projectkinda link at the top of the readme.unicorn
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.