You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a big issue that covers a lot of TODOs in order to move away from ssb-gossip and adopt ssb-conn. Feel free to edit this list if you come across some other task related to gossip.
Patchcore REQUIRED
patchcore/sbot.js should replace sbot.gossip.peers (a sync api) with ssb.conn.peers (a source api), should pull.drain that and update localPeers and connectedPeers
Patchcore REQUIRED
patchcore/sbot.js should expose a new api called stagedPeers, similar to localPeers and connectedPeers, based on ssb.conn.stagedPeers (a source api)
Patchcore OPTIONAL
patchcore/sbot.js should replace gossipConnect with connConnect, replace sbot.gossip.connect with sbot.conn.connect
Patchbay REQUIRED
patchbay's Network page should also observe stagedPeers, display them, and allow the user to "approve" a staged peer, which should call patchcore.connConnect and then publish a new follow message
Patchbay REQUIRED
patchbay should use ssb-lan instead of ssb-local
ssb-ahoy OPTIONAL
ssb-ahoy/views/replication should replace server.gossip.connect with server.conn.connect
ssb-invite OPTIONAL
ssb-invite should replace server.gossip.add with server.gossip.remember
ssb-replicate OPTIONAL
ssb-replicate should replace ssbServer.gossip.peers (a sync api) with ssbServer.conn.peers (a source api), pull.filter that to have only type==='lan' and truthy .key, pull.drain that, and request() replication
ssb-ebt OPTIONAL
ssb-ebt/index.js should remove the sbot.gossip.disconnect call because ssb-conn's scheduler automatically makes sure that blocked peers will never be connected to
ssb-device-address OPTIONAL
ssb-device-address/index.js should replace sbot.gossip.add/remove with sbot.conn.remember/forget, notice the TODO comment in ssb-device-address, ssb-conn supports multiserver addresses
ssb-friend-pub OPTIONAL
ssb-friend-pub/index.js should replace sbot.gossip.add/remove with sbot.conn.remember/forget
Note: gossip's add() is equivalent to CONN's remember() + connect(), so in some cases where we had gossip.add, we might want to do only conn.remember, and in other cases, we might want to do conn.remember plus conn.connect. "Remember" means "store in the persistent db", and "Connect" means "connect to them right now".
The text was updated successfully, but these errors were encountered:
Here's a big issue that covers a lot of TODOs in order to move away from ssb-gossip and adopt ssb-conn. Feel free to edit this list if you come across some other task related to gossip.
patchcore/sbot.js
should replacesbot.gossip.peers
(async
api) withssb.conn.peers
(asource
api), should pull.drain that and updatelocalPeers
andconnectedPeers
patchcore/sbot.js
should expose a new api calledstagedPeers
, similar tolocalPeers
andconnectedPeers
, based onssb.conn.stagedPeers
(asource
api)patchcore/sbot.js
should replacegossipConnect
withconnConnect
, replacesbot.gossip.connect
withsbot.conn.connect
stagedPeers
, display them, and allow the user to "approve" a staged peer, which should callpatchcore.connConnect
and then publish a new follow messagessb-ahoy/views/replication
should replaceserver.gossip.connect
withserver.conn.connect
ssb-invite
should replaceserver.gossip.add
withserver.gossip.remember
ssb-replicate
should replacessbServer.gossip.peers
(async
api) withssbServer.conn.peers
(asource
api), pull.filter that to have onlytype==='lan'
and truthy.key
, pull.drain that, andrequest()
replicationssb-ebt/index.js
should remove thesbot.gossip.disconnect
call because ssb-conn's scheduler automatically makes sure that blocked peers will never be connected tossb-device-address/index.js
should replacesbot.gossip.add/remove
withsbot.conn.remember/forget
, notice the TODO comment in ssb-device-address, ssb-conn supports multiserver addressesssb-friend-pub/index.js
should replacesbot.gossip.add/remove
withsbot.conn.remember/forget
Note: gossip's
add()
is equivalent to CONN'sremember()
+connect()
, so in some cases where we hadgossip.add
, we might want to do onlyconn.remember
, and in other cases, we might want to doconn.remember
plusconn.connect
. "Remember" means "store in the persistent db", and "Connect" means "connect to them right now".The text was updated successfully, but these errors were encountered: