Loading video...

Video Failed to Load

Go Home

After some Saturday night debugging, I finally got Google Sheets running in Ladybird 🤓🧮 It's glitchy and unstable, but this is solid progress! Been told many times over the years that "you'll never get complex stuff like Google Docs running" lmao 😄

56,504 views • 1 year ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

OK, I have a definitive word on the CJ Abrams play from today's Pittsburgh Pirates at Washington Nationals game after talking with Elias Sports Bureau on this. This play will stay as a sacrifice fly. The originial ruling of NOT a sacrifice fly was for the exact same reason that I thought, which is that the infielder is not running into the outfield, which is year's past would have been correct As it was explained to me, in past years, an infielder had to be running almost in a straight line towards the outfield wall to be considered "running in the outfield". Here, since he is running, and he ends up further away from home (157 feet) than when he started (145 feet), this is going to count as a sacrifice fly. That definition is changing, in part from this play to help bring greater consistency, and to take some of the guesswork out of it (the argument that he is running into the outfield as opposed to more parallel). Now, folks all the time ask "why doesn't MLB publish the OS Manual" and I always say because it is a living document that can have the wording change, and the wording for this play will be modified to something like "more towards the outfield wall than towards home plate" to eliminate any confusion. The big key to this play is that he was running on a full sprint. Also, and this is helpful for me, but for all fly ball outs that score a run, Elias Saba reviews to ensure consistency. So, yes, it's a sacrifice fly, and now that I have that info from Elias themselves, that sort of settles this one. Sounds like the guidelines for this definition will be changing, either this season, or certainly for next season.

MLB Scoring Changes

49,141 views • 3 months ago

✨ Okay with lots of help from Javi Lopez ⛩️ and his Spanish scraping friends I've managed to vibe code my own ScrapingBee alternative and replace my $249/mo Scrapingbee plan with my own $1/mo scraper running on my VPS! First I tried OpenSERP, an open source project that seems freshly maintained but it didn't work on my VPS IP or laptop IP and got blocked fast Then I tried to use residential IP proxies from IPRoyal but they were already quite tainted IPs meaning Google already knew they were scrapers and just blocked about 60% of them already, not so great, also didn't work! Then I discovered OpenSERP uses a vanilla headless Chrome, Google instantly detects that and blocks that, so literally the entire repo is useless cause it won't even work? I don't get why they don't say that in the docs? OpenSERP is even worse than just basic CURL, as my AI said: "plain curl got 7% blocked but OpenSERP's headless browser got 100% blocked" So then I just built my own with Playwright and a real Google Chrome on my VPS, headful and persistent context, and slow pacing like every 30 seconds or so And I got some better residential IP recommendations (which I can't tell you because thenhey t stop working!) Now I'm at about 90% success rate, which is similar or better than Scrapingbee And it costs me ~$1/mo (measured by GBs, obviously for text scraping I barely use a lot) instead of the $249/mo I paid Scrapingbee! My only remaining SaaS now are: - Cloudflare Domains - Cloudflare Email Sending - Cloudflare R2 Storage - Backblaze B2 for backups - Hetzner for all my servers for all my sites (VPS) - xAI for all LLMs for all my sites (so many things like moderation, writing emails, anything)

@levelsio

759,478 views • 29 days ago