i'm autistic asf (diagnosed) about growth so i built an AI to find people just like me it uses @treg_ai + @p0 read 1.52M posts and ignored everyone with a ring light and a course out of all of it it handed me one random fella i'd never heard of @letsgodavis here's how it works

i am based, and i am in asia + thousands of oss downloads for our agency lets work listeningkit.com

there is a massive opportunity in the dictation space for a piece of software that can dictate Irish accents with 100% accuracy

update on the rubbish removal side quest days 3 and 4 with @AdsPowerBrowser the whole point of this is getting people in these cities to message about rubbish removal so the jobs can be passed on and sold as leads. bethlehem's first listing has now been live for a day. it got 23 clicks and not one message 23 people opened it so the ad is getting in front of the right people in the right city. nobody messaging is down to the ad itself, the photos are plain and the copy is weak. so the next job is the creatives. better photos and copy, different offers, different kinds of ad, testing them until one gets people messaging. we've already made a start on it. every ad now has at least 3 versions of its copy, written from the rules we pulled out of the best performing marketplace and classified ads, and each listing in a city gets the version least like what's already up there, with its own changed photos the maths so far. an aged account is 29 cents from our account vendor. bethlehem's whole day and a half of us hammering it with test runs, the publish, two full warm ups, a reels session and every check, used 957mb of @byteful residential proxy. byteful is $3.25 a gb on its 10gb pack so that's about $3.11. so $3.40 to get one account to a live listing, then its adspower profile on top, we pay $12.99 a month for 22 profiles so about 59 cents a month each scale it to 100 accounts and it's $29 for the accounts and about 96gb of proxy, which is byteful's 100gb pack at $275. so $304 to get 100 accounts to a live listing, and that's at our test usage, a normal account won't browse anywhere near that much. adspower's own price list has 150 profiles at $25.74 a month paid yearly, so that covers all 100 with room to spare. if those 100 listings did what bethlehem's did that's about 2,300 people opening a rubbish removal ad in their first 18 hours, around 13 cents for each person who opened one. but clicks don't pay, messages do, and right now that's zero that's why the creatives matter so much. a rubbish removal job runs anywhere from $500 on the small end to $2,000 for a big clear out, and a qualified lead for one banks about $150. getting 100 accounts live plus a month of adspower is about $330, so 3 qualified leads pays for the whole lot. out of 2,300 people opening the ads that's 1 in every 770 or so turning into a real job enquiry. one account costs about $4 for its first month so a single lead covers 37 of them. the setup isn't the hard part anymore, getting the ad good enough that people message is getting to that first listing is where most of the work went adspower is the backbone of all of it now. every account has its own profile and its own device and keeps one browser open for its day, and log cli drives every step inside it. the profile never holds the proxy, it only goes on when the browser opens. log cli checks the ip is in the account's country, then checks again from inside the adspower browser that the ip, the timezone and the language all match before facebook ever loads. that paid off today, the residential ip rotated between those two checks twice and the browser got shut before a single facebook page loaded with that in place the groups came first. log cli read bethlehem's local group straight out of the feed query facebook's own page uses, 13 posts and every comment under them, then every single thing you can do on a group page got recorded live and turned into a flow that runs again on any account. posting, photo posts, commenting and deleting all done for real then the listing. it took a few goes because typing "bethlehem, pa" put it in the west bank and a bare zip code offered granada, spain first lol. the way we found out how is the bit that changed everything. every step adspower takes gets recorded raw, every request and every response, and @morluto's rea reads each step's recording the moment it lands. reading the west bank step back, facebook's own answers had the west bank in them seconds before we clicked it, and the search itself had gone out with coordinates in lima because the account was already set to peru then we looked back at the day 2 warm up. it had opened the create listing page twice and both times facebook's answer said the account was in barranco, peru. it passed anyway, because all it checked was that the page loaded. we'd been deciding everything off the screen and that's the thing about facebook's client. every tiny thing you do in it fires an internal api call. swipe past a reel and it tells facebook that reel was seen by that account. open a listing and it sends how long you looked at it. scroll and it asks for more. adspower makes the device look like one person, but what the account does inside the client is the other half of who it looks like, and the warm up had been building that the whole time without ever reading a word of what came back so we turned it around. log cli now pulls every internal call out of rea's recording of each step, what we sent and what facebook answered in seconds from our action, and those answers get kept even when the run gets deleted. we cleared 6gb of old runs and kept every answer in 22mb then the inspect flow and @subquadratic got tied into it as one system. as the agent goes step by step, each step builds up the screenshot, the page, the mouse and every internal call, and when it lands somewhere we don't know all of it goes to subq in one go with the goal and the account. subq says whether that step got us closer to the goal or not and why. read back on the west bank step it said wrong result at 93% and pointed straight at lima and the west bank. then it writes up what went wrong in one line, quotes the exact calls that prove it with what was sent and what came back, and explains why it happened. a @claudeai code hook won't let the agent stop until the goal is reached and every problem has its fix written next to it, and the state gets a name so next time it's already known ran it live on bethlehem and it found two things straight away. after that first listing facebook's answer on the create page went from saying the account can post to saying it can't, so it's one listing per account for now. and marketplace was showing it catawiki listings from italy at €95, to an account in pennsylvania. we also had it like 2 posts and it judged the goal across the whole session, the first like didn't count as done, the second did after that every warm up step got moved onto facebook's answers. the create page has to come back with the account's own city and country, a like only counts when facebook says it saved the like we sent, a swipe only counts when facebook marks that reel seen for that account. today i ran the full warm up live in adspower after my computer crashed halfway through lol. feed, marketplace, selling and messages all passed on what facebook actually answered, the create page came back as can't post so it got noted and the warm up carried on, then 8 reels went through with every step passing watching it caught two last things. the gap between warm up activities was 2 minutes and it should be 10 seconds, fixed. and coming back from a creator's profile reloaded the reel muted, so every reel after it was watched with no sound, now the sound goes back on every time a reel loads so the machine works. it gets an account to a live listing for $3.40 and local people open the ad. next up is the creatives, trialling photos, copy, offers and different kinds of ad until people actually message, and then doing the maths again with leads in it

