Forget about stalking your crush on Facebook with this new feature!

Facebook is rolling out a feature to check if strangers have viewed your Story outside of your friends list. So, even if strangers have viewed your Story, they will still be displayed in the list. Previously, when you checked the list of people who viewed your Story, it would only show the full name of the friends list and the people who were following.

For strangers who view your Story, Facebook only displays the number in the Strangers section but not their Facebook account name. You cannot know who is the stranger who viewed your Story.

Forget about stalking your crush on Facebook with this new feature!
Previously, Facebook did not show the names of strangers viewing Stories.

And with this new update, we can completely know which strangers have "visited" our Story. Facebook clearly divides your Story into 3 audiences: friends, followers and non-followers. Accounts that have never interacted or are not friends but still view your story will now show their full account name and profile picture in the Unfollowers section.

Forget about stalking your crush on Facebook with this new feature!
New feature shows names of strangers viewing Facebook Story

Many people agree with this new feature of Facebook when they want to know all the people who have viewed the Story, ensuring privacy and transparency.

Currently, Facebook is only testing this feature on a few accounts and certain areas. If you don't have it yet, please update Facebook to the latest version and wait for the coming time.

Leave a Comment

Diagnose a SUSE Server That Hangs at the systemd Shutdown Screen

Diagnose a SUSE Server That Hangs at the systemd Shutdown Screen

Use systemd jobs and the previous boot journal to locate a slow service, mount, or storage dependency, then correct it without masking the cause.

Open Only the Web Traffic Your SLES 15 Server Needs

Open Only the Web Traffic Your SLES 15 Server Needs

Use firewall-cmd to inspect the active zone, allow HTTP safely, preserve SSH access, and verify that the rule survives a reload on SLES 15.

Diagnose SLES PAM Login Failures Without Locking Yourself Out

Diagnose SLES PAM Login Failures Without Locking Yourself Out

Trace a PAM failure to its service, account policy, or identity provider, then repair the right SLES configuration while preserving a working admin session.

SLES Boot Module Load Failure: Find the Driver and Fix It

SLES Boot Module Load Failure: Find the Driver and Fix It

Trace a failed kernel module at SLES startup, correct an obsolete boot entry or repair the required driver, and verify the next boot.

Set Up DM-Multipath on SLES 15 for Reliable SAN Paths

Set Up DM-Multipath on SLES 15 for Reliable SAN Paths

Prepare SCSI SAN paths, enable multipathd, inspect SUSE’s hardware defaults, and verify stable device maps without guessing array settings.

Clear a Zypper Lock Safely on SUSE Linux Enterprise

Clear a Zypper Lock Safely on SUSE Linux Enterprise

Find the process holding Zypper’s package lock, distinguish process conflicts from package locks, and retry updates without deleting lock files blindly.

Build a Supported SLES 15 HA Cluster with Fencing First

Build a Supported SLES 15 HA Cluster with Fencing First

Register SLE HA, bootstrap SLES 15 nodes, then add fencing, quorum, and tested service resources before relying on failover.

SLES Zypper HTTP 500: Find the Failing Repository

SLES Zypper HTTP 500: Find the Failing Repository

Trace a Zypper refresh error to SUSE, RMT, or a third-party endpoint, then apply the right server-side or cache fix without disabling essential updates.

SLES Thin Pool Out of Space: Extend LVM Safely and Restore Writes

SLES Thin Pool Out of Space: Extend LVM Safely and Restore Writes

Resolve SUSE LVM thin-pool space errors by checking data and metadata usage, expanding the pool safely, and preventing repeat outages.

When SLES Btrfs Goes Read-Only: Diagnose Before Remounting

When SLES Btrfs Goes Read-Only: Diagnose Before Remounting

Identify whether Btrfs is intentionally read-only, short on space, or protecting data after errors, then choose a recovery path that fits the cause.