The best Hacker News stories from Show from the past day

Go back

Latest posts:

Show HN: Symbiants – digital ant farm / mental health companion

Hello HN! Hope you are well.<p>I'm creating my first video game. It's nowhere near complete, but I am eager for feedback, so here I am!<p>My game is a digital ant farm. You should think SimAnt + Tamagotchi. Here's a picture: <a href="https://i.imgur.com/dIJaraG.png" rel="nofollow noreferrer">https://i.imgur.com/dIJaraG.png</a><p>It's written in Rust/Bevy, compiled to WASM, and is open-source, <a href="https://github.com/MeoMix/symbiants">https://github.com/MeoMix/symbiants</a>. Fair warning, though, this is my first time writing in Rust/Bevy.<p>My goal is to give people cute ants that do cute ant stuff 24/7, ask people to look after their ants and to feed them once-per-day, and then deny people the ability to provide ant care unless they engage in mental health exercises.<p>I started working on this project for a few reasons:<p>1) I've been a dev for ~15 years, but, on a personal level, I have very little to show for it. I've worked on multiple, multi-year projects which were subsequently shut down by lawyers and, frankly, I'm tired of practicing non-attachment with my work. So, I'm creating this as a personal affirmation.<p>2) I enjoy my fully-remote, WFH lifestyle, but I find myself more isolated than ever. The lack of disruption allows for some serious focus. Sometimes I get so focused on a project that days slip by without me practicing self-care, and I'll keep going until my output wanes due to lack of healthy behaviors. I thought having a digital companion who is interested in ensuring I remain consistent in caring for myself, by expecting consistent care for itself, would be effective and beneficial.<p>3) Ants are sweet. Obviously there should be more ant sims. :)<p>Currently, "Sandbox Mode" is all that exists. This mode provides the user with developer tools and allows them to treat the world like an unbounded playground. I use this mode for prototyping. In the future, I'll combine mechanics from Sandbox Mode with cutscenes to create a more restrictive/compelling Story Mode.<p>Sandbox Mode includes the following features:<p>* Queen Ant spawns, searches for a nesting spot, and begins to dig out a nest by hauling sand to the surface.<p>* Queen Ant establishes a nest and begins rearing worker ants once per hour.<p>* Worker Ants haul sand to the surface and emergently expand the nest with tunnels/chambers when they feel cramped.<p>* Ants get hungry and starve if not fed every 24 hours.<p>* Sand-fall physics applies to the environment. Food, sand tumble down surfaces.<p>* Basic day/night cycle. Sky background lightens/darkens with time of day.<p>* Option to link in-game time to real-world time and to sync sunrise/sunset.<p>* Ants go to sleep at night.<p>* Ants emote when sleeping and eating food.<p>* User Actions allow user to spawn sand, dirt, food, and ants. You can kill ants, despawn ants, despawn food, and select entities, too.<p>* Settings allow user to affect simulation speed (Sandbox Mode only), ant color, etc.<p>* Breathwork Prompt encourages user to meditate on a loose schedule in exchange for feeding ants.<p>Today, I am working on adding eggs to the birthing lifecycle and then allowing ants to carry eggs as well as other, dead ants. :)<p>If you'd like to read more about my stretch goals for Story Mode, feel free to peruse my ramblings. The high-level goal is to create a homage to Children of Time by Adrian Tchaikovsky, <a href="https://docs.google.com/document/d/17ACH1XLCn7hkKz2dhuL1c_nxbGOTZdUY6jJPsY_xA6I/edit#heading=h.4iljwczfftys" rel="nofollow noreferrer">https://docs.google.com/document/d/17ACH1XLCn7hkKz2dhuL1c_nx...</a><p>If you'd like to talk more directly - my email is in my profile or you can reach me through Discord - <a href="https://discord.gg/Qugp2Es4" rel="nofollow noreferrer">https://discord.gg/Qugp2Es4</a><p>So, what do you think?<p>Good idea with poor execution?<p>Love everything and just want to see more?<p>Feel that I'm just throwing away time with a non-viable starter?<p>Want to help but don't know where to start?<p>Let me hear it! Thanks for your time.

