3 ms·
Will you be flooded with spam messages now that you have published the magic URL? Some twisted soul could even put sending a message to you via cronrab every m
by nine_k 5y ago
Will you be flooded with spam messages now that you have published the magic URL?
Some twisted soul could even put sending a message to you via cronrab every minute, and you don't seem to have any way to block it, or filter it from the rest.
I'd say that it's infinitely better to have an opaque an otherwise useless API token in your bash history than to have a URL of a bare and uncontrolled web service in the same bash history, and now on the open internet.
If I were to design a service like that, I'd have an URL like domain.api/username/${token}, where the token can be changed and / or retited, should it become a target of a spam attack. Exporting this token once in the beginning of a shell session should not be hard; SSH even allows you do it with SendEnv.
- NotEvil 5y agoThat url is the demo one. I think the author have his own magic url for personal use
- binwiederhier 5y agoYes that's correct. You control your own destiny. If you choose any of the demo topic names, you may be getting spam. If you choose your username, likely not. If you choose "phil-likes-dogs" then there's almost no chance someone will guess that. It's just like with passwords.
- binwiederhier 5y agoI responded here: https://news.ycombinator.com/item?id=29723347 https://news.ycombinator.com/item?id=29723347 As for the retirable token, you are right. In the current approach this cannot be done. I have an open ticket for auth (optional) that I'll soon implement. I want to get it right, so if you have thoughts, I'd love input on it: https://github.com/binwiederhier/ntfy/issues/19 https://github.com/binwiederhier/ntfy/issues/19