2 ms·
In most use cases I can think of the generated data is used only in a closed (testing) environment and won't be visible to web crawlers and spambots. Many devel
by paavo 14y ago
In most use cases I can think of the generated data is used only in a closed (testing) environment and won't be visible to web crawlers and spambots. Many developers like me use these libraries for prototyping different UI views for their apps.
Unfortunately, spammers do have way more advanced technologies to try and guess working addresses. Libraries like this generate mostly very improbable addresses: you would get way better results just by taking lists of most popular first names and family names and concatenating them with some well-known web mail providers.
- mindcrime 14y agoIn most use cases I can think of the generated data is used only in a closed (testing) environment and won't be visible to web crawlers and spambots. Many developers like me use these libraries for prototyping different UI views for their apps. The bigger problem, in my experience, is when you accidentally spam people yourself, while testing some function that somehow generates an outgoing email. I think almost everybody that's ever worked on code that sends emails has - at one time or another - ran a job that somehow wound up sending 6,712,374 "test" messages to every user in the production database. :-) Dummy addresses are better, but it's better still if they use @example.com so you know there's no way they'll actually get delivered to anybody.