Show HN: Symbiants – digital ant farm / mental health companion

Hello HN! Hope you are well.<p>I'm creating my first video game. It's nowhere near complete, but I am eager for feedback, so here I am!<p>My game is a digital ant farm. You should think SimAnt + Tamagotchi. Here's a picture: <a href="https://i.imgur.com/dIJaraG.png" rel="nofollow noreferrer">https://i.imgur.com/dIJaraG.png</a><p>It's written in Rust/Bevy, compiled to WASM, and is open-source, <a href="https://github.com/MeoMix/symbiants">https://github.com/MeoMix/symbiants</a>. Fair warning, though, this is my first time writing in Rust/Bevy.<p>My goal is to give people cute ants that do cute ant stuff 24/7, ask people to look after their ants and to feed them once-per-day, and then deny people the ability to provide ant care unless they engage in mental health exercises.<p>I started working on this project for a few reasons:<p>1) I've been a dev for ~15 years, but, on a personal level, I have very little to show for it. I've worked on multiple, multi-year projects which were subsequently shut down by lawyers and, frankly, I'm tired of practicing non-attachment with my work. So, I'm creating this as a personal affirmation.<p>2) I enjoy my fully-remote, WFH lifestyle, but I find myself more isolated than ever. The lack of disruption allows for some serious focus. Sometimes I get so focused on a project that days slip by without me practicing self-care, and I'll keep going until my output wanes due to lack of healthy behaviors. I thought having a digital companion who is interested in ensuring I remain consistent in caring for myself, by expecting consistent care for itself, would be effective and beneficial.<p>3) Ants are sweet. Obviously there should be more ant sims. :)<p>Currently, "Sandbox Mode" is all that exists. This mode provides the user with developer tools and allows them to treat the world like an unbounded playground. I use this mode for prototyping. In the future, I'll combine mechanics from Sandbox Mode with cutscenes to create a more restrictive/compelling Story Mode.<p>Sandbox Mode includes the following features:<p>* Queen Ant spawns, searches for a nesting spot, and begins to dig out a nest by hauling sand to the surface.<p>* Queen Ant establishes a nest and begins rearing worker ants once per hour.<p>* Worker Ants haul sand to the surface and emergently expand the nest with tunnels/chambers when they feel cramped.<p>* Ants get hungry and starve if not fed every 24 hours.<p>* Sand-fall physics applies to the environment. Food, sand tumble down surfaces.<p>* Basic day/night cycle. Sky background lightens/darkens with time of day.<p>* Option to link in-game time to real-world time and to sync sunrise/sunset.<p>* Ants go to sleep at night.<p>* Ants emote when sleeping and eating food.<p>* User Actions allow user to spawn sand, dirt, food, and ants. You can kill ants, despawn ants, despawn food, and select entities, too.<p>* Settings allow user to affect simulation speed (Sandbox Mode only), ant color, etc.<p>* Breathwork Prompt encourages user to meditate on a loose schedule in exchange for feeding ants.<p>Today, I am working on adding eggs to the birthing lifecycle and then allowing ants to carry eggs as well as other, dead ants. :)<p>If you'd like to read more about my stretch goals for Story Mode, feel free to peruse my ramblings. The high-level goal is to create a homage to Children of Time by Adrian Tchaikovsky, <a href="https://docs.google.com/document/d/17ACH1XLCn7hkKz2dhuL1c_nxbGOTZdUY6jJPsY_xA6I/edit#heading=h.4iljwczfftys" rel="nofollow noreferrer">https://docs.google.com/document/d/17ACH1XLCn7hkKz2dhuL1c_nx...</a><p>If you'd like to talk more directly - my email is in my profile or you can reach me through Discord - <a href="https://discord.gg/Qugp2Es4" rel="nofollow noreferrer">https://discord.gg/Qugp2Es4</a><p>So, what do you think?<p>Good idea with poor execution?<p>Love everything and just want to see more?<p>Feel that I'm just throwing away time with a non-viable starter?<p>Want to help but don't know where to start?<p>Let me hear it! Thanks for your time.

