joschan21 / profanity.dev Goto Github PK

yea.

Went ahead and make a Python library for this: https://pypi.org/project/profanity-api/

I am a new contributors and it would be nice to others new newcomers if they could can quickly understand the project and get started without needing to ask questions or search through code.

I think it is a key tool for a project like this. Maybe someone is already working on this, but I didn't found it in my quick tour.

Thanks!

like "its h" gets for sh_t
same for n and more!

Use form for the demo so as to enable checkProfanity mutation to be run when the user presses the enter key.

Onnx can be perfomatic
https://onnxruntime.ai/docs/get-started/with-javascript/node.html

Found below 2 warning while running on local -

1. Using <img> could result in slower LCP and higher bandwidth. Consider using <Image /> from next/image to automatically optimize images.
2. img elements must have an alt prop, either with meaningful text, or an empty string for decorative images.

Allow developers to configure it, such as allowing them to add custom allowed or blocked words, and disable specific categories from being flagged (as an example, allowing fuck this, but not allowing racial slurs)

using the default prompt ending with the letter f flags it as profanity

swear words with spaces in between them, dont work.

the reason for this is that they naturally score lower, as shown here:

alsowhenwordsaretogether:

and also ascii text isnt supported:



etc etc... i used https://lingojam.com/SpecialText for this

other languages:

^ tbf turkish is obscure but- still...

random letters? honestly i dont know what the correlation is, but if i find one ill update it:

theres a million ways to cheese this, i think this project would be awesome if you kept on adding to it!
if nobody plans on implimenting it, i could give it a try :p

Phrases like:

• "dog dog dog"
• "monkey monkey monkey"

trick the algorithm into responding with false positives. Just remove repeating words, could improve API latency and accuracy.

bad practice to leave the end of lines empty without a semicolon (;)

using the default prompt ending with the letter f flags it as profanity

Every online FPS:

commit not live

Avatar the Last Air Bender:

I'll end you

https://choosealicense.com/

I was unable to find a LICENSE file at the root or in the sub project folders. I would appreciate it if the license terms for this code were clarified in a standard LICENSE file 😜

Quote from https://choosealicense.com/no-permission/

No License

When you make a creative work (which includes code), the work is under exclusive copyright by default. Unless you include a license that specifies otherwise, nobody else can copy, distribute, or modify your work without being at risk of take-downs, shake-downs, or litigation. Once the work has other contributors (each a copyright holder), “nobody” starts including you.

tldr nobody can use the code without you giving them permission via a LICENSE of some kind 🤷‍♂️ and right now there is no clear LICENSE 😭

currently this (pretty cool!) project isn't open-source, just source-available. see here and here

While checking out PR #11 I realized that supporting multi languages should be fairly easy to implement, however I would allow an optional langs parameter to pass a list of languages (eg eng,deu,ita) and split each language in its own training data.

If no langs param is passed, then all are checked.

Why? Well:

1. we don't want to update/rebuild the whole vector/dataset if we add a new language or update an exisiting one
2. we don't want to overload the server if we know that a certain site is going to use mostly one or two languages (eg, german and english)
3. it makes the code more sustainable (not just a single huge .csv file with a bunch of commits)

When I use text symbol "ｆ" which looks almost the same as "f" the app doesn't detect it.
Would be nice if App treat that symbol same as character f

Found a comment on the recent Youtube video that mentioned sending the input "mosquitoes suck blood" is flagged as 1.000 profanity. Tried this a few more times and noticed that the word "suck" is the culprit. Funnily enough, the word "sucks" is not flagged like this.

Should we whitelist this word along with the several others that are whitelisted right now?

Description
Currently, the website and API only supports text input in the form of JSON. However, it would be beneficial to have the ability to input PDF files and send them through the API for processing.

Proposed Solution

1. PDF File Input: Add a new file input field or drag-and-drop area to allow users to upload PDF files directly into the application.

2. API Support for PDF Files: Extend the existing API endpoints to accept PDF file uploads and process them accordingly. This could involve converting the PDF to text or images, depending on the use case.

@joschan21, I would like to work on this if you approve of this feature.