John Carvalho Profile picture
Oct 31 18 tweets 7 min read Read on X
Here's Part 2 of my Pubky presentation summary, beginning with Pubky App!
👇 Image
Pubky App - Let's Unlock the Web! 🧵 Image
A Progressive Web App

Runs in your browser or installed locally.

Content publishing, social tagging, semantic social graph — it’s all here.Image
In addition to Pubky Core, we add our new Nexus Indexer to power the graph. Image
You Are The Key

Pubky App allows users to represent themselves as public keys. No email or phone number required.Image
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.Image
Image
Image
Image
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.Image
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.Image
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.Image
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.Image
The Web As You See it

Customize and save any custom view of the Pubky web and its social graph.Image
Image
Pubky fixes what's wrong with the web today.

Here’s how: Image
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.Image
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.Image
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.Image
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.Image
is almost ready!

We will begin a private, invite-only beta very soon, and a public beta in Q1 2025.Pubky.appImage
Contribute and learn more about Pubky Core:

github.com/pubky
docs.pubky.org
pubky.org Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with John Carvalho

John Carvalho Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @BitcoinErrorLog

Oct 31
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! 👇 Image
The Problem: A Captured Web

The web today is a mess of poisoned algorithms, censorship, and walled gardens.Image
🕸️ 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.Image
Read 25 tweets
Dec 6, 2022
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 Image
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.

3/10
Read 12 tweets
Nov 16, 2022
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
Read 5 tweets
Nov 8, 2022
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.

We can't.
Read 4 tweets
Nov 3, 2022
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
Read 5 tweets
Nov 2, 2022
The new Slashtags.to website has a lot of info about the Slashtags protocol, including this awesome Slashtags Playground,

The Playground shows both use-cases & UX examples to spark your creativity about what's possible with Slashtags!

1/7
Install the beta-testing version of Bitkit Wallet from bitkit.to to try each Playground demo!

Let's start with the Slashtags Profiles demo, which allows you to search any slashtag key and view the profile.

We included the Synonym team's profiles to try also!

2/7
The Slashtags Accounts demo shows you passwordless account creation & sign-in for websites, as well as the cool tap-to-login feature in Bitkit!

The website can pull your Profile automagically, and even knows if you are new or returning!

Try it at slashtags.to!

3/7
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(