Famous spam removal script for Hubzilla which came in handy since mad Ivan Zlax started terrorizing the Fediverse.git.c-r-t.tk
#!/usr/bin/env ruby
# Load diaspora environment
ENV["RAILS_ENV"] ||= "production"
require_relative "config/environment"
toxic_accounts = Person.find_by_substring('ivan zlax')
toxic_list = toxic_accounts.map { |z| z.diaspora_handle }
toxic_list.append('vm66%@diaspora.ruhrmail.de', 'ivan_exlax@pod.dapor.net ', 'zlax@%', 'zlaxyizlax@%')
puts toxic_list.inspect
#exit
for toxic in toxic_list do
puts "Blocking and cleaning #{toxic}"
local_spammers, remote_spammers = Person.where("diaspora_handle LIKE ?", toxic).where(closed_account: false).partition(&:local?)
# Retract all comments of local spammers and close their accounts
local_spammers.each do |spammer|
Comment.where(author_id: spammer.id).each do |comment|
puts "delete #{comment.guid} from post #{comment.parent.guid}"
spammer.owner.retract(comment)
end
spammer.owner.close_account!
end
# Retract all spam comments on posts of local users and delete the rest
Comment.where(author_id: remote_spammers.map(&:id)).each do |comment|
puts "delete #{comment.guid} from post #{comment.parent.guid}"
post_author = comment.parent.author
if post_author.local?
post_author.owner.retract(comment)
else
comment.destroy
end
end
# Close accounts of remote users if wanted
remote_spammers.each do |spammer|
puts "close account #{spammer.diaspora_handle}"
#AccountDeleter.new(spammer.diaspora_handle).perform!
spammer.update_column(:serialized_public_key, "BLOCKED")
puts "closed account #{spammer.diaspora_handle}"
end
end
#!/usr/bin/env ruby
# Load diaspora environment
ENV["RAILS_ENV"] ||= "production"
require_relative "config/environment"
for toxic in [ 'ivan_exlax@pod.dapor.net ', 'zlax@%', 'zlaxyizlax@%' ] do
puts "Blocking and cleaning #{toxic}"
local_spammers, remote_spammers = Person.where("diaspora_handle LIKE ?", toxic).where(closed_account: false).partition(&:local?)
# Retract all comments of local spammers and close their accounts
local_spammers.each do |spammer|
Comment.where(author_id: spammer.id).each do |comment|
puts "delete #{comment.guid} from post #{comment.parent.guid}"
spammer.owner.retract(comment)
end
spammer.owner.close_account!
end
# Retract all spam comments on posts of local users and delete the rest
Comment.where(author_id: remote_spammers.map(&:id)).each do |comment|
puts "delete #{comment.guid} from post #{comment.parent.guid}"
post_author = comment.parent.author
if post_author.local?
post_author.owner.retract(comment)
else
comment.destroy
end
end
# Close accounts of remote users if wanted
remote_spammers.each do |spammer|
puts "close account #{spammer.diaspora_handle}"
#AccountDeleter.new(spammer.diaspora_handle).perform!
spammer.update_column(:serialized_public_key, "BLOCKED")
puts "closed account #{spammer.diaspora_handle}"
end
end
I have tried to search for a place which actually summarize what antispam possibilities a podmin have. So, I have seen several threads, most of them from many years ago, mentioning various spam problems: how to control spammy registrations on the pod how to control fake email for the spammy accounts (how not to send email with unverified addresses) how to control connections and content of spammy pods how a podmin can destroy a spammy acocunts’ contributions (posts, comments, likes, whatever...discourse.diasporafoundation.org
Your reputation and business are at stake!
We on your behalf in the message your website address EXAMPLE.COM and your contact information (including in social. Networks and messengers) will send:
+ on 15,897,318 sites, threats with insults to site owners, US residents, Europeans, LGBT and BLM.
+ 790,000 messages to bloggers with threats and insults
+ 2 367 896 public figures and politicians (from the USA and Europe) with threats and insults
+ 70,000 negative reviews about you and your website EXAMPLE.COM
+ 23 467 849 contact forms of sites with threats and insults
+ 150,000 emails messages to people with disabilities with threats and insults, many of them will definitely sue you
+ 57000 emails of messages to veterans with threats and insults, FOR THIS YOU WILL BE EXACTLY SITTED
Following from all of the above, you will get a lot of losses:
+ an abuse from spam house, amazon and many webmasters (for spam, insults and threats) will come to your site EXAMPLE.COM, as a result, your domain will be banned and blacklisted
+ people will sue you because you threatened and humiliated them
+ in court you will not prove anything, everything will look as if you did it all, MOST YOU WILL GO TO PRISON
+ internet will be inundated with negative reviews about you and your website EXAMPLE.COM
+ threats and reprisals from BLM and LGBT community members, in fact, these are dangerous community guys
Total: you will lose your business, all your money, you will spend on lawyers and compensation for court decisions, you will go to jail, your life will turn to hell ...
We already have everything ready to launch all of the above, but we decided to give you a chance to avoid all this, you can buy off a small amount of money.
Make a payment, transfer 0.39 Bitcoins to this address
1JDYfBMP3vg8TcuFuwSHc1Wop3rREqupC4
We are waiting for the transfer from you until November 27, on Saturday November 28, if payment does not come from you, we will begin to destroy your business and you along with it.
Various approaches have been employed over many years to distinguish human users of web sites from robots. The traditional CAPTCHA approach asking users to identify obscured text in an image remains common, but other approaches have emerged. All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, further complicating the challenge of providing services secured from robotic intrusion yet accessible to people with disabilities. This document examines a number of approaches that allow systems to test for human users and the extent to which these approaches adequately accommodate people with disabilities, including recent non-interactive and tokenized approaches. We have grouped these approaches by two category classifications: Stand-Alone Approaches that can be deployed on a web host without engaging the services of unrelated third parties and Multi-Party Approaches that engage the services of an unrelated third party.www.w3.org