VitorPamplona
Vitor Pamplona

Nostr's Chief Android Officer - Amethyst/Brainstorm

Public Key

npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

NIP-05 Address

Profile Code

nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzrthwden5te0dehhxtnvdakqz9thwden5te0wfjkccte9ehx7um5wghxuet5qyg8wumn8ghj7mn0wd68ytnhd9hx2qg0waehxw309ahx7um5wghx6mmdqyt8wumn8ghj7anfw3hhytnwdaehgu339e3k7mgynqayw

Publishing to

Author Public Key

npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

Show more details

Published at

2026-07-25T01:53:25+02:00

Kind type

0 Metadata

Event JSON

{ "id": "b48187a7aa20d1607f8767c46f8656ad01d18d66a91ebb33efda712860be91d5", "pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c", "created_at": 1784937205, "kind": 0, "tags": [ [ "alt", "User profile for VitorPamplona" ], [ "name", "VitorPamplona" ], [ "display_name", "Vitor Pamplona" ], [ "picture", "https://vitorpamplona.com/images/me_300.jpg" ], [ "banner", "https://pbs.twimg.com/profile_banners/15064756/1414451651/1080x360" ], [ "website", "https://vitorpamplona.com" ], [ "pronouns", "he/him" ], [ "about", "Nostr's Chief Android Officer - Amethyst/Brainstorm" ], [ "nip05", "[email protected]" ], [ "lud16", "[email protected]" ], [ "client", "Amethyst" ], [ "clink_offer", "noffer1qvqsyqjqx5crzcn9v43kxdp4xdnrvcmpxv6ngdphxg6ngcfhxyenzvfex4jkvctxxceryvf5vyenyd3svcuxxenrvc6kgde4xdnrjdfhxfjxxccprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcezf5k3" ] ], "content": "{\"about\":\"Nostr's Chief Android Officer - Amethyst/Brainstorm\",\"banner\":\"https://pbs.twimg.com/profile_banners/15064756/1414451651/1080x360\",\"display_name\":\"Vitor Pamplona\",\"lud16\":\"[email protected]\",\"name\":\"VitorPamplona\",\"nip05\":\"[email protected]\",\"picture\":\"https://vitorpamplona.com/images/me_300.jpg\",\"website\":\"https://vitorpamplona.com\",\"displayName\":\"Vitor Pamplona\",\"pronouns\":\"he/him\",\"clink_offer\":\"noffer1qvqsyqjqx5crzcn9v43kxdp4xdnrvcmpxv6ngdphxg6ngcfhxyenzvfex4jkvctxxceryvf5vyenyd3svcuxxenrvc6kgde4xdnrjdfhxfjxxccprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcezf5k3\"}", "sig": "6cb948cc0a66a1cade744b52d9c7684b0bce0b8c0028e80008ef34157b13f65fa1f3b00798a4be03b66c69861c6571d32126a04f4cb05ccf3d4be4bfb82b2147" }

Last Notes

2026-09-08 00:19:06 CEST

- reply

lol.

2026-09-08 00:12:53 CEST

- reply

Yet everyone is using it and feeding all relays with their data.

2026-09-08 00:06:34 CEST

- reply

You know the definition of our relays is to proliferate content, right? That's the whole point of it.
And yes. There are multiple service providers storing your nostr events forever.

2026-09-08 00:00:52 CEST

- reply

Don't lose my Bitcoin, @nprofile…uh0e

2026-09-08 00:00:29 CEST

- reply

How is that an invasion of privacy? You posted publicly anyone can store it.. in fact many do. There are storage services that only store deleted tweets and sell that information to the highest bidder. There is no privacy when you post things on the web.

2026-09-07 21:44:11 CEST

- reply

I have local as well. But it never finds what I want (not enough space locally) so I got no option but building NIP 50 relay.

2026-09-07 21:39:47 CEST

- reply

I got 6 posts from Fiatjaf
https://search-staging.brainstorm.world/?q=from%3Anpub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6+lightning+sucks

2026-09-07 19:55:46 CEST

- reply

How do you place said attestation in replaceable events that are mutable by design? Do we now have to deal with revocation of revocations through replaceable events by attackers?

2026-09-07 19:54:31 CEST

- reply

I read about 15 or so proposals on this. All of them suffer from the same issues. So, it's not that I have given up. We just run out of ideas.
Even the ideas that delegate identity to a separate protocol fail to address the same issues.
That's why I am investing so much in WoT. I don't think identity can be solved by anything else at this point.

