This is awesome. Lots of carriers have broke the ability to text phones. It just gets blocked so this is a great work around.
Ntfy.sh – Send push notifications to your phone via PUT/POST
141–150 of 306 posts
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#142Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#143This is great, will add it to my docker-compose.yaml and my scripts! To be clear, if 100 people subscribe to ntfy.sh/mytopic, they all receive this message, right? curl -d "Backup successful :)" ntfy.sh/mytopic I wonder how many people got one when I was testing...
Correct.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#144Hey cool, this is my project. Happy to answer questions. Edit: I am also looking for a new opportunity. If you need a good Staff/Principal Engineer, check out my resume here: https://heckel.io/resume.pdf
Have you thought about integrating with Matrix in any way? I.E. curl ntfy.sh/matrix and put the matrix room id in the post payload. The user would have to invite your ntfy.sh matrix user to the room, and it would not offer encryption, but it might add value for use cases where you want to send to a team or the user wants their notifications in the same place.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#145Hey cool, this is my project. Happy to answer questions. Edit: I am also looking for a new opportunity. If you need a good Staff/Principal Engineer, check out my resume here: https://heckel.io/resume.pdf
From the repository that I found, it seems that you wrote the backend in Go. How did it hold up? Any lessons learned?
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#146Earlier quoted context omitted.
Genuine question - have you ever implemented an E2E encrypted system? Because it's not particularly easy to do, and there are a lot of caveats and drawbacks. Let me rephrase your assumption: "Why couldn't you just mail me the letter in a 100lb safe. In 2022, that's my standard expectation from any service". So - are you willing to pay to ship 100lbs for every letter you send? Are you meticulously managing the details…
> Are you working out the details on recovery and storage, handling lost devices, configuring a communication channel for sharing certs/keys, managing several crypto dependencies and libraries - all so that you can go "Hey - what's up!" in a notification to your phone? In 2022, there is no need to invent anything new about E2E encryption. There are many successful open-source examples, including Keybase and Firefox S…
>This is Hacker News, a discussion platform, and I am raising a question about software development in general.
No - no you aren't. You're complaining about a feature in a product you've admitted you won't use.
Which... is fine. At the end of the day - the feedback might be helpful or it might not, part of the journey of publishing software (or making anything, really) is figuring out what advice to listen to, and what to ignore.
But personally - I don't really find your point sensible. You have no use-case, you have no threat model, you have a very unclear understanding of what E2E encryption entails, in my opinion - since you point to apps whose entire marketing shtick is that they have E2E encryption and say "if they are doing it, it must be easy" - Ignoring that they are literally using the difficulty of doing it as the distinguishing factor for their product.
But hey - I worked for a security company that did E2E encryption for fortune 100 companies, mostly banks, for 5 years (and eventually went out of business... as an aside) so what do I know...
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#147Earlier quoted context omitted.
Why couldn't the entire system be E2E encrypted by default, though? In 2022, that's my standard expectation from any service. Even such things as Pocket / Instapaper / Raindrop should come with E2E encryption by default. It's better for the service provider, too: no issues with GDPR, or in case of a database hack.
Go figure out key exchange and use this as transport for encrypted messages. Encrypting stuff isn't hard.
Encrypting stuff in a way that can’t be trivially subverted by a malicious client app is actually pretty hard, so what have you actually gained if you’re going to trust the client app?
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#148Hey cool, this is my project. Happy to answer questions. Edit: I am also looking for a new opportunity. If you need a good Staff/Principal Engineer, check out my resume here: https://heckel.io/resume.pdf
verynice, thanks for making
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#149Earlier quoted context omitted.
If you run binaries compiled by the author of the software it wouldn't matter that it is open source, so play store is out of the question. So then it must be open source and you must use distributor you trust: your distro maintainers and F-Droid. Also you must trust that people did really take a look at the code.
That's exactly how Signal and Keybase work, and nobody has any problems with that.
That’s because most people hear “E2E” and think that somehow means they can automatically trust the client app. It’s a panacea.
Re: Ntfy.sh – Send push notifications to your phone via PUT/POST
#150This is great, will add it to my docker-compose.yaml and my scripts! To be clear, if 100 people subscribe to ntfy.sh/mytopic, they all receive this message, right? curl -d "Backup successful :)" ntfy.sh/mytopic I wonder how many people got one when I was testing...
Correct.
So, any nice topics? ;)