DEV Community: Niloy Majumder

Nothing you’ve ever sent has truly disappeared: a psychological breakdown

Niloy Majumder — Tue, 19 May 2026 05:05:14 +0000

Hello world, I’m Niloy, Co-founder, Product Lead & Researcher at BurnLink.Today, I wanted to share something interesting about the thinking behind our product "BurnLink" — what led us to build it in the first place from a psychological perspective and what's the future of BurnLink.

A small breakdown of the neuroscience and psychology behind why your instincts about file sharing are often more accurate than the tools themselves.

There is a moment; brief, easily dismissed — that happens right before you send something sensitive. A half-second pause. A small internal question: is this okay? Then you override it and hit send anyway.

Neuroscientists who study decision-making have documented what they call somatic markers where physical signals the body generates ahead of conscious reasoning, based on prior experience with similar situations. The original research, from Antonio Damasio, was about financial risk decisions. But the broader point holds: your nervous system can flag a situation as worth pausing on before your conscious mind catches up.

Whether that's precisely what's happening when you hesitate before sending a file — that's a stretch to claim definitively. But the behavior matches: you've seen enough news about data breaches, you've heard enough about cloud retention policies, you've had enough moments of "wait, where did I send that?" and some part of you registered it, even if you never consciously processed it.

The hesitation isn't irrational anxiety. It's compressed pattern recognition. The question is what you do with it.

"Privacy anxiety isn't irrational. It's the correct response to how the internet actually works."

In 2019, a study published in Computers in Human Behavior identified a phenomenon researchers called privacy fatigue — a state where people stop protecting their data not because they stopped caring, but because the effort felt futile. The system was too opaque. The controls too buried. The defaults always against them.

This is learned helplessness applied to data. Martin Seligman's original research on learned helplessness showed that when people repeatedly find they cannot control outcomes, they stop trying — even when control becomes available. The behavior persists long after the cause is gone.

Most people using Google Drive, email, or Slack to send sensitive files aren't naive. They're fatigued. They know something is off. They've just run out of alternatives — so they compress the discomfort and move on.

Research note:

A 2023 Pew Research study found 79% of Americans feel they have little control over data companies collect — yet the majority continue using the same platforms. Researchers have called this privacy fatigue: not indifference, but the behavioral result of repeatedly finding no viable alternative. It looks like acceptance. It isn't.

Here is the thing nobody explains when you sign up for cloud storage or email: the default state of the internet is permanence. Everything is retained. Copied. Synced. Indexed. Your file doesn't go to one place, it distributes across systems you don't control, under retention policies you didn't read, held by third parties with no accountability to you.

The word "sharing" implies a temporary social act. I share a meal, we both eat it, it's gone. But digital sharing has been quietly redefined. Sharing now means distributing forever, to an address list you only partially see, on infrastructure you cannot audit.

The anxiety you feel before hitting send is your brain noticing this mismatch, the gap between what "sharing" is supposed to mean and what actually happens. Your instincts were built for a world where sharing was finite. The internet broke that contract without telling you.

"The file doesn't go to one place. It distributes across systems you don't control, under retention policies you didn't read."

Most privacy tools operate at the layer of access control who can see what, under what permissions. Password protection. Expiring links. View-only modes. These are real improvements. But they don't address the underlying problem, which is that the file still exists somewhere after the exchange. The surface area of risk shrinks, but it doesn't disappear.

Psychologically, this matters. Research on perceived control the degree to which people feel they can influence outcomes, consistently shows it's one of the primary variables in whether people feel safe in a situation. Shrinking risk isn't the same as restoring control. As long as the file persists somewhere outside your reach, a residual anxiety persists with it. You're managing the fear, not resolving it.

Email is basically a non-revocable communication system. Once it’s delivered, control shifts fully to the recipient and their infrastructure—you can’t guarantee deletion, retention, or how it gets redistributed afterward. If it ends up in a breach three years from now because their IT security didn't keep up. You extended trust once and that trust became permanent.

This is the one of those core psychological problems that BurnLink is designed to solve. Not encryption as a feature. Not "better" file storage. But the restoration of temporal control, the ability to say: this exists for exactly as long as it needs to, and then it stops.

"Shrinking risk isn't the same as restoring control. As long as the file persists somewhere outside your reach, the residual anxiety persists with it."

There's a reason we used a phrase "burn after reading" and it carries cultural weight. From wartime intelligence to personal letters, the act of destruction after reading was understood as the ultimate trust signal: I shared this with you completely, and now it no longer exists. The act of sharing didn't create a permanent object. It created a moment. That's the model we are rebuilding for the digital world. The moment of transfer is real and complete, and then it's over.

