[hackerspaces] So, how much spam do you get?

[Joshua Pritt]

Ah OK I see.  It would help to hide the email addresses behind a captcha
perhaps but we still have the email right on our contact page of our main
website.  So a crafty crawler could still find it from the hackerspaces.org
links to our websites...

on a side note:
What needs to be fixed on the map?  Do we need to implement the Space API
on Google Maps or just glean the addresses from each space's entry on the
main hackerspaces.org website and plot it on a Google map?  I just recently
added a Google map plugin for Solarwinds Orion software so they can see the
red, yellow, green markers on the map to quickly see the state of their
network on a map of the state of Alabama.  Perhaps I could help fix the map?

On Mon, Oct 27, 2014 at 10:50 AM, Sector67 Team <team at sector67.org> wrote:

> I think Nate is talking about targeted "spam" around the latest
> Kickstarter project for hackers to support, etc - not so much the typical
> Viagra or low budget stock options spam.  There have been a few lately that
> haven't BCC'd, so it was apparent that they're just gathering all of the
> addresses from a single location (probably this site) and then bugging
> everyone.
>
> I would suggest putting a CAPTCHA to reveal the contact address, but
> knowing that the map still isn't fixed, I don't think this is going to fall
> into a high priority bucket.
>
>
> Chris
>
> Chris Meyer
> Director
> Sector67
>
> 608-241-4605
> http://sector67.org
>
> 2100 Winnebago St
> Madison, WI  53704
>
> On Mon, Oct 27, 2014 at 9:43 AM, Joshua Pritt <ramgarden at gmail.com> wrote:
>
>> Publishing an email on a public website so that the public can contact
>> you is one of ways spammers can scrape your email address to add to their
>> database.  But it's just one of the things to deal with if you truly want
>> the public to be able to contact you.  I think changing your email is a
>> good way to go but if you gave out a lot of business cards or flyers with
>> your email it might not be easy or even possible.  So our best bet is to
>> use all the anti-spam tools at our disposal to try to get rid of it.  It's
>> not going to go away so we just have to stay ahead of them and be able to
>> add their email addresses, domains, subject lines, and email bodies to a
>> spam database that can be used for smart filters.
>> We've set up our admin at melbournemakerspace.org main email to bounce to
>> several board members that mostly use Gmail.  So if any spam has gone to
>> our email address I, for one, have not seen it thanks to Gmail's spam
>> filtering.
>>
>>
>> On Mon, Oct 27, 2014 at 10:19 AM, Nathaniel Bezanson <myself at telcodata.us
>> > wrote:
>>
>>> We get/got a LOT of maker-targeted spam to our contact address. Once in
>>> a while, the spammers wouldn't understand BCC, and we'd get a look at the
>>> address list: All hackerspace contact emails. I finally realized that these
>>> folks were just scraping addresses from the hackerspaces.org wiki.
>>>
>>> I finally went and changed the contact address on our entry, and the
>>> volume seems to have fallen off quite sharply. A real human trying to
>>> contact us should figure it out in no time. But I wonder whether anyone
>>> else has taken this step, and how many more will be pushed to do so, and
>>> what this suggests for the future of the resource.
>>>
>>> -Nate B-
>>>
>>> _______________________________________________
>>> Discuss mailing list
>>> Discuss at lists.hackerspaces.org
>>> http://lists.hackerspaces.org/mailman/listinfo/discuss
>>>
>>>
>>
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
>>
>>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20141027/160f9b44/attachment-0001.html>