HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jal505

no profile record

comments

jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
Hey, congrats on the momentum! Side projects that find their own legs are the best kind.

Just curious - if you're looking into any kind of automation down the line (LinkedIn outreach, etc), I'd recommend staying away from cloud-based tools.

LinkedIn's getting really good at detecting datacenter IPs and non-human browser fingerprints. I built ZenMode after seeing too many people get banned by cloud tools - it runs locally on your desktop using Electron/Puppeteer with your actual Chrome profile and home IP, so LinkedIn just sees normal browsing behavior. We're seeing 32% acceptance rates because it looks completely human.
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
I think you're right - the Tauri vs Electron comparison isn't quite the same scale of difference.

Both still run web tech in a wrapper, just with different performance characteristics. The local-first vs cloud distinction is more fundamental, especially for tools that interact with platforms like LinkedIn.

When I built ZenMode, the core insight was that LinkedIn can easily detect automation coming from AWS/datacenter IPs, but when your desktop app uses your actual Chrome browser and home IP, it's indistinguishable from manual usage.

That's why we went with an Electron/Puppeteer architecture running locally rather than yet another cloud service. Check it out at https//zen-mode.io if you're curious about the local execution model.
jal505
·há 4 meses·discuss
[dead]
jal505
·há 4 meses·discuss
[dead]