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: #!/usr/bin/env docker run

Show HN: #!/usr/bin/env docker run

Show HN: #!/usr/bin/env docker run

Show HN: Blockly BOT – AI to assist in learning block programming

Hello, I am a 15-year-old middle school student living in Japan. Learning programming can be challenging for beginners, but block programming makes this learning process easier. In particular, Scratch, developed by the MIT Media Lab, is a wonderful tool that allows intuitive learning using blocks. It is based on Google's Blockly project.<p>I have developed my own block learning assistant using Blockly. With this tool, it's possible to add explanations to existing blocks, customize them, or create new blocks using natural language. It was built using OpenAI, React, and Vite.<p>This project's source is publicly available on GitHub, and I hope it can contribute to the advancement of programming education. I am eagerly awaiting your valuable feedback!<p>Demo (Japanese): <a href="https://blockly.yutakobayashi.dev" rel="nofollow">https://blockly.yutakobayashi.dev</a>

Show HN: I'll build unstyled projects to focus on functionality

Show HN: I made a site to simplify recommending talented people to others

Hey HN, i made this app to improve tech hiring via personal recommendations let me know what you think!

Show HN: I made a site to simplify recommending talented people to others

Hey HN, i made this app to improve tech hiring via personal recommendations let me know what you think!

Show HN: I built a 4000 watt solar array on top of my Tesla (AMA)

Show HN: Just F-Ing Ping

Show HN: Just F-Ing Ping

Show HN: Conway's Game of Life, but with a gallery of other peoples patterns

This is my spin on Conway's Game of Life. I have added the ability to create an account, save grids that you have discovered, and browse the gallery of grids saved by other people and replay them.<p>This project has served as a sandbox for me to practice various aspects of developing a comprehensive web application from scratch. This was my first time developing a full scale web app with [almost] all the features you would expect. I know it is nowhere near perfect in its current state, but I feel it has reached a point of diminishing returns, and therefore my time is better spent focussing on other projects with more potential. I may continue to develop this project further in the future just for fun.

Show HN: Conway's Game of Life, but with a gallery of other peoples patterns

This is my spin on Conway's Game of Life. I have added the ability to create an account, save grids that you have discovered, and browse the gallery of grids saved by other people and replay them.<p>This project has served as a sandbox for me to practice various aspects of developing a comprehensive web application from scratch. This was my first time developing a full scale web app with [almost] all the features you would expect. I know it is nowhere near perfect in its current state, but I feel it has reached a point of diminishing returns, and therefore my time is better spent focussing on other projects with more potential. I may continue to develop this project further in the future just for fun.

Show HN: Conway's Game of Life, but with a gallery of other peoples patterns

This is my spin on Conway's Game of Life. I have added the ability to create an account, save grids that you have discovered, and browse the gallery of grids saved by other people and replay them.<p>This project has served as a sandbox for me to practice various aspects of developing a comprehensive web application from scratch. This was my first time developing a full scale web app with [almost] all the features you would expect. I know it is nowhere near perfect in its current state, but I feel it has reached a point of diminishing returns, and therefore my time is better spent focussing on other projects with more potential. I may continue to develop this project further in the future just for fun.

Show HN: Conway's Game of Life, but with a gallery of other peoples patterns

This is my spin on Conway's Game of Life. I have added the ability to create an account, save grids that you have discovered, and browse the gallery of grids saved by other people and replay them.<p>This project has served as a sandbox for me to practice various aspects of developing a comprehensive web application from scratch. This was my first time developing a full scale web app with [almost] all the features you would expect. I know it is nowhere near perfect in its current state, but I feel it has reached a point of diminishing returns, and therefore my time is better spent focussing on other projects with more potential. I may continue to develop this project further in the future just for fun.

Show HN: I made an extension to keep Twitter from losing my scroll position

Show HN: I made an extension to keep Twitter from losing my scroll position

Show HN: RemoteStorage – sync localStorage across devices and browsers

