#62 と両立するためにはどうしたらいいか考える必要がある

https://github.com/nostr-protocol/nips/blob/master/26.md

• Fix filter match check process
• singer

or another test framework.

cf.

• #18
• #25

https://github.com/nostr-protocol/nips/blob/master/13.md

Thanks for providing this cool library.

I was trying [email protected] with the code in app/main.ts, but when I do two or more subscriptions at the same time, the events get mixed up.

import { debounceTime } from 'rxjs';
import { Relays, BackwardReq, MonoFilterAccumulater, uniq } from 'rx-nostr';
import { webcrypto } from 'crypto';
import WebSocket from 'ws';

global.WebSocket = WebSocket;
global.crypto = webcrypto;

const relays = new Relays([
  "wss://relay-jp.nostr.wirednet.jp",
  "wss://nostr-relay.nokotaro.com",
]);

const acc0 = new MonoFilterAccumulater({ kinds: [0], limit: 5 });
const req0 = BackwardReq.from(acc0, debounceTime(500));

const acc1 = new MonoFilterAccumulater({ kinds: [1], limit: 5 });
const req1 = BackwardReq.from(acc1, debounceTime(500));

relays.observeReq(req0).pipe(uniq()).subscribe((e) => console.log('req0', e.message[2].kind));
relays.observeReq(req1).pipe(uniq()).subscribe((e) => console.log('req1', e.message[2].kind));

# output
# req0 expects to get only kind0 and req1 expects to get only kind1
req0 1
req1 1
req0 1
req1 1
req0 1
req1 1
req0 1
req1 1
req0 1
req1 1
req0 0
req1 0
req0 0
req1 0
req0 0
req1 0
req0 0
req1 0
req0 0
req1 0

Am I using it incorrectly?
As far as I've tried, it reproduced in both node and browser.

Full code is here: https://github.com/akiomik/rx-nostr-playground/blob/859e6be14512023b788eddf650070c2e24683736/main.js

• nocheck option

Provide signed event object

ref. note1g63p0ny60fsg2yfvqrmzde675dadwgvm65sgpp0sdus0ccj6zz9q6nq8w5

テストでrx-nostrがなんか上手く動かない問題、デバッガ使って追跡しようとしてるけどなんかトランスパイル後のコードに飛んじゃう sourcemapあるのに

• Connection レイヤーで REQ を割って投げて、まとめてから返す
• MessageSize 上限も気にしてあげられるとなおいい
• ほとんど同じことだが max_limit にも対応してあげたい

https://github.com/nostr-protocol/nips/blob/master/40.md

https://github.com/nostr-protocol/nips/blob/master/42.md

https://www.rfc-editor.org/rfc/rfc6455.html#section-7.2.3

To prevent this, clients SHOULD use some form of backoff when trying to reconnect after abnormal closures as described in this section.

Not bug. I/F design issue.

When RxNostrImpl#setRelays([]) is called, it seems that the previous relay connections remain undisconnected.

Provide an option to lazily evaluate since or until time when the REQ is (re)sent.

Like that enableTimeShift: true

send() のシグネチャに影響を与えるので v3 かも

note1n0uf87xu2a0xadjt3dhgrafujyjx7dw24hc3sy2hntkc34plwgrs2jt7fk

• REQ 等の送受信の生の値を console.log 出力できてもいい

• extend(req, batchMixin(interval))
• .update(filters => newFilters)

or

• .pipe(bufferFilter(mergeFilter, toChunks), throttle(interval))

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry

Ensure that old REQ is to be closed.

Closing the issue will remove preid rc from v1.0.0-rc.x.

• Code comment
• websocket-polyfill
• [ ] ready for EN doc

I tried v0.1.0 with the code from app/main.ts but it didn't work.

The following objects should be exported in dist/index.es.js at v0.1.0 (3c48c0b).

export {
  pe as Nostr,
  so as RxBackwardReq,
  co as RxForwardReq,
  ao as createRxNostr,
  io as filterKind,
  ro as latest,
  no as uniq,
  oo as verify
};

In practice it looks like this:

export {
  Je as BackwardReq,
  Ke as ForwardReq,
  $r as MonoFilterAccumulater,
  Nt as Nostr,
  Pr as Relays,
  zr as Req,
  Vr as collect,
  Mr as filterKind,
  Dr as latest,
  Zt as normalizeFilter,
  Kt as normalizeFilters,
  Wr as pickEvent,
  jr as uniq,
  Fr as verify
};

(ref: https://www.npmjs.com/package/rx-nostr?activeTab=code)

Please fix v0.1.0 or release a new version.