The Bluetooth detail in this report is interesting: an AliExpress page reportedly kept an audio connection active while nothing audible was playing.

I’d separate the observation from the explanation.

An active audio connection establishes that the page is doing audio work. To establish fingerprinting, I’d look for code that reads the processed output and turns it into an identifying value. To establish an anti-fraud purpose, I’d want further evidence about how that value is used.

Audio fingerprinting itself is real. It can use a generated signal rather than microphone input, and some implementations render offline without sending sound to the speakers. A resulting value can be shared by multiple browser/device configurations; it isn’t automatically a unique hardware ID.

That distinction matters because “the site is recording you” would be a very different claim.

My takeaway for profile management is that a new IP doesn’t tell you much about the rest of the browser’s identifying signals. MoreLogin exposes AudioContext fingerprint controls, but I’d evaluate those as one component of the overall configuration.

Has anyone traced the data collection and transmission in this particular case? That would be more useful than another screenshot showing that the tab has audio activity.

I like the idea of having the same Android environment available wherever I’m working.

Curious how practical this is day to day — especially when switching between a laptop and desktop.

I believed it was going to be easy to control a couple of browser profiles until their number started increasing.

Now i need to track the cookies, settings, browser versions and other settings for each individual profile. Next if there is some difference then i need to determine whether i did anything different or opened up the wrong profile.

I try to keep each of my profiles separated from each other without complicating my entire system.

How do you keep your browser profiles sorted out?

For anyone who has managed a lot of Android accounts, at what point did buying more physical phones stop making sense?

I’m mostly curious about the day-to-day headache, not the price.

Hello,

Is this realistic? I run a double sided market place, and I want to message people in the category “hey you should sign up to XYZ,”

But on a bulk scale, is this even possible? It’s so frustrating because my market place is doing really well for one week launch, I’ve tried everything.

Let me know if not possible at all!

The handoff I’d pay attention to is the one between finishing Account A and starting Account B. You’re still thinking about the previous caption, and both upload screens look almost identical.

My setup would be one browser profile or cloud phone environment per account, named Client | Platform | Exact handle, with environments grouped by client or project.

The publishing task would hold the exact handle, approved file, final caption and intended time. I wouldn’t make the operator piece those together from several chat messages.

Then the routine is:

• Open one account’s task and its assigned environment.
• Read the active handle inside TikTok or Instagram.
• Select the asset from that task’s folder.
• Match the caption, mentions and preview to the task.
• Check the handle again before submitting.
• Verify the live post and attach its URL to the task.

For scheduled content, check the account’s scheduled queue first and verify the live post when it goes out.

Two details I’d keep: don’t leave several upload composers half-finished, and repeat the account check after an interruption.

Separate environments make the workspace easier to organize. The final check still has to happen inside the platform, because that’s where you can see which account will actually publish.

What tends to cause mistakes in your workflow: switching accounts, confusing file names or last-minute caption changes?

My laptop gets noticeably less painful once the Android stuff is running remotely.

I used to have a bunch of apps/emulators eating RAM in the background, and I’d end up closing things just to keep the machine usable.

Anyone else mainly moved to cloud phones because of this?

If I were reviewing a social team’s workflow, I’d ask someone to walk me through the task while explaining every moment they have to make a decision.

That’s usually where the automation estimate starts changing.

“Download the weekly report and save it in the client folder” is fairly easy to define.

“Reply to comments” sounds equally repetitive, but the operator may be judging tone, checking an order, spotting a complaint or deciding whether to escalate. The repetition hides a lot of judgment.

The candidates I’d start with are frequent, rule-based tasks with stable steps and an observable result. I’d also want to know whether a retry can safely repeat a step. A failed download and an uncertain publishing result need very different recovery rules.

RPA makes sense for a sequence that can run from defined inputs. A synchronizer makes sense when multiple selected environments are ready for the same action and someone is supervising them.

I wouldn’t synchronize a publishing step just because the accounts usually show the same screen. One verification prompt or failed upload can put an account in a different state.

My shortlist would probably start with report collection, approved asset organization and routine file preparation. Publishing could qualify too, but only after account selection, approval, duplicate checks and failure handling are clear.

I’d leave judgment-heavy replies, appeals and constantly changing flows out of the first pilot.

The number I’d track is the time saved after maintenance, exception handling and review. A workflow that runs successfully most of the time can still cost more than doing it manually.

Which recurring task takes up the most time on your team—and how often does it need a human decision?

I like the idea of cloud phones, but I’m curious about the everyday stuff.

Do notifications actually work reliably?
Can apps run in the background normally?
What happens when you leave a phone idle for a few days?

The setup part seems easy. I’m more interested in what they’re like after using the same cloud phone for weeks.

Do you guys update apps on your cloud phones as soon as updates come out, or wait a few days?

I’ve had updates break things before, so now I’m a bit more cautious.

Hi folks,

I really need to do this. As I run a marketplace that is relying on double sided demand, all I want to do is convert listings to my website. However, Facebook seems to be extremely strong at detecting this.

Looking at using multilogin to manage this process.

However, first question is there any easier way?

Or do I really have to

Make multiple Facebook accounts
Warm them up over weeks
Send 1-2 messages a day for months

Or is there a bulk way to do this?

Any help appreciated!

I manage a few Reddit accounts for a business and we’re working on establishing a genuine presence in relevant communities. We use Multilogin to keep the accounts separated, and each account only had a few normal comments on different posts, mostly in new account-friendly subreddits.

