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: Fruits – Sell digital products via your website, newsletter, etc

Hi HN!<p>Whilst trying to build an online community for content creators, we failed! Taking the learnings and stripping down our product to a true MVP, we now started working on "fruits", which allows creators to sell files such as ebooks, designs, checklists, music and online coachings online in less than two minutes.<p><a href="https://fruits.de/en" rel="nofollow">https://fruits.de/en</a><p>It works as simple as this:<p>1. upload a file at "fruits" & set a price 2. you will receive your individual fruits-sales-link 3. share the link wherever your customers are (e.g. website, newsletter, social media)<p>In addition, we also take care of the tedious office work such as invoicing and VAT collection for you, and this is completely automated.<p>What do you think? We are looking forward to your feedback!

Show HN: Fruits – Sell digital products via your website, newsletter, etc

Hi HN!<p>Whilst trying to build an online community for content creators, we failed! Taking the learnings and stripping down our product to a true MVP, we now started working on "fruits", which allows creators to sell files such as ebooks, designs, checklists, music and online coachings online in less than two minutes.<p><a href="https://fruits.de/en" rel="nofollow">https://fruits.de/en</a><p>It works as simple as this:<p>1. upload a file at "fruits" & set a price 2. you will receive your individual fruits-sales-link 3. share the link wherever your customers are (e.g. website, newsletter, social media)<p>In addition, we also take care of the tedious office work such as invoicing and VAT collection for you, and this is completely automated.<p>What do you think? We are looking forward to your feedback!

Show HN: A Full-Stack Web Framework for Go

Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!

Show HN: A Full-Stack Web Framework for Go

Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!

Show HN: A Full-Stack Web Framework for Go

Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!

Show HN: A Full-Stack Web Framework for Go

Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!

Show HN: A Full-Stack Web Framework for Go

Hey HN! I want to share my side project with you. It's called Bud and it's a full-stack web framework for Go.<p>I created a short video to show you how to create a minimal Hacker News clone with Bud: <a href="https://www.youtube.com/watch?v=LoypcRqn-xA" rel="nofollow">https://www.youtube.com/watch?v=LoypcRqn-xA</a>.<p>The framework is free, open source and MIT Licensed. You can find it on Github: <a href="https://github.com/livebud/bud" rel="nofollow">https://github.com/livebud/bud</a>.<p>I started working on Bud 2 years ago after watching the introductory Laracast videos about the Laravel web framework. I was just blown away by how productive you can be in Laravel. However, like many of you, I've been so spoiled by Go. I didn't want to go back to writing PHP, so I decided to try creating Laravel for the Go ecosystem.<p>At this point, I just had the following goal:<p>• Be as productive as Laravel in a typed language like Go.<p>I got the first version working in 6 months and tried building a blog from it... It fell flat. You needed to scaffold all these files just to get started. If you're coming from Rails or Laravel you may shrug, this is pretty normal. Unfortunately, I've also been spoiled by the renaissance in frontend frameworks like Next.js. What I love about Next is that it starts out barebones and every file you add incrementally enhances your web application. This keeps the initial complexity under control.<p>With these newly discovered constraints, I started working on the next iteration. Bud should:<p>• Generate files only as you need them. Keep these generated files away from your application code and give developers the choice to keep them out of source control.<p>• Feel like using a modern JS framework. This means it should work with modern frontend frameworks like Svelte and React, support live reload and have server-side rendering for better performance and SEO.<p>With these new goals, the Bud you see today started to take shape. But along the way, I discovered a few more project goals:<p>• The framework should be extensible from Day 1. Bud is too ambitious for one person. We're going to need an ambitious community behind this framework.<p>• Bud should be able to provide high-level APIs for developers while compiling down to performant low-level Go code for production.<p>• Bud should compile to a single binary. With platforms like Fly.io and Heroku, these days it's easy to not care about this, but I still cherish the idea that I can build a single binary that contains my entire web app and secure copy it up to a tiny server that doesn't even have Go installed.<p>It's still super early days. You can find the the Roadmap on Github: <a href="https://github.com/livebud/bud/discussions/9" rel="nofollow">https://github.com/livebud/bud/discussions/9</a>. I encourage you to contribute your thoughts.<p>And here's the current documentation for what's already in Bud: <a href="https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f9917c5033e5205c69" rel="nofollow">https://denim-cub-301.notion.site/Hey-Bud-4d81622cc49942f991...</a>. Comments are enabled for anyone to chime in.<p>I have big plans for the framework. I hope you'll join me on this journey to build ambitious websites faster with Go!

