▲ 479 ▼ This old food court stand at the mall had digital menus, but used stickers when the prices changed. (fedia.io) submitted 2 years ago by wagesj45@fedia.io to c/mildlyinteresting@lemmy.world 56 comments fedilink hide all child comments
[–] Alexstarfire@lemmy.world 2 points 2 years ago (4 children) Wouldn't have been useful in this particular case. permalink fedilink source parent hideshow 4 child comments replies: [–] ulterno@programming.dev 0 points 2 years ago (3 children) Yeah. Definitely needs the form makers to implement it on their side. permalink fedilink source parent hideshow 3 child comments replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 0 points 2 years ago (1 child) Yeah, in your case, the most I see could be done, is to remove the address that gives an unreachable response and add it to a list which can be referred to, right before a mail to the next record's address is sent (to not retry duplicates). Or maybe use some AI mumbo-jumbo to determine availability. Of course, I can also think of using DNS records to precheck if the domain name exists, but I would think they would mostly be parked domains anyway, so maybe not. permalink fedilink source parent hideshow 1 child comment replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago 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. permalink fedilink source parent
[–] ulterno@programming.dev 0 points 2 years ago (3 children) Yeah. Definitely needs the form makers to implement it on their side. permalink fedilink source parent hideshow 3 child comments replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 0 points 2 years ago (1 child) Yeah, in your case, the most I see could be done, is to remove the address that gives an unreachable response and add it to a list which can be referred to, right before a mail to the next record's address is sent (to not retry duplicates). Or maybe use some AI mumbo-jumbo to determine availability. Of course, I can also think of using DNS records to precheck if the domain name exists, but I would think they would mostly be parked domains anyway, so maybe not. permalink fedilink source parent hideshow 1 child comment replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago 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. permalink fedilink source parent
[–] Alexstarfire@lemmy.world 1 point 2 years ago (2 children) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 0 points 2 years ago (1 child) Yeah, in your case, the most I see could be done, is to remove the address that gives an unreachable response and add it to a list which can be referred to, right before a mail to the next record's address is sent (to not retry duplicates). Or maybe use some AI mumbo-jumbo to determine availability. Of course, I can also think of using DNS records to precheck if the domain name exists, but I would think they would mostly be parked domains anyway, so maybe not. permalink fedilink source parent hideshow 1 child comment replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago 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. permalink fedilink source parent
[–] ulterno@programming.dev 0 points 2 years ago (1 child) Yeah, in your case, the most I see could be done, is to remove the address that gives an unreachable response and add it to a list which can be referred to, right before a mail to the next record's address is sent (to not retry duplicates). Or maybe use some AI mumbo-jumbo to determine availability. Of course, I can also think of using DNS records to precheck if the domain name exists, but I would think they would mostly be parked domains anyway, so maybe not. permalink fedilink source parent hideshow 1 child comment replies: [–] Alexstarfire@lemmy.world 1 point 2 years ago 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. permalink fedilink source parent
[–] Alexstarfire@lemmy.world 1 point 2 years ago 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. permalink fedilink source parent