Show HN: We’re building a gaming console for the browser
4 by kdzapp | 0 comments on Hacker News.
hey all, We’re excited to share bash.gg - a way to play all games on your browser. Our mission is to enable you to play games, from any device, with your friends. We're planning on using a combination of WebGL (soon WebGPU) & pixel streaming to run any game. Our product is going viral within a few school districts, here’s what we’ve built. The Problem: Poor Experiences: Mobile gaming is limited by hardware. Most mobile games are spammy & focused on optimizing value extraction. Existing web games are junk. Expensive: For good games, you need a console or PC, costing $600 - $3k. Not Scalable: Consoles are sold at a loss & desktop computers are too expensive. Necessary hardware is increasing in size and cost. On the other hand, games continue to get more computationally expensive. bash.gg: Great Experiences: We’re bringing the best games from PC and console to your browser so you can play from any device instantly. Affordable: You don’t need expensive hardware, just a stable internet connection. Scalable: As games demand more resources, they’re run in the cloud. The games that don’t need all that power can run in a browser. TLDR: Consoles make it difficult to play with all of your friends. If your friend has Xbox, and you have Playstation - you might not be able to play together. Having games on the browser lets anyone play, by just clicking a link. Not only that, but you can chat and play, all in one place. In progress features: pixel streaming (quic + webcodecs), community features, live audio/text chat (should release within in 2 weeks) Excited to hear what you all think!
Wednesday, 11 January 2023
New Show Hacker News story: latest news
Show HN: Tagging Assistant – add AWS cost allocation tags in your dev pipeline
16 by isemenov | 7 comments on Hacker News.
Hi HN! My name is Ilia. I'm here with my co-founders Thomas and Daniele to share our new feature, Tagging Assistant. AWS Cost Allocation Tags are labels on resources that attribute and track cloud costs. Tagging is a prerequisite to assigning cost ownership (e.g. by team/app/cost center) and creating cloud cost accountability. Tagging AWS resources is a manual process that’s done either when a resource is spun up or during a cost firefighting initiative to understand cost ownership. We figured there had to be a better way and set out to make tagging a seamless part of development pipelines that use GitHub and Terraform. Once set up, the Tagging Assistant GitHub action will allow you to continuously enforce and maintain your AWS tagging strategy within your Terraform projects. Each GitHub repository can be associated with a catalog key that maps to tag key-value pairs within the Tag Catalog on the Cloudthread App. Adding or changing tag key-value pairs in a Cloudthread’s Tag Catalog entry will generate a tagging update Pull Request each time the action runs, and fail if the appropriate tagging is not in place. An example of such an update is `.tf` build file getting `(locals {tags = …}})` added. All resources defined via Terraform in the repository will receive the same tags defined via the Tag Catalog. This is just the start – in the future we’ll create more tagging granularity so that it is possible to tag different provider aliases differently within a single project. A graphic showing how this works is here: https://ift.tt/mEInrl5 Tagging Assistant is free to use and instructions to set it up are in our docs below. https://ift.tt/T9B1Ntk By installing Tagging Assistant you’ll get access to the free version of Cloudthread’s cost visibility, savings insights, and unit economics features. Very excited to get feedback! Try it out, let us know what you think, and feel free to reach out directly to hey@cloudthread.io or by using the chat icon bottom right on the Cloudthread app.
16 by isemenov | 7 comments on Hacker News.
Hi HN! My name is Ilia. I'm here with my co-founders Thomas and Daniele to share our new feature, Tagging Assistant. AWS Cost Allocation Tags are labels on resources that attribute and track cloud costs. Tagging is a prerequisite to assigning cost ownership (e.g. by team/app/cost center) and creating cloud cost accountability. Tagging AWS resources is a manual process that’s done either when a resource is spun up or during a cost firefighting initiative to understand cost ownership. We figured there had to be a better way and set out to make tagging a seamless part of development pipelines that use GitHub and Terraform. Once set up, the Tagging Assistant GitHub action will allow you to continuously enforce and maintain your AWS tagging strategy within your Terraform projects. Each GitHub repository can be associated with a catalog key that maps to tag key-value pairs within the Tag Catalog on the Cloudthread App. Adding or changing tag key-value pairs in a Cloudthread’s Tag Catalog entry will generate a tagging update Pull Request each time the action runs, and fail if the appropriate tagging is not in place. An example of such an update is `.tf` build file getting `(locals {tags = …}})` added. All resources defined via Terraform in the repository will receive the same tags defined via the Tag Catalog. This is just the start – in the future we’ll create more tagging granularity so that it is possible to tag different provider aliases differently within a single project. A graphic showing how this works is here: https://ift.tt/mEInrl5 Tagging Assistant is free to use and instructions to set it up are in our docs below. https://ift.tt/T9B1Ntk By installing Tagging Assistant you’ll get access to the free version of Cloudthread’s cost visibility, savings insights, and unit economics features. Very excited to get feedback! Try it out, let us know what you think, and feel free to reach out directly to hey@cloudthread.io or by using the chat icon bottom right on the Cloudthread app.
Tuesday, 10 January 2023
New Show Hacker News story: latest news
Show HN: A Harry Potter Trivia Bot, Powered by GPT-3
5 by caltonji | 1 comments on Hacker News.
Over winter break I resurfaced an old project, a harry potter trivia bot. I rebuilt it using generative models instead of the extractive ones I had used previously. The generative approach was far easier to implement and performed better. Cheers.
5 by caltonji | 1 comments on Hacker News.
Over winter break I resurfaced an old project, a harry potter trivia bot. I rebuilt it using generative models instead of the extractive ones I had used previously. The generative approach was far easier to implement and performed better. Cheers.
New Show Hacker News story: latest news
Show HN: iMessage-exporter, a full-featured CLI app and library
2 by css | 0 comments on Hacker News.
I've spent a long time reverse engineering nearly every aspect of Apple's iMessage SQLite tables to build this program. As far as I know, there are no other tools that support the full corpus of iMessage features, including edited messages, app messages, reactions, and threads. I built this software to preserve some conversations with loved ones; I hope others find it useful as well. For the curious, here are some of the more interesting aspects of the database I came across: - Dates are stored as Unix timestamp with an epoch of 1/1/2001 00:00:00 - Messages can have multiple parts, denoted by some special invisible characters - Reactions are stored by prefixing the GUID of the reacted message with the index of the message part [0]. - URL messages cache data in the table, which we can parse and display [1]. - Edited messages store the history message edits [2] (I wanted to try out DDD here, which was fun!). [0]: https://ift.tt/b53iuqD... [1]: https://ift.tt/b53iuqD... [2]: https://ift.tt/b53iuqD...
2 by css | 0 comments on Hacker News.
I've spent a long time reverse engineering nearly every aspect of Apple's iMessage SQLite tables to build this program. As far as I know, there are no other tools that support the full corpus of iMessage features, including edited messages, app messages, reactions, and threads. I built this software to preserve some conversations with loved ones; I hope others find it useful as well. For the curious, here are some of the more interesting aspects of the database I came across: - Dates are stored as Unix timestamp with an epoch of 1/1/2001 00:00:00 - Messages can have multiple parts, denoted by some special invisible characters - Reactions are stored by prefixing the GUID of the reacted message with the index of the message part [0]. - URL messages cache data in the table, which we can parse and display [1]. - Edited messages store the history message edits [2] (I wanted to try out DDD here, which was fun!). [0]: https://ift.tt/b53iuqD... [1]: https://ift.tt/b53iuqD... [2]: https://ift.tt/b53iuqD...
Subscribe to:
Posts (Atom)