Nostr Web Client

Replying to

jb55

I think so? It uses strfry

Orange Crush 2y ago

I thought strfry only compressed relay to relay comms not relay to client.

Reply to this note

Please Login to reply.

Discussion

jb55 2y ago

Oh really? Dang then no

Orange Crush 2y ago

If you setup Damus to use yesstr, then you can sync compressed.

jb55 2y ago

hmm sounds pretty custom

Cutetug 2y ago

Will is there any lightning poker site or roulette or something ?

jb55 2y ago

There is but its not very good. Maybe I'll build one one day 😅

Cutetug 2y ago

Awesomeeeeee

Lightning is so much fun !!!!!!!!

I m having so much fun on nostr

DonkHODL🗿🌽🦨 2y ago

lightning poker would be lit

Cutetug 2y ago

There is a lottery bot called #[8] and another one #[9]

elsat 2y ago

yesstr is a relay, or something else?

elsat 2y ago

Thanks 🍊.

I wrote up the compression question on nostr nips issues yesterday.

I wondered if 1) there are further data savings to be had (per 🍊 sounds like yes to/from client) and 2) if these are worthwhile. Maybe worth exploring for clients in order to reduce bandwidth needs further?

https://github.com/nostr-protocol/nips/issues/265

21823843... 2y ago

Actually strfry *does* compress relay->client messages by default, using websocket per-message compression with sliding window (if supported by client).

This is configurable with the relay.compression.enabled and relay.compression.slidingWindow parameters in the beta branch.

The strfry logs also include the compression negotation parameters on client connect, and the total compression ratios on disconnect (up and down).

Orange Crush 2y ago

This is 🔥🔥🔥

f 2y ago

これSnortにリダイレクトされるんだ。Damus Webが生きてたときはこれで飛べたのかな。

https://damus.io/#[0]

f 2y ago

これでURL表示できるかな

`https://damus.io/#[1]`