binwiederhier
Joined 12 years ago
Karma
2,891
Submissions
384
Member since
Jul 21
Recent submissions
Comment · 2 months ago
Go to ntfy.sh/settings and enable background notifications. Or do it like I do it an pin the tab and just leave it open.
Unless you have a pro account, notifications are only cached on the server for 12h so that's why you may miss old notifications.
Comment · 2 months ago
If you use ntfy.sh and don't use instant delivery, ntfy uses Google's FCM for delivery, which is what everyone else does. It doesn't require a foreground service and has no battery impact.
ntfy offers you additional options with instant delivery or the selfhostable server. That requires a server connection and does impact battery a little. On my phone it doesn't show up in the list it's so low, but others have reported more consumption
Comment · 2 months ago
I'm the maintainer of ntfy. Happy to answer questions. Sorry that I'm late to the party :-)
Comment · 4 months ago
4 years later and I'm still working on ntfy. Trying to make push notifications easy as pie. I would have never thought that it would blow up like this. It's still a lot of fun, and I've learned a lot. Thanks everyone for your support and for your amazing ideas and contributions. Open source is awesome. HN ist awesome. https://github.com/binwiederhier/ntfy
Comment · 7 months ago
Thanks.
Comment · 7 months ago
I love that you love it. That's why I do it. :-)
Comment · 7 months ago
My co-worker figured out a way to run the GitHub CLI with read-only keys restricted to specific repos. I need to do that still.
Comment · 7 months ago
I don't want to isolate the container from the Internet :-) I understand that this is not the safest possible way (exfiltrating is still possible, but I mostly work on open source anyway, so that's not an issue), but I think the convenience wins here.
That said, if you have suggestions that are not super inconvenient, please let me know.
My main goal with this was to make sure it cannot go wild on my own system.
Comment · 7 months ago
I love how everyone is trying to solve the same problems, and how different the solutions are.
I made this little Dockerfile and script that lets me run Claude in a Docker container. It only has access to the workspace that I'm in, as well as the GitHub and JIRA CLI tool. It can do whatever it wants in the workspace (it's in git and backed up), so I can run it with --dangerously-skip-permissions. It works well for me. I bet there are better ways, and I bet it's not as safe as it could be. I'd love to learn about other ways that people do this.
Comment · 1 year ago
Oh my bad. I misread your comment. You are doing ZFS on top of dmcrypt, not dmcrypt images/volumes on top of ZFS.
Comment · 1 year ago
ZFS encryption is much more space efficient than dmcrypt+unencrypted ZFS when combined with zstd compression. This is because it can do compress-then-encrypt instead of encrypt-then-(not-really-)compress. It is also much much faster.
Source: I work for a backup company that uses ZFS a lot.
Comment · 1 year ago
I love hearing that. Anything worth sharing? I love hearing how people use it. My favorite one is the guy protecting his apple tree from thieves by adding a camera and motion sensor and then sending himself a notification with the picture to catch the apple thief.
Comment · 1 year ago
Disclaimer: I am the ntfy maintainer. Pleasantly surprised to be mentioned, hehe.
Pushover is an amazing tool and works well. In my obviously biased opinion though, I think that ntfy has a ton more features than Pushover and is fully open source. You can self host all aspects of it or you can use the hosted version on ntfy.sh for free, without signups, or pay for higher limits.
I suggest you try out ntfy;-)
Comment · 1 year ago
Thank you to all the Debian volunteers that make Debian and all its derivatives possible. It's remarkable how many people and businesses have been enabled by your work. Thank you!
On a personal note, Trixie is very exciting for me because my side project, ntfy [1], was packaged [2] and is now included in Trixie. I only learned about the fact that it was included very late in cycle when the package maintainer asked for license clarifications. As a result the Debian-ized version of ntfy doesn't contain a web app (which is a reaaal bummer), and has a few things "patched out" (which is fine). I approached the maintainer and just recently added build tags [3] to make it easier to remove Stripe, Firebase and WebPush, so that the next Debian-ized version will not have to contain (so many) awkward patches.
As an "upstream maintainer", I must say it isn't obvious at all why the web app wasn't included. It was clearly removed on purpose [4], but I don't really know what to do to get it into the next Debian release. Doing an "apt install ntfy" is going to be quite disappointing for most if the web app doesn't work. Any help or guidance is very welcome!
[1] https://github.com/binwiederhier/ntfy
[2] https://tracker.debian.org/pkg/ntfy
[3] https://github.com/binwiederhier/ntfy/pull/1420
[4] https://salsa.debian.org/ahmadkhalifa/ntfy/-/blob/debian/lat...
https://ntfy.sh - https://slide.tech - https://heckel.io - https://github.com/binwiederhier