Oneric 932810c35e mrf/object_age: fix handling of non-public objects ... Current logic unconditionally adds public adressing to "cc" and follower adressing to "to" after attempting to strip it from the other one. This creates serious problems: First the bug prompting this investigation and fix, unconditional addition creates duplicates when adressing URIs already were in their intended final field; e.g. this is prominently the case for all "unlisted" posts. Since List.delete only removes the first occurence, this then broke follower-adress stripping later on making the policy ineffective. It’s also just not safe in general wrt to non-public adressing: e.g. pre-existing duplicates didn’t get fully stripped, bespoke adressing modes with only one of public addressing or follower addressing are mangled — and most importantly: any belatedly received DM or follower-only post also got public adressing added! Shockingly this last point was actually asserted as "correct" in tests; it appears to be a mistake from mindless match adjustments while fixing crashes on nil adressing in 10c792110e. Clean up this sloppy logic up, making sure no more duplicates are added by us, all instances of relevant adresses are purged and only readded when they actually existed to begin with.		2024-11-17 00:44:51 +01:00
..
mix	fix wrong type when importing emojis	2024-10-18 14:57:31 +02:00
phoenix/transports/web_socket	Migrate to phoenix 1.7 (#626)	2023-08-15 10:22:18 +00:00
pleroma	mrf/object_age: fix handling of non-public objects	2024-11-17 00:44:51 +01:00