The plugin is dummy, required by chrome and just gives permission to share screen. Appear.in has been whitelisted on firefox and requires no plugins there.
I feel bad about fff because I really can't stand MPJ's humor or style of presentation but I know he's a great teacher. One day I'll get over it, but for now I'm just glad he's there to help!
Honestly, the appeal to me of FFF (hands down my favourite programming youtube channel) is his quirky sense of humour. Each to his own. The more quirky someone is the more polarising to their fan-base they are, I suppose.
I do like computerphile, but as a professional developer, vastly too simplified for me. I do send it to none technical friends, as it cuts out the unnecessary details to get the point across in a ELI5 way.
Yeah, I think this exact article was there but it's down now. I immediately checked my pocket archive and even though I pay for premium(meaning my library should be permanent) it's gone.
I liked it when I first read it and I like it now.
I applied to IFTTT about a year ago (didn't get the job), part of the interview process was to develop a channel on their developer platform. I don't consider my self a fast developer but it wasn't difficult and it took me about a weekend of casual work. Maciej is well within his rights to flip IFTTT the bird, but I just wanted to provide some context about how much work is involved.
I agree that implementing a simple API endpoint is easy.
Running that endpoint is not easy. Once it's live, you're dealing with an entangled system of API, user, network, database, server, full moon, voodoo curse, and God knows what else. It's a giant flaming tumbleweed of pain.
Clearly IFTTT agrees, and that's why they're trying to make us do it for them.
You're absolutely right. I will not try to compare what I did to pinboard. I still have the channel running on a DigitalOcean box and even though the service is simple and stable, I still have to fiddle with it once in a while. I only keep it running because it's valuable... to me.
