2023-02-24T17:14:01Z https://nostr.ae shafemtol https://nostr.ae/npub1mh94j7j7nwvzl7kwcg70fhxe67kdy50fccakmueq9jjf77zmc25svanahj https://void.cat/d/HUBDjrsgNcc4YH7Htv9HMc.webp https://void.cat/d/HUBDjrsgNcc4YH7Htv9HMc.webp https://nostr.ae/nevent1qqspsu4rq7gvdywnnspe90gr2gc49m4cljwywyt7e8p9j4d0wzmuk7szyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0tss09 In reply to <a href='/nevent1qqsymn4wmgcyjpp3gtg8c96wrg9ratp86qvlkr7ujj9sl5vttukl7gsa6lm95'>nevent1q…lm95</a><br/>_________________________<br/><br/>I guess that&#39;s the end of my attempts to do the exact opposite 🙃<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/note154fktkfdycyyrntcw9qv8ry29mcjmmgxqwegvl6dkduehu49kresg60hss" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">note154f…0hss</a></span> </div> Exploring a method to reduce the risk of block storms on Bitcoin testnet </blockquote> 2024-05-04T17:30:34Z https://nostr.ae/nevent1qqs20lgh4mad57xulfkmrh5awjw9drzudgrxns4mqe8nljpfcedpnhszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2je4qpje Mining block 820132 took 98 minutes. In the next 3 minutes, 3 blocks followed. <a href="https://stacker.news/items/342425">https://stacker.news/items/342425</a> 2023-12-07T15:30:04Z https://nostr.ae/nevent1qqsp567gv5gf7yxysm4uqpk9fjccfkk9mzcs2wrk32yetkunmnhjvjszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jg2w2jl In reply to <a href='/nevent1qqsv9z6axgj74x05yefc42lvme34egrmh3ge9rzt4pp355c4dff6xdqn4x3u6'>nevent1q…x3u6</a><br/>_________________________<br/><br/>Apart from the shared secret issue, one thing not addressed here is sender authentication.<br/><br/>Assuming the encryption key is `S&#39; = w * Q2`, since the sender signs with the ephemeral key `w`, unless the recipient can somehow verify that `w` belongs to the intended counterparty, the recipient has no way of authenticating the sender.<br/><br/>Anyone who correctly guesses one of the participants of the silent inbox (e.g. a relay operator would be able to trivially figure this out in many cases) can send a DM to that participant with an ephemeral private key of their own, pretending to be the other participant. 2023-06-06T00:43:53Z https://nostr.ae/nevent1qqs2hjw06zseklv8gp5ndhslq4f06sne9ltt657dd8jw9kqr7gsk8lqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jt8j7uc In reply to <a href='/nevent1qqs94lqhhzsyxjnd5ycgfmgy8mufpe24c7jrq3dn69vvelna93vph6qwupk5c'>nevent1q…pk5c</a><br/>_________________________<br/><br/>What you could do is hash the shared secret curve point `S` (preferably using a tagged hash function) into a shared private key `r`, then use the corresponding public key `R = r * G` for the `p` tag. This would not leak the actual shared secret. 2023-06-04T21:49:17Z https://nostr.ae/nevent1qqs94lqhhzsyxjnd5ycgfmgy8mufpe24c7jrq3dn69vvelna93vph6qzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jmk2qzg In reply to <a href='/nevent1qqstr6xlh5223gqcqnegez8u7sg2aqteltjsnj66r82yvltpayrnpgqp6lhea'>nevent1q…lhea</a><br/>_________________________<br/><br/>Maybe something&#39;s missing in the pictures. Note that I&#39;m not talking about decrypting *silent inbox* DMs. Here&#39;s an example of it going wrong as I understand it:<br/><br/>First, Alice (keypair p1, Q1) sends Bob (keypair p2, Q2) a *regular* NIP-04 DM (no silent inbox).<br/><br/>NIP-04 uses shared secret `S = p1 * Q2 = p2 * Q1` to encrypt the message. In NIP-04, this is given in the example code as:<br/><br/>`let sharedPoint = secp.getSharedSecret(ourPrivateKey, &#39;02&#39; + theirPublicKey)`<br/><br/>Eve also picks up this DM. She sees that Alice sent Bob a DM of a certain length at a certain point in time. She can&#39;t decrypt it yet, but stores it in her collection for later.<br/><br/>Next, they Bob decides to try using a silent inbox. This time, Bob sends a message to Alice.<br/><br/>Silent inbox uses shared secret `S = p1 * Q2 = p2 * Q1` (from the picture titled &#34;Shared Secrets&#34;).<br/><br/>Bob constructs the event using an ephemeral key `w`, encrypting to `Q1` (I presume using `w * Q1` as the NIP-04 encryption key, but this is not relevant to the attack). She puts `S` in the `p` tag of the event and signs it (from the picture titled &#34;Send and receive flow&#34;).<br/><br/>Eve also picks up this DM. She doesn&#39;t yet know its sender or recipient, but she reads the `p` tag and starts trying to decrypt the DMs she&#39;s got in her collection one by one, using the contents of the `p` tag as the shared secret.<br/><br/>One of the DMs does decrypt to a valid message, namely the first, regular, DM from Alice to Bob. Eve can now decrypt every past and future regular (not silent inbox) DM between Alice and Bob. Furthermore, while Eve can not decrypt silent inbox messages due to the use of different encryption keys here, she learns that the silent inbox in question belongs to Alice and Bob and can see the length and timing of each message going to it. 2023-06-04T21:38:41Z https://nostr.ae/nevent1qqsruu8fxth2fd2c49s4myw8jy3mt900xcgzkc2h4erlrcy7hp3uzvqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jr9d2nt In reply to <a href='/nevent1qqs86kpjzgewpf9srxg99nz3drn6ar080pukjgmp8n474qpl9ef4egs868utl'>nevent1q…8utl</a><br/>_________________________<br/><br/>NIP-92: Rendezvous Beacons (draft; <a href="https://github.com/nostr-protocol/nips/pull/333">https://github.com/nostr-protocol/nips/pull/333</a> ) enables anonymous establishment of communication between two parties, addressing the issue of receiving messages from unknown contacts.<br/><br/>A shared secret is derived using ECDH like in NIP-04, but this shared secret is only used through *tagged hashes*, with a different tag (not to be confused with nostr tags) for each purpose.<br/><br/>From the shared secret, a *rendezvous keypair* is established, where the sender knows the private key and the recipient knows the public key. This is done by tweaking the sender&#39;s key (an ephemeral key in the case of NIP-92) using a tweak value derived from the shared secret. 2023-06-04T17:32:09Z https://nostr.ae/nevent1qqs86kpjzgewpf9srxg99nz3drn6ar080pukjgmp8n474qpl9ef4egszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jdu3xmy In reply to <a href='/nevent1qqsv9z6axgj74x05yefc42lvme34egrmh3ge9rzt4pp355c4dff6xdqn4x3u6'>nevent1q…x3u6</a><br/>_________________________<br/><br/>I&#39;d be uneasy about a supposed &#34;shared secret&#34; being put in a public `p` tag.<br/><br/>Indeed, AIUI, using a silent inbox as presented here completely breaks the security of any past and future regular NIP-04 DMs between the same parties, because the same &#34;shared secret&#34; used for encryption in regular NIP-04 DMs is being used publicly in the silent inbox. An attacker doing trial and error decryption of NIP-04 DMs would be able to decrypt all regular DMs between the two, as well as deanonymize the silent inbox. 2023-06-04T17:02:31Z https://nostr.ae/nevent1qqs0urv0uyrh2kawht3lcpd9yffmvlanj7amqauglpegtc95v7wzaaczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jk24948 Seems like Binance has currently queued up at least 5 blocks worth of panic consolidation transactions in the mempool at 201 sat/vB for a total of at least 10 BTC in transaction fees. <a href="https://mempool.space/address/bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h">https://mempool.space/address/bc1qm34lsc65zpw79lxes69zkqmk6ee3ewf0j77s3h</a> 2023-05-09T04:35:29Z https://nostr.ae/nevent1qqspauxv3x0dyvte527jruwyllyyzy72w7fm76aps4l9uqttqrssdggzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j9kfh69 In reply to <a href='/nevent1qqsfh2aytsnvetqepnmh3vs7e5gs9p5wmhdxahu3f8v62gzls3ycjdqfys2q2'>nevent1q…s2q2</a><br/>_________________________<br/><br/>Twitter didn&#39;t have retweets originally, they introduced a retweet feature in 2009. The &#34;RT @twitterhandle&#34; form started as a convention among users a year or two earlier. Twitter may have implemented their APIs in a backwards-compatible way by presenting their later implementation of retweet as such to older clients, though I&#39;m pretty sure their internal representation of a retweet would be different. 2023-05-09T02:04:53Z https://nostr.ae/nevent1qqsfhzuvmhxy78ktsn09l6vumg7gu4c4dcwatzek38uhvsc6a7w623gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j7r6vjn In reply to <a href='/nevent1qqs06006jfvx6dq29jqhxy0hl8kxtw7pw0d62qwx2crdylf6prnh95gj9qnte'>nevent1q…qnte</a><br/>_________________________<br/><br/>Some of the inputs don&#39;t even cover the cost of including them! 2023-05-09T01:18:33Z https://nostr.ae/nevent1qqsqsnhvgl2q23h42apuwvyfgu0stwucm4taxyha0s5jhsmarkqy6lgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2ja3kn5l In reply to <a href='/nevent1qqs2pngqc27hlzyxaxjcxmwrx0payng3xhennlre6nvnfvpcehf2sngcd0mxc'>nevent1q…0mxc</a><br/>_________________________<br/><br/>Since nostr uses Schnorr signatures, it already supports n-of-n multisig. Though in this case I guess you&#39;re thinking of something where not all users need to sign? 2023-03-23T06:11:24Z https://nostr.ae/nevent1qqs8nlqw7hf95mfardnrexf23y6tpzylrlfylxqvuzfz3f9u49q0nqqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2ju5htl4 In reply to <a href='/nevent1qqsqa6qgssntqgp0jaa3ctf7u6p3wq58p0dxj45p9m8csq2ajmv82fc4qjtz3'>nevent1q…jtz3</a><br/>_________________________<br/><br/>Maybe not (see: Deniable authentication) 2023-03-23T02:33:17Z https://nostr.ae/nevent1qqsyfj997jxwxmh902wsvqgyue3qj44zvr9rvm69rmp5dr4y693l06gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jw4sqsx I don&#39;t like the concept of duplicating the original event and putting its json in the content. There&#39;s a lot of duplication and it&#39;s not trivial for a relay to deduplicate as the original event can be serialized in countless different ways.<br/><br/>Rather have the relay optionally send the original event alongside the (first) repost event. 2023-03-22T15:06:37Z https://nostr.ae/nevent1qqsfhjm503dj4d8j37axj2dss9j5d88lyhk5kj4jkjza89dpmllj2tqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j28d798 In reply to <a href='/nevent1qqsxv7mm26ag0sd75a3m8ndy5d3hd72mt2dhp3cj9yjgnr43cuptx7szzjv2g'>nevent1q…jv2g</a><br/>_________________________<br/><br/>Not gonna compromise my on-chain privacy for the sake of keeping some pocket money secure. Sorry not sorry. 2023-03-21T12:55:53Z https://nostr.ae/nevent1qqsfns7j6agf0e9vsnj4fsmp2vnw5a7hyermfe9w5jvuh53pcc4dkqszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jsuam9g In reply to <a href='/nevent1qqs8na6rl8z9paa620um7pavqclhevlwvdh0ts7tqke3ukevmg7ppacqa5j9v'>nevent1q…5j9v</a><br/>_________________________<br/><br/>Relays shouldn&#39;t have to be trusted.<br/><br/>It&#39;s not really true that you need a full node to verify OTS timestamps, you can use an SPV-like trust model where you just have the Bitcoin block headers and check their POW. The headers are just 80 bytes per block. 2023-03-19T19:35:32Z https://nostr.ae/nevent1qqsrxc59yu5ghz3yj2ln5h2utpyla03gr32nhn28gjptq6ynme67fdgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0pemus In reply to <a href='/nevent1qqs0cq0alfp7twyyysfkqaudyrstn4zgpt7ghh55smmhqxg4vjjnllq9q85ja'>nevent1q…85ja</a><br/>_________________________<br/><br/>NIP-03: OpenTimestamps Attestations for Events 2023-03-19T18:27:36Z https://nostr.ae/nevent1qqszgzhnqr9tsyaexl88wwq0yuts2h3k6mlxcncqup9nmwe2ww3anrczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jgjcmgm In reply to <a href='/nevent1qqs8a5t3u4yunh86ldd56n7ypr7rd72gjuheef00hefahl20nnf7fpsfg9pgg'>nevent1q…9pgg</a><br/>_________________________<br/><br/>With confidential amounts you&#39;d have better anonymity guarantees. With public denominations, each denomination effectively has its own anonymity set, which might especially affect user anonymity when different denominations are combined, and the issuer knows a per-denomination lower bound on a user&#39;s funds and upper bound on amounts being transferred between users.<br/><br/>I&#39;m still trying to wrap my head around the cryptography needed for confidential amounts. I think each token has to be bigger by some constant factor, but each user only needs to store a single token. And someone might have a single token worth 4.2 BTC and remain in the same anonymity set as someone with a balance of 69 sat.<br/><br/>UX-wise there should be no difference, but it could be made insanely private, with the issuer not even knowing whether a particular user is sending, receiving or just renewing a token. 2023-03-15T15:12:15Z https://nostr.ae/nevent1qqsrd739n3g8kwqk2f4ptgsnpgy92qjetl5ddvpkycct858yv4qzwuszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j25nr0e When the client adds `&#34;nip05valid&#34;:true` to the public profile 🎖️<br/><br/> <img src="https://nostr.build/i/nostr.build_a6962c7495538ac66b36e2aaea9944915997c2bb87d985977d4415e0d729165d.jpg"> 2023-03-15T11:21:15Z https://nostr.ae/nevent1qqs0n74tc0ddssdalhevgnxy5jcer7hmls4xysvy94dqtqygfwfv9fgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jtc8jv9 In reply to <a href='/nevent1qqsye8mm8gd9kjr5wq2ujkj65teqfu3hf04pql8njyz95ac4twusd5gxpuecm'>nevent1q…uecm</a><br/>_________________________<br/><br/>Cashu tokens are still power-of-2 denominations, right?<br/><br/>Wen confidential amounts? 2023-03-15T10:51:22Z https://nostr.ae/nevent1qqsgmt5qt2ndl924zvfznwxltdzshf0rk6qyam8g7sxnz4djds7ja0gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jyk7zme Idea: Relay that only serves events that are slightly corrupted in different ways, if your client accepts any of them, it&#39;s broken<br/><br/>#[0] 2023-03-12T20:49:56Z https://nostr.ae/nevent1qqs9ku7e5vwkk9sewnu6gyv4n24qh8vcyr7q6j6pnte69yjr2n7n5dczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j00aghc In reply to <a href='/nevent1qqs2kv8pjm0f8uzl02zsrfk3f94ehpw9hdjkq89vcpwwmpy0ex8w79qpremhxue69uhkummnw3ez6un9d3shjtnpd3jkkcn9wfnjumn9wstyqfxy'>nevent1q…qfxy</a><br/>_________________________<br/><br/>Ok, apparently this is just some weird font thing I&#39;m seeing on some clients as well as in the Flamingo extension, it is actually an &#39;x&#39;. 2023-03-12T20:37:54Z https://nostr.ae/nevent1qqs2kv8pjm0f8uzl02zsrfk3f94ehpw9hdjkq89vcpwwmpy0ex8w79qzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j3lr646 Why is there no client that lets me put a plain old &#39;x&#39; in between two digits? Like, 0x1 what? #nostr 2023-03-12T20:34:48Z https://nostr.ae/nevent1qqsfq04sgvm4z65s6yd9eua7zxvxkhcgg6xkvh7r5scyt4zqyr74ahszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j9nfjhc In reply to <a href='/nevent1qqs2dxuwjvp4tyax7m69uzzxrmmtsylazrncg90mvrp5g4frpmh98jgpp4mhxue69uhkummn9ekx7mqrd3k7q'>nevent1q…3k7q</a><br/>_________________________<br/><br/>(that is 22 in hexadecimal, or 34 in base 10, of course) 2023-03-12T20:29:57Z https://nostr.ae/nevent1qqsgr29csu8l87k04k0u0xspx6h5xny85aene9vjkysapz7t4umemcszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j8xpncl In reply to <a href='/nevent1qqsf4k76kxe9rha2zjeq986dcwqy8rrl9fsxh38nwky0pjtmwka0wsgl9m9d4'>nevent1q…m9d4</a><br/>_________________________<br/><br/>The current specs could be much better even if sticking to &#34;human language&#34;. E.g., nowhere does NIP-01 say that created_at must be an integer, yet to #[2] that is apparently obvious. All NIP-01 says is that it&#39;s a unix timestamp in seconds. Go to the Wikipedia page for Unix time, and you&#39;ll see several non-integer examples.<br/><br/>Test vectors that cover all kinds of corner cases would definitely help. 2023-03-12T19:47:42Z https://nostr.ae/nevent1qqsqz5r2ewmvnl50xcj3tmfv3ukksydsc5yjes29xy0vnyx9ydtfz9qzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jvq06z7 In reply to <a href='/nevent1qqsp332n4rn8kepz99mjr4rc8cjvddqd727escwk8k4vwsy0hnvmurg89qq7f'>nevent1q…qq7f</a><br/>_________________________<br/><br/>It&#39;s not so fun when you just want to type plaintext but random clients absolutely want to imagine it&#39;s markdown and completely butcher your note. I&#39;d be mostly fine with it if they&#39;d stick to only modifying the style and not the text itself. Cf. #[2] 2023-03-12T19:30:43Z https://nostr.ae/nevent1qqs2dxuwjvp4tyax7m69uzzxrmmtsylazrncg90mvrp5g4frpmh98jgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j963xcu In reply to <a href='/nevent1qqsvzchkutke2nc3pa3n3xyyn4welu4t67xskzj6x3cwsfvedunespcv7379n'>nevent1q…379n</a><br/>_________________________<br/><br/>JCS, although more complicated than binary, is a well-specified JSON serialization form. Luckily, for hashing, nostr only relies on a few types (list, integer, string), which are not the most complicated parts of JCS, and it seems that most client implementations happen to be compatible with JCS for these types, at least for most notes. The most complicated part here is that there are 22 characters that require specific escape sequences when encoding strings.<br/><br/>Unfortunately it appears that some devs really really really REALLY want to use a generic JSON library to generate things that look like JSON even when they know that this results in critical bugs. 2023-03-12T19:04:10Z https://nostr.ae/nevent1qqsvdk4qj8hwv6e0qcwm6vwys8qemfellc493jgp8ch2565df3sl69gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j8zy9q9 In some cases, the spec really needs to be more clear. <a href="https://github.com/nostr-protocol/nips/issues/354">https://github.com/nostr-protocol/nips/issues/354</a> #nostr<br/><br/>#[0] 2023-03-12T18:16:37Z https://nostr.ae/nevent1qqs2qspznylmn6aay6wg6xmrjn6pvus487sfegm5akxwfvgp6mc2uugzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jcey5vy In reply to <a href='/nevent1qqsf3fuzg38fmuvpqvftymvj53x8al42u93vdx4mshf5spsk94mjndc996za7'>nevent1q…6za7</a><br/>_________________________<br/><br/>If you want public broadcast that&#39;s resistant to jamming from someone with the same transmission capability as the broadcaster, I think it gets difficult. I don&#39;t have too much knowledge about radio stuff, but something I can imagine working to some extent in theory is very short bursts at changing frequencies across a wide spectrum. A jammer would have to hit the right frequencies at the right time to be efficient, but unless close to the broadcaster, their timing would differ depending on receiver location. It gets more difficult to avoid interference between multiple legitimate broadcasters at different locations, though.<br/><br/>A hardware-based solution might be receivers with multiple antennas, where the signals from the different antennas are continuously automatically tuned and combined in such a way that the signal from the identified broadcaster is amplified compared to any source of noise. I don&#39;t know the specifics, but I believe certain satellite receivers work like this, consisting of a large array of small antennas. Again, there would have to be a difference in location between the broadcaster and the jammer. 2023-03-10T07:53:17Z https://nostr.ae/nevent1qqs0sw9ztk9wxxus0tw3xfpwucg8my8y0z8khyr4epax5swzzre3s5czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0cnfjl In reply to <a href='/nevent1qqsguxajjsvjmtqxjgh3gkf0hm5luc83yxk40mdxuend00rdamm2cqqazzr5s'>nevent1q…zr5s</a><br/>_________________________<br/><br/>I see value in doing secure messaging over nostr rather than a separate network. With a network dedicated to secure messaging, you lose the effect of blending in with other types of use and thus leak more information to your network provider about your types of activity.<br/><br/>I do in fact see the public nature of relays as a potentially good thing for the core design of secure message delivery, as you&#39;re forced to minimize the trust in put in relays. The issue of trusting relays with traffic information (who sends and receives what) can be solved with separate solutions, used by users/clients that want better anonymity without affecting messaging compatibility with other users/clients.<br/><br/>I wouldn&#39;t see the issue of relays wanting to know the identity of its users specifically as a hindrance to secure messaging on nostr, but rather a problem that should be solved in and of itself. And as I mentioned in <a href="https://github.com/nostr-protocol/nips/pull/306">https://github.com/nostr-protocol/nips/pull/306</a> I think it can be solved with anonymous tokens based on blind signatures. 2023-03-09T11:41:26Z https://nostr.ae/nevent1qqszev98v8nax79wcsn4hnyryzqkvlpsdkax6psx5xcade53pkc4q4gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jraygf7 In reply to <a href='/nevent1qqspskw6mm5ny72ve6taw7xu4q0dk39zp8wv6y5qynqs6hk2xekrdrq2vu3a5'>nevent1q…u3a5</a><br/>_________________________<br/><br/>Excluding Satoshi?<br/><br/> <img src="https://nostr.build/i/nostr.build_a3951d7df0053fab5a38ee956872ca617693dc2ef50466e08e978016b49b1f8d.png"> 2023-03-09T09:44:17Z https://nostr.ae/nevent1qqs27uvgqhqgcuc2q5tyxt59t52yfhtl6v0uck7a6s7ckt8shrqum9czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j8f6yhu In reply to <a href='/nevent1qqswl9x7f3u6l5kaeta6davmrzy2p28u4duxrq3s789xf69nyz4wrlgcsrxgm'>nevent1q…rxgm</a><br/>_________________________<br/><br/>I think public broadcast standards mostly rely on most people being unwilling to go to the trouble of setting up high-power transmission equipment in order to interfere with public broadcasts in a way that&#39;s probably not too hard for some government agency to track down. 2023-03-09T09:10:41Z https://nostr.ae/nevent1qqszl8u48nwr4js8hsp7y90kms22htt5ljuuuc7ssq8lnr6cv7ctkzqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jnfrefp NIP-92: Rendezvous Beacons (draft) <a href="https://github.com/nostr-protocol/nips/pull/333">https://github.com/nostr-protocol/nips/pull/333</a> #nostr 2023-03-08T06:26:34Z https://nostr.ae/nevent1qqstdku7t4te7vg3s20l7a3e99q8ef7x32akcept0fjw02zane3ejdqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jq9w4ka In reply to <a href='/nevent1qqsgk24s03snw9vtz9zlcdhawf2xh4mm7kj4ssawamrw9s63prn65zqy4rvew'>nevent1q…rvew</a><br/>_________________________<br/><br/>See also my NIP PR: #[2]<br/><br/>I proposed using a single-letter tag for the hash to cover a particular use case. Unfortunately the PR discussion derailed a bit IMO. 2023-03-07T05:51:55Z https://nostr.ae/nevent1qqsywa8ataslgawl999v6a9ggmsjue0swmttd8x2npmpvulyrs52teczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j27c6ee Successfully mined another preventive #testnet block at height 2423230. Next block came 32 min later, would have been 12 min after a &#34;normal&#34; block 2423230. If so, no block storm would occur even without a preventive block. But would have been a close call. #[0] 2023-03-07T04:00:44Z https://nostr.ae/nevent1qqsqupz7d8j97jf2vxyruzt3t3xwz4shfv9kf7gh42905347j26ss6gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jqcxyhr In reply to <a href='/nevent1qqs934cwwxrpmec58t5cavt6g7fd2la20j5ua26ky6lue70u4sv5xecrtlrhw'>nevent1q…lrhw</a><br/>_________________________<br/><br/>I proposed a NIP for just that kind of tag: #[2] 2023-03-07T00:23:46Z https://nostr.ae/nevent1qqsfy2ndvxj8u3jetdtkl6udfnr6nxr3ee73xgfz6rsed9xetau7kwczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jj03qrj In reply to <a href='/nevent1qqstcf3ktzfqzdqruv0j5920kmszx6r9zfwe7suqle3tyr2m2wm6qtqlnmc6r'>nevent1q…mc6r</a><br/>_________________________<br/><br/>The Flamingo signing extension shows you the follow list before you sign it. Unfortunately it&#39;s just a list of npubs, but at least you&#39;d notice if the list is considerably shorter than expected. 2023-03-06T06:54:20Z https://nostr.ae/nevent1qqsgh6ea8k9ljldj5ypfss0fnahtmj0myp5hpmltzytjygvem368npszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2js89848 In reply to <a href='/nevent1qqsf3w2j0p8vajj9n0r88etteprvj70jzhn97l47zr600wz5vvtzp4qffl3d6'>nevent1q…l3d6</a><br/>_________________________<br/><br/>I was thinking about the quality impact on a global feed. In any case, a more refined filter on the client side is also an option. 2023-03-06T06:45:13Z https://nostr.ae/nevent1qqs9qxjl8xuksqcq9wjc40aejmrzrwk034fd0kaptaw57wv8uprz76czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j9gsqz5 In reply to <a href='/nevent1qqs0rjs50t0zlgel5pqqd5gvgvxhvngd4ys3zq5wkna53cmxrtjlvjqfqc0sh'>nevent1q…c0sh</a><br/>_________________________<br/><br/>Was just thinking about this.<br/><br/>#[2]<br/><br/>Some users follow a _lot_ of others, though, and might have a higher risk of following spam/impersonation accounts. As a refinement, maybe you could score each follow by dividing by the paid user&#39;s total follow count, and only include users with a follow score above a certain level, e.g. 1/200. And/or disregard the follows of users who follow identified spammers/impersonators. 2023-03-06T05:20:08Z https://nostr.ae/nevent1qqsgecyxpgv365wyz4slwn3gzcz78a7ra7uu3zans8q9u6cerqymvggzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j86zc6x In reply to <a href='/nevent1qqsr8hc08utvyp4we78xp7ewrap4p5kss4r3qlnmjnuauhk0nsvdp9qyycgft'>nevent1q…cgft</a><br/>_________________________<br/><br/>I had to look up the claim about the difference in difficulty scale, because that was new to me, and I&#39;ve been using the same code for testnet bits/target/difficulty calculations as those for mainnet.<br/><br/>The statement was added here, in January 2011: <a href="https://en.bitcoin.it/w/index.php?title=Testnet&amp;diff=2244&amp;oldid=2212">https://en.bitcoin.it/w/index.php?title=Testnet&amp;diff=2244&amp;oldid=2212</a><br/><br/>Testnet3 genesis was in February 2011: <a href="https://mempool.space/testnet/block/0">https://mempool.space/testnet/block/0</a><br/><br/>Within the current difficulty period on testnet3, I can find no regular-difficulty block that has a hash outside the supposed target using mainnet bits/target/difficulty calculations. The difficulty scale must have been different on testnet versions 1 and 2, but changed to the mainnet scale in version 3. 2023-03-06T04:42:50Z https://nostr.ae/nevent1qqstwasxu0vt8mchaf42xz9a6f0w06yhglljg8rlfet2mj5v6avt4yczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jh45s9x In reply to <a href='/nevent1qqsqjzaxea84llzg8cwywjeeh978thnpy2z2n296ct6hruhza862f8gyj4gqt'>nevent1q…4gqt</a><br/>_________________________<br/><br/>It&#39;s not a block storm, just someone modifying the timestamps of their blocks into the future to get to mine at difficulty 1. mempool.space shows future-timestamp blocks as mined &#34;just now&#34;.<br/><br/>They&#39;re limited by the 2-hour rule, no big deal. But we&#39;re approaching a difficulty adjustment, and if they happen to be doing this on the last block in this difficulty period, they will trigger a block storm.<br/><br/>Better fire up my storm-blocking miner again... #[4] 2023-03-06T03:40:59Z https://nostr.ae/nevent1qqsylpvpkvzys4wxwzqx9sq573mqeqz448vp4hjpmp578ma2aqva97czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j09plav In reply to <a href='/nevent1qqsdxtc50lnuhngxd6g4paex229lssq3vhkp4xw7hkhlt0h206hfswcpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet539wkd8'>nevent1q…wkd8</a><br/>_________________________<br/><br/>Ok, by &#39;clients&#39; I mean snort.social, and by &#39;removing&#39; I mean default disabled in settings. I&#39;d be fine with DM functionality treated similarly. 2023-03-06T01:41:37Z https://nostr.ae/nevent1qqsdxtc50lnuhngxd6g4paex229lssq3vhkp4xw7hkhlt0h206hfswczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0aw836 I see clients are removing likes/reactions. How about removing something actually harmful like NIP-04 DMs? That would be something. 2023-03-06T01:18:33Z https://nostr.ae/nevent1qqspdkrajdkv0mkphhluaz296eskav0l797t8has4jx5ewcj0elym6qzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j5fruc6 Some of the relays I had in my profile are unusable over Tor. I removed them, hopefully my posts are still reaching most of the network. 2023-03-06T01:16:12Z https://nostr.ae/nevent1qqs9k8fath7slxzkmxgt7c8hg24367sz2569exyg5as3x7l7c6g55ggzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jk2sq8h This is why we can&#39;t have nice things<br/><br/> <img src="https://nostr.build/i/nostr.build_3816dcfc090da03ddc43cd29cff1b2db31a65307e6035711567226093081c43c.png"> 2023-03-03T03:56:53Z https://nostr.ae/nevent1qqs2lvspsm8dga903q7n0smd6upz65m4cg5zejw6mqysqtmtyvs9paszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j3s2ysk In reply to <a href='/nevent1qqsp9m8es6xqj2rmr5z9crqamctn0xqvj94jxgv6lq675tu8tmxxwkspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqnecq2'>nevent1q…ecq2</a><br/>_________________________<br/><br/>I have created an issue on NIP-08&#39;s failure to specify correct behavior here: <a href="https://github.com/nostr-protocol/nips/issues/319">https://github.com/nostr-protocol/nips/issues/319</a> #nostr 2023-03-02T23:18:11Z https://nostr.ae/nevent1qqsp9m8es6xqj2rmr5z9crqamctn0xqvj94jxgv6lq675tu8tmxxwkszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2juak3lh In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqjzsq4s'>nevent1q…sq4s</a><br/>_________________________<br/><br/>Results on generating notes:<br/>- astral.ninja: 💩 fail #[2]<br/>- coracle.social: 💩 fail #[3]<br/>- iris.to: 💩 fail #[4]<br/>- snort.social: 💩 fail #[5]<br/><br/>They *all* fail to avoid creating false-positive NIP-08 mentions. This is a failure of NIP-08: It does not specify how to actually create a message with the plaintext `#[x]` (where x is a number) in it if the event has tags. #nostr 2023-03-02T20:51:54Z https://nostr.ae/nevent1qqsxk7zpr54khjjr8elufahz2dz574wgfh8t0cv5tkvfvu72ffhcdgczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jr4y4yp In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqjzsq4s'>nevent1q…sq4s</a><br/>_________________________<br/><br/>Testing reply from snort.social: #[0] #[1] #[9] 2023-03-02T20:40:30Z https://nostr.ae/nevent1qqsgx2vdwzlkggyy0zuyrt32y2ahzqu5l07epxfmp7pfmyw2rnfaw7gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jg6thdj In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqjzsq4s'>nevent1q…sq4s</a><br/>_________________________<br/><br/>Testing reply from iris.to: #[0] #[1] #[9] 2023-03-02T20:37:59Z https://nostr.ae/nevent1qqs0e5ekqsdudk92w4r3ycf5ls5ykpks0h3jkk626m64jf5vrcszyfczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jgxrqsv In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet57frclv'>nevent1q…rclv</a><br/>_________________________<br/><br/>Testing reply from coracle.social: #[0] #[1] #[9] 2023-03-02T20:37:01Z https://nostr.ae/nevent1qqsgrcrjljz4qnmrt8w26uqnvtx3vj985tx0wmrdxartuzp6sthwjmqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jw8kyzz In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqpp4mhxue69uhkummn9ekx7mqphmxsj'>nevent1q…mxsj</a><br/>_________________________<br/><br/>Testing reply from astral.ninja: #[0] #[1] #[9] 2023-03-02T20:33:51Z https://nostr.ae/nevent1qqszc904h85t2mpnwzc9cyt4la5t065445pnh30rygzaj6zh96hev0gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j6jw78p In reply to <a href='/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqjzsq4s'>nevent1q…sq4s</a><br/>_________________________<br/><br/>Results on viewing:<br/>- astral.ninja: 🤙 pass<br/>- coracle.social: 🤙 pass<br/>- iris.to: 💩 fail, removes part of the text, shows as `0 9`<br/>- snort.social: 💩 fail, highlights text in bold red and appends question marks 2023-03-02T20:29:32Z https://nostr.ae/nevent1qqsp22tmvgs309lz7lyazxuyxgp6k0zrv2cycq6z9uaf4va7rmkgdzgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jlnywx5 In reply to <a href='/nevent1qqs87xfwrdlvfzmm7ecjwz70v2ced46l090xw3nm33e8kwh0zl9xweqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdu7kmpff'>nevent1q…mpff</a><br/>_________________________<br/><br/>astral.ninja to the rescue, coracle.social now works after I re-added the relays without trailing slash 2023-03-02T20:18:19Z https://nostr.ae/nevent1qqs87xfwrdlvfzmm7ecjwz70v2ced46l090xw3nm33e8kwh0zl9xweqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jt5w2n0 coracle.social seems to fail on relay URLs with a trailing slash. My profile there is outdated and shows none of my posts, presumably because it refuses to connect to the relays declared in my profile. And snort.social adds a trailing slash to the URL of every relay I add to my profile 💩 2023-03-02T19:19:31Z https://nostr.ae/nevent1qqsfh84eh0zta55rpu5qm2344jd3ylkddda9x4dnrxe6vv9xmatculqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jkvy025 Testing how clients deal with undefined parts of NIP-08: #[0] #[9] 2023-03-02T18:31:14Z https://nostr.ae/nevent1qqsrfk30gmvgvkuqhc62ntyhc7qqg2ex4v37xyhg09hgyce5jdzj50szyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jc6crj3 In reply to <a href='/nevent1qqswmesdfkd9uugfu4nqn6u54cr3r9k09vd37ae9c36yztqhdhneq0sfz3776'>nevent1q…3776</a><br/>_________________________<br/><br/>Clients could improve their cut-off functionality by having some extra tolerance. If length is greater than cut-off + tolerance, then it&#39;s shortened to the cut-off length. 2023-03-02T17:31:29Z https://nostr.ae/nevent1qqsx7wn22rqkge6hlfuye2hz05lj4rx56vl4pjlxf6wg5gqnuf2cgeczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jqmwwqq Trying to understand the cryptography behind WabiSabi for like the fifth time 2023-03-02T03:08:13Z https://nostr.ae/nevent1qqsw36gvgnf94kzhzqfpaunvavu50ylhmsrqnxqj2grs0l2l2jhx3lczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j8cj48h In reply to <a href='/nevent1qqsdy9z8s5phs8695gfphz9entr37h9g577j8yas2jsr7kgppp4f2hswqzznf'>nevent1q…zznf</a><br/>_________________________<br/><br/>This broke my internet connection 2023-03-01T03:30:09Z https://nostr.ae/nevent1qqs0p6ju6vf4w6nqmeelhxxnw9ylns92s28hyap4jukwlvnxnzanckczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jcy8de6 In reply to <a href='/nevent1qqsqkfjzlcx0fg7ymte3t0ka2wpzve68hykep8rq7aflj9svhg7jragupuzv9'>nevent1q…uzv9</a><br/>_________________________<br/><br/>Assuming the best option initially would be not trying to host git repos themselves on nostr, but repository metadata (description, repository URL, branch hashes) and an issue tracking system to begin with. 2023-03-01T02:56:19Z https://nostr.ae/nevent1qqsxs6ssgkf55j2lwgh0pmedxy7r48v3zqy8qlua5qg54gw037n2jsgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j9lzppn In reply to <a href='/nevent1qqs06z82m6mn29hxlekhetzhrytm9nys0st902skk5q0mc88k04ewtg2elkll'>nevent1q…lkll</a><br/>_________________________<br/><br/>Or rather, I&#39;d like the whole event shown in human-readable format, falling back to the json values for things it doesn&#39;t know how to parse. 2023-03-01T02:45:48Z https://nostr.ae/nevent1qqs06z82m6mn29hxlekhetzhrytm9nys0st902skk5q0mc88k04ewtgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jx7yhac In reply to <a href='/nevent1qqszghj775vr7l04w3nhk9l6vzcndzpakcxlk944kaeh82w627ge2lc9sxeaz'>nevent1q…xeaz</a><br/>_________________________<br/><br/>Using Flamingo right now. Its signing dialog is very limited, it only shows the `content` part of the event, with newlines replaced with spaces for some reason. For events without content it just shows a blank dialog. I would want it to show the whole event to be signed in json format. Otherwise it seems to be working well. 2023-03-01T02:39:05Z https://nostr.ae/nevent1qqsgjsfraxcr0j2qnexllfwgpqmqfvnlfrvqzcmus057sm90k0qlvrqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j44yz4v In reply to <a href='/nevent1qqs2v3rdw0pktwa0a98uljre85gxv2qwzsx2q7ktu53qehkw2k9dndqsxlnf3'>nevent1q…lnf3</a><br/>_________________________<br/><br/>Any reasonably sane email client will not load remote content by default. Nostr DM clients need to behave similarly. Some email clients might load external content through a dedicated proxy. That is also problematic as it lets the sender know exactly when the email is opened. 2023-02-28T17:28:56Z https://nostr.ae/nevent1qqsfx3cqg3uhazfn9vye4d0fas6mvsl8snw6kppj59kle0gcr57vdnszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jqezjup In reply to <a href='/nevent1qqszwhgf5yp4f27pgm35dakdc2uhz4w0vze6wm6447h4r9whyw6gu9cx643wg'>nevent1q…43wg</a><br/>_________________________<br/><br/>Results: iris.to and coracle.social display the image, snort.social fails (doesn&#39;t strip off the fragment before sending the URL to its image proxy, guessing the proxy itself doesn&#39;t remove it either). 2023-02-28T16:56:12Z https://nostr.ae/nevent1qqszwhgf5yp4f27pgm35dakdc2uhz4w0vze6wm6447h4r9whyw6gu9czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jw6dz7f In reply to <a href='/nevent1qqs0mwcwvswxwt2xh8r85pg0fjpmc45tafljm4jr0utygmjzyagerhcq4f4jc'>nevent1q…f4jc</a><br/>_________________________<br/><br/>Testing .png URL with fragment<br/> <img src="https://i.stack.imgur.com/Iil7a.png#1"> 2023-02-28T16:45:58Z https://nostr.ae/nevent1qqsqfc4vjr7jk0v4exwchnc8mq2xu3mxjg084chw068j7afjjxgvkrszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j3hgzsd In reply to <a href='/nevent1qqsfytla0v6ss4zusk3zyvc6p3tcxda63uagj43ju78k3y4mmh5uhlqeld6z2'>nevent1q…d6z2</a><br/>_________________________<br/><br/>Regarding referrer, browsers send the `Origin` header on WebSocket connections, revealing the domain name of the client app. Other resources can be loaded without referrer/origin through `Referrer-Policy`. This does not affect the WebSocket `Origin` header.<br/><br/>I did some testing and found a trick: Put the WebSocket client in a sandboxed iframe.<br/><br/>Demo here: <a href="https://sha.femtol.net/dev-tests/ws-origin/iframe-sandbox.html">https://sha.femtol.net/dev-tests/ws-origin/iframe-sandbox.html</a> (use the browser&#39;s network console).<br/><br/>Tested and works on both Firefox and Chromium. It might not work on older Firefox browsers, though. 2023-02-28T16:10:48Z https://nostr.ae/nevent1qqsq4fuah3dvqcz5y72avq2q4tw6p623tl7ajjw20t8g8vja3gpaw3gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jl46553 In reply to <a href='/nevent1qqs0mwcwvswxwt2xh8r85pg0fjpmc45tafljm4jr0utygmjzyagerhcq4f4jc'>nevent1q…f4jc</a><br/>_________________________<br/><br/>Test without fragment<br/> <img src="https://void.cat/d/HUBDjrsgNcc4YH7Htv9HMc.webp"> 2023-02-28T13:03:23Z https://nostr.ae/nevent1qqs0mwcwvswxwt2xh8r85pg0fjpmc45tafljm4jr0utygmjzyagerhczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jekrflj Test<br/> <img src="https://void.cat/d/HUBDjrsgNcc4YH7Htv9HMc.webp#1"> 2023-02-28T12:09:40Z https://nostr.ae/nevent1qqswzp46fc9qemetkdwmyqy8nd6lw93tn8h9sm8fc7qraj4y03y86ggzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jjsezrp NIP-93: Secret Events (draft)<br/><a href="https://github.com/nostr-protocol/nips/pull/306">https://github.com/nostr-protocol/nips/pull/306</a><br/><br/>Nothing too exciting in this particular NIP, just intended a small building block. #nostr 2023-02-27T22:56:23Z https://nostr.ae/nevent1qqs25evg4gx9dju33d68f5hlgp2jx7fr8rjg7dcf38vxuwdeaq2v7cqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j5npj7y In reply to <a href='/nevent1qqsprhjnn9eaej7nuxq4upkd3rdwr9qqagy2np0075whpdq3sqhzv3c873cx7'>nevent1q…3cx7</a><br/>_________________________<br/><br/>The proxy could pass the challenge and response to and from the client through some protocol extension (client/user would still have to trust proxy not to abuse the authenticated session).<br/><br/>I&#39;d rather like to see an anonymous solution, though, like some kind of usage tokens based on blind signatures. 2023-02-27T12:06:08Z https://nostr.ae/nevent1qqsq657eyzd3yd0us8yuaruy9qrelsxh2fzwcx5lehlamq3pqst77lqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jjalsvp In reply to <a href='/nevent1qqs2h7hu8jhz4l85lucd4fayn2ughvf2gsvtp0j9c66mqfkq0xad6accxyf62'>nevent1q…yf62</a><br/>_________________________<br/><br/>The NIPs don&#39;t seem to be fully consistent in its use:<br/><br/>| kind | description | NIP | content | note |<br/>|-------|-----------------|-----|---------|------|<br/>| 0 | Metadata | 1 | Yes | - |<br/>| 1 | Text Note | 1 | Yes | Yes |<br/>| 2 | Recommend Relay | 1 | Yes | - |<br/>| 3 | Contacts | 2 | ignored | - |<br/>| 4 | Encrypted DMs | 4 | Yes | - |<br/>| 5 | Event Deletion | 9 | MAY | - |<br/>| 7 | Reaction | 25 | Yes | Yes |<br/>| 8 | Badge Award | 58 | - | - |<br/>| 40-42 | Chat | 28 | Yes | - |<br/>| 43-44 | Chat | 28 | may | - |<br/>| 1984 | Reporting | 56 | MAY | Yes |<br/>| 9734 | Zap Request | 57 | MAY | Yes |<br/>| 9735 | Zap | 57 | No | Yes |<br/>| 10002 | Relay List Meta | 65 | No | - |<br/>| 22242 | Client Auth | 42 | - | - |<br/>| 24133 | Nostr Connect | 46 | Yes | - |<br/>| 30008 | Profile Badges | 58 | - | - |<br/>| 30009 | Badge Def | 58 | - | - |<br/>| 30023 | Long-form | 23 | Yes | - | 2023-02-26T21:05:14Z https://nostr.ae/nevent1qqsf6vu7gulhrtw35yqupadp05w4x94vcpjmxvcns5s3hdu5lrzxjvqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jk7j5j3 Ideas on anonymous delivery of secret events<br/><a href="https://github.com/shafemtol/nostr-secure-messaging/blob/main/anonymous-delivery.md">https://github.com/shafemtol/nostr-secure-messaging/blob/main/anonymous-delivery.md</a> #nostr 2023-02-26T16:50:21Z https://nostr.ae/nevent1qqsr42cmgf79ckjkdgayv3ve92aehjjqf0qy3w46rsf25u80sfg3kegzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0za8rk In reply to <a href='/nevent1qqsx58cup8gtnwxd78m2wcq3h0a742uc8u4uxlahjqkjr9tjmw4lz2s0z3jv5'>nevent1q…3jv5</a><br/>_________________________<br/><br/>Working on it 🤙 2023-02-26T15:32:22Z https://nostr.ae/nevent1qqsfkryn6rsdjkg9v8evgsvk5p2lmtjutjyd93q67drvmjnu848lwfczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jvpt87k Having scanned through all of the NIPs, I&#39;m still not sure exactly what is meant by a &#34;note&#34;. All notes are events, but I&#39;m guessing not all events are to be called notes? #nostr 2023-02-25T23:26:00Z https://nostr.ae/nevent1qqsz47v0drmemv8vsf5p3pfwruf8h6r8dst7nyrhjehhlzyr937se3czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0ha9hr In reply to <a href='/nevent1qqsp9ad9wj2ck7ukq0mkegqhycvs0t9quzmsxjhqksuhw7lr2snl9agfcykkz'>nevent1q…ykkz</a><br/>_________________________<br/><br/>&gt; Including a recent block hash is a proof of absence, meaning that the note cannot have been created before that block was mined. It proofs the lower bound, that the message is older than that block. The attacker can include a very old blockhash years after it was mined.<br/><br/>I think you&#39;re missing the idea here. The point is exactly to prove that a note&#39;s id was created after a certain block was mined. But the block is not chosen by the attacker. It must match a set of recent blocks by the filtering client. The client is only interested in recent notes, not historical ones. By using a filter as provided in the example, the client is guaranteed (by the promised behavior of any relay that follows NIP-01 + NIP-12) that any notes returned were created after the list of block hashes chosen by the client.<br/><br/>Proof of freshness does not solve the case where an attacker concentrates PoW on creating notes targeting a very old block hash. For that case, you can combine this NIP with an opentimestamps proof as you mentioned.<br/><br/><a href="https://github.com/nostr-protocol/nips/pull/296#issuecomment-1443568647">https://github.com/nostr-protocol/nips/pull/296#issuecomment-1443568647</a> 2023-02-24T11:44:59Z https://nostr.ae/nevent1qqsxmspltry8gaqm679v9unu5f3sgj34wvzjmrr05c25veq7csu6qhczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j9kykwl NIP: Proof of Freshness<br/><a href="https://github.com/nostr-protocol/nips/pull/296">https://github.com/nostr-protocol/nips/pull/296</a> #nostr 2023-02-24T06:21:36Z https://nostr.ae/nevent1qqsrsmeglpxz2tvc5l6757ujdlyf8adjrr23p4s0yjvnerzx9kp8afszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jtvl4af Going down the rabbit hole of secure, private DMs. I think a good design will require multiple smaller, composable NIPs. #nostr 2023-02-23T21:39:28Z https://nostr.ae/nevent1qqsqw7w28emqaj54rr8acw72zt644d4ywlt8s24rrwm62x40es9x3sgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jeeklvc A preventive block was successfully mined at height 2421214. The two blocks that followed had an interval of 31 minutes between them.<br/><br/>If those blocks had been mined at the same rate without the preventive block, there would have been another block storm! #bitcoin #testnet #[0] 2023-02-23T20:25:57Z https://nostr.ae/nevent1qqs83zd6j9d2vzl0j6k7laack4mh0aqmkff4v33ka66s4cncam694dqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jdaa7zh In reply to <a href='/nevent1qqsvqu5e2c0uumn807cj38e9ep2e46nshrlngvlarps4lheg33exk8svg2zte'>nevent1q…2zte</a><br/>_________________________<br/><br/>These are the concerns and edge cases I can think of regarding a soft fork to set a maximum timestamp limit on block 2015:<br/><br/>## Can a maximum timestamp requirement of prev timestamp + 20 min conflict with the minimum timestamp requirement of prev mediantime + 1 sec, making it impossible to mine a new block on top of the latest one?<br/><br/>No, because prev mediantime can not be greater than prev timestamp. The mediantime of a block is the median of the timestamps of that block and the 10 before it. Because that block itself must have a timestamp greater than the median of the 11 blocks before it, it must have a timestamp greater than that of at least 6 of those blocks. It follows that it must have a timestamp greater than at least 5 of the 10 blocks before it. Thus, its timestamp can only be set so low as to also define the block&#39;s own mediantime.<br/><br/>## Could non-upgraded miners run off in a chain split?<br/><br/> Yes, if they start a block storm. But they would reorg and join the upgraded chain as soon as the upgraded chain finds block 2015. This is because the non-upgraded chain would all consist of difficulty-1 blocks for the next 2017 blocks (and then increasing by no more than 4x for every difficulty period after that). That is, the blocks do not make a heavy chain. Even if the non-upgraded chain had more hashing power in theory, they would be limited by the rate of new blocks having to be sent across the network.<br/><br/>## Could the chain stop at block 2014 for hours because all ASIC miners left?<br/><br/>This is a possibility. Is it worse than a block storm, though? Not everyone has their own ASIC miner, but renting some ASIC time shouldn&#39;t be too hard or expensive (should cost no more than about 40 cents per expected block at the current difficulty and BTC price). 2023-02-22T20:41:19Z https://nostr.ae/nevent1qqsv2gtmfcj92hp2q6dn5tcdy60x2rss4mxmyjd7x6pzdyxh0mse47szyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j0mupmz In reply to <a href='/nevent1qqs83r4wxh8yq4neu8dswpm404d355hac98zgmvqkugxs3vyvyn3uwsyz286e'>nevent1q…286e</a><br/>_________________________<br/><br/>So, kind 6 was NIP-18, but it got removed because it wasn&#39;t being implemented as specified: <a href="https://github.com/nostr-protocol/nips/issues/173">https://github.com/nostr-protocol/nips/issues/173</a><br/><br/>Quoting works by regular text notes with mentions of other notes embedded in the text body. I would have assumed reposts were the same but with no other text in the body. 2023-02-22T18:30:06Z https://nostr.ae/nevent1qqs83r4wxh8yq4neu8dswpm404d355hac98zgmvqkugxs3vyvyn3uwszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jt8z78t In reply to <a href='/nevent1qqsxqqu023grl6ez78d8h52m08zm0gpu9ygxtk0ymhlhpfd09rz6u6gxv7r5q'>nevent1q…7r5q</a><br/>_________________________<br/><br/>Apparently a boost/repost is kind 6, which I can&#39;t find mention of in the NIPs? And snort includes the reposted event in full as stringified JSON in the content field, while iris leaves the content field blank? 2023-02-22T18:05:59Z https://nostr.ae/nevent1qqs06xypa8ge7wt77v4a4jhuncgh8stpcg4aurvkgz9h3nszwmdruxgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jagy8x8 In reply to <a href='/nevent1qqs92ns4ewe6n49py42zn34js5ezx4f7xmm5cw20sy6vl9cjp749cgsmj7a3e'>nevent1q…7a3e</a><br/>_________________________<br/><br/>ChatGPT seems to be excellent at breaking down code and explaining exactly what each part does. I&#39;m curious: would it be able to explain why this command works on a pruned node? 2023-02-22T17:47:17Z https://nostr.ae/nevent1qqsdyrmrfjm6q5nc6p872fsw32mkc4txwxaqp798fe9q9wfreky4e0gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jgam5c7 In reply to <a href='/nevent1qqszpxdwrer60vf93pqxu2lhnw43v9e4zlstfey43nn46xahaj9dqcgyddxxq'>nevent1q…dxxq</a><br/>_________________________<br/><br/>Looks like the address it gave in the example there is completely made up, getting &#34;invalid address&#34;. Did I transcribe it correctly? 1F5MsWgRyxA6lekVMrhKmUsPJdQaYjP9sm 2023-02-22T17:30:40Z https://nostr.ae/nevent1qqsqnxhu0c08gj9pntfrv364qvahx2qavj2w79rkatcumzgzun4djpczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jymvane In reply to <a href='/nevent1qqs225m9mykjvzzpe4u8zsxr3j9zaufda5rq8v5x0axmx7vm72jmpucsyeeau'>nevent1q…eeau</a><br/>_________________________<br/><br/>The method I&#39;m exploring is to try to force the mining of the last block in a difficulty adjustment to happen at full difficulty for as long as possible, to maximize the chance that a full-difficulty block is found before difficulty drops to 1.<br/><br/>Last block storm was triggered on Oct 31, it might take a few months to see if this method is effective.<br/><br/>The triggering block, at height 2378879, seems to have been _deliberately_ set 20 minutes ahead of actual time. Its timestamp is exactly 20 min 1 sec after the previous block, and 20 min 3 sec _after_ the _following_ block.<br/><br/>Deliberate attacks might still succeed in triggering block storms. 2023-02-22T17:18:42Z https://nostr.ae/nevent1qqs068n4h4l3a8uq0yvnt4hdma7ph54sdvwu4u7js3vx0e0zl0ka4gszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jg0snn2 In reply to <a href='/nevent1qqswyhdxd4am9ts08c3ae0ktya2uvmk42j8srdh9304av44uwntmqmc0sn37u'>nevent1q…n37u</a><br/>_________________________<br/><br/>By the way, #[3] , you say that a fix would require a hard fork. Is that a common belief?<br/><br/>A simple soft fork* would be to require that the last block in a difficulty adjustment period has a timestamp no greater than 20 minutes after the previous block.<br/><br/>__<br/>* A soft fork in the sense that it only restricts consensus rules. Miners that don&#39;t implement the change might get their block invalidated by this. But such a block would be a difficulty-1 block, so no big deal. 2023-02-22T16:33:14Z https://nostr.ae/nevent1qqswyhdxd4am9ts08c3ae0ktya2uvmk42j8srdh9304av44uwntmqmczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jj69mv9 In reply to <a href='/nevent1qqs225m9mykjvzzpe4u8zsxr3j9zaufda5rq8v5x0axmx7vm72jmpucsyeeau'>nevent1q…eeau</a><br/>_________________________<br/><br/>Background on Bitcoin testnet block storms by #[2]: <a href="https://blog.lopp.net/the-block-storms-of-bitcoins-testnet/">https://blog.lopp.net/the-block-storms-of-bitcoins-testnet/</a> 2023-02-22T16:18:47Z https://nostr.ae/nevent1qqs225m9mykjvzzpe4u8zsxr3j9zaufda5rq8v5x0axmx7vm72jmpuczyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jpc25rv Exploring a method to reduce the risk of block storms on Bitcoin testnet 2023-02-22T16:12:36Z https://nostr.ae/nevent1qqszyy7lezak3rkt6d7ntrahhdqs708mhtls759vmd2aeyshtz5c29gzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j7vasy4 There you have it. #777777<br/><br/>2023-02-22T09:58:27Z UpdateTip: new best=00000000000000000005d35085cbcb510c14917f928aaa45facb0c0d24d471ce height=777777 version=0x2feaa000 log2_work=94.018808 tx=807684568 date=&#39;2023-02-22T09:58:09Z&#39; progress=1.000000 cache=139.8MiB(1043516txo) 2023-02-22T10:04:25Z https://nostr.ae/nevent1qqsyua7makxk8w4v5ttfxhxp7a69h64u2l7ka5r9jcy3uc2a5emrm2szyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jf0n49j In reply to <a href='/nevent1qqs8dd6cj3p6uru8p7hc4tvvhqqs4xyezr4e0czungmqz86zhqcrf7s7pmsxu'>nevent1q…msxu</a><br/>_________________________<br/><br/>His client mangled the npub in the plaintext as per NIP-08, your client might show the mangled part as &#34;@jimmysong&#34;. If you replace that text with the npub, you should be able to verify it. 2023-02-20T20:21:23Z https://nostr.ae/nevent1qqsvp84mnxkntyjkxqssean7glx6mzqqvpde76jg439w0rtz6754qqqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jqe9a4a In reply to <a href='/nevent1qqsxq7gunalzfeh3eghays686g9ldel6r94cd7hgvu9twuu4lqhsd5c74zfa9'>nevent1q…zfa9</a><br/>_________________________<br/><br/>NIP-04 is absolutely nowhere near what Bitmessage did. A major goal of Bitmessage is to provide anonymity and hide almost all metadata. NIP-04 does absolutely nothing to hide the metadata, the metadata is completely public to everyone (unlike almost every other communications protocol/platform where this is usually only visible to some centralized third party).<br/><br/>In Bitmessage, messages do not have any address label. Apart from a timestamp, every message is an opaque blob to everyone except the sender and recipient. All messages are broadcast through the peer-to-peer network to every participant, who each simply tries to decrypt every single message they receive with their private key. This means the recipient of a message has the full anonymity set of all Bitmessage users.<br/><br/>In comparison, NIP-04 DMs is Babbys First Crypto Project (and was AFAICT not meant to be much more):<br/>- Metadata like sender and recipient is provided in the clear in each message. The messages are public. Everyone can see who DMs whom when and how long the messages are.<br/>- Sender sends the DM directly to one or more relays, recipient receives DM by asking relays for messages matching their pubkey. Relays may be able to learn some extra information about the sender and recipient, such as IP address, browser, operating system, and usage patterns.<br/>- The encryption itself has issues like non-uniform AES key. 2023-02-20T19:05:09Z https://nostr.ae/nevent1qqsgwna3ccuam6umlch2yh3ea28xnz3msdcqw50f7h4872zluf9es3czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jrxa746 In reply to <a href='/nevent1qqstm3wgpjuxpj6x2k0sqets9g7j5dh5jq9dtwv2th9nn47aecjqxyg4f3qsq'>nevent1q…3qsq</a><br/>_________________________<br/><br/>To address the last point, in order to retain previously received zaps, maybe one could define a new event type for explicitly authorizing old zaps via `e` tags and/or old `nostrPubkey`s via `p` tags, in the 10000-19999 (replaceable) or 30000-39999 (parameterized replaceable) range. #nostr 2023-02-20T10:16:00Z https://nostr.ae/nevent1qqstm3wgpjuxpj6x2k0sqets9g7j5dh5jq9dtwv2th9nn47aecjqxygzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jnjruam Issues with #nostr NIP-57 Lightning Zaps:<br/>- Can be faked, as noted in the NIP itself<br/>- Includes payment info that may aid LN surveillance entities, for no good reason (see above)<br/>- If you later change your LNURL server or your LNURL server changes the `nostrPubkey` key for whatever reason, you lose all previously received zaps as the old zap notes can no longer be validated 2023-02-20T09:53:49Z https://nostr.ae/nevent1qqswk7hs9hpwxfnkz6c90235ukrlvx3wy7lhr5jnku8pp4m4vg5a8cqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jcgrjhl In reply to <a href='/nevent1qqs2yj8f7v68qpn90m37pr00rqfwft9sg4565hr8kdt76hpxvjydxucckfpu8'>nevent1q…fpu8</a><br/>_________________________<br/><br/>Indeed, you&#39;d need to reconstruct some of the data, though. I have the bolt11 invoice, which is needed for the zap note, but not the description, which also goes into the zap note and must hash to the bolt11 description hash. The description is supposed to be the zap request, which is signed by the sender&#39;s nostr key (I&#39;m not sure if such a thing was even created in this instance), while the zap note is signed by the recipient. 2023-02-19T16:45:16Z https://nostr.ae/nevent1qqsr99tmeftw87hu9y635zsmp06ud8cwqxdmnxsuzkrrwrqfruun2tgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j3amx67 In reply to <a href='/nevent1qqsdmsek6wgtgyyktq7xhjdwdls995u9ztf2j7865s50xpzkrt9qlysn89d0r'>nevent1q…9d0r</a><br/>_________________________<br/><br/>My biggest gripe with NIP-04 is that all DM metadata is public, including sender and recipient: #[5] 2023-02-19T16:25:30Z https://nostr.ae/nevent1qqsp54npptag8vmp0jmuueq6hrgrvsw2n4r3xj6z376yz60zq9a220qzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j29ak98 In reply to <a href='/nevent1qqs8wyvwwt8kjne283h0l56adkufqru0ugkr3km4ur72scupjt73g5sh56she'>nevent1q…6she</a><br/>_________________________<br/><br/>So I checked your lnurl-pay endpoint, and it doesn&#39;t include the NIP-57 fields `allowsNostr` and `nostrPubkey`. So no zap support, just regular lnurl-pay. But apparently that doesn&#39;t stop #snort from calling it a zap and then doing absolutely nothing on payment 🤪 2023-02-19T15:30:41Z https://nostr.ae/nevent1qqs8wyvwwt8kjne283h0l56adkufqru0ugkr3km4ur72scupjt73g5szyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j5a4zfu In reply to <a href='/nevent1qqstxrluvyd39slzph7g3plxu404rmfshewrd9rpesdxpdva0d8rpjgavv9rg'>nevent1q…v9rg</a><br/>_________________________<br/><br/>I zapped 1000 sats, the LN payment went through, but no feedback on my nostr client, did it do anything? 2023-02-19T15:12:56Z https://nostr.ae/nevent1qqsqk5a9uzsxng7t7zg0wsa9un27crkwrkj2ns7jcattwvh7vmysp9czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jtcdszt In reply to <a href='/nevent1qqs8wgfmj7nhcd3u4j3vca9s6xz0nzr2ydjcd9l4lzdqlhp3auhe8gq5fnmjm'>nevent1q…nmjm</a><br/>_________________________<br/><br/>Zaps are defined by NIP-57, apparently it records the bolt11 invoice and preimage in a public nostr event. So not as private. 2023-02-19T14:30:05Z https://nostr.ae/nevent1qqsg6uj6fya98rqkgatht538mhlj7yw88wlqq4hkehumf8eflk9mlmgzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jrmsxnf In reply to <a href='/nevent1qqsr9vuhs94jcjmfmhfxnetwh53cf8efn2g7txjq8njr4tdq0325x7cdpyyw4'>nevent1q…yyw4</a><br/>_________________________<br/><br/>IMHO, the current NIP-04 DM stuff should be killed with fire. The less integrated it is with other functionality, the better. 2023-02-19T11:41:49Z https://nostr.ae/nevent1qqsdtmmewucw2gzcjyshgcfdsazs2sewcv9hcj9nnavrts3m0yttdwszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2japd98g In reply to <a href='/nevent1qqsq5966gv2va7tlartsd0r6dhl8h2qn0qgmdrr0qr0p3usw30zf5fq2fc68d'>nevent1q…c68d</a><br/>_________________________<br/><br/>I think &#34;aspects&#34; is a good term for this feature. 2023-02-19T05:43:58Z https://nostr.ae/nevent1qqstnld4y52d4mumj8cymaj5ys9uahk3ntgrrk55l26d5a4vjzdwjnszyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jxweh5x In reply to <a href='/nevent1qqs9jq0awt2wuecp9eazc9yk7rqhstmcmt60089mk7srzwnk5quqkhg8da7w3'>nevent1q…a7w3</a><br/>_________________________<br/><br/>Apparently snort defined only a single hashtag for this message, according to the json output. Does it only ever add one tag per message, or was there some other issue with the second hashtag? #Nostr #hashtag #test 2023-02-19T05:31:04Z https://nostr.ae/nevent1qqsq5966gv2va7tlartsd0r6dhl8h2qn0qgmdrr0qr0p3usw30zf5fqzyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2j60htk7 In reply to <a href='/nevent1qqsfzvm7syz5nwa7nfzq2kufn9hkyftxtuj2jk3kzku5p0y69fuxqfg9uc22j'>nevent1q…c22j</a><br/>_________________________<br/><br/>I do like the idea of &#34;personas&#34; (I would maybe call them something else, maybe &#34;personal topics&#34;?)<br/><br/>This could be implemented per NIP-12 in combination with a new tag type for this feature. Or, if we make it a convention, just plain #hashtags. 2023-02-19T05:19:55Z https://nostr.ae/nevent1qqsg78v9hjpe9nsg27sd2ypjavur74rq6py0tudpdly0whx0htnmq5czyrwukkt6t6destl6empreaxum8t6e5j3a8rrkm0nyqk2f8mct0p2jn7ck7h In reply to <a href='/nevent1qqswurspsn279fn4svdg893m2dtxgv8jnmws4gjzmhh72r0wefgt4ugmst7u3'>nevent1q…t7u3</a><br/>_________________________<br/><br/>I learned about silent.link from CD77. Very exciting project. Looks like (for low usage) the data price can be quite decent as well in certain areas.<br/><br/>One issue I have with it is that you&#39;d ideally have to use this on a phone whose IMEIs are not tied to your identity (so no KYC SIMs ever used on it).<br/><br/>They said on CD77 that the physical-SIM and eSIM IMEIs are different and thus the network operator cannot easily link these, but from what I&#39;ve seen, the two IMEIs seem to be adjacent (apart from the final Luhn checksum digit), e.g:<br/>- 004101846898885<br/>- 004101846898893<br/>So it seems they would be trivially linkable.<br/><br/>Are there devices where these IMEIs are at least somewhat unrelated? 2023-02-19T03:06:33Z