We are at an early inflection point in how people think about digital permanence. GDPR, data minimization laws, the right to erasure these aren't bureaucratic quirks. They're early signals that permanence is becoming recognized as a liability, not a feature. The next version of the internet won't ask you to manage your privacy through settings menus and opt-outs. It will build privacy into the architecture of transfer itself. I guess I've discussed a lot, should probably stop now haha.

BurnLink is currently a small, precise product that sits at the beginning of that shift. It doesn't ask you to change how you think. It just gives your instincts somewhere to land. That hesitation before you hit send is not anxiety to be managed. It's intelligence to be trusted. We’ve been building BurnLink as a response to that signal. And as we move forward, we’re seeing the world shift into a new era of technology one where BurnLink’s role will continue to evolve alongside it..

(to be continued..)

A Complete Beginner's Guide to Zsh Setup on WSL

Niloy Majumder — Sun, 22 Jun 2025 18:50:46 +0000

bluefloyd • June 23rd 2025

If you're a new developer using WSL (Windows Subsystem for Linux) and want a terminal that feels fast, looks amazing, and helps you work smarter, setting up zsh with a few enhancements can completely change your workflow. In this blog post, I'll walk you through my complete Zsh setup on WSL, step-by-step.

🧰 Setup

Zsh (with Oh My Zsh)
Powerlevel10k theme
Plugins: Autosuggestions & Syntax Highlighting
Nerd Fonts
GUI Terminal & Dircolors themes
Useful dev aliases

Before diving into the ZSH setup, let's make sure you have WSL (Windows Subsystem for Linux) with Ubuntu installed on your system.

Verify WSL and Ubuntu Installation

Open your terminal (Command Prompt or PowerShell) and run the following command to check if WSL is installed:

wsl --list --verbose

If Ubuntu is installed properly, you should see an output similar to this:

  NAME      STATE           VERSION
* Ubuntu    Running         2

If you don’t have WSL or Ubuntu set up yet, you can install them by following Microsoft’s official guide here: Install WSL

Now get back into the main process.

🛠️ Step-by-Step Zsh Setup on WSL (Ubuntu)

1. Install Zsh & Oh My Zsh

sudo apt update
sudo apt install zsh -y
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

2. Set Zsh as Your Default Shell

chsh -s $(which zsh)

You may need to restart WSL for the change to apply.

3. Install Powerlevel10k Theme

Copy the following into your WSL terminal:

git clone --depth=1 https://github.com/romkatv/powerlevel10k.git \
  ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k

Then, edit ~/.zshrc:

ZSH_THEME="powerlevel10k/powerlevel10k"

Run:

source ~/.zshrc
p10k configure

For more theme

4. Install Nerd Font (for Icons)

Powerlevel10k needs a Nerd Font. I recommend MesloLGS NF:

Download here: https://github.com/romkatv/powerlevel10k#manual-font-installation
Install on Windows
Set it as the font in Windows Terminal > Settings > Ubuntu profile > Appearance > Font Face

5. Install Plugins

I didn't install so many plugins as I don't need many of them, so I only used plugins for editing text and a couple of plugins for formatting. However, if you need to install more plugins you can visit the list of extensions from here Zsh Plugins

Autosuggestions:

git clone https://github.com/zsh-users/zsh-autosuggestions \
  ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

Syntax Highlighting:

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git \
  ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting

Add plugins to your ~/.zshrc:
Then find the plugins=(...) line and add:

plugins=(git zsh-autosuggestions zsh-syntax-highlighting)

Then reload:

source ~/.zshrc

🎨 Color Scheme (optional): Solarized Dark Dircolors Theme

git clone https://github.com/seebi/dircolors-solarized.git ~/.solarized-dircolors
cp ~/.solarized-dircolors/dircolors.ansi-dark ~/.dircolors

In ~/.zshrc, add:

eval "$(dircolors -b ~/.dircolors)"

Useful Developer Aliases

Add these to the bottom of your ~/.zshrc:

alias ll='ls -la --color=auto'
alias gs='git status'
alias ga='git add .'
alias gc='git commit -m'
alias gp='git push'
alias codehere='code .'
alias open='explorer.exe'
alias desktop='cd /mnt/c/Users/$USER/Desktop'

Then reload the zsh config file:

source ~/.zshrc

This setup turns your terminal into a beautiful, fast, and powerful command center for development. This is my first tech blog, since I'm also a newbie, trying to explore things, get ideas, and share this with the world, so I might have some mistakes. Pardon me. Thank you for reading.
If you give this setup a try, I’d love to hear your thoughts in the comments!

Connect with me:
Linkedin or GitHub!