Show HN: EnfinBref- {GPT3-5|Mistral-7B} YouTube summaries, segment by segment

A neat (in my opinion) little side-project I've been working on, both to get somewhat basic React skills going, and to work with LLMs on even more cool projects to build.<p>It should work for most major languages and output English summaries (or French summaries, if using the main <a href="https://enfinbref.io" rel="nofollow noreferrer">https://enfinbref.io</a> page instead of the /en/ subpage), no matter the input language.<p>Currently planning on expanding in various directions, including some nice new features like choosing a summary type, better video type identification and LLM routing, and bullet points exec summaries. Pretty basic on functionalities at the moment, and relying on a few tricks. The key stack:<p>- FastAPI + Python backend, with some extra libs for type validation (Pydantic), translation and YouTube transcript fetching. - Chained LLM calls with logic. id video type w/ a light model, break down into segments and sections, parallelise as much as can be, general high level summaries. - Models are a mix of Mistral fine-tune and GPT-3.5, with prompts tailored to the identified type of content and the current context. - Front-end is my first foray into React + Tailwind, with my last front-end experience before that being jQuery.<p>Inspired by a post a while back about Summary Cat, but with a more in-depth approach: all summaries are segment-by-segment to get a more in-depth view at potentially complex videos. Segments are defined as being 3mn long for short videos, 5mn for longer ones. Anything above 45mn is broken down into 45 minute sections, both for ease of context length handling (solidly into gpt-3.5-16k territory, which is already more annoying to run than Mistral-7B, and any further would require GPT-4) and because things get a bit murkier to handle in terms of clarity when going above that limit.<p>(the name is from a common French idiom for "anyway")

Show HN: Clone someone and talk to them like in real life

Show HN: EdgeDB Cloud and 4.0 with FTS and Auth

Hi there! This is Yury, a co-founder.<p>We've been busy for a while building EdgeDB Cloud and now it's finally here.<p>EdgeDB Cloud is pretty cool and takes full advantage of our database. You get declarative schema, strict typing throughout, great performance, a query language that's best of GraphQL & SQL, and many many other perks.<p>The Cloud itself is quite unique because of EdgeDB. Our query language gives you composability - so you can fetch everything for your page or API endpoint in one network request. And our protocol and client libraries give you auto recovery on network errors, automatic transaction retry, built-in transparent connection pooling, and many other benefits.<p>Check out the blog post where we explain it all. And watch the currently ongoing YouTube Premiere of the launch!

Show HN: EdgeDB Cloud and 4.0 with FTS and Auth

Hi there! This is Yury, a co-founder.<p>We've been busy for a while building EdgeDB Cloud and now it's finally here.<p>EdgeDB Cloud is pretty cool and takes full advantage of our database. You get declarative schema, strict typing throughout, great performance, a query language that's best of GraphQL & SQL, and many many other perks.<p>The Cloud itself is quite unique because of EdgeDB. Our query language gives you composability - so you can fetch everything for your page or API endpoint in one network request. And our protocol and client libraries give you auto recovery on network errors, automatic transaction retry, built-in transparent connection pooling, and many other benefits.<p>Check out the blog post where we explain it all. And watch the currently ongoing YouTube Premiere of the launch!

Show HN: EdgeDB Cloud and 4.0 with FTS and Auth

Hi there! This is Yury, a co-founder.<p>We've been busy for a while building EdgeDB Cloud and now it's finally here.<p>EdgeDB Cloud is pretty cool and takes full advantage of our database. You get declarative schema, strict typing throughout, great performance, a query language that's best of GraphQL & SQL, and many many other perks.<p>The Cloud itself is quite unique because of EdgeDB. Our query language gives you composability - so you can fetch everything for your page or API endpoint in one network request. And our protocol and client libraries give you auto recovery on network errors, automatic transaction retry, built-in transparent connection pooling, and many other benefits.<p>Check out the blog post where we explain it all. And watch the currently ongoing YouTube Premiere of the launch!

