kawangoとshi3zが生命の冒涜だとめっちゃ怒られてるやつ世界に認知されてるんだな^^;
よお
"Important things are usually troublesome" - Hayao Miyazaki
The good thing about anime creation is that it's not bound by reality.
What I was thinking this month:
If we follow the current standards, the features for end users can not be realized.
If we don't, the features for developers can not be realized.
So,
Should we realize the features for end users and work towards a change in the standards in the future?
Or should we prioritize the standards and give up on the features for end users for now?
We are pleased to announce the publication of the First Public Working Draft for the did:nostr method specification:
https://nostrcg.github.io/did-nostr/
This specification defines a Decentralized Identifier (DID) method
(did:nostr) that utilizes the cryptographic key pairs inherent to the Nostr protocol. It describes how a did:nostr identifier can be created, resolved to a DID Document.
This initial draft represents the collaborative effort of several
contributors. We would like to extend our sincere thanks to:
- Maximillian George for valuable feedback and support throughout the initial stages.
- Manu Sporny for providing an essential sanity check on the approach and structure.
- The team at Block for engaging in insightful discussions that helped
shape the work.
We believe the specification is now at a stage where it is ready for
broader review and contributions. We warmly welcome feedback, suggestions, issue reporting, and contributions from the CG and W3C DID community and anyone interested in integrating Nostr identities with did-identity
standards.
We look forward to engaging with the community to refine and advance this specification.
https://lists.w3.org/Archives/Public/public-nostr/2025Mar/0006.html
I found it an interesting read.
How do you firstly get a DID document that contains a services section with relay list? In other words, what/where is a resolver or VDR?
The Cambrian explosion of use cases is coming :shakingeyes_sm:
nostr:nevent1qqsxssyqgz0znnlkqyh72948e5x4m6xtktsng3x6pg0z85uqrwmzakq3nuh2v
ディフィカルティの決定レンジを外れた過去ブロックに費やされた電力はサンクコスト、同意です👌
最後の一文の帰結すごいですね笑
This is the meme that represents the creation essence of the Ghibli master. He is saying again and again, "Uh, cumbersome!"
労働価値説が当てはまるパターンもあるんだけど（まあ価値より”原価”）やっぱ主観的価値理論のほうがしっくりきます。
過去のマイニングに消費した電力は価値にならない派なんですが、そこどうですか！？
All right.
Apart from checking the legitimacy of the URL, I don't also know of any other security defense other than a visual check by the user.
I know there are some that go a step further and validate and alert the sign message in Web3, but to do this, the attack case needs to be templated/specified.
Imagine you are visiting a phishing site. You are going to post a photo of your meal, but the app is asking a signer to sign for something new to identity usecase and something new to Bitcoin API.
Yes! And web is the key. of course, depending on politics, my intuition is gonna be harder times for apps. Who knows!