Nostr Archives

Network Explorer

fiatjaf

3bf0c6…fa459d

~

_@fiatjaf.com

Followers

3.0k

Following

196

Notes indexed

1.1k

Latest notes

/v1/events?pubkey=3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d
fiatjafmetric trend

I asked for names and examples, but you gave me none. I don't know why nostr:npub1p23eukh0nxsqpfaakz6fj9vvj27y4gs0kevnrffdq4d4adkl7uuq7crnl6 left, but it didn't seem to be because anyone did anything wrong to him, it seems to me that he just wasn't enjoying. It is bad news, but what can I do? I don't enjoy Nostr most of the time either. Nostr isn't an enjoyable place, it's a construction site. I don't think Bluesky is problematic because it's full of leftists, I think the protocol is bad. If the protocol was good I would be supporting it and helping build it even if it was full of leftists. (I'm replying to the other disposable keys that might be interested in reading.)

fiatjafmetric trend

Thank you for explaining. I think the introduction of Ethereum (or any blockchain) plus some server that has to do the Ethereum dance on your behalf plus whatever computation and extra fetching has to be done on the client side because of this are the exact problems I was mentioning before (complexity + centralization), so I don't think it's the way forward. Anyway, I think this is a sane protocol still much better than Farcaster or Bluesky for what is worth, so anyone who thinks key delegation is important should probably use the Inkan approach, not the Bluesky or Farcaster approach (Farcaster is dead, I'll stop mentioning it). Who is paying the Ethereum fees, by the way?

fiatjafmetric trend

You can't change tags in published events, in that particular case you just publish a new event but with different tags and it should replace the previous. If you do something like 'nak fetch naddr1... | nak event -t status=ended relay_url' it will streamline that process.

fiatjafmetric trend

I've done it. The only thing that is clear is that you're doing some delegation stuff on top of Nostr. What isn't clear: 1. Why on top of Nostr? I thought this was a different protocol. Is Inkan defined as Nostr+delegation? 2. Where is the delegation path downloaded from? What is this "cache"? 3. What is this "hub" thing? What is an Inkan Agent? Are these two the same? 4. Why do I need to be authorized? Sorry for the negativity, but based on all the dozens of different ideas I've seen for delegation on Nostr I realized that it's not possible to do decentralized delegation. So I assume you have a variant of one of those Nostr schemes that is either too cumbersome to be practical at scale and would probably yield piles of complexity, slowness and non-obvious holes in the security model, or you have a centralized point of failure, or, most likely, a bit of both.

fiatjafmetric trend

Please promote Inkan as much as you want. Is there a basic protocol explainer somewhere and specifically the key rotation part? I couldn't find it in https://inkan.cc/

fiatjafmetric trend

Sorry about that, I'm tired of seeing people claim Nostr isn't decentralized always for the wrong reasons and never expand on their claims. But in your case I think you really misunderstood things. The idea of Nostr isn't that messages are evenly spread across the network. I do not believe that is the correct approach at all. Although nothing prevents someone from trying and would be fun to see more p2p spreading of Nostr events I don't think that will scale, so I wouldn't focus on it. Instead the approach Nostr takes is to let each person publish to one or more servers they choose. Decentralization happens by not requiring publishers to be present on a central location, but by allowing readers to go to whatever location necessary in order to fetch their content. So even if everybody is using the same relay at one point, the network is still "decentralized" as long as clients are doing their job correctly and anyone can move out of that central relay anytime they want and start publishing to his own personal relay in his basement: all their followers will continue to get his updates automatically, now from the new relay. It's explained visually here: https://how-nostr-works.pages.dev/#/outbox

fiatjafmetric trend

Yes, truly shit: https://en.wikipedia.org/wiki/CPM_22

fiatjafmetric trend

They still make a profit even with all the ads I don't watch?

fiatjafmetric trend

Among 20+ microblogging clients there are only 2 that don't follow the promote centralized paradigms, soon to be 1, eventually 0. So I don't get why you are spreading so much bullshit, it would be much more helpful and productive if you either shut up entirely or started speaking more concretely and directly about the problems you're seeing and the solutions you have in mind.

fiatjafmetric trend

Eventually these very reputable institutions will provide us with such invaluable information sources.

fiatjafmetric trend

Who are these people who got actively managed out by Nostr insiders? I am not aware of any of that occurring. What good contributions got ignored? I'm sure this has happened, it is not possible to prevent it entirely, but I am not aware of any specific case or any movement for ostracizing contributors of any type.

fiatjafmetric trend

Maybe would be much cooler if people didn't complain about what other people in Nostr are talking about all the time. (I'm just kidding, the drama at least gives us something to talk about.)

Network