Show HN: EdgeDB Cloud and 4.0 with FTS and Auth

Hi there! This is Yury, a co-founder.<p>We've been busy for a while building EdgeDB Cloud and now it's finally here.<p>EdgeDB Cloud is pretty cool and takes full advantage of our database. You get declarative schema, strict typing throughout, great performance, a query language that's best of GraphQL & SQL, and many many other perks.<p>The Cloud itself is quite unique because of EdgeDB. Our query language gives you composability - so you can fetch everything for your page or API endpoint in one network request. And our protocol and client libraries give you auto recovery on network errors, automatic transaction retry, built-in transparent connection pooling, and many other benefits.<p>Check out the blog post where we explain it all. And watch the currently ongoing YouTube Premiere of the launch!

Show HN: Anchor – developer-friendly private CAs for internal TLS

Hi HN! I'm Ben, co-founder of Anchor (<a href="https://anchor.dev/" rel="nofollow noreferrer">https://anchor.dev/</a>). Anchor is a hosted service for ACME powered internal X.509 CAs. We recently launched our features & tooling for local development. The goal is to make it easy and toil-free to develop locally with HTTPS, and also provide dev/prod parity for TLS/HTTPS encryption.<p>You can add Anchor to your development workflow in minutes. Here's how:<p>- <a href="https://blog.anchor.dev/getting-started-with-anchor-for-local-development-6dd2cd605c08" rel="nofollow noreferrer">https://blog.anchor.dev/getting-started-with-anchor-for-loca...</a><p>- <a href="https://blog.anchor.dev/service-to-service-tls-in-development-d0df479d67ce" rel="nofollow noreferrer">https://blog.anchor.dev/service-to-service-tls-in-developmen...</a><p>We started Anchor because private CAs were a constant source of frustration throughout our careers. Avoiding them makes it all the more painful when you're finally forced to use one. The release of ACME and Let's Encrypt was a big step forward in certificate provisioning, but the improvements have been almost entirely in the WebPKI and public CA space. Internal TLS is still as unpleasant & painful to use as it has been for the past 20 years. So we've built Anchor to be a developer-friendly way to setup internal TLS that fully leverages the benefits of ACME:<p>- no encryption experience or X.509 knowledge required<p>- automatically generated system and language packages to manage client trust stores<p>- ACME (RFC 8555) compliant API, broad language/tooling support for cert provisioning<p>- fully hosted, no services or infra requirements<p>- works the same in all deployment environments, including development<p>If you're interested in more specific details and strategy, our blog posts cover all this and more: <a href="https://blog.anchor.dev/" rel="nofollow noreferrer">https://blog.anchor.dev/</a><p>We are asking for feedback on our features for local development, and would like to hear your thoughts & questions. Many thanks!

Show HN: Anchor – developer-friendly private CAs for internal TLS

Hi HN! I'm Ben, co-founder of Anchor (<a href="https://anchor.dev/" rel="nofollow noreferrer">https://anchor.dev/</a>). Anchor is a hosted service for ACME powered internal X.509 CAs. We recently launched our features & tooling for local development. The goal is to make it easy and toil-free to develop locally with HTTPS, and also provide dev/prod parity for TLS/HTTPS encryption.<p>You can add Anchor to your development workflow in minutes. Here's how:<p>- <a href="https://blog.anchor.dev/getting-started-with-anchor-for-local-development-6dd2cd605c08" rel="nofollow noreferrer">https://blog.anchor.dev/getting-started-with-anchor-for-loca...</a><p>- <a href="https://blog.anchor.dev/service-to-service-tls-in-development-d0df479d67ce" rel="nofollow noreferrer">https://blog.anchor.dev/service-to-service-tls-in-developmen...</a><p>We started Anchor because private CAs were a constant source of frustration throughout our careers. Avoiding them makes it all the more painful when you're finally forced to use one. The release of ACME and Let's Encrypt was a big step forward in certificate provisioning, but the improvements have been almost entirely in the WebPKI and public CA space. Internal TLS is still as unpleasant & painful to use as it has been for the past 20 years. So we've built Anchor to be a developer-friendly way to setup internal TLS that fully leverages the benefits of ACME:<p>- no encryption experience or X.509 knowledge required<p>- automatically generated system and language packages to manage client trust stores<p>- ACME (RFC 8555) compliant API, broad language/tooling support for cert provisioning<p>- fully hosted, no services or infra requirements<p>- works the same in all deployment environments, including development<p>If you're interested in more specific details and strategy, our blog posts cover all this and more: <a href="https://blog.anchor.dev/" rel="nofollow noreferrer">https://blog.anchor.dev/</a><p>We are asking for feedback on our features for local development, and would like to hear your thoughts & questions. Many thanks!

