-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MyMeta] Custom Backgrounds #443
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.001 SC attached to it.
|
I have some questions about this:
Thanks! |
|
Thanks for fleshing out the requirements, will be good for later!
We could go the hands off route and only let people link to the image. I'm not a lawyer but that seems like a way to avoid problems. But its only a matter of time before someone says "Hmm, so I can post child porn. Lets do it." and that isn't a fun thing to show anywhere. Content moderation is a pain and we probably have the same problems with avatars/headers, even though they come from 3box at the moment. |
Yeah, probably good enough to begin with 🤷♂️ |
Seems that having control of the image would be preferable.
I wouldn't count on this migration happening anytime soon. Do you have any experience hosting images in IPFS?
This sort of thing is only a problem at a certain scale, I think we have a solid enough community right now to police itself. At some point we can add a flag button or something |
Forgive me if I have missed the discussion somewhere but has there been any progress on this? I have looked through the last few weeks meeting notes and not found it in searches in Discord. @alalonde |
Not sure about others but I was keeping the discussion here to try and flesh out the requirements when I was looking for a first issue to participate in. I haven't done any work on this since.
Sorry, I totally missed this question! I do have some experience but using the CLI, not programming the interaction. |
I'm working on this using ipfs. Everything is working fine, but I need to do some changes in the Smart Contract so I can save the hash returned by the ipfs and link that hash with the wallet address so we can have a relation. (simple smart contract mapping). Is it ok? |
We are in the process of creating an IDX MetaGame profile where this data will be stored. (Like in the next two weeks.) ¿Are you talking about creating a smart contract to store the user's background? The data will be living in Ceramic with a cached reference stored in Hasura. ¿Where are you pinning the IPFS hash? I'm pretty sure we want to use web3.storage for this. |
@dysbulic hey man, okay. I was working with infura and getting the hash returned by it. But I see web3.storage more useful and if you guys want to use it I can do it. Another members are going to use work on this one? bc I can help :) |
@CastilloLuis, we're in the process of switching from storing profile information in a database to having that data in the Ceramic Network as the source of truth. Before we get to that though, we are going to build a frontend for storing the IDX basic profile. It has two images (a profile and header background) in it that will need to be stored in the same manner as the background you're adding, so you could certainly be useful. 😸 As for web3.storage, it's free and theoretically reliable, so it seems like the way to go. Otherwise, anyone using the system is going to have to deal with pinning costs. Not that they'd be huge, but if we can eliminate a concern it seems like a good idea. |
@CastilloLuis, I was wrong about using web3.storage. It relies on an API key for authentication, and to use it in MyMeta we would need to include the key in the application (or hack together some way to keep it private). Anyone with the key has the ability to remove all the files from an account, so until they add an alternative authentication mechanism or add scoping to keys so you can create an upload-only one, we should probably just use a traditional pinning service. |
Ok, so there's been another change of course. @Cali93 & I implemented a web3.storage uploader Hasura action. You send it a file & it returns you a CID. Or at least it will when it's done in the next day or so. The action handler exists, but Hasura actions don't have All of the pinning services I examined – pinata, infura, & web3.storage – utilize an API token for authentication. A token that shouldn't be sent to the client necessitating a service running somewhere to authenticate and proxy the upload. The base64 encoding is a bit of a hack, but the next best alternative – uploading via a Next.js API endpoint – is blocked by the need for webpack 5 to run web3.storage. That is in turn blocked by the upgrade to Next v11 and React v17 (#792). |
Currently there is being worked on storing a potential background image in Ceramic. |
So the profiles now have a page background image. There is no interface, however, for including it in the page. To accomplish the custom background, I would like to enable profile theming (#1158) which would let me specify not only the image, but also how it is positioned and a background color and other properties. I would also like to keep track of all the background images that have ever been entered (they are all saved in web3.storage, but will be orphaned currently if a new image is uploaded). I would like to present the user with an interface that conglomerates the backgrounds from all the users and makes it simple to insert that into a custom theme. |
Right on, great to hear! |
Maybe it could be token gated by an NFT that one buys and must be in your wallet to access extended features? |
I have it in the interface to upload the background image & it shows it as saved when revisiting later but it never actually displays in the background.. Is it just me or the feature isn't finished yet? |
Done by @dan13ram as a part of the 1.0 push |
Allow people to set custom backgrounds on their MyMeta profile.
Bonus points if hosted on IPFS or other decentralized storage.
The text was updated successfully, but these errors were encountered: