logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git

Fighting Harrassement.xhtml (1927B)


  1. <article xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" class="h-entry">
  2. <a class="u-url" href="/articles/Fighting%20Harrassement"><h1 class="p-name">Fighting Harrassement</h1></a>
  3. <p>After reading <a href="http://mrsroots.fr/2016/11/25/lillusion-du-signalement-ou-la-gangraine-des-reseaux-sociaux">this post</a>(in french). I noticed that theses new techniques are basically the same as for fighting spam years ago, and there the definition of spam by [Pirate Bay Member] makes even more sense. Basically spam got defined by “unwanted messages”, which is true for most commercial-messages and harassement.</p>
  4. <p>And so I think we can actually reuse anti-spam software/code to make it more diverse and able to block not only commercial/weird messages but <strong>all</strong> unwanted messages.</p>
  5. <p>I’ll code something I can use for most of my messaging software as I do also receive unwanted messages not flagged as traditionnal spam.</p>
  6. Type of programs and example that can be useful for inspiration:
  7. <ul>
  8. <li>Spam-filtering: SpamAssasin</li>
  9. <li>Spam-slowing: spamd</li>
  10. </ul>
  11. Requirements for the code:
  12. <ul>
  13. <li>Highly portable(OS and existing clients)</li>
  14. <li>Well documented/commented</li>
  15. <li>Easy to read (≠obfuscation)</li>
  16. <li>Doesn’t censor / Filter by final score</li>
  17. <li>Verbose mode</li>
  18. </ul>
  19. <p>Also I think accounts like <a href="http://twitter.com/SaferBlueBird">@SaferBlueBird</a> are mostly bad because it’s managed by few people and actually censors things they doesn’t want to, also it’s totalitarist/oligarchist, only one/few people are needed to start the storm of reports. I follow it because at the moment it’s the best solution we have…</p>
  20. <p>Warning: It’s a concept, useable software might not exist at the end, feel free to contact me if you want to participate in it (even if you don’t know how to code, everyone can be useful)</p>
  21. </article>