API stands for Application Program Interfaces, which developers use to access web tools or information on the cloud. It allows different cross-platform applications to talk to each other.\nOne of the common examples of it is Google Speech to Text API used when you talk to Google Assistant.
\nGithub APIs( or Github ReST APIs) are the APIs that you can use to interact with GitHub. They allow you to create and manage repositories, branches, issues, pull requests, and many more.\nFor fetching publicly available information (like public repositories, user profiles, etc.), you can call the API. For other actions, you need to provide an authenticated token.
\nThe base URL for GitHub APIs is:- GithubAPI
\nRequest type: GET\nAPI endpoint: /users/{username}
\nExample :- curl https://api.github.com/users/devkapilbansal
Request type: GET\nAPI endpoint: /users/{username}/followers Example :- This URL returns info about all the users that follow a particular user. Request type: GET\nAPI endpoint: /user/{username}/following/{target_username} This endpoint doesn't return any content. It just returns a status code. A status code of 204 means the Example :- When a user follows another user\n When a user doesn't follow another user\n By providing the token, you can create repositories/gists, comment on pull requests/issues, and all other tasks that you can perform from the Web Interface. You can get a token by going to Personal access tokens and clicking on Generate new token. You will be asked for the permissions/scopes of that token. Choose them wisely while creating one as some of these might be destructive. After selecting scopes, click on generate token and save the token somewhere as you will not see that token again. Note:- Store your token in a secured environment while using it. Request type: POST\nAPI endpoint: /user/{repos}\nRequired data: name Example :- Request type: GET\nAPI endpoint: /issues Example :- Request type: POST\nAPI endpoint: /repos/{owner}/{repo_name}/issues\nRequired data: title Example :- Request type: POST\nAPI endpoint: /repos/{owner}/{reponame}/issues/{issueno}/comments\nRequired data: body Example :- Note - The same endpoint is used for commenting on pull requests too. Just change the issue number with the pull request number. Request type: PUT\nAPI endpoint: /repos/{owner}/{reponame}/issues/{issueno} Example :- Note - The same endpoint is valid for updating pull requests too. The above results can be verified on the GitHub website too.\n There are a lot more endpoints that you can explore at Github. Also, you can only do the work you are authorized to with that token.\nAlthough there are plenty of data fields that can be sent with these endpoints, only required ones are shown above. In recent times, Android became the world's most popular operating system for various reasons. As an Android programmer, I want to share what the Android Studio is? Android Studio is an IDE for Google Android Development launched on 16th May 2013, during Google's I/O 2013 event. Android Studio contains all the Android tools to design, test, debug, and profile your application. The Android Studio uses Gradle to manage your project, a Build Automation Tool. For developing your first app, you need to download Android Studio for your preferred platform (Windows®, Mac OS X, or Linux) from the Android developers site. Android Studio can develop and test your application on either a real device or an emulator. You can experience all the awesome features by using Android Studio in-hand. In this article, we're going to build a simple \"Hello World\" Android Application. Requirement: Make sure you have Android Studio installed. If you don't, refer to this link. It's pretty straightforward. To create the application, we will follow these steps through the process in a pretty painless manner. Step 1. Open your Android Studio after installing, and this following screen appears after starting: Step 2. Click on \"Start a New Android Project\" and choose the activity we want the project to be. For me, I'm selecting an empty activity. Step 3. Configure your project by changing the project's name and the desired language the user wants to code with. Android Studio supports two languages, i.e., Java and Kotlin. The user can also choose their desired API, like which android version they want to run, and then click on finish. Step 4.Wait until your Gradle build finishes successfully and find your java and .xml file from folders of the app, as shown in the given image.\n Step 5. Click onto your .xml file to see the initial layout of the file like the given image. You can drag and drop from the palette's items and change your layout by dragging and dropping. Step 6. At last, Run your file by the run button on the top right corner in your emulator configured.\nAnd hurray! You created your First Android Application! This article introduces Android, including just enough hands-on dragging and dropping to hopefully get you excited to know more about the Android platform. As we dig deeper, we can explore the capabilities of this great platform. A login screen is a web page or an entry page to a web/mobile application that requires user identification and authentication, regularly performed by entering a username and password combination.\nThe login process is the most essential feature for any system/application as it provides access to an entire web-site/application or part of it. So, testing of the login screen needs complete coverage. Mentioned below are few tips that can be referred for testing the login screen of any system/application. UI/UX: Security Checks: Functionality: Thanks for reading and happy testing! JAMstack is not a specific set of tools or any language. Still, it's a new and modern way of building apps and sites that deliver better performance, higher security, lower scaling cost, and better developer experience. It achieves this by retaining most of the client-side functionality and abstracting all other functionality to the third-party API. APIs do all the heavy lifting. It is based on the client-side, and it doesn't depend on the backend server. JAM stands for JavaScript, APIs & Markup. JavaScript: Any dynamic programming during the request/response cycle is handled by the JS, running entirely on the client-side. It can be any front-end framework or library or even vanilla JavaScript.\nAPIs: All server-side processes or database actions are contained in reusable APIs, accessed over HTTPS with JavaScript. These can be custom-made or leveraged third party services.\nMarkup: Template markup must be pre-built at the time of deployment, usually using a site generator for content sites or a build tool for web applications. Modern web development architecture based on client-side JavaScript, reusable APIs, and pre-built Markup. The term was introduced by Mathias Biilmann, co-founder of Netlify. With the JAMstack, we have no longer talk about specific technologies such as web servers, programming languages, or databases. Check the following best practices defining a JAMstack project: We can easily understand the JAMstack value when comparing it with a monolithic architecture, today's most common practice in Web development. In a monolithic project, the frontend is closely coupled with a backend server, e.g., node js. Each page request to backend server which pulls data from database renders into Html and then send it across the network. A single page gets regenerated every time the server receives a request for that URL.\nIn a JAMstack architecture, the page request does not go to the server for Html because it directly fetches Html from CDN, where the Html file has been pre-built, and it's ready to be downloaded; that's why no server is involved here. Traditional workflow → Building and hosting are closely coupled. JAMstack workflow → Building and hosting are loosely coupled. A JAMstack architecture can bring all sorts of benefits to the sites and project workflows. Some of the key benefits are: Faster performance: Building JAMstack helps to get pages generated at deploy time since they are mainly stored as Markup and can be served over a CDN.\nHigher security: JAMstack websites reduce server and database, so we don't need to worry about vulnerabilities anymore.\nLower cost: It uses fewer resources, so comparably, it's lower than Others.\nBetter developer experience Frontend developer can focus on frontend development without tied to monolithic architecture. Static site generators remove the need to maintain a separate stack for content and marketing. In a JAMStack architecture, however, the frontend and backend are decoupled. A frontend consists of JavaScript, HTML, and CSS. SSG generates these files during the build process and sends it over a CDN. A JAMStack backend is a content API that returns JSON/XML. This API can be a hosted datastore, a headless CMS, serverless functions, or a custom application. React Speech Recognition is a react hook that accesses the Web Speech API to convert speech from the machine’s microphone to the app’s React components. There are two hooks in this framework: This version requires React 16.8 so that React hooks can be used; please see the full framework README here for more information. Note: This framework uses WebSpeech API. Browser support for this API is currently limited, with Chrome having the best experience. As of June 2020 these browsers support the API: I will be making a simple voice memo app with basic voice commands that run in the browser. If you would like to follow this tutorial, please be ready to work with the create-react-app boilerplate. NOTE: We haven't built the Dictaphone component yet; we'll jump into that next! And that's it for our basic setup! Next, we need to fetch certain props out of useSpeechRecognition. The props we will need are transcript, interimTranscript, finalTranscript, resetTranscript, and listening. You can do so like this: We will also need to enable commands through this hook so add commands to gain access: Moving swiftly onward, we need to need to add several functions that are built into the hook and React. First we will be using useEffect to print the transcript to the page. We will add some page elements to access our dictaphone and print the words to the page. We will need three buttons: stop, listen, and reset - to control the dictaphone and reset the transcript. We may also want to add an indicator that informs the user if the dictaphone is listening or not. Within Dictaphone's return div create the following elements: Your return statement should look similar to this: If you go to localhost:3000 in your browser, the dictaphone should now be working. Now that our dictaphone is working, let's add some commands. We won't do anything too complicated but instead access the functions we already have at our disposal. Within the dictaphone component, declare an array called commands. This will be an array of objects containing two properties each: A voice command that resets the transcript should look like this: When the dictaphone picks up the words 'reset' or 'clear' from the user's speech, it will execute the callback associated with the command. Let's add a response feature. If we add a react hook to manipulate the state like this: Then add the message to the output, we can add commands that generate a response. For instance, if I were to say ‘Hello’, the app would print back 'Hi there!' or something to that effect. Below, I've written some simple commands. With that our quick dictaphone is complete! Take a look at this code where it all comes together: Thanks for following along, and I hope this helps! Statistics suggest that a whopping 64 billion IoT devices can be speculated by 2025. When we talk about the latest technologies shaping the IT industry, Artificial Intelligence and the Internet of Things are often top the list. No wonder these technologies complement each other so well. The duet has revamped the conventional solutions both on the industrial and business fronts.\n Consolidating IoT with AI can help us make Intelligent Machines. These smart automation systems not only help in facilitating the monotonous tasks but making witty decisions without even the slightest of human involvement.\n A typical IoT system integrates various sensors, servo motors, either on an Arduino board or Raspberry pi board. This integrated circuit is then fit into the device that is intended to be made smart. Now, these devices generate data. The data can either be structured or unstructured. The devices actually become smart when they invoke the experiential analysis from this data. This is where AI comes into the picture.\n Both IoT and AI have their part to play. IoT server generates humongous data, while AI has the potential to decipher and derive insights from it. Hence, by coupling both the capabilities, one can establish an intelligent-acting system.\n Businesses and Enterprises across verticals can leverage the IoT-based analysis to make efficacious decisions and creative plans. An artificial Intelligence-based IoT-system can also provide enhanced security and confidentiality.\n The continuous data streams, along with complex data points, can be analyzed using various Machine Learning algorithms like Linear or Logistic Regression, Random Forest, etc. Which, in turn, can help find the loopholes that need to be fixed for efficient system execution.\n It also helps in identifying the deficiencies and find an optimal alternative for a pre-existing architecture. Thus, eventually resulting in increased efficiency.\n AI-enabled IoT systems can predict a wide range of risk points well in advance. This not only helps in mitigating the risk but also ensures a smooth recovery just in case the system failure occurs. This serves as a dual benefit saving the overhead expenses and avoiding a breakdown facilitating BAU (Business as Usual).\n Thus, enterprises should have a well-structured business continuity plan in place so that the risk mitigation can be implemented. IoT-based smart devices get a high degree of benefit when it comes to mitigating risk and disaster recovery, provided they have a research-intensive analysis in place.\n The low-end sensors and ICs which form the entire IoT system may not be cent percent accurate at all times. But, if the system has an AI filter that analyzes the data and sends the refined version for further processing, the scalability prospects can be increased dramatically.\n\nThink of it as a screening mechanism wherein the machine learning techniques analyze and filter the valid data points and transmit if further to give a more concrete overview of things.\n The smart systems are actually 'smart' when they employ experiential learning and caters to the users with a predictive fault-tolerant mechanism. The predictive maintenance enables the users to forecast possible damages and breakdowns well in time.\n\nAnother facet to the reduced expenditure is the reduced operational cost. The integration of AI into the IoT system saves the cost and effort for an explicit mechanism to handle data concerns.\n These were the benefits that an AI-based IoT-system offers to its users. Now, let's look at the real-world implementation of the same.\n Self-Driving Cars are the best example of AI+IoT based system in the real world. These cars can predict the pedestrian's movements and suggest possible measures to be taken for the cognitive sensing machines. It helps in finding the suitable driving speed, amount of time, and the optimum path to reach a destination.\n Thus, if we critically analyze the integration of Artificial Intelligence with the Internet of Things, then it is a win-win situation. The AI-based systems manage the data streams and evaluate data points in real-time to make wise decisions in order to optimize the performance and efficiency of the smart devices and automation systems. Google has prepared a roadmap to restrict third-party cookies in Chrome. Since 04 January 2024, Chrome has rolled out third-party cookie restrictions for 1% of stable clients and 20% of Canary, Dev, and Beta clients. What does it mean for user authentication? On one hand, Google believes third-party cookies are widely used for cross-site tracking, greatly affecting user privacy. Hence, Google wants to phase out (or restrict) supporting third-party cookies in Chrome by early Q2 2025 (subject to regulatory processes). On the other hand, Google introduced Privacy Sandbox to support the use cases (other than cross-site tracking and advertising) previously implemented using third-party cookies. In this article, we’ll discuss: Third-party cookie restrictions affect user authentication in three ways, as follows. If your website or app uses an external Identity Provider (IdP) — like LoginRadius, the IdP sets a third-party cookie when the user authenticates on your app. If you have multiple apps across domains within your organization and authentication is handled using an IdP (internal or external) with web SSO, you already use third-party cookies to facilitate seamless access for each user using a single set of credentials. If you have implemented web SSO with one primary domain and multiple sub-domains of the primary domain, third-party cookie restrictions may not apply. For now, Google doesn’t consider the cookies set by sub-domains as third-party cookies, although this stance may change in the future. For example, you have apps at Federated SSO is similar to, albeit different from, web SSO. It can handle multiple IdPs and applications—aka., Service Providers (SPs)—spanning multiple organizations. It can also implement authentication scenarios that are usually implemented through web SSO. Usually, authentication is handled on a separate pop-up or page when the user wants to authenticate rather than on the application or website a user visits. For example, you already use federated SSO if you facilitate authentication for a set of apps through multiple social identity providers as well as traditional usernames and passwords. Note: It is also possible to store tokens locally, not within cookies. In this case, third-party cookie restrictions won’t affect token-based authentication. However, the restrictions still affect authentication where tokens are stored within third-party cookies (a common and secure method). Google has been developing alternative features and capabilities for Chrome to replace third-party cookies as part of its Privacy Sandbox for Web initiative. Specific to authentication, Google recommends the following: CHIPS are a restricted way of setting third-party cookies on a top-level site without making them accessible on other top-level sites. Thus, they limit cross-site tracking and enable specific cross-site functionalities, such as maps, chat, and payment embeds. For example, a user visits If the user visits You should specifically opt for partitioned cookies (CHIPS), which are set with partitioned and secure cookie attributes. If you’re using an external identity provider for your application, CHIPS is a good option to supplant third-party cookie restrictions. However, CHIPS may not be ideal if you have a web SSO or federated SSO implementation. It creates separate partitioned cookies for each application with a separate domain, which can increase complexity and create compatibility issues. With Storage Access API, you can access the local storage in a third-party context through iframes, similar to when users visit it as a top-level site in a first-party context. That is, it gives access to unpartitioned cookies and storage. Storage Access API requires explicit user approval to grant access, similar to locations, camera, and microphone permissions. If the user denies access, unpartitioned cookies and storage won’t be accessible in a third-party context. It is most suitable when loading cross-site resources and interactions, such as: Verifying user sessions when allowing interactions on an embedded social post or providing personalization for an embedded video.\nEmbedded documents requiring user verification status to be accessible. As it requires explicit user approval, it is advisable to use Storage Access API when you can’t implement an identity use case with the other options. With Related Website Sets, you can declare a Chrome automatically recognizes related website sets declared, accepted, and maintained in this open-source GitHub repository: Related Website Sets It provides access through Storage Access API directly without prompting for user approval, but only after the user interacts with the relevant iframe. It is important to declare a limited number of domains in related website sets that are meaningful and used for specific purposes. Google may block or suspend any exploitative use of this feature. The top-level site can also request approval for specific cross-site resources and scripts to Storage Access API using If you’re using an external identity provider for your web application, you can declare the domain of the identity provider in the related set to ensure limited third-party cookies and storage access to the identity provider, thus ensuring seamless user authentication. Related Website Sets can also work to supplement third-party cookie restrictions in web SSO and federated SSO if the number of web applications (or domains) is limited. FedCM API enables federated SSO without third-party cookies. With FedCM API, a user follows these steps for authentication: You can access a user demo of FedCM here: FedCM. For more information about implementing federated SSO with FedCM API, go through the FedCM developer guide. Firstly, we’re committed to solving our customers' user identity pain points — and preparing for the third-party cookies phase-out is no different. We’ll implement the most relevant and widely useful solutions to facilitate a smooth transition for our customers. Please subscribe to our blog for more information. We’ll update you on how we help with the third-party cookie phase-out. The proposed changes to phase out third-party cookies and suggested alternatives are evolving as Google has been actively collaborating and discussing changes with the border community. Moreover, browsers like Firefox, Safari, and Edge may approach restricting third-party cookies differently than Google does. From LoginRadius, we’ll keep you updated on what we’re doing as a leading Customer Identity and Access Management (CIAM) vendor to prepare for the third-party cookie phase-out. Top-level site: It is the primary site a user has visited. First-party cookie: A cookie set by the top-level site. Third-party cookie: A cookie set by a domain other than the top-level site. For example, let’s assume that a user has visited curl https://api.github.com/devkapilbansal/followersCheck if a user follows another
\ntarget_user is followed by the user, whereas a status code of 404 means the user does not follow a target_user.curl https://api.github.com/devkapilbansal/following/KapilBansalGenerating Token
\nCreating a Repository
\ncurl -H \"Authorization: token ${token}\" -d '{\"name\":\"Github API Testing\"}' https://api.github.com/user/reposList issues assigned to you
\ncurl -H \"Authorization: token ${token}\" https://api.github.com/issuesCreating an issue
\ncurl -H \"Authorization: token ${token}\" -d '{\"title\":\"Issue_For_Test\"}' https://api.github.com/repos/devkapilbansal/Github-API-Testing/issuesCommenting on issue
\ncurl -H \"Authorization: token ${token}\" -d '{\"body\":\"Test comment\"}' https://api.github.com/repos/devkapilbansal/Github-API-Testing/issues/1/commentsOpening/Closing an issue
\ncurl -H \"Authorization: token ${token}\" -d '{\"state\":\"close\"}' https://api.github.com/repos/devkapilbansal/Github-API-Testing/issues/1Results
\nConclusion
\nWhat is Android Studio?
\nAndroid Studio has many exciting features that can help you to develop your Android application like :
\n\n
\nLet's Build Something!!!
\n\n
\nClosing Thoughts
\n\n
\n\n
\n\n
\nWhat is JAMstack
\n\n
\n\n
\nValue of JamStack
\nWorkflow comparison (JAMstack vs. traditional)
\n
\n→ Whenever a user requests a page, The file request to the back end and interacts with a database, back-end code, server, browser, and caching layers.
\n→ Updated code is pushed to servers often through FTP. The database must be updated again.\n→ Updated content is also pushed through CMS like WordPress, Joomla, or drupal.
\n→ Whenever a user requests a page, The file is already pre-built and directly served to the browser from a CDN.
\n→ Updated code is pushed through Git; Modern tools like static site generators easily re-built the entire site.\n→ Updated content is also pushed through GIt or static site CMS.Why the JAMstack?
\nThat's A Wrap!
\nUseful resources
\n\n
\n","frontmatter":{"date":"October 29, 2020","updated_date":null,"description":"You may have heard the term JAMstack before, but you may not have understood what it means. In this article, We will introduce you to JAMstack as to why you need, best practice, and value.","title":"Introduction to JAMstack","tags":["Jamstack","Web"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/bcb720c279e21781ba1caeeec7a1e54e/ee604/jamstack_cover.png","srcSet":"/static/bcb720c279e21781ba1caeeec7a1e54e/69585/jamstack_cover.png 200w,\n/static/bcb720c279e21781ba1caeeec7a1e54e/497c6/jamstack_cover.png 400w,\n/static/bcb720c279e21781ba1caeeec7a1e54e/ee604/jamstack_cover.png 800w,\n/static/bcb720c279e21781ba1caeeec7a1e54e/f3583/jamstack_cover.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Versha Gupta","github":"vershagupta","avatar":null}}}},{"node":{"excerpt":"Overview React Speech Recognition is a react hook that accesses the Web Speech API to convert speech from the machine’s microphone to the…","fields":{"slug":"/engineering/quick-look-at-react-speech-recognition/"},"html":"Overview
\n\n
\nPrerequisites
\n\n
\nWhat We’ll Make
\nLet's Get Started
\nStep 1: Setting up the workspace
\n\n
\n
\nnpx create-react-app dictaphone\n
\n
\nimport Dictaphone from './dictaphoneSetup.js'\n\nfunction App() {\n return (\n <div className="App">\n <header className="Dictaphone-Tester">\n <Dictaphone />\n </header>\n </div>\n );\n}\n\nexport default App;\n
\n
\nnpm i react-speech-recognition\n
\n
\nimport React, { useEffect, useState } from 'react';\nimport SpeechRecognition, { useSpeechRecognition } from 'react-speech-recognition';Step 2: Setting up the dictaphone
\n\n
\n
\nimport React, { useEffect, useState } from 'react';\nimport SpeechRecognition, { useSpeechRecognition } from 'react-speech-recognition';\n\nconst Dictaphone = () => {\n return (\n <div></div>\n );\n};\n\nexport default Dictaphone1;\n
\n
\nconst {\ntranscript,\ninterimTranscript,\nfinalTranscript,\nresetTranscript,\nlistening,\n} = useSpeechRecognition();
\n} = useSpeechRecognition({ commands });
\nuseEffect(() => {\nif (finalTranscript !== '') {\n console.log('Got final result:', finalTranscript);\n}\n}, [interimTranscript, finalTranscript]);
\n if (!SpeechRecognition.browserSupportsSpeechRecognition()) {\n return null;\n }\n\n if (!SpeechRecognition.browserSupportsSpeechRecognition()) {\n console.log('Your browser does not support speech recognition software! Try Chrome desktop, maybe?');\n }\n const listenContinuously = () => {\n SpeechRecognition.startListening({\n continuous: true,\n language: 'en-GB',\n });\n };Step 3: Building the dictaphone controls and page elements
\n\n
\n
\n return (\n <div>\n <div>\n <span>\n listening:\n {' '}\n {listening ? 'on' : 'off'}\n </span>\n <div>\n <button type="button" onClick={resetTranscript}>Reset</button>\n <button type="button" onClick={listenContinuously}>Listen</button>\n <button type="button" onClick={SpeechRecognition.stopListening}>Stop</button>\n </div>\n </div>\n <div>\n <span>{transcript}</span>\n </div>\n </div>\n );Step 4: Adding commands
\n\n
\n
\n const commands = [\n {\n command: 'reset',\n callback: () => resetTranscript()\n },\n {\n command: 'clear',\n callback: () => resetTranscript()\n }\n ]
\nconst [message, setMessage] = useState('');
\n const commands = [\n {\n command: 'reset',\n callback: () => resetTranscript()\n },\n {\n command: 'shut up',\n callback: () => setMessage('I wasn\\'t talking.')\n },\n {\n command: 'Hello',\n callback: () => setMessage('Hi there!')\n },\n ]
\nimport React, { useEffect, useState } from 'react';\nimport SpeechRecognition, { useSpeechRecognition } from 'react-speech-recognition';\n\nconst Dictaphone1 = () => {\n const [message, setMessage] = useState('');\n const commands = [\n {\n command: 'reset',\n callback: () => resetTranscript()\n },\n {\n command: 'shut up',\n callback: () => setMessage('I wasn\\'t talking.')\n },\n {\n command: 'Hello',\n callback: () => setMessage('Hi there!')\n },\n ]\n const {\n transcript,\n interimTranscript,\n finalTranscript,\n resetTranscript,\n listening,\n } = useSpeechRecognition({ commands });\n\n useEffect(() => {\n if (finalTranscript !== '') {\n console.log('Got final result:', finalTranscript);\n }\n }, [interimTranscript, finalTranscript]);\n if (!SpeechRecognition.browserSupportsSpeechRecognition()) {\n return null;\n }\n\n if (!SpeechRecognition.browserSupportsSpeechRecognition()) {\n console.log('Your browser does not support speech recognition software! Try Chrome desktop, maybe?');\n }\n const listenContinuously = () => {\n SpeechRecognition.startListening({\n continuous: true,\n language: 'en-GB',\n });\n };\n return (\n <div>\n <div>\n <span>\n listening:\n {' '}\n {listening ? 'on' : 'off'}\n </span>\n <div>\n <button type="button" onClick={resetTranscript}>Reset</button>\n <button type="button" onClick={listenContinuously}>Listen</button>\n <button type="button" onClick={SpeechRecognition.stopListening}>Stop</button>\n </div>\n </div>\n <div>\n {message}\n </div>\n <div>\n <span>{transcript}</span>\n </div>\n </div>\n );\n};\n\nexport default Dictaphone1;Why IoT and AI together make the perfect match!
\nHow AI enhances IoT-based Systems?
\nWhy use AI-enabled IoT Systems?
\nIncreased Efficiency
\nReliable Disaster Recovery
\nBetter Scalability Prospects
\nReduced Overhead Expenditure
\nReal-Life Implications
\nSelf Driving Cars
\nSumming Up
\n\n
\nHow is User Authentication Affected?
\nExternal Identity Providers
\nWeb SSO
\nexample.com, travel.example.com, stay.example.com, and web SSO is handled by auth.example.com. In this case, third-party cookie restrictions don’t apply.Federated SSO
\n\n
\nChrome’s Alternatives for Third-Party Cookies
\n\n
\nCookies Having Independent Partitioned State (CHIPS)
\na.com with a map embed from map-example.com, which can set a partitioned cookie that is only accessible on a.com. b.com with a map embed from map-example.com, it cannot access the partitioned cookie set on a.com. It has to create a separate partitioned cookie specific to b.com, thus blocking cross-site tracking yet allowing limited cross-site functionality.Storage Access API
\nRelated Website Sets
\nprimary website and associatedSites for limited purposes to grant third-party cookie access and local storage for a limited number of sites.resuestStorageAccessFor() API.Federated Credential Management (FedCM) API
\n\n
\nHow is LoginRadius Preparing for the Third-party Cookie Phase-out?
\nIn Conclusion
\nGlossary
\na.com, which might use an embed from loginradius.com to facilitate authentication. If loginradius.com sets a cookie when the user visits a.com, it is called a third-party cookie as the user hasn’t directly visited loginradius.com.References
\n\n","frontmatter":{"date":"July 08, 2024","updated_date":null,"description":"Google Chrome has planned to phase out third-party cookies, which will affect different website functionalities depending on third-party cookies. This blog focuses on how this phase-out affects identity and user authentication and discusses alternatives for overcoming challenges.","title":"How Chrome’s Third-Party Cookie Restrictions Affect User Authentication?","tags":["Identity","Cookies","Chrome"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png","srcSet":"/static/eb7396060c0adc430dbed2d04b63d431/69585/third-party-cookies-phaseout-chrome.png 200w,\n/static/eb7396060c0adc430dbed2d04b63d431/497c6/third-party-cookies-phaseout-chrome.png 400w,\n/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png 800w,\n/static/eb7396060c0adc430dbed2d04b63d431/f3583/third-party-cookies-phaseout-chrome.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Raghunath Reddy","github":"raghunath-r-a","avatar":null}}}},"pageContext":{"limit":6,"skip":120,"currentPage":21,"type":"//engineering//","numPages":52,"pinned":"17fa0d7b-34c8-51c4-b047-df5e2bbaeedb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}