stylegan2-pytorch VS CyberChef

export default function ChannelListBottomBar(): JSX.Element { const { client } = useChatContext(); const [micActive, setMicActive] = useState(false); const [audioActive, setAudioActive] = useState(false); return (

{client.user?.image && (

div> )}

{client.user?.name} span> {client.user?.online ? 'Online' : 'Offline'} span> p> button>

setMicActive((currentValue) => !currentValue)} > button> setAudioActive((currentValue) => !currentValue)} > button> button> div> ); }

I wonder if we will ever get a realism model which can produce normal faces like https://thispersondoesnotexist.com instead of like super symmetrical faces of models

this has been in circulation since a while AI images took off, and they certainly weren't convincing before they did. You know the old "try to name one thing in this image" macro? Pretty sure that was AI generated, there was also thispersondoesnotexist.com which was always pretty good but of course it is

Not the workflow for these images, but if you easily want to spice up your gens with a bit more natural look, try using images from thispersondoesnotexist.com with IPAdapter face model.

...then they just use the app on generated images of not real people (potentially based on specific inputs to remind you of a real person).

Also we can generate very realistic faces with AI, https://thispersondoesnotexist.com/ (old example), fully 3D faces are doable at this point. So in another 5-10 years a low profile model like him wouldn't even be hired for this, they would just generate a digital face model. Unionizing will only speed up studios adoption of digital replacements.

It looks like they all use a profile picture made with https://thispersondoesnotexist.com/

Then we take the encrypted text and use CyberChef to decrypt it.

Let's go to CyberChef and insert our pieces of evidence.

A parameter was changed from '2AMBCgIQBg' to 'CgIIAdgDAQ%3D%3D' which is just the correct base64 encoding they should have been using the entire time.

I don't think this was a hostile action by Google, I think someone just added better input validation for security reasons and it accidently broke the bad requests they were sending.

https://gchq.github.io/CyberChef/#recipe=URL_Decode()From_Ba...

❗This is indeed the flag, but the text is encrypted with Base64. Usually, the presence of padding character "=" indicates that's Base64 type of encoding (but that's only one of the hints). To decrypt it, we can use CyberChef. Copy-paste the text and we either:

It uses a combination of magic bytes (like the `file` command), entropy analysis and character frequency detection to determine whether an output is likely to be of interest to the user.

The file type mechanism is written here[0]. There's a list of all signatures we detect here[1].

[0] https://github.com/gchq/CyberChef/blob/master/src/core/lib/F...

I think this can be deciphered using CyberChef...