\r\n\r\nFinally, we have an endpoint we can start to integrate multi-chain components.\r\n\r\nAt some point would be nice to have some component which would wrap and abstract the current endpoint in case we find Supabase is not sufficient for our case. \r\n\r\n\r\n## Endpoint\r\nFollow up what can be done with new endpoint\r\nIf anyone wants to play with that here is the URL\r\n\r\n```\r\nhttps://xtnvtbdyvpbbnonbbcif.supabase.co/graphql/v1\r\n```\r\n\r\nYou need to add `apiKey` header into your request. You can find the key in the discord group.\r\n\r\n\r\nSample Query\r\n```graphql\r\nquery findCollections {\r\n\tcollectionsCollection(first: 10) {\r\n\t\tedges {\r\n\t\t\tnode {\r\n\t\t\t\tname\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}\r\n```\r\n\r\n\r\n## Tasks \r\n- https://github.com/kodadot/nft-gallery/issues/4865\r\n- https://github.com/kodadot/nft-gallery/issues/4617\r\n- https://github.com/kodadot/nft-gallery/issues/4380\r\n- https://github.com/kodadot/nft-gallery/issues/4618\r\n- https://github.com/kodadot/nft-gallery/issues/4073\r\n- https://github.com/kodadot/nft-gallery/issues/4275\r\n- https://github.com/kodadot/nft-gallery/issues/4753\r\n\r\nOnce all the above done \r\n- https://github.com/kodadot/nft-gallery/issues/4379\r\n\r\n## Ref\r\n- https://developers.cloudflare.com/d1/platform/client-api/\r\n- https://github.com/kodadot/nft-gallery/issues/1824",[2865,2868,2871,2874,2877],{"name":2866,"color":2867},"$$","0E8A16",{"name":2869,"color":2870},"p2","D4C5F9",{"name":2872,"color":2873},"A-search","FBCA04",{"name":2875,"color":2876},"chief","67EA1F",{"name":2878,"color":2873},"A-multi-chain",4257,"kodadot","nft-gallery","open","Enable Multi-chain capabilities in KodaDot","2023-03-15T14:49:24Z","https://github.com/kodadot/nft-gallery/issues/4257",0.7760439,{"description":2888,"labels":2889,"number":2899,"owner":2880,"repository":2881,"state":2882,"title":2900,"updated_at":2901,"url":2902,"score":2903},"Right now, KodaDot was built mostly to be an on-chain data explorer and being a thin layer. Hence we would like to enhance comfort and are not sure if we should put these numbers like views on-chain as it might get expensive; we would like to provide users/artists some off-chain metrics and close to real-time.\r\n\r\nMaking a serverless function (worker?) which will be storing this stuff in KV in some efficient way. \r\nProbably each 1k, or 10k we can offload some stores to some remark to store these numbers on-chain to having only small increments off-chain. \r\n\r\nThis would be helpful for artists, creators and game item designers to have approximate estimation of which item is in demand. Similiar you have plays in Spotify, this would help estimate general audience likeliness of particular artifact \r\n\r\nWe could collect \r\n- load times of item (we should put some filter/captcha to account it was human viewing and not programmatically made or bumping some views)\r\n- if it's video play times\r\n- if it's 3d, time user has played with item?\r\n- if it's downloadable, times user/owner has downloaded it \r\n\r\nwyt?\r\n\r\n\r\nWe can then incorporate this into the new v1.1 Gallery item detail\r\n- #4403 \r\n\r\n\r\nTo start iterating on this, we would like to start showing this views per visit from logged persons. \r\nI think we can still trigger workers somehow and I guess we should split it to counting with logged vs not logged persons with wallet\r\nWe can trigger worker from which item was it visited and take it from there? \r\n\r\nUsing Workers/CF infrastructure would be probably easiest \r\n\r\n",[2890,2893,2895,2897],{"name":2891,"color":2892},"enhancement","a2eeef",{"name":2894,"color":2873},"A-research",{"name":2896,"color":2870},"p3",{"name":2898,"color":2873},"A-worker",4593,"Views counter/ranking","2023-04-11T20:04:33Z","https://github.com/kodadot/nft-gallery/issues/4593",0.78910685,{"description":2905,"labels":2906,"number":2907,"owner":2880,"repository":2881,"state":2908,"title":2909,"updated_at":2910,"url":2911,"score":2912},"- [x] Merge latest main to the VR \n- [x] Test and deploy rubick#18",[],1869,"closed","KodaDot stuff that needs to be resolved","2022-01-17T12:26:37Z","https://github.com/kodadot/nft-gallery/issues/1869",0.7550828,{"description":2914,"labels":2915,"number":2925,"owner":2880,"repository":2881,"state":2908,"title":2926,"updated_at":2927,"url":2928,"score":2929},"Had idea to write article about Subquery and what we are doing with it for RMRK and beyond\r\n\r\r\nWould be good to migrate indexer under kodadot organization afterwards #1394\n\nExtend with article about rubick\n\nIt would help our new developers to onboard how we use indexers from SubSquid and Subquery \n\n#2013",[2916,2919,2920,2923],{"name":2917,"color":2918},"subquery","EC2C6D",{"name":2896,"color":2870},{"name":2921,"color":2922},"onboarding","715318",{"name":2924,"color":2873},"A-writing-✍️",1501,"Article about vikiival/magick on dev.to","2023-01-18T10:48:57Z","https://github.com/kodadot/nft-gallery/issues/1501",0.75577325,{"description":2931,"labels":2932,"number":2936,"owner":2880,"repository":2881,"state":2908,"title":2937,"updated_at":2938,"url":2939,"score":2940},"Hence to ease onboarding for new contributors, would be nice to have a lightweight article on how KodaDot actually works in the background. How KodaDot is actually middleware and leveraging existing web3 infrastructure to drive end-user experience and how can anyone use us as a template to make spinoffs with existing components.\r\n\r\nI would suggest mentioning\r\n- subquery (vikiival/magick, kodadot/unique)\r\n- subsquid (kodadot/rubick, kodadot/snek)\r\n- Cloudflare / workers\r\n- bao (pictures)\r\n- packages (subapi, minimark, vuex-options)\r\n- Nuxt \r\n- Infra providers (Netlify, CF)\r\n- Storage, [you can recycle from @kkukelka article about past, present and future of data storage](https://medium.com/kodadot/on-the-past-present-and-future-of-data-storage-at-kodadot-7634a0c32530?source=collection_home---------2-------------------------------)\r\n\r\nBonus stage (required for better awareness for new comers)\r\n- Make a dedicated page on docs.kodadot.xyz for tech-stack for better reachability\r\n\r\nAnything I'm missing? 📟 @vikiival \r\n\r\nh/t @thea-exe for amazing nudge and spotting blind spot",[2933,2934,2935],{"name":2866,"color":2867},{"name":2896,"color":2870},{"name":2924,"color":2873},2766,"Write article about tech stack of KodaDot ","2022-06-25T08:20:51Z","https://github.com/kodadot/nft-gallery/issues/2766",0.75845355,{"description":2942,"labels":2943,"number":2948,"owner":2880,"repository":2881,"state":2908,"title":2949,"updated_at":2950,"url":2951,"score":2952},"KodaDot is started as a fork of vue-polkadot and we took a lot of components from that which are now useless.\r\n\r\nDeliverables: \r\n- [ ] check and remove unnecessary components \r\n- [ ] check and remove unnecessary node packages\r\n- [ ] test it properly\r\n- [ ] Optional: If there is some logic which could be reused add it to the report",[2944,2945,2946],{"name":2866,"color":2867},{"name":2896,"color":2870},{"name":2947,"color":2873},"A-maintenance",439,"Reduce bundle size","2023-10-11T13:32:10Z","https://github.com/kodadot/nft-gallery/issues/439",0.7591516,{"description":2954,"labels":2955,"number":2957,"owner":2880,"repository":2881,"state":2908,"title":2958,"updated_at":2959,"url":2960,"score":2961},"- archive old repository \r\n- migrate code we use to under kodadot1\r\n- release package\r\n- install into new code\r\n- make PR\r\n- close this down",[2956],{"name":2869,"color":2870},2077,"Migrate vue-polkadot packages under kodadot1","2022-01-27T09:57:49Z","https://github.com/kodadot/nft-gallery/issues/2077",0.7661652,{"description":2963,"labels":2964,"number":2967,"owner":2880,"repository":2881,"state":2908,"title":2968,"updated_at":2969,"url":2970,"score":2971},"We have successfully migrated magic under the kodadot \r\nOnce https://github.com/kodadot/magick/issues/24 will be done we will create a new instance for SubQuery\r\n\r\nThis is a tracking issue for the issues that has to be done before:\r\n- [ ] https://github.com/kodadot/magick/issues/24\r\n- [ ] https://github.com/kodadot/magick/issues/25\r\n- [x] #2862 ",[2965,2966],{"name":2917,"color":2918},{"name":2896,"color":2870},2865,"Migrate vikiival/magick to kodadot/magic","2023-01-12T14:03:24Z","https://github.com/kodadot/nft-gallery/issues/2865",0.7730461,{"description":2973,"labels":2974,"number":2980,"owner":2880,"repository":2881,"state":2908,"title":2981,"updated_at":2982,"url":2983,"score":2984},"We would need to build a developer audience around kodadot and show them how easy is to write your own resolver to the Rubick\r\n\r\n- write an easy SubSquid query \r\n- Leverage the usefulness of Viki's tutorial, in a simple format, hence video is 1 hour long \r\n- I guess we can publish it to dev.to as there is better developer audience \r\n\r\n### Ref\r\n- https://github.com/kodadot/rubick/\r\n- \r\n",[2975,2976,2977,2979],{"name":2866,"color":2867},{"name":2896,"color":2870},{"name":2978,"color":2873},"A-subsquid",{"name":2924,"color":2873},3042,"how to make NFT resolver to Rubick and use it in KodaDot ","2023-12-22T10:58:53Z","https://github.com/kodadot/nft-gallery/issues/3042",0.77513844,{"description":2986,"labels":2987,"number":2995,"owner":2880,"repository":2881,"state":2908,"title":2996,"updated_at":2997,"url":2998,"score":2999},"### Setup\r\n\r\n- [ ] KodaDot hack template (Nuxt3 + Naive UI)\r\n- [ ] Make mint SDK\r\n- [x] Finish Uniquery \r\n",[2988,2989,2991,2992,2993],{"name":2891,"color":2892},{"name":2990,"color":2867},"$",{"name":2894,"color":2873},{"name":2978,"color":2873},{"name":2994,"color":2873},"A-uniquery",3976,"What have I missed on hackhatons?","2023-02-06T13:48:59Z","https://github.com/kodadot/nft-gallery/issues/3976",0.7771656,["Reactive",3001],{},["Set"],["ShallowReactive",3004],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7elDZ_cBQT4yCAflJMOrX-6lvVx2lkDGkPIY1zsmPgQ":-1},"/kodadot/nft-gallery/600"]