| I got a little stuck in the weeds trying to figure out how it all works (I'm not well versed in Ruby). At first I thought this was acting as a thin client for data stored on IPFS/Ethereum, but it seems this is actually a full blown ruby+postgresss activitypub server that also happens to backup some data onto an IPFS node. I also saw that there are two version of the numa.sol contract posted, both to the ethereum network, and also in the github https://github.com/numaverse/numaverse-gateway/tree/master/c... When I send messages to your server from a different ActvityPub instance (like my account on mastodon), is it also being added to the IPFS node, or just to the gateway's postgres? I'm thinking about the case of moving an account but not being able to keep the threading of replies since the activitypub 'actor' isn't tied to the hash/wallet transactions, but to the server. Makes me think there is a bit of an impedance mismatch in what you're trying to do. That suggests taking my account someplace else will be tricky since my follower's accounts will still be following the old one. As it stands, it looks like i'd just be paying to have a hash stored on ethereum, but I'd still need to run my own/pay for an IPFS node to mirror those hashes if I wanted to secure my data. Those two things combined makes me question the "Because all the data is stored in a distributed fashion, that means you’re not reliant on any central server." bit. Seems that this could all be done with an export/import functionality and a bit of pgp. Maybe I missing something fancy going on with how you're handling the wallet stuff internally? ---- But maybe im focusing too much on the activity pub thing and that's actually more of a bonus feature - expecting that to work across servers might be asking too much. Lets say I signed up on numaverse.com and created a profile. Then at some later time I manually publish a transaction to my own IPFS node linked up to the main IPFS network, then published my own hash on ethereum using the same wallet address and contract - And did so outside of the ruby app running on your server. Would numaverse.com be aware of that publication and be able accept replies/federate it out? Lets say someone spins up a separate copy of numaverse on a different URL with their own IPFS node linked to the larger IPFS network, and then followed me. would that instance be using activity pub to get the content, or would it be looking directly at the hash/wallet/ipfs and the ruby servers would never actually have to talk to each other? Maybe the feature i'm looking for here with regards to user identity being nomadic and tied to the wallet is just not implemented fully yet? ---- "Token Curated Registries" reminds me of what Colony is trying to do - having a bunch of tokens that track reputation within the group that is somewhat separate from the global token. I saw you just added in a tipping system - presumably you'll be creating a set of smart contracts that facilitate the registries under a similar mechanism. Would be neat to have different kinds of reputation mechanisms and not just the raw token counts we see today. |