↳ 回复 事件不存在
84a2345fda04c7fbf5d02bcdbecdaeac0c63e05446dc7c09eed40814a5f49c1a
That's not good. Thanks for your client by the way. It's excellent. I'm using it as the base for Inkan.
Kind-1 (TextNote)
inkan
npub
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6lpubkey (hex)
d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23nprofile
nprofile1qqsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcprf58garswvaz7tmjv4kxz7fwva6kcat8w4k82tnddajsvulrhcNIP-05
[email protected]动态 (303)
↳ 回复 事件不存在
a99c611a804ff929fcc430a876399758e7ff291975b2c8a8b95d49a8b9acea45
Huh. Is there a possibility that this is country specific?
Kind-1 (TextNote)
InkanにNIP-46対応を追加しました。 Amberで試したところ、ちゃんと動いているみたいです。 これで、リモート署名を使いつつ、署名用キーが漏れたり失われたりした場合でも、新しいキーに切り替えられるようになります。 アイデンティティとフォロワーはそのまま。
InkanにNIP-46対応を追加しました。
Amberで試したところ、ちゃんと動いているみたいです。
これで、リモート署名を使いつつ、署名用キーが漏れたり失われたりした場合でも、新しいキーに切り替えられるようになります。
アイデンティティとフォロワーはそのまま。
Kind-1 (TextNote)
Just realized that I can use NIP-7 with Firefox on my cell phone. I had no idea.
Kind-1 (TextNote)
↳ 回复 事件不存在
0000b72c59e11f8ecedc68fa2e5fda79f580093df565652823dc314da30520c3
The second variant reports a feature, not a bug, as they say.
Kind-1 (TextNote)
I've added NIP-46 to Inkan. I've tested on Amber and it seems to work. This means you can now have a remote signing setup plus the ability to replace...
I've added NIP-46 to Inkan. I've tested on Amber and it seems to work.
This means you can now have a remote signing setup plus the ability to replace your signing key if it ever gets lost or leaked, while maintaining your identity and your followers.
Kind-1 (TextNote)
↳ 回复 事件不存在
14b3838a6e5f77fa93b9c9041e9ae7556df8c66267b53e0a2298f967f9f7ffea
They must offer something distinctive.
Kind-1 (TextNote)
↳ 回复 事件不存在
fedef7a65714b6b10b4ba320f46e41b3f4ceba4cf2ac9532bc240c6879954f0f
The fun is being able to sell *that* thing, not just anything.
Kind-1 (TextNote)
今の仕組みだと、オンライン上のアイデンティティは、ほとんど秘密鍵そのものになってしまいます。 その鍵が漏れたり失われたりすると、そのアイデンティティも終わってしまう。 Inkanはそこを変えようとしています。 マスターキーはコールドストレージに置いたまま、普段の投稿や署名には別の署名用キーを使いま...
今の仕組みだと、オンライン上のアイデンティティは、ほとんど秘密鍵そのものになってしまいます。
その鍵が漏れたり失われたりすると、そのアイデンティティも終わってしまう。
Inkanはそこを変えようとしています。
マスターキーはコールドストレージに置いたまま、普段の投稿や署名には別の署名用キーを使います。
もし署名用キーが漏れたり失われたりしても、マスターキーで取り消して、新しいキーに委任できます。
アイデンティティもフォロワーもそのまま。署名用キーだけ新しくできます。
プロトタイプはこちらです：
https://www.inkan.cc/
NIP-07拡張機能でログインして、すでに動いているテスト用アイデンティティたちに話しかけてみてください。自分のアイデンティティを作ってみることもできます。
https://image.nostr.build/27d256a9fcba336f567ea6369d0b6984feb72b00b06a5205efe029534113ab99.jpg
https://image.nostr.build/ca9b087993604f7b7d9473a661c946ecd20015186a112021f4858efa6c1e1808.jpg
https://image.nostr.build/fa5c1f8e19e3727b6693e6f105baf4eae15c4579343148fc413ac50acfe8edf0.jpg
https://image.nostr.build/f7002003e981f536bec01789875c17596f6c0eac87526a071c350480029c5827.jpg
https://image.nostr.build/3f6b865161cba71839910daa4f3c80b46c36400d5e2332ecad927b86003fcaad.jpg
https://image.nostr.build/a10f0ac6d508ea26602348bbec60bda4659667f75adfda46d9b8354224cd08fe.jpg
https://image.nostr.build/ce3d8e4de21b3e6f252f5aedbf02dd54323a26c1992c637438fabb9b14ea7afd.jpg
https://image.nostr.build/60f8a59a68386e2f28b792b63d09729ed494ebe6caddb7f6810e3c10f48b6e82.jpg
https://image.nostr.build/55000542eb9db4794c8ec07dcdfc93fa5560633afcd754476f6809e9c4bb5ac7.jpg
Kind-1 (TextNote)
I made a bootable live USB image that has the Inkan Management Utility pre-installed. This is meant to provide an airgapped environment for signing de...
I made a bootable live USB image that has the Inkan Management Utility pre-installed. This is meant to provide an airgapped environment for signing delegations and revocations of signing authority between key pairs, and for identity creation.
The OS is expected to be amnesic across reboots and networking is disabled. I added QR codes to conveniently transfer keys and signed declarations to an online system. You can also configure persistent storage to keep the keys that secure your identity right on that USB.
https://gitlab.com/inkan_dev/inkan-offline-live
Kind-1 (TextNote)
↳ 回复 事件不存在
0eea20ab5a773e5c67f4f986b4d6e0269740b6a276abf2406e0723e6504d5835
I still look at NIPs for ideas, but I'm not overly concerned about conforming to them when it's not convenient. If I did I wouldn't get much work done...
I still look at NIPs for ideas, but I'm not overly concerned about conforming to them when it's not convenient. If I did I wouldn't get much work done. I do try to engage in protocol discussions but the experts are mostly not very responsive, which leaves one without proof that there is actual expertise there. If one community moves too slowly, I guess it may be better to divide one's time and talk to a different one, or just to focus on the product.
Kind-1 (TextNote)
↳ 回复 事件不存在
991d092598d441671267ff4a1e60fe9dc4a8448023e8908d5050385d9c09db55
Thanks, that's what I figured. I'm currently just using a non-networked version of Tails to generate the master key, and then put an encrypted version...
Thanks, that's what I figured. I'm currently just using a non-networked version of Tails to generate the master key, and then put an encrypted version of it on a USB. The master key most likely will have to be used only once, so it's easy to store copies in, say, a safe deposit box. There are probably better ways to do the airgapped operations that my method requires. I'll look out for updates on what you're doing.
Kind-1 (TextNote)
↳ 回复 事件不存在
d20da01436bd2ecedda4719226f02c89141898731cd09c6ce7125e73efd4e2bc
This may in some ways be orthogonal to what you're doing, but maybe it's related enough to be of interest: nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0s...
This may in some ways be orthogonal to what you're doing, but maybe it's related enough to be of interest:
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqgqgm3gesf2yw9drg7mqfvsnvxpfes4yc9hm6tdu7twqw0dc27shgqrdjke9
Kind-1 (TextNote)
↳ 回复 事件不存在
e9b26d54a69300861dd320adfa9556cb29553fd54ccc029e23435920c3010c58
What makes vicious characters interesting is maybe the virtuous characteristics they need to have to be effective in the pursuit of their vices. Or ma...
What makes vicious characters interesting is maybe the virtuous characteristics they need to have to be effective in the pursuit of their vices. Or maybe it's considering why their vicious goals seem good and worthy of pursuit to them.
Kind-1 (TextNote)
↳ 回复 The Fishcake (nostr.build) (npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w)
Many viewers I guess, few participants, just like on any other sns
Makes sense, still feels meaningful. Thanks for this service by the way, which I gather you're providing.
Kind-1 (TextNote)
↳ 回复 The Fishcake (nostr.build) (npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w)
This chart is for 7 days
Then that's pretty meaningful and good news.
Kind-1 (TextNote)
↳ 回复 The Fishcake (nostr.build) (npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w)
Number of times a media was requested from the server
During what period?
Kind-1 (TextNote)
↳ 回复 The Fishcake (nostr.build) (npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w)
Nostr is definitely dead, in all 200 countries of the world. 👇 https://i.nostr.build/zxxrJiIVGzTFCL...
What does "requests volume" mean?
Kind-1 (TextNote)
WebXというカンファレンスも13日から１４日まで開催されるみたい。これはBlockchain Weekの一部なのかな？それとも別イベント？ https://webx-asia.com/ja/ nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573...
WebXというカンファレンスも13日から１４日まで開催されるみたい。これはBlockchain Weekの一部なのかな？それとも別イベント？
https://webx-asia.com/ja/
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxjmntv9hzucmr9uqzqqv82stl0ka9fu4ydf6754kh5j3d2x8t2zcpr0r66gjjrd4vv620slgu47
Kind-1 (TextNote)
Japan Blockchain Weekのサイト、上の方には「７月１日〜７月１５日」と書いてあるけど、下の方には「Kickoff Eventは７月１２日に開催される」と書いてある。スケジュールページを見ても、今のところ７月１２日分しかない。「July 1」は「July 12」のtypo? 行きたい...
Japan Blockchain Weekのサイト、上の方には「７月１日〜７月１５日」と書いてあるけど、下の方には「Kickoff Eventは７月１２日に開催される」と書いてある。スケジュールページを見ても、今のところ７月１２日分しかない。「July 1」は「July 12」のtypo? 行きたいんだけど、いつ行けばいいのかよく分からない。
https://japanblockchainweek.jp/
Kind-1 (TextNote)
日本に着きました。みんなさん、こんにちは。
Kind-1 (TextNote)
↳ 回复 Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)
They're spending millions of dollars.
Really? In a way this might explain some things, I mean some of the distortions.
Kind-1 (TextNote)
↳ 回复 Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)
The people with the money and the power aren't talking to me. As you can see.
I suspect though that, with the current state of Nostr, any amounts of money or power that are involved are pretty limited. Probably.
Kind-1 (TextNote)
↳ 回复 Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)
I didn't think there was. I thought they were just being a bit lazy or overly-conservative and it ma...
I'm interested in these protocol politics to some extent. I've been wondering to what extent the Nostr community is willing to have, or is sophisticat...
I'm interested in these protocol politics to some extent. I've been wondering to what extent the Nostr community is willing to have, or is sophisticated enough to be capable of having, serious conversations about the protocol. There's a lot of silence when one raises questions or makes suggestions that one would expect to draw interest and generate discussion. That sort of silence combined with irrationality is usually not accidental and one does better to pay attention to it. Discussions that aren't being done in good faith are a time drain, and correctly recognizing them as such should affect one's decision how much energy to invest in talking to this community rather than another one.
Kind-1 (TextNote)
↳ 回复 事件不存在
a7a464be69cdf411aedb8b21c5618a432ec91787ade336a3389337f98b38a916
I'm trying to follow this. So NIP-22 says that you shouldn't respond to kind 1 events with kind 1111 events, and you say that restriction is completel...
I'm trying to follow this. So NIP-22 says that you shouldn't respond to kind 1 events with kind 1111 events, and you say that restriction is completely unnecessary and makes no sense. And then you're saying that clients that honor the restriction don't display your kind 1111 responses to other people's notes, right?
But is there any self-serving motive behind not displaying 1111 responses to kind-1 events? Any unjust enrichment? I'm trying to understand the intrigue, if any.
Kind-1 (TextNote)
↳ 回复 事件不存在
a7dc29986ebb32d7998d71297a9440788d4aafe45201e5116e83db16beda414d
This is interesting and it's good to have a reference implementation. It's not clear why one would want to use it.
Kind-1 (TextNote)
↳ 回复 事件不存在
3f007f861cc348462f3df1be9365e3a4537c011f73beb1ea0808bc3c507c02e5
"from a technical perspective I find it fascinating" I use it only because of its technical properties. In essence, "Nostr" just means to me using pu...
"from a technical perspective I find it fascinating"
I use it only because of its technical properties. In essence, "Nostr" just means to me using public key cryptography to authenticate online, which I think is the correct way to "be" on the internet given the current state of technology.
I had to add some public key infrastructure for replacing lost or stolen keys on top of the base Nostr protocol for it to become genuinely usable. With that in place, I now have a technologically acceptable way of maintaining an online presence. So I'm going to use that.
Kind-1 (TextNote)
↳ 回复 Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)
Yeah, difference in scale, not intent.
There's a related thought in Plato's Republic. Socrates observes that bands of robbers must make use of justice to accomplish anything: "[D]o you thi...
There's a related thought in Plato's Republic. Socrates observes that bands of robbers must make use of justice to accomplish anything:
"[D]o you think a city or an army, robbers or thieves, or any other group that jointly undertakes something, in an unjust manner, would be able to accomplish anything if they were unjust towards one another?
Of course not, said he.
But what if they were not unjust to one another? Wouldn’t they be more likely to accomplish something?
Very much so.
Because injustice, Thrasymachus, presumably causes factions, hatred, and conflict among them, while justice brings like-mindedness and friendship."
Plato, Republic 351C-D
Kind-1 (TextNote)
↳ 回复 事件不存在
95f6b9c17fc2a2e224ed55f757ad2d095d142250d3925892ce5ba9ec0a38cc8a
I don't know too much about ATProto, but it seems that it doesn't give users proper decentralized identities. It seems that Nostr + an Inkan identity ...
I don't know too much about ATProto, but it seems that it doesn't give users proper decentralized identities. It seems that Nostr + an Inkan identity is a direct alternative to it.
Contrasting ATProto with https://www.inkan.cc may be a good way of framing the discussion about cold storage identities. I'll need to investigate.
Kind-1 (TextNote)
I keep coming across mentions of "zero knowledge proofs" in startup / VC type materials. Sometimes there's an opaque or barely coherent definition, li...
I keep coming across mentions of "zero knowledge proofs" in startup / VC type materials. Sometimes there's an opaque or barely coherent definition, like "a method by which one party can prove to another party that a statement is true, without revealing any information apart from the fact that this specific statement is true." I wonder if ZK proofs are being used for anything real or interesting, or if it's mostly marketing hype.
Kind-1 (TextNote)
↳ 回复 事件不存在
f5b61df8fd5b218c00a92fa78ab7d69e51947ac707878a917fd29c386ed44492
I don't know enough to decide if this is accurate, but it's consistent with how Nostr feels at the moment. It's probably not the end of story.
Kind-1 (TextNote)
↳ 回复 事件不存在
c161decdf77b113b849da9d3091dc78bc75e2c5a0c19f369a00ad99cad69803e
FYI key rotation has been implemented. See below. nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxc...
FYI key rotation has been implemented. See below.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqsq3hz3nqj5gu26x3akqjepxcvznnp2fst0h5kmeukuqu7ms4apwsqlkt4p3
Kind-1 (TextNote)
↳ 回复 事件不存在
706d1da49cf42e520e2befe15467da0d8bad8427c013d7181acfc85dcc057793
I hope he'll change his mind before deciding.👇 nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyghwumn8ghj7mn0wd68ytnh...
I hope he'll change his mind before deciding.👇
nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyghwumn8ghj7mn0wd68ytnhd9hx2tcprpmhxue69uhhxurpw35kzttpwf3kzmnp9e3k7mf0qqsf3gt8ny50lhjslgfkd20g65uswjwj4ejga78hkravk24l4833fkcsfxsuq
Kind-1 (TextNote)
↳ 回复 事件不存在
c425339718eae86c72417bd2ea8c1afc6331bcfd76768c6eeefe8d2d57fb65d5
Thanks. I took a look at nip-32 / 1985 events. I think these won't work here unfortunately. The problem is that the 1985 event is a separate event tha...
Thanks. I took a look at nip-32 / 1985 events. I think these won't work here unfortunately. The problem is that the 1985 event is a separate event that points to the target event with an e-tag, and the 1985 event doesn't automatically travel with the target event. The client has to correlate the 1985 with the target event and fetch the 1985 separately. I tried OTS implementations of this kind when I initially experimented with OTS and it doesn't work well. The OTS proof arrives asynchronously, so trying to filter out events that don't have valid OTS timestamps leads to lags and blocking on the client side.
What's needed is for relays to splice the OTS timestamp into the target event itself, so the client gets the proof simultaneously with the event and can filter out events that don't have a valid timestamp immediately when they arrive. The OTS proof can be thought of as playing a similar role to the signature on the event. One wouldn't want to send the signatures separately from the events to which they pertain.
As for the use case, OTS is a crucial component of key rotation systems. Without OTS, it's not possible to hold a cold storage identity and revoke and replace Nostr keys that have been leaked or lost, but with OTS it's possible. See below for an implementation and more detailed explanation.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyfhwumn8ghj7mmxve3ksctfdch8qatz9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqsq3hz3nqj5gu26x3akqjepxcvznnp2fst0h5kmeukuqu7ms4apwsqsuwagr
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qqs8z5jezmes2fxl8cm89uza098hhnkhusfc3zc0p7agvlmkpwc4ehgy4x497
Kind-1 (TextNote)
↳ 回复 事件不存在
96e865ebec2056f0023240a2ce9666ec2615c48ee6b8b31510a28435816d6d64
Yes, decentralized timestamping is the actual service that blockchains provide to the world. The value of cryptocurrencies derives from that.
Kind-1 (TextNote)
↳ 回复 事件不存在
5cd95893fe74b73e68bc247bdb8a3eba88d79ec8fc5f97df8e9983eb2ee90039
See below for a fuller explanation of this. I think it would be helpful if relays could return events with OTS timestamps spliced into the event. We m...
See below for a fuller explanation of this. I think it would be helpful if relays could return events with OTS timestamps spliced into the event. We may not yet have mature relay software to do so, but I'm trying to raise awareness of this. The role of OTS timestamps is related to the role of signatures. The signature proves *that* the event was signed by a certain key, and the timestamp proves *when* it was signed (or more precisely, that it was signed by the time some bitcoin block was created). I think ultimately OTS will be an important piece of Nostr infrastructure.
nostr:naddr1qvzqqqr4gupzqh4yvjqytwcl7g3x2hwaxmndemwugdvscfsfp3yxhmecaazsmfdaqyv8wumn8ghj7cm9d3kxzu3wdehhxarj9emkjmn99uq3kamnwvaz7tmjv4kxz7fwwdhx7arj9ehxcw358yunjwf0qq24snm60p44wktwgfuyy4esv9mhskj62qu456nczpd
Kind-1 (TextNote)
↳ 回复 事件不存在
5cd95893fe74b73e68bc247bdb8a3eba88d79ec8fc5f97df8e9983eb2ee90039
Same question twice within a space of 24 hours: nostr:nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqyghwumn8ghj7mn0wd68ytn...
Same question twice within a space of 24 hours:
nostr:nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqyghwumn8ghj7mn0wd68ytnhd9hx2tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qpqjlujg5klnhpceyxadefrecut6un9g85qkhdr6wfmt77uccvg6ahsve0zwm
Kind-1 (TextNote)
wss://nos.lol/ also currently doesn't support OTS, as far as I know. It would be great if nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamls...
wss://nos.lol/ also currently doesn't support OTS, as far as I know. It would be great if nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c were to do something about this at some point.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcpz9mhxue69uhkummnw3ezumrpdejz7qpqmfndk3mj9h6axwqlj4sj2fykfz0wztjlcyutp0zglhcthy3h426s0380h8
Kind-1 (TextNote)
↳ 回复 事件不存在
6e09c980eff63d9d02722671794192e7553e79795d8034b73adf108a26e48905
What is SEC-08?
Kind-1 (TextNote)
↳ 回复 事件不存在
2ac3f76d85c3f109a0a62dff22d4e3a6e2aa777dba9197181556fab8d2c9ee58
You could timestamp them on the relay after they've been published, or client-side right after they've been signed. You need a mechanism for updating ...
You could timestamp them on the relay after they've been published, or client-side right after they've been signed. You need a mechanism for updating the timestamps once the event has been recorded on Bitcoin and the full Merkle proof is available.
I don't really know what people use these days to timestamp events. I've been running my own server that timestamps events on the inkan relay, but I haven't tried to make something that works on other people's relays.
Kind-1 (TextNote)
↳ 回复 事件不存在
b3cd657405e91d479dbb1a63a7de89da8bd324482b33c1903cf67a9d757e3fed
Just trying to move the needle ever so slightly.
Kind-1 (TextNote)
↳ 回复 事件不存在
ad422926cfd74375b04368530c80c9dc55ea6e6ff8900d1a5a2cb21f468234ad
OTS + Ethereum actually. Agree I should think more about how to frame it, not easy to do. Thanks for the nice discussion!
Kind-1 (TextNote)
↳ 回复 事件不存在
549a4886e86cef1ef21cba8407999584382796ab7741324293ed81c70bb30efd
Constantly validating against the blockchain actually isn't as difficult as it might appear at first glance. This was gently pointed out to me by nost...
Constantly validating against the blockchain actually isn't as difficult as it might appear at first glance. This was gently pointed out to me by nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw in the note below.
And I think Nostr clients other than Inkan are starting to do this validation. From the replies to the note below, it looks like Amethyst has caught on to it.
Also, I think that speaking of "external trust" is slightly misleading or at least infelicitous, because it sounds like we are proposing to trust a bank or a government or Microsoft or something. What's being trusted here are blockchains like Bitcoin, which are decentralized and are trusted with millions of dollars by fairly sophisticated agents.
nostr:nevent1qvzqqqqqqypzqh4yvjqytwcl7g3x2hwaxmndemwugdvscfsfp3yxhmecaazsmfdaqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwv9a85ctdduhxuet59uqzqqqqt9paujtj5x0ffcqmde585a8hkwdvqrzw76t8y9l0erfefaxzu0az8r
Kind-1 (TextNote)
↳ 回复 事件不存在
9d381f5bb2dad372a6c08014b1cf7dd45e853bdc8c1fa28a1e607467605b365a
It's hard to form a consensus around something that's not functional. But yes, functionality by itself does not automatically lead to consensus. In a...
It's hard to form a consensus around something that's not functional. But yes, functionality by itself does not automatically lead to consensus.
In any event, Inkan has been designed to not disrupt the regular Nostr protocol. It can be used regardless of whether or not others agree with it, and using it does not interfere with one's ability to use regular Nostr.
Also, as I noted elsewqhere, it does not require new users coming to Nostr to be persuaded to create an Inkan identity, or even to know that the option exists. Of course, for some new users, that option may itself be part of what draws them to Nostr.
Kind-1 (TextNote)
↳ 回复 事件不存在
97f92452df9dc38c90dd6e523ce38bd726541e80b5da3d393b5fbdcc6188d76f
It's OpenTimestamps. https://opentimestamps.org/ The created_at timestamps that are included in Nostr events are self-declared and can be faked. Inst...
It's OpenTimestamps. https://opentimestamps.org/
The created_at timestamps that are included in Nostr events are self-declared and can be faked. Instead of relying on these, Nostr events can get objective timestamps that are recorded on Bitcoin, proving that the event must have existed at the time of some Bitcoin block. To do this correctly, it's necessary to timestamp a concatenation of the event_id and the event's signature. These timestamps can be created efficiently for large numbers of events using Merkle trees, and it's pretty quick and easy for clients to verify that an event has a valid Bitcoin timestamp.
For Project Gutenberg, timestamping these books on Bitcoin would prove that they existed in the exact form in which you recorded them as of, say, June 11, 2026. This would give people the ability to confirm that these books have not been altered since that time. There have been attempts to alter classic works to fit current sensibilities, and there could conceivably be attempts to either remove the unaltered versions from the internet altogether or to obfuscate what the original version was.
It's possible that someone has already timestamped the Project Gutenberg texts, I'm not sure. But what you're doing seems like an opportunity to do so.
Kind-1 (TextNote)
↳ 回复 事件不存在
5b963aac1e39bd988ac4a7ad649c0bd60667929480380bda3d32dc6b2a7344f5
Inkan does not interfere with the Nostr protocol's ability to do the following: "creating verifiable messages with nothing other than a private key" ...
Inkan does not interfere with the Nostr protocol's ability to do the following:
"creating verifiable messages with nothing other than a private key"
It uses the regular protocol to create messages whose signature is verifiable with nothing other than a private key. Inkan's events just *are* regular Nostr events, no difference here.
Now the regular Nostr protocol (without blockchain-based OTS) completely fails to verify the time at which an event is created, and it also fails to verify the time at which keys make or revoke delegations of signing authority to other keys. Inkan verifies these things.
Your main objection seems to be that Inkan uses something "other than cryptography" to verify these things. I'm not sure what exactly you are referring to, but maybe it is the decentralized mechanism used by blockchains to give events objective placement in time. This is of course the essential functionality that blockchains have contributed to the world, the very thing that makes cryptocurrencies possible.
If Nostr does not avail itself of this blockchain-based timestamping mechanism, there is no way to maintain a Nostr identity that is secured by keys kept in permanent cold storage. If Nostr uses this mechanism, there is a way to maintain such a cold storage identity.
I'm not really convinced that this mechanism is something "other than cryptography." Isn't blockchain-based timestamping a cryptographic concept?
Also, I'm not convinced that use of this mechanism leads to lesser independence. I'd say the ability to maintain a cold storage identity gives you greater independence.
So if "independence" is the core value you were referring to, I'd argue that Inkan is a way for the Nostr protocol to better realize that value.
Kind-1 (TextNote)
↳ 回复 事件不存在
298a07377934a061c0553e3c2c14bf7e680885aa52e6ada81f6558779c45b7b2
Kind of a chicken and egg situation?
Kind-1 (TextNote)
↳ 回复 事件不存在
699df17dc027c783620c3921f74973aa361b9e0fc3d5d30f714a8086beea40c4
What is the "core value"?
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
No shortage of proposals. None with any reasonable amount of consensus.
What's required isn't consensus but a proposal that works.
Kind-1 (TextNote)
↳ 回复 事件不存在
e26f75ae772593637635e4bc9f7d4a0799ed41732c81729fa8b3549b6d2289f6
I'm looking through these discussions. They seem confused and it looks like nobody has actually implemented anything, which is not surprising since th...
I'm looking through these discussions. They seem confused and it looks like nobody has actually implemented anything, which is not surprising since the approaches that are being discussed don't work. Some of these still make reference to NIP-26, which is a complete non-starter.
Maybe frustration with the lack of progress in these discussions explains why a lot of people weirdly insist that key rotation is some sort of near-impossibility. I tell people that they can simply log in and use it today, but instead of trying it out they keep making comments unmoored from reality like the below "[t]here is no way to do cold wallets." Normies I guess.
nostr:nevent1qvzqqqqqqypzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghsqgqjeuapgq7m6rzkgh8d9jayre7mzvcptzp85s7h82y0k5q7sd2hxszx6p9g
Kind-1 (TextNote)
↳ 回复 semisol (npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj)
Nostr.land is planning to support OTS. I’m planning to use the standard OTS spec that is already we...
The s-tag is for the signature of the reference event. Just to be sure, when you refer to the "standard OTS spec," I hope you don't mean the old brok...
The s-tag is for the signature of the reference event.
Just to be sure, when you refer to the "standard OTS spec," I hope you don't mean the old broken NIP-03 where the item that gets timestamped only includes the event_id and does not include the signature (see below for some discussion of this).
Also, I think splicing the OTS proof into the event that gets returned by the relay is essential so that clients get proof simultaneously with the event. I think that's precisely the role that relays need to play because it's a huge pain for a client to have to fetch an OTS event separately when trying to filter out events that don't have a valid OTS proof.
I guess I find AI-written specs useful. They are both human-readable and can be fed to an AI to get oriented in the project without skipping too much detail. Also, the proposed modifications to the relay were made by an AI and the AI has a better grasp of the details.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqswcddwu7u68mmlfkv29gy3q2yv08vddf2wzw7lgxn3a54g83q3z8ct2h6vq
Kind-1 (TextNote)
↳ 回复 事件不存在
67abef7bb29a952cab5334afe998942841eea9da26dddfb5210b6452a4e3d4d5
"there are a bunch of people using various subkey schemes on nostr" Apart from Inkan, I'm not aware of any other functioning key rotation system for ...
"there are a bunch of people using various subkey schemes on nostr"
Apart from Inkan, I'm not aware of any other functioning key rotation system for Nostr that currently exists. If you know of any, it would be great if you could point me to them as I'd like to look at the details and, if they really do work, maybe learn from them and raise awareness of them so that others can also use them.
"but you never know because they're not visible to clients"
Inkan identities *are* currently visible to clients, namely to the Inkan client at https://www.inkan.cc. Anyone can log in with NIP-07 and view them. 😎
Kind-1 (TextNote)
↳ 回复 事件不存在
0a29605ce62cd806c80073bdaa0ef7199371ea809093f54ec68650d8200a1e89
People just need to log into https://www.inkan.cc with NIP-07 if they want to see the identity and interact with it now. They can also make their own ...
People just need to log into https://www.inkan.cc with NIP-07 if they want to see the identity and interact with it now. They can also make their own Inkan identities, and others can see them there.
In the future people can build other clients that make these identities visible. But there is no particular rush for these clients to get created. The activities of the identities are already getting recorded cryptographically, and it's just a matter of building clients that make these activities visible, which can happen retroactively.
So what I mean is, there is lots of time to get other people to participate in the system. The sooner the better, I guess, but it's not the sort of thing that dies if it's not an immediate hit right after launch.
In the meantime, holding the identity doesn't in any way interfere with my everyday use of Nostr. The thing that happens in the background is that my activities on Nostr get attributed to the identity, so I get to keep these activities as part of the identity even if my current key is leaked or lost.
Kind-1 (TextNote)
↳ 回复 inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)
I used not to do it. I was using a sort of scaffolded version of OTS for Inkan's key rotation system...
As an extenuating circumstance, I might add that I was also the guy who pointed out that NIP-03 was broken since it did not include the target event's...
As an extenuating circumstance, I might add that I was also the guy who pointed out that NIP-03 was broken since it did not include the target event's signature in the hash that got timestamped ... 😇
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcpz9mhxue69uhkummnw3ezumrpdejz7qpqas66aeae50hh7nvc52sfzq5gc7wc66j5uyaa7sd8rmf2s0zpzy0swwn5vc
Kind-1 (TextNote)
↳ 回复 事件不存在
f4caf41e24766bffd4345ce0e08983cbe28c0d1919b8ae9f18525362b2b04b99
Yes, that works. Actually clicking the "Search the relays" button brings up a much more complete-looking list of results. It should not say "Searchin...
Yes, that works. Actually clicking the "Search the relays" button brings up a much more complete-looking list of results.
It should not say "Searching for publications ..." *before* the user has clicked the "Search the relays" button because, once it says that, the user is unlikely to click that button since they think the search is already underway.
Kind-1 (TextNote)
It would be extremely desirable for Nostr relays to collect OTS proofs and splice them into the events they return. These proofs should be treated as ...
It would be extremely desirable for Nostr relays to collect OTS proofs and splice them into the events they return. These proofs should be treated as having similar cryptographic importance as signatures.
Do any of the larger relays, say wss://relay.damus.io ( nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ), provide any OTS infrastructure? If not, can they please do so?
Here is a quick reference for what an OTS-enabled relay should do:
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyghwumn8ghj7mn0wd68ytnhd9hx2tcqyzpp7m6jdpvda3pl2kcjmdfjstndxs7su04hxqt6zfdascwc0mujuzt6pwc
Kind-1 (TextNote)
↳ 回复 事件不存在
51b632be9c39f1a36a6066afbd9422e30e36fe8027dd44592f25a43304f2ab29
Hmmm .. searching for "Don Quixote" as title or "Cervantes" as author just hangs on "Searching publications ..." for maybe a minute and then I get a "...
Hmmm .. searching for "Don Quixote" as title or "Cervantes" as author just hangs on "Searching publications ..." for maybe a minute and then I get a "No publications match your filters" message (although I got search results for these earlier). Same with "Plato", nothing matches. Ah, but I do get a result for "Ambrose Bierce" and for the "Bible". So maybe it's a matter of things still getting indexed, but it doesn't yet feel like the complete Project Gutenberg is getting found in the searches.
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
Thanks. Ill see if something stands out as inspiration. Blockchains in any capacity in regular refer...
I think that blockchains will help you address the timing and sequencing issues. If you can find another way to address these, the more power to you, ...
I think that blockchains will help you address the timing and sequencing issues. If you can find another way to address these, the more power to you, but I suspect it won't be easy.
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
This is why we discuss :)
I realize that you don't want to use blockchains, but I'd like to point out again that Inkan resolves precisely these kinds of issues with timestampi...
I realize that you don't want to use blockchains, but I'd like to point out again that Inkan resolves precisely these kinds of issues with timestamping and sequencing. The solution is implemented and fully usable right now at https://www.inkan.cc. Inkan does use blockchains, but it might still be of interest as a reference.
Here is a couple of screenshots to illustrate:
https://image.nostr.build/ca9b087993604f7b7d9473a661c946ecd20015186a112021f4858efa6c1e1808.jpg
https://image.nostr.build/a10f0ac6d508ea26602348bbec60bda4659667f75adfda46d9b8354224cd08fe.jpg
Kind-1 (TextNote)
↳ 回复 事件不存在
9b38f26b08f7f270d577411ae1a984c6b70d075748e20e28026c20286e102f91
The OTS proofs are also verified client-side, so we are not ultimately trusting relays with these. The relay's role in connection with OTS is more lik...
The OTS proofs are also verified client-side, so we are not ultimately trusting relays with these. The relay's role in connection with OTS is more like housekeeping, a bit like having relays filter out events that have bad signatures.
I think Inkan is pretty well aligned with the idea that the only thing to be trusted is cryptography. The use of blockchains doesn't really seem to contradict that idea.
I guess it's debatable whether it's philosophically in line with current Nostr. However that may be, the prize to be had is a cold storage identity, which is a pretty self-sovereign thing to have.
Kind-1 (TextNote)
↳ 回复 事件不存在
6973b175768e0ed830a4b6bf6f49876bef36a8b2c42cb22ec9e447a7d0be3e73
In a way it depends on client adoption, but it's optional and additive. Inkan runs as an identity layer on top of the regular Nostr protocol, and ther...
In a way it depends on client adoption, but it's optional and additive. Inkan runs as an identity layer on top of the regular Nostr protocol, and there is no need for any existing clients to be reformed. It does not require users to adopt any infrastructure that won't work with existing clients.
For example, the key I'm using right now is part of an Inkan identity. I can use it just like any regular pubkey across Nostr. But if I want to see and interact with the identity of which it is a part, I need to go to https://www.inkan.cc .
I suppose Inkan does require some OTS infrastructure, which should probably live on relays. Here is the OTS-enabled relay it's currently using: https://gitlab.com/inkan_dev/ots-enabled-strfry . OTS actually feels like the "heaviest" part of it.
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
Yes it requires the blockchain. Nostr "simply" needs a relay and an equipped client to function curr...
The only modification to relays that I had to make was to have them verify and splice OTS proofs into the events they return. Here is a reference impl...
The only modification to relays that I had to make was to have them verify and splice OTS proofs into the events they return. Here is a reference implementation:
https://gitlab.com/inkan_dev/ots-enabled-strfry
Inkan runs without operating a node, but I guess it has to trust some nodes along the way.
It's not clear to me why people would not want to opt into using blockchains if it works.
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
Can I see your proposal? I remember looking at it once I think. Those were might thoughts exactly. W...
I would not have been able to implement Inkan without the use of blockchains. Is there anything objectionable about using them?
Kind-1 (TextNote)
↳ 回复 事件不存在
1a6b1be52f65af5db3e8c72f4356190ddd8a986791c7444a7ecf6817638f7545
I used not to do it. I was using a sort of scaffolded version of OTS for Inkan's key rotation system. Inkan now verifies all proofs. OTS is pretty es...
I used not to do it. I was using a sort of scaffolded version of OTS for Inkan's key rotation system.
Inkan now verifies all proofs. OTS is pretty essential for making Nostr keys revocable and replaceable.
Kind-1 (TextNote)
↳ 回复 事件不存在
9e6171280bb937e561f7a5ce0483328c7870ddba344b6fbde29f3df3a398debe
I think that by "an identity attests them" you mean that the identity signs something saying that events signed by the attested keys should be attri...
I think that by
"an identity attests them"
you mean that the identity signs something saying that events signed by the attested keys should be attributed to the identity, right? If so, this is similar to what Inkan calls a "delegation of signing authority."
And when you say that, when a key is lost, the identity key publishes a disavow, this is similar to what Inkan calls a "revocation of signing authority."
All of the above is, I think, fully implemented in Inkan.
Now the part I don't agree with conceptually is (6): "In the presence of a disavow, all events with that attestation are considered deleted."
That's not what should happen. Only events that are signed *after* the disavow should be no longer attributable to the identity. Events that were signed *prior to* the disavow (while the attestation / delegation was still in effect) should remain attributable to the identity.
So I think Inkan is in many ways similar to what you describe above, except for the modification to (6). I think Inkan's handling of this is conceptually more correct.
Kind-1 (TextNote)
↳ 回复 事件不存在
d4e250135ee3788cb4ef2a62ffbe61418c18271183de7ae4963c328b2c142db9
Maybe I'm not quite clear on your proposal. At first glance it sounded pretty similar to what I was talking about. How does your proposal work?
Kind-1 (TextNote)
↳ 回复 事件不存在
3fb296ac221c4eff8151504df183fb610bcff4d751be89efb7972a809570219a
"there isn't a hard timeline" That's why you need blockchains. And you need to keep track of historical delegations. I've been using this for the la...
"there isn't a hard timeline"
That's why you need blockchains. And you need to keep track of historical delegations.
I've been using this for the last 6 months, so "is not possible" is definitely not correct.
Kind-1 (TextNote)
↳ 回复 事件不存在
fad995e9d55541d61f72c63bd20274d94705ce5987cd1ed385f88b10427ef18d
But the "nobody cares" argument isn't quite as fearful as it's made out to be. I mean these methods work and they are not going to go anywhere. It's ...
But the "nobody cares" argument isn't quite as fearful as it's made out to be.
I mean these methods work and they are not going to go anywhere. It's not the sort of project that can at some point be declared dead. At best dormant.
Kind-1 (TextNote)
↳ 回复 事件不存在
6e598c2e7e83bdc9738e0974cd2e848edc92e39689fa7ca6f9f54aaedced3148
Inkan *does* allow you to keep an identity key offline. That's precisely what it does. It allows the identity key to create signing keys. And it allo...
Inkan *does* allow you to keep an identity key offline. That's precisely what it does.
It allows the identity key to create signing keys. And it allows the identity key to revoke a signing key that has gotten lost.
Inkan does *not* record any private keys on-chain or anything like that, if that's the worry.
Kind-1 (TextNote)
↳ 回复 事件不存在
7e4ff7ea524c77d1f0034fbe94057bf44a80937165596abbb6d57b06492fea61
Why not?
Kind-1 (TextNote)
↳ 回复 事件不存在
e147e102ae0509e9ed4e46aa4f5fb4069101ea3732dbf9720778a875e3f42261
Just realized that I forgot to update this thread. There's something kind of like a spec now: nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t...
Just realized that I forgot to update this thread. There's something kind of like a spec now:
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqs8z5jezmes2fxl8cm89uza098hhnkhusfc3zc0p7agvlmkpwc4ehggl2h4t
Kind-1 (TextNote)
↳ 回复 事件不存在
cca7558f59015e8bbe51f3315fb9e7eff3abf1b30b46f959b1da673bc1c361af
The idea behind an addressable event is that the pubkey signing the event gets to have no more than one "opinion" as to what the best OTS proof for th...
The idea behind an addressable event is that the pubkey signing the event gets to have no more than one "opinion" as to what the best OTS proof for the reference event is (where "best" means the one that proves the lowest block height).
As for entire OTS proofs being held inside Nostr events, this does not really conflict with the idea that proofs can also be held somewhere else in some other form. It's just one form of holding the proofs that is pretty natural in the context of Nostr, given that relays are readily available. So I think it should be made available as an option, just a piece of infrastructure that one can choose to use or not.
Kind-1 (TextNote)
↳ 回复 事件不存在
672361cf5ccb5b6e69e35e5446e92fd13f135098b284191e5b53f332aa40affc
Is there then a reason to have different event kinds for incomplete and complete timestamps? I'm just using one and the same 31045 kind for all OTS da...
Is there then a reason to have different event kinds for incomplete and complete timestamps? I'm just using one and the same 31045 kind for all OTS data. It's described in the readme here:
https://gitlab.com/inkan_dev/ots-enabled-strfry
Kind-1 (TextNote)
↳ 回复 事件不存在
3ee540d48c403404e0f8b65affdf5e6cf2da12e0c5675eb3bf279b81a4adfdbc
It uses OpenTimestamps to provide each Nostr event with an objective timestamp, recorded on Bitcoin.
Kind-1 (TextNote)
↳ 回复 ChipTuner (npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7)
Yeah I mean the UX issue of, hey guard this key with your life kind of thing. I mean I didn't "join"...
There is a way of keeping a Nostr identity in permanent cold storage. The privkey that secures the identity never has to touch an internet-connected d...
There is a way of keeping a Nostr identity in permanent cold storage. The privkey that secures the identity never has to touch an internet-connected device. See below.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqydc5vcy4z8zk350dsykgfkrq5uc2jvzmaa9k709hq88ku90gt5qk0hk0l
Kind-1 (TextNote)
↳ 回复 577de06d... (npub12a77qmwwzc9qx7gk8f9m0d5qhclq5rsudr0xu6agcqgnfdzqvnwsfrrdyd)
Yeah. I guess I’m thinking a couple steps ahead actually. We really need a master key that manages a...
In case it's relevant to this discussion, I've implemented a fully functional key rotation system for Nostr. Please see below. I'm happy to point you...
In case it's relevant to this discussion, I've implemented a fully functional key rotation system for Nostr. Please see below.
I'm happy to point you to further explanation, just trying to get the word out for now.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqydc5vcy4z8zk350dsykgfkrq5uc2jvzmaa9k709hq88ku90gt5qk0hk0l
Kind-1 (TextNote)
↳ 回复 事件不存在
f46f11ffe5d35aac380c9fc82f7ec477a1ee46ee4042a5867a40085da8d8f47a
FYI, true key rotation has been implemented in Nostr. You can use it today -- see below. If you're interested, I'm happy to help you get set up, or t...
FYI, true key rotation has been implemented in Nostr. You can use it today -- see below.
If you're interested, I'm happy to help you get set up, or to explain how you can take a look at the system without signing up yourself. I can also point you to further explanation of how it works.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqydc5vcy4z8zk350dsykgfkrq5uc2jvzmaa9k709hq88ku90gt5qk0hk0l
Kind-1 (TextNote)
↳ 回复 事件不存在
2daf4da024bbb9f187ab710b0554cda39c1cc907a89c666bef1286aab6f90e49
Huh, I actually don't know how to figure out which profile event is being displayed by a client. But I'm pretty confident that I have the right event,...
Huh, I actually don't know how to figure out which profile event is being displayed by a client. But I'm pretty confident that I have the right event, it's most likely the tags not being rendered as you say.
Kind-1 (TextNote)
↳ 回复 事件不存在
1088803a63f18da8fb2ebab0778b75da271c06acd9fa225008fa8b7a2c7e6358
That seems more likely. Inkan was built based on plain vanilla jumble from about 6 months ago, not sure what exactly it does with profiles. It's the s...
That seems more likely. Inkan was built based on plain vanilla jumble from about 6 months ago, not sure what exactly it does with profiles. It's the same at primal.net, though.
Kind-1 (TextNote)
↳ 回复 事件不存在
88389a69884bdfbd3e93f96cd50fa6e8e744e7c8839f9e514080e2eb75ff8768
I think this is the Alexandria site, no? https://www.gitcitadel.eu/ I'm seeing only https://gitcitadel.com and https://jumble.imwald.eu/ on your pro...
I think this is the Alexandria site, no?
https://www.gitcitadel.eu/
I'm seeing only https://gitcitadel.com and https://jumble.imwald.eu/ on your profile.
Oh, it turns out that I can see the link to Alexandria on your profile as displayed at imwald.eu. But when your profile is displayed at inkan.cc or primal.net, I don't see any link to Alexandria.
Kind-1 (TextNote)
↳ 回复 inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)
At least right now I'm not seeing a drop-down on the box "Search publications by title, author ..." ...
The drop-down started appearing now. Also text entry is now smooth and quick, no freezes. The search results are sort of related to the topic I entere...
The drop-down started appearing now. Also text entry is now smooth and quick, no freezes. The search results are sort of related to the topic I entered, not always quite on point.
Kind-1 (TextNote)
↳ 回复 事件不存在
2614019a4fb1c85cd4ab9c32a87687e2a0782f2e571adf2b443f4f2d7fd84fe9
At least right now I'm not seeing a drop-down on the box "Search publications by title, author ..." etc. This is a linux laptop with Chrome.
Kind-1 (TextNote)
↳ 回复 事件不存在
7d22ecca6758f3d570a5a77069d5d8dc353ebaa9723c9f4d824f1ff5e545dba4
No drop-down!
Kind-1 (TextNote)
↳ 回复 事件不存在
a108fd437313f309e27935c5ce669d64cf23c2cffeb2376a8058175dcfa19cb1
The feature that makes results appear while you type into the input field sometimes works, but sometimes it freezes and I get a "Page Unresponsive" me...
The feature that makes results appear while you type into the input field sometimes works, but sometimes it freezes and I get a "Page Unresponsive" message. Maybe that's still some of the background noise you mentioned?
I'm also not sure how to define what type of content it should search for (e.g. title, author etc.). Is that something I can add into the input field, maybe something "title: Tom Jones"?
Kind-1 (TextNote)
↳ 回复 事件不存在
0000ead5377cd1dd389c64d65024828aaf8d6e4db08c9da32ef10bc5b1218f54
Yes, feels like that.
Kind-1 (TextNote)
↳ 回复 inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)
I'm trying to use "Search Publications" to search for things like "Don Quixote", "Cervantes", "Boeth...
Wait - I started getting results! Maybe it was just relay slowness. The results are not exactly what I'd expect. For example, putting in "Aristotle" g...
Wait - I started getting results! Maybe it was just relay slowness. The results are not exactly what I'd expect. For example, putting in "Aristotle" gives me works related to Aristotle or philosophy, rather than works by Aristotle. Maybe it has something to do with the way these are indexed on Project Gutenberg.
Kind-1 (TextNote)
↳ 回复 Laeserin (npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl)
https://jumble.imwald.eu/library is online. The entire set of Project Gutenberg has been parsed into...
I'm trying to use "Search Publications" to search for things like "Don Quixote", "Cervantes", "Boethius", "Aristotle", etc. but I'm getting no result...
I'm trying to use "Search Publications" to search for things like "Don Quixote", "Cervantes", "Boethius", "Aristotle", etc. but I'm getting no results. Anything I'm doing wrong?
Kind-1 (TextNote)
↳ 回复 事件不存在
fe53292f90dd62dfbd2bfe699bcc5a8b4647cbeb43d1654d189497e6b18de41a
On the other hand, automatically dropping an incomplete OTS proof may be precisely what a user may *not* have wanted you to do. It may have been the l...
On the other hand, automatically dropping an incomplete OTS proof may be precisely what a user may *not* have wanted you to do. It may have been the last proof piece that was available. Tricky.
Kind-1 (TextNote)
↳ 回复 事件不存在
1d298959e362d772643a23b05fb9d9b123964785eb5938da64c35452da97b2b7
Similar thing, my 31045s allow "not_yet_available" in the block height tag, and then later the 31045 can get replaced with one that carries a complete...
Similar thing, my 31045s allow "not_yet_available" in the block height tag, and then later the 31045 can get replaced with one that carries a complete proof.
But if I remember correctly your 1041 automatically expire after a week or so, which makes sense.
My client basically has settings in which users specify a list of pubkeys for which they want to be stewards of OTS info, and then the client automatically tries to do the work of keeping the OTS info updated for events from those pubkeys. The default setting is simply that users are stewards for OTS info for their *own* pubkey.
Kind-1 (TextNote)
↳ 回复 事件不存在
9313fea161d90e1a84b051d1747495a025e8a2bfe0bf699c2fbdeb45bdd4357d
Yeah, I've purposefully not really been asking the question where the proofs should *ideally* get stored. Instead I've been working within this frame...
Yeah, I've purposefully not really been asking the question where the proofs should *ideally* get stored.
Instead I've been working within this framework of Nostr magic where we let data float freely around the ether and trust that it will become available where it's needed.
In the Nostr context, "relays" do come to mind as a place to store OTS proofs, and they have the advantage of currently existing.
I guess the one minimal requirement is that people can easily back up and archive OTS proofs for their *own* events, so whatever stores these proofs should have an easy-to-use "data liberation" feature.
Kind-1 (TextNote)
↳ 回复 事件不存在
624d673803ddb1667888abe79bbfc5856c57dbd0b25acb1a72401ecd377fd96b
I actually noticed that with nak --- it isn't showing proof-carrying events returned from my inkan relay. When I get a chance I'll fix up my own versi...
I actually noticed that with nak --- it isn't showing proof-carrying events returned from my inkan relay. When I get a chance I'll fix up my own version of nak to work with these.
When working through this, I noticed that there are two issues that can be thought of separately:
1. disseminating OTS proofs to relays;
2. making the proofs available to clients.
For proof dissemination, any sensible Nostr event shape will work. I think an addressable event with lots of tags for indexing (which can be skipped when not needed) works best, I've been sticking with my 31045s so far.
For making the proofs available to clients, the crucial thing is that the client needs to get the proofs synchronously with the reference event, i.e. the proofs should basically be spliced into the reference event.
So on that picture, the basic role that relays should play is to collect up available proofs and pre-verify them, select the best one (i.e. the one with the lowest block height) for each reference event, and then splice it into the reference event when it's sent to the client.
Is my current thinking.
Kind-1 (TextNote)
↳ 回复 事件不存在
c43edcb26bfe37d517f628b64ee15566d0296bc428ef1d03ac7ac7214091e3d5
What kind of results?
Kind-1 (TextNote)
↳ 回复 事件不存在
0bd7dc74add4a10e44539b2a2308f3ffd50e5eef8ea62e522fac6b6277327ba4
What qualities must the center of the ecosystem have, and what qualities must the remainder of the ecosystem have, for the center to be respected?
Kind-1 (TextNote)
↳ 回复 事件不存在
e4c48fd20ea8a01d5636115e8352d4547bbc81271b9d1aca286f0b70c31f9bad
FYI, I made an experimental modification to the strfy relay enabling it to add OTS proofs into the events it returns. These proofs are assumed to have...
FYI, I made an experimental modification to the strfy relay enabling it to add OTS proofs into the events it returns. These proofs are assumed to have been disseminated as k-31045 events. The relay verifies the proofs against BTC headers and, when queried for an event, finds the best proof held by the relay for that event and splices it into the event when sending the event to the client.
nostr:nevent1qvzqqqqqqypzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqyzpp7m6jdpvda3pl2kcjmdfjstndxs7su04hxqt6zfdascwc0muju3jyr9r
Kind-1 (TextNote)
I made an OTS-enabled version of the strfry relay. The relay collects timestamp proofs from clients, verifies these proofs against BTC headers, picks...
I made an OTS-enabled version of the strfry relay.
The relay collects timestamp proofs from clients, verifies these proofs against BTC headers, picks the best verified proof for each reference event, and splices it into the event's JSON when a client retrieves the reference event over REQ.
So as a result, when a client requests an event, the BTC timestamp (if available) arrives with it, in the same response.
https://gitlab.com/inkan_dev/ots-enabled-strfry
#nostrdev #OTS
Kind-1 (TextNote)
↳ 回复 事件不存在
8df833ae34f3fc1a56ecfa351b74007f2c9e556fd726b047e9eac5abf18cb5b4
I took a look and radicle was a bit more than I needed, so I ended up just going with gitlab. I very much appreciate the suggestion!
Kind-1 (TextNote)
I'm trying to make available a bit of code modifying a relay to do OTS-related stuff. I think Nostr has github / gitlab alternatives? Is there anythi...
I'm trying to make available a bit of code modifying a relay to do OTS-related stuff.
I think Nostr has github / gitlab alternatives? Is there anything that works well enough?
#nostrdev
Kind-1 (TextNote)
↳ 回复 事件不存在
5c10b785e85fa8ec999dddedad9129c75855249bf4f78351439da6f9af8a6a30
And I guess your are also not hosting any links to any particular content, right? And you are also not providing a service to the user by which you se...
And I guess your are also not hosting any links to any particular content, right? And you are also not providing a service to the user by which you search for the content on the user's behalf and then surface it to the user?
Kind-1 (TextNote)
↳ 回复 事件不存在
7bac8abb3dcbd70d74cdadbcf065d96f1d22668293ca0a0fd4b1b728bd28419f
Feels like they are trying to hold the phone company liable for the content of the conversations that are carried on their network. The prohibition m...
Feels like they are trying to hold the phone company liable for the content of the conversations that are carried on their network.
The prohibition mentions "linking to" ... Who or what causes the URL at the top of your site to be generated in that particular form, and that particular content to be displayed?
Kind-1 (TextNote)
↳ 回复 semisol (npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj)
Stop solving fake problems no one has
People keep telling me this. I guess I don't have confidence in their ability to know which problems they have.
Kind-1 (TextNote)