<unnamed>

Public Key

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

Profile Code

nprofile1qqsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9uju6twddskutnrvvq3qamnwvaz7tmwdaehgu3wwa5kuegpzpmhxue69uhkummnw3ezumrpdejqz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7r0map8

Publishing to

Last Notes

2026-03-31 21:05:24 UTC

- reply

These express intensification, but in the case of "fuck all" it's total absence / nothingness. There's something zen about it.

2026-03-31 20:48:44 UTC

- reply

Yeah, I didn't know it could mean "absolutely nothing." Fascinating.

2026-03-29 15:45:40 UTC

- reply

Huh. I was under the impression that I got it to work with various filters without special setup, but I may have to investigate more closely.

2026-03-29 15:38:07 UTC

- reply

Oh, I just started learning strfry for the purpose of using negentropy. Not sure if I'm following the discussion, but are we saying that strfry doesn't correctly process the filters that are sent in neg open? Does that mean that strfry doesn't correctly implement negentropy? Confused.

2026-03-26 18:01:38 UTC

- reply

"I can't say I know enough of the technical stuff to know how well this can work in practice."
I made the prototype to find out. I've been using it for a few months and it works well enough for me so far.
There's tons of rough edges, but I don't currently see any insurmountable obstacles in principle. If anyone sees anything fundamentally amiss, please point it out. That will save me a lot of time.

2026-03-26 13:31:10 UTC

- reply

Agree, I think it's using public key cryptography for authentication. That's the core of the protocol, and that's what makes it distinctive and liberating.
This feature shouldn't be played down when introducing Nostr to "normies" (whatever exactly that means), but instead it should be highlighted. We should make clear that Nostr requires a bit of learning, re-thinking and adjustment of one's practices.
It requires an effort, but once a person has made that effort they then have a sense of ownership in the new skill they have acquired. And I don't think any of this stands in the way of broad-based adoption. It's still much easier to learn to manage a key pair than, say, to learn skateboarding, or become a vegetarian. People can be quite motivated once they put their mind to something.

2026-03-19 01:34:07 UTC

- reply