Hey HN! Wanted to share a new library and server I've recently been working on called remoteStorage.<p>When building frontends with Javascript, the native localStorage API is super useful for keeping track of state between sessions in the same browser, but it's not as good a solution when your data needs to be shared across multiple devices or browsers.<p>For instance, let's say you want to show a welcome modal to all new users that sign up for your product. If you use localStorage to track if a user has already seen this modal, your users will end up getting the experience repeatedly every time they switch devices or browsers, or whenever Chrome decides to nuke your data.<p>I built remoteStorage to help fix that. Using the same API as localStorage, remoteStorage allows you to easily read and write data on the fly while maintaining state across browsers and devices in order to provide a better user experience.<p>The project is built as a monorepo in Typescript and contains a JS library that works across any Javascript stack (including Node.js and React Native) and is lightweight (~1 kb minified). The server is built with Nest.js with a disk-persisted Redis Database. It can be deployed in a few minutes using Docker.<p>One of the biggest challenges when building this was coming up with a secure scheme for handling authentication while still keeping the API dead simple for frontend devs to use. While the project is intended to store non-sensitive data like impression events/preferences, I still wanted to make sure data couldn’t easily leak or be tampered with.<p>One solution has been to generate a unique secret UUID per user on your own backend to identify the user. Alternatively, you could create a simple wrapper/proxy API around remoteStorage that uses your own authentication method to verify the user's identity before allowing them to access the data (this is super simple to build with React Server Components). Then, you could pick a secure and secret Instance ID that is not publicly available to ensure that only your application can access the data.<p>Has anyone felt the same pain points with localStorage before? Is this solution useful? Let me know what you think or ideas for how I can improve it :)

Show HN: RemoteStorage – sync localStorage across devices and browsers

Hey HN! Wanted to share a new library and server I've recently been working on called remoteStorage.<p>When building frontends with Javascript, the native localStorage API is super useful for keeping track of state between sessions in the same browser, but it's not as good a solution when your data needs to be shared across multiple devices or browsers.<p>For instance, let's say you want to show a welcome modal to all new users that sign up for your product. If you use localStorage to track if a user has already seen this modal, your users will end up getting the experience repeatedly every time they switch devices or browsers, or whenever Chrome decides to nuke your data.<p>I built remoteStorage to help fix that. Using the same API as localStorage, remoteStorage allows you to easily read and write data on the fly while maintaining state across browsers and devices in order to provide a better user experience.<p>The project is built as a monorepo in Typescript and contains a JS library that works across any Javascript stack (including Node.js and React Native) and is lightweight (~1 kb minified). The server is built with Nest.js with a disk-persisted Redis Database. It can be deployed in a few minutes using Docker.<p>One of the biggest challenges when building this was coming up with a secure scheme for handling authentication while still keeping the API dead simple for frontend devs to use. While the project is intended to store non-sensitive data like impression events/preferences, I still wanted to make sure data couldn’t easily leak or be tampered with.<p>One solution has been to generate a unique secret UUID per user on your own backend to identify the user. Alternatively, you could create a simple wrapper/proxy API around remoteStorage that uses your own authentication method to verify the user's identity before allowing them to access the data (this is super simple to build with React Server Components). Then, you could pick a secure and secret Instance ID that is not publicly available to ensure that only your application can access the data.<p>Has anyone felt the same pain points with localStorage before? Is this solution useful? Let me know what you think or ideas for how I can improve it :)

Show HN: RemoteStorage – sync localStorage across devices and browsers

Hey HN! Wanted to share a new library and server I've recently been working on called remoteStorage.<p>When building frontends with Javascript, the native localStorage API is super useful for keeping track of state between sessions in the same browser, but it's not as good a solution when your data needs to be shared across multiple devices or browsers.<p>For instance, let's say you want to show a welcome modal to all new users that sign up for your product. If you use localStorage to track if a user has already seen this modal, your users will end up getting the experience repeatedly every time they switch devices or browsers, or whenever Chrome decides to nuke your data.<p>I built remoteStorage to help fix that. Using the same API as localStorage, remoteStorage allows you to easily read and write data on the fly while maintaining state across browsers and devices in order to provide a better user experience.<p>The project is built as a monorepo in Typescript and contains a JS library that works across any Javascript stack (including Node.js and React Native) and is lightweight (~1 kb minified). The server is built with Nest.js with a disk-persisted Redis Database. It can be deployed in a few minutes using Docker.<p>One of the biggest challenges when building this was coming up with a secure scheme for handling authentication while still keeping the API dead simple for frontend devs to use. While the project is intended to store non-sensitive data like impression events/preferences, I still wanted to make sure data couldn’t easily leak or be tampered with.<p>One solution has been to generate a unique secret UUID per user on your own backend to identify the user. Alternatively, you could create a simple wrapper/proxy API around remoteStorage that uses your own authentication method to verify the user's identity before allowing them to access the data (this is super simple to build with React Server Components). Then, you could pick a secure and secret Instance ID that is not publicly available to ensure that only your application can access the data.<p>Has anyone felt the same pain points with localStorage before? Is this solution useful? Let me know what you think or ideas for how I can improve it :)

Show HN: Run Stable Diffusion Directly on iPhone