Replying to Avatar MichaelJ

Can you expound on that a bit? Are you saying relays and clients should be developed in parallel, or should the relay live in the client?

The latter solution ends up being peer-to-peer, with the associated problems.
Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

i think the client and the relay should be developed as an integrated unit, then the features are going to work reliably, and it lets you shrink the feature set targets down so they get implemented systematically

also, for business use case, good interop is basically essential between clients and relays

there is a definitely discord between the "universal social network protocol" stream of development that gives you the outbox model, and the business use case of isolated subnetworks that don't get contaminated with the general open network

Reply to this note

Please Login to reply.

Discussion

Avatar
MichaelJ 1y ago

I completely agree with that. For business cases, the client and relay should be a paired set.

A group chat app would have to be something like that. Interop lets you open the door to let in events from the global network, but not every client needs to see every event.

Avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

exactly... this means a mostly private team chat, slack style, can have a public facing forum side as well, that isn't just specific to a website or client as well, though the internal version is paired because it's mission critical