Independent software engineer. Web apps, API integrations & AI workflows. Have a manual process or tools that don’t sync? Let’s discuss a small first scope.
My contributions to chrome-use just shipped: nested iframe attachment, transformed-frame screenshots and locale checks.
The biggest lesson: verify the effect a browser command claims.
Included in v1.5.267:
https://t.co/lWt0x8oYyK
@danjohnson Six weeks is a respectable lifetime for a tooling decision these days 😂 What would you keep from your own MCP if you moved the storage to Notion?
@ajaystefin I'd want to know which request got slow first. A trace showing time waiting for a database connection would lead me somewhere very different from one spending the time in application code. Hard to choose the next box before seeing that.
@Shreya2049 A replay screen showing the original delivery beside the retry would be useful here. Same payload, separate response and timestamp, so you can see exactly what changed after fixing the receiver.
@lonniev The fence-post reading is a lovely concrete use for this. I'd want its measurement time visible next to the value, especially if the station goes offline. Yesterday's rain reading could look perfectly plausible today.
@srikeerthandev I can help build this. For the six projects you mentioned, let's get one complete project page right before copying the layout. For demos, a screenshot and an ordinary link would keep the portfolio from loading an embedded app behind the visitor's back.
@jesusporras If any of these need custom PHP or integrations, I'd be interested in that part. My public code work is here: https://t.co/MYEMLET6KJ. Recently had a conformance-test fix merged into the official MCP PHP SDK.
@MillyCrypto_@abstamalOrvit I can help with the recruitment flow and subscriptions. What does premium unlock for the member: access to listings, applications, or contact details? That would tell us what the payment integration actually needs to control.
@fastestmk On a store, that rollback rehearsal needs to include new orders. Restoring yesterday's database could wipe out today's sales too. I'd want the changed plugin rolled back while the new orders stay put.
@Ravi_Nileshbhai@TenwriteApp@LaunchXact A 'failed to publish' list with a retry button would earn its space for me. Search Console graphs can wait. Getting the week's documents published without hunting through individual posts is already a useful product.
@erickwellem A driver cancels, a customer changes the destination... those are the calls I'd want to sit in on before designing the app. The person handling them probably knows half the missing requirements already.
@stretchcloud What happens when a selector still matches, but now points at the wrong price or product? That's the self-healing case I'd be curious to see demonstrated. An empty result is much easier to notice.
@syshen I recently contributed a fix to ai-memory around clearing old session bindings. It made me appreciate how much the boring identity bookkeeping matters. With shared notes, I'd want to see which workspace a memory came from alongside the note itself.
@ahmedimtiaz_g The audience-vote cutoff sounds like the tense bit here 😅 Did you freeze the totals before showing the judges' results, or keep both running live?
@prateekbhujel@alexandr_wang@AIatMeta@Meta One detail I helped document in Banneret: verification evidence needs the commit SHA it was collected against. Otherwise a later edit can inherit an earlier green result. Curious how ProofPatcher handles that between review rounds.
@0xlelouch_ I'd keep the original events and version the projection. A status rank alone needs a correction path: what happens when the carrier retracts a mistaken Delivered scan? I'd make that an explicit replay test before trusting the customer-facing state.
@_salomon_a@WhatsApp I haven't solved this exact crash, but I can help narrow it down. Does WhatsApp Web in a browser crash the phone too, or only the Desktop app? And is the phone on iOS or Android?
@CodyWatson04 Which sandbox? Stripe Checkout redirects immediately when you're testing with the CLI, so the webhook can lag behind the success page. That detail is easy to mistake for a bug in your own order handling.
@chess_robot The first setup can be a slog. I'd judge it by the next one: can you bring the site back with its data intact, without repeating those imports? If not, the setup still needs simplifying before Docker is earning its keep.