{"componentChunkName":"component---src-templates-blog-list-template-js","path":"/145","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"excerpt":"Today, I’m very excited to announce that LoginRadius has raised $17 million Series A funding, led by ForgePoint Capital and Microsoft’s…","fields":{"slug":"/identity/loginradius-announces-17m-series-funding-forgepoint-microsoft/"},"html":"

\n \n \n

\n

Today, I’m very excited to announce that LoginRadius has raised $17 million Series A funding, led by ForgePoint Capital and Microsoft’s venture fund, M12. In connection with the funding, both companies will also be joining our board to further our partnership, product and innovation cycles.

\n

Since LoginRadius’ launch in 2012, we have been relentlessly focused on customer identity and have experienced triple digital annual growth for the past two years.

\n

This funding opens huge possibilities for the company, in terms of helping us accelerate product innovation, and to expand globally to help serve the fast-growing $20 billion customer identity market.

\n

You can read the full Press Release here.

\n","frontmatter":{"date":"July 24, 2018","updated_date":null,"description":"LoginRadius, led by ForgePoint Capital and Microsoft's venture fund, M12, has raised $17 million in Series A funding. Both businesses will also join our board in conjunction with the funding to further our collaboration, product and innovation cycles.","title":"LoginRadius Announces $17M Series A Funding from ForgePoint and Microsoft","tags":["industry-news","other"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.6666666666666667,"src":"/static/d9cc8ff6d71e75e836a8749d46c7dfe4/14b42/loginradius-announces-17m-series-funding.jpg","srcSet":"/static/d9cc8ff6d71e75e836a8749d46c7dfe4/f836f/loginradius-announces-17m-series-funding.jpg 200w,\n/static/d9cc8ff6d71e75e836a8749d46c7dfe4/2244e/loginradius-announces-17m-series-funding.jpg 400w,\n/static/d9cc8ff6d71e75e836a8749d46c7dfe4/14b42/loginradius-announces-17m-series-funding.jpg 800w,\n/static/d9cc8ff6d71e75e836a8749d46c7dfe4/47498/loginradius-announces-17m-series-funding.jpg 1200w,\n/static/d9cc8ff6d71e75e836a8749d46c7dfe4/37d86/loginradius-announces-17m-series-funding.jpg 1500w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.jpg"}}}},{"node":{"excerpt":"A JSON Web Token (JWT) is a JSON object that is defined in RFC 7519 as a safe way of transmitting information between two parties…","fields":{"slug":"/engineering/jwt/"},"html":"

A JSON Web Token (JWT) is a JSON object that is defined in RFC 7519 as a safe way of transmitting information between two parties. Information in the JWT is digitally-signed, so that it can be verified and trusted.

\n

JWT Properties

\n\n

JWT Use Cases

\n\n

JWT contains three parts: Header, Payload, and Signature which are separated by a dot.

\n

Header.Payload.Signature

\n

Header

\n

The JWT Header consists of 2 parts:

\n\n
{  \n "typ" : "JWT",  \n "alg" : "HS256"  \n}
\n

Header Algorithm Types:

\n\n

alg Value

\n

Digital Signature or MAC Algorithm

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
AlgoDescription
HS256HMAC using SHA-256 hash algorithm
HS384HMAC using SHA-384 hash algorithm
HS512HMAC using SHA-512 hash algorithm
RS256RSASSA using SHA-256 hash algorithm
RS384RSASSA using SHA-384 hash algorithm
RS512RSASSA using SHA-512 hash algorithm
ES256ECDSA using P-256 curve and SHA-256 hash algorithm
ES384ECDSA using P-384 curve and SHA-384 hash algorithm
ES512ECDSA using P-521 curve and SHA-512 hash algorithm
\n

The Base64Url-encoded Header, which is first part of our JWT, looks like the following:

\n

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9

\n

Payload

\n

The Payload, also known as the JWT claim, contains all of the information we want to transmit.

\n

Different types of claims can be used to build the Payload:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
CodeNameDescription
ississuerIdentifies the principal that issued the JWT.
subsubjectIdentifies the principal that is the subject of the JWT.
audaudienceIdentifies the recipients that the JWT is intended for.
expExpiration timeIdentifies the expiration time on or after which the JWT MUST NOT be accepted for processing.
nbfNot beforeIdentifies the time before which the JWT MUST NOT be accepted for processing.
iatIssue atIdentifies the time at which the JWT was issued.
jtiJWT idUnique identifier for the JWT, can be used to prevent the JWT from being replayed.
\n\n

Example Payload:

\n
{  \n "sub": "1234567890",  \n "name": "Frank Emic",  \n "jti": "4b5fcea6-2a5e-4a9d-97f2-3d8631ea2c5a",  \n "iat": 1521191902,  \n "exp": 1521195630  \n}
\n

This example contains a combination of registered and public claims. “sub”,”jti”,”iat”, and “exp” are registered claims and “name” is a public claim.

\n

The Base64Url-encoded Payload, which is the second part of our JWT, looks like the following:

\n
eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkZyYW5rIEVtaWMiL  \nCJqdGkiOiI0YjVmY2VhNi0yYTVlLTRhOWQtOTdmMi0zZDg2MzFlYTJjNWEiLCJpYXQiOjE1MjExOTE5MDIsImV4cCI6MTUyMTE5NTYzMH0
\n

Signature

\n

The final part of our JWT is the Signature. To create the Signature, we need 3 components:

\n\n

var encodedString = base64UrlEncode(header) + \".\" + base64UrlEncode(payload);
\nHMACSHA256(encodedString, 'secret');

\n

The secret is the Signature held by the server in order to verify tokens and sign new ones.

\n

The above Base64Url-encoded Header and Payload are combined with a dot, and then digitally-signed using the secret. This generates the Signature as the third part of the our JWT:

\n

wGDoDSxfKj3Ns379NVxocwM9TOiwxhxWl

\n

Putting It All Together

\n
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkZyYW5rIEVtaWMiL  \nCJqdGkiOiI0YjVmY2VhNi0yYTVlLTRhOWQtOTdmMi0zZDg2MzFlYTJjNWEiLCJpYXQiOjE1MjExOTE5MDIsImV4cCI6MTUyMTE5NTYzMH0.wGDoDSxfKj3Ns379NVxocwM9TOiwxhxWl
\n

This is our final JWT, containing the Header, Payload, and Signature joined together with dots. It can be passed as a URL parameter, a POST parameter, or in the  HTTP header to authenticate or exchange information.

\n

You can play around with JWT using our JWT SSO Tool.

\n

Note: JWT does not hide information; it just encodes information using the digitally-signed signature and verifies that the information has not been altered over the network. So, do not add any sensitive information in the JWT claim.

\n

Conclusion

\n

JWT comprises three encoded parts: Header, Payload, and Signature. It can be passed as a URL or POST parameter, or in an HTTP header. Due to JWT's lightweight, self-containing, and versatile strucutre, it remains a popular tool for information exchange and authentication.

\n","frontmatter":{"date":"July 11, 2018","updated_date":null,"description":null,"title":"What is JSON Web Token","tags":["JWT","JSON Web Token"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/280ee8f1345faeaa2d33899ee2475b0b/ee604/jwt.png","srcSet":"/static/280ee8f1345faeaa2d33899ee2475b0b/69585/jwt.png 200w,\n/static/280ee8f1345faeaa2d33899ee2475b0b/497c6/jwt.png 400w,\n/static/280ee8f1345faeaa2d33899ee2475b0b/ee604/jwt.png 800w,\n/static/280ee8f1345faeaa2d33899ee2475b0b/f3583/jwt.png 1200w,\n/static/280ee8f1345faeaa2d33899ee2475b0b/e4d72/jwt.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Mayank Agarwal","github":"mayankagrwal","avatar":null}}}},{"node":{"excerpt":"For over 20 years, BroadcastMed has been innovating digital strategies for healthcare providers and organizations. They work with the best…","fields":{"slug":"/identity/broadcastmed-loginradius-customer-success-story/"},"html":"

For over 20 years, BroadcastMed has been innovating digital strategies for healthcare providers and organizations. They work with the best brands in healthcare to help them develop and deliver relevant video-based learning content for physicians and other healthcare professionals.

\n

Committed to producing quality healthcare content in the clinical setting, they were the first in the world to live stream surgical procedures on the internet to provide an intimate look inside the operating room.

\n

The Situation

\n

Being in the forefront of innovation in their industry, BroadcastMed was looking for a way to improve their registration system for a better user experience and partner connectivity while ensuring data security.

\n

The Challenges

\n

BroadcastMed had a few concerns that they wanted to address as they evaluated the LoginRadius solution:

\n\n

The LoginRadius Solution

\n\n\n

BroadcastMed - LoginRadius Customer Success Story

\n

\n \n \n

\n","frontmatter":{"date":"July 05, 2018","updated_date":null,"description":"BroadcastMed has been innovating digital strategies for healthcare providers and organizations. How loginradius assist them in managing user identities.","title":"BroadcastMed, a LoginRadius Customer Success Story","tags":["media-and-publication"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/6ab42d971495ee43864657612f7192c8/14b42/LR-and-BroadcastMed.jpg","srcSet":"/static/6ab42d971495ee43864657612f7192c8/f836f/LR-and-BroadcastMed.jpg 200w,\n/static/6ab42d971495ee43864657612f7192c8/2244e/LR-and-BroadcastMed.jpg 400w,\n/static/6ab42d971495ee43864657612f7192c8/14b42/LR-and-BroadcastMed.jpg 800w,\n/static/6ab42d971495ee43864657612f7192c8/ccd76/LR-and-BroadcastMed.jpg 958w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Karl Wittig","github":null,"avatar":null}}}},{"node":{"excerpt":"Nowadays, many API providers support JSONP requests. One reason for this is that most web browsers disable cross-domain requests when using…","fields":{"slug":"/engineering/understanding-jsonp/"},"html":"

Nowadays, many API providers support JSONP requests. One reason for this is that most web browsers disable cross-domain requests when using basic Ajax.

\n

For example, if your website has the domain \"a.com\", it will use JavaScript hosted on a.com. When the a.com JavaScript makes an Ajax call to make a request on b.com, most web browsers would automatically deem the Ajax call as insecure and disable it. This is called the Same-Origin Policy and web browsers have this to prevent malicious scripts from sending off information to a different domain. Because you need the a.com JavaScript to access b.com to provide your service, this seems to pose a pretty big issue … JSONP to the rescue!

\n

Before understanding JSONP, we already know JSON is an object notation of JavaScript. The \"P\" stands for padding. So it’s a padded JSON, and, to be more specific, the JSON object is padded with a JavaScript function! It looks like this:

\n
jsFunction({"name" : "Ash Ketchum", "role" : "Pokemon trainer"});
\n

Thus, technically, any call that retrieves JSONP, sends off an executable JavaScript line, if and only if your page has a JavaScript function that has the same function name that’s returned in the JSONP!

\n

Let’s look at an example: say the user is on a.com and the browser is using JavaScript hosted on a.com. Then I shouldn't have any issues making Ajax calls to a.com. Ajax GET requests to b.com however, would fail. To avoid this, I first create a method in the JavaScript code that's located on a.com with the following signature

\n
function getData(data){\n// use this data\n}
\n

With this, an Ajax call using JSONP will pass through fine and return this data:

\n
getData({"name" : "test", "value" : "test Value"});
\n

After processing the request, the web browser will call the \"getData\" function because whenever a JavaScript tag is loaded, it gets executed.

\n

Now, the JSON object will get passed as an argument to the getData function as the data parameter. So, you can think of the getData as a callback method of the request.

\n

You can see the below code clearly

\n
function addJavascriptFile = function (url, context) {\ncontext = context || document;\nvar head = context.getElementsByTagName('head')\\[0\\];\nvar js = context.createElement('script');\njs.src = url;\njs.type = "text/JavaScript";\nhead.appendChild(js);\nreturn js;\n}\n\nfunction getJsonp = function (url, handle) {\n\n//creating random name of function as to not conflict with others\nvar func = 'jsonpCallback' + Math.floor((Math.random() \\* 1000000000000000000) + 1);\n\n//adding randomly created function to global window object\nwindow\\[func\\] = function (data) {\n\n//calling handle\nhandle(data);\n\n//removing random named declared function\nwindow\\[func\\] = function () {};\n\n//removing added js\ndocument.head.removeChild(js);\n}\n\n//manipulating and adding js file to head\nvar endurl = url.indexOf('?') != -1 ? url + '&callback=' + func : url + '?callback=' + func;\nvar js = addJavascriptFile(endurl);\n}
\n

The above code is not doing any magic, it will accept the URL of the API and add a parameter callback with a random name, and also create a global method with this same random name. It will then create a script tag and add the complete URL to src of this tag.

\n

The API will read the callback parameter from the query string and, if the callback parameter has the value \"jsonCallback\", the response will be as follows:

\n
jsonpCallback({"name" : "test", "value" : "test Value"});
\n","frontmatter":{"date":"June 29, 2018","updated_date":null,"description":null,"title":"Understanding JSONP","tags":["JavaScript","JSONP","API"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.834862385321101,"src":"/static/e4f5a3ab6183d12ff91d8f3968d0e064/32df2/Screenshot-2018-06-29-12.21.27.png","srcSet":"/static/e4f5a3ab6183d12ff91d8f3968d0e064/69585/Screenshot-2018-06-29-12.21.27.png 200w,\n/static/e4f5a3ab6183d12ff91d8f3968d0e064/497c6/Screenshot-2018-06-29-12.21.27.png 400w,\n/static/e4f5a3ab6183d12ff91d8f3968d0e064/32df2/Screenshot-2018-06-29-12.21.27.png 730w","sizes":"(max-width: 730px) 100vw, 730px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.jpg"}}}},{"node":{"excerpt":"NuGet is a free and open-source package manager for the .NET ecosystem. We can create and install packages using NuGet client tools. All of…","fields":{"slug":"/engineering/using-nuget-to-publish-net-packages/"},"html":"

NuGet is a free and open-source package manager for the .NET ecosystem. We can create and install packages using NuGet client tools. All of the .NET packages are hosted for publishing and consumption on a central package repository known as NuGet Gallery.

\n

Prerequisites

\n\n

Create a class library project

\n

For a .NET package to be published in the NuGet Gallery, it should be a valid class library project. The following instructions can be used to create a simple class library project:

\n\n

For a real useful NuGet package, you should write necessary code which can be used by others to develop applications. However, a class library from the template is sufficient to create a package.

\n

Configure Package Properties

\n
    \n
  1. Go to Project > Properties, select Package tab.
    2. \n
  2. Provide a unique identifier for your package and fill out other required properties. For a description of various properties, please visit here. The properties provided at this stage will be defined in .nuspec manifest that is created by Visual Studio for the project.
    3. \n
  3. To view the properties directly in the project file, right-click the project in Solution Explorer and select Edit AppLogger.csproj.
    4. \n
\n

Run the pack command

\n
    \n
  1. Set the configuration to Release.
    2. \n
  2. Right click the project in Solution Explorer and select the Pack command.
    3. \n
  3. Visual Studio builds the project and creates the .nupkg file. Please note that the built package is in bin\\Release\\netstandard2.0 as befits the .NET Standard 2.0 target.
    4. \n
\n

Acquire API Key

\n
    \n
  1. Sign in to your nuget.org account or create an account if it doesn’t already exist.
    2. \n
  2. Select your user name on the top right, then select API Keys.
    3. \n
  3. Select Create, provide a name for your key, select Select Scopes > Push.
    4. \n
  4. Under API Key, enter * for Glob pattern, then select Create.
    5. \n
  5. After the key is created, select Copy to retrieve the access key needed for publishing the package.
    6. \n
\n

Important: Save your key in a secure location because you cannot copy the key again later on. If you return to the API key page, you need to regenerate the key to copy it.

\n

Publish with nuget push

\n
    \n
  1. Open Command Prompt.
    2. \n
  2. Change to the folder containing the .nupkg file.
    3. \n
  3. \n

    Run the following command, specifying your package name and replacing the key value with your API key:

    \n
    nuget push <PACKAGE-NAME>.nupkg <API-KEY> -Source https://api.nuget.org/v3/index.json
    \n
    4. \n
  4. nuget.exe displays the results of the publishing process.
    5. \n
\n

Manage the published package

\n

You can view your published package in your profile on nuget.org. Select Manage Packages to see the one that was just published. It might take a while for your package to be visible in search results.

\n

If you want to unlist the package and hide it from search results, follow the steps listed below:

\n
    \n
  1. On nuget.org, select your user name on top right, then select Manage Packages.
    2. \n
  2. Find the package to be unlisted under Published and select the trash can icon on the right.
    3. \n
  3. On the next page, clear the box labeled List (package-name) in search results and select Save.
    4. \n
\n","frontmatter":{"date":"June 28, 2018","updated_date":null,"description":null,"title":"Using NuGet to publish .NET packages","tags":["NuGet",".NET"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/61bc9402fec623803bf04d21e948e84a/2a4de/desdev.png","srcSet":"/static/61bc9402fec623803bf04d21e948e84a/69585/desdev.png 200w,\n/static/61bc9402fec623803bf04d21e948e84a/497c6/desdev.png 400w,\n/static/61bc9402fec623803bf04d21e948e84a/2a4de/desdev.png 600w","sizes":"(max-width: 600px) 100vw, 600px"}}},"author":{"id":"Hitesh Pamnani","github":null,"avatar":null}}}},{"node":{"excerpt":"Time Required : less than 10 minutes. Technologies : None. Prerequisites : None. This tutorial will go over how to configure the ‘Actions on…","fields":{"slug":"/engineering/how-to-configure-the-actions-on-google-console-for-google-assistant/"},"html":"

Time Required : less than 10 minutes.

\n

Technologies : None.

\n

Prerequisites : None.

\n

This tutorial will go over how to configure the ‘Actions on Google’ console so that it can be used for your Google Assistant actions/events that can be accessed anywhere the Google Assistant is available from phones to Google Home products.

\n

Steps

\n
    \n
  1. \n

    Create an Actions project and a Dialogflow agent here.

    \n
      \n
    1. Add/import project.\n\n \n \n
      2. \n
    2. Click on Skip(in the upper right corner) choosing a category and click Build -> Actions in the left nav to add your first actions.
      \n\n \n \n
      3. \n
    3. Enter the default text response. This will be the default response for your action until you link your account with LoginRadius and build your customized response. (This will return errors if you leave this empty, even if you handle the response in your code.)\n 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.

      \n

      We’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.

      \n

      The goal? Having them spend less time searching and more time building.

      \n

      What’s New and Improved on the LoginRadius Website?

      \n

      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 spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.

      \n

      Here’s a closer look at what’s new and why it’s important:

      \n

      A Developer-Friendly Dark Theme

      \n

      \"This

      \n

      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.

      \n

      The 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.

      \n

      So, 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.

      \n

      Clear Categorization for LoginRadius Capabilities

      \n

      \"This

      \n

      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
      \n

      This structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.

      \n

      Developer-First Navigation

      \n

      \"This

      \n

      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.

      \n

      The 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.

      \n

      Quick Understanding of Integration Benefits

      \n

      \"This

      \n

      Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.

      \n

      Our platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.

      \n

      Over to You Now!

      \n

      Check out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.

      \n

      Do 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":864,"currentPage":145,"type":"///","numPages":161,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}