2026-09-07 19:36:34 CEST

- reply

People are using all kinds for this, not just kind one. It's not about kind 1 at all. They use whatever kind is available in the app they use.
It's about ease of use and integrity of identity across all apps and all relays.

2026-09-07 19:34:12 CEST

- reply

This is different. All apps have the same profile picture. We can't have some apps with some profiles and other apps with other ones. You fuck with identity, you destroy the only thing that works all the time on Nostr.
If people start questioning if the npub I am talking to is still the same npub I was talking to yesterday, we will have major problems.
Nostr somewhat works because the identity is immutable. Once that mutates, a whole slew of issues arise. And we don't have the consensus layer to follow just one path, together.
If identity breaks like DMs are broken, nostr dies.

2026-09-07 19:08:33 CEST

- reply

You now understand why Nostr will never have key rotation.

2026-09-07 19:05:21 CEST

- reply

Everything on Nostr is the client chicken and egg problem. It's quite literally where most of my time as a dev goes. Trying to make shit work with other clients.

2026-09-07 18:58:14 CEST

- reply

Then implement a solution and let's see how far it gets without getting called "it doesn't work" because Primal still displays the old account I rotated of that Amethyst users were automatically migrated to a new account because the attacker got my nsec but I don't even use key rotation apps.

2026-09-07 18:51:06 CEST

- reply

Yes.

2026-09-07 18:50:37 CEST

- reply

Unless clients don't implement revocations... then nothing works. They don't even implement deletions right now. That's my point. The system breaks because it requires clients to implement it. It's optional. And identify management shouldnt be optional. It either exists and is implemented by literally every one, every little nostr app, or it doesn't exist (which is what we have today).

2026-09-07 18:47:43 CEST

- reply

But then it is the same issue that Marmot has. If a user has 5 clients, why is the sender choosing which app the receiver has to reply on? Marmot solves it by creating a group chat of all sender and all receiver devices. Every new device needs to be added to all other device conversations. It is a lot of work.

2026-09-07 18:34:56 CEST

- reply

Yep, a 2FA for every like, encryption, decryption, visit to a relay, every notification, some picture downloads etc.

2026-09-07 18:29:03 CEST

- reply

Its just formalizing the wot verification that already happens on a single kind 1.
I don't disagree with you that it works in the same way, but you have to see that it is way more complicated to implement for the exact same result.
OTS alone is not even coded by 99% of nostr apps.

2026-09-07 18:26:16 CEST

- reply

Why would you revoke if you can just delete the event?

2026-09-07 18:23:39 CEST

- reply

Yes, amber is being hit with all that all the time. The performance difference between keeping the key on Amethyst and putting on Amber is negligible. That's why we recommend Amber so much.

2026-09-07 18:21:11 CEST

- reply

Make the transition more legit can also be used by attackers to make their attack more legit. That's where all crypto-first ideas die.
I think it will always be out of band communications. At least I have not seen a single idea that doesn't require active web of trust verifying things around it... Which is the same as the kind 1 post.

2026-09-07 18:16:54 CEST

- reply

If I send a DM to the master key do all usable keys decrypt it?

2026-09-07 18:13:59 CEST

- reply

Most relays right now require auth. So to download them, every app is signing authenticating with that relay.
But even if that's done, every description of each individual message in your chats would also require a code. Amethyst loads 1000 DMs on start to build your lastest chats. Those would be 2000 codes (2 decryptions) that you would have to insert from the 2FA.

2026-09-07 18:09:20 CEST

- reply

I didn't say it was solved. It's just what people do and solve their rotation needs right now. You can't build anything that is harder than that for the user. Otherwise, they will just go back to that simple thing.

2026-09-07 18:03:32 CEST

- reply

Correct. That's how easy we have it today.

2026-09-07 18:02:51 CEST

- reply

But they are not 2FA apps. Apps require access to them to do everything on any Nostr app.
Imagine having a 2FA code for every follow your app is trying to download posts from. It would take forever.

2026-09-07 18:00:36 CEST

- reply

That's all I need as a user.

2026-09-07 18:00:08 CEST

- reply

Good thing is that you will always have something to complain. Just pick two apps and boom... New anger-triggering content for the day. Endless material.

2026-09-07 17:55:22 CEST

- reply

Nobody will care until devs release apps that prove their thing works, that is actually secure and not just more technical bureocracy to reach the same rotation standards we have today.