Show HN: Anchor – developer-friendly private CAs for internal TLS

Hi HN! I'm Ben, co-founder of Anchor (<a href="https://anchor.dev/" rel="nofollow noreferrer">https://anchor.dev/</a>). Anchor is a hosted service for ACME powered internal X.509 CAs. We recently launched our features & tooling for local development. The goal is to make it easy and toil-free to develop locally with HTTPS, and also provide dev/prod parity for TLS/HTTPS encryption.<p>You can add Anchor to your development workflow in minutes. Here's how:<p>- <a href="https://blog.anchor.dev/getting-started-with-anchor-for-local-development-6dd2cd605c08" rel="nofollow noreferrer">https://blog.anchor.dev/getting-started-with-anchor-for-loca...</a><p>- <a href="https://blog.anchor.dev/service-to-service-tls-in-development-d0df479d67ce" rel="nofollow noreferrer">https://blog.anchor.dev/service-to-service-tls-in-developmen...</a><p>We started Anchor because private CAs were a constant source of frustration throughout our careers. Avoiding them makes it all the more painful when you're finally forced to use one. The release of ACME and Let's Encrypt was a big step forward in certificate provisioning, but the improvements have been almost entirely in the WebPKI and public CA space. Internal TLS is still as unpleasant & painful to use as it has been for the past 20 years. So we've built Anchor to be a developer-friendly way to setup internal TLS that fully leverages the benefits of ACME:<p>- no encryption experience or X.509 knowledge required<p>- automatically generated system and language packages to manage client trust stores<p>- ACME (RFC 8555) compliant API, broad language/tooling support for cert provisioning<p>- fully hosted, no services or infra requirements<p>- works the same in all deployment environments, including development<p>If you're interested in more specific details and strategy, our blog posts cover all this and more: <a href="https://blog.anchor.dev/" rel="nofollow noreferrer">https://blog.anchor.dev/</a><p>We are asking for feedback on our features for local development, and would like to hear your thoughts & questions. Many thanks!

Show HN: Halloween game to show off my new Terminal

Hi hi,<p>I made a little Halloween themed game this week to show off my new terminal. You can play it in the browser. at <a href="https://joel.tools/halloween/" rel="nofollow noreferrer">https://joel.tools/halloween/</a><p>Two years ago, I started building an experiment tracking tool for myself as I have been venturing into ai research, and it has morphed into a terminal with rich content support and a bunch of fancy features. <a href="https://github.com/JoelEinbinder/snail/">https://github.com/JoelEinbinder/snail/</a><p>I can't recommend people start using snail for important stuff today, but I think the game is fun and it shows off a lot of the capabilities of the terminal.<p>Joel Einbinder

Show HN: Streamdal – an open-source tail -f for your data

