Oneric 89801abad5 federation/in: drop remote part from received emoji reactions ... The remote part is included in federated emoji names by e.g. Iceshrimp.NET ever since remote emoji support was added in 4d21aa1670 and as of writing it still continues to do so. It adds no value for us though; we add the remote part automatically based on the URL and it makes it more difficult to correctly coalesce the original reaction (from a user for whom the moji was local) and the subsequent reactions with the identical emoji from users of other instances. Additionally the remote part can cause issues when later used with our REST API. For non-reactions this is unproblematic and thus there’s no need to change anything there. Use a migration to fix up existing activities. This will cause some (further) desync from the inlined reactions array, but will be fixable with the resync mix task and avoids issues when running the resync without first fixing existing activities.		2025-08-30 00:00:00 +00:00
..
config
credo/check/consistency
fixtures	Prevent key-actor mapping poisoning and key take overs	2025-02-14 22:10:25 +01:00
instance_static
mix	test/emoji: clean up after failure	2025-06-07 21:22:37 +02:00
pleroma	federation/in: drop remote part from received emoji reactions	2025-08-30 00:00:00 +00:00
support	Fix Content-Type sanitisation for emoji and local uploads	2025-03-10 19:45:26 +01:00
test_helper.exs	add a snapshot test for api prefixes	2025-02-23 16:51:48 +00:00