Lionel Péramo’s Post

Did you know you can actually save code snippets in the browser without creating custom browser extensions and things? Here's a set of custom scripts to scrape content like links and images off of any webpage - stored in my Sources >> Snippets tab of your browser dev tools. You can upload whatever custom scripts you like - yes scrapers, but also content analysis and more complex operations. Thing of it as bookmarklets on steroids. I have pasted the code Gist here in the comments if you want to make yourself a copy.

It's time to remove IE and Edge from feature support tables. One has been dead for almost 4 years (that's 28 in Internet years), the other one is three Chromes wearing a trench coat. As an alternative, add the canary/nightly versions of Chrome, Firefox, and Safari in their place. That way it will be easier to check if a feature is in the pipeline and will be available soon. And before someone says, "But support tables include version numbers so you don't really need to include the nightly/canary in the table!" I double dare any developer not closely involved or interested in browser development to tell me which is the current version of Safari and Safari TP without searching for it. And that's the thing. The goal of support tables is to provide quick and valid information. Sometimes, reducing data (deprecated and duplicated browsers, in this case) improves the quality of the data.

Differences between slug, route and URL A URL is the complete, unique address of a web resource, like https://lnkd.in/gGPBN65S. A slug is the human-readable, descriptive part of the URL that identifies a specific page, such as "how-to-make-a-website". A route is the system or pattern that a web application uses to match an incoming URL to a specific piece of code or functionality, acting as the set of rules for directing a request to the correct handler.  

📁Throughout the File Inclusion module I learned how web apps become vulnerable when they include files dynamically without validating input. I learned the difference between Local File Inclusion (LFI), which lets you read or execute local files on the target, and Remote File Inclusion (RFI), which can let you pull in and run files hosted elsewhere and lead to remote code execution. 🌐I studied how PHP functions like include(), require(), and file_get_contents() behave depending on whether they accept local or remote paths, and how wrappers such as php://, data://, and expect:// can be abused to execute commands or bypass filters. 🌠I've also learned the practical path from simple file disclosure to full code execution, for example by finding credentials or SSH keys in config files or by uploading a web shell. The module made it clear that using user-controlled input in file inclusion is extremely dangerous and that mastering these techniques reveals realistic web exploitation chains.

Most agents are useless without web access. We tested top 6 MCPs for browsing. Learn their weaknesses to save yourself hours of debugging. With every web automation agent that we built, we spent hours trying to figure out why the agent doesn’t work. Most of the time, it was because the agent was getting blocked by websites. Then, we tried different providers and managed to get results. When the agent worked well during testing, we pushed it to production and everything broke down again. Performance under load ≠ test performance. We tested all these MCPs both with single and 250 concurrent requests. In all cases, there is some performance degradation at scale but in some providers, performance degradation was quite significant. You can find the full benchmark by searching for “browser MCP aimultiple”. 👉 Learn from our mistakes, build faster.

🌐 Ever wondered how your browser talks to websites? 🌐 When you click a link, fill out a form, or upload a photo — your device is actually sending tiny “requests” to a server using something called HTTP methods. Each method tells the server what to do 👇 💙 GET – “Show me the data.” 💜 POST – “Here’s new data to save.” 💚 PUT – “Replace this data with an updated version.” 🧡 PATCH – “Just update this part.” ❤️ DELETE – “Remove this item.” 💡 HEAD – “Just check if it’s there.” ⚙️ OPTIONS – “What can I do here?” 🔍 TRACE – “Repeat what I just sent (for testing).” 🔗 CONNECT – “Let’s make a secure tunnel between us.” These are the basic “verbs” of the internet — how all websites, apps, and systems talk to each other behind the scenes. Understanding them gives you a peek into how the web really works! #Technology #WebDevelopment #APIs #Learning #HTTP #InternetBasics #SoftwareMadeSimple

🧠 While building some production scrapers, I kept running into the same pain: certain sites would reject or challenge every request, no matter how well I spoofed headers or user-agents. After a few rounds of frustration (and way too many failed Axios requests), I realized the only stable way was curl-impersonate --- but using it cleanly inside Node.js wasn’t great. So I wrapped it. Introducing cuimp --- a minimal Node.js wrapper around curl-impersonate. It lets you send requests that actually behave like real browsers --- Chrome, Safari, Firefox --- and just work where others fail. I originally wrote it for my own automation stack, but figured it might help others too. If you build crawlers, data extractors, or automation tools, this might save you a few headaches. 👉 https://lnkd.in/ebpZXxdc 💡 Open to contributions and feedback: 👉 https://lnkd.in/ed6MWznB

Need to inspect web traffic/API requests? Too much noise from unrelated apps when debugging your API integration? Requests from every process slow you down and clutter your logs. With Dev Proxy, you can intercept requests from only the processes you care about. Filter by process name or PID to focus your workflow. Spend less time searching for the right requests. See only the traffic you want, so you can debug faster and avoid distractions. Here's how to do it: https://lnkd.in/eZ7r-t9H

Why is Lazy Loading absolutely crucial for mobile? When a user visits a page, the browser tries to download all resources as soon as possible. All the components are bundled and loaded immediately, even if the user never visits those sections. So, lazy loading is very critical. By using lazy loading, you can offload some pages that are not regularly visited, thereby reducing the initial loading time and increasing performance and ranking. https://lnkd.in/gjpYEX7s

HTTP/1 vs HTTP/2 vs HTTP/3 This article provides a detailed, clear-cut analysis of HTTP/1 vs HTTP/2 vs HTTP/3, focusing on how each version improves (or fails to improve) web performance, efficiency, and modern use cases. What is HTTP? HTTP stands for Hypertext Transfer Protocol. It’s the foundation of data communication on the World Wide Web. When you visit a website, your browser uses #HTTP to request content (like text, images, videos) from a server and display it for you. In simple terms: HTTP is how your browser and a website's server talk to ... Keep Reading 👉 https://lnkd.in/gs6ZdqYa #quiccloud