Hey there! This is Dan and Ustin (@uzarubin), and we want to share something cool we've been working on for the past year - an open-source <i>`tail -f`</i> for your data, with a UI. We call it <i>"Streamdal"</i> which is a word salad for streaming systems (because we love them) and DAL or data access layer (because we’re nerds).<p>Here's the repo: <a href="https://github.com/streamdal/streamdal">https://github.com/streamdal/streamdal</a><p>Here's the site: <a href="https://streamdal.com">https://streamdal.com</a><p>And here's a live demo: <a href="https://demo.streamdal.com">https://demo.streamdal.com</a> (github repo has an explanation of the demo)<p>— — —<p>THE PROBLEM<p>We built this because the current observability tooling is not able to provide real-time insight into the actual data that your software is reading or writing. Meaning that it takes longer to identify issues and longer to resolve them. That’s time, money, and customer satisfaction at stake.<p>Want to build something in-house? Prepare to deploy a team, spend months of development time, and tons of money bringing it to production. Then be ready to have engineers around to babysit your new monitoring tool instead of working on your product.<p>— — —<p>THE BASIC FLOW<p>So, wtf is a “tail -f for your data”. What we mean is this:<p>1. We give you an SDK for your language, a server, and a UI.<p>2. You instrument your code with <i>`StreamdalSDK.Process(yourData)`</i> anytime you read or write data in your app.<p>3. You deploy your app/service.<p>4. Go to the provided UI (or run the CLI app) and be able to peek into what your app is reading or writing, like with <i>`tail -f`</i>.<p>And that's basically it. There's a bunch more functionality in the project but we find this to be the most immediately useful part. Every developer we've shown this to has said "I wish I had this at my gig at $company" - and we feel exactly the same. We are devs and this is what we’ve always wanted, hundreds of times - a way to just quickly look at the data our software is producing in real-time, without having to jump through any hoops.<p><i>If you want to learn more about the "why" and the origin of this project - you can read about it here: <a href="https://streamdal.com/manifesto">https://streamdal.com/manifesto</a></i><p>— — —<p>HOW DOES IT WORK?<p>The SDK establishes a long-running session with the server (using gRPC) and "listens" for commands that are forwarded to it all the way from the <i>UI -> server -> SDK</i>.<p>The commands are things like: <i>"show me the data that you are currently consuming"</i>, <i>"apply these rules to all data that you produce"</i>, <i>"inspect the schema for all data"</i>, and so on.<p>The SDK interprets the command and either executes Wasm-based rules against the data it's processing or if it's a <i>`tail`</i> request - it'll send the data to the server, which will forward it to the UI for display.<p>The SDK <i>IS</i> part of the critical path but it does not have a dependency on the server. If the server is gone, you won't be able to use the UI or send commands to the SDKs, but that's about it - the SDKs will continue to work and attempt to reconnect to the server behind the scenes.<p>— — —<p>TECHNICAL BITS<p>The project consists of a lot of "buzzwordy" tech: we use gRPC, grpc-Web, protobuf, redis, Wasm, Deno, ReactFlow, and probably a few other things.<p>The server is written in Go, all of the Wasm is Rust and the UI is Typescript. There are SDKs for Go, Python, and Node. We chose these languages for the SDKs because we've been working in them daily for the past 10+ years.<p><i>The reasons for the tech choices are explained in detail here:</i> <a href="https://docs.streamdal.com/en/resources-support/open-source/">https://docs.streamdal.com/en/resources-support/open-source/</a><p>— — —<p>LAST PART<p>OK, that's it. What do you think? Is it useful? Can we answer anything?<p>- If you like what you're seeing, give our repo a star: <a href="https://github.com/streamdal/streamdal">https://github.com/streamdal/streamdal</a><p>- And If you <i>really</i> like what you're seeing, come talk to us on our discord: <a href="https://discord.gg/streamdal" rel="nofollow noreferrer">https://discord.gg/streamdal</a><p>Talk soon!<p>- Daniel & Ustin

Show HN: Streamdal – an open-source tail -f for your data

