Aidan Raney’s Post

#OSINT Tip - Deepweb Search Tools I've been working on a list of deep web search tools that allow you to search non-indexed parts of the internet like paste sites, source code of sites, hosting services, file sharing services, online IDE's, FTP servers, unlisted Google Drive files, PDF sites, usenet, short URL services, etc. Today I am releasing the current version of that list for free: https://psbdmp.ws/ - psbdmp, The biggest archive of {paste} dumps https://lnkd.in/gEUAq9pW - search-pastebin, Google CSE powered tool, Search 33 Paste Sites at once https://lnkd.in/gcFGiE4H - RedHuntlabs online-ide-search, looks for keywords/strings in following Online IDEs, Paste(s) sites, and Code Sharing Platforms https://lnkd.in/g32ujPrN - NerdyData.com, Find websites by searching for specific technologies, HTML code, or Javascript code https://publicwww.com/ - Publicwww, search the source code of 480,057,956 web pages https://lnkd.in/gVBjCHfp - Grayhatwarfare, search index of public buckets from hosting services (AWS, DigitalOcean, etc) and URL shorteners https://lnkd.in/g3BbEbNs - CSE for search 20 source code hosting services - bitbucket.org, codeberg.org, fedoraproject.org, github.com, gitlab.com, sourceforge.net, tizen.org, etc https://grep.app/ - grep.app, Search across a half million git repos https://searchcode.com/ - searchcode, Search 75 billion lines of code from 40 million projects https://lnkd.in/gF4kjyHh - Open Directory Search Tool, Find files in open directories https://www.mmnt.ru/int/ - Mamont, Largest FTP Search Engine https://lnkd.in/gERfPm7R - fidigger, Look for public archives in different File Sharing services https://lnkd.in/gnVRhfVP - s3digger, Find public files in Amazon S3 https://lnkd.in/gMFAcveK - yadigger, Find public files in Disk Yandex https://lnkd.in/gy29QkFa - dedigger, Find public files in Google Drive https://lnkd.in/gQgBwb52 - shortdigger, Enables the search for documents that are made accessible through the use of URL shortening services https://lnkd.in/gwjf5u9i - NAPALM FTP Indexer, Searching 894,766,414 files (10317.90 TB) in 3,063 FTP servers https://sourcegraph.com/ - Sourcegraph, extremely good code search, good filters, specifically geared toward devs https://issuu.com/ - Issuu, search user submitted pdfs http://uvrx.com/ - UVRX, Search files from Badongo, 4Shared, Depositfiles, Zshare, Taringa, Mediafire, Usenet, Mega, and more https://www.pdfdrive.com - PDF Drive, Search over 75,474,759 eBooks https://lnkd.in/giBcCG-A - SlideShare, Search user-submitted slideshows https://www.pdfsearch.io/ - PDFSEARCH.IO, search index of 18,184,479 items, organized by smart labels I could not fit the full list here, please check the comments for the remainder of the tools. If you found this helpful, please share this with your network!

🚀 26 Next.js Features You Need to Master for Modern Web Development 🚀 Just published a full guide on my GitHub with 26 Next.js features, complete with explanations and code examples for each! From Server-Side Rendering (SSR) to Incremental Static Regeneration (ISR), API Routes, Middleware, Edge Functions and more, this has everything you need to get the most out of Next.js. Whether you’re scaling, SEO, or building server-rendered pages, Next.js has got you covered with built-in tools and zero config. Check it out for real examples and practical info! 👉 https://lnkd.in/dwgWQumX #Nextjs #WebDevelopment #React #Frontend #FullStackDevelopment #JavaScript #Programming

