bitcoinerrorlog
John Carvalho

CEO at Synonym, creators of Pubky, Bitkit, and Blocktank.

Public Key

npub13ndpm2hm9hud4azsq5euhf5mv3d05r90wymwxsd7rdn29609hhvqp60svh

Profile Code

nprofile1qqsgeksa4tajm7x673gq2v7t56dkgkh6pjhhzdhrgxlpke4za8jmmkqpzdmhxue69uhkuethwvh82arcduhx7mn9qyghwumn8ghj7mn0wd68yat99e3k7mgm6ftx8

Publishing to

news.utxo.one

nostrue.com

Author Public Key

npub13ndpm2hm9hud4azsq5euhf5mv3d05r90wymwxsd7rdn29609hhvqp60svh

Show more details

Last Notes

2026-05-24 08:10:50 CEST

- reply

Everyone is too scared, i dunno. All of the arguments against Pubky are extremely juvenile and ignorant. I know how both systems work, and anyone objective would never claim Nostr is special or better. It's just loyalty, which is fine, but not a conversation about tech or solving problems at scale.

2026-05-24 08:08:03 CEST

- reply

Porting Nostr to Pubky results in ... Pubky.

2026-05-23 11:02:35 CEST

- reply

Odell is too scared

2026-05-23 09:11:46 CEST

- reply

You don't understand how biased you are for an unimpressive solution. We didn't skip building on Nostr out of ego. Nostr is not relevant to anyone but Bitcoin maximalists (because they are the only ones gullible enough to think Nostr is amazing).
We don't build on Nostr because when we did try to give our ideas to Nostr people they were totally ignored and insulted. Our designs are not new, and they predate Nostr. Believe it or not, our work inspired Nostr, not copied it.
Pubky is strictly better than Nostr. There is literally nothing better about Nostr aside from having some (decreasing) users.
Useful people aren't welcome to build on Nostr. You have to be some kind of fake-famous blessed-by-Jack-or-Odell asshole to work here. Nostr wants loyalty and tribal behavior, and we aren't in your tribe so we don't get any respect.
So, fuck you, and fuck everyone that thinks Nostr is a holy grail, or anything special at all. Because the design is bad, and the community wouldn't let you save it if you tried. Nostr is for Bitcoin Podcast listeners that want to feel like they understand tech, but are too lazy to actually learn.
You don't care about solving problems or helping people. You care about being "cool" with your fake internet friends. Have fun staying on nostr, I don't care because the world is actually a better place when losers like you stay away from other platforms. X is better without such people. Pubky too. Nostr's best feature is gathering moronic losers into one place.
I'm only here to save the people that ended up here by mistake. The rest of you can go back to your stupid life larping as Satoshi.
#nevent1q…5ke8

2026-05-22 11:00:42 CEST

Or, you could actually learn how Pubky works.
https://pubky.org
https://blossom.primal.net/b7de76d043d44b097ff7c7651331b5248977a6ec0cd9a36cb88865495601867c.png

2026-05-22 10:56:45 CEST

- reply

No, it just exposes your ignorance of the differences between open source software & networks compared to regulated products and services.
It also shows you are not genuine, as you would notice that every legitimate app product has a ToS, and ours is as boilerplate as possible for the services our active products contain.
If what you care about is the tech, why arent you asking questions about that?
Why are you fishing for plot holes like a jobless wanna-be podcaster?
I couldn't be less interested in your armchair lazy attempts to discredit our hard work.

2026-05-19 15:50:33 CEST

- reply

It is Pubky, not Nostr.
The things that people do with Nostr are a subset of what is possible with Pubky.

2026-05-19 11:28:10 CEST

mypubky.com
https://blossom.primal.net/f802abfd44e8ee76821f568dc53d9675ea87a8eccb6e96fc398ca13472ef8439.png

2026-05-18 11:30:22 CEST

- reply

Using it is the only solution for that problem :)