Hey there! This is Dan and Ustin (@uzarubin), and we want to share something cool we've been working on for the past year - an open-source <i>`tail -f`</i> for your data, with a UI. We call it <i>"Streamdal"</i> which is a word salad for streaming systems (because we love them) and DAL or data access layer (because we’re nerds).<p>Here's the repo: <a href="https://github.com/streamdal/streamdal">https://github.com/streamdal/streamdal</a><p>Here's the site: <a href="https://streamdal.com">https://streamdal.com</a><p>And here's a live demo: <a href="https://demo.streamdal.com">https://demo.streamdal.com</a> (github repo has an explanation of the demo)<p>— — —<p>THE PROBLEM<p>We built this because the current observability tooling is not able to provide real-time insight into the actual data that your software is reading or writing. Meaning that it takes longer to identify issues and longer to resolve them. That’s time, money, and customer satisfaction at stake.<p>Want to build something in-house? Prepare to deploy a team, spend months of development time, and tons of money bringing it to production. Then be ready to have engineers around to babysit your new monitoring tool instead of working on your product.<p>— — —<p>THE BASIC FLOW<p>So, wtf is a “tail -f for your data”. What we mean is this:<p>1. We give you an SDK for your language, a server, and a UI.<p>2. You instrument your code with <i>`StreamdalSDK.Process(yourData)`</i> anytime you read or write data in your app.<p>3. You deploy your app/service.<p>4. Go to the provided UI (or run the CLI app) and be able to peek into what your app is reading or writing, like with <i>`tail -f`</i>.<p>And that's basically it. There's a bunch more functionality in the project but we find this to be the most immediately useful part. Every developer we've shown this to has said "I wish I had this at my gig at $company" - and we feel exactly the same. We are devs and this is what we’ve always wanted, hundreds of times - a way to just quickly look at the data our software is producing in real-time, without having to jump through any hoops.<p><i>If you want to learn more about the "why" and the origin of this project - you can read about it here: <a href="https://streamdal.com/manifesto">https://streamdal.com/manifesto</a></i><p>— — —<p>HOW DOES IT WORK?<p>The SDK establishes a long-running session with the server (using gRPC) and "listens" for commands that are forwarded to it all the way from the <i>UI -> server -> SDK</i>.<p>The commands are things like: <i>"show me the data that you are currently consuming"</i>, <i>"apply these rules to all data that you produce"</i>, <i>"inspect the schema for all data"</i>, and so on.<p>The SDK interprets the command and either executes Wasm-based rules against the data it's processing or if it's a <i>`tail`</i> request - it'll send the data to the server, which will forward it to the UI for display.<p>The SDK <i>IS</i> part of the critical path but it does not have a dependency on the server. If the server is gone, you won't be able to use the UI or send commands to the SDKs, but that's about it - the SDKs will continue to work and attempt to reconnect to the server behind the scenes.<p>— — —<p>TECHNICAL BITS<p>The project consists of a lot of "buzzwordy" tech: we use gRPC, grpc-Web, protobuf, redis, Wasm, Deno, ReactFlow, and probably a few other things.<p>The server is written in Go, all of the Wasm is Rust and the UI is Typescript. There are SDKs for Go, Python, and Node. We chose these languages for the SDKs because we've been working in them daily for the past 10+ years.<p><i>The reasons for the tech choices are explained in detail here:</i> <a href="https://docs.streamdal.com/en/resources-support/open-source/">https://docs.streamdal.com/en/resources-support/open-source/</a><p>— — —<p>LAST PART<p>OK, that's it. What do you think? Is it useful? Can we answer anything?<p>- If you like what you're seeing, give our repo a star: <a href="https://github.com/streamdal/streamdal">https://github.com/streamdal/streamdal</a><p>- And If you <i>really</i> like what you're seeing, come talk to us on our discord: <a href="https://discord.gg/streamdal" rel="nofollow noreferrer">https://discord.gg/streamdal</a><p>Talk soon!<p>- Daniel & Ustin

Show HN: Formbricks – Open-source alternative to Typeform and Sprig

Show HN: Formbricks – Open-source alternative to Typeform and Sprig

Show HN: MicroTCP, a minimal TCP/IP stack

Show HN: MicroTCP, a minimal TCP/IP stack

Show HN: MicroTCP, a minimal TCP/IP stack

Show HN: MicroTCP, a minimal TCP/IP stack

< 1 2 3 ... 325 326 327 328 329 ... 852 853 854 >