Search Results for 'spam'
-
AuthorSearch Results
-
March 14, 2011 at 5:02 am #107724
In reply to: Is anyone using Cloudflare?
LPH2005
ParticipantBased on the testimonials, cloudflare might help with spam problems, too. Let us know.
March 10, 2011 at 8:56 pm #107469In reply to: Buddypress roles
larrysmith1000
Member“Providing that flexibility is nice. However, with the exception of groups, there is no reason that the current BP core components need to offer the ability to assign roles. Why would a user want to grant someone the right to control their personal content? Facebook and Twitter don’t offer users that option.” — Jeff Sayre
Hi Jeff, sorry to reopen this topic, but I think it needs a revisiting.
The ability to easily hook into wp user capabilities and extend them to buddypress user capabilities is useful in several social network contexts. And, I hope buddypress is trying to be a more flexible platform than facebook or twitter since it is an open source platform that developers would like to be robust and scalable. I understand the idea of an egalitarian social network like facebook, etc. However, there are many social contexts in which a hierarchical social network structure might be needed. Furthermore, adding the flexibility to developers as an additional component of buddypress would not complicate it’s egalitarian default settings.
One example of a hierarchical context is an educational institution with Administrators, Professors, Instructors, Teaching Assistants, Students, Prospective Students, Alumni, etc.:
As it is now, there are only bbPress roles within groups (which are needed). However, without the ability to assign capabilities within buddypress outside the scope of groups, it is nearly impossible to create capabilities restrictions such as:
user_may_create_groups
user_may_start_forum
user_may_delete_comment (e.g. spam or inappropriate comments)
user_may_assign_capabilities
and so on.In particular, the ability to restrict certain users from creating groups has been a topic in many other forums about buddypress. Yet, it hasn’t been well addressed.
Paul Wong-Gibbs
Keymaster@xxxxx Stop notification spamming. Consider this your third (and final?) warning.
March 8, 2011 at 10:17 am #107167In reply to: How to avoid spam registration?
Jose Conti
ParticipantHi,
You can try WangGuard https://buddypress.org/community/groups/wangguard/
March 7, 2011 at 2:22 pm #107054Rob 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
March 6, 2011 at 2:20 am #106934r-a-y
Keymaster[EDIT]
“blocked” and “inactive” roles appear to come from bbPress as this is not native to WordPress. My suggestion would be to *not* use these roles at all for the moment.If you’re using multisite, just use WordPress’ native Network Admin user administration panel and set users as spammers:
https://codex.wordpress.org/Network_Admin_Users_ScreenDo not use the regular WP admin users screen for this!
https://codex.wordpress.org/Users_Users_SubPanelMarch 5, 2011 at 7:55 pm #106914Virtuali
ParticipantNO, this is NOT a buddypress problem.
If you mark a user as Spammer, does it block him from logging in?
Use a plugin called “wp-ban” to ban users
March 5, 2011 at 3:28 pm #106893ParticipantDo you have buddypress installed? This is not really a bp issue. Although if you do have buddypress installed, just mark him as spammer
March 4, 2011 at 3:42 am #106782In reply to: How to avoid spam registration?
matthewalan
MemberOkay, what are some examples of software for that?
March 4, 2011 at 12:59 am #106770In reply to: How to avoid spam registration?
ParticipantYou 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.
March 3, 2011 at 8:55 pm #106755In reply to: What do your spam signups look like?
phcapgh
MemberHello,
I am leaving this here in case anybody else is at wits end with this problem. I installed the following plugin:https://wordpress.org/extend/plugins/si-captcha-for-wordpress/
It is a capcha for subscriber sign up. Our buddypress has not been released yet, and we were getting upwards of a dozen spam sign ups a day. I installed this plugin a week ago. So far, no spam signups. I hope this helps.
March 3, 2011 at 8:52 pm #106753Morgue89
MemberDo you put the capatcha only on the registration area or on other parts of your site as well?
March 3, 2011 at 8:31 pm #106752MemberI have been fighting this issue for awhile. Last week, I found this plug in:
https://wordpress.org/extend/plugins/si-captcha-for-wordpress/
I’ve gone from dozens of spam subscribers a day to nothing over the last week. I hope this helps.
March 3, 2011 at 10:37 am #106708In reply to: How to stop spam registration?
ParticipantHi,
Test this plugin: https://buddypress.org/community/groups/wangguard/
March 3, 2011 at 10:37 am #106707ParticipantHi,
Test this new plugin: https://buddypress.org/community/groups/wangguard/
March 3, 2011 at 10:07 am #106706In reply to: Found this all new 'Anti-Splog_ anti -spam for BP
ParticipantHi,
There is a new anti-splog plugin, you can try it, is free for personal use:
March 2, 2011 at 5:31 am #106648In reply to: How to I delete Groups started by spammers?
gregfielding
ParticipantThanks guys.
March 2, 2011 at 4:38 am #106641In reply to: How to I delete Groups started by spammers?
March 2, 2011 at 3:30 am #106637In reply to: How to I delete Groups started by spammers?
Pisanojm
ParticipantGreg,
You have to do this front-end…. go to the group.. choose the admin link –> then delete group… There are some plugins for the back-end management of groups too…
February 26, 2011 at 8:40 am #106354In reply to: WordPress 3.1
zkwc
Participant@josh101 I totally hear ya!
i found another (insert curse word here) bug. When you mark someone as a spammer from their profile in Buddypress – they don’t actually get marked as a spammer on backend. Probably because of this (insert curse word here) way of separating the stupid (insert curse word here) network admin from regular admin. This is totally reedonkulas. So now… deleting spam got even harder. And I know for certain some of my spam plug-ins got broken too. So they are descending upon me like …. it’s not even worth discussing anymore. I’m just going to get angrier.
edit:
and… (am i angrier… yes) when you delete the (cuss word) spam after you’ve clicked on “registered” to make it show last joined and first joined, it reverts to alphabetical again just to piss you off and make you have to click the stupid “registered” button again to show first joined or last joined. Welcome to HOURS of spam deleting made possible to you by WordPress… the official WP motto “we aren’t into efficiency, we’re just into kicking all of you in the stomach”
February 26, 2011 at 5:33 am #106345In reply to: WordPress 3.1
Participant@travel-junkie – I get over 2 million hits per month to my site. I get at least 400 spam sign ups a week. This is not an efficient change!
February 25, 2011 at 11:22 pm #106328In reply to: WordPress 3.1
Anonymous User 96400
Inactive@zkwc
Well, I get around 1 spam signup a week, if that. On any of my BP sites. For me, alphabetic ordering makes sense. And it would be for most WP sites (most of which aren’t BP enabled sites, btw). Obviously, WP development is separate from BP development, so changes made to WP might not make much sense for some BP users, but a lot of sense for the majority of WP users. Just some food for thought…I just upgraded 7 of my sites to WP 3.1 plus a few client ones and didn’t have any plugin problems at all. With the widespread adoption of WP it’s natural that some sites will experience problems, but don’t make this out to be an issue for everybody, when in fact it isn’t.
As for the network admin page, this way is more organized. Stay on the current blog admin page to handle everything to do with this particular blog, go to the network page for anything related to running the network, like sitewide enabled plugins. To me this makes sense…
February 25, 2011 at 10:18 pm #106321In reply to: WordPress 3.1
Participant@chouf1 try uploading a picture. It doesn’t work. Where is the settings options on the BP drop down menu in the plug-in list? Not there! He is aware and was on my website testing it. It broke their plug-in and many others. And the other change only makes sense if you want an hour tacked onto your administrative duties. Do you get at least 50 slogs and spammers a day? Good luck clicking around trying to delete them in the minute it used to take. UGH! I don’t know why you insist upon arguing about that. Unless you have a vested interest. I just feel sorry for all the plug-in developers who are frantically trying to make their stuff work. And now my site is broken. I’m screwed. Tried downgrading. Sucked. Didn’t work.
@ewebber I wish I had waited. You are making a wise decision!
February 25, 2011 at 12:19 pm #106257In reply to: WordPress 3.1
Participant@DJPaul – well, people ought to know that if they are running plug-ins (any plug-ins including spam plug-ins) that most of their installed plug-ins are going to get killed. Including Welcome Pack. And I did comment on the WordPress site. Not happy. There is no way there was enough testing on this. On Buddypress side, things are working fine. It’s WordPress. All my major plug-ins… dead. Now I’m going to have to revert back to the previous versions. I really shouldn’t have hit the update button. But… you’d think that you should be safe to do so.
February 25, 2011 at 9:43 am #106244In reply to: WordPress 3.1
ParticipantWP really irritates. I’m going to refrain from using foul language because everyone who commented was able to.
It’s broken lots of the plug-ins I was using. Welcome Pack – doesn’t work. BP Album + – doesn’t work, although I spoke with the plug-in developer and he is currently working on a fix. I don’t know who the Welcome Pack developer is so I don’t know if he is aware that it is broken. The BP Album + developer didn’t know that their plug-in wasn’t working. So maybe the other plug-in developers don’t know that their plug-ins don’t work either. Who knows?
Wouldn’t it be easier if all the plug-in developers, BuddyPress, and WordPress somehow got on the same page so that all updates could be easily streamlined so that we didn’t need to go through this every time? If the plug-in developers were able to test their plug-ins before the updates were integrated that could save EVERYONE lots of headaches. Is it possible for this simple streamlining of events to happen? Can’t there be a centralized place where things are actually tested first?
Not only did WP break certain plug-ins but they’ve also changed the way “users” and “sites” are listed in the dashboard. They are all alphabetical now. If anyone knows about spammers and how OFTEN we have to mark them as spam on the fly or delete them, they will know that an alphabetical listing is not efficient. This is an IDIOTIC change. Having users and sites listed as first joined or created and last joined or created was better as deleting spam took 1 minute. Now it takes an hour. You have to click through each page or copy and paste the spammers user name into search users in order to delete or edit or whatever.
And what’s up with “network admin” and who thought that was a good idea? What’s going on WordPress? I know this isn’t a Buddypress issue, but a cook is a better designer of a kitchen than an architect. Just sayin’. UGH.
-
AuthorSearch Results
