Blocking people should actually work

There are features you can sell with a headline, and there are features you can only live without until you can't. Blocking is the second kind. No announcement ever wins a product launch, but its absence quietly decides how the space feels to everyone in it. Here's what we think about it, and why we keep coming back to it.

Control is a feature

For a long time, Hopick had no way to block anyone. You could scroll past a person, but you couldn't stop them mattering to your feed. That sounds like a small gap — most people rarely block anyone. But there's a difference between knowing you can't do a thing and knowing you can, and the difference is not hypothetical. It decides whether an app reads as safe ground or as somewhere you have to stay alert.

A block you never use still does its work, because it sets the terms of the room. That's what we mean by calling control a feature: not a request, not an edge case. Just a quiet guarantee underneath everything else.

It has to be two directions

A half a block is a worse version of nothing. When you block someone, their content leaves your feed — that's the obvious part. But a real block also works the other way: yours leaves theirs. It hides the connection itself, not just your view of it. Otherwise you've tidied your own screen and called it done, while the other person keeps a window on you. Nothing about the situation that made you block has changed for them.

That's not a petty detail. It's the difference between a filter and a boundary. A filter is what you apply to content. A boundary is what you draw between two people.

The leak is in the notifications

The place a block most often quietly fails is exactly where we forget it matters most: notifications. You block someone, and an hour later a new alert from them slides in — the block suddenly means nothing, and you feel exposed all over. A true block reaches into the notification layer. No new alerts from that person. The history already sitting there is cleared the moment you block. If the app can still surface them later, it has. Then the block was a suggestion, nothing more.

Unblocking as forgiveness — and the doors stay open

It is tempting to make blocking a one-way and final, to decide it once and never again. But people block in anger, in small misunderstandings, in the middle of a bad day. That isn't the point. The point is that you are the type who decides whether a door stays shut, and you should be able to reopen it without creating an entire ceremony. So every block lives in the same list, under settings, where you can see what you've ever done and undo any of it. Blocking is a decision. Re-blocking is a decision too. That these both stay easy is what makes the feature real: it is yours to use, not a trap you've fallen into.

What we're building underneath

We like to say Hopick is about reliability and speed, and it is. But there is a quieter third value, and this is where it shows up. A community app asks a lot of you. It wants to live in your pocket, to become part of a habit. In return, it should hand you the controls to that exactly. The people you can't be bothered with, gone. The places you'd rather not be, closed. The ability to shape your own space all the way down is what a real home offers, and we don't think you should have to plead for it.

If you've ever wished a platform would just let you make someone stop mattering to you, you already know why any of this matters. We're trying to get that right, slowly and honestly. Come see how we're doing on Discord.

Blocking people should actually work · Hopick