2026-04-30 10:30:12 CEST

- reply

Any terms that seem weird in our app ToS are there as boilerplate, we don't inject special weird things into our terms, we just ask our lawyers to make sure we are doing what is required.
You will find the same terms in other similar apps, and if you don't it is probably just amatuers.
If someone ever finds anything in our ToS we can remove, I am happy to check with legal about removing it.
We dont want anything to do with laws, regulations, or your personal shit, but we can't legally produce things without proper terms.

2026-04-15 15:23:12 CEST

test

2026-04-09 18:34:28 CEST

- reply

I graduated from "the guy the triggered Roger Ver" to "the guy that triggered 'sats' lovers"
See you in Prague!
#nevent1q…2z6v

2026-04-09 05:49:17 CEST

- reply

Thank you for reading, and for your thoughts on the topics!
Basically I think term carries misconceptions, and would be easier to reach consensus with people if rights were treated more like wishes or initiatives.

2026-04-06 21:16:16 CEST

- reply

look at my feed...

2026-04-06 21:05:51 CEST

- reply

my last post before this is a clear link

2026-04-06 20:39:19 CEST

https://x.com/BitcoinErrorLog/status/2041223606378635593

2026-04-06 19:57:36 CEST

- reply

90% of my interactions here feel like they are with 12-year-olds, so yeah, not fun for complex/conceptual systems design discussions.

2026-04-06 09:20:27 CEST

- reply

people know how to tip here me i think, there are zap buttons everywhere

2026-04-05 19:35:31 CEST

- reply

that's why i made the article 😉
i dont recall which show, maybe @nprofile…ly0z ?

2026-04-05 19:33:41 CEST

Hunger is Not Bread
https://pubky.app/post/gujx6qd8ksydh1makdphd3bxu351d9b8waqka8hfg6q7hnqkxexo/0034XEBK9V9Q0
https://blossom.primal.net/63fad407e09732a18404224c602d7ed63cc9341c1d5615fbefab654f4fe35131.png

2026-04-05 18:58:51 CEST

- reply

https://pubky.app/post/gujx6qd8ksydh1makdphd3bxu351d9b8waqka8hfg6q7hnqkxexo/0034XEBK9V9Q0

2026-04-04 09:52:37 CEST

- reply

This is correct, and it does create a new paradigm where people can know for sure what you declare as your data, but I think you guys were cross-talking about use cases.
Digital-rights-management (the ability to enforce ownership rights like deletion) is actually an oxymoron, impossible.

2026-04-04 09:42:01 CEST

- reply

If I made it 6 months ago you'd say I can't predict the future.
Read it or stfu thx

2026-04-03 15:50:11 CEST

You can't actually solve problems while following current norms.
Because acceptable norms provably allow current problems to exist.

2026-04-03 14:00:01 CEST

https://paperbitco.in/

2026-04-03 13:21:32 CEST

- reply

That is not a fact. It uses Mainline DHT to store personal DNS records that point to any location you want, hosted, or self-hosted. Indexers can support multiple homeservers.

2026-04-03 08:47:42 CEST

- reply

Not to mention, isn't Nostr funding just as centralized around Dorsey?

2026-04-03 05:58:55 CEST

- reply

Well, I certainly made it clear what i think about the tech in very specific ways. It cannot scale, it cannot provide real censorhip resistance or security, relay dependance is a naive design.

2026-04-03 05:56:23 CEST

- reply

Pubky (and Nostr) are not consensus enforced systems, if people dont like how we build they can fork and build. Everything we make is modular anyway.

2026-04-03 05:53:28 CEST

- reply

If you have an issue please share and we will fix it.
Even our marketing team of nondevs is building with the Pubky SDK and ai.

2026-04-02 23:37:26 CEST

- reply

Some people cant accept an idea until all their friends have already. It really is that simple.
Nostr people never criticize Pubky directly, it is always complaints about form, not function.