doing things maxxing

i got this here email in the early hours of the morning alongside about 8 other massive providers and it just goes to show you the issues that are going to become more common coming into the next few months. is it worrying, yes. can you do much about it? not really. I've been a heavy railway user since early 2024, I personally don't think this is an issue to stop using the platform entirely but it does mean that you should take more caution being locked into one provider entirely. i've got half a dozen providers I'd recommend that you should have so you can alternate between for example. i would never use railway for anything todo with production. (it's not economically the best for production anyways) but i would use it for staging, this is just another blip. php is the backbone of the net there will probably be a major zero day within the next 6 months over the past few months I've been seeing large scale attacks on Inference Providers.

pdate on the rubbish removal side quest day 2 with @AdsPowerBrowser log cli now drives adspower and camoufox through one @playwrightweb layer so both go through the exact same proxy gate, the same self check, the same recorded human mouse and the same raw recording of every request. first live adspower run was a group search on bethlehem and it just worked then groups. the accounts can now find a local group, read its join questions, answer them and fill the dialog. bethlehem is in 3 groups with 3 more pending then the warm up. every account gets a persona built from real datasets plus one real viewer out of 980 from kuairand (11.7m rows). @subquadratic looks at every reel the moment it lands, about 1.6s each, and decides if it's this person's kind of thing. 48 reels in one session, 32 judged theirs, one like that's also how i found out each reel burns about 4.5mb of residential proxy so we ran @2captcha's traffic dry lol. every account now has its own 1gb a day traffic budget and i added @byteful beside it, a sticky 24h ip in the account's own city then the home feed, post by post. a glance at most posts, a proper read of the ones it likes. one run went 33 steps with none failing, a 26 second read on a long post and a like how we actually see what facebook does: every step the browser takes records a raw har, every request and every response, nothing stripped. @morluto's rea reads each step's har the moment it lands so every click comes back with an evidence id, what facebook sent, what it answered and how long it took then log cli parses facebook's own javascript bundles into a syntax tree, 31,873 modules so far, cuts out just the code behind each graphql request and rea reads each slice in about 4 seconds. reading a whole bundle in one go kept getting killed so slices it is out of that comes a doc for every request facebook makes in our runs, 145 so far: what it sends, what it reads, which of our steps fired it and how fast. a push gets refused if any run is newer than the docs so when reading got checkpointed opening marketplace after about 40 minutes we didn't guess. rea's read of the recording showed facebook pushed the checkpoint to the browser with no click from us. log cli pressed through the first page and solved the text captcha by itself and stopped at the video selfie because that one needs a human so now any page log cli knows how to get past gets handled straight away. hooks in @claudeai code tell the agent which page every browser is on after each step and won't let it stop while there's something it can clear itself also turned the readme into something generated from the code with @mermaidjs_ diagrams, every command, every flag, which browser and which platform each one runs on, and a commit gets refused if they ever drift then brought my openmagpie box back from the dead. it had been down since a reboot in august, so it's back up, pointed straight at @agnesai_sapiens agnes 3.0 flash and the old x keyword listening is switched off last thing today: recorded a live read of a bethlehem recommendations group with rea reading every step. the whole group feed is one graphql query, 3 posts a page, every post with its id, author, text and time. and the recording caught our own recorder dropping the 2.3mb group page with the first posts in it, so that's fixed too next up is turning that into a triage job. the account sits in the group, openmagpie reads every post and picks out the ones worth replying to, they land in @twentycrm, and log cli replies from the same account in the same browser. log cli is also replacing the old log repo, no convex, everything on twenty

i have a competiton that is due here in 11 days gonna build on top of this here but make it so that you’re able to get your website a backlink too! Sick job Jason and team

very cool to see this i will make my own showreel with this amount of creativity aswell now smh very talented young women !

asked @claudeai opus 5.5 to research @AniC_dev's @boatdotdev for my rubbish removal side quest and with no internet it said "verify what this is, if no such product exists say so" then in the same breath listed every single one of its competitors from memory @e2b @daytonaio @modal @flydotio @vercel sandbox @Cloudflare @browserbase @steeldotdev @hyperbrowser @AnchorBrowser that's how new boat is. the smartest model on the planet knows the whole market except the guy who just shipped full VMs for agents at $20 a month billed by the second the plan is to plaster facebook marketplace with rubbish removal adverts across 4 cities while i'm sitting in vietnam so every account has to look like a normal person in its own city so i turned the hackathon stuff into one cli called log-cli that gives each account a @2captcha residential proxy in its own city and opens camoufox for it first galway test looked perfect but the browser clock still said asia/bangkok lol so i treated the whole stack as broken, had @p0 parallel run deep research, did 5 live launches against every leak test i could find and found 22 leaks fixed the lot except one. camoufox changes the name of the graphics card but not how it draws so every account on one pc draws the exact same image underneath so now i'm running matrixes over boat vs all of those competitors, 10 options vs 16 criteria with all 22 leak files and the deep research loaded into @subquadratic in one go (384K context window) to see if a VM per account is the cheapest fix for our use case i already know i'll be using boat by tonight but lets see what the matrix says