- From: <sandy.aggarwal.apps@gmail.com>
- Date: Sat, 18 Mar 2023 09:52:00 -0400
- To: "'Nick Tipping'" <nick.tipping@bbc.co.uk>, "'Raf Mertens'" <raf@crazygames.com>, "'Team Community Process'" <team-community-process@w3.org>
- Cc: <public-games@w3.org>, "'Francois Daoust'" <fd@w3.org>
- Message-ID: <144901d959a0$d04284c0$70c78e40$@gmail.com>
Good day group members. I’m wondering if it might make sense to have a quick call to get a roster of topics of mutual interest. I’m particularly looking int the aspects of identity and payments in gaming and working towards kicking off a research paper work in that area. Would love to get some feedback from this community. Since I’m rather new to this specific group, please note I’m involved in other Linux Foundation projects focusing on this nexus of blockchains and gaming but more from what practical utility can blockchains and DLT provide to gaming and NOT from the viewpoint that blockchains cure all ills in gaming – present or not. And rooted in this viewpoint, I believe that decentralized identity, micro-payments and digital asset tracking are three areas where we can have a real value-add by using decentralized assets. Please join the group below if you would like to be part of that discusion/project work (Intention is not to siphon off resources from this group – I guess this community group here at W3C in more focused on overall web games and the Hyperledger group is focused on use of DLT in games, not web only). https://wiki.hyperledger.org/display/MESIG/MESIG+-+Gaming+Subgroup PS: I had started this group at Hyperledger in 2021. We were able to churn out some papers and presentations but are running low on attendance there as well, especially in second half of ’22 due to lack of resources – which I’m trying to address this year. Best – Sandy From: Nick Tipping <nick.tipping@bbc.co.uk> Sent: Tuesday, March 7, 2023 11:15 AM To: Raf Mertens <raf@crazygames.com>; Team Community Process <team-community-process@w3.org> Cc: public-games@w3.org Subject: Re: Planning to close Games Community Group due to inactivity unless we hear from you I would also second this staying open if possible. Hopefully we can look at more involvement through 2023 and if anyone has suggestions how we can help we would love to hear. Nick Tipping Engineering Team Lead BBC Games _____ From: Raf Mertens <raf@crazygames.com <mailto:raf@crazygames.com> > Sent: 07 March 2023 09:29 To: Team Community Process <team-community-process@w3.org <mailto:team-community-process@w3.org> > Cc: public-games@w3.org <mailto:public-games@w3.org> <public-games@w3.org <mailto:public-games@w3.org> > Subject: Re: Planning to close Games Community Group due to inactivity unless we hear from you Hi W3 team, As the browser becomes a stronger and stronger platform for games with new APIs going live or getting implemented, I think it would be very unfortunate timing to close down this community. At CrazyGames, we see a big interest from mobile publishers moving into the web space as an additional publishing channel for their game. In addition, many indie developers look at the browser as an accessible publishing channel to discover an early audience for their games. So, I would definitely vote to keep the community going. Best regards, Raf Mertens On Mon, Mar 6, 2023 at 7:29 PM Team Community Process <team-community-process@w3.org <mailto:team-community-process@w3.org> > wrote: Dear participants in the Games Community Group https://www.w3.org/community/games/ Your Community Group appears to have become inactive (per [1]). W3C plans to close this group in 10 days unless we hear compelling reasons from you to keep it open. Thank you, CG/BG System [1] https://www.w3.org/community/about/faq/#close-inactive -- Raf Mertens CEO <https://www.crazygames.com/> <https://files.crazygames.com/assets/email-footer/line.png> <https://be.linkedin.com/company/crazygames> <https://twitter.com/crazygamescom> IMPORTANT NOTICE: This email and any files attached to it are confidential and/or privileged, and solely for use by the intended individual or entity. If you have received it by mistake, do not read, copy, store, disclose, distribute or use it in any manner and notify the sender by email reply.
Received on Saturday, 18 March 2023 13:52:17 UTC