This is all for this blog post at the moment. I hope you had a great time reading this and learned something new. Do let me know in the comments if you liked the content.
\n\n\n","frontmatter":{"date":"October 21, 2021","updated_date":null,"description":"This article discusses the differences between Bootstrap 4 and Bootstrap 5 and helps you understand which version you should use for your projects.","title":"Bootstrap 4 vs. Bootstrap 5: What is the Difference?","tags":["Bootstrap","Frontend","Sass"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/8f7ef876ee3ee88f8ddb1becc34c70fa/ee604/coverImage.png","srcSet":"/static/8f7ef876ee3ee88f8ddb1becc34c70fa/69585/coverImage.png 200w,\n/static/8f7ef876ee3ee88f8ddb1becc34c70fa/497c6/coverImage.png 400w,\n/static/8f7ef876ee3ee88f8ddb1becc34c70fa/ee604/coverImage.png 800w,\n/static/8f7ef876ee3ee88f8ddb1becc34c70fa/f3583/coverImage.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rutam Prita Mishra","github":"Rutam21","avatar":null}}}},{"node":{"excerpt":"With the increasing involvement of people in online gaming, there have been many disruptions in the cyber world that's causing major…","fields":{"slug":"/growth/risk-based-authentication-gaming-industry/"},"html":"NOTE: All the images used in this blog post are taken from the official Bootstrap website and are used here for reference purposes only.
\n
With the increasing involvement of people in online gaming, there have been many disruptions in the cyber world that's causing major security concerns—malware, unwanted software, credit card, personal information theft, etc. In fact, the number of people affected by cyber threats related to gaming has increased multifold recently.
\nThe gaming authorities take different measures to protect the gaming industry from these threats, including risk-based authentication. In this article, we are going to discuss what it is and how it works.
\nWhat is Risk-Based Authentication
\nRisk-based authentication (RBA), also called adaptive authentication, monitors consumers’ identity and access using a set of stringent rules. The objective is to authenticate a user profile before allowing it access to ensure that it is not a threat. These restrictions become more stringent with increasing risks.
\nHow Does RBA Works
\nRisk-based authentication works on a model that requires permission and response. A user asks for permission to access a file or software. In response, the file or software responds by presenting options to log in using either an ID and password method or by sending mail or OTP to a registered contact number.
\nWhile performing the authentication, RBA analyses the following factors:
\n- \n
- The device used to gain access, i.e., mobile or laptop. \n
- The location of the device. It includes components such as the physical address of the server. \n
- Network. This refers to the IP address of the user. \n
- How sensitive is the data? Is the required data general or significant? \n
If the system detects any risk, then it follows either of the following measures:
\n- \n
- The system blocks the user if any risk is observed. \n
- The system uses multi-factor authentication to authenticate the user identity, i.e., using SMS or Google authenticator. \n
How to Use RBA in the Gaming Industry
\nA significant amount of people play games online. This includes people of different ages, geographical areas, and criminal backgrounds. This can result in increased cybercrime related to gaming.
\nTo counter these crimes, the gaming industry should put risk-based authentication to use. But how can it help in gaming? The answer is mentioned below:
\nVerifying location
\nIn the USA, only the bettors within the state are allowed to participate in online betting games. Anyone participating from other states may have to face the consequences. RBA can authenticate the user location by asking questions or tracing IP addresses to distinguish the necessary information.
\nYou can also use this to track users who come from places where incidents of cybercrime are common.
\nAuthenticating age
\nAge is another factor that can be verified using RBA. Many games have a certain age limit that you should follow. By identity verification, the authorities can confirm the age of the users.
\nAuthorities can use digital identity verification to gather data from the user. The data may include name, address, and date of birth. RBA can check this data against existing records to see whether the information is correct or not or has been changed recently.
\nAvoiding money laundering with KYC
\nMany people use money from criminal proceedings and money laundering in online gaming or betting. Know our customer (KYC) and anti-money laundering initiates are taken into account in these cases.
\nThe KYC is usually not required at the time of signing in but when the suspicion arises. Suspicion may arise in the cases where the user pays a huge amount of money in one go.
\nIdentity verification is done at the time of KYC, and it requires identity verification via documents and photos of a user. Incorporating AML and KYC at the time of payment for gaming makes the entire risk mitigation process smarter.
\nWhat Should You Look for in a Risk-Based Authentication System
\nAn effective RBA can make a huge difference between a safe and unsafe gaming experience. When you are choosing an RBA, look for the following features:
\n- \n
- Real-time data: Access to real-time data helps identify the risk at the earliest and prevent potential threats that may affect the gaming system. \n
- User analytics: User analytics include all the information related to a user, like their name, address, and age. This analytics helps in profiling potential cybercriminals. \n
- Multi-factor authentication or verification: If any risk is detected or a user seems questionable, RBA can use extra authentication. It includes asking for additional information that may reveal useful insights about the background of a user. \n
- Configuration policies: Passwords are widely used for authentication, but other configuration policies help set up advanced technology like RBA that ensures the security and smart functioning of the gaming industry. \n
The focus is to confide the users' personal information, and with LoginRadius, you will find more than just one solution to your digital predicaments. Contact us to know more.
\n\n","frontmatter":{"date":"October 18, 2021","updated_date":null,"description":"It is not possible to create an application that protects against everything, especially in the gaming industry. Although it is important to effectively protect sensitive data in electronic gaming environments, it is also essential to create systems that maintain the fun and excitement of online gaming. Risk-Based Authentication makes it possible.","title":"Embracing Risk-Based Authentication in the Gaming Industry","tags":null,"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.941747572815534,"src":"/static/12e96a1af309feefb043f036ea486d0b/14b42/rba-gaming-cover.jpg","srcSet":"/static/12e96a1af309feefb043f036ea486d0b/f836f/rba-gaming-cover.jpg 200w,\n/static/12e96a1af309feefb043f036ea486d0b/2244e/rba-gaming-cover.jpg 400w,\n/static/12e96a1af309feefb043f036ea486d0b/14b42/rba-gaming-cover.jpg 800w,\n/static/12e96a1af309feefb043f036ea486d0b/16310/rba-gaming-cover.jpg 1024w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Navanita Devi","github":null,"avatar":null}}}},{"node":{"excerpt":"Delivering rich consumer experiences isn’t a luxury anymore; it’s the necessary fuel that keeps businesses up and running in the most…","fields":{"slug":"/identity/sso-integration-secure-cx/"},"html":"Delivering rich consumer experiences isn’t a luxury anymore; it’s the necessary fuel that keeps businesses up and running in the most competitive digital ecosystem.
\nMoreover, the entire e-commerce industry’s success largely depends on how they make their consumers feel whenever they land on their website or mobile application.
\nWhether it’s the personalized greeting or a suggestion of a product based on a buyer’s search history, online vendors can deliver rich consumer experiences that not only enhance sales but ensure returning customers.
\nHowever, when we talk about loyalty platforms, things aren’t that smooth as they should be. In other words, consumers can’t indulge in a seamless experience when they connect with a loyalty platform for potential benefits.
\nStats reveal that approximately 75B U.S. dollars were spent on loyalty management back in 2019.
\nBusinesses are spending a good amount of money and time offering loyalty to their consumers, which eventually brings good returns on investment. But not everyone can yield good profits.
\nBuyers cannot redeem benefits as cash points or discounts on e-commerce platforms since the most significant barrier, i.e., identity verification, hampers user experience. This leads to poor conversions and eventually a decline in the number of visitors on loyalty platforms.
\nThis post helps you understand the biggest challenge for loyalty platforms and how Single Sign-On (SSO) integration for consumer loyalty platforms can be the game-changer.
\nThe Biggest Challenge for Consumer Loyalty Platforms
\nAs discussed earlier, consumer experience is essential for any online business; the same goes for loyalty platforms.
\nConsumers today are always on a hunt for a seamless experience as they already interact with brands like Amazon, Microsoft, and Apple. They know what a great user experience means, and they’re expecting at least something closer to it.
\nHowever, when they interact with platforms offering loyalty for third-party websites, including Amazon, they cannot find that sophisticated and seamless experience.
\nA little friction during the authentication process can lead to a poor experience for consumers that further impacts overall sales.
\nAuthenticating and authorizing a user by the loyalty provider for an e-commerce vendor through its unique identity should be a matter of seconds.
\nUnfortunately, it isn’t.
\nUsers may face several challenges while expecting discount benefits or redeeming cash points because their loyalty provider lacks a robust identity management partner.
\nLet’s understand this issue further in detail.
\nConsequences of a Bad Identity Management System for Loyalty Platforms
\nManaging the consumer journey in the business landscape can be challenging for any organization, especially if they’re dealing with multiple parties.
\nThe same goes for accessing electronic records and loyalty vendors handling multiple identities of consumers seeking benefits and their regular clients and employees.
\nPoor identity management impacts sales and affects recurring consumers since users demand rich experiences, and when it’s about rewards, they cannot compromise. Moreover, the market is flooded with several loyalty providers, and consumers are just a click away to switch.
\nHence, loyalty vendors must quickly put their best effort into enhancing user experience, especially when they’re handling third-party users seeking benefits in terms of rewards and discounts that eventually build trust and lasting relationships.
\nFurthermore, securing consumer accounts is yet another tough nut to crack for enterprises delivering loyalty benefits since attacks and fraud reward platforms are always looking for ways to sneak into a network and exploit consumer identities.
\nThis raises the demand for a robust mechanism that handles consumer identities securely and manages consumer onboarding from third-party websites like a breeze.
\nHere’s where a consumer identity and access management (CIAM) solution like LoginRadius comes into play.
\nLet’s understand how industry-leading CIAM like LoginRadius pave the path for a flawless user onboarding experience coupled with robust security for loyalty platforms using cutting-edge SSO integration.
\nWhy is LoginRadius’ Single Sign-On (SSO) the Need of the Hour for Loyalty Platforms?
\nSingle Sign-on (or SSO) is a unique authentication method that allows users to access multiple applications with a single set of credentials, like a username and password.
\nLoginRadius SSO is designed to simplify the verification process and create a seamless environment when accessing multiple apps, portals, and servers.
\nSimply put, LoginRadius SSO has entirely removed the need for users to enter their login credentials for individual applications. Alternatively, users sign in once, and the interface sends the necessary credentials to the assigned systems through various proxies and agents.
\nLoginRadius’ SSO Capabilities
\nLoginRadius Single Sign-On is the perfect fit for organizations that want to reduce their data protection vulnerabilities, improve consumer experiences, and streamline processes for identity management and log in.
\nWhat else makes LoginRadius single sign-on the best choice for your enterprise? Let's find out.
\nSSO offers robust security
\nAccording to a survey by Google, 53% of users still reuse the same password for multiple accounts. Therefore, reducing login to a single set of credentials is a good start in reducing the attackers' surface area. Because users log in only once, there are fewer opportunities for mistakes.
\nEnterprises can also go the extra mile with two-factor authentication (2FA) and multifactor authentication (MFA) techniques.
\nSSO helps with regulatory compliance
\nRegulations like HIPAA require users to authenticate before they can access electronic records along with options like automatic log-off and audit controls to track user access.
\nLoginRadius SSO makes these requirements around data access and control at the granular level. It also allows enterprises and developers to comply with regulations that require provisioning and deprovisioning users.
\nSSO saves time
\nBecause users need not remember multiple credentials for multiple logins anymore, it saves time and improves productivity.
\nAlso, remembering one password instead of many miraculously reduces password fatigue. More so, it gives users the perfect opportunity to come up with even stronger passwords.
\nSSO lowers IT costs
\nThis one is interlinked. When there are fewer passwords to remember, there will be even lesser chances of users forgetting them—leading to a reduced number of reset help tickets. This will reduce the need for IT involvement and lower IT costs.
\nWhy LoginRadius is the Right Choice in 2021 and Beyond
\nLoginRadius’ cutting-edge CIAM goes beyond a single sign-on solution with its broader consumer identity and access management functions, but it is an excellent platform for SSO nonetheless.
\nWith its simple-to-use one-click access, it works great for small to large-scale, consumer-facing deployment. The added 2FA/MFA security protects data—both in-house and consumers.
\nThe LoginRadius Identity Platform offers SSO in the following ways:
\n- \n
- Web SSO: LoginRadius offers browser-based session management when the SSO is required between two or more web applications. It uses localStorage, cookies, and similar storage mechanisms to maintain the user's session across applications. To execute the authentication, a centralized domain operated by LoginRadius IDX is used. \n
- Mobile SSO: After logging into an application, the user can log in across multiple apps without the need for multiple passwords. It works by storing the LoginRadius access token in a shared session. It enables you to identify a currently active session and utilize the data to configure the user account in successive applications. \n
- Federated SSO: Login also helps you implement SSO with third-party applications. It is done through federated SSO. LoginRadius Identity Platform supports all major industry single sign-on protocols like SAML, JWT, OAuth, and OpenID SSO protocols for interaction with various third-party web applications. \n
- Custom IDPs: Consider this as Social Login. Custom IDPs are used to configure a Social Login provider that is not available in the default list of providers by LoginRadius. You can use any external database to authenticate your application users. \n
One of the most used authentication standards in web applications is the JSON Web Token standard. It is mostly used for authentication, authorization, and information exchange.
\nJSON Web tokens are made of three parts separated by dots (.) — and look like this typically: xxxxx.yyyyy.zzzzz. These correspond to the Header, the Payload, and the Signature. You can learn more about JWT tokens here.
And before using them and continuing to read this article, you might want to check the advantages compared to the session authentication method. You can learn more about JWTs vs. Sessions here.
\nWhen to Use JWT Authentication?
\nAuthentication
\nAuthentication is done when a client successfully proves its identity via a login endpoint. If it's successful, the server will create JSON Web Token and send it in response to the client.
\nThe client will use this JWT on every request for a protected resource.
\nAuthorization
\nA server built on JWT for authorization will create a JWT when a client logs in. This JWT is signed, so any other party can’t alter it.
\nEach time the client has access to protected resources, the server will verify that the JWT’s signature matches its payload and header to determine that the JWT is valid.
\nThen if the JWT is successfully verified, it can grant or deny access to the resource.
\nData Exchanges
\nJWT is also a great way to secure information transmission between parties — two servers, for example — and because you can verify the validity of the token (signature, structure, or the standards claimed in the JWT).
\nWhen Not to Use JWT Authentication?
\nRevocable Tokens
\nJWT doesn’t require any lookup of the database, so revoking them before the expiration is quite difficult.
\nRevocation is very important in many cases.
\nFor example, when logging out users or banning users, or changing permissions or passwords instantly, if the token hasn't been revoked, it might be possible for the user to continue to make requests even if this user no longer has the required authorization to do so.
\nSensitive Information
\nJWT is usually signed to protect against data manipulation or alteration. With this, the data can be easily read or decoded.
\nSo, you can’t include sensitive information such as the user’s record or any identifier because the data is not encrypted.
\nCookie Size Factor
\nThe size of a JWT is greater than the size of a session token. And this can quickly increase linearly as you add more data to the JWT. And because you need to send the JWT at each request, you're increasing the payload size. This can become heavily complex if there is a low-speed internet connection.
\nJWT: Best Practices
\n1) JWT as Access Token
\nJWT can be used as an access token to prevent unwanted access to a protected resource. They're often used as Bearer tokens, which the API will decode and validate before sending a response.
\nAuthorization: Bearer <token>2) Refresh Tokens Logic with JWT
\nHow do you get a new access token if this one is expired? The natural first idea is to log in again. But from a User Experience point, this can be quite painful.
\nJWT can be used as refresh tokens; these tokens are used to retrieve a new access token.
\nFor example, when a client requests a protected resource and receives an error, which can mean that the access token has expired, the client can be issued a new access token by sending a request with a refresh token in the headers or the body.\nIf the refresh token is valid, a new access token will be created and sent as a response.
\nNote that the refresh token is obtained at authentication and has a bigger lifetime.
\n3) Which Signing Algorithm to Use?
\nInterestingly enough, JWT can be signed using many different algorithms. But let’s quickly talk about the alg value in the JWT header. When it’s decoded:
The alg value in JWT headers simply tells you how the JWT was signed. For example, with an alg value of RS512.
RS512 => RS 512 where RS is the signature algorithm and SHA-512 is the hashing algorithm.
SHA-512 will produce a 512-bits hash while SHA-256 will produce a 256-bit hash. And each of these algorithms gives you 50% of their output size of security level. This means that, for example, SHA-512 will provide you with 256-bits security.
In any case, make sure to use a minimum of 128-bit security.
4) Expiration, Issued Time, and Clock Skew
\nJWTs are hard to revoke when they are created. Most of the time, you’ll have to wait until expiry. That’s why you should use a short expiration time.
\nAdditionally, you can implement your own revocation system.
\nJWT comes with a time-based claim iat — issued at. It can be used to reject tokens that are too old to be used by the resource server.\nAnd clock skew specifies the allowed time difference (in seconds) between the server and the client clocks when verifying exp and nbf time-based claims. The default recommended default value is 5.
5) JWT Signature
\nThe last part of a JWT is the signature, which is simply a MAC (or Message Authentication Code). This signature is created by the server using a secret key. This secret key is an important part of the JWT signature.
\nThere are two things to respect to decrease the probability of a secret key leaking or a successful brute force attack:
\n- \n
- Keep the secret key secret \n
- \n
The minimum key length must be equal to the size of bits of the hash function used along with the HMAC algorithm.
\n\n
\n\"A key of the same size as the hash output (for instance, 256 bits for \"HS256\") or larger MUST be used with this algorithm.\" - JSON Web Algorithms (RFC 7518), 3.2 HMAC with SHA-2 Functions
\n \n
6) Where to Store the Tokens?
\nThe easiest ways to store a token on the client side are localStorage and sessionStorage. However, both are vulnerable to XSS attacks, and sessionStorage is cleaned if the browser is closed.
A better, secure way is to store JWT in cookies. Cookies are not accessible via JavaScript, they can’t be read and written, and interestingly, they are automatically sent to the server.
\n7) Always Use HTTPS
\nOne of the main benefits of HTTPS is that it comes with security and trust. HTTP path and query parameters are encrypted when using HTTPS.
Then, there is no risk of someone intercepting the request, particularly the token in transit. These types of attacks are commonly called MitM (man in the middle) attacks that can be successful on compromised or insecure networks.
\nConclusion
\nThis article discussed JWT and some best practices to fully use its potential.
\nJWT is simply an authentication standard with its pros and cons. Thus, knowing some best practices can really help you use JWT better.
\n","frontmatter":{"date":"October 14, 2021","updated_date":null,"description":"JWT is a common way of implementing authentication in web and mobile apps. Read more to know how you can use JWT and learn the necessary best practices.","title":"JWT Authentication — Best Practices and When to Use","tags":["JWT","Authentication"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/dd60f505aa7484a17a6cd0b90a5b0fae/ee604/cover-image.png","srcSet":"/static/dd60f505aa7484a17a6cd0b90a5b0fae/69585/cover-image.png 200w,\n/static/dd60f505aa7484a17a6cd0b90a5b0fae/497c6/cover-image.png 400w,\n/static/dd60f505aa7484a17a6cd0b90a5b0fae/ee604/cover-image.png 800w,\n/static/dd60f505aa7484a17a6cd0b90a5b0fae/f3583/cover-image.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Kolawole Mangabo","github":"koladev32","avatar":null}}}}]},"markdownRemark":{"excerpt":"Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards…","fields":{"slug":"/identity/developer-first-identity-provider-loginradius/"},"html":"Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards and refining approaches to building secure, seamless experiences.
\nWe’re here to support developers on that journey. We know how important simplicity, efficiency, and well-structured documentation are when working with identity and access management solutions. That’s why we’ve redesigned the LoginRadius website—to be faster, more intuitive, and developer-first in every way.
\nThe goal? Having them spend less time searching and more time building.
\nWhat’s New and Improved on the LoginRadius Website?
\nLoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.
\nHere’s a closer look at what’s new and why it’s important:
\nA Developer-Friendly Dark Theme
\n![\"This](\"/f46881583c7518a93bb24e94c32320de/a-developer-friendly-dark-theme.webp\")
Developers spend long hours working in dark-themed IDEs and terminals, so we’ve designed the LoginRadius experience to be developer-friendly and align with that preference.
\nThe new dark mode reduces eye strain, enhances readability, and provides a seamless transition between a coding environment and our platform. Our new design features a clean, modern aesthetic with a consistent color scheme and Barlow typography, ensuring better readability. High-quality graphics and icons are thoughtfully placed to enhance the content without adding visual clutter.
\nSo, whether you’re navigating our API docs or configuring authentication into your system, our improved interface will make those extended development hours more comfortable and efficient.
\nClear Categorization for LoginRadius Capabilities
\n![\"This](\"/e5358b82be414940f3fb146013845933/capabilities.webp\")
We’ve restructured our website to provide a straightforward breakdown of our customer identity and access management platform capabilities, helping you quickly find what you need:
\n- \n
- Authentication: Easily understand how to choose the right login method, from traditional passwords and OTPs to social login, federated SSO, and passkeys with few lines of code. \n
- Security: Implement no-code security features like bot detection, IP throttling, breached password alerts, DDoS protection, and adaptive MFA to safeguard user accounts. \n
- User Experience: Leverage AI builder, hosted pages, and drag-and-drop workflows to create smooth, branded sign-up and login experiences. \n
- High Performance & Scalability: Confidently scale with sub-100ms API response times, 100% uptime, 240K+ RPS, and 28+ global data center regions. \n
- Multi-Brand Management: Efficiently manage multiple identity apps, choosing isolated or shared data stores based on your brand’s unique needs. \n
This structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.
\nDeveloper-First Navigation
\n![\"This](\"/a8c155c2b6faf3d5f4b4de4e2b14d763/developers-menu.webp\")
We’ve been analyzing developer workflows to identify how you access key resources. That’s why we redesigned our navigation with one goal in mind: to reduce clicks and make essential resources readily available.
\nThe new LoginRadius structure puts APIs, SDKs, and integration guides right at the menu bar under the Developers dropdown so you can get started faster. Our Products, Solutions, and Customer Services are also clearly categorized, helping development teams quickly find the right tools and make informed decisions.
\nQuick Understanding of Integration Benefits
\n![\"This](\"/b2f9a964a2da0ea83e2f8596b833bba7/we-support-your-tech-stack.webp\")
Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.
\nOur platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.
\nOver to You Now!
\nCheck out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.
\nDo not forget to explore the improved navigation and API documentation, and get started with our free trial today. We’re excited to see what you’ll build with LoginRadius!
\n","frontmatter":{"date":"February 21, 2025","updated_date":null,"description":"LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve redesigned our website interface, making navigation more intuitive and reassuring that essential resources are easily accessible.","title":"Revamped & Ready: Introducing the New Developer-First LoginRadius Website","tags":["Developer tools","API","Identity Management","User Authentication"],"pinned":true,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp","srcSet":"/static/80b4e4fbe176a10a327d273504607f32/61e93/hero-section.webp 200w,\n/static/80b4e4fbe176a10a327d273504607f32/1f5c5/hero-section.webp 400w,\n/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp 800w,\n/static/80b4e4fbe176a10a327d273504607f32/99238/hero-section.webp 1200w,\n/static/80b4e4fbe176a10a327d273504607f32/7c22d/hero-section.webp 1600w,\n/static/80b4e4fbe176a10a327d273504607f32/1258b/hero-section.webp 2732w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.jpg"}}}},"pageContext":{"limit":6,"skip":366,"currentPage":62,"type":"///","numPages":161,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}