2026-04-01 10:14:34 CEST

Noise for Pubky
https://crates.io/crates/pubky-noise/0.1.0-rc1

2026-03-29 17:30:03 CEST

- reply

Huge loss, I'm sure.

2026-03-29 15:45:23 CEST

https://pubky.app/post/gujx6qd8ksydh1makdphd3bxu351d9b8waqka8hfg6q7hnqkxexo/0034WADK62XRG
https://image.nostr.build/b591face6fdad0a830d7a5395e8d16e97c2c30a7ad7354514a326ed2476125ba.jpg

2026-03-28 13:34:28 CET

Would you?
https://x.com/BitcoinErrorLog/status/2037870619874783701?s=20

2026-03-22 09:26:21 CET

https://howtofixtheweb.com/

2026-03-21 12:18:33 CET

https://howtofixtheweb.com/

2026-03-21 12:16:50 CET

- reply

vlad gives a platform to the most brain-damaging idiotic guests in the space, and for that we are thankful

2026-03-21 12:13:49 CET

- reply

https://blossom.primal.net/3d662d15ede2192f504bec18043f2c714d05726052a69c21f1f3f2ec1c34236e.gif

2026-03-16 08:30:15 CET

- reply

bro wtf are you even talking about i make open source software

2026-03-16 08:21:18 CET

- reply

i'm just curious whether you actually know anything at all

2026-03-16 08:16:30 CET

- reply

what does that even mean, are you capable of substantive text?

2026-03-12 07:58:26 CET

https://x.com/BitcoinErrorLog/status/2030921248750928239/

2026-03-11 14:17:50 CET

- reply

You’re confusing routing with enforcement.
Bitcoin isn’t a packet network, it’s a global arbitration system with finite capacity.
Layering only works while users can still enforce their claims on L1 within the required time window. When that becomes too expensive, the system shifts from trustless to trusted.
Your probabilistic outcomes assume proof of work is obtained already, but layers create new trust games on top of future blockspace, not PoW.
The security model degrades under congestion. Because it doesn't scale, by design. Layers force you to trust your cosigner and compromise your prior PoW assurances.
The base layer size still determines how many people can retain real sovereignty. Layers force you to trust your cosigner and compromise your prior PoW assurances.

2026-03-11 12:47:13 CET

- reply

i have a deadline to share my paper on this in May, til then my advice is, well, actually do the math

2026-03-11 11:42:09 CET

- reply

I cant speak for others, but no, I am arguing that onchain scale ultimately limits active users to the millions, and if you compress too many in a layer, you quickly get cascading issues interacting directly with onchain blockspace limits. 2-week windows become too expensive to enforce, channels become trusted, etc.
It's just admitting that Bitcoin has a size. You can increase blockspace, but you can't gain meaningful scale via layering to even 10 million active users in current conditions.
Will users tolerate regular blocksize increases so layers can slowly scale at pretty much the same proportion to onchain? Or will they tolerate their channels requiring regulation due to being trusted?
Note, I AM a Lightning provider since the beginning.

2026-03-10 18:39:36 CET

- reply

All layers introduce counterparty risk via shared msig constructions, and then use some form of onchain enforcement to mitigate betrayals.
That's why layers dont actually scale Bitcoin, because their assurances require onchain txns.

2026-03-10 11:50:51 CET

- reply

Layers are just unconfirmed transactions. They do not provide scale, they provide coordination of trust.
You're just arguing for bigger blocks in the end, which is fine, but also requires coordination or trust to pull off, and can only do so much.
What you're missing about our work is that being trust-compatible enables actual scale, and having a credible exit from that scale is all you need to commoditize central providers.
You're just reciting your script while remaining ignorant of the design.

2026-03-10 07:16:23 CET

- reply

Sorry, I don't have time to dismantle all of your preconceived personal limits and misconceptions about our work. Your posts are hot air. Just propose something specific instead of nihilizing everything.
Trust is society, you must design it into any network.

