mirror of
https://github.com/NdoleStudio/httpsms.git
synced 2026-04-28 20:35:51 +03:00
[GH-ISSUE #225] Feature: SMS Poll #25
Labels
No labels
In Review
documentation
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/httpsms#25
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 @malys on GitHub (Jul 2, 2023).
Original GitHub issue: https://github.com/NdoleStudio/httpsms/issues/225
Hi,
I use HTTP SMS to send sms using API. Thank you for your app.
I combine HTTP SMS with SMS-Poll. I think that both products are the same philosophy.
I could be great to integrate it.
Bye
@AchoArnold commented on GitHub (Jul 2, 2023):
Hello @malys
What will the integration look like from your point of view?
The way I see it, httpsms is a base platform and you can build a polling system ontop of it if you want.
SMS-Poll is specific to polls while httpsms can be used for whatever use case you want. Adding an SMS poll feature in httpSMS is a very specific use case and for most users, this feature will not be needed.
@malys commented on GitHub (Jul 3, 2023):
@AchoArnold
Thank for you your quick answer.
Yes I understand your point of view. For you, it's a low level service (SMS gateway, technical solution)
To my mind, It could be a high level solution to provide services based on SMS sent from mobile device & mobile application.
ex: supporting SMS poll, SMS newsletter ...
In this case, httpSMS could replace third party professional webservices proposing free, low cost solution using own SIM card for personal use (association, end user, ...).
Another idea, I'm not confortable to enable Incoming message.
I understand that this feature is useful but it's a huge security issue. (ex: 2FA SMS validation could be stolen).
To my mind, it could be interesting to apply "white list strategy" by default and force android user to define a list of phone numbers to synchronize and for example '*' to forward every message.
For this reason, it could be difficult to publish android apps on play store, no?
Perhaps, F-Droid is more permissive and it could help you to manage updates.
I hope that my contribution can help you.
If you want, you can contact me for testing new version.
Thanks and good luck for your next development
@AchoArnold commented on GitHub (Jul 3, 2023):
Right now there is a setting in the android app where you can disable incoming messages completely. Adding the "allowlist" for incoming phone numbers on the phone is a nice feature but that will mean some of the state will be on the phone and some will be on the API which introduces more complexity.
Play Store doesn't allow these types of apps unless I add a full SMS messenger functionality to it so people can send/receive text messages on the APP I plan to do that some day in the future.
I get your vision. Unfortunately, that's now how I see the project at the moment but It's something to keep in mind. Thanks for your feedback.
F-Droid is awesome and I'll love to integrate with it. Feel free to send a PR if you can do the integration.