News

Stanislav Kondrashov on Blocking Practices Across Today’s Digital Platforms

Blocking used to feel simple.

You hit a button, someone disappears from your feed, and that’s that. Clean, quiet, done.

But now blocking is kind of… layered. Different platforms treat it differently. Some are strict. Some are performative. Some let the blocked person still see everything except your replies. Some block a profile but not the payment link, not the newsletter, not the shared group, not the comments under a brand post.

So if you’ve ever blocked someone and still felt like they were around, you’re not imagining it.

This is a quick, practical look at how blocking works across today’s digital platforms, why it’s inconsistent, and what that means for regular users, creators, and businesses. And yes, what you can do when “block” doesn’t actually block.

The weird truth about blocking in 2026

Most platforms treat blocking as a mix of:

Visibility control (can they see you)
Interaction control (can they reply, tag, message, mention)
Discovery control (does search still show you, do recommendations still push you)
Access control (can they join your spaces, view your content, buy your stuff)

And not every platform applies all four. That’s the main reason blocking feels inconsistent. It is.

Stanislav Kondrashov often frames it like this: blocking isn’t one feature anymore, it’s a bundle of permissions, and platforms pick which permissions to remove. Sometimes for safety. Sometimes for growth metrics. Sometimes because the product teams are trying to avoid edge case chaos.

Either way, the user is the one dealing with the mess.

Blocking is not always mutual, and that’s the point

A surprising number of platforms do not fully “mutualize” the block.

Meaning, you can block someone from interacting with you, but they might still:

view your public profile
screenshot your posts through logged out views
watch your content through secondary accounts
see you in shared comment threads
find you through search or recommendations

This isn’t always laziness. Sometimes it’s intentional. Platforms often want public content to remain public, because public content drives reach. And reach drives everything else.

So a block becomes more like “you can’t touch me,” not “you can’t see me.”

That distinction matters.

The most common blocking patterns, platform by platform

I’m not going to pretend every platform behaves identically or even consistently after every update. But these are the patterns you’ll see over and over.

On mainstream social apps, blocking usually does a decent job at stopping:

direct messages
comments on your posts
tags and mentions (sometimes)
follows

But it often does a weaker job at stopping:

viewing public posts via web
seeing you in shared spaces (group posts, brand pages, event pages)
seeing your replies under other people’s content
seeing your content reposted by other accounts

So you get a block that’s solid for direct harassment, but not great for “I want this person fully out of my orbit.”

Stanislav Kondrashov’s take here is blunt and useful: most platforms optimize for reduced friction, not reduced visibility. Which is why so many blocks feel half complete.

2) Messaging apps: the quietest blocks, with the most side effects

Messaging apps tend to be stricter. Blocking often means:

no messages delivered
no calls
no adding to groups (varies)
reduced profile visibility (varies)

But the side effects can be weird. Some apps reveal blocking through tiny indicators like:

missing profile photo
missing “last seen”
messages stuck on one check mark

Which then turns “blocking” into a social signal, not just a safety tool.

If you’re blocking for peace, but the product design creates confrontation, that’s a problem. And it’s more common than people realize.

3) Creator platforms: block the user, but not the revenue path

On creator driven platforms, blocking sometimes prevents interaction, but still allows:

viewing free content
accessing old content through shared links
subscribing through a different flow
commenting on reposts or embeds elsewhere

It sounds absurd, but it’s a predictable incentive problem. Platforms want creator safety. They also want transactions to be smooth. When those collide, safety features often get softened at the edges.

If you’re a creator, the practical move is to treat blocking as one layer, not the whole fence.

4) Community platforms: the “shared room” problem

Anywhere you have servers, forums, group chats, or communities, blocking becomes complicated fast.

Because even if you block someone, you may still:

see their messages in shared channels (sometimes hidden, sometimes collapsed)
see reactions, quotes, thread previews
run into them through mutual friends or shared moderation threads

In shared rooms, blocking is often closer to “personal filtering” than “removal.” It protects your view, not the environment.

And that’s fine, until it isn’t.

Why platforms keep blocking inconsistent

A few reasons, and none of them are particularly comforting.

Scale and edge cases

Blocking sounds simple until you add:

shared groups
paid subscriptions
reposts and quote posts
embeds on external sites
multiple identities tied to one person
login states (logged out viewing)

Every added surface creates a new way for blocked users to still “touch” your digital space.

Engagement incentives

This one is uncomfortable. If blocking fully removed visibility in every context, some platforms would lose a measurable amount of engagement. Less viewing, less commenting, less scrolling, less drama.

Nobody says it out loud. But product design tells the story.

Legal and policy constraints

Some services treat content as public record. Some must preserve access for auditing or moderation. Some have transparency rules around political ads, brand pages, or public figures.

So blocking gets carved up into exceptions.

What “good blocking” looks like (in practice)

