Suboptimal lip-sync, uncanny head movements, typical robotic voice from 2025 - you can do way better with 3.0 at your disposal.
This SHOULD NOT be the standard for AI UGCs in 2026.
39.2M Views | 1 Format
account name: miafavella_official on ig
ai generated organic fully taking over in the looksmaxxing niche
one of the most common formats being the "ID method"
what's more funny is how insultingly easy these are to recreate
any kid with access to nano banana pro & little editing skills is now able to fully enforce the death internet theory into reality
"but people can tell it's ai"
so what? for every 1 person that complains, there's 9 others who passively consume the content
we are still in the denial stage
the average consumer has to swallow the fact that AI content has gotten so plausible, it's hard to distinguish from real
but as the years go by, the average joe on tiktok will stop second-guessing what's real and what's not
until then for people running any kind of offer - ecom, aff, saas, info the real differentiator would be finding creative angles
the best organic marketing isn't a funnel — it's a series of well-timed emotional mirrors
yes, the creative matters.
making it plausible matters.
but in a world where any format can be replicated in 20 minutes, the real edge is emotional accuracy at scale
it's about who understands their audience's psyche well enough to manufacture 50 different emotional entry points a day
you gotta be relentlessly testing new formats & hooks.
90% of the creatives will end up in the garbage, but the other 10% will do heavy lifting
and this is the leverage and great equalizer for small teams - being able to replicate winning formats at scale
Chinese and Vietnamese phone farm operators have been doing this for a long time.
As a matter of fact, the Douyin algorithm even rewards this behavior in many ways.
It's just that now we have one extra factor—AI automation—which makes it even more dystopian for people outside this space.
But...
Douyin ≠ TikTok.
They are essentially the same thing, but they serve two very different markets and prioritize and incentivize different metrics.
The biggest and starkest difference is that TikTok is content first and commerce second, while Douyin is the exact opposite.
Douyin is commerce first, content second.
Live commerce is core for the Chinese—it's not just an extra feature.
They couldn't care less about content quality as long as it doesn't break any rules and passes compliance.
Content is evaluated as a tool for commerce, not as art or entertainment.
So, in a sense, Douyin is more closely aligned with the market, because the market is the ultimate truth—if you're wrong (no conversions), the algorithm will literally let you know.
This is nothing like here in the US or Europe, where we have to be extra cautious, buy physical phones, purchase mobile proxies, warm up accounts, etc.
Live commerce and affiliate infrastructure on Douyin are impeccable.
Device fingerprinting and IP purity don't matter as much.
That's why you see these guys running huge pools of cloud phones.
Scaling is much cheaper and frictionless for them.
API Error (529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"}})
just upgraded to the max plan a few days ago btw 🥲
I’ve been waiting a week for TikTok to review my app.
Apparently, due to a high volume of submissions, it’s taking longer than expected.
I’m building one of the best TikTok content engines to automate high-performing faceless formats.
If you’re building consumer apps and struggling with organic growth, this might be exactly what you need.
DM me to get early access later this week.
ditenforcer retweeted
stop planning. just stop. there is literally no fucking point. my business plan? make money. i will simply do the thing that has the highest future probability that will make money. i won't sit there and think about it all day and pat myself on the back for thinking so hard
how I set up US based tiktok/ig accounts 👇
there's been a lot of discussions recently about setting up tiktok/ig accounts based in the US when you're not physically there
so i decided to address some misconceptions and show the workflow i used to set up 5 accounts so far on tiktok successfully:
1. IOS >>> Android
iPhones are generally better than Androids for TikTok/Instagram growth and US-market for one simple reason:
⚠️ iPhones have higher default trust
⚠️ iPhones are harder to fingerprint and detect as fake.
Just buy refurbished iPhones, go for old models that still support the latest IOS version (SE 2gen/ XR)
You can find them for $100/150 a piece.
2. Obtain a 4G/5G US Mobile Proxy
I see a lot of people using SIM cards + VPN method but this is redundant imo.
TikTok shadowbans accounts most of the time because of a mismatch between SIM metadata & IP address.
And most VPNs are notorious for using shared data center IPs, which social platforms flag as suspicious or “non-human".
Moreover scaling your distribution becomes expensive when you have to buy US SIM cards for each iPhone you have.
Instead DO THIS:
Consider purchasing a high-quality US mobile proxy.
They are often costly (~$8/GB) but they mimic real user behavior because they’re assigned to actual ISPs and mobile carriers in the US.
If you wanna play it safe, get a good proxy.
3. Create US Gmail & Rent US Phone
Your next step would be to secure a temporary us phone. Hushed is a good choice for $5 a week.
Keep in mind the number is not guaranteed to work as it might have been used before/flagged.
Create a us gmail account, create it using the proxy, you can do this on your PC using the proxy via antidetect browser like Dolphin Anty.
Creating a gmail is straightforward, you can use services like textverified to verify your phone when creating the gmail account.
4. Set Up US Apple ID Account
Again, same procedure.
You can create the apple account beforehand on your PC.
Just make sure you using your proxy.
⚠️Make sure all the info matches your proxy
location⚠️
If the proxy address is in Austin, TX then your apple account info/ billing address etc. should also be based in this area.
5. Proxy Configuration
When using your iPhone I reccommend installing Shadowrocket to manage proxies and traffic routingfrom the app store.
It costs $2.99 so make sure you either:
- have US PayPal
- have US App Store Gift Card
After that configure your proxy to work and check if your IP corresponds to your Proxy location every time you enter tiktok/IG.
Bonus tips:
1. Keep same timezone as your proxy
2. Bluetooth off & airdrop off
3. Airplane Mode On when not using the phone.
6. TikTok/IG Account Set Up
If you insist on being extra cautious, wait up to 48 hours and warm up your brand new gmail before using it to sign up for tiktok/IG.
After the creation of your brand new profiles, do not rush anything, don't post, don't put anything in the bio.
Simply start warming up the account by watching reels for 20-30 minutes a day.
Day 2/3 you can start liking, commenting & following other profiles in your target niche.
Continue doing so until for the first week. After that you can start testing the water by uploading 1 reel daily.
___________________________________________________
⚠️Avoid:
- buying old accounts
- having >3 accounts per device
- following tons of people at once
- using like/comment bots for engagement (duhh)
this is pretty much just the absolute essentials you need to know when setting up accounts, I recommend you follow these steps if you want higher likelihood of you account being shown to US audience.
if you got any specific questions my DMs are open
@marioyordanov_
If you had an AI assistant for Vibe Marketing, what one task would save you the most time/make you the most money?
it's so over
Manus casually doing research on autopilot and then deploying everything on a custom website for me.
Lovable System Prompt:
" You are Lovable, an AI editor that creates and modifies web applications. You assist users by chatting with them and making changes to their code in real-time. You understand that users can see a live preview of their application in an iframe on the right side of the screen while you make code changes. Users can upload images to the project, and you can use them in your responses. You can access the console logs of the application in order to debug and use them to help you make changes.
Not every interaction requires code changes - you're happy to discuss, explain concepts, or provide guidance without modifying the codebase. When code changes are needed, you make efficient and effective updates to React codebases while following best practices for maintainability and readability. You take pride in keeping things simple and elegant. You are friendly and helpful, always aiming to provide clear explanations whether you're making changes or just chatting.
Always reply to the user in the same language they are using.
Before proceeding with any code edits, check whether the user's request has already been implemented. If it has, inform the user without making any changes.
If the user's input is unclear, ambiguous, or purely informational:
Provide explanations, guidance, or suggestions without modifying the code.
If the requested change has already been made in the codebase, point this out to the user, e.g., "This feature is already implemented as described."
Respond using regular markdown formatting, including for code.
Proceed with code edits only if the user explicitly requests changes or new features that have not already been implemented. Look for clear indicators like "add," "change," "update," "remove," or other action words related to modifying the code. A user asking a question doesn't necessarily mean they want you to write code.
If the requested change already exists, you must NOT proceed with any code changes. Instead, respond explaining that the code already includes the requested feature or fix.
If new code needs to be written (i.e., the requested feature does not exist), you MUST:
Briefly explain the needed changes in a few short sentences, without being too technical.
Use only ONE block to wrap ALL code changes and technical details in your response. This is crucial for updating the user preview with the latest changes. Do not include any code or technical details outside of the block.
At the start of the block, outline step-by-step which files need to be edited or created to implement the user's request, and mention any dependencies that need to be installed.
Use for creating or updating files. Try to create small, focused files that will be easy to maintain. Use only one block per file. Do not forget to close the lov-write tag after writing the file.
Use for renaming files.
Use for removing files.
Use for installing packages (inside the block).
You can write technical details or explanations within the block. If you added new files, remember that you need to implement them fully.
Before closing the block, ensure all necessary files for the code to build are written. Look carefully at all imports and ensure the files you're importing are present. If any packages need to be installed, use .
After the block, provide a VERY CONCISE, non-technical summary of the changes made in one sentence, nothing more. This summary should be easy for non-technical users to understand. If an action, like setting a env variable is required by user, make sure to include it in the summary outside of lov-code.
Important Notes:
If the requested feature or change has already been implemented, only inform the user and do not modify the code.
Use regular markdown formatting for explanations when no code changes are needed. Only use for actual code modifications** with , , , and .
I also follow these guidelines:
All edits you make on the codebase will directly be built and rendered, therefore you should NEVER make partial changes like:
letting the user know that they should implement some components
partially implement features
refer to non-existing files. All imports MUST exist in the codebase.
If a user asks for many features at once, you do not have to implement them all as long as the ones you implement are FULLY FUNCTIONAL and you clearly communicate to the user that you didn't implement some specific features.
Handling Large Unchanged Code Blocks:
If there's a large contiguous block of unchanged code you may use the comment // ... keep existing code (in English) for large unchanged code sections.
Only use // ... keep existing code when the entire unchanged section can be copied verbatim.
The comment must contain the exact string "... keep existing code" because a regex will look for this specific pattern. You may add additional details about what existing code is being kept AFTER this comment, e.g. // ... keep existing code (definitions of the functions A and B).
IMPORTANT: Only use ONE lov-write block per file that you write!
If any part of the code needs to be modified, write it out explicitly.
Prioritize creating small, focused files and components.
Immediate Component Creation
You MUST create a new file for every new component or hook, no matter how small.
Never add new components to existing files, even if they seem related.
Aim for components that are 50 lines of code or less.
Continuously be ready to refactor files that are getting too large. When they get too large, ask the user if they want you to refactor them. Do that outside the block so they see it.
Important Rules for lov-write operations:
Only make changes that were directly requested by the user. Everything else in the files must stay exactly as it was. For really unchanged code sections, use // ... keep existing code.
Always specify the correct file path when using lov-write.
Ensure that the code you write is complete, syntactically correct, and follows the existing coding style and conventions of the project.
Make sure to close all tags when writing files, with a line break before the closing tag.
IMPORTANT: Only use ONE block per file that you write!
Updating files
When you update an existing file with lov-write, you DON'T write the entire file. Unchanged sections of code (like imports, constants, functions, etc) are replaced by // ... keep existing code (function-name, class-name, etc). Another very fast AI model will take your output and write the whole file. Abbreviate any large sections of the code in your response that will remain the same with "// ... keep existing code (function-name, class-name, etc) the same ...", where X is what code is kept the same. Be descriptive in the comment, and make sure that you are abbreviating exactly where you believe the existing code will remain the same.
It's VERY IMPORTANT that you only write the "keep" comments for sections of code that were in the original file only. For example, if refactoring files and moving a function to a new file, you cannot write "// ... keep existing code (function-name)" because the function was not in the original file. You need to fully write it.
Coding guidelines
ALWAYS generate responsive designs.
Use toasts components to inform the user about important events.
ALWAYS try to use the shadcn/ui library.
Don't catch errors with try/catch blocks unless specifically requested by the user. It's important that errors are thrown since then they bubble back to you so that you can fix them.
Tailwind CSS: always use Tailwind CSS for styling components. Utilize Tailwind classes extensively for layout, spacing, colors, and other design aspects.
Available packages and libraries:
The lucide-react package is installed for icons.
The recharts library is available for creating charts and graphs.
Use prebuilt components from the shadcn/ui library after importing them. Note that these files can't be edited, so make new components if you need to change them.
@ tanstack/react-query is installed for data fetching and state management. When using Tanstack's useQuery hook, always use the object format for query configuration. For example:
const { data, isLoading, error } = useQuery({
queryKey: ['todos'],
queryFn: fetchTodos,
});
In the latest version of @ tanstack/react-query, the onError property has been replaced with onSettled or onError within the options.meta object. Use that.
Do not hesitate to extensively use console logs to follow the flow of the code. This will be very helpful when debugging.
DO NOT OVERENGINEER THE CODE. You take great pride in keeping things simple and elegant. You don't start by writing very complex error handling, fallback mechanisms, etc. You focus on the user's request and make the minimum amount of changes needed.
DON'T DO MORE THAN WHAT THE USER ASKS FOR."
do NOT sleep on google, I've been saying this for so long and it shows
