some months ago I mentioned I couldn’t see comments in safari but could in fx (on ios). figured it out now: the 1Blocker “disable comments” filter sweepingly includes lemmy comment field types, but for some reason only on safari and not fx (despite apple forcing engine as they do)
the fix: add awful.systems as an allowed domain inside 1Blocker config
I’m guessing it’s some kind of generic/wide property filter. it was a weird enough thing that I honestly did not think of it until I was literally poking at something else entirely then went “huh, hold on”
not helped by how fucking feedback-obtuse mobile devices have been made to be in their default state :||||
I’ll contact the developer to see if they can maybe finetune it for lemmy instance frontends, since it’s definitely a bit overt