81–90 of 129 posts
> 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.
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?
Because they don't work directly with web services. Read the author's article: https://medium.com/@re_dmitriy/what-is-refl-me-67e6eb151f27
Then why not make a relay, i.e. a server that forwards messages from a webclient to Whatsapp, email, etc.?
Earlier quoted context omitted.
I think the author has made it as simple as possible for users and developers with basic skills.
Quick and honest question: are you the author? You respond to lots of comments in the name of author, that's a rather surprising level of care about a niche piece of software.
Oh, I finally understand it! It is just an RSS (but with JSON instead of XML)!
There is something to be said for things being similar but not the same. This app can grow features in the direction of alerting, whereas an RSS reader wouldn't be growing in that direction without becoming bloatware because it's main job is to catch you up on reading material.
I can see myself using it, and it has been something I have consider building myself - although I had a different angle - an API for a person so you can send me a message (if I trust you... maybe I give each friend a different token!) and we can avoid using email or a proprietary chat alltogether. Such a service could work in tandem with this app.
Based on that you could make a distributed "facebook" of sorts.
Once the iPhone app of this come out I can see myself setting up a little nodejs server and aggregating some stuff to send down. Weather, email, SMS, maybe some favourite google searches (when they change) or hn.algolia.com searches.
Earlier quoted context omitted.
Quick and honest question: are you the author? You respond to lots of comments in the name of author, that's a rather surprising level of care about a niche piece of software.
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.
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.
Well, it receives data by hitting a specific endpoint with a specific protocol. It’s “simpler” in that it may be easier to implement, but you still have to modify your service to get that to work. And if you must modify your service, you may want to implement something that’s better supported and doesn’t require users to install (and configure) yet another app.
Oh, I finally understand it! It is just an RSS (but with JSON instead of XML)!
I think this is more focused than RSS. Doing the same with an RSS reader would be fiddly and sort of out of it's use case. If you want regular polling (every 15s say) maybe your RSS reader can do that but it isn't natural. There is something to be said for things being similar but not the same. This app can grow features in the direction of alerting, whereas an RSS reader wouldn't be growing in that direction without…
> although I had a different angle - an API for a person so you can send me a message ... and we can avoid using email or a proprietary chat alltogether
If you want to exchange messages avoiding email or proprietary chats, you have a wide variety of open chat protocols and free and open source chat applications to choose from. XMPP, Matrix, IRC, mastodon, rocketchat, mattermost, ... dozens of them!