2026-03-09 20:23:00 CET

- reply

show me what you got

2026-03-09 20:20:53 CET

- reply

You're still conflating money, payments, settlement, and credit. This is why your replying with weird hot-air "fallacies" and metaphors.
Bitcoin does not need to scale (it could never) for every economic interaction on-chain. Layers, altcoins, stablecoins, etc, already concede that.
Bitcoin only needs to be censorship-resistant sovereign money with large-enough proof of work.
Lightning "scales" payments by reusing liquidity and delaying final settlement ... thanks to trusted unconfirmed transactions, not amazing protocol design.
Atomicity scales further by digitizing trust explicitly, so obligations can be routed, netted, and settled incidentally instead of pretending every meaningful economic act must be immediate final settlement. It's a mutual credit system. It coordinates trust where it exists, not as a last resort.
An occasional block increase does not solve for global retail, commerce, or finance. It just moves the bottleneck while increasing centralization pressure on validation and propagation.
The real fallacy is thinking Bitcoin failed because finance cannot be made fully trustless. Trust is not a bug in finance, nor for massively scalable payments. It is a requirement. Trust is the subject.
The gap is whether trust is explicit, contextual, and user-controlled, or, managed by institutions and platforms.
The next step is not pretending the base layer or LN should become Visa. The next step is building open payment and credit systems that preserves Bitcoin as the settlement anchor, to the degree its users require, not a crusade for Bitcoin domination.
#nevent1q…mhe9

2026-03-08 10:12:35 CET

Minimizing Violence Through Systems Design
https://pubky.app/post/gujx6qd8ksydh1makdphd3bxu351d9b8waqka8hfg6q7hnqkxexo/0034RZVYA7780
https://blossom.primal.net/f59d89bab86e0e8a6c16441af94623799a9963016200ba17594bfdb7061e4175.png

2026-03-08 07:31:03 CET

Good morning, you should be building on Pubky.

2026-03-07 07:53:23 CET

- reply

You have Bitcoin goggles on, so you deny yourself understanding.
"Bitcoin doesn't scale" is not a mantra, it is an objective fact that any rational engineer can observe about its design.
You can just use math; it isn't actually debatable. I will make anyone look like a fool for such beliefs if given a fair format.
Further, Bitcoiners have some retarded views on what things like money, payments, and settlements are, so they support dead-end research that appeals to their emotions and hopes.
You. Will. Never. Scale. Bitcoin. Trustlessly.
Thus you will always need to digitize trust explicitly.
It's your lack of creativity & experience that makes you think any of this is coping or naive.
I am offering a solution that maintains P2P sovereignty, not excuses.
#nevent1q…z2ek

2026-03-06 18:46:40 CET

- reply

I'll just build it and show you instead of try to explain it further. Have fun waiting for covenants or whatever it is you do.
Freedom can't compete without coordination and trust.

2026-03-05 19:55:01 CET

- reply

Do you actually know our design for our system, and specifically for how to employ P2P credit?

2026-02-28 15:29:46 CET

https://blossom.primal.net/bb113afe0d2fd561d5cabc89a88df06b3da24ffb412227e6f86bba0f542ecba1.png

2026-02-27 09:13:33 CET

Everyone, except you, is tracking everything you do on the web, trying to infer everything about you.
Shouldn't you be tracking too?
Shouldn't you know as much as the people marketing to you, as the governments propagandizing you?
Why don't you?

2026-02-26 11:58:48 CET

PKDNS provides the most decentralized identity and discovery system on the planet.
Key-based domain names that tell everyone where to find your data.
Use it.

2026-02-26 09:00:22 CET

- reply

