You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@hamnox-to-be-deprecated %9BHbTvu0N2e8MutmpFOBXzKcK9TvddKhtDRooYsukdk=.sha256

Doesn't a pub invite try to post to your feed? That, uh, is a problem if you are trying to restore an existing feed. In the days of patchwork I got around that by running ssb-server and feeding it gossip connections by command line.

@Rabble %jAmicrLFpXUwhXR4UcqrUST2gQEo0EAnRRSnflzQQJ8=.sha256

So bugs and bugs. What’s happening here is two intersecting bugs. One that EBT doesn’t want to give you your own feed back to you. That’s what you need to restore. The legacy syncing system does work for restoring but Manyverse doesn’t support it. We fixed the ebt bug in Scuttlego but I’m not sure if it’s fixed in JS.

Rooms don’t generally host content so you need to connect to a peer through a room.

There is one pub implementation that does support ebt and legacy and giving you back your own feed. That’s planetary-graphql that Cherese and mixmix wrote. It’s pretty nifty and is running in production at civic.love, planetary.pro, and planetary.name. If one of those room+pub servers has your feed and you join then you’ll be able to restore to any ssb app I believe.

The Scuttlego and planetary-graphql apps are open source. The latter should probably be renamed as it is really ssb-pub using ssb-db2 and graphql. We at planetary are no longer doing active development on them as of about a month ago. We’d love it if they continued to live on in use and growth. Maybe migrate to ssbc.

In terms of planetary we have shifted or development focus to nostr and nos.social. We switched because we wanted delete, faster syncing, and multi device support. And because it’s a simpler protocol and tech stack to support.

Join Scuttlebutt now