genius 
within the first hours of using the mostr.pub bridge, it goes down on me. not a good sign. i wonder what it does once it comes up again? i mean, hopefully, it syncs up from the last known position. not that this repairs the damage of posts being delayed, but better than getting lost to /dev/null.
manually managing relays struck me as one of the least user-friendly aspects of setting up my clients. they came with defaults, yes, but different ones, so i'd have different views of Nostr depending on which one i was using, until i "synced" them all using the shared list that's stored in the profile metadata.
not sure if WebSocket does any gzip compression, but it would most certainly be convenient if it did, because it should be able to compress Base64 quite efficiently.
i mean, you could make one of the binary JSON formats out there available on a separate port, for clients/servers that support that. at least some of those formats support binary blobs or typed arrays, and virtually all of them are strongly typed. it does lead to the question of what to do with these binary blobs once they need to be serialised as plain-text JSON. one possibility is to standardise on Base64 encoding.
#[0] is there any chance you might implement support for line breaks in your ActivityPub/Nostr bridge? they don't seem to carry across to Mastodon when i post from Nostr, at least.
and further, i see that clients offer you the option of rebroadcasting any post you come across - not only your own posts, but any post - to all of the relays you're connected to. doesn't this imply that clients can copy posts between relays? if so, the next question is: does this happen when a client shares a post also? doesn't the client then expose that post to all the relays it's connected to?
not quite sure everyone understood the question i asked earlier about Nostr relays, because i WASN'T describing a scenario with no relay overlap.
rather, the scenario i was asking about was this:
John: i made a post. i talk to relays A and B.
Pete: i'm sharing John's post,. i talk to relays A, B and C.
Charles: i talk to relay C only. can i see John's post, since Pete is sharing it?
hey, wouldn't it be up to the Nostr *client* to broadcast the original post to all connected relays for a reblog/share? i mean, if i was making a client, i'd make it do that. it's not like posts *have* to stay on the relays they were originally posted to. as i understand it, a client can share *any* post it knows about with a relay. it's signed with the private key of the user who originally made it, so...
one of the least extensible and least debuggable serialisation formats out there? 😬
well, it seems that boosting on Nostr doesn't always carry across to Mastodon even between mutually followed accounts
in this case i am mutually following my own accounts
but as i understand it, i can rebroadcast anyone's message that is visible to me to all the relays i'm connected to. would i have to do that prior to sharing so that people will see it?
hm, that's quite a drawback in the case of relay.mostr.pub, which is a bridge to Mastodon. it's far less effective as a bridge if nothing from there is even possible to share to people who aren't using it.
(if you're a dying moth i don't know what to tell ya)
"fly toward the light" is good advice if you're dying and are trying to get to heaven but bad advice if you're a moth
for some reason, shares/reblogs don't always make it through the mostr.pub bridge.
can anyone tell me which relays are the ones with the Chinese spam bots on them? 😫