The best Hacker News stories from Show from the past day

from

All Show

from the past*

day week month

with these search terms:

Create follow Go back

Latest posts:

Show HN: Nudges.fyi – simple, unmissable reminders via phone/text/email

I built this app primarily for my wife, who has tried many mainstream todo-list apps (OmniFocus, Things, and Todoist come to mind) over the years with little success. She isn't particularly interested in setting up a productivity system and the administrivia that goes with it. Even having to remember to look at an app once a day was far from ideal for her. This app is an attempt at a solution for anyone that fits this description, with a focus on alerting over organization.<p>Here's how it works: you create a nudge that's set to trigger at a given date and time, and the app phones you, texts you, or emails you (or all three) at the right moment. Nudges can trigger on a schedule, so something like "call me about monthly bills for the next month on the last day of every month" is quite easy to set up. It also works well (sample size 1, admittedly) as a supplement to a more robust GTD system. I use Things for almost everything, but my most important reminders are set up as nudges.<p>I've worked on this on and off for the last month or so and I think it's ready for a Show HN. There's likely some rough edges in there so I wouldn't use it for anything _critical_ just yet (let me know if you see anything that looks buggy!). I cut a lot of scope in order to release an initial version quickly; here's a list of things I'm considering adding to the app in the near future:<p><pre><code> - Implement something analogous to Pagerduty: create nudges that repeatedly nag you (with something like an escalation policy) until you acknowledge them - More notification channels: get nudges on Telegram, WhatsApp, Slack, etc. - Families (or teams, possibly) share a namespace and can send nudges to each other - Nudges that collect a response: possibly for polls, a daily diary entry, or habit tracker - Incoming and outgoing webhooks - Snooze a nudge so it re-triggers in X minutes </code></pre> I work on distributed systems at my day job and haven't done frontend and CRUD things in a long while now, so building this out was a nice change of pace. If anyone's curious, the app is built with: Next.js (in static HTML mode) and Tailwind for the frontend, Go for the API server and background nudge loop, and SQLite (+Litestream) for persistence.<p>In any case, I'm looking for feedback from the HN community here: is this something you would use?<p>TL;DR: schedule reminders for yourself via phone call, text message, and/or email<p>(PS: the free plan doesn't allow call/SMS nudges because I'm a bit wary of spam, but if you'd like to give this a shot and can't [or don't want to] subscribe to a paid plan at this point, send me an email at tim@nudges.fyi for a 1-month code)

Show HN: Nudges.fyi – simple, unmissable reminders via phone/text/email

I built this app primarily for my wife, who has tried many mainstream todo-list apps (OmniFocus, Things, and Todoist come to mind) over the years with little success. She isn't particularly interested in setting up a productivity system and the administrivia that goes with it. Even having to remember to look at an app once a day was far from ideal for her. This app is an attempt at a solution for anyone that fits this description, with a focus on alerting over organization.<p>Here's how it works: you create a nudge that's set to trigger at a given date and time, and the app phones you, texts you, or emails you (or all three) at the right moment. Nudges can trigger on a schedule, so something like "call me about monthly bills for the next month on the last day of every month" is quite easy to set up. It also works well (sample size 1, admittedly) as a supplement to a more robust GTD system. I use Things for almost everything, but my most important reminders are set up as nudges.<p>I've worked on this on and off for the last month or so and I think it's ready for a Show HN. There's likely some rough edges in there so I wouldn't use it for anything _critical_ just yet (let me know if you see anything that looks buggy!). I cut a lot of scope in order to release an initial version quickly; here's a list of things I'm considering adding to the app in the near future:<p><pre><code> - Implement something analogous to Pagerduty: create nudges that repeatedly nag you (with something like an escalation policy) until you acknowledge them - More notification channels: get nudges on Telegram, WhatsApp, Slack, etc. - Families (or teams, possibly) share a namespace and can send nudges to each other - Nudges that collect a response: possibly for polls, a daily diary entry, or habit tracker - Incoming and outgoing webhooks - Snooze a nudge so it re-triggers in X minutes </code></pre> I work on distributed systems at my day job and haven't done frontend and CRUD things in a long while now, so building this out was a nice change of pace. If anyone's curious, the app is built with: Next.js (in static HTML mode) and Tailwind for the frontend, Go for the API server and background nudge loop, and SQLite (+Litestream) for persistence.<p>In any case, I'm looking for feedback from the HN community here: is this something you would use?<p>TL;DR: schedule reminders for yourself via phone call, text message, and/or email<p>(PS: the free plan doesn't allow call/SMS nudges because I'm a bit wary of spam, but if you'd like to give this a shot and can't [or don't want to] subscribe to a paid plan at this point, send me an email at tim@nudges.fyi for a 1-month code)

Show HN: Nudges.fyi – simple, unmissable reminders via phone/text/email

I built this app primarily for my wife, who has tried many mainstream todo-list apps (OmniFocus, Things, and Todoist come to mind) over the years with little success. She isn't particularly interested in setting up a productivity system and the administrivia that goes with it. Even having to remember to look at an app once a day was far from ideal for her. This app is an attempt at a solution for anyone that fits this description, with a focus on alerting over organization.<p>Here's how it works: you create a nudge that's set to trigger at a given date and time, and the app phones you, texts you, or emails you (or all three) at the right moment. Nudges can trigger on a schedule, so something like "call me about monthly bills for the next month on the last day of every month" is quite easy to set up. It also works well (sample size 1, admittedly) as a supplement to a more robust GTD system. I use Things for almost everything, but my most important reminders are set up as nudges.<p>I've worked on this on and off for the last month or so and I think it's ready for a Show HN. There's likely some rough edges in there so I wouldn't use it for anything _critical_ just yet (let me know if you see anything that looks buggy!). I cut a lot of scope in order to release an initial version quickly; here's a list of things I'm considering adding to the app in the near future:<p><pre><code> - Implement something analogous to Pagerduty: create nudges that repeatedly nag you (with something like an escalation policy) until you acknowledge them - More notification channels: get nudges on Telegram, WhatsApp, Slack, etc. - Families (or teams, possibly) share a namespace and can send nudges to each other - Nudges that collect a response: possibly for polls, a daily diary entry, or habit tracker - Incoming and outgoing webhooks - Snooze a nudge so it re-triggers in X minutes </code></pre> I work on distributed systems at my day job and haven't done frontend and CRUD things in a long while now, so building this out was a nice change of pace. If anyone's curious, the app is built with: Next.js (in static HTML mode) and Tailwind for the frontend, Go for the API server and background nudge loop, and SQLite (+Litestream) for persistence.<p>In any case, I'm looking for feedback from the HN community here: is this something you would use?<p>TL;DR: schedule reminders for yourself via phone call, text message, and/or email<p>(PS: the free plan doesn't allow call/SMS nudges because I'm a bit wary of spam, but if you'd like to give this a shot and can't [or don't want to] subscribe to a paid plan at this point, send me an email at tim@nudges.fyi for a 1-month code)

Show HN: Open Source Authentication and Authorization

I’m Rishabh and the co-founder and CTO at <a href="https://supertokens.com" rel="nofollow">https://supertokens.com</a> (YC S20). We offer open-source user authentication and we just released our user roles product for companies implementing authorization.<p>Our users are web developers, and a prominent and adjacent pain point for our users is authorization. Developers typically implement two independent solutions for authentication and authorization. Offering AuthN and AuthZ in a single solution is something we’ve been thinking about for the last few years.<p>Quick primer, authentication is knowing who the user is, and authorization is knowing what the user has access to. A physical analogy: A person enters a building. Authentication means reading their ID card and knowing that the person’s name is John. Authorization means knowing which floors, offices, and files John has access to.<p>With increasing privacy and data complexity, companies like Netflix[1], Slack[2], and Airbnb[3] have built out their own complex authorization systems.<p>To build our user roles product, we started with a first principles approach of covering authorization use cases using scripting languages such as XACML and OPA. But looking at existing solutions built by talented teams like Oso[4], Aserto[5], Cerbos[6], Strya[7], we realized that while these were powerful solutions, they were often overkill for most early to mid-stage companies (especially on the B2C side).<p>We went back to the drawing board, reached out to our users and after dozens of conversations, we realized that most authorization needs require the ability to<p>1. Assign and manage roles and permissions<p>2. Store roles in the DB and session tokens to make it readable on the frontend and<p>3. Protect APIs and websites based on these roles and permissions.<p>And so, we built user roles – a simple RBAC authorization service that focuses on the balance between simplicity and utility. It doesn’t cover many complex cases and we’re not looking to displace any of the authorization incumbents. But you can add AuthN and AuthZ using a single solution, quickly.<p>In the near future, we’ll be launching an admin GUI where you can manage your users and their roles with a few clicks.<p>We’d love for you to try it out and hear what additional functionality you’d like to see. What are your favorite authentication providers and what do they get right?<p>- [1]: <a href="https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.oreillystatic.com/en/assets/1/event/270/The distributed authorization system_ A Netflix case study Presentation.pdf" rel="nofollow">https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.orei...</a><p>- [2]: <a href="https://slack.engineering/role-management-at-slack/" rel="nofollow">https://slack.engineering/role-management-at-slack/</a><p>- [3]: <a href="https://medium.com/airbnb-engineering/himeji-a-scalable-centralized-system-for-authorization-at-airbnb-341664924574" rel="nofollow">https://medium.com/airbnb-engineering/himeji-a-scalable-cent...</a><p>- [4]: <a href="https://www.osohq.com/" rel="nofollow">https://www.osohq.com/</a><p>- [5]: <a href="https://www.aserto.com/" rel="nofollow">https://www.aserto.com/</a><p>- [6]: <a href="https://cerbos.dev/" rel="nofollow">https://cerbos.dev/</a><p>- [7]: <a href="https://www.styra.com/" rel="nofollow">https://www.styra.com/</a>

Show HN: Open Source Authentication and Authorization

I’m Rishabh and the co-founder and CTO at <a href="https://supertokens.com" rel="nofollow">https://supertokens.com</a> (YC S20). We offer open-source user authentication and we just released our user roles product for companies implementing authorization.<p>Our users are web developers, and a prominent and adjacent pain point for our users is authorization. Developers typically implement two independent solutions for authentication and authorization. Offering AuthN and AuthZ in a single solution is something we’ve been thinking about for the last few years.<p>Quick primer, authentication is knowing who the user is, and authorization is knowing what the user has access to. A physical analogy: A person enters a building. Authentication means reading their ID card and knowing that the person’s name is John. Authorization means knowing which floors, offices, and files John has access to.<p>With increasing privacy and data complexity, companies like Netflix[1], Slack[2], and Airbnb[3] have built out their own complex authorization systems.<p>To build our user roles product, we started with a first principles approach of covering authorization use cases using scripting languages such as XACML and OPA. But looking at existing solutions built by talented teams like Oso[4], Aserto[5], Cerbos[6], Strya[7], we realized that while these were powerful solutions, they were often overkill for most early to mid-stage companies (especially on the B2C side).<p>We went back to the drawing board, reached out to our users and after dozens of conversations, we realized that most authorization needs require the ability to<p>1. Assign and manage roles and permissions<p>2. Store roles in the DB and session tokens to make it readable on the frontend and<p>3. Protect APIs and websites based on these roles and permissions.<p>And so, we built user roles – a simple RBAC authorization service that focuses on the balance between simplicity and utility. It doesn’t cover many complex cases and we’re not looking to displace any of the authorization incumbents. But you can add AuthN and AuthZ using a single solution, quickly.<p>In the near future, we’ll be launching an admin GUI where you can manage your users and their roles with a few clicks.<p>We’d love for you to try it out and hear what additional functionality you’d like to see. What are your favorite authentication providers and what do they get right?<p>- [1]: <a href="https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.oreillystatic.com/en/assets/1/event/270/The distributed authorization system_ A Netflix case study Presentation.pdf" rel="nofollow">https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.orei...</a><p>- [2]: <a href="https://slack.engineering/role-management-at-slack/" rel="nofollow">https://slack.engineering/role-management-at-slack/</a><p>- [3]: <a href="https://medium.com/airbnb-engineering/himeji-a-scalable-centralized-system-for-authorization-at-airbnb-341664924574" rel="nofollow">https://medium.com/airbnb-engineering/himeji-a-scalable-cent...</a><p>- [4]: <a href="https://www.osohq.com/" rel="nofollow">https://www.osohq.com/</a><p>- [5]: <a href="https://www.aserto.com/" rel="nofollow">https://www.aserto.com/</a><p>- [6]: <a href="https://cerbos.dev/" rel="nofollow">https://cerbos.dev/</a><p>- [7]: <a href="https://www.styra.com/" rel="nofollow">https://www.styra.com/</a>

Show HN: Open Source Authentication and Authorization

I’m Rishabh and the co-founder and CTO at <a href="https://supertokens.com" rel="nofollow">https://supertokens.com</a> (YC S20). We offer open-source user authentication and we just released our user roles product for companies implementing authorization.<p>Our users are web developers, and a prominent and adjacent pain point for our users is authorization. Developers typically implement two independent solutions for authentication and authorization. Offering AuthN and AuthZ in a single solution is something we’ve been thinking about for the last few years.<p>Quick primer, authentication is knowing who the user is, and authorization is knowing what the user has access to. A physical analogy: A person enters a building. Authentication means reading their ID card and knowing that the person’s name is John. Authorization means knowing which floors, offices, and files John has access to.<p>With increasing privacy and data complexity, companies like Netflix[1], Slack[2], and Airbnb[3] have built out their own complex authorization systems.<p>To build our user roles product, we started with a first principles approach of covering authorization use cases using scripting languages such as XACML and OPA. But looking at existing solutions built by talented teams like Oso[4], Aserto[5], Cerbos[6], Strya[7], we realized that while these were powerful solutions, they were often overkill for most early to mid-stage companies (especially on the B2C side).<p>We went back to the drawing board, reached out to our users and after dozens of conversations, we realized that most authorization needs require the ability to<p>1. Assign and manage roles and permissions<p>2. Store roles in the DB and session tokens to make it readable on the frontend and<p>3. Protect APIs and websites based on these roles and permissions.<p>And so, we built user roles – a simple RBAC authorization service that focuses on the balance between simplicity and utility. It doesn’t cover many complex cases and we’re not looking to displace any of the authorization incumbents. But you can add AuthN and AuthZ using a single solution, quickly.<p>In the near future, we’ll be launching an admin GUI where you can manage your users and their roles with a few clicks.<p>We’d love for you to try it out and hear what additional functionality you’d like to see. What are your favorite authentication providers and what do they get right?<p>- [1]: <a href="https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.oreillystatic.com/en/assets/1/event/270/The distributed authorization system_ A Netflix case study Presentation.pdf" rel="nofollow">https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.orei...</a><p>- [2]: <a href="https://slack.engineering/role-management-at-slack/" rel="nofollow">https://slack.engineering/role-management-at-slack/</a><p>- [3]: <a href="https://medium.com/airbnb-engineering/himeji-a-scalable-centralized-system-for-authorization-at-airbnb-341664924574" rel="nofollow">https://medium.com/airbnb-engineering/himeji-a-scalable-cent...</a><p>- [4]: <a href="https://www.osohq.com/" rel="nofollow">https://www.osohq.com/</a><p>- [5]: <a href="https://www.aserto.com/" rel="nofollow">https://www.aserto.com/</a><p>- [6]: <a href="https://cerbos.dev/" rel="nofollow">https://cerbos.dev/</a><p>- [7]: <a href="https://www.styra.com/" rel="nofollow">https://www.styra.com/</a>

Show HN: Open Source Authentication and Authorization

I’m Rishabh and the co-founder and CTO at <a href="https://supertokens.com" rel="nofollow">https://supertokens.com</a> (YC S20). We offer open-source user authentication and we just released our user roles product for companies implementing authorization.<p>Our users are web developers, and a prominent and adjacent pain point for our users is authorization. Developers typically implement two independent solutions for authentication and authorization. Offering AuthN and AuthZ in a single solution is something we’ve been thinking about for the last few years.<p>Quick primer, authentication is knowing who the user is, and authorization is knowing what the user has access to. A physical analogy: A person enters a building. Authentication means reading their ID card and knowing that the person’s name is John. Authorization means knowing which floors, offices, and files John has access to.<p>With increasing privacy and data complexity, companies like Netflix[1], Slack[2], and Airbnb[3] have built out their own complex authorization systems.<p>To build our user roles product, we started with a first principles approach of covering authorization use cases using scripting languages such as XACML and OPA. But looking at existing solutions built by talented teams like Oso[4], Aserto[5], Cerbos[6], Strya[7], we realized that while these were powerful solutions, they were often overkill for most early to mid-stage companies (especially on the B2C side).<p>We went back to the drawing board, reached out to our users and after dozens of conversations, we realized that most authorization needs require the ability to<p>1. Assign and manage roles and permissions<p>2. Store roles in the DB and session tokens to make it readable on the frontend and<p>3. Protect APIs and websites based on these roles and permissions.<p>And so, we built user roles – a simple RBAC authorization service that focuses on the balance between simplicity and utility. It doesn’t cover many complex cases and we’re not looking to displace any of the authorization incumbents. But you can add AuthN and AuthZ using a single solution, quickly.<p>In the near future, we’ll be launching an admin GUI where you can manage your users and their roles with a few clicks.<p>We’d love for you to try it out and hear what additional functionality you’d like to see. What are your favorite authentication providers and what do they get right?<p>- [1]: <a href="https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.oreillystatic.com/en/assets/1/event/270/The distributed authorization system_ A Netflix case study Presentation.pdf" rel="nofollow">https://conferences.oreilly.com/velocity/vl-ca-2018/cdn.orei...</a><p>- [2]: <a href="https://slack.engineering/role-management-at-slack/" rel="nofollow">https://slack.engineering/role-management-at-slack/</a><p>- [3]: <a href="https://medium.com/airbnb-engineering/himeji-a-scalable-centralized-system-for-authorization-at-airbnb-341664924574" rel="nofollow">https://medium.com/airbnb-engineering/himeji-a-scalable-cent...</a><p>- [4]: <a href="https://www.osohq.com/" rel="nofollow">https://www.osohq.com/</a><p>- [5]: <a href="https://www.aserto.com/" rel="nofollow">https://www.aserto.com/</a><p>- [6]: <a href="https://cerbos.dev/" rel="nofollow">https://cerbos.dev/</a><p>- [7]: <a href="https://www.styra.com/" rel="nofollow">https://www.styra.com/</a>

Show HN: Sprig, open-source game console and engine, by teenagers for teenagers

Show HN: Sprig, open-source game console and engine, by teenagers for teenagers

Show HN: Sprig, open-source game console and engine, by teenagers for teenagers

Show HN: Sprig, open-source game console and engine, by teenagers for teenagers

Show HN: Sprig, open-source game console and engine, by teenagers for teenagers

Show HN: I made an open-source code snippet manager

Show HN: Wrote a tiny WebAssembly (wat2wasm) compiler in Go

As a personal project I wrote a really tiny Wat 2 Wasm compiler in Go. Mainly for demonstrative and educational purposes. It was tough: I didn't know anything about WebAssembly internals and I'm a newbie with Go... so I tried to document it as much as I could for anyone that would like to approach the quest in the future!<p>It misses a lot of features (that will be gradually implemented).<p>Any feedback is welcomed!!<p>Demo: <a href="https://luna-demo.vercel.app" rel="nofollow">https://luna-demo.vercel.app</a>

Show HN: I made a volumetric audio visualizer

I'm developing Hyperstep[0], a spatial language for music production. I find using existing DAWs frustrating because they don't allow me to navigate and operate intuitively on the latent spaces behind my musical ideas. This is why I've decided to build my own set of "seeing tools".(Bret Victor)[1]. I'm also convinced that by framing music as processes and interactions in the 3D world, spatialization and mixing should become fairly pain-free.<p>I'm still early in development and I would love to build this into an actual product that can be integrated into existing DAWs or even turn it into a musical framework itself for AR and VR experiences.<p>If you're interested in working on it or if you simply want to know more, feel free to contact me.<p>[0] <a href="https://github.com/a-sumo/hyperstep" rel="nofollow">https://github.com/a-sumo/hyperstep</a>.<p>[1] <a href="https://www.youtube.com/watch?v=klTjiXjqHrQ" rel="nofollow">https://www.youtube.com/watch?v=klTjiXjqHrQ</a>

Show HN: I made a volumetric audio visualizer

I'm developing Hyperstep[0], a spatial language for music production. I find using existing DAWs frustrating because they don't allow me to navigate and operate intuitively on the latent spaces behind my musical ideas. This is why I've decided to build my own set of "seeing tools".(Bret Victor)[1]. I'm also convinced that by framing music as processes and interactions in the 3D world, spatialization and mixing should become fairly pain-free.<p>I'm still early in development and I would love to build this into an actual product that can be integrated into existing DAWs or even turn it into a musical framework itself for AR and VR experiences.<p>If you're interested in working on it or if you simply want to know more, feel free to contact me.<p>[0] <a href="https://github.com/a-sumo/hyperstep" rel="nofollow">https://github.com/a-sumo/hyperstep</a>.<p>[1] <a href="https://www.youtube.com/watch?v=klTjiXjqHrQ" rel="nofollow">https://www.youtube.com/watch?v=klTjiXjqHrQ</a>

Show HN: Docker in the browser using x86-to-WASM recompilation

Show HN: Tier.run – Terraform for Stripe

Hi HN, we are Jevon, Blake and Isaac, we've been working on Tier for a little while ( <a href="http://github.com/tierrun/tier" rel="nofollow">http://github.com/tierrun/tier</a> )<p>Tier is "Terraform for Stripe" but it goes further and gives you feature flag style access checks, and allows you to count/report usage which can be used for metered billing.<p>When we started Tier, we knew that there was something interesting in the SaaS pricing and packaging space. Adjusting price is the single most effective lever a business can use to achieve product/market fit, and there's a strong correlation price nimbleness and market success.<p>In spite of overwhelming evidence of this, most startups pick the price for their product once and then never change it, opting instead to invest in less effective levers like CAC, sales efficiency, "virality", churn, etc. Why?<p>It's just too hard. Any change you make to the pricing model means refactoring not just the entire product, but sometimes the entire <i>company</i>. The path of least resistance leads to a place where there's no single source of truth, and changes anywhere require changes everywhere.After over 50 or so customer conversations and user research chats, this represents our third or fourth implementation (depending on how you count them), and our conception of how best to solve it has been refined and adjusted along the way.<p>The concept of "PriceOps" came out of those conversations, looking at where mature companies end up after several expensive rounds of iterating on how they implement their prices for flexibility and order. <a href="https://priceops.org" rel="nofollow">https://priceops.org</a><p>What we're releasing now is an open source tool you can use to set up your Stripe system that keeps everything organized around a single source of truth. With this, changes to your pricing model don't require changes to your application code or business processes.<p>As a bonus, I think it's actually easier to integrate with than integrating with Stripe the "normal" way. Use the identifiers for your customers and features that you already have. Define plans and subscribe customers to them. No ever-growing pile of object ids to manage.<p>If you are just starting to think about adding pricing to your product, or if you've built something custom but would like something less maintenance intensive, then please give Tier a try and we'd love your feedback.

Show HN: Tier.run – Terraform for Stripe

Hi HN, we are Jevon, Blake and Isaac, we've been working on Tier for a little while ( <a href="http://github.com/tierrun/tier" rel="nofollow">http://github.com/tierrun/tier</a> )<p>Tier is "Terraform for Stripe" but it goes further and gives you feature flag style access checks, and allows you to count/report usage which can be used for metered billing.<p>When we started Tier, we knew that there was something interesting in the SaaS pricing and packaging space. Adjusting price is the single most effective lever a business can use to achieve product/market fit, and there's a strong correlation price nimbleness and market success.<p>In spite of overwhelming evidence of this, most startups pick the price for their product once and then never change it, opting instead to invest in less effective levers like CAC, sales efficiency, "virality", churn, etc. Why?<p>It's just too hard. Any change you make to the pricing model means refactoring not just the entire product, but sometimes the entire <i>company</i>. The path of least resistance leads to a place where there's no single source of truth, and changes anywhere require changes everywhere.After over 50 or so customer conversations and user research chats, this represents our third or fourth implementation (depending on how you count them), and our conception of how best to solve it has been refined and adjusted along the way.<p>The concept of "PriceOps" came out of those conversations, looking at where mature companies end up after several expensive rounds of iterating on how they implement their prices for flexibility and order. <a href="https://priceops.org" rel="nofollow">https://priceops.org</a><p>What we're releasing now is an open source tool you can use to set up your Stripe system that keeps everything organized around a single source of truth. With this, changes to your pricing model don't require changes to your application code or business processes.<p>As a bonus, I think it's actually easier to integrate with than integrating with Stripe the "normal" way. Use the identifiers for your customers and features that you already have. Define plans and subscribe customers to them. No ever-growing pile of object ids to manage.<p>If you are just starting to think about adding pricing to your product, or if you've built something custom but would like something less maintenance intensive, then please give Tier a try and we'd love your feedback.

Show HN: Minimax – A Compressed-First, Microcoded RISC-V CPU

RISC-V's compressed instruction (RVC) extension is intended as an add-on to the regular, 32-bit instruction set, not a replacement or competitor. Its designers intended RVC instructions to be expanded into regular 32-bit RV32I equivalents via a pre-decoder.<p>What happens if we explicitly architect a RISC-V CPU to execute RVC instructions, and "mop up" any RV32I instructions that aren't convenient via a microcode layer? What architectural optimizations are unlocked as a result?<p>"Minimax" is an experimental RISC-V implementation intended to establish if an RVC-optimized CPU is, in practice, any simpler than an ordinary RV32I core with pre-decoder. While it passes a modest test suite, you should not use it without caution. (There are a large number of excellent, open source, "little" RISC-V implementations you should probably use reach for first.)