UPDATE:

I've tried selectively enabling and disabling Safari extensions and it seems to be related to the Wipr 2 content blocker.

Removing that. Caution to anyone else who uses it.

Apologies to Meta.

▲

demibabs an hour ago | parent | next [-]

I’m confused as to how a content blocker could cause this. Could someone more knowledgeable than me elaborate?

▲

schleck8 an hour ago | parent | prev | next [-]

That does not sound plausible at all, wipr is an adblocker. No adblocker should be causing this. If it's spoofing your JS fingerprint and Meta uses that for suggesting accounts, wow would that be ridiculous.

	▲	pmuse 38 minutes ago \| parent \| next [-]
		Wasn't something I expected -- seems to be related to having Wipr Extra enabled. Emailed the dev about it and will share if I hear anything back. For now I have it uninstalled and have not experienced this since. Recorded a video of enabling Wipr Extra and the auth page refreshing to show three random people, might be a pain to redact it but I can try to if people really don't believe me.
	▲	gcr 23 minutes ago \| parent \| prev [-]
		My guess (pure speculation) is that Wipr sets the fingerprint to a well-known value for privacy / anonymization reasons, and Meta is indeed using that to suggest related accounts.

▲

alexinma 2 hours ago | parent | prev [-]

Good to know. thank you!