
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
I’d like to respectfully add some perspective here.
Simply sharing a CodeBase link is not automatically self-promotion, especially when the context is technical and the recommendation is directly relevant to the user's question. CodeBase is a public resource intended to be shared, and it's freely available for the benefit of the community.
It becomes self-promotion only when there’s no real context, or when the sole purpose of the message is to drive attention to oneself or one's work, without contributing to the discussion in a meaningful way.
In this case, the original suggestion pointed directly to a specific problem (tick downloading), and the author offered a solution hosted in the CodeBase. That’s a valid and helpful contribution, not a promotion.
Otherwise, we risk discouraging developers from sharing their free tools just because they happen to be the authors, which goes against the very spirit of collaboration that the CodeBase was created for.
Also, let's remember: moderators recommending their own code is more delicate and understandably discouraged to avoid perceived bias. But that’s not the same as a regular user pointing to a resource, especially when it solves a problem concretely.
Let’s not apply rules in such a rigid way that it hurts the exchange of knowledge. Context always matters.
I’d like to respectfully add some perspective here.
Simply sharing a CodeBase link is not automatically self-promotion, especially when the context is technical and the recommendation is directly relevant to the user's question. CodeBase is a public resource intended to be shared, and it's freely available for the benefit of the community.
It becomes self-promotion only when there’s no real context, or when the sole purpose of the message is to drive attention to oneself or one's work, without contributing to the discussion in a meaningful way.
In this case, the original suggestion pointed directly to a specific problem (tick downloading), and the author offered a solution hosted in the CodeBase. That’s a valid and helpful contribution, not a promotion.
Otherwise, we risk discouraging developers from sharing their free tools just because they happen to be the authors, which goes against the very spirit of collaboration that the CodeBase was created for.
Also, let's remember: moderators recommending their own code is more delicate and understandably discouraged to avoid perceived bias. But that’s not the same as a regular user pointing to a resource, especially when it solves a problem concretely.
Let’s not apply rules in such a rigid way that it hurts the exchange of knowledge. Context always matters.
Got it. Thanks.
I’d like to respectfully add some perspective here.
Simply sharing a CodeBase link is not automatically self-promotion, especially when the context is technical and the recommendation is directly relevant to the user's question. CodeBase is a public resource intended to be shared, and it's freely available for the benefit of the community.
It becomes self-promotion only when there’s no real context, or when the sole purpose of the message is to drive attention to oneself or one's work, without contributing to the discussion in a meaningful way.
In this case, the original suggestion pointed directly to a specific problem (tick downloading), and the author offered a solution hosted in the CodeBase. That’s a valid and helpful contribution, not a promotion.
Otherwise, we risk discouraging developers from sharing their free tools just because they happen to be the authors, which goes against the very spirit of collaboration that the CodeBase was created for.
Also, let's remember: moderators recommending their own code is more delicate and understandably discouraged to avoid perceived bias. But that’s not the same as a regular user pointing to a resource, especially when it solves a problem concretely.
Let’s not apply rules in such a rigid way that it hurts the exchange of knowledge. Context always matters.