2026-09-07 17:52:41 CEST

- reply

Relays largely don't need auth to know who you are. You need a different IP per REQ if you want to improve that.

2026-09-07 17:47:03 CEST

- reply

It's not our choice either. I was here before outbox was even a thing. Users want it. They use tools that have it. If you want to talk to them, you have no choice but use a tool that speaks their language.

2026-09-07 17:46:04 CEST

- reply

You can keep insisting that every tool needs to work with every other tool as much as you want. It will never be the case. Nostr or not.

2026-09-07 17:44:56 CEST

- reply

The proof of authorship is irrelevant since Twitter is a trusted platform. There is no way to prove anything. You have to trust the company is not fucking around with people's posts.

2026-09-07 17:42:37 CEST

- reply

That would be ideal, but nobody is doing that. + If enough people follow and trust the bridge account, who cares if it is the user posting or not. They want to see that npub's posts.

2026-09-07 17:36:33 CEST

- reply

I am not handwaving them. I am just saying that there is no way around it since EVERYONE is using outbox relay lists. You can choose to miss it and thats you call, but don't pretend that it is a solution. There is no way to use nostr today without outbox. It's literally everywhere.

2026-09-07 17:32:32 CEST

- reply

It's actually quite a feat to implement it correctly. Remember that even StrFry didn't have deletions properly implemented until one year ago..
Managing all the thumbstones effectively is not easy.

2026-09-07 17:21:45 CEST

- reply

What are you talking about? Nip09 is not implemented by most clients. It's only relay implementations that are saving everybody by deleting records. Clients generally never delete records, it keeps showing until the user reinstalls the app.

2026-09-07 17:16:53 CEST

- reply

It's fine to try something new, but nostr truly works with outbox. Every user that is active today has an outbox relay and his/her client is only posting there, replies to that user only go to the inbox relay list of that user.
Literally every active account that is not a bot or a disposable npub has them. And everything reacts to that record.

2026-09-07 17:08:29 CEST

- reply

But he wants to use an iOS signer with Android apps.. how many people you know have an iPhone and an Android phone in their pocket to make this usecase worth implementing?
It's like saying that I cannot use my flathead screwdriver in my hex screws. It's idiotic.
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/bf850174a157fa6544408caca20b7f63e0a2393ffc80dfd68cd4c9e2021636fa.jpg

2026-09-07 17:02:13 CEST

- reply

I tried those systems. They don't work. Half of the information on nostr doesn't even load on them. And then 6 months later those servers disappear and all users get rug pulled. Even the paid services have left users hanging.

2026-09-07 16:59:55 CEST

- reply

Correct. All proposals created more problems than solutions. All of them. Including mine. The lack of key rotation is not because we didn't try.

2026-09-07 16:53:26 CEST

- reply

? Why am I moving goalposts? I never said that only one signer should exist. In fact, it never made sense. Since the early days we have browser extensions for web, remote signers for services, Android signers for Android and Bluetooth signers for secure environments. Signers were never designed to be one size fits all solution.

2026-09-07 16:32:53 CEST

- reply

You might need to study the legal notion of implied license. This has been tested multiple times in the courts already.
Property vs. Copyright: Legally, the email content is not considered "property" in the traditional sense; rather, it is a literary work protected by copyright law upon creation. While you are the author and hold the copyright, the recipient receives a copy and typically gains an implied license to use, store, or share that content unless a prior agreement (like an NDA) restricts this.

2026-09-07 16:26:14 CEST

- reply

The purpose is not to have one signer for everything. That will never work. The goal is to separate the key from the apps by using the signer that can work with every app.

2026-09-07 16:24:17 CEST

- reply

Or just use the appropriate signer for each platform.

2026-09-07 16:15:17 CEST

The slop I grew up with.
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/868ef5c4b09e6999cc89c49b77ee98fc707aa26ea37220b58cadda629cce9203.mp4

2026-09-07 15:58:26 CEST

- reply

Most apps just centralize everything in their own relays. That's how they make nostr work.
Not us.
You can add proxy relays in the relay list, that will disable outbox for the feed. But usually people regret doing that because they miss a lot of posts.

2026-09-07 15:53:19 CEST

- reply

Lol.. failure is having to use remote signers because iOS doesn't allow devs to write any more efficient ways of having a signer there.
Don't put an idiotic iOS limitation on us.

2026-09-07 15:50:39 CEST

- reply