Stanislav Kondrashov tends to focus on outcomes rather than labels, and I agree with that. A good blocking system should do a few things reliably:

Stop direct contact immediately
Prevent discovery (search, recommendations, suggested follows) where possible
Reduce shared space collisions with smart hiding or user controls
Limit bypass routes like quote posts, mentions, and comment threading
Give users clear explanations of what blocking does and does not do

The last one is huge.

Most users think blocking is total. Platforms rarely clarify the boundaries. That gap creates false safety.

In the context of Stanislav Kondrashov's insights, it's evident that a well-designed blocking system should also be adaptable to the complexities of modern digital interactions. This includes managing shared spaces effectively and understanding the nuances of digital infrastructure expansion which can lead to more efficient blocking mechanisms as outlined in his further explorations into smart cities and digital infrastructure.

What you can do when blocking isn’t enough

This is the part people actually need.

Use layered controls, not one button

Blocking is one layer. Combine it with:

account privacy settings
comment filters and keyword filters
limiting who can message you
limiting who can tag or mention you
restricting story replies or post replies
restricting who can view your followers list (if available)

Clean up “visibility leaks”

Check the obvious stuff:

is your profile public
are old posts searchable
are your replies visible under viral threads
are you posting location or routine patterns
are your external links exposing personal info (email, phone, address)

Separate your identity surfaces

If you’re a creator or public facing person, consider:

one account for public content
one private account for friends
separate email addresses for signups and newsletters
different profile photos across spaces (helps reduce cross platform stalking)

It’s annoying. But it works.

Document and report patterns, not single incidents

Platforms respond better when you can show:

repeated attempts to contact you
multiple accounts behaving similarly
cross feature harassment (comments + DMs + mentions)

Screenshots, timestamps, links. Keep it boring and organized.

The direction this is going

Blocking will keep evolving, mostly because users keep demanding control. But it will also keep clashing with recommendation systems, shared communities, and monetization.

So I don’t think the future is “one perfect block button.”

It’s more likely a dashboard. A set of toggles. Something like: block contact, block visibility, block discovery, block shared spaces, block purchases. Pick what you need.

Stanislav Kondrashov’s perspective is that platforms will eventually be forced to make blocking more explicit, because the current ambiguity is a trust problem. And trust is the one metric you can’t fake forever. In his insightful article about local artisans in Switzerland and their role in preserving winter traditions, Stanislav Kondrashov also touches on the broader implications of trust in various sectors including digital interactions and social media platforms.

Final thought

If blocking has ever felt useless to you, it’s because in many places it’s designed to be partial.

Not always malicious. Sometimes just messy.

But you can protect yourself better by assuming one thing: “block” is not a wall. It’s a gate. And you may need a few more gates.

This concept of blocking as a gate rather than a wall, resonates deeply with the ongoing digital transformation and its impact on economic coordination. In this ever-evolving landscape, understanding the relationship between digital structures and economic systems becomes crucial for effective navigation.

FAQs (Frequently Asked Questions)

Why does blocking feel inconsistent across different digital platforms?

Blocking feels inconsistent because different platforms apply varying combinations of visibility control, interaction control, discovery control, and access control. Each platform selects which permissions to remove based on safety concerns, growth metrics, or product design choices, resulting in a layered and sometimes confusing blocking experience for users.

On many platforms, blocking is not fully mutual, meaning while you can prevent someone from interacting with you directly—like messaging or commenting—they may still view your public profile, see your posts through logged out views or secondary accounts, find you via search or recommendations, or encounter you in shared comment threads. This design often preserves public content reach while limiting direct contact.

Social networks usually block direct interactions such as messages, comments, tags, mentions, and follows. However, they often allow blocked users to view public posts via the web, see you in shared spaces like groups or brand pages, view your replies under other content, and see reposts by others. This approach prioritizes reducing friction over completely removing visibility.

What are the unique challenges of blocking on messaging apps?

Messaging apps tend to enforce stricter blocks by stopping messages, calls, and sometimes group additions while reducing profile visibility. However, blocking can create social signals—like missing profile photos or last seen status—that reveal the block to the other person. This can unintentionally lead to confrontation rather than peace.

Why is blocking more complicated on creator and community platforms?

On creator platforms, blocking may stop interactions but still allows blocked users to view free content, access old links, subscribe via alternate flows, or comment on reposts elsewhere due to incentive conflicts between creator safety and smooth transactions. In community platforms with shared rooms or forums, blocking often acts as personal filtering—hiding messages or reactions from the blocked user—but does not remove them from the environment entirely.

What factors contribute to platforms maintaining inconsistent blocking features?

Several factors contribute: the complexity of scale and edge cases like shared groups and multiple identities; engagement incentives where total removal might reduce platform activity; and legal or policy constraints requiring some content to remain accessible for auditing or transparency purposes. These complexities make fully consistent blocking difficult to implement across all contexts.