Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Messages via JSON

refl.me

Post reply on HN
Print view View original

11–20 of 129 posts

Re: Messages via JSON

#11

Post by teko_ji »

beefhash wrote: post #9
teko_ji wrote: post #8

Earlier quoted context omitted.

I think the author has made it as simple as possible for users and developers with basic skills.

While I agree with the notion of making things simple, security theater is worse than no security at all because it makes you feel safe when you may not be.

Maybe so.)

Re: Messages via JSON

#14

Post by kissgyorgy »

Andrew_nenakhov wrote: post #2

What's the point? Why not just forward a message to XMPP, Telegram, WhatsApp or email? You know, to the app users actually use. Why make them install one more quasi-messenger?

Do you realize that's the opposite direction of this? In that case you SEND something to a chat app, but this app can RECEIVE data from a web service. Way simpler architecture.

Re: Messages via JSON

#15

Post by geoah »

Andrew_nenakhov wrote: post #2

What's the point? Why not just forward a message to XMPP, Telegram, WhatsApp or email? You know, to the app users actually use. Why make them install one more quasi-messenger?

This would be nice for websites and services users want to get push notifications from. I get that html5 notifications should be able to do this at some point but there is still merit in having another way of getting stuff to your phone and possibly desktop.

Re: Messages via JSON

#16

Post by [deleted] »

geoah wrote: post #15
Andrew_nenakhov wrote: post #2

What's the point? Why not just forward a message to XMPP, Telegram, WhatsApp or email? You know, to the app users actually use. Why make them install one more quasi-messenger?

This would be nice for websites and services users want to get push notifications from. I get that html5 notifications should be able to do this at some point but there is still merit in having another way of getting stuff to your phone and possibly desktop.

[deleted]

Re: Messages via JSON

#17

Post by kam »

beefhash wrote: post #7

> Request signature format(crc): [time_stamp]_[md5(time_stamp+secret_key)] This should probably be an HMAC construction at the very least, and MD5 in general just should be discarded entirely in favor of BLAKE2b, SHA-2 or SHA-3. And ideally, it'd actually validate the rest of the contents as well.

Also the example PHP code doesn't validate the age of the passed timestamp so you could just replay a "signature" indefinitely...

Given that, you might as well just use an unchanging token or Basic Auth. Assuming https, that wouldn't be terrible for this kind of use case. But put it in an Authorization header, not in a query parameter, so it doesn't end up in logs.

Re: Messages via JSON

#19

Post by noahster11 »

poyu wrote: post #18

What's the difference between this and [Pushover]( https://pushover.net )?

Pushover also handles a server, which you can make requests to, that sends push notifications to your phone. It looks like this project just scrapes JSON from a URL for changes, and notifies from that.

Pushover is push based, while this looks to be pull based.

Post reply on HN