You’re mixing up the bootstrap server with the actual architecture.
Yes, most users are on pubky.app right now. We’re early, so of course there’s a default host. That’s onboarding convenience, not a system dependency.
Your account isn’t “on pubky.app.”
Your identity lives via PKDNS in the millions of DHT nodes that do already exist. Your pubkey points to where your data is hosted, and that location is controlled by YOU.
So if you leave pubky.app, or Synonym's server, you don’t lose your identity, nor your continuity of threads, etc. You just point your key at a new homeserver (self-hosted, private, paid, all are supported). Same key, same social graph, new data location.
The DHT’s job is just like DNS. It answers “where do I find this user’s data?” It’s not meant to carry traffic or connect devices.
If Synonym disappeared tomorrow, users would lose a popular host, not their identities. They’d re-host, update their record, and carry on.
That’s we separate the parts:
- PKDNS
- homeservers
- indexers/apps
So decentralization isn’t “how many homeservers exist today,” it’s whether users are willing to self-host if no one else will host them.
The protocol itself, the entire system, is decentralized, but it supports centralization safely because PKDNS provides a credible exit path, unlike any other system.

2026-02-26 08:49:23 CET

https://x.com/jturner/status/2026456244723044522?s=20

2026-02-22 14:16:18 CET

- reply

only an ignorant subhuman would think so

2026-02-22 12:19:37 CET

- reply

https://primal.net/e/nevent1qqs0y32e8zcz0pa4nt6458nhneltww2vpp794x9fyxh3p8fgxf98r9ch4svwr

2026-02-22 12:18:59 CET

- reply

This was meant to quote this note, but Primal sucks so here: https://primal.net/e/nevent1qqspu9tps6dda9w7kxvyqcqqw7gekt90m0529a2edj7yqy2mnv8f0zssdujqz

2026-02-22 12:17:27 CET

FREE OPEN fucking SOURCE FREEDOM fucking SOFTWARE
You are paranoid about its heritage? Are you a fucking puritan or something?
Do you even know my heritage?!
Who the hell are YOU to doubt me in the first place? Who fucking cares which retarded hang-ups you have about your backwards tribal way of thinking?
Why is it that when I make you feel uncomfortable about your SOFTWARE you respond by talking about me?
Why is this place such a fucking cesspool? Why do you all tolerate this, and support this behavior?
You think being a fucking memetard is a win? No, it's being a fucking meme! A fucking oversimplified idea made into a joke. Forgettable.
Stop with the "pleb" shit and take some fucking responsibility.
Your memes are stupid. You are stupid. You make everyone that supports you more stupid.
Being stupid and insignificant is not cool, it is a fucking psyop.
Holy fuck, grow the fuck up and suffer some fucking reality.
YOU HAVE NO IDEA WHAT YOU ARE CAPABLE OF!

2026-02-22 10:13:20 CET

A list of products you are probably neglecting as a Bitcoiner, and as a proponent of freedom software in general.
https://blossom.primal.net/6f652f81cbc62cf919c6493ce6a92735362c4dab3f196f3fc10cee39b7f95c95.png

2026-02-22 08:52:27 CET

- reply

You figured out that ignoring me is the safe strategy, surely you can figure out that ignoring Kratter and knotzis is all you need to do. You give them power when you say their names.

2026-02-21 12:01:06 CET

Some people really are eerily consistent at being contra-indicators.

2026-02-19 21:57:09 CET

- reply

You’re still blending authority with attribution.
Bridge admins have no authority, agreed. They’re just reposting content. That’s precisely the problem with proxy identity. There is nothing binding the bridged account to the origin user beyond social assumption.
Pubky doesn’t grant bridges authority either. It removes the need for them to have any.
Authority comes from key control. Attribution comes from signatures. Discovery comes from resolving the user’s published endpoints.
If a bridge reposts ActivityPub content, you can verify:
• Did this originate from the user’s key?
• Does it resolve from their declared endpoints?
• Is it mirrored faithfully or modified?
If not, it’s just an unaffiliated repost, exactly as you described. The difference is it becomes trivially provable instead of socially ambiguous.
On your other questions:
DHT = Distributed Hash Table. Think of it as a decentralized key-value store. Instead of DNS mapping domains to IPs via registrars, pubky records map public keys to user-declared resource endpoints via the DHT.
And no, DNS is not limited to IP mapping. It’s a general record system. Pubky uses the same concept, just key-native and registrarless.
Compatibility with ActivityPub wouldn’t be about protocol replacement. It’s about identity resolution. ActivityPub actors could publish pubky (PKARR) records pointing to their canonical data, mirrors, or servers. Apps that resolve those records gain cryptographic attribution instead of trusting instance admins.

