-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
Payments #367
Comments
Hi, we are working on making Telegraph as solid as possible, but we will add payments soon |
check it. rejected for no reason |
@pou , this is quite a rude comment: the reason is that payments are a sensible feature, and I want to be sure that the implementation is solid and sticks with our code style, so it is not planned until I find the time to analyze the issue and write a proper code for it. We aim to have a top quality code and a trustworthy codebase, it is not simply "throw a feature and release it", but more of a long-term plan that involves support and maintenance meanwhile, feel free to fork the project and maintain your implementation |
Hello, I was wondering if you could kindly share an estimated timeframe for the release of this new feature? Thank you! |
I am planning to release a working version before the end of September |
I understand that it is important to you to maintain the quality and reliability of our codebase, and I respect that. However, I would also like to discuss some important points in order to find the best way forward. While I acknowledge that you are doing everything possible to create high-quality software, I would like to suggest considering the possibility of implementing the payment feature more promptly. Perhaps we can find a compromise that allows us to move forward with this project without compromising the code quality. If it is convenient for you and if time constraints allow, I am willing to contribute and assist in analyzing and developing the appropriate code. Maybe we can find a way to mitigate some of the challenges involved in implementing this functionality while strengthening our codebase simultaneously. While being persistent in achieving our goals, it is also important to remember that the urgency of certain features may be crucial in fulfilling user requests or achieving our business objectives. Taking into consideration their needs can help us strike a balance between quality and deadlines. Let's work together, communicate openly and transparently, to find a solution that satisfies our common interests. I am confident that through our collaborative efforts, we can achieve the best outcome and continue the development of our project. |
@pou I understand your point and the payment feature is on top of my todo list I've seen your implementation, but such a feature should be included in a wider plan, I first need to implement all support features that unlock the payment API, in order to move one step at a time You are free to contribute and we can collaborate on this, but we should start with designing the feature first |
@fabio-ivona Hi, may I know the latest status of the payment feature? |
Hi @jialeee17 we have a working proof of concept that is under testing in our private projects. As soon as I'm sure it works, will release it |
Anyone interested in testing payments? we are about to release and would like to have a beta tester before going public |
I'm interested. My project really needs payments |
Hi! thanks for your help you can test payments requiring the dev-payments branch ( we are awaiting for your feedback 🙌 |
Hi. Are there any plans to implement telegram payments?
The text was updated successfully, but these errors were encountered: