nusa
Nusa

Public Key

npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4

Profile Code

nprofile1qqsdgawwfvuhw5r3xr6zcluxx3h0jd5qpuawwn27e7qgj2qvmsvj86gqruz2m

Author Public Key

npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4

Show more details

Last Notes

2025-04-02 18:41:53

- reply

I’ve been thinking about this, yes. Have a couple of my own ideas percolating. I also have a demo selective crawler set up to pick from and have some plans to give people previews and selections, essentially saving them from endless test articles.

2025-02-27 22:08:01

- reply

From the accessibility standpoint there are a couple of things. There are too many buttons per page and it amplifies the urgency to understand what they are for. But there are no labels, the icons are very thin and for very nostr-specific actions. They take away the focus from titles. I’d consider putting them all into a three-dot menu with labels. It would signal that some actions are available but not be so distracting. And once you learn what those actions are, you can ignore the three dots more easily.

2024-12-19 11:05:11

- reply

You might be overestimating how much can be done in a year. Most projects don’t get a whole year’s worth of development done, because people work on them in their spare time and it’s disheartening to see the minuscule progress making everything even slower. Building something for free and supposedly for fun (or why would you?) makes it less likely to be polished and well made.

2024-11-29 15:11:07

- reply

The signing part is obvious, but posting to public relays is basically shouting in a public forum. You can always claim your content, but others can claim it as well. I am wondering if we all assume similar things or do we differ in our expectations? For instance, copying content is 0 cost. We might agree that impersonation is unwelcome and discouraged or not. Do users, clients or relays care? If we have a licence tag on a post, does it mean anything in practice?

2024-10-23 15:12:39

- reply

I agree. I just wanted the point of giving credit emphasized.

2024-10-23 06:41:46

- reply

When is it plagiarism?
Is intellectual property not a thing anymore?

2024-10-14 07:44:35

- reply

I might be a little naive, thinking that anyone else might use a content search DVM I’m building for my own use, but I find the idea of interchangable microservices and cross-implementations fascinating.

2024-10-12 07:12:38

- reply

The current proposal for DVMs has all the right parts already. Whichever DVMs answer your event, which describes your query, are the ones up and running. If you find any of them suspect, you can filter either on client or user level. We just don’t have enough of them built yet.

2024-10-11 18:40:55

- reply

If you turn custom APIs into DVMs you can keep the relays as they are and also keep the interoperability while handling complex queries in any backend configuration you find suitable for a given task without prescribing anything.

2024-10-02 07:10:25

- reply

I’ve noticed in the EU context, a propaganda campaign priming people to believe it is their overconsumption that causes electricity supply and pricing issues and telling them the virtuous way to live is to downscale their energy needs. Energy use is now bad across the board.

2024-09-22 10:03:39

- reply

Is this in line with what you are saying? I’m really curious, but don’t quite know how to discuss this.
https://github.com/pubkeychain/pkc-protocol

2024-09-22 08:50:13

- reply

For all the women out there, who find their menstrual cycle getting longer and longer or disappearing on low carb, dial some more carbs into your diet in the last week of your cycle, approximately day 20+.

2024-09-13 16:15:44

- reply

An effective search requires an index. In a decentralized system, the index can’t find all the content unless someone tells it where to look. Looking up content, indexing and storage take resources, so it can’t be done well or long term for free. I want to make a DVM that would take a npub and a list of relays and index the events for a fee. The same DMV would then serve the results of a search as a list of nostr events that match the query. Users keep the index alive by adding to it.

2024-09-13 15:24:06

- reply

I actually want to build a Discovery tool. I have a real open question though. If you could give a few sats to an open source DVM so it would index your content from a relay you supply and make it searchable, would any of you do it?

2024-09-13 14:52:47

- reply

I like the bootstrap archive notion. We can keep it out of the general relays. I’m mostly interested in content creators who have invested major effort and would be willing to go an extra mile to set this up on a self-hosted or paid relay. I don’t expect it to work with zero input from the user.
For the clients, maybe they can offload the task to a DVM so they don’t independently have to implement the same lookups. The DVM provider can also supply the archive and then use it to inform the clients on demand.

2024-09-12 16:00:58

- reply

I see both as closely related in that you want to utilize a reference to the previous npub. I know I might be going off on a tangent, but I can see cases where you might want to preserve an identity over multiple key rotations. Should I consider that a completely separate topic?

2024-09-12 14:34:53

- reply

I like your proposal. I have been thinking about this a lot lately as well.
Do you think it’s possible to treat this as a sort of password reset? The phrase is not ideal, but it’s descriptive. Users sometimes have a hard time with any sort of secret keeping. In that case, I would imagine they would appreciate it, if the chain of keys remained and was linked as one identity. So the revoked keys remain read-only, as you already have planned, but some relays might opt to keep the events and clients might include them as part of the profile/history of a user and have that as a feature.

2024-09-09 09:45:52

Does nostr have any inherent intellectual property or licensing assumptions for the published content?
#askNostr

2024-09-04 06:36:44

- reply

I think reputation and trust go hand in hand. I like the web of trust concepts, where global trust scores don’t mean as much. We’ve found in the last few years that we vary in major ways by how much each of us trust public authority figures with established credentials or various conspiracy theorists. I don’t think it’s a stretch to find two people who sort a given list in exactly opposite directions.
People are also incredibly ingenious about gaming reputation systems. If given enough time we tend to produce a situation where everyone is suspect and we just end up with zero reputation all round, then resort to buying standing and pretend it’s meritocratic.
We should try to avoid the trap of social scores and any scoring authority, even in algorithmic form.
I don’t have any solutions though, only wishes.

2024-08-31 08:32:42

- reply

Look for the feeling and attitude of being a team. From your description it doesn’t seem like it. Your life with a partner will require some adjustment from the solo play and either one of you should not be making all the sacrifices.
Additionally, kids are amazing, but they will expose all your weaknesses in sometimes heartbreaking ways. Try to aim for ‘oh dear, how do we handle this’ and not ‘whose fault is this mess’. Consider other situations as signposts.

2024-08-25 21:17:31

- reply

I’m aware. But it’s and idea I would like explored and debated, not simply dismissed on principle.

2024-08-25 17:52:24

- reply

For the unique static identifier linked to a permanent record on a distributed ledger that you own.
It's a safety net. If your nsec is compromised you would want a way to rotate the keys that is not accessible simply by way of having the nsec in hand. If all you require is nostr events, then the bad actor that grabbed your keys could post these same events in your name and permanently lock you out.
It is also service-agnostic and nostr is not the only reason you might use this, just currently the most obvious one.

2024-08-25 10:59:30

- reply

I’m writing it down here for now: https://github.com/pubkeychain/pkc-protocol
Do you have recommendations where to share this for some feedback?

2024-08-24 15:50:48

- reply

I know how to do this in a self sovereign way. It basically gives you a ‘reset pass’ flow as well. It would require a few things though, which I can only describe atm and not yet code into existence.

2024-08-24 08:45:43

- reply

Wow, I was spectacularly unclear 🙈 I meant to say that the static identifier can as well be a satoshi name even if it’s a mostly random mix of letters and the websites and users can then name themselves whatever they want.

2024-08-24 07:34:58

- reply

In the end it’s possible that the names don’t even matter. For the lookup to work you need a static identifier to which you can associate new ips and new certs. Maybe we can live without the global naming, since we use search engines, social media posts, adds, and qr codes to get where we want to go.

2024-08-23 19:56:09

- reply

My main focus has been on providing a self sovereign failsafe for lost nostr keys, and my reason for using the ord name instead or number was because it’s shorter. Readability of handles didn’t matter to me as much. I consider it more in the sense of a ‘telephone number’ made up with letters, for which you could maintain a personal ‘phonebook’ and just name things what you want for your reference, but you never need to look at the ‘phone number’ to get to the person or website you want.
I see the value in naming though and in vanity names. I don’t expect the ord names to become suddenly popular and the availability of names people actually want is a real problem. But I absolutely don’t want to introduce a third party authority into it. That’s a hard pass.

2024-08-23 18:15:49

- reply

First, thank you 😊
It touches on both, depending on the service you plug it into. I’ll try to describe what I mean.
The handle or global namespace is the satoshi name, for instance the satoshi with ord number 1953186218210489 has a name of ‘aaaaaaaaaaa’.
For nostr, you could save the sat name to your profile and after anyone plugging that satoshi name into search could retrieve all history of all pubkeys contained in the inscriptions of that satoshi and it would all be your content. There are also ways to make sure your pubkeys aren’t appropriated by others.
I can also imagine a service that would handle websites. Dns basically does cert and ip lookup. If you extend the inscription and provide the ip address beside the pubkey, which can be used to verify that the server holds the private key, I can imagine a legit request can be made to get the website data.
Does that make sense?

2024-08-23 14:43:12

- reply

Here goes…
https://github.com/pubkeychain/pkc-protocol

2024-08-19 20:07:15

- reply

I have something like this thought out and am in the middle of trying to write out a protocol description. It ticks your boxes, except possibly the last one, since that wasn’t my main focus. Can I ask for your comment once I get over myself and actually publish my idea?

2024-08-18 08:42:07

- reply

Where I’m from, when millennials mention they don’t expect to ever get any pension from their mandatory payemnts into the system, the older generations mostly agree that it doesn’t look great, but their answer is that we now have this extra gov-run fund where you can invest additional money into your own retirement with a tiny tax deduction incentive. And I ask if they have ever looked up their portfolio and they look at me funny when I say why would I pay into a fund that will buy local government and government-owned businesses’ bonds with this money and tell me it’s all taken care of. It’s a great plan to distribute government debt, but not a great retirement plan. That part hasn’t sunk in yet.

2024-08-09 11:11:08

A storm with unusually dense lightning broke directly over our neighborhood the other night. We have a home office set up with quite an elaborate network and a lot of electronics. We had multiple surge protections in place for the power, but the surge came in over the coax data cable and fried our router and switch. 🙈