Piwik PRO for server-side Google Tag Manager! Yes, you read that right. Over the past month or so, I've had the distinct pleasure of working with the wonderful Piwik PRO team in creating TWO new templates for server-side Google Tag Manager: - Piwik PRO: A tag template for sending event data to Piwik PRO servers. - Piwik PRO Client: a client template for claiming incoming requests from the Piwik PRO JavaScript tracker. The tag template is in the Community Template Gallery and can be found in your container's Templates section. The client template needs to be downloaded from the official GitHub repo (https://lnkd.in/gqC2p-bR). The templates are designed to work so that you can optionally pipe other vendors' tools into the pipeline, too. For example, you can use the GA4 client to generate event data for the Piwik PRO tag. Or you can use an Amplitude tag to read the data generated by the Piwik PRO client. I've written an article on how the templates work, and you can find it here: https://lnkd.in/g8WAG6DE I will also release a walkthrough video of the process soon. If you have feature requests or bug reports to file, please use the Issues feature in the official GitHub repo for the templates. - Tag template: https://lnkd.in/gKgMt_rY - Client template: https://lnkd.in/gPbWa2iz Piwik PRO is a wonderful platform for data and analytics. I'm really happy it is now supported by server-side Google Tag Manager. #piwikpro #serverside

🚀 Here comes yet another Friday! And you probably already know that the #fingowebteam comes to you with a #QWERYlinks post! Today we have something for #WebDevelopers and those who use SQL databases. 👀 #JavaScript Tricks Discover the versatile and surprising capabilities of vanilla JavaScript through practical examples. Learn how to find operating system details, prevent page refreshing, redirect users to new pages, validate emails, get the current #URL, and detect mobile browsers. To read all about this, check the article. ➡️ https://lnkd.in/dFWKGrYZ 📚 SQL #Databases Modern databases designed to handle large-scale and diverse data challenges are crucial for organizations. This article explores seven advanced #SQL databases in 2024: Dolt, MongoDB, Redis, MindsDB, ClickHouse, Elasticsearch, and Snowflake. These databases offer robust performance, scalability, and advanced features. Check out the article to find out more about this. ➡️ https://lnkd.in/dEgnUC8s 👼 #CSS Holy Grail Pattern Do you know what the "#HolyGrail" in CSS is? It's a technique used to create a 3-column #Layout on a webpage. It's called this because of its comprehensive structure for webpage layout, providing the essential components needed for most webpages, using CSS techniques to achieve equal heights for multiple content columns. Learn about it and its advantages in web design below. ➡️ https://lnkd.in/dK-p9KAV 💫 That is it for today. We wish you an amazing weekend! #WebDesign #TipsandTrics #SQLDatabases

Hello everyone, I'd like to share a project I've been working on since mid-2022. Its name is Jequi: https://lnkd.in/d32RNAi5 Jequi is a web server written in Rust, with the aim of being highly extensible and stable. One of the main reasons that led me to develop Jequi was the need for a server that allowed extensibility across different programming languages, similar to what OpenResty does with Lua, but natively on the server itself. Currently, Jequi can execute code in Go, but the idea is that it will eventually support plugins to execute code in other languages (I'm planning to implement a javascript plugin soon). The aim is to make Jequi a complete server similar to Nginx, with exceptional extensibility allowing the community to develop plugins to add functionality without the need to change the core of the server and with an API that allows simple integration with other languages. To demonstrate a little how Jequi works, I've provided three URLs for you to access: - https://lnkd.in/dVscBfFN: Here, I've uploaded some static files. The /go and /conf paths contain different files and there is a mini "WAF" demonstrating Go code being executed by Jequi. Test the WAF by going to: https://lnkd.in/dmCxx8vc. - https://lnkd.in/defa2ach: In this URL, Jequi is working as a proxy for https://lnkd.in/dXnUvH8R, which is another project I developed with Felipe Fernandes, Luan Caliel Casuni Schneider and Kauã Barbosa do Nascimento. - https://lnkd.in/d44fzrC5: In the /google uri, it acts as a proxy for Google and I've configured HTTP/2 to be disabled, so you can only access HTTP/1. All three URLs use the same configuration, which you can see here: https://lnkd.in/dcV-W8Fh I'm very proud of this project and I've learned a lot from it. I intend to keep evolving Jequi, but I think it's solid enough to share with you.

Writing code on the client that runs on the server is a bit "unorthodox" by modern web standards and often thought as a remnant of older times when PHP dominated the web. Next.js brings back this feature in what's called "server actions." We implement a dynamic general-purpose cache-configured Infinite Scroll component in Next.js using server actions: https://lnkd.in/g7qcV-RQ

Day 99 of #100daysofcodingchallenge The topic of #day99 is: 𝑨𝒅𝒅𝒊𝒏𝒈 𝑴𝒆𝒕𝒂𝒅𝒂𝒕𝒂 𝒊𝒏 𝑵𝒆𝒙𝒕.𝒋𝒔 → What is metadata? In web development, metadata provides additional details about a webpage. These details are important for search engines to understand the content of the web. Metadata is crucial for SEO and shareability. → Types of metadata: ● Title metadata: The text displayed on the browser tab and in search engine results. ● Description metadata: A brief summary of the webpage content, often shown in search results. ● Keyword metadata: A list of words describing the webpage content, used by some search engines in the past. ● Open Graph metadata: Controls how a webpage is presented when shared on social media. ● Favicon metadata: Links a small icon (favicon) to the webpage, displayed in the address bar or tab. → Metadata in Next.js: Next.js has a Metadata API that can be used to define your application's metadata. There are two ways you can add metadata to your application: ● Config-based: This involves exporting a static metadata object or using the dynamic generateMetadata function in a layout.tsx or page.tsx file. ● File-based: Next.js has a range of special files that are specifically used for metadata purposes: GitHub repo link: https://lnkd.in/eXgG2AMj #100DaysOfCodeChallenge #Nextjs #Metadata #SEO

Excited to share my latest blog on accessing databases directly in HTML! Learn how to streamline your web development process with this innovative approach. Check it out here: https://lnkd.in/gTQqrjXi check out github repository : https://lnkd.in/giZvzzUG #HTML #WebDevelopment #DatabaseAccess #firebase #blogging

HTTP1.1 vs HTTP2 The first usable version of HTTP was created in 1997. Because it went through several stages of development, this first version of HTTP was called HTTP/1.1. This version is still in use on the web. In 2015, a new version of HTTP called HTTP/2 was created. HTTP/2 solves several problems that the creators of HTTP/1.1 din't anticipate. In particular, HTTP/2 is much faster and more efficient than HTTP/1.1. One of the ways in which HTTP/2 is faster is in how it priorities content during the loading process. In the context of web performance, prioritization refers to the order in which pieces of content are loaded. Suppose a user visits a news website and navigates to an article. Should the photo at the top of the article load first? Should the text of the article load first? Should the banner ads load first? Prioritisation affects a webpage's load time. For example, certain resources, like large JavaScript files, may block the rest of the page from loading if they have to load first. More of the page can load at once if these render-blocking resources load last. In addition, the order in which these page resources load affects how the user perceives page load time. If only behind-the-scenes content (like a CSS file) or content the user can't see immediately loads first, user will think the page is not loading at all. If the content that's most important to the user loads first, such as the image at the top of the page, then the user will perceive the page as loading faster. -> Multiplexing: HTTP/1.1 loads resources one after the other, so if one resource cannot be loaded, it blocks all the other resources behind it. In contrast, HTTP/2 is able to use a single TCP connection to send multiple streams of data at once so that no one resource blocks any other resource. HTTP/2 does this by splitting data into binary-code messages and numbering these messages so that the client knows which stream each binary message belongs to. -> Server push: Typically, a server only serves content to a client device if the client asks for it. However, this approach is not always practical for modern webpages, which often involve several dozen separate resources that the client must request. HTTP/2 solves this problem by allowing a server to "push" content to a client before the client asks for it. The server also sends a message letting the client know what pushed content to expect – like if Bob had sent Alice a Table of Contents of his novel before sending the whole thing. -> Header compression: Small files load more quickly than large ones. To speed up web performance, both HTTP/1.1 and HTTP/2 compress HTTP messages to make them smaller. However, HTTP/2 uses a more advanced compression method called HPACK that eliminates redundant information in HTTP header packets. This eliminates a few bytes from every HTTP packet. Given the volume of HTTP packets involved in loading even a single webpage, those bytes add up quickly, resulting in faster loading