Security ideas

1: Sticker visibility controls

Context: The stickers are one of the pros of GJ to make some posts funnier. Sadly, some jolters use them to create art posts a bit awkward by placing them on private parts, for example, to make them a bit more lewd.

--

Recommendation: The owner of the post in question can delete awkward stickers (or turn them invisible if charged) to clean the post.

------------------------------------

2: External link safety

Context: This is just a little thing, but many scam links don't have a secured connection, so having HTTP in the URL instead of HTTPS.

--

Recommendation: Prevent opening any links that are not HTTPS (secured). A little move that can help a few, right?

-------------------------------------

3: Play my game, pleeeaasseee

Context: Let's be honest jolters, how many times our posts were polluted by jolters massively posting links to their games and asking people to try them? Just annoying.

--

Recommendation: Adding a new rule about "If you spam unwanted commercials on GJ, your game will be timed out 1-2 days", just to keep them in order minimally.

---------------------------------------

4: Accept. The. Block.

Context: How many times do we daily see people posting stuff like "Why are you blocking me?" "What did I even do for being blocked??", etc etc. Annoying child behaviours.

--

Recommendation: This is more a goofy idea than a big one, but if the textarea catches the sentence "why are you blocking me" and mentions a user (after fetch seeing he blocked them), change the string for "Accept the block".
I bet it will be fun for Fernando to do.

--------------------------------------------

5: Report one time DANG IT

Context: If there is a problematic user, people will use the report button as intended for the GJ team to handle it. However, some users can be intense and use it a LOT of time, causing more delay in handling the situation.

--

Recommendation: Have a cooldown when a jolter reports a user to avoid spam reporting them. Something like: "You already reported this user like 2 sec ago. Do you suffer from amnesia? Hmm".

-----------------------------------------

6: The more is reported, the more an action must be fast

Context: If a specific post, in the same timelapse, is reported by multiple different users. Let's say there is no chance to be a video about a guy drinking a glass of water.

--

Recommendation: If a specific post is reported, let's say, 10-15 times in the same X hour(s), the post will be temporarily unlisted to be reviewed by a GJ mod to be sure there is nothing not okidokie there. Can prevent a lot of drama and quick response, even if mods are on a coffee break.

----------------------------------------------

7: Integrating Google Lens API to be considered

Context: Let's be honest, ladies and gentlemen. Recently, we got a LOT of 18+ images around that no one asked to see. The report button is the main tool to handle them, but sometimes, not quick enough to start a fire.

--

Recommendation: I was thinking for nearly 10 minutes about "How can we stop an 18+ photo being sent on GJ without it being published?". The answer is Google Lens API:

I read the doc, and there is some object in the JSON worth to be considered:

Source is MAYBE the key to this problem. If GJ do a little JSON file with an array of xxx website links. We can do the following check:

• If the image about to be sent has no source from xxxwebsite . json => accept the publish.

• If the source of the image about to be sent matches with an xxx website from the JSON => block the publish.

I know and I am aware that NOT every lewd image is detectable on Google Lens, but most of them yes.