[deleted] Not maintained anymore
https://github.com/moezbhatti/qksms/releases
Last update was January this year. Still being maintained, but it's one of those devs who keep the "stable" version for a long time, and run with the prerelease channel.
[deleted] Not maintained anymore
https://github.com/moezbhatti/qksms/releases
Last update was January this year. Still being maintained, but it's one of those devs who keep the "stable" version for a long time, and run with the prerelease channel.
Graphite What about 476 open issues?
Why do my comments need approval? What's happening?
(It seems that the number is triggering this approval)
[deleted] it must be either your day off work today or your main job, I don't know which one.
[deleted] What do you mean?
Yeah, agreed that QKSMS is a problematic app for that reason. (There was some activity on their "pre-release" on Jan 16th 2023, but I agree that it's not too promising)
One thing I struggled with though - is an out of date SMS app really all that much worse than the SMS protocol itself? My understanding is that the SMS protocol is so badly vulnerable / compromisable that using it at all is a huge security vulnerability, regardless of the app.
My position is: I'm unwilling to abstain from using SMS entirely (too many contacts use it exclusively, I don't have the social capital to cut those off or make them switch to Signal), I dislike the AOSP messenger aesthetics, and I hope to avoid using google software on principle.
Given those, I chose QKSMS because it seemed to be the "lesser of the evils".
I have not tried @thompson's other recommendations though (Molly, Partisan, Simple SMS).
I'd be open to trying other apps / rethinking my approach too.
[deleted] don't take things to seriously please, that's all.
zzz One thing I struggled with though - is an out of date SMS app really all that much worse than the SMS protocol itself? My understanding is that the SMS protocol is so badly vulnerable / compromisable that using it at all is a huge security vulnerability, regardless of the app.
Using Google Messages with RCS is the way. At least you get E2EE encryption.
[deleted] Are we talking about me being confused about why some of my comments needed approval? (Which is because of that number.)
[deleted] don't take it the wrong way mate, I like you. But you've made 52 posts so far today and there must must be a reason for that.
[deleted] If I'm not hyperactive on this forum, then I'm on a different one. There were times when I would be quite active on Matrix, but I don't really like it because there are just too many things going on at once, and it's just messy for me, so I prefer forums.
This one is my favorite one because I love GrapheneOS project. It's not my day off today and this is not my job unfortunately. (If GrapheneOS needs volunteer moderators from Eastern Europe, then I'm available. I can go through a tryout to prove myself.) 😀
Skyway This is probably because comments by spam bots usually contain numbers.
To confirm, this does not have SMS integration like the old Signal had.
Developer says so at the bottom of this thread. https://github.com/johanw666/Signal-Android/issues/41
Max-Zorin Not only that, but I wouldn't use a Signal fork by a random guy, especially if I'm using the same app for communicating over Signal.
One thing I absolutely hate about QKSMS is that if you receive five messages from five different people, there will be five incoming message icons on the status bar which looks messy. Google Messages combine them together and show only one incoming message icon on the statusbar. I reported this issue to the QKSMS developer long time ago, but he ignored it like all other open issues.
What is happening? Why is every message with numbers need approval?
Deleted.