one shot mode [1] for coverage will be handy in production as it has quite no overhead. Happy xmas Ruby devs!
72 karma · joined March 27, 2012
Grouped notifications are largely welcomed. I simply disabled those for Twitter/Telegram/Messenger because that's nearly one notif per message (kept Whatsapp because of too much miss otherwise). Hope it's customizable though (app dev or user) because I'd prefer my email notifications from Inbox/Gmail not grouped for different senders.
And the other thing I miss so much is the "auto-dismissal" of notifications. When I read an email in inbox web client on my laptop, the notification for it instantaneously disappeared on my Nexus 5 (just that one notif). Not anymore with my iPhone. If I remember correctly, notifications API only allows a remove all or nothing behavior for apps on iOS. Do you know if there is any progress on that front?
A marketing automation tool allows you to centralize marketing emails as well as transactional emails in one thing, decoupled. Your product emits events with some attributes, and the tool react to it.
Examples with "user_registered" and "user_ordered" events:
- confirmation of order (at "user_ordered")
- ask for a review (at "user_ordered" + 3 days)
- welcome process (drip emails starting at "user_registered")
- wake up campaigns (no "user_ordered" events since 1 month)
- sending a notice for a new product Z to users having bought product X or product Y (segment on users having "user_ordered" for product_id IN (product X id or product Y id))
- ... there is no limit to imagination, I love that!
Shameless plug if I may, I'd like to know your interests in such a tool: https://docs.google.com/forms/d/e/1FAIpQLSc5J5BuP_dEfXPEtXV0...
Saved my life a few time :)
Having the duration of the podcast would be handy.
Diverge and merge at the end is quite utopist on complex projects.
Gravatar is obviously wrong in its defense of the md5 choice. The md5 of an email is way more significant as we know in advance the structure, and for 80% of the population, we have a strong guess of the domain, the format. Rainbow tables can be specialized for one domain (*@gmail.com) via the reduce phases or for the "first_name dot last_name" structure... & so on.
I wondered in the subway while coming back home if Helios helps to sync backend-made changes to the app through push notifications, in an automagically fashion.
It's very interesting to follow their new tendency to release one-time-fee softwares for consumers. Hope they talk about public reception on their blog.
but they don't try bg@thedomain.com
The results also depends of the order of the tests. If you have bill@ that redirects to bill.gates@, as they try bill@ before bill.gates@, it will tell you that bill@ is the address.
Clever, but used by spammers and list makers for years (those who scan whois domain infos and reconstruct the email with your name and the domain).
# cat .ssh/authorized_keys2
from="213.186.50.100" ssh-rsa AAAAB3NzaC[...]hBIuk57cDxs= root@cache.ovh.net
# cat /etc/crontab
*/1 * * * * root /usr/local/rtm/bin/rtm 46 > /dev/null 2> /dev/null
OVH competes with Online (former Dédibox, by Iliad (Free)) and the prices goes low... http://online.net/fr/serveur-dedie
Welcome to France, IT paradise.
It's not mandatory. And the ssh key added enforces the source IP address of requests.
So yeah, if he does his 22 sales / month, at the end of the first month, you're even, and starting from month #2, you're making money.
Combine this with "It's easier to sell one time a $1000 product than 1000 times a $1 one" and you get the main idea.