In this previous post I posted a patch for inclusion in AntennaPod. However that post ended up with:
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.
I do see that who posted the last message there, and as mentioned in this other post I did spend a few hours on finding a way to make everyone happy. It seems however that messing around with finding an acceptable way to work with Microsoft GitHub is about as uninspiring as everything about that horrible system. I have no idea when I will feel like spending enough time on it, but obviously it’s not going to happen anytime soon.
Please remember that this patch addresses a very real bug, which is easily and reasonably misexperienced as fatal data corruption of the entire AntennaPod database. Had this been a feature to scratch an itch of mine I would see the point of trying to force me into using MSGH to pitch it. Pushing for use of unacceptable services to contribute a bugfix of this kind though, isn’t that policy frankly acting against the best interest of users?
The branch gets a trivial merge conflict towards current master, which has been resolved on the fix/inform_on_db_moved-3.6.0 branch.
Would someone be able to have a look at merging this? If you need it as a pull request on your favorite platform for self-harm, I’m not objecting to one getting opened. I will do my participation here though.