The best Hacker News stories from Show from the past day

Go back

Latest posts:

Show HN: I gamified a habit tracker to fight procrastination

Show HN: A tiny solar-powered server only awake during the day

Solar Witch is a little webpage and server which receives and displays messages, so I suppose it's a tiny message board. It's coded in very dubious Arduino C.<p>It's not a 24/7 website. Depending on the state of the battery, the server itself might run all night, but all the messages it receives during the day are deleted at sunset, and the messaging function itself is only active between sunrise and sunset. This is for two reasons:<p>1. Less usage of Solar Witch during the night conserves battery power.<p>2. I like the idea of websites which _aren't_ constantly available. Websites which have to sleep too. Websites living on servers which aren't somewhere in the cloud, but which are bound to a particular location, giving you a sense of where in the world they actually live.<p>Solar Witch is very much inspired by the solar-powered version of Low Tech Magazine (<a href="https://solar.lowtechmagazine.com/" rel="nofollow">https://solar.lowtechmagazine.com/</a>) and the not-always-online chatroom Gossips Cafe (<a href="https://gossips.cafe/" rel="nofollow">https://gossips.cafe/</a>), but at a far, far smaller scale.<p>PSA: Solar Witch is a teensy hand-written C server running on a teensy microcontroller attached to a teensy solar panel which can only handle one HTTP request at a time and may have buffer overrun issues due to my ineptitude with C. If it's gone down, please don't be surprised, and rest assured I'll hit the reset button soon! Solar Witch encourages patience.

Show HN: A tiny solar-powered server only awake during the day

Solar Witch is a little webpage and server which receives and displays messages, so I suppose it's a tiny message board. It's coded in very dubious Arduino C.<p>It's not a 24/7 website. Depending on the state of the battery, the server itself might run all night, but all the messages it receives during the day are deleted at sunset, and the messaging function itself is only active between sunrise and sunset. This is for two reasons:<p>1. Less usage of Solar Witch during the night conserves battery power.<p>2. I like the idea of websites which _aren't_ constantly available. Websites which have to sleep too. Websites living on servers which aren't somewhere in the cloud, but which are bound to a particular location, giving you a sense of where in the world they actually live.<p>Solar Witch is very much inspired by the solar-powered version of Low Tech Magazine (<a href="https://solar.lowtechmagazine.com/" rel="nofollow">https://solar.lowtechmagazine.com/</a>) and the not-always-online chatroom Gossips Cafe (<a href="https://gossips.cafe/" rel="nofollow">https://gossips.cafe/</a>), but at a far, far smaller scale.<p>PSA: Solar Witch is a teensy hand-written C server running on a teensy microcontroller attached to a teensy solar panel which can only handle one HTTP request at a time and may have buffer overrun issues due to my ineptitude with C. If it's gone down, please don't be surprised, and rest assured I'll hit the reset button soon! Solar Witch encourages patience.

Show HN: A tiny solar-powered server only awake during the day

Solar Witch is a little webpage and server which receives and displays messages, so I suppose it's a tiny message board. It's coded in very dubious Arduino C.<p>It's not a 24/7 website. Depending on the state of the battery, the server itself might run all night, but all the messages it receives during the day are deleted at sunset, and the messaging function itself is only active between sunrise and sunset. This is for two reasons:<p>1. Less usage of Solar Witch during the night conserves battery power.<p>2. I like the idea of websites which _aren't_ constantly available. Websites which have to sleep too. Websites living on servers which aren't somewhere in the cloud, but which are bound to a particular location, giving you a sense of where in the world they actually live.<p>Solar Witch is very much inspired by the solar-powered version of Low Tech Magazine (<a href="https://solar.lowtechmagazine.com/" rel="nofollow">https://solar.lowtechmagazine.com/</a>) and the not-always-online chatroom Gossips Cafe (<a href="https://gossips.cafe/" rel="nofollow">https://gossips.cafe/</a>), but at a far, far smaller scale.<p>PSA: Solar Witch is a teensy hand-written C server running on a teensy microcontroller attached to a teensy solar panel which can only handle one HTTP request at a time and may have buffer overrun issues due to my ineptitude with C. If it's gone down, please don't be surprised, and rest assured I'll hit the reset button soon! Solar Witch encourages patience.

Show HN: A tiny solar-powered server only awake during the day

Solar Witch is a little webpage and server which receives and displays messages, so I suppose it's a tiny message board. It's coded in very dubious Arduino C.<p>It's not a 24/7 website. Depending on the state of the battery, the server itself might run all night, but all the messages it receives during the day are deleted at sunset, and the messaging function itself is only active between sunrise and sunset. This is for two reasons:<p>1. Less usage of Solar Witch during the night conserves battery power.<p>2. I like the idea of websites which _aren't_ constantly available. Websites which have to sleep too. Websites living on servers which aren't somewhere in the cloud, but which are bound to a particular location, giving you a sense of where in the world they actually live.<p>Solar Witch is very much inspired by the solar-powered version of Low Tech Magazine (<a href="https://solar.lowtechmagazine.com/" rel="nofollow">https://solar.lowtechmagazine.com/</a>) and the not-always-online chatroom Gossips Cafe (<a href="https://gossips.cafe/" rel="nofollow">https://gossips.cafe/</a>), but at a far, far smaller scale.<p>PSA: Solar Witch is a teensy hand-written C server running on a teensy microcontroller attached to a teensy solar panel which can only handle one HTTP request at a time and may have buffer overrun issues due to my ineptitude with C. If it's gone down, please don't be surprised, and rest assured I'll hit the reset button soon! Solar Witch encourages patience.