It's not a fail. It's an impossibility. We can't send a network request for every auth, every decryption, every draft save the app does.
Amethyst more likely will NEVER work with remote signers over http/websockets. It's just too expensive. Data plans will go bust just on the back and forth.

2026-09-07 15:47:52 CEST

- reply

The way Nostr works is that apps MUST connect with ALL relays declared by your follow's outbox lists. Otherwise, you will be missing their posts. That's by design of Nostr.
You can block relays you don't like, though. But we will never centralize the app in just a few relays.

2026-09-07 15:45:49 CEST

- reply

Even if we supported, just the 400 relay AUTH requests we do to load your feed on average, would completely overflow your Clave. We tried.

2026-09-07 15:43:31 CEST

- reply

Oh you think we are the only ones creating a copy of everybody's tweet? That's cute.

2026-09-07 15:37:55 CEST

Any bots moving ALL of Twitter into Nostr with a separate key per profile? I need to index it.

2026-09-07 13:55:05 CEST

- reply

Yep, but they claimed to be decentralized on their website and several publications repeatedly.
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/75020f9661a80dc609fb70e5ed5e44ed011e115214abb09b72da2daaec1f949e.png

2026-09-07 04:59:38 CEST

Me, following the Liquid drama at dinner
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/667273b53ce49260727bb83719170c477d8bb2e1c68f8bec8a12451ec47326ef.mp4

2026-09-06 22:55:03 CEST

They paused their "decentralized" chain.
#nevent1q…v8lw

2026-09-06 22:51:12 CEST

- reply

Do you have property insurance on it?

2026-09-06 22:05:00 CEST

Dev takes a project that had some bugs, forks it because "it wasn't working" and delivers a far worse build after investing weeks and lots of money on tokens for it.
Gotta love 2026.
They can't donate to devs, but $200/mo to Anthropic -> Google in a rewrite that nobody will ever use is a no brainer.

2026-09-05 22:28:19 CEST

lol, yes. Mine is all yelling, BTW.
#nevent1q…0ltt

2026-09-05 18:51:56 CEST

Is the next generation going to be talking like LLMs do?

2026-09-05 17:52:37 CEST

- reply

Production is on http://brainstorm.world
It's quite basic with just profile search, but more is coming.

2026-09-05 16:54:34 CEST

The beautiful thing about doing a Web of Trust Search on Nostr is that we already have the entire Wikipedia indexed (thanks to GitCitadel), but your friends' posts will always come first, even if you misspell your search.
https://image.nostr.build/e558c06599a0c5d898e213c6bc063b2fe6eface9d2d53e11e949c70490871f85.png

2026-09-05 15:54:57 CEST

- reply

You choose your own algorithm. We just rank them and present in the search. You can define trust in any way you want.

2026-09-05 15:51:44 CEST

- reply

Web of trust search is very different than regular search

2026-09-05 15:44:34 CEST

This is going to be so awesome.
https://image.nostr.build/fc28f76336f0ebea2559f17805613a8438ee26b66bc87c60bec126ee7dccb8e8.png

2026-09-05 15:36:22 CEST

- reply

Try it out on a desktop:
https://search-staging.brainstorm.world
Same url is the relay. You have to auth with your user to see posts in your web of trust.

2026-09-05 04:21:48 CEST

- reply

Yeah, but I absolutely despise slack interfaces.
Plus, it's so hard to control multiple work streams in parallel over there.

2026-09-04 23:16:33 CEST

Next on DeFi: "Token Farming" from AI plans.
#nevent1q…pqp6

2026-09-04 22:31:19 CEST

Has anybody built a tool that allows you to share your AI plan with anyone in the web?
Like a marketplace that I can just "provide compute" (aka access to my Claude Max) to others?

2026-09-04 03:02:00 CEST

Research right now is more based on creativity than ever. If an AI can do it, it's not researchy enough.

2026-09-04 01:56:30 CEST

- reply

Cool. The server is processing, let me wait to finish and then I can connect the production brainstorm to our staging search relay and will send you a link

2026-09-04 01:50:30 CEST

- reply

All your users can select their sources of trust independently. Your app doesn't need to do anything special besides authenticating with our nip 50 relay and making sure users have their outbox relay lists set correctly so we can find and index their events.

2026-09-04 01:42:49 CEST

- reply

You can search without any nip 85, but then any search relay would work. You don't need us for that. We specialize in web of trust. The point of the relay is to have a filter by trust. Otherwise it would just be a regular nip 50 search relay.

