Stories

Why I don't see many advantages in decentralized platforms

Article news.ycombinator.com

Why I don't see many advantages in decentralized platforms

Honestly, from my point of view, I don’t see many advantages in decentralized platforms, where my personal data is distributed across nodes worldwide in public. In this post, I would like to note some key points about the current landscape and problems in the on-chain world that you should know.

For example, let's take a look at the Bitcoin blockchain:

1) Block size limitations: The Bitcoin blockchain is limited due to its block size, which restricts how much data can fit in a block.

2) Expensive storage: Storing data on the Bitcoin blockchain is expensive and limited because it must be replicated across all nodes, and blockchain data constantly grows.

3) Slowness: For Bitcoin, a new block is mined approximately every 10 minutes, and full confirmation of transactions can take up to an hour.

4) Lack of privacy: On public blockchains like Bitcoin, Ethereum, and Solana, all transactions, amounts, and wallet balances are visible.

5) Limited smart contracts: Bitcoin doesn't have, or has limited, Turing-complete smart contracts.

6) Out of your control: While there’s no centralized “third party,” control is distributed among nodes and validators outside your control.

7) Immutability: On-chain data cannot be deleted; it stays forever there.

8) Hard to upgrade and deliver: Significant changes usually require a hard fork.

9) Nodes and validators have their homes: Some of them could be regulated or even shut down, that’s exactly what makes decentralization stronger than centralization — the network keeps running.

Engineers are trying to solve these problems, but most of them affect nearly every blockchain in one way or another.

In Hashmate, I made different decisions:

1) Privacy by design: You don’t have to expose your information to the service, and the service never asks for personal data.

2) Principle of minimal knowledge: The platform knows as little about you as possible. In fact, it has only what you provide.

3) Your data means your data: Once you delete something, it’s gone forever. On-chain? Right, your data stays there forever, due to the immutable nature of blockchains.

4) Centralized decentralization: Nowadays, practically all mid-size projects and platforms are distributed under the hood. I mean load balancers, replicas, computational and storage nodes. The difference is who controls this infrastructure — random people or a company. So, it’s more about Ownership than Privacy.

5) Easy upgrades: Centralized control over infrastructure allows easy delivery of changes and upgrades.

6) Public content: Most content is public by its nature.

Just to be clear, I’m not against decentralization or anything like that. My main point is that we can build truly centralized and fully private platforms as well — it’s just that most existing ones lack many essential core privacy features.

TO SUM THINGS UP:

- Decentralization doesn’t mean Privacy.

- Decentralization means Distribution.

- Privacy is about design, not Distribution.

- Public decentralization means your history and transactions are visible, trackable, and stay there forever in public.

- Just one good thing I could really say is that decentralization could mean Ownership — but your data is spread across nodes that you don’t control.

- Being on-chain is still expensive.

Discussion 2 comments · 2 points · DeveloperOne · 2025-11-04
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.