Fama Product Release Notes: Renaming “Harassment” Behavior Flag to "Trolling"

Based on customer feedback, Fama is changing the name of our “Harassment” Behavior Flag to “Trolling.“ What we flag on reports will not change, just the name of the Behavioral Flag that appears on Fama reports.

What’s changing?

1. Moving forward, the flag known as “Harassment” will now be called “Trolling,” defined as “Online harassment, and content that bullies, intimidates, ostracizes, shames, name-calls, or insults a person.”

2. All mentions of “Harassment” within the new Fama web application and on new Fama reports will display as “Trolling.” Reports on the older web application will continue to display the “Harassment” label.

All online report Harassment flags will be relabeled from “Harassment” to “Trolling.” This change will occur automatically on new and old reports. This change will appear across flagged content, filtering options, and sorting features.
All new PDF reports will display the “Trolling” label when downloaded. Old downloaded reports will contain the “Harassment” label on them. Old reports can be updated to display the “Trolling” label by manually regenerating the PDF from the drop down menu.‍

Please note: the original version of the report with the Harassment flag will be updated and no longer available. If you would like the report with the previous Harassment terminology, please download the PDF before regenerating the PDF.

What to do?

Non-API Customers: If you do not use Fama’s API, you do not need to take any action. If you would like to update older PDF reports created in Fama’s new web application to display the updated “Trolling” terminology, please manually regenerate PDFs as indicated in the image above.
API Customers: If you use a Fama API, you will need to check your integration to make sure you do not experience a break. The changes we have made to rename “Harassment” to “Trolling” will be updated in the data returned from our API. This will affect new and existing reports. If your API integration pulls the behavior labels directly from the returned data, the naming convention will update automatically and no action is required. However, if you apply any business logic for styling or formatting based on the behavior names, you will need to add a new case for this update. Below is an example payload before and after the labeling change.