2026-09-04 01:26:32 CEST

- reply

Create an account on brainstorm.world first so you have a NIP85 provider and I can send you the urls for the staging relay we are working on. It is still early, but it already works.

2026-09-03 23:44:32 CEST

- reply

Then you can just find a provider that considers other things like the people you reply to.. it's up to you.

2026-09-03 22:58:58 CEST

- reply

Probably, but you can choose a trust provider with less if you want

2026-09-03 22:48:27 CEST

- reply

Follows of follows of follows.. 12 times up

2026-09-03 22:36:02 CEST

- reply

You can just mark never auth in the relay permission screen (we had a bug in that in the last version, but the upcoming one should allow this)

2026-09-03 22:33:53 CEST

Are we building the best WoT Search relay out there? Probably.
A relay that has everything: spam, scams, slop... all of it. But REQs and Search only return results from each user's wider network (follows-of-follows, 12 hops deep, minus mutes and reports). So, if a scammer or bot network uses the relay, they'll get the scam network. If a real human uses it, they'll get the network around them. Everyone stays happy.
And since it uses NIP-85 trust providers, you can choose any algorithm to score your network by any provider. Just subscribe to one and it will work automatically.
It's your WoT, not the relay operator's WoT.
It fixes Nostr without centralizing anywhere.

2026-09-03 14:20:36 CEST

GM https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/fd34f0e4e320725ddb589596a64a023c8d9367ed2bad20ab39836832fbbf2af7.jpg

2026-09-02 19:50:55 CEST

- reply

Should I generate a different nsite for the html page of each day?

2026-09-02 17:05:36 CEST

- reply

Checking.. did it ask you to send a report after you start it again?

2026-09-02 16:09:09 CEST

Turns out many people treat their chat apps as long-term backups for their personal stuff. Where did you save that contract? "It's here on WhatsApp"

2026-09-02 13:34:31 CEST

- reply

https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/98afd908d4805dfdcea1b37c1e02e9bbb798a36d468fe79c3e6796185be5cd43.jpg

2026-09-02 13:30:38 CEST

GM
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/dc3f71d2c9b9aef25eed939876a53cf61f7f00fd50a42123addf43135c8bce81.jpg

2026-09-01 20:51:32 CEST

- reply

Hum.. I can try it later.. maybe it's the report download that is not considering proxy relays and hits all the outbox relays of your follows to download their reports for every user in the screen.

2026-09-01 19:34:39 CEST

- reply

It will still connect to other stuff, like your community relays, location relays, chat relays, buzz/Concord relays, etc etc etc.
The proxy is only used to assemble the main feed from one relay.
It will also connect to the relays users on the screen use if the proxy relays fail to deliver any event we want from them, like profile, their outbox settings, etc.

2026-09-01 16:51:39 CEST

This is me, when I am required to go to LinkedIn to find a colleague.
#nevent1q…zmcy

2026-09-01 16:41:04 CEST

Interface design is so hard that we’re literally building agents just to avoid dealing with your ad-filled, rage-inducing horseshit of a UI

2026-09-01 08:58:05 CEST

- reply

Seems normal compared to the zap store...

2026-08-31 22:52:33 CEST

- reply

lol. Are you new here? 😅

2026-08-31 22:49:30 CEST

- reply

Well, it's very easy to make a client if you just centralized all the info in one relay. The hard part is resolving the amount of relays out there on the client, without any intermediary servers.

2026-08-31 14:05:07 CEST

Every dev has a "protocol" these days.
A protocol of 1 is not a protocol.
GM.

2026-08-31 00:59:55 CEST

- reply

Bots can pay more than us :)

2026-08-30 20:18:59 CEST

- reply

CeNSorShIP!

2026-08-30 19:46:47 CEST

- reply

Regular Claude should be able to do it too. But yes. You need an AI account of some sort

2026-08-30 19:36:28 CEST

- reply

First create and activate your brainstorm.world account, wait for everything to sync up and your posts to load (a few hours) then use the skill at https://github.com/NosFabrica/the-nostr-observer to ask for your observer page for today.

2026-08-30 19:22:06 CEST

This is how I learned about the reply mess 😂 https://image.nostr.build/b03bb353cb85ee218e214635707e23e9f5b88137f5d5ab780602a528b8d830a6.png

2026-08-30 14:43:22 CEST

GM https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.blossom.band/b7f8d03c4507b1e64654af2c626b3b82c7d473c98f7802c273a5f6913b94446f.jpg