-
Notifications
You must be signed in to change notification settings - Fork 11.1k
5-11 #4770
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
Closed
Closed
5-11 #4770
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
f4e671b
refactor: redesign UI to modern minimalist style
EthaninUK d76060a
fix: update global ICON_BUTTON_CLASS constant to match minimalist theme
EthaninUK e1d6d9c
refactor: redesign UI to match right.codes warm gradient style
EthaninUK 3f4d05b
chore: add TokenAllIn logo
EthaninUK 2495427
chore: add TokenAllIn shield logo
EthaninUK a74bffa
fix: change footer credit to plain text 'New' without link
EthaninUK d49f60e
Merge branch 'QuantumNous:main' into main
EthaninUK File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: QuantumNous/new-api
Length of output: 119
🏁 Script executed:
Repository: QuantumNous/new-api
Length of output: 511
🏁 Script executed:
Repository: QuantumNous/new-api
Length of output: 50376
🏁 Script executed:
Repository: QuantumNous/new-api
Length of output: 477
🏁 Script executed:
Repository: QuantumNous/new-api
Length of output: 754
🌐 Web query:
AGPL-3.0 license attribution requirements source code availability💡 Result:
AGPL-3.0 attribution requirements (what you must keep/show) 1) Keep license/copyright/warranty notices intact, and provide the license text - When conveying copies, you must “keep intact all notices” and ensure the work “carry prominent notices stating that it is released under this License and any conditions added under section 7” (i.e., you can’t strip out the AGPL notices). [1][2] 2) If you modify and convey: mark that you modified + the relevant date - For conveying modified source versions under section 5, you must include prominent notices stating that you modified the work and giving a relevant date. [1][2] 3) If the program has interactive user interfaces: show “Appropriate Legal Notices” - AGPL-3.0 requires “Appropriate Legal Notices” when the program has interactive user interfaces. [3] AGPL-3.0 source-code availability requirements (the “Corresponding Source” obligation) A) If you convey/distribute object code (distributed software) - When conveying object code, you must provide the “Corresponding Source” (including the scripts and source needed to generate/install the object code) under the AGPL’s conveying terms. [4][5] B) If you run a modified AGPL program over a network (SaaS/web app use) - Unlike GPL, AGPL section 13 adds a network-interaction requirement: if you modify the Program and users interact with it remotely over a computer network, you must “prominently offer” those users an opportunity to receive the Corresponding Source “by providing access … from a network server at no charge.” [1][2][5] - The license gives an example approach: a web app interface could display a “Source” link to an archive of the code. [1][2] Bottom line - “Attribution” under AGPL-3.0 is primarily about preserving required prominent legal/copyright/license notices, and adding “modified” notices + date when you convey modified versions. [1][2] - “Source code availability” under AGPL-3.0 is primarily about providing “Corresponding Source”: via the conveying rules when distributing, and via a network-offer mechanism when running modified versions for remote users (SaaS). [4][5]
Citations:
Incomplete text: "New" should be "New API" or similar.
The text "设计与开发由 New" (Designed and developed by New) is grammatically incomplete and unclear. "New" alone is not a recognizable entity name—it should likely be "New API" or the actual project/organization name. This affects both line ranges (202-204 and 229-231).
Update the span text to reflect the complete project identifier.
Also applies to: 229-231
🤖 Prompt for AI Agents