You are reading content from Scuttlebutt
@dokoissho
Subscribed to channel #ssb-dev
@Anders
Re: %FsOuR9ov9

@punkmonk correct to the last point. ssb-identities don't have any relationship between feeds (on purpose). Meta feeds is meant to be on a single computer to make it easy to split data for different purposes into multiple feeds. For that purpose you then don't need to use ssb-identities.

@Hiure
Voted # SSB meta feeds As part of our work on the #ngipointer grant, over the co
User has chosen not to be hosted publicly
@tohl
Subscribed to channel #ssb-dev
@cel
Voted Awesome thanks so much for this info [@cel](@f/6sQ6d2CMxRUhLpspgGIulDxDCwYD
@miles
Re: %Ov7f/vGgS

Awesome thanks so much for this info @cel .. helpful, also @zelf . I think in the end its probably worth the hassle to be able to switch and change wallets and ssb feeds so perhaps its ok to have to like sign a message on your feed saying this is your public eth address (and vice versa in an eth transaction of some kind ?)

But that said could be handy and fun to be able to derive a 'default' ssb feed from an eth address in a predictable way. I wonder if that woudl be a specfication of some kind - could be a very short one pager - and if so where one would publish such a thing? Perhaps as an library beginning "ssb-xxx" or something?

@miles
Voted Also, [@sean](@N/vWpVVdD1e8IbACUQE4EVGL6+aodQfbQZ8ByC+k79s=.ed25519) and [@
@miles
Voted Apache Tuweni's SSB implementation supports secp256k1 feeds: https://github
@Zenna
Re: %Ov7f/vGgS

Also, @sean and @adria0 might have some insights 🌸


Show whole feed
Join Scuttlebutt now