2026-02-19 17:47:26 CET

- reply

If you had a login bug I am happy to provide a free code, and happy to collect your bug report.

2026-02-19 12:36:27 CET

Ha! Google published BoomerTabs :)
https://chromewebstore.google.com/detail/boomertabs/hmgjoneiakpbapigllgmgcaickalcjef

2026-02-19 12:13:43 CET

- reply

You need to isolate the problems you’re describing. You’re mixing impersonation, data integrity, and discovery into one bridge issue.
Your pubky (a public-key-signed DNS record in Mainline DHT) tells anyone where to find the canonical endpoints for your data. Any app can resolve those endpoints and verify it is looking at the user-designated source, even if that source is a trusted third party.
Integrity is a separate layer. If you want verifiable data, you still need explicit mechanisms such as cryptree structures, versioning, snapshots, mirrors, etc. Discovery does not replace integrity, it enables it.
If the complaint is: I trusted a third-party proxy account and now they are censoring or exploiting it, this gives you a way to set the record straight. You can publish canonical endpoints and authentic data. It does not and cannot prevent bad actors from continuing to impersonate you. Protocols cannot stop attempts at impersonation, they can only make authentic identity cryptographically distinguishable.
If the complaint is: impersonators exist, there is no digital way to prevent someone from copying your public data. The enforceable boundary is signature verification and canonical resolution. If an app refuses to verify, that is an application design choice, not a protocol limitation.
If the complaint is: I want trustless bridging inside legacy apps, then those apps must adopt identity resolution and verification models like this, or accept the tradeoffs of custodial bridges.
Not your key, not your account.

2026-02-18 16:26:12 CET

Bitcoin is what happens when money stops asking who is in charge.

2026-02-18 15:53:47 CET

If you watch this you will find that some people think I said some interesting things and that I wear interesting clothing
https://rumble.com/v75u0om-why-using-bitcoin-matters-real-world-use-cases-plan-forum.html

2026-02-15 18:13:20 CET

Introducing BoomerTabs!
BoomerTabs is a Chrome extension for people who always have too many tabs open.
The goal was simple: make tab management faster and less annoying.
What it does best:
- Replaces tiny-labels with larger, readable tabs
- Supports multi-row layouts so you can actually see more
- Lets you drag, drop and organize tabs, including between rows
- Supports tab groups with color cues and inline collapse/expand
- Includes fast search so you can jump to the tab you need
- Handles zoom levels properly, so the UI doesn’t break at different scales
If your browser usually has dozens of tabs open, this makes a real difference!
https://github.com/BitcoinErrorLog/boomertabs
You have to install manually with the ZIP for now, but I did submit it to the Chrome Store for review!
(Yes, this is a Sunday vibe-coded project)
https://blossom.primal.net/6c2f29a7e59fda3869bc774b96a951f50f8e6aef073962fd7d7ac1eb93973cc0.png
https://blossom.primal.net/d7425c568b7f799ae563aa8572799fb22b039b13deffe484203ce24bbc2eb297.jpg

2026-02-14 16:32:57 CET

The fact the dropping my iPhone is unlikely to break the glass gives me hope for humanity.

2026-02-14 01:02:37 CET

- reply

Okay, but you will be on Pubky eventually, may as well start now.

2026-02-12 10:44:37 CET

When you choose bad role models, you choose a smaller life for yourself.