Show HN: A Visual IDE for React

I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!

Show HN: A Visual IDE for React

I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!

Show HN: A Visual IDE for React

I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!

Show HN: A Visual IDE for React

I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!

Show HN: A Visual IDE for React

I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!

Show HN: YouCode, a Search Engine for Coding

Hi Hacker News,<p>We're Bryan and Richard, cofounders of you.com. Together with our team of engineers, we are working on YouCode, a search engine for people who code. You can try it at code.you.com. The main idea is to make the search experience better and more efficient when coding. We’d love your feedback for a few use cases that we have in mind so far:<p>* searching through StackOverflow for quick code snippets: reverting a git commit for example [1]<p>* searching through GitHub Issues: when you’re getting an error message that looks unfamiliar [2, 3]<p>* searching through the documentation for quick reference: PyTorch [4], HuggingFace [5], Docker, PyPi, AWS, MDN, and several others<p>* searching for walkthroughs, tutorials, tips, and quick intros to a new subject: Medium [6], Tutorials Point, Geeks for Geeks, and others as well<p>* searching for utilities: code completion (from a large language model that writes code) [7], JSON validator/formatter [8]<p>* searching for relevant discussions and projects: HackerNews [9], ArXiv [10], Github Repos [11]<p>* changing preferences in the account dropdown menu so that you can influence which sources you get answers from<p>* doing all of this from VS Code: we made an extension to make that easier [12]<p>YouCode is still a work in progress — we’re adding new apps each week and improving the search results — and we would love your feedback. Where do Google or other search engines leave you wanting more when it comes to coding searches? Which sources do you go to when you can’t get what you need from Google and others? What other utilities and use cases would you like to see? How else can we make this better?<p>If you find something that we can improve, apps that you’d want to see, or a search query didn’t give you a good result, please let us know! We’re here to answer any questions!<p>Richard and Bryan<p>[1] <a href="https://code.you.com/search?q=revert+a+git+commit" rel="nofollow">https://code.you.com/search?q=revert+a+git+commit</a><p>[2] <a href="https://code.you.com/search?q=MLflowCallback+to+log+run_name+argument" rel="nofollow">https://code.you.com/search?q=MLflowCallback+to+log+run_name...</a><p>[3] <a href="https://code.you.com/search?q=onnxruntime+segfault" rel="nofollow">https://code.you.com/search?q=onnxruntime+segfault</a><p>[4] <a href="https://code.you.com/search?q=pytorch+isnan" rel="nofollow">https://code.you.com/search?q=pytorch+isnan</a><p>[5] <a href="https://code.you.com/search?q=huggingface+transformers" rel="nofollow">https://code.you.com/search?q=huggingface+transformers</a><p>[6] <a href="https://code.you.com/search?q=git+rebase+interactive" rel="nofollow">https://code.you.com/search?q=git+rebase+interactive</a><p>[7] <a href="https://code.you.com/search?q=#+this+function+sorts+a+list+in+ascending+order+code+complete" rel="nofollow">https://code.you.com/search?q=#+this+function+sorts+a+list...</a><p>[8] <a href="https://code.you.com/search?q=json+validator" rel="nofollow">https://code.you.com/search?q=json+validator</a><p>[9] <a href="https://code.you.com/search?q=show+hn" rel="nofollow">https://code.you.com/search?q=show+hn</a><p>[10] <a href="https://code.you.com/search?q=attention+is+all+you+need" rel="nofollow">https://code.you.com/search?q=attention+is+all+you+need</a><p>[11] <a href="https://code.you.com/search?q=pytorch+examples" rel="nofollow">https://code.you.com/search?q=pytorch+examples</a><p>[12] <a href="https://marketplace.visualstudio.com/items?itemName=youdotcom.YouCode" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=youdotco...</a>

Swimlanes for Trello

Show HN: I built a service to help companies reduce AWS spend by 50%

