Here's Part 2 of my Pubky presentation summary, beginning with Pubky App!
👇
Pubky App - Let's Unlock the Web! 🧵
A Progressive Web App
Runs in your browser or installed locally.
Content publishing, social tagging, semantic social graph — it’s all here.
In addition to Pubky Core, we add our new Nexus Indexer to power the graph.
You Are The Key
Pubky App allows users to represent themselves as public keys. No email or phone number required.
Posts & Post Types
Posts aren’t just text. They are anything you might find in Google or other apps, except we can curate them together.
Notes, articles, images, files, videos, links, and more post types are coming.
The Taggable Web
Forget the black-box algorithms. You create the network through Social Tagging, a new concept where you tag posts and users as you see fit, putting the algorithm in users' hands.
Tagging Posts
This isn’t just “likes” and “shares.” Tagging is about how you see the web, how you want others to see it. Social curation, the way it should be.
Create any custom tag as a button that others can add onto.
Tagging Users
Want to elevate someone’s voice? Tag them.
Pubky builds a web of trust, one tag at a time. Trust matters, and with Pubky, trust is transparent and sortable.
You Are the Algorithm
You choose your experience. Tagging builds your lens into the web, the one made by you and the people you trust.
You (we!) are the algorithm now.
The Web As You See it
Customize and save any custom view of the Pubky web and its social graph.
Pubky fixes what's wrong with the web today.
Here’s how:
Poisoned Algorithms?
With Pubky, You Are the Algorithm. Social tagging and custom feeds give you control over what you see and how you see it.
Censorship?
With PKARR identities, you can’t be censored in the traditional sense. Banned from a server? Keep your data, contacts, followers — and just keep going.
Walled Gardens? Nope.
Pubky’s about portability. Your identity, your social graph, your content. It’s all yours. No lock-in. Big Tech can keep their gardens.
Semantic Social Graph
Pubky isn’t just another feed — it’s a decentralized Semantic Social Graph. A network enriched by meaning.
Relationships are contextual and weighted by trust. It’s personalization that’s built from the ground up for real people, by real people.
is almost ready!
We will begin a private, invite-only beta very soon, and a public beta in Q1 2025.Pubky.app
For those of you that missed my presentation in Lugano, here is a tweetstorm summary and introduction to our new Pubky ecosystem.
Let's begin! 👇
The Problem: A Captured Web
The web today is a mess of poisoned algorithms, censorship, and walled gardens.
🕸️ Poisoned Algorithms
Big Tech feeds you what serves them: corporate and state interests, toxic engagement, user manipulation... Algorithms are broken, and they’re breaking us.
Good morning, Bitcoin does not support or enforce any sort of "transactions" or "settlements."
These actions are misnamed within the protocol and Bitcoin literature.
1/10
A bitcoin "transaction" or "txn" or "tx" is actually a signed authorization to update the score of an originating account to redistribute its units into other accounts.
It is a proof, or a payment, not a transaction.
2/10
Nodes store these proofs in a temporary cache called the "mempool" until they're included in a new block by miners, validated by what is called "probabilistic finality."
Actual commerce and transacting happens outside of Bitcoin between peers in the physical world.
After weeks of arguing and consideration, I am now confident I can refute all arguments for a full-RBF regime, and that we should protect first-seen mempool policy from being subverted by keeping the existing environment intact.
1/5
My arguments include clear rationale that consider miners, incentive compatibility, maximization of fees per block, priority competition, utility for merchants, intelligent doublespend risk mitigation, protection of the user space, optimal culture of development of Bitcoin,
2/5
and optimizartion of Bitcoin adoption, utility, and activity.
What I do not know is the best path to communicating these learnings to Core, and best process for civilly halting the damage of the full-RBF regime.
3/5
I will be freezing my personal Bitcoin Core nodes at the current version (pre-taproot) permanently, barring any critical CVE fixes or such.
I will also stop using native segwit addresses and never use taproot (my nodes don't support it anyway).
Maybe this is inconsequential in the long run, but Bitcoin conservatism needs to start somewhere and I find the culture of Core to have soured and become reckless, and I simply do not want to trust my coin with their leadership any longer.
99% of users *should* be doing the same as me, simply because few of us are qualified to assess the code changes and complexity implications, making this a totally trusted process.
"Don't trust, verify" only works when you can actually verify.
A subset of Core devs are currently trying to attack Bitcoin by forcing a pet agenda to make all transactions RBF by default.
This attack includes bitcoin-dev mailing list lies and lobbying, code changes in Core node, and bribery attempts to miners.
1/5
Merchants rely on 0-conf txns as a way to meet consumer needs in commerce. RBF makes the mempool less reliable and spending Bitcoin more dangerous for consumers and businesses.
2/5
Bitcoin ATMs, Bitrefill, Muun, our company (Synonym/Blocktank) and any merchant can manage doublespend risks easily. We are working on tools to make 0conf acceptance easier/safer, but some devs would rather try and break a Bitcoin use case to protect their niche designs.
3/5