Why reviving QKSM and not other QKSM fork for example Partisan SMS? #33
-
|
Maybe its even good question to Readme |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
I'm not sure I understand the question. |
Beta Was this translation helpful? Give feedback.
-
|
you didnt even use 3.10 branch right? |
Beta Was this translation helpful? Give feedback.
-
|
@octoshrimpy Hey Marcos, I have a similar question (at least, I think so. The above is a little hard to parse. Let me see if I can phrase my question more clearly) Do you have a particular reason why you started your own fork of QKSMS, as opposed to contributing to (or at least forking off of) an existing fork like wrwrabbit/Partisan-SMS? Partisan has added some optional encryption features, but I think they have also made some general improvements to the app. Have you checked if they've done anything worth copying? (note: I'm actually not sure if Partisan is still actively maintained; I just now posted in their Discussions asking about it) |
Beta Was this translation helpful? Give feedback.
-
|
@e-t-l idk Why is the title hard to parse? Partisan is dead, 9 months is too long. |
Beta Was this translation helpful? Give feedback.
-
|
I've taken this undertaking as a way of becoming more comfrotable with CI/CD, as well as learn kotlin. I did use the 3.10 branch, and had it come back and bite me once already 😅 As of now, I do believe quik is the most up-to-date fork of QKSMS. |
Beta Was this translation helpful? Give feedback.
I've taken this undertaking as a way of becoming more comfrotable with CI/CD, as well as learn kotlin. I did use the 3.10 branch, and had it come back and bite me once already 😅
As of now, I do believe quik is the most up-to-date fork of QKSMS.