mirror of
https://github.com/deepseek-ai/awesome-deepseek-integration.git
synced 2026-11-05 00:57:30 +00:00
[GH-ISSUE #258] [DISCUSSION] Consider highlighting native Deepseek integrations over one-size-fits-all #73
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/awesome-deepseek-integration#73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wdpatti on GitHub (Feb 15, 2025).
Original GitHub issue: https://github.com/deepseek-ai/awesome-deepseek-integration/issues/258
Many of the integrations listed here require each user to create API keys and manually paste in the Deepseek API URL. This feels far from an "integration" and more like a one-size-fits-all app that poses as a more deeply integrated app. Consider highlighting the true native Deepseek integrations, especially those that don't require a user to generate their own API key like Liubai, ToMemo, Ray.so, Geneplore AI.
How do you think we should go about this change? Should better integrations be moved to the top, highlighted, starred, or something else?
@mowentian commented on GitHub (Feb 17, 2025):
awesome-deepseek-integration is open for every one, and we do not recommend integrations, every integrations is good
@wdpatti commented on GitHub (Feb 17, 2025):
Thanks for the feedback!
I'm just saying that an integration that requires lots of user effort to set up (such as switching the OpenAI endpoint to Deepseek manually, generating API keys, etc) may not be an "integration" in the eyes of the average person who looks at this repo. I'm only suggesting this because the repository already has nearly 100 entries, some of which barely meet the definition of "integration." It's hard to say that "Wiper Fluid 9000" is "deeply integrated" with the Jeep Defender just because it can be used in any car.
@mowentian commented on GitHub (Feb 18, 2025):
Indeed, but I prefer not to introduce too much subjective judgment.
On one hand, whether it is deeply integrated with Deepseek is self-evident.
In reality, it may not be necessary to deeply integrate the official Deepseek API, as the Deepseek itself can be deployed open-source and Deepseek API is compatible with the OpenAI API. If there is a better AI that can provide greater assistance, it is not mandatory to insist on native Deepseek integration.