mheap
Joined 14 years ago
Joined 14 years ago
I'm obviously rubbish at the explaining what we do thing (though in my defence we're still working out the details)
I wasn't expecting to see many people on Hacker News saying that they'd adopt the system themselves, but I was hoping that some people would see the merit in it.
You hit the nail on the head about less optimised communication methods. Por Favor is primarily about asking people to do things, then reminding them when the time is right automatically. The time might be a specific time (e.g. 6pm), or when they're next in a certain area (geofencing) (or something else that we haven't thought of yet).
Based on feedback from HN, we're thinking about selling a "Family plan" or something like that, where it's a slightly higher fee, but you can share the service with X people. It's definitely about getting lots of people invested in the system, otherwise it's just another app on your home screen (or, hopefully on your home screen)
As for the data, it really is worth it for me. I don't have an iOS dev license, or know anything about mobile development particularly. If I'm going to dedicate weeks of my life to this, there needs to be at least enough interest for us to break even, or it's not worth it.
It is another communication channel, but it's one that's reserved only for the most important people, and only when they need something. If you get a message on it, you know it needs acting on, right now.
Everyone needing the app is an issue that we know about, and we're trying to work out a way to solve the issue so people can try it out and see how it's beneficial before having to cough up some cash.
Someone else mentioned integrating with apps that they use every day, so we might take a look into the various other to do products and see of we can build on top of them
> Using GitHub actions with branch names or tags is unsafe. Use commit hash instead.
Instead of updating to use a SHA everywhere, I wrote a tool to do it for you, making a note of the original version (e.g. @master).
This allows you to run the tool in the future and have the sha updated to the most recent version whilst still pinning to a specific commit.