Hey HN: Kaveh here, the founder of https://www.usage.ai/<p>We help companies drive down AWS EC2 spend. Why? Because the way it's done now is a pain. DevOps engineers end up becoming cloud accountants trying to figure out what commitments are expiring soon and how much they're saving.<p>Previous to founding Usage, I worked on high-performance computing research at JP Morgan Chase and as a software engineer at a number of medium-sized startups.<p>Here's how it works: We are typically brought in by a DevOps manager to cut AWS EC2 costs. The app is entirely self-service and the savings are generated automatically, typically we do this live on a call. On average, we reduce AWS EC2 spend by 57% for 5 minutes of work.<p>To reduce by ~57%, we don't touch the instances, require any code change, or change the performance of your instances. We buy Reserved Instances on your behalf (a billing layer change only) and bundle them with guaranteed buyback. So you get the steep 57% savings of 3-year no-upfront RIs with none of the commitment (you can sell them back to us anytime after 30 days).<p>We make money off a 20% Savings Fee. Happy to chat directly kaveh@usage.ai<p>Have you experienced any issues with managing your company or organization's AWS expenses? We'd love to hear your feedback and ideas!

Show HN: Paperd.ink – an open-source e-paper development board

paperd.ink (<a href="https://paperd.ink" rel="nofollow">https://paperd.ink</a>) is an open-source e-paper development board. We wanted to build something with e-paper given its low-power nature and beautiful, high contrast display which complements your environment and is easy on the eye. Thus, we started working on something to be developed along the lines of Arduino, Raspberry Pi’s open-source ecosystem.<p>paperd.ink has a 4.2” e-paper display comes mounted on the PCB which we have designed to be a general-purpose development board suitable for your projects and applications. You can sync calendars, set up your home IoT dashboard, get to-do lists, and notifications, display art, etc. We have used an ESP32-based microcontroller with WiFi, Bluetooth, and microUSB connectivity. The board can be programmed in Arduino IDE, micropython, or ESP-IDF, you can check out the documentation at docs.paperd.ink. paperd.ink is designed to be low power so you can charge the battery once and go on for months on it depending on the refresh rate. It’s suitable to display low to medium latency or static information. Every paperd.ink comes with a hand-polished, 3D-printed external enclosure.<p>The first paperd.ink prototype was first posted on Show HN (<a href="https://news.ycombinator.com/item?id=22340398" rel="nofollow">https://news.ycombinator.com/item?id=22340398</a>) and other related communities (Reddit, Hackaday, etc) a little more than 2 years ago. We had a landing page, a short video of the prototype, and a user survey form asking a couple of questions along with a “Would you like to be a part of the waitlist?” question in the end. We got quite an interest from everyone on it so we decided to move ahead.<p>After receiving a positive response to the prototype, the next step was to figure out how to actually bring the product to the real world. We had no upfront capital required for manufacturing so we decided to do a crowdfunding campaign (finding a platform supporting our country India was another issue). At the same time, the pandemic happened which delayed everything because of unfeasible component prices, supply chain issues, and lockdowns everywhere. After researching thoroughly and formulating a production plan and figuring out unit economics, we launched the crowdfunding campaign roughly last year and had the 2nd Show HN post (<a href="https://news.ycombinator.com/item?id=27331311" rel="nofollow">https://news.ycombinator.com/item?id=27331311</a>). In the course of promoting the campaign, we got in contact with FOSS United which is a non-profit foundation that aims at promoting and strengthening the Free and Open Source Software (FOSS) ecosystem in India. FOSS United offered us a grant and that’s how we survived despite failing to achieve our crowdfunding target goal (we had ~40%).<p>After accepting the grant, we tweaked the PCB a bit and redesigned the external enclosure to make it ready for production. Scouted for manufacturers, suppliers, and shipping agents. Samples were ordered and tested. Test criteria and SOPs were exchanged. Vacuum casting (or any other method of manufacturing) of the enclosures was out of the question given the high NRE cost and high quantity needed to be manufactured, so we 3D printed them. Finally, the first batch was ready in the inventory to be shipped. All the orders received until now have been shipped and users should start receiving them shortly. Thanks to the HN community and our early supporters for everything. And special thanks to Daniel (moderator) for helping with the post. We plan to get feedback on the first batch and then decide on how to move forward. Please feel free to ask any questions!

Show HN: Paperd.ink – an open-source e-paper development board

paperd.ink (<a href="https://paperd.ink" rel="nofollow">https://paperd.ink</a>) is an open-source e-paper development board. We wanted to build something with e-paper given its low-power nature and beautiful, high contrast display which complements your environment and is easy on the eye. Thus, we started working on something to be developed along the lines of Arduino, Raspberry Pi’s open-source ecosystem.<p>paperd.ink has a 4.2” e-paper display comes mounted on the PCB which we have designed to be a general-purpose development board suitable for your projects and applications. You can sync calendars, set up your home IoT dashboard, get to-do lists, and notifications, display art, etc. We have used an ESP32-based microcontroller with WiFi, Bluetooth, and microUSB connectivity. The board can be programmed in Arduino IDE, micropython, or ESP-IDF, you can check out the documentation at docs.paperd.ink. paperd.ink is designed to be low power so you can charge the battery once and go on for months on it depending on the refresh rate. It’s suitable to display low to medium latency or static information. Every paperd.ink comes with a hand-polished, 3D-printed external enclosure.<p>The first paperd.ink prototype was first posted on Show HN (<a href="https://news.ycombinator.com/item?id=22340398" rel="nofollow">https://news.ycombinator.com/item?id=22340398</a>) and other related communities (Reddit, Hackaday, etc) a little more than 2 years ago. We had a landing page, a short video of the prototype, and a user survey form asking a couple of questions along with a “Would you like to be a part of the waitlist?” question in the end. We got quite an interest from everyone on it so we decided to move ahead.<p>After receiving a positive response to the prototype, the next step was to figure out how to actually bring the product to the real world. We had no upfront capital required for manufacturing so we decided to do a crowdfunding campaign (finding a platform supporting our country India was another issue). At the same time, the pandemic happened which delayed everything because of unfeasible component prices, supply chain issues, and lockdowns everywhere. After researching thoroughly and formulating a production plan and figuring out unit economics, we launched the crowdfunding campaign roughly last year and had the 2nd Show HN post (<a href="https://news.ycombinator.com/item?id=27331311" rel="nofollow">https://news.ycombinator.com/item?id=27331311</a>). In the course of promoting the campaign, we got in contact with FOSS United which is a non-profit foundation that aims at promoting and strengthening the Free and Open Source Software (FOSS) ecosystem in India. FOSS United offered us a grant and that’s how we survived despite failing to achieve our crowdfunding target goal (we had ~40%).<p>After accepting the grant, we tweaked the PCB a bit and redesigned the external enclosure to make it ready for production. Scouted for manufacturers, suppliers, and shipping agents. Samples were ordered and tested. Test criteria and SOPs were exchanged. Vacuum casting (or any other method of manufacturing) of the enclosures was out of the question given the high NRE cost and high quantity needed to be manufactured, so we 3D printed them. Finally, the first batch was ready in the inventory to be shipped. All the orders received until now have been shipped and users should start receiving them shortly. Thanks to the HN community and our early supporters for everything. And special thanks to Daniel (moderator) for helping with the post. We plan to get feedback on the first batch and then decide on how to move forward. Please feel free to ask any questions!

Show HN: Paperd.ink – an open-source e-paper development board

paperd.ink (<a href="https://paperd.ink" rel="nofollow">https://paperd.ink</a>) is an open-source e-paper development board. We wanted to build something with e-paper given its low-power nature and beautiful, high contrast display which complements your environment and is easy on the eye. Thus, we started working on something to be developed along the lines of Arduino, Raspberry Pi’s open-source ecosystem.<p>paperd.ink has a 4.2” e-paper display comes mounted on the PCB which we have designed to be a general-purpose development board suitable for your projects and applications. You can sync calendars, set up your home IoT dashboard, get to-do lists, and notifications, display art, etc. We have used an ESP32-based microcontroller with WiFi, Bluetooth, and microUSB connectivity. The board can be programmed in Arduino IDE, micropython, or ESP-IDF, you can check out the documentation at docs.paperd.ink. paperd.ink is designed to be low power so you can charge the battery once and go on for months on it depending on the refresh rate. It’s suitable to display low to medium latency or static information. Every paperd.ink comes with a hand-polished, 3D-printed external enclosure.<p>The first paperd.ink prototype was first posted on Show HN (<a href="https://news.ycombinator.com/item?id=22340398" rel="nofollow">https://news.ycombinator.com/item?id=22340398</a>) and other related communities (Reddit, Hackaday, etc) a little more than 2 years ago. We had a landing page, a short video of the prototype, and a user survey form asking a couple of questions along with a “Would you like to be a part of the waitlist?” question in the end. We got quite an interest from everyone on it so we decided to move ahead.<p>After receiving a positive response to the prototype, the next step was to figure out how to actually bring the product to the real world. We had no upfront capital required for manufacturing so we decided to do a crowdfunding campaign (finding a platform supporting our country India was another issue). At the same time, the pandemic happened which delayed everything because of unfeasible component prices, supply chain issues, and lockdowns everywhere. After researching thoroughly and formulating a production plan and figuring out unit economics, we launched the crowdfunding campaign roughly last year and had the 2nd Show HN post (<a href="https://news.ycombinator.com/item?id=27331311" rel="nofollow">https://news.ycombinator.com/item?id=27331311</a>). In the course of promoting the campaign, we got in contact with FOSS United which is a non-profit foundation that aims at promoting and strengthening the Free and Open Source Software (FOSS) ecosystem in India. FOSS United offered us a grant and that’s how we survived despite failing to achieve our crowdfunding target goal (we had ~40%).<p>After accepting the grant, we tweaked the PCB a bit and redesigned the external enclosure to make it ready for production. Scouted for manufacturers, suppliers, and shipping agents. Samples were ordered and tested. Test criteria and SOPs were exchanged. Vacuum casting (or any other method of manufacturing) of the enclosures was out of the question given the high NRE cost and high quantity needed to be manufactured, so we 3D printed them. Finally, the first batch was ready in the inventory to be shipped. All the orders received until now have been shipped and users should start receiving them shortly. Thanks to the HN community and our early supporters for everything. And special thanks to Daniel (moderator) for helping with the post. We plan to get feedback on the first batch and then decide on how to move forward. Please feel free to ask any questions!

Show HN: Paperd.ink – an open-source e-paper development board

paperd.ink (<a href="https://paperd.ink" rel="nofollow">https://paperd.ink</a>) is an open-source e-paper development board. We wanted to build something with e-paper given its low-power nature and beautiful, high contrast display which complements your environment and is easy on the eye. Thus, we started working on something to be developed along the lines of Arduino, Raspberry Pi’s open-source ecosystem.<p>paperd.ink has a 4.2” e-paper display comes mounted on the PCB which we have designed to be a general-purpose development board suitable for your projects and applications. You can sync calendars, set up your home IoT dashboard, get to-do lists, and notifications, display art, etc. We have used an ESP32-based microcontroller with WiFi, Bluetooth, and microUSB connectivity. The board can be programmed in Arduino IDE, micropython, or ESP-IDF, you can check out the documentation at docs.paperd.ink. paperd.ink is designed to be low power so you can charge the battery once and go on for months on it depending on the refresh rate. It’s suitable to display low to medium latency or static information. Every paperd.ink comes with a hand-polished, 3D-printed external enclosure.<p>The first paperd.ink prototype was first posted on Show HN (<a href="https://news.ycombinator.com/item?id=22340398" rel="nofollow">https://news.ycombinator.com/item?id=22340398</a>) and other related communities (Reddit, Hackaday, etc) a little more than 2 years ago. We had a landing page, a short video of the prototype, and a user survey form asking a couple of questions along with a “Would you like to be a part of the waitlist?” question in the end. We got quite an interest from everyone on it so we decided to move ahead.<p>After receiving a positive response to the prototype, the next step was to figure out how to actually bring the product to the real world. We had no upfront capital required for manufacturing so we decided to do a crowdfunding campaign (finding a platform supporting our country India was another issue). At the same time, the pandemic happened which delayed everything because of unfeasible component prices, supply chain issues, and lockdowns everywhere. After researching thoroughly and formulating a production plan and figuring out unit economics, we launched the crowdfunding campaign roughly last year and had the 2nd Show HN post (<a href="https://news.ycombinator.com/item?id=27331311" rel="nofollow">https://news.ycombinator.com/item?id=27331311</a>). In the course of promoting the campaign, we got in contact with FOSS United which is a non-profit foundation that aims at promoting and strengthening the Free and Open Source Software (FOSS) ecosystem in India. FOSS United offered us a grant and that’s how we survived despite failing to achieve our crowdfunding target goal (we had ~40%).<p>After accepting the grant, we tweaked the PCB a bit and redesigned the external enclosure to make it ready for production. Scouted for manufacturers, suppliers, and shipping agents. Samples were ordered and tested. Test criteria and SOPs were exchanged. Vacuum casting (or any other method of manufacturing) of the enclosures was out of the question given the high NRE cost and high quantity needed to be manufactured, so we 3D printed them. Finally, the first batch was ready in the inventory to be shipped. All the orders received until now have been shipped and users should start receiving them shortly. Thanks to the HN community and our early supporters for everything. And special thanks to Daniel (moderator) for helping with the post. We plan to get feedback on the first batch and then decide on how to move forward. Please feel free to ask any questions!

Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs