ifttt Reviews

NSQ Reviews

ifttt mentions (179)

• Todoist + Google Calendar + IFTTT: How I created a GTD "tickler" for recurring events

  What I've done instead is, for any recurring event that isn't really due on that date, like "book a haircut" or "fertilize roses", I add an event on a Google Calendar called "Tickler" with the desired recurrence. I then have an IFTTT (https://ifttt.com/explore) integration that creates a Todoist event in my inbox whenever that event shows up on my calendar. It doesn't show up with a due date so I can schedule it... Source: 12 months ago

• what are your recommendations

  Or head to the Explore page and see if anything grabs your attention. Source: over 1 year ago

• Messages after death

  Slack has a feature to schedule messages, also a bunch of bots that do various scheduling tasks… Also you could use a email marketing tool like Mailchimp that could allow you scheduling Mails far a head. But any service you choose should be around somewhat longterm right? It will probably require some money and a bit of luck for the service or app of choice to stay around for a while. So ideally something relying... Source: over 1 year ago

• They air tagged nana because she kept running the streets.

  I don’t know about the air tag nativity, which it probably does. But you can do that with any smartphone they has gps; with an app / website called ifttt. Source: over 1 year ago

• Trying to create Alexa routine to automate thermostat changes when both my and my wife's phones are gone

  There's also some automation that you can do with something like https://ifttt.com/explore. Source: over 1 year ago

NSQ mentions (7)

• Any thoughts on using Redis to extend Go's channels across application / machine boundaries?

  (G)NATS can do millions of messages per second and is the right tool for the job (either that or NSQ). Redis isn't even the fastest Redis protocol implementation, KeyDB significantly outperforms it. Source: over 1 year ago

• FileWave: Why we moved from ZeroMQ to NATS

  Bit.ly's NSQ is also an excellent message queue option. Source: over 1 year ago

• Infinite loop pattern to poll for a queue in a REST server app

  Queue consumers are interesting because there are many solutions for them, from using Redis and persisting the data in a data store - but for fast and scalable the approach I would take is something like SQS (as I advocate AWS even free tier) or NSQ for managing your own distributed producers and consumers. Source: over 1 year ago

• What are pros and cons of Go?

  Distrubition server engine ( for example websocket server multi ws gateway and worker pool,nsq.io realtime message queue and so on). Source: almost 2 years ago

• Distributed IM Service in Golang

  NSQ is a message queue implemented by Golang, and all messages are routed through NSQ. Reasons for choosing NSQ compared to other MQs: decentralized distribution (direct connection between production and consumption), low latency, No ordering, high performance, simple binary protocol. - Source: dev.to / about 2 years ago