# Profanity filter

**URL:** <https://community.glideapps.com/t/profanity-filter/74483>\
**Category:** Ask for Help\
**Created:** [June 29, 2024, 10:27pm UTC](https://community.glideapps.com/t/profanity-filter/74483 "2024-06-29T22:27:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jake\_Rushby1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jake_rushby1/32/77087_2.png) [@jake\_Rushby1](https://community.glideapps.com/u/jake_Rushby1)\
**Post date:** [June 29, 2024, 10:27pm UTC](https://community.glideapps.com/t/profanity-filter/74483/1 "2024-06-29T22:27:23Z")

</div>

Hi, im wondering if Glide itself has a profanity filter/website link blocker built in? and if not would i need to create a list of words that are not acceptable and do visibility filters on the front end “x” does not contain “y”?

this would prevent it being visible on the front end so no-one could see the profanity or be taken to a strange link? or would there be a way of preventing the input from the beginning in the data sheets?

thanks community 🙂

---

<div class="post-metadata">

**Author:** ![Himaladin](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/himaladin/32/71023_2.png) [@Himaladin](https://community.glideapps.com/u/Himaladin)\
**Post date:** [June 29, 2024, 11:00pm UTC](https://community.glideapps.com/t/profanity-filter/74483/2 "2024-06-29T23:00:40Z")

</div>

This topic has been discussed in another thread. You can use Glide’s AI.

> [@Prohibit profanity in usernames](https://community.glideapps.com/t/prohibit-profanity-in-usernames/73816/5):
>
> Robert Petito once demonstrated in his video the use of open AI in a Build AI chat. I haven’t tried Glide’s native AI for profanity. You can see it around the 25 minute mark [[Build No Code Private and AI Chats using the Glide Chat Component] ](https://www.youtube.com/watch?v=c0vW0GFc2io)

---

<div class="post-metadata">

**Author:** ![jake\_Rushby1](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jake_rushby1/32/77087_2.png) [@jake\_Rushby1](https://community.glideapps.com/u/jake_Rushby1)\
**Post date:** [June 30, 2024, 6:50pm UTC](https://community.glideapps.com/t/profanity-filter/74483/3 "2024-06-30T18:50:57Z")

</div>

thankyou for your response all though this is in theory a more efficient solution to the problem, using 3-6 updates every single time something is typed is not efficient in costs. this would wrack up very high costs/ where as a visability/data limiters would be able to hide the potentially offesnsive material, and a simple if then else check on the back end to show someone using offesnsive language/materials letting the account be reviewed.

what are your thoughts on this?

thank you

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 30, 2024, 11:35pm UTC](https://community.glideapps.com/t/profanity-filter/74483/4 "2024-06-30T23:35:12Z")

</div>

Preventing it to be created would be the most efficient in my opinion.

> [@Exploring the Enhanced Capabilities of Glide's Native Form](https://community.glideapps.com/t/exploring-the-enhanced-capabilities-of-glides-native-form/69876/1):
>
> I want to share about the additional capabilities that we can achieve with Glide’s native form. What I have tested with the help of CSS is that native forms can also be applied for validation. Create your validation in the table columns and present it through messages via the “hint” component. Add the visibility conditional and the class “prevent-submit” to these hint components. Add the following CSS code: /\*Container Form\*/ #page-root:has(.prevent-submi…