> Also, this means that anyone who has your phone number is told you're on the app and given your username, which you may not want for privacy reasons.
You can disable that behavior in your privacy settings iirc
Because most people are not privacy conscious and just want their messaging app to work (including having people know they are available to message on said platform).
Magic beans that live in your computer, or, uh, digital Chuck E. Cheese tokens. On a side note did you know the E. stands for Entertainment? Entertainment is literally that mouse’s middle name.
Nope. Fiat money is created as debt repayable only in that currency, and backed by a government which levies taxes only in that currency, so future demand to obtain the currency doesn't depend entirely on the assumption its purchasing power will go up. Even then, it needs a lot of intervention to keep it stable on a day to day basis.
I find it a shame to talk about something you're actively using in your company, which is apparently mature enough to be used in production environments and not show a single snippet of code as an example. For what it's worth you could say you reinvented programming altogether and that it makes things amazing for your company, but without examples or source code it feels sort of useless to announce as if it were such a big thing
They had a teenager as guest and the talk dynamic was good, with a lot of Q&A. Since I don't usually interact w/ teenagers I was completely blind to how they were using the web today.
We've seen problems from time to time with sendgrid and mailgun IPs getting blacklisted. Moved to Postmark, who are super-strict about transactional email only, and we've not had trouble since.
I've been recommending Postmark for transactional email and one of the others for newsletters.
I tried using it once. It did not seem solid. It didn’t support 2FA, and required my actual account username and password to send email from the server.
How hard can it be to send an email? Why pay $$$ for it?
For deliverability, which is pretty good on Mailchimp.
However I think that send emails out using the gmail API or the Amazon SES might be the way to go. Also depends on what you are doing, I think that those that over analyse the mail openings are getting it wrong, focusing on the wrong metrics. You should be focused on the sales metrics not be navel gazing in newsletter software. Content is king, get that right and again, focus on that, not the analytics.
I personally love the idea of having users log in with a temporary token sent by email, and have been doing so in my own projects for a while now.
However, I don't think sending them a link is a good idea, since it just gets them used to clicking on things in their emails, which could potentially lead them being phished quite easily.
You make a fair point against sending links in emails, so how do you implement the token in the email? I'd like to start doing that in my own projects too.
