The linked post dismisses the v0.18.0 upgrade as a possible cause, but appears to do so without evidence and it’s by far the most likely explanation.
Whether the fix has to happen on the Lemmy or the kbin side to restore compatibility is an open question, but I don’t see any evidence of anything beyond a normal upgrade that broke an untested cross-app interaction.
The linked post dismisses the v0.18.0 upgrade as a possible cause, but appears to do so without evidence and it’s by far the most likely explanation.
Whether the fix has to happen on the Lemmy or the kbin side to restore compatibility is an open question, but I don’t see any evidence of anything beyond a normal upgrade that broke an untested cross-app interaction.