I think there has to be a balance.
Most people that are “toxic” exhibits habits ingrained from childhood or trauma, they are some time aware of those habits, and the scope of the habits can be relatively limited in some cases or more generalized in others.
I would say that if that person has a “toxic” reaction, they have to be aware that they had a bad reaction, own to it and apologize later WHEN things have calmed down in their heads.
The toxic occurences in the relationship with the person should also be at a ratio where the good feelings/moments with that person are at a bare mininum of 75% vs 25% toxic. You need time to “recharge” to be able to be patient and understanding with that person when the toxic reaction is aimed at you.
So yeah balance, and if the balance doesn’t overall feel good for you, then it’s not good for you, cut it.
Well I’m not acquainted with Apk tool, but I understand a bit about reverse engineering, so I went on their github page to read about it.
Essentially, an android application is packaged under the .APK extension which lets you install and run the application on your phone. This is akin to a software with the .exe extension on windows. An .apk or .exe is a bunch of compiled code and ressources, this means that in this form, the code is mostly a bunch of mumbo jumbo that no one can understand or make edit to.
By reverse engineering, you transform the .apk to it’s initial state before compilation, the code is now organised, readable, and editable. This allows you to understand what is going on under hood and add new code and functionnalities. If you decide to edit the code, you can package/compile this extended application into a new .APK and enjoy additionnal features in the application.
Note that reverse engineering will not get you an exact copy of the code and file structures the original developper created, it is (in general) an approximation. Depending on the decompiler, you can lose variables names, function names…etc, but the code will work fine.
For an example
If the original developper had this function. private String getAge(String userId) { String age = this.users.get(userId); return age; }
Decompiling might get you :
private String getAge(String var1) { String var2 = this.var3.get(var1); return var2; }
You get the code, but it’s harder to understand than if you had the original code. So reverse engineering / decompiling is useful in some use cases, but not always a miracle.