Show HN: tttfi – Middleware for IFTTT
github.com
github.com
Either way, I think this is a good introduction for someone who is looking to do very simple things with an IFTTT integration. I don't think a node.js server running a python script inside of a docker container is the best way to go about it. Anyone who is trying to learn how to write integrations to services (such as IFTTT) will get the wrong impression if they try to dissect this code.
There are many ways of getting this setup, whatever you're most comfortable with. The key here is that this Maker service exists that let's you do basic REST input/output
no code except the SQL-Schema and complete freedom in data and API design.
You can also write your own private apps that execute on your own infrastructure in whatever language you want.
Donors Choose also has an API that one can use to programmatically list projects. I paired that API with Zapier to notify me about projects that I cared about - namely, classrooms that were filled with lower income students who had trouble getting fed at home.
Now I get a notification whenever a new project is created that fits the profile of what I want to donate to. Doing the same with IFTTT, from what I can tell, is kind of impossible. I looked into writing a shim API that would enable that type of notification but I couldn't get keys for the IFTTT service.
I dunno. Zapier seemed to offer better functionality and I didn't even have to pay for it.
1. Logged to a google spreadsheet when I enter and leave a radius around my work. I have to log hours worked, so this gives me a starting point at the end of the week for when I was physically here.
2. I get a stock price emailed to me when the market closes. I own a few shares of a single company (lowers my auto insurance premium, and keeps my engaged in the market), so this helps me see day-to-day changes.
3. I get the weather pushed to my phone at 6am every morning, so it is there on my lock screen as I'm getting up.
4. I get an email every time someone goes into space. SPACE.
Does this link work for you?
https://ifttt.com/emails/unsubscribe?email_type=newsletter (visiting this link unsubscribes you if you're signed in)
That is not an unsubscribe link. Unsub links remove you from the list without having to log in
One of my more annoying frequent inbox flyers is a newsletter from some website or other that says I need to log in to change my preferences.. only my account there must have been purged as they have no record of my email address (the exact email being sent the newsletters)
Sites - just provide easy one-click unsubscribe links, chances are it'll improve your open/click rate as you're letting people who aren't interested sift themselves out.
I've been concocting a bunch of things in AWS Lamdba lately which should be in a service like IFTTT.
I'd use stringify exclusively but IFTTT has a lot more integrations, so I end up using IFTTT as both a trigger and action in stringify. Ugly, but it works.
https://google.com/search?q=ifttt+yahoo+pipes
https://www.import.io/post/5-yahoo-pipes-alternatives-that-a...
Sorry but I could understand if you had to maintain a legacy code base.
You can write middleware in anything that's executable via a terminal window.
On Fedora, Python comes pre-installed with first class support for
Python virtual environments. It is ready for use straight out of the
box. No guessing package names, no installation, just dive in and go.
Look:
[fedora]$ python3 -m venv env
[fedora]$ . env/bin/activate
(env) [fedora]$ python ...
Note the python3 ...EDIT: wow, 4 downvotes for stating a fact that Fedora developers themselves are shouting from rooftoops. The Python3 hate is strong today.
python --version
(note not python3) This recommendation will be periodically reviewed over
the next few years, and updated when the core development
team judges it appropriate.
So it's likely that at some point between here and 2020, or in 2020 at worst, the recommendation will change.IMHO Python 3 has now reached a level of maturity and backward-compatibility where it can safely take over as system python. It's now shipped by Fedora, which means the next RHEL will also ship it. Updating old scripts should mostly be a matter of grepping and shebanging from python to python2, and there is now no point in procrastinating further with this move.
#!/usr/bin/env python3
This works on all modern Linux distributions today.I was one of them until the last couple of months. I think moving to 3 now makes sense, and it's pain-free in my experience.
In 2016 I hadn't made the move yet. And as recently as a couple of months ago, sometimes py2 was still the choice (for instance, Amazon Lambda didn't support 3 yet).
Sure, lots of Enterprise apps use Python 2 because that was what they could build with.
I'm a Python developer and I don't know anyone who doesn't use Python 3 by default.
I understand this is purely anecdotal, but it seems outlandish to say that Python devs mostly use Python 2.
Then again, if your language is completely representable with US-ASCII, you might not have experienced the pain caused by having to unit test pretty much all string operations in your code.
[1]: https://semaphoreci.com/blog/2016/11/11/python-versions-used...
Then I guess it's a good thing I didn't say that. I said the majority of the ones I know use it.
The idea is that I'd like to write little to make little things work with IFTTT. Py2 is just enough to do a lot while keeping things casual and of fun. Py3 is too serious to me and shell script just awful...
Happy hacking.