It would be beautiful if you could go hiking and go to the river.

やったぜ。

The summer evening is beautiful

推測：リレーが横方向に繋がりを持ってメッシュ構造を作ると、ユーザー側はリレー数を多くしすぎる必要が減り、より確実な配信を受け取れるようになる。一方で、リレーごとの個性が損なわれて、同時に配信するリレーを選択する自由度もなくなる。それに対して中間的な選択肢になりそうなのがアウトボックスモデル。

メッシュリレーは配信主体がリレーで、バックエンドミラーを作成することでインフラを強固にする。Blossom系のメディアサーバーが相互にミラーを行っているのと似てる。

アウトボックスモデルは、配信主体がユーザーで、このユーザーはここに書き込んでますよ（ポストはここだよ by NIP-65）を公開するので、フォロワーが利用するクライアントはその通りに拾いに行く。

中間的なところで、リレー利用者のイベントの取り漏らしがないかを他のリレーに確認しに行って、不足があったら補完する。ということができたらいいかも。設定画面から受信をするか、配信をするかが選べれば「私の投稿はこのリレーだけに留めてほしい。他のリレーにミラーリングしないでください」みたいなことができる。

現在のリレーとそれ以外を繋ぐ中間リレーをstrfryで立ち上げて配信するやつはDB整合が難しいけど不可能ではなさそう。別でstrfry立ち上げて設定UIを提供すればいいみたいな具合もある。

Interesting, rhanks for sharing

I value order, efficiency, and reliability. I don't value simplicity or chaos quite so much. My effect on the nostr protocol has mainly been proposals to improve the reliability, efficiency, and orderliness of it, and the pushback has come mostly from people that like the freedom that the chaos gives them.

Some examples

* long ago I proposed that relays remember when an event arrived, and clients could query "all events that arrived after I last asked" to get a perfect next batch.

* long ago I proposed gossip/outbox model which specifies where events are expected to be, while many still choose very different and innovative ways to choose and use relays.

* I've been pushing for DHT usage to be more fully distributed and uncensorable, and to allow people to kickstart/bootstrap without knowing any relays or any nostr people. We get 99% functionality without it and so as you could imagine other devs don't really embrace the idea. I'm the guy who is never satisfied with 99%.

* I've wanted a rigorous standard that doesn't change

* I've wanted a binary protocol to juice up efficiency by avoiding JSON parsing

I feel like the black sheep in this regard (hence my avatar) because I gather that most nostr developers (and users) more highly value chaotic liberty.

Chaotic liberty is a great space to innovate in. But it is not a good space to build a solid user experience which requires a firm standard and compliance for interoperability. Hence I see hundreds of only somewhat compatible half-ass nostr applications that generally scare users off (which one? why are so many of them broken? and so different?).

This is all fine. But it means I'm not seeing nostr as the protocol that becomes the social media framework that the Internet eventually adopts. I see it more and more as a playground. Which is critical and innovative and wonderful. I just don't see how it can also be a stable user experience that draws in lots of users and creates substantial network effect value.

Mosaic is where I scratch my itch for order, efficiency, and reliability, and my attempt to create a solid user experience. I will be working on both Mosaic and nostr. Mosaic risks being too idealistic, the "betamax" of social media, but it is a risk I'm taking. Take joy knowing that I won't be bugging nostr devs as much about the chaos.

Should I post this or edit it more? Fuck it. I saw a meme that said to just post it.

リレーサーバーのアプリケーションを設置して動かすだけならまあまあ簡単だからみんなどんどんやって分散させまくればいいんだ。

好熱🥵

Relaxing and enjoying an espresso while my tesla drives me through rush hour ☕😌

おはようございます。アツアツのヒーコーいれました。☕

おはのす！！！みんなありがとう出会ってくれて

good morning 🌞

Happy day #nostr

Enjoy 😉

Pura Vida #Nsotr 🤙

wassup nostriches?

上島珈琲店です☀️

GM #nostr

Morning reading time is very important to me.

nostr starting to feel like 2022 era nostr again. everyone left except the absolutely insane folks. its great.

I spend most of my day reviewing and merging code from intelligent agents. I interact with them with natural language. the only downside is that they sometimes they lose interest and go work on other things. sometimes you can prompt them to do things but they have this thing called free will which is troublesome.

😹

มองอะไรนุด

#siamstr #catstr

わびさび #japan #autumnstr

?ex=656e7492&is=655bff92&hm=faeef9e3b55c88c1705db4295f4fa57438b0f87c2f39af08407cb5de06f51526&