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

101–110 of 129 posts

Re: Messages via JSON

#101

Post by joshstrange »

ValueNull wrote: post #100
joshstrange wrote: post #81

Earlier quoted context omitted.

I won't pretend it's "so easy" or anything like that but could you just proxy those requests and add the key yourself? AWS Lambda comes to mind as a cheap/free way to accomplish this with the benefit of letting you modify the data if needed on the fly (or even check against a DynamoDB for history/other rules).

Wouldn’t this defeat one of the benefits of this software, the need to not host your own server (or any backend infrastructure)?

I think the value-add with this service is the notification sending just by exposing an endpoint. I don't see any mention of not needing backend infrastructure (they even call out "connect your web service").

I think this is aimed at people who already are or can expose data via an HTTP endpoint and want notifications when that changes/updates. This includes the wide array of software developers who work on large OS projects that support sending notifications via services like PushBullet/Pushover/etc. Also, presumably, web services would just add a new endpoint with some auth token to easily send push notifications to their users without managing an app and everything else needed (push tokens, certs, GCM/FCM, apns, it can be a headache, trust me).

Personally I see pushover-type services (I use pushover so I'm only speaking from that experience) as more useful since I can "push" out of my networks much easier than a service can "poll" me. That said pushover has always been a little clunky IMHO with trying to get a service to send me notifications. So a simple "Paste this url into the refl.me app to get notifications from us" is a pretty attractive alternative for certain use cases.

Re: Messages via JSON

#102

Post by Semiapies »

semiotagonal wrote: post #63
Semiapies wrote: post #57

Earlier quoted context omitted.

As far as I can tell, that's it. It's a reinvention of RSS without any notable advantages and no compatibility with existing systems. So, a reinvented wheel that doesn't work on roads.

It's like re-inventing the wheel after everyone stopped using the wheel . It might meet with some success. To people who don't know about RSS, it's a new thing.

I think everybody using Feedbin, Feedly, Newsblur, The Old Reader, Inoreader, etc. would wonder who your "everybody" really is.

Re: Messages via JSON

#103

Post by icedchai »

Andrew_nenakhov wrote: post #68
nicolas314 wrote: post #50

Earlier quoted context omitted.

And yet, this is exactly how push notifications are implemented on mobile phones. You have the illusion to push a message from server to device while in fact you also push a message onto a queue that is polled at regular intervals by the mobile. No way around it, mobile devices don't have guaranteed connectivity as servers do.

No. That's not how it works. From the Apple Developers Documentation [1], "On initial launch of your app on a user’s device, the system automatically establishes an accredited, encrypted, and persistent IP connection between your app and APNs." This persistent connection is, in fact, an XMPP session (likely, a modified one) [2]. Google's FCM too uses XMPP [3]. [1] https://developer.apple.com/library/archive/documenta…

If you look at the format of APNS messages, they are nothing like XMPP. It seems very unlikely Apple uses it. That link you post does not confirm it.

Re: Messages via JSON

#104

Post by tlrobinson »

ValueNull wrote: post #78
purple_ducks wrote: post #49

> The "refl.me" key must always be true, otherwise an error will be called. Why?

Wish this wasn’t the case, would love to integrate services I don’t control into this.

I’m curious how many services you want to integrate match the format refl.me expects (namely a JSON object with at least a “message” property).

It seems likely you’d need to proxy most services anyway. With numerous FaaS providers these days that seems trivial.

Re: Messages via JSON

#105

Post by orasis »

NickBusey wrote: post #92
miki123211 wrote: post #85

If you need something like that, go for a Telegram bot. It's really simple to make, the API is very nice and developer friendly. It's not oAuth, just a simple secret. It even accepts parameters via GET, so writing a bash script that check something and sends a message via Curl is pretty easy. There are few APIs simpler than this one. This is also more efficient, as your app only sends data out when it needs to, inste…

I created a Telegram bot for one of my apps, but had to remove Telegram from my phone/computer after their terrible handling of Facebook linking. I made the mistake of linking my Telegram account to my Facebook account, which gave me the wonderful 'feature' of getting a notification any time one of my (due to the linked account being promotional) thousands of friends joined Telegram. These notifications play at any t…

Turn off contact sync in Telegram and delete your uploaded contacts.

Re: Messages via JSON

#106

Post by stevekemp »

poyu wrote: post #18

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

You self-host the source of the messages in this case.

(I use pushover, and it rocks. But there you POST the message to pushover, here you host them on your own machine(s))

Re: Messages via JSON

#107

Post by sz4kerto »

miki123211 wrote: post #85

If you need something like that, go for a Telegram bot. It's really simple to make, the API is very nice and developer friendly. It's not oAuth, just a simple secret. It even accepts parameters via GET, so writing a bash script that check something and sends a message via Curl is pretty easy. There are few APIs simpler than this one. This is also more efficient, as your app only sends data out when it needs to, inste…

Push is not always more efficient than pull. Pull puts a lower limit on traffic but it also puts an upper limit on it, plus you get an extra health check.

That's why many monitoring tools are now pull-based (Prometheus) instead of push (Graphite).

Re: Messages via JSON

#108

Post by Supermancho »

hk__2 wrote: post #87
shujito wrote: post #84

Earlier quoted context omitted.

Is that a good or a bad thing to do?

> Is that a good or a bad thing to do? Posting comments in favor of a service without disclosing your’re its author is usually seen as a conflict of interest and, as such, a bad thing.

> Posting comments in favor of a service without disclosing your’re its author is usually seen as a conflict of interest

Not sure why, since it isn't in any practical or philosophical sense.

I judge the merits of a post by the content. I don't know if you're Celebrity X or Author of Y and I don't care much. Yes it would be useful to reference other statements, but that's something you often sacrifice in an open (even moderated) online forum. It's a strength of the platform as well.

Re: Messages via JSON

#109

Post by tngranados »

orasis wrote: post #105
NickBusey wrote: post #92

Earlier quoted context omitted.

I created a Telegram bot for one of my apps, but had to remove Telegram from my phone/computer after their terrible handling of Facebook linking. I made the mistake of linking my Telegram account to my Facebook account, which gave me the wonderful 'feature' of getting a notification any time one of my (due to the linked account being promotional) thousands of friends joined Telegram. These notifications play at any t…

Turn off contact sync in Telegram and delete your uploaded contacts.

You can also turn off new contacts notifications which is something I also hated and discovered recently that you can do.

Re: Messages via JSON

#110

Post by teko_ji »

miki123211 wrote: post #85

If you need something like that, go for a Telegram bot. It's really simple to make, the API is very nice and developer friendly. It's not oAuth, just a simple secret. It even accepts parameters via GET, so writing a bash script that check something and sends a message via Curl is pretty easy. There are few APIs simpler than this one. This is also more efficient, as your app only sends data out when it needs to, inste…

The update frequency can be set in JSON.
Post reply on HN