@BoorishBears 72d
> and then swear up and down that their code is perfect

Even worse when they don't do this and just flat out admit they broke a usecase intentionally and label it Won't Fix because the team that implemented the breaking change is also the team that triages the issue. See logcat access being completely broken in Android 13: https://www.reddit.com/r/tasker/comments/wpt39b/dev_warning_...

@yazzku 72d
That's completely fucked up. Arrogance much or?
@ofchnofc 71d