Show HN: gh-dash – GitHub CLI dashboard for pull requests and issues

Show HN: gh-dash – GitHub CLI dashboard for pull requests and issues

Show HN: gh-dash – GitHub CLI dashboard for pull requests and issues

Show HN: Redo – Command line utility for quickly creating shell functions

Show HN: Redo – Command line utility for quickly creating shell functions

Show HN: Redo – Command line utility for quickly creating shell functions

Show HN: Google Search results are below the fold

Show HN: Google Search results are below the fold

Show HN: Visualize your day as 144 rectangles

Show HN: Visualize your day as 144 rectangles

Show HN: Visualize your day as 144 rectangles

Show HN: Visualize your day as 144 rectangles

Show HN: A plain-text file format for todos and check lists

After having cycled through various CLI-based todo apps, I started to realise that I actually don’t need a tool at all for managing my todos. Most of the time, my use cases are quite simple, like viewing my todo items, checking them off, or adding a new one.<p>Rather than having to memorise CLI commands for these interactions (which I’m not super good at), I figured that it’s easier for me to use my text editor directly, and have an editor plugin help me with the visual structure and some convenience functionality. So, kind-of similar to Emacs Org Mode, but without having to use Emacs. I personally use Sublime Text, and even though I enjoy it a lot, I don’t like being bound to specific tools.<p>I think the best basis for staying independent is to have a data format that’s properly specified and meaningful on its own. This puts the data first, and it allows the tools to be built on top and shared (or interchanged) more easily.<p>This is what [x]it! is about, which is a plain-text file format for todos and check lists. I’m curious for thoughts and feedback. There is obviously not much tooling support (yet), but feel free to create something if the idea resonates with you.<p>Website with demo: <a href="https://xit.jotaen.net" rel="nofollow">https://xit.jotaen.net</a><p>File specification: <a href="https://github.com/jotaen/xit/blob/main/Specification.md" rel="nofollow">https://github.com/jotaen/xit/blob/main/Specification.md</a>

Show HN: A plain-text file format for todos and check lists

After having cycled through various CLI-based todo apps, I started to realise that I actually don’t need a tool at all for managing my todos. Most of the time, my use cases are quite simple, like viewing my todo items, checking them off, or adding a new one.<p>Rather than having to memorise CLI commands for these interactions (which I’m not super good at), I figured that it’s easier for me to use my text editor directly, and have an editor plugin help me with the visual structure and some convenience functionality. So, kind-of similar to Emacs Org Mode, but without having to use Emacs. I personally use Sublime Text, and even though I enjoy it a lot, I don’t like being bound to specific tools.<p>I think the best basis for staying independent is to have a data format that’s properly specified and meaningful on its own. This puts the data first, and it allows the tools to be built on top and shared (or interchanged) more easily.<p>This is what [x]it! is about, which is a plain-text file format for todos and check lists. I’m curious for thoughts and feedback. There is obviously not much tooling support (yet), but feel free to create something if the idea resonates with you.<p>Website with demo: <a href="https://xit.jotaen.net" rel="nofollow">https://xit.jotaen.net</a><p>File specification: <a href="https://github.com/jotaen/xit/blob/main/Specification.md" rel="nofollow">https://github.com/jotaen/xit/blob/main/Specification.md</a>

Show HN: A plain-text file format for todos and check lists

After having cycled through various CLI-based todo apps, I started to realise that I actually don’t need a tool at all for managing my todos. Most of the time, my use cases are quite simple, like viewing my todo items, checking them off, or adding a new one.<p>Rather than having to memorise CLI commands for these interactions (which I’m not super good at), I figured that it’s easier for me to use my text editor directly, and have an editor plugin help me with the visual structure and some convenience functionality. So, kind-of similar to Emacs Org Mode, but without having to use Emacs. I personally use Sublime Text, and even though I enjoy it a lot, I don’t like being bound to specific tools.<p>I think the best basis for staying independent is to have a data format that’s properly specified and meaningful on its own. This puts the data first, and it allows the tools to be built on top and shared (or interchanged) more easily.<p>This is what [x]it! is about, which is a plain-text file format for todos and check lists. I’m curious for thoughts and feedback. There is obviously not much tooling support (yet), but feel free to create something if the idea resonates with you.<p>Website with demo: <a href="https://xit.jotaen.net" rel="nofollow">https://xit.jotaen.net</a><p>File specification: <a href="https://github.com/jotaen/xit/blob/main/Specification.md" rel="nofollow">https://github.com/jotaen/xit/blob/main/Specification.md</a>

< 1 2 3 ... 591 592 593 594 595 ... 831 832 833 >