Ideally we can build a completely non-custodial stack where we never obtain user information beyond what everyone can see on the blockchain. Our proposed SDK and the publisher-side widgets wouldn’t pose any problems here, as they would be implemented on third party websites.
Yet the easiest was to implement a user dashboard would be to host them on a site that we build, which would involve capturing exposed metadata like IP addresses associated with user accounts. Capturing and storing that information is not desirable for a secure and permisionless protocol, if for no other reason that it could serve as a honeypot for malicious actors.
I don’t think it’s a good idea to omit a user dashboard where tribute allocations can be tracked and managed outside of the context of what publishers want to display. Otherwise users might feel out of control and unhappy with the tribute layer. Of course we could leave it to another dev team to make a user dashboard on their own site, but if that weren’t available at launch it would leave a pretty big hole in the ecosystem. I’m in favor of launching a user dashboard ourselves. It might make the overall system more robust if there were a truly decentralized fallback user dashboard option that 3rd party dashboards had to improve upon to gain traction.
Is there any way we can build and deploy an easy-to-access user dashboard front end without hosting it ourselves? Is there any kind of IPFS solution for this?