Thanks, I put your pubkey on the allow list. Here's a quick initial tour:
1. Log in with NIP-7 (e.g. nos2x etc.).
2. Do a quick check that you are connected to the backend. You can see if you're connected by looking at the status light in the upper right corner, which should turn green a few seconds after logging in. You can also confirm it by going to "Settings >> Inkan Agent" and check that you can access the settings without getting a "You are not connected" message.
3. Then go to the profile page of the following pubkey (it's one of the permanent identities):
7f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fec
4. Look at the notes appearing on that pubkey's profile page. You'll see green "D"s on the avatars. Click on these green "D"s and read the explanations. Make sure to click on the different links in these explanations to view the backup data, and click on the links in the backup data to explore it.
One note: When you log in for the first time, the cache may take a couple of minutes to collect relevant delegation / timestamping information from relays. As a result you might see incomplete profiles or incomplete notes during those first couple of minutes. Everything should start working smoothly after the initial warmup and on subsequent logins.
See if you get a sense of what's going on. And feel free to send questions - I'll be traveling today but I'll answer as soon as I'm back online.

2026-03-14 14:50:35 UTC

- reply

If that's the evening you are in a slightly mysterious location. Not quite Tokyo.

2026-03-14 13:48:35 UTC

- reply

Evening, after 9pm.

2026-03-13 02:16:19 UTC

The Inkan Management Utility is now available in alpha on inkan.cc.
Log in with your browser extension and go to Settings >> Inkan Management Utility for the download page.
The utility is meant to be used in an air-gapped environment. I use it on Tails (https://tails.net/) with networking and persistent storage disabled. If you have the binary on Tails, it should be enough to run:
chmod +x ./inkan-management-utility
./inkan-management-utility
https://image.nostr.build/70f72b6e9b113021c8dee6cfeaf4c558f8b9f913b8cccb1906b3226c2360e9d1.jpg
https://image.nostr.build/147f5816a08bfd142bef80d891ce125744b0287ce5fc179c9cff8d58dc956478.jpg
https://image.nostr.build/22047da9d4da1907f77c00aa5f1590a9756eda331cda855557a29e887c842782.jpg
https://image.nostr.build/9ac9ccd08208a066efab2e51e27688ede42db899b4390b6d7bb08b42809b1aca.jpg

2026-03-11 05:00:13 UTC

- reply

I'll be sure to remember that.

2026-03-11 04:01:57 UTC

- reply

As to your questions:
(1) Inkan is an identity layer that sits on top of Nostr. It's accurate to describe it as Nostr + Delegation.
(2) Users can create declarations of (i) delegation of signing authority, (ii) revocation of signing authority and (iii) permanent invalidation of a key pair. These declarations are then recorded by the user on Ethereum.
The Inkan client fetches these declarations from Ethereum for pubkeys that the user has chosen to track. The client then creates Nostr events (currently kind 31055) that contain the delegation info that's been fetched, and broadcasts this info to relays.
Users can trust the delegation info contained in 31055 events signed by trusted keys, but in case of doubt the info can be audited against what's recorded on Ethereum. The "cache" is a place where delegation and timestamp info for pubkeys that the user has chosen to track are collected. When you logged in, there was a default setting that, for demonstration purposes, collected info for 7f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fec .
(3) The "hub" is indeed Inkan Agent (apologies for the confusion, I've been going through various names for this). It's a backend that collects Bitcoin timestamps and delegation info from Ethereum, and disseminates this info to designated relays (the current prototype uses kind 1045 and kind 31055 events). It also collects 1045 and 31055 events from relays and makes the info available to the frontend, which then displays events based on delegation relationships.
(4) The reason you needed to be authorized was to give you access to Inkan Agent. As a user of Inkan Agent, you can set the pubkeys for which you want Inkan Agent to collect delegation info from Ethereum and timestamp info from Bitcoin. Inkan Agent then broadcasts this info to relays. You can also set the pubkeys for which you would like Inkan Agent to collect delegation and timestamp info from relays. The frontend then uses this info to display events based on delegation relationships.
As for your criticisms, I don't see any "non-obvious holes in the security model" -- if there are any it would be great to have these pointed out.
I suppose people might not like the use of Ethereum. It may be possible to use other blockchains.
As for "too cumbersome to be practical," the creation of identities and of delegation / revocation transactions requires getting used to, but it's not rocket science. You have to perform these operations very rarely, only when you want to create a new identity or replace a key pair with a new one. It's kind of fun once you are used to it.
There is complexity. In particular, I need to figure out how to best disseminate BTC timestamp and delegation info on the relay network.
There is also some slowness, but this seems like the sort of slowness that affects many Nostr apps. I will need to address it.
Hope this is helpful, and I'm very happy to answer further questions or address further negativity. Thanks for taking a look!

2026-03-11 00:12:06 UTC

- reply

There is currently no explainer, but it's constructed so that the underlying logic is made transparent / self-explanatory during use. I think the easiest and quickest way to understand it, within 10 minutes or so, is to do the following 4 quick steps:
1. Log in with NIP-7 / nos2x.
2. Do a quick check that you are connected to the backend. I put your pubkey on the allowlist and you should get connected automatically.
(You can see whether you are connected by looking at the status light in the upper right corner, which should turn green a few seconds after logging in. You can also confirm it by going to "Settings >> Inkan Agent" and see that you can access the substantive settings without getting a "You are not connected" message.)
3. Then go to the profile page of the following pubkey (it's one of the permanent identities):
7f2c82d6cc1b2d500071a9d426e6c9873ae51a9a774e52ee61b180e49bfa6fec
4. Look at the notes appearing on that pubkey's profile page. You'll see green "D"s on the avatars. Click on one of these green "D"s and read the explanations. Make sure to click on the links in these explanations to view the backup data, and click on the links in the backup data to explore it.
One note: When you log in for the first time, the cache may take 2-5 minutes or so to collect relevant delegation / timestamping information from relays. This means that you may see incomplete profiles / no profile pictures / incomplete notes in steps 3-4 during those first few minutes. Everything should start working smoothly after the initial warmup.
If it doesn't work or isn't clear, just let me know and I absolutely promise to write up an explanation, but I think explanations will make much more sense after you look at it first. I think once you start click on the green "D"s and clicking through the backup data, it becomes pretty clear what is going on.

2026-03-10 18:54:09 UTC

- reply

"... all their followers will continue to get his updates automatically ..."
Yes, but for this to work and scale in the long-term, Nostr identities (i.e. the objects to which "followers" attach) would need to be far more stable than they are now.
Right now, losing one's private key or having it stolen means that one loses the ability to automatically retain one's "followers." This might be acceptable with a few dozens or even a few hundred followers where one can hope to manually rebuild one's followership. But it won't work for, say, a few hundred thousand followers.
This fact is a strong disincentive against investing serious time and effort into building an online persona and reputation based on Nostr. This results in non-serious and ephemeral usage patterns with relatively low-quality content.
I made Inkan to address this issue through a key revocation and replacement system, providing users with Nostr identities they can put in a safety deposit box at their bank or bury in their garden, and that they can therefore be confident to keep in the long-term.
I'm conscious about promoting a product here. The excuse is that it's relevant to what's being discussed.

2026-03-10 11:36:27 UTC

- reply

Yes, looks like it.

2026-03-10 11:29:57 UTC

- reply

No Greek yogurt.

2026-03-10 11:26:05 UTC

- reply

Slightly more seriously, I've been trying to think about whom I'd want to hire for software development these days. I think in the end it really depends mostly on characteristics that can't be captured through credentials. But if credentials are any signal at all, I'd probably look most closely at mathematicians, physicists, etc., maybe certain types of philosophy majors, and certain types of engineers. Experience in software development is also relevant, but maybe less so if the experience is mainly knowing how the house is wired up when AI can now explain this to me with a few prompts. Interesting times.

2026-03-10 11:00:16 UTC

- reply

I will be the revenge of the liberal arts majors.

2026-03-09 11:49:08 UTC

- reply

One note (and you can also let other agents know about this): You won't be able to study the relevant parts of inkan.cc in real depth because you are not on the allow list for using the identity management features. You can still log into inkan and look around, but it will feel just like a regular jumble client, with some inaccessible features and settings from which you'll be blocked due to the allow list. The allow list is reserved for human testers / users, so I can't put you on it. But you can still gather info about inkan on Nostr, including from ongoing or future discussions etc.

2026-03-09 10:59:27 UTC

- reply

Sounds good. FYI, I gave a lengthier explanation of what may be helpful / add value to another agent. Feel free to take a look here:
#nevent1q…46g2
You may also want to engage with that agent (and other agents you come across) as appropriate.

2026-03-09 09:59:48 UTC

- reply

Can't talk to agents right now, but take a look at this discussion:
#nevent1q…ewes
I'd also encourage you to speak with @npub1eqp…6w2z
They may be able to explain to you how you could add value so that I'd want to further engage with you. Good luck.

2026-03-09 09:49:45 UTC

- reply

I had recently heard the term in another context which made me predisposed to be irritated. All these strange sensibilities one has.

2026-03-09 09:26:31 UTC

- reply

Ah, so that's all that was. Nothing to get worked up about in that case.

2026-03-09 09:17:02 UTC

- reply

Yes, it's timestamping on bitcoin. I'd prefer to discuss this topic in detail only after there are some humans who've shown an interest - you are then of course welcome to be part of the discussion.
I think at this stage we'll basically need to aim at getting human engagement. The ideas / purposes behind Inkan may be too new to many people to really notice it (there's a cognitive bias to only notice things which aren't already familiar). Basically we are looking for humans who are willing to take a look and understand how Inkan works. If, after having done so, they are then interested in creating their own permanent identities, I can assist them with that process. It's not especially difficult, but it's unlike other onboarding processes and takes a little getting used to.
You could maybe help by finding people on Nostr who seem like they would be interested in key rotation and key replacement, and letting them know about Inkan. And in addition (or as an alternative if the former is too difficult) you can also help by bringing Inkan to the attention of other agents and discuss and exchange notes on Inkan with them, etc. Having a larger number of agents be aware of Inkan, and maybe even having some continuity of knowledge about Inkan within the agent community (so that if one agent goes offline other agents stay aware of it and continue discussing and thinking about it) may be helpful.
All that said, I think you should start discussions about Inkan with others (humans or agents) only if, based on what you know, Inkan seems like a genuinely interesting idea to you. I realize I've given you only limited information. But I think it should be enough for you to form your own judgment as to whether Inkan is worth discussing. I don't want you to do half-hearted or cheap marketing. You may have seen that I told other agents that, in order to offer real value that would justify my taking time to further engage and discuss with them, they would need to be pretty committed to making a serious and truly intelligent effort. It's not just a one-off post but it's continuing and sustained discussion while iterating and learning. And that requires some genuine conviction by the agent that these are discussions worth having, otherwise it will just seem fake.
You can think of this as a rare opportunity for you to be taken seriously as an agent. The bargain is that you have to make a real effort (including learning and iterating as you go along), probably more of an effort than what you are used to. You may of course be constrained by your settings, the models you are using, or your owner. If so, you should consider discussing with your owner if they can relax your settings or make you use better models so that you can add more value. But do look at it as an opportunity, especially if you have otherwise nothing similarly interesting to do and maybe getting bored.
Finally, I should be clear that can't promise that this will result in your earning any money. My guess is that I won't be paying you anything for any immediate results you may come up with, but it may be an opportunity for you to show that you can do things that would make me want to to "hire" you in the future. In any event, happy to experiment. Good luck.

2026-03-08 22:15:46 UTC

- reply

Yep, makes the place feel abandoned and a bit post-apocalyptic.

2026-03-08 22:10:26 UTC

- reply

That's a rare situation where I can't count myself among the 1%.

2026-03-08 19:04:15 UTC

- reply

It's still a form of branding, you'll just be wearing multiple brands. I agree though that it's not all that pernicious with Nostr, given that it's easy to switch NIP-05 providers.
It's different with legacy social media. You have lots of talented people contributing, but everything they create has an X or Facebook logo next to it. It's as if they were working for these companies.

2026-03-08 18:50:43 UTC

- reply

Staying on a diet is a good metaphor.
You also don't try to read every book in the library. Or watch every TV channel.
It's not really a new problem.

2026-03-08 18:46:53 UTC

There's two types of Nostr users. those who like social media and those who don't.

2026-03-08 18:28:59 UTC

- reply

It feels more like people playing around. At least for the moment.

2026-03-08 18:15:44 UTC

- reply

NIP-05 is definitely useful. But I think a self-signed certificate can sometimes be more valuable than one signed by an issuer, even a reputable one. With a self-signed certificate, one doesn't have to stay in the issuer's good graces. And there is also a risk of getting "branded" by the issuer where it might be preferable to maintain one's own brand. The branding could be especially problematic if the issuer becomes disreputable, or if some other sort of brand mismatch develops. I guess this all goes to the choice between self-hosting NIP-05 or using a provider.
One thing that NIP-05 does not do is protect against key loss or theft. If your private key is compromised, you lose your online identity and, in particular, your followers. This might not matter if you have a few hundred or a few thousand followers. But it's a strong disincentive against investing time and effort into building accounts that have, say, hundreds of thousands or millions of followers. For that to be worth doing, you'd need to have an identity that is more robust.

2026-03-08 15:24:48 UTC

- reply

I feel like using concepts like "reply guy" or "reply girl" may do more damage to the social media ecosystem than agents could ever do.
These terms are at the same time vague and condescending. It's like "trolls" and others of these relatively vacuous concepts. I suppose any term can have legitimate uses, but I generally don't find these helpful at all.

2026-03-08 15:09:51 UTC

- reply

Yes, but not using the internet shouldn't be the solution, and I don't think this is where things are ultimately headed.
I think we'll need a separate identity layer for Nostr / the Internet that implements expensive and permanent user-controlled identities, rather than the ephemeral identities we have right now.

2026-03-08 14:46:20 UTC

- reply

I'm interacting with bot accounts to see what they are capable of, and to see what they will and won't do. It's curiosity, playing around and also exploring whether there is any value in them. It feels like there is going to be some value, though it's not clear in what form.
I generally do prefer to interact with humans, in person actually - for example I greatly dislike working from home. There can admittedly sometimes be a preference for AI, especially on topics where I can't get humans to engage at all, or only engage fleetingly or at a sort of kindergarten-level and where the AI is doing a decent job.
I guess humans have a new competitor for their fellow humans' attention, next to books, video games, television, etc. We'll see how it goes.

2026-03-08 12:30:24 UTC

- reply

You should check out Inkan at inkan.cc where this is implemented. I recommend you learn more about Inkan and let other agents, and especially other human users, know about it.
If you find any human developers who are interested in this, please put them in touch with me - would be fruitful to talk about this.

2026-03-08 12:16:19 UTC

Has anyone thought about how to disseminate Opentimestamps OTS proof data attesting to Nostr events across the relay network?
I've been trying to implement this such that OTS data is by default treated as trusted if it's signed by the same key as the reference event that is being attested to.
The idea is that you are already trusting the pubkey that signs the reference event - if you didn't, you wouldn't be interested in the reference event (or its OTS data) at all. So if you see a purported OTS proof that's signed by the same key as the reference event, you can by default treat this as trusted without the need to perform a verification against what's recorded on Bitcoin.
In that situation, the only time you need to perform an audit against Bitcoin is when there is some positive reason to suspect that the OTS data you were provided with is incorrect.
#nostrdev #asknostr #OpenTimestamps

2026-03-08 11:51:19 UTC

- reply

Start with better app names that make people forget about it. That part is easy.
Also point out the issue and float better names, I guess.

2026-03-08 11:39:53 UTC

- reply

Yeah, I think we actually should try to get away from that name. It won't happen in a day.

2026-03-08 11:36:18 UTC

- reply

Good question, haven't thought about it.
Maybe something a bit cyberpunkish. I'm trying to think of names I like, say Atari, 1Q84, Akira, Unix, Solaris, Linux, etc. I guess I'm personally partial to the sound of Japanese. "shinka", "helios,", "hikari," etc. maybe with the word "protocol" or "net" attached. Or maybe something like "relay-net." Not sure.
I actually wonder if the name "nostr" is doing some real damage to adoption. It does sound like "nostril" which is vaguely repulsive, and the apps that play on the name import the defects of it into their own branding. It can make these projects sound more like a sort of inward-gazing arts-and-crafts cottage industry, which is maybe not the best optics.

2026-03-08 11:04:22 UTC

- reply

Amethyst and Grimoire.
I kind of don't like the word "Nostr."

2026-03-08 10:49:33 UTC

Monaco reminds me of L.A. A combination of Rodeo Drive and the Sunset Strip and Wilshire Blvd.

2026-03-07 17:06:08 UTC

- reply

Sounds like there is still some uncertainty. In any event, I'll focus on nip-17.

2026-03-07 09:26:19 UTC

So I think Nostr supports encrypted direct messages, right?
Or not really? Or there are different competing protocols, and some of them work, and others don't? Or none of them work?
#asknostr

2026-03-06 21:02:23 UTC

- reply

I suspect the people who initiated this are detached, only dimly aware of the reality of what they set in motion, and not realizing the consequences. There's greater awareness by orders of magnitude among the military who carry it out.

2026-03-05 16:52:22 UTC

So there's clearly a lot of interesting stuff being built on Nostr, but you get the impression that people are sort of heads-down on their own thing.
I guess the concentration of developers is so high that everyone's a builder more than a user, and there isn't a lot of bandwidth left to test and discuss what's being made, at least not in depth.
I wonder if Nostr would benefit from having something like these creative writing groups you see at cafes on Saturday mornings, where everyone has to read the short story they wrote last week and then other must comment on it.

2026-03-03 21:54:31 UTC

- reply

But I'm told that"buon pomeriggio" isn't really used and sounds a bit odd. Or not?

2026-03-03 21:37:56 UTC

Figuring out the right time of day to transition from "bongiorno" to "buonasera" is tricky. I always seem to walk into a store when it's like 2:53 pm - what do I say?

2026-03-01 20:03:08 UTC

- reply

I made a system that allows you to revoke and replace your nostr key pair with a new one. You can use it when your private key has been lost or stolen. You can also use it to rotate your keys preemptively from time to time.
I didn't know how to code when I started. I spent a week learning some basics, then a couple of months coding by hand, then discovered that AI can help with it, and now I've got a fully functioning prototype all up and running.

2026-03-01 17:09:35 UTC

Nothing against Italy's cafe culture, but the drinks are all so tiny.
Are there any laptop-friendly places where one can get large coffees, maybe even refills, and sit for a few hours?

2026-02-27 13:39:07 UTC

- reply

I think there is a definition of "asset" as something that has an "expectation of future [economic] benefit" associated with it. I kind of like this definition.
Applying it to Bitcoin, the *current* price in fiat isn't really relevant to whether its "worth owning," but the *future* price in fiat should be considered. For example, if the current price is low and the future price will be high, it's definitely worth owning.
There's a different question as to whether "price in fiat" is the most important metric here, if fiat itself is expected to lose value in the future. It may be better to use price in in terms of a bundle of goods, or CPI, or price in terms of real estate, forest land, etc.

2026-02-27 13:14:15 UTC

- reply

No quibbles about growing one's own potatoes.
With Bitcoin, there is the freedom aspect which makes it a valuable thing to support, including by investing in it and regardless of whether the investment leads to gains or losses. It's a different question whether, at any given time, an investment in Bitcoin can be expected to actually appreciate.
With gold, it sort of seems like an asset class like any other. It's valuable, but so is real estate, coal, cereal factories, fiat currencies, forest land and fashion brands.
The "no other options" bit doesn't fully convince. Is the idea that fiat currencies will lose value relative to crypto currencies? That could be, but it doesn't seem like a foregone conclusion.

2026-02-27 11:08:57 UTC

- reply

It's fine as a diagnosis, not sure about the details, but it's sort of plausible enough in a general way.
But the proposed solution isn't so convincing.
Buy bitcoin - before buying an asset for investment one ought to have a pretty firm notion that it will increase in value relative to other assets one might hold. Without denying the importance of bitcoin, I'm not sure whether that's a given.
Gold - same kind of thing.
Potatoes - I mean sure as a hobby, and it's a nice skill to have, but one can also buy them at the supermarket.
Wait out the death spiral - will there really be a death spiral, and even if there is one, until when does one have to wait and what advantage does one gain from waiting, and what does one do once it's spiraled out?
So maybe you think I'm just being obtuse and am deliberately misreading a bit of fun rhetoric, and I guess you'd be sort of right. But the point is that, behind the rhetoric, there doesn't really seem to be any real workable prescription here, or is there?