2026-02-12 10:43:12 CET

- reply

Ready when you are!
(well, give me a couple weeks, heading back to Portugal this weekend)

2026-02-12 10:42:00 CET

- reply

I think he is confusing you for how Odell won't talk to me due to conflicts of interest.
Either way, I am happy to talk about our work, or Bitcoin, with anyone!
Do you have your own show currently? Livestreams? I don't know what the current "scene" is.

2026-02-11 18:05:58 CET

https://x.com/i/broadcasts/1zqJVdjrWMlKB

2026-02-11 14:16:36 CET

- reply

Correct!

2026-02-11 13:09:53 CET

Join us for a public Pubky Dev Call -- TODAY!
We’ll walk through recent updates, roadmap updates, and hear directly from the community.
- Pubky overview
- Pubky SDK walkthrough
- Events demo
- Homeserver Dashboard demo
- Q1/Q2 Roadmap
- Q&A
Google Meet:
https://meet.google.com/qfp-dihh-gbi
X stream:
https://x.com/i/broadcasts/1zqJVdjrWMlKB
Starts in 5 hours from this post!
https://blossom.primal.net/053e05d70fa838332b5866c86a33dcf22acee0cda38a5773bbda2b7d619d2c0f.png

2026-02-10 14:56:18 CET

- reply

Everybody is somebody in Pubky!
Don't worry, you dont have to pretend to enjoy nostr anymore.
We believe in you!

2026-02-10 14:49:50 CET

- reply

you should cry harder on pubky instead

2026-02-10 14:18:15 CET

- reply

Most of what we have shipped is for public-only use cases.
However, we are wrapping up work on a pubky-noise library this month, and related tools for our keychain and wallet. This unlocks private messages and related features for Pubky.
After that set of features ships, we'll be working on more access-control related features, maybe versioned data, etc.

2026-02-10 14:14:13 CET

- reply

You can say anything you want about Nostr!
It's okay for people to appreciate Nostr; it's cool in its own way, and has its own history and community.
But if I'm gonna spend money on building something, it is, and always was, (since before nostr existed), something else: the atomic economy.
I'm a man on a mission, and I have no loyalties to inferior technologies!

2026-02-09 10:09:24 CET

- reply

Nope. Read it.

2026-02-08 16:39:43 CET

- reply

Can he assume you read the article he linked first? The post exists to answer your exact questions.

2026-02-07 17:52:32 CET

https://eventky.app/event/gabri5dk51q1c1kzi53hjpqw5yhmw1nqsryzsfx5kubd7jpm63jy/0034M8WQCPK20?instance=2026-02-11T18%3A00%3A37

2026-02-07 17:49:13 CET

- reply

🕺

2026-02-06 21:21:32 CET

- reply

https://github.com/pubky/pubky-backup is basic backups for now, and we have a Umbrel homeserver WIP here: https://github.com/francismars/homeserver-dashboard

2026-02-06 18:25:54 CET

Bitcoin 101
https://bitkit.to
https://x.com/bitkitwallet/status/2019814845751914750?s=20

2026-02-06 13:35:11 CET

https://www.youtube.com/watch?v=KnnHprUGKF0

2026-02-06 13:26:47 CET

- reply

Is uses a "semantic social graph" for tagging URLs and keys.

2026-02-05 16:39:54 CET

- reply

You can have as many servers as you want. Just set up mirrors and add those to your pkarr record.
Nostr is a subset of Pubky capabilities.

2026-02-05 15:59:21 CET

- reply

Okay, now tell me about Mainline DHT and Pubky's protocol and how it fits in and why.

2026-02-05 15:58:36 CET

- reply

what happens in nostr if someone can't find your data in their relays? and how do they know whether they have all the data?

2026-02-05 15:57:36 CET

- reply

You switch to another one or host it yourself.

2026-02-05 13:25:06 CET

- reply

...
do you have something useful to say? or maybe a genuine question?