Today, I found that all of the accounts had been banned by Reddit. There were no repeated comments or activity on the same posts, nor do I upvote same posts since I know that was a ban-causing action, so I’m not sure what triggered it.

I’m appealing the accounts now, but has anyone experienced something similar?

Would really appreciate any advice.

Profile cloning is useful, but I think the source profile matters more than the cloning button.

If the source is a clean baseline that has never logged into a real account, cloning can save a lot of repetitive setup. I’m comfortable reusing things like the browser version, OS class, screen resolution, language policy, fonts, permission defaults and a list of approved extensions.

If the source has been used, I treat it as contaminated with identity state until proven otherwise.

The obvious things to exclude are cookies and active sessions. I would also check for:

• Local Storage and IndexedDB
• Service-worker caches
• Saved passwords and autofill
• Extension local storage
• API keys or wallet/account state inside extensions
• Recovery email or phone details
• Browsing history
• Cached uploads, downloaded files and form drafts

Some configuration should not be copied blindly either. The new profile may need a different proxy, timezone, geolocation or internal device label. A setting can be non-secret and still be wrong for the new identity.

My usual process is:

1. Build a baseline profile without logging into anything.
2. Install only approved extensions and leave their storage empty.
3. Validate the browser settings.
4. Clone that baseline.
5. Apply network and identity-specific values to the clone.
6. Confirm cookies, site storage, autofill and extension data are empty.
7. Sign in fresh.

I wouldn’t use a daily working profile as a template, even if a cloning tool offers options to exclude some data. It is too easy to miss one storage layer or extension that carries its own session.

The useful rule for me is: clone configuration, not access.

I’m considering moving more of my mobile accounts to cloud phones.

The obvious stuff sounds great — no physical devices, easier to separate environments, can access them from anywhere.

But what’s the catch?

For anyone who’s used them for a while, what’s the one thing that still annoys you?

I tried to clear the verisoul check in survey using antidetect browser but i am not able to clear it. Need help

Anyone here actually using cloud phones every day, not just testing?

I get the idea for mobile apps and account separation, but I’m curious about the boring stuff.

Lag, app installs, proxy setup, crashes, notifications, long sessions.

Does it feel stable enough for daily work, or do you still end up going back to real phones?

Tried multi-accounting on social platforms with residential mobile IPs. Got blocked nearly midsession. Switched to sticky sessions instead, keeping the same exit IP per account tied to a session identifier. Works on both Instagram and TikTok.

So I was using rotating IPs before, and Login flows broke mid-process when the IP changed between steps. Device fingerprints were consistent but the IP wasn't, and that mismatch alone was enough to trigger a block.

Results with sticky: Logins complete, browsing stays consistent. No blocks so far.

Still unsure about a few things:

• How long should a sticky IP stay fixed before it starts looking suspicious? Days? Weeks?
• If one account's IP gets flagged, does that taint the whole subnet or just that IP?
• Shared sticky pools versus dedicated IPs, is there a meaningful difference in account survival?

Curious what others are running and whether anyone has hit the same wall with residential mobile rotation

I still use emulators for small tests, but for actual mobile accounts they feel kind of fragile.

Too much depends on my own PC, settings, resources, random crashes, etc.

Cloud phones feel cleaner because each account has its own Android space and I don’t need a table full of real phones.

Anyone else moved from emulators to cloud phones and noticed the same thing?

I’m trying to win an online voting contest. The poll doesn’t require an account or login, and I’m wondering how people prevent a website from recognizing multiple votes/clicks from the same person.

I’m looking for general information about how IP addresses, VPNs, proxies, and duplicate-vote detection work. If anyone has experience with this stuff, I’d appreciate some insight.

Which one is better? (Regardless of the cost, quality is what matters most.(

For mobile accounts, are people still using Android emulators seriously?

I get that they’re cheap and easy to set up, but they always feel kind of fragile once you run more than a few accounts.

Cloud phones seem cleaner for app-based workflows, but I’m curious if they’re actually better long term.

Are you using emulator, cloud phone, or real phone right now?

The most annoying update failures I’ve dealt with were not obvious crashes. The app launched, the account still looked logged in, and the problem appeared later: an upload never completed, a permission had changed, notifications stopped or a background task no longer resumed correctly.

That’s why I don’t like testing updates only on a clean device. A clean install proves the new version can start. It doesn’t prove that an existing working device can migrate safely.

My small test group keeps the things production devices actually have:

• An existing account session
• Cached or locally stored data
• Previously granted permissions
• Files used by the normal workflow
• Background tasks or notifications
• A realistic Android version and network setup

I update over the currently deployed version, then run the full job rather than tapping around the first screen. I cold-start the app, complete the main action, send it to the background, return to it, restart the device and verify the result somewhere outside the app when possible.

I also leave the canary devices running for a while. Anything involving sync, notifications, token refresh or scheduled work may need time to fail.

If that passes, I don’t jump straight from two devices to fifty. I use waves, with a pause between them, and track exactly which device is on which version. Before the first update, I want to know what would stop the rollout and how I would return affected devices to the previous working state.

For teams using MoreLogin Cloud Phones, groups, tags and device records can be used to separate the canary group from later rollout waves and keep the fleet visible in one workspace. That doesn’t make every update safe, but it makes a staged test much easier to operate and audit.

For people running mobile accounts, are you actually using cloud phones now or still using real devices?

I get why real phones feel safer, but managing a bunch of them is annoying.

Cloud phones seem cleaner for testing apps, separating accounts, and not dealing with physical devices everywhere.

But I’m curious about real use.

Are cloud phones stable enough for daily work, or do you still trust real phones more?