By BY KARAN DEEP SINGH from NYT Arts https://ift.tt/On0tSaV
via IFTTT
Thursday, April 6, 2023
New top story on Hacker News: Show HN: StorySeed – AI Facilitated, immersive, creative learning experience
Show HN: StorySeed – AI Facilitated, immersive, creative learning experience
12 by nvln | 0 comments on Hacker News.
Hello HN, Are you looking for a fun and engaging way to spark your creativity or your teen's creativity? Or maybe you're interested in exploring the world of storytelling? Introducing Story Seed - an AI-facilitated learning experience that will take you on an immersive and interactive journey through the art of storytelling with movies, books and tv shows you love. With bite-sized lessons, fun guessing games, and AI facilitation, you'll be inspired to tap into your imagination and bring your stories to life like never before. This learning experience is perfect for pre-teens and teens who are interested in writing, as well as anyone who wants to improve their storytelling skills. It's a great way to spend quality time with your kids, or to explore your own creativity. It is integrated with our new tool for creative writing, Papyr. We are excited about launching them together. When you complete StorySeed, the learning experience, you are given 3 prompts to choose from and you begin writing, in Papyr. Today we are releasing our pilot, Chapter 1: Story DNA. We will be releasing the rest of the chapters during the coming months and adding new content hopefully, forever. It's free but signup is required to track credits. Please check them both out and let us know what you think. Papyr: https://ift.tt/Es07rlF StorySeed: https://seed.kood.app
12 by nvln | 0 comments on Hacker News.
Hello HN, Are you looking for a fun and engaging way to spark your creativity or your teen's creativity? Or maybe you're interested in exploring the world of storytelling? Introducing Story Seed - an AI-facilitated learning experience that will take you on an immersive and interactive journey through the art of storytelling with movies, books and tv shows you love. With bite-sized lessons, fun guessing games, and AI facilitation, you'll be inspired to tap into your imagination and bring your stories to life like never before. This learning experience is perfect for pre-teens and teens who are interested in writing, as well as anyone who wants to improve their storytelling skills. It's a great way to spend quality time with your kids, or to explore your own creativity. It is integrated with our new tool for creative writing, Papyr. We are excited about launching them together. When you complete StorySeed, the learning experience, you are given 3 prompts to choose from and you begin writing, in Papyr. Today we are releasing our pilot, Chapter 1: Story DNA. We will be releasing the rest of the chapters during the coming months and adding new content hopefully, forever. It's free but signup is required to track credits. Please check them both out and let us know what you think. Papyr: https://ift.tt/Es07rlF StorySeed: https://seed.kood.app
New top story on Hacker News: Show HN: Sym, define just-in-time access workflows in code
Show HN: Sym, define just-in-time access workflows in code
21 by abuggia | 2 comments on Hacker News.
Hello HN, My cofounder (jon918) and I started Sym three years ago because we were frustrated with how hard it was to manage access to cloud infrastructure. We wanted to build a tool for JIT access that was actually designed for developers. We were wary of tools that tried to accommodate both devs and IT but ended up with usability compromises for both. First, we figured no one wants another web app to log into so we let administrators define access workflows in Terraform and let developers request and gain access via Slack. That seemed to pay off: being code-based was a big plus for our early customers since it let them manage the logic in version control and test in CI/CD. Second, we knew that updating permissions/roles/access was a major source of toil and risk in the world of cloud infrastructure. Have you ever tried to avoid annoying, persistent access requests by setting policies that are a bit more permissive than you’d like? We felt that fully automated just-in-time access + approvals could really help here. But we also knew that a simple approval tool could end up leading to request fatigue - kind of defeating the purpose. So we built an SDK to let you define checks in code (e.g. pagerduty.on_call, okta.is_user_in_group, github.get_repo_collaborators) in order to dynamically route requests or fast-track access when appropriate. This seems to be paying off: users are creating Slack-based approvals in front of different types of risky actions like production access, sensitive queries and triggering Lambdas. We’d love your feedback on our approach so far. Does this make sense to you? Is this a tool you'd use? What would you want to see out of it? To learn more, check out the video that Nick (nmeans (Sym VPEng)) made [1]. You can also check out our docs [2] or set up your own flow [3]. thanks! -adam [1] https://ift.tt/2ITb7oC [2] https://docs.symops.com [3] https://ift.tt/oheSK9i
21 by abuggia | 2 comments on Hacker News.
Hello HN, My cofounder (jon918) and I started Sym three years ago because we were frustrated with how hard it was to manage access to cloud infrastructure. We wanted to build a tool for JIT access that was actually designed for developers. We were wary of tools that tried to accommodate both devs and IT but ended up with usability compromises for both. First, we figured no one wants another web app to log into so we let administrators define access workflows in Terraform and let developers request and gain access via Slack. That seemed to pay off: being code-based was a big plus for our early customers since it let them manage the logic in version control and test in CI/CD. Second, we knew that updating permissions/roles/access was a major source of toil and risk in the world of cloud infrastructure. Have you ever tried to avoid annoying, persistent access requests by setting policies that are a bit more permissive than you’d like? We felt that fully automated just-in-time access + approvals could really help here. But we also knew that a simple approval tool could end up leading to request fatigue - kind of defeating the purpose. So we built an SDK to let you define checks in code (e.g. pagerduty.on_call, okta.is_user_in_group, github.get_repo_collaborators) in order to dynamically route requests or fast-track access when appropriate. This seems to be paying off: users are creating Slack-based approvals in front of different types of risky actions like production access, sensitive queries and triggering Lambdas. We’d love your feedback on our approach so far. Does this make sense to you? Is this a tool you'd use? What would you want to see out of it? To learn more, check out the video that Nick (nmeans (Sym VPEng)) made [1]. You can also check out our docs [2] or set up your own flow [3]. thanks! -adam [1] https://ift.tt/2ITb7oC [2] https://docs.symops.com [3] https://ift.tt/oheSK9i