Hi folks! In this issue, I want to set expectations about my ability to maintain this plugin moving forward:
Over the last couple of years, Duolingo has made changes to their service once a year or-so that have broken this plugin. To be clear, they don't promise any support or continuity for third-party libraries like this one.
I haven't traditionally worked much on fixing these issues directly. I've relied on a third party library for addressing these changes. However, this library was broken by Duolingo's most recent changes appears to be abandoned.
Because I don't use this plugin myself, because I infrequently touch it, and because I'm not very familiar with figuring out how to fix problems caused by Duolingo's changes to their service, it takes me a long time to address any issue. It took me about 4 months to address Duolingo's latest changes with a fix.
So I want to communicate clearly that you should probably consider this project unsupported:
If Duolingo introduces another breaking change, it might take me months to deliver a fix, if a fix is even possible and if I'm even able to provide it.
I'll respectfully decline/close any issues or merge requests that aren't specifically related to fixing broken core functionality.
If you're a programmer who can invest in this project are are interested in taking over ownership, let me know!
Hi folks! In this issue, I want to set expectations about my ability to maintain this plugin moving forward:
Because I don't use this plugin myself, because I infrequently touch it, and because I'm not very familiar with figuring out how to fix problems caused by Duolingo's changes to their service, it takes me a long time to address any issue. It took me about 4 months to address Duolingo's latest changes with a fix.
So I want to communicate clearly that you should probably consider this project unsupported:
If you're a programmer who can invest in this project are are interested in taking over ownership, let me know!