Alexstarfire @ Alexstarfire @lemmy.world

Posts

0

Comments

2,013

Joined

2 yr. ago

Your stance feels more like a "everyone disliked that" to me.

I've never looked before, but I'm surprised that was previously private information. Why? Seems like it should have been public.

Why a pic of AoE2?

So schools can have a backbone. That's surprising.

Surely a government would never lie to us and have an alternate agenda. Iraq totally had WMDs.

Just waiting for someone to come along and say they are all slightly different colors.

He's got more clothes than I think I've ever owned in my entire life.

Uhh, price?

It's more integrated. Also, I don't think the expectation is to carry them around. You'd pick what you want for your trip and leave the rest at home. I expect this to be more like DS and less like Switch. I.e. A single person per device.

Honestly, impressive as hell. It's obviously not done but it looks far better than I thought could be managed on a GBA even as-is.

We should unite some citizens and enforce some changes.

I don't even know what they ended up doing, not my department. They did come to us though as we were the ones sending out the emails though.

I meant you wouldn't want to do that in this use case. We can't wait to verify an email at this step. There are plenty of things that could be implemented, if we knew about this workflow.

Wouldn't have been useful in this particular case.

What the hell?

I'll share my story about stupid customers too. In our application we have the option to require an email address or not require an email address for new users based on the customer's preference. So naturally, we have/had a customer that set it to require an email address, but when they took information from their customers they did not actually require them to provide an email address. So for all their customers that didn't actually provide an email address they would enter something like noemail@fake.com. Something to satisfy the field requirement without actually being an email address. No consistency mind you.

This worked fine until we started offering a SaaS version of our software and emails stated being sent from AWS servers. Needless to say, AWS doesn't like it when you have an undelivered rate of like 30% for your emails. It ended up locking a pod out of sending emails for a day which ending up affecting multiple customers of ours.

And naturally, the customer using the fake emails never said anything about it to us beforehand or indicated what type of workforce they actually wanted; which was, "we want our employers to be forced to ask for an email and if the email is required they can't accidently forget to ask because they won't be able to continue in the app until they enter something." Probably a bit more paraphrased at this point since it happened years ago.

We don't expect all entered email addresses to be valid, but come on.

Thanks

Damn, not for the US.

When you start with a conclusion and work your way back to reasons, you almost always end up with odd logic. That's why good science does it the other way around.