Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'bots'

Viewing 25 results - 251 through 275 (of 415 total)
  • Author
    Search Results
  • #113694
    @mercime
    Participant

    Reality is that you would have to be proactive in killing those spam robots and human spammers if you have open registration. Search through BP.org shows many threads which share tips in plugins to use to prevent this and not all are 100% perfect since these spammers are really gung-ho about overcoming such preventions. Having said that, check out this thread – https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/has-anyone-tried-this-spammer-blocking-plugin-with-buddypress/

    #113276
    dennissmolek
    Participant

    I am currently writing my own theme that looks nothing like BP-default, but I’ve been on trac almost daily with the UI tickets. I don’t know if we need a dedicated “UI/UX” team, but as long as folks are submitting on those tickets it will ease some of the other dev’s needing to mess with it. I DO think it is an important component with BP and we need to keep talking about 1.3’s problems.

    I’m glad to see all the discussion going on, especially in light of all the “BP IS DEAD” nonsense. I think the biggest issue is how the forums make it hard to actually talk, but the testBP forums are great and I’m excited to see them go live here. I’m also anxious to see the new BP.org which seems to be slated to June.

    My biggest issue with the BP sites I run is spam. Even my non indexed test servers get spammed. My AIGA site was deleting 250 spam users/blogs a day before shutting off new user registration. The first part of that comes from spam users being registered. There are two types of spam services, bots, and (slave) labor. These folks get through the Captcha’s and set up real fake accounts. But in my experience with my comment forms adding a Captcha killed a vast majority of spamers. Then with comments, contact forms, etc this would kill most spam. From there heuristic spam fighting from splogs, comments, etc. Also a system that users can mark a item as spam would help a ton.

    Second, its that to learn how to do ANYTHING in BP I have to take something that works with the current version and hack it a part to figure out basic commands and actions. Once the new site is up I think there should be a real push on getting the Codex up to snuff(look at jQuery and WP) that have examples, resources, etc. Then have tutorials on things, hell syndicate them from other bloggers.

    So as my thing(s) I want to keep being a part of fixing UI issues, and will as long as I can.
    I want to write for the Codex, and am here and willing to write Blog articles for BP. Tutorials, Updates, whatever. I’m game. I will be writing tutorials for AIGA members anyway, so why not sync the content here.
    I am working on the Group Documents plugin with its original developer because my sites need it.

    And lastly I will be writing a BP-Spam component. I will do it as a plugin first and will want/need tons of feedback. But to get the University to sign off on my project I will need to stop all the Viagra and other inappropriate content from making it through. I will do this regardless of it being a part of BP but want to give back however I can.

    I’m so psyched to see all the energy is still in this project!

    gregfielding
    Participant

    Found it…thanks @aces !

    Robots Meta plugin was adding webmaster info that was already there.

    #108368

    In reply to: Spam registrations

    cjones81
    Member

    These automated bots are usually just that, automated that are programmed to look for specific strings in search engines that return a list of buddypress sites and then harvested. I was getting hammered with 20+ blogs getting created a day that was spam. I tried ever plugin and .htaccess tricks known to man and none of them worked. I was tired of all of the spam I was getting so I put on my tin foil and went to war. I was determined to win this war and to stop 99.9% of automated spam dead in its tracks.
    First I went to cpanel and under the “Website Traffic” on the left side of the page and clicked “View all traffic” then clicked on my domain name.

    When the statistics page for that domain loaded I looked on the left hand side of the page for “Search Keyphrases”, this will show me a list of the keyphrases that was used to find my site.

    I found all the keyphrases that was used by the spammers to find my site in the search engines and here is the list of the keyphrases.

    1. intext create an account username required email address required blog details inurl register
    2. to start connecting please log in first. you can also create an account. .cr. blogs
    3. allintext create an account account details profile details blog details yes i d like to create a new blog
    4. yes i d like to create a new blog
    5. “blog url required ” inurl /register
    6. “yes i’d like to create a new blog”
    7. intext create an account blog details inurl register
    8. to start connecting please log in first. you can also create an account. .be.blogs
    9. inurl register yes i d like to create a new blog
    10. intext blogs create an account username email address blog details inurl register
    11. to start connecting please log in first. you can also create an account. .de.

    What I did was I went downloaded the buddypress to my desktop and open every file with NotePad++ and started searching for “create an account; blog details; yes i d like to create a new blog” Once I found those strings, I changed the name to something else and on the registration page I removed the “yes i/d like to create a new blog” along with its checkbox completely and i searched everything with the word “blog” and changed it to something completely different. I Also renamed the “bp-blog.php” and the /bp-blog/ folder.
    Make sure to search through the other files in the buddypress folder for anything calling the “bp-blog.php” and the /bp-blogs/ and rename it accordingly.

    It has been a week since I done this and I have yet to be spammed. I went from 20 a day to zero overnight by doing this.

    mars-hill
    Member

    Hi Mikey3D, thanks for the fix – testing that in webmaster tools seems to be working. Have added to robots.txt.

    @mikey3d
    Participant

    You haven’t add Disallow: /? in your robots.txt file.

    mars-hill
    Member

    Thanks for your explanation, Boone. The fix is beyond my technical capabilities, and I appreciate you moving it to trac and looking into it.

    Boone Gorges
    Keymaster

    acpage is the way that BP renders activity pagination to those clients with javascript disabled – such as search engines.

    I started a ticket for discussion of technical issues: https://trac.buddypress.org/ticket/3116

    mars-hill
    Member

    Hi crew,

    Since installing BuddyPress, I’ve noticed that Google’s Webmaster Tools is finding pages with ?acpage=xx on the end.

    e.g.
    http://indietravelpodcast.com/ might read
    http://indietravelpodcast.com/?acpage=32
    http://indietravelpodcast.com/?acpage=2
    http://indietravelpodcast.com/?acpage=15
    etc.

    I’ve told Google to ignore it, via the Webmaster Tools > Settings > Parameter Handling function but it’s still showing up in search results, analytics and crawl errors.

    Doing a search on this support forum comes up null, searching for the string in Google just shows dozens of buddypress sites with the same issues.

    Does anyone know what ?acpage=xx is, does or how to get rid of it?

    If it is necessary to the running of a BuddyPress site, how can I stop Google from indexing it? (Especially since it seems to be causing penalties … lots of page not found and slow page load errors thanks to it.)

    #107922
    fizk
    Member

    r-a-y,

    Thanks, I’ve disabled registration. Hopefully this stops the bots completely.

    #107896
    gregfielding
    Participant

    I did install the plugin, but am afraid to hit the “Database Optimize” button because we use multiple databases.

    And yes, there is a way to block specific bots and ip addresses

    Rob Watson
    Member

    # There are lots of WordPress hacks designed to take the contents of your wp-config
    # file (username and password) and dump them to a text file a spambot can pickup and
    # send to a hacker. If you block access to wp-config file in your .htaccess using
    # this method, you block those hackers from getting your database login information.
    Order deny,allow
    deny from all

    # Turn off directory indexing to keep anyone from seeing the contents of a directory
    # if there is no index file.
    Options All -Indexes

    # Block known spambots and crawlers. Update the following section with newly discovered
    # spambots and crawlers. This blocks them from ripping off posts and images (costing
    # bandwidth in the process.
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTP_USER_AGENT} ^BlackWidow [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Bot mailto:craftbot@yahoo.com [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ChinaClaw [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Custo [OR]
    RewriteCond %{HTTP_USER_AGENT} ^DISCo [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Download Demon [OR]
    RewriteCond %{HTTP_USER_AGENT} ^eCatch [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EirGrabber [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Express WebPictures [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR]
    RewriteCond %{HTTP_USER_AGENT} ^EyeNetIE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^FlashGet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GetRight [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GetWeb! [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Go!Zilla [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Go-Ahead-Got-It [OR]
    RewriteCond %{HTTP_USER_AGENT} ^GrabNet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Grafula [OR]
    RewriteCond %{HTTP_USER_AGENT} ^HMView [OR]
    RewriteCond %{HTTP_USER_AGENT} HTTrack [NC,OR]
    RewriteCond %{HTTP_USER_AGENT} ^Image Stripper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Image Sucker [OR]
    RewriteCond %{HTTP_USER_AGENT} Indy Library [NC,OR]
    RewriteCond %{HTTP_USER_AGENT} ^InterGET [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Internet Ninja [OR]
    RewriteCond %{HTTP_USER_AGENT} ^JetCar [OR]
    RewriteCond %{HTTP_USER_AGENT} ^JOC Web Spider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^larbin [OR]
    RewriteCond %{HTTP_USER_AGENT} ^LeechFTP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Mass Downloader [OR]
    RewriteCond %{HTTP_USER_AGENT} ^MIDown tool [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Mister PiX [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Navroad [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NearSite [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetAnts [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetSpider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Net Vampire [OR]
    RewriteCond %{HTTP_USER_AGENT} ^NetZIP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Octopus [OR]

    RewriteCond %{HTTP_USER_AGENT} ^Offline Explorer [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Offline Navigator [OR]
    RewriteCond %{HTTP_USER_AGENT} ^PageGrabber [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Papa Foto [OR]
    RewriteCond %{HTTP_USER_AGENT} ^pavuk [OR]
    RewriteCond %{HTTP_USER_AGENT} ^pcBrowser [OR]
    RewriteCond %{HTTP_USER_AGENT} ^RealDownload [OR]
    RewriteCond %{HTTP_USER_AGENT} ^ReGet [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SiteSnagger [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SmartDownload [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SuperBot [OR]
    RewriteCond %{HTTP_USER_AGENT} ^SuperHTTP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Surfbot [OR]
    RewriteCond %{HTTP_USER_AGENT} ^tAkeOut [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Teleport Pro [OR]
    RewriteCond %{HTTP_USER_AGENT} ^VoidEYE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Web Image Collector [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Web Sucker [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebAuto [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebCopier [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebFetch [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebGo IS [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebLeacher [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebReaper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebSauger [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Website eXtractor [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Website Quester [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebStripper [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebWhacker [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WebZIP [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Wget [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Widow [OR]
    RewriteCond %{HTTP_USER_AGENT} ^WWWOFFLE [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Xaldon WebSpider [OR]
    RewriteCond %{HTTP_USER_AGENT} ^Zeus
    RewriteRule ^.* – [F,L]

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    #106770
    Virtuali
    Participant

    You must search for anti-spam plugins that filter out spam activity that the users make.

    If the “spammers” are going past the captcha, that means they are not robots, actually people, just spamming your site.

    So keep the captcha for robots, and you will need to search for anti-spam software to filter out the spam content posted on your site.

    #105839
    modemlooper
    Moderator

    You create a file called robots.txt and you specify which URL so for instance it could be anything after /activity

    User-agent: Googlebot
    Disallow: /activity/*

    This blocks google from scraping your images. This is a MUST for social networks that are using Albums.
    User-agent: Googlebot-Image
    Disallow: /

    #105821

    In reply to: BP_register_Slug

    imjscn
    Participant

    @modemlooper, thanks for your suggestion on different forms for different users in the register.php.
    I also want to change the register slug. Because spam bots know bp register slug. We can get rid of a lot of them by simply change the register slug. But, how?

    #19798
    sverdlov
    Member

    Hi there,

    I’ve been trying to set up a new buddypress community for the past 2 weeks – and everything seems to be working, with a few exceptions..

    Few days ago when I created a new user from wp-admin, it appeared in the members directory too. Now, when I create a new user, it doesn’t get created in Buddypress… the question is, why could that happen, and how do I manually add a user to buddypress after it has been added to wp-admin? Buddypress profile syncing is enabled.

    2. How do I manage the forums? I mean… how do I create topics for discussion, etc? Or is it just groups? I thought bbpress has more features in managing the forums?

    3. Is it possible to… well… allow registration, but hold users for moderation until their user is “approved”? I don’t want to allow open registration… I had it open for a few hours, and the site filled up with bots… I have since enabled captcha, but that doesn’t stop malicious users from signing up…

    #104816
    thinkinbox
    Member

    Solved. I’m an idiot.
    user_spam_remover Plugin was improperly configured.

    As a side note: If you use buddypress for commenting, the User Spam Remover plugin won’t pick up on buddypress activity as being actual site activity – thus causing users to be mistaken as spam bots.

    #103930
    thealchemist
    Member

    @hnla I know that there will be a segment of the population who will be prevented from joining because I am blocking IP addresses. But, I want/need these prevented in the first place and I do not understand why this is not addressed in the core and has to be something I must “hunt through the forum threads to reducing spam signups”. Its not like this is an unknown issue.

    Besides, I HAVE searched for “reduce spambots” “reduce fake sign ups” “Reduce and reducing spam sign ups” with zero results.

    #103925
    thealchemist
    Member

    What I have to ask is “Why?” and “How?” are these spambots accessing and creating users? I have one site that uses WP multisite with BP and there’s a great plugin “BP Registration Options” that works well enough to grab and display all new member requests and displays IP addresses; which I then add to WP-Ban. Its taken a month but I am now down to a dozen or so spambot signups per day.

    Now, I have another WP/BP site that is NOT multisite and “BP Registration Options” does not work the same. BUT I copy the IP addresses from the one and paste it into the “WP Ban” of this site. However, I am still 100+ spambot signups per day. So, I have a plugin “Pending Activations” (which doesn’t work in multisite) but this plugin does not display the IP address of the offending spambot signups. Thus, my battle with the signups continues …

    So … How are the spambots signing up? Why does the registration form not have CAPTCHA? and how can we stop them from signing up?

    Nahum
    Participant

    Has anyone got/seen a tutorial/reference/tips/how-to’s/anything for the best way to setup robots.txt and a sitemap for buddypress components. I’ve literally searched all day with no success in finding anything. I’ve tried the bp sitemap generator but haven’t had luck getting it work work, the files get generated but I get a error invalid feed template and google won’t accept it. So if anyone could pass a little good energy this way…i’d be appreciate it.

    How to setup sitemap generator for BP and Any other suggestions on what to put in the robots.txt would be cool….thanks

    #103270
    Andrea Rennick
    Participant

    “how to disallow bots to follow signup link?”

    Put a nofollow, noindex on it, right in the theme where it is linked. And change the default text that is linked. If you look at your access logs and your visitor stats, you’ll see they basically google for you.

    #103240
    Hugo Ashmore
    Participant

    @imjscn try hunting for a plugin called KB robots text it allows you to edit the WP robots text from the dashboard and might be handy to have available.

    #103232
    imjscn
    Participant

    @hnla,
    I failed to search out your robots.txt thread. But I found this one was recommended in another thread: http://perishablepress.com/press/2010/07/14/blackhole-bad-bots/
    I will try it and feed back.
    By the way, the .htaccess referer trap doesn’t work.

    #103231
    Hugo Ashmore
    Participant

    #2 stops bots following the link on other pages, but BP spammers come without a reference page. They know which link is BP register page. I’m not sure if there’s another way for BP.
    Jenny this is why I said or mentioned adding a referer trap in .htaccess. Yes bots do link directly so you disallow any direct links that do not contain a referer in the header get request

    #103230
    Hugo Ashmore
    Participant

    True search here is a chore :)

    Robots.txt is a file that lives in the root document directory of a site, however I seem to remember issues in the past adding one as WP might be trying to add it’s own one?

    What results – if any do you get from running:

    http://example.com/robots.txt (your site name obviously)

Viewing 25 results - 251 through 275 (of 415 total)
Skip to toolbar