url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://dumb.dev.to/bingkahu/gemini-told-me-it-had-20-years-in-coding-experience-and-spent-2-hours-debugging-a-for-loop-42p7#comments | Gemini told me it had 20 years in coding experience and spent 2 hours debugging a for-loop - DUMB DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DUMB DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse bingkahu Posted on Jan 12 Gemini told me it had 20 years in coding experience and spent 2 hours debugging a for-loop # coding # ai # dumb # debugging The "Expert" Experience So I asked an AI with "20 years of experience" to help me out today. It bragged about building complex game engines, unofficial wikis, and massive websites through GitHub, but then it absolutely folded when it saw a basic for loop. We spent the next two hours staring at the screen together in silence. Turns out, "senior developer" just means you've made the same mistake so many times you've started calling it a feature. 10/10 experience, would debug nothing again. Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Om Shree Om Shree Om Shree Follow Technical Evangelist | AI Researcher | Simplifying Complex AI & Agent Workflows for Developers Email omshree0709@gmail.com Location India Education Jaypee University Of Information Technology Pronouns He/Him Work Founder of Shreesozo Joined Feb 27, 2025 • Jan 12 Dropdown menu Copy link Hide 😂😂😂 Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse bingkahu Follow Full-stack developer focused on decentralized communication and privacy-centric web applications. Lead maintainer of CodeChat, an open-source peer-to-peer messaging platform built on WebRTC and PeerJS Education School Work Student Joined Jan 11, 2026 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DUMB DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DUMB DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://open.forem.com/code-of-conduct#main-content | Code of Conduct - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Code of Conduct Last updated July 31, 2023 All participants of DEV Community are expected to abide by our Code of Conduct and Terms of Service , both online and during in-person events that are hosted and/or associated with DEV Community. Our Pledge In the interest of fostering an open and welcoming environment, we as moderators of DEV Community pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Our Standards Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Referring to people by their pronouns and using gender-neutral pronouns when uncertain Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Citing sources if used to create content (for guidance see DEV Community: How to Avoid Plagiarism ) Following our AI Guidelines and disclosing AI assistance if used to create content Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances The use of hate speech or communication that is racist, homophobic, transphobic, ableist, sexist, or otherwise prejudiced/discriminatory (i.e. misusing or disrespecting pronouns) Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Plagiarizing content or misappropriating works Other conduct which could reasonably be considered inappropriate in a professional setting Dismissing or attacking inclusion-oriented requests We pledge to prioritize marginalized people's safety over privileged people's comfort. We will not act on complaints regarding: 'Reverse' -isms, including 'reverse racism,' 'reverse sexism,' and 'cisphobia' Reasonable communication of boundaries, such as 'leave me alone,' 'go away,' or 'I'm not discussing this with you.' Someone's refusal to explain or debate social justice concepts Criticisms of racist, sexist, cissexist, or otherwise oppressive behavior or assumptions Enforcement Violations of the Code of Conduct may be reported by contacting the team via the abuse report form or by sending an email to support@dev.to . All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Further details of specific enforcement policies may be posted separately. Moderators have the right and responsibility to remove comments or other contributions that are not aligned to this Code of Conduct or to suspend temporarily or permanently any members for other behaviors that they deem inappropriate, threatening, offensive, or harmful. If you agree with our values and would like to help us enforce the Code of Conduct, you might consider volunteering as a DEV moderator. Please check out the DEV Community Moderation page for information about our moderator roles and how to become a mod. Attribution This Code of Conduct is adapted from: Contributor Covenant, version 1.4 Write/Speak/Code Geek Feminism 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:29 |
https://dumb.dev.to/t/debugging | Debugging - DUMB DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DUMB DEV Community Close # debugging Follow Hide Troubleshooting code issues Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Gemini told me it had 20 years in coding experience and spent 2 hours debugging a for-loop bingkahu bingkahu bingkahu Follow Jan 12 Gemini told me it had 20 years in coding experience and spent 2 hours debugging a for-loop # coding # ai # dumb # debugging 3 reactions Comments 1 comment 1 min read loading... trending guides/resources Gemini told me it had 20 years in coding experience and spent 2 hours debugging a for-loop 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DUMB DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DUMB DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://stackoverflowteams.com/teams/create/free?isLogin=true | Stack Internal - Create Profile Skip to main content Get started Collaborate, connect, and grow your team’s wisdom Free plan Free knowledge sharing and collaboration platform No credit card required Free for up to 50 members Save and share information with your whole team Search for answers when you need them most Log in with Google Log in with GitHub Log in with Facebook Work email Password Forgot password? Log in Don’t have an account? Sign up Used by thousands of organizations around the globe | 2026-01-13T08:48:29 |
https://www.linkedin.com/legal/privacy-policy?trk=registration_footer-privacy-policy | LinkedIn Privacy Policy Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Privacy Policy Effective November 3, 2025 Your Privacy Matters LinkedIn’s mission is to connect the world’s professionals to allow them to be more productive and successful. Central to this mission is our commitment to be transparent about the data we collect about you, how it is used and with whom it is shared. This Privacy Policy applies when you use our Services (described below). We offer our users choices about the data we collect, use and share as described in this Privacy Policy, Cookie Policy , Settings and our Help Center. Key Terms Choices Settings are available to Members of LinkedIn and Visitors are provided separate controls. Learn More . Table of Contents Data We Collect How We Use Your Data How We Share Information Your Choices and Obligations Other Important Information Introduction We are a social network and online platform for professionals. People use our Services to find and be found for business opportunities, to connect with others and find information. Our Privacy Policy applies to any Member or Visitor to our Services. Our registered users (“Members”) share their professional identities, engage with their network, exchange knowledge and professional insights, post and view relevant content, learn and develop skills, and find business and career opportunities. Content and data on some of our Services is viewable to non-Members (“Visitors”). We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. Members and Visitors located in the Designated Countries or the UK can review additional information in our European Regional Privacy Notice . Services This Privacy Policy, including our Cookie Policy applies to your use of our Services. This Privacy Policy applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-branded sites, apps, communications and services offered by LinkedIn (“Services”), including off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins, but excluding services that state that they are offered under a different privacy policy. For California residents, additional disclosures required by California law may be found in our California Privacy Disclosure . Data Controllers and Contracting Parties If you are in the “Designated Countries”, LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you are outside of the Designated Countries, LinkedIn Corporation will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. As a Visitor or Member of our Services, the collection, use and sharing of your personal data is subject to this Privacy Policy and other documents referenced in this Privacy Policy, as well as updates. Change Changes to the Privacy Policy apply to your use of our Services after the “effective date.” LinkedIn (“we” or “us”) can modify this Privacy Policy, and if we make material changes to it, we will provide notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. If you object to any changes, you may close your account. You acknowledge that your continued use of our Services after we publish or send a notice about our changes to this Privacy Policy means that the collection, use and sharing of your personal data is subject to the updated Privacy Policy, as of its effective date. 1. Data We Collect 1.1 Data You Provide To Us You provide data to create an account with us. Registration To create an account you need to provide data including your name, email address and/or mobile number, general location (e.g., city), and a password. If you register for a premium Service, you will need to provide payment (e.g., credit card) and billing information. You create your LinkedIn profile (a complete profile helps you get the most from our Services). Profile You have choices about the information on your profile, such as your education, work experience, skills, photo, city or area , endorsements, and optional verifications of information on your profile (such as verifications of your identity or workplace). You don’t have to provide additional information on your profile; however, profile information helps you to get more from our Services, including helping recruiters and business opportunities find you. It’s your choice whether to include sensitive information on your profile and to make that sensitive information public. Please do not post or add personal data to your profile that you would not want to be publicly available. You may give other data to us, such as by syncing your calendar. Posting and Uploading We collect personal data from you when you provide, post or upload it to our Services, such as when you fill out a form, (e.g., with demographic data or salary), respond to a survey, or submit a resume or fill out a job application on our Services. If you sync your calendars with our Services, we will collect your calendar meeting information to keep growing your network by suggesting connections for you and others, and by providing information about events, e.g. times, places, attendees and contacts. You don’t have to post or upload personal data; though if you don’t, it may limit your ability to grow and engage with your network over our Services. 1.2 Data From Others Others may post or write about you. Content and News You and others may post content that includes information about you (as part of articles, posts, comments, videos) on our Services. We also may collect public information about you, such as professional-related news and accomplishments, and make it available as part of our Services, including, as permitted by your settings, in notifications to others of mentions in the news . Others may sync their calendar with our Services Contact and Calendar Information We receive personal data (including contact information) about you when others import or sync their calendar with our Services, associate their contacts with Member profiles, scan and upload business cards, or send messages using our Services (including invites or connection requests). If you or others opt-in to sync email accounts with our Services, we will also collect “email header” information that we can associate with Member profiles. Customers and partners may provide data to us. Partners We receive personal data (e.g., your job title and work email address) about you when you use the services of our customers and partners, such as employers or prospective employers and applicant tracking systems providing us job application data. Related Companies and Other Services We receive data about you when you use some of the other services provided by us or our Affiliates , including Microsoft. For example, you may choose to send us information about your contacts in Microsoft apps and services, such as Outlook, for improved professional networking activities on our Services or we may receive information from Microsoft about your engagement with their sites and services. 1.3 Service Use We log your visits and use of our Services, including mobile apps. We log usage data when you visit or otherwise use our Services, including our sites, app and platform technology, such as when you view or click on content (e.g., learning video) or ads (on or off our sites and apps), perform a search, install or update one of our mobile apps, share articles or apply for jobs. We use log-ins, cookies, device information and internet protocol (“IP”) addresses to identify you and log your use. 1.4 Cookies and Similar Technologies We collect data through cookies and similar technologies. As further described in our Cookie Policy , we use cookies and similar technologies (e.g., pixels and ad tags) to collect data (e.g., device IDs) to recognize you and your device(s) on, off and across different services and devices where you have engaged with our Services. We also allow some others to use cookies as described in our Cookie Policy. If you are outside the Designated Countries, we also collect (or rely on others, including Microsoft, who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. Learn more . You can opt out from our use of data from cookies and similar technologies that track your behavior on the sites of others for ad targeting and other ad-related purposes. For Visitors, the controls are here . 1.5 Your Device and Location We receive data through cookies and similar technologies When you visit or leave our Services (including some plugins and our cookies or similar technology on the sites of others), we receive the URL of both the site you came from and the one you go to and the time of your visit. We also get information about your network and device (e.g., IP address, proxy server, operating system, web browser and add-ons, device identifier and features, cookie IDs and/or ISP, or your mobile carrier). If you use our Services from a mobile device, that device will send us data about your location based on your phone settings. We will ask you to opt-in before we use GPS or other tools to identify your precise location. 1.6 Communications If you communicate through our Services, we learn about that. We collect information about you when you communicate with others through our Services (e.g., when you send, receive, or engage with messages, events, or connection requests, including our marketing communications). This may include information that indicates who you are communicating with and when. We also use automated systems to support and protect our site. For example, we use such systems to suggest possible responses to messages and to manage or block content that violates our User Agreement or Professional Community Policies . 1.7 Workplace and School Provided Information When your organization (e.g., employer or school) buys a premium Service for you to use, they give us data about you. Others buying our Services for your use, such as your employer or your school, provide us with personal data about you and your eligibility to use the Services that they purchase for use by their workers, students or alumni. For example, we will get contact information for “ LinkedIn Page ” (formerly Company Page) administrators and for authorizing users of our premium Services, such as our recruiting, sales or learning products. 1.8 Sites and Services of Others We get data when you visit sites that include our ads, cookies or plugins or when you log-in to others’ services with your LinkedIn account. We receive information about your visits and interaction with services provided by others when you log-in with LinkedIn or visit others’ services that include some of our plugins (such as “Apply with LinkedIn”) or our ads, cookies or similar technologies. 1.9 Other We are improving our Services, which means we get new data and create new ways to use data. Our Services are dynamic, and we often introduce new features, which may require the collection of new information. If we collect materially different personal data or materially change how we collect, use or share your data, we will notify you and may also modify this Privacy Policy. Key Terms Affiliates Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., GitHub, Inc.). 2. How We Use Your Data We use your data to provide, support, personalize and develop our Services. How we use your personal data will depend on which Services you use, how you use those Services and the choices you make in your settings . We may use your personal data to improve, develop, and provide products and Services, develop and train artificial intelligence (AI) models, develop, provide, and personalize our Services, and gain insights with the help of AI, automated systems, and inferences, so that our Services can be more relevant and useful to you and others. You can review LinkedIn's Responsible AI principles here and learn more about our approach to generative AI here . Learn more about the inferences we may make, including as to your age and gender and how we use them. 2.1 Services Our Services help you connect with others, find and be found for work and business opportunities, stay informed, get training and be more productive. We use your data to authorize access to our Services and honor your settings. Stay Connected Our Services allow you to stay in touch and up to date with colleagues, partners, clients, and other professional contacts. To do so, you can “connect” with the professionals who you choose, and who also wish to “connect” with you. Subject to your and their settings , when you connect with other Members, you will be able to search each others’ connections in order to exchange professional opportunities. We use data about you (such as your profile, profiles you have viewed or data provided through address book uploads or partner integrations) to help others find your profile, suggest connections for you and others (e.g. Members who share your contacts or job experiences) and enable you to invite others to become a Member and connect with you. You can also opt-in to allow us to use your precise location or proximity to others for certain tasks (e.g. to suggest other nearby Members for you to connect with, calculate the commute to a new job, or notify your connections that you are at a professional event). It is your choice whether to invite someone to our Services, send a connection request, or allow another Member to become your connection. When you invite someone to connect with you, your invitation will include your network and basic profile information (e.g., name, profile photo, job title, region). We will send invitation reminders to the person you invited. You can choose whether or not to share your own list of connections with your connections. Visitors have choices about how we use their data. Stay Informed Our Services allow you to stay informed about news, events and ideas regarding professional topics you care about, and from professionals you respect. Our Services also allow you to improve your professional skills, or learn new ones. We use the data we have about you (e.g., data you provide, data we collect from your engagement with our Services and inferences we make from the data we have about you), to personalize our Services for you, such as by recommending or ranking relevant content and conversations on our Services. We also use the data we have about you to suggest skills you could add to your profile and skills that you might need to pursue your next opportunity. So, if you let us know that you are interested in a new skill (e.g., by watching a learning video), we will use this information to personalize content in your feed, suggest that you follow certain Members on our site, or suggest related learning content to help you towards that new skill. We use your content, activity and other data, including your name and photo, to provide notices to your network and others. For example, subject to your settings , we may notify others that you have updated your profile, posted content, took a social action , used a feature, made new connections or were mentioned in the news . Career Our Services allow you to explore careers, evaluate educational opportunities, and seek out, and be found for, career opportunities. Your profile can be found by those looking to hire (for a job or a specific task ) or be hired by you. We will use your data to recommend jobs and show you and others relevant professional contacts (e.g., who work at a company, in an industry, function or location or have certain skills and connections). You can signal that you are interested in changing jobs and share information with recruiters. We will use your data to recommend jobs to you and you to recruiters. We may use automated systems to provide content and recommendations to help make our Services more relevant to our Members, Visitors and customers. Keeping your profile accurate and up-to-date may help you better connect to others and to opportunities through our Services. Productivity Our Services allow you to collaborate with colleagues, search for potential clients, customers, partners and others to do business with. Our Services allow you to communicate with other Members and schedule and prepare meetings with them. If your settings allow, we scan messages to provide “bots” or similar tools that facilitate tasks such as scheduling meetings, drafting responses, summarizing messages or recommending next steps. Learn more . 2.2 Premium Services Our premium Services help paying users to search for and contact Members through our Services, such as searching for and contacting job candidates, sales leads and co-workers, manage talent and promote content. We sell premium Services that provide our customers and subscribers with customized-search functionality and tools (including messaging and activity alerts) as part of our talent, marketing and sales solutions. Customers can export limited information from your profile, such as name, headline, current company, current title, and general location (e.g., Dublin), such as to manage sales leads or talent, unless you opt-out . We do not provide contact information to customers as part of these premium Services without your consent. Premium Services customers can store information they have about you in our premium Services, such as a resume or contact information or sales history. The data stored about you by these customers is subject to the policies of those customers. Other enterprise Services and features that use your data include TeamLink and LinkedIn Pages (e.g., content analytics and followers). 2.3 Communications We contact you and enable communications between Members. We offer settings to control what messages you receive and how often you receive some types of messages. We will contact you through email, mobile phone, notices posted on our websites or apps, messages to your LinkedIn inbox, and other ways through our Services, including text messages and push notifications. We will send you messages about the availability of our Services, security, or other service-related issues. We also send messages about how to use our Services, network updates, reminders, job suggestions and promotional messages from us and our partners. You may change your communication preferences at any time. Please be aware that you cannot opt out of receiving service messages from us, including security and legal notices. We also enable communications between you and others through our Services, including for example invitations , InMail , groups and messages between connections. 2.4 Advertising We serve you tailored ads both on and off our Services. We offer you choices regarding personalized ads, but you cannot opt-out of seeing non-personalized ads. We target (and measure the performance of) ads to Members, Visitors and others both on and off our Services directly or through a variety of partners, using the following data, whether separately or combined: Data collected by advertising technologies on and off our Services using pixels, ad tags (e.g., when an advertiser installs a LinkedIn tag on their website), cookies, and other device identifiers; Member-provided information (e.g., profile, contact information, title and industry); Data from your use of our Services (e.g., search history, feed, content you read, who you follow or is following you, connections, groups participation, page visits, videos you watch, clicking on an ad, etc.), including as described in Section 1.3; Information from advertising partners , vendors and publishers ; and Information inferred from data described above (e.g., using job titles from a profile to infer industry, seniority, and compensation bracket; using graduation dates to infer age or using first names or pronoun usage to infer gender; using your feed activity to infer your interests; or using device data to recognize you as a Member). Learn more about the inferences we make and how they may be used for advertising. Learn more about the ad technologies we use and our advertising services and partners. You can learn more about our compliance with laws in the Designated Countries or the UK in our European Regional Privacy Notice . We will show you ads called sponsored content which look similar to non-sponsored content, except that they are labeled as advertising (e.g., as “ad” or “sponsored”). If you take a social action (such as like, comment or share) on these ads, your action is associated with your name and viewable by others, including the advertiser. Subject to your settings , if you take a social action on the LinkedIn Services, that action may be mentioned with related ads. For example, when you like a company we may include your name and photo when their sponsored content is shown. Ad Choices You have choices regarding our uses of certain categories of data to show you more relevant ads. Member settings can be found here . For Visitors, the setting is here . Info to Ad Providers We do not share your personal data with any non-Affiliated third-party advertisers or ad networks except for: (i) hashed IDs or device identifiers (to the extent they are personal data in some countries); (ii) with your separate permission (e.g., in a lead generation form) or (iii) data already visible to any users of the Services (e.g., profile). However, if you view or click on an ad on or off our Services, the ad provider will get a signal that someone visited the page that displayed the ad, and they may, through the use of mechanisms such as cookies, determine it is you. Advertising partners can associate personal data collected by the advertiser directly from you with hashed IDs or device identifiers received from us. We seek to contractually require such advertising partners to obtain your explicit, opt-in consent before doing so where legally required, and in such instances, we take steps to ensure that consent has been provided before processing data from them. 2.5 Marketing We promote our Services to you and others. In addition to advertising our Services, we use Members’ data and content for invitations and communications promoting membership and network growth, engagement and our Services, such as by showing your connections that you have used a feature on our Services. 2.6 Developing Services and Research We develop our Services and conduct research Service Development We use data, including public feedback, to conduct research and development for our Services in order to provide you and others with a better, more intuitive and personalized experience, drive membership growth and engagement on our Services, and help connect professionals to each other and to economic opportunity. Other Research We seek to create economic opportunity for Members of the global workforce and to help them be more productive and successful. We use the personal data available to us to research social, economic and workplace trends, such as jobs availability and skills needed for these jobs and policies that help bridge the gap in various industries and geographic areas. In some cases, we work with trusted third parties to perform this research, under controls that are designed to protect your privacy. We may also make public data available to researchers to enable assessment of the safety and legal compliance of our Services. We publish or allow others to publish economic insights, presented as aggregated data rather than personal data. Surveys Polls and surveys are conducted by us and others through our Services. You are not obligated to respond to polls or surveys, and you have choices about the information you provide. You may opt-out of survey invitations. 2.7 Customer Support We use data to help you and fix problems. We use data (which can include your communications) to investigate, respond to and resolve complaints and for Service issues (e.g., bugs). 2.8 Insights That Do Not Identify You We use data to generate insights that do not identify you. We use your data to perform analytics to produce and share insights that do not identify you. For example, we may use your data to generate statistics about our Members, their profession or industry, to calculate ad impressions served or clicked on (e.g., for basic business reporting to support billing and budget management or, subject to your settings , for reports to advertisers who may use them to inform their advertising campaigns), to show Members' information about engagement with a post or LinkedIn Page , to publish visitor demographics for a Service or create demographic workforce insights, or to understand usage of our services. 2.9 Security and Investigations We use data for security, fraud prevention and investigations. We and our Affiliates, including Microsoft, may use your data (including your communications) for security purposes or to prevent or investigate possible fraud or other violations of the law, our User Agreement and/or attempts to harm our Members, Visitors, company, Affiliates, or others. Key Terms Social Action E.g. like, comment, follow, share Partners Partners include ad networks, exchanges and others 3. How We Share Information 3.1 Our Services Any data that you include on your profile and any content you post or social action (e.g., likes, follows, comments, shares) you take on our Services will be seen by others, consistent with your settings. Profile Your profile is fully visible to all Members and customers of our Services. Subject to your settings , it can also be visible to others on or off of our Services (e.g., Visitors to our Services or users of third-party search tools). As detailed in our Help Center , your settings, degree of connection with the viewing Member, the subscriptions they may have, their usage of our Services , access channels and search types (e.g., by name or by keyword) impact the availability of your profile and whether they can view certain fields in your profile. Posts, Likes, Follows, Comments, Messages Our Services allow viewing and sharing information including through posts, likes, follows and comments. When you share an article or a post (e.g., an update, image, video or article) publicly it can be viewed by everyone and re-shared anywhere (subject to your settings ). Members, Visitors and others will be able to find and see your publicly-shared content, including your name (and photo if you have provided one). In a group , posts are visible to others according to group type. For example, posts in private groups are visible to others in the group and posts in public groups are visible publicly. Your membership in groups is public and part of your profile, but you can change visibility in your settings . Any information you share through companies’ or other organizations’ pages on our Services will be viewable by those organizations and others who view those pages' content. When you follow a person or organization, you are visible to others and that “page owner” as a follower. We let senders know when you act on their message, subject to your settings where applicable. Subject to your settings , we let a Member know when you view their profile. We also give you choices about letting organizations know when you've viewed their Page. When you like or re-share or comment on another’s content (including ads), others will be able to view these “social actions” and associate it with you (e.g., your name, profile and photo if you provided it). Your employer can see how you use Services they provided for your work (e.g. as a recruiter or sales agent) and related information. We will not show them your job searches or personal messages. Enterprise Accounts Your employer may offer you access to our enterprise Services such as Recruiter, Sales Navigator, LinkedIn Learning or our advertising Campaign Manager. Your employer can review and manage your use of such enterprise Services. Depending on the enterprise Service, before you use such Service, we will ask for permission to share with your employer relevant data from your profile or use of our non-enterprise Services. For example, users of Sales Navigator will be asked to share their “social selling index”, a score calculated in part based on their personal account activity. We understand that certain activities such as job hunting and personal messages are sensitive, and so we do not share those with your employer unless you choose to share it with them through our Services (for example, by applying for a new position in the same company or mentioning your job hunting in a message to a co-worker through our Services). Subject to your settings , when you use workplace tools and services (e.g., interactive employee directory tools) certain of your data may also be made available to your employer or be connected with information we receive from your employer to enable these tools and services. 3.2 Communication Archival Regulated Members may need to store communications outside of our Service. Some Members (or their employers) need, for legal or professional compliance, to archive their communications and social media activity, and will use services of others to provide these archival services. We enable archiving of messages by and to those Members outside of our Services. For example, a financial advisor needs to archive communications with her clients through our Services in order to maintain her professional financial advisor license. 3.3 Others’ Services You may link your account with others’ services so that they can look up your contacts’ profiles, post your shares on such platforms, or enable you to start conversations with your connections on such platforms. Excerpts from your profile will also appear on the services of others. Subject to your settings , other services may look up your profile. When you opt to link your account with other services, personal data (e.g., your name, title, and company) will become available to them. The sharing and use of that personal data will be described in, or linked to, a consent screen when you opt to link the accounts. For example, you may link your Twitter or WeChat account to share content from our Services into these other services, or your email provider may give you the option to upload your LinkedIn contacts into its own service. Third-party services have their own privacy policies, and you may be giving them permission to use your data in ways we would not. You may revoke the link with such accounts. The information you make available to others in our Services (e.g., information from your profile, your posts, your engagement with the posts, or message to Pages) may be available to them on other services . For example, search tools, mail and calendar applications, or talent and lead managers may show a user limited profile data (subject to your settings ), and social media management tools or other platforms may display your posts. The information retained on these services may not reflect updates you make on LinkedIn. 3.4 Related Services We share your data across our different Services and LinkedIn affiliated entities. We will share your personal data with our Affiliates to provide and develop our Services. For example, we may refer a query to Bing in some instances, such as where you'd benefit from a more up to date response in a chat experience. Subject to our European Regional Privacy Notice , we may also share with our Affiliates, including Microsoft, your (1) publicly-shared content (such as your public LinkedIn posts) to provide or develop their services and (2) personal data to improve, provide or develop their advertising services. Where allowed , we may combine information internally across the different Services covered by this Privacy Policy to help our Services be more relevant and useful to you and others. For example, we may personalize your feed or job recommendations based on your learning history. 3.5 Service Providers We may use others to help us with our Services. We use others to help us provide our Services (e.g., maintenance, analysis, audit, payments, fraud detection, customer support, marketing and development). They will have access to your information (e.g., the contents of a customer support request) as reasonably necessary to perform these tasks on our behalf and are obligated not to disclose or use it for other purposes. If you purchase a Service from us, we may use a payments service provider who may separately collect information about you (e.g., for fraud prevention or to comply with legal obligations). 3.6 Legal Disclosures We may need to share your data when we believe it’s required by law or to help protect the rights and safety of you, us or others. It is possible that we will need to disclose information about you when required by law, subpoena, or other legal process or if we have a good faith belief that disclosure is reasonably necessary to (1) investigate, prevent or take action regarding suspected or actual illegal activities or to assist government enforcement agencies; (2) enforce our agreements with you; (3) investigate and defend ourselves against any third-party claims or allegations; (4) protect the security or integrity of our Services or the products or services of our Affiliates (such as by sharing with companies facing similar threats); or (5) exercise or protect the rights and safety of LinkedIn, our Members, personnel or others. We attempt to notify Members about legal demands for their personal data when appropriate in our judgment, unless prohibited by law or court order or when the request is an emergency. We may dispute such demands when we believe, in our discretion, that the requests are overbroad, vague or lack proper authority, but we do not promise to challenge every demand. To learn more see our Data Request Guidelines and Transparency Report . 3.7 Change in Control or Sale We may share your data when our business is sold to others, but it must continue to be used in accordance with this Privacy Policy. We can also share your personal data as part of a sale, merger or change in control, or in preparation for any of these events. Any other entity which buys us or part of our business will have the right to continue to use your data, but only in the manner set out in this Privacy Policy unless you agree otherwise. 4. Your Choices & Obligations 4.1 Data Retention We keep most of your personal data for as long as your account is open. We generally retain your personal data as long as you keep your account open or as needed to provide you Services. This includes data you or others provided to us and data generated or inferred from your use of our Services. Even if you only use our Services when looking for a new job every few years, we will retain your information and keep your profile open, unless you close your account. In some cases we choose to retain certain information (e.g., insights about Services use) in a depersonalized or aggregated form. 4.2 Rights to Access and Control Your Personal Data You can access or delete your personal data. You have many choices about how your data is collected, used and shared. We provide many choices about the collection, use and sharing of your data, from deleting or correcting data you include in your profile and controlling the visibility of your posts to advertising opt-outs and communication controls. We offer you settings to control and manage the personal data we have about you. For personal data that we have about you, you can: Delete Data : You can ask us to erase or delete all or some of your personal data (e.g., if it is no longer necessary to provide Services to you). Change or Correct Data : You can edit some of your personal data through your account. You can also ask us to change, update or fix your data in certain cases, particularly if it’s inaccurate. Object to, or Limit or Restrict, Use of Data : You can ask us to stop using all or some of your personal data (e.g., if we have no legal right to keep using it) or to limit our use of it (e.g., if your personal data is inaccurate or unlawfully held). Right to Access and/or Take Your Data : You can ask us for a copy of your personal data and can ask for a copy of personal data you provided in machine readable form. Visitors can learn more about how to make these requests here . You may also contact us using the contact information below, and we will consider your request in accordance with applicable laws. Residents in the Designated Countries and the UK , and other regions , may have additional rights under their laws. 4.3 Account Closure We keep some of your data even after you close your account. If you choose to close your LinkedIn account, your personal data will generally stop being visible to others on our Services within 24 hours. We generally delete closed account information within 30 days of account closure, except as noted below. We retain your personal data even after you have closed your account if reasonably necessary to comply with our legal obligations (including law enforcement requests), meet regulatory requirements, resolve disputes, maintain security, prevent fraud and abuse (e.g., if we have restricted your account for breach of our Professional Community Policies ), enforce our User Agreement, or fulfill your request to "unsubscribe" from further messages from us. We will retain de-personalized information after your account has been closed. Information you have shared with others (e.g., through InMail, updates or group posts) will remain visible after you close your account or delete the information from your own profile or mailbox, and we do not control data that other Members have copied out of our Services. Groups content and ratings or review content associated with closed accounts will show an unknown user as the source. Your profile may continue to be displayed in the services of others (e.g., search tools) until they refresh their cache. 5. Other Important Information 5.1. Security We monitor for and try to prevent security breaches. Please use the security features available through our Services. We implement security safeguards designed to protect your data, such as HTTPS. We regularly monitor our systems for possible vulnerabilities and attacks. However, we cannot warrant the security of any information that you send us. There is no guarantee that data may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. 5.2. Cross-Border Data Transfers We store and use your data outside your country. We process data both inside and outside of the United States and rely on legally-provided mechanisms to lawfully transfer data across borders. Learn more . Countries where we process data may have laws which are different from, and potentially not as protective as, the laws of your own country. 5.3 Lawful Bases for Processing We have lawful bases to collect, use and share data about you. You have choices about our use of your data. At any time, you can withdraw consent you have provided by going to settings. We will only collect and process personal data about you where we have lawful bases. Lawful bases include consent (where you have given consent), contract (where processing is necessary for the performance of a contract with you (e.g., to deliver the LinkedIn Services you have requested) and “legitimate interests.” Learn more . Where we rely on your consent to process personal data, you have the right to withdraw or decline your consent at any time and where we rely on legitimate interests, you have the right to object. Learn More . If you have any questions about the lawful bases upon which we collect and use your personal data, please contact our Data Protection Officer here . If you're located in one of the Designated Countries or the UK, you can learn more about our lawful bases for processing in our European Regional Privacy Notice . 5.4. Direct Marketing and Do Not Track Signals Our statements regarding direct marketing and “do not track” signals. We currently do not share personal data with third parties for their direct marketing purposes without your permission. Learn more about this and about our response to “do not track” signals. 5.5. Contact Information You can contact us or use other options to resolve any complaints. If you have questions or complaints regarding this Policy, please first contact LinkedIn online. You can also reach us by physical mail . If contacting us does not resolve your complaint, you have more options . Residents in the Designated Countries and other regions may also have the right to contact our Data Protection Officer here . If this does not resolve your complaint, Residents in the Designated Countries and other regions may have more options under their laws. Key Terms Consent Where we process data based on consent, we will ask for your explicit consent. You may withdraw your consent at any time, but that will not affect the lawfulness of the processing of your personal data prior to such withdrawal. Where we rely on contract, we will ask that you agree to the processing of personal data that is necessary for entering into or performance of your contract with us. We will rely on legitimate interests as a basis for data processing where the processing of your data is not overridden by your interests or fundamental rights and freedoms. LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:29 |
https://www.instagram.com/p/DJCy2XNT5hv/?utm_source=ig_web_button_share_sheet&hl=es | Instagram Close By continuing, you agree to Instagram's Terms of Use and Privacy Policy . Instagram Log In Sign Up Meta About Blog Jobs Help API Privacy Terms Locations Instagram Lite Meta AI Threads Contact Uploading & Non-Users Meta Verified English Down chevron icon Afrikaans العربية Čeština Dansk Deutsch Ελληνικά English English (UK) Español (España) Español فارسی Suomi Français עברית Bahasa Indonesia Italiano 日本語 한국어 Bahasa Melayu Norsk Nederlands Polski Português (Brasil) Português (Portugal) Русский Svenska ภาษาไทย Filipino Türkçe 中文(简体) 中文(台灣) বাংলা ગુજરાતી हिन्दी Hrvatski Magyar ಕನ್ನಡ മലയാളം मराठी नेपाली ਪੰਜਾਬੀ සිංහල Slovenčina தமிழ் తెలుగు اردو Tiếng Việt 中文(香港) Български Français (Canada) Română Српски Українська © 2026 Instagram from Meta | 2026-01-13T08:48:29 |
https://dev.to/axonixtools | Axonix Tools - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Axonix Tools Professional, free, and privacy-focused web tools for developers, designers, and daily productivity. Joined Joined on Jan 12, 2026 Personal website https://axonixtools.com/ github website twitter website More info about @axonixtools Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 1 post published Comment 1 comment written Tag 0 tags followed I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently Axonix Tools Axonix Tools Axonix Tools Follow Jan 12 I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently # showdev # learning # productivity # webdev 3 reactions Comments 1 comment 2 min read Want to connect with Axonix Tools? Create an account to connect with Axonix Tools. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://stackoverflowteams.com/teams/create/free/?utm_medium=referral&utm_source=stackoverflow-community&utm_campaign=side-bar&utm_content=explore-teams#content | Stack Internal - Create Profile Skip to main content Get started Collaborate, connect, and grow your team’s wisdom Free plan Free knowledge sharing and collaboration platform No credit card required Free for up to 50 members Save and share information with your whole team Search for answers when you need them most Sign up with Google Sign up with GitHub Work email Must contain 8+ characters, including at least 1 letter and 1 number. Password Submit Opt-in to receive occasional product updates, user research invitations, company announcements, and digests. We know you hate spam, and we do too. That’s why we make it easy for you to update your email preferences or unsubscribe at anytime. We never share your email address with third parties for marketing purposes. Sign up Already have an account? Log in Used by thousands of organizations around the globe | 2026-01-13T08:48:29 |
https://aws.amazon.com/security/?nc1=f_cc | Cloud Security – Amazon Web Services (AWS) Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Cloud Security Security Services Use Cases Compliance Data Protection Blog More AWS Cloud Security › AWS Cloud Security Proven security to accelerate innovation Learn about our culture of security Move fast, stay secure Strong security at the core of an organization enables digital transformation and innovation. AWS helps organizations to develop and evolve security, identity, and compliance into key business enablers. At AWS, security is our top priority . AWS is architected to be the most secure global cloud infrastructure on which to build, migrate, and manage applications and workloads. This is backed by the trust of our millions of customers, including the most security sensitive organizations like government, healthcare, and financial services. Play Benefits Architected to be the most secure cloud infrastructure Build, run, and scale your applications on infrastructure architected to be the most secure cloud computing environment available today. As organizations migrate and build on cloud, they need assurance that they have a secure foundation. AWS has the most proven operational experience of any cloud provider. Our cloud infrastructure is highly trusted and secure-by-design, giving customers the confidence to accelerate innovation. Security automation that drives speed and agility Move fast and stay secure by confidently integrating and automating security into every part of your organization. Building securely should be the path of least resistance – with no tradeoff between security with speed. With security automation, teams spend their limited time on the highest value tasks, reduce human error, and scale security best practices across the organization. End-to-end security and guidance Innovate with a wide portfolio of security services and partner solutions to help achieve end-to-end security for your organization. Organizations require powerful capabilities, designed and built by experts, which encode years of experience, knowledge and best practices, all available at their fingertips. They don’t want to navigate this changing threat and compliance landscape alone. Strategic Security AWS is your guide in understanding and executing best practices to manage and reduce security risk, and protect your networks and data. Built by experts, AWS security, identity, and compliance services give you the confidence to keep building and innovating. Identify Understand and manage risk with deep visibility and automation. Prevent Define user permissions and identities, infrastructure protection and data protection measures for a smooth and planned AWS adoption strategy. Detect Gain visibility into your organization’s security posture with logging and monitoring services. Ingest this information into a scalable platform for event management, testing, and auditing. Respond Automated incident response and recovery to help shift the primary focus of security teams from response to analyzing root cause. Remediate Leverage event driven automation to quickly remediate and secure your AWS environment in near real-time. Partners APN Partners offer hundreds of industry-leading security solutions that help customers improve their security and compliance. The scalability, visibility, and affordability our partners inherit with the cloud enables them to create world-class offerings for customers. Learn about products and solutions pre-qualified by the AWS Partner Competency Program to support you in multiple areas, including: infrastructure security, policy management, identity management, security monitoring, vulnerability management, data protection, and consulting services. These products complement existing AWS services to help you deploy a comprehensive security architecture and a more seamless experience across your cloud and on-premises environments. To learn more about the NIST framework and our Cybersecurity Partners, click here . In addition, refer to our Security Solutions in AWS Marketplace for a broad selection of security offerings from hundreds of independent software vendors. Learning Browse resources to learn more about cloud security. Learn more Report Building Cloud Trust How trust and security are shaping the next phase of cloud growth Read the report Training AWS Security Fundamentals Learn fundamental AWS cloud security concepts, including AWS access control, data encryption methods, and how network access to your AWS infrastructure can be secured. AWS Training Course Guidance AWS Security Reference Architecture Design, implement, and manage AWS security services so that they align with AWS recommended practices. AWS Prescriptive Guidance What's new in Security, Identity, & Compliance? Loading Loading Loading Loading Loading AWS Security, Identity, & Compliance Events Loading Loading Loading Loading Loading Found something suspicious? Learn about our practice for addressing potential vulnerabilities in any aspect of our cloud services. Report vulnerabilities Learn more Report suspicious emails Notify us Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:29 |
https://developer.x.com/developer-terms/policy#4-b | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:29 |
https://dev.to/michelle | Michelle Marcelline - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Michelle Marcelline I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Joined Joined on Jun 19, 2020 twitter website Work Co-Founder at The Prompting Company Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close More info about @michelle Organizations Cotter Post 4 posts published Comment 5 comments written Tag 0 tags followed Pin Pinned LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End Michelle Marcelline Michelle Marcelline Michelle Marcelline Follow for Cotter Jul 21 '20 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # javascript # webdev 754 reactions Comments 46 comments 7 min read OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Michelle Marcelline Michelle Marcelline Michelle Marcelline Follow for Cotter Aug 4 '20 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 68 reactions Comments Add Comment 8 min read Want to connect with Michelle Marcelline? Create an account to connect with Michelle Marcelline. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in What is WebAuthn: Logging in with Face ID and Touch ID on the web Michelle Marcelline Michelle Marcelline Michelle Marcelline Follow for Cotter Jul 28 '20 What is WebAuthn: Logging in with Face ID and Touch ID on the web # javascript # react # authentication # tutorial 70 reactions Comments 1 comment 7 min read What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site Michelle Marcelline Michelle Marcelline Michelle Marcelline Follow for Cotter Jul 14 '20 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site # security # javascript # webdev # oauth 155 reactions Comments Add Comment 7 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://dev.to/ajtiti/ajtiti-36-o-roli-team-leada-2-2#main-content | AjTiTi #36 - O roli Team Leada (2/2) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close AjTiTi [PL] Follow AjTiTi #36 - O roli Team Leada (2/2) Mar 4 '22 play Ostatnio było trochę o tym kim jest Team Lead i jaka jest jego rola. Tym razem rozmawiamy sobie w jaki sposób Team Lead może zarządzać zespołem oraz wypełniać powierzone mu zadania w sposób efektywny. Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://twitter.com/alfrodo_perez | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:29 |
https://developer.x.com/developer-terms/agreement#SVGID_1_ | Developer Agreement – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Agreement X Developer Agreement Last Updated: October 17, 2025 By clicking “Accept & Subscribe”, continuing to pay the recurring subscription fee for Paid Services, or by otherwise accessing or using any Licensed Material, you agree to the terms of our Agreement. Subscriptions auto-renew until canceled, as described below. A verified phone number is required to subscribe. If you've subscribed through another platform, manage your subscription through that platform. This X Developer Agreement (“ Agreement ”) is a binding legal agreement between you (referred to in this Agreement as “ you ”) and X and governs your access to and use of the Licensed Material (defined below), including any Paid Services (defined below). By accessing or using any Licensed Material (defined below), or clicking on a button to accept the terms of this Agreement or recurring subscription payment for Paid Services, you agree to be bound by the terms of this Agreement. If you do not understand the terms herein or do not accept any part of them, then you may not use or access any Licensed Material. You may not use the Licensed Material or accept this Agreement if you are not of legal age to form a binding contract with X or if you are barred from using or receiving the Licensed Material under applicable law. To purchase and use a Paid Service you must: (i) be at least 18 years old or the age of majority as determined by the laws of the jurisdiction in which you live or (ii) have the express consent of your parent or guardian to purchase and use that Paid Service. If you are a parent or legal guardian and you allow your child (or a child that you are a guardian of) to purchase or use a Paid Service, you agree that the terms of this Agreement apply to you, you will abide by this Agreement, and you are responsible for the child’s activity on the Paid Services and for ensuring that the child also abides by the terms of this Agreement. In any case, as stated in the Who May Use the Services section of the X Terms of Service , you must be at least 13 years old to use the "Services" as defined in the X Terms of Service. If you are accepting this Agreement or using the Licensed Material on behalf of a company, organization, government, or other legal entity, you represent and warrant that you have the authority to bind such company, organization, government, or other legal entity to this Agreement, in which case the words “you” and “your” as used in this Agreement shall refer to such entity. If you do not agree to the terms of this Agreement, you may not (and you may not allow any of your personnel to) access or use the Licensed Material. I. Definitions. In this Agreement, the following definitions apply: 1. “ Developer Site ” means X’s developer site located at https://developer.x.com 2. “ Direct Message ” means a private message that is sent on X Applications by one user to one or more other specific user(s) using X’s direct messaging function. 3. “ Intellectual Property Rights ” means all copyrights, moral rights, patent rights, trademarks, and any other intellectual property or similar rights (registered or unregistered) throughout the world. 4. “ Licensed Material ” means, individually or collectively, the X API and X Content. 5. " Paid Service(s) ” means features or functionality of the Licensed Material that you access in exchange for payment of a recurring fee, as applicable to the relevant features or functionality and this Agreement. Unless otherwise set forth in this Agreement, all references to “Licensed Material” are intended to include the Paid Service(s). 6. “ Payment Portal ” means the online portal made available to you to opt-in to your use of the Licensed Material, manage subscriptions for Paid Services, manage payment methods for Paid Services, and update account information. 7. “ Services ” means your services, websites, applications, and other offerings (including research) that display X Content or otherwise use the Licensed Material. 8. “ Post ” means a short-form text and multimedia-based message distributed via the X Applications. 9. “ X ” means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. 10. “ X API ” means X Application Programming Interfaces (each, an “API” ), Software Development Kits (each, an “SDK” ), and the related tools, documentation, data, technology, code, and other materials provided by X through the Developer Site. 11. “ X Applications ” means X’s real-time information service, commonly referred to as “X,” which includes those services currently provided by X at its websites and X-owned, operated, or controlled mobile applications, social plug-ins, and application programming interfaces. 12. “ X Content ” means Posts, the unique identification number generated for each Post, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. 13. “X Marks ” means the X name, trademarks, and logos that X makes available to you, including via the Developer Site, solely for use in accordance with this Agreement. 14. “ Users ” means visitors, users, or customers of your Services. II. X API and X Content. A. License from X. Subject to your compliance with the terms of this Agreement and the applicable Incorporated Developer Terms (as defined below), X hereby grants you a non-exclusive, royalty free, non-transferable, non-sublicensable, and revocable license to solely: 1. Use the X API to integrate X Content into your Services or conduct analysis of the X Content, as explicitly approved by X; 2. Copy a reasonable amount of and display the X Content on and through your Services to Users, as permitted by this Agreement; 3 . Modify X Content only to format it for display on your Services; and 4. Use and display X Marks to attribute X Applications as the source of the X Content, as set forth in this Agreement. B. License to X. You hereby grant X a non-exclusive, royalty free, non-transferable, and non-sublicensable revocable license to access, index, and cache by any means, including web spiders and/or crawlers, any webpage or applications on which you display X Content using embedded Posts or embedded timelines . C. Incorporated Terms. Your access to and use of the Licensed Material is also subject to, and you shall comply with, the following additional terms and policies (collectively, “ Incorporated Developer Terms ”): 1. the X Developer Policy ; 2. the API Restricted Use Rules ; 3. the X Rules ; 4. as it relates to your display of any of the X Content, the Display Requirements ; 5. as it relates to your use and display of the X Marks, the X Brand Guidelines ; and 6. as it relates to taking automated actions on your account, the Automation Rules . III. Restrictions on Use. A. Reverse Engineering and other Restrictions. You shall not and you shall not attempt to (or allow others to): (a) reverse engineer, decompile, disassemble, or translate the X API or otherwise attempt to derive source code, trade secrets, or know-how in or underlying any X API or any portion thereof; (b) interfere with, modify, disrupt, or disable features or functionality of the X API or monitoring mechanisms of the X API; (c) use or access the Licensed Material to create or attempt to create a substitute or similar service or product to the X Applications; (d) sell, rent, lease, sublicense, distribute, redistribute, syndicate, create derivative works of, assign, or otherwise transfer or provide access to, in whole or in part, the Licensed Material to any third party except as expressly permitted in this Agreement; (e) provide use of the X API on a service bureau, rental or managed services basis, or permit other individuals or entities to create links to the X API or "frame" or "mirror" the X API on any other server, or wireless or Internet-based device, or otherwise make available to a third party any token, key, password, or other login credentials to the X API; (f) use the Licensed Material for any illegal, unauthorized, or other improper purpose; (g) use the Licensed Material to derive or obtain non-public information of individual X users; (h) interfere with or disrupt the integrity or performance of the X Applications, X API, or X Content contained therein; (i) remove or alter any proprietary notices or marks on the X Content; (j) attempt to gain unauthorized access to the X Applications, X API, X Content, or related systems or networks; (k) use the X API or X Content to fine-tune or train a foundation or frontier model; or (l) use X Content, by itself or bundled with third party data, or derivative analysis therefrom, to target or serve users with advertising outside of the X Applications. B. Commercial Use Restrictions. If your Services are designated as ‘non-commercial,’ you shall not make Commercial Use (as defined below) of the Licensed Material. Commercial Use restrictions may not apply to officially registered non-profits or NGOs. “Commercial Use” means any use of the Licensed Material or access to the X API: (a) by or for a business (i.e. an entity whose primary purpose is to earn revenue through a product or service), or (b) as part of a product or service that is monetized (e.g., website advertising, licensing fees, in-app promotions, and sponsorships). C. No Monitoring or Measuring. Notwithstanding anything to the contrary, you may use the following information only for non-commercial, internal purposes (e.g., to improve the functionality of the Services): (a) aggregate X Applications user metrics, such as number of active users or accounts on X Applications; (b) the responsiveness of X Applications; and (c) results, usage statistics, data, or other information (in the aggregate or otherwise) derived from analyzing, using, or regarding the performance of the X API. All such information is Confidential Information (as defined below). D. Rate Limits. You will not attempt to exceed or circumvent limitations on access, calls, and use of the X API (" Rate Limits ") or otherwise use the X API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise does not comply with this Agreement. If you exceed or X reasonably believes that you have attempted to circumvent Rate Limits, controls to limit use of the X APIs, or the terms of this Agreement, then your ability to use the Licensed Material may be temporarily suspended or permanently blocked. X may monitor your use of the X API to improve the Licensed Material and X Applications and to ensure your compliance with this Agreement and the Incorporated Developer Terms. E. Location Data. You shall not, and you shall not allow others to, aggregate, cache, or store location data and other geographic information contained in the X Content except in conjunction with the X Content to which it is attached. You may only use location data and geographic information to identify the location tagged by the X Content. F. Use of X Marks. You shall not include any of the X Marks in your registered corporate name(s), your logos, or your service or product names. You shall not create any derivative works of the X Marks or use the X Marks in a manner that creates or reasonably implies an endorsement, sponsorship, or association with X. All use of the X Marks and all goodwill arising out of the use will inure to X's benefit. You will not remove or alter any proprietary notices or X Marks on the Licensed Material. G. Security. You will maintain the security of the X API and will not make available to any third party any token, key, password, or other login credentials to the X API. You will use industry standard security measures to prevent unauthorized access or use of any of the features and functionality of the X API, including access by viruses, worms, or any other harmful code or material. You shall keep X Content confidential and secure from unauthorized access by using industry-standard organizational and technical safeguards for such data, and with no less care than you use in connection with securing similar data you store. You will immediately notify X, consult and cooperate with investigations, assist with any required notices, and provide any information reasonably requested by X if you know of or suspect any breach of security or potential vulnerability related to the Licensed Material. You will promptly remedy such breach or potential vulnerability resulting from your access to the Licensed Material. H. Digital Services Act . Notwithstanding anything to the contrary in this Agreement, to the extent you are provided access to the Licensed Material pursuant to the procedures described in Article 40 of the Digital Services Act (Regulation (EU) 2022/2065) (“DSA”), your access and use of the Licensed Material is limited solely to performing research that contributes to the detection, identification, and understanding of systemic risks in the European Union and only to the extent necessary for X to comply with its obligations under the DSA. Any such use of the Licensed Material is non-commercial as described in Section III(B) of this Agreement. You may not disclose, reproduce, license, or otherwise distribute the Licensed Material (including any derivatives thereof) that you retrieve through the X API to any person or entity outside the persons specified within your approved application unless (i) the information is disclosed to the Digital Services Coordinator or other party specifically permitted by the DSA pursuant to the “vetted researcher” status and procedures described in Article 40, or (ii) disclosure is required by law. I. Tokens. X may limit the number of tokens that it provides to you, including but not limited to tokens that enable access and use of functionality or features on X Applications. J. Access Tiers. X provides different tiers of access (as described at developer.x.com/en ) to the Licensed Material, and you shall subscribe to the tier that best fits your use case. X may, at any time, review your use of its Licensed Materials and require a change in the access tier to which you are subscribed, including but not limited to, application for Enterprise access (as described at developer.x.com/en ). K. Prohibition on I-Framing: You shall not, under any circumstances, embed, display, or otherwise incorporate any Licensed Material, X Content, X API, or elements of the X Applications within an iframe, inline frame, or any similar embedding mechanism on your Services or any other platform. This prohibition is absolute and includes, but is not limited to, attempts to frame X Content for display, integration, or redistribution purposes. Violation of this clause may result in immediate termination of your Developer Agreement and your access to the Licensed Material (e.g., X API, X Data License, Developer Portal) as outlined in Section VII.I. IV. Updates and Removals. A. Updates. X may update, modify or discontinue any features or function of the Licensed Material, in whole or in part, from time to time (in each instance, an “Update” ). You shall implement and use the most current version of the Licensed Material and make any changes to your Services that are required as a result of the Update, at your sole expense. Updates may adversely affect the way your Services access or communicate with the X API or display X Content. X will not be liable for damages of any sort that result from any Update. B. Removals. If X Content is deleted, gains protected status, or is otherwise suspended, withheld, modified, or removed from the X Applications (including removal of location information), you will make all reasonable efforts to delete or modify that X Content (as applicable) as soon as possible, and in any case within twenty four (24) hours after a written request to do so by X or by an X user with regard to its X Content unless prohibited by law or regulation and with the express written permission of X. V. Ownership, Betas, and Feedback. A. Ownership. Except to the extent expressly stated otherwise in this Agreement, neither party will acquire any right, title, or interest in any Intellectual Property Rights owned or licensed by the other party. The Licensed Material is licensed, not sold, and X (or its licensors or X Application users, as applicable) retains and reserves all rights, including all Intellectual Property Rights, not expressly granted in this Agreement. You shall not do anything inconsistent with X’s ownership, including without limitation, challenging X’s ownership of the X Marks, challenging the validity of the licenses granted in this Agreement, or otherwise copying or exploiting the X Marks except as specifically authorized in this Agreement. If you acquire any rights in the X Marks or any confusingly similar marks, by operation of law or otherwise, you will, at no expense to X, immediately assign those rights to X. B. Betas. X may provide you with early access to non-generally available alphas, betas, research studies, pilots, marketing services, or other programs from time to time (each, a “ Beta ”). Betas will be considered Confidential Information. Your participation in any Beta is at your own risk, may be subject to additional requirements, and may assist X in research, analyzing, and validating existing or prospective programs, products and/or tools. C. Feedback. X will be free to use any feedback, comments, or suggestions you provide X related to X, the Licensed Material, Betas, or any other of X’s products or services (“ Feedback ”) in any way without any compensation or obligation to you or any third party and Feedback will be deemed Confidential Information. You hereby irrevocably assign to X all right, title, and interest to Feedback. VI. Confidentiality. You may be given access to non-public information, software, and specifications relating to the Licensed Material (“ Confidential Information ”). You may use Confidential Information only as necessary in exercising your rights under this Agreement. You shall not disclose Confidential Information to any third party without X’s prior written consent. You shall protect Confidential Information from unauthorized use, access, or disclosure in the same manner that you would use to protect your own confidential information of a similar nature and in no event with less than a reasonable degree of care. VII. Term; Subscription Fees; Payment; Suspension, and Termination. A. Term. The term of this Agreement will start on the date (i) you accept the terms herein or (ii) start accessing or using any of the Licensed Material, whichever is earlier, and will continue until you stop accessing and using the Licensed Material unless terminated earlier as described below. B. Subscription Terms. Paid Services provided as part of the Licensed Material are made available as a recurring subscription service that provides access to certain features, benefits, or services, as described on the Developer Site and the Payment Portal. If you purchase a Paid Service, you do so by paying a subscription fee in advance on a monthly basis in accordance with the payment terms set forth below. When you subscribe to access the Paid Service(s) via the Payment Portal, you expressly agree that you are authorizing recurring payments and that payments will be made by the payment method you have selected until the applicable Paid Service is canceled by you or by X or this Agreement is otherwise terminated. Your subscription to the Paid Service will automatically renew monthly until canceled in accordance with this Agreement. Your payment information will be automatically processed by the Payment Processor (as defined below) at the start of each subscription period applicable to the Paid Service(s). If your payment information is declined, your subscription may be canceled until you provide new payment information for the applicable Paid Service(s). If you provide new payment information and your payment account is successfully charged, your new subscription period will be based on the original renewal date and not the date the successful charge took place. Prices for Paid Services are subject to change from time to time. X will provide reasonable advance notice of any material change to the price of Paid Services, which notice may be provided via the Developer Site. For subscription fees, price changes will take effect at the start of the next subscription period following the date of the price change. If you do not agree with a price change, you have the right to reject the change by canceling your subscription to the applicable Paid Service(s) prior to the price change going into effect. C. Payment Terms. X may offer payment options that vary by Paid Service, device, operating system, geographic location, or other factors, which may be updated from time to time. These payment options may include web payments using a third party payment processor (“ Payment Processor ”). When you access a Paid Service, you agree: (i) to pay the price listed for the Paid Service, along with any additional amounts relating to applicable taxes, surcharges, credit card fees, bank fees, foreign transaction fees, foreign exchange fees, and currency fluctuations, on a recurring basis during the applicable subscription period; and (ii) to abide by any applicable terms of service, privacy policies, or other legal agreements or restrictions (including additional age restrictions) imposed by the Payment Processor in connection with your use of a given payment method. The subscription fee will automatically be applied at the start of the renewal period for the applicable subscription period unless you cancel the Paid Service(s) on the Developer Site. It is your responsibility to make sure your banking, credit card, debit card, and/or other payment information is up to date, complete, and accurate at all times. If you make a payment for a Paid Service through a Payment Processor, X may receive information about your transaction such as when it was made, when a subscription is set to expire or auto- renew, what platform you made the purchase on, and other information. X will not be liable for any errors made or delays by the Payment Processor, your bank, your credit card company, or any payment network. All payments to X are non-refundable except as otherwise expressly provided in this Agreement or as required by law. D. Taxes and fees. All fees exclude any and all taxes and similar fees now in force, enacted, or imposed in the future on the transaction, delivery of the Licensed Material, or the delivery of the X Content including any sales, use or value added taxes, goods and services tax, consumption tax, customs duties, tariffs, or similar charges. These taxes may include but are not limited to, VAT, GST, sales tax, withholding tax, and any other applicable taxes but exclude taxes solely based on X’s net income. You are responsible for the payment of all such taxes, duties, and charges and any related penalties and interest arising from the payment of such amounts. In addition, a surcharge may be charged to recover costs associated with Digital Services Tax ("DST") or similar jurisdiction-specific taxes or regulatory fees incurred by X in certain jurisdictions. This surcharge will appear as a separate line item on your invoice, where applicable, and will be calculated as a percentage of applicable charges as determined by X in its sole discretion. X may adjust this surcharge at any time, without prior notice, in response to increased tax or fee rates or related administrative costs. Depending on your location, X may be responsible for collecting and reporting information related to transaction taxes arising from your purchase of Paid Services. You grant X permission to provide your account and personal information to relevant tax authorities to fulfill our tax collection and reporting obligations. E. Canceling Your Subscription for Paid Services. Your subscription for Paid Services will automatically renew monthly unless you cancel your subscription at least 24 hours before the end of your current subscription period. There are no refunds or credits for any partial subscription periods, including in a situation where certain features, benefits, and/or services are modified or discontinued. SUBSCRIPTION PLANS ARE PREPAID, NON-REFUNDABLE (UNLESS REQUIRED BY LAW), AND AUTOMATICALLY RENEW AT THE END OF EACH SUBSCRIPTION PERIOD UNLESS THE SUBSCRIPTION IS CANCELED FOLLOWING THE CANCELLATION PROCEDURES HEREIN. You may cancel your subscription for Paid Services at any time via the Developer Site and you will no longer have access to the Paid Services (or any features or functionality thereof) at the end of your then-current subscription term. When you cancel the Paid Services, your subscription will remain active from the time you cancel until the end of your current subscription period. You will not receive a refund or credit for any remaining days in your current subscription period unless required by law. All payments for Paid Services are final and not refundable or exchangeable except as required by applicable law. X makes no guarantee as to the nature, quality, or value of a Paid Service or the availability or supply thereof. Refunds or credits are not provided for any unused or partially used Paid Service (for example, a partially used subscription period). All transactions are final unless you have a right to withdraw pursuant to law, such as provided below . 1. Withdrawal Right & Refunds for Users Living in EU or UK. When you purchase any Paid Services on subscription, you expressly agree to do so on a subscription basis and that the subscription will commence immediately on your date of purchase. If you are a consumer in an EU Member State or the UK, you agree you have fourteen (14) days after your purchase to withdraw from your contract for purchase for any reason. 2. No Withdrawal Right for Users Living in Taiwan. When you purchase Paid Services, you do so on a subscription basis, the subscription will commence immediately on your date of purchase, and the Paid Service is fully performed once started. If you are a consumer in Taiwan, you agree that you can cancel your subscription for any Paid Services in accordance with Section VII.E above, but that there is otherwise no right to rescind your subscription and no refund will be issued. F. Paid Services Are Non-Transferable between X Accounts. Each purchase of a Paid Service applies to a single X account, meaning that your purchase will apply solely to the account you were using when you purchased the Paid Service and will not apply to other accounts that you may have access to or control over. If you have or control multiple accounts and you want access to Paid Services on each account, you must purchase the Paid Service on each account individually. You may not allow others to use your X account to access any Licensed Material that such person did not order. You may not purchase a Paid Service or use any Licensed Material if you are a person with whom U.S. persons are not permitted to have dealings pursuant to economic sanctions, including, without limitation, sanctions administered by the United States Department of the Treasury's Office of Foreign Assets Control or any other applicable sanctions authority (" Prohibited Person "). This includes, without limitation, persons located in, a citizen of, or ordinarily resident in the following countries and regions: Cuba, Iran, the Crimea Region of Ukraine, North Korea and Syria. You represent and warrant that you are not a Prohibited Person. G. Restrictions and Obligations. You may only purchase and use a Paid Service or use the Licensed Material if you are legally allowed to use the Licensed Material in your country and you live in a country supported by X for the applicable Paid Service or Licensed Material. X may, in its discretion, restrict the ability to access the Licensed Material or purchase a Paid Service in certain countries. X reserves the right to modify the list of supported countries from time to time. X reserves the right to refuse Paid Services transactions or to cancel or discontinue the sale or use of a Paid Service or the use of any Licensed Material in its sole discretion. H. Suspension. X may suspend your use of and access to the Licensed Material immediately without notice (a) if X reasonably believes that (i) your use of the Licensed Material would cause damage to, or an inordinate burden upon, the Licensed Material, (ii) you have violated this Agreement, (iii) you create risk or possible legal exposure for X, (iv) X’s provision of the Licensed Material to you is no longer commercially viable; (b) for prolonged inactivity; (c) if X is requested or directed to do so by any competent court of law, regulatory authority, or law enforcement agency; or (d) for failure to pay for the Paid Services. X will not be liable for damages of any sort that result from any such suspension. I. Termination. X may terminate this Agreement for any reason at X’s sole discretion. Except where such early termination is the result of your breach of this Agreement, such early termination by X shall be effective at the end of the then-current subscription period. If you violate the terms of this Agreement, X may terminate this Agreement for cause immediately upon notice to you and you will not receive a prorated refund for any Paid Services. You may cancel your subscription for the Paid Services or your use of the Licensed Material on the Developer Site. Upon termination of this Agreement: (a) all licenses granted in this Agreement immediately expire and you must cease use of any Licensed Material; and (b) you shall permanently delete all Licensed Material in all forms and types of media, and copies thereof, in your possession. Upon the request of X for any reason, you will promptly (and in any event within ten (10) business days of such request) provide evidence (e.g., screenshots of deletion confirmation) of compliance with the provisions of the aforementioned subpart (b) of this Section. The parties to this Agreement will not be liable to each other for any damages resulting solely from termination of this Agreement as permitted under this Agreement. VIII. Compliance Audit. X or a mutually agreed upon third party agent subject to obligations of confidentiality will be entitled to inspect and audit any records related to the performance of this Agreement in your control or possession upon reasonable notice to you, and at a reasonable time during normal business hours, for the purpose of verifying compliance with this Agreement and the fees payable to X for the two (2) year period preceding the audit. X may exercise its audit right no more than once every twelve (12) months unless it has reasonable cause for noncompliance, and such audit shall not unreasonably interfere with your business activities. You will provide your full cooperation and assistance with such audit and provide access to all Licensed Material in your possession, applicable agreements, and records. Without limiting the generality of the foregoing, as part of the audit, X may request, and you agree to provide, a written report, signed by an authorized representative, listing your then-current deployment of the Licensed Material. You will pay X within thirty (30) business days after the completion of the audit the amount of any underpayment revealed by any such audit. In addition, if any such audit reveals an underpayment by you of five percent (5%) or more, then you will also reimburse X for the reasonable costs and expenses of such audit. The requirements of this Section will survive for one (1) year following the termination of this Agreement. IX. Disclaimer. TO THE MAXIMUM EXTENT PERMISSIBLE BY APPLICABLE LAW, THE LICENSED MATERIAL IS PROVIDED TO YOU “AS IS”, “WHERE IS”, WITH ALL FAULTS, AND X DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, AND ANY WARRANTIES OR CONDITIONS ARISING OUT OF THIS AGREEMENT, COURSE OF DEALING OR USAGE OF TRADE. X DOES NOT WARRANT THAT THE LICENSED MATERIAL OR ANY OTHER X PRODUCT OR SERVICE PROVIDED HEREUNDER WILL MEET ANY OF YOUR REQUIREMENTS OR THAT USE OF SUCH LICENSED MATERIAL OR OTHER PRODUCTS OR SERVICES WILL BE ERROR-FREE, UNINTERRUPTED, VIRUS-FREE, OR SECURE. YOU ARE RESPONSIBLE FOR YOUR USE OF THE LICENSED MATERIAL AND ANY CONTENT YOU PROVIDE. THIS DISCLAIMER OF WARRANTY MAY NOT BE VALID IN SOME JURISDICTIONS AND YOU MAY HAVE WARRANTY RIGHTS UNDER LAW WHICH MAY NOT BE WAIVED OR DISCLAIMED. FURTHER YOU UNDERSTAND AND AGREE THAT THE PAID SERVICES ARE PROVIDED TO YOU ON AN “AS IS” AND “AS AVAILABLE” BASIS. X. Indemnification. You shall defend X against any and all proceedings, demands, claims, and suits (including without limitation product liability claims), and indemnify X from any and all liabilities, damages, and costs (including without limitation reasonable attorneys' fees) to the extent arising out of (a) your use of the Licensed Material in any manner that is inconsistent with this Agreement or (b) the performance, promotion, sale, or distribution of your Services. If X seeks indemnification or defense from you under this Section, X will promptly notify you in writing of the claim(s) brought against X for which it seeks indemnification or defense. X may assume full control of the defense of claims with legal counsel of its choice. You shall not enter into any third-party agreement that would affect the rights of X, constitute an admission of fault by X, or bind X in any manner without the prior written consent of X. If X assumes control of the defense of such claim, X shall not settle any such claim requiring payment from you without your prior written approval. XI. Limitation of Liability. IN NO EVENT WILL X BE LIABLE TO YOU OR ANY USERS FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR ANY LOSS OF OR DAMAGE TO USE, DATA, BUSINESS, GOODWILL OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT. IN ANY CASE, X'S AGGREGATE LIABILITY FOR ANY AND ALL CLAIMS UNDER THIS AGREEMENT WILL NOT EXCEED FIFTY DOLLARS ($50.00). THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY REGARDLESS OF WHETHER SUCH LIABILITY ARISES FROM ANY CLAIM BASED UPON CONTRACT, WARRANTY, TORT, STRICT LIABILITY OR OTHERWISE, AND WHETHER OR NOT X HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. IF APPLICABLE LAW PROHIBITS ANY LIMITATION ON LIABILITY HEREIN, THE PARTIES AGREE THAT THE LIMITATION WILL BE DEEMED TO HAVE BEEN MODIFIED TO CONFORM TO APPLICABLE LAW. THE PARTIES AGREE THAT THE LIMITATIONS ON LIABILITIES SET FORTH HEREIN ARE AGREED ALLOCATIONS OF RISK AND SUCH LIMITATIONS WILL APPLY NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. XII. Agreement Updates. X may update or amend this Agreement or any of the Incorporated Developer Terms from time to time. You will check the Developer Site regularly for updates. X will alert you of material revisions to these terms by posting the updated terms on these sites, via a service notification, or by other suitable means (e.g., via email to an email address associated with your account). The changes will not be retroactive and the most current version of this Agreement, available at the Developer Site, will govern your access to and use of the Licensed Material and any corresponding transactions. Your continued access or use of the Licensed Material will constitute binding acceptance of such updates and modifications. XIII. Dispute Resolution and Class Action Waiver. A. THIS SECTION APPLIES TO YOU ONLY IF YOU LIVE OUTSIDE THE EUROPEAN UNION, EFTA STATES, OR THE UNITED KINGDOM, INCLUDING IF YOU LIVE IN THE UNITED STATES. PLEASE READ THIS SECTION CAREFULLY – IT MAY SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING YOUR RIGHT TO FILE A LAWSUIT IN COURT. 1. Choice of Law and Forum Selection. The laws of the State of Texas, excluding its choice of law provisions, will govern this Agreement and any dispute that arises between you and X, notwithstanding any other agreement between the parties to the contrary. All disputes related to this Agreement, including any disputes, claims, or controversies arising out of or relating to this Agreement, the marketing of the Licensed Material, and/or your participation in the Licensed Material will be brought exclusively in the U.S. District Court for the Northern District of Texas or state courts located in Tarrant County, Texas, United States, and you consent to personal jurisdiction in those forums and waive any objection as to inconvenient forum. Without prejudice to the foregoing, you agree that, in its sole discretion, X may bring any claim, cause of action, or dispute it has against you in any competent court in the country in which you reside that has jurisdiction and venue over the claim. If you are a federal, state, or local government entity in the United States using the Licensed Material in your official capacity and legally unable to accept the controlling law, jurisdiction, or venue clauses above, then those clauses do not apply to you. For such U.S. federal government entities, this Agreement and any action related thereto will be governed by the laws of the United States of America (without reference to conflict of laws) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of Texas (excluding choice of law). 2. YOU HAVE ONE YEAR TO BRING A CLAIM AGAINST X. You must bring any claim against X arising out of or related to this Agreement within one (1) year after the date of the occurrence of the event or facts giving rise to the dispute unless applicable law provides that the normal statute of limitations for that claim may not be shortened by agreement. If you do not bring a claim within this period, you forever waive the right to pursue any claim or cause of action, of any kind or character, based on such events or facts, and such claims or causes of action are permanently banned and X will have no liability with respect to such claim. 3. Class Action Waiver. To the extent permitted by law, you also waive the right to participate as a plaintiff or class member in any purported class action, collective action, or representative action proceeding. 4. Changes to this Section. This Dispute Resolution Section survives the end of the relationship between you and X, including cancellation of or unsubscribing from any services or communications provided by X. 5. Injunctive Relief. Notwithstanding the foregoing, you agree that money damages would be an inadequate remedy for X in the event of a breach or threatened breach of this Agreement protecting X's intellectual property or Confidential Information, and that in the event of such a breach or threat, X, in addition to any other remedies to | 2026-01-13T08:48:29 |
https://dev.to/himanshu_bhatt/networking-101-1-networking-introduction-4ip0#comments | Networking 101 #1. Networking Introduction - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Himanshu Bhatt Posted on Jan 13 Networking 101 #1. Networking Introduction # devops # networking # cloud # beginners 👋 Short Intro (Why I’m Writing This) I’m currently learning Networking for DevOps and decided to learn in public by documenting my journey. This blog is part of my Networking 101 series, where I’m learning DevOps step by step from scratch. This series is not written by an expert — it’s a beginner learning out loud, sharing: what I understand, what confuses me, and what I learn along the way. The goal is to build consistency, clarity, and invite discussion. 📌 What This Blog Covers In this post, I’ll cover: 📂 GitHub Repository All my notes, diagrams, and learning resources for this series live here: 👉 GitHub Repo: https://github.com/dmz-v-x/networking-for-devops-101 This repo is updated as I continue learning. 📚 Learning Notes Why should DevOps engineers even care about networking? Let’s start from basics. Most DevOps failures are not code bugs . They look like this: ❌ “The app works locally but not in production” ❌ “The service is running but not reachable” ❌ “502 Bad Gateway” ❌ “Connection refused” ❌ “Request timed out” All of these comes down to one problem that is networking problems . If you don’t understand networking: You won’t know where the problem is You’ll randomly try fixes You’ll depend on someone else to debug This blog series exists to change that — from zero . Goal of this series By the end of this series, you should be able to: Understand how traffic flows from browser → cloud → server Debug basic production networking issues Understand Docker & Kubernetes networking at a high level Read cloud architecture diagrams without fear And i hope you and i we both be able to answer networking related questions in your interview The ONE mental model we must remember Everything in networking can be explained using three boxes : Client (Browser / App) ↓ Network (DNS, Internet, Load Balancer) ↓ Server (VM / Container / App) Enter fullscreen mode Exit fullscreen mode Rule: When something breaks, the problem is always in one of these boxes or the connection between them. We’ll keep coming back to this model in every blog. Before we go further: 3 tiny building blocks You must understand these three things first. Don’t worry — we’ll go slow. 1. DNS — turning names into addresses When you type any url into our browser: For Example: https://example.com Enter fullscreen mode Exit fullscreen mode Your computer does not understand example.com . Computers only understand numbers (IP addresses). 👉 DNS exists to solve this problem. DNS = Name → IP address Means resolving Name(address/url) to IP Address. Example: example.com → 93.184.216.34 Enter fullscreen mode Exit fullscreen mode 📌 Think of DNS like a phone book : You search by name You get a number If DNS breaks, nothing works — even if your server is perfectly fine. 2. IP addresses & Ports — where and what to connect to 2.1 IP Address An IP address identifies a machine on a network . Examples: 192.168.1.10 (private IP) 13.234.56.78 (public IP) Public IP → reachable from the internet Private IP → only reachable inside a private network (like cloud VPCs - Virtual Private Cloud) 2.2 Port A port identifies which application on that machine you want to talk to. Okay, so when we connect to an application, we are actually connecting to an IP address where that application is running. However, this does not mean that only one application can run on a single IP address. But in reality, mulitple application can run on the same IP address , and they are distinguished from each other using different port numbers. Example: Let say we have a server that has an IP: 192.168.1.10 Now on this same IP, we might have: Web app running on port 80 Backend API running on port 3000 Database running on port 5432 So: 192.168.1.10:80 → Web application 192.168.1.10:3000 → Backend service 192.168.1.10:5432 → Database Examples: 22 → SSH 80 → HTTP 443 → HTTPS 5432 → PostgreSQL 📌 IP = which computer 📌 Port = which app on that computer 3. TCP vs UDP — how data is sent This is about rules of communication . 3.1 TCP (most important for DevOps) Reliable Ordered Connection-based Used by: HTTP / HTTPS SSH Databases Think of TCP like a phone call : You connect You talk You hang up 3.2 UDP (less common, but important) Fast No guarantee of delivery No connection Used by: DNS (often) Streaming Some internal systems Think of UDP like shouting messages — fast, but no confirmation. 🛠️ Tiny hands-on demo (run these now) These commands make networking real . 🔍 Check DNS resolution dig google.com +short Enter fullscreen mode Exit fullscreen mode Computers cannot understand domain names. Computers only understand IP addresses like: 93.184.216.34 . So in the above command we are asking a tool called dig (Domain Information Groper) to provide us the IP address of domain: google.com . So finding IP address of a domain name is called as DNS resolution. We run: dig google.com +short We ask the dig tool: Hey DNS, what is the IP address of google.com? The DNS system looks it up and replies with something like: 74.125.68.101 The +short flag means: Don't show technical details, just give me the final answer i.e IP Address. or nslookup example.com Enter fullscreen mode Exit fullscreen mode nslookup means (Name Server Lookup) nslookup does the same job as dig, but with different output style. By different style what i meant is it does provides the IP address of the domain name, but it also provides the DNS server that answered the query. We run: nslookup google.com Our computer contacts a DNS server The DNS server responds with the IP address & The DNS server that answered the query Example output: Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: example.com Address: 93.184.216.34 Enter fullscreen mode Exit fullscreen mode If DNS fails → nothing else matters. 📡 Check basic connectivity ping google.com OR ping 93.184.216.34 Enter fullscreen mode Exit fullscreen mode Before anything else, we always ask what is the IP address of google.com, like we did it using above two tools (dig & nslookup). So internally this happens: example.com → DNS → 93.184.216.34 So if DNS fails everything fails. Once IP is known, we do ping to that IP address, ping sends a special network message called ICMP Echo request . It like asking to that server, hey server, are you alive? Now there could two things happens, either the server responds or it doesn't. If server is reachable and allows ping. It replies with ICMP Echo Reply . Our terminal prints something like: 64 bytes from 93.184.216.34: time=12ms This means: the server is reachable, the network path work & the round trip time is 12 milliseconds. By default ping keeps sending packets every second: ping → reply ping → reply ping → reply Until you stop it with: Ctrl + C If ping fails: Network issue Firewall issue Host down What ping google.com actually verifies: The IP is reachable over the network Basic connectivity exists What Pings does not verify Application is running Website is working Port is open Server is healthy A server can reply to ping still have a down website. Sometimes ping may fail but website might be working fine. That's because many servers block (ICMP) ping for security reasons. So this can happen: ping google.com - may fail curl https://google.com - may work This does not mean site is down. A Basic Debugging Order: DNS: dig example.com Network reachability: ping example.com Application check: curl example.com Does ping do DNS resolution? Yes ping does the DNS resolution. But it only does the DNS resolution when we provide it a domain to find the IP of that particular domain it does the DNS resolution, If we provide it IP it won't do the DNS resolution. Example: Let's say we have a domain example.com, and we want to ping it. ping example.com Internally: ping sees the domain. It asks the DNS to resolve this domain The DNS server responds back with the IP: ping IP vs ping domain CASE A: ping google.com In this case we type the domain name which we want to ping ping google.com The computer doesn't understand names, it needs an IP, so DNS lookup happens means finding the IP address for the domain name. (Yes ping does the DNS if we provide it domain (bare minimum DNS just to find IP Address)) google.com → 93.184.216.34 Now ping sends packets to the IP address. DNS is involved only once at the beginning CASE B: ping 93.184.216.34 In this case we type the IP Address which we want to ping ping 93.184.216.34 The computer doesn't need to do DNS resolution as it already have the IP address. So DNS is skipped completely Ping sends packets directly to the IP. Difference in one sentence | Command | DNS involved? | What is pinged | | ------------- | ------------- | --------------------- | | ping domain | ✅ Yes | Application server IP | | ping IP | ❌ No | Application server IP | Why Cloud servers block ping Ping uses ICMP protocol, when we do ping we ask server (ICMP echo request) are you alive? This is a low-level network check, not an application request. Security Reasons: If ping were to allowed Attackers could easily find live servers Map infrastructure Launch attacks (DDoS Scanning) So cloud providers decide not to respond to ping at all. Ping ≠ Real Usage: User don't use ICMP, Ping. Users use HTTPS, HTTP, APIs, TCP Connection. So blocking ping does not affect real users. Common real-world situation: ping myserver.com → fails curl https://myserver.com → works This means: Server is running, application is working, ICMP is blocked intentionally. ICMP vs TCP ICMP ICMP = Internet Control Message Protocol Used only to check reachability, report network errors what it does: Can i reach this machine/server at all? TCP TCP = Transmission Control Protocol Used to open reliable connections, talk to applications on ports TCP → Port 80 / 443 → Web server HTTP/HTTPS Application-level protocols Build on top of TCP They answers questions like: Give me this web page, process this api request. Comparison: Thing ICMP (Ping) TCP / HTTP Purpose Reachability Real communication Uses ports? ❌ No ✅ Yes Talks to app? ❌ No ✅ Yes Blocked often? ✅ Yes ❌ Rarely Used by users? ❌ No ✅ Yes 🔌 Check if a port is open nc -vz example.com 443 Enter fullscreen mode Exit fullscreen mode If you see: ❌ connection refused → service or firewall issue ❌ timeout → routing or security group issue 🌍 Test HTTP directly curl -I https://example.com Enter fullscreen mode Exit fullscreen mode If this works → TCP + HTTP + DNS are all working. 🔧 Real DevOps debugging example Problem: Your app is deployed but users can’t access it. Debug like this (always in order): ❓ Does DNS resolve? ❓ Is the IP reachable? ❓ Is the port open? ❓ Is the application responding? 📌 Never jump steps. 📌 Networking debugging is layered , not random. 🚫 What we intentionally skipped (for now) We will explain these later — slowly and clearly: Subnets & CIDR NAT Firewalls & security groups Load balancers Docker networking Kubernetes services Each deserves its own beginner-friendly post. ✅ Key takeaways DevOps problems are often network problems Use the Client → Network → Server mental model Learn DNS, IPs, ports, and TCP first — everything builds on them Debug step by step, not by guessing ⏭️ Coming next Part 2: How the Internet Actually Works (Step by Step) We’ll trace what happens when you type a URL into your browser: DNS resolution Packets Servers Responses No jargon. No assumptions. If this helped you, consider bookmarking or sharing — the next parts build directly on this foundation. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Himanshu Bhatt Follow Aspiring DevOps professional passionate about cloud technologies. Sharing my learning journey to help others and grow. Looking to connect and explore new career opportunities! Location Nainital, Uttarakhand Education Bipin Tripathi Kuamon Institute of Technology Pronouns He/Him Work Seeking opportunities in DevOps & Cloud Engineering. Building skills through projects & blogging. Joined Jan 24, 2025 More from Himanshu Bhatt Introduction to DevOps #5. DevOps Tooling Landscape # devops # cloud # beginners # discuss [Boost] # devops # cloud # beginners # discuss Introduction to DevOps #4. What Problems DevOps Solves # devops # cloud # beginners # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://dev.to/axonixtools/i-built-97-free-online-tools-and-games-while-learning-to-ship-consistently-2g7d | I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Axonix Tools Posted on Jan 12 I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently # learning # productivity # showdev # webdev When I started building small web utilities, I never planned to create a large platform. I just wanted to solve simple problems that annoyed me during daily work. One small tool turned into several. Several slowly turned into many. Today, that experiment has grown into 97 free online tools, including browser-based games , all available under one project. Why I Focused on Small Tools Instead of One Big Product Big ideas sound exciting, but they also come with pressure and long timelines. Small tools, on the other hand, are easier to start and easier to finish. Each tool had: a clear purpose a limited scope a short build time Some tools took hours. Some took a single evening. What mattered most was finishing and publishing them. What Kind of Tools and Games I Built The tools fall into a few simple categories. Utility Tools Password generators Text and string converters JSON, Base64, and URL formatters Image compression and conversion tools Calculators and validators Browser-Based Games Small logic and puzzle games Memory games Classic mini-games built for learning and fun Everything runs directly in the browser with no signups and no downloads. You can explore the full collection here: https://axonixtools.com Technical Choices That Made This Possible I avoided complicated stacks whenever possible. Most tools use: lightweight JavaScript minimal dependencies simple and fast user interfaces The goal was never perfection. The goal was speed, clarity, and reliability. Boring technology turned out to be the best decision. What I Learned from Shipping 97 Tools Consistency Beats Motivation There were days when I didn’t feel like building anything. Instead of stopping, I worked on something small. Even: fixing a bug improving UI adding a minor feature counts as progress. Not Every Tool Needs to Be a Hit Some tools get traffic. Some don’t. That’s fine. Each tool is an experiment, and experiments don’t need to succeed to be valuable. SEO and Traffic (An Honest Take) I didn’t chase trends or viral keywords. Each page focuses on: one clear problem one clear solution Over time, some tools started ranking naturally through long-tail searches. Slow growth turned out to be more stable than chasing quick wins. Advice for Developers Building Side Projects If you’re thinking about starting something similar: Don’t wait for the perfect idea Build something useful, not impressive Ship fast and iterate later Let usage guide your improvements Keep everything simple You don’t need a big launch to make progress. What’s Next I’m still building, learning, and refining the platform. Axonix Tools started as practice and slowly became a growing collection of 97 tools and games . I plan to continue expanding it while keeping everything fast, free, and simple. If you’re curious, you can check it out here: https://axonixtools.com If you’re working on your own side project, feel free to share it. I enjoy reading how others approach building and shipping. Thanks for reading. Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Bhavin Sheth Bhavin Sheth Bhavin Sheth Follow Founder of AllInOneTools. Building privacy-first, browser-based tools with no sign-up, no tracking, and simple UX for daily tasks. Location Modasa, Gujarat, India Pronouns he/him Work Founder & Builder at AllInOneTools Joined Jan 9, 2026 • Jan 12 Dropdown menu Copy link Hide This really resonates. I’ve had a very similar experience building small, browser-based tools — once you remove signups and friction, usage patterns become very clear. Most users come for one specific task, get it done fast, and leave happy. Shipping many small, focused tools feels underrated compared to chasing one “big” product, but the learning compounds quickly. Curious — did you notice a few tools getting most of the repeat usage, or did it stay fairly distributed? Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Axonix Tools Follow Professional, free, and privacy-focused web tools for developers, designers, and daily productivity. Joined Jan 12, 2026 Trending on DEV Community Hot What was your win this week??? # weeklyretro # discuss I Didn’t “Become” a Senior Developer. I Accumulated Damage. # programming # ai # career # discuss Stop Overengineering: How to Write Clean Code That Actually Ships 🚀 # discuss # javascript # programming # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://dev.to/ajtiti/ajtiti-44-narzedzia-pomagajace-w-pracy-zdalnej#main-content | AjTiTi #44 - Narzędzia pomagające w pracy zdalnej - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close AjTiTi [PL] Follow AjTiTi #44 - Narzędzia pomagające w pracy zdalnej Jun 24 '22 play Kontynuujemy temat pracy zdalnej. Tym razem rozmawiamy o narzędziach, które nam pomagają i ułatwiają pracę w rozproszonym zespole. Czego użyć, by zadbać o efektywność pracy, komunikację, bazę wiedzy, ogarnięcie różnych stref czasowych, czy też ducha zespołu? Po odpowiedzi na te pytania, zapraszamy do odcinka. Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://aws.amazon.com/what-is/agentic-ai/?nc1=f_cc | What is Agentic AI? - Agentic AI Explained - AWS Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account What is Cloud Computing? › Cloud Computing Concepts Hub › Artificial Intelligence What Is Agentic AI? Create an AWS account What is Agentic AI? What are the characteristics of agentic AI systems? What are the use cases of agentic AI? What are the benefits of agentic AI? What are the types of agentic AI systems? How does agentic AI work? What are the challenges with agentic AI systems? How can AWS support your agentic AI requirements? What is Agentic AI? Agentic AI is an autonomous AI system that can act independently to achieve pre-determined goals. Traditional software follows pre-defined rules, and traditional artificial intelligence also requires prompting and step-by-step guidance. However, agentic AI is proactive and can perform complex tasks without constant human oversight. "Agentic" indicates agency — the ability of these systems to act independently, but in a goal-driven manner. AI agents can communicate with each other and other software systems to automate existing business processes. But beyond static automation, they make independent contextual decisions. They learn from their environment and adapt to changing conditions, enabling them to perform sophisticated workflows with accuracy. For example, an agentic AI system can optimize employee shift schedules. If an employee is off sick, the agent can communicate with other employees and readjust the schedule while still meeting project resource and time requirements. What are the characteristics of agentic AI systems? Here are the key features of an agentic AI system. Proactive Agentic AI acts proactively rather than waiting for direct input. Traditional systems are reactive, responding only when triggered and following predefined workflows. In contrast, agentic systems anticipate needs, identify emerging patterns, and take initiative to address potential issues before they escalate. Their proactive behavior is driven by environmental awareness and their ability to evaluate outcomes against long-term goals. For instance, in a supply chain setting, a traditional logistics platform updates delivery statuses when a user checks in or through periodic notifications. An agentic AI system, however, can monitor inventory levels, track weather conditions, and anticipate shipping delays. It can proactively raise alerts and even reroute shipments to reduce downtime. Adaptable A key feature of agentic AI is its ability to adapt to changing environments and specific domains. Traditional SaaS solutions are built to scale across industries and handle repetitive tasks, but they often lack the depth to understand unique domain-specific situations. Agentic systems fill this gap by using context awareness and domain knowledge, enabling AI agents to respond intelligently. They adjust their actions based on real-time input and can handle complex scenarios that standard solutions cannot. For example, while a generic customer service platform might respond with predefined answers, an agentic AI system supporting a healthcare provider understands medical terminology and complies with healthcare regulations. It can adapt to evolving patient concerns and delivers more accurate, context-sensitive support. Collaborative Agentic AI is designed to collaborate with humans and with other agentic AI systems. AI agents work as part of a broader team. They can understand shared goals, interpret human intent, and coordinate actions accordingly. They work well in settings that require human oversight or decision-making by considering inputs from multiple sources. For example, a treatment planning agent can coordinate with several different medical teams to prepare an integrated treatment and follow-up plan for a cancer patient. Specialized Agentic AI typically builds upon multiple hyperspecialized agents, with each focused on a narrow area of expertise. These AI-powered agents coordinate with each other, sharing insights and handing off tasks as needed. This approach enables significantly deeper domain-specific performance. For instance, in financial services, one agent might specialize in regulatory compliance, another in fraud detection, and another in portfolio optimization. Working together, they can monitor transactions in real time, flagging anomalies and recommending investment adjustments, all while maintaining regulatory compliance. What are the use cases of agentic AI? Agentic AI has unlimited applications and can be fully customized to any requirement. We give some examples of early adoption. Supporting research and development Research and development in any field requires a great deal of manual processes, such as testing hypotheses, gathering research information, collecting data, synthesizing insights across data sources, and more. Agentic AI can reduce the need for human intervention with these manual processes. It streamlines research and better coordinates teams that are working on research and development challenges. Agentic AI also facilitates multi-agent orchestration, where supervisors use multiple specialist models to construct complex research and development pipelines. For example, agentic AI could draw from recent research published on credible platforms, synthesize the results, plan further tests, and present researchers with the final product they need to investigate. This approach saves a significant amount of time and cost involved in research. Code transformation Agentc AI can use specialized AI-powered agents to remove the complexity of modernization and migration tasks. For example, agentic AI models for .NET can modernize Windows-based .NET applications to Linux significantly faster using machine learning, graph neural networks, Large language models (LLMs), and automated reasoning. Equally, agentic AI can decompose monolithic z/OS COBOL applications into individual components, reducing the timeframe of this process from months to minutes. Agentic AI offers unmatched speed, scale, and performance in automating application migration and modernization. Incident response automation Whenever an incident occurs, whether due to a vulnerability or a manual error, agentic AI can expedite the incident response process, saving your business time and improving time-to-recovery. Agentic AI can automate the entire incident response pathway, rolling back issues, creating incident reports, and notifying any team members who need to stay informed. Agentic AI enhances incident response speed while also providing a more specific and in-depth post-incident analysis to prevent the same errors from recurring in the future. Customer service automation In many customer service scenarios, the information that a customer needs is already online in a tutorial or help article. Agentic AI processes customer service inquiries and rapidly searches through available company documents to find a suitable answer that helps them out. If this alone isn’t enough to solve a query, agentic AI can then communicate with the user to gather more information about their case and direct them toward a solution. They are designed with modular components, such as reasoning engines, memory, cognitive skills, and tools, that enable them to remedy the vast majority of problems. AI-powered agents can operate independently, learn from their environment, adapt to changing conditions, and develop more effective strategies to assist customers. If, after several attempts, it cannot solve a customer’s issue, it then contacts a human support agent and assigns them to the case. Utilizing this form of AI in customer service scenarios alleviates the burden on human teams and enables the vast majority of customer-oriented services to operate 24/7. What are the benefits of agentic AI? There are several business benefits to using agentic AI. Increased efficiency Agentic artificial intelligence enables businesses to simplify the complexity of various challenging or specialized tasks through automation. Instead of relying on human-driven manual practices, using agentic AI can automate tedious processes, freeing up time for your employees. Your employees can use the extra time that agentic AI saves them on more demanding tasks, such as problem-solving, strategic planning, and other drivers of growth. Increased user trust Agentic AI can offer a higher degree of personalization when interacting with customers. By utilizing existing customer data, agentic AI can quickly produce tailored messaging, engage with the customer in their preferred tone, and offer practical product recommendations. Over time, agentic AI improves customer relationships and builds trust between customers and your business. Businesses can also utilize agentic artificial intelligence to analyze customer feedback, identify the most frequently occurring information, and provide it to product engineers. It can also directly respond to users who leave feedback, creating positive feedback loops where customers feel that their feedback is taken seriously by your company. Continuous improvement Agentic AI can continuously learn and improve, adapting to any tasks assigned to it. It interacts, learns from feedback, and optimizes its decision-making based on this recursive loop. For businesses, this means that it continues to deliver its benefits at higher and higher levels over time. Human augmentation Agentic AI can serve as a fantastic collaboration tool for human agents, enhancing their productivity and reducing the number of laborious manual tasks they must complete. By working alongside agentic AI models, human agents can overcome complex challenges, automate difficult decision-making pathways, and drive their efficiency. What are the types of agentic AI systems? Agentic AI can be single or multi-agent setups. In a single-agentic AI system, one AI agent handles all tasks sequentially. These are preferable when businesses need a faster solution that can work on a well-defined problem or process. Multi-agentic AI, on the other hand, involves multiple AI agents collaborating to break down complex workflows into smaller segments. This approach is more scalable than single systems and is much more flexible for solving complex scenarios. The vast majority of agentic AI agents refer to this latter, more diverse form of AI deployment. Here are a few different structures of multi-agent systems. Horizontal multi-agent Horizontal multi-agent AI is a system of working where every AI agent has the same level of technical proficiency and complexity. Each agent specializes in a narrow skill, bringing their findings together to solve a complex problem. This structure utilizes lateral collaboration and communication among the specialized AI agents. Vertical multi-agent In a vertical multi-agent system, there is a hierarchical structure in which lower-level AI agents have ‘easier’ tasks compared to the higher ones. The highest levels of this structure handle tasks that require more processing power and LLMs, such as critical thinking, reasoning, and decision-making. Lower-level AI agents in this structure perform tasks such as collecting data, formatting it, or processing it to pass it to higher levels. How does agentic AI work? Agentic AI agents operate by using a structured pathway that moves through four stages — perceive, reason, act, and learn. Each stage in this process integrates several advanced AI technologies and methods. Perceive At the perception stage, AI agents collect real-time data from a range of diverse sources, ingesting structured, semi-structured, and unstructured data. Agents directly interact with RESTful APIs, gRPC services, and GraphQL endpoints to ingest data as needed from cloud platforms, enterprise systems, and SaaS applications. In certain legacy systems or those that require interaction with document-heavy environments, optimal character recognition technology (OCR) and natural language processing can help sift through scanned documents for relevant information. At the perceive stage, agents also process data to determine what is useful based on the task context in which they are working. Reason The reasoning stage is powered by LLMs that help to interpret the context of the goals a model has, develop an action plan to follow, and adapt in real-time using new information received through the perceive stage. LLMs employ models that utilize semantic reasoning, error handling, and adjust to any ambiguous user inputs. Beyond just processing ideas and developing strategy in this stage, some LLMs use predictive machine learning models to manage complex problems. For example, a predictive ML model can forecast surges in demand, enabling better preparation for future use cases. At this stage, LLMs use long-term memory systems to ensure that situational and context-dependent tasks remain consistent throughout the entire process. Act At the act stage, agentic AI takes action to achieve what was set out by the reasoning stage effectively. As agentic AI can access administrator-installed plugins on each of these external software systems, it can directly interact with and run tasks on these third-party applications. The act stage orchestrates several subtasks that the agentic models will then tackle sequentially, with specific actions ranging from compiling code to interacting with software and documents, running simulations, migrating applications, and performing functions within a third-party application. For some agentic AI models, actions are gated by human-in-the-loop systems, where developers must verify what the model is doing and approve its actions. All actions taken by a model are closely monitored and logged, allowing businesses to align with governance and safeguard their use of this technology. Learn The learning stage of agentic AI is what enables these models to continually improve their functionality and effectiveness. The agent utilizes reinforcement learning techniques, such as proximal policy optimization (PPO) and Q-learning, to refine actions based on the success of a specific task within the broader system. AI agents learn from autonomous agents, LLMs, or through human feedback, all of which can fine-tune the system to improve its functioning. There are several metrics that a model can use to track its performance, including latency, confidence, and success rate. Multi-agent AI typically distributes learning across different agents, sharing information in communal memory layers to enhance the entire system's performance. Over time, this style of reinforcement learning can utilize successful iterations to improve its overall functioning and enhance efficiency continually. What are the challenges with agentic AI systems? Several challenges are associated with agentic AI and building effective models. System design The process of building a multi-agent architecture that effectively coordinates with other models, has specific knowledge of how to tackle certain tasks, and can perform high-level reasoning and strategic planning is a challenging task. Agentic AI is a cutting-edge area of technology that relies on numerous challenging AI strategies. Due to the complexity of designing an effective system, many companies will struggle to access an effective version of agentic AI. Testing and debugging Agentic AI works independently and with minimal human intervention. This benefit also makes testing, debugging, and determining where an AI model has gone wrong a challenge. Developers must build traceability and reproducibility into the AI model, with special attention paid to tracing any errors and determining their causes. Trust and transparancy Even in advanced AI systems, AI hallucinations can impact workflows, leading to significant errors and problems for the business operating the model. If models generate false information and then relay it to the rest of the AI agents, incorrect data can rapidly spread, escalating errors in the final output. Especially in industries such as finance and healthcare that have severe real-world implications, businesses must have a great deal of trust in their product before using it extensively. How can AWS support your agentic AI requirements? Amazon Bedrock is a fully managed service that offers a choice of industry-leading foundation models (FMs) along with a broad set of capabilities needed to build generative AI applications. Amazon Bedrock Agents use the reasoning of FMs, APIs, and data to break down user requests, gather relevant information, and efficiently perform tasks. Building an agent is straightforward and fast, with setup in just a few steps. Amazon Bedrock supports: Memory retention for seamless task continuity Multi-agent collaboration to build multiple specialized agents under the coordination of a supervisor agent Amazon Bedrock Guardrails for built-in security and reliability. AWS has introduced an open-source toolkit with a growing catalog of starter agents purpose-built for healthcare and life sciences use cases. AWS Transform is the first agentic AI service for transforming .NET, mainframe, and VMware workloads. Built on 19 years of migration experience, it deploys specialized AI agents to automate complex tasks like assessments, code analysis, refactoring, decomposition, dependency mapping, validation, and transformation planning. It helps organizations to simultaneously modernize hundreds of applications while maintaining quality and control. Amazon Q Business is a generative AI-powered assistant designed to help you find information, gain insights, and take action at work. It puts the power of agentic AI creation in the hands of every employee. Anyone can use it to create lightweight agentic AI apps that interact with common enterprise software and automate repetitive tasks. Get started with agentic AI on AWS by creating a free account today. Next steps on AWS Check out additional product-related resources Learn more Sign up for a free account Instantly get access to the AWS Free Tier. Sign up Start building in the console Get started building with AWS in the AWS Management Console. Sign in Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:29 |
https://developer.x.com/docs/twitter-for-websites/privacy | Privacy | Docs | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Privacy What information does X collect through X for Websites and how is that information used? When you view X content such as embedded Tweets, buttons, or timelines integrated into other websites using X for Websites, X may receive information, including the web page you visited, your IP address, browser type, operating system, and cookie information. This information helps us to improve our products and services. Learn more about the information we receive and how we use it in our privacy policy and cookies policy . How long do you keep this information? To protect privacy, we never associate this web browsing history we collect from X for Websites with customers’ names, email addresses, phone numbers, or X handles, and we delete, obfuscate, or aggregate it after no longer than 30 days, as explained in our privacy policy . We don't store this web browsing history from certain domains such as .mil and .gov. <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>"> Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:29 |
https://www.linkedin.com/pulse/my-book-charlie-walks-novel-now-available-worldwide-daniel-bourke | My book Charlie Walks: A Novel is now available worldwide Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Join now Sign in 6 min read The Charlie Walks paperback edition will look fantastic on your bookshelf. My book Charlie Walks: A Novel is now available worldwide Report this article Daniel Bourke Daniel Bourke Published Nov 15, 2022 + Follow Almost five years to the day since writing the first line, my first novel is complete and ready to ship worldwide. Self-published with help from Saeah and the Otterpine team . You can buy the beautiful paperback (and digital) edition at charliewalks.com . I'm used to selling digital products so selling a physical product is something new. But I'm excited! This is the best thing I've ever made. I made a launch video to go along with it, a cumulation of the journey. The video adds a visual element to the letter below. A letter to Pauly letting him know the book's ready to go. If you've read the book you'll be a fan of the meta. If not... Launch letter Dear Pauly, It happened. Go to charliewalks.com and you can buy my beautiful book anywhere in the world! We talked about this for years. That book I was writing. All done! Out in the wild! You can hold it, flip the pages. Four, five years from the first line . I started typing the first draft then moved to pen and paper. Slower. But the rhythm feels better. The same feeling as when I first learned to write as a child. The curiosity of the blank page teasing me forward. Six or seven notepads by the end. The original handwritten notepads for Charlie Walks: A Novel. Readers of the final copy will read text not too far from what's on these pages. Then I typed them up and retyped the words four, five, six, seven different times. Every couple of months going to the printer and printing the next version. The printing clerk got to know me. You’re back they’d say. Yes, I’d say. Getting up earlier and earlier each morning. My tools: sometimes coffee sometimes tea always walks always other writers. Looking out the window looking at the wall wondering where I’ll go today where I go when my pen comes off the page when I pause when I sit back from my screen I care an increasing amount about how things look. Beauty of the highest standard even with words on a page. It sounds silly with writing. How can words on a page look good? Easy. Compare a legal terms sheet and my new book. I decorated my whiteboard with edits. Ticking off one chapter at a time. Some too long. Cutting them in two, in three. Deleting them. My high school teacher gave me a C in English. Deserved! I wouldn’t read that mud either. But this! Charlie Walks! I did it Pauly. Ho ho, I did it! I wrote a book I’d like to read. I think you will too. You’re in it after all. Those stories we talked about, the man on the boat, skydiver Rick, the women, the friends, the enemies, Raj! Oh, Raj! All these characters you helped create. Sometimes I forget you’re my nephew Pauly. Such a label doesn’t describe our relationship. You’ll love the cover too. Charlie’s a funambulist! Do you know what that word means? Well, in Latin, funis means rope and ambulo means walk. So a funambulist is a rope walker or better a tightrope walker. Charlie the funambulist, Charlie the tightrope walker! Why? No spoilers now c’mon. There’s the blurb for that! But I prefer fun-ambulist. A fun walker! I designed the cover with that in mind. Drew a man walking between city and nature. A modern dichotomy. Many artists submitted their interpretations. I went through them all and picked the one you see. Perhaps I should’ve gotten my computer to make one. Used one of the new generative artificial intelligence models. Charlie, me, the main character, is a machine learning engineer after all. Next time! The digital version came out on my birthday last year. But it’s not the same. You can’t hold it. Can’t smell it can’t feel the tactile satisfaction of flipping pages and most important: can’t show it off on your bookshelf. I lost a bet Pauly. I bet Dave it would be out three years ago. $500. Recommended by LinkedIn Feel This Book: The Tactile Renaissance of Print in a… Kevin Abergel 5 months ago The Disappearance of Magazine Culture—and of the… Tomohiko TANIGUCHI 7 months ago The Software Architect Elevator Gregor Hohpe 5 years ago A bet I made to my friend Dave about having the book published by a certain date. I lost on the timeline but completed the overall goal. A reasonable sum. I better sell some copies! He said not to worry about it. But I have more self-respect than that. It’s here Dave! And don’t worry my friend, you’ll get your money soon! When the first printed copies arrived I almost cried. My book Pauly! The book I’d like to read! The book I’d like to write! I picked one up and kissed it. All those days walking past bookstores and public libraries holding the works of my gods and imagining one day my name being amongst theirs! Ruby helped me unpack them and I got to work signing and numbering each one, the first 150 copies. I gave one each to friends and family far and near. Handwriting letters to put inside just like this one. Thank you thank you thank you enjoy my book it’s the best thing I’ve ever made. I being the cumulation of a lifetime of people and stories around me. I as in me, Charlie, only took the time to put them down on paper. Hand-wrapping the first editions on the floor sweating because of the summer heat because of the fire under my feet! One to India Italy Melbourne Canada New Zealand. Leaving them outside for the delivery person to collect. One of them even got caught in a local flooding event! And to local public libraries! A Charlie Walks hit list. Someone converted an old red phone booth into one. Out the front of homes, old sheds, old fridges, saying hello to the caretakers, this is a custom book and them saying oh yes, thank you. Will anyone find them? Don’t answer that. The fun is in not knowing! Like the feeling of watching birds fly behind the clouds. The Japanese call it yugen. The enchanting mysticism of the unknown. And the reverse heist! What a laugh! I’ll show you a video next time I see you. But if a heist is taking without asking a reverse heist is leaving without asking. I left a few copies of Charlie Walks at a large bookstore. I heard later the manager wasn’t happy. They wanted to sue me. Oh goodness Pauly. What have I done? Wrong to leave the books? Perhaps. But forgive me for assuming the lightheartedness of a bookstore owner towards a new author. Next time I’ll just ask. Excuse me, would you like my book? I tried it. One bookstore said yes. Another said no. Turns out it’s that easy. You just ask! I held a makeshift bookstore of my own near the water. The local cafe owner Andrew offered a good deal. Anyone who buys a book gets a free coffee he said. I printed signs. Buy a book, get a coffee. People loved it! One of my primary school teachers even bought a copy! It’s incredible how supportive the world seems to become when you support yourself first. I’ll let you on a secret Pauly: I’m my own biggest fan. I stood by my book and said, hello this is what I’ve made. Many people said they’d always wanted to write a book. Some even had drafts waiting to be finished. Now they’d seen my novel, felt it in their hands, it gave them a healthy dose of well, if he can do it… I sold out Pauly. And I could order more for myself to sell locally. But what about my readers elsewhere? I asked a publisher to help. And they said they’d never done fiction but there’s a first for everything. Wow! Again! It surprised me what you can achieve by just asking. They helped with the formatting made it look even better than I could on my own, we’ll get our special printer to print the next copies, they said, you’ll love the quality. And I do I do I do. The pages! Like a real novel! The feel, thick and solid, the sound of the pages turning, the typeset easy on the eyes, plenty of white space to let the reading mind wander. The story… Oh you’ll love the story! Science fiction but not too much. Coming of age. Love, loss, enough song and dance for the romantics, enough technology for the nerds. I’ve gone on for too long. But I can’t help it! I’m sure you can tell how excited I am to finally let these words go and become yours. I did it Pauly. I wrote a beautiful book. A book that’s now available to buy worldwide . A book I’d like to read. And I’m sure you will too. Love always, Charlie PS Let me know when you’re finished and we can talk about ideas for the next one. The typeset on Charlie Walks looks outstanding. Buy ten copies and stack them together! Confirmed: Charlie Walks looks good on kitchen tables. Like Like Celebrate Support Love Insightful Funny Comment Copy LinkedIn Facebook X Share 37 2 Comments Sharun Kumar G 3y Report this comment Congratulations Daniel !! Like Reply 1 Reaction Parth Kalkar 3y Report this comment Great job, do you have a pdf version of it? Like Reply 1 Reaction See more comments To view or add a comment, sign in More articles by Daniel Bourke Introducing Nutrify 2.0: Multi-Food Mode, 552 New Foods and Food Share Dec 9, 2025 Introducing Nutrify 2.0: Multi-Food Mode, 552 New Foods and Food Share TL;DR: Nutrify 2.0 introduces: Multi-Food Mode - Identify all visible foods/drinks, number of servings and weights from… 104 2 Comments Introducing Nutrify 1.2.3: Whole Food Streaks, Widgets, Quick Summaries and 41 New Foods Nov 4, 2024 Introducing Nutrify 1.2.3: Whole Food Streaks, Widgets, Quick Summaries and 41 New Foods Nutrify version 1.2. 101 8 Comments The importance of a test set Aug 19, 2024 The importance of a test set Real things, real places Had a phone call the other day with someone who wanted advice for their machine learning… 113 5 Comments Introducing Nutrify 1.2: Calorie and Macronutrient Goals, Breakdowns and 57 New Foods May 28, 2024 Introducing Nutrify 1.2: Calorie and Macronutrient Goals, Breakdowns and 57 New Foods Nutrify 1.2 is here! What is Nutrify? Nutrify is a food tracking and education app focused on whole foods. 75 9 Comments Introducing Nutrify | Learn about food with AI Feb 27, 2024 Introducing Nutrify | Learn about food with AI Short Version Nutrify is an iOS application designed to make learning about whole foods fun and in turn, reduce the… 113 7 Comments A Learner's Fight: Adaptation vs. Education Aug 15, 2023 A Learner's Fight: Adaptation vs. Education My grades sucked at high school. And I failed my first two years of university. 95 4 Comments How to get your first machine learning job (5 practical tips) Mar 27, 2023 How to get your first machine learning job (5 practical tips) You can see the video version of this article on YouTube. This article originally appeared on zerotomastery. 115 1 Comment The Top 4 Reasons to Learn PyTorch (and start getting into AI) Feb 17, 2023 The Top 4 Reasons to Learn PyTorch (and start getting into AI) Machine learning and artificial intelligence (AI) are exploding! And as you'll find out, PyTorch is one of the biggest… 191 7 Comments Learn PyTorch for deep learning (beginner-friendly course) Sep 7, 2022 Learn PyTorch for deep learning (beginner-friendly course) Short version The Zero to Mastery PyTorch course, taught by myself, is live and available. Sign up for the full video… 198 6 Comments Survivability and Scalability May 10, 2022 Survivability and Scalability Been thinking about skills for the future. And fun things to do now. 26 Show more See all articles Others also viewed What goes on behind the scenes? 1. The Proposal stage Eloise Cook 2y What You Need to Know Before Getting a Book Design Quote Michelle M. White 4mo A Beginner's Guide to Polished Documents Shruti Bhatt 1y Top 20 Book Cover Artists For Hire Cynthia Davis 2y Success Strategies for Self-Publishing your Nonfiction Book Stephanie Chandler 6y Will my book be copyedited or proofread? Eloise Cook 1y The Best Route for Self-Publishing Your Book Michele DeFilippo 9y The Visualist | Summer Visual Poetry Maram Mohammad Al-Badrawy 5mo How to Typeset a Book Michele DeFilippo 9y 5 tips to build author photo confidence Fi Phillips 2y Show more Show less Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Recruitment & HR Customer Experience Real Estate Marketing Sales Retail & Merchandising Science Supply Chain Management Future Of Work Consulting Writing Economics Artificial Intelligence Employee Experience Workplace Trends Fundraising Networking Corporate Social Responsibility Negotiation Communication Engineering Hospitality & Tourism Business Strategy Change Management Organizational Culture Design Innovation Event Planning Training & Development Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:29 |
https://developer.x.com/docs/twitter-for-websites/timelines/overview | Overview | Docs | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Overview Please note: We retired the Likes, Collections, and Moments timelines on January 13, 2023. We recommend you use the Profile and Lists timelines, which we’re updating to become faster, easier to use, and more up-to-date with X features and functionality. You can learn more about this change in our announcement . Embedded Timelines Embedded timelines are an easy way to embed Tweets on your website in a compact, linear view. Choose between a profile timeline to get the latest Tweets from a X account, or a List timeline containing a curated list of Tweets from your favorite X accounts. An embedded timeline consists of two parts: including an embed code that links your webpage to the timeline on x.com, and the X for Websites JavaScript to transform the link into a fully-rendered timeline. Timeline types Profile timeline A profile timeline displays the latest Tweets from the specified (public) X account. Tweets by XDevelopers List timeline A list timeline displays the latest Tweets from a curated, public list of X accounts. The timeline includes a header displaying the list’s name, description, and curator. To create lists on x.com, the X app, or in TweetDeck, learn more here . A List by XDevelopers How to add an embedded timeline to your website Visit publish.twitter.com to generate embed codes for profiles and lists. Customization Dimensions An embedded timeline automatically adjusts to the width of its parent element with a minimum width of 180 pixels and a maximum width of 520 pixels. The grid display has a minimum width of 220 pixels. Set the maximum width or the maximum height of an embedded timeline by adding a data-width or data-height attribute to the embed code anchor element. <a class="twitter-timeline" href="https://twitter.com/TwitterDev" data-width="300" data-height="300"> Tweets by @TwitterDev </a> Custom chrome Control the frame around the linear timeline by setting a data-chrome attribute with space-separated tokens for each chrome component. Token Description noheader Hides the timeline header. Implementing sites must add their own X attribution, link to the source timeline, and comply with other X display requirements . nofooter Hides the timeline footer and Tweet composer link, if included in the timeline widget type. noborders Removes all borders within the widget including borders surrounding the widget area and separating Tweets. noscrollbar Crops and hides the main timeline scrollbar, if visible. Please consider that hiding standard user interface components can affect the accessibility of your website. transparent Removes the widget’s background color. Example: <a class="twitter-timeline" href="https://twitter.com/TwitterDev" data-chrome="nofooter noborders"> Tweets by @TwitterDev </a> Tweets by TwitterDev Limiting the number of Tweets displayed Display a specific number of items between 1 and 20 by customizing your embed HTML. Add a data-tweet-limit attribute to the embed code to specify a number of Tweets. The timeline will automatically adjust its height to display a specified number of Tweets. The timeline is fixed after display; it will not poll for new Tweets until the page is refreshed. Example: <a class="twitter-timeline" href="https://twitter.com/TwitterDev" data-tweet-limit="3"> Tweets by @TwitterDev </a> Tweets by TwitterDev Accessibility: Override ARIA live politeness An embedded timeline describes its content for screen readers and other assistive technologies using additional markup defined in WAI-ARIA standards . A timeline widget is a live region of a page which will receive updates when new Tweets become available. By default, a timeline has a politeness value of polite by default; set a data-aria-polite attribute value of assertive to set the embedded timeline live region politeness to assertive , for example if you’re using the embedded Timeline as a primary source of live content in your page. <a class="twitter-timeline" href="https://twitter.com/TwitterDev" data-aria-polite="assertive"> Tweets by @TwitterDev </a> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>"> Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:29 |
https://youtu.be/5X3VZBKllh4 | Signals, the Future of Reactive Programming in Angular - AiA 377 - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xa869a1fe1c96d913"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtOV2d0bjJ1RzJuVSjcjZjLBjIKCgJLUhIEGgAgOQ%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRrCE1Ujyhs1c4E9aFEQykABLCkjiR4c7Qc8HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","markerRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","topicLinkRenderer","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtOV2d0bjJ1RzJuVSjcjZjLBjIKCgJLUhIEGgAgOQ%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwiwya3xkIiSAxXQejgFHVtaBMcyDHJlbGF0ZWQtYXV0b0ierJaVwaz1vuUBmgEFCAMQ-B3KAQQPdFWj","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=3oIL71er4YI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"3oIL71er4YI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiwya3xkIiSAxXQejgFHVtaBMcyDHJlbGF0ZWQtYXV0b0ierJaVwaz1vuUBmgEFCAMQ-B3KAQQPdFWj","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=3oIL71er4YI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"3oIL71er4YI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwiwya3xkIiSAxXQejgFHVtaBMcyDHJlbGF0ZWQtYXV0b0ierJaVwaz1vuUBmgEFCAMQ-B3KAQQPdFWj","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=3oIL71er4YI\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"3oIL71er4YI","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Signals, the Future of Reactive Programming in Angular - AiA 377"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 117회"},"shortViewCount":{"simpleText":"조회수 117회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESCzVYM1ZaQktsbGg0GmBFZ3MxV0ROV1drSkxiR3hvTkVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTHpWWU0xWmFRa3RzYkdnMEwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}}],"trackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"3","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJ8CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},{"innertubeCommand":{"clickTrackingParams":"CJ8CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CKACEPqGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CKACEPqGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"5X3VZBKllh4"},"likeParams":"Cg0KCzVYM1ZaQktsbGg0IAAyDAjcjZjLBhCynPCJAg%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CKACEPqGBCITCLDJrfGQiJIDFdB6OAUdW1oExw=="}}}}}}}]}},"accessibilityText":"다른 사용자 3명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJ8CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"4","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJ4CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},{"innertubeCommand":{"clickTrackingParams":"CJ4CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"5X3VZBKllh4"},"removeLikeParams":"Cg0KCzVYM1ZaQktsbGg0GAAqDAjcjZjLBhCoivGJAg%3D%3D"}}}]}},"accessibilityText":"다른 사용자 3명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJ4CEKVBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isTogglingDisabled":true}},"likeStatusEntityKey":"Egs1WDNWWkJLbGxoNCA-KAE%3D","likeStatusEntity":{"key":"Egs1WDNWWkJLbGxoNCA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJwCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oExw=="}},{"innertubeCommand":{"clickTrackingParams":"CJwCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJ0CEPmGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJ0CEPmGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"5X3VZBKllh4"},"dislikeParams":"Cg0KCzVYM1ZaQktsbGg0EAAiDAjcjZjLBhDGufKJAg%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CJ0CEPmGBCITCLDJrfGQiJIDFdB6OAUdW1oExw=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJwCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oExw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJsCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oExw=="}},{"innertubeCommand":{"clickTrackingParams":"CJsCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"5X3VZBKllh4"},"removeLikeParams":"Cg0KCzVYM1ZaQktsbGg0GAAqDAjcjZjLBhCE3vKJAg%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJsCEKiPCSITCLDJrfGQiJIDFdB6OAUdW1oExw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isTogglingDisabled":true}},"dislikeEntityKey":"Egs1WDNWWkJLbGxoNCA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"Egs1WDNWWkJLbGxoNCD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJkCEOWWARgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},{"innertubeCommand":{"clickTrackingParams":"CJkCEOWWARgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"Cgs1WDNWWkJLbGxoNKABAQ%3D%3D","commands":[{"clickTrackingParams":"CJkCEOWWARgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CJoCEI5iIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJkCEOWWARgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CJcCEOuQCSITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJgCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D5X3VZBKllh4\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJgCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X3VZBKllh4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X3VZBKllh4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh266.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e57dd56412a5961e\u0026ip=1.208.108.242\u0026initcwndbps=3431250\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"idamTag":"66427"}},"trackingParams":"CJgCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oExw=="}}}}}},"trackingParams":"CJcCEOuQCSITCLDJrfGQiJIDFdB6OAUdW1oExw=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CJUCEOuQCSITCLDJrfGQiJIDFdB6OAUdW1oExw=="}},{"innertubeCommand":{"clickTrackingParams":"CJUCEOuQCSITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CJYCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D5X3VZBKllh4\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CJYCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X3VZBKllh4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X3VZBKllh4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh266.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e57dd56412a5961e\u0026ip=1.208.108.242\u0026initcwndbps=3431250\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"idamTag":"66427"}},"trackingParams":"CJYCEPuGBCITCLDJrfGQiJIDFdB6OAUdW1oExw=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CJUCEOuQCSITCLDJrfGQiJIDFdB6OAUdW1oExw==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","superTitleLink":{"runs":[{"text":"Adventures in Angular Podcast Episodes","navigationEndpoint":{"clickTrackingParams":"CJQCELW0CRgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLJesql-aSfX6PKiA6XAjzbUCWiYCUkU2q","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLJesql-aSfX6PKiA6XAjzbUCWiYCUkU2q"}}}]},"dateText":{"simpleText":"2023. 4. 9."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Top End Devs","navigationEndpoint":{"clickTrackingParams":"CJMCEOE5IhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CJMCEOE5IhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 4.5천명"}},"simpleText":"구독자 4.5천명"},"trackingParams":"CJMCEOE5IhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCABJEQ57MIn6X3TIHIebJUw","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CIQCEJsrIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Top End Devs을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CJICEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CJECEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Top End Devs 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CIoCEJf5ASITCLDJrfGQiJIDFdB6OAUdW1oExw==","command":{"clickTrackingParams":"CIoCEJf5ASITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIoCEJf5ASITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CJACEOy1BBgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQQPdFWj","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggBGAAgBFITCgIIAxILNVgzVlpCS2xsaDQYAA%3D%3D"}},"trackingParams":"CJACEOy1BBgDIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CI8CEO21BBgEIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQQPdFWj","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcSAggDGAAgBFITCgIIAxILNVgzVlpCS2xsaDQYAA%3D%3D"}},"trackingParams":"CI8CEO21BBgEIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CIsCENuLChgFIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIsCENuLChgFIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIwCEMY4IhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CI4CEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHMgV3YXRjaMoBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILNVgzVlpCS2xsaDQYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CI4CEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CI0CEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CIsCENuLChgFIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CIQCEJsrIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CIkCEP2GBCITCLDJrfGQiJIDFdB6OAUdW1oExzIJc3Vic2NyaWJlygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253D5X3VZBKllh4%26continue_action%3DQUFFLUhqbFF4cE9qd09FbEI3emxRcm93R19NaENMX1NPZ3xBQ3Jtc0trczF4ZDYwY1c1QXladlBmakhONWVJMFl2VWpZbzRrUEw5akI2S2M0LWxQdmQ1VlA3dXBPX1BtQzFBMllIak5UYnhnQXVHbVBDUm1VclBhNXZydjE0d0hfZ1BUYzRMX0RhcjltSURDZjg5Ykd6dlRLem5wdFVPc1lxNTdDSm4zUklzQ2ZHSWxKRy1Ca1NFNkRVNzdxMHBoVUh6ZGxNYVdYdWIyZU9NbTBaT2FDaHhyM1JZckhjUkhDaUpDY19lZDl1U1YzRHc\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CIkCEP2GBCITCLDJrfGQiJIDFdB6OAUdW1oEx8oBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=5X3VZBKllh4","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"5X3VZBKllh4","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh266.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e57dd56412a5961e\u0026ip=1.208.108.242\u0026initcwndbps=3431250\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}},"continueAction":"QUFFLUhqbFF4cE9qd09FbEI3emxRcm93R19NaENMX1NPZ3xBQ3Jtc0trczF4ZDYwY1c1QXladlBmakhONWVJMFl2VWpZbzRrUEw5akI2S2M0LWxQdmQ1VlA3dXBPX1BtQzFBMllIak5UYnhnQXVHbVBDUm1VclBhNXZydjE0d0hfZ1BUYzRMX0RhcjltSURDZjg5Ykd6dlRLem5wdFVPc1lxNTdDSm4zUklzQ2ZHSWxKRy1Ca1NFNkRVNzdxMHBoVUh6ZGxNYVdYdWIyZU9NbTBaT2FDaHhyM1JZckhjUkhDaUpDY19lZDl1U1YzRHc","idamTag":"66429"}},"trackingParams":"CIkCEP2GBCITCLDJrfGQiJIDFdB6OAUdW1oExw=="}}}}}},"subscribedEntityKey":"EhhVQ0FCSkVRNTdNSW42WDNUSUhJZWJKVXcgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CIQCEJsrIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHKPgdMgV3YXRjaMoBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"EgIIAxgAIgs1WDNWWkJLbGxoNA%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CIQCEJsrIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CIQCEJsrIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CIYCEMY4IhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","dialogMessages":[{"runs":[{"text":"Top End Devs"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CIgCEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHKPgdMgV3YXRjaMoBBA90VaM=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCABJEQ57MIn6X3TIHIebJUw"],"params":"CgIIAxILNVgzVlpCS2xsaDQYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CIgCEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CIcCEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}],"timedAnimationData":{"animationTiming":[313919,2086139,1753559],"macroMarkersIndex":[0,1,2],"animationDurationSecs":1.5,"borderStrokeThicknessDp":2,"borderOpacity":1,"fillOpacity":0,"trackingParams":"CIUCEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","animationOrigin":"ANIMATION_ORIGIN_SMARTIMATION"}}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Armen, Chuck, and Lucas join this week's panelist episode to talk about Signals in Angular. Armen starts off as he gives an introduction to Signals and H\\he explains the difference between RxJS. Additionally, they discuss the problems they solve in Angular.\n\nhttps://topenddevs.com/podcasts/adven...","commandRuns":[{"startIndex":260,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CIMCEM2rARgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHSJ6slpXBrPW-5QHKAQQPdFWj","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa1UwVEJuR09LelFZVzUyaDBzX3NCRVVKZS1OQXxBQ3Jtc0tsVUZyelJmZVBuQkZ6cUVrSWFXOE1iM24zU2QxZUljcVB6Umt5enVsbk1sMTBuOXA5ZXplOWRYMnJqc19SSkRobFRiWkJZUTQtdktUZXlqOXFHTEROZVdzVjlIOTBtanFCT0RKaHJiQnBaUFQ0aE9GVQ\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-angular%2Fepisodes%2Fb91c0e60-e0ce-4eb0-90c6-fe00da7bacfb\u0026v=5X3VZBKllh4","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa1UwVEJuR09LelFZVzUyaDBzX3NCRVVKZS1OQXxBQ3Jtc0tsVUZyelJmZVBuQkZ6cUVrSWFXOE1iM24zU2QxZUljcVB6Umt5enVsbk1sMTBuOXA5ZXplOWRYMnJqc19SSkRobFRiWkJZUTQtdktUZXlqOXFHTEROZVdzVjlIOTBtanFCT0RKaHJiQnBaUFQ0aE9GVQ\u0026q=https%3A%2F%2Ftopenddevs.com%2Fpodcasts%2Fadventures-in-angular%2Fepisodes%2Fb91c0e60-e0ce-4eb0-90c6-fe00da7bacfb\u0026v=5X3VZBKllh4","target":"TARGET_NEW_WINDOW","nofollow":true}}}}],"styleRuns":[{"startIndex":0,"length":260,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4294967295},{"key":"USER_INTERFACE_THEME_LIGHT","value":4279440147}]}},"fontFamilyName":"Roboto"},{"startIndex":260,"length":40,"styleRunExtensions":{"styleRunColorMapExtension":{"colorMap":[{"key":"USER_INTERFACE_THEME_DARK","value":4282296063},{"key":"USER_INTERFACE_THEME_LIGHT","value":4278607828}]}},"fontFamilyName":"Roboto"}]},"headerRuns":[{"startIndex":0,"length":260,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"},{"startIndex":260,"length":40,"headerMapping":"ATTRIBUTED_STRING_HEADER_MAPPING_UNSPECIFIED"}]}},{"compositeVideoPrimaryInfoRenderer":{}},{"itemSectionRenderer":{"contents":[{"continuationItemRenderer":{"trigger":"CONTINUATION_TRIGGER_ON_ITEM_SHOWN","continuationEndpoint":{"clickTrackingParams":"CIICELsvGAMiEwiwya3xkIiSAxXQejgFHVtaBMfKAQQPdFWj","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/next"}},"continuationCommand":{"token":"Eg0SCzVYM1ZaQktsbGg0GAYyJSIRIgs1WDNWWkJLbGxoNDAAeAJCEGNvbW1lbnRzLXNlY3Rpb24%3D","request":"CONTINUATION_REQUEST_TYPE_WATCH_NEXT"}}}}],"trackingParams":"CIICELsvGAMiEwiwya3xkIiSAxXQejgFHVtaBMc=","sectionIdentifier":"comment-item-section","targetId":"comments-section"}}],"trackingParams":"CIECELovIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},"secondaryResults":{"secondaryResults":{"results":[{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/YKewvvRJTzs/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLD8qR6cflBteOpJll4KlQXB8PgqGQ","width":168,"height":94},{"url":"https://i.ytimg.com/vi/YKewvvRJTzs/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLD_XqAbadCQEcK_eHtxKiH2t6dw-Q","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"1:29:52","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"YKewvvRJTzs","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"1시간 29분 52초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CIACEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"YKewvvRJTzs","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CIACEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CP8BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"YKewvvRJTzs"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP8BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPgBENTEDBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CP4BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CP4BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"YKewvvRJTzs","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CP4BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["YKewvvRJTzs"],"params":"CAQ%3D"}},"videoIds":["YKewvvRJTzs"],"videoCommand":{"clickTrackingParams":"CP4BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=YKewvvRJTzs","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"YKewvvRJTzs","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=60a7b0bef4494f3b\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}}}}]}}},"accessibilityText":"현재 재생목록에 추가","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP4BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CP0BEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CPgBENTEDBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}}]}}]}},"metadata":{"lockupMetadataViewModel":{"title":{"content":"The Comeback of RPC: SolidJS, TanStack, and the Future of JavaScript Frameworks - JSJ 691"},"image":{"decoratedAvatarViewModel":{"avatar":{"avatarViewModel":{"image":{"sources":[{"url":"https://yt3.ggpht.com/r4E-gcyrX9QnraJ6rUeGwEb4H-BA3E_64MkDQ6KJzjs-pGNPvUrfHfxFFuJcDw-1bM0D_Iog_A=s68-c-k-c0x00ffffff-no-rj","width":68,"height":68}]},"avatarImageSize":"AVATAR_SIZE_M"}},"a11yLabel":"Top End Devs 채널로 이동","rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPgBENTEDBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/@TopEndDevs","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCABJEQ57MIn6X3TIHIebJUw","canonicalBaseUrl":"/@TopEndDevs"}}}}}}},"metadata":{"contentMetadataViewModel":{"metadataRows":[{"metadataParts":[{"text":{"content":"Top End Devs"}}]},{"metadataParts":[{"text":{"content":"조회수 3.6천회"}},{"text":{"content":"3개월 전"}}]}],"delimiter":" • "}},"menuButton":{"buttonViewModel":{"iconName":"MORE_VERT","onTap":{"innertubeCommand":{"clickTrackingParams":"CPkBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","showSheetCommand":{"panelLoadingStrategy":{"inlineContent":{"sheetViewModel":{"content":{"listViewModel":{"listItems":[{"listItemViewModel":{"title":{"content":"현재 재생목록에 추가"},"leadingImage":{"sources":[{"clientResource":{"imageName":"ADD_TO_QUEUE_TAIL"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPwBEP6YBBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPwBEP6YBBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPwBEP6YBBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"YKewvvRJTzs","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPwBEP6YBBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["YKewvvRJTzs"],"params":"CAQ%3D"}},"videoIds":["YKewvvRJTzs"],"videoCommand":{"clickTrackingParams":"CPwBEP6YBBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=YKewvvRJTzs","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"YKewvvRJTzs","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=60a7b0bef4494f3b\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}}}}]}}}}}}},{"listItemViewModel":{"title":{"content":"재생목록에 저장"},"leadingImage":{"sources":[{"clientResource":{"imageName":"BOOKMARK_BORDER"}}]},"rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPsBEJSsCRgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","visibility":{"types":"12"}}},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPsBEJSsCRgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPsBEJSsCRgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtZS2V3dnZSSlR6cw%3D%3D"}}}}}}}}}}},{"listItemViewModel":{"title":{"content":"공유"},"leadingImage":{"sources":[{"clientResource":{"imageName":"SHARE"}}]},"rendererContext":{"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPkBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtZS2V3dnZSSlR6cw%3D%3D","commands":[{"clickTrackingParams":"CPkBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPoBEI5iIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}}}}}]}}}}}}}},"accessibilityText":"추가 작업","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPkBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TEXT","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}}}},"contentId":"YKewvvRJTzs","contentType":"LOCKUP_CONTENT_TYPE_VIDEO","rendererContext":{"loggingContext":{"loggingDirectives":{"trackingParams":"CPgBENTEDBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","visibility":{"types":"12"}}},"accessibilityContext":{"label":"The Comeback of RPC: SolidJS, TanStack, and the Future of JavaScript Frameworks - JSJ 691 1시간 29분"},"commandContext":{"onTap":{"innertubeCommand":{"clickTrackingParams":"CPgBENTEDBgAIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHMgdyZWxhdGVkSJ6slpXBrPW-5QGaAQUIARD4HcoBBA90VaM=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=YKewvvRJTzs","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"YKewvvRJTzs","nofollow":true,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr3---sn-ab02a0nfpgxapox-bh2zz.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=60a7b0bef4494f3b\u0026ip=1.208.108.242\u0026initcwndbps=3655000\u0026mt=1768293662\u0026oweuc=\u0026pxtags=Cg4KAnR4Egg1MTY2NjQ2NQ\u0026rxtags=Cg4KAnR4Egg1MTY2NjQ2Mw%2CCg4KAnR4Egg1MTY2NjQ2NA%2CCg4KAnR4Egg1MTY2NjQ2NQ%2CCg4KAnR4Egg1MTY2NjQ2Ng%2CCg4KAnR4Egg1MTY2NjQ2Nw"}}}}}}}}}},{"lockupViewModel":{"contentImage":{"thumbnailViewModel":{"image":{"sources":[{"url":"https://i.ytimg.com/vi/MvoFYuEn6SU/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLAj5XbgK08pmBosYp9NaPExufEm6g","width":168,"height":94},{"url":"https://i.ytimg.com/vi/MvoFYuEn6SU/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLAA0yDJubDcWd08tqQGduBvjsOaXw","width":336,"height":188}]},"overlays":[{"thumbnailOverlayBadgeViewModel":{"thumbnailBadges":[{"thumbnailBadgeViewModel":{"text":"37:52","badgeStyle":"THUMBNAIL_OVERLAY_BADGE_STYLE_DEFAULT","animationActivationTargetId":"MvoFYuEn6SU","animationActivationEntityKey":"Eh8veW91dHViZS9hcHAvd2F0Y2gvcGxheWVyX3N0YXRlIMMCKAE%3D","lottieData":{"url":"https://www.gstatic.com/youtube/img/lottie/audio_indicator/audio_indicator_v2.json","settings":{"loop":true,"autoplay":true}},"animatedText":"지금 재생 중","animationActivationEntitySelectorType":"THUMBNAIL_BADGE_ANIMATION_ENTITY_SELECTOR_TYPE_PLAYER_STATE","rendererContext":{"accessibilityContext":{"label":"37분 52초"}}}}],"position":"THUMBNAIL_OVERLAY_BADGE_POSITION_BOTTOM_END"}},{"thumbnailHoverOverlayToggleActionsViewModel":{"buttons":[{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"WATCH_LATER","onTap":{"innertubeCommand":{"clickTrackingParams":"CPcBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"MvoFYuEn6SU","action":"ACTION_ADD_VIDEO"}]}}},"accessibilityText":"나중에 볼 동영상","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPcBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"CHECK","onTap":{"innertubeCommand":{"clickTrackingParams":"CPYBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"MvoFYuEn6SU"}]}}},"accessibilityText":"추가됨","style":"BUTTON_VIEW_MODEL_STYLE_OVERLAY_DARK","trackingParams":"CPYBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH","type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_COMPACT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE"}},"isToggled":false,"trackingParams":"CO8BENTEDBgBIhMIsMmt8ZCIkgMV0Ho4BR1bWgTH"}},{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"ADD_TO_QUEUE_TAIL","onTap":{"innertubeCommand":{"clickTrackingParams":"CPUBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPUBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","addToPlaylistCommand":{"openMiniplayer":false,"openListPanel":true,"videoId":"MvoFYuEn6SU","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPUBEPBbIhMIsMmt8ZCIkgMV0Ho4BR1bWgTHygEED3RVow==","commandMetadata":{"webCommandMetadata":{"sendPost | 2026-01-13T08:48:29 |
https://stackoverflow.blog/author/scott-mccarty/ | Scott McCarty - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Scott McCarty April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Scott McCarty 10 comment s automation devops AI contributed Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://dev.to/ivanjurina/i-built-a-free-url-shortener-with-qr-codes-and-click-tracking-looking-for-feedback-201b#comments | I built a free URL shortener with QR codes and click tracking — looking for feedback - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Ivan Jurina Posted on Jan 12 I built a free URL shortener with QR codes and click tracking — looking for feedback # tooling # showdev # webdev # discuss Hey everyone, I'm a developer who got tired of the bloated dashboards and paywalls on most link shorteners, so I built my own. mnml.ink — does what it says: Shorten URLs Generate QR codes Track clicks & basic stats No sign-up required for basic use It's fast, free, and I tried to keep it as simple as possible. Would love honest feedback — what features would make this actually useful for your workflow? Anything obviously missing? https://mnml.ink/ Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Ivan Jurina Follow Skateboarding and programming enthusiast Education Mendel University Work Developer Joined Apr 19, 2022 Trending on DEV Community Hot AI should not be in Code Editors # programming # ai # productivity # discuss Stop Overengineering: How to Write Clean Code That Actually Ships 🚀 # discuss # javascript # programming # webdev The FAANG is dead💀 # webdev # programming # career # faang 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://www.instagram.com/p/DJCy2XNT5hv/?utm_source=ig_web_button_share_sheet&hl=fr-ca | Instagram Close By continuing, you agree to Instagram's Terms of Use and Privacy Policy . Instagram Log In Sign Up Meta About Blog Jobs Help API Privacy Terms Locations Instagram Lite Meta AI Threads Contact Uploading & Non-Users Meta Verified English Down chevron icon Afrikaans العربية Čeština Dansk Deutsch Ελληνικά English English (UK) Español (España) Español فارسی Suomi Français עברית Bahasa Indonesia Italiano 日本語 한국어 Bahasa Melayu Norsk Nederlands Polski Português (Brasil) Português (Portugal) Русский Svenska ภาษาไทย Filipino Türkçe 中文(简体) 中文(台灣) বাংলা ગુજરાતી हिन्दी Hrvatski Magyar ಕನ್ನಡ മലയാളം मराठी नेपाली ਪੰਜਾਬੀ සිංහල Slovenčina தமிழ் తెలుగు اردو Tiếng Việt 中文(香港) Български Français (Canada) Română Српски Українська © 2026 Instagram from Meta {"require":[["ScheduledServerJS","handle",null,[{"__bbox":{"require":[["AsyncData","resolve",[],["adp_WebWorkerV2HasteResponsePreloader_IGDAWMainWebWorkerBundle_696606d7523b40631003989",{"data":{"__bbox":{"hrp":{"hsrp":{"hsdp":{"bxData":{"30933":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/ye\/r\/COs9e0Kj0ic.wasm"},"31853":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/yf\/r\/SOSPkPfT1k-.wasm"},"237":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/yR\/r\/ayqr5HQtlkb.wasm"},"6946":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/yf\/r\/rogm88TRRiw.wasm"},"33861":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/yj\/r\/wP_Nd8029HG.wasm"},"30948":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/yr\/r\/gbPXWYVntw6.wasm"},"32099":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/y1\/r\/F52bvVmXVXq.wasm"},"77770":{"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/ye\/r\/au6vCkajLkU.wasm"}},"clpData":{"6476":{"r":1000,"s":1},"1744178":{"r":1,"s":1},"1838142":{"r":1,"s":1},"4266":{"r":1,"s":1},"5721":{"r":1,"s":1},"5727":{"r":1,"s":1},"5728":{"r":1,"s":1},"5729":{"r":1,"s":1},"1848815":{"r":10000,"s":1},"1399":{"r":1,"s":1},"1828905":{"r":1},"1271":{"r":1,"s":1},"3226":{"r":1,"s":1},"6934":{"r":1,"s":1},"1744057":{"r":500,"s":1},"1744058":{"r":5000,"s":1},"1744059":{"r":10000,"s":1},"1744060":{"r":1000,"s":1},"1814852":{"r":1},"5722":{"r":1,"s":1},"5723":{"r":1,"s":1},"5720":{"r":1,"s":1},"5725":{"r":1,"s":1},"5726":{"r":1,"s":1},"1109":{"r":1,"s":1},"5080":{"r":1,"s":1},"1744234":{"r":1},"5829":{"r":1,"s":1},"5831":{"r":1,"s":1},"1962341":{"r":1,"s":1},"177":{"r":1,"s":1},"1823926":{"r":1,"s":1},"819":{"r":1,"s":1},"1857112":{"r":1},"1755537":{"r":1}},"gkxData":{"4":{"result":false,"hash":null},"148":{"result":true,"hash":null},"196":{"result":false,"hash":null},"269":{"result":false,"hash":null},"380":{"result":false,"hash":null},"414":{"result":false,"hash":null},"503":{"result":false,"hash":null},"704":{"result":false,"hash":null},"834":{"result":false,"hash":null},"1006":{"result":true,"hash":null},"1154":{"result":true,"hash":null},"1174":{"result":false,"hash":null},"1196":{"result":false,"hash":null},"1326":{"result":false,"hash":null},"1327":{"result":true,"hash":null},"1371":{"result":false,"hash":null},"1458":{"result":true,"hash":null},"1514":{"result":false,"hash":null},"1624":{"result":false,"hash":null},"1760":{"result":true,"hash":null},"1800":{"result":false,"hash":null},"1842":{"result":true,"hash":null},"1910":{"result":false,"hash":null},"2067":{"result":false,"hash":null},"2160":{"result":false,"hash":null},"2400":{"result":false,"hash":null},"2419":{"result":true,"hash":null},"2456":{"result":false,"hash":null},"2656":{"result":false,"hash":null},"2661":{"result":false,"hash":null},"2792":{"result":false,"hash":null},"2815":{"result":false,"hash":null},"2909":{"result":false,"hash":null},"2947":{"result":false,"hash":null},"3053":{"result":true,"hash":null},"3176":{"result":false,"hash":null},"3193":{"result":false,"hash":null},"3272":{"result":false,"hash":null},"3282":{"result":false,"hash":null},"3378":{"result":false,"hash":null},"3570":{"result":true,"hash":null},"3577":{"result":true,"hash":null},"3739":{"result":false,"hash":null},"4008":{"result":false,"hash":null},"4022":{"result":false,"hash":null},"4070":{"result":false,"hash":null},"4225":{"result":false,"hash":null},"4258":{"result":false,"hash":null},"4337":{"result":false,"hash":null},"4444":{"result":false,"hash":null},"4741":{"result":true,"hash":null},"4778":{"result":true,"hash":null},"4792":{"result":false,"hash":null},"4996":{"result":false,"hash":null},"5039":{"result":false,"hash":null},"5113":{"result":true,"hash":null},"5163":{"result":false,"hash":null},"5380":{"result":false,"hash":null},"5415":{"result":false,"hash":null},"5519":{"result":false,"hash":null},"5607":{"result":false,"hash":null},"5675":{"result":false,"hash":null},"5679":{"result":false,"hash":null},"5782":{"result":false,"hash":null},"6123":{"result":false,"hash":null},"6236":{"result":false,"hash":null},"6275":{"result":false,"hash":null},"6636":{"result":true,"hash":null},"6650":{"result":false,"hash":null},"6754":{"result":false,"hash":null},"6756":{"result":false,"hash":null},"6795":{"result":false,"hash":null},"6817":{"result":false,"hash":null},"6840":{"result":false,"hash":null},"7137":{"result":false,"hash":null},"7170":{"result":false,"hash":null},"7313":{"result":false,"hash":null},"7445":{"result":false,"hash":null},"7695":{"result":true,"hash":null},"7742":{"result":false,"hash":null},"7816":{"result":false,"hash":null},"7840":{"result":true,"hash":null},"7918":{"result":false,"hash":null},"8029":{"result":false,"hash":null},"8048":{"result":false,"hash":null},"8068":{"result":false,"hash":null},"8174":{"result":false,"hash":null},"8216":{"result":false,"hash":null},"8334":{"result":false,"hash":null},"8460":{"result":false,"hash":null},"8483":{"result":false,"hash":null},"8566":{"result":false,"hash":null},"8737":{"result":false,"hash":null},"8869":{"result":false,"hash":null},"9063":{"result":false,"hash":null},"9159":{"result":false,"hash":null},"9338":{"result":true,"hash":null},"9339":{"result":true,"hash":null},"9340":{"result":false,"hash":null},"9396":{"result":false,"hash":null},"9699":{"result":false,"hash":null},"9841":{"result":true,"hash":null},"9855":{"result":true,"hash":null},"9921":{"result":true,"hash":null},"10029":{"result":false,"hash":null},"10133":{"result":false,"hash":null},"10182":{"result":false,"hash":null},"10233":{"result":false,"hash":null},"10326":{"result":false,"hash":null},"10465":{"result":false,"hash":null},"10665":{"result":false,"hash":null},"10726":{"result":false,"hash":null},"10839":{"result":false,"hash":null},"11557":{"result":false,"hash":null},"11582":{"result":false,"hash":null},"11610":{"result":false,"hash":null},"11685":{"result":false,"hash":null},"11826":{"result":false,"hash":null},"11869":{"result":false,"hash":null},"12236":{"result":false,"hash":null},"12286":{"result":false,"hash":null},"12288":{"result":false,"hash":null},"12290":{"result":false,"hash":null},"12291":{"result":false,"hash":null},"12292":{"result":false,"hash":null},"12293":{"result":false,"hash":null},"12294":{"result":false,"hash":null},"12296":{"result":false,"hash":null},"12297":{"result":false,"hash":null},"12343":{"result":false,"hash":null},"12547":{"result":true,"hash":null},"12572":{"result":false,"hash":null},"12661":{"result":false,"hash":null},"12766":{"result":false,"hash":null},"12896":{"result":true,"hash":null},"12996":{"result":false,"hash":null},"13037":{"result":false,"hash":null},"13090":{"result":false,"hash":null},"13108":{"result":false,"hash":null},"13409":{"result":false,"hash":null},"13484":{"result":false,"hash":null},"13725":{"result":false,"hash":null},"14417":{"result":false,"hash":null},"14470":{"result":false,"hash":null},"14634":{"result":true,"hash":null},"14697":{"result":true,"hash":null},"14711":{"result":true,"hash":null},"14887":{"result":false,"hash":null},"14925":{"result":false,"hash":null},"14926":{"result":false,"hash":null},"14927":{"result":false,"hash":null},"15065":{"result":false,"hash":null},"15207":{"result":false,"hash":null},"15236":{"result":true,"hash":null},"15418":{"result":true,"hash":null},"15620":{"result":false,"hash":null},"15740":{"result":true,"hash":null},"15745":{"result":false,"hash":null},"15957":{"result":false,"hash":null},"15959":{"result":true,"hash":null},"16129":{"result":false,"hash":null},"16269":{"result":false,"hash":null},"16464":{"result":false,"hash":null},"16596":{"result":true,"hash":null},"16674":{"result":false,"hash":null},"16675":{"result":false,"hash":null},"16990":{"result":false,"hash":null},"17154":{"result":true,"hash":null},"17181":{"result":false,"hash":null},"17201":{"result":false,"hash":null},"17219":{"result":false,"hash":null},"17337":{"result":true,"hash":null},"17440":{"result":false,"hash":null},"17703":{"result":true,"hash":null},"17846":{"result":false,"hash":null},"18296":{"result":false,"hash":null},"18428":{"result":false,"hash":null},"18463":{"result":false,"hash":null},"18494":{"result":true,"hash":null},"19024":{"result":true,"hash":null},"19103":{"result":true,"hash":null},"19108":{"result":false,"hash":null},"19338":{"result":true,"hash":null},"19417":{"result":false,"hash":null},"19586":{"result":true,"hash":null},"19588":{"result":false,"hash":null},"19609":{"result":false,"hash":null},"19866":{"result":false,"hash":null},"19892":{"result":true,"hash":null},"20053":{"result":false,"hash":null},"20157":{"result":false,"hash":null},"20483":{"result":false,"hash":null},"20484":{"result":false,"hash":null},"20485":{"result":false,"hash":null},"20836":{"result":false,"hash":null},"20863":{"result":false,"hash":null},"20864":{"result":true,"hash":null},"20865":{"result":false,"hash":null},"20879":{"result":false,"hash":null},"20911":{"result":false,"hash":null},"20915":{"result":false,"hash":null},"20916":{"result":false,"hash":null},"20918":{"result":false,"hash":null},"20919":{"result":true,"hash":null},"20920":{"result":false,"hash":null},"20921":{"result":true,"hash":null},"20922":{"result":true,"hash":null},"20923":{"result":true,"hash":null},"20924":{"result":true,"hash":null},"20925":{"result":true,"hash":null},"20926":{"result":true,"hash":null},"20929":{"result":true,"hash":null},"20935":{"result":true,"hash":null},"20936":{"result":false,"hash":null},"20942":{"result":false,"hash":null},"20980":{"result":false,"hash":null},"20981":{"result":false,"hash":null},"20982":{"result":false,"hash":null},"20983":{"result":false,"hash":null},"20984":{"result":true,"hash":null},"21003":{"result":false,"hash":null},"21004":{"result":false,"hash":null},"21005":{"result":false,"hash":null},"21043":{"result":false,"hash":null},"21050":{"result":false,"hash":null},"21051":{"result":false,"hash":null},"21053":{"result":false,"hash":null},"21055":{"result":false,"hash":null},"21056":{"result":false,"hash":null},"21057":{"result":false,"hash":null},"21058":{"result":true,"hash":null},"21063":{"result":false,"hash":null},"21072":{"result":false,"hash":null},"21089":{"result":false,"hash":null},"21095":{"result":false,"hash":null},"21106":{"result":true,"hash":null},"21107":{"result":false,"hash":null},"21114":{"result":false,"hash":null},"21115":{"result":false,"hash":null},"21117":{"result":false,"hash":null},"21118":{"result":false,"hash":null},"21119":{"result":false,"hash":null},"21120":{"result":true,"hash":null},"21122":{"result":false,"hash":null},"21123":{"result":true,"hash":null},"21124":{"result":false,"hash":null},"22803":{"result":false,"hash":null},"22826":{"result":false,"hash":null},"22843":{"result":false,"hash":null},"22875":{"result":false,"hash":null},"22877":{"result":false,"hash":null},"22885":{"result":false,"hash":null},"22968":{"result":false,"hash":null},"22979":{"result":true,"hash":null},"23390":{"result":false,"hash":null},"23403":{"result":false,"hash":null},"23404":{"result":false,"hash":null},"23405":{"result":false,"hash":null},"23414":{"result":false,"hash":null},"23903":{"result":false,"hash":null},"23906":{"result":false,"hash":null},"23909":{"result":false,"hash":null},"23910":{"result":false,"hash":null},"23914":{"result":false,"hash":null},"23915":{"result":false,"hash":null},"23924":{"result":false,"hash":null},"23941":{"result":true,"hash":null},"23949":{"result":false,"hash":null},"23955":{"result":true,"hash":null},"23956":{"result":false,"hash":null},"23960":{"result":false,"hash":null},"23961":{"result":false,"hash":null},"23973":{"result":false,"hash":null},"23974":{"result":false,"hash":null},"23975":{"result":false,"hash":null},"23986":{"result":false,"hash":null},"23999":{"result":false,"hash":null},"24021":{"result":false,"hash":null},"24025":{"result":false,"hash":null},"24027":{"result":false,"hash":null},"24028":{"result":false,"hash":null},"24113":{"result":false,"hash":null},"24151":{"result":false,"hash":null},"24163":{"result":false,"hash":null},"24215":{"result":false,"hash":null},"26332":{"result":false,"hash":null},"26340":{"result":false,"hash":null},"26341":{"result":false,"hash":null},"26342":{"result":false,"hash":null},"26373":{"result":false,"hash":null},"26374":{"result":false,"hash":null},"26382":{"result":false,"hash":null},"26383":{"result":false,"hash":null},"26390":{"result":false,"hash":null},"33008":{"result":true,"hash":null}},"ixData":{"1876411":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yd\/r\/3mD7kKai_7W.gif","width":12,"height":12},"1876412":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y1\/r\/mHADa0fT0mI.gif","width":16,"height":16},"1876413":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yV\/r\/ZY0eC865SgX.gif","width":20,"height":20},"1876414":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y8\/r\/M3mvaC7u8oH.gif","width":24,"height":24},"1876415":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yL\/r\/hVe2HmwMRpE.gif","width":32,"height":32},"1876416":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yC\/r\/yFaaylccZ5L.gif","width":48,"height":48},"1876418":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yk\/r\/96GJYGbUDCJ.gif","width":72,"height":72},"1876419":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yS\/r\/NiR8M1k4AVU.gif","width":12,"height":12},"1876420":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ym\/r\/FNERtXIk9xp.gif","width":16,"height":16},"1876421":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yJ\/r\/l2FWxc8ihQj.gif","width":20,"height":20},"1876422":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yo\/r\/Io_N1z4MXYh.gif","width":24,"height":24},"1876423":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yD\/r\/-1hifBvDgEQ.gif","width":32,"height":32},"1876424":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yG\/r\/RcIiVWWukEr.gif","width":48,"height":48},"1876426":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yP\/r\/9ISCYYcy94m.gif","width":72,"height":72},"1876427":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yU\/r\/MStXnCtsaSe.gif","width":12,"height":12},"1876428":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y6\/r\/dw2egiKdoVV.gif","width":16,"height":16},"1876429":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yA\/r\/1DbfjOftY0d.gif","width":20,"height":20},"1876430":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yi\/r\/2uPGz8a6lb6.gif","width":24,"height":24},"1876431":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yw\/r\/60r9oPEvxiL.gif","width":32,"height":32},"1876432":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yM\/r\/NlAFhiEx3a1.gif","width":48,"height":48},"1876434":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yx\/r\/uzrQzxgD_Bg.gif","width":72,"height":72},"1876435":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yM\/r\/TtXj9IXnkoK.gif","width":12,"height":12},"1876436":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yy\/r\/HNs8yq0QiXE.gif","width":16,"height":16},"1876437":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yT\/r\/ay_drQe6StD.gif","width":20,"height":20},"1876438":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y4\/r\/iACDMhAROS_.gif","width":24,"height":24},"1876439":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yy\/r\/WEhNL1y2zoZ.gif","width":32,"height":32},"1876440":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y-\/r\/mAeZkO4yhqj.gif","width":48,"height":48},"1876442":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yl\/r\/79uB7ciX8vY.gif","width":72,"height":72},"1876443":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yG\/r\/dzn6it4Fw3p.gif","width":12,"height":12},"1876444":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yc\/r\/wqjQpFb4tea.gif","width":16,"height":16},"1876445":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yk\/r\/yy3mR2PXKrn.gif","width":20,"height":20},"1876446":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yl\/r\/gTdm7zPKz-c.gif","width":24,"height":24},"1876447":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ym\/r\/kdaft251gQ_.gif","width":32,"height":32},"1876448":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yG\/r\/6-FTd4KBtOk.gif","width":48,"height":48},"1876450":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yq\/r\/Tks_lRPtYc-.gif","width":72,"height":72},"1876451":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yK\/r\/Bys0xcVibDa.gif","width":12,"height":12},"1876452":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/Wk0dcHGH6EG.gif","width":16,"height":16},"1876453":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ys\/r\/aOTs7vt2hEc.gif","width":20,"height":20},"1876454":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yh\/r\/wVjfNbGZ3CH.gif","width":24,"height":24},"1876455":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yw\/r\/oT6wM_vuQNQ.gif","width":32,"height":32},"1876456":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yp\/r\/ac61i44rSWK.gif","width":48,"height":48},"1876458":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yg\/r\/ZH27Vvjc9-u.gif","width":72,"height":72},"1940508":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y3\/r\/ycQ2OPoZwUA.gif","width":64,"height":64},"1940509":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yg\/r\/8kyIVWHZW-b.gif","width":64,"height":64},"1940510":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yK\/r\/8gPN8wBD9yB.gif","width":64,"height":64},"1940511":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yG\/r\/WtK_u51t3nM.gif","width":64,"height":64},"1940512":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yj\/r\/JYwEre3ewp7.gif","width":64,"height":64},"1940513":{"sprited":0,"uri":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yu\/r\/M2HDLLPAUWl.gif","width":64,"height":64}},"metaconfigData":{"179":{"value":false},"191":{"value":false},"32":{"value":false},"36":{"value":false},"10":{"value":0},"15":{"value":false},"62":{"value":false},"78":{"value":false},"87":{"value":false},"99":{"value":false},"148":{"value":false},"156":{"value":false},"258":{"value":false},"262":{"value":false},"271":{"value":false},"73":{"value":false},"57":{"value":0},"84":{"value":""},"100":{"value":0},"101":{"value":0},"102":{"value":0},"109":{"value":0},"110":{"value":0},"111":{"value":0},"113":{"value":""},"119":{"value":0},"120":{"value":false},"121":{"value":0},"122":{"value":0},"123":{"value":0},"124":{"value":0},"125":{"value":0},"126":{"value":0},"127":{"value":0},"128":{"value":0},"129":{"value":0},"130":{"value":""},"131":{"value":0},"133":{"value":0},"134":{"value":0},"143":{"value":false},"154":{"value":false},"234":{"value":false},"206":{"value":false}},"qexData":{"3999":{"r":null,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"135":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"161":{"r":null},"662":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"954":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"1244":{"r":null,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"440":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"468":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"603":{"r":null,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"923":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"2072":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"2094":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"4006":{"r":"NONE","l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"507":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"853":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"855":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"940":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"263":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"18":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"23":{"r":0,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"121":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"125":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"670":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"2071":{"r":"default","l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"2082":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"401":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"729":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"ig\",\"gks\":[],\"qe\":null}"},"2097":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"2100":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"2103":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"104":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"128":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"344":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"388":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"}},"qplData":{"1438":{"r":100},"2062":{"r":100},"6155":{"r":1000},"6702":{"r":1},"310":{"r":1},"419":{"r":1},"1127":{"r":12},"1551":{"r":1},"6204":{"r":7},"106":{},"112":{},"807":{},"808":{},"2862":{},"2909":{},"2716":{"r":500},"418":{"r":1},"115":{"r":1000000},"118":{"r":100000},"119":{"r":10000},"560":{"r":100},"718":{"m":3,"r":1},"905":{"r":1000},"1566":{"r":200},"2028":{},"2955":{"r":10000},"83":{"m":3,"r":4},"124":{"r":1000},"131":{"m":3,"r":1},"136":{"r":1000},"150":{"r":1000},"494":{"r":10000},"540":{"r":10},"804":{"r":10},"813":{"r":1000},"814":{},"948":{"r":1},"1004":{"r":100},"1154":{"r":1000},"1204":{"r":10},"1406":{"r":100},"2007":{"r":100},"2195":{},"2352":{"r":1},"5664":{"r":4},"11176":{},"12933":{"r":1},"16":{"r":1},"27":{"r":1},"31":{"r":1},"141":{"r":1},"143":{"r":5},"164":{"r":1},"263":{"r":1},"272":{"r":1},"295":{"r":1},"296":{"r":1},"378":{"r":1},"409":{"r":1},"504":{"r":1},"817":{"r":1},"827":{"r":100},"829":{"r":1000},"909":{"r":100},"1069":{"r":1000},"1118":{"r":500},"1167":{"r":1000},"1285":{"r":5},"1290":{"r":1},"1329":{"r":1},"1331":{"r":10000},"1407":{"r":100},"1454":{"r":100},"1460":{"r":1},"1488":{"r":1},"1519":{"r":1},"1530":{},"1646":{"r":1},"1876":{"r":100},"1939":{"r":1},"2143":{"r":1},"2163":{"r":1},"2200":{"r":2000},"2275":{"r":5000},"2395":{"r":5000000},"2432":{"r":1000},"2454":{},"2558":{},"2586":{"r":1},"2612":{},"2684":{"r":100},"2698":{"r":5000},"2703":{"r":1},"2704":{"r":1},"2715":{"r":1},"2768":{"r":1},"2778":{"r":10000},"2806":{"r":1000},"2831":{"r":100},"2832":{},"2834":{"r":10},"2835":{"r":1},"2850":{"r":1},"2859":{},"2910":{"r":1},"2968":{},"2995":{"r":1},"3055":{"r":1},"3099":{},"3100":{"r":1},"3101":{},"3102":{},"3103":{},"3104":{},"3105":{"r":1},"3106":{"r":1},"3107":{},"3108":{"r":1000000},"3109":{"r":1000000},"3110":{"r":1000000},"3111":{},"3112":{},"3114":{},"3115":{},"3116":{},"3117":{},"3118":{},"3120":{},"3121":{},"3122":{"r":1},"3124":{},"3126":{},"3127":{},"3128":{"r":1},"3129":{"r":1},"3131":{},"3132":{"r":1},"3133":{},"3134":{"r":700},"3135":{"r":1000},"3136":{"r":1},"3137":{"r":1},"3138":{"r":1},"3140":{"r":1},"3212":{"r":1},"3232":{"r":1},"2369":{"r":100},"615":{"r":1},"691":{"r":1000},"970":{"r":10},"971":{"r":1},"1410":{},"1562":{"r":1},"2398":{"r":1000},"2399":{"r":100},"2667":{"r":1},"2729":{"r":1},"3222":{"r":1000},"3249":{"r":100},"3287":{"r":1},"3294":{"r":1},"1081":{"r":1},"1751":{"r":1},"1328":{"r":1},"1476":{"r":1},"1216":{"r":1},"2242":{"r":10000},"2258":{"r":1000000},"2267":{"r":10000},"2268":{"r":10000},"2396":{"r":10000},"2408":{"r":10000},"2853":{},"4750":{"r":1},"2919":{"r":100},"3037":{"r":1},"994":{"r":1}},"justknobxData":{"1276":{"r":true},"1399":{"r":1},"1400":{"r":30000},"1401":{"r":10000},"1402":{"r":86400000},"1403":{"r":100},"1404":{"r":2000},"2596":{"r":120000},"1707":{"r":true},"1979":{"r":true},"4177":{"r":true},"1417":{"r":true},"2269":{"r":true},"3323":{"r":true},"3409":{"r":true},"3414":{"r":true},"3483":{"r":true},"3946":{"r":4},"1495":{"r":false},"4240":{"r":120000},"5256":{"r":true},"168":{"r":60000},"1410":{"r":true},"187":{"r":4096},"652":{"r":300},"1716":{"r":126},"2033":{"r":720},"2144":{"r":2048},"2338":{"r":80},"2340":{"r":80},"2545":{"r":128},"2635":{"r":true},"3166":{"r":100},"3300":{"r":10000},"3415":{"r":60000},"3424":{"r":false},"3427":{"r":90},"3594":{"r":1000},"4087":{"r":true},"4988":{"r":1048576},"5255":{"r":false},"847":{"r":25000},"1970":{"r":6},"1971":{"r":10},"1972":{"r":1500},"2141":{"r":5},"2240":{"r":10000},"3218":{"r":10},"3264":{"r":30000},"3429":{"r":10000},"3546":{"r":300000},"3614":{"r":60000},"3720":{"r":true},"4337":{"r":20000},"4338":{"r":10000},"4339":{"r":500},"4535":{"r":50},"4536":{"r":50},"4538":{"r":10},"4539":{"r":10000},"4540":{"r":100},"96":{"r":true},"154":{"r":true},"467":{"r":200},"862":{"r":true},"960":{"r":false},"1143":{"r":5000},"1146":{"r":true},"1405":{"r":600000},"1414":{"r":true},"1453":{"r":10000},"1460":{"r":60000},"1596":{"r":7},"1676":{"r":20},"2045":{"r":300000},"2366":{"r":60000},"2368":{"r":50},"2392":{"r":1},"2477":{"r":250},"2539":{"r":100},"2722":{"r":1},"2800":{"r":30000},"2950":{"r":500000},"3047":{"r":600000},"3092":{"r":100},"3177":{"r":20},"3227":{"r":true},"3472":{"r":300000},"3485":{"r":200000},"3573":{"r":5},"3763":{"r":10000},"3895":{"r":true},"3949":{"r":60000},"3952":{"r":1},"3957":{"r":8},"3969":{"r":100},"3970":{"r":50},"3973":{"r":450},"3977":{"r":60},"3981":{"r":450},"4207":{"r":3600},"4405":{"r":30000},"4688":{"r":30},"4841":{"r":10},"4947":{"r":true},"5155":{"r":true},"5177":{"r":10},"5394":{"r":false},"5395":{"r":5000},"3914":{"r":10},"308":{"r":600000},"1008":{"r":true},"1132":{"r":21},"1786":{"r":20},"1889":{"r":180000},"1938":{"r":300000},"1980":{"r":true},"2027":{"r":true},"2367":{"r":1000},"2444":{"r":120000},"2606":{"r":30000},"2608":{"r":300000},"2645":{"r":1},"2646":{"r":10000},"2647":{"r":5000},"2671":{"r":50},"2678":{"r":5},"2859":{"r":60000},"2860":{"r":100},"2865":{"r":true},"2928":{"r":false},"2954":{"r":20},"3065":{"r":7},"3206":{"r":300000},"3282":{"r":true},"3325":{"r":100},"3366":{"r":200},"3455":{"r":1},"3525":{"r":100},"3526":{"r":true},"3587":{"r":false},"3679":{"r":100},"3748":{"r":10},"3951":{"r":2},"4094":{"r":2},"4183":{"r":5000},"4211":{"r":60000},"4369":{"r":false},"4370":{"r":true},"4553":{"r":90000},"4597":{"r":1000},"4600":{"r":5},"4703":{"r":10000},"4743":{"r":100},"4744":{"r":25},"1601":{"r":true},"946":{"r":true},"1310":{"r":true},"4226":{"r":100000},"3868":{"r":60000},"776":{"r":false},"5261":{"r":true},"803":{"r":true},"1099":{"r":true},"317":{"r":16},"2595":{"r":0},"3244":{"r":4000},"4662":{"r":400},"4146":{"r":false},"5277":{"r":true},"3335":{"r":true},"432":{"r":true}}},"hblp":{"consistency":{"rev":1031920881},"rsrcMap":{"Y7kF\/NS":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yt\/r\/MyF1Cp9roAV.js","c":1,"p":":1","m":"1031920881_main","prelude":1},"hGTKnd\/":{"type":"css","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v5\/y8\/l\/0,cross\/J3FUI33fjDQ_CeKo1gBhPdfgQe914iiBfONMKn3YhINqU49pVNahkCk.css","c":1,"p":":8,3,40,39,38","m":"1031920881_main"},"0X7MTki":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ime94\/yz\/l\/en_US\/rIL06yzusM4HPUK2-uS5MZrSsuTIWgirRnr1K62wrP83M5Emjr-935ylHnbyewHU9FpZD8TYpFtr_GzrBUm-HRVe-kCjjlQ_TdZfg13Jy6faM3dL1conmM5B5kxB56esr_XmmluV7afi-eie-bY0K04sVni3WC72IcjQSksxDCe3I1HYJmwBGYZTX1_LrUIo6P-HlkzkTUyyZ-Utty-ayoV4rCWTsW1OSSeKLsXucK0FzTFzrEmese8PpaA6YZDMWSOW4VZX7odNDboPV5nrlJGlfhZL0osiDtUWwwLlT9ghhQwTjNukKYQPeEYW0s-RlZoqThUVBt.js","c":1,"p":":22,26,53,15,9,21,4,79,24,28,18,43,42,47,14,35,12,27,5,17,55,23,19,74,2,11,34,6,20,13","m":"1031920881_main"},"F6\/Lqf+":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iYcR4\/yM\/l\/en_US\/uzXNlTbcM6lURI3GIb_Gc2sW7_eD92aVJKnB1PoE4beLKGlXFkE6Z7UZoI2kgze1tr.js","c":1,"p":":75,36,29,76,7,25","m":"1031920881_main"},"39VnefO":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iLok4\/yb\/l\/en_US\/HSlhMa4diYZU5wQMrPMfMHF_HMlhVCXGak47Rc3xnxbfrrCxjEFdRGj2qlJiMIJI3rCKsLT24hAEx74o92dGxzJ_.js","c":1,"p":":52,33,16,48,78,10,31,80","m":"1031920881_main"},"5up3qbB":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4isZf4\/yp\/l\/en_US\/FvA_sbDXyfk.js","c":1,"p":":58","m":"1031920881_main"},"4\/fChtY":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yM\/r\/Xwavpw8z2is.js","c":1,"p":":31507","m":"1031920881_longtail"},"LTzphN+":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iksA4\/yU\/l\/en_US\/Xu2cDeqTJht.js","c":1,"p":":30","m":"1031920881_main"},"Q\/NLE8B":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yE\/r\/ZpM9suqmuD_.js","c":1,"p":":30417","m":"1031920881_longtail"},"iW020u0":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iUGu4\/yL\/l\/en_US\/3D3T9pYeQnM.js","c":1,"p":":37","m":"1031920881_main"},"+OffgwQ":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yC\/r\/RBv2_HTVe6i.js","c":1,"p":":31505","m":"1031920881_longtail"},"mdcDkEc":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ic5v4\/yB\/l\/en_US\/ajoRgcIqSmF.js","c":1,"p":":71","m":"1031920881_main"},"JGnLOk1":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yl\/r\/kzD0FEHb09j.js","c":1,"p":":159","m":"1031920881_main"},"yyhy4aU":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yZ\/r\/-1kmgQhHwhK.js","c":1,"p":":31506","m":"1031920881_longtail"},"eyot5CC":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yL\/r\/FHuDCAa2FwD.js","c":1,"p":":122","m":"1031920881_main"},"54VwGsP":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i3Ty4\/yL\/l\/en_US\/r6RbL19Oced.js","c":1,"p":":189","m":"1031920881_main"},"+pKf1S4":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iUhJ4\/yQ\/l\/en_US\/m9fJdPSCX_i.js","c":1,"p":":109","m":"1031920881_main"},"0\/Dcv0N":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yx\/r\/yvS82wPOlzJ.js","c":1,"p":":31504","m":"1031920881_longtail"},"J2lSIbp":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iPRb4\/yc\/l\/en_US\/5CVEjIEWK-s.js","c":1,"p":":83","m":"1031920881_main"},"jn5dc6L":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ivww4\/yv\/l\/en_US\/n_R5_AoK2O4.js","c":1,"p":":1226","m":"1031920881_main"},"dtqjoDV":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ys\/r\/H-HIBQRAJs6.js","c":1,"p":":183","m":"1031920881_main"},"2ckvraP":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yB\/r\/3_lQZ1zxh-j.js","c":1,"p":":31442","m":"1031920881_longtail"},"ot01GdI":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yJ\/r\/RY9nBnN_1VD.js","c":1,"p":":31399","m":"1031920881_longtail"},"S9C9Rft":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yx\/r\/MMkRHcwq0M-.js","c":1,"p":":31382","m":"1031920881_longtail"},"gPm1+Zq":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iKzn4\/yI\/l\/en_US\/OEJdxCLBoaT.js","c":1,"p":":457","m":"1031920881_main"},"C5BgXyH":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yx\/r\/-Ek2btx-qUe.js","c":1,"p":":31488","m":"1031920881_longtail"},"jXK4trC":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/ZIet57V2H-N.js","c":1,"p":":31443","m":"1031920881_longtail"},"lrf6t4Z":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y6\/r\/R7PZTzW4IzN.js","c":1,"p":":31379","m":"1031920881_longtail"},"MO4tbsc":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/bq6wzgEayB3.js","c":1,"p":":179","m":"1031920881_main"},"X8yJvz\/":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ihIp4\/ye\/l\/en_US\/eN3TEecBsng.js","c":1,"p":":114","m":"1031920881_main"},"0tr8X2v":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i1m04\/yi\/l\/en_US\/GAoR9357Wzj.js","c":1,"p":":30570","m":"1031920881_longtail"},"eGbZ8YT":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yV\/r\/HP4q9iBdabu.js","c":1,"p":":30569","m":"1031920881_longtail"},"cPdYdME":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iWzq4\/yA\/l\/en_US\/UgqvYJcORzv.js","c":1,"p":":64","m":"1031920881_main"},"63yQZSF":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yp\/r\/ivmzpuqp_nv.js","c":1,"p":":31502","m":"1031920881_longtail"},"YFEqPE\/":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yj\/r\/mwH9EyY7M8u.js","c":1,"p":":31489","m":"1031920881_longtail"},"+HUKfNX":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yM\/r\/X06UnxS6Lkx.js","c":1,"p":":31498","m":"1031920881_longtail"},"mDE6Z1N":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yP\/r\/LZFGsCmbYDj.js","c":1,"p":":31501","m":"1031920881_longtail"},"5J\/P95k":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/yGkPfsbzf2W.js","c":1,"p":":31500","m":"1031920881_longtail"},"oRx1asa":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yh\/r\/iHyngubAurh.js","c":1,"p":":31503","m":"1031920881_longtail"},"\/aRLGlk":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ie4-4\/yt\/l\/en_US\/Dj3HwRXizZg.js","c":1,"p":":432","m":"1031920881_main"},"lb5Q3a1":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yl\/r\/5KZei_ntnYj.js","c":1,"p":":1305","m":"1031920881_main"},"ALBhwn6":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iDyq4\/yR\/l\/en_US\/XSxKyNnhGVL.js","c":1,"p":":27969","m":"1031920881_longtail"},"Wg3WAEH":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i-wR4\/yw\/l\/en_US\/Mb5sniT94ol.js","c":1,"p":":131","m":"1031920881_main"},"t+3QBPm":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yK\/r\/wZE6aXHOakE.js","c":1,"p":":25500","m":"1031920881_longtail"},"CaW3ujw":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yt\/r\/qF75LFfKDEr.js","c":1,"p":":25496","m":"1031920881_longtail"},"LI1H\/tm":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i1Au4\/yk\/l\/en_US\/hsMzxgWM8md.js","c":1,"p":":138","m":"1031920881_main"},"8Xwviui":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i__L4\/yX\/l\/en_US\/XD7yXVnnR8A.js","c":1,"p":":196","m":"1031920881_main"},"V1mU87K":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iE5l4\/y8\/l\/en_US\/baEN-PSi1-_.js","c":1,"p":":946","m":"1031920881_main"},"M65WC6L":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ip674\/yA\/l\/en_US\/_sk0HKmaluo.js","c":1,"p":":86","m":"1031920881_main"},"ogGbRC5":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iYD_4\/yI\/l\/en_US\/JOKTXyfLLvc.js","c":1,"p":":238","m":"1031920881_main"},"YX4FyO6":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iNTD4\/yt\/l\/en_US\/jfYywkLoD7k.js","c":1,"p":":85","m":"1031920881_main"},"DnHy4+W":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iW5m4\/yw\/l\/en_US\/tneglfoiVHw.js","c":1,"p":":177","m":"1031920881_main"},"XNaS9lQ":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yq\/r\/7hkI0Nmow2I.js","c":1,"p":":27289","m":"1031920881_longtail"},"WwCPTJr":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yb\/r\/VPQk0MD3qaG.js","c":1,"p":":25502","m":"1031920881_longtail"},"6m3CyQ3":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yp\/r\/TE6Lx-rxXy6.js","c":1,"p":":587","m":"1031920881_main"},"wIJVNj8":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iQvT4\/yG\/l\/en_US\/7v9DcqDTVyq.js","c":1,"p":":60","m":"1031920881_main"},"v9++ZOL":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iNrA4\/yF\/l\/en_US\/zVzJnQPlEx3.js","c":1,"p":":94","m":"1031920881_main"},"vnCDI+b":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4il1f4\/yX\/l\/en_US\/e-raN4oU0_h.js","c":1,"p":":25501","m":"1031920881_longtail"},"41Xaxna":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iLpP4\/yu\/l\/en_US\/YBMC51sdJPa.js","c":1,"p":":45","m":"1031920881_main"},"sZLvqyW":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iVNv4\/ya\/l\/en_US\/B_s9KF-seXr.js","c":1,"p":":405","m":"1031920881_main"},"w9mX8rx":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yt\/r\/iQ4jUYtLp-L.js","c":1,"p":":25497","m":"1031920881_longtail"},"GaaI8wv":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ibbe4\/yV\/l\/en_US\/iS8hKs0iZLc.js","c":1,"p":":102","m":"1031920881_main"},"vEXl2XN":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iblK4\/yI\/l\/en_US\/v4VSyBlPEbd.js","c":1,"p":":1062","m":"1031920881_main"},"iLtKfnG":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y6\/r\/Z4-7QIgRhRF.js","c":1,"p":":27282","m":"1031920881_longtail"},"rg+Uh8U":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y0\/r\/JnlXnNhLkGu.js","c":1,"p":":27286","m":"1031920881_longtail"},"mjNs7mT":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y7\/r\/ULi0yBv6z3J.js","c":1,"p":":25498","m":"1031920881_longtail"},"PdbWgF4":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ilK04\/ys\/l\/en_US\/h09S4ZBm0lt.js","c":1,"p":":202","m":"1031920881_main"},"1ou1bf9":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iqvl4\/yS\/l\/en_US\/xhO_4yUX54o.js","c":1,"p":":56","m":"1031920881_main"},"CJ7ZV8+":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iE754\/yr\/l\/en_US\/fBF8zEM6rmz.js","c":1,"p":":25503","m":"1031920881_longtail"},"Na1E3Dy":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i5Un4\/yn\/l\/en_US\/XwnNQ0bh4d5.js","c":1,"p":":25494","m":"1031920881_longtail"},"USuNYW0":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y1\/r\/PwedoNDIhIJ.js","c":1,"p":":27293","m":"1031920881_longtail"},"4yAN+my":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iNq64\/yA\/l\/en_US\/CBP8r3wKxr-.js","c":1,"p":":757","m":"1031920881_main"},"IibJ0+J":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yx\/r\/AXV6_6tFEzg.js","c":1,"p":":25499","m":"1031920881_longtail"},"Aubq+FV":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4irSG4\/yw\/l\/en_US\/WkdT272mStE.js","c":1,"p":":160","m":"1031920881_main"},"kPi4+\/\/":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iMuT4\/yC\/l\/en_US\/V_E9Eto7itP.js","c":1,"p":":62","m":"1031920881_main"},"I+GHswV":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yR\/r\/XAqzp11_JpC.js","c":1,"p":":110","m":"1031920881_main"},"im5u5w6":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ihIp4\/yi\/l\/en_US\/by5f8X_Z2_H.js","c":1,"p":":461","m":"1031920881_main"},"iRKzpVq":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iy2y4\/yo\/l\/en_US\/T65KRyBjmdY.js","c":1,"p":":104","m":"1031920881_main"},"YEd8ioO":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y4\/r\/uF9BQkEuOjL.js","c":1,"p":":580","m":"1031920881_main"},"vK6wenv":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/3CTZqE650Lr.js","c":1,"p":":32280","m":"1031920881_longtail"},"wiHl0GB":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yv\/r\/idfHM9fpbDR.js","c":1,"p":":422","m":"1031920881_main"},"\/qgsfZB":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4itpv4\/yB\/l\/en_US\/ScvHGN-0odl.js","c":1,"p":":943","m":"1031920881_main"},"2klhqM2":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iOyV4\/yH\/l\/en_US\/0FrSlNxRxHO.js","c":1,"p":":27970","m":"1031920881_longtail"},"gHIk4we":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yP\/r\/tPSZbFYiFvV.js","c":1,"p":":280","m":"1031920881_main"},"ODMYNhL":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y8\/r\/Zux4reSGle7.js","c":1,"p":":105","m":"1031920881_main"},"W+TDAGO":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yY\/r\/mKp8he_3Xb1.js","c":1,"p":":32278","m":"1031920881_longtail"},"5rhjQJ5":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ys\/r\/AfjFFF2Osl1.js","c":1,"p":":894","m":"1031920881_main"},"ET06ios":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4irkz4\/yf\/l\/en_US\/3qKWpDodjNX.js","c":1,"p":":1183","m":"1031920881_main"},"ttiLvDt":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yF\/r\/D8cmWyJ8LQK.js","c":1,"p":":32966","m":"1031920881_longtail"},"Z\/hfEbx":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/y4\/r\/nQ8PmhDvyPf.js","c":1,"p":":32968","m":"1031920881_longtail"},"QB2NeHg":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iOmt4\/y_\/l\/en_US\/2GAINXXTM0D.js","c":1,"p":":1209","m":"1031920881_main"},"gjVzLf0":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iMBn4\/yo\/l\/en_US\/ZB-ILfVOfYr.js","c":1,"p":":158","m":"1031920881_main"},"wmt6DTl":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yo\/r\/RyUrJflO9Ut.js","c":1,"p":":27971","m":"1031920881_longtail"},"7c2Cs9E":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4im6D4\/yZ\/l\/en_US\/fSPu0f2EqON.js","c":1,"p":":87","m":"1031920881_main"},"75\/rhqb":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yS\/r\/GaeSAQddUPH.js","c":1,"p":":152","m":"1031920881_main"},"r01o1aa":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yv\/r\/XsOpJM2mnmH.js","c":1,"p":":45101","m":"1031920881_longtail"},"12euusk":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/n20VC3QbJ5B.js","c":1,"p":":26833","m":"1031920881_longtail"},"\/DqDAUP":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i7UB4\/yQ\/l\/en_US\/p5efzCKLCOl.js","c":1,"p":":1468","m":"1031920881_main"},"fHUdg2x":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yk\/r\/RmPIh0sCTrk.js","c":1,"p":":46413","m":"1031920881_longtail"},"5KE0nhz":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4idBq4\/yp\/l\/en_US\/HlP9BtZpe56.js","c":1,"p":":120","m":"1031920881_main"},"\/NTWV2I":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ipLN4\/yo\/l\/en_US\/m0b-tGKRTM2.js","c":1,"p":":27972","m":"1031920881_longtail"},"hAW\/IbR":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yV\/r\/f5iLA6NZ3_H.js","c":1,"p":":868","m":"1031920881_main"},"f+2p4BY":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ym\/r\/6rGfbhLWlVP.js","c":1,"p":":32277","m":"1031920881_longtail"},"TWcE9Ba":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iZdf4\/yI\/l\/en_US\/As6t3rxlnAi.js","c":1,"p":":91","m":"1031920881_main"},"5ROgmA3":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i2Zh4\/ya\/l\/en_US\/S_tcrXbLPIn.js","c":1,"p":":32275","m":"1031920881_longtail"},"KWXf0Cj":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yr\/r\/goXtBZpWr-T.js","c":1,"p":":32274","m":"1031920881_longtail"},"qBM\/ARz":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yG\/r\/Q-Xm5lHZZc6.js","c":1,"p":":32269","m":"1031920881_longtail"},"HTgKT5a":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yX\/r\/CH6MubcCKNj.js","c":1,"p":":115","m":"1031920881_main"},"3BtMGFJ":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ikTN4\/yY\/l\/en_US\/bZZ3K4I3xC2.js","c":1,"p":":97","m":"1031920881_main"},"tM\/SHRv":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ys\/r\/C2PgpwpQ1In.js","c":1,"p":":49","m":"1031920881_main"},"6h\/1uiq":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i2AS4\/yH\/l\/en_US\/E5U_f653GKI.js","c":1,"p":":1131","m":"1031920881_main"},"Ly9xw\/n":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yy\/r\/ZrmMmidyWOa.js","c":1,"p":":239","m":"1031920881_main"},"7nQ2xrR":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yz\/r\/WnYWYwYEkPq.js","c":1,"p":":825","m":"1031920881_main"},"Zyw83oL":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4ivUC4\/yy\/l\/en_US\/6OpwUnfz2fR.js","c":1,"p":":711","m":"1031920881_main"},"vRIf6Oc":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yI\/r\/kTA3AJlHSNG.js","c":1,"p":":1020","m":"1031920881_main"},"fAYq9VP":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iLeJ4\/yD\/l\/en_US\/FmbRgdvMi5-.js","c":1,"p":":1256","m":"1031920881_main"},"zdM8Fq\/":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yQ\/r\/W2k74LmZC50.js","c":1,"p":":644","m":"1031920881_main"},"p0PNIbt":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iAt94\/yP\/l\/en_US\/SfyNW7M9tT7.js","c":1,"p":":134","m":"1031920881_main"},"HBOwAIG":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yS\/r\/VBnHoycqOdu.js","c":1,"p":":32282","m":"1031920881_longtail"},"UGNod5x":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4igFL4\/yF\/l\/en_US\/WsgJmnCkuzT.js","c":1,"p":":1467","m":"1031920881_main"},"GiyZbLC":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i3lU4\/yp\/l\/en_US\/n904sahz6Y0.js","c":1,"p":":1083","m":"1031920881_main"},"G\/RswIW":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yj\/r\/MUCqdmVwVU1.js","c":1,"p":":32281","m":"1031920881_longtail"},"XphhRHh":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i1kT4\/yU\/l\/en_US\/HRQ0UgJHMzm.js","c":1,"p":":149","m":"1031920881_main"},"BJQXboE":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yP\/r\/E5-pQciVZPT.js","c":1,"p":":32276","m":"1031920881_longtail"},"UWyJiup":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yB\/r\/0HOuJU6Ig3X.js","c":1,"p":":148","m":"1031920881_main"},"ea0e0\/Q":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/ys\/r\/RohQH_3os6v.js","c":1,"p":":32961","m":"1031920881_longtail"},"4V1AlBf":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yq\/r\/ScfNnAyHYyi.js","c":1,"p":":32224","m":"1031920881_longtail"},"znpYU5X":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yj\/r\/6QsUjY2H1K8.js","c":1,"p":":959","m":"1031920881_main"},"yjxUCAc":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yE\/r\/yYiOLH7WMcl.js","c":1,"p":":32972","m":"1031920881_longtail"},"jz67ePp":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iSL74\/yM\/l\/en_US\/he2V_eLtx2k.js","c":1,"p":":1146","m":"1031920881_main"},"v5x0l84":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iFEb4\/y2\/l\/en_US\/9BT3dr0Jpl_.js","c":1,"p":":32970","m":"1031920881_longtail"},"zdMsZ1+":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4iSWn4\/yq\/l\/en_US\/WXf8SudbKjx.js","c":1,"p":":563","m":"1031920881_main"},"t+yxLVI":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yZ\/r\/Ge4J6mZXYV-.js","c":1,"p":":32969","m":"1031920881_longtail"},"9oq\/IaS":{"type":"js","src":"https | 2026-01-13T08:48:29 |
https://dev.to/beck_moulton/stop-sending-sensitive-data-to-the-cloud-build-a-local-first-mental-health-ai-with-webllm-5100 | Stop Sending Sensitive Data to the Cloud: Build a Local-First Mental Health AI with WebLLM - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Beck_Moulton Posted on Jan 13 Stop Sending Sensitive Data to the Cloud: Build a Local-First Mental Health AI with WebLLM # privacy # typescript # webgpu # webllm In an era where data breaches are common, privacy in Edge AI has moved from a "nice-to-have" to a "must-have," especially in sensitive fields like healthcare. If you've ever worried about your private conversations being used to train a massive corporate model, you're not alone. Today, we are exploring the frontier of Privacy-preserving AI by building a medical Q&A bot that runs entirely on the client side. By leveraging WebLLM , WebGPU , and TVM Unity , we can now execute large language models directly in the browser. This means the dialogue never leaves the user's device, providing a truly decentralized and secure experience. For those looking to scale these types of high-performance implementations, I highly recommend checking out the WellAlly Tech Blog for more production-ready patterns on enterprise-grade AI deployment. The Architecture: Why WebGPU? Traditional AI apps send a request to a server (Python/FastAPI), which queries a GPU (NVIDIA A100), and sends a JSON response back. This "Client-Server" model is the privacy killer. Our "Local-First" approach uses WebGPU , the next-gen graphics API for the web, to tap into the user's hardware directly. graph TD subgraph User_Device [User Browser / Device] A[React UI Layer] -->|Dispatch| B[WebLLM Worker] B -->|Request Execution| C[TVM Unity Runtime] C -->|Compute Kernels| D[WebGPU API] D -->|Inference| E[VRAM / GPU Hardware] E -->|Streaming Text| B B -->|State Update| A end F((Public Internet)) -.->|Static Assets & Model Weights| A F -.->|NO PRIVATE DATA SENT| A Enter fullscreen mode Exit fullscreen mode Prerequisites Before we dive in, ensure you have a browser that supports WebGPU (Chrome 113+ or Edge). Framework : React (Vite template) Language : TypeScript AI Engine : @mlc-ai/web-llm Core Tech : WebGPU & TVM Unity Step 1: Initializing the Engine Running an LLM in a browser requires significant memory management. We use a Web Worker to ensure the UI doesn't freeze while the model is "thinking." // engine.ts import { CreateMLCEngine , MLCEngineConfig } from " @mlc-ai/web-llm " ; const modelId = " Llama-3-8B-Instruct-v0.1-q4f16_1-MLC " ; // Lightweight quantized model export async function initializeEngine ( onProgress : ( p : number ) => void ) { const engine = await CreateMLCEngine ( modelId , { initProgressCallback : ( report ) => { onProgress ( Math . round ( report . progress * 100 )); console . log ( report . text ); }, }); return engine ; } Enter fullscreen mode Exit fullscreen mode Step 2: Creating the Privacy-First Chat Hook In a medical context, the system prompt is critical. We need to instruct the model to behave as a supportive assistant while maintaining strict safety boundaries. // useChat.ts import { useState } from ' react ' ; import { initializeEngine } from ' ./engine ' ; export const useChat = () => { const [ engine , setEngine ] = useState < any > ( null ); const [ messages , setMessages ] = useState < { role : string , content : string }[] > ([]); const startConsultation = async () => { const instance = await initializeEngine (( p ) => console . log ( `Loading: ${ p } %` )); setEngine ( instance ); // Set the System Identity for Mental Health await instance . chat . completions . create ({ messages : [{ role : " system " , content : " You are a private, empathetic mental health assistant. Your goal is to listen and provide support. You do not store data. If a user is in danger, provide emergency resources immediately. " }], }); }; const sendMessage = async ( input : string ) => { const newMessages = [... messages , { role : " user " , content : input }]; setMessages ( newMessages ); const reply = await engine . chat . completions . create ({ messages : newMessages , }); setMessages ([... newMessages , reply . choices [ 0 ]. message ]); }; return { messages , sendMessage , startConsultation }; }; Enter fullscreen mode Exit fullscreen mode Step 3: Optimizing for Performance (TVM Unity) The magic behind WebLLM is TVM Unity , which compiles models into highly optimized WebGPU kernels. This allows us to run models like Llama-3 or Mistral at impressive tokens-per-second on a standard Macbook or high-end Windows laptop. If you are dealing with advanced production scenarios—such as model sharding or custom quantization for specific medical datasets—the team at WellAlly Tech has documented extensive guides on optimizing WebAssembly runtimes for maximum throughput. Step 4: Building the React UI A simple, clean interface is best for mental health applications. We want the user to feel calm and secure. // ChatComponent.tsx import React , { useState } from ' react ' ; import { useChat } from ' ./useChat ' ; export const MentalHealthBot = () => { const { messages , sendMessage , startConsultation } = useChat (); const [ input , setInput ] = useState ( "" ); return ( < div className = "p-6 max-w-2xl mx-auto border rounded-xl shadow-lg bg-white" > < h2 className = "text-2xl font-bold mb-4" > Shielded Mind AI 🛡️ </ h2 > < p className = "text-sm text-gray-500 mb-4" > Status: < span className = "text-green-500" > Local Only (Encrypted by Hardware) </ span ></ p > < div className = "h-96 overflow-y-auto mb-4 p-4 bg-gray-50 rounded" > { messages . map (( m , i ) => ( < div key = { i } className = { `mb-2 ${ m . role === ' user ' ? ' text-blue-600 ' : ' text-gray-800 ' } ` } > < strong > { m . role === ' user ' ? ' You: ' : ' AI: ' } </ strong > { m . content } </ div > )) } </ div > < div className = "flex gap-2" > < input className = "flex-1 border p-2 rounded" value = { input } onChange = { ( e ) => setInput ( e . target . value ) } placeholder = "How are you feeling today?" /> < button onClick = { () => { sendMessage ( input ); setInput ( "" ); } } className = "bg-purple-600 text-white px-4 py-2 rounded hover:bg-purple-700" > Send </ button > </ div > < button onClick = { startConsultation } className = "mt-4 text-xs text-gray-400 underline" > Initialize Secure WebGPU Engine </ button > </ div > ); }; Enter fullscreen mode Exit fullscreen mode Challenges & Solutions Model Size : Downloading a 4GB-8GB model to a browser is the biggest hurdle. Solution : Use IndexedDB caching so the user only downloads the model once. VRAM Limits : Mobile devices may struggle with large context windows. Solution : Implement sliding window attention and aggressive 4-bit quantization. Cold Start : The initial "Loading" phase can take time. Solution : Use a skeleton screen and explain that this process ensures their privacy. Conclusion By moving the "brain" of our AI from the cloud to the user's browser, we've created a psychological safe space that is literally impossible for hackers to intercept at the server level. WebLLM and WebGPU are turning browsers into powerful AI engines. Want to dive deeper into Edge AI security , LLM Quantization , or WebGPU performance tuning ? Head over to the WellAlly Tech Blog where we break down the latest advancements in local-first software architecture. What do you think? Would you trust a local-only AI more than ChatGPT for sensitive topics? Let me know in the comments below! 👇 Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Beck_Moulton Follow Joined Aug 22, 2022 More from Beck_Moulton Private & Fast: Building a Browser-Based Dermatology Screener with WebLLM and WebGPU # privacy # ai # web # webdev Federated Learning or Bust: Architecting Privacy-First Health AI # machinelearning # architecture # privacy # devops Why Your Health Data Belongs on Your Device (Not the Cloud): A Local-First Manifesto # architecture # privacy # offlinefirst # database 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://dev.to/cotter/oauth-2-0-before-you-start-pick-the-right-flow-for-your-website-spa-mobile-app-tv-app-and-cli-17n4 | OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Aug 4, 2020 • Originally published at blog.cotter.app on Aug 4, 2020 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # security # react # javascript # webdev OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI OAuth 2.0 has at least 4 different flows for different use cases. Find out which flow you should use to secure your app. We learned how OAuth 2.0 works in general in What on Earth is OAuth? and learned how to securely store access tokens in the front end. In this post, we'll learn which OAuth 2.0 flow you should use based on what you're building. OAuth 2.0 Recap: In general, the OAuth 2.0 flow looks like this diagram below (if you're not familiar with the OAuth 2.0 Flow below, check our explanation here ). OAuth 2.0 Flow with Google Sign In Step 1: The website requests authorization for Albert. Albert is being redirected to Google's site to log in. Step 2: Google's site returned with an Authorization Grant. This is the part that has several different cases based on which flow you're using. Step 3-4: Depending on the flow, the client will have a way to exchange this Authorization Grant with an access token, and sometimes a refresh token Step 5-6: The website uses the access token to access resources. Common OAuth 2.0 Flows As mentioned above, there are 4 common OAuth 2.0 Flows: Authorization Code Flow Authorization Code Flow with Proof Key for Code Exchange (PKCE) Client Credentials Flow Device Code Flow Which Flow Should I Use? Different apps should use different flows based on whether or not the app can hold secrets securely. Web Server Apps and Command Line Scripts : Use Authorization Code Flow Single Page Apps and Mobile Apps : Use Authorization Code Flow with PKCE Server-to-Server API Calls : Use Client Credentials Flow TV Apps and other apps on input-constrained devices : Use Device Code Flow Web Server Apps and Command Line Scripts → Use Authorization Code Flow Web Server Apps are apps that are running on a server where the source code is not publicly exposed. Requirements: Your app needs to be able to hold a Client Secret securely in the back end server. For example: ✅ Your app runs on a server (Node.js, PHP, Java, .NET): Your server code is not publicly exposed and you can put secret keys in environment variables without it being visible to users of the application. ❌ React-only website: React is a SPA framework, your code is publicly exposed, and therefore cannot hold secrets securely, even if you put secrets in .env files. Authorization Code Flow OAuth 2.0 Authorization Code Flow Step 1-4: User clicks Sign in with Google, and get redirected to Google's Site to authenticate. Step 5: When the user successfully authenticated, Google will redirect the user back to your website, and include an authorization_code in the redirect URL. For example: https://mysite.com/redirect ?code=ABCDEFGHIJ12345 &state=abcde123abc Enter fullscreen mode Exit fullscreen mode Step 6-9: With the code above and a Client ID + Client Secret that you get from Google when registering an application, you can request for an access_token for the user that you can then use to fetch data. See the full spec at RFC 6749 Section 4.1 How do I do this from the command line? On step 3 , show the URL that the user should go to in their browser. Get your script to listen to a local port, for example, http://127.0.0.1:8000 and set the redirect URL to be http://127.0.0.1:8000/redirect On step 5 , the user's browser will redirect to https://127.0.0.1:8000/redirect ?code=ABCDEFGHIJ12345 &state=abcde123abc Enter fullscreen mode Exit fullscreen mode Your script should then handle this GET request, parse the code and state and proceed to step 6-9. Single Page Apps & Mobile Apps → Use Authorization Code Flow with PKCE Single Page Apps (SPA) and Mobile Apps are not able to hold secrets securely because their source code is publicly exposed or can be decompiled. How does the PKCE flow work without a Client Secret? The PKCE flow requires the app to generate a secret on the fly. This secret is generated at the beginning of the flow when the user started the login flow and then checked when exchanging authorization code with an access token. This makes sure that the entity that is requesting to exchange the authorization code with an access token is still the same entity where the user requested to authenticate. Authorization Code Flow with PKCE OAuth 2.0 Authorization Code Flow with PKCE Step 1: User clicks the login button in your app Step 2: Generate a code_verifier and code_challenge , then make an authorization request by sending the code_challenge . code_verifier = "a cryptographic random string" code_challenge = base64url_encode(sha256(ascii(code_verifier))) Enter fullscreen mode Exit fullscreen mode Step 3-5: The Authorization Server will save the code_challenge for later and redirect the user to log in, then redirect to your app with an authorization_code Step 6 : Your app then sends the code_verifier , client_id , and authorization_code to get an access token. Step 7: The Authorization Server will check if the original code_challenge == base64url_encode(sha256(ascii(code_verifier))) . This is where it determines whether the entity that started this flow is the same one as the one that is currently requesting an access token. If yes, it returns the access token. Step 8-9 : Your app can now fetch data using the access token. See the full spec at RFC 7636 . Here are some resources to help you generate a code challenge and verifier: Generate code_verifier and code_challenge online . See how to generate code_verifier and code_challenge using JavaScript, Java, or Swift 3 . Server-to-Server API calls → Use Client Credentials Flow For example, your back end server wants to call an API endpoint at Stripe to retrieve a list of payments. This is a machine-to-machine authorization, and there's no end-user authorization. In this case, Stripe is only trying to authorize your server to access the API endpoint. Since your server can also hold secrets securely, all you need for accessing the data is a Client ID and Client Secret . Client Credentials Flow OAuth 2.0 Client Credentials Flow Step 1: Your server authenticates itself using its Client ID and Client Secret. Notice that this doesn't involve any user. This is because your server is acting as itself. (For example, your server is acting as Hello Merchant that you registered to Stripe). Step 2: If the Client ID and Client Secret checks out, you'll receive an access token. Step 3: Use the access token to fetch data. See the full spec at RFC 6749 Section 4.4 TV Apps and other apps on input-constrained devices → Use Device Code Flow It'll be horrible if you have to input your super-secure Google password to watch YouTube on your brand new smart TV, right? OAuth 2.0 Device Code Flow is designed so that you can authorize apps on an input constraint device by opening a URL and entering a code on your browser (on your phone/laptop). Requirements: Your app needs to be able to display a URL and a User Code to the user. This can also be done by showing a QR Code. Device Code Flow Step 1: User requests to log in on your TV App. Step 2-3: Your TV App makes an authorization request to the Authorization Server (Google Accounts in this case) with your app's Client ID, and receive 3 things: a device_code , a user_code , and a verification_uri . Step 4 : Your TV App now asks the user to go to the verification_uri and enter the user_code . You can optionally do this by asking the user to scan a QR Code that encodes both the verification_uri and the user_code . Step 5: Your TV App now requests an access token to the Authorization Server using the device_code and client_id . If the user hasn't authenticated and allowed access to your app yet (they haven't gone to the verification_uri ), the Authorization Server will respond with an error authorization_pending . Your TV App should keep on requesting until you get an access token. Step 6: The user typed in the verification_uri on their phone or laptop, and entered the user_code . Step 7-8: The user is now redirected to Google's Login page where they can authenticate and allow your TV App to access certain data. Step 9 : Google accounts now mark that your user has authenticated and allowed your app to access their data. The next time your app requested for an access token with the device_code , Google Accounts will return an access token. Step 10-11 : Use the access token to fetch data. See the full spec at RFC 8628 Section 3.4 That's It! This should help you pick which OAuth 2.0 flow you need for different use cases. We didn't go into the specific HTTP Request parameters that you should use, we will cover that next time. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a website, we have a ready-made solution that implements the flows above for you. Sign in with Magic Link via Email, SMS, or WhatsApp on: React.js React Native Flutter References We referred to these articles and specs to write this post: The OAuth 2.0 Authorization Framewor k (RFC 6749) OAuth Grant Types OAuth 2.0 Device Flow Grant Authentication and Authorization Flows Questions & Feedback If you need help or have any feedback, ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security What is WebAuthn: Logging in with Face ID and Touch ID on the web # javascript # react # authentication # tutorial 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://stackoverflow.blog/author/daly-singh/ | Daly Singh - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Daly Singh As AI Squad Lead and Product Owner at Bosch Digital, he turns generative-AI research into real-world impact. He focuses on creating human-centered AI products that blend seamlessly into everyday experiences—believing that the best technology feels invisible, empowering both users and developers alike. October 20, 2025 From multilingual semantic search to virtual assistants at Bosch Digital From sprawling PDFs to a fast, factual conversational assistant. Daly Singh , Jeremy Teichmann 4 comment s AI contributed CC BY-SA 4.0 Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://stackoverflow.blog/author/or-lenchner/ | Or Lenchner - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Or Lenchner April 3, 2025 From training to inference: The new role of web data in LLMs Data has always been key to LLM success, but it's becoming key to inference-time performance as well. Or Lenchner 4 comment s data science generative AI data contributed Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://aws.amazon.com/contact-us/?nc2=h_ut_cu | AWS Support and Customer Service Contact Info | Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Support › Contact AWS Contact AWS General support for sales, compliance, and subscribers Want to speak with an AWS sales specialist? Get in touch Chat online or talk by phone Connect with support directly Monday through Friday Request form Request AWS sales support Submit a sales support form Compliance support Request support related to AWS compliance Connect with AWS compliance support Subscriber support services Technical support Support for service related technical issues. Unavailable under the Basic Support Plan. Sign in and submit request Account or billing support Assistance with account and billing related inquiries Sign in to request Wrongful charges support Received a bill for AWS, but don't have an AWS account? Learn more Support plans Learn about AWS support plan options See Premium Support options AWS sign-in resources See additional resources for issues related to logging into the console Help signing in to the console Need assistance to sign in to the AWS Management Console? View documentation Trouble shoot your sign-in issue Tried sign in, but the credentials didn’t work? Or don’t have the credentials to access AWS root user account? View solutions Help with multi-factor authentication (MFA) issues Lost or unusable Multi-Factor Authentication (MFA) device View solution Still unable to sign in to your AWS account? If you are still unable to log into your AWS account please fill out this form. View form Additional resources Self-service re:Post provides access to curated knowledge and a vibrant community that helps you become even more successful on AWS View AWS re:Post Service limit increases Need to increase to service limit? Fill out a quick request form Sign in to request Report abuse Report abusive activity from Amazon Web Services Resources Report suspected abuse Amazon.com support Request Kindle or Amazon.com support View on amazon.com Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:29 |
https://stackoverflow.blog/2025/04/28/how-self-supervised-language-revolutionized-natural-language-processing-and-gen-ai/#comments | How self-supervised learning revolutionized natural language processing and gen AI - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 28, 2025 How self-supervised learning revolutionized natural language processing and gen AI Self-supervised learning is a key advancement that revolutionized natural language processing and generative AI. Here’s how it works and two examples of how it is used to train language models. Credit: Alexandra Francis TL;DR: Self-supervised learning is a key advancement in deep learning that is used across a variety of domains. Put simply, the idea behind self-supervised learning is to train a model over raw/unlabeled data by making out and predicting portions of this data. This way, the ground truth “labels” that we learn to predict are already present in the data itself and no human annotation is required. Types of learning. Machine learning models can be trained in a variety of ways. For example, supervised learning trains a machine learning model over pairs of input data and output labels (usually annotated manually by humans). The model learns to predict these output labels by supervising the model (i.e., showing it several examples of input data with the correct output)! On the other hand, unsupervised learning uses no output labels and discovers inherent trends within the input data itself (e.g., by forming clusters). “Self-supervised learning obtains supervisory signals from the data itself, often leveraging the underlying structure in the data. The general technique of self-supervised learning is to predict any unobserved or hidden part (or property) of the input from any observed or unhidden part of the input.” - from Self-supervised learning: The dark matter of intelligence What is self-supervised learning? Self-supervised learning lies between supervised and unsupervised learning. Namely, we train the model over pairs of input data and output labels. However, no manual annotation from humans is required to obtain output labels within our training data—the labels are naturally present in the raw data itself! To understand this better, let’s take a look at a few commonly-used self-supervised learning objectives. (1) The Cloze task is more commonly referred to as the masked language modeling (MLM) objective. Here, the language model takes a sequence of textual tokens (i.e., a sentence) as input. To train the model, we mask out (i.e., set to a special “mask” token) ~10% of tokens in the input and train the model to predict these masked tokens. Using this approach, we can train a language model over an unlabeled textual corpus, as the “labels” that we predict are just tokens that are already present in the text itself. This objective is used to pretrain language models like BERT and T5. (2) Next token prediction is the workhorse of modern generative language models like ChatGPT and PaLM. After downloading a large amount of raw textual data from the internet, we can repeatedly i) sample a sequence of text and ii) train the language model to predict the next token given preceding tokens as input. This happens in parallel for all tokens in the sequence. Again, all the “labels” that we learn to predict are already present in the raw textual data. Pretraining (and finetuning) via next token prediction is universal used by all generative language models. Other options exist too! Although Cloze and next token prediction are the most commonly-used self-supervised objectives for training language models, many examples of self-supervised learning exist. For example, many self-supervised objectives exist for video deep learning models (e.g., predicting the next frame), and BERT models also use a self-supervised next-sentence prediction objective. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Cameron R. Wolfe, PhD Director of AI at Rebuy I’m currently the Director of AI at Rebuy, a personalized search and recommendations platform for D2C e-commerce brands. Prior to Rebuy, I was a Research Scientist at Alegion. Additionally, I worked for Salesforce Commerce Cloud … llm AI contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://ruul.io/freelancer/generate-tax-invoices | Ruul | Sell Services & Digital Products | Get Paid as a Freelancer Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up Merchant of Record for Independents INDEPENDENT’S PAY BUTTON Sell anything. Get paid anywhere. Great for freelancers, creators, and indie sellers. ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Trustpilot Trusted by thousands of teams RUUL FOR INDEPENDENCE You chose independence.We make sure you keep it. Sell your time, your talent, whatever you create or build always on your terms. Get started See Example Payment Requests Sell Services Sell Products Subscriptions Get paid for your freelance services. Send professional payment requests and get paid fast. Billing, compliance, and payments, all in one. Get started Learn more Sell services like ordering food. List your services, share your link, and get paid—no back-and-forth, no hassle. Get started Learn more Create once, sell forever. Made something great? Sell it again and again. Drop a link or use your store—it’s all set up for you. Get started Learn more Get paid like Netflix. On repeat. No chasing. No awkward follow-ups. Get paid on a schedule with subscription payments. Get started Learn more PAYMENT REQUESTS Get paid for your freelance services. Send professional payment requests and get paid fast. Billing, compliance, and payments, all in one. Get started Learn more SELL SERVICES Sell services like ordering food. List your services, share your link, and get paid—no back-and-forth, no hassle. Get started Learn more SELL PRODUCTS Create once, sell forever. Made something great? Sell it again and again. Drop a link or use your store—it’s all set up for you. Get started Learn more SUBSCRIPTIONS Get paid like Netflix. On repeat. No chasing. No awkward follow-ups. Get paid on a schedule with subscription payments. Get started Learn more RUUL SPACE YOUR SPACE, BUILT TO SELL Sell what you do. Show what you’ve made. Ruul Space is your personal storefront for sales, bio, and payments. Learn more @coffeeandpixels @milesbecker @videovibes @productgeek @coffeeandpixels @brandwizard @videovibes @milesbecker Meet the independents. Designers, developers, marketers, creators building, creating, and delivering with passion. Get started WHY RUUL The little things that make a big difference. Get started Checkout Links No storefront? No problem. Share a direct link to sell or get paid. Connected Wallets Connect your favorite digital wallets and manage payouts your way. Stablecoin Payouts Get paid in crypto using stablecoins, with fast and flexible payouts. Human Support Real people, real help. Get 5-star customer support that actually solves things. Secure Payments Every transaction is safe, smooth, and built with business-grade security. MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot How to Sell Subscriptions Turn your services into steady monthly revenue: learn the best subscription models, smart pricing, and retention tactics that keep customers paying. Read more Best Portfolio Platforms for Freelancers in 2025 Discover the best portfolio building platforms for solo talents and freelancers to showcase their work and impress potential clients. Explore WP.ruul.io's expert recommendations and find the perfect platform to create a stunning portfolio that stands out. Read more What is an Invoice? Discover Everything You Need to Know About Invoices Discover the essentials of invoicing in our detailed guide. Learn what an invoice is, its importance, key elements, historical evolution, and tips for effective invoicing. Simplify your financial transactions and improve cash flow with Ruul's Invoice Generator. Read more Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:29 |
https://www.apple.com/newsroom/2022/05/the-music-lives-on/ | The music lives on - Apple Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + Newsroom Open Newsroom navigation Close Newsroom navigation Apple Services Apple Stories Search Newsroom Close opens in new window UPDATE May 10, 2022 The music lives on iPod touch will be available while supplies last iPod redefined how music was discovered, listened to, and shared. iPod touch will be available while supplies last. Since its introduction over 20 years ago, iPod has captivated users all over the world who love the ability to take their music with them on the go. Today, the experience of taking one’s music library out into the world has been integrated across Apple’s product line — from iPhone and Apple Watch to iPad and Mac — along with access to more than 90 million songs and over 30,000 playlists available via Apple Music. “Music has always been part of our core at Apple, and bringing it to hundreds of millions of users in the way iPod did impacted more than just the music industry — it also redefined how music is discovered, listened to, and shared,” said Greg Joswiak, Apple’s senior vice president of Worldwide Marketing. “Today, the spirit of iPod lives on. We’ve integrated an incredible music experience across all of our products, from the iPhone to the Apple Watch to HomePod mini, and across Mac, iPad, and Apple TV. And Apple Music delivers industry-leading sound quality with support for spatial audio — there’s no better way to enjoy, discover, and experience music.” The original iPod model is shown. The first iPod mini is shown. iPod nano (2nd generation) is shown. The first iPod touch is shown. iPod nano (7th generation) is shown. iPod shuffle (4th generation) is shown. iPod touch (7th generation) is shown. The original iPod, introduced on October 23, 2001, was the first MP3 player to pack a mind-blowing 1,000 songs and a 10-hour battery into a stunning 6.5-ounce package. iPod mini, introduced on February 20, 2004, brought everything users loved about iPod into a smaller design at just 3.6 ounces. iPod nano (2nd generation), introduced on September 25, 2006, offered a thin design, a bright color display, six stylish colors, and up to 24 hours of battery life, and put up to 2,000 songs in users’ pockets. iPod touch, first introduced on September 5, 2007, brought the revolutionary Multi-Touch interface that made iPhone a hit to iPod with a gorgeous 3.5-inch widescreen display. iPod nano (7th generation), introduced on September 12, 2012, was the thinnest iPod to date at just 5.4mm and featured a 2.5-inch Multi-Touch display. iPod shuffle (4th generation), introduced on July 15, 2015, offered a sleek design with up to 15 hours of battery life, 2GB of storage good for hundreds of songs, and a VoiceOver button to hear a song title, playlist name, or battery status. iPod touch (7th generation), introduced on May 28, 2019, features the A10 Fusion chip, enabling immersive augmented reality experiences and Group FaceTime, along with 256GB of storage. previous next Among the incredible ways to enjoy music across a range of devices, including a wide variety of models from the new iPhone SE to the latest iPhone 13 Pro Max, iPhone is the best device for streaming Apple Music or storing an entire music library on the go. Apple Watch and AirPods are the perfect companion, allowing users to access over 90 million songs right from their wrist, starting at just $279 with Apple Watch SE. iPad starts at just $329, comes with a more powerful chip, larger display and the latest iPadOS features. And for the best way to enjoy music at home, HomePod mini is just $99. An incredible music experience is integrated across Apple’s product line — from iPhone, Apple Watch, and AirPods to HomePod mini, iPad, and Mac. Customers can purchase iPod touch through apple.com , Apple Store locations, and Apple Authorized Resellers while supplies last. Share article Media Text of this article May 10, 2022 UPDATE The music lives on iPod touch will be available while supplies last Since its introduction over 20 years ago, iPod has captivated users all over the world who love the ability to take their music with them on the go. Today, the experience of taking one’s music library out into the world has been integrated across Apple’s product line — from iPhone and Apple Watch to iPad and Mac — along with access to more than 90 million songs and over 30,000 playlists available via Apple Music. “Music has always been part of our core at Apple, and bringing it to hundreds of millions of users in the way iPod did impacted more than just the music industry — it also redefined how music is discovered, listened to, and shared,” said Greg Joswiak, Apple’s senior vice president of Worldwide Marketing. “Today, the spirit of iPod lives on. We’ve integrated an incredible music experience across all of our products, from the iPhone to the Apple Watch to HomePod mini, and across Mac, iPad, and Apple TV. And Apple Music delivers industry-leading sound quality with support for spatial audio — there’s no better way to enjoy, discover, and experience music.” Among the incredible ways to enjoy music across a range of devices, including a wide variety of models from the new iPhone SE to the latest iPhone 13 Pro Max, iPhone is the best device for streaming Apple Music or storing an entire music library on the go. Apple Watch and AirPods are the perfect companion, allowing users to access over 90 million songs right from their wrist, starting at just $279 with Apple Watch SE. iPad starts at just $329, comes with a more powerful chip, larger display and the latest iPadOS features. And for the best way to enjoy music at home, HomePod mini is just $99. Customers can purchase iPod touch through apple.com , Apple Store locations, and Apple Authorized Resellers while supplies last. Press Contacts Apple Media Helpline media.help@apple.com Apple Media Helpline media.uk@apple.com Copy text Images in this article Download all images Press Contacts Apple Media Helpline media.help@apple.com Apple Media Helpline media.uk@apple.com More from Apple Newsroom UPDATE 2025 marked a record-breaking year for Apple services January 12, 2026 UPDATE Chase to become new issuer of Apple Card January 7, 2026 UPDATE Spectrum Front Row tips off January 9 on Apple Vision Pro January 5, 2026 Apple Newsroom The latest news and updates, direct from Apple. Read more Stay up to date with the latest articles from Apple Newsroom. Dismiss Get Notifications Apple Footer Apple Newsroom The music lives on Shop and Learn Shop and Learn Store Mac iPad iPhone Watch Vision AirPods TV & Home AirTag Accessories Gift Cards Apple Wallet Apple Wallet Wallet Apple Card Apple Pay Apple Cash Account Account Manage Your Apple Account Apple Store Account iCloud.com Entertainment Entertainment Apple One Apple TV Apple Music Apple Arcade Apple Fitness+ Apple News+ Apple Podcasts Apple Books App Store Apple Store Apple Store Find a Store Genius Bar Today at Apple Group Reservations Apple Camp Apple Store App Certified Refurbished Apple Trade In Financing Carrier Deals at Apple Order Status Shopping Help For Business For Business Apple and Business Shop for Business For Education For Education Apple and Education Shop for K-12 Shop for College For Healthcare For Healthcare Apple and Healthcare For Government For Government Apple and Government Shop for Veterans and Military Shop for State and Local Employees Shop for Federal Employees Apple Values Apple Values Accessibility Education Environment Inclusion and Diversity Privacy Racial Equity and Justice Supply Chain Innovation About Apple About Apple Newsroom Apple Leadership Career Opportunities Investors Ethics & Compliance Events Contact Apple More ways to shop: Find an Apple Store or other retailer near you. Or call 1-800-MY-APPLE (1-800-692-7753). United States Español Copyright © 2026 Apple Inc. All rights reserved. Privacy Policy Terms of Use Sales and Refunds Legal Site Map | 2026-01-13T08:48:29 |
https://dev.to/t/privacy/page/3 | Privacy Page 3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # privacy Follow Hide Create Post Older #privacy posts 1 2 3 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 33 Million Accounts Exposed: What the Condé Nast Breach Teaches Engineering Leaders Ed Ed Ed Follow Dec 28 '25 33 Million Accounts Exposed: What the Condé Nast Breach Teaches Engineering Leaders # leadership # privacy # security Comments Add Comment 5 min read Oasis for Developers: an underrated EVM for privacy-first dApps Zerod0wn Gaming Zerod0wn Gaming Zerod0wn Gaming Follow Jan 11 Oasis for Developers: an underrated EVM for privacy-first dApps # solidity # cryptocurrency # blockchain # privacy 1 reaction Comments 2 comments 1 min read How to Quickly Diagnose Network Issues Using Browser-Based Tools myip casa myip casa myip casa Follow Dec 27 '25 How to Quickly Diagnose Network Issues Using Browser-Based Tools # security # webdev # privacy # networking Comments Add Comment 3 min read Is This the Most Private Way to Track Your Life? Dashboard of Life. techno kraft techno kraft techno kraft Follow Dec 27 '25 Is This the Most Private Way to Track Your Life? Dashboard of Life. # showdev # tooling # privacy # productivity 1 reaction Comments Add Comment 2 min read I Built a Privacy-First Currency Converter in 2 Weeks Demetria Darjean Demetria Darjean Demetria Darjean Follow Dec 29 '25 I Built a Privacy-First Currency Converter in 2 Weeks # showdev # webdev # javascript # privacy 3 reactions Comments Add Comment 2 min read Is Your AI Agent a Compliance Risk? How to Find Violations Hidden in Traces shashank agarwal shashank agarwal shashank agarwal Follow Dec 26 '25 Is Your AI Agent a Compliance Risk? How to Find Violations Hidden in Traces # privacy # agents # security # ai Comments Add Comment 2 min read Stop Uploading Your Thoughts: A 100% Private, Local-First Sticky Notes Browser Tool techno kraft techno kraft techno kraft Follow Dec 26 '25 Stop Uploading Your Thoughts: A 100% Private, Local-First Sticky Notes Browser Tool # showdev # privacy # webdev # productivity 1 reaction Comments Add Comment 2 min read Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private sid sid sid Follow Dec 25 '25 Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private # privacy # web3 # blockchain # security 1 reaction Comments 2 comments 4 min read Launched: Pain Tracker v1.0.0 (Open Source, Local-First, Trauma-Informed) CrisisCore-Systems CrisisCore-Systems CrisisCore-Systems Follow Dec 25 '25 Launched: Pain Tracker v1.0.0 (Open Source, Local-First, Trauma-Informed) # showdev # opensource # react # privacy Comments Add Comment 2 min read Recreate Physical Calendar Notes Digitally — With Absolute Privacy techno kraft techno kraft techno kraft Follow Dec 25 '25 Recreate Physical Calendar Notes Digitally — With Absolute Privacy # showdev # productivity # privacy # webdev 1 reaction Comments Add Comment 2 min read I Built a Privacy-First Currency Converter in 2 Weeks Demetria Darjean Demetria Darjean Demetria Darjean Follow Dec 24 '25 I Built a Privacy-First Currency Converter in 2 Weeks # showdev # webdev # javascript # privacy Comments Add Comment 2 min read Why I Built a Client-Side Alternative to Common Dev Tools Sam T Sam T Sam T Follow Dec 29 '25 Why I Built a Client-Side Alternative to Common Dev Tools # showdev # webdev # privacy # productivity Comments 1 comment 2 min read Verifiable Compute for Onchain Prop Trading: How Carrotfunding Uses ROFL Manav Manav Manav Follow Dec 25 '25 Verifiable Compute for Onchain Prop Trading: How Carrotfunding Uses ROFL # web3 # blockchain # privacy # proptrading 2 reactions Comments 2 comments 2 min read x402: Turning HTTP 402 into a Real Payment Primitive Manav Manav Manav Follow Dec 25 '25 x402: Turning HTTP 402 into a Real Payment Primitive # privacy # blockchain # web3 # http 1 reaction Comments 2 comments 3 min read Why Oasis Is Backing Custody-Native Credit Infrastructure Manav Manav Manav Follow Dec 25 '25 Why Oasis Is Backing Custody-Native Credit Infrastructure # privacy # web3 # blockchain # infrastructure 2 reactions Comments 2 comments 2 min read Federated Learning or Bust: Architecting Privacy-First Health AI Beck_Moulton Beck_Moulton Beck_Moulton Follow Dec 28 '25 Federated Learning or Bust: Architecting Privacy-First Health AI # machinelearning # architecture # privacy # devops Comments Add Comment 3 min read No Complex Regular Expressions Required: The New SLS Data Masking Function Makes Privacy Protection Simpler and More Efficient ObservabilityGuy ObservabilityGuy ObservabilityGuy Follow Dec 24 '25 No Complex Regular Expressions Required: The New SLS Data Masking Function Makes Privacy Protection Simpler and More Efficient # data # privacy # tooling # cybersecurity Comments Add Comment 7 min read I built a "Privacy Firewall" for ChatGPT using Next.js 15 & WebAssembly (100% Offline) Arpit Singhal Arpit Singhal Arpit Singhal Follow Dec 23 '25 I built a "Privacy Firewall" for ChatGPT using Next.js 15 & WebAssembly (100% Offline) # showdev # nextjs # privacy # webdev 1 reaction Comments 1 comment 2 min read Midnight — The 4th-Generation Privacy Blockchain Bringing "Rational Privacy" to Developers | Introducing midnightexplorer.com Midnight Network Challenge: Enhance the Ecosystem Minh Le Dinh Minh Le Dinh Minh Le Dinh Follow Dec 29 '25 Midnight — The 4th-Generation Privacy Blockchain Bringing "Rational Privacy" to Developers | Introducing midnightexplorer.com # midnightchallenge # zk # privacy 5 reactions Comments Add Comment 3 min read Tokenomics' Hidden Flaw: Why Economic Models Need Privacy to Prevent Manipulation sid sid sid Follow Dec 25 '25 Tokenomics' Hidden Flaw: Why Economic Models Need Privacy to Prevent Manipulation # privacy # web3 # blockchain # security 1 reaction Comments 2 comments 5 min read Healthcare Data Breaches Have Become Cost Centers, Not Emergencies ZB25 ZB25 ZB25 Follow Dec 24 '25 Healthcare Data Breaches Have Become Cost Centers, Not Emergencies # cybersecurity # healthcare # databreach # privacy Comments Add Comment 6 min read Is it possible to create powerful 3D photo animations with only browser tools and client-side processing? techno kraft techno kraft techno kraft Follow Dec 23 '25 Is it possible to create powerful 3D photo animations with only browser tools and client-side processing? # showdev # animation # privacy # webtools 1 reaction Comments Add Comment 2 min read The Ephemeral Signal Ethics Manifesto Nnamdi Okpala Nnamdi Okpala Nnamdi Okpala Follow Dec 26 '25 The Ephemeral Signal Ethics Manifesto # discuss # privacy # architecture # security Comments Add Comment 2 min read Explaining What Happens On-Chain vs Off-Chain Marycynthia Ihemebiwo Marycynthia Ihemebiwo Marycynthia Ihemebiwo Follow Dec 22 '25 Explaining What Happens On-Chain vs Off-Chain # privacy # opensource # blockchain # beginners Comments Add Comment 1 min read Adding a Missing Example for Privacy Controls Kalu Jennifer Kalu Jennifer Kalu Jennifer Follow Dec 21 '25 Adding a Missing Example for Privacy Controls # privacy # web3 # documentation # opensource Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:29 |
https://opensource.org/sponsors | Our supporters – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home Our supporters Our supporters The following companies are generously supporting the OSI. Interested in sponsoring, or partnering with, the OSI? Please see our Sponsorship Prospectus and our Annual Report . Please contact us to find out more about how your company can promote Open Source development, communities and software. Titanium Platinum Gold Silver Bronze Partner Community While we are very grateful for their support, we do not endorse these or any other companies. The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and by public institutions. The Open Source Initiative is a California 501(c)3 non-profit. Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:29 |
https://stackoverflow.blog/2025/01/22/why-all-developers-should-adopt-a-safety-critical-mindset/ | Why all developers should adopt a safety-critical mindset - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 22, 2025 Why all developers should adopt a safety-critical mindset Is anyone designing software where failures don't have consequences? Credit: Alexandra Francis In a world where software powers everything from spacecraft to banking systems, the consequences of failure can be devastating. Even minor software failures can have far-reaching consequences—we’ve seen platforms crash, businesses lose millions, and users lose trust, all due to bugs or breakdowns that could have been prevented. Just ask Crowdstrike. This raises an important question: Shouldn’t all developers think about safety, reliability, and trust, even when building apps or services that don’t seem critical? The answer is a resounding yes. Regardless of what type of software you’re building, adopting the principles of safety-critical software can help you create more reliable, trustworthy, and resilient systems. It's not about over-engineering; it's about taking responsibility for what happens when things inevitably go wrong. All software should be considered high-stakes The first principle of safety-critical software is that every failure has consequences. In industries like aerospace, medical devices, or automotive, “criticality” is often narrowly defined as failures risking loss of life or major assets. This definition, while appropriate for these fields, overlooks the broader impacts failures can have in other contexts—lost revenue, eroded user trust, or disruptions to daily operations. Expanding the definition of criticality means recognizing that every system interacts with users, data, or processes in ways that can have cascading effects. Whether the stakes involve safety, financial stability, or user experience, treating all software as potentially high-stakes helps developers build systems that are resilient, reliable, and ready for the unexpected. Adopting a safety-critical mindset means anticipating failures and understanding their ripple effects. By preparing for breakdowns, developers improve communication, design for robustness, and ultimately deliver systems that users can trust to perform under pressure. Designing for inevitable failure Failure isn’t just possible—it’s inevitable. Every system will eventually encounter some condition it wasn’t explicitly designed for and how it responds to that failure defines whether it causes a major issue or is just a bump in the road. For safety-critical systems, this means implementing two-fault tolerance, where multiple failures can occur without losing functionality or data. But you don’t need to go that far for everyday software. Simple failover mechanisms, active-passive system designs, and reducing single points of failure can dramatically increase resilience. One effective approach is active-passive system design, where an active component handles requests while a standby component remains idle until needed. If the active component fails, the passive one takes over, minimizing downtime. In more dynamic systems, proxies and load balancers play a key role in distributing traffic across multiple instances or services, ensuring no single point of failure can bring the entire system down. Load balancing also provides the ability to shift workloads dynamically, allowing systems to respond to surges or outages more effectively.Modern distributed architectures, like containerization and microservices, build on these principles to further enhance resilience. By breaking applications into smaller, independently deployable units, microservices architectures avoid the fragility of monoliths, where a single failure can cascade across the system. Distributed systems also make it easier to isolate and recover from failures, as individual services can be restarted or rerouted without affecting others. Developers can also integrate continuous monitoring and observability to detect problems early. The faster you can detect and diagnose a problem, the faster you can fix it—often before users even notice. Beyond detection, testing for failure is equally critical. Practices like chaos engineering, which involve intentionally introducing faults into a system, help developers identify weak points and ensure systems can recover gracefully under stress. Whether it’s a memory leak, performance degradation, or data inconsistency, these strategies work alongside observability as proactive defenses against failure. Learning from safety-critical practices Safety-critical industries don’t just rely on reactive measures; they also invest heavily in proactive defenses. Defensive programming is a key practice here, emphasizing robust input validation, error handling, and preparation for edge cases. This same mindset can be invaluable in non-critical software development. A simple input error could crash a service if not properly handled—building systems with this in mind ensures you’re always anticipating the unexpected. Rigorous testing should also be a norm, and not just unit tests. While unit testing is valuable, it's important to go beyond that, testing real-world edge cases and boundary conditions. Consider fault injection testing, where specific failures are introduced (e.g., dropped packets, corrupted data, or unavailable resources) to observe how the system reacts. These methods complement stress testing under maximum load and simulations of network outages, offering a clearer picture of system resilience. Validating how your software handles external failures will build more confidence in your code. Graceful degradation is another principle worth adopting. If a system does fail, it should fail in a way that’s safe and understandable. For example, an online payment system might temporarily disable credit card processing but allow users to save items in their cart or check account details. Similarly, a video streaming service might reduce playback quality instead of halting entirely. Users should be able to continue with reduced functionality, rather than experience total shutdowns, ensuring continuity of service and keeping user trust intact. Moreover, techniques like error detection, redundancy, and modular design allow systems to recover from failures more easily. In safety-critical environments, these are a given. In more general software development, these practices still make a difference in reducing risks and ensuring that failures don’t lead to catastrophic outcomes. While adopting safety-critical methods may seem like overkill for non-critical applications, even simplified versions of these principles can lead to more robust and user-friendly software. At its core, adopting a safety-critical mindset is about preparing for the worst while building for the best. Every piece of code matters. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Austin Spiegel Co-founder and CTO of Sift Austin’s early interest in manufacturing and space led him to study Computer Science at USC, where he shifted from game design to building real-world systems. At SpaceX, he contributed to spacecraft development, reusable vehicle data … testing observability failover contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://opensource.org/members | Get involved – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home Get involved Get involved Hundreds of individuals and organizations worldwide join as members and support as donors or sponsors of the OSI. They trust in our neutral stewardship of open source licensing and our role in enabling a global community. “I think this is an organization that you really should support, because they specifically focus on Open Source licenses. And I think that’s a very important area that needs continuous support and evaluation.” -Peter Zaitsev , Founder, Percona “Thank you OSI for protecting what open source means, so that everybody uses the same definition when we’re talking about open source.” -Emily Omier , Founder, Open Source Founders Summit “The Open Source Initiative does vital work defining, maintaining and keeping consistent the definition of what open source actually is.” -Michael Meeks , CEO, Collabora Productivity Membership Join OSI as an individual to belong to the organization that stewards the Open Source Definition. ✅ Voting rights ✅ Tax deductible ✅ Newsletter ✅ Discussions Become a member Donation You can make a one-time or recurring donation as an individual to directly support our mission. ✕ No voting rights ✅ Tax deductible ✅ Flexible giving options ✅ Anonymous if desired Make a donation Sponsorship Show your organization’s commitment to open source. Your funds advance OSI’s overall mission. ✕ No voting rights ✅ Tax deductible ✅ Various tiers ✅ Recognition Sponsor our work Our mission We are a non-profit organization with global scope, formed to educate and advocate for the benefits of Open Source and to build bridges among different constituencies in the Open Source community. ✅ Supporting a healthy ecosystem. ✅ Promoting worldwide collaboration. ✅ Educating about the value of Open Source. ✅ Advocating for frictionless innovation. Testimonials “I firmly believe that open source is the best way to build technology that’s collaborative, transparent and that’s impactful and the OSI crystallizes all these values in the same place.” -Florent Zara, Open Source Services Team Lead, Eclipse Foundation “I support OSI as a thought leader in the open source ecosystem because it provides a set of norms that we can all agree on.” -Anais Concepcion, Co-CEO, Grist “The Open Source Initiative creates a level playing field for all commercial open source vendors to flourish.” -Sandro Groganz Head of Marketing, Passbolt “Thank you OSI for protecting what open source means, so that everybody uses the same definition when we’re talking about open source.” -Raphael Michel , Managing Director, pretix FAQ: Membership, Donations, Sponsorship Who can become an OSI member? OSI membership is open to any individual. If you live in a country under U.S. embargo, please contact us for assistance. Companies cannot become voting members. What membership levels are available and what do they include? OSI offers two paid membership tiers. Supporting Members ($50/year) can nominate and vote for OSI’s Board of Directors, run for a board seat, and get early access to events, workshops, and member discounts. Professional Members ($300/year) get all Supporting Member benefits plus priority access to meetings and exclusive OSI content. We also offer a free Basic Membership that shows your support but does not include voting rights. How long does membership last, and how do I renew? A membership lasts 12 months from your join date. When you sign up, you can choose to renew automatically. Otherwise, we will remind you to renew each year. You can renew online through the OSI member portal or by purchasing a new membership when your term expires. What do OSI membership fees support? Membership dues fund OSI’s programs and staff. Your support pays professional staff salaries and covers activities that promote and protect open source software around the world. In short, your membership helps OSI fulfill its mission as the steward of the Open Source Definition and community. Are OSI membership fees tax-deductible? Yes. The OSI is a California-based 501(c)(3) public charity, so membership dues (and donations) are generally tax-deductible for U.S. taxpayers. As always, please consult your tax advisor about deductibility in your situation. How can I donate to the OSI? You can give by mail or online. Online, you can donate via the OSI member portal. We also accept micro-donations via Flattr. You can also send a check payable to “Open Source Initiative” to our address. Are donations to the OSI tax-deductible? Yes. The OSI is a U.S. 501(c)(3) nonprofit, so donations are generally tax-deductible for U.S. taxpayers. If you are a U.S. donor, you can claim your charitable gift on your federal tax return (check with a tax professional for details). Can I make a one-time gift or a recurring donation? Yes. Our donation form lets you choose a one-time contribution or an annual recurring donation. When you donate online, simply select “One-Time” or “Yearly” on the form. Who can sponsor the OSI and how do we get involved? Any company or organization can become an OSI sponsor. To explore sponsorship, interested organizations should contact OSI . Please see our Sponsorship Prospectus or reach out through the OSI contact form for details. What are the benefits of sponsoring OSI? Sponsors receive public recognition and networking opportunities. For example, sponsors are featured on OSI’s supporters page with their logos displayed prominently. Depending on the sponsorship level, benefits can include logo placement on the website, mentions in newsletters and social media, and invitations to special OSI events. Full details are available in the Sponsorship Prospectus. Does OSI endorse its sponsors or their products? No. OSI is a neutral steward of the Open Source Definition and community. Listing a sponsor on our site is simply a way to thank their support; OSI does not endorse any particular company, product, or service. Does sponsorship give my organization influence over OSI’s decisions or policies? No. Sponsorship of the OSI is a financial contribution that supports our mission, not a governance role. Sponsors do not receive any special influence over OSI’s decisions, licensing approvals, or policy positions. As a 501(c)(3) nonprofit, OSI maintains strict neutrality and independence in all of its work. This ensures that open source remains a community-led effort, not driven by commercial interests. Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:29 |
https://forms.gle/btDwenPF7M3hgSvw7 | X DSA Researcher Application 자바스크립트가 브라우저에서 활성화되어 있지 않아 이 파일을 열 수 없습니다. 활성화하고 새로고침하세요. X DSA Researcher Application This is an application form for research access to public X data pursuant to Article 40(12) of the Digital Services Act (Regulation (EU) 2022/2065, DSA). The applicant must meet the criteria defined in Article 40 Sections 8 & 12 to receive access to public X data. Please submit the application below with as much detail as possible, and X will contact you soon at the email address you provide below. If you do not meet the criteria or otherwise wish to access the X API, please review our subscription options here . Google에 로그인 하여 진행상황을 저장하세요. 자세히 알아보기 * 표시는 필수 질문임 Contact Name * 내 답변 Contact Email Address * Please use the email address associated with your organization. We will not use this email address for any purpose besides communicating with you regarding this application and any provision of X data. 내 답변 Name of Organization * 내 답변 Organization Affiliation * Describe your organization’s affiliation (e.g. university, lab, NGO, etc.) and not-for-profit status. 내 답변 Funding * Please disclose the funding of your research, including amounts raised and direct and indirect sources of funding. 내 답변 Commercial Interests * Is your organization independent from commercial interests? Please provide detailed evidence that substantiates your answer. In addition to the information provided in the question above regarding funding, relevant information includes, but is not limited to, the following: (i) purpose and mission, (ii) information about your board members, officers, and individuals with access to X data, (iii) previously published research, (iv) affiliation with other organizations, networks, or causes, and (v) the organization’s membership, shareholders, or grant recipients. 내 답변 Data Security and Confidentiality * Are you capable of fulfilling the specific data security and confidentiality requirements corresponding to each request and to protect personal data? Please describe the appropriate technical and organizational measures you have put in place to this end, including any compliance certifications. 내 답변 Description of Research * Please describe in detail the research for which you wish to use data from the X platform. Please describe whether the research will contribute to the detection, identification and understanding of systemic risks in the Union pursuant to Article 34(1), whether the X data will serve any other purpose as part of your research, and whether you plan to publish your research in a particular medium. 내 답변 Scope of X Data * What X data do you wish to receive? Please describe how that data is needed for the research described above and not otherwise currently accessible to you by other sufficient means. 내 답변 Timeframe * How long do you need access to this data? Please provide a detailed justification for this timeframe. 내 답변 Developer Agreement * You agree and acknowledge that, if your application is approved, your access to the X API is governed by the X Developer Agreement and Developer Policy . I agree 필수 제출 양식 지우기 Google Forms를 통해 비밀번호를 제출하지 마세요. 이 설문지는 X Corp. 내부에서 생성되었습니다. 양식이 의심스러운가요? 보고서 설문지 고객센터 양식 소유자에게 문의 Forms 개선 돕기 보고서 | 2026-01-13T08:48:29 |
https://opensource.org/osd/ | The Open Source Definition – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home The Open Source Definition The Open Source Definition Page created on July 7, 2006 | Last modified on February 16, 2024 Introduction Open source doesn’t just mean access to the source code. The distribution terms of open source software must comply with the following criteria: 1. Free Redistribution The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale. 2. Source Code The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed. 3. Derived Works The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software. 4. Integrity of The Author’s Source Code The license may restrict source-code from being distributed in modified form only if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software. 5. No Discrimination Against Persons or Groups The license must not discriminate against any person or group of persons. 6. No Discrimination Against Fields of Endeavor The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research. 7. Distribution of License The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties. 8. License Must Not Be Specific to a Product The rights attached to the program must not depend on the program’s being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program’s license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution. 9. License Must Not Restrict Other Software The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open source software. 10. License Must Be Technology-Neutral No provision of the license may be predicated on any individual technology or style of interface. The Open Source Definition was originally derived from the Debian Free Software Guidelines (DFSG). Version 1.9, last modified, 2007-03-22 Here’s the historical “ Annotated OSD ” from the early 2000’s. Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:29 |
https://techcrunch.com/2022/04/15/us-officials-link-north-korean-lazarus-hackers-to-625m-axie-infinity-crypto-theft/ | N Korean Lazarus hackers tied to $625M theft TechCrunch Desktop Logo TechCrunch Mobile Logo Latest Startups Venture Apple Security AI Apps Events Podcasts Newsletters Search Submit Site Search Toggle Mega Menu Toggle Topics Latest AI Amazon Apps Biotech & Health Climate Cloud Computing Commerce Crypto Enterprise EVs Fintech Fundraising Gadgets Gaming Google Government & Policy Hardware Instagram Layoffs Media & Entertainment Meta Microsoft Privacy Robotics Security Social Space Startups TikTok Transportation Venture More from TechCrunch Staff Events Startup Battlefield StrictlyVC Newsletters Podcasts Videos Partner Content TechCrunch Brand Studio Crunchboard Contact Us Image Credits: NurPhoto / Chris Jung / Getty Images US officials link North Korean Lazarus hackers to $625M Axie Infinity crypto theft Carly Page 7:53 AM PDT · April 15, 2022 U.S. officials have linked North Korean state-backed hacking group Lazarus to the recent theft of $625 million in cryptocurrency from the Ronin Network, an Ethereum -based sidechain made for the popular play-to-earn game Axie Infinity . The Treasury Department’s Office of Foreign Assets Control (OFAC) on Thursday announced new sanctions against an Ethereum wallet belonging to Lazarus. Blockchain analysis firms Elliptic and Chainalysis have both confirmed that the U.S. Treasury’s wallet address is identical to the one used in the Ronin hack , which saw the attackers exploit the network for 173,600 ether, or about $597 million, and $25.5 million worth of the stablecoin USDC. The heist, which totaled $625 million at the time, is the largest decentralized finance hack to date, according to the DeFiYield REKT database , which tracks DeFi scams, hacks and exploits. The wallet itself — which held 148,000 ether as of Thursday — was discovered by the FBI as part of its ongoing investigation of the threat posed by North Korea and state-sponsored actors like Lazarus Group. Blockchain analysis firm Elliptic estimated that 14% of the stolen funds had already been laundered, while another $9.7 million worth is in intermediary wallets in preparation for laundering. The newly announced sanctions prohibit U.S. individuals and entities from making transactions with the identified Ethereum account. This ensures the state-sponsored group — which has previously been linked to a 2014 hack on Sony Pictures and the 2017 WannaCry ransomware attacks — can’t cash out through U.S.-based crypto exchanges any further funds they continue to hold. “Many commentators believe that crypto assets stolen by Lazarus Group are used to fund the state’s nuclear and ballistic missile programs,” Elliptic said. “With recent reports that North Korea may be again preparing for nuclear testing, today’s sanctions activity highlights the importance of ensuring that Lazarus Group is not able to successfully launder the proceeds of these attacks.” In an updated post about the incident, the Ronin Network, which is owned by developer group Sky Mavis, said it expects to deliver a full post-mortem of the crypto-heist by the end of the month. “We are still in the process of adding additional security measures before redeploying the Ronin Bridge to mitigate future risk,” Ronin says, adding that will bring its bridge back online “by the end of the month.” The bridge allows users to transfer funds between other blockchains and Axie Infinity and has been blocked off since the attack. Techcrunch event Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. San Francisco | October 13-15, 2026 W AITLIST NOW According to a recent report by blockchain analysis firm Chainalysis , North Korean hackers launched at least seven attacks on cryptocurrency platforms last year to steal almost $400 million worth of digital assets. As per the report, the Lazarus Group is suspected of carrying out the attacks. Topics Axie Infinity , blockchains , Crypto , cryptocurrencies , cryptography , decentralization , Elliptic , ethereum , Federal Bureau of Investigation , North Korea , ronin , Security , Sky Mavis , sony pictures , technology , United States Carly Page Sr. Reporter, Cybersecurity Carly Page was a Senior Reporter at TechCrunch, where she covered the cybersecurity beat. Prior to that, she had spent more than a decade in the technology industry, writing for titles including Forbes, TechRadar and WIRED. You can contact Carly securely on Signal at +441536 853956 View Bio Dates TBD Locations TBA Plan ahead for the 2026 StrictlyVC events. Hear straight-from-the-source candid insights in on-stage fireside sessions and meet the builders and backers shaping the industry. Join the waitlist to get first access to the lowest-priced tickets and important updates. Waitlist Now Most Popular Google announces a new protocol to facilitate commerce using AI agents Ivan Mehta The most bizarre tech announced so far at CES 2026 Lauren Forristal Yes, LinkedIn banned AI agent startup Artisan, but now it’s back Julie Bort OpenAI unveils ChatGPT Health, says 230 million users ask about health each week Amanda Silberling Techcrunch event Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. San Francisco | October 13-15, 2026 W AITLIST NOW How Quilt solved the heat pump’s biggest challenge Tim De Chant A viral Reddit post alleging fraud from a food delivery app turned out to be AI-generated Amanda Silberling Founder of spyware maker pcTattletale pleads guilty to hacking and advertising surveillance software Zack Whittaker Loading the next article Error loading the next article X LinkedIn Facebook Instagram youTube Mastodon Threads Bluesky TechCrunch Staff Contact Us Advertise Crunchboard Jobs Site Map Terms of Service Privacy Policy RSS Terms of Use Code of Conduct CES 2026 Elon Musk v OpenAI Clicks Communicator Gmail Larry Page Tech Layoffs ChatGPT © 2025 TechCrunch Media LLC. | 2026-01-13T08:48:29 |
https://www.youtube.com/user/AmazonWebServices/Cloud/ | Amazon Web Services - YouTube var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"GFEEDBACK","params":[{"key":"route","value":"channel.Cloud"},{"key":"is_owner","value":"false"},{"key":"is_alc_surface","value":"false"},{"key":"browse_id","value":"UCd6MoB9NC6uYN2grvUNT-Zg"},{"key":"browse_id_prefix","value":""},{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtvUTFOQnh6YTlmQSjbjZjLBjIKCgJLUhIEGgAgHg%3D%3D"}]},{"service":"GOOGLE_HELP","params":[{"key":"browse_id","value":"UCd6MoB9NC6uYN2grvUNT-Zg"},{"key":"browse_id_prefix","value":""}]},{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetChannelPage_rid","value":"0x2578957af091fbf9"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"maxAgeSeconds":300,"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRz3Q-TK6jfmE1Mtojz1ejAkdCsyiQI01QEMwRgkuswmIBwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["pageHeaderRenderer","pageHeaderViewModel","imageBannerViewModel","dynamicTextViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","flexibleActionsViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","descriptionPreviewViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sectionListRenderer","itemSectionRenderer","continuationItemRenderer","attributionViewModel","channelMetadataRenderer","twoColumnBrowseResultsRenderer","tabRenderer","channelVideoPlayerRenderer","shelfRenderer","horizontalListRenderer","gridVideoRenderer","metadataBadgeRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayToggleButtonRenderer","thumbnailOverlayNowPlayingRenderer","menuRenderer","menuServiceItemRenderer","menuNavigationItemRenderer","unifiedSharePanelRenderer","lockupViewModel","collectionThumbnailViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayViewModel","lockupMetadataViewModel","gridChannelRenderer","expandableTabRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","microformatDataRenderer"]},"ytConfigData":{"visitorData":"CgtvUTFOQnh6YTlmQSjbjZjLBjIKCgJLUhIEGgAgHg%3D%3D","rootVisualElementType":3611},"hasDecorated":true}},"contents":{"twoColumnBrowseResultsRenderer":{"tabs":[{"tabRenderer":{"endpoint":{"clickTrackingParams":"CCgQ8JMBGAUiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/@amazonwebservices/featured","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCd6MoB9NC6uYN2grvUNT-Zg","params":"EghmZWF0dXJlZPIGBAoCMgA%3D","canonicalBaseUrl":"/@amazonwebservices"}},"title":"홈","selected":true,"content":{"sectionListRenderer":{"contents":[{"itemSectionRenderer":{"contents":[{"channelVideoPlayerRenderer":{"videoId":"HhBph2M5ZaU","title":{"runs":[{"text":"Amazon Bedrock AgentCore와 Claude: 에이전트 AI를 통한 비즈니스 혁신 | Amazon Web Services","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=HhBph2M5ZaU","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"HhBph2M5ZaU","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2ed.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1e106987633965a5\u0026ip=1.208.108.242\u0026initcwndbps=3931250\u0026mt=1768293662\u0026oweuc="}}}}}}],"accessibility":{"accessibilityData":{"label":"Amazon Bedrock AgentCore와 Claude: 에이전트 AI를 통한 비즈니스 혁신 | Amazon Web Services 3분 19초"}}},"description":{"runs":[{"text":"많은 기업이 에이전트 AI를 개념 증명(PoC) 단계를 넘어서는 데 어려움을 겪고 있습니다. Amazon Bedrock AgentCore와 Claude가 프로덕션 환경에 즉시 적용 가능한 AI 에이전트를 대규모로 배포하는 것을 어떻게 더 쉽게 만들어 주는지 알아보세요.\n\n자세히 알아보기:\n📖 전체 블로그 게시물 읽기: "},{"text":"https://go.aws/4rmUcSj","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFBFU1NUQy02VEdqSEJmMmwtam5fU3VzUXNoQXxBQ3Jtc0tsU2lxTFVhcERqT2M2QlJQZUlYSWZLdXF1Z2RwUFREQmlGTnl3TWJ3eUVhc0R6UUxuZFlzUS1vWlNyblFwOWxZR3ZhRUNkVjdzaGJrMFdlcFo4cEZvS0dDTHYtZ0wyOHRyWVZneHZXYUtocEFnZ2pEOA\u0026q=https%3A%2F%2Fgo.aws%2F4rmUcSj","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFBFU1NUQy02VEdqSEJmMmwtam5fU3VzUXNoQXxBQ3Jtc0tsU2lxTFVhcERqT2M2QlJQZUlYSWZLdXF1Z2RwUFREQmlGTnl3TWJ3eUVhc0R6UUxuZFlzUS1vWlNyblFwOWxZR3ZhRUNkVjdzaGJrMFdlcFo4cEZvS0dDTHYtZ0wyOHRyWVZneHZXYUtocEFnZ2pEOA\u0026q=https%3A%2F%2Fgo.aws%2F4rmUcSj","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n🔧 Amazon Bedrock AgentCore 시작하기: "},{"text":"https://go.aws/4nJmvrP","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW5fUVRoSVdJQXJsaThoRngwNDRKd3dNMzA1Z3xBQ3Jtc0ttQVotODM5UDRKbF90bHhsQ3JVbWlWQkdsTHBOWUprWlE4bzZHbXRpbzNKNkE2YjBfX3c0aWNZN1NPMzBPdFJHQjhIQ21WaUhJUFJLSnRFcXlxN19YYUMwck9LcWdRYXZZdk9ZTHVjSnEtemE5UWViWQ\u0026q=https%3A%2F%2Fgo.aws%2F4nJmvrP","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW5fUVRoSVdJQXJsaThoRngwNDRKd3dNMzA1Z3xBQ3Jtc0ttQVotODM5UDRKbF90bHhsQ3JVbWlWQkdsTHBOWUprWlE4bzZHbXRpbzNKNkE2YjBfX3c0aWNZN1NPMzBPdFJHQjhIQ21WaUhJUFJLSnRFcXlxN19YYUMwck9LcWdRYXZZdk9ZTHVjSnEtemE5UWViWQ\u0026q=https%3A%2F%2Fgo.aws%2F4nJmvrP","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n🤖 Claude Sonnet 4.5 살펴보기: "},{"text":"https://go.aws/47o75lQ","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblhZd0FrdGF3a180NldRX0lrU1paR3BjOWtKZ3xBQ3Jtc0tseVFoQnkxbXN2Y21ZQlo4eHFiNjZKSTFSM2t1N0R3eC0zZWM4MXp6WjUteDRjbmF5eHFQQTJObS1NRkVRT0EtcjZyRDZrSktyS2hHOW16eXhhQnVvTDl6cTMtcWVXdTlpamZUNVM0MjJHNzlIQkN2NA\u0026q=https%3A%2F%2Fgo.aws%2F47o75lQ","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqblhZd0FrdGF3a180NldRX0lrU1paR3BjOWtKZ3xBQ3Jtc0tseVFoQnkxbXN2Y21ZQlo4eHFiNjZKSTFSM2t1N0R3eC0zZWM4MXp6WjUteDRjbmF5eHFQQTJObS1NRkVRT0EtcjZyRDZrSktyS2hHOW16eXhhQnVvTDl6cTMtcWVXdTlpamZUNVM0MjJHNzlIQkN2NA\u0026q=https%3A%2F%2Fgo.aws%2F47o75lQ","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n\nAWS 구독: "},{"text":"https://go.aws/subscribe","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW9qdlNONXJfYmlRNGRyZURVQ1QtMGl5OWY5QXxBQ3Jtc0tsVmEtZGdsczNSejg5ald5SEdJbGVHaHNmUjY5a0JUd25XLWtSY05ER1pvdW1VQVJISFJRMlA0VGx5bE1OOHVfdXA5RWJNTEFOY0FNVTB2RWJiZkFfSDNxQXhCWEhMLVR6VU1hM0lrdWlaMDdmMW9Qbw\u0026q=https%3A%2F%2Fgo.aws%2Fsubscribe","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW9qdlNONXJfYmlRNGRyZURVQ1QtMGl5OWY5QXxBQ3Jtc0tsVmEtZGdsczNSejg5ald5SEdJbGVHaHNmUjY5a0JUd25XLWtSY05ER1pvdW1VQVJISFJRMlA0VGx5bE1OOHVfdXA5RWJNTEFOY0FNVTB2RWJiZkFfSDNxQXhCWEhMLVR6VU1hM0lrdWlaMDdmMW9Qbw\u0026q=https%3A%2F%2Fgo.aws%2Fsubscribe","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n\n무료 AWS 계정 생성: "},{"text":"https://go.aws/signup","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0hzMDRUZl9DbFVXbjV3OVV0TmhkakxIR2ZlQXxBQ3Jtc0trRmRkUWNxM2tCT0tiTFI1ZEtDOV9RaW1IZlFsTzItRnZ1WGd3QlJ3RlMyN0lXYlVCR1dvZG5Wang1R3ROb0VjYmFHV0tISGRVVmdNTWlyVDFmdzFqM2MySjJsd1pqZmd5cXh4UUV0MUYtZUlWd3pCVQ\u0026q=https%3A%2F%2Fgo.aws%2Fsignup","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0hzMDRUZl9DbFVXbjV3OVV0TmhkakxIR2ZlQXxBQ3Jtc0trRmRkUWNxM2tCT0tiTFI1ZEtDOV9RaW1IZlFsTzItRnZ1WGd3QlJ3RlMyN0lXYlVCR1dvZG5Wang1R3ROb0VjYmFHV0tISGRVVmdNTWlyVDFmdzFqM2MySjJsd1pqZmd5cXh4UUV0MUYtZUlWd3pCVQ\u0026q=https%3A%2F%2Fgo.aws%2Fsignup","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\nAWS 무료 체험: "},{"text":"https://go.aws/free","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbm80My1BVkp0aUl2c2R1S1hTSDk1ckNpbFJ6UXxBQ3Jtc0tsYXFYRjVkQUNaMUVJV2R5UW5IQWtoay1LSnN1cEhobWc4aHluUlJuY3h6SVFCb1dUR05SYjgzdzFSWG5URmUySldPVHlVQmxnNFF3ZElINWZfQXZsSXd3cmNpQ29rWEViU2p5dWJyR0dTXzJ0U0N3MA\u0026q=https%3A%2F%2Fgo.aws%2Ffree","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbm80My1BVkp0aUl2c2R1S1hTSDk1ckNpbFJ6UXxBQ3Jtc0tsYXFYRjVkQUNaMUVJV2R5UW5IQWtoay1LSnN1cEhobWc4aHluUlJuY3h6SVFCb1dUR05SYjgzdzFSWG5URmUySldPVHlVQmxnNFF3ZElINWZfQXZsSXd3cmNpQ29rWEViU2p5dWJyR0dTXzJ0U0N3MA\u0026q=https%3A%2F%2Fgo.aws%2Ffree","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n전문가에게 문의: "},{"text":"https://go.aws/contact","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbG5uMm53cVFxTnFNb3FHS3FsNDZHejNEOTNaZ3xBQ3Jtc0trMmpwTmpVOVBIZlJHWGU3Y1laWXJNU25lQlViUzdaQmVQV2ZvNElPbGN5NGszaFNJTGxIMGNsdFZ4bmREdkFMRmM2OXVVOEQ4X2xPV0FWZjN0dWNqOS1zZGVqRjhtSEswdGFaQ2NOZUpUZE1GQ212bw\u0026q=https%3A%2F%2Fgo.aws%2Fcontact","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbG5uMm53cVFxTnFNb3FHS3FsNDZHejNEOTNaZ3xBQ3Jtc0trMmpwTmpVOVBIZlJHWGU3Y1laWXJNU25lQlViUzdaQmVQV2ZvNElPbGN5NGszaFNJTGxIMGNsdFZ4bmREdkFMRmM2OXVVOEQ4X2xPV0FWZjN0dWNqOS1zZGVqRjhtSEswdGFaQ2NOZUpUZE1GQ212bw\u0026q=https%3A%2F%2Fgo.aws%2Fcontact","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n더 알아보기: "},{"text":"https://go.aws/more","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbWlZNUhVaHNoU2tRdk1iUDZNMHdib0VjdHNhUXxBQ3Jtc0ttZHZCeXlub3I4MXBjdkM3by1SdFU3cDRSSHhJOV9KYjBvcnk1LVlCelk0WDd3YkszaF9FTVhYeUxkYUlUdHA2MzRadG1LTzhQSjlrSlFzY2lNcFdCX1dxTGVIYWM2Nmp5bGhpdUVBazBpS3U4QkVRcw\u0026q=https%3A%2F%2Fgo.aws%2Fmore","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbWlZNUhVaHNoU2tRdk1iUDZNMHdib0VjdHNhUXxBQ3Jtc0ttZHZCeXlub3I4MXBjdkM3by1SdFU3cDRSSHhJOV9KYjBvcnk1LVlCelk0WDd3YkszaF9FTVhYeUxkYUlUdHA2MzRadG1LTzhQSjlrSlFzY2lNcFdCX1dxTGVIYWM2Nmp5bGhpdUVBazBpS3U4QkVRcw\u0026q=https%3A%2F%2Fgo.aws%2Fmore","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n\n다음 단계:\nAnalyst Research에서 AWS 살펴보기: "},{"text":"https://go.aws/reports","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqazNqLVh4MklBRS1MNE5BYXAzZ1hQU2VvZFZOUXxBQ3Jtc0tuWUREbUJnVk0yQjRGU3V0TE9yeXh5RndTR3NJZ3pPeUd1WElrVWItNEgxb0pjRk9jTnFmYVI4b1kyTVEtLVJfY0ZGZEJyQnkxZzh4dEI0bkdFNzJUbnliVVlvRzA1Zk5HckNXNFhiTFhkZERYckw1dw\u0026q=https%3A%2F%2Fgo.aws%2Freports","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqazNqLVh4MklBRS1MNE5BYXAzZ1hQU2VvZFZOUXxBQ3Jtc0tuWUREbUJnVk0yQjRGU3V0TE9yeXh5RndTR3NJZ3pPeUd1WElrVWItNEgxb0pjRk9jTnFmYVI4b1kyTVEtLVJfY0ZGZEJyQnkxZzh4dEI0bkdFNzJUbnliVVlvRzA1Zk5HckNXNFhiTFhkZERYckw1dw\u0026q=https%3A%2F%2Fgo.aws%2Freports","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\nAWS에서 실행되는 소프트웨어 검색, 배포 및 관리: "},{"text":"https://go.aws/marketplace","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGVBQTIxQWVyS1gzMFpBWXdWZG4wZnFaZTNfd3xBQ3Jtc0tuUURYeC1iV2ZwdnI4b1VVb1hMc04yTld0MGJkN3ZhNGFmT3lVb1B2ejZMcnpNOXd3d0o4SFl2UDdSWVh3eUgzOE1ualZxNmhETWFJVlRLUloxU3B1c1hzWGFzQ2JXM2dBWUppTlhSRnFnbjFEMlVaOA\u0026q=https%3A%2F%2Fgo.aws%2Fmarketplace","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbGVBQTIxQWVyS1gzMFpBWXdWZG4wZnFaZTNfd3xBQ3Jtc0tuUURYeC1iV2ZwdnI4b1VVb1hMc04yTld0MGJkN3ZhNGFmT3lVb1B2ejZMcnpNOXd3d0o4SFl2UDdSWVh3eUgzOE1ualZxNmhETWFJVlRLUloxU3B1c1hzWGFzQ2JXM2dBWUppTlhSRnFnbjFEMlVaOA\u0026q=https%3A%2F%2Fgo.aws%2Fmarketplace","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\nAWS 파트너 네트워크 가입: "},{"text":"https://go.aws/partners","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbF8tOXB1SEFYWk9Vci1zTVUwb3kyX1JLZlE4UXxBQ3Jtc0tsTG9nVG5GWUdDdkdBQ0NVcGdOSldieENOeGFXaEJ4UUVJTFNYbHF0VzNObFBVUHkwX1pCUzhTY0tmSk50dlhYVnRjZWV2REItQXNaSUpnR2pULXhHRk00Tm51cnc3c3BfWWtEM0dHTkNyeGkyX1UwZw\u0026q=https%3A%2F%2Fgo.aws%2Fpartners","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbF8tOXB1SEFYWk9Vci1zTVUwb3kyX1JLZlE4UXxBQ3Jtc0tsTG9nVG5GWUdDdkdBQ0NVcGdOSldieENOeGFXaEJ4UUVJTFNYbHF0VzNObFBVUHkwX1pCUzhTY0tmSk50dlhYVnRjZWV2REItQXNaSUpnR2pULXhHRk00Tm51cnc3c3BfWWtEM0dHTkNyeGkyX1UwZw\u0026q=https%3A%2F%2Fgo.aws%2Fpartners","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\nAmazon의 소프트웨어 구축 및 운영 방식에 대해 자세히 알아보기: "},{"text":"https://go.aws/library","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUlTQjRpYVcxOHl3Yjk0bElRV1VzYVVrSjhCd3xBQ3Jtc0tsN2hoNExNQ2RJNVZxbzNTY1ZOd3lZeE5ibFRsY2ZDWlRqSUZTQVV6dGtBLTdxeWxlWDB2dXd0YkJ0NDBEODR0N2NUUC1aLXRTTUJsT3U0UDlWeTRBUVd2blpIZXJ3SndFbnowc1c3RWlZMzhFbHA2Zw\u0026q=https%3A%2F%2Fgo.aws%2Flibrary","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbUlTQjRpYVcxOHl3Yjk0bElRV1VzYVVrSjhCd3xBQ3Jtc0tsN2hoNExNQ2RJNVZxbzNTY1ZOd3lZeE5ibFRsY2ZDWlRqSUZTQVV6dGtBLTdxeWxlWDB2dXd0YkJ0NDBEODR0N2NUUC1aLXRTTUJsT3U0UDlWeTRBUVd2blpIZXJ3SndFbnowc1c3RWlZMzhFbHA2Zw\u0026q=https%3A%2F%2Fgo.aws%2Flibrary","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n\nAWS 관련 기술적인 질문이 있으신가요?\nAWS 전문가 커뮤니티에 문의하세요. re:Post: "},{"text":"https://go.aws/3lPaoPb","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFZLSE1iV29nRFVVZU9SUUFlaGk4TU14RDBWUXxBQ3Jtc0ttaTJIR0MxcVVBcldkZ0tJNE8wQ0FRSWpqMWRoZXdmOFlEU0dWRldodE1XLVVSc2VINnVWdzZPUzdNSXNScG5FZVYzMkc1dmRlaFJ2dk5aMDNYM2dhWXZDZFhVRjRObVhuVFdNajJtYWRDS3UwbFFhOA\u0026q=https%3A%2F%2Fgo.aws%2F3lPaoPb","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbFZLSE1iV29nRFVVZU9SUUFlaGk4TU14RDBWUXxBQ3Jtc0ttaTJIR0MxcVVBcldkZ0tJNE8wQ0FRSWpqMWRoZXdmOFlEU0dWRldodE1XLVVSc2VINnVWdzZPUzdNSXNScG5FZVYzMkc1dmRlaFJ2dk5aMDNYM2dhWXZDZFhVRjRObVhuVFdNajJtYWRDS3UwbFFhOA\u0026q=https%3A%2F%2Fgo.aws%2F3lPaoPb","target":"TARGET_NEW_WINDOW","nofollow":true}}},{"text":"\n\nAWS를 선택해야 하는 이유\nAmazon Web Services는 세계에서 가장 포괄적이고 널리 채택된 클라우드로, 고객이 상상하는 모든 것을 구축할 수 있도록 지원합니다. Amazon Web Services는 업계 최고의 보안, 안정성 및 성능을 갖춘 가장 광범위한 글로벌 인프라를 기반으로 혁신적인 클라우드 기능과 전문 지식을 제공합니다.\n\n"},{"text":"#AgenticAI","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/agenticai","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUNCglhZ2VudGljYWkYAQ%3D%3D"}}},{"text":" "},{"text":"#AmazonBedrock","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/amazonbedrock","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gURCg1hbWF6b25iZWRyb2NrGAE%3D"}}},{"text":" "},{"text":"#Claude","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/claude","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUKCgZjbGF1ZGUYAQ%3D%3D"}}},{"text":" "},{"text":"#AWS","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/aws","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUHCgNhd3MYAQ%3D%3D"}}},{"text":" "},{"text":"#AIAgents","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/aiagents","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUMCghhaWFnZW50cxgB"}}},{"text":" "},{"text":"#EnterpriseAI","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/enterpriseai","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUQCgxlbnRlcnByaXNlYWkYAQ%3D%3D"}}},{"text":" "},{"text":"#MachineLearning","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/machinelearning","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUTCg9tYWNoaW5lbGVhcm5pbmcYAQ%3D%3D"}}},{"text":" "},{"text":"#Anthropic","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/anthropic","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUNCglhbnRocm9waWMYAQ%3D%3D"}}},{"text":" "},{"text":"#CloudComputing","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/cloudcomputing","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUSCg5jbG91ZGNvbXB1dGluZxgB"}}},{"text":" "},{"text":"#AmazonWebServices","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/amazonwebservices","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUVChFhbWF6b253ZWJzZXJ2aWNlcxgB"}}}]},"viewCountText":{"simpleText":"조회수 8,459회"},"publishedTimeText":{"runs":[{"text":"1개월 전"}]},"readMoreText":{"runs":[{"text":"자세히 알아보기","navigationEndpoint":{"clickTrackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=HhBph2M5ZaU","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"HhBph2M5ZaU","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr6---sn-ab02a0nfpgxapox-bh2ed.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=1e106987633965a5\u0026ip=1.208.108.242\u0026initcwndbps=3931250\u0026mt=1768293662\u0026oweuc="}}}}}}]}}}],"trackingParams":"CPQEELsvGAAiEwjcyvfwkIiSAxUv40wCHXhMIbY="}},{"itemSectionRenderer":{"contents":[{"shelfRenderer":{"title":{"runs":[{"text":"Just Announced","navigationEndpoint":{"clickTrackingParams":"CKcEENwcGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLhr1KZpdzukcqC4WBSssSqrQXDjAUMCp5","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLhr1KZpdzukcqC4WBSssSqrQXDjAUMCp5"}}}]},"endpoint":{"clickTrackingParams":"CKcEENwcGAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLhr1KZpdzukcqC4WBSssSqrQXDjAUMCp5","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLhr1KZpdzukcqC4WBSssSqrQXDjAUMCp5"}},"content":{"horizontalListRenderer":{"items":[{"gridVideoRenderer":{"videoId":"VgUUYKRm9zg","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/VgUUYKRm9zg/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDf8VPc8UAlecWRv10fCoPnvR8xCw","width":168,"height":94},{"url":"https://i.ytimg.com/vi/VgUUYKRm9zg/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLC72ClAtQCr07O90Bd_mDSIhIThAg","width":196,"height":110},{"url":"https://i.ytimg.com/vi/VgUUYKRm9zg/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDbTDpGldyLB6LJgyZtrvZQ24rU9A","width":246,"height":138},{"url":"https://i.ytimg.com/vi/VgUUYKRm9zg/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDBPs06OTATTXnOXk2hP25K82G1sQ","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Accelerate AI Model Customization with Amazon SageMaker AI | Amazon Web Services 1분 34초"}},"simpleText":"Accelerate AI Model Customization with Amazon SageMaker AI | Amazon Web Services"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 1,332회"},"navigationEndpoint":{"clickTrackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbYyBmctaGlnaFoYVUNkNk1vQjlOQzZ1WU4yZ3J2VU5ULVpnmgEFEPI4GGSqASJQTGhyMUtacGR6dWtjcUM0V0JTc3NTcXJRWERqQVVNQ3A1ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=VgUUYKRm9zg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"VgUUYKRm9zg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=56051460a466f738\u0026ip=1.208.108.242\u0026initcwndbps=3900000\u0026mt=1768293662\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Amazon Web Services","navigationEndpoint":{"clickTrackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/@amazonwebservices","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCd6MoB9NC6uYN2grvUNT-Zg","canonicalBaseUrl":"/@amazonwebservices"}}}]},"badges":[{"metadataBadgeRenderer":{"style":"BADGE_STYLE_TYPE_SIMPLE","label":"자막","trackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"자막"}}}],"ownerBadges":[{"metadataBadgeRenderer":{"icon":{"iconType":"CHECK_CIRCLE_THICK"},"style":"BADGE_STYLE_TYPE_VERIFIED","tooltip":"인증됨","trackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"인증됨"}}}],"trackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbZAuO6bo4qMxYJWqgEiUExocjFLWnBkenVrY3FDNFdCU3NzU3FyUVhEakFVTUNwNQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 1.3천회"}},"simpleText":"조회수 1.3천회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CPMEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CPMEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"VgUUYKRm9zg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CPMEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["VgUUYKRm9zg"],"params":"CAQ%3D"}},"videoIds":["VgUUYKRm9zg"],"videoCommand":{"clickTrackingParams":"CPMEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=VgUUYKRm9zg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"VgUUYKRm9zg","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2sd.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=56051460a466f738\u0026ip=1.208.108.242\u0026initcwndbps=3900000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}},"trackingParams":"CPMEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"CPIEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPIEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtWZ1VVWUtSbTl6Zw%3D%3D"}}}}}},"trackingParams":"CPIEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtWZ1VVWUtSbTl6Zw%3D%3D","commands":[{"clickTrackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPEEEI5iIhMI3Mr38JCIkgMVL-NMAh14TCG2","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbY=","hasSeparator":true}}],"trackingParams":"CO4EEJQ1GAAiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"1분 34초"}},"simpleText":"1:34"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CPAEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"VgUUYKRm9zg","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"CPAEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"VgUUYKRm9zg"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CPAEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"CO8EEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CO8EEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"VgUUYKRm9zg","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CO8EEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["VgUUYKRm9zg"],"params":"CAQ%3D"}},"videoIds":["VgUUYKRm9zg"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"CO8EEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"BspjnO1Vjao","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/BspjnO1Vjao/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLCqfRQvAfHr8zrQx15xmQvpuoKLNg","width":168,"height":94},{"url":"https://i.ytimg.com/vi/BspjnO1Vjao/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLDNx1xlpXPfutue7fqziQQhCWjkjA","width":196,"height":110},{"url":"https://i.ytimg.com/vi/BspjnO1Vjao/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBZI1N5sO_QLTayFPeitjNpuoiZFg","width":246,"height":138},{"url":"https://i.ytimg.com/vi/BspjnO1Vjao/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLDYYxESwd0iYlBPaCnk6tZFKKAlcQ","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Get Started with Serverless Model Customization Using Amazon SageMaker AI | Amazon Web Services 2분 46초"}},"simpleText":"Get Started with Serverless Model Customization Using Amazon SageMaker AI | Amazon Web Services"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 1,562회"},"navigationEndpoint":{"clickTrackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbYyBmctaGlnaFoYVUNkNk1vQjlOQzZ1WU4yZ3J2VU5ULVpnmgEFEPI4GGSqASJQTGhyMUtacGR6dWtjcUM0V0JTc3NTcXJRWERqQVVNQ3A1ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BspjnO1Vjao","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BspjnO1Vjao","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=06ca639ced558daa\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Amazon Web Services","navigationEndpoint":{"clickTrackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/@amazonwebservices","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCd6MoB9NC6uYN2grvUNT-Zg","canonicalBaseUrl":"/@amazonwebservices"}}}]},"badges":[{"metadataBadgeRenderer":{"style":"BADGE_STYLE_TYPE_SIMPLE","label":"자막","trackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"자막"}}}],"ownerBadges":[{"metadataBadgeRenderer":{"icon":{"iconType":"CHECK_CIRCLE_THICK"},"style":"BADGE_STYLE_TYPE_VERIFIED","tooltip":"인증됨","trackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"인증됨"}}}],"trackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbZAqpvW6s7zmOUGqgEiUExocjFLWnBkenVrY3FDNFdCU3NzU3FyUVhEakFVTUNwNQ==","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 1.5천회"}},"simpleText":"조회수 1.5천회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"CO0EEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CO0EEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"BspjnO1Vjao","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"CO0EEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["BspjnO1Vjao"],"params":"CAQ%3D"}},"videoIds":["BspjnO1Vjao"],"videoCommand":{"clickTrackingParams":"CO0EEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=BspjnO1Vjao","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"BspjnO1Vjao","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-jwwe7.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=06ca639ced558daa\u0026ip=1.208.108.242\u0026initcwndbps=3695000\u0026mt=1768293662\u0026oweuc="}}}}}}}]}},"trackingParams":"CO0EEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"COwEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COwEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtCc3Bqbk8xVmphbw%3D%3D"}}}}}},"trackingParams":"COwEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtCc3Bqbk8xVmphbw%3D%3D","commands":[{"clickTrackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COsEEI5iIhMI3Mr38JCIkgMVL-NMAh14TCG2","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbY=","hasSeparator":true}}],"trackingParams":"COgEEJQ1GAEiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"2분 46초"}},"simpleText":"2:46"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COoEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"BspjnO1Vjao","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"COoEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"BspjnO1Vjao"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COoEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COkEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COkEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"BspjnO1Vjao","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COkEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["BspjnO1Vjao"],"params":"CAQ%3D"}},"videoIds":["BspjnO1Vjao"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현재 재생목록에 추가"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COkEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"thumbnailOverlayNowPlayingRenderer":{"text":{"runs":[{"text":"지금 재생 중"}]}}}]}},{"gridVideoRenderer":{"videoId":"pO2rZ6MoN1Y","thumbnail":{"thumbnails":[{"url":"https://i.ytimg.com/vi/pO2rZ6MoN1Y/hqdefault.jpg?sqp=-oaymwEiCKgBEF5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLBWzwwmdMHqISiuTdHL-qm9MNQ5-g","width":168,"height":94},{"url":"https://i.ytimg.com/vi/pO2rZ6MoN1Y/hqdefault.jpg?sqp=-oaymwEiCMQBEG5IWvKriqkDFQgBFQAAAAAYASUAAMhCPQCAokN4AQ==\u0026rs=AOn4CLANSIMbWEyHC6Wqe_fPXxj6XKNhuA","width":196,"height":110},{"url":"https://i.ytimg.com/vi/pO2rZ6MoN1Y/hqdefault.jpg?sqp=-oaymwEjCPYBEIoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBM0QScQqJpoipmbIxunCAYPN0bTA","width":246,"height":138},{"url":"https://i.ytimg.com/vi/pO2rZ6MoN1Y/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=\u0026rs=AOn4CLBOMdSabEGqov4URA4lh9dQhvHW5Q","width":336,"height":188}]},"title":{"accessibility":{"accessibilityData":{"label":"Introducing Amazon Nova 2 Sonic | Amazon Web Services 3분 51초"}},"simpleText":"Introducing Amazon Nova 2 Sonic | Amazon Web Services"},"publishedTimeText":{"simpleText":"1개월 전"},"viewCountText":{"simpleText":"조회수 3,429회"},"navigationEndpoint":{"clickTrackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbYyBmctaGlnaFoYVUNkNk1vQjlOQzZ1WU4yZ3J2VU5ULVpnmgEFEPI4GGSqASJQTGhyMUtacGR6dWtjcUM0V0JTc3NTcXJRWERqQVVNQ3A1ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pO2rZ6MoN1Y","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pO2rZ6MoN1Y","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a4edab67a3283756\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}},"shortBylineText":{"runs":[{"text":"Amazon Web Services","navigationEndpoint":{"clickTrackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"url":"/@amazonwebservices","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCd6MoB9NC6uYN2grvUNT-Zg","canonicalBaseUrl":"/@amazonwebservices"}}}]},"badges":[{"metadataBadgeRenderer":{"style":"BADGE_STYLE_TYPE_SIMPLE","label":"자막","trackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"자막"}}}],"ownerBadges":[{"metadataBadgeRenderer":{"icon":{"iconType":"CHECK_CIRCLE_THICK"},"style":"BADGE_STYLE_TYPE_VERIFIED","tooltip":"인증됨","trackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibilityData":{"label":"인증됨"}}}],"trackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbZA1u6gmfrs6vakAaoBIlBMaHIxS1pwZHp1a2NxQzRXQlNzc1NxclFYRGpBVU1DcDU=","shortViewCountText":{"accessibility":{"accessibilityData":{"label":"조회수 3.4천회"}},"simpleText":"조회수 3.4천회"},"menu":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"현재 재생목록에 추가"}]},"icon":{"iconType":"ADD_TO_QUEUE_TAIL"},"serviceEndpoint":{"clickTrackingParams":"COcEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COcEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"pO2rZ6MoN1Y","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COcEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pO2rZ6MoN1Y"],"params":"CAQ%3D"}},"videoIds":["pO2rZ6MoN1Y"],"videoCommand":{"clickTrackingParams":"COcEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=pO2rZ6MoN1Y","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"pO2rZ6MoN1Y","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr4---sn-ab02a0nfpgxapox-bh2z6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a4edab67a3283756\u0026ip=1.208.108.242\u0026initcwndbps=4452500\u0026mt=1768293662\u0026oweuc="}}}}}}}]}},"trackingParams":"COcEEP6YBBgHIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuNavigationItemRenderer":{"text":{"runs":[{"text":"재생목록에 저장"}]},"icon":{"iconType":"BOOKMARK_BORDER"},"navigationEndpoint":{"clickTrackingParams":"COYEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COYEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","showSheetCommand":{"panelLoadingStrategy":{"requestTemplate":{"panelId":"PAadd_to_playlist","params":"-gYNCgtwTzJyWjZNb04xWQ%3D%3D"}}}}}},"trackingParams":"COYEEJSsCRgIIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"공유"}]},"icon":{"iconType":"SHARE"},"serviceEndpoint":{"clickTrackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtwTzJyWjZNb04xWQ%3D%3D","commands":[{"clickTrackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbbKAQTqnZ7C","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"COUEEI5iIhMI3Mr38JCIkgMVL-NMAh14TCG2","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}},"trackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbY=","hasSeparator":true}}],"trackingParams":"COIEEJQ1GAIiEwjcyvfwkIiSAxUv40wCHXhMIbY=","accessibility":{"accessibilityData":{"label":"작업 메뉴"}}}},"thumbnailOverlays":[{"thumbnailOverlayTimeStatusRenderer":{"text":{"accessibility":{"accessibilityData":{"label":"3분 51초"}},"simpleText":"3:51"},"style":"DEFAULT"}},{"thumbnailOverlayToggleButtonRenderer":{"isToggled":false,"untoggledIcon":{"iconType":"WATCH_LATER"},"toggledIcon":{"iconType":"CHECK"},"untoggledTooltip":"나중에 볼 동영상","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COQEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"addedVideoId":"pO2rZ6MoN1Y","action":"ACTION_ADD_VIDEO"}]}},"toggledServiceEndpoint":{"clickTrackingParams":"COQEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/browse/edit_playlist"}},"playlistEditEndpoint":{"playlistId":"WL","actions":[{"action":"ACTION_REMOVE_VIDEO_BY_VIDEO_ID","removedVideoId":"pO2rZ6MoN1Y"}]}},"untoggledAccessibility":{"accessibilityData":{"label":"나중에 볼 동영상"}},"toggledAccessibility":{"accessibilityData":{"label":"추가됨"}},"trackingParams":"COQEEPnnAxgDIhMI3Mr38JCIkgMVL-NMAh14TCG2"}},{"thumbnailOverlayToggleButtonRenderer":{"untoggledIcon":{"iconType":"ADD_TO_QUEUE_TAIL"},"toggledIcon":{"iconType":"PLAYLIST_ADD_CHECK"},"untoggledTooltip":"현재 재생목록에 추가","toggledTooltip":"추가됨","untoggledServiceEndpoint":{"clickTrackingParams":"COMEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COMEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","addToPlaylistCommand":{"openMiniplayer":true,"videoId":"pO2rZ6MoN1Y","listType":"PLAYLIST_EDIT_LIST_TYPE_QUEUE","onCreateListCommand":{"clickTrackingParams":"COMEEMfsBBgEIhMI3Mr38JCIkgMVL-NMAh14TCG2ygEE6p2ewg==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/playlist/create"}},"createPlaylistServiceEndpoint":{"videoIds":["pO2rZ6MoN1Y"],"params":"CAQ%3D"}},"videoIds":["pO2rZ6MoN1Y"]}}]}},"untoggledAccessibility":{"accessibilityData":{"label":"현 | 2026-01-13T08:48:29 |
https://stackoverflow.blog/author/jeremy-teichmann/ | Jeremy Teichmann - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Jeremy Teichmann Tech Lead at Bosch Digital, builds the architecture behind Bosch’s AI products and services. Leading an international engineering team, he bridges innovation and reliability—designing scalable AI systems that turn ambitious ideas into dependable, future-ready solutions. October 20, 2025 From multilingual semantic search to virtual assistants at Bosch Digital From sprawling PDFs to a fast, factual conversational assistant. Daly Singh , Jeremy Teichmann 4 comment s AI contributed CC BY-SA 4.0 Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://stackoverflow.blog/author/austin-spiegel/ | Austin Spiegel - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Austin Spiegel Austin’s early interest in manufacturing and space led him to study Computer Science at USC, where he shifted from game design to building real-world systems. At SpaceX, he contributed to spacecraft development, reusable vehicle data tools, and telemetry systems for Starlink. Now as a co-founder and Sift’s CTO, Austin leverages his experience to lead engineering, drive technical strategy, and create scalable software for machine innovators. January 22, 2025 Why all developers should adopt a safety-critical mindset Is anyone designing software where failures don't have consequences? Austin Spiegel 9 comment s testing observability failover contributed Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:29 |
https://stackoverflow.blog/2025/04/14/like-self-driving-cars-fully-ai-automated-sysadmins-don-t-exist/#comments | Like self-driving cars, fully AI-automated sysadmins don't exist - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Credit: Alexandra Francis The Society of Automotive Engineers has defined six levels of autonomous driving, ranging from Level 0—where the driver is responsible for everything—to Level 5—where a car performs all driving tasks under any conditions from Point A to Point B. The same spectrum can be used with system administration tasks to determine where and to what extent AI should be leveraged. If we apply the SAE’s levels to system administration tasks, it would look something like this: Level 0: No Automation Level 1: Assistance Required Level 2: Partial Automation Level 3: Conditional Automation Level 4: High Automation Level 5: Full Automation I thought about the sysadmin tasks ripest for AI-based automation and leveled them based on this spectrum. It’s important to note that all of this is a snapshot in time. As AI technology matures—and organizations’ comfort level with AI increases—what’s a Level 2 today may be a Level 3 or 4 tomorrow. It stands to reason, but none of the tasks I focused on landed at Level 0 or Level 1. As with cars, there are few system administration tasks that involve little to no automation. You could say something like racking servers and unraveling cables, but AI will never help detangle a Clark Griswold-level cable ball. You’ll also notice that there are no Level 5 tasks—yet. (More on that later.) I’m open to discussion and even argument on what I’ve come up with. I would also be really interested to hear how sysadmins would categorize these and other functions, as well as how they see the sysadmin role changing as AI matures. Level 2 System shutdown: In the traditional world, this could be a server shutdown, but in a modern, cloud-native world, it could be the shutdown of a critical application, load balanced across thousands of containers which run on hundreds of worker nodes. Either way, a human needs to be involved at a high level. There are a variety of reasons for initiating a shutdown, but humans should always be the ones driving them. At most, system shutdown should be Level 2 on the autonomy scale. AI can help suss out behavior anomalies or security threats. A “driver” assistance might prompt: “Are you really sure you want to shut that down?” “I noticed a couple of containers didn’t shut down correctly and were still serving traffic” “A critical task is hanging, and data hasn't been flushed to disk, so shutting down now could cause database corruption” Sort of like lane keeping. AI has the potential to really enlighten the user about the subtasks that are happening, and what their status is, in a completely new and transparent way. But the decision to initiate a shutdown should come only after a human has verified an issue and authorized defensive actions — feet on gas and brakes, if you will. Repairing system issues: Using AI to diagnose issues and then automatically fix those issues is a promising use case, but still a Level 2. I’ve had conversations with colleagues who used agentic AI to determine whether a set of pods in Kubernetes was healthy and recommend tools to use to fix them if they weren’t. At this point, we’re staying away from automatic fixes because the prospect is a little bit terrifying, but it’s something we may see in the future. If you basically control the inputs and the outputs—for example, saying, “Here's a set of tools you can use, and here are the things you can do with them”—AI is really good at figuring it all out. These capabilities could eventually be used to support safe automatic repairs, but might require some modifications to existing utilities. Level 3 Powering shells: Language models are being integrated into shells and CLIs , enabling users to enter natural-language commands rather than the cryptic shell commands that have been developed organically during the last 30 or 40 years—and that are very difficult to remember, much less understand . In this case, the commands are driving the operating system, but sysadmins need to keep their feet poised over the gas and the brake to ensure that telling an OS to copy a file or directory doesn’t result in, say, the deletion of a file or directory. With all that said, I’m giving this a Level 3 designation because we are starting to experiment with asking AI to make changes to the shell that currently require searching the web to find weird strings of characters that you copy and paste (and then pray will work). We’ve seen it work in simple use cases, but you still need a human in the loop—with the ability to take control at any time. Log analysis: Log analysis is tedious and tiring—like driving six hours on a freeway. Log data is essentially free form, natural language. Taking humans completely out of the log analysis process would be irresponsible, but we can use generative AI to reduce the cognitive load massively, say, 80-90%. For example, sysadmins could use generative AI to summarize a million lines of log data to a couple of sentences. Or, a sysadmin might analyze the log data using RAG, and ask interactive questions until they get the answer they're looking for, say, the cause of a problem they're seeing. This might be used in the future to comply with regulations which require “reading the logs.” But, a human still needs to evaluate the data and make decisions on what actions to take, which I’d say puts this use case at Level 3. Level 4 Generating config files: Generating config files is natural language processing, and natural language processing is something that AI innately does really well—a Level 4 task if ever there was one, especially when you constrain the inputs and outputs. In fact, I would say that generating config files is the same as asking AI to translate a sentence from Spanish to English or even to generate an original story with the theme of man vs. machine. But, while humans might want to write a poem, they probably don't want to manually generate config files. Using a language model to perform the task is a huge time saver that can potentially trim hundreds of human work hours down to just a few. With that said, humans must review and validate files to ensure that they, for example, address organization-specific factors or comply with industry standards. Humans also need to make sure config files are documented to help avoid problems with future translation. Updating config files: Updating config files is another tedious job that no one wants to do—the perfect candidate for generative AI and one that can be performed almost 100% autonomously. Almost. Sysadmins shouldn’t completely rely on AI to determine what config options have been deprecated and what new ones are in place—they must be the final arbiter of what’s OK and what’s not. However, a machine learning model can provide support along the way and is about as close to hands-off “driving” as sysadmins can get at this time. Put it this way: On a good day, when skies are clear and the road is straight, sysadmins could use AI to update (or generate) config files without putting their hands on the wheel, gas, or brake. But on a bad day, when you're driving up a mountain, in a snow storm, and need to swerve to avoid a deer deciding which side of the road he is going to run toward, sysadmins need to be fully back in the driver’s seat. Providing peer perspective: This one might not do much for sysadmins’ social pragmatic skills, but it can be done with little human interaction. Want to find out how peers have handled a certain challenge or the criteria they have used to evaluate a certain type of technology? Where sysadmins may have reached out to their human connections in the past, they can now enter any scenario they need help with into a generative AI tool and get loads of advice, anecdotes, stories, examples, and directions. However, just as when you have a conversation with a human, you have to consider the source—and biases and potential for hallucination—when you “talk” to AI. To be fair, in years past, I've been extremely frustrated with the guidance my colleagues have given me, so mileage may vary. Conclusion Level 5 is not possible with cars today, but there are times when Level 4 is achievable—under certain conditions. I wouldn’t put that much trust in autonomous driving during a blinding snowstorm or on a mountain road with hairpin turns, but I might on a sunny day driving along a long lonesome highway in a desert in Arizona. The same is true for system administration tasks. The extent to which AI can support sysadmin tasks is increasing quickly. But, in the end, the most powerful tool in a sysadmin's arsenal isn't AI—it's the combination of AI and human expertise. And that will likely always be the case. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Scott McCarty Global - Senior Principal Product Manager, Red Hat Enterprise Linux automation devops AI contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/04/03/from-training-to-inference-the-new-role-of-web-data-in-llms/ | From training to inference: The new role of web data in LLMs - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 3, 2025 From training to inference: The new role of web data in LLMs Data has always been key to LLM success, but it's becoming key to inference-time performance as well. Credit: Alexandra Francis Large language models (LLMs) have consumed massive parts of the internet, with the leading models using trillions of tokens during training. Meanwhile, AI startups are carving out niches by focusing on smaller, specialized models, leveraging more specific web data. As the race for the most comprehensive and accurate AI continues, competing giants are investing in three critical areas to maintain an edge: Compute, Talent, and Tokens . Of these, tokens —the data that LLMs use during training and inference— can define success or lead to failure. Web data remains central to the evolution of these systems, offering an unprecedented opportunity to shape and enhance their accuracy and relevance. This targeted use of web data allows LLMs to excel in niche applications, delivering domain-specific accuracy that general training alone cannot achieve. Yet, the role of web data extends far beyond the static datasets used during training and fine-tuning. As the demands placed on LLMs grow more dynamic, the use of web data has too, from its pivotal role in shaping LLMs to the emerging practice of using real-time web data for reasoning. As we move forward, one thing is clear: inference-time data is not just an enhancement; it is the foundation of a smarter, more responsive AI future. Tokens: The (potentially) unfair advantage. In the context of web data and inference-time data, tokens represent the fundamental building blocks of an LLM’s capabilities, but the role of tokens doesn't stop at training. Models using real-time data or inference data during the reasoning process can now fetch and process fresh tokens from live web data to enhance their outputs. The ability to dynamically integrate new information during inference supplements pre-trained and fine-tuned knowledge with the latest, most relevant data, ensuring outputs are accurate, timely, and context-aware. This dual role of web data—providing tokens for training and live tokens for inference—creates opportunities for AI companies to gain a competitive advantage. While compute and talent are essential, they often level out across competitors. Web data, by contrast, is not only harder to replicate but can also vary dramatically in quality. High-quality inference-time data ensures that the tokens integrated during reasoning are precise, relevant, and timely, giving models a tangible edge in real-world applications. Conversely, poor-quality or irrelevant web data can degrade performance, underscoring the critical importance of data curation and infrastructure in both training and inference contexts. Here are some examples of different contexts: Social media data: Tokens from social platforms help models understand informal language, slang, and real-time trends, which are essential for applications like sentiment analysis or chatbots. Structured datasets: Tokens from structured sources like product catalogs or financial reports enable precise, domain-specific understanding, critical for recommendation systems or financial forecasting. Niche contexts: Startups and specialized applications benefit from tokens sourced from hyper-relevant datasets tailored to their use cases, such as legal documents for legal tech or medical journals for healthcare AI. The birth of ‘reasoning’ Reasoning in artificial intelligence, particularly within large language models (LLMs), represents a significant leap in their ability to solve complex problems and adapt to dynamic situations. It goes beyond simple pattern recognition, enabling AI systems to deliberate, synthesize information, and arrive at informed conclusions. Initially, reasoning in LLMs was rooted in increasing computational depth during inference. By deploying greater computational power, models could evaluate multiple possible outcomes, refining their responses through iterative processes. While this approach brought incremental improvements, it exposed inherent limitations in relying solely on static pre-trained knowledge and brute computational force. Models trained on static datasets struggle to respond to dynamic, evolving contexts, leaving gaps in their ability to address real-world problems, which is how the true transformation in reasoning emerged. The integration of dynamic, real-time data into the decision-making process marked a pivotal shift from static reasoning, where models operated exclusively within the boundaries of their training datasets, to adaptive reasoning, which allows them to incorporate new, relevant information during inference. Dynamic reasoning equips models to engage with ever-changing contexts, validating outputs against live data and aligning responses with current realities. This opens doors to unprecedented adaptability, enabling AI systems to address problems and scenarios that extend far beyond their original training. Web data for reasoning Dynamic reasoning reflects the trajectory of AI systems toward greater contextual intelligence, but it cannot be done without web data. For example, an LLM tasked with analyzing current geopolitical events can enhance its output by integrating up-to-the-minute news data, ensuring accuracy and relevance. Similarly, in fields like healthcare or finance, the ability to incorporate recent findings or market trends empowers models to deliver insights that are not only accurate but also timely. This approach reduces reliance on outdated or incomplete information, making AI tools more aligned with real-world needs. Here’s the typical inference workflow: A user (either manually or via an API) enters a prompt into an LLM. This prompt could be anything from a simple query to a complex, multi-layered instruction. The LLM generates a response based on its pre-trained knowledge. Some advanced LLMs incorporate reasoning layers to improve the accuracy of their outputs. These layers may involve more computational effort or running agents to validate and refine the response. Add in real-time web data for additional information not included in training, process it at inference time, and incorporate it into the output. An important consideration is whether incorporating inference-time data affects the weights and biases of the LLM itself. It does not directly alter the model’s underlying structure. Instead, this process functions as an external reasoning layer, giving the model the option to incorporate real-time insights into its responses. This creates an important distinction: AI developers can continuously improve model accuracy without retraining the underlying LLM. The future of LLMs and real-time reasoning The integration of real-time web data into reasoning processes transforms LLMs from static repositories of knowledge into adaptive, dynamic agents capable of navigating change. This is the next phase in LLM development and is set to dominate the industry over the next one to two years. AI companies are looking to develop model capabilities with real-time reasoning that improve accuracy by bridging the gap between static training data and the real world that creates a competitive edge. An ecosystem is already emerging to meet the demands for real-time inference data, as companies look to outsource data collection to APIs. Companies and startups are already capitalizing on this trend, developing inference-time data as a service (ITDaaS) solutions. These solutions provide processed, context-specific data that models can query during inference, enabling them to enhance their reasoning capabilities without retraining their core architectures. The future of reasoning in AI will likely revolve around increasingly sophisticated systems that blend static pre-trained knowledge with dynamic, real-time inputs. For AI developers, the challenge will be to build robust data pipelines that can seamlessly integrate these real-time inputs while maintaining high standards of accuracy and efficiency. As the field matures, companies that invest in high-quality data sourcing, real-time integration infrastructure, and innovative inference-time tools will lead the way. In this, web data is the defining advantage that drives the evolution of AI. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Or Lenchner CEO of Bright Data data science generative AI data contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://dev.to/ajtiti/ajtiti-51-wzorce-w-chmurze-messaging#main-content | AjTiTi #51 - Wzorce w chmurze - messaging - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close AjTiTi [PL] Follow AjTiTi #51 - Wzorce w chmurze - messaging Sep 30 '22 play W dzisiejszym odcinku rozpoczynamy temat wzorców projektowych używanych w chmurze publicznej. Na pierwszy ogień idzie messaging, czyli: W jaki sposób przekazywać wiadomości pomiędzy serwisami, by obsłużyć asynchroniczność? Czy można przekazać duże ilości danych bez przeciążania brokera wiadomości? Czy da się sterować procesem biznesowym poprzez wiadomości? Jak zapewnić, że nasz proces na pewno się wykona? O tych, i kilku innych rzeczach, dowiesz się z 51. odcinka podcastu AjTiTi. Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/program/scoring-guidelines/ | CFP Scoring Guidelines | LF Events Skip to content Register Attend Experiences Instant Giveaways CNCF Slack Workspace Community Guidelines Diversity + Inclusion Scholarships Code of Conduct Sponsor Program Schedule Interactive Sessions Co-Located Events Contact Us View All Events Events All Upcoming Events ArgoCon Europe Past KubeCon + CloudNativeCon + other CNCF Events This event has passed. View the upcoming KubeCon + CloudNativeCon + other CNCF Events. CFP Scoring Guidelines Skip to page section Overview General Info + Dates to Remember Requirements + Considerations Review Process Best Practices Contact Us Overview Thank you in advance for your efforts as a member of the Program Committee for KubeCon + CloudNativeCon North America, taking place November 17 – 20, 2020. These are the official CFP Scoring Guidelines and Best Practices to use when reviewing your set of proposals. Please bookmark this page for easy reference. If you have any questions, please email Nanci Lancaster . Important Dates to Remember Program Committee Review Period: Friday, July 24–Tuesday, August 11, 2020 (2.5 weeks) Must have at least 50% of your assigned proposals reviewed: Tuesday, August 4, 2020 Must have 100% of your assigned proposals reviewed: 11:59 pm PDT, Tuesday, August 11, 2020 Track Chair Selection Period: Friday, August 14–Sunday, August 30, 2020 (2 weeks) Co-Chair Selection Period + Schedule Building: Tuesday, September 1–Sunday, September 20, 2020 (2.5 weeks) Schedule Announced: Thursday, October 1, 2020 Event Dates: November 17–20, 2020 Scoring Guidelines Grade the quality of each proposal on a 5 to 1 grading scale for content, originality, relevance, and speaker(s): 5 (Excellent) 4 (Above Average) 3 (Average) 2 (Below Average) 1 (Poor) Reminder: You are required to leave comments for each proposal you review, detailing the reasoning for your score. For each proposal, you will indicate whether or not you see it ultimately being part of the accepted program by stating “yes” or “no.” If you come across a proposal that does not seem to fit in the topic you are reviewing, you will indicate which topic you think the proposal fits best within an optional drop-down menu. Please still grade this proposal as you would any others within your review set. Review Process Best Practices Time Commitment: Please plan on committing 2-40 hours total to review all of the submissions in your track, depending on the amount you have been assigned. Aim to do 10-15 sessions at a time – then take a break / walk away. This helps prevent burnout and allows you to see more proposals with fresh eyes. Process Integrity: It is very important to protect the integrity of the review process, and to avoid undue bias, by keeping the submissions and your comments on them confidential. Please review and adhere to our Code of Conduct . Public & Author Interaction: To ensure an unbiased review process, program committee members should not discuss submissions with authors and/or the overall public (i.e., please no tweeting). Of course, please feel free to tweet about accepted sessions that you are excited to attend once the schedule has been published. Conflict of Interest: Reviewers are asked to wear their “KubeCon + CloudNativeCon” hats rather than the company or other affiliation when scoring submissions so that you rate all submissions fairly. If a submission was written by a colleague you work closely with or someone that you are seen to be associated with or in competition with, please skip by marking as a conflict of interest. Review Metrics: As listed above , the ranking system is divided into 5 options: 5 (Excellent), 4 (Above Average), 3 (Average), 2 (Below Average), 1 (Poor). It is important that you highlight your level of confidence in your recommendation and the reasons why you gave the score you did. When reviewing proposals, keep in mind the following criteria: Relevance – Does the content provide takeaways that are new and exciting vs information that was “so last year?” Is the content relevant to the conference? Originality – Is this a presentation that is original and not one that a speaker repeats at every conference? Is the way the content is presented original? Soundness – Does the content make sense in delivery or is it all over the place? Does the speaker seem to lack focus? Quality of Presentation – Is the proposal engaging and well thought out? Does the background material suggest the speaker will deliver this presentation effectively? Importance – How important is the content for the KubeCon + CloudNativeCon audience? Experience – Is this speaker a good person to deliver this presentation? Does their experience with the subject matter align with the proposed content? 30% Rule: You’ll be asked for each proposal, “Overall, do you want to see this session at this conference?” Only about 30% of your proposals should get a “yes” vote. Keynote Selections: To assist the track and co-chairs with keynote selection, you will answer the question for each proposal, “Would you recommend this talk for the keynote stage?” These should be talks that are the best of the best and would be incredibly exciting and engaging for the entire KubeCon + CloudNativeCon audience. Topic Re-Routing: If you believe a talk would be better suited in a different topic, please use the last question to indicate which topic . This proposal will be filtered into its suggested topic when given to the track chairs for review. Please still review and score the proposal in accordance with the content, speaker, relevance, and originality pieces, and indicate in the comments section why you feel this presentation should be in a different topic. Experience Level: Use your expert knowledge to assess the experience level for the audience to understand the presentation. If you feel the presentation is not the experience level the speaker indicated, please use this section in the form to indicate which experience would be a better fit. Speakers with multiple submissions: We will not accept more than one talk from the same speaker. If you are in the position of reviewing more than one strong proposal from the same speaker, you can help the program co-chairs by only giving one of them a response of “yes” when answering the question, “do you see this session being part of the accepted programming for this conference.” Please use your comments to indicate why you prefer one talk over another. Review Comments: Keep in mind that submitting authors may be a VP at a large company or a university student. Ensure your feedback is constructive, in particular for rejected proposals as we do receive requests for feedback and we may pass on some comments (though we would not associate them with you). Good examples of review elements include: Highlighting the positive aspects of a proposal. Providing constructive feedback, “It would have been helpful if…” and include facts when applicable. Avoid direct attacks “Their YouTube video gives me concerns about their speaking style” rather than “this person is a terrible speaker.” Panel Discussions: The ideal panel is comprised of diverse thought leaders who talk 80% of the time with 20% audience interaction. Some things to keep in mind when reviewing a panel submission: Is the panel diverse, is there a mix of gender on the panel? Note for all KubeCon + CloudNativeCon Events: All panels are required to have at least one speaker that does not identify as a man. Is the submission cohesive and does it provide a clear view of how the panel would progress for 35 minutes? Could they cover everything within the proposal in the given 35 minutes? Have they included any sample questions? Does the panel include panelists from different organizations, including the moderator? Research the panelists and moderator, if needed. Is their experience relevant to the topic? Will the panelists provide diverse perspectives or will they repeat the same thing four times? Are there any high-profile panelists? In the instance that 1-2 of the panelists are unable to attend how would it impact the panel? Breakout Sessions: A presentation is delivered by a topic expert with a fresh or unique point of view. Some things to keep in mind when reviewing presentation proposals: Is the submission well written? Is the topic relevant, original and are they considered to be subject matter experts? Are they talking about a specific product from their company? If so, is it engaging in a way that is not advertorial? Keep in mind that sessions that come across as a pitch or infomercial for their company are most often rated very poorly among the audience. Who is their target audience? Does the abstract and description match up with the expertise required? AMAs (Ask Me Anything): The ideal AMA has an engaging and interesting person as the “Me” for the attendees to want to ask them questions. These types of sessions could potentially be great for a keynote for how big of a draw this “Me” person is. Tutorials: A tutorial is a presentation that is delivered by 1 to 5 subject-matter experts over the course of 90-minutes. Some things to keep in mind when reviewing tutorials: Have the instructors (speakers) conducted a tutorial before? This should not be their first time teaching attendees a new skill. Are they engaging enough to hold a “class” for 90-minutes? Is the topic relevant, original and are they considered to be subject matter experts? Are the instructors from a diverse set of companies? (You want to sway away from tutorials in which the instructors all come from the same company) Contact Us If you require any assistance reviewing proposals or have questions about the review process or any of the best practices we have suggested, please contact Nanci Lancaster for assistance. Sponsors DIAMOND Platinum gold silver Start-up End User Diversity Supporters Media Partners Join the CNCF mailing list to learn more about KubeCon + CloudNativeCon and other upcoming CNCF events! By submitting this form, I consent to receive marketing emails from the LF and its projects regarding their events, training, research, developments, and related announcements. I understand that I can unsubscribe at any time using the links in the footers of the emails I receive. Privacy Policy . #KubeCon + #CloudNativeCon Register Experiences Instant Giveaways CNCF Slack Workspace Community Guidelines Diversity + Inclusion Scholarships Code of Conduct Sponsor Schedule Interactive Sessions Co-Located Events Contact Us Copyright © 2026 The Linux Foundation®. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page. Linux is a registered trademark of Linus Torvalds. Terms of Use | Privacy Policy | Bylaws | Antitrust Policy | Good Standing Policy . | 2026-01-13T08:48:30 |
https://dev.to/t/webdev/page/6#main-content | Web Development Page 6 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Web Development Follow Hide Because the internet... Create Post submission guidelines Be nice. Be respectful. Assume best intentions. Be kind, rewind. Older #webdev posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I built a free URL shortener with QR codes and click tracking — looking for feedback Ivan Jurina Ivan Jurina Ivan Jurina Follow Jan 12 I built a free URL shortener with QR codes and click tracking — looking for feedback # discuss # showdev # tooling # webdev Comments Add Comment 1 min read I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently Axonix Tools Axonix Tools Axonix Tools Follow Jan 12 I Built 97 Free Online Tools (and Games) While Learning to Ship Consistently # showdev # learning # productivity # webdev 3 reactions Comments 1 comment 2 min read From ChatGPT to Gemini: How We Built a GDPR-Compliant CV Parser for Odoo DERICK TEMFACK DERICK TEMFACK DERICK TEMFACK Follow Jan 11 From ChatGPT to Gemini: How We Built a GDPR-Compliant CV Parser for Odoo # python # webdev # ai # productivity Comments Add Comment 5 min read An Introduction to Docker: Stop asking your stakeholders to install Postgres! 🚀 Francisco Luna Francisco Luna Francisco Luna Follow Jan 11 An Introduction to Docker: Stop asking your stakeholders to install Postgres! 🚀 # webdev # devops # productivity # learning 1 reaction Comments Add Comment 5 min read My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack ILshat Khamitov ILshat Khamitov ILshat Khamitov Follow Jan 11 My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack # webdev # javascript # programming # ai Comments Add Comment 1 min read Kubernetes Namespace Isolation: Why It's Not a Security Feature (And What Actually Is) inboryn inboryn inboryn Follow Jan 12 Kubernetes Namespace Isolation: Why It's Not a Security Feature (And What Actually Is) # kubernetes # devops # webdev Comments Add Comment 2 min read Integrating HubSpot with Salesforce using Webhooks for Real-Time Data Synchronization CallStack Tech CallStack Tech CallStack Tech Follow Jan 12 Integrating HubSpot with Salesforce using Webhooks for Real-Time Data Synchronization # api # webdev # tutorial # programming 1 reaction Comments Add Comment 13 min read Self-Documenting Code vs. Comments: Lessons from Maintaining Large-Scale Codebases ThankGod Chibugwum Obobo ThankGod Chibugwum Obobo ThankGod Chibugwum Obobo Follow Jan 11 Self-Documenting Code vs. Comments: Lessons from Maintaining Large-Scale Codebases # webdev # softwaredevelopment # programming Comments Add Comment 3 min read I Built a Free All-in-One Tools Website — Here’s What I Learned the Hard Way Bhavin Sheth Bhavin Sheth Bhavin Sheth Follow Jan 12 I Built a Free All-in-One Tools Website — Here’s What I Learned the Hard Way # webdev # productivity # buildinpublic # sass 2 reactions Comments Add Comment 2 min read Getting Started with MUI X Data Grid in React: Building Your First Data Table Michael Turner Michael Turner Michael Turner Follow Jan 12 Getting Started with MUI X Data Grid in React: Building Your First Data Table # webdev # programming # javascript # beginners Comments Add Comment 6 min read I Built a Mock API Platform in 2.5 Months (Django + React + Redis + PostgreSQL) Marcus Marcus Marcus Follow Jan 11 I Built a Mock API Platform in 2.5 Months (Django + React + Redis + PostgreSQL) # showdev # django # webdev # startup Comments Add Comment 2 min read A Five-Minute UI Feature That Became an XSS Time Bomb Parth G Parth G Parth G Follow Jan 12 A Five-Minute UI Feature That Became an XSS Time Bomb # frontend # javascript # security # webdev 3 reactions Comments 1 comment 5 min read How to protect server functions with auth middleware in TanStack Start Hiroto Shioi Hiroto Shioi Hiroto Shioi Follow Jan 12 How to protect server functions with auth middleware in TanStack Start # webdev # typescript # fullstack # security 1 reaction Comments Add Comment 3 min read Starting My Learning Journey in Tech Hassan Olamide Hassan Olamide Hassan Olamide Follow Jan 12 Starting My Learning Journey in Tech # beginners # devjournal # learning # webdev 1 reaction Comments Add Comment 1 min read Demystifying Real-time Admin Previews: JavaScript & PHP for Dynamic Chat Widget Configuration Shahibur Rahman Shahibur Rahman Shahibur Rahman Follow Jan 12 Demystifying Real-time Admin Previews: JavaScript & PHP for Dynamic Chat Widget Configuration # javascript # jquery # webdev # wordpress 2 reactions Comments Add Comment 6 min read Google's Universal Commerce Protocol: What Developers Need to Know Okkar Kyaw Okkar Kyaw Okkar Kyaw Follow Jan 12 Google's Universal Commerce Protocol: What Developers Need to Know # webdev # ai # gemini Comments Add Comment 4 min read What's new in Webpixels v3 Alexis Enache Alexis Enache Alexis Enache Follow Jan 12 What's new in Webpixels v3 # webdev # programming # ai # productivity Comments Add Comment 3 min read EC2 (single instance with db and redis and all) vs EC2 + RDS + MemoryDB, ECS/EKS (docker-based approach): when and why Saif Ullah Usmani Saif Ullah Usmani Saif Ullah Usmani Follow Jan 11 EC2 (single instance with db and redis and all) vs EC2 + RDS + MemoryDB, ECS/EKS (docker-based approach): when and why # webdev # programming # devops # javascript Comments Add Comment 3 min read EU Digital Omnibus: New Requirements for Websites and Online Services Mehwish Malik Mehwish Malik Mehwish Malik Follow Jan 12 EU Digital Omnibus: New Requirements for Websites and Online Services # webdev # ai # beginners # productivity 17 reactions Comments Add Comment 3 min read Create Your First MCP Server in 5 Minutes with create-mcp-server Ali Ibrahim Ali Ibrahim Ali Ibrahim Follow Jan 11 Create Your First MCP Server in 5 Minutes with create-mcp-server # webdev # javascript # ai # programming 1 reaction Comments Add Comment 10 min read Code Coverage Best Practices for Agentic Development Ariel Frischer Ariel Frischer Ariel Frischer Follow Jan 11 Code Coverage Best Practices for Agentic Development # webdev # programming # ai # productivity Comments Add Comment 3 min read 3 Ways to Run AI in the Browser with Next.js (No API Keys Required) Niroshan Dh Niroshan Dh Niroshan Dh Follow Jan 12 3 Ways to Run AI in the Browser with Next.js (No API Keys Required) # javascript # webdev # ai # machinelearning Comments Add Comment 3 min read How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey CallStack Tech CallStack Tech CallStack Tech Follow Jan 11 How to Build Custom Pipelines for Voice AI Integration: A Developer's Journey # ai # voicetech # machinelearning # webdev 1 reaction Comments Add Comment 13 min read 🧩 Runtime Snapshots #11 — The Design Loop: From 'Make It Like That Site' to Pixel-Perfect Code Alechko Alechko Alechko Follow Jan 11 🧩 Runtime Snapshots #11 — The Design Loop: From 'Make It Like That Site' to Pixel-Perfect Code # e2llm # cicd # webdev # automation 1 reaction Comments Add Comment 4 min read Who is Krishna Mohan Kumar? | Full Stack Developer & B.Tech CSE Student Krishna Mohan Kumar Krishna Mohan Kumar Krishna Mohan Kumar Follow Jan 12 Who is Krishna Mohan Kumar? | Full Stack Developer & B.Tech CSE Student # webdev # beginners # portfolio # google Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://stackoverflow.blog/contributed/ | contributed - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. contributed Community-generated articles submitted for your reading pleasure. Related Tags AI llm generative AI Code for a Living Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. October 20, 2025 From multilingual semantic search to virtual assistants at Bosch Digital From sprawling PDFs to a fast, factual conversational assistant. Daly Singh , Jeremy Teichmann 4 comment s AI contributed CC BY-SA 4.0 April 28, 2025 How self-supervised learning revolutionized natural language processing and gen AI Self-supervised learning is a key advancement that revolutionized natural language processing and generative AI. Here’s how it works and two examples of how it is used to train language models. Cameron R. Wolfe, PhD 26 comment s llm AI contributed April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Scott McCarty 10 comment s automation devops AI contributed April 3, 2025 From training to inference: The new role of web data in LLMs Data has always been key to LLM success, but it's becoming key to inference-time performance as well. Or Lenchner 4 comment s data science generative AI data contributed February 26, 2025 Variants of LoRA Want to train a specialized LLM on your own data? The easiest way to do this is with low rank adaptation (LoRA), but many variants of LoRA exist. Cameron R. Wolfe, PhD 0 comment s llm AI contributed January 22, 2025 Why all developers should adopt a safety-critical mindset Is anyone designing software where failures don't have consequences? Austin Spiegel 9 comment s testing observability failover contributed December 31, 2024 Generative AI is not going to build your engineering team for you It’s easy to generate code, but not so easy to generate good code. Charity Majors 20 comment s generative AI Engineering coding Business Hub contributed December 24, 2024 You should keep a developer’s journal A developer’s journal is a place to define the problem you’re solving and record what you tried and what worked. Max Pekarsky 24 comment s writing Productivity contributed December 20, 2024 This developer tool is 40 years old: can it be improved? Would updating a tool few think about make a diff(erence)? Bill Harding 26 comment s pull requests code review diff contributed December 5, 2024 Four approaches to creating a specialized LLM Wondering how to go about creating an LLM that understands your custom data? Start here. Cameron R. Wolfe, PhD 2 comment s llm AI contributed September 26, 2024 Masked self-attention: How LLMs learn relationships between tokens Masked self-attention is the key building block that allows LLMs to learn rich relationships and patterns between the words of a sentence. Let’s build it together from scratch. Cameron R. Wolfe, PhD 1 comment llm AI contributed September 5, 2024 The hidden cost of speed It’s tempting to push projects out the door to woo and impress colleagues and supervisors, but the stark truth is that even the smallest projects should have proper review periods. Brayden A. Hord 8 comment s tech debt contributed September 4, 2024 Best practices for cost-efficient Kafka clusters In today's data-driven world, Apache Kafka has emerged as a cornerstone of modern data streaming, particularly with the rise of AI and the immense volumes of data it generates. Yaniv Ben Hemo 0 comment s kafka apache contributed August 22, 2024 LLMs evolve quickly. Their underlying architecture, not so much. The decoder-only transformer architecture is one of the most fundamental ideas in AI research. Cameron R. Wolfe, PhD 0 comment s llm architecture AI contributed August 15, 2024 Practical tips for retrieval-augmented generation (RAG) Retrieval-augmented generation (RAG) is one of the best (and easiest) ways to specialize an LLM over your own data, but successfully applying RAG in practice involves more than just stitching together pretrained models. Cameron R. Wolfe, PhD 0 comment s retrieval augmented generation llm generative AI contributed August 13, 2024 Navigating cities of code with Norris Numbers Settling down in a new city (or codebase) is a marathon, not a sprint. Isaac Lyman 1 comment coding contributed July 10, 2024 How data are reshaping society: “Datafication” and socioeconomic transformations More and more of our lives are becoming data-driven. Is that a good thing? Cristina Alaimo , Jannis Kallinikos 0 comment s data research academic papers contributed June 27, 2024 Explaining generative language models to (almost) anyone Here’s a simple, three-part framework that explains generative language models. Cameron R. Wolfe, PhD 19 comment s generative AI llm contributed April 15, 2024 How to succeed as a data engineer without the burnout The key strategies for building a headache-free data platform. Katja Belova 3 comment s data engineering burnout contributed April 4, 2024 How do mixture-of-experts layers affect transformer models? This new LLM technique has started improving the results of models without additional training. Cameron R. Wolfe, PhD 0 comment s generative AI llm mixture of experts contributed December 29, 2023 The hardest part of building software is not coding, it's requirements Why replacing programmers with AI won’t be so easy. Jared Toporek 43 comment s AI ai assistant Code for a Living llm requirements software engineering contributed December 27, 2023 Stop saying “technical debt” Everyone who says "tech debt" assumes they know what we’re all talking about, but their individual definitions differ quite a bit. Chelsea Troy 50 comment s Code for a Living code maintenance technical debt contributed December 25, 2023 Is software getting worse? With all the advancements in software development, apps could be much better. Why aren't they? Isaac Lyman 83 comment s Code for a Living software development contributed December 11, 2023 Three types of AI-assisted programmers What matters isn’t just whether you use it, but how. Isaac Lyman 26 comment s Code for a Living AI career development contributed Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/04/28/how-self-supervised-language-revolutionized-natural-language-processing-and-gen-ai/ | How self-supervised learning revolutionized natural language processing and gen AI - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 28, 2025 How self-supervised learning revolutionized natural language processing and gen AI Self-supervised learning is a key advancement that revolutionized natural language processing and generative AI. Here’s how it works and two examples of how it is used to train language models. Credit: Alexandra Francis TL;DR: Self-supervised learning is a key advancement in deep learning that is used across a variety of domains. Put simply, the idea behind self-supervised learning is to train a model over raw/unlabeled data by making out and predicting portions of this data. This way, the ground truth “labels” that we learn to predict are already present in the data itself and no human annotation is required. Types of learning. Machine learning models can be trained in a variety of ways. For example, supervised learning trains a machine learning model over pairs of input data and output labels (usually annotated manually by humans). The model learns to predict these output labels by supervising the model (i.e., showing it several examples of input data with the correct output)! On the other hand, unsupervised learning uses no output labels and discovers inherent trends within the input data itself (e.g., by forming clusters). “Self-supervised learning obtains supervisory signals from the data itself, often leveraging the underlying structure in the data. The general technique of self-supervised learning is to predict any unobserved or hidden part (or property) of the input from any observed or unhidden part of the input.” - from Self-supervised learning: The dark matter of intelligence What is self-supervised learning? Self-supervised learning lies between supervised and unsupervised learning. Namely, we train the model over pairs of input data and output labels. However, no manual annotation from humans is required to obtain output labels within our training data—the labels are naturally present in the raw data itself! To understand this better, let’s take a look at a few commonly-used self-supervised learning objectives. (1) The Cloze task is more commonly referred to as the masked language modeling (MLM) objective. Here, the language model takes a sequence of textual tokens (i.e., a sentence) as input. To train the model, we mask out (i.e., set to a special “mask” token) ~10% of tokens in the input and train the model to predict these masked tokens. Using this approach, we can train a language model over an unlabeled textual corpus, as the “labels” that we predict are just tokens that are already present in the text itself. This objective is used to pretrain language models like BERT and T5. (2) Next token prediction is the workhorse of modern generative language models like ChatGPT and PaLM. After downloading a large amount of raw textual data from the internet, we can repeatedly i) sample a sequence of text and ii) train the language model to predict the next token given preceding tokens as input. This happens in parallel for all tokens in the sequence. Again, all the “labels” that we learn to predict are already present in the raw textual data. Pretraining (and finetuning) via next token prediction is universal used by all generative language models. Other options exist too! Although Cloze and next token prediction are the most commonly-used self-supervised objectives for training language models, many examples of self-supervised learning exist. For example, many self-supervised objectives exist for video deep learning models (e.g., predicting the next frame), and BERT models also use a self-supervised next-sentence prediction objective. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Cameron R. Wolfe, PhD Director of AI at Rebuy I’m currently the Director of AI at Rebuy, a personalized search and recommendations platform for D2C e-commerce brands. Prior to Rebuy, I was a Research Scientist at Alegion. Additionally, I worked for Salesforce Commerce Cloud … llm AI contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://developer.x.com/developer-terms/policy#3-d | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://www.haproxy.com/ | HAProxy Technologies | Powering the World's Busiest Applications Privacy Settings HAProxy's website uses cookies. By proceeding, you consent to our cookie usage. Please see our Privacy Policy and Cookie Policy for cookie usage details and instructions on how to disable cookies. Privacy and Cookie Policy More information Functional Cookies that make the website usable. Analytics Help website owners understand how visitors interact with websites. Ads Enables advertising related storage. User data Consent for sending user data to Google for advertising purposes. Ad personalization Consent for personalized advertising. Show details Consent date: User Unique Id: Deny Save Accept and close Accept all Ingress NGINX retirement > Explore replacement options Contact us Blog Customer login Languages Translation not available HAProxy Technologies Products HAProxy One The world’s fastest application delivery and security platform consisting of a flexible data plane, scalable control plane, and secure edge network. HAProxy Enterprise Software load balancer and API/AI gateway. HAProxy Edge Secure global network for ADN/CDN. HAProxy ALOHA Plug-and-play load balancer appliance. HAProxy Fusion Control Plane Management, observability, and automation. HAProxy Enterprise Kubernetes Ingress Controller K8s-native routing and security. Solutions Load balancing Security Universal mesh UDP load balancing SSL/TLS processing Kubernetes API gateway DDoS protection and rate limiting Service discovery AI gateway Bot management Load balancer management Application acceleration High availability Observability Public sector Web application firewall (WAF) Automation and self-service HAProxy GUI Live Webinar HAProxy 3.3 Feature Roundup The HAProxy 3.3 webinar is a unique opportunity to hear directly from HAProxy experts and stay ahead of the curve by exploring HAProxy's many new capabilities. Register now Resources PRODUCT OVERVIEW Upgrade from Community to Enterprise Migrate from F5 Migrate from Avi Networks Migrate from NetScaler ADC Migrate from Ingress NGINX Certified integrations Datasheets LEARNING HUB Blog Webinars E-books Content library Technical Resources Documentation Glossary Use Cases Success stories User spotlight series Support Expert Support Support details Professional services Customer support portal Community Slack Reddit Mailing list Featured Webinar HAProxy 3.2 feature roundup Watch the webinar Other on-demand webinars Company PARTNERS Partner program Certified integration program Find a partner Company About us News Events Careers Meet Loady CONNECT WITH US Contact us Slack Twitter Facebook LinkedIn Reddit YouTube GitHub Featured Event KubeCon + CloudNativeCon Europe 2026 Learn more Other events $refs?.search?.focus());" aria-label="Search button" > Search $refs?.search?.focus());" type="button" class="block p-3 border rounded-lg text-text-inverse-default hover:no-underline hover:text-neutral-bold border-neutral-subtlest hover:bg-neutral-subtlest" aria-label="Search button" > Get HAProxy Products HAProxy One The world’s fastest application delivery and security platform consisting of a flexible data plane, scalable control plane, and secure edge network. HAProxy One HAProxy Enterprise load balancer HAProxy Fusion Control Plane HAProxy Edge HAProxy Enterprise Kubernetes Ingress Controller HAProxy ALOHA Solutions Load balancing UDP load balancing API gateway AI gateway High availability Security SSL/TLS processing DDoS protection and rate limiting Bot management Web application firewall (WAF) Universal mesh Kubernetes Service discovery Automation and self-service Load balancer management Observability HAProxy GUI Application acceleration Public sector Blog Resources Technical Resources Documentation Glossary PRODUCT OVERVIEW Upgrade from Community to Enterprise Migrate from F5 Migrate from Avi Networks Migrate from NetScaler ADC Migrate from Ingress NGINX Certified integrations Datasheets LEARNING HUB Blog Webinars E-books Content library Use Cases Success stories User spotlight series Support Expert Support Support details Professional services Customer support portal Community Slack Reddit Mailing list Company PARTNERS Partner program Certified integration program Find a partner Company About us News Events Careers Meet Loady CONNECT WITH US Contact us Slack Twitter Facebook LinkedIn Reddit YouTube GitHub Get HAProxy Languages 1" x-for="language in locales"> Contact us Blog Customer login Your browser does not support the video tag. Powering the world's busiest websites and applications High-performance traffic management and next-gen security with multi-cloud management and observability. Built for the enterprise — open source at heart. Discover HAProxy One See what's new in our latest releases Watch HAProxy success stories from industry leaders at HAProxyConf LIVE WEBINAR > HAProxy 3.3 Feature Roundup Learn why we are G2's top-ranked solution User reviews on G2 rank HAProxy as a Leader in Load Balancing, Container Networking, API Management, DDoS Protection, and WAF. Read the G2 reviews "HAProxy showcases community at its best and this project is the very definition of sustainability." Kelsey Hightower Software Engineer and Technologist Read more "An example of a company that focuses on performance and efficiency, that is why HAProxy remains my favorite proxy. Not just adding flashy features." Hussein Nasser Software Engineer and Author Read more Platform Overview Do more with HAProxy One The world's fastest application delivery and security platform seamlessly blends data plane, control plane, and edge network to deliver the world's most demanding applications, APIs, and AI services in any environment. Discover HAProxy One HAProxy Enterprise A flexible data plane layer that provides high-performance load balancing, an API/AI gateway, Kubernetes application routing, best-in-class SSL processing, and multi-layered security. HAProxy Fusion Control Plane A scalable control plane that provides full-lifecycle management, monitoring, and automation of multi-cluster, multi-cloud, and multi-team HAProxy Enterprise deployments. HAProxy Edge A secure edge network that provides a high-capacity global ADN and threat intelligence — enhanced by machine learning — that powers the next-generation security layers in HAProxy Fusion and HAProxy Enterprise. World-class experience 24/7 support from real humans! We're the authoritative experts on HAProxy — including the edge, data plane, control plane, and security layers. We'll do whatever it takes to make your HAProxy deployment a success. Featured Solutions Trusted solutions from the experts in application delivery HAProxy One keeps your mission-critical websites and applications fast, secure, and highly available — in any environment. Contact us Load balancing Web app and API protection High availability Kubernetes app routing { setTimeout(() => { $el?.scrollIntoView({ behavior: 'smooth' })}, 100); });" > Load balancing High-performance traffic management at massive scale Load balancer and reverse proxy for HTTP, TCP, UDP, and QUIC applications — with HAProxy’s legendary performance and reliability! Robust architecture, highly customizable, and runs anywhere. Go to solution Cost-efficient performance 2 million TPS on a single AWS Arm instance. Best-in-class SSL/TLS processing. Efficiency that saves you money. Trusted and proven Over 20 years of open source development. The world’s most widely used software load balancer. Any app, any environment Works with virtually any app, API, or AI service. Advanced routing options and customizable with Lua and SPOE. Run on any Linux server, cloud, container, or VM with identical performance and features. Load Balancing as a Service (LBaaS) Offload load balancer management from central Ops teams while making self-service application delivery more efficient for App teams. Central management Multi-cluster, multi-cloud, and multi-team management, observability, and automation via a central control plane. SaaS ADN Fully managed app delivery services on our global network, powered by HAProxy. For the ultimate scale and simplicity. { setTimeout(() => { $el?.scrollIntoView({ behavior: 'smooth' })}, 100); });" > Web app and API protection Next-gen security with threat intelligence Multi-layered security fends off threats before they can reach your application — powering your uptime while keeping your organization, data, and users safe. Go to solution DDoS protection Maintain service availability without slowdowns, even under sustained attacks or unpredictable traffic spikes. Bot management and protection Fast and cost-efficient bot detection and enforcement, all done locally on your infrastructure. API/AI protection Authentication, filtering, rate limiting, and routing for API traffic and AI/LLM prompts ensures performance and security. Web application firewall Exceptional balanced accuracy and ultra-low latency, without relying on static lists and regex-based attack signatures. Central security policy Multi-cluster, multi-cloud, and multi-team management, security policy, WAF configuration, and observability. SaaS ADN Fully managed app security services on our global network, powered by HAProxy. For the ultimate full-spectrum protection. { setTimeout(() => { $el?.scrollIntoView({ behavior: 'smooth' })}, 100); });" > High availability Uptime for mission-critical applications Seamless redundancy, a resilient architecture, and proactive monitoring ensure high availability for the most demanding applications. Go to solution Fault tolerant clusters With Active/Active or Active/Standby configuration and automatic failover, your backup load balancer will always be ready. Maintain network stability Advanced health checks monitor server health. Retry-requests and circuit-breaking route traffic around unhealthy server groups. Mitigate deployment risks Increase and drain traffic to servers during application deployments. Hitless reloads when updating HAProxy configuration. Resilience to attack Stay online, and protect your users, data, transactions, and content — even under sustained heavy attack. Maximize efficiency Timeouts, connection pooling, and traffic overload protection mean your servers are always running at their best. SaaS ADN Fully managed app delivery services on our global network, powered by HAProxy. For the ultimate reliability and capacity. { setTimeout(() => { $el?.scrollIntoView({ behavior: 'smooth' })}, 100); });" > Kubernetes app routing Simplify Kubernetes on-premises or in the cloud Intelligent external load balancing, multi-cluster routing, direct-to-pod load balancing, and high-performance ingress for Kubernetes applications. Go to solution External load balancing Simplify deploying Kubernetes on-premises with fully automated external load balancing. Multi-cluster routing Enable high-performance load balancing for your Kubernetes clusters within one or many cloud regions. Direct-to-pod load balancing Consolidate Kubernetes app routing into a single layer for reduced complexity and infrastructure costs. Ingress control Kubernetes-standard traffic routing using the Ingress API, in a high-performance package. Service discovery Service discovery, dynamic config generation, and multi-cluster observability via a central control plane. Container images Easily deploy HAProxy nodes in containers with verified images on Docker Hub. Why HAProxy? Powering the future of secure application delivery HAProxy Technologies is the company behind HAProxy One, the world’s fastest application delivery and security platform, and HAProxy, the most widely used software load balancer. About us Incredible technology From performance, security, and control planes to the use of AI/ML, HAProxy has led the way for over 20 years — providing a platform for continuous innovation. Open source and independent HAProxy Technologies is proudly independently owned and operated. We owe our open source development and rapid growth to our thriving community and customers, alike. Relentless customer focus We have only one priority: serving our users by providing the best products and the best customer experience in the world. HAProxy User Stories Real experiences, better solutions Leading platforms and cloud providers trust HAProxy to simplify, scale, and secure modern applications, APIs, and AI services in any environment. Watch them tell their stories at HAProxyConf. See more user stories Contact us 2 }" > 2 }" > 2 }" > 2 }" > 2 }" > 2 }" > 2 }" > Data informed decision making: Roblox use case for more metrics Adam Mills from Roblox discusses methods and implementations of data processing and analysis, and shares some tips so you can prove the value of MORE metrics. Go to user story Adam Mills Principal Site Reliability Engineer, Roblox Modernizing LinkedIn’s traffic stack Rapid changes in the ecosystem forced LinkedIn to revisit its traffic stack. After an extensive evaluation process, HAProxy came out as a winner. See why. Go to user story Sri Ram Bathina Staff Software Engineer, System Infrastructure, LinkedIn Load balancing and high availability on Postgres using HAProxy Discover how Cloudflare uses HAProxy for load balancing, health checks & directing traffic in Postgres clusters across multiple data centers. Go to user story Vignesh Ravichandran Engineering Manager, Databases, Cloudflare Handling 80 petabytes a month: autoscaling with traffic volume to protect revenue and reputation Docker's HAProxy-based cloud-native API gateway is scalable, resilient & highly available. Learn how to leverage Kubernetes for autoscaling in this talk. Go to user story Ryan Hristovski Infrastructure Engineer, Docker Load balancers at DigitalOcean In this presentation, Neal Shrader describes how DigitalOcean leverages HAProxy to power several key components within its infrastructure. Go to user story Neal Shrader Software Engineer, DigitalOcean Inside the GitHub load balancer GitHub built a resilient custom solution on top of HAProxy to intelligently route requests coming from various clients, including Git, SSH, and MySQL. Go to user story Joe Williams Staff Engineer, GitHub How we achieved 2 million RPS: HAProxy on Arm processors Learn how Arm’s Graviton2 processor, which was specially developed to run on AWS EC2 instances, created the opportunity to benchmark HAProxy on a machine. Go to user story Kailas Jawadekar Sr Manager, Software Ecosystem, Arm Featured Resources See how it works in practice Your next-gen app delivery and security are closer than you think. Get started with technical webinars, documentation, and more. See more resources Live webinar HAProxy 3.3 Feature Roundup The HAProxy 3.3 webinar is a unique opportunity to hear directly from HAProxy experts and stay ahead of the curve by exploring HAProxy's many new capabilities. Register now On-demand webinar Life After Ingress NGINX: A Zero-Stress Migration Guide to HAProxy Watch our hands-on session where we break down exactly how to move from Ingress NGINX to the HAProxy Kubernetes Ingress Controller—and why this switch gives you immediate performance wins and a future-proof path to the Gateway API. Watch now Discover what's possible Contact the authoritative experts at HAProxy to find the best solutions for your deployment, scalability, and security needs. Contact us Products HAProxy One HAProxy Enterprise load balancer HAProxy Fusion Control Plane HAProxy Edge HAProxy Enterprise Kubernetes Ingress Controller HAProxy ALOHA Solutions Load balancing UDP load balancing API gateway AI gateway High availability Security SSL/TLS processing DDoS protection and rate limiting Bot management Web application firewall (WAF) Universal mesh Kubernetes Service discovery Automation and self-service Load balancer management Observability HAProxy GUI Application acceleration Public sector Resources HAProxy Enterprise documentation HAProxy ALOHA documentation HAProxy Kubernetes Ingress Controller documentation Upgrade from Community to Enterprise Certified integrations User spotlight series Content library Blog Success stories Partners Partner program Certified integration program Find a partner Partner deal registration Support Customer support portal Support options Professional services Community mailing list Company About us Contact us Events Careers News +1 (844) 222-4340 Email HAProxy Techologies HAProxy Techologies on Facebook HAProxy Techologies on GitHub HAProxy Techologies on LinkedIn HAProxy Techologies on YouTube HAProxy Techologies on Slack © 2026 HAProxy Technologies, LLC. All Rights Reserved Trademark | Privacy | DMCA Policy | Subpoena Response Policy | Acceptable Use Policy (AUP) | Do Not Sell My Personal Information Sitemap Manage Cookie Preferences | 2026-01-13T08:48:30 |
https://dumb.dev.to/subforems/new#main-content | Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DUMB DEV Community Close Information Subforems are New and Experimental Subforems are a new feature that allows communities to create focused spaces within the larger Forem ecosystem. These networks are designed to empower our community to build intentional community around what they care about and the ways they awant to express their interest. Some subforems will be run communally, and others will be run by you . What Subforems Should Exist? What kind of Forem are you envisioning? 🤔 A general Forem that should exist in the world Think big! What community is the world missing? A specific interest Forem I'd like to run myself You have a passion and want to build a community around it. A company-run Forem for our product or ecosystem For customer support, developer relations, or brand engagement. ✓ Thank you for your response. ✓ Thank you for completing the survey! Give us the elevator pitch! What is your Forem about, and what general topics would it cover? 💡 ✓ Thank you for your response. ✓ Thank you for your response. ✓ Thank you for completing the survey! ← Previous Next → Survey completed 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DUMB DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DUMB DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://www.linkedin.com/legal/privacy-policy?trk=public_profile_follow_contextual-sign-in-modal_sign-in-modal_auth-button_privacy-policy | LinkedIn Privacy Policy Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Privacy Policy Effective November 3, 2025 Your Privacy Matters LinkedIn’s mission is to connect the world’s professionals to allow them to be more productive and successful. Central to this mission is our commitment to be transparent about the data we collect about you, how it is used and with whom it is shared. This Privacy Policy applies when you use our Services (described below). We offer our users choices about the data we collect, use and share as described in this Privacy Policy, Cookie Policy , Settings and our Help Center. Key Terms Choices Settings are available to Members of LinkedIn and Visitors are provided separate controls. Learn More . Table of Contents Data We Collect How We Use Your Data How We Share Information Your Choices and Obligations Other Important Information Introduction We are a social network and online platform for professionals. People use our Services to find and be found for business opportunities, to connect with others and find information. Our Privacy Policy applies to any Member or Visitor to our Services. Our registered users (“Members”) share their professional identities, engage with their network, exchange knowledge and professional insights, post and view relevant content, learn and develop skills, and find business and career opportunities. Content and data on some of our Services is viewable to non-Members (“Visitors”). We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. Members and Visitors located in the Designated Countries or the UK can review additional information in our European Regional Privacy Notice . Services This Privacy Policy, including our Cookie Policy applies to your use of our Services. This Privacy Policy applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-branded sites, apps, communications and services offered by LinkedIn (“Services”), including off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins, but excluding services that state that they are offered under a different privacy policy. For California residents, additional disclosures required by California law may be found in our California Privacy Disclosure . Data Controllers and Contracting Parties If you are in the “Designated Countries”, LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you are outside of the Designated Countries, LinkedIn Corporation will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. As a Visitor or Member of our Services, the collection, use and sharing of your personal data is subject to this Privacy Policy and other documents referenced in this Privacy Policy, as well as updates. Change Changes to the Privacy Policy apply to your use of our Services after the “effective date.” LinkedIn (“we” or “us”) can modify this Privacy Policy, and if we make material changes to it, we will provide notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. If you object to any changes, you may close your account. You acknowledge that your continued use of our Services after we publish or send a notice about our changes to this Privacy Policy means that the collection, use and sharing of your personal data is subject to the updated Privacy Policy, as of its effective date. 1. Data We Collect 1.1 Data You Provide To Us You provide data to create an account with us. Registration To create an account you need to provide data including your name, email address and/or mobile number, general location (e.g., city), and a password. If you register for a premium Service, you will need to provide payment (e.g., credit card) and billing information. You create your LinkedIn profile (a complete profile helps you get the most from our Services). Profile You have choices about the information on your profile, such as your education, work experience, skills, photo, city or area , endorsements, and optional verifications of information on your profile (such as verifications of your identity or workplace). You don’t have to provide additional information on your profile; however, profile information helps you to get more from our Services, including helping recruiters and business opportunities find you. It’s your choice whether to include sensitive information on your profile and to make that sensitive information public. Please do not post or add personal data to your profile that you would not want to be publicly available. You may give other data to us, such as by syncing your calendar. Posting and Uploading We collect personal data from you when you provide, post or upload it to our Services, such as when you fill out a form, (e.g., with demographic data or salary), respond to a survey, or submit a resume or fill out a job application on our Services. If you sync your calendars with our Services, we will collect your calendar meeting information to keep growing your network by suggesting connections for you and others, and by providing information about events, e.g. times, places, attendees and contacts. You don’t have to post or upload personal data; though if you don’t, it may limit your ability to grow and engage with your network over our Services. 1.2 Data From Others Others may post or write about you. Content and News You and others may post content that includes information about you (as part of articles, posts, comments, videos) on our Services. We also may collect public information about you, such as professional-related news and accomplishments, and make it available as part of our Services, including, as permitted by your settings, in notifications to others of mentions in the news . Others may sync their calendar with our Services Contact and Calendar Information We receive personal data (including contact information) about you when others import or sync their calendar with our Services, associate their contacts with Member profiles, scan and upload business cards, or send messages using our Services (including invites or connection requests). If you or others opt-in to sync email accounts with our Services, we will also collect “email header” information that we can associate with Member profiles. Customers and partners may provide data to us. Partners We receive personal data (e.g., your job title and work email address) about you when you use the services of our customers and partners, such as employers or prospective employers and applicant tracking systems providing us job application data. Related Companies and Other Services We receive data about you when you use some of the other services provided by us or our Affiliates , including Microsoft. For example, you may choose to send us information about your contacts in Microsoft apps and services, such as Outlook, for improved professional networking activities on our Services or we may receive information from Microsoft about your engagement with their sites and services. 1.3 Service Use We log your visits and use of our Services, including mobile apps. We log usage data when you visit or otherwise use our Services, including our sites, app and platform technology, such as when you view or click on content (e.g., learning video) or ads (on or off our sites and apps), perform a search, install or update one of our mobile apps, share articles or apply for jobs. We use log-ins, cookies, device information and internet protocol (“IP”) addresses to identify you and log your use. 1.4 Cookies and Similar Technologies We collect data through cookies and similar technologies. As further described in our Cookie Policy , we use cookies and similar technologies (e.g., pixels and ad tags) to collect data (e.g., device IDs) to recognize you and your device(s) on, off and across different services and devices where you have engaged with our Services. We also allow some others to use cookies as described in our Cookie Policy. If you are outside the Designated Countries, we also collect (or rely on others, including Microsoft, who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. Learn more . You can opt out from our use of data from cookies and similar technologies that track your behavior on the sites of others for ad targeting and other ad-related purposes. For Visitors, the controls are here . 1.5 Your Device and Location We receive data through cookies and similar technologies When you visit or leave our Services (including some plugins and our cookies or similar technology on the sites of others), we receive the URL of both the site you came from and the one you go to and the time of your visit. We also get information about your network and device (e.g., IP address, proxy server, operating system, web browser and add-ons, device identifier and features, cookie IDs and/or ISP, or your mobile carrier). If you use our Services from a mobile device, that device will send us data about your location based on your phone settings. We will ask you to opt-in before we use GPS or other tools to identify your precise location. 1.6 Communications If you communicate through our Services, we learn about that. We collect information about you when you communicate with others through our Services (e.g., when you send, receive, or engage with messages, events, or connection requests, including our marketing communications). This may include information that indicates who you are communicating with and when. We also use automated systems to support and protect our site. For example, we use such systems to suggest possible responses to messages and to manage or block content that violates our User Agreement or Professional Community Policies . 1.7 Workplace and School Provided Information When your organization (e.g., employer or school) buys a premium Service for you to use, they give us data about you. Others buying our Services for your use, such as your employer or your school, provide us with personal data about you and your eligibility to use the Services that they purchase for use by their workers, students or alumni. For example, we will get contact information for “ LinkedIn Page ” (formerly Company Page) administrators and for authorizing users of our premium Services, such as our recruiting, sales or learning products. 1.8 Sites and Services of Others We get data when you visit sites that include our ads, cookies or plugins or when you log-in to others’ services with your LinkedIn account. We receive information about your visits and interaction with services provided by others when you log-in with LinkedIn or visit others’ services that include some of our plugins (such as “Apply with LinkedIn”) or our ads, cookies or similar technologies. 1.9 Other We are improving our Services, which means we get new data and create new ways to use data. Our Services are dynamic, and we often introduce new features, which may require the collection of new information. If we collect materially different personal data or materially change how we collect, use or share your data, we will notify you and may also modify this Privacy Policy. Key Terms Affiliates Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., GitHub, Inc.). 2. How We Use Your Data We use your data to provide, support, personalize and develop our Services. How we use your personal data will depend on which Services you use, how you use those Services and the choices you make in your settings . We may use your personal data to improve, develop, and provide products and Services, develop and train artificial intelligence (AI) models, develop, provide, and personalize our Services, and gain insights with the help of AI, automated systems, and inferences, so that our Services can be more relevant and useful to you and others. You can review LinkedIn's Responsible AI principles here and learn more about our approach to generative AI here . Learn more about the inferences we may make, including as to your age and gender and how we use them. 2.1 Services Our Services help you connect with others, find and be found for work and business opportunities, stay informed, get training and be more productive. We use your data to authorize access to our Services and honor your settings. Stay Connected Our Services allow you to stay in touch and up to date with colleagues, partners, clients, and other professional contacts. To do so, you can “connect” with the professionals who you choose, and who also wish to “connect” with you. Subject to your and their settings , when you connect with other Members, you will be able to search each others’ connections in order to exchange professional opportunities. We use data about you (such as your profile, profiles you have viewed or data provided through address book uploads or partner integrations) to help others find your profile, suggest connections for you and others (e.g. Members who share your contacts or job experiences) and enable you to invite others to become a Member and connect with you. You can also opt-in to allow us to use your precise location or proximity to others for certain tasks (e.g. to suggest other nearby Members for you to connect with, calculate the commute to a new job, or notify your connections that you are at a professional event). It is your choice whether to invite someone to our Services, send a connection request, or allow another Member to become your connection. When you invite someone to connect with you, your invitation will include your network and basic profile information (e.g., name, profile photo, job title, region). We will send invitation reminders to the person you invited. You can choose whether or not to share your own list of connections with your connections. Visitors have choices about how we use their data. Stay Informed Our Services allow you to stay informed about news, events and ideas regarding professional topics you care about, and from professionals you respect. Our Services also allow you to improve your professional skills, or learn new ones. We use the data we have about you (e.g., data you provide, data we collect from your engagement with our Services and inferences we make from the data we have about you), to personalize our Services for you, such as by recommending or ranking relevant content and conversations on our Services. We also use the data we have about you to suggest skills you could add to your profile and skills that you might need to pursue your next opportunity. So, if you let us know that you are interested in a new skill (e.g., by watching a learning video), we will use this information to personalize content in your feed, suggest that you follow certain Members on our site, or suggest related learning content to help you towards that new skill. We use your content, activity and other data, including your name and photo, to provide notices to your network and others. For example, subject to your settings , we may notify others that you have updated your profile, posted content, took a social action , used a feature, made new connections or were mentioned in the news . Career Our Services allow you to explore careers, evaluate educational opportunities, and seek out, and be found for, career opportunities. Your profile can be found by those looking to hire (for a job or a specific task ) or be hired by you. We will use your data to recommend jobs and show you and others relevant professional contacts (e.g., who work at a company, in an industry, function or location or have certain skills and connections). You can signal that you are interested in changing jobs and share information with recruiters. We will use your data to recommend jobs to you and you to recruiters. We may use automated systems to provide content and recommendations to help make our Services more relevant to our Members, Visitors and customers. Keeping your profile accurate and up-to-date may help you better connect to others and to opportunities through our Services. Productivity Our Services allow you to collaborate with colleagues, search for potential clients, customers, partners and others to do business with. Our Services allow you to communicate with other Members and schedule and prepare meetings with them. If your settings allow, we scan messages to provide “bots” or similar tools that facilitate tasks such as scheduling meetings, drafting responses, summarizing messages or recommending next steps. Learn more . 2.2 Premium Services Our premium Services help paying users to search for and contact Members through our Services, such as searching for and contacting job candidates, sales leads and co-workers, manage talent and promote content. We sell premium Services that provide our customers and subscribers with customized-search functionality and tools (including messaging and activity alerts) as part of our talent, marketing and sales solutions. Customers can export limited information from your profile, such as name, headline, current company, current title, and general location (e.g., Dublin), such as to manage sales leads or talent, unless you opt-out . We do not provide contact information to customers as part of these premium Services without your consent. Premium Services customers can store information they have about you in our premium Services, such as a resume or contact information or sales history. The data stored about you by these customers is subject to the policies of those customers. Other enterprise Services and features that use your data include TeamLink and LinkedIn Pages (e.g., content analytics and followers). 2.3 Communications We contact you and enable communications between Members. We offer settings to control what messages you receive and how often you receive some types of messages. We will contact you through email, mobile phone, notices posted on our websites or apps, messages to your LinkedIn inbox, and other ways through our Services, including text messages and push notifications. We will send you messages about the availability of our Services, security, or other service-related issues. We also send messages about how to use our Services, network updates, reminders, job suggestions and promotional messages from us and our partners. You may change your communication preferences at any time. Please be aware that you cannot opt out of receiving service messages from us, including security and legal notices. We also enable communications between you and others through our Services, including for example invitations , InMail , groups and messages between connections. 2.4 Advertising We serve you tailored ads both on and off our Services. We offer you choices regarding personalized ads, but you cannot opt-out of seeing non-personalized ads. We target (and measure the performance of) ads to Members, Visitors and others both on and off our Services directly or through a variety of partners, using the following data, whether separately or combined: Data collected by advertising technologies on and off our Services using pixels, ad tags (e.g., when an advertiser installs a LinkedIn tag on their website), cookies, and other device identifiers; Member-provided information (e.g., profile, contact information, title and industry); Data from your use of our Services (e.g., search history, feed, content you read, who you follow or is following you, connections, groups participation, page visits, videos you watch, clicking on an ad, etc.), including as described in Section 1.3; Information from advertising partners , vendors and publishers ; and Information inferred from data described above (e.g., using job titles from a profile to infer industry, seniority, and compensation bracket; using graduation dates to infer age or using first names or pronoun usage to infer gender; using your feed activity to infer your interests; or using device data to recognize you as a Member). Learn more about the inferences we make and how they may be used for advertising. Learn more about the ad technologies we use and our advertising services and partners. You can learn more about our compliance with laws in the Designated Countries or the UK in our European Regional Privacy Notice . We will show you ads called sponsored content which look similar to non-sponsored content, except that they are labeled as advertising (e.g., as “ad” or “sponsored”). If you take a social action (such as like, comment or share) on these ads, your action is associated with your name and viewable by others, including the advertiser. Subject to your settings , if you take a social action on the LinkedIn Services, that action may be mentioned with related ads. For example, when you like a company we may include your name and photo when their sponsored content is shown. Ad Choices You have choices regarding our uses of certain categories of data to show you more relevant ads. Member settings can be found here . For Visitors, the setting is here . Info to Ad Providers We do not share your personal data with any non-Affiliated third-party advertisers or ad networks except for: (i) hashed IDs or device identifiers (to the extent they are personal data in some countries); (ii) with your separate permission (e.g., in a lead generation form) or (iii) data already visible to any users of the Services (e.g., profile). However, if you view or click on an ad on or off our Services, the ad provider will get a signal that someone visited the page that displayed the ad, and they may, through the use of mechanisms such as cookies, determine it is you. Advertising partners can associate personal data collected by the advertiser directly from you with hashed IDs or device identifiers received from us. We seek to contractually require such advertising partners to obtain your explicit, opt-in consent before doing so where legally required, and in such instances, we take steps to ensure that consent has been provided before processing data from them. 2.5 Marketing We promote our Services to you and others. In addition to advertising our Services, we use Members’ data and content for invitations and communications promoting membership and network growth, engagement and our Services, such as by showing your connections that you have used a feature on our Services. 2.6 Developing Services and Research We develop our Services and conduct research Service Development We use data, including public feedback, to conduct research and development for our Services in order to provide you and others with a better, more intuitive and personalized experience, drive membership growth and engagement on our Services, and help connect professionals to each other and to economic opportunity. Other Research We seek to create economic opportunity for Members of the global workforce and to help them be more productive and successful. We use the personal data available to us to research social, economic and workplace trends, such as jobs availability and skills needed for these jobs and policies that help bridge the gap in various industries and geographic areas. In some cases, we work with trusted third parties to perform this research, under controls that are designed to protect your privacy. We may also make public data available to researchers to enable assessment of the safety and legal compliance of our Services. We publish or allow others to publish economic insights, presented as aggregated data rather than personal data. Surveys Polls and surveys are conducted by us and others through our Services. You are not obligated to respond to polls or surveys, and you have choices about the information you provide. You may opt-out of survey invitations. 2.7 Customer Support We use data to help you and fix problems. We use data (which can include your communications) to investigate, respond to and resolve complaints and for Service issues (e.g., bugs). 2.8 Insights That Do Not Identify You We use data to generate insights that do not identify you. We use your data to perform analytics to produce and share insights that do not identify you. For example, we may use your data to generate statistics about our Members, their profession or industry, to calculate ad impressions served or clicked on (e.g., for basic business reporting to support billing and budget management or, subject to your settings , for reports to advertisers who may use them to inform their advertising campaigns), to show Members' information about engagement with a post or LinkedIn Page , to publish visitor demographics for a Service or create demographic workforce insights, or to understand usage of our services. 2.9 Security and Investigations We use data for security, fraud prevention and investigations. We and our Affiliates, including Microsoft, may use your data (including your communications) for security purposes or to prevent or investigate possible fraud or other violations of the law, our User Agreement and/or attempts to harm our Members, Visitors, company, Affiliates, or others. Key Terms Social Action E.g. like, comment, follow, share Partners Partners include ad networks, exchanges and others 3. How We Share Information 3.1 Our Services Any data that you include on your profile and any content you post or social action (e.g., likes, follows, comments, shares) you take on our Services will be seen by others, consistent with your settings. Profile Your profile is fully visible to all Members and customers of our Services. Subject to your settings , it can also be visible to others on or off of our Services (e.g., Visitors to our Services or users of third-party search tools). As detailed in our Help Center , your settings, degree of connection with the viewing Member, the subscriptions they may have, their usage of our Services , access channels and search types (e.g., by name or by keyword) impact the availability of your profile and whether they can view certain fields in your profile. Posts, Likes, Follows, Comments, Messages Our Services allow viewing and sharing information including through posts, likes, follows and comments. When you share an article or a post (e.g., an update, image, video or article) publicly it can be viewed by everyone and re-shared anywhere (subject to your settings ). Members, Visitors and others will be able to find and see your publicly-shared content, including your name (and photo if you have provided one). In a group , posts are visible to others according to group type. For example, posts in private groups are visible to others in the group and posts in public groups are visible publicly. Your membership in groups is public and part of your profile, but you can change visibility in your settings . Any information you share through companies’ or other organizations’ pages on our Services will be viewable by those organizations and others who view those pages' content. When you follow a person or organization, you are visible to others and that “page owner” as a follower. We let senders know when you act on their message, subject to your settings where applicable. Subject to your settings , we let a Member know when you view their profile. We also give you choices about letting organizations know when you've viewed their Page. When you like or re-share or comment on another’s content (including ads), others will be able to view these “social actions” and associate it with you (e.g., your name, profile and photo if you provided it). Your employer can see how you use Services they provided for your work (e.g. as a recruiter or sales agent) and related information. We will not show them your job searches or personal messages. Enterprise Accounts Your employer may offer you access to our enterprise Services such as Recruiter, Sales Navigator, LinkedIn Learning or our advertising Campaign Manager. Your employer can review and manage your use of such enterprise Services. Depending on the enterprise Service, before you use such Service, we will ask for permission to share with your employer relevant data from your profile or use of our non-enterprise Services. For example, users of Sales Navigator will be asked to share their “social selling index”, a score calculated in part based on their personal account activity. We understand that certain activities such as job hunting and personal messages are sensitive, and so we do not share those with your employer unless you choose to share it with them through our Services (for example, by applying for a new position in the same company or mentioning your job hunting in a message to a co-worker through our Services). Subject to your settings , when you use workplace tools and services (e.g., interactive employee directory tools) certain of your data may also be made available to your employer or be connected with information we receive from your employer to enable these tools and services. 3.2 Communication Archival Regulated Members may need to store communications outside of our Service. Some Members (or their employers) need, for legal or professional compliance, to archive their communications and social media activity, and will use services of others to provide these archival services. We enable archiving of messages by and to those Members outside of our Services. For example, a financial advisor needs to archive communications with her clients through our Services in order to maintain her professional financial advisor license. 3.3 Others’ Services You may link your account with others’ services so that they can look up your contacts’ profiles, post your shares on such platforms, or enable you to start conversations with your connections on such platforms. Excerpts from your profile will also appear on the services of others. Subject to your settings , other services may look up your profile. When you opt to link your account with other services, personal data (e.g., your name, title, and company) will become available to them. The sharing and use of that personal data will be described in, or linked to, a consent screen when you opt to link the accounts. For example, you may link your Twitter or WeChat account to share content from our Services into these other services, or your email provider may give you the option to upload your LinkedIn contacts into its own service. Third-party services have their own privacy policies, and you may be giving them permission to use your data in ways we would not. You may revoke the link with such accounts. The information you make available to others in our Services (e.g., information from your profile, your posts, your engagement with the posts, or message to Pages) may be available to them on other services . For example, search tools, mail and calendar applications, or talent and lead managers may show a user limited profile data (subject to your settings ), and social media management tools or other platforms may display your posts. The information retained on these services may not reflect updates you make on LinkedIn. 3.4 Related Services We share your data across our different Services and LinkedIn affiliated entities. We will share your personal data with our Affiliates to provide and develop our Services. For example, we may refer a query to Bing in some instances, such as where you'd benefit from a more up to date response in a chat experience. Subject to our European Regional Privacy Notice , we may also share with our Affiliates, including Microsoft, your (1) publicly-shared content (such as your public LinkedIn posts) to provide or develop their services and (2) personal data to improve, provide or develop their advertising services. Where allowed , we may combine information internally across the different Services covered by this Privacy Policy to help our Services be more relevant and useful to you and others. For example, we may personalize your feed or job recommendations based on your learning history. 3.5 Service Providers We may use others to help us with our Services. We use others to help us provide our Services (e.g., maintenance, analysis, audit, payments, fraud detection, customer support, marketing and development). They will have access to your information (e.g., the contents of a customer support request) as reasonably necessary to perform these tasks on our behalf and are obligated not to disclose or use it for other purposes. If you purchase a Service from us, we may use a payments service provider who may separately collect information about you (e.g., for fraud prevention or to comply with legal obligations). 3.6 Legal Disclosures We may need to share your data when we believe it’s required by law or to help protect the rights and safety of you, us or others. It is possible that we will need to disclose information about you when required by law, subpoena, or other legal process or if we have a good faith belief that disclosure is reasonably necessary to (1) investigate, prevent or take action regarding suspected or actual illegal activities or to assist government enforcement agencies; (2) enforce our agreements with you; (3) investigate and defend ourselves against any third-party claims or allegations; (4) protect the security or integrity of our Services or the products or services of our Affiliates (such as by sharing with companies facing similar threats); or (5) exercise or protect the rights and safety of LinkedIn, our Members, personnel or others. We attempt to notify Members about legal demands for their personal data when appropriate in our judgment, unless prohibited by law or court order or when the request is an emergency. We may dispute such demands when we believe, in our discretion, that the requests are overbroad, vague or lack proper authority, but we do not promise to challenge every demand. To learn more see our Data Request Guidelines and Transparency Report . 3.7 Change in Control or Sale We may share your data when our business is sold to others, but it must continue to be used in accordance with this Privacy Policy. We can also share your personal data as part of a sale, merger or change in control, or in preparation for any of these events. Any other entity which buys us or part of our business will have the right to continue to use your data, but only in the manner set out in this Privacy Policy unless you agree otherwise. 4. Your Choices & Obligations 4.1 Data Retention We keep most of your personal data for as long as your account is open. We generally retain your personal data as long as you keep your account open or as needed to provide you Services. This includes data you or others provided to us and data generated or inferred from your use of our Services. Even if you only use our Services when looking for a new job every few years, we will retain your information and keep your profile open, unless you close your account. In some cases we choose to retain certain information (e.g., insights about Services use) in a depersonalized or aggregated form. 4.2 Rights to Access and Control Your Personal Data You can access or delete your personal data. You have many choices about how your data is collected, used and shared. We provide many choices about the collection, use and sharing of your data, from deleting or correcting data you include in your profile and controlling the visibility of your posts to advertising opt-outs and communication controls. We offer you settings to control and manage the personal data we have about you. For personal data that we have about you, you can: Delete Data : You can ask us to erase or delete all or some of your personal data (e.g., if it is no longer necessary to provide Services to you). Change or Correct Data : You can edit some of your personal data through your account. You can also ask us to change, update or fix your data in certain cases, particularly if it’s inaccurate. Object to, or Limit or Restrict, Use of Data : You can ask us to stop using all or some of your personal data (e.g., if we have no legal right to keep using it) or to limit our use of it (e.g., if your personal data is inaccurate or unlawfully held). Right to Access and/or Take Your Data : You can ask us for a copy of your personal data and can ask for a copy of personal data you provided in machine readable form. Visitors can learn more about how to make these requests here . You may also contact us using the contact information below, and we will consider your request in accordance with applicable laws. Residents in the Designated Countries and the UK , and other regions , may have additional rights under their laws. 4.3 Account Closure We keep some of your data even after you close your account. If you choose to close your LinkedIn account, your personal data will generally stop being visible to others on our Services within 24 hours. We generally delete closed account information within 30 days of account closure, except as noted below. We retain your personal data even after you have closed your account if reasonably necessary to comply with our legal obligations (including law enforcement requests), meet regulatory requirements, resolve disputes, maintain security, prevent fraud and abuse (e.g., if we have restricted your account for breach of our Professional Community Policies ), enforce our User Agreement, or fulfill your request to "unsubscribe" from further messages from us. We will retain de-personalized information after your account has been closed. Information you have shared with others (e.g., through InMail, updates or group posts) will remain visible after you close your account or delete the information from your own profile or mailbox, and we do not control data that other Members have copied out of our Services. Groups content and ratings or review content associated with closed accounts will show an unknown user as the source. Your profile may continue to be displayed in the services of others (e.g., search tools) until they refresh their cache. 5. Other Important Information 5.1. Security We monitor for and try to prevent security breaches. Please use the security features available through our Services. We implement security safeguards designed to protect your data, such as HTTPS. We regularly monitor our systems for possible vulnerabilities and attacks. However, we cannot warrant the security of any information that you send us. There is no guarantee that data may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. 5.2. Cross-Border Data Transfers We store and use your data outside your country. We process data both inside and outside of the United States and rely on legally-provided mechanisms to lawfully transfer data across borders. Learn more . Countries where we process data may have laws which are different from, and potentially not as protective as, the laws of your own country. 5.3 Lawful Bases for Processing We have lawful bases to collect, use and share data about you. You have choices about our use of your data. At any time, you can withdraw consent you have provided by going to settings. We will only collect and process personal data about you where we have lawful bases. Lawful bases include consent (where you have given consent), contract (where processing is necessary for the performance of a contract with you (e.g., to deliver the LinkedIn Services you have requested) and “legitimate interests.” Learn more . Where we rely on your consent to process personal data, you have the right to withdraw or decline your consent at any time and where we rely on legitimate interests, you have the right to object. Learn More . If you have any questions about the lawful bases upon which we collect and use your personal data, please contact our Data Protection Officer here . If you're located in one of the Designated Countries or the UK, you can learn more about our lawful bases for processing in our European Regional Privacy Notice . 5.4. Direct Marketing and Do Not Track Signals Our statements regarding direct marketing and “do not track” signals. We currently do not share personal data with third parties for their direct marketing purposes without your permission. Learn more about this and about our response to “do not track” signals. 5.5. Contact Information You can contact us or use other options to resolve any complaints. If you have questions or complaints regarding this Policy, please first contact LinkedIn online. You can also reach us by physical mail . If contacting us does not resolve your complaint, you have more options . Residents in the Designated Countries and other regions may also have the right to contact our Data Protection Officer here . If this does not resolve your complaint, Residents in the Designated Countries and other regions may have more options under their laws. Key Terms Consent Where we process data based on consent, we will ask for your explicit consent. You may withdraw your consent at any time, but that will not affect the lawfulness of the processing of your personal data prior to such withdrawal. Where we rely on contract, we will ask that you agree to the processing of personal data that is necessary for entering into or performance of your contract with us. We will rely on legitimate interests as a basis for data processing where the processing of your data is not overridden by your interests or fundamental rights and freedoms. LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/10/20/from-multilingual-semantic-search-to-virtual-assistants-at-bosch-digital/#comments | From multilingual semantic search to virtual assistants at Bosch Digital - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. October 20, 2025 From multilingual semantic search to virtual assistants at Bosch Digital From sprawling PDFs to a fast, factual conversational assistant. Credit: Alexandra Francis This article is licensed under a CC BY-SA license. An e-bike rider types “reset Kiox 300 display,” and the answer must land in a heartbeat—not as a 200-page manual or a dozen near-miss FAQ links. The same expectation applies to mechanics updating brake firmware in a noisy workshop and to sales reps hunting torque specs on weak showroom Wi-Fi. Bosch eBike Systems an independent business division within the Bosch Group that serves millions of pages of manuals, release notes, and CAD drawings in twenty-seven languages. Roughly five percent of that content changes every month. But for Bosch eBike Systems, this wasn't just about efficiency; it was about elevating the customer experience and ensuring seamless support for riders, dealers, and service partners worldwide. Meeting expectations like these forced us from Bosch Digital to leave plain keyword search behind and build a retrieval engine that understands intent across languages, keeps costs predictable, and still answers in under a second. Why did keyword search crumble? Let's talk about why the old approach just couldn’t keep up. The world of bikes—and bike documentation—is wild with synonyms, part nicknames, and shifting terminology. “Display,” “NYON2,” or “BUI350” might all mean the same thing to a rider, but a bag-of-words search engine treats each as a stranger. Recall falls off a cliff unless you’re willing to hand-craft endless synonym lists. Typographical quirks and voice-to- text slip-ups don’t help. Real-world queries show up as “Kioxx 300,” “réinitialiser kios,” or, thanks to smeared microphones, as voice-recognition garble like “reset chaos 300.” Exact-token searches? They just shrug and show “No results.” In contrast, embedding-based search is far more forgiving of noisy input. Intent also gets lost in translation, especially for complex or constraint-laden queries. Someone might type, “Update brake firmware without a laptop” or “max torque under rain mode only.” Keyword search latches onto negated words (“laptop”) and dredges up the wrong docs. Modern transformer models, by contrast, grasp what the user really meant and rank results accordingly. Combine all these headaches—synonyms, noisy input, intent confusion, rapidly changing languages—and you’ve got the main reasons keyword search kept missing the mark. For Bosch Digital, moving to a vector-based, multilingual SmartSearch wasn’t an upgrade. It was survival. Designing a smarter way to search Once we mapped out every pitfall of traditional keyword search, it was time to rethink the pipeline from the ground up. Today, every answer SmartSearch delivers takes a precise, three-step journey from raw document to ranked result-a journey engineered for speed, accuracy, and multilingual scale. Step one: Crawling . Our self-developed Rust-based crawler zips through about 25 webpages per second, swiftly navigating vast documentation libraries while remaining polite enough never to trip rate limits—a digital librarian who reads fast but never ruffles feathers. Step two: Chunking before embedding. HTML gets dissected to separate titles from contents, and semantically coherent topics are stitched together using LLMs. Then come embeddings. Thanks to OpenAI's Ada 002 model (with a hefty 1536 dimensions), every content chunk lands accurately in semantic space. If it quacks like “reset Kiox 300,” our system will surface answers, even if the actual language is wildly different. Step three: Rank searches using a hybrid approach . Semantic search isn’t always the best approach. Dense vectors live in a vector database, while BM25 keeps classic keyword search in the mix. At query time, we blend the two—70% semantic, 30% sparse—then run the finalists through a MiniLM cross-encoder for the decisive sort. The result? Answers typically appear in about 750 ms, with 95% delivered in under a second and a half—even during those infamous firmware launch stampedes. But all this performance wasn’t without pain. Building SmartSearch meant ramming into hard limits: a 10-million vector per collection cap, painful re-indexing every time we added metadata, storage bills bloated by 32-bit floats, and no elegant ways to compress, quantize, or tier out storage to cheaper SSDs. Scale much beyond eight million vectors and everything slowed to a crawl. SmartSearch forced us to evolve—crawl, structure, represent, and rank—leaving the constraints of generic search infrastructure behind. The result is nimble, cost-effective, and fluent in every dialect your e-bike manuals throw at it. When search becomes chat With search bars, ten imperfect links might do. But for Bosch eBike Systems to deploy this as a conversational assistant for its global user base , there’s no room for error—the bot usually only has one shot. The very first retrieval must be laser-accurate, because every token we hand off to an LLM costs real money—and user trust evaporates if the bot’s opening statement misses the mark. Chat also explodes the data scale. Now we're not just retrieving from documentation, but juggling vast conversational histories and real-time follow-ups. Hundreds of thousands of chat snippets in the form of a short-term and long-term memory need to be stored, searched, and surfaced in milliseconds. Here, the cracks in our previous vector store yawned open: hard vector count limits, glacial re-index times, zero support for quantization or in-build multi-stage queries, and an insistence on keeping all vectors on DISC—bloating budgets and bottlenecking speed. Every shortcoming of the old architecture was amplified by chat’s relentless demand for cheaper, smarter, and scalable retrieval. Enter Qdrant. After pitting several vector databases against our most punishing workloads, Qdrant won hands-down. On a 25k-query, multilingual test set, it delivered recall above 0.96 with quantization, kept p95 latency under 120 ms with 400 concurrent chats, and we reduced the storage costs for our 10M dataset through quantization by 16x. Qdrant didn’t just handle chat’s challenges—it thrived on them. Now, suddenly, lightning-fast, chat-scale retrieval was not only possible, it was affordable. Slimming the brain, not the brains Our first prototype spoke fluent relevance but was a glutton for storage. Every text chunk wrapped itself in a massive 1536-dimensional Ada-002 vector—millions of high-precision floats devouring our SSDs by the rackful. Something had to give. The breakthrough came with Jina Embeddings v3. Flip a flag and you get binary quantized embeddings with 1024-dimension vector, flip another flag the 1024-dimension vector can be reduced with the power of Matryoshka Representation Learning down to 64. With lots of internal testing on recall quality, we found the best performance to quality ratio at 256-dimensions. Overnight, the footprint dropped by ninety-eight percent, and search quality even crept up over Ada-002. In recent evaluations, this setup outperformed Ada-003 and left a few MTEB chart-toppers in the dust (we will evaluate the Qwen3 embeddings model next). Additionally, thanks to our fine-tuned ModernBERT re-ranker, any minuscule loss vanishes completely. Qdrant turns those slimmed vectors into lightning answers. Because it natively understands multi-stage retrieval, we now run a two-stage search: a blistering-fast 256-dimension recall phase fused with BM25, then a fine-tuned reranker based on ModernBERT for pinpoint precision. This is how an ultra-lean operation should look like. Most importantly, Qdrant’s tiered storage lets us keep hot shards in RAM and cold vectors chilling on SSD, again cutting storage making it a total storage reduction of 5x while p95 latency remains well below 400 ms. Hybrid search? Dense scores blend seamlessly with BM25 in the same API call, so typo-riddled or perfect queries get equal love. The result: the answer to “reset Kiox 300” flashes onto a rider’s screen before the traffic light turns green—lighter vectors today, headroom for even slimmer tomorrow, and no compromises in quality. This is SmartSearch at chat-speed-fast, frugal, and fiercely precise, perfectly suiting as a backbone for our assistant. Names, not guesses: How GLiNER supercharged recognition By now, our assistant could find relevant facts with impressive speed and accuracy—but it still stumbled where it mattered most: names. “My Kiox 300 flashes 503 after the v1.7.4-B update” and “Nyon freezes on boot” appeared almost identical to a language model that didn’t truly see products, error codes, or firmware versions—just a blur of nouns and verbs. Context got lost; precision suffered. And bringing in a multi-billion-parameter AI hammer for this problem was pure overkill. The breakthrough came from an unexpected place—a doomscroll through LinkedIn. There it was: GLiNER, promising general, lightweight NER (named-entity recognition). Few-shot learning, CPU-fast inference, and a footprint small enough (800 MB) to fit in our Docker image—GLiNER checked every box we didn’t even know we had. It wasn’t just “easy”—it was transformative. With only a handful of annotated examples—just two for products, two for error codes, and two for firmware—GLiNER learned our entire domain in minutes. Inference was nearly instant: less than 30 ms per paragraph, even on a single laptop core. With labels persisting across chat turns, context sticks. So when a rider says, “Kiox 300 shows 503 after v1.7.4-B,” then follows up with, “Does it also hit CX Gen4?” the assistant keeps every product, error, and firmware straight. Each answer is routed with surgical precision, no more mistaking a Kiox for a Nyon, no more guesswork. All because of a LinkedIn scroll, a 800 MB model, and few lines of labeled text. Names matter. Now, finally, the assistant knows them cold. From answers to actions: Agentic workflows for the next-gen assistant Finding the right paragraph is one thing. For the Bosch eBike Systems assistant, tasked with supporting diverse user needs from simple inquiries to complex troubleshooting, carrying out a real-world task—filing a warranty claim, collecting the latest firmware links for three different drive units, or guiding a mechanic step-by-step through a “display reset” on chat—demands something more. A simple pipeline falls short: modern assistants need to reason, plan, coordinate, and act, not just retrieve. This is where agentic workflows come in. Instead of funneling every query through a single, monolithic language model (and hoping it never drops a detail), our platform orchestrates a team of specialized AI agents, each with a defined responsibility. Picture a user asking, “My Kiox 300 flashes error 503. Can you check if my firmware is out of date, tell me how to fix it, and draft a message to support if that doesn’t work?” In the old days, that threw a tangle of ambiguous instructions at a black-box chatbot. Now, agentic workflows break the request into manageable, coordinated steps—each agent picking up what it does best. The process starts with an orchestrator agent that parses user intent into subtasks: error code lookup, firmware verification, troubleshooting guide retrieval, and, if needed, support ticket drafting. Each subtask is routed to a specialist agent—e.g. a custom reasoning workflow based on product variants and corresponding information. These agents consult our retrieval backbone (built for precision, even with noisy queries), gather facts, cross-check versions, and piece together the findings. The upshot? Agentic workflows let our assistant go beyond answering “what”—they let it do “how” and “what’s next,” chaining knowledge, actions, and even human handover, seamlessly. Whether it’s a simple spec lookup, a multi-step troubleshooting procedure, or orchestrating real-world follow-ups, agentic workflows are the connective tissue behind our assistant’s leap from search box to conversational partner. We’ve found that this modular, transparent approach doesn't just improve speed-it brings new peace of mind. When something breaks, the scratchpad log shows exactly what was done (and why). If a process hits a wall, the orchestrator pivots—never leaving the user in limbo, and never letting important details fall between the cracks. The result: tasks handled start-to-finish, user intent actually understood, and the confidence that, under the hood, every answer isn’t just the luck of a generative roll, but the well-planned output of agents working in concert. That’s agentic workflow in action-the step change from answers to real assistance. What we’d do again—and what we wouldn’t Scars teach deeper than trophies, so here are the three that still itch (in all the right ways): Polish the pages before you pamper the model We once spent a solid week deduplicating near-identical paragraphs, chopping out boilerplate (“© 2021 Bosch eBike Systems-All rights reserved”), and flattening FAQ echo-chambers until they stopped swallowing fresh questions whole. The improvement in search quality? Bigger than any new encoder, model drop, or clever agent could manage—by a mile. Lesson learned: a clean, well-structured corpus is the cheapest upgrade you’ll never find on Hugging Face, and it makes every downstream agent that much sharper. Bake shrinkage into your day-one plans Binary quantization and dimension-slimming saved a small fortune on storage and inference. But we bolted those features on after launch, which meant re-encoding 10 million chunks while users were searching live—a gnarly headache nobody needs. Next time, the compression and size targets go on the first whiteboard, right up there with recall, latency, and now, agent handoff compatibility. Diets work better before the group photo. And it’s not just storage: your embedding model, vector database, chunking strategy, and, yes, agent workflows and communication schemes all need to work together from the start. Complex queries mean complex agent designs LLMs are both a blessing and a budget breaker—latency, cost, and “intelligence” all become make-or-break variables in a multi-agent system. As workflows get agentic—planning, delegating, keeping state—the challenge shifts from “Can we answer this?” to “Can we coordinate this, auditable and efficient?” Keep the data clean, plan your storage and compute diet early, and never skimp on people who can read between the lines and handle the edge cases. Everything else is just another line on a model card, or now, an agent manifest. This collaborative endeavor, made possible by the strategic investment and close partnership with Bosch eBike Systems, has truly reshaped how information is accessed and utilized within their ecosystem. In the end, it’s the painful lessons—not just the pretty graphs—that shaped SmartSearch into the system it is now. And with each round of learning, our answers get a little faster, a little sharper, and maybe-one day—just a little closer to perfect. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Daly Singh AI Squad Lead and Product Owner at Bosch Digital As AI Squad Lead and Product Owner at Bosch Digital, he turns generative-AI research into real-world impact. He focuses on creating human-centered AI products that blend seamlessly into everyday experiences—believing that the best technology feels … Jeremy Teichmann Tech Lead at Bosch Digital Tech Lead at Bosch Digital, builds the architecture behind Bosch’s AI products and services. Leading an international engineering team, he bridges innovation and reliability—designing scalable AI systems that turn ambitious ideas into dependable, future-ready solutions. AI contributed CC BY-SA 4.0 Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://docs.devcycle.com/cli-mcp/mcp-getting-started/#available-tools | MCP Getting Started | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up CLI / MCP Overview CLI CLI Reference CLI User Guides Projects Environments SDK Keys Features Variables Variations Targeting Rules Self-Targeting CLI User Guides MCP MCP Getting Started MCP Reference MCP User Guides Incident Investigation MCP On this page DevCyle MCP Getting Started The DevCycle Model Context Protocol (MCP) Server is based on the DevCycle CLI, it enables AI-powered code editors like Cursor and Windsurf, or general-purpose tools like Claude Desktop, to interact directly with your DevCycle projects and make changes on your behalf. Quick Setup The DevCycle MCP is hosted so there is no need to set up a local server. We'll walk you through installation and authentication with your preferred AI tools. Direct Connection: For clients that natively support the MCP specification with OAuth authentication, you can connect directly to our hosted server: https://mcp.devcycle.com/mcp Protocol Support : Our MCP server supports both SSE and HTTP Streaming protocols, automatically negotiating the best option based on your client's capabilities. Alternative Endpoint : If your client has issues with protocol negotiation, use the SSE-only endpoint: https://mcp.devcycle.com/sse MCP Registry : If you're using registry.modelcontextprotocol.io , the DevCycle MCP is listed as: com.devcycle/mcp info These instructions use the remote DevCycle MCP server. For installation of the local MCP server, see the reference docs . Configure Your AI Client Cursor VS Code Claude Code Claude Desktop Windsurf Codex CLI Gemini CLI 📦 Install in Cursor To open Cursor and automatically add the DevCycle MCP, click the install button above. Alternatively, add the following to your ~/.cursor/mcp_settings.json file. To learn more, see the Cursor documentation . { "mcpServers" : { "DevCycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Authentication in Cursor: After configuration, you'll see DevCycle MCP listed as "Needs login" with a yellow indicator Click on the DevCycle MCP server to initiate the authorization process This opens a browser authorization page at mcp.devcycle.com Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com You'll be redirected back to Cursor with the server now active 📦 Install in VS Code To open VS Code and automatically add the DevCycle MCP, click the install button above. Alternatively, add the following to your .continue/config.json file. To learn more, see the Continue documentation . { "mcpServers" : { "DevCycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Authentication in VS Code: After configuration, open the MCP settings panel in VS Code Find the DevCycle MCP server and click "Start Server" VS Code will show a dialog: "The MCP Server Definition 'DevCycle' wants to authenticate to mcp.devcycle.com" Click "Allow" to proceed with authentication This opens a browser authorization page at mcp.devcycle.com Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com You'll be redirected back to VS Code with the server now active Step 1: Open Terminal Open your terminal to access the Claude CLI. Step 2: Add DevCycle MCP Server claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp Step 3: Manage MCP Connection In the Claude CLI, enter the MCP management interface: /mcp Step 4: Authentication You'll see the DevCycle server listed as "disconnected • Enter to login": Select the DevCycle server and press Enter to login Follow the CLI prompts to initiate the Authentication process This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Claude Code where the server will show as connected For more details, see the Claude Code MCP documentation . Step 1: Access MCP Configuration Option 1: Through Claude Desktop Settings (Recommended) Open Claude Desktop and go to Settings Navigate to Developer → Local MCP servers Click "Edit Config" to open the configuration file directly Option 2: Manual Configuration File Alternatively, locate and edit your Claude Desktop configuration file: macOS : ~/Library/Application Support/Claude/claude_desktop_config.json Windows : %APPDATA%\Claude\claude_desktop_config.json Step 2: Add DevCycle Configuration Add or merge the following configuration: { "mcpServers" : { "devcycle" : { "command" : "npx" , "args" : [ " [email protected] " , "https://mcp.devcycle.com/mcp" ] } } } Step 3: Restart Claude Desktop Close and reopen Claude Desktop for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, Claude Desktop will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Claude Desktop where the MCP tools will be active Step 1: Access MCP Configuration Open Windsurf and go to Settings > Winsurf Settings Scroll to the Cascade section Click "Manage MCPs" Step 2: Edit Raw Configuration In the "Manage MCP servers" interface, click "View raw config" Add the following configuration to the JSON file: { "mcpServers" : { "DevCycle" : { "serverUrl" : "https://mcp.devcycle.com/mcp" } } } Step 3: Refresh and Authenticate Save the configuration file Click "Refresh" in the "Manage MCP servers" interface The DevCycle server will appear and prompt for authentication Follow the authentication flow: Browser opens at mcp.devcycle.com for authorization Click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Windsurf where DevCycle will show as "Enabled" with all tools available which can be configured independently Step 1: Access MCP Configuration Locate and edit your OpenAI Codex CLI configuration file: All platforms : ~/.codex/config.toml Step 2: Add DevCycle MCP Server Add the following TOML configuration to enable the DevCycle MCP server: [mcp_servers.devcycle] url = "https://mcp.devcycle.com/mcp" Step 3: Restart Codex CLI Restart your Codex CLI session for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, the Codex CLI will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to the Codex CLI where the DevCycle MCP tools will be active For more details, see the OpenAI Codex MCP documentation . Step 1: Access MCP Configuration Locate and edit your Gemini CLI settings file: All platforms : ~/.gemini/settings.json Step 2: Add DevCycle MCP Server Add or merge the following configuration to enable the DevCycle MCP server: { "mcpServers" : { "devcycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Step 3: Restart Gemini CLI Restart your Gemini CLI session for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, the Gemini CLI will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to the Gemini CLI where the DevCycle MCP tools will be active For more details, see the Gemini CLI MCP documentation . Available Tools The DevCycle MCP Server provides comprehensive feature flag management tools organized into 6 categories : Category Tools Description Feature Management list_features , create_feature , update_feature , update_feature_status , delete_feature , cleanup_feature , get_feature_audit_log_history Create and manage feature flags Variable Management list_variables , create_variable , update_variable , delete_variable Manage feature variables Project Management list_projects , get_current_project , select_project Project selection and details Self-Targeting & Overrides get_self_targeting_identity , update_self_targeting_identity , list_self_targeting_overrides , set_self_targeting_override , clear_feature_self_targeting_overrides Testing and overrides Results & Analytics get_feature_total_evaluations , get_project_total_evaluations Usage analytics SDK Installation install_devcycle_sdk SDK install guides and examples Try It Out Once configured, try asking your AI assistant: "Create a new feature flag called 'new-checkout-flow'" "List all features in my project" "Enable targeting for the header-redesign feature in production" "Show me evaluation analytics for the last 7 days" Next Steps MCP Reference - Complete tool documentation with all parameters CLI Reference - Learn about the underlying CLI commands Getting Help GitHub Issues : GitHub Issues General Documentation : DevCycle Docs DevCycle Community : Discord Support : Contact Support Edit this page Last updated on Jan 9, 2026 Previous CLI User Guides Next MCP Getting Started Quick Setup Configure Your AI Client Available Tools Try It Out Next Steps Getting Help DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:30 |
https://developer.x.com/en/products/twitter-api/enterprise/enterprise-api-interest-form | Apply for enterprise API access | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> X Enterprise API Interest Form Thanks for reaching out to X Developer Platform! Please visit our documentation hub and developer forum for additional information and support. In order to get started, we will need some preliminary information from you. For self service access, please explore our Basic or Pro API access tiers. Tell us about yourself Enterprise API pricing starts at $50,000 / Month, based on usage and needs. Disclaimer: personal emails will be automatically filtered Acknowledgment of X Terms - By filling out this form, you consent to X processing of the data you provide as set forth in the X Privacy Policy and accept that your company policy permits you to accept messages from X. <path d="M27.243 36l14.879-14.879a2.998 2.998 0 0 0 0-4.242 2.998 2.998 0 0 0-4.242 0L23 31.758 8.122 16.879a2.998 2.998 0 0 0-4.242 0 2.998 2.998 0 0 0 0 4.242L18.758 36 3.879 50.879A2.998 2.998 0 0 0 6.001 56a2.99 2.99 0 0 0 2.121-.879L23 40.242l14.879 14.879A2.991 2.991 0 0 0 40 56a2.998 2.998 0 0 0 2.121-5.121L27.243 36z" /> </svg>"> By choosing “Yes” you agree to receive various marketing communications via email, telephone and/or text message from X. You may unsubscribe at any time. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://stackoverflow.blog/author/cameron-r-wolfe-phd/ | Cameron R. Wolfe, PhD - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Cameron R. Wolfe, PhD I’m currently the Director of AI at Rebuy, a personalized search and recommendations platform for D2C e-commerce brands. Prior to Rebuy, I was a Research Scientist at Alegion. Additionally, I worked for Salesforce Commerce Cloud for two years. April 28, 2025 How self-supervised learning revolutionized natural language processing and gen AI Self-supervised learning is a key advancement that revolutionized natural language processing and generative AI. Here’s how it works and two examples of how it is used to train language models. Cameron R. Wolfe, PhD 26 comment s llm AI contributed February 26, 2025 Variants of LoRA Want to train a specialized LLM on your own data? The easiest way to do this is with low rank adaptation (LoRA), but many variants of LoRA exist. Cameron R. Wolfe, PhD 0 comment s llm AI contributed December 5, 2024 Four approaches to creating a specialized LLM Wondering how to go about creating an LLM that understands your custom data? Start here. Cameron R. Wolfe, PhD 2 comment s llm AI contributed October 31, 2024 A brief summary of language model finetuning Here's a (brief) summary of language model finetuning, the various approaches that exist, their purposes, and what we know about how they work. Cameron R. Wolfe, PhD 0 comment s llm AI September 26, 2024 Masked self-attention: How LLMs learn relationships between tokens Masked self-attention is the key building block that allows LLMs to learn rich relationships and patterns between the words of a sentence. Let’s build it together from scratch. Cameron R. Wolfe, PhD 1 comment llm AI contributed August 22, 2024 LLMs evolve quickly. Their underlying architecture, not so much. The decoder-only transformer architecture is one of the most fundamental ideas in AI research. Cameron R. Wolfe, PhD 0 comment s llm architecture AI contributed August 15, 2024 Practical tips for retrieval-augmented generation (RAG) Retrieval-augmented generation (RAG) is one of the best (and easiest) ways to specialize an LLM over your own data, but successfully applying RAG in practice involves more than just stitching together pretrained models. Cameron R. Wolfe, PhD 0 comment s retrieval augmented generation llm generative AI contributed June 27, 2024 Explaining generative language models to (almost) anyone Here’s a simple, three-part framework that explains generative language models. Cameron R. Wolfe, PhD 19 comment s generative AI llm contributed April 4, 2024 How do mixture-of-experts layers affect transformer models? This new LLM technique has started improving the results of models without additional training. Cameron R. Wolfe, PhD 0 comment s generative AI llm mixture of experts contributed Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stripe.com/en-sk/privacy | Chat with Stripe sales Privacy Policy Stripe logo Legal Stripe Privacy Policy & Privacy Center Privacy Policy Cookies Policy Data Privacy Framework Service Providers List Data Processing Agreement Supplier Data Processing Agreement Stripe Privacy Center Privacy Policy This Privacy Policy will be updated on January 16, 2026. Please review the upcoming changes here . Last updated: January 16, 2025 This Privacy Policy includes important information about your personal data and we encourage you to read it carefully. Welcome We provide financial infrastructure for the internet. Individuals and businesses of all sizes use our technology and services to facilitate purchases, accept payments, send payouts, and manage online businesses. This Privacy Policy (“Policy”) describes the Personal Data that we collect, how we use and share it, and details on how you can reach us with privacy-related inquiries. The Policy also outlines your rights and choices as a data subject, including the right to object to certain uses of your Personal Data. Depending on the activity, Stripe assumes the role of a “data controller” and/or “data processor” (or “service provider”). For more details about our privacy practices, including our role, the specific Stripe entity responsible under this Policy, and our legal bases for processing your Personal Data, please visit our Privacy Center . Defined Terms In this Policy, “Stripe”, “we”, “our,” or “us” refers to the Stripe entity responsible for the collection, use, and handling of Personal Data as described in this document. Depending on your jurisdiction, the specific Stripe entity accountable for your Personal Data might vary. Learn More . “Personal Data” refers to any information associated with an identified or identifiable individual, which can include data that you provide to us, and that we collect about you during your interaction with our Services (such as device information, IP address, etc.). “Services” refers to the products, services, devices, and applications, that we provide under the Stripe Services Agreement (“Business Services”) or the Stripe Consumer Terms of Service (“End User Services”); websites (“Sites”) like Stripe.com and Link.com; and other Stripe applications and online services. We provide Business Services to entities (“Business Users”). We provide End User Services directly to individuals for their personal use. “Financial Partners” are financial institutions, banks, and other partners such as payment method acquirers, payout providers, and card networks that we partner with to provide the Services. Depending on the context, “you” might be an End Customer, End User, Representative, or Visitor: End Users. When you use an End User Service, such as saving a payment method with Link, for personal use we refer to you as an “End User.” End Customers. When you are not directly transacting with Stripe, but we receive your Personal Data to provide Services to a Business User, including when you make a purchase from a Business User on a Stripe Checkout page or receive payments from a Business User, we refer to you as an “End Customer.” Representatives. When you are acting on behalf of an existing or potential Business User—perhaps as a company founder, account administrator for a Business User, or a recipient of an employee credit card from a Business User via Stripe Issuing—we refer to you as a “Representative.” Visitors. When you interact with Stripe by visiting a Site without being logged into a Stripe account, or when your interaction with Stripe does not involve you being an End User, End Customer, or Representative, we refer to you as a “Visitor.” For example, you are a Visitor when you send a message to Stripe asking for more information about our Services. In this Policy, “Transaction Data” refers to data collected and used by Stripe to facilitate transactions you request. Some Transaction Data is Personal Data and may include: your name, email address, contact number, billing and shipping address, payment method information (like credit or debit card number, bank account details, or payment card image chosen by you), merchant and location details, amount and date of purchase, and in some instances, information about what was purchased. 1. Personal Data that we collect and how we use and share it 2. More ways we collect, use and share Personal Data 3. Legal bases for processing data 4. Your rights and choices 5. Security and retention 6. International data transfers 7. Updates and notifications 8. Jurisdiction-specific provisions 9. Contact us 10. US Consumer Privacy Notice 1. Personal Data we collect and how we use and share it Our collection and use of Personal Data differs based on whether you are an End User, End Customer, Representative, or Visitor, and the specific Service that you are using. For example, if you're a sole proprietor who wants to use our Business Services, we may collect your Personal Data to onboard your business; at the same time, you might also be an End Customer if you've bought goods from another Business User that is using our Services for payment processing. You could also be an End User if you used our End User Service, such as Link, for those transactions. 1.1 End Users We provide End User Services when we provide the Services directly to you for your personal use (e.g., Link). Additional details regarding our collection, usage, and sharing of End User Personal Data, including the legal bases we rely on for processing such data, can be found in our Privacy Center . a. Personal Data we collect about End Users Using Link or Connecting your bank account . Stripe offers a service called "Link," which allows you to create an account and store information for future interactions with Stripe’s Services and Business Users. You may save a number of different kinds of Personal Data using Link. For instance, you may save your name, payment method details, contact information, and address to conveniently use saved information to pay for transactions across our Business Users. When you choose to pay with Link, we will also collect Transaction Data associated with your transactions. Learn More . You can also share and save bank account details to your Link account using Stripe’s Financial Connections product. When you use Financial Connections, Stripe will periodically collect and process your account information (such as bank account owner information, account balances, account number and details, account transactions, and, in some cases, log-in credentials). You can ask us to cease the collection of such data at any time. Learn More . You can also use your Link account to access services provided by Stripe’s partner businesses, such as Buy Now, Pay Later (BNPL) services or crypto wallet services. In these situations, we will collect and share additional Personal Data with partner businesses to facilitate your use of such services. You can save this information to your Link account to access similar services in the future. We may also receive certain information about you from partner businesses in connection with the services they provide. Learn More . Finally, you can use Link to store your identity documents (such as your driver’s license) so that you can share them in future interactions with Stripe or its Business Users. Paying Stripe . When you purchase goods or services directly from Stripe, we receive your Transaction Data. For instance, when you make a payment to Stripe Climate, we collect information about the transaction, as well as your contact and payment method details. Identity/Verification Services . We offer an identity verification service that automates the comparison of your identity document (such as a driver’s license) with your image (such as a selfie). You can separately consent to us using your biometric data to enhance our verification technology, with the option to revoke your consent at any time. Learn More . More . For further information about other types of Personal Data that we may collect about End Users, including about your online activity and your engagement with our End User Services, please see the More ways we collect, use, and share Personal Data section below. b. How we use and share Personal Data of End Users Services . We use and share your Personal Data to provide the End User Services to you, which includes support, personalization (such as language preferences and setting choices), and communication about our End User Services (such as communicating Policy updates and information about our Services). For example, Stripe may use cookies and similar technologies or the data you provide to our Business Users (such as when you input your email address on a Business User’s website) to recognize you and help you use Link when visiting our Business User’s website. Learn more about how we use cookies and similar technologies in Stripe’s Cookie Policy . Our Business Users. When you use Link to make payments with our Business Users, we share your Personal Data, including name, contact information, payment method details, and Transaction Data with those Business Users. Learn More . You can also direct Stripe to share your saved bank account information and identity documents with Business Users you do business with. Once we share your Personal Data with Business Users, we may process that Personal Data as a Data Processor for those Business Users, as detailed in Section 1.2 of this Policy. You should consult the privacy policies of the Business Users’ you do business with for information on how they use the information shared with them. Fraud Detection and Loss Prevention . We use your Personal Data collected across our Services to detect fraud and prevent financial losses for you, us, and our Business Users and Financial Partners, including detecting unauthorized purchases. We may provide Business Users and Financial Partners, including those that use our fraud prevention-related Business Services (such as Stripe Radar), with Personal Data about you (including your attempted transactions) so that they can assess the fraud or loss risk associated with the transaction. Learn more about how we may use technology to assess the fraud risk associated with an attempted transaction and what information we share with Business Users and Financial Partners here and here . Advertising . Where permitted by applicable law, we may use your Personal Data, including Transaction Data, to assess your eligibility for, and offer you, other End User Services or promote existing End User Services, including through co-marketing with partners such as Stripe Business Users. Learn more . Subject to applicable law, including any consent requirements, we use and share End User Personal Data with third party partners to allow us to advertise our End User Services to you, including through interest-based advertising, and to track the efficacy of such ads. We do not transfer your Personal Data to third parties in exchange for payment, but we may provide your data to third-party partners, such as advertising partners, analytics providers, and social networks, who assist us in advertising our Services to you. Learn more . More . For further information about ways we may use and share End Users' Personal Data, please see the More ways we collect, use, and share Personal Data section below. 1.2 End Customers Stripe provides various Business Services to our Business Users, which include processing in-person or online payments or payouts for those Business Users. When acting as a service provider—also referred to as a Data Processor—for a Business User, we process End Customer Personal Data in accordance with our agreement with the Business User and the Business User's lawful instructions. This happens, for example, when we process a payment for a Business User because you purchased a product from them, or when the Business User asks us to send you funds. Business Users are responsible for ensuring that the privacy rights of their End Customers are respected, including obtaining appropriate consents and making disclosures about their own data collection and use associated with their products and services. If you're an End Customer, please refer to the privacy policy of the Business User you're doing business with for its privacy practices, choices, and controls. We provide more comprehensive information about our collection, use, and sharing of End Customer Personal Data in our Privacy Center , including the legal bases we rely on for processing your Personal Data. a. Personal Data we collect about End Customers Transaction Data . If you're an End Customer making payments to, receiving refunds or payments from, initiating a purchase or donation, or otherwise transacting with our Business User, whether in-person or online, we receive your Transaction Data. We may also receive your transaction history with the Business User. Learn More . Additionally, we may collect information entered into a checkout form even if you opt not to complete the form or transaction with the Business User. Learn More . A Business User who uses Stripe’s Terminal Service to provide its goods or services to End Customers may use the Terminal Service to collect End Customer Personal Data (like your name, email, phone number, address, signature, or age) in accordance with its own privacy policy. Identity/Verification Information . Stripe provides a verification and fraud prevention Service that our Business Users can use to verify Personal Data about you, such as your authorization to use a particular payment method. During the process, you’d be asked to share with us certain Personal Data (like your government ID and selfie for biometric verification, Personal Data you input, or Personal Data that is apparent from the physical payment method like a credit card image). To protect against fraud and determine if somebody is trying to impersonate you, we may cross-verify this data with information about you that we've collected from Business Users, Financial Partners, business affiliates, identity verification services, publicly available sources, and other third party service providers and sources. Learn More . More . For further information about other types of Personal Data that we may collect about End Customers, including about your online activity, please see the More ways we collect, use, and share Personal Data section below. b. How we use and share Personal Data of End Customers To provide our Business Services to our Business Users, we use and share End Customers' Personal Data with them. Where allowed, we also use End Customers' Personal Data for Stripe’s own purposes such as enhancing security, improving and offering our Business Services, and preventing fraud, loss, and other damages, as described further below. Payment processing and accounting . We use your Transaction Data to deliver Payment-related Business Services to Business Users — including online payment transactions processing, sales tax calculation, and invoice, bill, and dispute handling — and to help them determine their revenue, settle their bills, and execute accounting tasks. Learn More . We may also use your Personal Data to provide and improve our Business Services. During payment transactions, your Personal Data is shared with various entities in connection with your transaction. As a service provider or data processor, we share Personal Data to enable transactions as directed by Business Users. For instance, when you choose a payment method for your transaction, we may share your Transaction Data with your bank or other payment method provider, including as necessary to authenticate you, Learn More , process your transaction, prevent fraud, and handle disputes. The Business User you choose to do business with also receives Transaction Data and might share the data with others. Please review your merchant’s, bank’s, and payment method provider’s privacy policies for more information about how they use and share your Personal Data. Financial services . Certain Business Users leverage our Services to offer financial services to you via Stripe or our Financial Partners. For example, a Business User may issue a card product with which you can purchase goods and services. Such cards could carry the brand of Stripe, the bank partner, and/or the Business User. In addition to any Transaction Data we may generate or receive when these cards are used for purchases, we also collect and use your Personal Data to provide and manage these products, including assisting our Business Users in preventing misuse of the cards. Please review the privacy policies of the Business User and, if applicable, our bank partners associated with the financial service (the brands of which may be shown on the card) for more information. Identity/Verification services . We use Personal Data about your identity to perform verification services for Stripe or for the Business Users that you are transacting with, to prevent fraud, and to enhance security. For these purposes we may use Personal Data you provide directly or Personal Data we obtain from our service providers, including for phone verification. Learn More . If you provide a selfie along with an image of your identity document, we may employ biometric technology to compare and calculate whether they match and verify your identity. Learn More . Fraud detection and loss prevention. We use your Personal Data collected across our Services to detect and prevent losses for you, us, our Business Users, and Financial Partners. We may provide Business Users and Financial Partners, including those using our fraud prevention-related Business Services, with your Personal Data (including your attempted transactions) to help them assess the fraud or loss risk associated with a transaction. Learn more about how we may use technology to assess the fraud risk associated with an attempted transaction and what information we share with Business Users and Financial Partners here and here . Our Business Users (and their authorized third parties). We share End Customers' Personal Data with their respective Business Users and parties directly authorized by those Business Users to receive such data. Here are common examples of such sharing: When a Business User instructs Stripe to provide another Business User with access to its Stripe account, including data related to its End Customers, via Stripe Connect. Sharing information that you have provided to us with a Business User so that we can send payments to you on behalf of that Business User. Sharing information, documents, or images provided by an End Customer with a Business User when the latter uses Stripe Identity, our identity verification Service, to verify the identity of the End Customer. The Business Users you choose to do business with may further share your Personal Data with third parties (like additional third party service providers other than Stripe). Please review the Business User’s privacy policy for more information. Advertising by Business Users . If you initiate a purchasing process with a Business User, the Business User receives your Personal Data from us in connection with our provision of Services even if you don't finish your purchase. The Business User may use your Personal Data to market and advertise their products or services, subject to the terms of their privacy policy. Please review the Business User’s privacy policy for more information, including your rights to stop their use of your Personal Data for marketing purposes. More . For further information about additional ways by which we may use and share End Customers' Personal Data, please see the More ways we collect, use, and share Personal Data section below. 1.3 Representatives We collect, use, and share Personal Data from Representatives of Business Users (for example, business owners) to provide our Business Services. For more information about how we collect, use, and share Personal Data from Representatives, as well as the legal bases we rely on for processing such Personal Data, please visit our Privacy Center . a. Personal Data we collect about Representatives Registration and contact information . When you register for a Stripe account for a Business User (including incorporation of a Business), we collect your name and login credentials. If you register for or attend an event organized by Stripe or sign up to receive Stripe communications, we collect your registration and profile data. As a Representative, we may collect your Personal Data from third parties, including data providers, to advertise, market, and communicate with you as detailed further in the More ways we collect, use, and share Personal Data section below. We may also link a location with you to tailor the Services or information effectively to your needs. Learn More . Identification Information . As a current or potential Business User, an owner of a Business User, or a shareholder, officer, or director of a Business User, we need your contact details, such as name, postal address, telephone number, and email address, to fulfill our Financial Partner and regulatory requirements, verify your identity, and prevent fraudulent activities and harm to the Stripe platform. We collect your Personal Data, such as ownership interest in the Business User, date of birth, government-issued identity documents, and associated identifiers, as well as any history of fraud or misuse, directly from you and/or from publicly available sources, third parties such as credit bureaus and via the Services we provide. Learn More . You may also choose to provide us with bank account information. More . For further information about other types of Personal Data that we may collect about Representatives, including your online activity, please see the More ways we collect, use, and share Personal Data section below. b. How we use and share Personal Data of Representatives We typically use the Personal Data of Representatives to provide the Business Services to the corresponding Business Users. The ways we use and share this data are further described below. Business Services . We use and share Representatives’ Personal Data with Business Users to provide the Services requested by you or the Business User you represent. In some instances, we may have to submit your Personal Data to a government entity to provide our Business Services, for purposes such as the incorporation of a business, or calculating and paying applicable sales tax. For our tax-related Business Services, we may use your Personal Data to prepare tax documents and file taxes on behalf of the Business User you represent. For our Atlas business incorporation Services, we may use your Personal Data to submit forms to the IRS on your behalf and file documents with other government authorities, such as articles of incorporation in your state of incorporation. We share Representatives’ Personal Data with parties authorized by the corresponding Business User, such as Financial Partners servicing a financial product, or third party apps or services the Business User chooses to use alongside our Business Services. Here are common examples of such sharing: Payment method providers, like Visa or WeChat Pay, require information about Business Users and their Representatives who accept their payment methods. This information is typically required during the onboarding process or for processing transactions and handling disputes for these Business Users. Learn More . A Business User may authorize Stripe to share your Personal Data with other Business Users to facilitate the provision of Services through Stripe Connect. The use of Personal Data by a third party authorized by a Business User is subject to the third party’s privacy policy. If you are a Business User who has chosen a name that includes Personal Data (for example, a sole proprietorship or family name in a company name), we will use and share such information for the provision of our Services in the same way we do with any company name. This may include, for example, displaying it on receipts and other transaction-identifying descriptions. Fraud detection and loss prevention . We use Representatives’ Personal Data to identify and manage risks that our Business Services might be used for fraudulent activities causing losses to Stripe, End Users, End Customers, Business Users, Financial Partners, and others. We also use information about you obtained from publicly available sources, third parties like credit bureaus and from our Services to address such risks, including to identify patterns of misuse and monitor for terms of service violations. Stripe may share Representatives' Personal Data with Business Users, our Financial Partners, and third party service providers, including phone verification providers, Learn More , to verify the information provided by you and identify risk indicators. Learn More . We also use and share Representatives' Personal Data to conduct due diligence, including conducting anti-money laundering and sanctions screening in accordance with applicable law. Advertising . Where permitted by applicable law, and where required with your consent, we use and share Representatives’ Personal Data with third parties, including Partners , so we can advertise and market our Services and Partner integrations. Subject to applicable law, including any consent requirements, we may advertise through interest-based advertising and track the efficacy of such ads. See our Cookie Policy . We do not transfer your Personal Data to third parties in exchange for payment. However, we may provide your data to third party partners, like advertising partners, analytics providers, and social networks, who assist us in advertising our Services. Learn more . We may also use your Personal Data, including your Stripe account activity, to evaluate your eligibility for and offer you Business Services or promote existing Business Services. Learn more . More . For further information about additional ways by which we may use and share Representatives’ Personal Data, please see the More ways we collect, use, and share Personal Data section below. 1.4 Visitors We collect, use, and share the Personal Data of Visitors. More details about how we collect, use, and share Visitors’ Personal Data, along with the legal bases we rely on for processing such Personal Data, can be found in our Privacy Center . a. Personal Data we collect about Visitors When you browse our Sites, we receive your Personal Data, either provided directly by you or collected through our use of cookies and similar technologies. See our Cookie Policy for more information. If you opt to complete a form on the Site or third party websites where our advertisements are displayed (like LinkedIn or Facebook), we collect the information you included in the form. This may include your contact information and other information pertaining to your questions about our Services. We may also associate a location with your visit. Learn More . More . Further details about other types of Personal Data that we may collect from Visitors, including your online activity, can be found in the More ways we collect, use, and share Personal Data section below. b. How we use and share Personal Data of Visitors Personalization . We use the data we collect about you using cookies and similar technologies to measure engagement with the content on the Sites, improve relevancy and navigation, customize your experience (such as language preference and region-specific content), and curate content about Stripe and our Services that's tailored to you. For instance, as not all of our Services are available globally, we may customize our responses based on your region. Advertising . Where permitted by applicable law, and where required with your consent, we use and share Visitors’ Personal Data with third parties, including Partners , so we can advertise and market our Services and Partner integrations. Subject to applicable law, including any consent requirements, we may advertise through interest-based advertising and track the efficacy of such ads. See our Cookie Policy . We do not transfer your Personal Data to third parties in exchange for payment, but we may provide your data to third party partners, like advertising partners, analytics providers, and social networks, who assist us in advertising our Services. Learn more . Engagement . As you interact with our Sites, we use the information we collect about and through your devices to provide opportunities for further interactions, such as discussions about Services or interactions with chatbots, to address your questions. More . For more information about additional ways we may use and share Visitors’ Personal Data, please see the More ways we collect, use, and share Personal Data section below. 2. More ways we collect, use, and share Personal Data In addition to the ways described above, we also process your Personal Data as follows: a. Collection of Personal Data Online Activity . Depending on the Service used and how our Business Services are implemented by the Business Users, we may collect information related to: The devices and browsers you use across our Sites and third party websites, apps, and other online services (“Third Party Sites”). Usage data associated with those devices and browsers and your engagement with our Services, including data elements like IP address, plug-ins, language preference, time spent on Sites and Third Party Sites, pages visited, links clicked, payment methods used, and the pages that led you to our Sites and Third Party Sites. We also collect activity indicators, such as mouse activity indicators, to help us detect fraud. Learn More . See also our Cookie Policy . Communication and Engagement Information . We also collect information you choose to share with us through various channels, such as support tickets, emails, or social media. If you respond to emails or surveys from Stripe, we collect your email address, name, and any other data you opt to include in your email or responses. If you engage with us over the phone, we collect your phone number and any other information you might provide during the call. Calls with Stripe or Stripe representatives may be recorded. Learn More . Additionally, we collect your engagement data, like your registration for, attendance at, or viewing of Stripe events and any other interactions with Stripe personnel. Forums and Discussion Groups . If our Sites allow posting of content, we collect Personal Data that you provide in connection with the post. b. Use of Personal Data. Besides the use of Personal Data described above, we use Personal Data in the ways listed below: Analyzing, Improving, and Developing our Services . We collect and process Personal Data throughout our various Services, whether you are an End User, End Customer, Representative, or Visitor, to improve our Services, develop new Services, and support our efforts to make our Services more efficient, relevant, and useful to you. Learn More . We may use Personal Data to generate aggregate and statistical information to understand and explain how our Services are used. Examples of how we use Personal Data to analyze, improve, and develop our products and services include: Using analytics on our Sites, including as described in our Cookie Policy, to help us understand your use of our Sites and Services and diagnose technical issues. Training artificial intelligence models to power our Services and protect against fraud and other harm. Learn more . Analyzing and drawing inferences from Transaction Data to reduce costs, fraud, and disputes and increase authentication and authorization rates for Stripe and our Business Users. Communications . We use the contact information we have about you to deliver our Services, Learn More , which may involve sending codes via SMS for your authentication. Learn More . If you are an End User, Representative, or Visitor, we may communicate with you using the contact information we have about you to provide information about our Services and our affiliates’ services, invite you to participate in our events, surveys, or user research, or otherwise communicate with you for marketing purposes, in compliance with applicable law, including any consent or opt-out requirements. For example, when you provide your contact information to us or when we collect your business contact details through participation at trade shows or other events, we may use this data to follow up with you regarding an event, provide information requested about our Services, and include you in our marketing information campaigns. Where permitted under applicable law, we may record our calls with you to provide our Services, comply with our legal obligations, perform research and quality assurance, and for training purposes. Social Media and Promotions . If you opt to submit Personal Data to engage in an offer, program, or promotion, we use the Personal Data you provide to manage the offer, program, or promotion. We also use the Personal Data you provide, along with the Personal Data you make available on social media platforms, for marketing purposes, unless we are not permitted to do so. Fraud Prevention and Security . We collect and use Personal Data to help us identify and manage activities that could be fraudulent or harmful across our Services, enable our fraud detection Business Services, and secure our Services and transactions against unauthorized access, use, alteration or misappropriation of Personal Data, information, and funds. As part of the fraud prevention, detection, security monitoring, and compliance efforts for Stripe and its Business Users, we collect information from publicly available sources, third parties (such as credit bureaus), and via the Services we offer. In some instances, we may also collect information about you directly from you, or from our Business Users, Financial Partners, and other third parties for the same purposes. Furthermore, to protect our Services, we may receive details such as IP addresses and other identifying data about potential security threats from third parties. Learn More . Such information helps us verify identities, conduct credit checks where lawfully permitted, and prevent fraud. Additionally, we might use technology to evaluate the potential risk of fraud associated with individuals seeking to procure our Business Services or arising from attempted transactions by an End Customer or End User with our Business Users or Financial Partners. Compliance with Legal Obligations . We use Personal Data to meet our contractual and legal obligations related to anti-money laundering, Know-Your-Customer ("KYC") laws, anti-terrorism activities, safeguarding vulnerable customers, export control, and prohibition of doing business with restricted persons or in certain business fields, among other legal obligations. For example, we may monitor transaction patterns and other online signals and use those insights to identify fraud, money laundering, and other harmful activity that could affect Stripe, our Financial Partners, End Users, Business Users and others. Learn More . Safety, security, and compliance for our Services are key priorities for us, and collecting and using Personal Data is crucial to this effort. Minors . Our Services are not directed to children under the age of 13, and we request that they do not provide Personal Data to seek Services directly from Stripe. In certain jurisdictions, we may impose higher age limits as required by applicable law. c. Sharing of Personal Data. Besides the sharing of Personal Data described above, we share Personal Data in the ways listed below: Stripe Affiliates . We share Personal Data with other Stripe-affiliated entities for purposes identified in this Policy. Service Providers or Processors . In order to provide, communicate, market, analyze, and advertise our Services, we depend on service providers. These providers offer critical services such as providing cloud infrastructure, conducting analytics for the assessment of the speed, accuracy, and/or security of our Services, verifying identities, identifying potentially harmful activity, and providing customer service and audit functions. We authorize these service providers to use or disclose the Personal Data we make available to them to perform services on our behalf and to comply with relevant legal obligations. We require these service providers to contractually commit to security and confidentiality obligations for the Personal Data they process on our behalf. The majority of our service providers are based in the European Union, the United States of America, and India. Learn More . Financial Partners . We share Personal Data with certain Financial Partners to provide Services to Business Users and offer certain Services in conjunction with these Financial Partners. For instance, we may share certain Personal Data, such as payment processing volume, loan repayment data, and Representative contact information, with institutional investors and lenders who purchase loan receivables or provide financing related to Stripe Capital. Learn More . Others with Consent . In some situations, we may not offer a service, but instead refer you to others (like professional service firms that we partner with to deliver the Atlas Service). In these instances, we will disclose the identity of the third party and the information to be shared with them, and seek your consent to share the information. Corporate Transactions . If we enter or intend to enter a transaction that modifies the structure of our business, such as a reorganization, merger, sale, joint venture, assignment, transfer, change of control, or other disposition of all or part of our business, assets, or stock, we may share Personal Data with third parties in connection with such transaction. Any other entity that buys us or part of our business will have the right to continue to use your Personal Data, subject to the terms of this Policy. Compliance and Harm Prevention . We share Personal Data when we believe it is necessary to comply with applicable law; to abide by rules imposed by Financial Partners in connection with the use of their payment method; to enforce our contractual rights; to secure and protect the Services, rights, privacy, safety, and property of Stripe, you, and others, including against malicious or fraudulent activity; and to respond to valid legal requests from courts, law enforcement agencies, regulatory agencies, and other public and government authorities, which may include authorities outside your country of residence. 3. Legal bases for processing Personal Data For purposes of the General Data Protection Regulation (GDPR) and other applicable data protection laws, we rely on a number of legal bases to process your Personal Data. Learn More . For some jurisdictions, there may be additional legal bases, which are outlined in the Jurisdiction-Specific Provisions section below. a. Contractual and Pre-Contractual Business Relationships . We process Personal Data to enter into business relationships with prospective Business Users and End Users and fulfill our respective contractual obligations with them. These processing activities include: Creation and management of Stripe accounts and Stripe account credentials, including the assessment of applications to initiate or expand the use of our Services; Creation and management of Stripe Checkout accounts; Accounting, auditing, and billing activities; and Processing of payments and related activities, which include fraud detection, loss prevention, transaction optimization, communications about such payments, and related customer service activities. b. Legal Compliance . We process Personal Data to verify the identities of individuals and entities to comply with obligations related to fraud monitoring, prevention, and detection, laws associated with identifying and reporting illicit and illegal activities, such as those under the Anti-Money Laundering ("AML") and Know-Your-Customer (“KYC") regulations, and financial reporting obligations. For example, we may be required to record and verify a Business User’s identity to comply with regulations designed to prevent money laundering, fraud, and financial crimes. These legal obligations may require us to report our compliance to third parties and subject ourselves to third party verification audits. c. Legitimate Interests . Where permitted under applicable law, we rely on our legitimate business interests to process your Personal Data. The following list provides an example of the business purposes for which we have a legitimate interest in processing your data: Detection, monitoring, and prevention of fraud and unauthorized payment transactions; Mitigation of financial loss, claims, liabilities or other harm to End Customers, End Users, Business Users, Financial Partners, and Stripe; Determination of eligibility for and offering new Stripe Services ( Learn More ); Response to inquiries, delivery of Service notices, and provision of customer support; Promotion, analysis, modification, and improvement of our Services, systems, and tools, as well as the development of new products and services, including enhancing the reliability of the Services; Management, operation, and improvement of the performance of our Sites and Services, through understanding their effectiveness and optimizing our digital assets; Analysis and advertisement of our Services, and related improvements; Aggregate analysis and development of business intelligence that enable us to operate, protect, make informed decisions about, and report on the performance of our business; Sharing of Personal Data with third party service providers that offer services on our behalf and business partners that help us in operating and improving our business ( Learn More) ; Enabling network and information security throughout Stripe and our Services; and Sharing of Personal Data among our affiliates. d. Consent . We may rely on consent or explicit consent to collect and process Personal Data regarding our interactions with you and the provision of our Services such as Link, Financial Connections, Atlas, and Identity. When we process your Personal Data based on your consent, you have the right to withdraw your consent at any time, and such a withdrawal will not impact the legality of processing performed based on the consent prior to its withdrawal. e. Substantial Public Interest . We may process special categories of Personal Data, as defined by the GDPR, when such processing is necessary for reasons of substantial public interest and consistent with applicable law, such as when we conduct politically-exposed person checks. We may also process Personal Data related to criminal convictions and offenses when such processing is authorized by applicable law, such as when we conduct sanctions screening to comply with AML and KYC obligations. f. Other valid legal bases . We may process Personal Data further to other valid legal bases as recognized under applicable law in specific jurisdictions. See the Jurisdiction-specific provisions section below for more information. 4. Your rights and choices Depending on your location and subject to applicable law, you may have choices regarding our collection, use, and disclosure of your Personal Data: a. Opting out of receiving electronic communications from us If you wish to stop receiving marketing-related emails from us, you can opt-out by clicking the unsubscribe link included in such emails or as described here . We'll try to process your request(s) as quickly as reasonably practicable. However, it's important to note that even if you opt out of receiving marketing-related emails from us, we retain the right to communicate with you about the Services you receive (like support and important legal notices) and our Business Users might still send you messages or instruct us to send you messages on their behalf. b. Your data protection rights Depending on your location and subject to applicable law, you may have the following rights regarding the Personal Data we process about you as a data controller: The right to request confirmation of whether Stripe is processing Personal Data associated with you, the categories of personal data it has processed, and the third parties or categories of third parties with which your Personal Data is shared; The right to request access to the Personal Data Stripe processes about you ( Learn More ); The right to request that Stripe rectify or update your Personal Data if it's inaccurate, incomplete, or outdated; The right to request that Stripe erase your Personal Data in certain circumstances as provided by law ( Learn More ); The right to request that Stripe restrict the use of your Personal Data in certain circumstances, such as while Stripe is considering another request you've submitted (for instance, a request that Stripe update your Personal Data); The right to request that we export the Personal Data we hold about you to another company, provided it's technically feasible; The right to withdraw your consent if your Personal Data is being processed based on your previous consent; The right to object to the processing of your Personal Data if we are processing your data based on our legitimate interests; unless there are compelling legitimate grounds or the processing is necessary for legal reasons, we will cease processing your Personal Data upon receiving your objection ( Learn More ); The right not to be discriminated against for exercising these rights; and The right to appeal any decision by Stripe relating to your rights by contacting Stripe’s Data Protection Officer (“DPO”) at dpo@stripe.com , and/or relevant regulatory agencies. You may have additional rights, depending on applicable law, over your Personal Data. For example, see the Jurisdiction-specific provisions section under United States below. c. Process for exercising your data protection rights To exercise your data protection rights related to Personal Data we process as a data controller, visit our Privacy Center or contact us as outlined below. For Personal Data we process as a data processor, please reach out to the relevant data controller (Business User) to exercise your rights. If you contact us regarding your Personal Data we process as a data processor, we will refer you to the relevant data controller to the extent we are able to identify them. 5. Security and Retention We make reasonable efforts to provide a level of security appropriate to the risk associated with the processing of your Personal Data. We maintain organizational, technical, and administrative measures designed to protect the Personal Data covered by this Policy from unauthorized access, destruction, loss, alteration, or misuse. Learn More . Unfortunately, no data transmission or storage system can be guaranteed to be 100% secure. We encourage you to assist us in protecting your Personal Data. If you hold a Stripe account, you can do so by using a strong password, safeguarding your password against unauthorized use, and avoiding using identical login credentials you use for other services or accounts for your Stripe account. If you suspect that your interaction with us is no longer secure (for instance, you believe that your Stripe account's security has been compromised), please contact us immediately. We retain your Personal Data for as long as we continue to provide the Services to you or our Business Users, or for a period in which we reasonably foresee continuing to provide the Services. Even after we stop providing Services directly to you or to a Business User that you're doing business with, and even after you close your Stripe account or complete a transaction with a Business User, we may continue to retain your Personal Data to: Comply with our legal and regulatory obligations; Enable fraud monitoring, detection, and prevention activities; and Comply with our tax, accounting, and financial reporting obligations, including when such retention is required by our contractual agreements with our Financial Partners (and where data retention is mandated by the payment methods you've used). In cases where we keep your Personal Data, we do so in accordance with any limitation periods and record retention obligations imposed by applicable law. Learn More . 6. International Data Transfers As a global business, it's sometimes necessary for us to transfer your Personal Data to countries other than your own, including the United States. These countries might have data protection regulations that are different from those in your country. When transferring data across borders, we take measures to comply with applicable data protection laws related to such transfer. In certain situations, we may be required to disclose Personal Data in response to lawful requests from officials, such as law enforcement or security authorities. Learn More . If you are located in the European Economic Area (“EEA”), the United Kingdom ("UK"), or Switzerland, please refer to our Privacy Center for additional details. When a data transfer mechanism is mandated by applicable law, we employ one or more of the following: Transfers to certain countries or recipients that are recognized as having an adequate level of protection for Personal Data under applicable law. EU Standard Contractual Clauses approved by the Europe | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/02/26/variants-of-lora/#comments | Variants of LoRA - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. February 26, 2025 Variants of LoRA Want to train a specialized LLM on your own data? The easiest way to do this is with low rank adaptation (LoRA), but many variants of LoRA exist. Credit: Alexandra Francis There are many variants of LoRA you can use to train a specialized LLM on your own data. Here’s an overview of all (or at least most) of the techniques that are out there. LoRA models the update derived for a model’s weights during finetuning with a low rank decomposition, implemented in practice as a pair of linear projections. LoRA leaves the pretrained layers of the LLM fixed and injects a trainable rank decomposition matrix into each layer of the model. QLoRA is (arguably) the most popular LoRA variant and uses model quantization techniques to reduce memory usage during finetuning while maintaining (roughly) equal levels of performance. QLoRA uses 4-bit quantization on the pretrained model weights and trains LoRA modules on top of this. In practice, QLoRA saves memory at the cost of slightly-reduced training speed. QA-LoRA is an extension of LoRA/QLoRA that further reduces the computational burden of training and deploying LLMs. It does this by combining parameter-efficient finetuning with quantization (i.e., group-wise quantization applied during training/inference). LoftQ studies a similar idea to QA-LoRA—applying quantization and LoRA finetuning on a pretrained model simultaneously. LongLoRA attempts to cheaply adapt LLMs to longer context lengths using a parameter-efficient (LoRA-based) finetuning scheme. In particular, we start with a pretrained model and finetune it to have a longer context length. This finetuning is made efficient by: Using sparse local attention instead of dense global attention (optional at inference time). Using LoRA (authors find that this works well for context extension). S-LoRA aims to solve the problem of deploying multiple LoRA modules that are used to adapt the same pretrained model to a variety of different tasks. Put simply, S-LoRA does the following to serve thousands of LoRA modules on a single GPU (or across GPUs): Stores all LoRA modules in main memory. Puts modules being used to run the current query into GPU memory. Uses unified paging to allocate GPU memory and avoid fragmentation. Proposes a new tensor parallelism strategy to batch LoRA computations. Many other LoRA variants exist as well… LQ-LoRA: uses a more sophisticated quantization scheme within QLoRA that performs better and can be adapted to a target memory budget. MultiLoRA: extension of LoRA that better handles complex multi-task learning scenarios. LoRA-FA: freezes half of the low-rank decomposition matrix (i.e., the A matrix within the product AB) to further reduce memory overhead. Tied-LoRA: leverages weight tying to further improve the parameter efficiency of LoRA. GLoRA: extends LoRA to adapt pretrained model weights and activations to each task in addition to an adapter for each layer. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Cameron R. Wolfe, PhD Director of AI at Rebuy I’m currently the Director of AI at Rebuy, a personalized search and recommendations platform for D2C e-commerce brands. Prior to Rebuy, I was a Research Scientist at Alegion. Additionally, I worked for Salesforce Commerce Cloud … llm AI contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/04/03/from-training-to-inference-the-new-role-of-web-data-in-llms/#comments | From training to inference: The new role of web data in LLMs - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 3, 2025 From training to inference: The new role of web data in LLMs Data has always been key to LLM success, but it's becoming key to inference-time performance as well. Credit: Alexandra Francis Large language models (LLMs) have consumed massive parts of the internet, with the leading models using trillions of tokens during training. Meanwhile, AI startups are carving out niches by focusing on smaller, specialized models, leveraging more specific web data. As the race for the most comprehensive and accurate AI continues, competing giants are investing in three critical areas to maintain an edge: Compute, Talent, and Tokens . Of these, tokens —the data that LLMs use during training and inference— can define success or lead to failure. Web data remains central to the evolution of these systems, offering an unprecedented opportunity to shape and enhance their accuracy and relevance. This targeted use of web data allows LLMs to excel in niche applications, delivering domain-specific accuracy that general training alone cannot achieve. Yet, the role of web data extends far beyond the static datasets used during training and fine-tuning. As the demands placed on LLMs grow more dynamic, the use of web data has too, from its pivotal role in shaping LLMs to the emerging practice of using real-time web data for reasoning. As we move forward, one thing is clear: inference-time data is not just an enhancement; it is the foundation of a smarter, more responsive AI future. Tokens: The (potentially) unfair advantage. In the context of web data and inference-time data, tokens represent the fundamental building blocks of an LLM’s capabilities, but the role of tokens doesn't stop at training. Models using real-time data or inference data during the reasoning process can now fetch and process fresh tokens from live web data to enhance their outputs. The ability to dynamically integrate new information during inference supplements pre-trained and fine-tuned knowledge with the latest, most relevant data, ensuring outputs are accurate, timely, and context-aware. This dual role of web data—providing tokens for training and live tokens for inference—creates opportunities for AI companies to gain a competitive advantage. While compute and talent are essential, they often level out across competitors. Web data, by contrast, is not only harder to replicate but can also vary dramatically in quality. High-quality inference-time data ensures that the tokens integrated during reasoning are precise, relevant, and timely, giving models a tangible edge in real-world applications. Conversely, poor-quality or irrelevant web data can degrade performance, underscoring the critical importance of data curation and infrastructure in both training and inference contexts. Here are some examples of different contexts: Social media data: Tokens from social platforms help models understand informal language, slang, and real-time trends, which are essential for applications like sentiment analysis or chatbots. Structured datasets: Tokens from structured sources like product catalogs or financial reports enable precise, domain-specific understanding, critical for recommendation systems or financial forecasting. Niche contexts: Startups and specialized applications benefit from tokens sourced from hyper-relevant datasets tailored to their use cases, such as legal documents for legal tech or medical journals for healthcare AI. The birth of ‘reasoning’ Reasoning in artificial intelligence, particularly within large language models (LLMs), represents a significant leap in their ability to solve complex problems and adapt to dynamic situations. It goes beyond simple pattern recognition, enabling AI systems to deliberate, synthesize information, and arrive at informed conclusions. Initially, reasoning in LLMs was rooted in increasing computational depth during inference. By deploying greater computational power, models could evaluate multiple possible outcomes, refining their responses through iterative processes. While this approach brought incremental improvements, it exposed inherent limitations in relying solely on static pre-trained knowledge and brute computational force. Models trained on static datasets struggle to respond to dynamic, evolving contexts, leaving gaps in their ability to address real-world problems, which is how the true transformation in reasoning emerged. The integration of dynamic, real-time data into the decision-making process marked a pivotal shift from static reasoning, where models operated exclusively within the boundaries of their training datasets, to adaptive reasoning, which allows them to incorporate new, relevant information during inference. Dynamic reasoning equips models to engage with ever-changing contexts, validating outputs against live data and aligning responses with current realities. This opens doors to unprecedented adaptability, enabling AI systems to address problems and scenarios that extend far beyond their original training. Web data for reasoning Dynamic reasoning reflects the trajectory of AI systems toward greater contextual intelligence, but it cannot be done without web data. For example, an LLM tasked with analyzing current geopolitical events can enhance its output by integrating up-to-the-minute news data, ensuring accuracy and relevance. Similarly, in fields like healthcare or finance, the ability to incorporate recent findings or market trends empowers models to deliver insights that are not only accurate but also timely. This approach reduces reliance on outdated or incomplete information, making AI tools more aligned with real-world needs. Here’s the typical inference workflow: A user (either manually or via an API) enters a prompt into an LLM. This prompt could be anything from a simple query to a complex, multi-layered instruction. The LLM generates a response based on its pre-trained knowledge. Some advanced LLMs incorporate reasoning layers to improve the accuracy of their outputs. These layers may involve more computational effort or running agents to validate and refine the response. Add in real-time web data for additional information not included in training, process it at inference time, and incorporate it into the output. An important consideration is whether incorporating inference-time data affects the weights and biases of the LLM itself. It does not directly alter the model’s underlying structure. Instead, this process functions as an external reasoning layer, giving the model the option to incorporate real-time insights into its responses. This creates an important distinction: AI developers can continuously improve model accuracy without retraining the underlying LLM. The future of LLMs and real-time reasoning The integration of real-time web data into reasoning processes transforms LLMs from static repositories of knowledge into adaptive, dynamic agents capable of navigating change. This is the next phase in LLM development and is set to dominate the industry over the next one to two years. AI companies are looking to develop model capabilities with real-time reasoning that improve accuracy by bridging the gap between static training data and the real world that creates a competitive edge. An ecosystem is already emerging to meet the demands for real-time inference data, as companies look to outsource data collection to APIs. Companies and startups are already capitalizing on this trend, developing inference-time data as a service (ITDaaS) solutions. These solutions provide processed, context-specific data that models can query during inference, enabling them to enhance their reasoning capabilities without retraining their core architectures. The future of reasoning in AI will likely revolve around increasingly sophisticated systems that blend static pre-trained knowledge with dynamic, real-time inputs. For AI developers, the challenge will be to build robust data pipelines that can seamlessly integrate these real-time inputs while maintaining high standards of accuracy and efficiency. As the field matures, companies that invest in high-quality data sourcing, real-time integration infrastructure, and innovative inference-time tools will lead the way. In this, web data is the defining advantage that drives the evolution of AI. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Or Lenchner CEO of Bright Data data science generative AI data contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/01/22/why-all-developers-should-adopt-a-safety-critical-mindset/#comments | Why all developers should adopt a safety-critical mindset - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 22, 2025 Why all developers should adopt a safety-critical mindset Is anyone designing software where failures don't have consequences? Credit: Alexandra Francis In a world where software powers everything from spacecraft to banking systems, the consequences of failure can be devastating. Even minor software failures can have far-reaching consequences—we’ve seen platforms crash, businesses lose millions, and users lose trust, all due to bugs or breakdowns that could have been prevented. Just ask Crowdstrike. This raises an important question: Shouldn’t all developers think about safety, reliability, and trust, even when building apps or services that don’t seem critical? The answer is a resounding yes. Regardless of what type of software you’re building, adopting the principles of safety-critical software can help you create more reliable, trustworthy, and resilient systems. It's not about over-engineering; it's about taking responsibility for what happens when things inevitably go wrong. All software should be considered high-stakes The first principle of safety-critical software is that every failure has consequences. In industries like aerospace, medical devices, or automotive, “criticality” is often narrowly defined as failures risking loss of life or major assets. This definition, while appropriate for these fields, overlooks the broader impacts failures can have in other contexts—lost revenue, eroded user trust, or disruptions to daily operations. Expanding the definition of criticality means recognizing that every system interacts with users, data, or processes in ways that can have cascading effects. Whether the stakes involve safety, financial stability, or user experience, treating all software as potentially high-stakes helps developers build systems that are resilient, reliable, and ready for the unexpected. Adopting a safety-critical mindset means anticipating failures and understanding their ripple effects. By preparing for breakdowns, developers improve communication, design for robustness, and ultimately deliver systems that users can trust to perform under pressure. Designing for inevitable failure Failure isn’t just possible—it’s inevitable. Every system will eventually encounter some condition it wasn’t explicitly designed for and how it responds to that failure defines whether it causes a major issue or is just a bump in the road. For safety-critical systems, this means implementing two-fault tolerance, where multiple failures can occur without losing functionality or data. But you don’t need to go that far for everyday software. Simple failover mechanisms, active-passive system designs, and reducing single points of failure can dramatically increase resilience. One effective approach is active-passive system design, where an active component handles requests while a standby component remains idle until needed. If the active component fails, the passive one takes over, minimizing downtime. In more dynamic systems, proxies and load balancers play a key role in distributing traffic across multiple instances or services, ensuring no single point of failure can bring the entire system down. Load balancing also provides the ability to shift workloads dynamically, allowing systems to respond to surges or outages more effectively.Modern distributed architectures, like containerization and microservices, build on these principles to further enhance resilience. By breaking applications into smaller, independently deployable units, microservices architectures avoid the fragility of monoliths, where a single failure can cascade across the system. Distributed systems also make it easier to isolate and recover from failures, as individual services can be restarted or rerouted without affecting others. Developers can also integrate continuous monitoring and observability to detect problems early. The faster you can detect and diagnose a problem, the faster you can fix it—often before users even notice. Beyond detection, testing for failure is equally critical. Practices like chaos engineering, which involve intentionally introducing faults into a system, help developers identify weak points and ensure systems can recover gracefully under stress. Whether it’s a memory leak, performance degradation, or data inconsistency, these strategies work alongside observability as proactive defenses against failure. Learning from safety-critical practices Safety-critical industries don’t just rely on reactive measures; they also invest heavily in proactive defenses. Defensive programming is a key practice here, emphasizing robust input validation, error handling, and preparation for edge cases. This same mindset can be invaluable in non-critical software development. A simple input error could crash a service if not properly handled—building systems with this in mind ensures you’re always anticipating the unexpected. Rigorous testing should also be a norm, and not just unit tests. While unit testing is valuable, it's important to go beyond that, testing real-world edge cases and boundary conditions. Consider fault injection testing, where specific failures are introduced (e.g., dropped packets, corrupted data, or unavailable resources) to observe how the system reacts. These methods complement stress testing under maximum load and simulations of network outages, offering a clearer picture of system resilience. Validating how your software handles external failures will build more confidence in your code. Graceful degradation is another principle worth adopting. If a system does fail, it should fail in a way that’s safe and understandable. For example, an online payment system might temporarily disable credit card processing but allow users to save items in their cart or check account details. Similarly, a video streaming service might reduce playback quality instead of halting entirely. Users should be able to continue with reduced functionality, rather than experience total shutdowns, ensuring continuity of service and keeping user trust intact. Moreover, techniques like error detection, redundancy, and modular design allow systems to recover from failures more easily. In safety-critical environments, these are a given. In more general software development, these practices still make a difference in reducing risks and ensuring that failures don’t lead to catastrophic outcomes. While adopting safety-critical methods may seem like overkill for non-critical applications, even simplified versions of these principles can lead to more robust and user-friendly software. At its core, adopting a safety-critical mindset is about preparing for the worst while building for the best. Every piece of code matters. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Austin Spiegel Co-founder and CTO of Sift Austin’s early interest in manufacturing and space led him to study Computer Science at USC, where he shifted from game design to building real-world systems. At SpaceX, he contributed to spacecraft development, reusable vehicle data … testing observability failover contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://www.anthropic.com/legal/privacy | Privacy Policy \ Anthropic Skip to main content Skip to footer Research Economic Futures Commitments Learn News Try Claude Privacy Policy Effective January 12, 2026 Previous Version English Anthropic is an AI safety and research company working to build reliable, interpretable, and steerable AI systems. This Privacy Policy explains how we collect, use, disclose, and process your personal data when you use our website and other places where Anthropic acts as a data controller —for example, when you interact with Claude.ai or other products as a consumer for personal use (" Services ") or when Anthropic operates and provides our commercial customers and their end users with access to our commercial products, such as the Claude Team plan (“ Commercial Services ”). This Privacy Policy does not apply where Anthropic acts as a data processor and processes personal data on behalf of commercial customers using Anthropic’s Commercial Services – for example, your employer has provisioned you a Claude for Work account, or you're using an app that is powered on the back-end with Claude. In those cases, the commercial customer is the controller, and you can review their policies for more information about how they handle your personal data. Please see our Non-User Privacy Policy for information on how our large language models are ‘trained’ and how personal data obtained from third party sources, including where others may submit personal data when using our services, may be used when developing or delivering our products and services. This Privacy Policy also describes your privacy rights. More information about your rights, and how to exercise them, is set out in Section 4 (“Rights and Choices”). If you are located in Canada, Brazil, or the Republic of Korea, please read the relevant Regional Supplemental Disclosure which applies to you. If you are located in Washington or a state with similar consumer health data laws, please read our Consumer Health Data Privacy Policy which applies to you if you integrate third party health applications with Claude. 1. Collection of Personal Data We collect the following categories of personal data: Personal data you provide to us directly Identity and Contact Data: Anthropic collects identifiers, including your name, email address, and phone number when you sign up for an Anthropic account, or to receive information on our Services. We may also collect or generate indirect identifiers (e.g., “USER12345”). Payment Information: We shall collect your payment information if you choose to purchase access to Anthropic’s products and services. Inputs and Outputs: You are able to interact with our Services in a variety of formats, including but not limited to chat, coding, and agentic sessions ( “Prompts” or "Inputs" ), which generate responses and actions ( “Outputs” ) based on your Inputs. This includes third-party applications you choose to integrate with our Services. If you include personal data or reference external content in your Inputs, we will collect that information and this information may be reproduced in your Outputs. Feedback on your use of our Services: We appreciate feedback, including ideas and suggestions for improvement or rating an Output in response to an Input (" Feedback "). If you rate an Output in response to an Input—for example, by using the thumbs up/thumbs down icon—we will store the entire related conversation as part of your Feedback. You can learn more about how we use Feedback here . Communication Information: If you communicate with us, including via our chatbot on our Help site, we collect your name, contact information, and the contents of any messages you send. Personal data we receive automatically from your use of the Services When you use the Services, we also receive certain technical data automatically (described below, collectively “ Technical Information ”). This includes: Device and Connection Information. Consistent with your device or browser permissions, your device or browser automatically sends us information about when and how you install, access, or use our Services. This includes information such as your device type, operating system information, browser information and web page referers, mobile network, connection information, mobile operator or internet service provider (ISP), time zone setting, IP address (including information about the location of the device derived from your IP address), identifiers (including device or advertising identifiers, probabilistic identifiers, and other unique personal or online identifiers), and device location. Usage Information. We collect information about your use of the Services, such as the dates and times of access, browsing history, search, information about the links you click, pages you view, and other information about how you use the Services, and technology on the devices you use to access the Services. Log and Troubleshooting Information. We collect information about how our Services are performing when you use them. This information includes log files. If you or your device experiences an error, we may collect information about the error, the time the error occurred, the feature being used, the state of the application when the error occurred, and any communications or content provided at the time the error occurred. Cookies & Similar Technologies. We and our service providers use cookies, scripts, or similar technologies (“ Cookies ”) to manage the Services and to collect information about you and your use of the Services. These technologies help us to recognize you, customize or personalize your experience, market additional products or services to you, and analyze the use of our Services to make them safer and more useful to you. For more details about how we use these technologies, and your opt-out controls and other options, please visit our Cookie Policy . Personal data we collect or receive to train our models Anthropic obtains personal data from third party sources in order to train our models. Specifically, we train our models using data from the following sources: Publicly available information via the Internet Datasets that we obtain through commercial agreements with third party businesses Data that our users or crowd workers provide, including Inputs and Outputs from our Services (unless users opt out) Feedback that users explicitly provide about our Services Materials flagged for safety, security, or policy review Data that we generate internally For more information about how we collect and use personal data to develop our language models that power our Services, the steps we take to minimize the privacy impact on individuals through the training process, and your choices with respect to that information, please see our separate Non-User Privacy Policy . 2. Uses of Personal Data Permitted Under Applicable Data Protection Laws We use your personal data for the following purposes: To provide, maintain and facilitate any products and services offered to you with respect to your Anthropic account, which are governed by our Terms of Service; To provide, maintain and facilitate optional services and features that enhance platform functionality and user experience; To communicate with you, including to send you information about our Services and events; To create and administer your Anthropic account; To facilitate payments for products and services provided by Anthropic; To prevent and investigate fraud, abuse, and violations of our Usage Policy , unlawful or criminal activity, unauthorized access to or use of personal data or Anthropic systems and networks, to protect our rights and the rights of others, and to meet legal, governmental and institutional policy obligations; To investigate and resolve disputes; To investigate and resolve security issues; To debug and to identify and repair errors that impair existing functionality To improve the Services and conduct research, including training our models; and To enforce our Terms of Service and similar terms and agreements, including our Usage Policy . We may use your Inputs and Outputs to train our models and improve our Services, unless you opt out through your account settings. Even if you opt-out, we will use Inputs and Outputs for model improvement when: (1) your conversations are flagged for safety review to improve our ability to detect harmful content, enforce our policies, or advance AI safety research, or (2) you've explicitly reported the materials to us (for example via our feedback mechanisms). Please see Section 10 below for details of our legal bases for processing your personal data. 3. How We Disclose Personal Data Anthropic will disclose personal data to the following categories of third parties for the purposes explained in this Policy: Affiliates & corporate partners. Anthropic discloses the categories of personal data described above between and among its affiliates and related entities. Service providers & business partners. Anthropic may disclose the categories of personal data described above with service providers and business partners for a variety of business purposes, including website and data hosting, ensuring compliance with industry standards, research, auditing, data processing, and providing you with the services. Anthropic may also disclose personal data in the following circumstances: As part of a significant corporate event. If Anthropic is involved in a merger, corporate transaction, bankruptcy, or other situation involving the transfer of business assets, Anthropic will disclose your personal data as part of these corporate transactions. Third-Party Websites and Services: Our Services may involve integrations with, or may direct you to, websites, apps, and services managed by third parties. By interacting with these third parties, you are providing information directly to the third party and not Anthropic and subject to the third party’s privacy policy.If you access third-party services, such as social media sites or other sites linked through the Services (e.g., if you follow a link to our Twitter account), these third-party services will be able to collect personal data about you, including information about your activity on the Services. If we link to a site or service via our Services, you should read their data usage policies or other documentation. Our linking to another site or service doesn’t mean we endorse it or speak for that third party. Pursuant to regulatory or legal requirements, safety, rights of others, and to enforce our rights or our terms. We may disclose personal data to governmental regulatory authorities as required by law, including for legal, tax or accounting purposes, in response to their requests for such information or to assist in investigations. We may also disclose personal data to third parties in connection with claims, disputes or litigation, when otherwise permitted or required by law, or if we determine its disclosure is necessary to protect the health and safety of you or any other person, to protect against fraud or credit risk, to enforce our legal rights or the legal rights of others, to enforce contractual commitments that you have made, or as otherwise permitted or required by applicable law. With an individual's consent. Anthropic will otherwise disclose personal data when an individual gives us permission or directs us to disclose this information, including as a part of our Services. You can find information on our Subprocessor List about the third parties Anthropic engages to help us process personal data provided to us where Anthropic acts as a data processor, such as with respect to personal data we receive, process, store, or host when you use Anthropic's commercial services. 4. Rights and Choices Depending on where you live and the laws that apply in your country of residence, you may enjoy certain rights regarding your personal data, as described further below. However, please be aware that these rights are limited, and that the process by which we may need to action your requests regarding our training dataset are complex. We may also decline a request if we have a lawful reason for doing so. That said, we strive to prioritize the protection of personal data, and comply with all applicable privacy laws. To exercise your rights, you or an authorized agent may submit a request by emailing us at privacy@anthropic.com . After we receive your request, we may verify it by requesting information sufficient to confirm your identity. You may also have the right to appeal requests that we deny by emailing privacy@anthropic.com . Anthropic will not discriminate based on the exercising of privacy rights you may have. Set out below is a summary of the rights which you may enjoy, depending on the laws that apply in your country of residence. Right to know: the right to know what personal data Anthropic processes about you, including the categories of personal data, the categories of sources from which it is collected, the business or commercial purposes for collection, and the categories of third parties to whom we disclose it. Access & data portability: the right to request a copy of the personal data Anthropic processes about you, subject to certain exceptions and conditions. In certain cases and subject to applicable law, you have the right to port your information. Deletion: the right to request that we delete personal data collected from you when you use our Services, subject to certain exceptions. You also are able to delete individual conversations , which will be removed immediately from your conversation history and automatically deleted from our back-end within 30 days. Learn more here . Correction: the right to request that we correct inaccurate personal data Anthropic retains about you, subject to certain exceptions. Please note that we cannot guarantee the factual accuracy of Outputs. If Outputs contain factually inaccurate personal data relating to you, you can submit a correction request and we will make a reasonable effort to correct this information—but due to the technical complexity of our large language models, it may not always be possible for us to do so. Objection: the right to object to processing of your personal data, including profiling conducted on grounds of public or legitimate interest. In places where such a right applies, we will no longer process the personal data in case of such objection unless we demonstrate compelling legitimate grounds for the processing which override your interests, rights, and freedoms, or for the establishment, exercise or defense of legal claims. If we use your information for direct marketing, you can object and opt out of future direct marketing messages using the unsubscribe link in such communications. Restriction: the right to restrict our processing of your personal data in certain circumstances. Withdrawal of consent. Where Anthropic’s processing of your personal data is based on consent, you have the right to withdraw your consent. The withdrawal of consent will not affect the lawfulness of processing based on consent before its withdrawal. Automated decision-making : Anthropic does not engage in decision making based solely on automated processing or profiling in a manner which produces a legal effect (i.e., impacts your legal rights) or significantly affects you in a similar way (e.g., significantly affects your financial circumstances or ability to access essential goods or services). Sale & targeted Anthropic marketing of its products and services . Anthropic does not “sell” your personal data as that term is defined by applicable laws and regulations. You can opt-out of sharing your personal data for targeted advertising to promote our products and services, and we will honor global privacy controls. To learn more, click here . Anthropic gives you access to a variety of tools to help you manage your data. You can access these in your Privacy Settings . 5. Data Transfers When you access our website or Services, your personal data may be transferred to our servers in the US, or to other countries outside the European Economic Area ( “EEA” ) and the UK. This may be a direct provision of your personal data to us, or a transfer that we or a third party make. Where information is transferred outside the EEA or the UK, we ensure it benefits from an adequate level of data protection by relying on: Adequacy decisions. These are decisions from the European Commission under Article 45 GDPR (or equivalent decisions under other laws) where they recognise that a country outside of the EEA offers an adequate level of data protection. We transfer your information as described in “Collection of Personal Data” to some countries with adequacy decisions, such as the countries listed here ; or Standard contractual clauses. The European Commission has approved contractual clauses under Article 46 GDPR that allows companies in the EEA to transfer data outside the EEA. These (and their approved equivalent for the UK and Switzerland) are called standard contractual clauses. We rely on standard contractual clauses to transfer information as described in “Collection of Personal Data” to certain affiliates and third parties in countries without an adequacy decision. In certain situations, we rely on derogations provided for under applicable data protection law to transfer information to a third country. 6. Data Retention, Data Lifecycle, and Security Controls Anthropic retains your personal data for as long as reasonably necessary for the purposes and criteria outlined in this Privacy Policy and explained further in our privacy center . When the personal data collected is no longer required by us, we and our service providers will perform the necessary procedures for destroying, deleting, erasing, or converting it into an anonymous form as permitted or required under applicable laws. Aggregated or De-Identified Information We may process personal data in an aggregated or de-identified form to analyze the effectiveness of our Services, conduct research, study user behavior, and train our AI models as permitted under applicable laws. For instance: When you submit Feedback, we disassociate Inputs and Outputs from your user ID to use them for training and improving our models. If our systems flag Inputs or Outputs for potentially violating our Usage Policy , we disassociate the content from your user ID to train our trust and safety internal classification and generative models. However, we may re-identify the Inputs or Outputs to enforce our Usage Policy with the responsible user if necessary. To improve user experience, we may analyze and aggregate general user behavior and usage data. This information does not identify individual users. Security Controls Relating to our Processing of Personal Data We implement appropriate technical and organizational security measures designed to protect personal data from loss, misuse, and unauthorized access, disclosure, alteration, or destruction. 7. Children Our Services are not directed towards, and we do not knowingly collect, use, disclose, sell, or share any information from children under the age of 18. If you become aware that a child under the age of 18 has provided any personal data to us while using our Services, please email us at privacy@anthropic.com and we will investigate the matter and, if appropriate, delete the personal data. 8. Changes to Our Privacy Policy Anthropic may update this Privacy Policy from time to time. We will notify you of any material changes to this Privacy Policy, as appropriate, and update the Effective Date at the top of https://www.anthropic.com/legal/privacy . You can view a summary of privacy policy changes and previous versions in our Privacy Center . 9. Contact Information If you live in the European Economic Area (EEA), UK or Switzerland (the “European Region”), the data controller responsible for your personal data is Anthropic Ireland, Limited. If you live outside the European Region, the data controller responsible for your personal data is Anthropic PBC. If you have any questions about this Privacy Policy, or have any questions, complaints or requests regarding your personal data, you can contact us as described below: Anthropic PBC with a registered address at 548 Market St, PMB 90375, San Francisco, CA 94104 (United States). Anthropic Ireland, Limited with a registered address at 6th Floor, South Bank House, Barrow Street. Dublin 4, D04 TR29 (Ireland). You can email us at privacy@anthropic.com and contact our Data Protection Officer at dpo@anthropic.com . Please note that under many countries' laws, you have the right to lodge a complaint with the supervisory authority in the place in which you live or work. A full list of EU supervisory authorities’ contact details is available here . If you live or work in the UK, you have the right to lodge a complaint with the UK Information Commissioner’s Office . If you live in Brazil, you have the right to lodge a complaint with the Brazilian Data Protection Authority (ANPD) .If you live in Australia, you have the right to lodge a complaint with the Office of the Australian Information Commissioner . 10. Legal Bases for Processing Purpose Type of Data Legal Basis To provide, maintain and facilitate any products and services offered to you with respect to your Anthropic account, which are governed by our Terms of Service Identity and Contact Data Payment Information Feedback Inputs and Outputs Technical Information Contract To provide, maintain and facilitate optional services and features that enhance platform functionality and user experience Identity and Contact Data Feedback Inputs and Outputs Technical Information Consent (for example for precise device location or for health app integrations) Legitimate interests It is in our and our users' legitimate interests to expand our product features and deliver additional services that enhance platform functionality and user experience. To communicate with you and to promote our Services Identity and Contact Data Communication Information Technical Information Where necessary to perform a contract with you, such as processing your contact information to send you a technical announcement about the Services. Your consent when we ask for it to process your personal data for a specific purpose that we communicate to you, such as processing your contact information to send you certain forms of marketing communications. Legitimate Interests It is in our legitimate interests to promote our Services and to send direct marketing. To create and administer your Anthropic account Identity and Contact Data Payment Information Feedback Contract To facilitate payments for products and services provided by Anthropic Identity and Contact Data Payment Information Contract To prevent and investigate fraud, abuse, and violations of our Usage Policy , unlawful or criminal activity, unauthorized access to or use of personal data or Anthropic systems and networks, to protect our rights and the rights of others, and to meet legal, governmental and institutional policy obligations Identity and Contact Data Payment Information Inputs and Outputs Technical Information Legitimate interests Legal obligation It is in our legitimate interests to protect our business, employees and users from illegal activities, inappropriate behavior or violations of terms that would be detrimental. We also have a duty to cooperate with authorities. To investigate and resolve disputes Identity and Contact Data Inputs and Outputs Feedback Legitimate interests Legal obligation It is in our legitimate interests to fully understand and make reasonable efforts to resolve customer complaints in order to improve user satisfaction. We also have a legal obligation in some cases. To investigate and resolve security issues Identity and Contact Data Feedback Technical Information Inputs and Outputs Legal obligation Legitimate interests It is in our legitimate interests to protect user data and our systems from intrusion or compromise through monitoring and swift response. We also have a legal obligation to provide adequate security safeguards. To debug and to identify and repair errors that impair existing functionality Identity and Contact Data Feedback Technical Information Legitimate interests It is in our legitimate interests to maintain continuous functioning of our services and rapid correction of problems to ensure a positive user experience that encourages engagement. To improve the Services and conduct research (excluding model training) Identity and Contact Data Feedback Technical Information Inputs and Outputs Legitimate interests It is in our legitimate interests and in the interest of Anthropic users to evaluate the use of the Services and adoption of new features to inform the development of future features and improve direction and development of the Services. Our research also benefits the AI industry and society: it investigates the safety, inner workings, and societal impact of AI models so that artificial intelligence has a positive impact on society as it becomes increasingly advanced and capable. To improve the Services and conduct research (including model training). See our Non-User Privacy Policy for more details on the data used to train our models. Feedback Inputs and Outputs Data provided through the Development Partner Program Consent (when users submit Feedback) Legitimate interests It is in our legitimate interests and in the interest of Anthropic users to evaluate the use of the Services and adoption of new features to inform the development of future features and improve direction and development of the Services. Our research also benefits the AI industry and society: it investigates the safety, inner workings, and societal impact of AI models so that artificial intelligence has a positive impact on society as it becomes increasingly advanced and capable. To enforce our Terms of Service and similar terms and agreements, including our Usage Policy . Identity and Contact Data Inputs and Outputs Technical Information Contract Legitimate interests In certain circumstances outside of the performance of our contract with you, we may rely on legitimate interests. It is in our legitimate interests to enforce the rules and policies governing use of our services, to maintain intended functionality and value for users. We aim to provide a safe, useful platform. Use of personal data 11. Regional Supplemental Disclosures Supplemental Disclosures for Residents of Canada These supplemental disclosures contain additional information relevant to residents of Canada. This content should be read in conjunction with the rest of our Privacy Policy. In case of conflict between our Privacy Policy and these supplemental disclosures, the supplemental disclosures shall prevail in relation to residents of Canada. Consent. By expressly consenting to this Privacy Policy, you confirm you have read, understand, and consent to the collection, use, processing, and disclosure of your personal data in accordance with this Privacy Policy and understand that, in jurisdictions where it is available, Anthropic also relies on other lawful bases for the foregoing as more fully set out in this policy. We will only collect, use and disclose your personal data with your consent, unless otherwise permitted or required by law. Your consent may be given expressly or implied, depending on the circumstances and the sensitivity of the information involved. You may withdraw consent at any time, subject to legal or contractual restrictions and reasonable notice. Cross-jurisdictional Transfers. By providing us with personal data, you acknowledge and agree that your personal data may be transferred or disclosed to other jurisdictions for processing and storage outside of Canada, including to the United States and the countries listed on our Subprocessor List , where laws regarding the protection of personal data may be less stringent than the laws in your jurisdiction. Furthermore, we may disclose your personal data in these jurisdictions in response to legal processes or where we believe in good faith that disclosure is required or permitted by law. Contact. If you have any questions or comments about our processing of your personal data, or to exercise your rights as outlined in Section 4. (“Rights and Choices”), please contact us at privacy@anthropic.com. Supplemental Disclosures for Residents of Brazil These supplemental disclosures contain additional information relevant to residents of Brazil. This content should be read in conjunction with the rest of our Privacy Policy. In case of conflict between our Privacy Policy and these supplemental disclosures, the supplemental disclosures shall prevail in relation to residents of Brazil. Legal Bases. Depending on the specific purpose of the processing, we may rely on different grounds than those listed under section 2, where permitted by and in accordance with the Brazilian General Data Protection Law (LGPD). For example, we may rely on the "exercise of legal rights" basis to process personal data associated with customer complaints and to enforce our Terms of Service and similar terms and agreements, including our Usage Policy. Data Subject's Rights. LGPD grants certain rights regarding your personal data, which differ from the ones listed under section 4. We will respond to your requests to exercise your rights below in accordance with applicable law: Confirmation of whether your data is being processed. You have the right to receive a confirmation on whether Anthropic processes your data.Access to your data. You have the right to know what personal data Anthropic processes about you. Correction of incomplete, inaccurate or outdated data. You have the right to request the correction of your data that is incomplete, inaccurate, or outdated. Anonymization, blocking or erasure of data. You have the right to request the anonymisation, blocking or erasure of data that is unnecessary, excessive or processed in non-compliance with the provisions of the law. Portability of personal data to a third party. You have the right to request portability of your data to a third-party, as long as this does not infringe on our trade secrets. Information of public and private entities with which we shared data. You have the right to request information of public and private entities with which we have shared your data. Information about the possibility to refuse to provide consent and the respective consequences, when applicable. Withdrawal of your consent. You have the right to withdraw your consent. This procedure will be carried out free of charge. Request a review of decisions made solely based on automated processing of personal data. Please keep in mind that these rights are not absolute and may not apply in certain circumstances. For example, in certain cases we may continue to process and retain data regardless of your request for deletion, objection, blocking or anonymisation, in order to comply with legal, contractual and regulatory obligations, safeguard and exercise rights, including in judicial, administrative and arbitration proceedings and in other cases provided for by law. International Data Transfers. You acknowledge that Anthropic is a company based and headquartered in the United States. Any information we hold about you will be transferred to, used, processed, and stored in the United States and other countries and territories, which may not have data privacy or data protection laws equivalent to those in your country or territory. For the proper operation of the Services, Anthropic needs to carry out international transfers of personal data. In the case of Brazil, we will rely on standard contractual clauses (SCCs) for our data transfers where required and in instances where they are not covered by an adequacy decision. These SCCs have been approved by the Brazilian Data Protection Authority (ANPD), which is the "competent supervisory authority" for these transfers, as governed by Brazilian Data Protection Laws. You can view the SCCs adopted by the ANPD here . Supplemental Disclosures for Residents of the Republic of Korea Domestic Representative in the Republic of Korea The domestic representative of Anthropic PBC for data protection and related regulatory purposes under Article 31-2 of the Personal Information Protection Act and Article 32-5 of the Act on Promotion of Information and Communications Network Utilization and Data Protection, Etc. in the Republic of Korea is as follows: Entity Name and Representative: Anthropic Korea, Limited (Representative Patrick Azubike Ekeruo) Registered Address: (Yeoksam-dong), 41F, 152 Teheran-ro, Gangnam-gu, Seoul, South Korea Telephone: [+82-2-6252-2080] Email: [anthropicprivacy@bkl.co.kr] Data Processors: Trustees and Contacts Bae, Kim & Lee LLC (02-3404-0001) Entrusted Data Name, ID, phone number, email, address, and other information that you may provide to the domestic representative Purpose Assisting with the domestic representative duties Recipient Location South Korea Retention period The period necessary to process your request Times and methods of transfer Telephone, text, or email Products Claude Claude Code Claude in Chrome Claude in Excel Claude in Slack Skills Max plan Team plan Enterprise plan Download app Pricing Log in to Claude Models Opus Sonnet Haiku Solutions AI agents Code modernization Coding Customer support Education Financial services Government Healthcare Life sciences Nonprofits Claude Developer Platform Overview Developer docs Pricing Regional Compliance Amazon Bedrock Google Cloud’s Vertex AI Console login Learn Blog Claude partner network Connectors Courses Customer stories Engineering at Anthropic Events Powered by Claude Service partners Startups program Tutorials Use cases Company Anthropic Careers Economic Futures Research News Responsible Scaling Policy Security and compliance Transparency Help and security Availability Status Support center Terms and policies Privacy policy Consumer health data privacy policy Responsible disclosure policy Terms of service: Commercial Terms of service: Consumer Usage policy © 2025 Anthropic PBC | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#cookies-and-csrf-attack | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://stackoverflow.blog/devops/ | devops - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. devops Related Tags platform engineering the stack overflow podcast Code for a Living Partner Content Bulletin Stackoverflow Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Scott McCarty 10 comment s automation devops AI contributed February 21, 2025 One quality every engineering manager should have? Empathy. And how the platform engineering landscape is evolving. Eira May 0 comment s The Stack Overflow Podcast software development platform engineering managers software engineering devops January 31, 2025 Feature flags: Theory meets reality Ryan is joined by Fynn Glover (CEO) and Ben Papillon (CTO), cofounders of Schematic, for a conversation about managing feature flags in software development. They explore theoretical and practical applications of feature flags, the issue of tech debt, and how orgs could manage entitlements and pricing models more effectively. Eira May 2 comment s The Stack Overflow Podcast software development software engineering devops November 7, 2023 He helped create Jira. Now he's searching for meaningful engineering metrics Dylan Etkin, founder and CEO of Sleuth, joins Ryan to talk all things engineering efficiency, DORA metrics, continuous delivery, and how his psychology degree has proven useful in his work as an engineering manager and startup founder. Eira May 0 comment s devops jira Engineering engineering leadership metrics The Stack Overflow Podcast August 8, 2023 Understanding SRE (Ep. 597) Vladyslav Ukis, Head of R&D at Siemens Healthineers and an expert in site reliability engineering (SRE), joins Ben and Ryan to talk about the relationship between SRE and DevOps, balancing SRE principles with organizational structure, and how he thinks GenAI will impact his field. Eira May 2 comment s devops site reliability engineering sre The Stack Overflow Podcast the stack overflow podcast July 26, 2023 Platform engineering is just DevOps with a product mindset DevOps has helped lots of organizations improve their processes, but others have only seen frustration and burnout. Luca Galante 1 comment Code for a Living devops platform engineering July 7, 2023 The Overflow #185: The hardest part of software is requirements DevX in energy sectors, fox talk, and Elixir loops and lists. Eira May , Cassidy Williams 0 comment s developer experience devops newsletter requirements the overflow newsletter June 27, 2023 The cofounder of Chef is cooking up a less painful DevOps (Ep. 584) Chef cofounder Adam Jacob joins the home team to discuss the problems with the current state of cloud infrastructure, what engineers need but aren’t getting, and why he’s focused on creating a new and improved approach to infrastructure automation. Eira May 0 comment s chef devops infrastructure as code infrastructure automation infrastructure management The Stack Overflow Podcast the stack overflow podcast May 5, 2023 Building golden paths for developers (Ep. 567) The home team talks with Luca Galante of Humanitec about how platform engineering is more art than science, how self-service platforms empower developers with “golden paths,” and why he’s excited, not anxious, about AI tools (at least for now). Eira May 0 comment s devops platform engineering The Stack Overflow Podcast the stack overflow podcast May 3, 2023 Don’t panic! A playbook for managing any production incident Knowing how to handle it when things break is more important than preventing things from ever breaking. Ben Matthews 7 comment s Code for a Living devops outages playbook November 30, 2022 Continuous delivery, meet continuous security Dynamic application security testing (DAST) can help catch security flaws in your code. And it can do it automatically in your build process. Tanya Janca 0 comment s Code for a Living continuous deployment continuous integration devops security October 12, 2022 How observability-driven development creates elite performers Most organizations struggle to change their culture or find a formula for success in difficult-to-mature processes. They don't always understand their own systems. Colin Fallwell 0 comment s Code for a Living devops observability observability driven development Partner Content Partner Content partnercontent August 4, 2022 Great engineering cultures are built on social learning communities For a successful Agile and DevOps practice, organizations need to think beyond tooling. Engineering organizations need a strong community of practice culture that supports the collecting and distributing of knowledge, greater cross-organizational collaboration, and breaks down the silos that can happen in companies of all sizes. Joy Liuzzo 0 comment s agile Code for a Living coding community Culture devops hype May 16, 2022 Stack under attack: what we learned about handling DDoS attacks When the bots came for us, we strengthened our defenses. Here's what we learned about parrying a few DDoS attacks. Josh Zhang 8 comment s Code for a Living DDoS devops Engineering security December 21, 2021 “This should never happen. If it does, call the developers.” If there is one thing developers like less than writing documentation, it's responding to unnecessary escalations. 26 comment s Code for a Living devops documentation sre December 13, 2021 A conversation about how to enable high-velocity DevOps culture at your organization Recently, Stack Overflow’s Chief Product and Technology Officer, Teresa Dietrich, sat down with Justin Stone, Senior Director of Secure DevOps Platforms at Liberty Mutual, for a conversation about building a high-velocity DevOps culture. Eira May 1 comment devops September 8, 2021 Observability is key to the future of software (and your DevOps career) Observability platforms enable you to easily figure out what’s happening with every request and to identify the cause of issues fast. Learning the principles of observability and OpenTelemetry will set you apart from the crowd and provide you with a skill set that will be in increasing demand as more companies perform cloud migrations. Greg Leffler 2 comment s Code for a Living devops observability opentelemetry Partner Content Partner Content partnercontent splunk May 24, 2021 How developers can be their own operations department Many companies run parallel development and operations organizations. But what if you just ran one team that did both? Daniel Orner 11 comment s Code for a Living continuous deployment continuous integration devops March 19, 2021 Podcast 322: Getting Dev and Ops to actually work together How to create a positive feedback loop between your developers and your SRE team. Ben Popper 0 comment s devops The Stack Overflow Podcast the stack overflow podcast June 10, 2020 The rise of the DevOps mindset Medi Madelen Gwosdz 13 comment s Bulletin Bulletin Code for a Living devops Stackoverflow Stackoverflow February 12, 2020 When laziness is efficient: Make the most of your command line DevOps job posts often ask for automation skills, which is a positive way of asking for someone who’s professionally lazy in a way that results in efficiency. The good news is that developers can also learn a few tricks from the land of ops to make their days easier and their work better. Breanne Boland 41 comment s bash Bulletin Bulletin Code for a Living command line devops Stackoverflow Stackoverflow July 26, 2018 The Importance of Getting DevOps Right Rich Moy 2 comment s For Work devops Productivity Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://docs.devcycle.com/cli-mcp/mcp-getting-started/#next-steps | MCP Getting Started | DevCycle Docs Skip to main content Home SDKs APIs Management API Bucketing API Integrations CLI / MCP Best Practices Community Blog Discord Search Sign Up CLI / MCP Overview CLI CLI Reference CLI User Guides Projects Environments SDK Keys Features Variables Variations Targeting Rules Self-Targeting CLI User Guides MCP MCP Getting Started MCP Reference MCP User Guides Incident Investigation MCP On this page DevCyle MCP Getting Started The DevCycle Model Context Protocol (MCP) Server is based on the DevCycle CLI, it enables AI-powered code editors like Cursor and Windsurf, or general-purpose tools like Claude Desktop, to interact directly with your DevCycle projects and make changes on your behalf. Quick Setup The DevCycle MCP is hosted so there is no need to set up a local server. We'll walk you through installation and authentication with your preferred AI tools. Direct Connection: For clients that natively support the MCP specification with OAuth authentication, you can connect directly to our hosted server: https://mcp.devcycle.com/mcp Protocol Support : Our MCP server supports both SSE and HTTP Streaming protocols, automatically negotiating the best option based on your client's capabilities. Alternative Endpoint : If your client has issues with protocol negotiation, use the SSE-only endpoint: https://mcp.devcycle.com/sse MCP Registry : If you're using registry.modelcontextprotocol.io , the DevCycle MCP is listed as: com.devcycle/mcp info These instructions use the remote DevCycle MCP server. For installation of the local MCP server, see the reference docs . Configure Your AI Client Cursor VS Code Claude Code Claude Desktop Windsurf Codex CLI Gemini CLI 📦 Install in Cursor To open Cursor and automatically add the DevCycle MCP, click the install button above. Alternatively, add the following to your ~/.cursor/mcp_settings.json file. To learn more, see the Cursor documentation . { "mcpServers" : { "DevCycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Authentication in Cursor: After configuration, you'll see DevCycle MCP listed as "Needs login" with a yellow indicator Click on the DevCycle MCP server to initiate the authorization process This opens a browser authorization page at mcp.devcycle.com Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com You'll be redirected back to Cursor with the server now active 📦 Install in VS Code To open VS Code and automatically add the DevCycle MCP, click the install button above. Alternatively, add the following to your .continue/config.json file. To learn more, see the Continue documentation . { "mcpServers" : { "DevCycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Authentication in VS Code: After configuration, open the MCP settings panel in VS Code Find the DevCycle MCP server and click "Start Server" VS Code will show a dialog: "The MCP Server Definition 'DevCycle' wants to authenticate to mcp.devcycle.com" Click "Allow" to proceed with authentication This opens a browser authorization page at mcp.devcycle.com Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com You'll be redirected back to VS Code with the server now active Step 1: Open Terminal Open your terminal to access the Claude CLI. Step 2: Add DevCycle MCP Server claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp Step 3: Manage MCP Connection In the Claude CLI, enter the MCP management interface: /mcp Step 4: Authentication You'll see the DevCycle server listed as "disconnected • Enter to login": Select the DevCycle server and press Enter to login Follow the CLI prompts to initiate the Authentication process This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Claude Code where the server will show as connected For more details, see the Claude Code MCP documentation . Step 1: Access MCP Configuration Option 1: Through Claude Desktop Settings (Recommended) Open Claude Desktop and go to Settings Navigate to Developer → Local MCP servers Click "Edit Config" to open the configuration file directly Option 2: Manual Configuration File Alternatively, locate and edit your Claude Desktop configuration file: macOS : ~/Library/Application Support/Claude/claude_desktop_config.json Windows : %APPDATA%\Claude\claude_desktop_config.json Step 2: Add DevCycle Configuration Add or merge the following configuration: { "mcpServers" : { "devcycle" : { "command" : "npx" , "args" : [ " [email protected] " , "https://mcp.devcycle.com/mcp" ] } } } Step 3: Restart Claude Desktop Close and reopen Claude Desktop for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, Claude Desktop will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Claude Desktop where the MCP tools will be active Step 1: Access MCP Configuration Open Windsurf and go to Settings > Winsurf Settings Scroll to the Cascade section Click "Manage MCPs" Step 2: Edit Raw Configuration In the "Manage MCP servers" interface, click "View raw config" Add the following configuration to the JSON file: { "mcpServers" : { "DevCycle" : { "serverUrl" : "https://mcp.devcycle.com/mcp" } } } Step 3: Refresh and Authenticate Save the configuration file Click "Refresh" in the "Manage MCP servers" interface The DevCycle server will appear and prompt for authentication Follow the authentication flow: Browser opens at mcp.devcycle.com for authorization Click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to Windsurf where DevCycle will show as "Enabled" with all tools available which can be configured independently Step 1: Access MCP Configuration Locate and edit your OpenAI Codex CLI configuration file: All platforms : ~/.codex/config.toml Step 2: Add DevCycle MCP Server Add the following TOML configuration to enable the DevCycle MCP server: [mcp_servers.devcycle] url = "https://mcp.devcycle.com/mcp" Step 3: Restart Codex CLI Restart your Codex CLI session for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, the Codex CLI will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to the Codex CLI where the DevCycle MCP tools will be active For more details, see the OpenAI Codex MCP documentation . Step 1: Access MCP Configuration Locate and edit your Gemini CLI settings file: All platforms : ~/.gemini/settings.json Step 2: Add DevCycle MCP Server Add or merge the following configuration to enable the DevCycle MCP server: { "mcpServers" : { "devcycle" : { "url" : "https://mcp.devcycle.com/mcp" } } } Step 3: Restart Gemini CLI Restart your Gemini CLI session for the changes to take effect. Step 4: Authentication When you first use DevCycle MCP tools, the Gemini CLI will prompt for authentication This will open a browser page at mcp.devcycle.com for authorization Review and click "Allow Access" to grant permissions If you have multiple organizations, select your desired organization at auth.devcycle.com Return to the Gemini CLI where the DevCycle MCP tools will be active For more details, see the Gemini CLI MCP documentation . Available Tools The DevCycle MCP Server provides comprehensive feature flag management tools organized into 6 categories : Category Tools Description Feature Management list_features , create_feature , update_feature , update_feature_status , delete_feature , cleanup_feature , get_feature_audit_log_history Create and manage feature flags Variable Management list_variables , create_variable , update_variable , delete_variable Manage feature variables Project Management list_projects , get_current_project , select_project Project selection and details Self-Targeting & Overrides get_self_targeting_identity , update_self_targeting_identity , list_self_targeting_overrides , set_self_targeting_override , clear_feature_self_targeting_overrides Testing and overrides Results & Analytics get_feature_total_evaluations , get_project_total_evaluations Usage analytics SDK Installation install_devcycle_sdk SDK install guides and examples Try It Out Once configured, try asking your AI assistant: "Create a new feature flag called 'new-checkout-flow'" "List all features in my project" "Enable targeting for the header-redesign feature in production" "Show me evaluation analytics for the last 7 days" Next Steps MCP Reference - Complete tool documentation with all parameters CLI Reference - Learn about the underlying CLI commands Getting Help GitHub Issues : GitHub Issues General Documentation : DevCycle Docs DevCycle Community : Discord Support : Contact Support Edit this page Last updated on Jan 9, 2026 Previous CLI User Guides Next MCP Getting Started Quick Setup Configure Your AI Client Available Tools Try It Out Next Steps Getting Help DevCycle Dashboard Blog Privacy Policy Twitter Discord GitHub Copyright © 2026 DevCycle. All rights reserved. | 2026-01-13T08:48:30 |
https://bsky.app/profile/atproto.com | @atproto.com on Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . Profile AT Protocol Developers atproto.com did:plc:ewvi7nxzyoun6zhxrhs64oiz Social networking technology created by Bluesky. Developer-focused account. Follow @bsky.app for general announcements! Bluesky API docs: docs.bsky.app AT Protocol specs: atproto.com | 2026-01-13T08:48:30 |
https://react.dev/ | React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog React The library for web and native user interfaces Learn React API Reference Create user interfaces from components React lets you build user interfaces out of individual pieces called components. Create your own React components like Thumbnail , LikeButton , and Video . Then combine them into entire screens, pages, and apps. Video.js function Video ( { video } ) { return ( < div > < Thumbnail video = { video } /> < a href = { video . url } > < h3 > { video . title } </ h3 > < p > { video . description } </ p > </ a > < LikeButton video = { video } /> </ div > ) ; } My video Video description Whether you work on your own or with thousands of other developers, using React feels the same. It is designed to let you seamlessly combine components written by independent people, teams, and organizations. Write components with code and markup React components are JavaScript functions. Want to show some content conditionally? Use an if statement. Displaying a list? Try array map() . Learning React is learning programming. VideoList.js function VideoList ( { videos , emptyHeading } ) { const count = videos . length ; let heading = emptyHeading ; if ( count > 0 ) { const noun = count > 1 ? 'Videos' : 'Video' ; heading = count + ' ' + noun ; } return ( < section > < h2 > { heading } </ h2 > { videos . map ( video => < Video key = { video . id } video = { video } /> ) } </ section > ) ; } 3 Videos First video Video description Second video Video description Third video Video description This markup syntax is called JSX. It is a JavaScript syntax extension popularized by React. Putting JSX markup close to related rendering logic makes React components easy to create, maintain, and delete. Add interactivity wherever you need it React components receive data and return what should appear on the screen. You can pass them new data in response to an interaction, like when the user types into an input. React will then update the screen to match the new data. SearchableVideoList.js import { useState } from 'react' ; function SearchableVideoList ( { videos } ) { const [ searchText , setSearchText ] = useState ( '' ) ; const foundVideos = filterVideos ( videos , searchText ) ; return ( < > < SearchInput value = { searchText } onChange = { newText => setSearchText ( newText ) } /> < VideoList videos = { foundVideos } emptyHeading = { `No matches for “ ${ searchText } ”` } /> </ > ) ; } example.com / videos.html React Videos A brief history of React Search 5 Videos React: The Documentary The origin story of React Rethinking Best Practices Pete Hunt (2013) Introducing React Native Tom Occhino (2015) Introducing React Hooks Sophie Alpert and Dan Abramov (2018) Introducing Server Components Dan Abramov and Lauren Tan (2020) You don’t have to build your whole page in React. Add React to your existing HTML page, and render interactive React components anywhere on it. Add React to your page Go full-stack with a framework React is a library. It lets you put components together, but it doesn’t prescribe how to do routing and data fetching. To build an entire app with React, we recommend a full-stack React framework like Next.js or React Router . confs/[slug].js import { db } from './database.js' ; import { Suspense } from 'react' ; async function ConferencePage ( { slug } ) { const conf = await db . Confs . find ( { slug } ) ; return ( < ConferenceLayout conf = { conf } > < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > </ ConferenceLayout > ) ; } async function Talks ( { confId } ) { const talks = await db . Talks . findAll ( { confId } ) ; const videos = talks . map ( talk => talk . video ) ; return < SearchableVideoList videos = { videos } /> ; } example.com / confs/react-conf-2021 React Conf 2021 React Conf 2019 Search 19 Videos React Conf React 18 Keynote The React Team React Conf React 18 for App Developers Shruti Kapoor React Conf Streaming Server Rendering with Suspense Shaundai Person React Conf The First React Working Group Aakansha Doshi React Conf React Developer Tooling Brian Vaughn React Conf React without memo Xuan Huang (黄玄) React Conf React Docs Keynote Rachel Nabors React Conf Things I Learnt from the New React Docs Debbie O'Brien React Conf Learning in the Browser Sarah Rainsberger React Conf The ROI of Designing with React Linton Ye React Conf Interactive Playgrounds with React Delba de Oliveira React Conf Re-introducing Relay Robert Balicki React Conf React Native Desktop Eric Rozell and Steven Moyes React Conf On-device Machine Learning for React Native Roman Rädle React Conf React 18 for External Store Libraries Daishi Kato React Conf Building Accessible Components with React 18 Diego Haz React Conf Accessible Japanese Form Components with React Tafu Nakazaki React Conf UI Tools for Artists Lyle Troxell React Conf Hydrogen + React 18 Helen Lin React is also an architecture. Frameworks that implement it let you fetch data in asynchronous components that run on the server or even during the build. Read data from a file or a database, and pass it down to your interactive components. Get started with a framework Use the best from every platform People love web and native apps for different reasons. React lets you build both web apps and native apps using the same skills. It leans upon each platform’s unique strengths to let your interfaces feel just right on every platform. example.com Stay true to the web People expect web app pages to load fast. On the server, React lets you start streaming HTML while you’re still fetching data, progressively filling in the remaining content before any JavaScript code loads. On the client, React can use standard web APIs to keep your UI responsive even in the middle of rendering. 1:08 AM Go truly native People expect native apps to look and feel like their platform. React Native and Expo let you build apps in React for Android, iOS, and more. They look and feel native because their UIs are truly native. It’s not a web view—your React components render real Android and iOS views provided by the platform. With React, you can be a web and a native developer. Your team can ship to many platforms without sacrificing the user experience. Your organization can bridge the platform silos, and form teams that own entire features end-to-end. Build for native platforms Upgrade when the future is ready React approaches changes with care. Every React commit is tested on business-critical surfaces with over a billion users. Over 100,000 React components at Meta help validate every migration strategy. The React team is always researching how to improve React. Some research takes years to pay off. React has a high bar for taking a research idea into production. Only proven approaches become a part of React. Read more React news Latest React News Additional Vulnerabilities in RSC December 11, 2025 Vulnerability in React Server Components December 3, 2025 React Conf 2025 Recap October 16, 2025 React Compiler v1.0 October 7, 2025 Read more React news Join a community of millions You’re not alone. Two million developers from all over the world visit the React docs every month. React is something that people and teams can agree on. This is why React is more than a library, an architecture, or even an ecosystem. React is a community. It’s a place where you can ask for help, find opportunities, and meet new friends. You will meet both developers and designers, beginners and experts, researchers and artists, teachers and students. Our backgrounds may be very different, but React lets us all create user interfaces together. Welcome to the React community Get Started Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms | 2026-01-13T08:48:30 |
https://status.coderabbit.ai/subscribe/discord | Get updates on Discord - CodeRabbit - Status CodeRabbit - Get updates on Discord Report an issue Get updates Email Slack Microsoft Teams Discord Google Chat Webhook RSS Atom API Report an issue Get updates Get status updates Get all status updates Only specific components Get updates on Discord Show current status Powered by Instatus | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2024/12/31/generative-ai-is-not-going-to-build-your-engineering-team-for-you/ | Generative AI is not going to build your engineering team for you - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. December 31, 2024 Generative AI is not going to build your engineering team for you It’s easy to generate code, but not so easy to generate good code. Credit: Alexandra Francis [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2025.] When I was 19 years old, I dropped out of college and moved to San Francisco. I had a job offer in hand to be a Unix sysadmin for Taos Consulting. However, before my first day of work I was lured away to a startup in the city, where I worked as a software engineer on mail subsystems. I never questioned whether or not I could find work. Jobs were plentiful, and more importantly, hiring standards were very low. If you knew how to sling HTML or find your way around a command line, chances were you could find someone to pay you. Was I some kind of genius, born with my hands on a computer keyboard? Assuredly not. I was homeschooled in the backwoods of Idaho. I didn’t touch a computer until I was sixteen and in college. I escaped to university on a classical performance piano scholarship, which I later traded in for a peripatetic series of nontechnical majors: classical Latin and Greek, musical theory, philosophy. Everything I knew about computers I learned on the job, doing sysadmin work for the university and CS departments. In retrospect, I was so lucky to enter the industry when I did. It makes me blanch to think of what would have happened if I had come along a few years later. Every one of the ladders my friends and I took into the industry has long since vanished. The software industry is growing up To some extent, this is just what happens as an industry matures. The early days of any field are something of a Wild West, where the stakes are low, regulation nonexistent, and standards nascent. If you look at the early history of other industries—medicine, cinema, radio—the similarities are striking. There is a magical moment with any young technology where the boundaries between roles are porous and opportunity can be seized by anyone who is motivated, curious, and willing to work their asses off. It never lasts. It can’t; it shouldn’t. The amount of prerequisite knowledge and experience you must have before you can enter the industry swells precipitously. The stakes rise, the magnitude of the mission increases, the cost of mistakes soars. We develop certifications, trainings, standards, legal rites. We wrangle over whether or not software engineers are really engineers . Software is an apprenticeship industry Nowadays, you wouldn’t want a teenaged dropout like me to roll out of junior year and onto your pager rotation. The prerequisite knowledge you need to enter the industry has grown, the pace is faster, and the stakes are much higher, so you can no longer learn literally everything on the job, as I once did. However, it’s not like you can learn everything you need to know at college either. A CS degree typically prepares you better for a life of computing research than life as a workaday software engineer. A more practical path into the industry may be a good coding bootcamp, with its emphasis on problem solving and learning a modern toolkit. In either case, you don’t so much learn “how to do the job” as you do “learn enough of the basics to understand and use the tools you need to use to learn the job.” Software is an apprenticeship industry. You can’t learn to be a software engineer by reading books. You can only learn by doing…and doing, and doing, and doing some more. No matter what your education consists of, most learning happens on the job—period. And it never ends! Learning and teaching are lifelong practices; they have to be, the industry changes so fast. It takes a solid seven-plus years to forge a competent software engineer. (Or as most job ladders would call it, a “senior software engineer”.) That’s many years of writing, reviewing, and deploying code every day, on a team alongside more experienced engineers. That’s just how long it seems to take. What does it mean to be a “senior engineer”? Here is where I often get some very indignant pushback to my timelines, e.g.: “Seven years?! Pfft, it took me two years!” “I was promoted to Senior Software Engineer in less than five years!” Good for you. True, there is nothing magic about seven years. But it takes time and experience to mature into an experienced engineer, the kind who can anchor a team. More than that, it takes practice . I think we have come to use “Senior Software Engineer” as shorthand for engineers who can ship code and be a net positive in terms of productivity, and I think that’s a huge mistake. It implies that less senior engineers must be a net negative in terms of productivity, which is untrue. And it elides the real nature of the work of software engineering, of which writing code is only a small part. To me, being a senior engineer is not primarily a function of your ability to write code. It has far more to do with your ability to understand, maintain, explain, and manage a large body of software in production over time, as well as the ability to translate business needs into technical implementation. So much of the work is around crafting and curating these large, complex sociotechnical systems, and code is just one representation of these systems. What does it mean to be a senior engineer? It means you have learned how to learn , first and foremost, and how to teach; how to hold these models in your head and reason about them, and how to maintain, extend, and operate these systems over time. It means you have good judgment, and instincts you can trust. Which brings us to the matter of AI. We need to stop cannibalizing our own future It is really, really tough to get your first role as an engineer. I didn’t realize how hard it was until I watched my little sister (new grad, terrific grades, some hands on experience, fiendishly hard worker) struggle for nearly two years to land a real job in her field. That was a few years ago; anecdotally, it seems to have gotten even harder since then. This past year, I have read a steady drip of articles about entry-level jobs in various industries being replaced by AI. Some of which absolutely have merit. Any job that consists of drudgery such as converting a document from one format to another, reading and summarizing a bunch of text, or replacing one set of icons with another, seems pretty obviously vulnerable. This doesn’t feel all that revolutionary to me, it’s just extending the existing boom in automation to cover textual material as well as mathy stuff. Recently, however, a number of execs and so-called “thought leaders” in tech seem to have genuinely convinced themselves that generative AI is on the verge of replacing all the work done by junior engineers. I have read so many articles about how junior engineering work is being automated out of existence, or that the need for junior engineers is shriveling up. It has officially driven me bonkers. All of this bespeaks a deep misunderstanding about what engineers actually do . By not hiring and training up junior engineers, we are cannibalizing our own future. We need to stop doing that . Writing code is the easy part People act like writing code is the hard part of software. It is not. It never has been, it never will be. Writing code is the easiest part of software engineering , and it’s getting easier by the day. The hard parts are what you do with that code—operating it, understanding it, extending it, and governing it over its entire lifecycle. A junior engineer begins by learning how to write and debug lines, functions, and snippets of code. As you practice and progress towards being a senior engineer, you learn to compose systems out of software, and guide systems through waves of change and transformation. Sociotechnical systems consist of software, tools, and people; understanding them requires familiarity with the interplay between software, users, production, infrastructure, and continuous changes over time. These systems are fantastically complex and subject to chaos, nondeterminism and emergent behaviors. If anyone claims to understand the system they are developing and operating, the system is either exceptionally small or (more likely) they don’t know enough to know what they don’t know. Code is easy, in other words, but systems are hard . The present wave of generative AI tools has done a lot to help us generate lots of code, very fast. The easy parts are becoming even easier, at a truly remarkable pace. But it has not done a thing to aid in the work of managing, understanding, or operating that code. If anything, it has only made the hard jobs harder. It’s easy to generate code, and hard to generate good code If you read a lot of breathless think pieces, you may have a mental image of software engineers merrily crafting prompts for ChatGPT, or using Copilot to generate reams of code, then committing whatever emerges to GitHub and walking away. That does not resemble our reality. The right way to think about tools like Copilot is more like a really fancy autocomplete or copy-paste function, or maybe like the unholy love child of Stack Overflow search results plus Google’s “I feel lucky”. You roll the dice, every time. These tools are at their best when there’s already a parallel in the file, and you want to just copy-paste the thing with slight modifications. Or when you’re writing tests and you have a giant block of fairly repetitive YAML, and it repeats the pattern while inserting the right column and field names, like an automatic template. However, you cannot trust generated code . I can’t emphasize this enough. AI-generated code always looks quite plausible, but even when it kind of “works”, it’s rarely congruent with your wants and needs. It will happily generate code that doesn’t parse or compile. It will make up variables, method names, function calls; it will hallucinate fields that don’t exist. Generated code will not follow your coding practices or conventions. It is not going to refactor or come up with intelligent abstractions for you. The more important, difficult or meaningful a piece of code is, the less likely you are to generate a usable artifact using AI. You may save time by not having to type the code in from scratch, but you will need to step through the output line by line, revising as you go, before you can commit your code, let alone ship it to production. In many cases this will take as much or more time as it would take to simply write the code—especially these days, now that autocomplete has gotten so clever and sophisticated. It can be a LOT of work to bring AI-generated code into compliance and coherence with the rest of your codebase. It isn’t always worth the effort, quite frankly. Generating code that can compile, execute, and pass a test suite isn’t especially hard; the hard part is crafting a code base that many people, teams, and successive generations of teams can navigate, mutate, and reason about for years to come. How working engineers really use generative AI So that’s the TLDR: you can generate a lot of code, really fast, but you can’t trust what comes out. At all. However, there are some use cases where generative AI consistently shines. For example, it’s often easier to ask chatGPT to generate example code using unfamiliar APIs than by reading the API docs—the corpus was trained on repositories where the APIs are being used for real life workloads, after all. Generative AI is also pretty good at producing code that is annoying or tedious to write, yet tightly scoped and easy to explain. The more predictable a scenario is, the better these tools are at writing the code for you. If what you need is effectively copy-paste with a template—any time you could generate the code you want using sed/awk or vi macros—generative AI is quite good at this. It’s also very good at writing little functions for you to do things in unfamiliar languages or scenarios. If you have a snippet of Python code and you want the same thing in Java, but you don’t know Java, generative AI has got your back. Again, remember, the odds are 50/50 that the result is completely made up. You always have to assume the results are incorrect until you can verify it by hand. But these tools can absolutely accelerate your work in countless ways. Generative AI is a little bit like a junior engineer One of the engineers I work with, Kent Quirk, describes generative AI as “an excitable junior engineer who types really fast”. I love that quote—it leaves an indelible mental image. Generative AI is like a junior engineer in that you can’t roll their code off into production. You are responsible for it—legally, ethically, and practically. You still have to take the time to understand it, test it, instrument it, retrofit it stylistically and thematically to fit the rest of your code base, and ensure your teammates can understand and maintain it as well. The analogy is a decent one, actually, but only if your code is disposable and self-contained, i.e. not meant to be integrated into a larger body of work, or to survive and be read or modified by others. And hey—there are corners of the industry like this, where most of the code is write-only, throwaway code. There are agencies that spin out dozens of disposable apps per year, each written for a particular launch or marketing event and then left to wither on the vine. But that is not most software. Disposable code is rare; code that needs to work over the long term is the norm. Even when we think a piece of code will be disposable, we are often (urf) wrong. But generative AI is not a member of your team In that particular sense—generating code that you know is untrustworthy—GenAI is a bit like a junior engineer. But in every other way, the analogy fails. Because adding a person who writes code to your team is nothing like autogenerating code. That code could have come from anywhere—Stack Overflow, Copilot, whatever. You don’t know, and it doesn’t really matter. There’s no feedback loop, no person on the other end trying iteratively to learn and improve, and no impact to your team vibes or culture. To state the supremely obvious: giving code review feedback to a junior engineer is not like editing generated code. Your effort is worth more when it is invested into someone else’s apprenticeship. It’s an opportunity to pass on the lessons you’ve learned in your own career. Even just the act of framing your feedback to explain and convey your message forces you to think through the problem in a more rigorous way, and has a way of helping you understand the material more deeply. And adding a junior engineer to your team will immediately change team dynamics. It creates an environment where asking questions is normalized and encouraged, where teaching as well as learning is a constant. We’ll talk more about team dynamics in a moment. The time you invest into helping a junior engineer level up can pay off remarkably quickly. Time flies. ☺️ When it comes to hiring, we tend to valorize senior engineers almost as much as we underestimate junior engineers. Neither stereotype is helpful. We underestimate the cost of hiring seniors, and overestimate the cost of hiring juniors People seem to think that once you hire a senior engineer, you can drop them onto a team and they will be immediately productive, while hiring a junior engineer will be a tax on team performance forever. Neither are true. Honestly, most of the work that most teams have to do is not that difficult, once it’s been broken down into its constituent parts. There’s plenty of room for lower level engineers to execute and flourish. The grossly simplified perspective of your accountant goes something like this. “Why should we pay $100k for a junior engineer to slow things down, when we could pay $200k for a senior engineer to speed things up?” It makes no sense! But you know and I know—every engineer who is paying attention should know— that’s not how engineering works . This is an apprenticeship industry, and productivity is defined by the output and carrying capacity of each team, not each person. There are lots of ways a person can contribute to the overall velocity of a team, just like there are lots of ways a person can sap the energy out of a team or add friction and drag to everyone around them. These do not always correlate with the person’s level (at least not in the direction people tend to assume), and writing code is only one way. Furthermore, every engineer you hire requires ramp time and investment before they can contribute. Hiring and training new engineers is a costly endeavor, no matter what level they are. It will take any senior engineer time to build up their mental model of the system, familiarize themselves with the tools and technology, and ramp up to speed. How long? It depends on how clean and organized the codebase is, past experience with your tools and technologies, how good you are at onboarding new engineers, and more, but likely around 6-9 months. They probably won’t reach cruising altitude for about a year. Yes, the ramp will be longer for a junior engineer, and yes, it will require more investment from the team. But it’s not indefinite. Your junior engineer should be a net positive within roughly the same time frame, six months to a year, and they develop far more rapidly than more senior contributors. (Don’t forget, their contributions may vastly exceed the code they personally write.) You do not have to be a senior engineer to add value In terms of writing and shipping features, some of the most productive engineers I’ve ever known have been intermediate engineers. Not yet bogged down with all the meetings and curating and mentoring and advising and architecture, their calendars not yet pockmarked with interruptions, they can just build stuff . You see them put their headphones on first thing in the morning, write code all day, and cruise out the door in the evening having made incredible progress. Intermediate engineers sit in this lovely, temporary state where they have gotten good enough at programming to be very productive, but they are still learning how to build and care for systems. All they do is write code, reams and reams of code. And they’re energized…engaged. They’re having fun! They aren’t bored with writing a web form or a login page for the 1000th time. Everything is new, interesting, and exciting, which typically means they will do a better job , especially under the light direction of someone more experienced. Having intermediate engineers on a team is amazing. The only way you get them is by hiring junior engineers. Having junior and intermediate engineers on a team is a shockingly good inoculation against overengineering and premature complexity. They don’t yet know enough about a problem to imagine all the infinite edge cases that need to be solved for. They help keep things simple, which is one of the hardest things to do. The long term arguments for hiring junior engineers If you ask, nearly everybody will wholeheartedly agree that hiring junior engineers is a good thing…and someone else should do it. This is because the long-term arguments for hiring junior engineers are compelling and fairly well understood. We need more senior engineers as an industry Somebody has to train them Junior engineers are cheaper They may add some much-needed diversity They are often very loyal to companies who invest in training them, and will stick around for years instead of job hopping Did we already mention that somebody needs to do it? But long-term thinking is not a thing that companies, or capitalism in general, are typically great at. Framed this way, it makes it sound like you hire junior engineers as a selfless act of public service, at great cost to yourself. Companies are much more likely to want to externalize costs like those, which is how we got to where we are now. The short term arguments for hiring junior engineers However, there are at least as many arguments to be made for hiring junior engineers in the short term—selfish, hard-nosed, profitable reasons for why it benefits the team and the company to do so. You just have to shift your perspective slightly, from individuals to teams, to bring them into focus. Let’s start here: hiring engineers is not a process of “picking the best person for the job”. Hiring engineers is about composing teams . The smallest unit of software ownership is not the individual, it’s the team. Only teams can own, build, and maintain a corpus of software. It is inherently a collaborative, cooperative activity. If hiring engineers was about picking the “best people”, it would make sense to hire the most senior, experienced individual you can get for the money you have, because we are using “senior” and “experienced” as a proxy for “productivity”. (Questionable, but let’s not nitpick.) But the productivity of each individual is not what we should be optimizing for. The productivity of the team is all that matters. And the best teams are always the ones with a diversity of strengths, perspectives, and levels of expertise. A monoculture can be spectacularly successful in the short term—it may even outperform a diverse team. But they do not scale well, and they do not adapt to unfamiliar challenges gracefully. The longer you wait to diversify, the harder it will be. We need to hire junior engineers, and not just once, but consistently. We need to keep feeding the funnel from the bottom up. Junior engineers only stay junior for a couple years, and intermediate engineers turn into senior engineers. Super-senior engineers are not actually the best people to mentor junior engineers; the most effective mentor is usually someone just one level ahead, who vividly remembers what it was like in your shoes. A healthy, high-performing team has a range of levels A healthy team is an ecosystem. You wouldn’t staff a product engineering team with six DB experts and one mobile developer. Nor should you staff it with six staff+ engineers and one junior developer. A good team is composed of a range of skills and levels. Have you ever been on a team packed exclusively with staff or principal engineers? It is not fun . That is not a high-functioning team. There is only so much high-level architecture and planning work to go around, there are only so many big decisions that need to be made. These engineers spend most of their time doing work that feels boring and repetitive, so they tend to over-engineer solutions and/or cut corners—sometimes at the same time. They compete for the “fun” stuff and find reasons to pick technical fights with each other. They chronically under-document and under-invest in the work that makes systems simple and tractable. Teams that only have intermediate engineers (or beginners, or seniors, or whatever) will have different pathologies, but similar problems with contention and blind spots. The work itself has a wide range in complexity and difficulty—from simple, tightly scoped functions to tough, high-stakes architecture decisions. It makes sense for the people doing the work to occupy a similar range. The best teams are ones where no one is bored, because every single person is working on something that challenges them and pushes their boundaries. The only way you can get this is by having a range of skill levels on the team. The bottleneck we face is hiring, not training The bottleneck we face now is not our ability to train up new junior engineers and give them skills. Nor is it about juniors learning to hustle harder; I see a lot of solid , well-meaning advice on this topic, but it’s not going to solve the problem. The bottleneck is giving them their first jobs . The bottleneck consists of companies who see them as a cost to externalize, not an investment in their—the company’s —future. After their first job, an engineer can usually find work. But getting that first job, from what I can see, is murder . It is all but impossible—if you didn’t graduate from a top college, and you aren’t entering the feeder system of Big Tech, then it’s a roll of the dice, a question of luck or who has the best connections. It was rough before the chimera of “Generative AI can replace junior engineers” rose up from the swamp. And now…oof. Where would you be, if you hadn’t gotten into tech when you did? I know where I would be, and it is not here . The internet loves to make fun of Boomers, the generation that famously coasted to college, home ownership, and retirement, then pulled the ladder up after them while mocking younger people as snowflakes. “Ok, Boomer” may be here to stay, but can we try to keep “Ok, Staff Engineer” from becoming a thing? Nobody thinks we need fewer senior engineers Lots of people seem to think we don’t need junior engineers, but nobody is arguing that we need fewer senior engineers, or will need fewer senior engineers in the foreseeable future. I think it’s safe to assume that anything deterministic and automatable will eventually be automated. Software engineering is no different—we are ground zero! Of course we’re always looking for ways to automate and improve efficiency, as we should be. But large software systems are unpredictable and nondeterministic, with emergent behaviors. The mere existence of users injects chaos into the system. Components can be automated, but complexity can only be managed. Even if systems could be fully automated and managed by AI, the fact that we cannot understand how AI makes decisions is a huge, possibly insurmountable problem. Running your business on a system that humans can’t debug or understand seems like a risk so existential that no security, legal or finance team would ever sign off on it. Maybe some version of this future will come to pass, but it’s hard to see it from here. I would not bet my career or my company on it happening. In the meantime, we still need more senior engineers. The only way to grow them is by fixing the funnel. Should every company hire junior engineers? No. You need to be able to set them up for success. Some factors that disqualify you from hiring junior engineers: You have less than two years of runway Your team is constantly in firefighting mode, or you have no slack in your system You have no experienced managers, or you have bad managers, or no managers at all You have no product roadmap Nobody on your team has any interest in being their mentor or point person The only thing worse than never hiring any junior engineers is hiring them into an awful experience where they can’t learn anything. (I wouldn’t set the bar quite as high as Cindy does in this article ; while I understand where she’s coming from, it is so much easier to land your second job than your first job that I think most junior engineers would frankly choose a crappy first job over none at all.) Being a fully distributed company isn’t a complete dealbreaker, but it does make things even harder. I would counsel junior engineers to seek out office jobs if at all possible. You learn so much faster when you can soak up casual conversations and technical chatter, and you lose that working from home. If you are a remote employer, know that you will need to work harder to compensate for this. I suggest connecting with others who have done this successfully (they exist!) for advice. I also advise companies not to start by hiring a single junior engineer. If you’re going to hire one, hire two or three. Give them a cohort of peers, so it’s a little less intimidating and isolating. Nobody is coming to fix our problems for us I have come to believe that the only way this will ever change is if engineers and engineering managers across our industry take up this fight and make it personal. Most of the places I know that do have a program for hiring and training entry level engineers, have it only because an engineer decided to fight for it. Engineers—sometimes engineering managers—were the ones who made the case and pushed for resources, then designed the program, interviewed and hired the junior engineers, and set them up with mentors. This is not an exotic project, it is well within the capabilities of most motivated, experienced engineers (and good for your career as well). Finance isn’t going to lobby for this. Execs aren’t likely to step in. The more a person’s role inclines them to treat engineers like fungible resources, the less likely they are to understand why this matters. AI is not coming to solve all our problems and write all our code for us—and even if it was , it wouldn’t matter . Writing code is but a sliver of what professional software engineers do, and arguably the easiest part. Only we have the context and the credibility to drive the changes we know form the bedrock for great teams and engineering excellence.. Great teams are how great engineers get made. Nobody knows this better than engineers and EMs. It’s time for us to make the case, and make it happen. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Charity Majors Charity is the cofounder and CTO of honeycomb.io, the leader in observability for complex software systems. She has worked as an ops engineer and engineering manager at Parse, Facebook, Linden Lab, and others, and is … generative AI Engineering coding Business Hub contributed Never miss out! Stay in the loop with fresh business content delivered straight to your inbox. Keep me updated Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://dev.to/help/organizations/creating-and-managing-organizations | Creating and Managing Organizations - DEV Help - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Help The latest help documentation, tips and tricks from the DEV Community. Help > Organizations > Creating and Managing Organizations Creating and Managing Organizations In this article Create An Organization Account Inviting Folks to Your Organization Assigning (& Removing) Organization Admin Responsibilities Create An Organization Account Now that you're logged into your DEV account, it's time to create your organization account! Navigate to https://dev.to/settings/organization . From the settings page of your member account, click on the "Create or Join Organization" button in the top right corner. Then complete all required fields under "Create An Organization." Once you've created your organization, you'll immediately be taken to a page that encourages you to invite members or "Grow The Team." Inviting Folks to Your Organization Logged-in Organization Admins can invite teammates to join the Organization at any time by sending them a secret code: Navigate to https://dev.to/settings/organization . Make sure that Your Organization's Name shows in the dropdown at the top of the page. Under the list of organization members, you'll see a section called "Grow the Team." Follow the instructions on screen to generate and send a secret code to your teammates, letting them know to follow these steps: Sign up at https://dev.to . Navigate to https://dev.to/settings/organization . Click on "Create or Join an Organization." Paste the secret code below and click "Join Organization." Assigning (& Removing) Organization Admin Responsibilities Organization admins can promote other members to admin status, and you can have multiple admins within your org. If you'd like to make someone an admin, you must first follow the instructions above to add them to your organization (or skip if your teammate is already a member): Navigate to https://dev.to/settings/organization . Locate the teammate whom you want to make an Admin from the list of Organization Members. There will be a button next to their name that says "Make Admin." Click on the "Make Admin" button, and you're good to go! Admins can manage Organization members' status from this page, including "Revoke Admin Status" and "Remove from Organization." 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://github.com/enterprise#start-of-content | GitHub Enterprise · The AI-powered developer platform for the agent-ready enterprise · GitHub Skip to content Navigation Menu Toggle navigation Sign in Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} Enterprise Navigation menu Advanced Security Premium Support The AI-powered developer platform for the agent-ready enterprise Bring your DevOps together on one secure platform built for speed, scale, and the agent-driven future of software. Start a 30-day free trial Contact sales /enterprise Section - logo Ford 3M Procter and Gamble American Airlines KPMG Stripe Spotify Ford 3M Procter and Gamble <path fill-rule="evenodd" clip-rule="evenodd" d="M76.0342 0.431968C76.0302 0.435738 75.8448 0.449711 75.6219 0.463019C74.4813 0.530665 74.1155 0.56593 74.1155 0.607848C74.1155 0.628474 74.0293 0.638899 73.9223 0.631579C73.8161 0.62426 73.7292 0.633132 73.7292 0.651319C73.7292 0.669284 73.6598 0.677712 73.5746 0.669506C73.4896 0.661299 73.42 0.669506 73.42 0.687692C73.42 0.705879 73.3632 0.71586 73.294 0.709872C73.2246 0.703883 73.1496 0.710315 73.1272 0.724066C73.105 0.737817 72.9749 0.760218 72.838 0.773525C72.3725 0.819436 72.3195 0.828973 72.3062 0.868452C72.2873 0.925008 72.1451 0.917468 72.1438 0.85958C72.1432 0.831191 72.1274 0.837623 72.1052 0.875327C72.0824 0.914584 71.9894 0.950293 71.865 0.968036C71.5499 1.01239 71.5288 1.01616 71.1684 1.09224C70.9821 1.1315 70.8377 1.17208 70.8479 1.18229C70.8798 1.21422 69.9448 1.41627 69.898 1.38722C69.8702 1.37014 69.8638 1.37657 69.8809 1.4043C69.8991 1.43357 69.8744 1.44888 69.8095 1.44888C69.7551 1.44888 69.7108 1.46817 69.7108 1.49168C69.7108 1.51874 69.6713 1.5254 69.6045 1.50987C69.5336 1.49346 69.516 1.49701 69.5515 1.52074C69.6183 1.56532 69.3896 1.62454 69.3193 1.58106C69.2914 1.56377 69.284 1.56953 69.3 1.59548C69.3231 1.63274 69.1745 1.68375 69.0345 1.68664C69.0132 1.68708 68.9749 1.70482 68.9491 1.72612C68.9236 1.74719 68.8855 1.75406 68.8646 1.7412C68.8438 1.72833 68.8125 1.74186 68.7954 1.77158C68.7781 1.80108 68.7227 1.83812 68.6723 1.85365C68.6009 1.87582 68.5874 1.8705 68.6114 1.82969C68.6282 1.80086 68.6054 1.80951 68.5606 1.84877C68.5158 1.88802 68.4605 1.90865 68.4379 1.89468C68.4155 1.88093 68.3969 1.88758 68.3969 1.90976C68.3969 1.93194 68.3188 1.96986 68.223 1.99382C68.1274 2.01799 68.0491 2.05148 68.0491 2.06812C68.0491 2.08497 67.9404 2.13377 67.8076 2.17679C67.4401 2.29567 67.3006 2.35223 67.2447 2.40524C67.2165 2.43185 67.173 2.45625 67.148 2.45936L67.0639 2.47111C67.0426 2.47422 66.971 2.50571 66.9047 2.54097C66.8381 2.57624 66.7765 2.59775 66.7676 2.58888C66.7587 2.57979 66.7004 2.61638 66.6383 2.66983C66.5747 2.7244 66.4948 2.75922 66.4564 2.74924C66.4185 2.73925 66.3877 2.74813 66.3877 2.76853C66.3877 2.78916 66.3704 2.79515 66.3491 2.78206C66.3278 2.76875 66.3105 2.77474 66.3105 2.79492C66.3105 2.81511 66.2366 2.86102 66.1464 2.89717C66.0561 2.93332 65.9734 2.97524 65.9627 2.99032C65.9292 3.03779 65.542 3.22631 65.4781 3.22631C65.4446 3.22631 65.426 3.24072 65.4369 3.25824C65.4477 3.27599 65.3271 3.34984 65.1689 3.42259C65.0106 3.49534 64.8808 3.56742 64.8808 3.58317C64.8806 3.62176 64.5089 3.80762 64.4832 3.78189C64.4721 3.7708 64.4508 3.79919 64.4361 3.8451C64.4177 3.90366 64.3874 3.92317 64.3361 3.90964C64.2955 3.899 64.2625 3.9072 64.2625 3.92783C64.2625 3.94824 64.2425 3.95267 64.2179 3.93759C64.1911 3.92096 64.1837 3.92694 64.1997 3.95267C64.2223 3.98927 64.0981 4.0904 64.0254 4.0944C64.0119 4.09506 63.9542 4.14252 63.897 4.19952C63.84 4.25652 63.743 4.31441 63.6818 4.32772C63.6204 4.34125 63.5598 4.38561 63.5468 4.42686C63.5259 4.49295 63.4576 4.52179 63.3613 4.50515C63.3438 4.50205 63.3394 4.5158 63.3518 4.53554C63.364 4.5555 63.2879 4.61472 63.1826 4.66706C63.0772 4.71962 63.0007 4.77219 63.0125 4.78416C63.038 4.80945 62.6796 5.04055 62.613 5.04166C62.5992 5.04257 62.5858 5.04655 62.5738 5.0533C62.5617 5.06005 62.5514 5.06941 62.5434 5.0807C62.5294 5.10332 62.5467 5.10842 62.586 5.09334C62.631 5.07604 62.6434 5.08247 62.6243 5.11308C62.609 5.13792 62.5771 5.15832 62.5536 5.15832C62.5299 5.15832 62.4757 5.18871 62.4332 5.22597C62.3755 5.27654 62.3628 5.27898 62.3837 5.23551C62.399 5.20379 62.3824 5.21666 62.3469 5.26456C62.3114 5.31247 62.2557 5.3515 62.2229 5.3515C62.1901 5.3515 62.1741 5.36259 62.1876 5.3759C62.2109 5.39919 62.0295 5.56398 61.9807 5.56398C61.9676 5.56398 61.8891 5.62963 61.8057 5.7097C61.4247 6.07654 61.4389 6.06611 61.4012 6.00645C61.3737 5.96276 61.3657 5.96964 61.3652 6.03728C61.3648 6.08851 61.3408 6.12422 61.3067 6.12422C61.2747 6.12422 61.2483 6.13731 61.2477 6.15328C61.245 6.24332 61.0933 6.37352 61.0563 6.3174C61.0226 6.26661 61.0179 6.26706 61.0175 6.32051C61.0166 6.39791 60.8469 6.5596 60.8074 6.52078C60.791 6.50459 60.7837 6.52056 60.791 6.55649C60.7983 6.5922 60.7921 6.62347 60.7773 6.62613C60.7624 6.62857 60.6034 6.77318 60.4242 6.94729C60.2448 7.12161 60.0309 7.32611 59.9489 7.40196C59.7575 7.57872 59.5166 7.84243 59.3762 8.0294C59.2953 8.13697 59.2573 8.1627 59.2338 8.12588C59.2099 8.08818 59.2019 8.09261 59.2014 8.14296C59.201 8.18 59.166 8.2319 59.1234 8.25851C59.081 8.28491 59.0462 8.32971 59.0462 8.35765C59.0462 8.3856 59.0291 8.39802 59.008 8.38493C58.987 8.37207 58.9792 8.38582 58.9905 8.41554C59.0025 8.44681 58.9706 8.49672 58.9156 8.53265C58.863 8.56724 58.7885 8.64842 58.7503 8.71296C58.7106 8.78016 58.6589 8.82208 58.6297 8.81099C58.6015 8.80013 58.5884 8.80722 58.6004 8.82696C58.6126 8.84648 58.5897 8.88529 58.5498 8.91346C58.5097 8.94141 58.4702 8.98177 58.4622 9.00284C58.454 9.02413 58.4349 9.03744 58.4196 9.03234C58.4046 9.02724 58.4019 9.04897 58.4141 9.08025C58.4261 9.11174 58.4103 9.14745 58.379 9.15943C58.3478 9.1714 58.2653 9.26899 58.1959 9.37634C58.1262 9.48368 58.012 9.62874 57.9421 9.69882C57.872 9.76869 57.8259 9.837 57.8394 9.85052C57.8532 9.86405 57.7926 9.94279 57.705 10.0251C57.6174 10.1076 57.5542 10.1837 57.5646 10.1939C57.595 10.2245 57.4861 10.3746 57.4333 10.3746C57.4065 10.3746 57.3848 10.4086 57.3848 10.45C57.3848 10.4915 57.3544 10.5423 57.3171 10.5631C57.2799 10.584 57.255 10.6066 57.2617 10.6135C57.2841 10.6363 57.2184 10.7798 57.1563 10.8433C57.0228 10.9799 56.9744 11.0568 56.9911 11.1063C57.0015 11.1374 56.9909 11.1473 56.9647 11.1311C56.9378 11.1145 56.921 11.134 56.921 11.1819C56.921 11.2245 56.8988 11.2733 56.8715 11.2904C56.8443 11.3075 56.7649 11.4388 56.6952 11.582C56.6253 11.7255 56.5535 11.8429 56.5353 11.8429C56.5169 11.8429 56.4814 11.905 56.4566 11.9808C56.4315 12.0567 56.3902 12.1268 56.365 12.1365C56.3397 12.1461 56.3164 12.1886 56.3133 12.2308C56.3102 12.2729 56.2818 12.3332 56.2503 12.3645C56.2188 12.396 56.1729 12.483 56.1483 12.5577C56.1219 12.6375 56.0862 12.6832 56.0618 12.6682C56.0385 12.6535 56.0314 12.6604 56.046 12.6839C56.0793 12.7378 56.0088 12.921 55.9245 12.9988C55.8881 13.0326 55.8535 13.0862 55.8473 13.1179C55.8271 13.2248 55.6772 13.556 55.626 13.6072C55.598 13.6349 55.5375 13.7713 55.4913 13.9102C55.4452 14.049 55.3787 14.1912 55.3438 14.2262C55.3088 14.2611 55.2797 14.3087 55.2795 14.3318C55.2782 14.4174 55.0894 14.8954 55.0568 14.8954C55.0384 14.8954 55.034 14.9129 55.0471 14.9344C55.0604 14.9557 55.044 15.0005 55.0109 15.0338C54.9777 15.067 54.9504 15.1256 54.9504 15.164C54.9504 15.2023 54.9269 15.2924 54.8983 15.364L54.8146 15.5716C54.7976 15.6142 54.7863 15.6619 54.7898 15.6779C54.7931 15.6938 54.7803 15.7069 54.761 15.7069C54.7419 15.7069 54.7053 15.7938 54.6798 15.9003C54.6543 16.0065 54.6177 16.1035 54.5982 16.1154C54.5787 16.1274 54.5736 16.1547 54.5866 16.1758C54.5997 16.1971 54.5782 16.2405 54.539 16.2727C54.4995 16.3046 54.4911 16.3186 54.5199 16.3037C54.5578 16.2842 54.5662 16.2969 54.5507 16.3492C54.5387 16.3891 54.5177 16.4696 54.5037 16.528C54.4897 16.5865 54.4629 16.6342 54.4438 16.6342C54.425 16.6342 54.4094 16.669 54.4094 16.7116C54.4094 16.754 54.3939 16.7888 54.3751 16.7888C54.3562 16.7888 54.3431 16.8105 54.3462 16.8372C54.3535 16.9035 54.167 17.6536 54.1371 17.6775C54.1082 17.7008 53.99 18.1451 53.9625 18.3329C53.9519 18.4065 53.9306 18.4762 53.9155 18.4875C53.9002 18.499 53.8822 18.5951 53.8754 18.7009C53.8683 18.8069 53.8483 18.9027 53.8306 18.9136C53.8128 18.9244 53.7866 19.0029 53.7725 19.0879C53.7583 19.1728 53.7363 19.2684 53.7237 19.3004C53.711 19.3323 53.6962 19.3931 53.6908 19.4356C53.6855 19.478 53.6731 19.5563 53.6636 19.6095C53.654 19.6625 53.6329 19.8147 53.617 19.9475C53.601 20.0804 53.5728 20.1891 53.5544 20.1891C53.5358 20.1891 53.5207 20.2419 53.5207 20.3062C53.5207 20.3707 53.4952 20.4843 53.4642 20.5588C53.4289 20.6435 53.424 20.6841 53.4513 20.6673C53.4786 20.6504 53.4875 20.6606 53.4744 20.6948C53.4628 20.7247 53.4307 20.9622 53.4027 21.2226C53.3748 21.483 53.342 21.6961 53.33 21.6961C53.318 21.6964 53.3031 21.8913 53.2969 22.1295C53.2907 22.3679 53.271 22.5722 53.253 22.5835C53.1404 22.6545 53.1326 26.1825 53.245 26.2524C53.265 26.2646 53.2927 26.4487 53.3069 26.6611C53.3209 26.8736 53.3397 27.0998 53.3486 27.1635L53.3921 27.4727C53.4072 27.5789 53.4205 27.7379 53.4218 27.8264C53.4231 27.9147 53.4349 27.9801 53.4482 27.9719C53.4615 27.9637 53.4843 28.0478 53.499 28.1584C53.5138 28.2693 53.5422 28.37 53.5626 28.3827C53.5828 28.3951 53.6059 28.4823 53.6141 28.5765C53.6221 28.6706 53.6414 28.7786 53.6567 28.8165C53.672 28.8544 53.6862 28.9456 53.688 29.0194C53.6899 29.0931 53.7053 29.1534 53.7221 29.1534C53.739 29.1534 53.7492 29.1665 53.7452 29.1825C53.729 29.2466 53.8 29.4626 53.8374 29.4626C53.8594 29.4626 53.8685 29.4974 53.8574 29.5398C53.8463 29.5823 53.8543 29.6276 53.8756 29.6407C53.8967 29.6538 53.9053 29.6972 53.8949 29.7374C53.8829 29.7833 53.8913 29.8008 53.9173 29.7846C53.9437 29.7684 53.9499 29.7826 53.9341 29.8232C53.9206 29.8587 53.9282 29.8875 53.9512 29.8875C53.9741 29.8875 53.9829 29.913 53.971 29.9443C53.959 29.9756 53.9641 30.0102 53.9823 30.0215C54.0005 30.0328 54.0362 30.1288 54.0617 30.2353C54.0872 30.3415 54.1209 30.4285 54.1364 30.4285C54.1934 30.4285 54.2546 30.7106 54.2094 30.7652C54.1761 30.8053 54.1808 30.8113 54.23 30.7924C54.2832 30.772 54.3256 30.8574 54.2846 30.9018C54.2797 30.9071 54.3056 30.9546 54.3425 31.0071C54.3793 31.0597 54.4094 31.1344 54.4094 31.1735C54.4094 31.2125 54.4256 31.2345 54.4454 31.2223C54.4651 31.2101 54.4924 31.2396 54.5061 31.2877C54.5578 31.4678 54.737 31.8581 54.7681 31.8581C54.7858 31.8581 54.7896 31.8757 54.7765 31.8967C54.7634 31.918 54.7729 31.9355 54.7978 31.9355C54.8224 31.9355 54.8328 31.9615 54.8204 31.9934C54.8082 32.0254 54.8131 32.0513 54.8313 32.0513C54.8492 32.0513 54.8743 32.0817 54.8867 32.119C54.9131 32.1973 54.9865 32.3141 55.0588 32.3927C55.0863 32.4228 55.1456 32.5251 55.1901 32.62C55.2347 32.7149 55.2948 32.8014 55.3234 32.8125C55.352 32.8234 55.3758 32.8524 55.3762 32.8766C55.3771 32.9314 55.5745 33.2317 55.704 33.3754C55.757 33.4342 55.8005 33.4952 55.8007 33.5107C55.8007 33.5262 55.8619 33.6054 55.9365 33.6866C56.011 33.768 56.0622 33.8505 56.05 33.8702C56.0378 33.89 56.0549 33.9062 56.0879 33.9062C56.1212 33.9062 56.1483 33.9321 56.1483 33.964C56.1483 33.996 56.1656 34.0219 56.1869 34.0219C56.2082 34.0219 56.2268 34.0525 56.2286 34.0896C56.2306 34.1344 56.2385 34.1399 56.2521 34.1062C56.2743 34.0505 56.4078 34.2071 56.3885 34.2663C56.3827 34.2839 56.3945 34.2881 56.4144 34.2757C56.4501 34.2537 56.6892 34.4653 56.6892 34.519C56.6892 34.534 56.74 34.5762 56.8021 34.613C56.864 34.6496 56.937 34.7297 56.9642 34.7911C56.9913 34.8523 57.0348 34.8942 57.0609 34.8842C57.1204 34.8614 57.2688 35.0062 57.2688 35.087C57.2688 35.12 57.2847 35.1371 57.3045 35.1251C57.3641 35.0881 57.6234 35.2622 57.5999 35.3236C57.5884 35.3538 57.5917 35.3709 57.6072 35.3615C57.6618 35.3296 57.8153 35.4114 57.7869 35.4574C57.7698 35.4849 57.776 35.4917 57.8026 35.4753C57.8625 35.4383 58.1823 35.6459 58.1364 35.6918C58.1266 35.7013 58.1415 35.7093 58.1692 35.7093C58.2737 35.7093 58.5846 35.8901 58.5347 35.9218C58.4975 35.9455 58.4997 35.9539 58.5438 35.9579C58.5758 35.9606 58.6192 35.967 58.6405 35.9719C58.6618 35.9768 58.702 35.9834 58.7297 35.9868C58.7574 35.9899 58.7692 36.0105 58.7559 36.0322C58.7423 36.054 58.7457 36.0677 58.7632 36.0628C58.8177 36.0478 59.0848 36.1513 59.0848 36.1875C59.0848 36.2066 59.111 36.2121 59.1429 36.1997C59.1746 36.1875 59.2008 36.1948 59.2008 36.2161C59.2008 36.2374 59.2449 36.2658 59.299 36.2793C59.3583 36.2942 59.3864 36.3212 59.3702 36.3474C59.3549 36.3722 59.3607 36.3802 59.3835 36.366C59.4359 36.3339 59.6643 36.4135 59.6643 36.4643C59.6643 36.4856 59.6892 36.4938 59.7191 36.4822C59.7493 36.4707 59.7845 36.4887 59.7974 36.5222C59.8103 36.5559 59.8318 36.5723 59.8451 36.559C59.8584 36.5457 59.8941 36.565 59.9243 36.6018C59.9544 36.6386 59.9682 36.647 59.9549 36.6204C59.924 36.5599 59.9551 36.5592 60.0631 36.6186C60.1095 36.6442 60.1822 36.6708 60.2248 36.6776C60.2671 36.6847 60.3071 36.7054 60.3135 36.7238C60.3197 36.7422 60.3563 36.7491 60.3947 36.7391C60.4166 36.7349 60.4392 36.736 60.4607 36.742C60.4822 36.7481 60.5019 36.7591 60.5184 36.7741C60.5701 36.8251 60.9223 36.9467 61.2834 37.0376C61.377 37.0613 61.4781 37.1053 61.5083 37.1354C61.5387 37.1658 61.6048 37.1904 61.6553 37.1904C61.7059 37.1904 61.7873 37.2066 61.8361 37.2266C61.8849 37.2465 61.9905 37.2734 62.0707 37.2865C62.151 37.2995 62.2076 37.3251 62.1963 37.3432C62.1852 37.3614 62.2105 37.3674 62.2526 37.3563C62.2948 37.3452 62.3602 37.3497 62.3977 37.3659C62.4352 37.3823 62.4981 37.3914 62.5376 37.3865C62.5771 37.3814 62.5993 37.394 62.5866 37.4142C62.574 37.4348 62.6523 37.4628 62.7638 37.4776C62.8736 37.4923 62.9821 37.5156 63.0045 37.5298C63.0269 37.5437 63.0888 37.5582 63.142 37.5619C63.195 37.5657 63.2819 37.5794 63.3352 37.5928C63.3884 37.6058 63.5445 37.6262 63.6821 37.6378C63.8198 37.6495 63.9416 37.6733 63.9526 37.6908C63.9719 37.7216 64.2128 37.7655 64.4943 37.7895C64.5688 37.7957 64.734 37.811 64.8615 37.8232C65.3107 37.8662 65.7134 37.8944 65.8951 37.8953C65.996 37.8957 66.0785 37.907 66.0785 37.9201C66.0785 37.9332 66.5177 37.9365 67.0542 37.9274C67.5909 37.9186 68.1906 37.9097 68.3873 37.9081C68.5838 37.9066 68.7446 37.8948 68.7446 37.8822C68.7446 37.8695 68.8099 37.858 68.8897 37.8567C69.2716 37.85 70.344 37.7274 70.3699 37.6875C70.3819 37.669 70.5234 37.6495 70.6847 37.6442C70.8459 37.6391 70.9685 37.6196 70.9572 37.601C70.9459 37.5823 70.9987 37.5743 71.0743 37.5832C71.1502 37.5921 71.205 37.5877 71.1961 37.5732C71.1872 37.5588 71.2797 37.5351 71.4017 37.5204C71.7845 37.4745 71.8932 37.4541 71.9131 37.4244C71.9513 37.3674 72.1449 37.341 72.1456 37.3925C72.146 37.4297 72.1542 37.4288 72.1793 37.3891C72.1977 37.3603 72.2625 37.3319 72.3237 37.3262C72.3847 37.3204 72.4608 37.3058 72.4927 37.2938C72.6224 37.2452 73.1902 37.1485 73.2239 37.1694C73.2439 37.1816 73.2727 37.1714 73.288 37.1465C73.3055 37.1181 73.2993 37.1115 73.2714 37.1288C73.247 37.1438 73.2268 37.1359 73.2268 37.111C73.2268 37.0829 73.2698 37.072 73.3408 37.0824C73.4034 37.0917 73.4471 37.0868 73.4377 37.072C73.4284 37.0569 73.4599 37.0343 73.5074 37.0214C73.6356 36.9873 73.6595 36.9919 73.6283 37.0456C73.6127 37.072 73.6334 37.0651 73.6742 37.0303C73.7152 36.9953 73.8833 36.9371 74.0479 36.9008C74.2127 36.8646 74.3475 36.8214 74.3475 36.805C74.3475 36.7664 74.843 36.6408 74.8871 36.6681C74.9055 36.6794 74.9264 36.6703 74.9339 36.6481C74.9413 36.6257 74.9907 36.6011 75.0435 36.5931C75.1948 36.5705 75.3134 36.5273 75.3134 36.4949C75.3134 36.4652 75.4858 36.4197 75.6514 36.4057C75.6993 36.4017 75.7384 36.3869 75.7384 36.3731C75.7384 36.3372 75.9728 36.2602 76.011 36.2837C76.0285 36.2944 76.0591 36.2742 76.079 36.2385C76.1014 36.1984 76.1398 36.1833 76.18 36.1988C76.2186 36.2134 76.2352 36.2079 76.221 36.1848C76.1992 36.1498 76.4128 36.0808 76.4823 36.1003C76.4982 36.1048 76.5113 36.089 76.5113 36.0653C76.5113 36.0413 76.5452 36.0311 76.5885 36.0424C76.6311 36.0535 76.6659 36.048 76.6659 36.0302C76.6659 36.0125 76.7049 35.9857 76.7528 35.9706C76.8005 35.9557 76.8509 35.926 76.8646 35.9047C76.8784 35.8834 76.9418 35.8641 77.0057 35.8617C77.0696 35.8592 77.1139 35.8444 77.1042 35.8284C77.0942 35.8124 77.109 35.7967 77.1368 35.7936C77.2481 35.7805 77.2692 35.7736 77.3854 35.712C77.4517 35.6767 77.5171 35.659 77.5307 35.6725C77.5442 35.686 77.5905 35.6594 77.6338 35.6131C77.7101 35.531 77.7551 35.5132 77.854 35.5261C77.8804 35.5294 77.9022 35.5124 77.9022 35.488C77.9022 35.4633 77.9283 35.4534 77.9603 35.4656C77.992 35.4778 78.0182 35.4711 78.0182 35.4505C78.0182 35.4299 78.0497 35.413 78.0882 35.413C78.1266 35.413 78.1951 35.3786 78.2404 35.3363C78.2856 35.2941 78.4356 35.2134 78.5733 35.1568C78.7403 35.0883 78.8226 35.0333 78.8202 34.992C78.8142 34.8929 78.9444 34.4857 78.9818 34.4857C79.0007 34.4857 79.0078 34.4336 78.9978 34.3697C78.9878 34.306 78.9956 34.2539 79.0155 34.2539C79.0353 34.2539 79.1005 34.0669 79.1604 33.8385C79.2203 33.6101 79.2815 33.4144 79.2961 33.4038C79.311 33.3932 79.3542 33.2714 79.3922 33.1332C79.4303 32.9953 79.478 32.8711 79.4984 32.8575C79.508 32.8512 79.5149 32.8414 79.5176 32.8302C79.5203 32.819 79.5187 32.8072 79.513 32.7972C79.4831 32.7488 79.5645 32.4377 79.6071 32.4377C79.6257 32.4377 79.641 32.406 79.641 32.3669C79.641 32.3279 79.6532 32.2838 79.6683 32.2689C79.6831 32.2538 79.7013 32.1946 79.7082 32.1369C79.7308 31.9528 79.8388 31.665 79.8856 31.6643C79.9116 31.6641 79.9063 31.6479 79.8728 31.6264C79.8362 31.6026 79.8322 31.5887 79.8619 31.5882C79.8878 31.588 79.8992 31.5616 79.8867 31.5297C79.8745 31.4979 79.8808 31.4718 79.9003 31.4718C79.92 31.4718 79.9668 31.3414 80.0043 31.1817C80.0475 30.9989 80.0879 30.9011 80.1141 30.9173C80.1389 30.9326 80.144 30.9244 80.1267 30.8967C80.0932 30.8426 80.1828 30.4631 80.2232 30.4879C80.2383 30.4975 80.2625 30.4267 80.2766 30.3309C80.2911 30.2348 80.319 30.1665 80.3385 30.1787C80.3583 30.1907 80.3643 30.1745 80.3521 30.1426C80.3461 30.1249 80.3438 30.1061 80.3454 30.0875C80.347 30.0689 80.3523 30.0508 80.3612 30.0344C80.3782 30.0072 80.39 29.9771 80.3962 29.9456C80.4108 29.795 80.4676 29.5784 80.4925 29.5784C80.5091 29.5784 80.5448 29.4914 80.5721 29.3852C80.5993 29.2789 80.6337 29.192 80.6486 29.192C80.6634 29.192 80.675 29.1703 80.6739 29.1439C80.6692 29.0148 80.6872 28.9187 80.7134 28.9347C80.7293 28.9443 80.7451 28.8821 80.7484 28.7965C80.7517 28.7109 80.7704 28.63 80.7899 28.6169C80.8296 28.5903 80.8841 28.4685 80.8961 28.3807C80.9152 28.2374 81.0789 27.6652 81.1057 27.6472C81.1314 27.6299 81.272 27.1535 81.331 26.8834C81.3417 26.8355 81.365 26.7964 81.3832 26.7964C81.4011 26.7964 81.406 26.7703 81.3938 26.7385C81.3816 26.7066 81.3887 26.6804 81.4096 26.6804C81.4442 26.6804 81.5131 26.4691 81.5009 26.4003C81.498 26.3843 81.5116 26.3715 81.5307 26.3715C81.5499 26.3715 81.5566 26.3367 81.5455 26.2941C81.5338 26.2493 81.5444 26.2169 81.5708 26.2169C81.5959 26.2169 81.6074 26.2027 81.5967 26.1856C81.5688 26.1404 81.6533 25.8305 81.6937 25.8305C81.7123 25.8305 81.7276 25.7871 81.7276 25.7338C81.7276 25.6806 81.746 25.6371 81.7684 25.6371C81.791 25.6371 81.7995 25.6209 81.787 25.6012C81.7748 25.5812 81.791 25.4901 81.823 25.3983C81.8549 25.3067 81.8813 25.2011 81.8815 25.1638C81.882 25.1268 81.8951 25.0962 81.911 25.0962C81.927 25.0962 81.9447 25.0319 81.9503 24.9531C81.956 24.8746 81.9742 24.8008 81.9909 24.789C82.0372 24.7566 82.1468 24.4404 82.1754 24.2565C82.1894 24.1667 82.2144 24.1015 82.2311 24.1117C82.2477 24.1221 82.2521 24.0957 82.2411 24.0531C82.2264 23.9968 82.2404 23.9748 82.2929 23.9726C82.3338 23.971 82.344 23.9611 82.3169 23.9502C82.2621 23.928 82.2504 23.8211 82.3027 23.8211C82.3351 23.8211 82.3803 23.7149 82.4012 23.5893C82.4333 23.3948 82.589 22.8721 82.6203 22.8528C82.6407 22.8399 82.6667 22.7805 82.6775 22.7206C82.6884 22.6605 82.7115 22.5837 82.7288 22.5498C82.7461 22.5159 82.7525 22.4664 82.743 22.4398C82.7336 22.4132 82.7441 22.3915 82.7665 22.3915C82.7887 22.3915 82.7971 22.3655 82.7849 22.3336C82.7725 22.3016 82.7776 22.2755 82.7957 22.2755C82.8139 22.2755 82.8326 22.2202 82.8374 22.1528C82.8421 22.0854 82.8609 22.0202 82.8791 22.008C82.9295 21.974 83.0422 21.7296 82.9934 21.7596C82.965 21.7773 82.9603 21.7616 82.9794 21.7121C82.9951 21.6713 83.0175 21.5915 83.0291 21.5342C83.0406 21.4772 83.0719 21.422 83.0989 21.4118C83.1267 21.4012 83.1402 21.3539 83.1304 21.3025C83.1198 21.2472 83.144 21.1743 83.1923 21.1159L83.3043 20.9804C83.3133 20.9689 83.3197 20.9555 83.3229 20.9413C83.326 20.927 83.326 20.9122 83.3227 20.8979C83.3147 20.8742 83.3351 20.828 83.368 20.7952C83.4008 20.7624 83.4276 20.6979 83.4276 20.6519C83.4276 20.6009 83.4578 20.5603 83.5046 20.5482C83.5467 20.5371 83.5718 20.5124 83.56 20.4936C83.5483 20.4745 83.5658 20.4486 83.5988 20.4359C83.6321 20.4233 83.6494 20.3971 83.6374 20.378C83.6068 20.3281 83.7632 20.121 83.853 20.0924C83.8945 20.0793 83.9244 20.0478 83.9196 20.0225C83.9147 19.9972 83.9338 19.9813 83.9619 19.9872C83.9901 19.993 84.0016 19.9793 83.9874 19.9564C83.9573 19.9076 84.0407 19.7947 84.0861 19.8229C84.1034 19.8338 84.1283 19.8089 84.1413 19.7681C84.1635 19.6976 84.3084 19.5769 84.3594 19.586C84.3725 19.5882 84.441 19.525 84.5115 19.4452C84.582 19.3656 84.6595 19.3004 84.6836 19.3004C84.7078 19.3004 84.7859 19.2482 84.8573 19.1844C84.9877 19.0681 85.0791 19.0298 85.0276 19.1132C85.0103 19.1409 85.017 19.1473 85.0451 19.1298C85.0702 19.1145 85.0815 19.0874 85.0706 19.0699C85.0447 19.0276 85.162 18.9839 85.2146 19.0165C85.2399 19.032 85.2443 19.0233 85.2259 18.9934C85.2053 18.9604 85.2181 18.9495 85.2667 18.9588C85.3062 18.9663 85.386 18.9251 85.4466 18.8659C85.5065 18.8073 85.5854 18.7587 85.6218 18.7581C85.6582 18.7574 85.7214 18.7317 85.7622 18.7009C85.8214 18.6561 85.848 18.6543 85.8953 18.6924C85.9354 18.7248 85.9454 18.7257 85.9272 18.6951C85.9236 18.6896 85.9213 18.6834 85.9204 18.6769C85.9196 18.6704 85.9202 18.6638 85.9223 18.6576C85.9243 18.6514 85.9278 18.6457 85.9324 18.641C85.937 18.6363 85.9426 18.6328 85.9487 18.6305C85.9753 18.6197 82.8414 18.6108 78.9841 18.6106C72.8149 18.6104 71.9897 18.617 72.1256 18.6663C72.2106 18.6971 72.2993 18.7477 72.3226 18.7789C72.3461 18.81 72.3756 18.8251 72.3885 18.8122C72.4013 18.7993 72.4381 18.8153 72.4705 18.8477C72.5029 18.8798 72.5907 18.9444 72.6659 18.9907C72.7409 19.0371 72.7925 19.0908 72.7808 19.1101C72.7688 19.1291 72.7892 19.1333 72.8258 19.1194C72.8793 19.099 72.8868 19.1085 72.8644 19.1668C72.8491 19.2072 72.8482 19.2283 72.8626 19.2139C72.8995 19.177 73.1496 19.3753 73.1496 19.4414C73.1496 19.4716 73.2033 19.5485 73.269 19.6129C73.3368 19.6792 73.379 19.7533 73.367 19.785C73.3548 19.8162 73.3661 19.8364 73.3925 19.8311C73.4182 19.8262 73.4371 19.8522 73.4342 19.8892C73.4311 19.9262 73.4413 19.9487 73.4566 19.9393C73.4719 19.9298 73.5078 20.0083 73.5364 20.1134C73.565 20.2188 73.605 20.3051 73.6247 20.3051C73.6447 20.3051 73.6518 20.3397 73.6407 20.3822C73.6296 20.4246 73.6351 20.4685 73.6531 20.4796C73.6711 20.4907 73.685 20.7167 73.6841 20.9818C73.6833 21.2468 73.67 21.4559 73.6549 21.4466C73.6396 21.4373 73.6347 21.4801 73.6438 21.542C73.654 21.6123 73.6369 21.6777 73.5981 21.7168C73.5639 21.7509 73.536 21.8199 73.536 21.87C73.536 21.9204 73.5158 22.0104 73.4912 22.0703C73.4666 22.13 73.4499 22.2007 73.4541 22.2273C73.4586 22.2539 73.4484 22.2757 73.4315 22.2757C73.4145 22.2757 73.3969 22.3313 73.3921 22.3992C73.3872 22.4671 73.3568 22.5374 73.3244 22.5556C73.292 22.5738 73.2656 22.6401 73.2656 22.7031C73.2656 22.8182 73.2022 22.9659 73.1303 23.0189C73.1064 23.0364 73.1099 23.0475 73.1399 23.0477C73.1665 23.0482 73.1882 23.0668 73.1882 23.0892C73.1882 23.1118 73.1683 23.1178 73.1436 23.1027C73.1175 23.0865 73.1095 23.0919 73.1241 23.1158C73.1598 23.1735 73.1088 23.3993 73.066 23.3729C73.0458 23.3605 73.0412 23.3937 73.0556 23.4509C73.0693 23.5057 73.0647 23.5508 73.0454 23.5508C73.0259 23.5508 72.9782 23.6727 72.9396 23.822C72.9008 23.971 72.8538 24.1028 72.8349 24.1143C72.8161 24.1261 72.8107 24.1522 72.8234 24.1724C72.8476 24.2117 72.7699 24.4845 72.7251 24.5166C72.701 24.5342 72.4936 25.2796 72.4922 25.3546C72.4918 25.3719 72.4738 25.3599 72.4523 25.3282C72.4235 25.2856 72.4199 25.2993 72.4388 25.3805C72.4559 25.4537 72.4474 25.5016 72.4137 25.5225C72.3858 25.5395 72.3585 25.5839 72.3532 25.6207C72.3476 25.6573 72.3228 25.7001 72.2977 25.7156C72.2629 25.7372 72.2629 25.7474 72.2975 25.7589C72.3321 25.7704 72.3317 25.8015 72.296 25.8891C72.27 25.9525 72.2463 26.0217 72.2434 26.043C72.2203 26.202 72.17 26.3715 72.1456 26.3715C72.1192 26.3715 72.0895 26.466 72.0425 26.6997C72.0338 26.7423 72.011 26.7825 71.9914 26.7893C71.9719 26.796 71.965 26.8246 71.9759 26.853C71.9868 26.8814 71.9768 26.9162 71.9537 26.9304C71.9307 26.9446 71.9198 26.969 71.9293 26.9847C71.9575 27.0304 71.8743 27.3522 71.8269 27.3815C71.8029 27.3964 71.7792 27.4365 71.7741 27.4709C71.7472 27.6539 71.6636 27.9105 71.6364 27.8936C71.619 27.883 71.6146 27.8994 71.6264 27.9302C71.6521 27.9972 71.5723 28.3133 71.5219 28.3448C71.5024 28.357 71.4787 28.4062 71.4696 28.4541C71.4577 28.512 71.4426 28.5691 71.4243 28.6253C71.4103 28.6652 71.3995 28.7061 71.3919 28.7477C71.3693 28.9553 71.3205 29.0691 71.2622 29.0505C71.2143 29.0354 71.211 29.0394 71.2489 29.0665C71.3015 29.1044 71.2753 29.308 71.2178 29.308C71.2012 29.308 71.1761 29.3863 71.1617 29.4819C71.1473 29.5775 71.1229 29.6558 71.1076 29.6558C71.0923 29.6558 71.0766 29.6861 71.073 29.7234C71.0555 29.8991 71.0125 30.0392 70.9818 30.0204C70.9632 30.0088 70.9581 30.0259 70.9708 30.0585C70.9832 30.0909 70.9654 30.1452 70.9313 30.1794C70.8971 30.2136 70.8778 30.2555 70.8885 30.2726C70.9053 30.3001 70.8687 30.4482 70.8022 30.6217C70.7716 30.7015 70.7725 30.698 70.7381 30.8851C70.7215 30.977 70.6818 31.0621 70.6503 31.0741C70.6035 31.0921 70.6024 31.1023 70.6445 31.1293C70.6829 31.1542 70.6844 31.1701 70.6507 31.1921C70.6259 31.2083 70.5931 31.2735 70.5778 31.3369C70.5624 31.4006 70.5398 31.4698 70.5274 31.4911C70.515 31.5124 70.499 31.5731 70.4919 31.6264C70.468 31.8067 70.3575 32.1478 70.314 32.1755C70.2903 32.1908 70.2699 32.2168 70.2686 32.2334C70.2575 32.3818 70.1989 32.5923 70.1688 32.5923C70.1481 32.5923 70.1415 32.6089 70.1539 32.6293C70.1843 32.6781 70.1355 32.8673 70.0985 32.8444C70.0827 32.8345 70.0778 32.8695 70.0878 32.9218C70.0982 32.976 70.0878 33.0174 70.0641 33.0174C70.041 33.0174 70.0332 33.046 70.047 33.0818C70.0634 33.125 70.0568 33.1368 70.0264 33.1181C69.9967 33.0997 69.9811 33.1219 69.9811 33.1827C69.9811 33.2335 69.9481 33.3778 69.9077 33.5036C69.8689 33.6234 69.835 33.7447 69.8061 33.8673C69.7908 33.9419 69.762 34.0131 69.7418 34.0259C69.7219 34.0386 69.6992 34.082 69.6917 34.1224C69.6842 34.1628 69.6753 34.1958 69.6722 34.1958C69.6688 34.1958 69.6586 34.2393 69.6493 34.2925C69.6212 34.4542 69.5981 34.4921 69.5466 34.4613C69.5094 34.4389 69.5083 34.4451 69.542 34.4879C69.5733 34.5276 69.5744 34.5715 69.5458 34.6403C69.5238 34.6933 69.5083 34.7629 69.5116 34.7949C69.5218 34.9002 69.4608 34.943 69.2681 34.9656C69.1634 34.9781 69.0669 35.0053 69.054 35.0262C68.9693 35.1633 66.2331 35.1619 66.2331 35.0249C66.2331 35.0093 66.1765 34.9878 66.1076 34.9772C66.0386 34.9665 65.9386 34.9459 65.8853 34.9313C65.8378 34.9177 65.7894 34.9076 65.7405 34.9011C65.7139 34.8993 65.6921 34.8814 65.6921 34.8614C65.6921 34.8414 65.6662 34.835 65.6345 34.8472C65.5753 34.8701 65.1858 34.7623 65.1512 34.7135C65.1405 34.6986 65.0341 34.6432 64.9148 34.5904C64.7952 34.5376 64.6859 34.4757 64.6719 34.4531C64.6579 34.4302 64.6209 34.4216 64.5896 34.4336C64.5539 34.4473 64.5331 34.4316 64.5331 34.391C64.5331 34.3555 64.5155 34.3373 64.494 34.3506C64.4727 34.3639 64.4448 34.3475 64.4319 34.3142C64.4193 34.281 64.3758 34.2539 64.3357 34.2539C64.2955 34.2539 64.2237 34.2147 64.1762 34.167C64.1269 34.1175 64.0718 34.0743 64.0121 34.0381C63.9693 34.0153 63.9389 33.9747 63.9447 33.9483C63.9506 33.9219 63.9384 33.9108 63.9178 33.9234C63.8704 33.9527 63.4512 33.5655 63.4512 33.4923C63.4512 33.4623 63.4337 33.4486 63.4121 33.4619C63.3908 33.4752 63.3616 33.4544 63.3472 33.4158C63.3327 33.3774 63.2893 33.3231 63.2507 33.2953C63.2121 33.2676 63.1806 33.2219 63.1806 33.1938C63.1806 33.1656 63.1467 33.1188 63.1052 33.0897C63.0635 33.0605 63.0244 33.0119 63.0182 32.9815C63.0067 32.9265 62.9371 32.8254 62.8401 32.7236C62.8122 32.6943 62.7869 32.6366 62.7838 32.5954C62.7807 32.5541 62.7665 32.5277 62.7521 32.5366C62.7226 32.5548 62.6268 32.3427 62.6268 32.2596C62.6268 32.2301 62.6124 32.2059 62.5946 32.2059C62.5769 32.2059 62.5625 32.1788 62.5625 32.1458C62.5625 32.1125 62.5474 32.0948 62.529 32.1061C62.4902 32.13 62.3238 31.6687 62.3538 31.6202C62.3646 31.6024 62.3566 31.5878 62.3358 31.5878C62.3152 31.5878 62.2859 31.5312 62.2708 31.4622C62.2557 31.393 62.2287 31.3269 62.2103 31.3154C62.1921 31.3037 62.1655 31.2358 62.1513 31.1644C62.1326 31.0717 62.138 31.0426 62.1694 31.0621C62.1981 31.0797 62.2056 31.0683 62.1907 31.0297C62.1783 30.9967 62.1537 30.9787 62.1364 30.9894C62.0967 31.0138 62.0459 30.792 62.0787 30.7385C62.0923 30.7168 62.0876 30.6991 62.0685 30.6991C62.0495 30.6991 62.0109 30.5511 61.9827 30.3706C61.9548 30.1898 61.917 30.0421 61.8993 30.0421C61.8816 30.0421 61.8669 30.0159 61.8669 29.9842C61.8669 29.9523 61.8887 29.9259 61.9153 29.9257C61.9483 29.9252 61.9459 29.9139 61.9073 29.8895C61.8687 29.8649 61.8505 29.7811 61.8494 29.6196C61.8483 29.4907 61.8332 29.3854 61.8159 29.3854C61.7986 29.3852 61.7875 29.2765 61.7913 29.1439C61.7953 29.011 61.7884 28.8762 61.7762 28.8442C61.7587 28.7983 61.7676 27.0562 61.7886 26.4487C61.7988 26.1473 61.8328 25.9833 61.8791 26.0111C61.9057 26.027 61.9029 26.0113 61.872 25.9734C61.8099 25.8966 61.8461 25.4817 61.919 25.4349C61.9514 25.4142 61.9503 25.4065 61.9153 25.406C61.8887 25.4056 61.8669 25.3783 61.8669 25.3453C61.8669 25.312 61.8842 25.2956 61.9055 25.3089C61.9277 25.3224 61.9441 25.2874 61.9441 25.2262C61.9441 25.0725 62.0974 23.8515 62.1253 23.7825C62.1382 23.7506 62.1448 23.6836 62.1397 23.6333C62.1348 23.5831 62.1459 23.5514 62.1646 23.563C62.1832 23.5745 62.1912 23.5224 62.1825 23.447C62.1737 23.3715 62.1856 23.2981 62.2089 23.2837C62.2544 23.2555 62.2843 23.134 62.289 22.9592C62.2905 22.898 62.3085 22.861 62.33 22.8743C62.3518 22.8876 62.3586 22.8725 62.3458 22.839C62.3192 22.77 62.403 22.2371 62.4403 22.2366C62.4542 22.2366 62.468 22.1564 62.4709 22.0583C62.4735 21.9603 62.4928 21.8691 62.5134 21.8556C62.544 21.8359 62.5762 21.7272 62.6179 21.5027C62.6199 21.4921 62.6343 21.4633 62.6501 21.4386C62.6658 21.414 62.668 21.3661 62.6549 21.3324C62.6421 21.2987 62.6483 21.271 62.6689 21.271C62.6893 21.271 62.698 21.2275 62.6878 21.1743C62.6776 21.1213 62.6844 21.0778 62.7029 21.0776C62.7213 21.0773 62.739 21.0039 62.7426 20.9145C62.7461 20.8249 62.7667 20.7455 62.7887 20.7382C62.8106 20.7309 62.8182 20.6983 62.8058 20.6657C62.7931 20.6331 62.8033 20.5938 62.8282 20.5783C62.8739 20.5501 62.8796 20.5308 62.9282 20.2376C62.9433 20.1474 62.9717 20.0635 62.9914 20.0513C63.0111 20.0391 63.0189 20.0156 63.0089 19.9992C62.9772 19.9482 63.0657 19.6867 63.1147 19.6863C63.144 19.6858 63.1398 19.6703 63.1034 19.6446C63.0597 19.6137 63.0573 19.5987 63.0936 19.584C63.1203 19.5732 63.142 19.5397 63.142 19.5097C63.142 19.4796 63.1577 19.4549 63.177 19.4549C63.1963 19.4549 63.203 19.4201 63.1917 19.3775C63.1806 19.3347 63.1908 19.2766 63.2143 19.2482C63.238 19.2198 63.2462 19.1857 63.2327 19.1722C63.2192 19.1586 63.2281 19.1238 63.252 19.095C63.2762 19.0659 63.2844 19.0307 63.2704 19.0167C63.2564 19.0027 63.2664 18.9912 63.2924 18.9912C63.3183 18.9912 63.3285 18.9732 63.315 18.951C63.2897 18.9104 63.3718 18.5243 63.4132 18.4888C63.4496 18.4578 63.5669 18.1251 63.5669 18.053C63.5669 18.0164 63.582 17.9867 63.6002 17.9867C63.6186 17.9867 63.6248 17.9406 63.614 17.8842C63.6033 17.8279 63.61 17.7915 63.629 17.803C63.6481 17.8148 63.667 17.7611 63.6712 17.6839C63.6752 17.6068 63.6965 17.5378 63.7182 17.5305C63.7399 17.5231 63.769 17.4577 63.7825 17.385C63.7963 17.312 63.8247 17.2526 63.846 17.2526C63.867 17.2526 63.8744 17.2264 63.8622 17.1945C63.85 17.1627 63.8579 17.1366 63.8797 17.1366C63.9016 17.1366 63.9156 17.1062 63.9109 17.0689C63.8974 16.9647 63.9575 16.7132 64.0081 16.6613C64.0578 16.6105 64.2474 16.0877 64.2596 15.9677C64.2612 15.9518 64.2867 15.9387 64.3164 15.9387C64.372 15.9387 64.4344 15.8273 64.3987 15.7914C64.3876 15.7803 64.3785 15.7945 64.3785 15.8229C64.3785 15.8511 64.3703 15.8662 64.3601 15.8559C64.3272 15.8231 64.479 15.4725 64.5127 15.5033C64.5306 15.5197 64.5328 15.5111 64.5175 15.4844C64.4883 15.4337 64.5683 15.166 64.6127 15.166C64.6269 15.166 64.6684 15.0704 64.7052 14.9533C64.742 14.8364 64.7877 14.7503 64.8065 14.7621C64.8256 14.7738 64.8309 14.7565 64.8183 14.7235C64.8056 14.6907 64.8101 14.6636 64.8283 14.6636C64.8465 14.6636 64.864 14.6179 64.8673 14.562C64.8706 14.5061 64.8955 14.4467 64.9225 14.4298C64.9498 14.413 64.9764 14.3693 64.9818 14.3325C64.9871 14.2957 65.0115 14.2533 65.0361 14.2382C65.0605 14.2229 65.0762 14.2038 65.0711 14.1956C65.0454 14.1548 65.1627 13.8933 65.1971 13.9146C65.2222 13.9301 65.2273 13.9091 65.2106 13.8569C65.1953 13.8084 65.2015 13.7749 65.2259 13.7749C65.2486 13.7749 65.2672 13.7489 65.2672 13.717C65.2672 13.6851 65.2845 13.6589 65.3058 13.6589C65.3271 13.6589 65.3402 13.646 65.3351 13.6301C65.3178 13.5764 65.4664 13.2339 65.507 13.2339C65.5298 13.2339 65.5243 13.263 65.4941 13.3016C65.4466 13.3619 65.448 13.3639 65.5047 13.3196C65.5396 13.292 65.56 13.2382 65.55 13.1996C65.5398 13.1612 65.5604 13.1009 65.5954 13.0658C65.6305 13.0308 65.6447 13.0015 65.6274 13.0011C65.6099 13.0004 65.6267 12.9815 65.6649 12.9594C65.7103 12.933 65.7261 12.8935 65.7108 12.8451C65.6948 12.795 65.7192 12.7416 65.7864 12.6795C65.8407 12.6289 65.8853 12.5677 65.8853 12.5431C65.8853 12.4834 65.9685 12.3395 66.0399 12.2756C66.0719 12.247 66.0761 12.2346 66.0497 12.2481C65.9787 12.284 65.9909 12.2166 66.0707 12.1303C66.1091 12.0891 66.1974 11.938 66.2673 11.7947C66.3371 11.6512 66.4059 11.5339 66.4205 11.5339C66.4349 11.5339 66.5059 11.4122 66.5782 11.2633C66.6505 11.1145 66.7339 10.993 66.7634 10.993C66.7931 10.993 66.8071 10.9763 66.7947 10.9562C66.782 10.936 66.8069 10.9007 66.8497 10.8779C66.8727 10.866 66.8916 10.8475 66.9038 10.8248C66.9161 10.802 66.9212 10.776 66.9184 10.7503C66.9131 10.7 66.9288 10.6683 66.9561 10.6736C66.9821 10.6787 66.9941 10.6592 66.983 10.6303C66.9719 10.6015 66.9898 10.5674 67.0231 10.5547C67.0562 10.5421 67.0832 10.505 67.0832 10.4724C67.0832 10.4398 67.0963 10.4132 67.1125 10.4132C67.1285 10.4132 67.1637 10.3633 67.1908 10.3021C67.2181 10.2409 67.2815 10.1424 67.3321 10.0836C67.3829 10.0246 67.4465 9.93126 67.4738 9.87603C67.5011 9.82081 67.5854 9.71789 67.6608 9.64736C67.7362 9.57684 67.7765 9.52982 67.7501 9.54312C67.7187 9.55887 67.7102 9.54667 67.7253 9.50719C67.7379 9.47437 67.7617 9.44731 67.7781 9.44731C67.7945 9.44731 67.8295 9.39519 67.8559 9.33131C67.8823 9.26766 67.9178 9.21554 67.9349 9.21554C67.9517 9.21554 68.0056 9.15033 68.0544 9.07049C68.118 8.97211 68.1902 8.87962 68.2702 8.79414C68.3399 8.72183 68.3969 8.64044 68.3969 8.61316C68.3969 8.5861 68.449 8.52666 68.5129 8.48141C68.5765 8.43595 68.6289 8.37584 68.6289 8.34767C68.6289 8.31973 68.689 8.24853 68.7626 8.18998C68.8363 8.13121 68.889 8.07088 68.8797 8.05602C68.8538 8.01388 69.0361 7.85862 69.0725 7.89167C69.0902 7.90786 69.0931 7.90032 69.0784 7.87504C69.064 7.84975 69.0742 7.81515 69.1013 7.79785C69.1283 7.78055 69.1703 7.73176 69.1944 7.68918C69.2186 7.64659 69.2663 7.61421 69.3002 7.61732C69.3342 7.6202 69.3535 7.60844 69.3428 7.59137C69.3322 7.57429 69.3455 7.53681 69.3723 7.50842C69.3989 7.47981 69.4861 7.38266 69.5657 7.29261C69.6456 7.20257 69.7108 7.13758 69.7108 7.14823C69.7108 7.1591 69.776 7.09433 69.8556 7.00473C70.0415 6.79536 70.2193 6.64299 70.2624 6.65652C70.2808 6.66229 70.2856 6.65053 70.2732 6.63013C70.251 6.59442 70.4744 6.35666 70.5303 6.35622C70.5454 6.35622 70.6323 6.28613 70.7235 6.20052C71.04 5.90332 71.083 5.86606 71.2081 5.78023C71.2771 5.73276 71.3338 5.70814 71.3341 5.72567C71.3345 5.74296 71.3567 5.71391 71.3833 5.6609C71.4101 5.60812 71.4636 5.55866 71.5022 5.55112C71.5408 5.5438 71.6062 5.50387 71.6477 5.46262C71.6889 5.42115 71.7393 5.39764 71.7595 5.41006C71.7799 5.4227 71.7861 5.40606 71.7734 5.3728C71.7603 5.33908 71.7708 5.31291 71.7967 5.31291C71.8224 5.31291 71.8939 5.27698 71.9555 5.23307C72.0342 5.17696 72.068 5.16831 72.0688 5.20401C72.0695 5.23551 72.0853 5.22885 72.1099 5.18649C72.1318 5.14879 72.1649 5.12727 72.1833 5.13881C72.2017 5.15012 72.2279 5.12395 72.2416 5.0807C72.2554 5.03745 72.3507 4.9596 72.4534 4.90748C72.5561 4.85558 72.6459 4.79925 72.6533 4.78283C72.669 4.74735 72.9407 4.61738 72.999 4.61738C73.0212 4.61738 73.0654 4.59121 73.0975 4.55905C73.1297 4.52689 73.1718 4.5107 73.1913 4.52267C73.2108 4.53487 73.2268 4.51757 73.2268 4.4843C73.2268 4.42952 73.28 4.40912 73.41 4.41377C73.4364 4.41466 73.4495 4.40202 73.4395 4.38561C73.4293 4.36919 73.4566 4.34635 73.5001 4.33504C73.5686 4.31707 73.5726 4.32284 73.5298 4.37895C73.5025 4.41444 73.5276 4.40135 73.5854 4.3499C73.6433 4.29822 73.6906 4.26917 73.6906 4.28491C73.6906 4.30088 73.7161 4.29068 73.7471 4.26273C73.8915 4.13254 73.9297 4.11147 74.0346 4.10393C74.0962 4.09927 74.137 4.07998 74.1251 4.06068C74.1133 4.04139 74.141 4.0354 74.1867 4.04738C74.2326 4.05935 74.2701 4.05203 74.2701 4.03096C74.2701 4.00989 74.2916 3.99991 74.318 4.00878C74.3444 4.01743 74.3892 4.00147 74.4174 3.9733C74.4458 3.94491 74.5023 3.91962 74.5434 3.91696C74.6795 3.90809 74.6977 3.90277 74.7257 3.86329C74.7691 3.80119 75.0814 3.73022 75.0821 3.78234C75.0825 3.80984 75.0936 3.80806 75.1131 3.77746C75.1298 3.75106 75.2904 3.69939 75.47 3.66235C75.6494 3.62553 75.8051 3.58361 75.8158 3.5692C75.8584 3.51197 76.2922 3.48336 76.2589 3.53992C76.2416 3.56942 76.2631 3.5621 76.3068 3.52395C76.3864 3.45431 76.5217 3.44965 76.6235 3.51353C76.663 3.53814 76.6692 3.53349 76.6464 3.49667C76.6231 3.45897 76.6364 3.45165 76.6985 3.46784C76.7442 3.47981 76.7732 3.4756 76.7626 3.45852C76.7406 3.42304 78.3253 3.41372 78.3826 3.44898C78.403 3.46185 78.5032 3.46762 78.6055 3.46229C78.7075 3.45697 78.7911 3.46673 78.7913 3.48425C78.7915 3.50177 78.914 3.51996 79.0635 3.52484C79.2462 3.5306 79.3547 3.55278 79.3944 3.59248C79.4267 3.62486 79.5044 3.65148 79.5669 3.65148C79.7348 3.65148 80.3924 3.80407 80.4073 3.84666C80.4144 3.86684 80.4525 3.88325 80.4918 3.88325C80.531 3.88325 80.6122 3.90343 80.6721 3.92805C80.732 3.95267 80.7945 3.96997 80.8114 3.9662C80.877 3.95178 80.9946 4.04338 80.9678 4.08796C80.9487 4.11968 80.9593 4.11879 81.0012 4.08464C81.0518 4.04383 81.0733 4.04605 81.1246 4.09706C81.1587 4.13121 81.1867 4.1423 81.1867 4.12145C81.1867 4.10061 81.2215 4.09284 81.2638 4.10393C81.3064 4.11502 81.3412 4.13942 81.3412 4.15827C81.3412 4.1769 81.3661 4.19243 81.3965 4.19243C81.4266 4.19243 81.4745 4.21416 81.5027 4.24056C81.5307 4.26717 81.5885 4.29423 81.6309 4.30066C81.7941 4.3255 81.9592 4.39315 81.9385 4.42686C81.9265 4.44616 81.9443 4.45126 81.9778 4.43839C82.0146 4.42442 82.068 4.4486 82.1122 4.49939C82.1525 4.54574 82.1954 4.58256 82.2076 4.58123C82.3071 4.56991 82.3466 4.58455 82.3224 4.62403C82.3036 4.65442 82.3156 4.66107 82.3588 4.64444C82.3941 4.63091 82.4231 4.63756 82.4231 4.65952C82.4231 4.68125 82.4391 4.68924 82.4586 4.67726C82.4781 4.66506 82.5196 4.68081 82.5507 4.71186C82.5817 4.74291 82.6183 4.75711 82.6318 4.74335C82.6456 4.72983 82.6833 4.75666 82.7159 4.80324C82.7485 4.84981 82.8097 4.88774 82.8516 4.88774C82.9388 4.88774 83.1045 4.98644 83.2085 5.10044C83.2473 5.1428 83.2695 5.15832 83.258 5.13482C83.2462 5.11131 83.34 5.14613 83.4664 5.21222C83.5926 5.27809 83.7011 5.35816 83.7073 5.3901C83.7108 5.40597 83.7195 5.42025 83.7319 5.43075C83.7443 5.44125 83.7598 5.44738 83.7761 5.4482C83.8615 5.4482 84.1613 5.63429 84.1615 5.6873C84.163 5.70216 84.1679 5.71649 84.1757 5.72923C84.1835 5.74197 84.194 5.75281 84.2066 5.76093C84.2352 5.77867 84.2405 5.77135 84.2216 5.74075C84.2054 5.71458 84.2533 5.73321 84.3283 5.78244C84.4033 5.83146 84.4545 5.88802 84.4421 5.90798C84.4297 5.92816 84.4476 5.93348 84.4829 5.91995C84.5005 5.91283 84.52 5.91245 84.5378 5.91888C84.5556 5.92531 84.5704 5.93809 84.5794 5.95477C84.5976 5.98738 84.6546 6.03595 84.706 6.06279C84.7573 6.0894 84.7952 6.13088 84.7903 6.15505C84.7852 6.17901 84.8056 6.18943 84.8356 6.1779C84.8666 6.16592 84.9087 6.19165 84.9331 6.23711C84.9566 6.28147 84.9946 6.3174 85.0174 6.3174C85.04 6.3174 85.1135 6.3622 85.1802 6.41676C85.4563 6.6421 85.6027 6.76453 85.6495 6.80889C85.6894 6.84659 85.7036 6.82752 85.7216 6.71219C85.7742 6.37462 85.8567 6.07454 85.9055 6.04416C85.925 6.03196 85.9487 5.98272 85.9578 5.93481C85.9671 5.88691 85.9873 5.80995 86.0031 5.76381C86.0186 5.71768 86.0332 5.66246 86.0354 5.64139C86.0523 5.48791 86.1084 5.31247 86.1297 5.34707C86.1439 5.37013 86.1556 5.32533 86.1556 5.24726C86.1556 5.16919 86.1765 5.09844 86.202 5.09001C86.2275 5.08159 86.2484 5.04233 86.2484 5.00285C86.2484 4.96337 86.267 4.91946 86.2896 4.90548C86.3125 4.89151 86.3224 4.85758 86.3118 4.8303C86.2881 4.7682 86.4185 4.33659 86.4511 4.36942C86.4642 4.3825 86.4655 4.35677 86.4537 4.31197C86.4422 4.26739 86.4497 4.23102 86.4708 4.23102C86.4919 4.23102 86.5225 4.17446 86.5387 4.10548C86.5666 3.98705 86.5728 3.9642 86.5959 3.89279C86.6013 3.87445 86.6031 3.85525 86.6012 3.83623C86.5988 3.82115 86.617 3.76016 86.6414 3.70094C86.6658 3.64194 86.6822 3.57163 86.678 3.54502C86.6735 3.51863 86.6837 3.49689 86.7006 3.49667C86.7177 3.49667 86.7352 3.44144 86.7401 3.37402C86.7447 3.3066 86.764 3.24139 86.7827 3.22919C86.8015 3.21699 86.8383 3.11563 86.8649 3.00407C86.8913 2.89251 86.9281 2.80136 86.9466 2.80136C86.965 2.80136 86.9707 2.77696 86.9594 2.74724C86.9479 2.71752 86.9574 2.68159 86.9805 2.6674C87.0036 2.65298 87.0144 2.62858 87.0049 2.61306C86.98 2.57291 87.0572 2.2471 87.0976 2.22226C87.1723 2.17613 87.1888 1.98716 87.1158 2.01533C87.0732 2.03174 87.0563 2.02664 87.0716 2.00202C87.0856 1.9794 87.0592 1.96277 87.0104 1.96321C86.8248 1.96476 86.7472 1.94968 86.7678 1.91619C86.7798 1.89689 86.7518 1.89091 86.7061 1.90288C86.6527 1.91686 86.6318 1.90998 86.648 1.88359C86.664 1.85786 86.6449 1.84987 86.5968 1.86252C86.5546 1.87361 86.4892 1.86917 86.4517 1.85276C86.4143 1.83657 86.3706 1.8257 86.3546 1.82925C86.3386 1.83258 86.3258 1.81794 86.3258 1.79665C86.3258 1.77535 86.2938 1.75805 86.2548 1.75805C86.2158 1.75805 86.1725 1.74652 86.1583 1.73233C86.1443 1.71835 86.0762 1.70061 86.007 1.69307C85.9379 1.68553 85.8755 1.66224 85.8684 1.64117C85.8611 1.6201 85.8409 1.61189 85.8232 1.62276C85.8057 1.63385 85.6983 1.62276 85.585 1.59836C85.4186 1.56243 85.3938 1.54757 85.4563 1.52162C85.5056 1.501 85.4796 1.49789 85.3845 1.51298C85.2818 1.52917 85.2255 1.52052 85.2039 1.48569C85.1866 1.45775 85.1407 1.43069 85.1019 1.42515L84.8573 1.39077C84.7617 1.37746 84.6783 1.35218 84.6719 1.33443C84.6657 1.31691 84.6264 1.31137 84.5849 1.32224C84.5435 1.3331 84.5095 1.32556 84.5095 1.3056C84.5095 1.28542 84.4574 1.27677 84.3937 1.28608C84.3299 1.2954 84.2777 1.28808 84.2775 1.26967C84.2775 1.25148 84.1957 1.23174 84.0957 1.22576C83.9959 1.21999 83.9023 1.19604 83.8878 1.17275C83.8734 1.14924 83.7943 1.12351 83.7122 1.1153C83.6301 1.10732 83.482 1.08204 83.3828 1.05919C83.1757 1.01173 83.0652 0.994651 82.7751 0.965596C82.6607 0.954063 82.5476 0.932549 82.5241 0.917911C82.5003 0.903051 82.4395 0.896397 82.3888 0.903051C82.3382 0.909483 82.2845 0.895288 82.2699 0.871557C82.255 0.847604 82.1401 0.818993 82.0142 0.807903C81.8884 0.796813 81.7615 0.779736 81.732 0.769755C81.7028 0.759996 81.5462 0.742031 81.3843 0.729833C81.2224 0.717856 81.076 0.694568 81.0587 0.678156C81.0414 0.661743 80.9589 0.656198 80.875 0.665735C80.7914 0.675494 80.7229 0.666844 80.7229 0.646661C80.7229 0.626035 80.6368 0.618494 80.5242 0.629362C80.3811 0.643113 80.333 0.636015 80.3525 0.604299C80.3822 0.556393 80.3381 0.54863 80.0717 0.555505C79.9792 0.557945 79.8874 0.549961 79.8674 0.53754C79.8293 0.51403 79.2094 0.47433 78.9907 0.481649C78.8953 0.484754 78.8696 0.472999 78.8918 0.43596C78.9153 0.397147 78.908 0.397369 78.8587 0.437291C78.8144 0.473221 78.7421 0.480318 78.6143 0.461244C78.462 0.4384 76.0551 0.41112 76.0342 0.431968ZM12.1379 0.866677C12.1379 0.886639 12.1683 0.913032 12.2056 0.925674C12.2856 0.952732 12.4633 1.11176 12.6112 1.28897C12.7197 1.41894 12.7532 1.51408 12.6729 1.46462C12.6449 1.44733 12.6387 1.45398 12.6563 1.48215C12.6716 1.50721 12.7004 1.51741 12.7201 1.50521C12.7399 1.49301 12.7563 1.52318 12.7567 1.57219C12.7572 1.64206 12.7652 1.64915 12.7931 1.6048C12.8505 1.51408 13.0298 1.96698 13.0413 2.23135C13.0437 2.28991 13.0677 2.33759 13.0943 2.33759C13.1296 2.33759 13.1424 2.44073 13.1424 2.72395C13.1424 2.95594 13.1271 3.11031 13.1038 3.11031C13.0825 3.11031 13.0652 3.17241 13.0652 3.24804C13.0652 3.32367 13.0522 3.37735 13.0362 3.36759C13.0202 3.35783 13.0045 3.42104 13.0009 3.5082C12.9972 3.60468 12.9699 3.68497 12.9313 3.71314C12.8965 3.73864 12.8838 3.76548 12.9033 3.77302C12.9415 3.78766 12.8432 4.23678 12.7949 4.26961C12.7627 4.29157 12.6347 4.70521 12.6174 4.84338C12.6074 4.9002 12.5788 4.95211 12.5363 4.99109C12.4977 5.02237 12.4906 5.03545 12.5203 5.02015C12.5631 4.99797 12.5684 5.01527 12.5465 5.10421C12.5312 5.16587 12.5023 5.22198 12.4828 5.22908C12.4631 5.23617 12.436 5.31025 12.4227 5.39342C12.4094 5.47659 12.3823 5.54468 12.3626 5.54468C12.3426 5.54468 12.3371 5.56176 12.35 5.58261C12.3781 5.62808 12.2923 5.93104 12.2513 5.93104C12.2353 5.93104 12.2322 5.96853 12.2442 6.01444C12.2581 6.06789 12.2513 6.08851 12.2249 6.07232C12.1987 6.05613 12.1914 6.07632 12.2049 6.12821C12.2167 6.17302 12.2098 6.2207 12.1896 6.23445C12.1499 6.26173 11.9833 6.81155 11.9833 6.91535C11.9833 6.95039 11.966 6.96836 11.9452 6.95527C11.9228 6.94152 11.917 6.95816 11.9314 6.99564C11.945 7.03068 11.9394 7.07082 11.9195 7.08458C11.8813 7.11075 11.7709 7.43611 11.7831 7.48624C11.7871 7.50221 11.7744 7.51529 11.7551 7.51529C11.7358 7.51529 11.7298 7.55278 11.7418 7.59869C11.758 7.66079 11.7507 7.67387 11.713 7.65059C11.6788 7.62952 11.6715 7.63439 11.6908 7.66544C11.7239 7.71912 11.6358 8.09483 11.5901 8.09483C11.573 8.09483 11.548 8.16447 11.5344 8.24942C11.5209 8.33459 11.4936 8.40401 11.4739 8.40401C11.4539 8.40401 11.4475 8.41975 11.4595 8.43905C11.4712 8.45812 11.4406 8.59342 11.3912 8.73936C11.3417 8.88552 11.3084 9.02613 11.3171 9.0523C11.3257 9.07825 11.3149 9.09954 11.2927 9.09954C11.2707 9.09954 11.2412 9.16031 11.2273 9.23483C11.2133 9.30913 11.1853 9.36991 11.1654 9.36991C11.1452 9.36991 11.1374 9.3841 11.1481 9.40162C11.1718 9.43977 11.0223 10.0377 10.9822 10.0652C10.9664 10.0761 10.931 10.1717 10.9034 10.2781C10.7651 10.8104 10.6939 11.0273 10.6639 11.0087C10.6457 10.9974 10.6295 11.0112 10.628 11.0389C10.6264 11.0666 10.6167 11.1243 10.6065 11.1669C10.596 11.2092 10.5858 11.2658 10.5836 11.2924C10.5814 11.319 10.5692 11.3407 10.5568 11.3407C10.5446 11.3407 10.5311 11.3798 10.5268 11.4275C10.512 11.6047 10.4667 11.7644 10.437 11.7459C10.4202 11.7355 10.4155 11.7617 10.4266 11.8043C10.4379 11.8475 10.4277 11.8817 10.4035 11.8817C10.3798 11.8817 10.3601 11.9121 10.3596 11.9491C10.3576 12.0835 10.1822 12.6178 10.1496 12.5881C10.1312 12.5715 10.1285 12.5792 10.1436 12.6054C10.1908 12.6877 10.1265 12.9323 10.064 12.9084C10.0336 12.8966 10.0189 12.9037 10.0314 12.9239C10.044 12.9441 10.0101 13.1264 9.95618 13.3289C9.90229 13.5316 9.85815 13.707 9.85815 13.719C9.85815 13.731 9.8424 13.7312 9.82311 13.7192C9.80381 13.7072 9.79694 13.7316 9.80803 13.7736C9.81889 13.8155 9.80004 13.8771 9.76566 13.9115C9.73151 13.9457 9.70356 14.0217 9.70356 14.0803C9.70356 14.1391 9.69136 14.1994 9.67628 14.2143C9.66142 14.2293 9.64301 14.2872 9.63547 14.3433C9.62575 14.4062 9.60685 14.4674 9.57936 14.5248C9.55585 14.5685 9.53145 14.6645 9.5248 14.7379C9.51815 14.8115 9.48687 14.8863 9.45516 14.904C9.42366 14.9215 9.40747 14.9617 9.41945 14.9932C9.43165 15.0245 9.421 15.05 9.39638 15.05C9.37154 15.05 9.36001 15.0642 9.37066 15.0812C9.39638 15.1229 9.31499 15.4396 9.28371 15.4204C9.27018 15.4121 9.25843 15.4745 9.25732 15.558 | 2026-01-13T08:48:30 |
https://stackoverflow.blog/llm/ | llm - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. llm Related Tags software development AI machine learning data generative AI contributed Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed December 23, 2025 Settle down, nerds. AI is a normal technology Ryan welcomes Anil Dash, writer and former Stack Overflow board member, back to the show to discuss how AI is not a magical technology, but rather the normal next step in computing’s evolution. They explore the importance of democratizing access to technology, the unique challenges that LLMs’ non-determinism poses, and how developers can keep Stack Overflow’s ethos of community alive in a world of AI. Phoebe Sajor 0 comment s The Stack Overflow Podcast llm software development AI coding community December 19, 2025 Last week in AWS re:Invent with Corey Quinn Ryan sits down with Corey Quinn, Chief Cloud Economist at Duckbill, at AWS re:Invent to get Corey’s patented snarky take on all the happenings from the conference. Phoebe Sajor 0 comment s The Stack Overflow Podcast aws cloud computing infrastructure management software development llm AI agentic AI August 19, 2025 The server-side rendering equivalent for LLM inference workloads Ryan is joined by Tuhin Srivastava, CEO and co-founder of Baseten, to explore the evolving landscape of AI infrastructure and inference workloads, how the shift from traditional machine learning models to large-scale neural networks has made GPU usage challenging, and the potential future of hardware-specific optimizations in AI. Phoebe Sajor 0 comment s llm The Stack Overflow Podcast server-side rendering AI hardware July 8, 2025 Attention isn’t all we need; we need ownership too Ryan welcomes Illia Polosukhin, co-author of the original "Attention Is All You Need" Transformers paper and co-founder of NEAR, on the show to talk about the development and impact of the Transformers model, his perspective on modern AI and machine learning as an early innovator of the tech, and the importance of decentralized, user-owned AI utilizing the blockchain. Phoebe Sajor 1 comment blockchain AI machine learning llm AI governance agentic AI AI agents The Stack Overflow Podcast June 11, 2025 Why you need diverse third-party data to deliver trusted AI solutions Diverse, high-quality data is a prerequisite for reliable, effective, and ethical AI solutions. David Gibson , Michael Geden 0 comment s Business Hub data data quality data diversity llm AI responsible ai May 30, 2025 Getting rid of the pain for developers on Shopify Ryan welcomes Glen Coates, VP of Product at Shopify, to dive into the intricacies of managing a developer-focused product, the challenges of backwards compatibility, and the implications of AI and LLMs in Shopify's development environment. Phoebe Sajor 0 comment s The Stack Overflow Podcast dev tools shopify AI ai assistant llm developer tools ecommerce May 2, 2025 Improving on a 30-year-old hardware architecture At HumanX 2025, Ryan chatted with Rodrigo Liang, cofounder and CEO of SambaNova, about reimagining 30-year-old hardware architecture for the AI era. Eira May 0 comment s The Stack Overflow Podcast generative AI AI hardware architecture software architecture llm humanx April 28, 2025 How self-supervised learning revolutionized natural language processing and gen AI Self-supervised learning is a key advancement that revolutionized natural language processing and generative AI. Here’s how it works and two examples of how it is used to train language models. Cameron R. Wolfe, PhD 26 comment s llm AI contributed February 28, 2025 “Translation is the tip of the iceberg”: A deep dive into specialty models Olga Beregovaya, VP of AI at Smartling, joins Ryan and Ben to explore the evolution and specialization of language models in AI. Eira May 0 comment s The Stack Overflow Podcast AI generative AI machine learning llm February 26, 2025 Variants of LoRA Want to train a specialized LLM on your own data? The easiest way to do this is with low rank adaptation (LoRA), but many variants of LoRA exist. Cameron R. Wolfe, PhD 0 comment s llm AI contributed February 24, 2025 Writing tests with AI, but not LLMs How Diffblue leverages machine learning techniques to write effective unit tests. Eira May 0 comment s The Stack Overflow Podcast software development software engineering AI generative AI autonomous agents automation unit tests testing java refactoring Productivity llm copilot ai coding dev tools developer tools December 27, 2024 Breaking up is hard to do: Chunking in RAG applications A look at some of the current thinking around chunking data for retrieval-augmented generation (RAG) systems. Ryan Donovan 2 comment s retrieval augmented generation llm December 5, 2024 Four approaches to creating a specialized LLM Wondering how to go about creating an LLM that understands your custom data? Start here. Cameron R. Wolfe, PhD 2 comment s llm AI contributed December 3, 2024 Even high-quality code can lead to tech debt Ben talks with Eran Yahav, a former researcher on IBM Watson who’s now the CTO and cofounder of AI coding company Tabnine. Ben and Eran talk about the intersection of software development and AI, the evolution of program synthesis, and Eran’s path from IBM research to startup CTO. They also discuss how to balance the productivity and learning gains of AI coding tools (especially for junior devs) against very real concerns around quality, security, and tech debt. Eira May 0 comment s The Stack Overflow Podcast llm AI generative AI software development tech debt ai assistant ai coding November 26, 2024 Your docs are your infrastructure Fabrizio Ferri-Benedetti, who spent many years as a technical writer for Splunk and New Relic, joins Ben and Ryan for a conversation about the evolving role of documentation in software development. They explore how documentation can (and should) be integrated with code, the importance of quality control, and the hurdles to maintaining up-to-date documentation. Plus: Why technical writers shouldn’t be afraid of LLMs. Eira May 2 comment s The Stack Overflow Podcast llm AI generative AI documentation technical writing software development November 12, 2024 A student of Geoff Hinton, Yann LeCun, and Jeff Dean explains where AI is headed Ben and Ryan are joined by Matt Zeiler, founder and CEO of Clarifai, an AI workflow orchestration platform. They talk about how the transformer architecture supplanted convolutional neural networks in AI applications, the infrastructure required for AI implementation, the implications of regulating AI, and the value of synthetic data. Eira May 1 comment The Stack Overflow Podcast AI data llm training machine learning synthetic data November 8, 2024 One of the world’s biggest web scrapers has some thoughts on data ownership Or Lenchner, CEO of Bright Data, joins Ben and Ryan for a deep-dive conversation about the evolving landscape of web data. They talk through the challenges involved in data collection, the role of synthetic data in training large AI models, and how public data access is becoming more restrictive. Or also shares his thoughts on the importance of transparency in data practices, the likely future of data regulation, and the philosophical implications of more people using AI to innovate and solve problems. Eira May 1 comment The Stack Overflow Podcast AI data training data ethics data scraping llm November 7, 2024 No code, only natural language: Q&A on prompt engineering with Professor Greg Benson Will prompt engineering replace the coder’s art or will software engineers who understand code still have a place in future software lifecycles? Ryan Donovan 5 comment s llm AI October 31, 2024 A brief summary of language model finetuning Here's a (brief) summary of language model finetuning, the various approaches that exist, their purposes, and what we know about how they work. Cameron R. Wolfe, PhD 0 comment s llm AI October 25, 2024 Tragedy of the (data) commons Ben chats with Shayne Longpre and Robert Mahari of the Data Provenance Initiative about what GenAI means for the data commons. They discuss the decline of public datasets, the complexities of fair use in AI training, the challenges researchers face in accessing data, potential applications for synthetic data, and the evolving legal landscape surrounding AI and copyright. Eira May 2 comment s The Stack Overflow Podcast AI llm data September 26, 2024 Masked self-attention: How LLMs learn relationships between tokens Masked self-attention is the key building block that allows LLMs to learn rich relationships and patterns between the words of a sentence. Let’s build it together from scratch. Cameron R. Wolfe, PhD 1 comment llm AI contributed September 20, 2024 Detecting errors in AI-generated code Ben chats with Gias Uddin, an assistant professor at York University in Toronto, where he teaches software engineering, data science, and machine learning. His research focuses on designing intelligent tools for testing, debugging, and summarizing software and AI systems. He recently published a paper about detecting errors in code generated by LLMs. Gias and Ben discuss the concept of hallucinations in AI-generated code, the need for tools to detect and correct those hallucinations, and the potential for AI-powered tools to generate QA tests. Eira May 1 comment The Stack Overflow Podcast AI llm September 13, 2024 The world’s largest open-source business has plans for enhancing LLMs Ben and Ryan talk to Scott McCarty, Global Senior Principal Product Manager for Red Hat Enterprise Linux, about the intersection between LLMs (large language models) and open source. They discuss the challenges and benefits of open-source LLMs, the importance of attribution and transparency, and the revolutionary potential for LLM-driven applications. They also explore the role of LLMs in code generation, testing, and documentation. Eira May 0 comment s The Stack Overflow Podcast llm AI Open Source August 22, 2024 LLMs evolve quickly. Their underlying architecture, not so much. The decoder-only transformer architecture is one of the most fundamental ideas in AI research. Cameron R. Wolfe, PhD 0 comment s llm architecture AI contributed Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2024/12/31/generative-ai-is-not-going-to-build-your-engineering-team-for-you/#comments | Generative AI is not going to build your engineering team for you - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. December 31, 2024 Generative AI is not going to build your engineering team for you It’s easy to generate code, but not so easy to generate good code. Credit: Alexandra Francis [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2025.] When I was 19 years old, I dropped out of college and moved to San Francisco. I had a job offer in hand to be a Unix sysadmin for Taos Consulting. However, before my first day of work I was lured away to a startup in the city, where I worked as a software engineer on mail subsystems. I never questioned whether or not I could find work. Jobs were plentiful, and more importantly, hiring standards were very low. If you knew how to sling HTML or find your way around a command line, chances were you could find someone to pay you. Was I some kind of genius, born with my hands on a computer keyboard? Assuredly not. I was homeschooled in the backwoods of Idaho. I didn’t touch a computer until I was sixteen and in college. I escaped to university on a classical performance piano scholarship, which I later traded in for a peripatetic series of nontechnical majors: classical Latin and Greek, musical theory, philosophy. Everything I knew about computers I learned on the job, doing sysadmin work for the university and CS departments. In retrospect, I was so lucky to enter the industry when I did. It makes me blanch to think of what would have happened if I had come along a few years later. Every one of the ladders my friends and I took into the industry has long since vanished. The software industry is growing up To some extent, this is just what happens as an industry matures. The early days of any field are something of a Wild West, where the stakes are low, regulation nonexistent, and standards nascent. If you look at the early history of other industries—medicine, cinema, radio—the similarities are striking. There is a magical moment with any young technology where the boundaries between roles are porous and opportunity can be seized by anyone who is motivated, curious, and willing to work their asses off. It never lasts. It can’t; it shouldn’t. The amount of prerequisite knowledge and experience you must have before you can enter the industry swells precipitously. The stakes rise, the magnitude of the mission increases, the cost of mistakes soars. We develop certifications, trainings, standards, legal rites. We wrangle over whether or not software engineers are really engineers . Software is an apprenticeship industry Nowadays, you wouldn’t want a teenaged dropout like me to roll out of junior year and onto your pager rotation. The prerequisite knowledge you need to enter the industry has grown, the pace is faster, and the stakes are much higher, so you can no longer learn literally everything on the job, as I once did. However, it’s not like you can learn everything you need to know at college either. A CS degree typically prepares you better for a life of computing research than life as a workaday software engineer. A more practical path into the industry may be a good coding bootcamp, with its emphasis on problem solving and learning a modern toolkit. In either case, you don’t so much learn “how to do the job” as you do “learn enough of the basics to understand and use the tools you need to use to learn the job.” Software is an apprenticeship industry. You can’t learn to be a software engineer by reading books. You can only learn by doing…and doing, and doing, and doing some more. No matter what your education consists of, most learning happens on the job—period. And it never ends! Learning and teaching are lifelong practices; they have to be, the industry changes so fast. It takes a solid seven-plus years to forge a competent software engineer. (Or as most job ladders would call it, a “senior software engineer”.) That’s many years of writing, reviewing, and deploying code every day, on a team alongside more experienced engineers. That’s just how long it seems to take. What does it mean to be a “senior engineer”? Here is where I often get some very indignant pushback to my timelines, e.g.: “Seven years?! Pfft, it took me two years!” “I was promoted to Senior Software Engineer in less than five years!” Good for you. True, there is nothing magic about seven years. But it takes time and experience to mature into an experienced engineer, the kind who can anchor a team. More than that, it takes practice . I think we have come to use “Senior Software Engineer” as shorthand for engineers who can ship code and be a net positive in terms of productivity, and I think that’s a huge mistake. It implies that less senior engineers must be a net negative in terms of productivity, which is untrue. And it elides the real nature of the work of software engineering, of which writing code is only a small part. To me, being a senior engineer is not primarily a function of your ability to write code. It has far more to do with your ability to understand, maintain, explain, and manage a large body of software in production over time, as well as the ability to translate business needs into technical implementation. So much of the work is around crafting and curating these large, complex sociotechnical systems, and code is just one representation of these systems. What does it mean to be a senior engineer? It means you have learned how to learn , first and foremost, and how to teach; how to hold these models in your head and reason about them, and how to maintain, extend, and operate these systems over time. It means you have good judgment, and instincts you can trust. Which brings us to the matter of AI. We need to stop cannibalizing our own future It is really, really tough to get your first role as an engineer. I didn’t realize how hard it was until I watched my little sister (new grad, terrific grades, some hands on experience, fiendishly hard worker) struggle for nearly two years to land a real job in her field. That was a few years ago; anecdotally, it seems to have gotten even harder since then. This past year, I have read a steady drip of articles about entry-level jobs in various industries being replaced by AI. Some of which absolutely have merit. Any job that consists of drudgery such as converting a document from one format to another, reading and summarizing a bunch of text, or replacing one set of icons with another, seems pretty obviously vulnerable. This doesn’t feel all that revolutionary to me, it’s just extending the existing boom in automation to cover textual material as well as mathy stuff. Recently, however, a number of execs and so-called “thought leaders” in tech seem to have genuinely convinced themselves that generative AI is on the verge of replacing all the work done by junior engineers. I have read so many articles about how junior engineering work is being automated out of existence, or that the need for junior engineers is shriveling up. It has officially driven me bonkers. All of this bespeaks a deep misunderstanding about what engineers actually do . By not hiring and training up junior engineers, we are cannibalizing our own future. We need to stop doing that . Writing code is the easy part People act like writing code is the hard part of software. It is not. It never has been, it never will be. Writing code is the easiest part of software engineering , and it’s getting easier by the day. The hard parts are what you do with that code—operating it, understanding it, extending it, and governing it over its entire lifecycle. A junior engineer begins by learning how to write and debug lines, functions, and snippets of code. As you practice and progress towards being a senior engineer, you learn to compose systems out of software, and guide systems through waves of change and transformation. Sociotechnical systems consist of software, tools, and people; understanding them requires familiarity with the interplay between software, users, production, infrastructure, and continuous changes over time. These systems are fantastically complex and subject to chaos, nondeterminism and emergent behaviors. If anyone claims to understand the system they are developing and operating, the system is either exceptionally small or (more likely) they don’t know enough to know what they don’t know. Code is easy, in other words, but systems are hard . The present wave of generative AI tools has done a lot to help us generate lots of code, very fast. The easy parts are becoming even easier, at a truly remarkable pace. But it has not done a thing to aid in the work of managing, understanding, or operating that code. If anything, it has only made the hard jobs harder. It’s easy to generate code, and hard to generate good code If you read a lot of breathless think pieces, you may have a mental image of software engineers merrily crafting prompts for ChatGPT, or using Copilot to generate reams of code, then committing whatever emerges to GitHub and walking away. That does not resemble our reality. The right way to think about tools like Copilot is more like a really fancy autocomplete or copy-paste function, or maybe like the unholy love child of Stack Overflow search results plus Google’s “I feel lucky”. You roll the dice, every time. These tools are at their best when there’s already a parallel in the file, and you want to just copy-paste the thing with slight modifications. Or when you’re writing tests and you have a giant block of fairly repetitive YAML, and it repeats the pattern while inserting the right column and field names, like an automatic template. However, you cannot trust generated code . I can’t emphasize this enough. AI-generated code always looks quite plausible, but even when it kind of “works”, it’s rarely congruent with your wants and needs. It will happily generate code that doesn’t parse or compile. It will make up variables, method names, function calls; it will hallucinate fields that don’t exist. Generated code will not follow your coding practices or conventions. It is not going to refactor or come up with intelligent abstractions for you. The more important, difficult or meaningful a piece of code is, the less likely you are to generate a usable artifact using AI. You may save time by not having to type the code in from scratch, but you will need to step through the output line by line, revising as you go, before you can commit your code, let alone ship it to production. In many cases this will take as much or more time as it would take to simply write the code—especially these days, now that autocomplete has gotten so clever and sophisticated. It can be a LOT of work to bring AI-generated code into compliance and coherence with the rest of your codebase. It isn’t always worth the effort, quite frankly. Generating code that can compile, execute, and pass a test suite isn’t especially hard; the hard part is crafting a code base that many people, teams, and successive generations of teams can navigate, mutate, and reason about for years to come. How working engineers really use generative AI So that’s the TLDR: you can generate a lot of code, really fast, but you can’t trust what comes out. At all. However, there are some use cases where generative AI consistently shines. For example, it’s often easier to ask chatGPT to generate example code using unfamiliar APIs than by reading the API docs—the corpus was trained on repositories where the APIs are being used for real life workloads, after all. Generative AI is also pretty good at producing code that is annoying or tedious to write, yet tightly scoped and easy to explain. The more predictable a scenario is, the better these tools are at writing the code for you. If what you need is effectively copy-paste with a template—any time you could generate the code you want using sed/awk or vi macros—generative AI is quite good at this. It’s also very good at writing little functions for you to do things in unfamiliar languages or scenarios. If you have a snippet of Python code and you want the same thing in Java, but you don’t know Java, generative AI has got your back. Again, remember, the odds are 50/50 that the result is completely made up. You always have to assume the results are incorrect until you can verify it by hand. But these tools can absolutely accelerate your work in countless ways. Generative AI is a little bit like a junior engineer One of the engineers I work with, Kent Quirk, describes generative AI as “an excitable junior engineer who types really fast”. I love that quote—it leaves an indelible mental image. Generative AI is like a junior engineer in that you can’t roll their code off into production. You are responsible for it—legally, ethically, and practically. You still have to take the time to understand it, test it, instrument it, retrofit it stylistically and thematically to fit the rest of your code base, and ensure your teammates can understand and maintain it as well. The analogy is a decent one, actually, but only if your code is disposable and self-contained, i.e. not meant to be integrated into a larger body of work, or to survive and be read or modified by others. And hey—there are corners of the industry like this, where most of the code is write-only, throwaway code. There are agencies that spin out dozens of disposable apps per year, each written for a particular launch or marketing event and then left to wither on the vine. But that is not most software. Disposable code is rare; code that needs to work over the long term is the norm. Even when we think a piece of code will be disposable, we are often (urf) wrong. But generative AI is not a member of your team In that particular sense—generating code that you know is untrustworthy—GenAI is a bit like a junior engineer. But in every other way, the analogy fails. Because adding a person who writes code to your team is nothing like autogenerating code. That code could have come from anywhere—Stack Overflow, Copilot, whatever. You don’t know, and it doesn’t really matter. There’s no feedback loop, no person on the other end trying iteratively to learn and improve, and no impact to your team vibes or culture. To state the supremely obvious: giving code review feedback to a junior engineer is not like editing generated code. Your effort is worth more when it is invested into someone else’s apprenticeship. It’s an opportunity to pass on the lessons you’ve learned in your own career. Even just the act of framing your feedback to explain and convey your message forces you to think through the problem in a more rigorous way, and has a way of helping you understand the material more deeply. And adding a junior engineer to your team will immediately change team dynamics. It creates an environment where asking questions is normalized and encouraged, where teaching as well as learning is a constant. We’ll talk more about team dynamics in a moment. The time you invest into helping a junior engineer level up can pay off remarkably quickly. Time flies. ☺️ When it comes to hiring, we tend to valorize senior engineers almost as much as we underestimate junior engineers. Neither stereotype is helpful. We underestimate the cost of hiring seniors, and overestimate the cost of hiring juniors People seem to think that once you hire a senior engineer, you can drop them onto a team and they will be immediately productive, while hiring a junior engineer will be a tax on team performance forever. Neither are true. Honestly, most of the work that most teams have to do is not that difficult, once it’s been broken down into its constituent parts. There’s plenty of room for lower level engineers to execute and flourish. The grossly simplified perspective of your accountant goes something like this. “Why should we pay $100k for a junior engineer to slow things down, when we could pay $200k for a senior engineer to speed things up?” It makes no sense! But you know and I know—every engineer who is paying attention should know— that’s not how engineering works . This is an apprenticeship industry, and productivity is defined by the output and carrying capacity of each team, not each person. There are lots of ways a person can contribute to the overall velocity of a team, just like there are lots of ways a person can sap the energy out of a team or add friction and drag to everyone around them. These do not always correlate with the person’s level (at least not in the direction people tend to assume), and writing code is only one way. Furthermore, every engineer you hire requires ramp time and investment before they can contribute. Hiring and training new engineers is a costly endeavor, no matter what level they are. It will take any senior engineer time to build up their mental model of the system, familiarize themselves with the tools and technology, and ramp up to speed. How long? It depends on how clean and organized the codebase is, past experience with your tools and technologies, how good you are at onboarding new engineers, and more, but likely around 6-9 months. They probably won’t reach cruising altitude for about a year. Yes, the ramp will be longer for a junior engineer, and yes, it will require more investment from the team. But it’s not indefinite. Your junior engineer should be a net positive within roughly the same time frame, six months to a year, and they develop far more rapidly than more senior contributors. (Don’t forget, their contributions may vastly exceed the code they personally write.) You do not have to be a senior engineer to add value In terms of writing and shipping features, some of the most productive engineers I’ve ever known have been intermediate engineers. Not yet bogged down with all the meetings and curating and mentoring and advising and architecture, their calendars not yet pockmarked with interruptions, they can just build stuff . You see them put their headphones on first thing in the morning, write code all day, and cruise out the door in the evening having made incredible progress. Intermediate engineers sit in this lovely, temporary state where they have gotten good enough at programming to be very productive, but they are still learning how to build and care for systems. All they do is write code, reams and reams of code. And they’re energized…engaged. They’re having fun! They aren’t bored with writing a web form or a login page for the 1000th time. Everything is new, interesting, and exciting, which typically means they will do a better job , especially under the light direction of someone more experienced. Having intermediate engineers on a team is amazing. The only way you get them is by hiring junior engineers. Having junior and intermediate engineers on a team is a shockingly good inoculation against overengineering and premature complexity. They don’t yet know enough about a problem to imagine all the infinite edge cases that need to be solved for. They help keep things simple, which is one of the hardest things to do. The long term arguments for hiring junior engineers If you ask, nearly everybody will wholeheartedly agree that hiring junior engineers is a good thing…and someone else should do it. This is because the long-term arguments for hiring junior engineers are compelling and fairly well understood. We need more senior engineers as an industry Somebody has to train them Junior engineers are cheaper They may add some much-needed diversity They are often very loyal to companies who invest in training them, and will stick around for years instead of job hopping Did we already mention that somebody needs to do it? But long-term thinking is not a thing that companies, or capitalism in general, are typically great at. Framed this way, it makes it sound like you hire junior engineers as a selfless act of public service, at great cost to yourself. Companies are much more likely to want to externalize costs like those, which is how we got to where we are now. The short term arguments for hiring junior engineers However, there are at least as many arguments to be made for hiring junior engineers in the short term—selfish, hard-nosed, profitable reasons for why it benefits the team and the company to do so. You just have to shift your perspective slightly, from individuals to teams, to bring them into focus. Let’s start here: hiring engineers is not a process of “picking the best person for the job”. Hiring engineers is about composing teams . The smallest unit of software ownership is not the individual, it’s the team. Only teams can own, build, and maintain a corpus of software. It is inherently a collaborative, cooperative activity. If hiring engineers was about picking the “best people”, it would make sense to hire the most senior, experienced individual you can get for the money you have, because we are using “senior” and “experienced” as a proxy for “productivity”. (Questionable, but let’s not nitpick.) But the productivity of each individual is not what we should be optimizing for. The productivity of the team is all that matters. And the best teams are always the ones with a diversity of strengths, perspectives, and levels of expertise. A monoculture can be spectacularly successful in the short term—it may even outperform a diverse team. But they do not scale well, and they do not adapt to unfamiliar challenges gracefully. The longer you wait to diversify, the harder it will be. We need to hire junior engineers, and not just once, but consistently. We need to keep feeding the funnel from the bottom up. Junior engineers only stay junior for a couple years, and intermediate engineers turn into senior engineers. Super-senior engineers are not actually the best people to mentor junior engineers; the most effective mentor is usually someone just one level ahead, who vividly remembers what it was like in your shoes. A healthy, high-performing team has a range of levels A healthy team is an ecosystem. You wouldn’t staff a product engineering team with six DB experts and one mobile developer. Nor should you staff it with six staff+ engineers and one junior developer. A good team is composed of a range of skills and levels. Have you ever been on a team packed exclusively with staff or principal engineers? It is not fun . That is not a high-functioning team. There is only so much high-level architecture and planning work to go around, there are only so many big decisions that need to be made. These engineers spend most of their time doing work that feels boring and repetitive, so they tend to over-engineer solutions and/or cut corners—sometimes at the same time. They compete for the “fun” stuff and find reasons to pick technical fights with each other. They chronically under-document and under-invest in the work that makes systems simple and tractable. Teams that only have intermediate engineers (or beginners, or seniors, or whatever) will have different pathologies, but similar problems with contention and blind spots. The work itself has a wide range in complexity and difficulty—from simple, tightly scoped functions to tough, high-stakes architecture decisions. It makes sense for the people doing the work to occupy a similar range. The best teams are ones where no one is bored, because every single person is working on something that challenges them and pushes their boundaries. The only way you can get this is by having a range of skill levels on the team. The bottleneck we face is hiring, not training The bottleneck we face now is not our ability to train up new junior engineers and give them skills. Nor is it about juniors learning to hustle harder; I see a lot of solid , well-meaning advice on this topic, but it’s not going to solve the problem. The bottleneck is giving them their first jobs . The bottleneck consists of companies who see them as a cost to externalize, not an investment in their—the company’s —future. After their first job, an engineer can usually find work. But getting that first job, from what I can see, is murder . It is all but impossible—if you didn’t graduate from a top college, and you aren’t entering the feeder system of Big Tech, then it’s a roll of the dice, a question of luck or who has the best connections. It was rough before the chimera of “Generative AI can replace junior engineers” rose up from the swamp. And now…oof. Where would you be, if you hadn’t gotten into tech when you did? I know where I would be, and it is not here . The internet loves to make fun of Boomers, the generation that famously coasted to college, home ownership, and retirement, then pulled the ladder up after them while mocking younger people as snowflakes. “Ok, Boomer” may be here to stay, but can we try to keep “Ok, Staff Engineer” from becoming a thing? Nobody thinks we need fewer senior engineers Lots of people seem to think we don’t need junior engineers, but nobody is arguing that we need fewer senior engineers, or will need fewer senior engineers in the foreseeable future. I think it’s safe to assume that anything deterministic and automatable will eventually be automated. Software engineering is no different—we are ground zero! Of course we’re always looking for ways to automate and improve efficiency, as we should be. But large software systems are unpredictable and nondeterministic, with emergent behaviors. The mere existence of users injects chaos into the system. Components can be automated, but complexity can only be managed. Even if systems could be fully automated and managed by AI, the fact that we cannot understand how AI makes decisions is a huge, possibly insurmountable problem. Running your business on a system that humans can’t debug or understand seems like a risk so existential that no security, legal or finance team would ever sign off on it. Maybe some version of this future will come to pass, but it’s hard to see it from here. I would not bet my career or my company on it happening. In the meantime, we still need more senior engineers. The only way to grow them is by fixing the funnel. Should every company hire junior engineers? No. You need to be able to set them up for success. Some factors that disqualify you from hiring junior engineers: You have less than two years of runway Your team is constantly in firefighting mode, or you have no slack in your system You have no experienced managers, or you have bad managers, or no managers at all You have no product roadmap Nobody on your team has any interest in being their mentor or point person The only thing worse than never hiring any junior engineers is hiring them into an awful experience where they can’t learn anything. (I wouldn’t set the bar quite as high as Cindy does in this article ; while I understand where she’s coming from, it is so much easier to land your second job than your first job that I think most junior engineers would frankly choose a crappy first job over none at all.) Being a fully distributed company isn’t a complete dealbreaker, but it does make things even harder. I would counsel junior engineers to seek out office jobs if at all possible. You learn so much faster when you can soak up casual conversations and technical chatter, and you lose that working from home. If you are a remote employer, know that you will need to work harder to compensate for this. I suggest connecting with others who have done this successfully (they exist!) for advice. I also advise companies not to start by hiring a single junior engineer. If you’re going to hire one, hire two or three. Give them a cohort of peers, so it’s a little less intimidating and isolating. Nobody is coming to fix our problems for us I have come to believe that the only way this will ever change is if engineers and engineering managers across our industry take up this fight and make it personal. Most of the places I know that do have a program for hiring and training entry level engineers, have it only because an engineer decided to fight for it. Engineers—sometimes engineering managers—were the ones who made the case and pushed for resources, then designed the program, interviewed and hired the junior engineers, and set them up with mentors. This is not an exotic project, it is well within the capabilities of most motivated, experienced engineers (and good for your career as well). Finance isn’t going to lobby for this. Execs aren’t likely to step in. The more a person’s role inclines them to treat engineers like fungible resources, the less likely they are to understand why this matters. AI is not coming to solve all our problems and write all our code for us—and even if it was , it wouldn’t matter . Writing code is but a sliver of what professional software engineers do, and arguably the easiest part. Only we have the context and the credibility to drive the changes we know form the bedrock for great teams and engineering excellence.. Great teams are how great engineers get made. Nobody knows this better than engineers and EMs. It’s time for us to make the case, and make it happen. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Charity Majors Charity is the cofounder and CTO of honeycomb.io, the leader in observability for complex software systems. She has worked as an ops engineer and engineering manager at Parse, Facebook, Linden Lab, and others, and is … generative AI Engineering coding Business Hub contributed Never miss out! Stay in the loop with fresh business content delivered straight to your inbox. Keep me updated Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://developer.x.com/developer-terms/policy#4-e | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://stackoverflow.blog/automation/ | automation - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. automation Related Tags AI generative AI testing developer tools Partner Content partnercontent Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed December 8, 2025 The shift in enterprise AI—what we learned on the floor at Microsoft Ignite There's a distinct shift in how enterprises are talking about their AI solutions. Speed and flashiness are giving way to steadier, slower, more focused AI strategies for companies, where market fit and proof points are more important than ever. Phoebe Sajor 1 comment AI software engineering automation agentic AI microsoft June 25, 2025 Not an option, but a necessity: How organizations are adopting and implementing AI internally AI is no longer just a luxury for the most tech savvy companies — it's now a necessity for organizational transformation. How are real teams successfully leveraging and innovating with these new tools? Phoebe Sajor 1 comment Business Hub AI automation workflow automation agentic AI Productivity June 24, 2025 How to build your prototypes without a 35% tariff Ryan and Ben welcome Alex Malcoci, CEO and founder of MiniProto, to talk innovations in hardware prototyping, the evolving complexities of the global supply chain, the impact of the US-China trade war on manufacturing, and how automation in production could lead to new training programs for future engineers. Phoebe Sajor 1 comment rapid prototyping supply chain The Stack Overflow Podcast hardware product automation infrastructure management April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Scott McCarty 10 comment s automation devops AI contributed February 24, 2025 Writing tests with AI, but not LLMs How Diffblue leverages machine learning techniques to write effective unit tests. Eira May 0 comment s The Stack Overflow Podcast software development software engineering AI generative AI autonomous agents automation unit tests testing java refactoring Productivity llm copilot ai coding dev tools developer tools February 11, 2025 “In the short term, more chaos”: What’s next for API design Sagar Batchu, CEO and cofounder of API tooling company Speakeasy, talks with Ryan about the evolving API landscape, AI integration, the role of human technologists in an increasingly automated environment, and what people building APIs right now should keep in mind. Eira May 0 comment s The Stack Overflow Podcast AI API software development generative AI workflow automation automation developer tools tooling February 10, 2025 Shifting left without slowing down: Q&A with Moti Gindi of Apiiro Can an org automate security, change its culture to up their dev velocity, and stave off burnout? Ryan Donovan 0 comment s security automation development velocity Q&A January 3, 2025 How AI apps are like Google Search Happy New Year! In this episode, Ryan talks with Jetify founder and CEO Daniel Loreto, a former engineering lead at Google and Twitter, about what AI applications have in common with Google Search. They also discuss the challenges inherent in developing AI systems, why a data-driven approach to AI development is important, the implications of non-determinism, and the future of test automation. Eira May 0 comment s The Stack Overflow Podcast AI generative AI developer tools google search environments testing automation May 24, 2024 Would you board a plane safety-tested by GenAI? Ben and Ryan are joined by Robin Gupta for a conversation about benchmarking and testing AI systems. They talk through the lack of trust and confidence in AI, the inherent challenges of nondeterministic systems, the role of human verification, and whether we can (or should) expect an AI to be reliable. Eira May 20 comment s The Stack Overflow Podcast AI generative AI testing automation August 2, 2023 How engineering teams at a large org can move at startup speed On this sponsored episode of the podcast, Ben talks with Amber Webb, Principal Engineer at Shell, and Naresh Kumar, Senior Principal Engineer at Shell, about their hyper automation initiative, which locates organization-level bottlenecks and removes them. Ryan Donovan 2 comment s Sponsored automation Partner Content Partner Content partnercontent the stack overflow podcast The Stack Overflow Podcast June 23, 2023 Throwing away the script on testing (Ep. 583) Syed Hamid, founder and CEO of no-code test automation platform Sofy, joins Ben and Ryan to talk about scriptless automation, why his platform targets mobile app developers, and what he learned in nearly two decades at Microsoft. Eira May 0 comment s AI application testing automation mobile development no code testing The Stack Overflow Podcast the stack overflow podcast March 7, 2023 “Move fast and break things” doesn’t apply to other people’s savings (Ep. 545) Christine Ryu, Engineering Lead at fintech platform Flourish, joins the home team to talk about how technology is transforming finance for everyone from big banks to individual consumers. Christine explains what it’s like to move from Goldman Sachs to a tiny startup, how legacy tech stacks lead to Frankencode, and what an acquisition taught her about build vs. buy and good vs. perfect. Eira May 3 comment s automation fintech The Stack Overflow Podcast October 14, 2022 The robots are coming… but when? (Ep 497) A new platform promises to make building a robot as easy as crafting a smartphone app. Ritika Puri 2 comment s automation mongodb robotics The Stack Overflow Podcast Viam July 25, 2022 Automate the boring parts of your job Turns out the robots are here to make your job more interesting. Oana Chicioroaga 10 comment s automation Code for a Living Partner Content Partner Content partnercontent robotic process automation June 16, 2022 Privacy is a moving target. Here’s how engineering teams can stay on track (Ep. 453) On this sponsored episode of the podcast, we talk with Rob Picard and Matt Cooper of Vanta. Ryan Donovan 0 comment s automation Partner Content Partner Content partnercontent privacy the stack overflow podcast The Stack Overflow Podcast Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://www.apple.com/newsroom/2022/05/apple-google-and-microsoft-commit-to-expanded-support-for-fido-standard/ | Apple, Google, and Microsoft commit to expanded support for FIDO standard - Apple Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + Newsroom Open Newsroom navigation Close Newsroom navigation Apple Services Apple Stories Search Newsroom Close opens in new window PRESS RELEASE May 5, 2022 Apple, Google, and Microsoft commit to expanded support for FIDO standard to accelerate availability of passwordless sign‑ins Faster, easier, and more secure sign‑ins will be available to consumers across leading devices and platforms Mountain View, California In a joint effort to make the web more secure and usable for all, Apple, Google, and Microsoft today announced plans to expand support for a common passwordless sign-in standard created by the FIDO Alliance and the World Wide Web Consortium. The new capability will allow websites and apps to offer consistent, secure, and easy passwordless sign-ins to consumers across devices and platforms. Password-only authentication is one of the biggest security problems on the web, and managing so many passwords is cumbersome for consumers, which often leads consumers to reuse the same ones across services. This practice can lead to costly account takeovers, data breaches, and even stolen identities. While password managers and legacy forms of two-factor authentication offer incremental improvements, there has been industry-wide collaboration to create sign-in technology that is more convenient and more secure. The expanded standards-based capabilities will give websites and apps the ability to offer an end-to-end passwordless option. Users will sign in through the same action that they take multiple times each day to unlock their devices, such as a simple verification of their fingerprint or face, or a device PIN. This new approach protects against phishing and sign-in will be radically more secure when compared to passwords and legacy multi-factor technologies such as one-time passcodes sent over SMS. An Expansion of Passwordless Standard Support Hundreds of technology companies and service providers from around the world worked within the FIDO Alliance and W3C to create the passwordless sign-in standards that are already supported in billions of devices and all modern web browsers. Apple, Google, and Microsoft have led development of this expanded set of capabilities and are now building support into their respective platforms. These companies’ platforms already support FIDO Alliance standards to enable passwordless sign-in on billions of industry-leading devices, but previous implementations require users to sign in to each website or app with each device before they can use passwordless functionality. Today’s announcement extends these platform implementations to give users two new capabilities for more seamless and secure passwordless sign-ins: Allow users to automatically access their FIDO sign-in credentials (referred to by some as a “passkey”) on many of their devices, even new ones, without having to reenroll every account. Enable users to use FIDO authentication on their mobile device to sign in to an app or website on a nearby device, regardless of the OS platform or browser they are running. In addition to facilitating a better user experience, the broad support of this standards-based approach will enable service providers to offer FIDO credentials without needing passwords as an alternative sign-in or account recovery method. These new capabilities are expected to become available across Apple, Google, and Microsoft platforms over the course of the coming year. “‘Simpler, stronger authentication’ is not just FIDO Alliance’s tagline — it also has been a guiding principle for our specifications and deployment guidelines. Ubiquity and usability are critical to seeing multi-factor authentication adopted at scale, and we applaud Apple, Google, and Microsoft for helping make this objective a reality by committing to support this user-friendly innovation in their platforms and products,” said Andrew Shikiar, executive director and CMO of the FIDO Alliance. “This new capability stands to usher in a new wave of low-friction FIDO implementations alongside the ongoing and growing utilization of security keys — giving service providers a full range of options for deploying modern, phishing-resistant authentication.” “The standards developed by the FIDO Alliance and World Wide Web Consortium and being led in practice by these innovative companies is the type of forward-leaning thinking that will ultimately keep the American people safer online. I applaud the commitment of our private sector partners to open standards that add flexibility for the service providers and a better user experience for customers,” said Jen Easterly, Director of the U.S. Cybersecurity and Infrastructure Security Agency. “At CISA, we are working to raise the cybersecurity baseline for all Americans. Today is an important milestone in the security journey to encourage built-in security best practices and help us move beyond passwords. Cyber is a team sport, and we’re pleased to continue our collaboration.” “Just as we design our products to be intuitive and capable, we also design them to be private and secure,” said Kurt Knight, Apple’s Senior Director of Platform Product Marketing. “Working with the industry to establish new, more secure sign-in methods that offer better protection and eliminate the vulnerabilities of passwords is central to our commitment to building products that offer maximum security and a transparent user experience — all with the goal of keeping users’ personal information safe.” “This milestone is a testament to the collaborative work being done across the industry to increase protection and eliminate outdated password-based authentication,” said Mark Risher, Senior Director of Product Management, Google. “For Google, it represents nearly a decade of work we’ve done alongside FIDO, as part of our continued innovation towards a passwordless future. We look forward to making FIDO-based technology available across Chrome, ChromeOS, Android and other platforms, and encourage app and website developers to adopt it, so people around the world can safely move away from the risk and hassle of passwords.” “The complete shift to a passwordless world will begin with consumers making it a natural part of their lives. Any viable solution must be safer, easier, and faster than the passwords and legacy multi-factor authentication methods used today,” says Alex Simons, Corporate Vice President, Identity Program Management at Microsoft. “By working together as a community across platforms, we can at last achieve this vision and make significant progress toward eliminating passwords. We see a bright future for FIDO-based credentials in both consumer and enterprise scenarios and will continue to build support across Microsoft apps and services.” Share article Media Text of this article May 5, 2022 PRESS RELEASE Apple, Google, and Microsoft commit to expanded support for FIDO standard to accelerate availability of passwordless sign‑ins Faster, easier, and more secure sign‑ins will be available to consumers across leading devices and platforms Mountain View, California In a joint effort to make the web more secure and usable for all, Apple, Google, and Microsoft today announced plans to expand support for a common passwordless sign-in standard created by the FIDO Alliance and the World Wide Web Consortium. The new capability will allow websites and apps to offer consistent, secure, and easy passwordless sign-ins to consumers across devices and platforms. Password-only authentication is one of the biggest security problems on the web, and managing so many passwords is cumbersome for consumers, which often leads consumers to reuse the same ones across services. This practice can lead to costly account takeovers, data breaches, and even stolen identities. While password managers and legacy forms of two-factor authentication offer incremental improvements, there has been industry-wide collaboration to create sign-in technology that is more convenient and more secure. The expanded standards-based capabilities will give websites and apps the ability to offer an end-to-end passwordless option. Users will sign in through the same action that they take multiple times each day to unlock their devices, such as a simple verification of their fingerprint or face, or a device PIN. This new approach protects against phishing and sign-in will be radically more secure when compared to passwords and legacy multi-factor technologies such as one-time passcodes sent over SMS. An Expansion of Passwordless Standard Support Hundreds of technology companies and service providers from around the world worked within the FIDO Alliance and W3C to create the passwordless sign-in standards that are already supported in billions of devices and all modern web browsers. Apple, Google, and Microsoft have led development of this expanded set of capabilities and are now building support into their respective platforms. These companies’ platforms already support FIDO Alliance standards to enable passwordless sign-in on billions of industry-leading devices, but previous implementations require users to sign in to each website or app with each device before they can use passwordless functionality. Today’s announcement extends these platform implementations to give users two new capabilities for more seamless and secure passwordless sign-ins: Allow users to automatically access their FIDO sign-in credentials (referred to by some as a “passkey”) on many of their devices, even new ones, without having to reenroll every account. Enable users to use FIDO authentication on their mobile device to sign in to an app or website on a nearby device, regardless of the OS platform or browser they are running. In addition to facilitating a better user experience, the broad support of this standards-based approach will enable service providers to offer FIDO credentials without needing passwords as an alternative sign-in or account recovery method. These new capabilities are expected to become available across Apple, Google, and Microsoft platforms over the course of the coming year. “‘Simpler, stronger authentication’ is not just FIDO Alliance’s tagline — it also has been a guiding principle for our specifications and deployment guidelines. Ubiquity and usability are critical to seeing multi-factor authentication adopted at scale, and we applaud Apple, Google, and Microsoft for helping make this objective a reality by committing to support this user-friendly innovation in their platforms and products,” said Andrew Shikiar, executive director and CMO of the FIDO Alliance. “This new capability stands to usher in a new wave of low-friction FIDO implementations alongside the ongoing and growing utilization of security keys — giving service providers a full range of options for deploying modern, phishing-resistant authentication.” “The standards developed by the FIDO Alliance and World Wide Web Consortium and being led in practice by these innovative companies is the type of forward-leaning thinking that will ultimately keep the American people safer online. I applaud the commitment of our private sector partners to open standards that add flexibility for the service providers and a better user experience for customers,” said Jen Easterly, Director of the U.S. Cybersecurity and Infrastructure Security Agency. “At CISA, we are working to raise the cybersecurity baseline for all Americans. Today is an important milestone in the security journey to encourage built-in security best practices and help us move beyond passwords. Cyber is a team sport, and we’re pleased to continue our collaboration.” “Just as we design our products to be intuitive and capable, we also design them to be private and secure,” said Kurt Knight, Apple’s Senior Director of Platform Product Marketing. “Working with the industry to establish new, more secure sign-in methods that offer better protection and eliminate the vulnerabilities of passwords is central to our commitment to building products that offer maximum security and a transparent user experience — all with the goal of keeping users’ personal information safe.” “This milestone is a testament to the collaborative work being done across the industry to increase protection and eliminate outdated password-based authentication,” said Mark Risher, Senior Director of Product Management, Google. “For Google, it represents nearly a decade of work we’ve done alongside FIDO, as part of our continued innovation towards a passwordless future. We look forward to making FIDO-based technology available across Chrome, ChromeOS, Android and other platforms, and encourage app and website developers to adopt it, so people around the world can safely move away from the risk and hassle of passwords.” “The complete shift to a passwordless world will begin with consumers making it a natural part of their lives. Any viable solution must be safer, easier, and faster than the passwords and legacy multi-factor authentication methods used today,” says Alex Simons, Corporate Vice President, Identity Program Management at Microsoft. “By working together as a community across platforms, we can at last achieve this vision and make significant progress toward eliminating passwords. We see a bright future for FIDO-based credentials in both consumer and enterprise scenarios and will continue to build support across Microsoft apps and services.” About the FIDO Alliance The FIDO (Fast IDentity Online) Alliance, www.fidoalliance.org , was formed in July 2012 to address the lack of interoperability among strong authentication technologies, and remedy the problems users face with creating and remembering multiple usernames and passwords. The FIDO Alliance is changing the nature of authentication with standards for simpler, stronger authentication that define an open, scalable, interoperable set of mechanisms that reduce reliance on passwords. FIDO Authentication is stronger, private, and easier to use when authenticating to online services. About Apple Apple revolutionized personal technology with the introduction of the Macintosh in 1984. Today, Apple leads the world in innovation with iPhone, iPad, Mac, Apple Watch, and Apple TV. Apple’s five software platforms — iOS, iPadOS, macOS, watchOS, and tvOS — provide seamless experiences across all Apple devices and empower people with breakthrough services including the App Store, Apple Music, Apple Pay, and iCloud. Apple’s more than 100,000 employees are dedicated to making the best products on earth, and to leaving the world better than we found it. About Google Google’s mission is to organize the world’s information and make it universally accessible and useful. Through products and platforms like Search, Maps, Gmail, Android, Google Play, Google Cloud, Chrome, and YouTube, Google plays a meaningful role in the daily lives of billions of people and has become one of the most widely-known companies in the world. Google is a subsidiary of Alphabet Inc. About Microsoft Microsoft (Nasdaq “MSFT” @microsoft) enables digital transformation for the era of an intelligent cloud and an intelligent edge. Its mission is to empower every person and every organization on the planet to achieve more. Press Contacts Apple Media Helpline media.help@apple.com Apple Media Helpline media.uk@apple.com Copy text About the FIDO Alliance The FIDO (Fast IDentity Online) Alliance, www.fidoalliance.org , was formed in July 2012 to address the lack of interoperability among strong authentication technologies, and remedy the problems users face with creating and remembering multiple usernames and passwords. The FIDO Alliance is changing the nature of authentication with standards for simpler, stronger authentication that define an open, scalable, interoperable set of mechanisms that reduce reliance on passwords. FIDO Authentication is stronger, private, and easier to use when authenticating to online services. About Apple Apple revolutionized personal technology with the introduction of the Macintosh in 1984. Today, Apple leads the world in innovation with iPhone, iPad, Mac, Apple Watch, and Apple TV. Apple’s five software platforms — iOS, iPadOS, macOS, watchOS, and tvOS — provide seamless experiences across all Apple devices and empower people with breakthrough services including the App Store, Apple Music, Apple Pay, and iCloud. Apple’s more than 100,000 employees are dedicated to making the best products on earth, and to leaving the world better than we found it. About Google Google’s mission is to organize the world’s information and make it universally accessible and useful. Through products and platforms like Search, Maps, Gmail, Android, Google Play, Google Cloud, Chrome, and YouTube, Google plays a meaningful role in the daily lives of billions of people and has become one of the most widely-known companies in the world. Google is a subsidiary of Alphabet Inc. About Microsoft Microsoft (Nasdaq “MSFT” @microsoft) enables digital transformation for the era of an intelligent cloud and an intelligent edge. Its mission is to empower every person and every organization on the planet to achieve more. Press Contacts Apple Media Helpline media.help@apple.com Apple Media Helpline media.uk@apple.com More from Apple Newsroom UPDATE 2025 marked a record-breaking year for Apple services January 12, 2026 UPDATE Chase to become new issuer of Apple Card January 7, 2026 UPDATE Spectrum Front Row tips off January 9 on Apple Vision Pro January 5, 2026 Apple Newsroom The latest news and updates, direct from Apple. Read more Stay up to date with the latest articles from Apple Newsroom. Dismiss Get Notifications Apple Footer Apple Newsroom Apple, Google, and Microsoft commit to expanded support for FIDO standard Shop and Learn Shop and Learn Store Mac iPad iPhone Watch Vision AirPods TV & Home AirTag Accessories Gift Cards Apple Wallet Apple Wallet Wallet Apple Card Apple Pay Apple Cash Account Account Manage Your Apple Account Apple Store Account iCloud.com Entertainment Entertainment Apple One Apple TV Apple Music Apple Arcade Apple Fitness+ Apple News+ Apple Podcasts Apple Books App Store Apple Store Apple Store Find a Store Genius Bar Today at Apple Group Reservations Apple Camp Apple Store App Certified Refurbished Apple Trade In Financing Carrier Deals at Apple Order Status Shopping Help For Business For Business Apple and Business Shop for Business For Education For Education Apple and Education Shop for K-12 Shop for College For Healthcare For Healthcare Apple and Healthcare For Government For Government Apple and Government Shop for Veterans and Military Shop for State and Local Employees Shop for Federal Employees Apple Values Apple Values Accessibility Education Environment Inclusion and Diversity Privacy Racial Equity and Justice Supply Chain Innovation About Apple About Apple Newsroom Apple Leadership Career Opportunities Investors Ethics & Compliance Events Contact Apple More ways to shop: Find an Apple Store or other retailer near you. Or call 1-800-MY-APPLE (1-800-692-7753). United States Español Copyright © 2026 Apple Inc. All rights reserved. Privacy Policy Terms of Use Sales and Refunds Legal Site Map | 2026-01-13T08:48:30 |
https://stackoverflow.blog/2025/04/14/like-self-driving-cars-fully-ai-automated-sysadmins-don-t-exist/ | Like self-driving cars, fully AI-automated sysadmins don't exist - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. April 14, 2025 Like self-driving cars, fully AI-automated sysadmins don't exist As with cars, there are few system administration tasks that involve little to no automation. Credit: Alexandra Francis The Society of Automotive Engineers has defined six levels of autonomous driving, ranging from Level 0—where the driver is responsible for everything—to Level 5—where a car performs all driving tasks under any conditions from Point A to Point B. The same spectrum can be used with system administration tasks to determine where and to what extent AI should be leveraged. If we apply the SAE’s levels to system administration tasks, it would look something like this: Level 0: No Automation Level 1: Assistance Required Level 2: Partial Automation Level 3: Conditional Automation Level 4: High Automation Level 5: Full Automation I thought about the sysadmin tasks ripest for AI-based automation and leveled them based on this spectrum. It’s important to note that all of this is a snapshot in time. As AI technology matures—and organizations’ comfort level with AI increases—what’s a Level 2 today may be a Level 3 or 4 tomorrow. It stands to reason, but none of the tasks I focused on landed at Level 0 or Level 1. As with cars, there are few system administration tasks that involve little to no automation. You could say something like racking servers and unraveling cables, but AI will never help detangle a Clark Griswold-level cable ball. You’ll also notice that there are no Level 5 tasks—yet. (More on that later.) I’m open to discussion and even argument on what I’ve come up with. I would also be really interested to hear how sysadmins would categorize these and other functions, as well as how they see the sysadmin role changing as AI matures. Level 2 System shutdown: In the traditional world, this could be a server shutdown, but in a modern, cloud-native world, it could be the shutdown of a critical application, load balanced across thousands of containers which run on hundreds of worker nodes. Either way, a human needs to be involved at a high level. There are a variety of reasons for initiating a shutdown, but humans should always be the ones driving them. At most, system shutdown should be Level 2 on the autonomy scale. AI can help suss out behavior anomalies or security threats. A “driver” assistance might prompt: “Are you really sure you want to shut that down?” “I noticed a couple of containers didn’t shut down correctly and were still serving traffic” “A critical task is hanging, and data hasn't been flushed to disk, so shutting down now could cause database corruption” Sort of like lane keeping. AI has the potential to really enlighten the user about the subtasks that are happening, and what their status is, in a completely new and transparent way. But the decision to initiate a shutdown should come only after a human has verified an issue and authorized defensive actions — feet on gas and brakes, if you will. Repairing system issues: Using AI to diagnose issues and then automatically fix those issues is a promising use case, but still a Level 2. I’ve had conversations with colleagues who used agentic AI to determine whether a set of pods in Kubernetes was healthy and recommend tools to use to fix them if they weren’t. At this point, we’re staying away from automatic fixes because the prospect is a little bit terrifying, but it’s something we may see in the future. If you basically control the inputs and the outputs—for example, saying, “Here's a set of tools you can use, and here are the things you can do with them”—AI is really good at figuring it all out. These capabilities could eventually be used to support safe automatic repairs, but might require some modifications to existing utilities. Level 3 Powering shells: Language models are being integrated into shells and CLIs , enabling users to enter natural-language commands rather than the cryptic shell commands that have been developed organically during the last 30 or 40 years—and that are very difficult to remember, much less understand . In this case, the commands are driving the operating system, but sysadmins need to keep their feet poised over the gas and the brake to ensure that telling an OS to copy a file or directory doesn’t result in, say, the deletion of a file or directory. With all that said, I’m giving this a Level 3 designation because we are starting to experiment with asking AI to make changes to the shell that currently require searching the web to find weird strings of characters that you copy and paste (and then pray will work). We’ve seen it work in simple use cases, but you still need a human in the loop—with the ability to take control at any time. Log analysis: Log analysis is tedious and tiring—like driving six hours on a freeway. Log data is essentially free form, natural language. Taking humans completely out of the log analysis process would be irresponsible, but we can use generative AI to reduce the cognitive load massively, say, 80-90%. For example, sysadmins could use generative AI to summarize a million lines of log data to a couple of sentences. Or, a sysadmin might analyze the log data using RAG, and ask interactive questions until they get the answer they're looking for, say, the cause of a problem they're seeing. This might be used in the future to comply with regulations which require “reading the logs.” But, a human still needs to evaluate the data and make decisions on what actions to take, which I’d say puts this use case at Level 3. Level 4 Generating config files: Generating config files is natural language processing, and natural language processing is something that AI innately does really well—a Level 4 task if ever there was one, especially when you constrain the inputs and outputs. In fact, I would say that generating config files is the same as asking AI to translate a sentence from Spanish to English or even to generate an original story with the theme of man vs. machine. But, while humans might want to write a poem, they probably don't want to manually generate config files. Using a language model to perform the task is a huge time saver that can potentially trim hundreds of human work hours down to just a few. With that said, humans must review and validate files to ensure that they, for example, address organization-specific factors or comply with industry standards. Humans also need to make sure config files are documented to help avoid problems with future translation. Updating config files: Updating config files is another tedious job that no one wants to do—the perfect candidate for generative AI and one that can be performed almost 100% autonomously. Almost. Sysadmins shouldn’t completely rely on AI to determine what config options have been deprecated and what new ones are in place—they must be the final arbiter of what’s OK and what’s not. However, a machine learning model can provide support along the way and is about as close to hands-off “driving” as sysadmins can get at this time. Put it this way: On a good day, when skies are clear and the road is straight, sysadmins could use AI to update (or generate) config files without putting their hands on the wheel, gas, or brake. But on a bad day, when you're driving up a mountain, in a snow storm, and need to swerve to avoid a deer deciding which side of the road he is going to run toward, sysadmins need to be fully back in the driver’s seat. Providing peer perspective: This one might not do much for sysadmins’ social pragmatic skills, but it can be done with little human interaction. Want to find out how peers have handled a certain challenge or the criteria they have used to evaluate a certain type of technology? Where sysadmins may have reached out to their human connections in the past, they can now enter any scenario they need help with into a generative AI tool and get loads of advice, anecdotes, stories, examples, and directions. However, just as when you have a conversation with a human, you have to consider the source—and biases and potential for hallucination—when you “talk” to AI. To be fair, in years past, I've been extremely frustrated with the guidance my colleagues have given me, so mileage may vary. Conclusion Level 5 is not possible with cars today, but there are times when Level 4 is achievable—under certain conditions. I wouldn’t put that much trust in autonomous driving during a blinding snowstorm or on a mountain road with hairpin turns, but I might on a sunny day driving along a long lonesome highway in a desert in Arizona. The same is true for system administration tasks. The extent to which AI can support sysadmin tasks is increasing quickly. But, in the end, the most powerful tool in a sysadmin's arsenal isn't AI—it's the combination of AI and human expertise. And that will likely always be the case. Interested in contributing? Submit an idea for an article and we may reach out to you in the future. Login with your stackoverflow.com account to suggest an article. Author s Scott McCarty Global - Senior Principal Product Manager, Red Hat Enterprise Linux automation devops AI contributed Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#jwt-tokens-are-awesome-but-how-do-you-store-them-securely-in-your-frontend-well-go-over-the-pros-and-cons-of-localstorage-and-cookies | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://support.apple.com/ro-ro/105082 | Ștergerea istoricului, a memoriei cache și a modulelor cookie din Safari pe iPhone - Apple Support (RO) Apple Mac iPad iPhone Watch AirPods Divertisment Asistență De unde cumperi Ștergerea istoricului, a memoriei cache și a modulelor cookie din Safari pe iPhone În configurările dispozitivului iPhone, poți alege să ștergi istoricul, modulele cookie, memoria cache sau un anumit site web din istoricul Safari. De asemenea, poți activa sisteme de blocare a conținutului. Ștergerea istoricului, a memoriei cache și a modulelor cookie Ștergerea modulelor cookie și a memoriei cache, dar păstrarea istoricului Ștergerea unui site web din istoric Blocarea cookie-urilor Utilizarea sistemelor de blocare a conținutului Ștergerea istoricului, a memoriei cache și a modulelor cookie Accesează Configurări > Aplicații > Safari. Derulează în jos și atinge Degajați istoricul și datele site‑urilor. Confirmă perioada de timp pe care dorești să o degajezi, apoi atinge Degajați istoricul. Această acțiune nu schimbă informațiile de auto-completare. Dacă acest buton este gri, este posibil să nu existe date de șters sau să fie necesar să verifici restricțiile privind conținutul web în Timp de utilizare . Ștergerea modulelor cookie și a memoriei cache, dar păstrarea istoricului Accesează Configurări > Aplicații > Safari > Avansat > Date site-uri web. Atinge Eliminare integrală date site‑uri web. Dacă acest buton este gri, este posibil să nu existe date de șters sau să fie necesar să verifici restricțiile privind conținutul web în Timp de utilizare . Atinge Eliminați acum. Acest lucru șterge datele folosite pentru urmărire și folosite de site-uri web pentru a salva informațiile de autentificare, pentru o navigare mai rapidă. Ștergerea unui site web din istoric Deschide aplicația Safari, apoi atinge butonul Mai multe . Atinge Marcaje. Atinge butonul Istoric , apoi atinge butonul Mai multe din nou. Atinge Selectați site-uri web, apoi selectează unul sau mai multe site-uri web pe care vrei să le ștergi din istoric. Atinge butonul Coș de gunoi . Blocarea modulelor cookie Dacă vrei să blochezi modulele cookie (datele pe care un site le plasează pe dispozitivul tău pentru a te recunoaște), accesează Configurări > Aplicații > Safari > Avansat. Activează opțiunea Blocare completă cookie-uri. Atinge Blocați tot. Acest lucru elimină toate modulele cookie și datele site-urilor web existente. Safari se închide, iar filele tale sunt reîncărcate. Dacă blochezi modulele cookie, este posibil ca unele pagini web să nu funcționeze. Iată câteva exemple: Este posibil să nu poți să te autentifici pe un site, chiar și atunci când utilizezi numele de utilizator și parola corecte. Este posibil să vezi un mesaj care te informează că modulele cookie sunt necesare sau că acestea sunt dezactivate în browser. Este posibil ca unele caracteristici ale site-ului să nu funcționeze. Utilizarea sistemelor de blocare a conținutului Accesează App Store și descarcă o aplicație de blocare a conținutului (aplicații și extensii terțe care permit Safari să blocheze modulele cookie, imaginile, resursele, ferestrele pop-up și alte tipuri de conținut). Atinge Configurări > Aplicații > Safari > Extensii. Atinge pentru a activa un sistem de blocare a conținutului afișat. Poți utiliza mai multe sisteme de blocare a conținutului. Dacă ai nevoie de ajutor, contactează dezvoltatorul aplicației . Informațiile despre produsele care nu sunt fabricate de Apple sau despre site-urile web independente care nu sunt controlate sau testate de Apple sunt furnizate fără recomandare sau aprobare. Apple nu își asumă nicio responsabilitate în ceea ce privește selectarea, funcționarea sau utilizarea site-urilor web sau produselor de la terți. Apple nu face niciun fel de declarații privind acuratețea sau fiabilitatea site-urilor web terțe. Contactează furnizorul acestor produse pentru a obține mai multe informații. Data publicării: 24 septembrie 2025 Util? Da Nu Limită de caractere: 250 Limita maximă de caractere este de 250. Te rugăm să nu incluzi informații personale în comentariul tău. Trimitere Îți mulțumim pentru feedback. Subiecte corelate Apple Footer Apple Asistență Ștergerea istoricului, a memoriei cache și a modulelor cookie din Safari pe iPhone România Copyright © 2025 Apple Inc. Toate drepturile rezervate. Condiţii de utilizare Hartă site Utilizarea cookie-urilor | 2026-01-13T08:48:30 |
https://www.atlassian.com/legal/privacy-policy#what-this-policy-covers | Privacy Policy | Atlassian Close View this page in your language ? All languages Choose your language 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Get it free Products Featured Developers Product Managers IT professionals Business Teams Leadership Teams Featured Developers Product Managers IT professionals Business Teams Leadership Teams See all apps Featured FEATURED APPS Jira Flexible project management Confluence Collaborative knowledge workspace Jira Service Management High-velocity service delivery ATLASSIAN COLLECTIONS Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Optimize strategy and outcomes confidently Focus • Talent • Align Deliver service at high-velocity Jira Service Management • Customer Service Management • Assets • Rovo Ship high-quality software fast Rovo Dev • DX • Pipelines • Bitbucket • Compass POWERED BY Rovo AI-powered apps – driven by your team's knowledge. Developers Jira Flexible project management Compass Software catalog for teams Pipelines Scalable CI/CD automation Bitbucket Source code and CI/CD DX Measure productivity and AI impact Rovo Dev Agentic AI for developers Ship high-quality software fast Rovo Dev • DX • Pipelines • Bitbucket • Compass Rovo AI-powered apps – driven by your team's knowledge. Product Managers Jira Flexible project management Confluence Knowledge, all in one place Jira Product Discovery Capture & prioritize ideas Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Rovo AI-powered apps – driven by your team's knowledge. IT professionals Jira Service Management High-velocity service delivery Guard Enhanced cloud security Rovo AI-powered apps – driven by your team's knowledge. Business Teams Jira Flexible project management Confluence Knowledge, all in one place Trello Organized & visualized work Loom Quick, async video updates Jira Service Management High-velocity service delivery Customer Service Management Customer experiences reimagined Supercharge teamwork seamlessly Jira • Confluence • Loom • Rovo Rovo AI-powered apps – driven by your team's knowledge. Leadership Teams Focus Enterprise-scale strategic planning Talent Knowledge workforce planning Jira Align Enterprise-wide work planning & value Optimize strategy and outcomes confidently Focus • Talent • Align Rovo AI-powered apps – driven by your team's knowledge. Back Solutions Solutions By use case Team collaboration Strategy and planning Service management Software development By team Software Marketing IT By size Enterprise Small business Startup Non-profit By industry Retail Telecommunications Professional services Government Rovo AI-powered apps – driven by your team's knowledge. Back Why Atlassian Why Atlassian System of Work New Atlassian's blueprint for how teams work together Integrations Connect thousands of apps to your Atlassian products Customers Case studies & stories powered by teamwork FedRAMP Compliant solutions for the public sector Resilience Enterprise-grade & highly performant infrastructure Platform Our deeply integrated, reliable & secure platform Trust center Ensure your data’s security, compliance & availability Back Resources Resources Customer Support Ask questions, report bugs & give us feedback Find Partners Consulting, training & product customization support Atlassian Ascend Resources and support for your transformation Community Learn, connect and grow with the Atlassian Community support General inquiries Product Advice Partner support Enterprise support Technical Support Pricing and Billing Developer support Purchasing & Licensing Resources Project Management Agile Atlassian Learning Get Started Project Collaboration Team Playbook Product Documentation Back Enterprise More + Less - Get it free Jira Flexible project management Jira Service Management High-velocity service delivery Confluence Knowledge, all in one place See all products Get it free Back Get it free Legal Legal information Privacy Policy Privacy Policy Privacy Policy Effective starting: October 7, 2025 Your privacy matters to us. This privacy policy explains how Atlassian Pty Ltd, Atlassian US, Inc. and our corporate affiliates (“Atlassian”, “we”, “us”, “our”) collect, use, share, and protect your information when you use our products, services, websites, or otherwise interact with us (a list of Atlassian’s corporate affiliates can be found in the List of Subsidiaries section of Atlassian’s most recent Form 10-K, available under the SEC Filings tab by selecting the “Annual Filings” filter on the page located here ). We offer a wide range of products, including our cloud and software products. We refer to all of these products, together with our other services and websites, as "Services" in this privacy policy. This privacy policy also explains your choices surrounding how we use information about you, which includes how you can object to certain uses of information about you and how you can access and update certain information about you. If you do not agree with this privacy policy, do not access or use our Services or interact with any other aspect of our business. For individuals in the European Economic Area, United Kingdom, or the United States: please refer to the appropriate “ Regional disclosures ” for additional details that may be relevant to you. This privacy policy is intended to help you understand: Information we collect How we use information How we disclose information How we store and secure information How long we keep information How to access and control your information Our policy towards children Regional disclosures Changes to our privacy policy How to contact us We offer additional policies tailored for specific audiences and use cases. These include: Cookies & Tracking Notice Atlassian Careers Privacy Notice – for job applicants Former Workplace Privacy Notice – for past employees Demographic Survey Privacy Notice – for voluntary survey data This privacy policy describes Atlassian’s data practices as a controller of personal information. Please note that this privacy policy does not apply to the extent that we process personal information in the role of a processor or service provider on behalf of our customers, as further specified in the Data Processing Addendum entered into with those customers. When Atlassian processes personal information on behalf of our customers (such as your employer, if applicable), the customer is the controller of the personal information processed and manages those accounts and any Service sites. In such cases, Atlassian acts as a processor or service provider on behalf of our customer and handles your information according to the instructions of that organization. We are not responsible for the privacy or security practices of our customers, which may differ from those described in this privacy policy. For more information about how an Atlassian customer uses your personal information, or to exercise the rights you may have with respect to that information, please contact that organization directly. Privacy policy overview Atlassian collects information directly from you when you provide it to us, automatically when you use our Services, and from other sources including other users of the Services, other services you link to your account, other Atlassian companies, partners, and third-party providers. How we use information depends on which Services you use, how you use them, and any preferences you have communicated to us. We use information for a range of purposes described below, including to provide the Services and personalize your experience, to develop and improve our Services, to communicate with you, to conduct marketing and promotional activities, to provide customer support, to maintain Service safety and security, to protect our interests and rights, with your consent, and to aggregate or de-identify data. We disclose information as described below, including to service providers, Atlassian partners, providers of third-party services, for compliance with enforcement requests and applicable laws, to enforce our terms and policies and our rights, to Atlassian affiliated companies or in connection with business transfers, as well as with your consent. Additionally, when you use the Services, we disclose certain information about you to other Service users as described in more detail below. Where applicable under local law, you may have certain rights or choices with respect to your personal information, including to request information about our processing of information, to request a copy of your information, to object to our use of information, to request the deletion or restriction of information, to request a disclosure of information in a portable format, or to opt out of certain disclosures of personal information and targeted advertising. See the “ How to access and control your information ” section for more detail on specific choices and how to exercise the rights you may have. In the “ Regional disclosures ” section, we provide additional information for individuals in the European Economic Area and United Kingdom, including information about the legal bases for processing information, international transfers, the specific rights applicable in these jurisdictions, and how to contact our EU and UK representatives. We also provide additional information for individuals in the United States, including details about information collected and disclosed in the past 12 months and specific rights available under applicable U.S. state laws. We provide details on how to contact us with any questions or concerns, or to exercise your rights, in the “ How to contact us ” section. Information we collect We collect information about you when you provide it to us, when you use our Services, and from other sources, as further described below. Information you provide We collect information about you when you input it into the Services or otherwise provide it directly to us. This includes the following categories of information: Account Information and Profile Information: We collect information when you register for an account, create or modify your profile, set preferences, sign up for or make purchases through the Services. For example, you provide contact information (e.g., name or email address) and, in some cases, billing information (e.g., billing address, email address or name), when you register for the Services. You also have options to add a display name, profile photo, job title, and other details to your profile. We also keep track of your preferences when you select settings within the Services. You may also provide information to us when you integrate or link a third-party service with our Services. For example, if you create an account or log into the Services using your Google credentials, we receive your name and email address as permitted by your Google profile settings in order to authenticate you. The information we receive when you link or integrate our Services with a third-party service depends on the settings, permissions and privacy policy controlled by that third-party service. You should always check the privacy settings and notices in these third-party services to understand what information may be disclosed to us or shared with our Services. Content you provide through our products: The Services include the Atlassian products you use, where we collect and store content that you post, send, receive and share. We process this content in the role of a processor or service provider on behalf of our customers; this privacy policy does not apply to that processing (see above for more information). Content you provide through our websites: The Services also include websites owned or operated by us. We collect content that you submit to these websites, which include social media or social networking websites operated by us, our support and documentation websites, our Community Forums, and our Marketplace. For example, you provide content to us when you provide feedback, directly to us through our Services or otherwise, or when you participate in any interactive features, surveys, contests, promotions, sweepstakes, activities or events. Information you provide through our support channels: The Services also include customer support, where you may submit inquiries or other information regarding a problem you are experiencing with a Service. Whether you designate yourself as a technical contact, open a support ticket, speak to one of our representatives directly or otherwise engage with our support team or support features, you will be asked to provide contact information, a summary or description of the problem you are experiencing, and any other documentation, screenshots or information that would be helpful in resolving the issue and/or a Support Entitlement Number (SEN). Payment Information: We collect payment and billing information when you register for certain paid Services. For example, we ask you to designate a billing representative, including name and contact information, upon registration. You might also provide payment information, such as payment card details, which we collect via secure payment processing services. Information we collect automatically We automatically collect information about you when you use our Services, including browsing our websites and taking certain actions within the Services. Information may also be collected about how you interact with and use features in our software products. This includes the following categories of information: Your use of the Services: We collect information about your use, operation, and interaction with any of our Services, including when you connect third party services to or use those services with ours. This information includes, for example, the features you use, the actions you perform, the links you click on; the type, size and filenames of attachments you upload to the Services; search terms; the number of words in a Jira ticket or @ mentions in a comment; the type of Loom videos you created and the number of views on your videos; and how you interact with others on the Services. We also collect information about the teams and people you work with and how you work with them, like who you collaborate with and communicate with most frequently. Administrators may enable our collection of this information from software products. Device and Connection Information: We collect information about your computer, phone, tablet, or other devices you use to access the Services. This device information includes your connection type and settings when you install, access, update, or use our Services. We also collect information through your device about your operating system, browser type, IP address, URLs of referring/exit pages, device identifiers, and diagnostic and crash data. We use your IP address and/or country preference to approximate your location to provide you with a better Service experience. How much of this information we collect depends on the type and settings of the device you use to access the Services. Cookies and Other Tracking Technologies: Atlassian and our third-party partners, such as our advertising and analytics partners, use cookies and other tracking technologies (e.g., web beacons, device identifiers and pixels) to provide functionality, to recognize you across different Services and devices, or to demonstrate that certain content was viewed or clicked. For more information, please see our Cookies & Tracking Notice , which includes information on how to control or opt out of these cookies and tracking technologies. Information from other sources We also receive information about you from other Service users, our related companies, our business and channel partners, and third-party providers, including from social media platforms and public databases. We may combine this information with information we collect through other means described above. This helps us, for example, to update and improve our records, provide and improve our Services, identify new customers, create more personalized advertising, and suggest services that may be of interest to you. This includes information collected from the following sources: Other users of the Services: We receive your email address from other Service users when they provide it in order to invite you to the Services. Similarly, an administrator may provide your contact information when they designate you as the billing or technical contact on your company's account or when they designate you as an administrator. Atlassian Companies: We receive information about you from other Atlassian corporate affiliates, in accordance with their terms and policies. Atlassian Partners: We work with a global network of partners who provide consulting, implementation, training and other services around our products. Some of these partners also help us to market and promote our Services, generate leads for us, and resell our Services. We receive information about you and your activities on and off the Services from these partners, such as billing information, billing and technical contact information, company name, what Atlassian Services you have purchased or may be interested in, evaluation information you have provided, what events you have attended, what country you are in, and information about your interest in and engagement with our Services and online advertisements. Third-Party Providers: We may receive information about you from third-party providers of business and security information and from publicly available sources (e.g., social media platforms), including physical mail addresses, job titles, email addresses, phone numbers, intent data (or user behavior data), IP addresses and social media profiles. How we use information How we use the information we collect depends on which Services you use, how you use them, and any preferences you have communicated to us. We use information for the following purposes: To provide the Services and personalize your experience: We use information about you to provide the Services to you, including to process transactions, authenticate you when you log in, provide customer support, and operate, maintain, and improve the Services. We may use your email domain to infer your affiliation with a particular organization or industry to personalize the content and experience you receive on our websites. Based on your interactions with different Atlassian products, third-party services you link or install, and advertisements, we will personalize your experience and tailor our communications, recommendations and offers to you. To develop and improve our Services: We are always looking for ways to make our Services smarter, faster, secure, integrated, and useful. We use information and collective learnings (including feedback) about how people use our Services to troubleshoot, to identify trends, usage, activity patterns and areas for integration, to improve our Services and to develop new products, features and technologies that benefit our users and the public. For example, to improve the @mention feature, we automatically analyze recent interactions among users and how often they @mention one another to surface the most relevant connections for users, or we might analyze Marketplace search terms to improve the accuracy and relevance of suggested apps returned when you use the search feature. In some cases, we apply these learnings across our Services to improve and develop similar features, to better integrate the Services you use, or to provide you with insights based on how others use our Services. We also test and analyze certain new features with some users before rolling the feature out to all users. To communicate with you about the Services: We use your contact information to send transactional communications via email and within the Services, including confirming your purchases, reminding you of subscription expirations, responding to your comments, questions and requests, and providing customer support. We also provide tailored communications based on your activity and interactions with us, and we may contact you regarding product feedback. If an opt out is available, you will find that option within the communication itself or in your account settings. To conduct marketing and promotional activities: We use information about you and how you use the Services for analysis, research and communications relating to marketing (including targeted advertising of products that may interest you), promotional activities, and business development. We may use your contact information and information about how you use the Services to send promotional communications that may be of specific interest to you, including by email and by displaying Atlassian ads on other companies' websites and applications. These communications may be informed by, for example, your interactions (like counting ad impressions), and are aimed at driving engagement and maximizing what you get out of the Services, including information about new features, survey requests, newsletters, and events we think may be of interest to you. We also communicate with you about new Services, product offers, promotions, and contests. You can control whether you receive these communications as described below at “ How to access and control your information ” under "Opt-out of communications." To provide customer support: We use your information to resolve technical issues you encounter, to respond to your requests for assistance, to analyze crash information, and to repair and improve the Services, including for development, training, or fine-tuning of machine learning and artificial intelligence models. We may also use generative artificial intelligence in responding to your support related requests. Where you give us express permission to do so, we may disclose information to a third-party expert for the purpose of responding to support-related requests. To maintain Service safety and security: We use information about you and your use of the Services to verify accounts and activity, to detect, prevent, and respond to potential or actual security incidents, and to monitor and protect against other malicious, deceptive, fraudulent, illegal or inappropriate activity, including violations of Service policies. Detection and response may leverage generative artificial intelligence or machine learning tools. To protect our legitimate business interests and legal rights: Where required by law or where we believe it is necessary to protect our legal rights and interests, or the legal rights or interests of others, we use information about you in connection with legal claims, compliance, regulatory, and audit functions, and disclosures in connection with the acquisition, merger or sale of a business. With your consent: We use information about you where you have given us consent to do so for a specific purpose not listed above. For example, we may publish testimonials or featured customer stories to promote the Services, with your permission. To aggregate or de-identify data : We may aggregate or de-identify your information collected through the Services so it can no longer be re-identified by us or another party. We may use and disclose aggregated or de-identified data for a number of purposes, including to develop and improve our Services and to conduct marketing and promotional activities. To the extent we aggregate any data originally based on personal information, we maintain and use such data in de-identified form and will not attempt to re-identify the data. How we disclose information We make collaboration tools, and we want them to work well for you. This means disclosing information through the Services and to certain third parties. We disclose information we collect in the ways discussed below. Disclosing to third parties We disclose information to third parties that help us operate, provide, improve, integrate, customize, support, and market our Services. All the above categories exclude text messaging originator opt-in data and consent. This information will not be shared with any third parties, excluding aggregators and providers of the text messaging services. Service Providers: We work with third-party service providers to provide website and application development, hosting, maintenance, backup, storage, virtual infrastructure, payment processing, analysis, marketing, and other services for us, which may require them to access or use information about you. If a service provider needs to access information about you to perform services on our behalf, they do so under close instruction from us, including appropriate security and confidentiality procedures designed to protect your information. Atlassian Partners: We work with a global network of partners who provide consulting, implementation, training and other services around our products. We may disclose your information to these third parties in connection with their services, such as to assist with billing and collections, to provide localized support, and to provide customizations. We may also disclose information to these third parties where you have agreed to that disclosure. Third-Party Services: You, your administrator or other Service users may choose to add new functionality or change the behavior of the Services by installing or connecting third-party services. Doing so may give third-party services access to your account and information about you, like your name and email address. When you intentionally interact with such third-party services, we may disclose certain information to those third parties or receive information from those third parties, consistent with your privacy settings on the third-party service. If you purchase or install a third-party service using Atlassian Marketplace, we will also disclose Order information to the third party in accordance with the Atlassian Marketplace Terms of Use . Third-party service policies and procedures are not controlled by us, and this privacy policy does not cover how third-party services use your information. We encourage you to review the privacy policies of third parties before connecting to or using their applications or services to learn more about their privacy and information handling practices. If you object to information about you being disclosed to these third parties, please do not install or connect the third-party service. Links to Third-Party Sites: The Services may include links that direct you to other websites or services whose privacy practices may differ from ours. If you submit information to any of those third-party sites, your information is governed by their privacy policies. We encourage you to carefully read the privacy policy of any website you visit. Third-Party Widgets: Some of our services contain widgets and social media features, such as the Twitter "tweet" button or Facebook "like" button. These widgets and features may collect your IP address, which page you are visiting on the Services, and may set a cookie to enable the feature to function properly. Widgets and social media features are either hosted by a third-party or hosted directly on our Services. You should always check the privacy settings and notices in these third-party services to understand how those third-parties may use your information. With your consent: We may also disclose information about you to third parties when you give us consent to do so. For example, we often display personal testimonials of satisfied customers on our public websites. With your consent, we may post your name alongside the testimonial. Compliance with Enforcement Requests and Applicable Laws; Enforcement of Our Terms and Policies; Enforcement of Our Rights: We may disclose information about you to government authorities, law enforcement, or industry peers if we believe that sharing is reasonably necessary to (a) comply with any applicable law, regulation, legal process or enforceable governmental request, or legal obligation, (b) enforce the terms of our agreements and our policies, (c) protect the security or integrity of our products and services, (d) protect Atlassian, our customers or the public from harm or illegal activities, or (e) respond to an emergency which we believe in good faith requires us to disclose information to assist in preventing the death or serious bodily injury of any person. For more information on how we respond to government requests, see our Guidelines for Law Enforcement and our Transparency Report . Disclosing to affiliated companies We disclose information we collect to affiliated companies and, in some cases, to prospective affiliates. Affiliated companies are companies owned or operated by us. The protections of this privacy policy apply to the information we disclose in these circumstances. Atlassian companies: We disclose information to other Atlassian corporate affiliates in order to operate, maintain, and improve the Services, and to offer you other Atlassian affiliated services. This includes companies that own or operate the Services. Business Transfers: We may disclose or transfer information we collect under this privacy policy in connection with any merger, sale of company assets, financing, reorganization, dissolution, or acquisition of all or a portion of our business to another company. You will be notified via email and/or a prominent notice on the Services if a transaction takes place, as well as any choices you may have regarding your information. Disclosing to other Service users When you use the Services, we disclose certain information about you to other Service users. Managed accounts and administrators: If you register or access the Services using an email address with a domain that is owned by your employer or organization, or associate that email address with your existing account, and such organization wishes to establish an account or site, certain information about you, including your name, profile picture, contact info, content and past use of your account may become accessible to that organization’s administrator and other Service users sharing the same domain. If you are an administrator for a particular site or group of users within the Services, we may disclose your contact information to current or past Service users, for the purpose of facilitating Service-related requests. Community Forums: Our websites offer publicly accessible blogs, forums, issue trackers, and wikis (e.g., Atlassian Community , Atlassian Developer Community , Trello Community , and Trello Inspiration ). You should be aware that any information you provide on these websites - including profile information associated with the account you use to post the information - may be read, collected, and used by any member of the public who accesses these websites. Your posts and certain profile information may remain even after you terminate your account. We urge you to consider the sensitivity of any information you input into these Services. To request removal of your information from publicly accessible websites operated by us, please contact us as provided below. In some cases, we may not be able to remove your information, in which case we will let you know if we are unable to and why. How we store and secure information We use industry standard technical and organizational measures to secure the information we store. For more information on where and how we store your information, please see the Atlassian Trust Center. While we implement safeguards designed to protect your information, no security system is impenetrable and due to the inherent nature of the Internet, we cannot guarantee that information, during transmission through the Internet or while stored on our systems or otherwise in our care, is absolutely safe from intrusion by others. How long we keep information How long we keep information we collect about you depends on the type of information, the purposes for which it was collected, applicable legal or regulatory requirements, and user expectations and preferences. After such time, we will either delete or de-identify your information or, if this is not possible (for example, because the information has been stored in backup archives), then we will securely store your information and isolate it from any further use until deletion is possible. Account information: We retain your account information for as long as your account is active and a reasonable period thereafter in case you decide to re-activate the Services. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information to develop and improve our Services, we take steps to de-identify the information. Information you share on the Services: If your account is deactivated or disabled, some of your information and the content you have provided will remain in order to allow your team members or other users to make full use of the Services. For example, we continue to display messages you sent to the users that received them and continue to display content you provided. Managed accounts: If the Services are made available to you through an organization (e.g., your employer), we retain your information as long as required by the administrator of your account. For more information, see "Managed accounts and administrators" at the “ How we disclose information ” section. Marketing information: If you have elected to receive marketing emails from us, we retain information about your marketing preferences for a reasonable period of time from the date you last expressed interest in our Services, such as when you last opened an email from us or ceased using your Atlassian account. We retain information derived from cookies and other tracking technologies for a reasonable period of time from the date such information was created. How to access and control your information Your Rights: Where applicable under local law, you may have certain rights with respect to your personal information. For more information about region-specific rights for residents of the European Economic Area, United Kingdom, and the United States, please refer to the “ Regional disclosures ” section. Depending on which jurisdiction you live in, you may have the right to request information about our processing of your information, to request a copy of your information, to object to our use of your information (including for marketing purposes), to request the deletion or restriction of your information, to request your information in a structured, electronic format, to request to correct or update your information, to request that we transfer your information to a third party, and to request to opt out of certain disclosures of personal information and targeted advertising. In the “ Your choices ” section, we describe the tools and processes for making different requests associated with these rights. You can exercise some of the choices by logging into the Services and using settings available within the Services or your account. For all other requests, you may contact us as provided in the “ How to contact us ” section. Your requests and choices may be limited in certain cases: for example, if fulfilling your request would reveal information about another person, or if you ask to delete information which we are required or permitted by law to retain. Where you have asked us to disclose data to third parties, for example, by installing third-party apps, you will need to contact those third-party service providers directly to have your information deleted or otherwise restricted. If you have unresolved concerns, you may have the right to complain to a data protection authority in the country where you live, where you work, or where you feel your rights were infringed. Your Choices: You have certain choices available to you when it comes to your information. Below is a summary of those choices, how to exercise them and any limitations: Access and update your information: Our Services give you the ability to access and update certain information about you from within the Service. For example, you can access your profile information from your account and update your profile information within your profile settings (see here for instructions on how to do this). You can also make a request to access information that Atlassian holds in relation to your account here . If you don’t have an Atlassian account, you can make a request to access your information here . Delete your information, including your account: Our Services give you the ability to delete certain information about you from within the Services. For example, you can remove certain profile information within your profile settings (see here for instructions on how to do this). If you would like to delete your Atlassian account, see here for more information. If you don’t have an Atlassian account, you can make a request to delete your information here . Please note, however, that we may need to retain certain information for record keeping purposes, to complete transactions, or to comply with our legal obligations. Request that we stop using your information: In some cases, you may ask us to stop accessing, storing, using and otherwise processing your information where you believe we don't have the appropriate rights to do so. For example, if you believe a Services account was created for you without your permission, or you are no longer an active user, you can request that we delete your account as provided in this privacy policy. Where you gave us consent to use your information for a limited purpose, you can contact us to withdraw that consent, but this will not affect any processing that has already taken place at the time. If you object to information about you being disclosed to a third-party service, please disable the service. Opt out of communications: You may opt out of receiving promotional communications from us by using the unsubscribe link within each email, updating your email preferences within your Service account settings menu, or by contacting us as provided below to have your contact information removed from our promotional email list or registration database. Even after you opt out from receiving promotional messages from us, you will continue to receive transactional messages from us regarding our Services. Please note, you will continue to receive generic ads. Opt out of targeted advertising: Where applicable under local law, you may have the right to opt out of targeted advertising by clicking “Manage Preferences” and following the instructions. Where required, we also honor requests to opt out submitted via privacy preference signals recognized under applicable law, such as the Global Privacy Control (“GPC”). For more information on the GPC and how to use a browser or browser extension incorporating the GPC signal, see Global Privacy Control — Take Control Of Your Privacy . Relevant browser-based cookie controls are described in our Cookies & Tracking Notice . You may also be able to opt out of receiving personalized advertisements from other companies who are members of the Network Advertising Initiative or who subscribe to the Digital Advertising Alliance's Self-Regulatory Principles for Online Behavioral Advertising. For more information about this practice and to understand your options, please visit: http://www.aboutads.info , http://optout.networkadvertising.org/ and http://www.youronlinechoices.eu . Data portability: Data portability is the ability to obtain some of your information in a format you can move from one service provider to another (for instance, when you transfer your mobile phone number to another carrier). Depending on the context, this applies to some of your information, but not to all of your information. Should you request it, we will provide you with an electronic file of your basic account information and the information you create on the spaces under your sole control, like your personal Bitbucket repository. Our policy towards children Our Services are not intended for use by anyone under the age of 16. If we become aware that a child under 16 has provided us with personal information, we will take steps to delete such information. Regional disclosures Depending on where you live, you may have specific privacy rights that apply to you. The following privacy representations and disclosures are intended to supplement the main privacy policy and provide additional information about those rights and other information relevant to data subjects located in the following jurisdictions. For data subjects located in the European Economic Area or the United Kingdom, please refer to the European Economic Area and United Kingdom privacy disclosures below. For residents of the United States, please refer to the U.S. State privacy disclosures below. European Economic Area and United Kingdom privacy disclosures If you are an individual in the European Economic Area (EEA) or United Kingdom (UK), we collect and process information about you only where we have legal bases for doing so under applicable data protection laws. The legal bases depend on the Services you use and how you use them. This means we collect and use your information only where: We need it to provide you the Services and personalise your experience, provide customer support and to maintain Service safety and security; It satisfies a legitimate interest (which is not overridden by your data protection interests), such as to develop and improve our Services, to conduct marketing and promotional activities and to protect our legal rights and interests; You give us consent to do so for a specific purpose; or We need to process your data to comply with a legal obligation. If you have consented to our use of information about you for a specific purpose, you have the right to change your mind at any time, but this will not affect any processing that has already taken place. Where we are using your information because we have a legitimate interest to do so, you have the right to object to that use, though, in some cases, this may mean no longer using the Services. The following chart identifies the applicable legal basis for each processing purpose: Purpose (see the How we use information section for more detail) Legal basis To provide the Services and personalize your experience; To develop and improve the Services, including machine learning and artificial intelligence model training; To communicate with you about the Services; To conduct marketing and promotional activities; To provide customer support; Verify your account credentials as needed to log you into the Services and help safeguard your account’s security; Protect our rights, privacy, safety, or property, and/or that of our affiliated companies, you, or other parties, including to enforce this privacy policy and any other agreements or policies; Detect and prevent fraud, illegal activity, or violations of the terms of our agreements and our Service policies, and to maintain the security of our IT systems, architecture, assets, customers, and networks; and Aggregate or de-identify data. Legitimate interests (Article 6(1)(f) GDPR) To provide the Services and personalize your experience; To develop and improve the Services; Communicate with you about changes to our terms, conditions, or policies; or to respond to your inquiries, comments, feedback, or questions; Verify your account credentials as needed to log you into the Services and help safeguard your account’s security; Process payments; Detect and prevent fraud, illegal activity, or violations of Service policies, and to maintain the security of our IT systems, architecture, assets, customers, and networks; and Protect our rights, privacy, safety, or property, and/or that of our affiliated companies, you, or other parties, including to enforce this privacy policy and any other agreements or policies. Contractual necessity (Article 6(1)(b) GDPR) To develop and improve the Services; Publish testimonials or featured customer stories; and To conduct marketing and promotional activities (where you have provided consent to receive such marketing or promotions). Consent (where legally required) (Article 6(1)(a) GDPR) To maintain Service safety and security; Detect and prevent fraud, illegal activity, or violations of the terms of our agreements and our Service policies; Authenticate account credentials, as necessary to log you into the Services and help protect the security of your account; and Comply with legal obligations and legal process and to protect our rights, privacy, safety, or property, and/or that of our affiliated companies, you, or other parties, including to enforce this privacy policy and any other agreements or policies. Compliance with a legal obligation (Article 6(1)(c) GDPR) Where applicable under local law and subject to applicable exceptions, you have the following rights regarding your personal information: To request access to and/or a copy of certain information we hold about you (including in a portable and/or machine-readable format); To object to how we process your personal information; To update or correct your personal information; To request that we delete certain personal information we hold about you; To restrict how we process certain personal information about you; To request that we transfer your information to a third-party provider of services; To withdraw your consent at any time (where you have provided consent for the processing of your personal information); and To lodge a complaint with the relevant supervisory authority. If you have a complaint or concern about your personal information, we encourage you to contact us first, and we will do our best to resolve your concern. You can submit inquiries to the appropriate representative here: EU Representative: Atlassian B.V. c/o Atlassian, Inc. 350 Bush Street, Floor 13 San Francisco, CA 94104 E-Mail: eudatarep@atlassian.com UK Representative: Atlassian (UK) Operations Limited c/o Herbert Smith Freehills LLP Exchange House Primrose Street London EC2A 2EG United Kingdom E-Mail: ukrepresentative@atlassian.com International transfers: We collect information globally and may transfer, process, and store your information outside of your country of residence, to wherever we or our third-party service providers operate for the purpose of providing you the Services. Whenever we transfer your information, we take steps to protect it. International transfers within the Atlassian Companies: To facilitate our global operations, we transfer information globally and allow access to that information from countries in which the Atlassian owned or operated companies have operations for the purposes described in this privacy policy. These countries may not have equivalent privacy and data protection laws to the laws of your country. When we disclose information about you within and among Atlassian corporate affiliates, we make use of the Data Privacy Framework to receive personal data transfers from the European Union/European Economic Area to the U.S. (see the “Data Privacy Framework notice” section below), and the standard contractual data protection clauses (see here ), which have been approved by the European Commission, to safeguard the transfer of information we collect from the European Economic Area, the United Kingdom (the "UK"), and Switzerland. Refer to this page for a list of countries to which we regularly transfer personal data. Data Privacy Framework notice: On July 10, 2023, the European Commission’s adequacy decision for the EU-U.S. Data Privacy Framework (EU-U.S. DPF) entered into force. Atlassian, Inc. and its U.S. subsidiaries (Atlassian Network Service, Inc., Dogwood Labs, Inc., AgileCraft LLC, Halp, Inc., Loom, Inc., Opsgenie, Inc., and Trello, Inc.) adhere to the Data Privacy Framework Principles regarding the collection, use, and retention of personal data that is transferred from the European Union and Switzerland to the U.S. Atlassian complies with the EU-U.S. Data Privacy Framework (EU-U.S. DPF), the UK Extension to the EU-U.S. DPF and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) as set forth by the U.S. Department of Commerce. Atlassian has certified to the U.S. Department of Commerce that it adheres to the EU-U.S. Data Privacy Framework Principles (EU-U.S. DPF Principles) with regard to the processing of personal data received from the European Union in reliance on the EU-U.S. DPF and from the United Kingdom (and Gibraltar) in reliance on the UK Extension to the EU-U.S. DPF. Atlassian has certified to the U.S. Department of Commerce that it adheres to the Swiss-U.S. Data Privacy Framework Principles (Swiss-U.S. DPF Principles) with regard to the processing of personal data received from Switzerland in reliance on the Swiss-U.S. DPF. If there is any conflict between the terms in this policy and the EU-U.S. DPF Principles and/or the Swiss-U.S. DPF Principles, the Principles shall govern. To learn more about the Data Privacy Framework (DPF) program, and to view our certification, please visit https://www.dataprivacyframework.gov/ . In compliance with the EU-U.S. DPF, the UK Extension to the EU-U.S. DPF, and the Swiss- | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#local-storage | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://open.forem.com/techresolve | Darian Vance - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Follow User actions Darian Vance Lead Cloud Architect & DevOps Strategist with 12+ years in the trenches. Founder of TechResolve. I turn complex cloud chaos into systems you can actually understand and manage. Joined Joined on Dec 26, 2025 Personal website https://techresolve.blog/ twitter website Education BS in Computer Science & 12 Years of Production Outages Work Founder & Lead Architect at TechResolve More info about @techresolve Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Skills/Languages Cloud Architecture (AWS/Azure), Kubernetes, Terraform, Python, Docker, Linux System Administration, CI/CD Automation, Bash Scripting, ITAM/SAM Strategy. Currently learning Integrating LLMs into DevOps pipelines, advanced eBPF for observability, and exploring Rust for high-performance CLI tools. Currently hacking on Building TechResolve.blog into the ultimate troubleshooting resource. Also developing open-source tools to visualize legacy code dependency graphs. Available for Consulting on legacy infrastructure modernization, speaking engagements on "Real-world DevOps Failures," and mentoring junior system admins who want to become architects. Post 3 posts published Comment 0 comments written Tag 5 tags followed Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem Darian Vance Darian Vance Darian Vance Follow Dec 31 '25 Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: PoE+++?! WHEN WILL THE MADNESS END? Darian Vance Darian Vance Darian Vance Follow Dec 28 '25 Solved: PoE+++?! WHEN WILL THE MADNESS END? # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: How to look for a good MSP Darian Vance Darian Vance Darian Vance Follow Dec 26 '25 Solved: How to look for a good MSP # devops # programming # tutorial # cloud Comments Add Comment 8 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:30 |
https://www.linkedin.com/top-content/productivity/ | Top Productivity Content from LinkedIn Members Skip to main content LinkedIn Top Content People Learning Jobs Games Join now Sign in Top Content Productivity Explore top LinkedIn content from expert professionals. Yamini Rangan Yamini Rangan is an Influencer 158,651 followers 2mo Report this post In the inbound marketing era, content was queen. In the AI era of marketing, yes, content is still queen. Last week, I spoke to a CMO whose content marketing strategy revolves entirely around SEO. After years of solid growth, her company’s traffic is declining. It’s a familiar story in 2025. She asked: “Now that SEO is less effective, is content marketing less important?” I told her the opposite is true. Content is more important than ever but a few things are different. 1. Content needs to be specific. Answer Engine Optimization (AEO), or how your brand shows up in AI-driven responses is becoming important. The difference between being cited or invisible often comes down to one thing: specific, high-quality content. Marketers leading in AEO are seeing 3–4x higher conversion rates, but only when their content goes deeper than surface-level keywords. Authority, clarity, and originality are the new ranking signals. 2. Content needs to be multi-modal and multi-channel. Buyers no longer follow a linear journey. They read, watch, listen, chat, and scroll, often in the same hour. AI makes it easier to meet them in those moments, but you still need powerful assets to show up well: Video and interactive demos for discovery, Long-form explainers for education, Bite-sized insights for social. The format changes, but the foundation doesn’t: clear, helpful, human content. 3. Content needs to be dynamic and personal. AI gives us the signal—who’s interested, what they need, when they’re ready. But only great content makes the connection. Dynamic, intent-based content can turn data into meaningful engagement. That’s how you create moments that feel personal instead of programmatic. The tools have changed. The algorithms have changed. The constant is content. It’s still queen – because it’s still how trust, engagement, and growth begin. Ps: Huge shoutout to our HubSpot partner Mole Street, who’s all-in on helping customers grow through great content. Whenever I speak with Brendan Walsh or Brian LaPann , “Content Hub” comes up within the first two minutes. Last week they released a fantastic whitepaper on it, link in the comments if you’d like to take a look. …more 657 81 Comments Like Comment Share Copy LinkedIn Facebook X Brett Mathews Brett Mathews is an Influencer Editor @ Apparel Insider | Editorial, Copywriting 44,848 followers 3mo Report this post STUDY FINDS COST PER WEAR INFORMATION SHIFTS SHOPPERS TO QUALITY: A new study published in Psychology & Marketing offers a fascinating look at what fashion drives fashion purchasing decisions. Researchers from the University of Bath and Cambridge University found that simply showing consumers the cost per wear (CPW) of garments (price divided by the number of times an item can be worn) can shift preferences away from cheap, low-quality clothing toward higher-priced, longer-lasting options. The findings draw on behavioural psychology to reveal that people respond more to perceived 'economic value' than to abstract sustainability messages. When shoppers could compare CPW between garments, and especially when figures were backed by trusted certification, they were far more likely to choose quality over quantity. The authors suggest CPW could be a powerful tool for brands and policymakers seeking to reframe sustainability as smart spending. Full story in comments. …more View C2PA information No more previous content View C2PA information No more next content 919 114 Comments Like Comment Share Copy LinkedIn Facebook X Andrew Ng Andrew Ng is an Influencer Founder of DeepLearning.AI; Managing General Partner of AI Fund; Exec Chairman of LandingAI 2,355,474 followers 1y Report this post AI Product Management AI Product Management is evolving rapidly. The growth of generative AI and AI-based developer tools has created numerous opportunities to build AI applications. This is making it possible to build new kinds of things, which in turn is driving shifts in best practices in product management — the discipline of defining what to build to serve users — because what is possible to build has shifted. In this post, I’ll share some best practices I have noticed. Use concrete examples to specify AI products. Starting with a concrete idea helps teams gain speed. If a product manager (PM) proposes to build “a chatbot to answer banking inquiries that relate to user accounts,” this is a vague specification that leaves much to the imagination. For instance, should the chatbot answer questions only about account balances or also about interest rates, processes for initiating a wire transfer, and so on? But if the PM writes out a number (say, between 10 and 50) of concrete examples of conversations they’d like a chatbot to execute, the scope of their proposal becomes much clearer. Just as a machine learning algorithm needs training examples to learn from, an AI product development team needs concrete examples of what we want an AI system to do. In other words, the data is your PRD (product requirements document)! In a similar vein, if someone requests “a vision system to detect pedestrians outside our store,” it’s hard for a developer to understand the boundary conditions. Is the system expected to work at night? What is the range of permissible camera angles? Is it expected to detect pedestrians who appear in the image even though they’re 100m away? But if the PM collects a handful of pictures and annotates them with the desired output, the meaning of “detect pedestrians” becomes concrete. An engineer can assess if the specification is technically feasible and if so, build toward it. Initially, the data might be obtained via a one-off, scrappy process, such as the PM walking around taking pictures and annotating them. Eventually, the data mix will shift to real-word data collected by a system running in production. Using examples (such as inputs and desired outputs) to specify a product has been helpful for many years, but the explosion of possible AI applications is creating a need for more product managers to learn this practice. Assess technical feasibility of LLM-based applications by prompting. When a PM scopes out a potential AI application, whether the application can actually be built — that is, its technical feasibility — is a key criterion in deciding what to do next. For many ideas for LLM-based applications, it’s increasingly possible for a PM, who might not be a software engineer, to try prompting — or write just small amounts of code — to get an initial sense of feasibility. [Reached length limit. Full text: https://lnkd.in/gYY-hvHh ] …more Amazon Nova’s Competitive Price/Performance, OpenAI o1 Pro’s High Price/Performance, Google’s Game Worlds on Tap, Factual LLMs deeplearning.ai 3,345 139 Comments Like Comment Share Copy LinkedIn Facebook X Marie-Doha Besancenot Senior advisor for Strategic Communications, Cabinet of 🇫🇷 Foreign Minister; #IHEDN, 78e PolDef 39,114 followers 1y Report this post RAND ‘s report on wartime #disinformation : Applying lessons learned from #Ukraine to other contexts. 92 pages, 3 chapters, 12 lessons learned : 🪖Before the war: shaping operations. 🔹 2014-22: building government &civil society institutions countering adversary disinformation 🔹 steps to stop the flow of Russian propaganda targeting the country 🔹 intelligence-driven “prebunk” informing international audiences about planned Russian operations 🪖During the war: countering false narratives across the 3 theaters of the information war. 🧰12 lessons learned : 🔸Prepare and plan for 3 theaters of information war, look for innovative ways to reach & communicate with populations in totalitarian countries; rally international institutions to effectively prebunk adversary campaigns targeting the rest of the world; support a broader array of institutions residing in host nations. 🔸Build critical host nation institutions in advance of and during conflict 🔸Build and maintain capacity to counter disinformation: assess own doctrine, training, and wargaming efforts to ensure it is able to counter disinformation during conflict. Ensure that institutions & psychological operations forces retain their capability. 🔸Invest in and work with civil society 🔸Build and maintain trust to effectively dispel adversary narratives. 🔸Work with and empower local and military influencers: promote online voices to help support national security objectives. 🔸Build #resilience of troops: to avoid frontline soldiers being a target of adversary campaigns, undermining their will to fight. Develop a mandatory media literacy education campaign to help deployed and garrison personnel recognize malign influence attempts and foster safer online behavior. 🔸Do not allow coordination to sacrifice speed in responding: the Ukrainian experience highlights the value of a loosely coordinated and redundant network response that involves multiple actors both monitoring media and communicating key narratives. 🔸Be prepared to take risks: accept that government communicators outsource their efforts to creative and agile civil society institutions. Allow communicators to quickly create unique, humorous, and engaging content. 🔸Plan on resourcing and executing 3 critical counterdisinformation tools: Debunking (fact checking), prebunking, and the promulgation of proactive information narratives. Ensure the 3 are integrated in military theaters of operation. 🔸Be prepared to build the capacity of key institutions: In future contingency operations, consider adversary targets for propaganda and disinformation and evaluate the ability of local institutions to effectively respond. 🔸Recognize the risk of waning support over time, as the time engaged in conflict increases and influence of messaging decreases & adversary disinformation narratives may become more influential. Wargame these risks and consider incorporating them in war plans. 👏🏼 Todd Helmus Khrystyna Holynska …more 502 24 Comments Like Comment Share Copy LinkedIn Facebook X Rahul Agarwal Staff ML Engineer | Meta, Roku, Walmart | 1:1 @ topmate.io/MLwhiz 44,583 followers 9mo Report this post Few Lessons from Deploying and Using LLMs in Production Deploying LLMs can feel like hiring a hyperactive genius intern—they dazzle users while potentially draining your API budget. Here are some insights I’ve gathered: 1. “Cheap” is a Lie You Tell Yourself: Cloud costs per call may seem low, but the overall expense of an LLM-based system can skyrocket. Fixes: - Cache repetitive queries: Users ask the same thing at least 100x/day - Gatekeep: Use cheap classifiers (BERT) to filter “easy” requests. Let LLMs handle only the complex 10% and your current systems handle the remaining 90%. - Quantize your models: Shrink LLMs to run on cheaper hardware without massive accuracy drops - Asynchronously build your caches — Pre-generate common responses before they’re requested or gracefully fail the first time a query comes and cache for the next time. 2. Guard Against Model Hallucinations: Sometimes, models express answers with such confidence that distinguishing fact from fiction becomes challenging, even for human reviewers. Fixes: - Use RAG - Just a fancy way of saying to provide your model the knowledge it requires in the prompt itself by querying some database based on semantic matches with the query. - Guardrails: Validate outputs using regex or cross-encoders to establish a clear decision boundary between the query and the LLM’s response. 3. The best LLM is often a discriminative model: You don’t always need a full LLM. Consider knowledge distillation: use a large LLM to label your data and then train a smaller, discriminative model that performs similarly at a much lower cost. 4. It's not about the model, it is about the data on which it is trained: A smaller LLM might struggle with specialized domain data—that’s normal. Fine-tune your model on your specific data set by starting with parameter-efficient methods (like LoRA or Adapters) and using synthetic data generation to bootstrap training. 5. Prompts are the new Features: Prompts are the new features in your system. Version them, run A/B tests, and continuously refine using online experiments. Consider bandit algorithms to automatically promote the best-performing variants. What do you think? Have I missed anything? I’d love to hear your “I survived LLM prod” stories in the comments! …more 1,168 46 Comments Like Comment Share Copy LinkedIn Facebook X Lenny Rachitsky Lenny Rachitsky is an Influencer Deeply researched product, growth, and career advice 325,649 followers 3mo Report this post My biggest takeaways from Ethan Smith on how to win at AEO (i.e. get ChatGPT to recommend your product): 1. Being mentioned most often beats ranking first. In Google, the #1 blue link wins. In ChatGPT, the answer summarizes multiple sources—so appearing in five citations beats ranking #1 in one. Ethan’s strategy: get mentioned on Reddit, YouTube, blogs, and affiliates. Volume of mentions matters more than any single placement. 2. LLM traffic converts 6x better than Google search traffic. Webflow saw this dramatic difference because users who come through AI assistants have built up much more intent through conversation and follow-up questions, making them highly qualified leads. 3. Early-stage startups can win at AEO immediately, unlike with SEO. Traditional SEO requires years of domain authority. But a brand-new Y Combinator company mentioned in a Reddit thread today can show up in ChatGPT tomorrow. The playing field is finally level. 4. The long tail of AEO is 4x bigger than SEO. People ask ChatGPT questions with 25 or more words (vs. 6 in Google). Ethan found gold in queries like “Which meeting transcription tool integrates with Looker via Zapier to BigQuery?”—questions that never existed in search but are perfect for AI. Own these micro-niches. 5. Reddit is proving to be the kingmaker for AI visibility. ChatGPT trusts Reddit because the community polices spam better than any algorithm. Ethan’s exact playbook: make one real account, say who you are and where you work, give genuinely helpful answers. Five good comments can transform your visibility. No automation, no fake accounts—just be helpful. 6. YouTube videos for “boring” B2B terms are a gold mine for AEO. Nobody makes videos about “AI-powered payment processing APIs”—which is exactly why you should. While everyone fights over “best CRM software,” the high-value, zero-competition long tail is wide open in video. 7. Your help center is now a growth channel. All those “Does your product do X?” questions flooding ChatGPT can be answered by help-center pages. Move them from subdomain to subdirectory, cross-link aggressively, and cover every feature question. Ethan calls this the most underutilized opportunity in AEO. 8. January 2025 was the inflection point in AEO growth. That’s when ChatGPT made answers more clickable (maps, shopping cards, citations) and adoption exploded. Webflow went from near zero to 8% of signups from AI. This channel is accelerating faster than any Ethan’s seen in 18 years. 9. The AEO playbook: (1) Find questions from competitor paid search data, (2) set up answer tracking, (3) see who’s showing up as citations, (4) create landing pages answering all follow-up questions, (5) get mentioned offsite via Reddit/YouTube/affiliates, (6) run controlled experiments, (7) build a dedicated team. This exact process is driving real results at scale. …more 2,890 261 Comments Like Comment Share Copy LinkedIn Facebook X Alpana Razdan Alpana Razdan is an Influencer Country Manager: Falabella | Co-Founder: AtticSalt | Built Operations Twice to $100M+ across 5 countries |Entrepreneur & Business Strategist | 15+ Years of experience working with 40 plus Global brands. 159,855 followers 7mo Report this post The most expensive mistake in business is assuming your customers will never change. Last year, something shifted in Indian retail. Gen Z (377 million) overtook millennials (356 million) to become our largest consumer group, influencing $40-45 billion worth of apparel and footwear purchases. But they're not shopping at the stores we built for them. [Et Retail] Brands watched their growth collapse in just 12 months. → ZARA fell from 40% to 8% growth, [Et Retail] → Levi Strauss & Co. crashed from 54% to 4% growth [Et Retail] → H&M dropped from 40% to 11% growth [Et Retail] Here's why the growth has slowed down: 📌 Gen Z discovered new brands like Freakins and Bonkers Corner, offering trendy clothes at ₹500-800 📌 They chose self-expression over brand loyalty 📌 70% of their shopping moved online, heavily influenced by Instagram 📌 They demanded inclusive sizing (XS to XXL) and unisex options that legacy brands ignored Take FREAKINS , which clocked ₹25 crore in FY2023, or Bonkers.corner , clocked ₹100 crore. [The Economic Times] [Et Retail] These brands understood what Gen Z wanted: crop tops, baggy clothes, Korean pants, and oversized tees at prices that let them experiment with three different outfits daily. Body positivity isn't a marketing campaign for this generation. It's how they think. When they couldn't find the sizes or styles they wanted at premium stores priced at ₹1,200-1,500, they simply went elsewhere. Myntra saw the shift and launched FWD with ₹500 price points. The result was explosive: 100% year-on-year growth and 16 million Gen Z users, who now represent one in three e-lifestyle shoppers. [Et Retail] Legacy brands bet that Gen Z would "grow up" and pay premium prices. Instead, 377 million young Indians chose values over logos. The most expensive mistake in business? Assuming your customers will never change. What changes in your customer base have surprised you recently? …more No more previous content No more next content 2,602 213 Comments Like Comment Share Copy LinkedIn Facebook X Maggie Sellers Reum Maggie Sellers Reum is an Influencer Founder, Hot Smart Rich | Investor in Women-Led Brands | Host: Hot Smart Rich Podcast 🎧 | Subscribe to the HSR Newsletter ⬇️ 24,246 followers 5mo Edited Report this post I built a Top 100 Global video podcast on Spotify . Here’s exactly how I did it. Six months ago, I launched Hot Smart Rich , a video-first podcast for anyone obsessed with the future of culture, creators, startups, and self-growth, on Spotify. We hit Spotify’s Top Business Podcasts in week one. Since then, we’ve charted 7 times, peaked at #5 in the U.S., and landed in Spotify’s Top 50 US podcasts overall. What surprised me most? How quickly video unlocked growth. On Spotify, my audience could seamlessly switch between watching and listening—just like the 300M+ listeners on the platform doing the same thing. That flexibility helped us attract not just more fans, but the right fans. The kind who binge episodes, send me DMs, share clips with their group chats, and now proudly call themselves HSR Angels. And yes, I turned it into a business. Through the Spotify Partner Program with Spotify for Creators , creators can monetize video content without giving up creative control. It’s real revenue, real reach, and a real community. (And let’s be honest: most platforms can’t say that.) If you’re thinking about launching, here’s what I’d tell you: - It is not too saturated. But you do need a plan. Get clear on your tone, flow, format, and point of view. Your audience doesn’t want a copy—they want something new. - Don’t waste money on aesthetic fluff. No one cares about your new photoshoot. Spend that cash on solid audio, decent lighting, and a camera that works. We started with iPhones. - Cut up your clips like your life depends on it. Post. Everywhere (Including Spotify). All the time. - Be consistent. Experiment early. When no one’s watching, try things. Switch formats. Get weird. Then double down on what hits. - Make it your personality. If you’re not hyping your own show, no one else will. You don’t need millions to start. You just need a camera, a mic, a message, and Spotify. Check out how to grow your video on spotify below. https://lnkd.in/gnB5ejaS #podcast #business #spotify #spotifypartner #videopodcast #growth …more 874 112 Comments Like Comment Share Copy LinkedIn Facebook X Ian Koniak Ian Koniak is an Influencer I help tech sales AEs perform to their full potential in sales and life by mastering their mindset, habits, and selling skills | Sales Coach | Former #1 Enterprise AE at Salesforce | $100M+ in career sales 97,449 followers 9mo Report this post For my first 16 years in tech sales, I averaged 240K/year W2 income. In my last 4 years, I averaged 720K/year. In order to triple my income, I had to change my sales approach entirely. Here's what I changed: I started using a new approach that I now call Yo-yo selling: 🪀 Yo-yo selling emphasizes starting at the executive level, conducting thorough discovery within the organization, and then returning to the executive with a tailored business case. Like holding a yo-yo, you are constantly in communication with the Executive Sponsor and updating them as you collect information and conduct deep discovery lower down in their organization. You are literally going up and down the organization, but always taking everything back to the Executive Sponsor to surface your findings along the way. Here's a breakdown of the framework: 🎯 𝐈𝐚𝐧 𝐊𝐨𝐧𝐢𝐚𝐤’𝐬 “𝐘𝐨-𝐘𝐨 𝐒𝐞𝐥𝐥𝐢𝐧𝐠” 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 This strategy involves a three-step process: 1. Start at the Top (Executive Engagement) Initiate contact with a senior executive to understand their most pressing challenges, the reasons behind the need for change, and the consequences of inaction. If your solution aligns with their needs, secure their sponsorship for further discovery within their organization. To secure the Executive Meetings, it's essential to create a tailored POV (point of view) on where you think you may be able to help them based on your initial research of their highest level goals and priorities. Chat GPT has made this research a LOT faster now. 2. Conduct In-Depth Discovery (Middle Management) Engage with department heads and key stakeholders to uncover the day-to-day challenges they face. Focus on understanding their processes, pain points, and the implications of current inefficiencies. Gather direct quotes and insights to build a comprehensive view of the organization's needs. 3. Return to the Executive (Present Findings) Compile the insights gathered into an executive summary and business case. Present this to the executive sponsor, highlighting how your solution addresses the identified challenges. Tailor your demonstration to focus solely on relevant aspects that solve their specific problems. 🚀 Why It Works 1. Accelerates Sales Cycles: Engaging executives early ensures alignment and expedites decision-making. 2. Builds Credibility: Demonstrates a deep understanding of the organization's challenges and showcases a tailored solution. 3. Facilitates Internal Buy-In: By involving various stakeholders, you ensure that the solution meets the needs of all parties, increasing the likelihood of adoption. I'm pleased to share that that Yo-yo selling was recently awarded as a Top 15 Sales Tactic of All Time by 30 Minutes to President's Club , and I received a cool plaque for entering the 30MPC Hall of Fame. Since I have no chance of entering the Hall of Fame for my baseball or golf game, this is a nice consolation prize 😁 …more No more previous content No more next content 1,148 71 Comments Like Comment Share Copy LinkedIn Facebook X Shulin Lee Shulin Lee is an Influencer #1 LinkedIn Creator 🇸🇬 | Founder helping you level up⚡️Follow for Careers & Work Culture insights⚡️Lawyer turned Recruiter 272,470 followers 12mo Report this post Law school taught me the law. But building a career? That’s a different story. Many years ago, I walked into my first day as a lawyer, armed with my 2nd Upper Degree, thinking I was ready. I WAS NOT. Here are 12 lessons I learnt the hard way: (I wish someone had shared with me before I started) 1️⃣ It’s Okay to Ask for Help Pretending to know everything? Rookie mistake. Ask questions. Get clarity. Even top-tier lawyers do. 2️⃣ Networking > Billable Hours Winning cases builds a reputation, but relationships build careers. That partner you avoid at events? Talk to them. 3️⃣ Reputation Is Currency Every email. Every call. They all shape how people see you. Guard your reputation like it’s your most valuable client. 4️⃣ Billing ≠ Just Hours Worked It’s not about grinding for numbers—it’s about delivering value. (And yes, padding your billables will get you noticed—for all the wrong reasons.) 5️⃣ Clients Crave More Than Advice They want trust, empathy, and someone who listens. Legal skills matter, but human connection wins clients for life. 6️⃣ The Best Lawyers Never Stop Evolving The law changes, and so should you. Stay curious. Stay sharp. Stay ahead. 7️⃣ Mentors = Secret Weapons Find someone who’s been where you want to go. The right mentor will save you years of trial and error. 8️⃣ Burnout Is the Silent Killer The late nights will come, but don’t make them your norm. Protect your energy—because no case is worth your health. 9️⃣ Pick Your Battles Not every fight is worth the courtroom. Strategic restraint is a superpower. 🔟 Mistakes Are Inevitable Here’s the secret: It’s not about never failing—it’s about how you bounce back. Own it, learn from it, and keep moving. 1️⃣1️⃣ It’s a Marathon, Not a Sprint You don’t need to win every deal or impress every partner. Pacing yourself is how you last in this game. 1️⃣2️⃣ Never Lose Sight of Your WHY When the grind feels endless (and it will), your WHY will keep you grounded. Don’t let go of it—it’s your anchor. Law school taught you the law. But no one taught you how to build a career in it. Lawyers reading this, did I miss anything? What else would you add to my list? --- Repost this♻️ to help the juniors out there! ➕ Follow Shulin Lee for more. P.S. To the trainees starting out: It’s okay to feel scared. P.P.S. The partners you’re intimidated by? They were once where you are. Everyone starts somewhere. You've got this! …more 1,138 361 Comments Like Comment Share Copy LinkedIn Facebook X More in Productivity Importance of Collaboration Focus Enhancement Strategies Reviewing Progress Regularly Administrative Tips For Productivity Resilience Building For Efficiency Boosting Daily Creativity Creating To-Do Lists Effectively Managing Workplace Interruptions Healthy Eating For Productivity Maximizing Workplace Productivity Balancing Personal Development with Work Goals Writing Productive Emails Using Mind Mapping for Project Planning Managing Screen Time At Work Evaluating Workflows for Efficiency Daily Routines for Increased Focus Organizing Digital Files Efficiently Evaluating Productivity Tools for Teams Deep Work Sessions Structure Virtual Collaboration Productivity Strategies for Fostering Innovation at Work Tools for Tracking Work Progress Productivity and Task Management Handling Meeting Overload Time Management In Crisis Daily Routines for Success Product Value Creation Evening Routine For Efficiency Excel Mastery Techniques Productivity Methods And Systems Streamlining Daily Tasks Cross-Functional Productivity Setting Boundaries to Avoid Burnout Handling Office Chatter Conducting Productivity Audits Using Feedback Loops to Improve Processes Creating Effective Standard Operating Procedures Livestock Production Management Overcoming Perfectionism Managing Underperformance Tips for Staying Motivated During Long Projects Improving Concentration Skills Improving Focus Techniques Automating Repetitive Work Tasks Ergonomic Setup For Productivity Energy Level Optimization Lunch Breaks For Productivity Efficient Decision-Making Process Strategies for Effective Delegation Email Productivity Tools Using Analytics to Measure Productivity Minimizing Commute Time Impact Calendar Management Tools Managing Time Zones in Global Teams Stress Management Techniques Short Burst Work Sessions Importance of Quality Content Techniques for Reducing Meeting Fatigue Planning Weekly Goals for Better Outcomes Streamlining Communication in Teams Implementing Agile Methodologies for Teams Avoiding Decision Fatigue Work Management Setting Boundaries For Focus Factors Influencing Workplace Productivity Managing Stress For Efficiency Prioritizing Tasks in a Workday Building a Habit of Daily Reflection Handling Urgent Tasks Declutter Work Desk Strategies Workflow Automation Hacks Podcast Creation Tips Optimizing Manufacturing Performance Effective Meeting Practices Workday Management Tips Importance Of Documentation Peak Performance Techniques Remote Work Productivity Improving Research Outcomes Using AI For Task Management Pomodoro Method Applications Using Kanban Boards for Task Management Techniques for Enhancing Creative Thinking Balancing Creativity And Efficiency Techniques for Better Decision Making Goal Setting For Efficiency Time Tracking For Productivity Focus And Concentration Hacks Overcoming Procrastination Building Productive Teams Improving Sleep For Productivity Workplace Focus Desk Organization For Focus Developer Productivity Metrics Poultry Production Practices Conducting Efficient Check-Ins Setting Up Daily Stand-Up Meetings Personal Productivity Metrics Goal Setting Strategies Improving Task Switching Skills Focus Music For Deep Work Developing a Personal Productivity System Creating a Mindful Work Environment Morning Routine For Productivity Farm Productivity Tools Break Techniques For Efficiency Resource Optimization Performance Optimization Techniques Adopting Minimalism in Workspaces Importance of Specialization Healthcare Model Advantages Healthy Work Habits Formation Incorporating Breaks for Sustained Energy Balancing Workload Effectively Task Prioritization Methods Setting Realistic Deadlines Managing Distractions At Home Managing Deadlines Without Stress Scheduling Downtime Effectively Email Automation Benefits Multitasking Without Burnout Operational Efficiency Concepts Optimizing Meeting Productivity Adapting to Change in Fast-Paced Environments Time Management Techniques Agile Task Management AI in Knowledge Work Productivity Utilizing Time Blocking for Daily Tasks Creative Breaks At Work Creating a Productive Workspace Environment Using Data To Improve Efficiency Implementing Kaizen In Workplace Manufacturing Improvement Techniques Strategies for Reducing Workplace Distractions Proactive Planning Techniques Managing Email Overload at Work Using Visual Aids for Task Management Enhancing Collaboration with Digital Tools Digital Decluttering Tips Analyzing Time-Use Patterns Setting Clear Goals for Team Projects Maintaining Focus in Open Office Environments Building Productive Habits Leveraging Technology For Better Productivity Planning Sprints Effectively The Power Of Feedback Using Checklists to Boost Efficiency Using Mindfulness For Focus Balancing Multiple Projects at Once Show more Show less Explore categories Hospitality & Tourism Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Recruitment & HR Customer Experience Real Estate Marketing Sales Retail & Merchandising Science Supply Chain Management Future Of Work Consulting Writing Economics Artificial Intelligence Employee Experience Healthcare Workplace Trends Fundraising Networking Corporate Social Responsibility Negotiation Communication Engineering Career Business Strategy Change Management Organizational Culture Design Innovation Event Planning Training & Development Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:30 |
http://coderabbit.ai/ | AI Code Reviews | CodeRabbit | Try for Free Features Enterprise Customers Pricing Blog Resources Docs Trust Center Contact Us FAQ Log In Get a free trial Cut code review time & bugs in half Instantly. Reviews for AI-powered teams who move fast (but don’t break things) Try it for free 2-click install | Also Available in CLI & IDE The leader in AI code reviews 2M Repositories 13M Pull Requests Most installed AI App Why teams prefer CodeRabbit Why teams prefer CodeRabbit Trusted by 10 , 000+ customers Meet our customers Code reviews were hard before. Now, they feel impossible. Your team moves fast with AI. But fast shouldn’t mean sloppy. We make sure every line still earns its merge. Faster reviews + better code. We do the heavy lifting & spot the hard to find issues. You do the final 10%. See a sample review //1-click & AI fixes Catch fast. Fix fast. 1-click commits for easy fixes and a “Fix with AI” button for harder ones. //Summaries & visual diagrams TL;DR for your diff. Quick context with a summary of changes, a walkthrough & an architectural diagram. //Agentic reviews Find the bugs. Skip the noise. We find bugs humans miss – & flag the time consuming and tedious. Without the noise. //Chat Chat with the CodeRabbit bot directly. Give feedback on reviews to create Learnings. Or create issues, trigger docstrings & more. //Your code, your way Most customizable tool. Customize everything from your coding guidelines to your workflow in a yaml file. //Automated reports The reports you need. Automate the creation of your daily standup reports, sprint reviews, and more. CR_Flexibility The only tool that reviews everywhere you work. Review at the PR stage or directly in your IDE & CLI GIT IDE CLI CR_Quality Industry-leading context. Codebase-awareness is tablestakes. We pull in dozens more points of context than other tools. See a sample review 1. Codebase intelligence Codegraph and custom guidelines help us understand complex dependencies across files to uncover the impact of changes. 2. External context We bring the right context via MCP servers, Linked Issues (Jira & Linear) & Web Query (to fetch the latest info on the web). 3. Linters & Scanners 40+ linters and security scanners catch more bugs – while we filter out the noise from false positives. CR_Intelligence Code reviews that learn from you. Set the baseline with your rules and style guides, then train the agent with feedback via replies. Reviews improve continuously. CodeRabbit learnings Give our AI agent feedback in natural language and it takes that into account in future reviews. Path & AST-based instructions Easily configurable instructions that let you quickly share how you want your code reviewed. Coding agent guidelines Pass your coding instructions from your AI coding tool to CodeRabbit in one click. CR_Finish Ship faster with pre-merge checks & finishing touches. Save hours of work and make sure your code’s ready to ship. Custom checks Create your own pre-merge code quality checks in natural language. Unit test generation Check test coverage and immediately generate any missing tests. Docstring generation Create docstrings to make it easier to understand the file in the future. CR_Security We take security seriously. Architected for security We protect your code and privacy with an architecture designed to ensure your code is private. SSL encrypted data End-to-end encryption protects your code during reviews with zero data retention post-review. SOC 2 Type II certified Enterprise-grade security validated annually through independent SOC2 Type II audits. Get started in 2 clicks. No credit card needed Your browser does not support the video. Start reviewing See pricing Your browser does not support the video. Why teams prefer CodeRabbit I love how deeply it analyzes code… it spots potential errors more often than other tools. Gabriel Almeida Technical Founder @ Langflow CodeRabbit routinely catches off-by-ones, edge cases, and even spec/security slips before they hit production. Brandon Romano Senior Staff Software Engineer @ Clerk It enforced a more precise UUID check and saved us from a production issue. Kyrylo Buha Member of Technical Staff @ Writer Writing code faster was never the issue; the bottleneck was always code review. I feel like CodeRabbit is solving that one problem and that was attractive. Why not solve that problem before we use a coding agent? Kiran Kanagasekar Senior Engineering Manager @ TaskRabbit CodeRabbit provides instant and accurate feedback on pull requests often catching real issues. Auto-generated summaries and walkthroughs are very helpful for human code reviewers. Our team loves having contextual conversations with AI right within GitHub's comment threads, turning each pull request into a collaborative AI chat. It is the most innovative application of AI in coding since Copilot! Code reviews will never be the same, thanks to CodeRabbit! Tanveer Gill CTO and Co-Founder, FluxNinja With CodeRabbit,, everybody was like, give me this. This is fantastic. It speeds up code reviews. We went from a small test to full adoption very quickly. Michael Archibald CTO @ SalesRabbit I love how deeply it analyzes code… it spots potential errors more often than other tools. Gabriel Almeida Technical Founder @ Langflow CodeRabbit routinely catches off-by-ones, edge cases, and even spec/security slips before they hit production. Brandon Romano Senior Staff Software Engineer @ Clerk It enforced a more precise UUID check and saved us from a production issue. Kyrylo Buha Member of Technical Staff @ Writer Writing code faster was never the issue; the bottleneck was always code review. I feel like CodeRabbit is solving that one problem and that was attractive. Why not solve that problem before we use a coding agent? Kiran Kanagasekar Senior Engineering Manager @ TaskRabbit CodeRabbit provides instant and accurate feedback on pull requests often catching real issues. Auto-generated summaries and walkthroughs are very helpful for human code reviewers. Our team loves having contextual conversations with AI right within GitHub's comment threads, turning each pull request into a collaborative AI chat. It is the most innovative application of AI in coding since Copilot! Code reviews will never be the same, thanks to CodeRabbit! Tanveer Gill CTO and Co-Founder, FluxNinja With CodeRabbit,, everybody was like, give me this. This is fantastic. It speeds up code reviews. We went from a small test to full adoption very quickly. Michael Archibald CTO @ SalesRabbit Products Pull Request Reviews IDE Reviews CLI Reviews Navigation About Us Features FAQ System Status Careers DPA Startup Program Vulnerability Disclosure Resources Blog Docs Changelog Case Studies Trust Center Brand Guidelines Contact Support Sales Pricing Partnerships Subscribe By signing up you agree to our Terms of Use and Privacy Policy Select language English 日本語 Terms of Service Privacy Policy CodeRabbit Inc © 2026 Products Pull Request Reviews IDE Reviews CLI Reviews Navigation About Us Features FAQ System Status Careers DPA Startup Program Vulnerability Disclosure Resources Blog Docs Changelog Case Studies Trust Center Brand Guidelines Contact Support Sales Pricing Partnerships Subscribe By signing up you agree to our Terms of Use and Privacy Policy | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#about-xss-attack | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://dev.to/ngxp/s3e7-liz-saling-on-life-at-github-attaining-your-ultimate-devlife#main-content | S3E7 | Liz Saling on Life at GitHub & Attaining Your Ultimate Dev.Life - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close Angular Experience Follow S3E7 | Liz Saling on Life at GitHub & Attaining Your Ultimate Dev.Life Nov 8 '22 play How do you rise the ranks to go from data entry to becoming a director of Engineering for the world’s largest source code host with more than 200 million repositories? Liz Saling, Director of Engineering at GitHub, joins us to share her journey of quickly moving into leadership positions, securing jobs at powerhouse companies, the inside scoop about life at GitHub, and finding true fulfillment in both life and career. She’s happily living her ultimate dev life (complete with ample use of emojis) and shares some simple yet effective tips for how YOU can too! LINKS: https://twitter.com/LizSaling https://www.lizsaling.com/ https://www.linkedin.com/in/lizsaling/ https://socialimpact.github.com/ https://lizsaling.medium.com/ CONNECT WITH US: Liz Saling @lizsaling Brooke Avery @JediBravery Erik Slack @erik_slack Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://developer.x.com/developer-terms/policy#SVGID_1_ | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://www.spreaker.com/user/14532324/s2e13-chau-tran-tale-of-a-vietnamese-imm | S2E13 | Chau Tran, Tale of a Vietnamese Immigrant Discover Your Library Search For Podcasters Your Podcasts Free Our Platform How Spreaker Works Podcasts App Spreaker Create New Prime Network Help { if (!hidden) { $refs.inputMobile.focus(); } }); if (isSearch && !query) { if (window.innerWidth Sign up Login Sign up For Podcasters Your Podcasts Free Settings Light Theme Dark Theme Our Platform How Spreaker Works Podcasts App Spreaker Create New Prime Network Help { if (this.toast) { this.toast = null; } }, timings[this.toast.type]); }, getClassType() { return { 'bg-neutral-700 dark:bg-neutral-100 text-white dark:text-neutral-950': this .toast?.type === 'default', 'bg-sky-700 text-white': this.toast?.type === 'info', 'bg-emerald-700 text-white': this.toast?.type === 'success', 'bg-red-800 text-white': this.toast?.type === 'error', 'bg-orange-400 text-neutral-950': this.toast?.type === 'warning' } } }" x-on:toast.window="showToast($event.detail)" x-show="toast" class="fixed left-0 right-0 z-10 md:left-[250px]" x-transition> Dev Life S2E13 | Chau Tran, Tale of a Vietnamese Immigrant Apr 25, 2022 · 59m 10s Loading Play Pause Add to queue In queue { SP.Utils.setDocumentShouldScroll(!opened); })"> Download Download and listen anywhere Download your favorite episodes and enjoy them, wherever you are! Sign up or log in now to access offline listening. Sign up to download { SP.Utils.setDocumentShouldScroll(!opened); })"> Embed Embed episode `; }, copyToClipboard() { this.copyStatus = 'DONE'; SP.Utils.copyToClipboard(this.getIframeCode()); setTimeout(() => { this.copyStatus = 'IDLE'; }, 2000); } }"> Dark Light Copy Done Looking to add a personal touch? Explore all the embedding options available in our developer's guide Share on X Share on Facebook Share on Bluesky Share on Whatsapp Share on Telegram Share on LinkedIn Description SHOW SUMMARY: In today’s episode of NgXP, we get real and raw with Chau Tran about his journey as a Vietnamese immigrant and developer. Chau shares his experiences working in... show more SHOW SUMMARY: In today’s episode of NgXP, we get real and raw with Chau Tran about his journey as a Vietnamese immigrant and developer. Chau shares his experiences working in the U.S. after having immigrated. From the good to the bad, Chau discusses both the opportunities he’s seized to the inequalities, biases, and prejudices he has experienced as a programmer of Asian descent. How can we become aware of racial and national biases or stereotypes? What can we do to help our teams, companies, and the developer community at large be better friends and colleagues to our coworkers from beyond our own borders? LINKS: https://twitter.com/ngvnofficial https://nartc.me/ https://www.youtube.com/c/ChauTran/videos CONNECT WITH US: Chau Tran @NarTC1410 Brooke Avery @JediBravery Erik Slack @erik_slack show less Comments Sign in to leave a comment Information Author Dev Life Podcast Organization Dev Life Podcast Website - Tags #angular #asian #chau #code #coding #developer #development #family #financial #immigrant #javascript #nartc #nrwl #programmer #programmers #programming #tran #vietnam 🇬🇧 English 🇬🇧 English 🇮🇹 Italiano 🇪🇸 Espanõl 🇬🇧 English 🇬🇧 English 🇮🇹 Italiano 🇪🇸 Espanõl Terms Privacy {e.preventDefault(); showOneTrustPreferenceCenter();}" class="inline-flex items-center gap-2 hover:underline"> Your Privacy Choices Copyright 2026 - Spreaker Inc. an iHeartMedia Company { SP.Utils.setDocumentShouldScroll(!opened); })"> Playing Now Queue Looks like you don't have any active episode Browse Spreaker Catalogue to discover great new content Browse now Current Looks like you don't have any episodes in your queue Browse Spreaker Catalogue to discover great new content Browse now 1" class="mt-6"> Next Up Manage Done svg]:text-white"> Up Up Down Down Remove svg]:text-white"> It's so quiet here... Time to discover new episodes! Discover Your Library Search { SP.Utils.setDocumentShouldScroll(!opened); })"> Unlock Spreaker's full potential Sign up to keep listening, access your Library to pick up episodes right where you left off, and connect with your favorite creators. Experience the ultimate podcast listening on Spreaker! Sign up for free | 2026-01-13T08:48:30 |
https://stackoverflow.blog/code-for-a-living/ | Code for a Living - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Code for a Living Related Tags AI llm contributed Business Hub partnercontent Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed December 10, 2024 It’s not what you know, it’s how you know you know it The complex relationship of give-and-take in the knowledge journey is untangled in the results from the latest Stack Overflow Knows survey. Erin Yepis 1 comment Pulse survey Code for a Living AI learning knowledge sharing December 29, 2023 The hardest part of building software is not coding, it's requirements Why replacing programmers with AI won’t be so easy. Jared Toporek 43 comment s AI ai assistant Code for a Living llm requirements software engineering contributed December 28, 2023 Self-healing code is the future of software development Developers love automating solutions to their problems, and with the rise of generative AI, this concept is likely to be applied to both the creation, maintenance, and the improvement of code at an entirely new level. Ben Popper 19 comment s AI ai assistant Code for a Living continuous integration generative AI December 27, 2023 Stop saying “technical debt” Everyone who says "tech debt" assumes they know what we’re all talking about, but their individual definitions differ quite a bit. Chelsea Troy 50 comment s Code for a Living code maintenance technical debt contributed December 26, 2023 Developer with ADHD? You’re not alone. Is there a connection between programming and ADHD? And could it be that people with ADHD are particularly well-suited to programming careers? Eira May 26 comment s adhd Code for a Living neurodivergence December 25, 2023 Is software getting worse? With all the advancements in software development, apps could be much better. Why aren't they? Isaac Lyman 83 comment s Code for a Living software development contributed December 11, 2023 Three types of AI-assisted programmers What matters isn’t just whether you use it, but how. Isaac Lyman 26 comment s Code for a Living AI career development contributed November 27, 2023 Are remote workers more productive? That’s the wrong question. Plenty of workers prefer flexibility, regardless of what the research says. Eira May 12 comment s Code for a Living remote work Productivity Business Hub November 9, 2023 An intuitive introduction to text embeddings Text embeddings are key to LLMs and convert text into vector coordinates. Kevin Henner 8 comment s Code for a Living AI text embeddings November 8, 2023 The product approach to open source communities A business wouldn’t take its product development for granted, so why would you neglect the OSS community that’s fundamental to the project’s very existence? Mike Donovan 1 comment Open Source coding community product management Code for a Living Business Hub November 1, 2023 AI is only as good as the data: Q&A with Satish Jayanthi of Coalesce AI systems obey the golden rule: garbage in, garbage out, Want good results, feed it good data. Ryan Donovan 8 comment s AI data data quality Code for a Living Q&A October 30, 2023 Edge and beyond: How to meet the increasing demand for memory The opportunities for edge computing are huge—but so are the memory requirements. John Overton 0 comment s Sponsored edge computing memory Code for a Living partnercontent October 26, 2023 Hopping instead of hustling: Survey tells us how developers are taking care of business Both new talent and late-career developers are more likely to be looking. Erin Yepis 4 comment s Pulse survey Code for a Living jobs career Business Hub October 23, 2023 Privacy in the age of generative AI The core challenge posed by generative AI right now is that unlike conventional applications, LLMs have no “delete” button. Sean Falconer 4 comment s generative AI privacy Code for a Living llm Business Hub October 18, 2023 Retrieval augmented generation: Keeping LLMs relevant and current Retrieval augmented generation (RAG) is a strategy that helps address both LLM hallucinations and out-of-date training data. Manny Silva 7 comment s Code for a Living retrieval augmented generation AI llm contributed October 16, 2023 Is AI enough to increase your productivity? Being an effective coder with a code generation tool still requires you to be an effective coder without one. Ryan Donovan 2 comment s AI ai coding Productivity Code for a Living October 12, 2023 Integrating AI tools into your workflow For AI tools to be useful to your team, they have to fit into your existing workflows. Eira May 1 comment AI ai coding developer tools Code for a Living Business Hub October 11, 2023 Wondering how sustainable your buildings are? Make your data speak If we can make operational data easier to manage and easier to access through simple, standardized APIs, everyone can transform their companies into sustainable data-driven organizations. Philippe Raffin 0 comment s Sponsored Code for a Living Partner Content partnercontent API data data analytics sustainability October 9, 2023 From prototype to production: Vector databases in generative AI applications What exactly is a vector database? And how does it relate to generative AI? Leonie Monigatti 1 comment Code for a Living vector search database vector contributed October 5, 2023 Open Discussion: What can be done to reduce infrastructure-as-code complexity? Highlighting one of the interesting discussions going on in our Collectives. Ben Popper 0 comment s infrastructure as code Code for a Living discussion September 25, 2023 Behind the scenes with OverflowAI Search Go behind the scenes to learn how we designed our new search. Emma Bulajewski , Ellen Chan 4 comment s Design search overflowai Code for a Living September 20, 2023 Do you need a specialized vector database to implement vector search well? Semantic search and augmenting LLMs have sent everyone turning their text into vectors. But where do you store all that vector data? Stanimira Vlaeva , Benjamin Flast 2 comment s Sponsored database vector search mongodb partnercontent Partner Content Code for a Living September 13, 2023 How to land the manager-to-IC pivot The conventional metaphor for career success is a ladder, but there are a lot of problems with this narrative. Eira May 6 comment s career advice career development Code for a Living August 30, 2023 Journey to the cloud part I: Migrating Stack Overflow Teams to Azure Stack Overflow for Teams' journey to the cloud started with a new name. Wouter de Kort 1 comment Engineering Code for a Living cloud Stack Internal Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
https://open.forem.com/techresolve/solved-i-hired-two-junior-people-and-realized-media-buyers-being-bad-at-creative-strategy-is-g1g | Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Darian Vance Posted on Dec 31, 2025 • Originally published at wp.me Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem # devops # programming # tutorial # cloud 🚀 Executive Summary TL;DR: Junior media buyers often lack creative strategy, leading to suboptimal ad performance and creative fatigue despite effective targeting. The solution involves implementing data-driven feedback loops, cross-functional training, and standardized creative briefs and playbooks to empower them with objective insights and strategic frameworks. 🎯 Key Takeaways Implement automated reporting dashboards with granular creative tagging (e.g., JSON-like metadata) to enable data-driven analysis of creative performance, moving from ‘this creative performed well’ to ‘UGC testimonial visuals with short copy and FOMO appeal drive highest ROAS’. Develop a skill matrix and conduct cross-functional workshops to train media buyers on fundamental creative principles like visual hierarchy and audience-creative matching, fostering a deeper understanding of ‘why’ certain creatives resonate. Standardize creative briefs with detailed templates that force strategic thinking about objectives, audience, and desired outcomes, and curate ‘Creative Playbooks’ with ‘Why it worked’ analysis for high-performing assets to codify best practices. Addressing the critical gap where junior media buyers lack creative strategy can derail campaigns. This post explores how integrating data-driven creative insights and structured collaboration can bridge this skill deficit, optimizing ad performance and team efficiency. The Hidden Cost: Symptoms of Poor Creative Strategy from Media Buyers In the fast-paced world of digital advertising, media buyers are often expected to be maestros of targeting, bidding, and optimization algorithms. However, a significant blind spot can emerge when junior team members, adept at platform mechanics, lack a fundamental understanding of creative strategy. This isn’t just an inconvenience; it’s a performance bottleneck with tangible, detrimental symptoms for your campaigns and your team’s morale. Suboptimal Ad Performance Despite Flawless Targeting: You’re reaching the right people, but they’re not converting. This often points to creatives that fail to resonate, persuade, or stand out in a crowded feed. The media buyer might correctly identify a high-performing audience, but without creative insight, they can’t articulate what kind of message that audience truly needs. Rapid Creative Fatigue: Campaigns burn through creatives at an alarming rate. Junior buyers, lacking strategic depth, might continuously request minor variations of existing assets (“change the background color,” “try a different font”) rather than fundamentally new conceptual approaches informed by performance data. This leads to diminishing returns and wasted creative resources. Vague or Unactionable Feedback for Creative Teams: When a campaign underperforms, the feedback loop from media buying to creative is often “this isn’t working.” Without a strategic understanding, junior buyers struggle to provide specific, data-backed insights like “the problem isn’t the offer, it’s the visual hierarchy failing to highlight the value proposition” or “the hook isn’t strong enough for this cold audience segment.” Repetitive Creative Requests: Creative teams receive requests that lack direction or are simply “more of the same, but different.” This prevents iterative learning and innovation, leading to a stagnant creative pipeline and frustration on both sides. Increased Overhead and Burnout for Senior Staff: Senior media buyers or creative directors end up constantly stepping in to fill the strategic gap, reviewing creative briefs, providing ad-hoc training, and re-interpreting performance data. This diverts their time from higher-level strategic initiatives and leads to team-wide burnout. Solution 1: Implement a Data-Driven Creative Feedback Loop The most effective way to empower junior media buyers with creative strategy is to arm them with objective, data-backed insights. By automating the analysis of creative performance and presenting it in an easily digestible format, you transform subjective hunches into actionable intelligence. Mechanism and Implementation: Automated Reporting Dashboards: Centralize your ad performance data. Tools like Google Looker Studio (formerly Data Studio), Power BI, or Tableau can pull data directly from ad platforms (Facebook Ads, Google Ads, TikTok Ads) and integrate with your CRM or attribution tools. The key is to visualize performance by creative asset . Granular Creative Tagging & Metadata: This is crucial. Every creative asset should be tagged with relevant metadata that describes its key attributes. This allows for deep-dive analysis beyond just “Creative ID 123 performs well.” Example: Creative Tagging Strategy Before launching, ensure your creative assets are tagged consistently. This can be done via your asset management system, file naming conventions, or directly within ad platforms if they support custom labels. Imagine a JSON-like structure for metadata: { "creative_id": "CR_001_v2", "campaign_objective": "conversion", "visual_type": "UGC_testimonial", "copy_length": "short", "cta_type": "Shop Now", "emotional_appeal": "fear_of_missing_out", "product_feature_highlight": "durability", "ad_format": "static_image", "test_variant": "A" } Enter fullscreen mode Exit fullscreen mode Example: SQL Query for Creative Performance Analysis Using these tags, a junior media buyer can query performance data to identify trends. For instance, to see which “visual_type” performs best for “conversion” campaigns: SELECT creative_metadata.visual_type, AVG(ad_performance.ROAS) AS average_roas, AVG(ad_performance.CTR) AS average_ctr, SUM(ad_performance.conversions) AS total_conversions FROM ad_performance JOIN creative_metadata ON ad_performance.creative_id = creative_metadata.creative_id WHERE creative_metadata.campaign_objective = 'conversion' GROUP BY creative_metadata.visual_type ORDER BY average_roas DESC; Enter fullscreen mode Exit fullscreen mode This kind of query, easily built into a dashboard, helps buyers move from “this creative performed well” to “UGC testimonial visuals with a short copy and FOMO appeal are driving the highest ROAS for conversions in this audience segment.” Solution 2: Cross-Functional Training & Skill Matrix Development While data provides answers, understanding why those answers are true requires foundational knowledge. Proactive training and clear skill development paths are crucial for long-term success. Mechanism and Implementation: Dedicated Workshops: Organize regular sessions where creative leads educate media buyers on fundamental creative principles (e.g., visual hierarchy, storytelling arcs, color psychology, psychological triggers in advertising). Conversely, media buyers can teach creative teams about ad platform specific limitations, common performance metrics, and audience segmentation. “Shadowing” Programs: Encourage media buyers to spend time with graphic designers, video editors, and copywriters to understand the creative process. Similarly, creative team members can shadow media buyers during campaign setup and optimization meetings to grasp performance drivers. Skill Matrix Development: Define the desired creative strategy skills for media buyers. This isn’t about turning them into full-stack designers, but about ensuring they can critically evaluate creative, interpret feedback, and provide strategic direction. Example: Skill Matrix for Junior Media Buyers (Creative Strategy Focus) Develop a shared competency framework. Here’s a simplified example: Skill Category Specific Skill Description Proficiency Level (1-5) Training Resource/Action Creative Analysis Interpret Visual Hierarchy Can identify primary message, CTA, and brand elements in an ad and assess their prominence. 3 Creative team workshop: “Decoding Ad Visuals” Creative Strategy Audience-Creative Match Can articulate why a certain creative concept is suitable for a specific audience segment (e.g., cold vs. warm). 2 Shadowing creative brief sessions, Reviewing creative playbooks Feedback Loop Data-Driven Creative Feedback Provides specific, actionable feedback to creative teams using performance data (e.g., CTR on CTA, engagement rate on hook). 3 Bi-weekly creative review meetings, Dashboard walkthroughs Creative Briefing Articulate Creative Needs Can complete a detailed creative brief, clearly outlining objectives, audience, and key messages for new assets. 2 Template review, Senior buyer mentorship Regularly assess and update these levels, providing targeted training and mentorship. Solution 3: Standardize Creative Briefs and Introduce “Creative Playbooks” Consistency and documented best practices can significantly elevate the creative output and strategic thinking of junior buyers. By providing frameworks and examples, you give them a clear roadmap. Mechanism and Implementation: Mandatory, Detailed Creative Brief Templates: Move beyond simple requests. A robust creative brief forces the media buyer to think strategically about the creative’s purpose, audience, and desired outcome before requesting assets. Living “Creative Playbooks” or Asset Libraries: Curate a collection of high-performing creatives. This isn’t just a dump of old ads; it’s a categorized library with analysis explaining why each creative worked (or didn’t). “Why it worked” Analysis: For each successful creative in the playbook, provide a brief summary of the campaign, audience, key performance indicators, and critically, a strategic breakdown of what made the creative effective (e.g., “The scarcity appeal combined with strong social proof drove a 15% higher CVR for this retargeting audience.”). Example: Creative Brief Template Structure Here’s a simplified structure for a mandatory creative brief that prompts strategic thinking: ### Creative Brief Template: [Campaign Name] - [Date] #### 1. Campaign Overview & Objective: * Campaign Name: * Primary Marketing Objective (e.g., Brand Awareness, Lead Generation, Purchase Conversion): * Key Performance Indicators (KPIs) for this creative: #### 2. Target Audience: * Specific Audience Segment (e.g., Cold Audience - "Interested in X," Retargeting - "Added to Cart"): * Key Persona Insights (Pain Points, Desires, Motivations relevant to this product/service): #### 3. Key Message & Value Proposition: * Core Message to convey: * Unique Selling Proposition (USP) highlighted: * Desired Emotional Response from viewer: #### 4. Creative Deliverables: * Requested Ad Formats (e.g., 1x Static Image, 1x 15-sec Video, 2x Copy Variants): * Required Dimensions/Aspect Ratios: * Call to Action (CTA) Text: * Any specific visual/brand guidelines or exclusions: #### 5. Previous Learnings & Inspiration: * What have we learned from past creatives for this audience/objective? * Links to successful internal/competitor creatives for inspiration (with notes on why they are inspiring): Enter fullscreen mode Exit fullscreen mode Example: Creative Playbook Entry An entry in your internal “Creative Playbook” might look like this: ### Creative Playbook: High-Performing UGC Testimonial (Q3 2023) * Creative ID: CR_UGC_007 * Campaign Type: Conversion - Retargeting (Viewed Product Page) * Ad Platform: Facebook/Instagram Feed * Creative Asset: [Link to Video File/Image] * Ad Copy: "I was skeptical, but [Product Name] actually saved my [problem]! Seriously, you NEED this. [Link] #GameChanger" * Performance: 2.8x ROAS, 1.2% CTR, 8% CVR for retargeting audience. * Why it worked: + Authenticity: User-generated content (UGC) with a genuine-sounding testimonial immediately built trust with a retargeting audience familiar with the product. + Relatable Problem/Solution: The copy quickly addressed a common pain point ("saved my [problem]") which resonated with users who had previously shown interest. + Strong Urgency/FOMO: Phrases like "you NEED this" created a sense of urgency without being overtly pushy. + Clear CTA: Direct link and hashtag provided clear next steps. + Visual Engagement: The video showed the product in real-world use, increasing relatability. Enter fullscreen mode Exit fullscreen mode Comparison of Solutions Each solution tackles the problem from a different angle, offering varying degrees of immediate impact, resource intensity, and long-term benefit. Combining them often yields the best results. Solution Immediate Impact Long-Term Impact Resource Intensity Primary Beneficiary 1. Data-Driven Feedback Loop High. Provides quick insights into what’s working/not, informing immediate optimizations. Develops data literacy and objective decision-making habits. Builds a culture of continuous testing. Moderate (Initial setup of dashboards/tagging, ongoing maintenance). Junior Media Buyers, Senior Media Buyers, Creative Teams 2. Cross-Functional Training & Skill Matrix Moderate. Initial knowledge transfer, but skill application takes time. Elevates overall team competency, fosters empathy between departments, creates clear career paths. High (Time commitment for workshops, ongoing mentorship, matrix updates). Junior Media Buyers, Creative Teams, Team Leads 3. Standardized Briefs & Playbooks Moderate. Provides immediate structure and reduces ambiguity for new requests. Codifies best practices, reduces “reinventing the wheel,” accelerates onboarding of new talent. Moderate (Initial creation of templates/playbook content, ongoing updates). Junior Media Buyers, Creative Teams, Project Managers The problem of junior media buyers lacking creative strategy is not a reflection of their individual capabilities, but often a systemic gap in how teams are structured, trained, and supported. By integrating robust data analysis, fostering cross-functional understanding, and establishing clear frameworks, organizations can empower their entire team to drive significantly better campaign performance and cultivate a more strategically astute workforce. 👉 Read the original article on TechResolve.blog Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Darian Vance Follow Lead Cloud Architect & DevOps Strategist with 12+ years in the trenches. Founder of TechResolve. I turn complex cloud chaos into systems you can actually understand and manage. Education BS in Computer Science & 12 Years of Production Outages Work Founder & Lead Architect at TechResolve Joined Dec 26, 2025 More from Darian Vance Solved: PoE+++?! WHEN WILL THE MADNESS END? # devops # programming # tutorial # cloud Solved: How to look for a good MSP # devops # programming # tutorial # cloud 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:30 |
https://www.instagram.com/p/DJCy2XNT5hv/?utm_source=ig_web_button_share_sheet&hl=fa | Instagram Close By continuing, you agree to Instagram's Terms of Use and Privacy Policy . Instagram Log In Sign Up Meta About Blog Jobs Help API Privacy Terms Locations Instagram Lite Meta AI Threads Contact Uploading & Non-Users Meta Verified English Down chevron icon Afrikaans العربية Čeština Dansk Deutsch Ελληνικά English English (UK) Español (España) Español فارسی Suomi Français עברית Bahasa Indonesia Italiano 日本語 한국어 Bahasa Melayu Norsk Nederlands Polski Português (Brasil) Português (Portugal) Русский Svenska ภาษาไทย Filipino Türkçe 中文(简体) 中文(台灣) বাংলা ગુજરાતી हिन्दी Hrvatski Magyar ಕನ್ನಡ മലയാളം मराठी नेपाली ਪੰਜਾਬੀ සිංහල Slovenčina தமிழ் తెలుగు اردو Tiếng Việt 中文(香港) Български Français (Canada) Română Српски Українська © 2026 Instagram from Meta {"require":[["ScheduledServerJS","handle",null,[{"__bbox":{"require":[["AsyncData","resolve",[],["adp_WebWorkerV2HasteResponsePreloader_ZenonSignalingSharedWorkerV2Bundle_696606d77c05a7822775191",{"data":{"__bbox":{"hrp":{"hsrp":{"hsdp":{"clpData":{"1744178":{"r":1,"s":1},"1838142":{"r":1,"s":1},"6476":{"r":1000,"s":1},"1744334":{"r":1,"s":1},"1755537":{"r":1},"1109":{"r":1,"s":1},"5080":{"r":1,"s":1},"6934":{"r":1,"s":1},"1744234":{"r":1},"1848815":{"r":10000,"s":1},"177":{"r":1,"s":1},"1823926":{"r":1,"s":1},"1744057":{"r":500,"s":1},"1744058":{"r":5000,"s":1},"1744059":{"r":10000,"s":1},"1744060":{"r":1000,"s":1},"1814852":{"r":1}},"gkxData":{"1174":{"result":false,"hash":null},"1624":{"result":false,"hash":null},"2160":{"result":false,"hash":null},"2815":{"result":false,"hash":null},"4070":{"result":false,"hash":null},"4337":{"result":false,"hash":null},"5163":{"result":false,"hash":null},"5415":{"result":false,"hash":null},"5679":{"result":false,"hash":null},"6754":{"result":false,"hash":null},"6756":{"result":false,"hash":null},"6840":{"result":false,"hash":null},"7742":{"result":false,"hash":null},"8068":{"result":false,"hash":null},"8869":{"result":false,"hash":null},"9063":{"result":false,"hash":null},"10839":{"result":false,"hash":null},"11152":{"result":false,"hash":null},"11557":{"result":false,"hash":null},"11685":{"result":false,"hash":null},"12572":{"result":false,"hash":null},"15745":{"result":false,"hash":null},"17201":{"result":false,"hash":null},"20483":{"result":false,"hash":null},"20836":{"result":false,"hash":null},"20935":{"result":true,"hash":null},"20936":{"result":false,"hash":null},"21043":{"result":false,"hash":null},"21050":{"result":false,"hash":null},"21051":{"result":false,"hash":null},"21053":{"result":false,"hash":null},"21055":{"result":false,"hash":null},"21056":{"result":false,"hash":null},"21057":{"result":false,"hash":null},"21058":{"result":true,"hash":null},"21063":{"result":false,"hash":null},"21072":{"result":false,"hash":null},"21118":{"result":false,"hash":null},"21119":{"result":false,"hash":null},"21120":{"result":true,"hash":null},"21122":{"result":false,"hash":null},"21123":{"result":true,"hash":null},"21124":{"result":false,"hash":null},"23403":{"result":false,"hash":null},"23404":{"result":false,"hash":null},"25152":{"result":false,"hash":null},"25162":{"result":false,"hash":null},"25209":{"result":false,"hash":null},"25224":{"result":false,"hash":null}},"metaconfigData":{"15":{"value":false},"99":{"value":false},"262":{"value":false}},"qexData":{"2103":{"r":false,"l":"J{\"qeid\":\"0\",\"u\":\"\",\"t\":\"fb_acting_account\",\"gks\":[],\"qe\":null}"},"3872":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"104":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"128":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"344":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"},"388":{"r":null,"l":"J{\"qeid\":\"\",\"u\":\"\",\"t\":\"fb\",\"gks\":[],\"qe\":null}"}},"qplData":{"2369":{"r":100},"737":{"r":10},"1094":{},"2452":{},"2919":{"r":100},"3037":{"r":1},"3052":{"r":1},"6172":{},"8823":{}},"justknobxData":{"3323":{"r":true},"3414":{"r":true},"1276":{"r":true},"1021":{"r":true},"1942":{"r":100},"2269":{"r":true},"2595":{"r":0},"5207":{"r":60000},"5208":{"r":10000},"5209":{"r":10000},"5210":{"r":8000}}},"hblp":{"consistency":{"rev":1031920881},"rsrcMap":{"Y7kF\/NS":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yt\/r\/MyF1Cp9roAV.js","c":1,"p":":1","m":"1031920881_main","prelude":1},"h9W1bjy":{"type":"css","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v5\/yL\/l\/0,cross\/_CeKo1gBhPd.css","c":1,"p":":3","m":"1031920881_main"},"jUfb\/wE":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4i8lX4\/yd\/l\/en_US\/q1oHGhstCjypZD8TYpFtr_F_HMlhVCXGaLrUIo6P-HlkzkTUyyZ-Utty-ayoV4rCWTYBMC51sdJPa7odNDboPV5n.js","c":1,"p":":32,4,16,27,5,17,45,2","m":"1031920881_main"},"ntSwSkd":{"type":"js","src":"https:\/\/static.cdninstagram.com\/rsrc.php\/v4\/yd\/r\/2qlJiMIJI3r.js","c":1,"p":":10","m":"1031920881_main"}},"indexUpgrades":{"__hsdp":":39,52,209,53,38,50,30,6,7,25,11,9,10,8,12,26,13,5,206,16,23,14,51,21,22,24,63,27,34,33,35,41,37,36,32,17,15,40,208,29,28,19,43,47,46,31,18,42,45,48,44,49,20,1"}}},"jsmods":{"define":[["cr:310",["RunWWW"],{"__rc":["RunWWW",null]},-1],["cr:686",[],{"__rc":[null,null]},-1],["cr:1126",["TimeSliceSham"],{"__rc":["TimeSliceSham",null]},-1],["cr:3725",["clearTimeoutWWWOrMobile"],{"__rc":["clearTimeoutWWWOrMobile",null]},-1],["cr:4344",["setTimeoutWWWOrMobile"],{"__rc":["setTimeoutWWWOrMobile",null]},-1],["cr:6640",[],{"__rc":[null,null]},-1],["cr:8958",["FBJSON"],{"__rc":["FBJSON",null]},-1],["cr:12180",[],{"__rc":[null,null]},-1],["cr:1752405",["QPLAddCometRequestHeaders"],{"__rc":["QPLAddCometRequestHeaders",null]},-1],["cr:1984081",[],{"__rc":[null,null]},-1],["cr:975",[],{"__rc":[null,null]},-1],["cr:1078",[],{"__rc":[null,null]},-1],["cr:1080",["unexpectedUseInComet"],{"__rc":["unexpectedUseInComet",null]},-1],["cr:7730",["getFbtResult"],{"__rc":["getFbtResult",null]},-1],["cr:8572",["RpWebStateMachineLoggingBlocklistJSModuleWrapper"],{"__rc":["RpWebStateMachineLoggingBlocklistJSModuleWrapper",null]},-1],["cr:7385",["clearIntervalWWW"],{"__rc":["clearIntervalWWW",null]},-1],["cr:7389",["setIntervalAcrossTransitionsWWW"],{"__rc":["setIntervalAcrossTransitionsWWW",null]},-1],["cr:7391",["setTimeoutAcrossTransitionsWWW"],{"__rc":["setTimeoutAcrossTransitionsWWW",null]},-1],["cr:7429",["CometBootloaderLoggerUtil"],{"__rc":["CometBootloaderLoggerUtil",null]},-1],["cr:8959",["DTSG"],{"__rc":["DTSG",null]},-1],["cr:8960",["DTSG_ASYNC"],{"__rc":["DTSG_ASYNC",null]},-1],["cr:696703",["JSScheduler"],{"__rc":["JSScheduler",null]},-1],["IntlCurrentLocale",[],{"code":"en_US"},5954],["ServerNonce",[],{"ServerNonce":"zR1IeqAaYz1T1VdsAm3w44"},141],["SiteData",[],{"server_revision":1031920881,"client_revision":1031920881,"push_phase":"C3","pkg_cohort":"HYP:instagram_web_pkg","haste_session":"20466.HYP:instagram_web_pkg.2.1...0","pr":1,"manifest_base_uri":"https:\/\/static.cdninstagram.com","manifest_origin":"instagram","manifest_version_prefix":"","be_one_ahead":true,"is_rtl":false,"is_experimental_tier":false,"is_jit_warmed_up":true,"hsi":"7594765342166962440","semr_host_bucket":"","bl_hash_version":2,"comet_env":7,"wbloks_env":false,"ef_page":null,"compose_bootloads":false,"spin":4,"__spin_r":1031920881,"__spin_b":"trunk","__spin_t":1768294103,"vip":"157.240.215.174"},317],["InitialCookieConsent",[],{"deferCookies":false,"initialConsent":[1,2],"noCookies":false,"shouldShowCookieBanner":false,"shouldWaitForDeferredDatrCookie":false,"optedInIntegrations":["adobe_marketo_rest_api","brightedge","chili_piper_api","giphy_media","google_ads_pixel_frame_legacy","google_ads_pixel_legacy","google_ads_remarketing_tag","google_ads_services","google_apis","google_cached_img","google_double_click_uri_connect","google_fonts_font","google_img","google_paid_ads_frame","google_paid_ads_img","google_tag","google_translate","google_universal_analytics_legacy","google_universal_analytics_legacy_img","google_universal_analytics_legacy_script","google_uri_script","linkedin_insight","linkedin_insight_img","reachtheworld_s3","salesforce_mcp_beacon","tenor_images","tenor_media","twitter_analytics_pixel","twitter_legacy_embed","youtube_embed","advertiser_hosted_pixel","airbus_sat","amazon_media","apps_for_office","arkose_captcha","aspnet_cdn","autodesk_fusion","bing_maps","bing_widget","boku_wallet","bootstrap","box","cardinal_centinel_api","chromecast_extensions","cloudflare_cdnjs","cloudflare_datatables","cloudflare_relay","conversions_api_gateway","demandbase_api","digitalglobe_maps_api","dlocal","dropbox","esri_sat","facebook_sdk","fastly_relay","gmg_pulse_embed_iframe","google_ads_conversions_tag","google_drive","google_fonts_legacy","google_hosted_libraries","google_oauth_api","google_oauth_api_v2","google_recaptcha","here_map_ext","hive_streaming_video","iproov","isptoolbox","jquery","js_delivr","kbank","mathjax","meshy","meta_pixel","metacdn","microsoft_excel","microsoft_office_addin","microsoft_onedrive","microsoft_speech","microsoft_teams","mmi_tiles","oculus","open_street_map","paypal_billing_agreement","paypal_fastlane_sdk","paypal_oauth_api","payu","payu_india","plaid","platformized_adyen_checkout","plotly","pydata","razorpay","recruitics","rstudio","salesforce_lighting","shopify_app_bridge","stripe","team_center","tripshot","trustly_direct_debit_ach","turbo_gala","twilio_voice","unifier","unpkg","unsplash_api","unsplash_image_loading","vega","whatsapp_arkose_captcha","yoti_api","youtube_oembed_api"],"hasGranularThirdPartyCookieConsent":true,"exemptedIntegrations":["advertiser_hosted_pixel","airbus_sat","amazon_media","apps_for_office","arkose_captcha","aspnet_cdn","autodesk_fusion","bing_maps","bing_widget","boku_wallet","bootstrap","box","cardinal_centinel_api","chromecast_extensions","cloudflare_cdnjs","cloudflare_datatables","cloudflare_relay","conversions_api_gateway","demandbase_api","digitalglobe_maps_api","dlocal","dropbox","esri_sat","facebook_sdk","fastly_relay","gmg_pulse_embed_iframe","google_ads_conversions_tag","google_drive","google_fonts_legacy","google_hosted_libraries","google_oauth_api","google_oauth_api_v2","google_recaptcha","here_map_ext","hive_streaming_video","iproov","isptoolbox","jquery","js_delivr","kbank","mathjax","meshy","meta_pixel","metacdn","microsoft_excel","microsoft_office_addin","microsoft_onedrive","microsoft_speech","microsoft_teams","mmi_tiles","oculus","open_street_map","paypal_billing_agreement","paypal_fastlane_sdk","paypal_oauth_api","payu","payu_india","plaid","platformized_adyen_checkout","plotly","pydata","razorpay","recruitics","rstudio","salesforce_lighting","shopify_app_bridge","stripe","team_center","tripshot","trustly_direct_debit_ach","turbo_gala","twilio_voice","unifier","unpkg","unsplash_api","unsplash_image_loading","vega","whatsapp_arkose_captcha","yoti_api","youtube_oembed_api"],"nonBlockingBannerPage":false,"consentRequiredForMetaPixel":false},4328],["ServerTimeData",[],{"serverTime":1768294103523,"timeOfRequestStart":1768294103510.2,"timeOfResponseStart":1768294103510.2},5943],["QPLMsgTypesSitevarConfig",[],{"QPL_MSG_TYPES":["join","server_media_update","client_media_update","ring"]},6908],["CookiePrivacySandboxConfig",[],{"is_affected_by_samesite_lax":false},7723],["CookieDomain",[],{"domain":"instagram.com"},6421],["IntlVariationHoldout",[],{"disable_variation":false},6533],["IntlNumberTypeProps",["IntlCLDRNumberType05"],{"module":{"__m":"IntlCLDRNumberType05"}},7027],["ZenonApp",[],{"isSocialPlugin":false},8447],["CookieCoreConfig",[],{"_fbp":{"t":7776000},"csrftoken":{"t":34560000},"dpr":{"t":604800},"ds_user_id":{"t":7776000},"ig_lang":{"t":34560000},"igd_ls":{"t":34560000},"locale":{"t":604800},"wd":{"t":604800}},2104],["CurrentUserInitialData",[],{"ACCOUNT_ID":"0","USER_ID":"0","NAME":"","SHORT_NAME":null,"IS_BUSINESS_PERSON_ACCOUNT":false,"HAS_SECONDARY_BUSINESS_PERSON":false,"IS_FACEBOOK_WORK_ACCOUNT":false,"IS_INSTAGRAM_BUSINESS_PERSON":false,"IS_WABA_BUSINESS_PERSON":false,"IS_MESSENGER_ONLY_USER":false,"IS_DEACTIVATED_ALLOWED_ON_MESSENGER":false,"IS_MESSENGER_CALL_GUEST_USER":false,"IS_WORK_MESSENGER_CALL_GUEST_USER":false,"IS_WORKROOMS_USER":false,"APP_ID":"936619743392459","IS_BUSINESS_DOMAIN":false,"NON_FACEBOOK_USER_ID":"0","IS_INSTAGRAM_USER":1,"IG_USER_EIMU":"0"},270],["DateFormatConfig",[],{"numericDateOrder":["m","d","y"],"numericDateSeparator":"\/","shortDayNames":["Mon","Tue","Wed","Thu","Fri","Sat","Sun"],"narrowDayNames":["M","T","W","T","F","S","S"],"timeSeparator":":","weekStart":6,"formats":{"D":"D","D g:ia":"D g:ia","D M d":"D M d","D M d, Y":"D M d, Y","D M j":"D M j","D M j, g:ia":"D M j, g:ia","D M j, y":"D M j, y","D M j, Y g:ia":"D M j, Y g:ia","D, M j, Y":"D, M j, Y","F d":"F d","F d, Y":"F d, Y","F g":"F g","F j":"F j","F j, Y":"F j, Y","F j, Y \u0040 g:i A":"F j, Y \u0040 g:i A","F j, Y g:i a":"F j, Y g:i a","F jS":"F jS","F jS, g:ia":"F jS, g:ia","F jS, Y":"F jS, Y","F Y":"F Y","g A":"g A","g:i":"g:i","g:i A":"g:i A","g:i a":"g:i a","g:iA":"g:iA","g:ia":"g:ia","g:ia F jS, Y":"g:ia F jS, Y","g:iA l, F jS":"g:iA l, F jS","g:ia M j":"g:ia M j","g:ia M jS":"g:ia M jS","g:ia, F jS":"g:ia, F jS","g:iA, l M jS":"g:iA, l M jS","g:sa":"g:sa","H:I - M d, Y":"H:I - M d, Y","h:i a":"h:i a","h:m:s m\/d\/Y":"h:m:s m\/d\/Y","j":"j","l F d, Y":"l F d, Y","l g:ia":"l g:ia","l, F d, Y":"l, F d, Y","l, F j":"l, F j","l, F j, Y":"l, F j, Y","l, F jS":"l, F jS","l, F jS, g:ia":"l, F jS, g:ia","l, M j":"l, M j","l, M j, Y":"l, M j, Y","l, M j, Y g:ia":"l, M j, Y g:ia","M d":"M d","M d, Y":"M d, Y","M d, Y g:ia":"M d, Y g:ia","M d, Y ga":"M d, Y ga","M j":"M j","M j, Y":"M j, Y","M j, Y g:i A":"M j, Y g:i A","M j, Y g:ia":"M j, Y g:ia","M jS, g:ia":"M jS, g:ia","M Y":"M Y","M y":"M y","m-d-y":"m-d-y","M. d":"M. d","M. d, Y":"M. d, Y","j F Y":"j F Y","m.d.y":"m.d.y","m\/d":"m\/d","m\/d\/Y":"m\/d\/Y","m\/d\/y":"m\/d\/y","m\/d\/Y g:ia":"m\/d\/Y g:ia","m\/d\/y H:i:s":"m\/d\/y H:i:s","m\/d\/Y h:m":"m\/d\/Y h:m","n":"n","n\/j":"n\/j","n\/j, g:ia":"n\/j, g:ia","n\/j\/y":"n\/j\/y","Y":"Y","Y-m-d":"Y-m-d","Y\/m\/d":"Y\/m\/d","y\/m\/d":"y\/m\/d","j \/ F \/ Y":"j \/ F \/ Y"},"ordinalSuffixes":{"1":"st","2":"nd","3":"rd","4":"th","5":"th","6":"th","7":"th","8":"th","9":"th","10":"th","11":"th","12":"th","13":"th","14":"th","15":"th","16":"th","17":"th","18":"th","19":"th","20":"th","21":"st","22":"nd","23":"rd","24":"th","25":"th","26":"th","27":"th","28":"th","29":"th","30":"th","31":"st"}},165],["FbtQTOverrides",[],{"overrides":{}},551],["IntlPhonologicalRules",[],{"meta":{},"patterns":{}},1496],["IntlViewerContext",[],{"GENDER":3,"regionalLocale":null},772],["NumberFormatConfig",[],{"decimalSeparator":".","numberDelimiter":",","minDigitsForThousandsSeparator":4,"standardDecimalPatternInfo":{"primaryGroupSize":3,"secondaryGroupSize":3},"numberingSystemData":null},54],["UserAgentData",[],{"browserArchitecture":"32","browserFullVersion":null,"browserMinorVersion":null,"browserName":"Unknown","browserVersion":null,"deviceName":"Unknown","engineName":"Unknown","engineVersion":null,"platformArchitecture":"32","platformName":"Unknown","platformVersion":null,"platformFullVersion":null},527],["CookieCoreLoggingConfig",[],{"maximumIgnorableStallMs":16.67,"sampleRate":9.7e-5,"sampleRateClassic":1.0e-10,"sampleRateFastStale":1.0e-8},3401],["CLDRDateFormatConfig",[],{"supportedPHPFormatsKeys":{"D":"E","D g:ia":"Ejm","D M d":"MMMEd","D M d, Y":"yMMMEd","D M j":"MMMEd","D M j, y":"yMMMEd","D, M j":"MMMEd","D, M j, Y":"yMMMEd","F d":"MMMMd","F d, Y":"date_long","F j":"MMMMd","F j, Y":"date_long","F j, Y \u0040 g:i A":"dateTime_long_short","F j, Y g:i a":"dateTime_long_short","F j, Y \u0040 g:i:s A":"dateTime_long_medium","F jS":"MMMMd","F jS, g:ia":"dateTime_long_short","F jS, Y":"date_long","F Y":"yMMMM","g A":"j","G:i":"time_short","g:i":"time_short","g:i a":"time_short","g:i A":"time_short","g:i:s A":"time_medium","g:ia":"time_short","g:iA":"time_short","g:ia F jS, Y":"dateTime_long_short","g:iA l, F jS":"dateTime_full_short","g:ia M jS":"dateTime_medium_short","g:ia, F jS":"dateTime_long_short","g:iA, l M jS":"dateTime_full_short","h:i a":"time_short","h:m:s m\/d\/Y":"dateTime_short_short","j":"d","j F Y":"date_long","l F d, Y":"date_full","l, F d, Y":"date_full","l, F j":"date_full","l, F j, Y":"date_full","l, F jS":"date_full","l, F jS, g:ia":"dateTime_full_short","l, M j":"date_full","l, M j, Y":"date_full","l, M j, Y g:ia":"dateTime_full_short","M d":"MMMd","M d, Y":"date_medium","M d, Y g:ia":"dateTime_medium_short","M d, Y ga":"dateTime_medium_short","M j":"MMMd","M j, Y":"date_medium","M j, Y g:i A":"dateTime_medium_short","M j, Y g:ia":"dateTime_medium_short","M jS, g:ia":"dateTime_medium_short","M y":"yMMM","M Y":"yMMM","M. d":"MMMd","M. d, Y":"date_medium","m\/d":"Md","m\/d\/Y":"yMd","m\/d\/Y g:ia":"dateTime_short_short","m\/d\/y H:i:s":"dateTime_short_short","n":"M","n\/j":"Md","n\/j, g:ia":"dateTime_short_short","n\/j\/y":"date_short","Y":"y"},"isLocaleInConfigerator":true,"CLDRConfigeratorFormats":{"dateFormats":{"full":"EEEE, MMMM d, y","long":"MMMM d, y","medium":"MMM d, y","short":"M\/d\/yy"},"timeFormats":{"full":"h:mm:ss\u202fa zzzz","long":"h:mm:ss\u202fa z","medium":"h:mm:ss\u202fa","short":"h:mm\u202fa"},"dateTimeFormats":{"full":"{1}, {0}","long":"{1}, {0}","medium":"{1}, {0}","short":"{1}, {0}"},"availableFormats":{"Bh":"h B","Bhm":"h:mm B","Bhms":"h:mm:ss B","E":"ccc","EBhm":"E h:mm B","EBhms":"E h:mm:ss B","EHm":"E HH:mm","EHms":"E HH:mm:ss","Ed":"d E","Ehm":"E h:mm\u202fa","Ehm-alt-ascii":"E h:mm a","Ehms":"E h:mm:ss\u202fa","Ehms-alt-ascii":"E h:mm:ss a","Gy":"y G","GyMMM":"MMM y G","GyMMMEd":"E, MMM d, y G","GyMMMd":"MMM d, y G","GyMd":"M\/d\/y G","H":"HH","Hm":"HH:mm","Hms":"HH:mm:ss","Hmsv":"HH:mm:ss v","Hmv":"HH:mm v","M":"L","MEd":"E, M\/d","MMM":"LLL","MMMEd":"E, MMM d","MMMMW-count-one":"'week' W 'of' MMMM","MMMMW-count-other":"'week' W 'of' MMMM","MMMMd":"MMMM d","MMMd":"MMM d","Md":"M\/d","d":"d","h":"h\u202fa","h-alt-ascii":"h a","hm":"h:mm\u202fa","hm-alt-ascii":"h:mm a","hms":"h:mm:ss\u202fa","hms-alt-ascii":"h:mm:ss a","hmsv":"h:mm:ss\u202fa v","hmsv-alt-ascii":"h:mm:ss a v","hmv":"h:mm\u202fa v","hmv-alt-ascii":"h:mm a v","ms":"mm:ss","y":"y","yM":"M\/y","yMEd":"E, M\/d\/y","yMMM":"MMM y","yMMMEd":"E, MMM d, y","yMMMM":"MMMM y","yMMMd":"MMM d, y","yMd":"M\/d\/y","yQQQ":"QQQ y","yQQQQ":"QQQQ y","yw-count-one":"'week' w 'of' Y","yw-count-other":"'week' w 'of' Y"}},"CLDRRegionalConfigeratorFormats":{"dateFormats":{"full":"EEEE, MMMM d, y","long":"MMMM d, y","medium":"MMM d, y","short":"M\/d\/yy"},"timeFormats":{"full":"h:mm:ss\u202fa zzzz","long":"h:mm:ss\u202fa z","medium":"h:mm:ss\u202fa","short":"h:mm\u202fa"},"dateTimeFormats":{"full":"{1}, {0}","long":"{1}, {0}","medium":"{1}, {0}","short":"{1}, {0}"},"availableFormats":{"Bh":"h B","Bhm":"h:mm B","Bhms":"h:mm:ss B","E":"ccc","EBhm":"E h:mm B","EBhms":"E h:mm:ss B","EHm":"E HH:mm","EHms":"E HH:mm:ss","Ed":"d E","Ehm":"E h:mm\u202fa","Ehm-alt-ascii":"E h:mm a","Ehms":"E h:mm:ss\u202fa","Ehms-alt-ascii":"E h:mm:ss a","Gy":"y G","GyMMM":"MMM y G","GyMMMEd":"E, MMM d, y G","GyMMMd":"MMM d, y G","GyMd":"M\/d\/y G","H":"HH","Hm":"HH:mm","Hms":"HH:mm:ss","Hmsv":"HH:mm:ss v","Hmv":"HH:mm v","M":"L","MEd":"E, M\/d","MMM":"LLL","MMMEd":"E, MMM d","MMMMW-count-one":"'week' W 'of' MMMM","MMMMW-count-other":"'week' W 'of' MMMM","MMMMd":"MMMM d","MMMd":"MMM d","Md":"M\/d","d":"d","h":"h\u202fa","h-alt-ascii":"h a","hm":"h:mm\u202fa","hm-alt-ascii":"h:mm a","hms":"h:mm:ss\u202fa","hms-alt-ascii":"h:mm:ss a","hmsv":"h:mm:ss\u202fa v","hmsv-alt-ascii":"h:mm:ss a v","hmv":"h:mm\u202fa v","hmv-alt-ascii":"h:mm a v","ms":"mm:ss","y":"y","yM":"M\/y","yMEd":"E, M\/d\/y","yMMM":"MMM y","yMMMEd":"E, MMM d, y","yMMMM":"MMMM y","yMMMd":"MMM d, y","yMd":"M\/d\/y","yQQQ":"QQQ y","yQQQQ":"QQQQ y","yw-count-one":"'week' w 'of' Y","yw-count-other":"'week' w 'of' Y"}},"CLDRToPHPSymbolConversion":{"G":"","yyyy":"Y","yy":"y","y":"Y","LLLLL":"M","LLLL":"f","LLL":"M","LL":"m","L":"n","MMMMM":"M","MMMM":"F","MMM":"M","MM":"m","M":"n","dd":"d","d":"j","ccccc":"D","cccc":"l","ccc":"D","cc":"D","c":"D","EEEEE":"D","EEEE":"l","EEE":"D","EE":"D","E":"D","aaaaa":"A","aaaa":"A","aaa":"A","aa":"A","a":"A","bbbbb":"A","bbbb":"A","bbb":"A","bb":"A","b":"A","BBBBB":"A","BBBB":"A","BBB":"A","BB":"A","B":"A","HH":"H","H":"G","hh":"h","h":"g","K":"g","mm":"i","m":"i","ss":"s","s":"s","z":"","zz":"","zzz":""},"intlDateSpecialChars":{"cldrDelimiter":"'","singleQuote":"'","singleQuoteHolder":"*"}},3019],["UriNeedRawQuerySVConfig",[],{"uris":["dms.netmng.com","doubleclick.net","r.msn.com","watchit.sky.com","graphite.instagram.com","www.kfc.co.th","learn.pantheon.io","www.landmarkshops.in","www.ncl.com","s0.wp.com","www.tatacliq.com","bs.serving-sys.com","kohls.com","lazada.co.th","xg4ken.com","technopark.ru","officedepot.com.mx","bestbuy.com.mx","booking.com","nibio.no","myworkdayjobs.com","united-united.com","gcc.gnu.org"]},3871],["IsInternSite",[],{"is_intern_site":false},4517],["MqttWebDeviceID",[],{"clientID":"c8b6f454-eb48-44af-bfba-828934a28f24"},5003],["WebDriverConfig",[],{"isTestRunning":false,"isJestE2ETestRun":false,"isXRequestConfigEnabled":false,"auxiliaryServiceInfo":{},"testPath":null,"originHost":null,"experiments":null},5332],["DGWWebConfig",[],{"appId":"936619743392459","appVersion":"0","dgwVersion":"2","endpoint":"","fbId":"0","authType":""},5508],["CometPersistQueryParams",[],{"relative":{},"domain":{"instagram.com":{}}},6231],["GetAsyncParamsExtraData",[],{"extra_data":{}},7511],["AdsManagerReadRegions",[],{"excluded_endpoints":["\/am_tabular","\/ad_limits_insights","\/ads_reporting","\/column_suggestions","\/customaudiences","\/insights","\/reporting","\/edit","\/adspixels"],"excluded_preloaders":["AdsPEInsightsEdgeDataLoaderPreloader","AdsPEInsightsEdgeSummaryDataLoaderPreloader","AdsPEInsightsColumnPresetDataLoaderPreloader","AdsReportBuilderBusinessViewReportPreloader","AdsReportBuilderAdAccountViewReportPreloader","AdsReportBuilderManageUnifiedReportsPreloader"]},7950],["BootloaderConfig",[],{"deferBootloads":false,"enableLoadingUnavailableResources":true,"enableRetryOnStuckResource":false,"immediatesBugFixKillswitch":true,"jsRetries":[200,500],"jsRetryAbortNum":2,"jsRetryAbortTime":5,"silentDups":true,"timeout":60000,"tieredLoadingFromTier":100,"hypStep4":true,"btCutoffIndex":1756,"fastPathForAlreadyRequired":true,"csrOn":true,"nonce":"RV2EvKom","shouldEnableProxyArgs":false,"translationRetries":[200,500],"translationRetryAbortNum":3,"translationRetryAbortTime":50},329],["CSSLoaderConfig",[],{"timeout":5000},619],["SprinkleConfig",[],{"param_name":"jazoest","version":2,"should_randomize":false},2111],["PromiseUsePolyfillSetImmediateGK",[],{"www_always_use_polyfill_setimmediate":false},2190],["JSErrorLoggingConfig",[],{"appId":936619743392459,"extra":[],"reportInterval":50,"sampleWeight":null,"sampleWeightKey":"__jssesw","projectBlocklist":[]},2776],["ImmediateImplementationExperiments",[],{"prefer_message_channel":true},3419],["WebConnectionClassServerGuess",[],{"connectionClass":"GOOD"},4705],["BootloaderEndpointConfig",[],{"retryEnabled":false,"debugNoBatching":false,"maxBatchSize":-1,"endpointURI":"https:\/\/www.instagram.com\/ajax\/bootloader-endpoint\/","adsManagerReadRegions":false},5094],["cr:8828",[],{"__rc":[null,null]},-1],["cr:1094907",[],{"__rc":[null,null]},-1],["cr:925100",["RunComet"],{"__rc":["RunComet",null]},-1],["cr:7386",["clearTimeoutWWW"],{"__rc":["clearTimeoutWWW",null]},-1],["cr:7390",["setTimeoutWWW"],{"__rc":["setTimeoutWWW",null]},-1],["cr:6895",["cometAsyncRequestHeaders"],{"__rc":["cometAsyncRequestHeaders",null]},-1],["cr:1183579",["InlineFbtResultImplComet"],{"__rc":["InlineFbtResultImplComet",null]},-1],["cr:1003267",["clearIntervalComet"],{"__rc":["clearIntervalComet",null]},-1],["cr:896462",["setIntervalComet"],{"__rc":["setIntervalComet",null]},-1],["cr:986633",["setTimeoutComet"],{"__rc":["setTimeoutComet",null]},-1],["FbtResultGK",[],{"shouldReturnFbtResult":true,"inlineMode":"NO_INLINE"},876],["RpWebStateMachineLoggingBlocklist",[],{"EVENT_TYPES":["xstate.init","receiveStateSyncNotifyRequest","receiveGenericDataMessageRequest","sendIceCandidateRequest","dataChannelMessageReceived","dataMessageReceived","receivePingResponse","receiveOverlayConfigServerUpdateRequest","receiveClientInfoRequest","sendClientEventRequest","receiveRoomContextUpdateRequest","sendGenericDataMessageRequest","capabilitiesReceived","receiveCapabilitiesRequest","createDataMessage | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#where-should-i-store-my-tokens-in-the-frontend | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://github.com/enterprise?locale=ja | GitHub Enterprise · エージェント対応エンタープライズのためのAI駆動の開発者プラットフォーム · GitHub Skip to content Navigation Menu Toggle navigation サインイン Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search サインイン サインアップ Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} Enterprise Navigation menu GitHub Advanced Security プレミアム サポート エージェント対応エンタープライズのためのAI駆動の開発者プラットフォーム ソフトウェアのスピード、スケール、そしてエージェント ドリブンな未来のために構築されたセキュアなプラットフォームで DevOps を 1 つにまとめましょう。 30日間の無料トライアルを開始する 営業へ問合せ /enterprise Section - logo Ford 3M Procter and Gamble American Airlines KPMG Stripe Spotify Ford 3M Procter and Gamble <path fill-rule="evenodd" clip-rule="evenodd" d="M76.0342 0.431968C76.0302 0.435738 75.8448 0.449711 75.6219 0.463019C74.4813 0.530665 74.1155 0.56593 74.1155 0.607848C74.1155 0.628474 74.0293 0.638899 73.9223 0.631579C73.8161 0.62426 73.7292 0.633132 73.7292 0.651319C73.7292 0.669284 73.6598 0.677712 73.5746 0.669506C73.4896 0.661299 73.42 0.669506 73.42 0.687692C73.42 0.705879 73.3632 0.71586 73.294 0.709872C73.2246 0.703883 73.1496 0.710315 73.1272 0.724066C73.105 0.737817 72.9749 0.760218 72.838 0.773525C72.3725 0.819436 72.3195 0.828973 72.3062 0.868452C72.2873 0.925008 72.1451 0.917468 72.1438 0.85958C72.1432 0.831191 72.1274 0.837623 72.1052 0.875327C72.0824 0.914584 71.9894 0.950293 71.865 0.968036C71.5499 1.01239 71.5288 1.01616 71.1684 1.09224C70.9821 1.1315 70.8377 1.17208 70.8479 1.18229C70.8798 1.21422 69.9448 1.41627 69.898 1.38722C69.8702 1.37014 69.8638 1.37657 69.8809 1.4043C69.8991 1.43357 69.8744 1.44888 69.8095 1.44888C69.7551 1.44888 69.7108 1.46817 69.7108 1.49168C69.7108 1.51874 69.6713 1.5254 69.6045 1.50987C69.5336 1.49346 69.516 1.49701 69.5515 1.52074C69.6183 1.56532 69.3896 1.62454 69.3193 1.58106C69.2914 1.56377 69.284 1.56953 69.3 1.59548C69.3231 1.63274 69.1745 1.68375 69.0345 1.68664C69.0132 1.68708 68.9749 1.70482 68.9491 1.72612C68.9236 1.74719 68.8855 1.75406 68.8646 1.7412C68.8438 1.72833 68.8125 1.74186 68.7954 1.77158C68.7781 1.80108 68.7227 1.83812 68.6723 1.85365C68.6009 1.87582 68.5874 1.8705 68.6114 1.82969C68.6282 1.80086 68.6054 1.80951 68.5606 1.84877C68.5158 1.88802 68.4605 1.90865 68.4379 1.89468C68.4155 1.88093 68.3969 1.88758 68.3969 1.90976C68.3969 1.93194 68.3188 1.96986 68.223 1.99382C68.1274 2.01799 68.0491 2.05148 68.0491 2.06812C68.0491 2.08497 67.9404 2.13377 67.8076 2.17679C67.4401 2.29567 67.3006 2.35223 67.2447 2.40524C67.2165 2.43185 67.173 2.45625 67.148 2.45936L67.0639 2.47111C67.0426 2.47422 66.971 2.50571 66.9047 2.54097C66.8381 2.57624 66.7765 2.59775 66.7676 2.58888C66.7587 2.57979 66.7004 2.61638 66.6383 2.66983C66.5747 2.7244 66.4948 2.75922 66.4564 2.74924C66.4185 2.73925 66.3877 2.74813 66.3877 2.76853C66.3877 2.78916 66.3704 2.79515 66.3491 2.78206C66.3278 2.76875 66.3105 2.77474 66.3105 2.79492C66.3105 2.81511 66.2366 2.86102 66.1464 2.89717C66.0561 2.93332 65.9734 2.97524 65.9627 2.99032C65.9292 3.03779 65.542 3.22631 65.4781 3.22631C65.4446 3.22631 65.426 3.24072 65.4369 3.25824C65.4477 3.27599 65.3271 3.34984 65.1689 3.42259C65.0106 3.49534 64.8808 3.56742 64.8808 3.58317C64.8806 3.62176 64.5089 3.80762 64.4832 3.78189C64.4721 3.7708 64.4508 3.79919 64.4361 3.8451C64.4177 3.90366 64.3874 3.92317 64.3361 3.90964C64.2955 3.899 64.2625 3.9072 64.2625 3.92783C64.2625 3.94824 64.2425 3.95267 64.2179 3.93759C64.1911 3.92096 64.1837 3.92694 64.1997 3.95267C64.2223 3.98927 64.0981 4.0904 64.0254 4.0944C64.0119 4.09506 63.9542 4.14252 63.897 4.19952C63.84 4.25652 63.743 4.31441 63.6818 4.32772C63.6204 4.34125 63.5598 4.38561 63.5468 4.42686C63.5259 4.49295 63.4576 4.52179 63.3613 4.50515C63.3438 4.50205 63.3394 4.5158 63.3518 4.53554C63.364 4.5555 63.2879 4.61472 63.1826 4.66706C63.0772 4.71962 63.0007 4.77219 63.0125 4.78416C63.038 4.80945 62.6796 5.04055 62.613 5.04166C62.5992 5.04257 62.5858 5.04655 62.5738 5.0533C62.5617 5.06005 62.5514 5.06941 62.5434 5.0807C62.5294 5.10332 62.5467 5.10842 62.586 5.09334C62.631 5.07604 62.6434 5.08247 62.6243 5.11308C62.609 5.13792 62.5771 5.15832 62.5536 5.15832C62.5299 5.15832 62.4757 5.18871 62.4332 5.22597C62.3755 5.27654 62.3628 5.27898 62.3837 5.23551C62.399 5.20379 62.3824 5.21666 62.3469 5.26456C62.3114 5.31247 62.2557 5.3515 62.2229 5.3515C62.1901 5.3515 62.1741 5.36259 62.1876 5.3759C62.2109 5.39919 62.0295 5.56398 61.9807 5.56398C61.9676 5.56398 61.8891 5.62963 61.8057 5.7097C61.4247 6.07654 61.4389 6.06611 61.4012 6.00645C61.3737 5.96276 61.3657 5.96964 61.3652 6.03728C61.3648 6.08851 61.3408 6.12422 61.3067 6.12422C61.2747 6.12422 61.2483 6.13731 61.2477 6.15328C61.245 6.24332 61.0933 6.37352 61.0563 6.3174C61.0226 6.26661 61.0179 6.26706 61.0175 6.32051C61.0166 6.39791 60.8469 6.5596 60.8074 6.52078C60.791 6.50459 60.7837 6.52056 60.791 6.55649C60.7983 6.5922 60.7921 6.62347 60.7773 6.62613C60.7624 6.62857 60.6034 6.77318 60.4242 6.94729C60.2448 7.12161 60.0309 7.32611 59.9489 7.40196C59.7575 7.57872 59.5166 7.84243 59.3762 8.0294C59.2953 8.13697 59.2573 8.1627 59.2338 8.12588C59.2099 8.08818 59.2019 8.09261 59.2014 8.14296C59.201 8.18 59.166 8.2319 59.1234 8.25851C59.081 8.28491 59.0462 8.32971 59.0462 8.35765C59.0462 8.3856 59.0291 8.39802 59.008 8.38493C58.987 8.37207 58.9792 8.38582 58.9905 8.41554C59.0025 8.44681 58.9706 8.49672 58.9156 8.53265C58.863 8.56724 58.7885 8.64842 58.7503 8.71296C58.7106 8.78016 58.6589 8.82208 58.6297 8.81099C58.6015 8.80013 58.5884 8.80722 58.6004 8.82696C58.6126 8.84648 58.5897 8.88529 58.5498 8.91346C58.5097 8.94141 58.4702 8.98177 58.4622 9.00284C58.454 9.02413 58.4349 9.03744 58.4196 9.03234C58.4046 9.02724 58.4019 9.04897 58.4141 9.08025C58.4261 9.11174 58.4103 9.14745 58.379 9.15943C58.3478 9.1714 58.2653 9.26899 58.1959 9.37634C58.1262 9.48368 58.012 9.62874 57.9421 9.69882C57.872 9.76869 57.8259 9.837 57.8394 9.85052C57.8532 9.86405 57.7926 9.94279 57.705 10.0251C57.6174 10.1076 57.5542 10.1837 57.5646 10.1939C57.595 10.2245 57.4861 10.3746 57.4333 10.3746C57.4065 10.3746 57.3848 10.4086 57.3848 10.45C57.3848 10.4915 57.3544 10.5423 57.3171 10.5631C57.2799 10.584 57.255 10.6066 57.2617 10.6135C57.2841 10.6363 57.2184 10.7798 57.1563 10.8433C57.0228 10.9799 56.9744 11.0568 56.9911 11.1063C57.0015 11.1374 56.9909 11.1473 56.9647 11.1311C56.9378 11.1145 56.921 11.134 56.921 11.1819C56.921 11.2245 56.8988 11.2733 56.8715 11.2904C56.8443 11.3075 56.7649 11.4388 56.6952 11.582C56.6253 11.7255 56.5535 11.8429 56.5353 11.8429C56.5169 11.8429 56.4814 11.905 56.4566 11.9808C56.4315 12.0567 56.3902 12.1268 56.365 12.1365C56.3397 12.1461 56.3164 12.1886 56.3133 12.2308C56.3102 12.2729 56.2818 12.3332 56.2503 12.3645C56.2188 12.396 56.1729 12.483 56.1483 12.5577C56.1219 12.6375 56.0862 12.6832 56.0618 12.6682C56.0385 12.6535 56.0314 12.6604 56.046 12.6839C56.0793 12.7378 56.0088 12.921 55.9245 12.9988C55.8881 13.0326 55.8535 13.0862 55.8473 13.1179C55.8271 13.2248 55.6772 13.556 55.626 13.6072C55.598 13.6349 55.5375 13.7713 55.4913 13.9102C55.4452 14.049 55.3787 14.1912 55.3438 14.2262C55.3088 14.2611 55.2797 14.3087 55.2795 14.3318C55.2782 14.4174 55.0894 14.8954 55.0568 14.8954C55.0384 14.8954 55.034 14.9129 55.0471 14.9344C55.0604 14.9557 55.044 15.0005 55.0109 15.0338C54.9777 15.067 54.9504 15.1256 54.9504 15.164C54.9504 15.2023 54.9269 15.2924 54.8983 15.364L54.8146 15.5716C54.7976 15.6142 54.7863 15.6619 54.7898 15.6779C54.7931 15.6938 54.7803 15.7069 54.761 15.7069C54.7419 15.7069 54.7053 15.7938 54.6798 15.9003C54.6543 16.0065 54.6177 16.1035 54.5982 16.1154C54.5787 16.1274 54.5736 16.1547 54.5866 16.1758C54.5997 16.1971 54.5782 16.2405 54.539 16.2727C54.4995 16.3046 54.4911 16.3186 54.5199 16.3037C54.5578 16.2842 54.5662 16.2969 54.5507 16.3492C54.5387 16.3891 54.5177 16.4696 54.5037 16.528C54.4897 16.5865 54.4629 16.6342 54.4438 16.6342C54.425 16.6342 54.4094 16.669 54.4094 16.7116C54.4094 16.754 54.3939 16.7888 54.3751 16.7888C54.3562 16.7888 54.3431 16.8105 54.3462 16.8372C54.3535 16.9035 54.167 17.6536 54.1371 17.6775C54.1082 17.7008 53.99 18.1451 53.9625 18.3329C53.9519 18.4065 53.9306 18.4762 53.9155 18.4875C53.9002 18.499 53.8822 18.5951 53.8754 18.7009C53.8683 18.8069 53.8483 18.9027 53.8306 18.9136C53.8128 18.9244 53.7866 19.0029 53.7725 19.0879C53.7583 19.1728 53.7363 19.2684 53.7237 19.3004C53.711 19.3323 53.6962 19.3931 53.6908 19.4356C53.6855 19.478 53.6731 19.5563 53.6636 19.6095C53.654 19.6625 53.6329 19.8147 53.617 19.9475C53.601 20.0804 53.5728 20.1891 53.5544 20.1891C53.5358 20.1891 53.5207 20.2419 53.5207 20.3062C53.5207 20.3707 53.4952 20.4843 53.4642 20.5588C53.4289 20.6435 53.424 20.6841 53.4513 20.6673C53.4786 20.6504 53.4875 20.6606 53.4744 20.6948C53.4628 20.7247 53.4307 20.9622 53.4027 21.2226C53.3748 21.483 53.342 21.6961 53.33 21.6961C53.318 21.6964 53.3031 21.8913 53.2969 22.1295C53.2907 22.3679 53.271 22.5722 53.253 22.5835C53.1404 22.6545 53.1326 26.1825 53.245 26.2524C53.265 26.2646 53.2927 26.4487 53.3069 26.6611C53.3209 26.8736 53.3397 27.0998 53.3486 27.1635L53.3921 27.4727C53.4072 27.5789 53.4205 27.7379 53.4218 27.8264C53.4231 27.9147 53.4349 27.9801 53.4482 27.9719C53.4615 27.9637 53.4843 28.0478 53.499 28.1584C53.5138 28.2693 53.5422 28.37 53.5626 28.3827C53.5828 28.3951 53.6059 28.4823 53.6141 28.5765C53.6221 28.6706 53.6414 28.7786 53.6567 28.8165C53.672 28.8544 53.6862 28.9456 53.688 29.0194C53.6899 29.0931 53.7053 29.1534 53.7221 29.1534C53.739 29.1534 53.7492 29.1665 53.7452 29.1825C53.729 29.2466 53.8 29.4626 53.8374 29.4626C53.8594 29.4626 53.8685 29.4974 53.8574 29.5398C53.8463 29.5823 53.8543 29.6276 53.8756 29.6407C53.8967 29.6538 53.9053 29.6972 53.8949 29.7374C53.8829 29.7833 53.8913 29.8008 53.9173 29.7846C53.9437 29.7684 53.9499 29.7826 53.9341 29.8232C53.9206 29.8587 53.9282 29.8875 53.9512 29.8875C53.9741 29.8875 53.9829 29.913 53.971 29.9443C53.959 29.9756 53.9641 30.0102 53.9823 30.0215C54.0005 30.0328 54.0362 30.1288 54.0617 30.2353C54.0872 30.3415 54.1209 30.4285 54.1364 30.4285C54.1934 30.4285 54.2546 30.7106 54.2094 30.7652C54.1761 30.8053 54.1808 30.8113 54.23 30.7924C54.2832 30.772 54.3256 30.8574 54.2846 30.9018C54.2797 30.9071 54.3056 30.9546 54.3425 31.0071C54.3793 31.0597 54.4094 31.1344 54.4094 31.1735C54.4094 31.2125 54.4256 31.2345 54.4454 31.2223C54.4651 31.2101 54.4924 31.2396 54.5061 31.2877C54.5578 31.4678 54.737 31.8581 54.7681 31.8581C54.7858 31.8581 54.7896 31.8757 54.7765 31.8967C54.7634 31.918 54.7729 31.9355 54.7978 31.9355C54.8224 31.9355 54.8328 31.9615 54.8204 31.9934C54.8082 32.0254 54.8131 32.0513 54.8313 32.0513C54.8492 32.0513 54.8743 32.0817 54.8867 32.119C54.9131 32.1973 54.9865 32.3141 55.0588 32.3927C55.0863 32.4228 55.1456 32.5251 55.1901 32.62C55.2347 32.7149 55.2948 32.8014 55.3234 32.8125C55.352 32.8234 55.3758 32.8524 55.3762 32.8766C55.3771 32.9314 55.5745 33.2317 55.704 33.3754C55.757 33.4342 55.8005 33.4952 55.8007 33.5107C55.8007 33.5262 55.8619 33.6054 55.9365 33.6866C56.011 33.768 56.0622 33.8505 56.05 33.8702C56.0378 33.89 56.0549 33.9062 56.0879 33.9062C56.1212 33.9062 56.1483 33.9321 56.1483 33.964C56.1483 33.996 56.1656 34.0219 56.1869 34.0219C56.2082 34.0219 56.2268 34.0525 56.2286 34.0896C56.2306 34.1344 56.2385 34.1399 56.2521 34.1062C56.2743 34.0505 56.4078 34.2071 56.3885 34.2663C56.3827 34.2839 56.3945 34.2881 56.4144 34.2757C56.4501 34.2537 56.6892 34.4653 56.6892 34.519C56.6892 34.534 56.74 34.5762 56.8021 34.613C56.864 34.6496 56.937 34.7297 56.9642 34.7911C56.9913 34.8523 57.0348 34.8942 57.0609 34.8842C57.1204 34.8614 57.2688 35.0062 57.2688 35.087C57.2688 35.12 57.2847 35.1371 57.3045 35.1251C57.3641 35.0881 57.6234 35.2622 57.5999 35.3236C57.5884 35.3538 57.5917 35.3709 57.6072 35.3615C57.6618 35.3296 57.8153 35.4114 57.7869 35.4574C57.7698 35.4849 57.776 35.4917 57.8026 35.4753C57.8625 35.4383 58.1823 35.6459 58.1364 35.6918C58.1266 35.7013 58.1415 35.7093 58.1692 35.7093C58.2737 35.7093 58.5846 35.8901 58.5347 35.9218C58.4975 35.9455 58.4997 35.9539 58.5438 35.9579C58.5758 35.9606 58.6192 35.967 58.6405 35.9719C58.6618 35.9768 58.702 35.9834 58.7297 35.9868C58.7574 35.9899 58.7692 36.0105 58.7559 36.0322C58.7423 36.054 58.7457 36.0677 58.7632 36.0628C58.8177 36.0478 59.0848 36.1513 59.0848 36.1875C59.0848 36.2066 59.111 36.2121 59.1429 36.1997C59.1746 36.1875 59.2008 36.1948 59.2008 36.2161C59.2008 36.2374 59.2449 36.2658 59.299 36.2793C59.3583 36.2942 59.3864 36.3212 59.3702 36.3474C59.3549 36.3722 59.3607 36.3802 59.3835 36.366C59.4359 36.3339 59.6643 36.4135 59.6643 36.4643C59.6643 36.4856 59.6892 36.4938 59.7191 36.4822C59.7493 36.4707 59.7845 36.4887 59.7974 36.5222C59.8103 36.5559 59.8318 36.5723 59.8451 36.559C59.8584 36.5457 59.8941 36.565 59.9243 36.6018C59.9544 36.6386 59.9682 36.647 59.9549 36.6204C59.924 36.5599 59.9551 36.5592 60.0631 36.6186C60.1095 36.6442 60.1822 36.6708 60.2248 36.6776C60.2671 36.6847 60.3071 36.7054 60.3135 36.7238C60.3197 36.7422 60.3563 36.7491 60.3947 36.7391C60.4166 36.7349 60.4392 36.736 60.4607 36.742C60.4822 36.7481 60.5019 36.7591 60.5184 36.7741C60.5701 36.8251 60.9223 36.9467 61.2834 37.0376C61.377 37.0613 61.4781 37.1053 61.5083 37.1354C61.5387 37.1658 61.6048 37.1904 61.6553 37.1904C61.7059 37.1904 61.7873 37.2066 61.8361 37.2266C61.8849 37.2465 61.9905 37.2734 62.0707 37.2865C62.151 37.2995 62.2076 37.3251 62.1963 37.3432C62.1852 37.3614 62.2105 37.3674 62.2526 37.3563C62.2948 37.3452 62.3602 37.3497 62.3977 37.3659C62.4352 37.3823 62.4981 37.3914 62.5376 37.3865C62.5771 37.3814 62.5993 37.394 62.5866 37.4142C62.574 37.4348 62.6523 37.4628 62.7638 37.4776C62.8736 37.4923 62.9821 37.5156 63.0045 37.5298C63.0269 37.5437 63.0888 37.5582 63.142 37.5619C63.195 37.5657 63.2819 37.5794 63.3352 37.5928C63.3884 37.6058 63.5445 37.6262 63.6821 37.6378C63.8198 37.6495 63.9416 37.6733 63.9526 37.6908C63.9719 37.7216 64.2128 37.7655 64.4943 37.7895C64.5688 37.7957 64.734 37.811 64.8615 37.8232C65.3107 37.8662 65.7134 37.8944 65.8951 37.8953C65.996 37.8957 66.0785 37.907 66.0785 37.9201C66.0785 37.9332 66.5177 37.9365 67.0542 37.9274C67.5909 37.9186 68.1906 37.9097 68.3873 37.9081C68.5838 37.9066 68.7446 37.8948 68.7446 37.8822C68.7446 37.8695 68.8099 37.858 68.8897 37.8567C69.2716 37.85 70.344 37.7274 70.3699 37.6875C70.3819 37.669 70.5234 37.6495 70.6847 37.6442C70.8459 37.6391 70.9685 37.6196 70.9572 37.601C70.9459 37.5823 70.9987 37.5743 71.0743 37.5832C71.1502 37.5921 71.205 37.5877 71.1961 37.5732C71.1872 37.5588 71.2797 37.5351 71.4017 37.5204C71.7845 37.4745 71.8932 37.4541 71.9131 37.4244C71.9513 37.3674 72.1449 37.341 72.1456 37.3925C72.146 37.4297 72.1542 37.4288 72.1793 37.3891C72.1977 37.3603 72.2625 37.3319 72.3237 37.3262C72.3847 37.3204 72.4608 37.3058 72.4927 37.2938C72.6224 37.2452 73.1902 37.1485 73.2239 37.1694C73.2439 37.1816 73.2727 37.1714 73.288 37.1465C73.3055 37.1181 73.2993 37.1115 73.2714 37.1288C73.247 37.1438 73.2268 37.1359 73.2268 37.111C73.2268 37.0829 73.2698 37.072 73.3408 37.0824C73.4034 37.0917 73.4471 37.0868 73.4377 37.072C73.4284 37.0569 73.4599 37.0343 73.5074 37.0214C73.6356 36.9873 73.6595 36.9919 73.6283 37.0456C73.6127 37.072 73.6334 37.0651 73.6742 37.0303C73.7152 36.9953 73.8833 36.9371 74.0479 36.9008C74.2127 36.8646 74.3475 36.8214 74.3475 36.805C74.3475 36.7664 74.843 36.6408 74.8871 36.6681C74.9055 36.6794 74.9264 36.6703 74.9339 36.6481C74.9413 36.6257 74.9907 36.6011 75.0435 36.5931C75.1948 36.5705 75.3134 36.5273 75.3134 36.4949C75.3134 36.4652 75.4858 36.4197 75.6514 36.4057C75.6993 36.4017 75.7384 36.3869 75.7384 36.3731C75.7384 36.3372 75.9728 36.2602 76.011 36.2837C76.0285 36.2944 76.0591 36.2742 76.079 36.2385C76.1014 36.1984 76.1398 36.1833 76.18 36.1988C76.2186 36.2134 76.2352 36.2079 76.221 36.1848C76.1992 36.1498 76.4128 36.0808 76.4823 36.1003C76.4982 36.1048 76.5113 36.089 76.5113 36.0653C76.5113 36.0413 76.5452 36.0311 76.5885 36.0424C76.6311 36.0535 76.6659 36.048 76.6659 36.0302C76.6659 36.0125 76.7049 35.9857 76.7528 35.9706C76.8005 35.9557 76.8509 35.926 76.8646 35.9047C76.8784 35.8834 76.9418 35.8641 77.0057 35.8617C77.0696 35.8592 77.1139 35.8444 77.1042 35.8284C77.0942 35.8124 77.109 35.7967 77.1368 35.7936C77.2481 35.7805 77.2692 35.7736 77.3854 35.712C77.4517 35.6767 77.5171 35.659 77.5307 35.6725C77.5442 35.686 77.5905 35.6594 77.6338 35.6131C77.7101 35.531 77.7551 35.5132 77.854 35.5261C77.8804 35.5294 77.9022 35.5124 77.9022 35.488C77.9022 35.4633 77.9283 35.4534 77.9603 35.4656C77.992 35.4778 78.0182 35.4711 78.0182 35.4505C78.0182 35.4299 78.0497 35.413 78.0882 35.413C78.1266 35.413 78.1951 35.3786 78.2404 35.3363C78.2856 35.2941 78.4356 35.2134 78.5733 35.1568C78.7403 35.0883 78.8226 35.0333 78.8202 34.992C78.8142 34.8929 78.9444 34.4857 78.9818 34.4857C79.0007 34.4857 79.0078 34.4336 78.9978 34.3697C78.9878 34.306 78.9956 34.2539 79.0155 34.2539C79.0353 34.2539 79.1005 34.0669 79.1604 33.8385C79.2203 33.6101 79.2815 33.4144 79.2961 33.4038C79.311 33.3932 79.3542 33.2714 79.3922 33.1332C79.4303 32.9953 79.478 32.8711 79.4984 32.8575C79.508 32.8512 79.5149 32.8414 79.5176 32.8302C79.5203 32.819 79.5187 32.8072 79.513 32.7972C79.4831 32.7488 79.5645 32.4377 79.6071 32.4377C79.6257 32.4377 79.641 32.406 79.641 32.3669C79.641 32.3279 79.6532 32.2838 79.6683 32.2689C79.6831 32.2538 79.7013 32.1946 79.7082 32.1369C79.7308 31.9528 79.8388 31.665 79.8856 31.6643C79.9116 31.6641 79.9063 31.6479 79.8728 31.6264C79.8362 31.6026 79.8322 31.5887 79.8619 31.5882C79.8878 31.588 79.8992 31.5616 79.8867 31.5297C79.8745 31.4979 79.8808 31.4718 79.9003 31.4718C79.92 31.4718 79.9668 31.3414 80.0043 31.1817C80.0475 30.9989 80.0879 30.9011 80.1141 30.9173C80.1389 30.9326 80.144 30.9244 80.1267 30.8967C80.0932 30.8426 80.1828 30.4631 80.2232 30.4879C80.2383 30.4975 80.2625 30.4267 80.2766 30.3309C80.2911 30.2348 80.319 30.1665 80.3385 30.1787C80.3583 30.1907 80.3643 30.1745 80.3521 30.1426C80.3461 30.1249 80.3438 30.1061 80.3454 30.0875C80.347 30.0689 80.3523 30.0508 80.3612 30.0344C80.3782 30.0072 80.39 29.9771 80.3962 29.9456C80.4108 29.795 80.4676 29.5784 80.4925 29.5784C80.5091 29.5784 80.5448 29.4914 80.5721 29.3852C80.5993 29.2789 80.6337 29.192 80.6486 29.192C80.6634 29.192 80.675 29.1703 80.6739 29.1439C80.6692 29.0148 80.6872 28.9187 80.7134 28.9347C80.7293 28.9443 80.7451 28.8821 80.7484 28.7965C80.7517 28.7109 80.7704 28.63 80.7899 28.6169C80.8296 28.5903 80.8841 28.4685 80.8961 28.3807C80.9152 28.2374 81.0789 27.6652 81.1057 27.6472C81.1314 27.6299 81.272 27.1535 81.331 26.8834C81.3417 26.8355 81.365 26.7964 81.3832 26.7964C81.4011 26.7964 81.406 26.7703 81.3938 26.7385C81.3816 26.7066 81.3887 26.6804 81.4096 26.6804C81.4442 26.6804 81.5131 26.4691 81.5009 26.4003C81.498 26.3843 81.5116 26.3715 81.5307 26.3715C81.5499 26.3715 81.5566 26.3367 81.5455 26.2941C81.5338 26.2493 81.5444 26.2169 81.5708 26.2169C81.5959 26.2169 81.6074 26.2027 81.5967 26.1856C81.5688 26.1404 81.6533 25.8305 81.6937 25.8305C81.7123 25.8305 81.7276 25.7871 81.7276 25.7338C81.7276 25.6806 81.746 25.6371 81.7684 25.6371C81.791 25.6371 81.7995 25.6209 81.787 25.6012C81.7748 25.5812 81.791 25.4901 81.823 25.3983C81.8549 25.3067 81.8813 25.2011 81.8815 25.1638C81.882 25.1268 81.8951 25.0962 81.911 25.0962C81.927 25.0962 81.9447 25.0319 81.9503 24.9531C81.956 24.8746 81.9742 24.8008 81.9909 24.789C82.0372 24.7566 82.1468 24.4404 82.1754 24.2565C82.1894 24.1667 82.2144 24.1015 82.2311 24.1117C82.2477 24.1221 82.2521 24.0957 82.2411 24.0531C82.2264 23.9968 82.2404 23.9748 82.2929 23.9726C82.3338 23.971 82.344 23.9611 82.3169 23.9502C82.2621 23.928 82.2504 23.8211 82.3027 23.8211C82.3351 23.8211 82.3803 23.7149 82.4012 23.5893C82.4333 23.3948 82.589 22.8721 82.6203 22.8528C82.6407 22.8399 82.6667 22.7805 82.6775 22.7206C82.6884 22.6605 82.7115 22.5837 82.7288 22.5498C82.7461 22.5159 82.7525 22.4664 82.743 22.4398C82.7336 22.4132 82.7441 22.3915 82.7665 22.3915C82.7887 22.3915 82.7971 22.3655 82.7849 22.3336C82.7725 22.3016 82.7776 22.2755 82.7957 22.2755C82.8139 22.2755 82.8326 22.2202 82.8374 22.1528C82.8421 22.0854 82.8609 22.0202 82.8791 22.008C82.9295 21.974 83.0422 21.7296 82.9934 21.7596C82.965 21.7773 82.9603 21.7616 82.9794 21.7121C82.9951 21.6713 83.0175 21.5915 83.0291 21.5342C83.0406 21.4772 83.0719 21.422 83.0989 21.4118C83.1267 21.4012 83.1402 21.3539 83.1304 21.3025C83.1198 21.2472 83.144 21.1743 83.1923 21.1159L83.3043 20.9804C83.3133 20.9689 83.3197 20.9555 83.3229 20.9413C83.326 20.927 83.326 20.9122 83.3227 20.8979C83.3147 20.8742 83.3351 20.828 83.368 20.7952C83.4008 20.7624 83.4276 20.6979 83.4276 20.6519C83.4276 20.6009 83.4578 20.5603 83.5046 20.5482C83.5467 20.5371 83.5718 20.5124 83.56 20.4936C83.5483 20.4745 83.5658 20.4486 83.5988 20.4359C83.6321 20.4233 83.6494 20.3971 83.6374 20.378C83.6068 20.3281 83.7632 20.121 83.853 20.0924C83.8945 20.0793 83.9244 20.0478 83.9196 20.0225C83.9147 19.9972 83.9338 19.9813 83.9619 19.9872C83.9901 19.993 84.0016 19.9793 83.9874 19.9564C83.9573 19.9076 84.0407 19.7947 84.0861 19.8229C84.1034 19.8338 84.1283 19.8089 84.1413 19.7681C84.1635 19.6976 84.3084 19.5769 84.3594 19.586C84.3725 19.5882 84.441 19.525 84.5115 19.4452C84.582 19.3656 84.6595 19.3004 84.6836 19.3004C84.7078 19.3004 84.7859 19.2482 84.8573 19.1844C84.9877 19.0681 85.0791 19.0298 85.0276 19.1132C85.0103 19.1409 85.017 19.1473 85.0451 19.1298C85.0702 19.1145 85.0815 19.0874 85.0706 19.0699C85.0447 19.0276 85.162 18.9839 85.2146 19.0165C85.2399 19.032 85.2443 19.0233 85.2259 18.9934C85.2053 18.9604 85.2181 18.9495 85.2667 18.9588C85.3062 18.9663 85.386 18.9251 85.4466 18.8659C85.5065 18.8073 85.5854 18.7587 85.6218 18.7581C85.6582 18.7574 85.7214 18.7317 85.7622 18.7009C85.8214 18.6561 85.848 18.6543 85.8953 18.6924C85.9354 18.7248 85.9454 18.7257 85.9272 18.6951C85.9236 18.6896 85.9213 18.6834 85.9204 18.6769C85.9196 18.6704 85.9202 18.6638 85.9223 18.6576C85.9243 18.6514 85.9278 18.6457 85.9324 18.641C85.937 18.6363 85.9426 18.6328 85.9487 18.6305C85.9753 18.6197 82.8414 18.6108 78.9841 18.6106C72.8149 18.6104 71.9897 18.617 72.1256 18.6663C72.2106 18.6971 72.2993 18.7477 72.3226 18.7789C72.3461 18.81 72.3756 18.8251 72.3885 18.8122C72.4013 18.7993 72.4381 18.8153 72.4705 18.8477C72.5029 18.8798 72.5907 18.9444 72.6659 18.9907C72.7409 19.0371 72.7925 19.0908 72.7808 19.1101C72.7688 19.1291 72.7892 19.1333 72.8258 19.1194C72.8793 19.099 72.8868 19.1085 72.8644 19.1668C72.8491 19.2072 72.8482 19.2283 72.8626 19.2139C72.8995 19.177 73.1496 19.3753 73.1496 19.4414C73.1496 19.4716 73.2033 19.5485 73.269 19.6129C73.3368 19.6792 73.379 19.7533 73.367 19.785C73.3548 19.8162 73.3661 19.8364 73.3925 19.8311C73.4182 19.8262 73.4371 19.8522 73.4342 19.8892C73.4311 19.9262 73.4413 19.9487 73.4566 19.9393C73.4719 19.9298 73.5078 20.0083 73.5364 20.1134C73.565 20.2188 73.605 20.3051 73.6247 20.3051C73.6447 20.3051 73.6518 20.3397 73.6407 20.3822C73.6296 20.4246 73.6351 20.4685 73.6531 20.4796C73.6711 20.4907 73.685 20.7167 73.6841 20.9818C73.6833 21.2468 73.67 21.4559 73.6549 21.4466C73.6396 21.4373 73.6347 21.4801 73.6438 21.542C73.654 21.6123 73.6369 21.6777 73.5981 21.7168C73.5639 21.7509 73.536 21.8199 73.536 21.87C73.536 21.9204 73.5158 22.0104 73.4912 22.0703C73.4666 22.13 73.4499 22.2007 73.4541 22.2273C73.4586 22.2539 73.4484 22.2757 73.4315 22.2757C73.4145 22.2757 73.3969 22.3313 73.3921 22.3992C73.3872 22.4671 73.3568 22.5374 73.3244 22.5556C73.292 22.5738 73.2656 22.6401 73.2656 22.7031C73.2656 22.8182 73.2022 22.9659 73.1303 23.0189C73.1064 23.0364 73.1099 23.0475 73.1399 23.0477C73.1665 23.0482 73.1882 23.0668 73.1882 23.0892C73.1882 23.1118 73.1683 23.1178 73.1436 23.1027C73.1175 23.0865 73.1095 23.0919 73.1241 23.1158C73.1598 23.1735 73.1088 23.3993 73.066 23.3729C73.0458 23.3605 73.0412 23.3937 73.0556 23.4509C73.0693 23.5057 73.0647 23.5508 73.0454 23.5508C73.0259 23.5508 72.9782 23.6727 72.9396 23.822C72.9008 23.971 72.8538 24.1028 72.8349 24.1143C72.8161 24.1261 72.8107 24.1522 72.8234 24.1724C72.8476 24.2117 72.7699 24.4845 72.7251 24.5166C72.701 24.5342 72.4936 25.2796 72.4922 25.3546C72.4918 25.3719 72.4738 25.3599 72.4523 25.3282C72.4235 25.2856 72.4199 25.2993 72.4388 25.3805C72.4559 25.4537 72.4474 25.5016 72.4137 25.5225C72.3858 25.5395 72.3585 25.5839 72.3532 25.6207C72.3476 25.6573 72.3228 25.7001 72.2977 25.7156C72.2629 25.7372 72.2629 25.7474 72.2975 25.7589C72.3321 25.7704 72.3317 25.8015 72.296 25.8891C72.27 25.9525 72.2463 26.0217 72.2434 26.043C72.2203 26.202 72.17 26.3715 72.1456 26.3715C72.1192 26.3715 72.0895 26.466 72.0425 26.6997C72.0338 26.7423 72.011 26.7825 71.9914 26.7893C71.9719 26.796 71.965 26.8246 71.9759 26.853C71.9868 26.8814 71.9768 26.9162 71.9537 26.9304C71.9307 26.9446 71.9198 26.969 71.9293 26.9847C71.9575 27.0304 71.8743 27.3522 71.8269 27.3815C71.8029 27.3964 71.7792 27.4365 71.7741 27.4709C71.7472 27.6539 71.6636 27.9105 71.6364 27.8936C71.619 27.883 71.6146 27.8994 71.6264 27.9302C71.6521 27.9972 71.5723 28.3133 71.5219 28.3448C71.5024 28.357 71.4787 28.4062 71.4696 28.4541C71.4577 28.512 71.4426 28.5691 71.4243 28.6253C71.4103 28.6652 71.3995 28.7061 71.3919 28.7477C71.3693 28.9553 71.3205 29.0691 71.2622 29.0505C71.2143 29.0354 71.211 29.0394 71.2489 29.0665C71.3015 29.1044 71.2753 29.308 71.2178 29.308C71.2012 29.308 71.1761 29.3863 71.1617 29.4819C71.1473 29.5775 71.1229 29.6558 71.1076 29.6558C71.0923 29.6558 71.0766 29.6861 71.073 29.7234C71.0555 29.8991 71.0125 30.0392 70.9818 30.0204C70.9632 30.0088 70.9581 30.0259 70.9708 30.0585C70.9832 30.0909 70.9654 30.1452 70.9313 30.1794C70.8971 30.2136 70.8778 30.2555 70.8885 30.2726C70.9053 30.3001 70.8687 30.4482 70.8022 30.6217C70.7716 30.7015 70.7725 30.698 70.7381 30.8851C70.7215 30.977 70.6818 31.0621 70.6503 31.0741C70.6035 31.0921 70.6024 31.1023 70.6445 31.1293C70.6829 31.1542 70.6844 31.1701 70.6507 31.1921C70.6259 31.2083 70.5931 31.2735 70.5778 31.3369C70.5624 31.4006 70.5398 31.4698 70.5274 31.4911C70.515 31.5124 70.499 31.5731 70.4919 31.6264C70.468 31.8067 70.3575 32.1478 70.314 32.1755C70.2903 32.1908 70.2699 32.2168 70.2686 32.2334C70.2575 32.3818 70.1989 32.5923 70.1688 32.5923C70.1481 32.5923 70.1415 32.6089 70.1539 32.6293C70.1843 32.6781 70.1355 32.8673 70.0985 32.8444C70.0827 32.8345 70.0778 32.8695 70.0878 32.9218C70.0982 32.976 70.0878 33.0174 70.0641 33.0174C70.041 33.0174 70.0332 33.046 70.047 33.0818C70.0634 33.125 70.0568 33.1368 70.0264 33.1181C69.9967 33.0997 69.9811 33.1219 69.9811 33.1827C69.9811 33.2335 69.9481 33.3778 69.9077 33.5036C69.8689 33.6234 69.835 33.7447 69.8061 33.8673C69.7908 33.9419 69.762 34.0131 69.7418 34.0259C69.7219 34.0386 69.6992 34.082 69.6917 34.1224C69.6842 34.1628 69.6753 34.1958 69.6722 34.1958C69.6688 34.1958 69.6586 34.2393 69.6493 34.2925C69.6212 34.4542 69.5981 34.4921 69.5466 34.4613C69.5094 34.4389 69.5083 34.4451 69.542 34.4879C69.5733 34.5276 69.5744 34.5715 69.5458 34.6403C69.5238 34.6933 69.5083 34.7629 69.5116 34.7949C69.5218 34.9002 69.4608 34.943 69.2681 34.9656C69.1634 34.9781 69.0669 35.0053 69.054 35.0262C68.9693 35.1633 66.2331 35.1619 66.2331 35.0249C66.2331 35.0093 66.1765 34.9878 66.1076 34.9772C66.0386 34.9665 65.9386 34.9459 65.8853 34.9313C65.8378 34.9177 65.7894 34.9076 65.7405 34.9011C65.7139 34.8993 65.6921 34.8814 65.6921 34.8614C65.6921 34.8414 65.6662 34.835 65.6345 34.8472C65.5753 34.8701 65.1858 34.7623 65.1512 34.7135C65.1405 34.6986 65.0341 34.6432 64.9148 34.5904C64.7952 34.5376 64.6859 34.4757 64.6719 34.4531C64.6579 34.4302 64.6209 34.4216 64.5896 34.4336C64.5539 34.4473 64.5331 34.4316 64.5331 34.391C64.5331 34.3555 64.5155 34.3373 64.494 34.3506C64.4727 34.3639 64.4448 34.3475 64.4319 34.3142C64.4193 34.281 64.3758 34.2539 64.3357 34.2539C64.2955 34.2539 64.2237 34.2147 64.1762 34.167C64.1269 34.1175 64.0718 34.0743 64.0121 34.0381C63.9693 34.0153 63.9389 33.9747 63.9447 33.9483C63.9506 33.9219 63.9384 33.9108 63.9178 33.9234C63.8704 33.9527 63.4512 33.5655 63.4512 33.4923C63.4512 33.4623 63.4337 33.4486 63.4121 33.4619C63.3908 33.4752 63.3616 33.4544 63.3472 33.4158C63.3327 33.3774 63.2893 33.3231 63.2507 33.2953C63.2121 33.2676 63.1806 33.2219 63.1806 33.1938C63.1806 33.1656 63.1467 33.1188 63.1052 33.0897C63.0635 33.0605 63.0244 33.0119 63.0182 32.9815C63.0067 32.9265 62.9371 32.8254 62.8401 32.7236C62.8122 32.6943 62.7869 32.6366 62.7838 32.5954C62.7807 32.5541 62.7665 32.5277 62.7521 32.5366C62.7226 32.5548 62.6268 32.3427 62.6268 32.2596C62.6268 32.2301 62.6124 32.2059 62.5946 32.2059C62.5769 32.2059 62.5625 32.1788 62.5625 32.1458C62.5625 32.1125 62.5474 32.0948 62.529 32.1061C62.4902 32.13 62.3238 31.6687 62.3538 31.6202C62.3646 31.6024 62.3566 31.5878 62.3358 31.5878C62.3152 31.5878 62.2859 31.5312 62.2708 31.4622C62.2557 31.393 62.2287 31.3269 62.2103 31.3154C62.1921 31.3037 62.1655 31.2358 62.1513 31.1644C62.1326 31.0717 62.138 31.0426 62.1694 31.0621C62.1981 31.0797 62.2056 31.0683 62.1907 31.0297C62.1783 30.9967 62.1537 30.9787 62.1364 30.9894C62.0967 31.0138 62.0459 30.792 62.0787 30.7385C62.0923 30.7168 62.0876 30.6991 62.0685 30.6991C62.0495 30.6991 62.0109 30.5511 61.9827 30.3706C61.9548 30.1898 61.917 30.0421 61.8993 30.0421C61.8816 30.0421 61.8669 30.0159 61.8669 29.9842C61.8669 29.9523 61.8887 29.9259 61.9153 29.9257C61.9483 29.9252 61.9459 29.9139 61.9073 29.8895C61.8687 29.8649 61.8505 29.7811 61.8494 29.6196C61.8483 29.4907 61.8332 29.3854 61.8159 29.3854C61.7986 29.3852 61.7875 29.2765 61.7913 29.1439C61.7953 29.011 61.7884 28.8762 61.7762 28.8442C61.7587 28.7983 61.7676 27.0562 61.7886 26.4487C61.7988 26.1473 61.8328 25.9833 61.8791 26.0111C61.9057 26.027 61.9029 26.0113 61.872 25.9734C61.8099 25.8966 61.8461 25.4817 61.919 25.4349C61.9514 25.4142 61.9503 25.4065 61.9153 25.406C61.8887 25.4056 61.8669 25.3783 61.8669 25.3453C61.8669 25.312 61.8842 25.2956 61.9055 25.3089C61.9277 25.3224 61.9441 25.2874 61.9441 25.2262C61.9441 25.0725 62.0974 23.8515 62.1253 23.7825C62.1382 23.7506 62.1448 23.6836 62.1397 23.6333C62.1348 23.5831 62.1459 23.5514 62.1646 23.563C62.1832 23.5745 62.1912 23.5224 62.1825 23.447C62.1737 23.3715 62.1856 23.2981 62.2089 23.2837C62.2544 23.2555 62.2843 23.134 62.289 22.9592C62.2905 22.898 62.3085 22.861 62.33 22.8743C62.3518 22.8876 62.3586 22.8725 62.3458 22.839C62.3192 22.77 62.403 22.2371 62.4403 22.2366C62.4542 22.2366 62.468 22.1564 62.4709 22.0583C62.4735 21.9603 62.4928 21.8691 62.5134 21.8556C62.544 21.8359 62.5762 21.7272 62.6179 21.5027C62.6199 21.4921 62.6343 21.4633 62.6501 21.4386C62.6658 21.414 62.668 21.3661 62.6549 21.3324C62.6421 21.2987 62.6483 21.271 62.6689 21.271C62.6893 21.271 62.698 21.2275 62.6878 21.1743C62.6776 21.1213 62.6844 21.0778 62.7029 21.0776C62.7213 21.0773 62.739 21.0039 62.7426 20.9145C62.7461 20.8249 62.7667 20.7455 62.7887 20.7382C62.8106 20.7309 62.8182 20.6983 62.8058 20.6657C62.7931 20.6331 62.8033 20.5938 62.8282 20.5783C62.8739 20.5501 62.8796 20.5308 62.9282 20.2376C62.9433 20.1474 62.9717 20.0635 62.9914 20.0513C63.0111 20.0391 63.0189 20.0156 63.0089 19.9992C62.9772 19.9482 63.0657 19.6867 63.1147 19.6863C63.144 19.6858 63.1398 19.6703 63.1034 19.6446C63.0597 19.6137 63.0573 19.5987 63.0936 19.584C63.1203 19.5732 63.142 19.5397 63.142 19.5097C63.142 19.4796 63.1577 19.4549 63.177 19.4549C63.1963 19.4549 63.203 19.4201 63.1917 19.3775C63.1806 19.3347 63.1908 19.2766 63.2143 19.2482C63.238 19.2198 63.2462 19.1857 63.2327 19.1722C63.2192 19.1586 63.2281 19.1238 63.252 19.095C63.2762 19.0659 63.2844 19.0307 63.2704 19.0167C63.2564 19.0027 63.2664 18.9912 63.2924 18.9912C63.3183 18.9912 63.3285 18.9732 63.315 18.951C63.2897 18.9104 63.3718 18.5243 63.4132 18.4888C63.4496 18.4578 63.5669 18.1251 63.5669 18.053C63.5669 18.0164 63.582 17.9867 63.6002 17.9867C63.6186 17.9867 63.6248 17.9406 63.614 17.8842C63.6033 17.8279 63.61 17.7915 63.629 17.803C63.6481 17.8148 63.667 17.7611 63.6712 17.6839C63.6752 17.6068 63.6965 17.5378 63.7182 17.5305C63.7399 17.5231 63.769 17.4577 63.7825 17.385C63.7963 17.312 63.8247 17.2526 63.846 17.2526C63.867 17.2526 63.8744 17.2264 63.8622 17.1945C63.85 17.1627 63.8579 17.1366 63.8797 17.1366C63.9016 17.1366 63.9156 17.1062 63.9109 17.0689C63.8974 16.9647 63.9575 16.7132 64.0081 16.6613C64.0578 16.6105 64.2474 16.0877 64.2596 15.9677C64.2612 15.9518 64.2867 15.9387 64.3164 15.9387C64.372 15.9387 64.4344 15.8273 64.3987 15.7914C64.3876 15.7803 64.3785 15.7945 64.3785 15.8229C64.3785 15.8511 64.3703 15.8662 64.3601 15.8559C64.3272 15.8231 64.479 15.4725 64.5127 15.5033C64.5306 15.5197 64.5328 15.5111 64.5175 15.4844C64.4883 15.4337 64.5683 15.166 64.6127 15.166C64.6269 15.166 64.6684 15.0704 64.7052 14.9533C64.742 14.8364 64.7877 14.7503 64.8065 14.7621C64.8256 14.7738 64.8309 14.7565 64.8183 14.7235C64.8056 14.6907 64.8101 14.6636 64.8283 14.6636C64.8465 14.6636 64.864 14.6179 64.8673 14.562C64.8706 14.5061 64.8955 14.4467 64.9225 14.4298C64.9498 14.413 64.9764 14.3693 64.9818 14.3325C64.9871 14.2957 65.0115 14.2533 65.0361 14.2382C65.0605 14.2229 65.0762 14.2038 65.0711 14.1956C65.0454 14.1548 65.1627 13.8933 65.1971 13.9146C65.2222 13.9301 65.2273 13.9091 65.2106 13.8569C65.1953 13.8084 65.2015 13.7749 65.2259 13.7749C65.2486 13.7749 65.2672 13.7489 65.2672 13.717C65.2672 13.6851 65.2845 13.6589 65.3058 13.6589C65.3271 13.6589 65.3402 13.646 65.3351 13.6301C65.3178 13.5764 65.4664 13.2339 65.507 13.2339C65.5298 13.2339 65.5243 13.263 65.4941 13.3016C65.4466 13.3619 65.448 13.3639 65.5047 13.3196C65.5396 13.292 65.56 13.2382 65.55 13.1996C65.5398 13.1612 65.5604 13.1009 65.5954 13.0658C65.6305 13.0308 65.6447 13.0015 65.6274 13.0011C65.6099 13.0004 65.6267 12.9815 65.6649 12.9594C65.7103 12.933 65.7261 12.8935 65.7108 12.8451C65.6948 12.795 65.7192 12.7416 65.7864 12.6795C65.8407 12.6289 65.8853 12.5677 65.8853 12.5431C65.8853 12.4834 65.9685 12.3395 66.0399 12.2756C66.0719 12.247 66.0761 12.2346 66.0497 12.2481C65.9787 12.284 65.9909 12.2166 66.0707 12.1303C66.1091 12.0891 66.1974 11.938 66.2673 11.7947C66.3371 11.6512 66.4059 11.5339 66.4205 11.5339C66.4349 11.5339 66.5059 11.4122 66.5782 11.2633C66.6505 11.1145 66.7339 10.993 66.7634 10.993C66.7931 10.993 66.8071 10.9763 66.7947 10.9562C66.782 10.936 66.8069 10.9007 66.8497 10.8779C66.8727 10.866 66.8916 10.8475 66.9038 10.8248C66.9161 10.802 66.9212 10.776 66.9184 10.7503C66.9131 10.7 66.9288 10.6683 66.9561 10.6736C66.9821 10.6787 66.9941 10.6592 66.983 10.6303C66.9719 10.6015 66.9898 10.5674 67.0231 10.5547C67.0562 10.5421 67.0832 10.505 67.0832 10.4724C67.0832 10.4398 67.0963 10.4132 67.1125 10.4132C67.1285 10.4132 67.1637 10.3633 67.1908 10.3021C67.2181 10.2409 67.2815 10.1424 67.3321 10.0836C67.3829 10.0246 67.4465 9.93126 67.4738 9.87603C67.5011 9.82081 67.5854 9.71789 67.6608 9.64736C67.7362 9.57684 67.7765 9.52982 67.7501 9.54312C67.7187 9.55887 67.7102 9.54667 67.7253 9.50719C67.7379 9.47437 67.7617 9.44731 67.7781 9.44731C67.7945 9.44731 67.8295 9.39519 67.8559 9.33131C67.8823 9.26766 67.9178 9.21554 67.9349 9.21554C67.9517 9.21554 68.0056 9.15033 68.0544 9.07049C68.118 8.97211 68.1902 8.87962 68.2702 8.79414C68.3399 8.72183 68.3969 8.64044 68.3969 8.61316C68.3969 8.5861 68.449 8.52666 68.5129 8.48141C68.5765 8.43595 68.6289 8.37584 68.6289 8.34767C68.6289 8.31973 68.689 8.24853 68.7626 8.18998C68.8363 8.13121 68.889 8.07088 68.8797 8.05602C68.8538 8.01388 69.0361 7.85862 69.0725 7.89167C69.0902 7.90786 69.0931 7.90032 69.0784 7.87504C69.064 7.84975 69.0742 7.81515 69.1013 7.79785C69.1283 7.78055 69.1703 7.73176 69.1944 7.68918C69.2186 7.64659 69.2663 7.61421 69.3002 7.61732C69.3342 7.6202 69.3535 7.60844 69.3428 7.59137C69.3322 7.57429 69.3455 7.53681 69.3723 7.50842C69.3989 7.47981 69.4861 7.38266 69.5657 7.29261C69.6456 7.20257 69.7108 7.13758 69.7108 7.14823C69.7108 7.1591 69.776 7.09433 69.8556 7.00473C70.0415 6.79536 70.2193 6.64299 70.2624 6.65652C70.2808 6.66229 70.2856 6.65053 70.2732 6.63013C70.251 6.59442 70.4744 6.35666 70.5303 6.35622C70.5454 6.35622 70.6323 6.28613 70.7235 6.20052C71.04 5.90332 71.083 5.86606 71.2081 5.78023C71.2771 5.73276 71.3338 5.70814 71.3341 5.72567C71.3345 5.74296 71.3567 5.71391 71.3833 5.6609C71.4101 5.60812 71.4636 5.55866 71.5022 5.55112C71.5408 5.5438 71.6062 5.50387 71.6477 5.46262C71.6889 5.42115 71.7393 5.39764 71.7595 5.41006C71.7799 5.4227 71.7861 5.40606 71.7734 5.3728C71.7603 5.33908 71.7708 5.31291 71.7967 5.31291C71.8224 5.31291 71.8939 5.27698 71.9555 5.23307C72.0342 5.17696 72.068 5.16831 72.0688 5.20401C72.0695 5.23551 72.0853 5.22885 72.1099 5.18649C72.1318 5.14879 72.1649 5.12727 72.1833 5.13881C72.2017 5.15012 72.2279 5.12395 72.2416 5.0807C72.2554 5.03745 72.3507 4.9596 72.4534 4.90748C72.5561 4.85558 72.6459 4.79925 72.6533 4.78283C72.669 4.74735 72.9407 4.61738 72.999 4.61738C73.0212 4.61738 73.0654 4.59121 73.0975 4.55905C73.1297 4.52689 73.1718 4.5107 73.1913 4.52267C73.2108 4.53487 73.2268 4.51757 73.2268 4.4843C73.2268 4.42952 73.28 4.40912 73.41 4.41377C73.4364 4.41466 73.4495 4.40202 73.4395 4.38561C73.4293 4.36919 73.4566 4.34635 73.5001 4.33504C73.5686 4.31707 73.5726 4.32284 73.5298 4.37895C73.5025 4.41444 73.5276 4.40135 73.5854 4.3499C73.6433 4.29822 73.6906 4.26917 73.6906 4.28491C73.6906 4.30088 73.7161 4.29068 73.7471 4.26273C73.8915 4.13254 73.9297 4.11147 74.0346 4.10393C74.0962 4.09927 74.137 4.07998 74.1251 4.06068C74.1133 4.04139 74.141 4.0354 74.1867 4.04738C74.2326 4.05935 74.2701 4.05203 74.2701 4.03096C74.2701 4.00989 74.2916 3.99991 74.318 4.00878C74.3444 4.01743 74.3892 4.00147 74.4174 3.9733C74.4458 3.94491 74.5023 3.91962 74.5434 3.91696C74.6795 3.90809 74.6977 3.90277 74.7257 3.86329C74.7691 3.80119 75.0814 3.73022 75.0821 3.78234C75.0825 3.80984 75.0936 3.80806 75.1131 3.77746C75.1298 3.75106 75.2904 3.69939 75.47 3.66235C75.6494 3.62553 75.8051 3.58361 75.8158 3.5692C75.8584 3.51197 76.2922 3.48336 76.2589 3.53992C76.2416 3.56942 76.2631 3.5621 76.3068 3.52395C76.3864 3.45431 76.5217 3.44965 76.6235 3.51353C76.663 3.53814 76.6692 3.53349 76.6464 3.49667C76.6231 3.45897 76.6364 3.45165 76.6985 3.46784C76.7442 3.47981 76.7732 3.4756 76.7626 3.45852C76.7406 3.42304 78.3253 3.41372 78.3826 3.44898C78.403 3.46185 78.5032 3.46762 78.6055 3.46229C78.7075 3.45697 78.7911 3.46673 78.7913 3.48425C78.7915 3.50177 78.914 3.51996 79.0635 3.52484C79.2462 3.5306 79.3547 3.55278 79.3944 3.59248C79.4267 3.62486 79.5044 3.65148 79.5669 3.65148C79.7348 3.65148 80.3924 3.80407 80.4073 3.84666C80.4144 3.86684 80.4525 3.88325 80.4918 3.88325C80.531 3.88325 80.6122 3.90343 80.6721 3.92805C80.732 3.95267 80.7945 3.96997 80.8114 3.9662C80.877 3.95178 80.9946 4.04338 80.9678 4.08796C80.9487 4.11968 80.9593 4.11879 81.0012 4.08464C81.0518 4.04383 81.0733 4.04605 81.1246 4.09706C81.1587 4.13121 81.1867 4.1423 81.1867 4.12145C81.1867 4.10061 81.2215 4.09284 81.2638 4.10393C81.3064 4.11502 81.3412 4.13942 81.3412 4.15827C81.3412 4.1769 81.3661 4.19243 81.3965 4.19243C81.4266 4.19243 81.4745 4.21416 81.5027 4.24056C81.5307 4.26717 81.5885 4.29423 81.6309 4.30066C81.7941 4.3255 81.9592 4.39315 81.9385 4.42686C81.9265 4.44616 81.9443 4.45126 81.9778 4.43839C82.0146 4.42442 82.068 4.4486 82.1122 4.49939C82.1525 4.54574 82.1954 4.58256 82.2076 4.58123C82.3071 4.56991 82.3466 4.58455 82.3224 4.62403C82.3036 4.65442 82.3156 4.66107 82.3588 4.64444C82.3941 4.63091 82.4231 4.63756 82.4231 4.65952C82.4231 4.68125 82.4391 4.68924 82.4586 4.67726C82.4781 4.66506 82.5196 4.68081 82.5507 4.71186C82.5817 4.74291 82.6183 4.75711 82.6318 4.74335C82.6456 4.72983 82.6833 4.75666 82.7159 4.80324C82.7485 4.84981 82.8097 4.88774 82.8516 4.88774C82.9388 4.88774 83.1045 4.98644 83.2085 5.10044C83.2473 5.1428 83.2695 5.15832 83.258 5.13482C83.2462 5.11131 83.34 5.14613 83.4664 5.21222C83.5926 5.27809 83.7011 5.35816 83.7073 5.3901C83.7108 5.40597 83.7195 5.42025 83.7319 5.43075C83.7443 5.44125 83.7598 5.44738 83.7761 5.4482C83.8615 5.4482 84.1613 5.63429 84.1615 5.6873C84.163 5.70216 84.1679 5.71649 84.1757 5.72923C84.1835 5.74197 84.194 5.75281 84.2066 5.76093C84.2352 5.77867 84.2405 5.77135 84.2216 5.74075C84.2054 5.71458 84.2533 5.73321 84.3283 5.78244C84.4033 5.83146 84.4545 5.88802 84.4421 5.90798C84.4297 5.92816 84.4476 5.93348 84.4829 5.91995C84.5005 5.91283 84.52 5.91245 84.5378 5.91888C84.5556 5.92531 84.5704 5.93809 84.5794 5.95477C84.5976 5.98738 84.6546 6.03595 84.706 6.06279C84.7573 6.0894 84.7952 6.13088 84.7903 6.15505C84.7852 6.17901 84.8056 6.18943 84.8356 6.1779C84.8666 6.16592 84.9087 6.19165 84.9331 6.23711C84.9566 6.28147 84.9946 6.3174 85.0174 6.3174C85.04 6.3174 85.1135 6.3622 85.1802 6.41676C85.4563 6.6421 85.6027 6.76453 85.6495 6.80889C85.6894 6.84659 85.7036 6.82752 85.7216 6.71219C85.7742 6.37462 85.8567 6.07454 85.9055 6.04416C85.925 6.03196 85.9487 5.98272 85.9578 5.93481C85.9671 5.88691 85.9873 5.80995 86.0031 5.76381C86.0186 5.71768 86.0332 5.66246 86.0354 5.64139C86.0523 5.48791 86.1084 5.31247 86.1297 5.34707C86.1439 5.37013 86.1556 5.32533 86.1556 5.24726C86.1556 5.16919 86.1765 5.09844 86.202 5.09001C86.2275 5.08159 86.2484 5.04233 86.2484 5.00285C86.2484 4.96337 86.267 4.91946 86.2896 4.90548C86.3125 4.89151 86.3224 4.85758 86.3118 4.8303C86.2881 4.7682 86.4185 4.33659 86.4511 4.36942C86.4642 4.3825 86.4655 4.35677 86.4537 4.31197C86.4422 4.26739 86.4497 4.23102 86.4708 4.23102C86.4919 4.23102 86.5225 4.17446 86.5387 4.10548C86.5666 3.98705 86.5728 3.9642 86.5959 3.89279C86.6013 3.87445 86.6031 3.85525 86.6012 3.83623C86.5988 3.82115 86.617 3.76016 86.6414 3.70094C86.6658 3.64194 86.6822 3.57163 86.678 3.54502C86.6735 3.51863 86.6837 3.49689 86.7006 3.49667C86.7177 3.49667 86.7352 3.44144 86.7401 3.37402C86.7447 3.3066 86.764 3.24139 86.7827 3.22919C86.8015 3.21699 86.8383 3.11563 86.8649 3.00407C86.8913 2.89251 86.9281 2.80136 86.9466 2.80136C86.965 2.80136 86.9707 2.77696 86.9594 2.74724C86.9479 2.71752 86.9574 2.68159 86.9805 2.6674C87.0036 2.65298 87.0144 2.62858 87.0049 2.61306C86.98 2.57291 87.0572 2.2471 87.0976 2.22226C87.1723 2.17613 87.1888 1.98716 87.1158 2.01533C87.0732 2.03174 87.0563 2.02664 87.0716 2.00202C87.0856 1.9794 87.0592 1.96277 87.0104 1.96321C86.8248 1.96476 86.7472 1.94968 86.7678 1.91619C86.7798 1.89689 86.7518 1.89091 86.7061 1.90288C86.6527 1.91686 86.6318 1.90998 86.648 1.88359C86.664 1.85786 86.6449 1.84987 86 | 2026-01-13T08:48:30 |
https://www.instagram.com/p/DJCy2XNT5hv/?utm_source=ig_web_button_share_sheet&hl=kn | Instagram Close By continuing, you agree to Instagram's Terms of Use and Privacy Policy . Instagram Log In Sign Up Meta About Blog Jobs Help API Privacy Terms Locations Instagram Lite Meta AI Threads Contact Uploading & Non-Users Meta Verified English Down chevron icon Afrikaans العربية Čeština Dansk Deutsch Ελληνικά English English (UK) Español (España) Español فارسی Suomi Français עברית Bahasa Indonesia Italiano 日本語 한국어 Bahasa Melayu Norsk Nederlands Polski Português (Brasil) Português (Portugal) Русский Svenska ภาษาไทย Filipino Türkçe 中文(简体) 中文(台灣) বাংলা ગુજરાતી हिन्दी Hrvatski Magyar ಕನ್ನಡ മലയാളം मराठी नेपाली ਪੰਜਾਬੀ සිංහල Slovenčina தமிழ் తెలుగు اردو Tiếng Việt 中文(香港) Български Français (Canada) Română Српски Українська © 2026 Instagram from Meta {"require":[["ScheduledServerJS","handle",null,[{"__bbox":{"define":[["cr:10762",[],{"__rc":[null,null]},-1],["cr:10763",["usePolarisNotificationsSecurityAlertUnseenCountDataDefault.react"],{"__rc":["usePolarisNotificationsSecurityAlertUnseenCountDataDefault.react",null]},-1],["cr:497",[],{"__rc":[null,"Aa7n7lSqr9SDD6YcVmIuGkICe9UecBQGVQiJKRwD1FBqrurbM364GvNOdWewtKouPYcQk5wFNFubIY2cWgW7Gy2ZcUHQGGHIyfYdnT9iFFuPuHjjCzEbf3iHjA"]},-1],["cr:2691",[],{"__rc":[null,null]},-1],["cr:3921",[],{"__rc":[null,"Aa6GU5zeP_0zABdGmWlMRZPLBMSSLv0xFO-qkb8Kn4_lmNEd_5LelGOAJyqzl-PYHoJB1hF0KcaUqS9KoHBSjcIO3jaQCp-KBbnSGjLjtGDEhoEAlRmyH9x8MQ"]},-1],["cr:4790",[],{"__rc":[null,null]},-1],["cr:5083",["LSPlatformRealtimeTransportEager"],{"__rc":["LSPlatformRealtimeTransportEager",null]},-1],["cr:6044",["LSPlatformTaskSystemTransportEager"],{"__rc":["LSPlatformTaskSystemTransportEager",null]},-1],["cr:6542",["LSDatascriptEvaluatorMaybeEagerly"],{"__rc":["LSDatascriptEvaluatorMaybeEagerly",null]},-1],["cr:6600",["IGDBundleResource"],{"__rc":["IGDBundleResource",null]},-1],["cr:6943",["EventListenerImplForCacheStorage"],{"__rc":["EventListenerImplForCacheStorage",null]},-1],["cr:6985",[],{"__rc":[null,"Aa7n7lSqr9SDD6YcVmIuGkICe9UecBQGVQiJKRwD1FBqrurbM364GvNOdWewtKouPYcQk5wFNFubIY2cWgW7Gy2ZcUHQGGHIyfYdnT9iFFuPuHjjCzEbf3iHjA"]},-1],["cr:6998",[],{"__rc":[null,"Aa7n7lSqr9SDD6YcVmIuGkICe9UecBQGVQiJKRwD1FBqrurbM364GvNOdWewtKouPYcQk5wFNFubIY2cWgW7Gy2ZcUHQGGHIyfYdnT9iFFuPuHjjCzEbf3iHjA"]},-1],["cr:6999",[],{"__rc":[null,"Aa7n7lSqr9SDD6YcVmIuGkICe9UecBQGVQiJKRwD1FBqrurbM364GvNOdWewtKouPYcQk5wFNFubIY2cWgW7Gy2ZcUHQGGHIyfYdnT9iFFuPuHjjCzEbf3iHjA"]},-1],["cr:7070",[],{"__rc":[null,null]},-1],["cr:7347",[],{"__rc":[null,null]},-1],["cr:7349",[],{"__rc":[null,null]},-1],["cr:7350",[],{"__rc":[null,null]},-1],["cr:7528",["MWPlatformTaskSystemEager"],{"__rc":["MWPlatformTaskSystemEager",null]},-1],["cr:7542",[],{"__rc":[null,null]},-1],["cr:8131",[],{"__rc":[null,null]},-1],["cr:8709",[],{"__rc":[null,null]},-1],["cr:9378",[],{"__rc":[null,"Aa7n7lSqr9SDD6YcVmIuGkICe9UecBQGVQiJKRwD1FBqrurbM364GvNOdWewtKouPYcQk5wFNFubIY2cWgW7Gy2ZcUHQGGHIyfYdnT9iFFuPuHjjCzEbf3iHjA"]},-1],["cr:9379",[],{"__rc":[null,null]},-1],["cr:10018",[],{"__rc":[null,null]},-1],["cr:12301",["LSPlatformClientDeferred"],{"__rc":["LSPlatformClientDeferred",null]},-1],["cr:12497",[],{"__rc":[null,null]},-1],["cr:1609",[],{"__rc":[null,null]},-1],["cr:3106",[],{"__rc":[null,null]},-1],["cr:4779",[],{"__rc":[null,null]},-1],["cr:4839",[],{"__rc":[null,null]},-1],["cr:7274",[],{"__rc":[null,null]},-1],["cr:8738",[],{"__rc":[null,null]},-1],["cr:9681",["PolarisQPManager.react"],{"__rc":["PolarisQPManager.react",null]},-1],["cr:27495",["IGSignalingListenerDeferred"],{"__rc":["IGSignalingListenerDeferred","Aa4MBKNttCUBoUtdFZ1L06ypksdvGmo4fkKCy84fffAwLJwpotzoIZyJ4wHSjWexpyDdbyiiaeOxjs4qs0GiJOlxmSTUWCTUMaRgyyI8ef9FNpvj6Dq0ZigI_Q"]},-1],["cr:3024",[],{"__rc":[null,null]},-1],["cr:2046346",[],{"__rc":[null,"Aa76QMhpyxKWE4AePNEXgX7Cb9Vj5bVS2dhBURlwtE-iBIK_-UZDD001qfZJe0hWZKg0PRmkh3rGrFiImSn12ryltPYMSaPigAnMYDW9V-0ve3iAx7wSjNI7mQ"]},-1],["cr:8828",[],{"__rc":[null,null]},-1],["cr:1094907",[],{"__rc":[null,null]},-1],["cr:4890",[],{"__rc":[null,null]},-1],["cr:2718",[],{"__rc":[null,null]},-1],["cr:17080",[],{"__rc":[null,null]},-1],["cr:22915",[],{"__rc":[null,null]},-1],["cr:1201738",[],{"__rc":[null,null]},-1],["cr:1332233",[],{"__rc":[null,null]},-1],["cr:1345969",["AccessibilityWebAssistiveTechTypedLoggerLite"],{"__rc":["AccessibilityWebAssistiveTechTypedLoggerLite",null]},-1],["cr:1516609",["BDCometSignalCollectionTrigger"],{"__rc":["BDCometSignalCollectionTrigger",null]},-1],["cr:2389",["PolarisLexicalMentionsPlugin.new.react"],{"__rc":["PolarisLexicalMentionsPlugin.new.react",null]},-1],["cr:3286",[],{"__rc":[null,null]},-1],["WorkerConfig",[],{"worker":"shared"},7679],["MqttWebConfig",[],{"fbid":"0","appID":219994525426954,"endpoint":"wss:\/\/edge-chat.facebook.com\/chat","pollingEndpoint":"https:\/\/edge-chat.facebook.com\/mqtt\/pull","subscribedTopics":[],"capabilities":10,"clientCapabilities":3,"chatVisibility":false,"hostNameOverride":""},3790],["MessengerWebRegion",[],{"regionNullable":null},5389],["ZenonApp",[],{"isSocialPlugin":false},8447],["CLDRDateFormatConfig",[],{"supportedPHPFormatsKeys":{"D":"E","D g:ia":"Ejm","D M d":"MMMEd","D M d, Y":"yMMMEd","D M j":"MMMEd","D M j, y":"yMMMEd","D, M j":"MMMEd","D, M j, Y":"yMMMEd","F d":"MMMMd","F d, Y":"date_long","F j":"MMMMd","F j, Y":"date_long","F j, Y \u0040 g:i A":"dateTime_long_short","F j, Y g:i a":"dateTime_long_short","F j, Y \u0040 g:i:s A":"dateTime_long_medium","F jS":"MMMMd","F jS, g:ia":"dateTime_long_short","F jS, Y":"date_long","F Y":"yMMMM","g A":"j","G:i":"time_short","g:i":"time_short","g:i a":"time_short","g:i A":"time_short","g:i:s A":"time_medium","g:ia":"time_short","g:iA":"time_short","g:ia F jS, Y":"dateTime_long_short","g:iA l, F jS":"dateTime_full_short","g:ia M jS":"dateTime_medium_short","g:ia, F jS":"dateTime_long_short","g:iA, l M jS":"dateTime_full_short","h:i a":"time_short","h:m:s m\/d\/Y":"dateTime_short_short","j":"d","j F Y":"date_long","l F d, Y":"date_full","l, F d, Y":"date_full","l, F j":"date_full","l, F j, Y":"date_full","l, F jS":"date_full","l, F jS, g:ia":"dateTime_full_short","l, M j":"date_full","l, M j, Y":"date_full","l, M j, Y g:ia":"dateTime_full_short","M d":"MMMd","M d, Y":"date_medium","M d, Y g:ia":"dateTime_medium_short","M d, Y ga":"dateTime_medium_short","M j":"MMMd","M j, Y":"date_medium","M j, Y g:i A":"dateTime_medium_short","M j, Y g:ia":"dateTime_medium_short","M jS, g:ia":"dateTime_medium_short","M y":"yMMM","M Y":"yMMM","M. d":"MMMd","M. d, Y":"date_medium","m\/d":"Md","m\/d\/Y":"yMd","m\/d\/Y g:ia":"dateTime_short_short","m\/d\/y H:i:s":"dateTime_short_short","n":"M","n\/j":"Md","n\/j, g:ia":"dateTime_short_short","n\/j\/y":"date_short","Y":"y"},"isLocaleInConfigerator":true,"CLDRConfigeratorFormats":{"dateFormats":{"full":"EEEE, MMMM d, y","long":"MMMM d, y","medium":"MMM d, y","short":"M\/d\/yy"},"timeFormats":{"full":"h:mm:ss\u202fa zzzz","long":"h:mm:ss\u202fa z","medium":"h:mm:ss\u202fa","short":"h:mm\u202fa"},"dateTimeFormats":{"full":"{1}, {0}","long":"{1}, {0}","medium":"{1}, {0}","short":"{1}, {0}"},"availableFormats":{"Bh":"h B","Bhm":"h:mm B","Bhms":"h:mm:ss B","E":"ccc","EBhm":"E h:mm B","EBhms":"E h:mm:ss B","EHm":"E HH:mm","EHms":"E HH:mm:ss","Ed":"d E","Ehm":"E h:mm\u202fa","Ehm-alt-ascii":"E h:mm a","Ehms":"E h:mm:ss\u202fa","Ehms-alt-ascii":"E h:mm:ss a","Gy":"y G","GyMMM":"MMM y G","GyMMMEd":"E, MMM d, y G","GyMMMd":"MMM d, y G","GyMd":"M\/d\/y G","H":"HH","Hm":"HH:mm","Hms":"HH:mm:ss","Hmsv":"HH:mm:ss v","Hmv":"HH:mm v","M":"L","MEd":"E, M\/d","MMM":"LLL","MMMEd":"E, MMM d","MMMMW-count-one":"'week' W 'of' MMMM","MMMMW-count-other":"'week' W 'of' MMMM","MMMMd":"MMMM d","MMMd":"MMM d","Md":"M\/d","d":"d","h":"h\u202fa","h-alt-ascii":"h a","hm":"h:mm\u202fa","hm-alt-ascii":"h:mm a","hms":"h:mm:ss\u202fa","hms-alt-ascii":"h:mm:ss a","hmsv":"h:mm:ss\u202fa v","hmsv-alt-ascii":"h:mm:ss a v","hmv":"h:mm\u202fa v","hmv-alt-ascii":"h:mm a v","ms":"mm:ss","y":"y","yM":"M\/y","yMEd":"E, M\/d\/y","yMMM":"MMM y","yMMMEd":"E, MMM d, y","yMMMM":"MMMM y","yMMMd":"MMM d, y","yMd":"M\/d\/y","yQQQ":"QQQ y","yQQQQ":"QQQQ y","yw-count-one":"'week' w 'of' Y","yw-count-other":"'week' w 'of' Y"}},"CLDRRegionalConfigeratorFormats":{"dateFormats":{"full":"EEEE, MMMM d, y","long":"MMMM d, y","medium":"MMM d, y","short":"M\/d\/yy"},"timeFormats":{"full":"h:mm:ss\u202fa zzzz","long":"h:mm:ss\u202fa z","medium":"h:mm:ss\u202fa","short":"h:mm\u202fa"},"dateTimeFormats":{"full":"{1}, {0}","long":"{1}, {0}","medium":"{1}, {0}","short":"{1}, {0}"},"availableFormats":{"Bh":"h B","Bhm":"h:mm B","Bhms":"h:mm:ss B","E":"ccc","EBhm":"E h:mm B","EBhms":"E h:mm:ss B","EHm":"E HH:mm","EHms":"E HH:mm:ss","Ed":"d E","Ehm":"E h:mm\u202fa","Ehm-alt-ascii":"E h:mm a","Ehms":"E h:mm:ss\u202fa","Ehms-alt-ascii":"E h:mm:ss a","Gy":"y G","GyMMM":"MMM y G","GyMMMEd":"E, MMM d, y G","GyMMMd":"MMM d, y G","GyMd":"M\/d\/y G","H":"HH","Hm":"HH:mm","Hms":"HH:mm:ss","Hmsv":"HH:mm:ss v","Hmv":"HH:mm v","M":"L","MEd":"E, M\/d","MMM":"LLL","MMMEd":"E, MMM d","MMMMW-count-one":"'week' W 'of' MMMM","MMMMW-count-other":"'week' W 'of' MMMM","MMMMd":"MMMM d","MMMd":"MMM d","Md":"M\/d","d":"d","h":"h\u202fa","h-alt-ascii":"h a","hm":"h:mm\u202fa","hm-alt-ascii":"h:mm a","hms":"h:mm:ss\u202fa","hms-alt-ascii":"h:mm:ss a","hmsv":"h:mm:ss\u202fa v","hmsv-alt-ascii":"h:mm:ss a v","hmv":"h:mm\u202fa v","hmv-alt-ascii":"h:mm a v","ms":"mm:ss","y":"y","yM":"M\/y","yMEd":"E, M\/d\/y","yMMM":"MMM y","yMMMEd":"E, MMM d, y","yMMMM":"MMMM y","yMMMd":"MMM d, y","yMd":"M\/d\/y","yQQQ":"QQQ y","yQQQQ":"QQQQ y","yw-count-one":"'week' w 'of' Y","yw-count-other":"'week' w 'of' Y"}},"CLDRToPHPSymbolConversion":{"G":"","yyyy":"Y","yy":"y","y":"Y","LLLLL":"M","LLLL":"f","LLL":"M","LL":"m","L":"n","MMMMM":"M","MMMM":"F","MMM":"M","MM":"m","M":"n","dd":"d","d":"j","ccccc":"D","cccc":"l","ccc":"D","cc":"D","c":"D","EEEEE":"D","EEEE":"l","EEE":"D","EE":"D","E":"D","aaaaa":"A","aaaa":"A","aaa":"A","aa":"A","a":"A","bbbbb":"A","bbbb":"A","bbb":"A","bb":"A","b":"A","BBBBB":"A","BBBB":"A","BBB":"A","BB":"A","B":"A","HH":"H","H":"G","hh":"h","h":"g","K":"g","mm":"i","m":"i","ss":"s","s":"s","z":"","zz":"","zzz":""},"intlDateSpecialChars":{"cldrDelimiter":"'","singleQuote":"'","singleQuoteHolder":"*"}},3019],["IsInternSite",[],{"is_intern_site":false},4517],["MarauderConfig",[],{"app_version":"1.0.0.0 (1031920881)","gk_enabled":false},31],["RTISubscriptionManagerConfig",[],{"config":{},"autobot":{},"assimilator":{},"unsubscribe_release":true,"bladerunner_www_sandbox":null,"is_intern":false},1081],["RequestStreamE2EClientSamplingConfig",[],{"sampleRate":500000,"methodToSamplingMultiplier":{"RTCSessionMessage":10000,"Presence":0.01,"FBGQLS:VOD_TICKER_SUBSCRIBE":0.01,"FBGQLS:STORIES_TRAY_SUBSCRIBE":100,"Collabri":0.1,"FBGQLS:WORK_AVAILABILITY_STATUS_FANOUT_SUBSCRIBE":0.1,"FBGQLS:GROUP_UNSEEN_ACTIVITY_SUBSCRIBE":0.1,"FBGQLS:GROUP_RESET_UNSEEN_ACTIVITY_SUBSCRIBE":0.1,"FBGQLS:INTERN_CALENDAR_UPDATE_SUBSCRIBE":0.1,"SKY:gizmo_manage":10000,"FBGQLS:XFB_HZW_CHALLENGE_COMPLETE_SUBSCRIBE":10,"FalcoMobile":1,"FBGQLS:HUDDLE_USERS_REQUESTED_TO_SPEAK_COUNT_SUBSCRIBE":1000,"FBGQLS:FEEDBACK_LIKE_SUBSCRIBE":1}},4501],["DGWWebConfig",[],{"appId":"936619743392459","appVersion":"0","dgwVersion":"2","endpoint":"","fbId":"0","authType":""},5508],["WebDevicePerfInfoData",[],{"needsFullUpdate":true,"needsPartialUpdate":false,"shouldLogResourcePerf":false},3977],["WebStorageMonsterLoggingURI",[],{"uri":null},3032],["cr:9977",[],{"__rc":[null,null]},-1],["cr:12495",[],{"__rc":[null,null]},-1],["cr:8572",["RpWebStateMachineLoggingBlocklistJSModuleWrapper"],{"__rc":["RpWebStateMachineLoggingBlocklistJSModuleWrapper",null]},-1],["cr:17347",["ZenonMQTTTransportChannelStatus"],{"__rc":["ZenonMQTTTransportChannelStatus","Aa5WvA6_f2FoHZacVhotv1ggqK6ErsFdiciIx0ehm96zboBNwvRivgqX64e3AJjS61zHJsR0bNWrZMhewzK-uk_2WJVh7yfAMCR-Za0ojn_IPvR_L3OpjFfcaQ"]},-1],["cr:4031",["MWPHandleNativeTaskBatched"],{"__rc":["MWPHandleNativeTaskBatched",null]},-1],["cr:6668",[],{"__rc":[null,null]},-1],["cr:567",["SaharaCometConsentFlowContextualConsentFallbackLoadingStateIGDS.react"],{"__rc":["SaharaCometConsentFlowContextualConsentFallbackLoadingStateIGDS.react",null]},-1],["cr:8666",["FDSListCellImpl_Old.react"],{"__rc":["FDSListCellImpl_Old.react",null]},-1],["cr:10389",["MDSGlimmerImpl.react"],{"__rc":["MDSGlimmerImpl.react",null]},-1],["cr:12310",["FXFetaMigrationMomentPromptDialogRootQuery$Parameters.instagram"],{"__rc":["FXFetaMigrationMomentPromptDialogRootQuery$Parameters.instagram",null]},-1],["cr:18509",["FXFetaPreMigrationDialogRootQuery$Parameters.instagram"],{"__rc":["FXFetaPreMigrationDialogRootQuery$Parameters.instagram",null]},-1],["cr:18511",["FXFetaToSDialogRootQuery$Parameters.instagram"],{"__rc":["FXFetaToSDialogRootQuery$Parameters.instagram",null]},-1],["QPLMsgTypesSitevarConfig",[],{"QPL_MSG_TYPES":["join","server_media_update","client_media_update","ring"]},6908],["ZenonPlatformRateLimitSitevarConfig",[],{"default":{"bucket_size":10,"refill_rate":5},"buckets":{"__map":[]}},6146],["RpWebMqttEnabledAppIds",[],{"APP_IDS":[2220391788200892,772021112871879,1586666294789976,424940172743869,436761779744620,514771569228061,1358015658191005,1581645579298526,949958857019662,1971595283112096]},6874],["ZenonSignalingSharedWorkerV2Resource",["__inst_e935a41e_0_0_89"],{"name":"ZenonSignalingSharedWorkerV2Bundle","v2HasteResponsePreloader":{"__m":"__inst_e935a41e_0_0_89"}},8632],["RpZenonBinaryThriftSignalingSitevarConfig",[],{"supported_message_types_mqtt":["JOIN","SERVER_MEDIA_UPDATE","HANGUP","ICE_CANDIDATE","RING","DISMISS","CONFERENCE_STATE","ADD_PARTICIPANTS","SUBSCRIPTION","CLIENT_MEDIA_UPDATE","DATA_MESSAGE","REMOVE_PARTICIPANTS","PING","UPDATE","NOTIFY","CLIENT_EVENT","UNSUBSCRIBE","APPROVAL","WAKEUP"],"inbound_supported_message_types_mqtt":["JOIN","SERVER_MEDIA_UPDATE","HANGUP","ICE_CANDIDATE","RING","DISMISS","CONFERENCE_STATE","ADD_PARTICIPANTS","SUBSCRIPTION","CLIENT_MEDIA_UPDATE","DATA_MESSAGE","REMOVE_PARTICIPANTS","PING","UPDATE","NOTIFY","CLIENT_EVENT","UNSUBSCRIBE","APPROVAL","WAKEUP"]},7272],["RoboticsPermission",[],{"is_authorized_robot":false},3486],["IGDAWMainWebWorkerResource",["__inst_e935a41e_0_1_zN"],{"name":"IGDAWMainWebWorkerBundle","v2HasteResponsePreloader":{"__m":"__inst_e935a41e_0_1_zN"}},6144],["CometDarkModeSetting",[],{"initialGuessForDarkModeOnClient":false,"initialClientStateGuess":false,"initialSetting":"UNDECLARED"},4414],["BDSignalCollectionData",[],{"sc":"{\"t\":1768294102,\"c\":[[30000,838801],[30001,838801],[30002,838801],[30003,838801],[30004,838801],[30005,838801],[30006,573585],[30007,838801],[30008,838801],[30012,838801],[30013,838801],[30015,806033],[30018,806033],[30021,540823],[30022,540817],[30040,806033],[30093,806033],[30094,806033],[30095,806033],[30101,541591],[30102,541591],[30103,541591],[30104,541591],[30106,806039],[30107,806039],[38000,541427],[38001,806643]]}","fds":60,"fda":60,"i":60,"sbs":1,"dbs":100,"bbs":100,"hbi":60,"rt":262144,"hbcbc":2,"hbvbc":0,"hbbi":30,"sid":-1,"hbv":"8735906576985231549"},5239],["cr:1012418",["CometRelay"],{"__rc":["CometRelay",null]},-1],["cr:8018",[],{"__rc":[null,null]},-1],["cr:6551",["IGDBridgedAPI"],{"__rc":["IGDBridgedAPI",null]},-1],["RpWebStateMachineLoggingBlocklist",[],{"EVENT_TYPES":["xstate.init","receiveStateSyncNotifyRequest","receiveGenericDataMessageRequest","sendIceCandidateRequest","dataChannelMessageReceived","dataMessageReceived","receivePingResponse","receiveOverlayConfigServerUpdateRequest","receiveClientInfoRequest","sendClientEventRequest","receiveRoomContextUpdateRequest","sendGenericDataMessageRequest","capabilitiesReceived","receiveCapabilitiesRequest","createDataMessageSubscription","removeDataMessageSubscription","clientInfoReceived","connectionRoomUpdateReceived","iceCandidateReady","messageSent"],"STATES":["terminated","terminating"],"MESSAGE_TYPES":["DATA_MESSAGE","NOTIFY","ICE_CANDIDATE","UPDATE","PING"]},6230],["YouthRegulationConfig",[],{"config":{"consent_jurisdiction":"KR","should_raise_age_gating":false,"age_of_consent":16,"requires_age_verification":false,"requires_parental_consent":false,"should_block_registration":false,"age_threshold_for_reg_blocking":null}},7506]],"instances":[["__inst_e935a41e_0_0_89",["AsyncDataPreloader"],[{"id":"adp_WebWorkerV2HasteResponsePreloader_ZenonSignalingSharedWorkerV2Bundle_696606d7525865a59655802"}],1],["__inst_e935a41e_0_1_zN",["AsyncDataPreloader"],[{"id":"adp_WebWorkerV2HasteResponsePreloader_IGDAWMainWebWorkerBundle_696606d75264c5e84010762"}],1]],"require":[["ODS"],["PolarisNotificationsNavBadge.react"],["IGDPageSetup.react"],["PolarisGlobalUIComponents.react"],["XAsyncRequest"],["InstagramODSImpl"],["ContextualConfig"],["PolarisLogger"],["BladeRunnerClient"],["CometToast.react"],["IGCoreModal.react"],["bumpVultureJSHash"],["FbtLogging"],["PolarisNotificationsNavBannerWrapper.react"],["DGWRequestStreamClient"],["IntlQtEventFalcoEvent"],["CometRelayEF"],["PolarisFBSDK"],["PolarisLogPushNotification"],["PolarisPerformanceLogger"],["IGDSPrivateToaster.react"],["PolarisBackgroundFeedDataFetchEager"],["polarisDebugLogODS"],["WebDevicePerfInfoLogging"],["PolarisInitWindowsPWAKeyCommand"],["CometPixelRatioUpdater"],["CometChromeDome"],["vulture"],["CometBrowserDimensionsLogger"],["CometOnBeforeUnloadDialog.react"],["ClientConsistencyFalcoEvent"],["CometRootDeferredShared"],["FalcoLoggerTransports"],["LSVoprfWasm"],["PolarisUnfollowDialog.react"],["PolarisCommentCover.react"],["PolarisUnfollowDialog.next.react"],["VideoPlayerWithLiveVideoInterruptedOverlay.react"],["PolarisPostBoostButton.react"],["KF2Loader"],["emptyFunction","thatReturns",["RequireDeferredReference"],[[{"__dr":"ODS"},{"__dr":"PolarisNotificationsNavBadge.react"},{"__dr":"IGDPageSetup.react"},{"__dr":"PolarisGlobalUIComponents.react"},{"__dr":"XAsyncRequest"},{"__dr":"InstagramODSImpl"},{"__dr":"ContextualConfig"},{"__dr":"PolarisLogger"},{"__dr":"BladeRunnerClient"},{"__dr":"CometToast.react"},{"__dr":"IGCoreModal.react"},{"__dr":"bumpVultureJSHash"},{"__dr":"FbtLogging"},{"__dr":"PolarisNotificationsNavBannerWrapper.react"},{"__dr":"DGWRequestStreamClient"},{"__dr":"IntlQtEventFalcoEvent"},{"__dr":"CrosspostControlsFalcoEvent"},{"__dr":"CometRelayEF"},{"__dr":"PolarisSwitchAppearancePushPage.react"},{"__dr":"BizSuiteCoreGrowthInstagramWebEntryPointClickFalcoEvent"},{"__dr":"BizSuiteCoreGrowthInstagramWebEntryPointImpressionFalcoEvent"},{"__dr":"PolarisFBSDK"},{"__dr":"PolarisLogPushNotification"},{"__dr":"PolarisPerformanceLogger"},{"__dr":"IGDSPrivateToaster.react"},{"__dr":"PolarisBackgroundFeedDataFetchEager"},{"__dr":"polarisDebugLogODS"},{"__dr":"WebDevicePerfInfoLogging"},{"__dr":"PolarisInitWindowsPWAKeyCommand"},{"__dr":"CometPixelRatioUpdater"},{"__dr":"CometChromeDome"},{"__dr":"vulture"},{"__dr":"CometBrowserDimensionsLogger"},{"__dr":"CometOnBeforeUnloadDialog.react"},{"__dr":"ClientConsistencyFalcoEvent"},{"__dr":"CometRootDeferredShared"},{"__dr":"PolarisCreationModalComposeCaptionLexicalInput.react"},{"__dr":"FalcoLoggerTransports"},{"__dr":"LSVoprfWasm"},{"__dr":"PolarisUnfollowDialog.react"},{"__dr":"PolarisCommentCover.react"},{"__dr":"PolarisUnfollowDialog.next.react"},{"__dr":"VideoPlayerWithLiveVideoInterruptedOverlay.react"},{"__dr":"MLCInstrumentationPlugin__INTERNAL.react"},{"__dr":"PolarisDirectMQTT"},{"__dr":"IGDAlertDialog.react"},{"__dr":"DirectComposeSelectRecipientFalcoEvent"},{"__dr":"ExternalShareSucceededFalcoEvent"},{"__dr":"ExternalShareOptionImpressionFalcoEvent"},{"__dr":"ShareSheetImpressionFalcoEvent"},{"__dr":"ExternalShareOptionTappedFalcoEvent"},{"__dr":"BillingWebWizardLoadingState.react"},{"__dr":"BillingWizardRootUPLogger"},{"__dr":"BillingWizardCustomerBehaviorLogger"},{"__dr":"BillingPolarisWizardRootLoader.react"},{"__dr":"BillingWizardXMDSDialog.react"},{"__dr":"BillingPolarisPaymentAccountID"},{"__dr":"BillingMobileWizardXMDSLoadingState.react"},{"__dr":"PolarisPostBoostButton.react"},{"__dr":"KF2Loader"}]]],["CometPlatformRootClient","setInitDeferredPayload",[],[{"sketchInfo":null,"userID":0,"deferredCookies":{"_js_ig_did":{"value":"50A072DD-2812-4C1E-AED7-71FC37E5BD0E","expiration_for_js":31536000000,"expiration_for_http":1799830102,"path":"\/","domain":".instagram.com","secure":true,"http_only":true,"first_party_only":true,"add_js_prefix":true,"same_site":"None"},"_js_datr":{"value":"1gZmaTwcxLLZJp06udt8VUzw","expiration_for_js":34560000000,"expiration_for_http":1802854102,"path":"\/","domain":".instagram.com","secure":true,"http_only":true,"first_party_only":true,"add_js_prefix":true,"same_site":"None"},"mid":{"value":"aWYG1wAEAAGazyofn4357-1WXtdJ","expiration_for_js":34560000000,"expiration_for_http":1802854102,"path":"\/","domain":".instagram.com","secure":true,"http_only":true,"first_party_only":false,"add_js_prefix":false,"same_site":"None"}},"blLoggingCavalryFields":{"bl_sample_rate":0,"hr_sample_rate":0,"parent_lid":"7594765338937293050"}}]],["MAWMainThreadLogger"],["MAWWebWorkerSingleton"],["CometRelayEnvironment"],["LSPlatformSyncSystem"],["hasDefaultThreadOneToOneCapability"],["LSDataTraceFlush"],["MqttLongPollingRunner"],["EncryptedBackupUploadFailureFalcoEvent"],["EncryptedBackupUploadSuccessFalcoEvent"],["sendToSentQPLLogger"],["IGDInboxErrorState.react"],["MAWThreadConsistencyLogger"],["MAWBridgeObserver"],["EBIsEbEnabledSubscriber"],["EBWriteMinosMailboxKeysToCache"],["EBMinosVerifySingleEpoch"],["PersistedQueue"],["ZenonCallWindowController"],["ZenonCallInviteModel"],["ZenonParentCallsManager"],["RTWebCallWindowOpener"],["delegateZenonCallInviteModel"],["Chromedome"],["LogWebQplNOP"],["ristretto255"],["LSDatascriptEvaluator"],["LSPlatformClient"],["XMDSToast.react"],["XMDSTooltipDeferredImpl.react"],["IgSignalingListener"],["Bootloader","markComponentsAsImmediate",[],[["MAWWaitForBackendSetup","IGCallUriBuilder","IGDSPro2ProDialog.react","PolarisBoostMusicErrorDialog.react","PolarisBoostNotDeliveringDialog.react","ZenonSharedWorkerProxyMessageSender","setE2eeIsMandatedForZenonLoggers","SharedWorkerBundleResource","ZenonGraphQLMWThriftMessageSender","ZenonDGWStreamController","ZenonDGWMWThriftMessageSender","publishLSPlatformDeidentifiedPayload","VideoPlayerHTML5ApiCea608State","VideoPlayerHTML5ApiWebVttState","LSLocalize"]]],["RequireDeferredReference","unblock",[],[["ODS","PolarisNotificationsNavBadge.react","IGDPageSetup.react","PolarisGlobalUIComponents.react","XAsyncRequest","InstagramODSImpl","ContextualConfig","PolarisLogger","BladeRunnerClient","CometToast.react","IGCoreModal.react","bumpVultureJSHash","FbtLogging","PolarisNotificationsNavBannerWrapper.react","DGWRequestStreamClient","IntlQtEventFalcoEvent","CrosspostControlsFalcoEvent","CometRelayEF","PolarisSwitchAppearancePushPage.react","BizSuiteCoreGrowthInstagramWebEntryPointClickFalcoEvent","BizSuiteCoreGrowthInstagramWebEntryPointImpressionFalcoEvent","PolarisFBSDK","PolarisLogPushNotification","PolarisPerformanceLogger","IGDSPrivateToaster.react","PolarisBackgroundFeedDataFetchEager","polarisDebugLogODS","WebDevicePerfInfoLogging","PolarisInitWindowsPWAKeyCommand","CometPixelRatioUpdater","CometChromeDome","vulture","CometBrowserDimensionsLogger","CometOnBeforeUnloadDialog.react","ClientConsistencyFalcoEvent","CometRootDeferredShared","PolarisCreationModalComposeCaptionLexicalInput.react","FalcoLoggerTransports","LSVoprfWasm","PolarisUnfollowDialog.react","PolarisCommentCover.react","PolarisUnfollowDialog.next.react","VideoPlayerWithLiveVideoInterruptedOverlay.react","MLCInstrumentationPlugin__INTERNAL.react","PolarisDirectMQTT","IGDAlertDialog.react","DirectComposeSelectRecipientFalcoEvent","ExternalShareSucceededFalcoEvent","ExternalShareOptionImpressionFalcoEvent","ShareSheetImpressionFalcoEvent","ExternalShareOptionTappedFalcoEvent","BillingWebWizardLoadingState.react","BillingWizardRootUPLogger","BillingWizardCustomerBehaviorLogger","BillingPolarisWizardRootLoader.react","BillingWizardXMDSDialog.react","BillingPolarisPaymentAccountID","BillingMobileWizardXMDSLoadingState.react","PolarisPostBoostButton.react","KF2Loader","MAWMainThreadLogger","MAWWebWorkerSingleton","CometRelayEnvironment","LSPlatformSyncSystem","hasDefaultThreadOneToOneCapability","LSDataTraceFlush","MqttLongPollingRunner","EncryptedBackupUploadFailureFalcoEvent","EncryptedBackupUploadSuccessFalcoEvent","sendToSentQPLLogger","IGDInboxErrorState.react","MAWThreadConsistencyLogger","MAWBridgeObserver","EBIsEbEnabledSubscriber","EBWriteMinosMailboxKeysToCache","EBMinosVerifySingleEpoch","PersistedQueue","GetLsDatabase","ZenonCallWindowController","ZenonCallInviteModel","ZenonParentCallsManager","RTWebCallWindowOpener","delegateZenonCallInviteModel","CometExceptionDialog.react","Chromedome","FDSTooltipDeferredImpl.react","TransportSelectingClientSingletonConditional","BillingBuildCommitMutation","BillingBuildFetchQuery","LogWebQplNOP","ristretto255","LSDatascriptEvaluator","LSPlatformClient","XMDSToast.react","CometTooltipDeferredImpl.react","VideoPlayerSpinner.react","VideoPlayerCaptionsArea.react","XMDSTooltipDeferredImpl.react","IgSignalingListener"],"sd"]],["RequireDeferredReference","unblock",[],[["ODS","PolarisNotificationsNavBadge.react","IGDPageSetup.react","PolarisGlobalUIComponents.react","XAsyncRequest","InstagramODSImpl","ContextualConfig","PolarisLogger","BladeRunnerClient","CometToast.react","IGCoreModal.react","bumpVultureJSHash","FbtLogging","PolarisNotificationsNavBannerWrapper.react","DGWRequestStreamClient","IntlQtEventFalcoEvent","CometRelayEF","PolarisFBSDK","PolarisLogPushNotification","PolarisPerformanceLogger","IGDSPrivateToaster.react","PolarisBackgroundFeedDataFetchEager","polarisDebugLogODS","WebDevicePerfInfoLogging","PolarisInitWindowsPWAKeyCommand","CometPixelRatioUpdater","CometChromeDome","vulture","CometBrowserDimensionsLogger","CometOnBeforeUnloadDialog.react","ClientConsistencyFalcoEvent","CometRootDeferredShared","FalcoLoggerTransports","LSVoprfWasm","PolarisUnfollowDialog.react","PolarisCommentCover.react","PolarisUnfollowDialog.next.react","VideoPlayerWithLiveVideoInterruptedOverlay.react","PolarisPostBoostButton.react","KF2Loader","MAWMainThreadLogger","MAWWebWorkerSingleton","CometRelayEnvironment","LSPlatformSyncSystem","hasDefaultThreadOneToOneCapability","LSDataTraceFlush","MqttLongPollingRunner","EncryptedBackupUploadFailureFalcoEvent","EncryptedBackupUploadSuccessFalcoEvent","sendToSentQPLLogger","IGDInboxErrorState.react","MAWThreadConsistencyLogger","MAWBridgeObserver","EBIsEbEnabledSubscriber","EBWriteMinosMailboxKeysToCache","EBMinosVerifySingleEpoch","PersistedQueue","GetLsDatabase","ZenonCallWindowController","ZenonCallInviteModel","ZenonParentCallsManager","RTWebCallWindowOpener","delegateZenonCallInviteModel","CometExceptionDialog.react","Chromedome","FDSTooltipDeferredImpl.react","TransportSelectingClientSingletonConditional","LogWebQplNOP","ristretto255","LSDatascriptEvaluator","LSPlatformClient","XMDSToast.react","CometTooltipDeferredImpl.react","VideoPlayerSpinner.react","VideoPlayerCaptionsArea.react","XMDSTooltipDeferredImpl.react","IgSignalingListener"],"css"]],["Deferred | 2026-01-13T08:48:30 |
https://developer.x.com/developer-terms/policy#2-a | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://developer.x.com/developer-terms/policy#1-b | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:30 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#main-content | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:30 |
https://opensource.org/about | About – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home About About the Open Source Initiative As steward of the Open Source Definition , we set the foundation for the open source software ecosystem. The Open Source Initiative (OSI) is a California public benefit corporation, with 501(c)3 tax-exempt status, founded in 1998. We are also actively involved in Open Source community-building, education, and public advocacy to promote awareness and the importance of non-proprietary software. OSI participates in Open Source conferences and events, to meet with open source developers and users, and to discuss with executives from the public and private sectors about how Open Source technologies, licenses, and models of development can provide economic and strategic advantages. Vision As the leading voice on the policies and principles of open source, the OSI helps build a world where the freedoms and opportunities of open source software can be enjoyed by all. The OSI supports institutions and individuals working together to create communities of practice in which the healthy open source ecosystem thrives. Mission The Open Source Initiative (OSI) is a non-profit corporation with global scope formed to educate about and advocate for the benefits of open source and to build bridges among different constituencies in the open source community. Open source enables a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is higher quality, better reliability, greater flexibility, lower cost, and an end to predatory vendor lock-in. One of our most important activities is as a standards body, maintaining the Open Source Definition for the good of the community. The Open Source Initiative Approved License trademark and program creates a nexus of trust around which developers, users, corporations and governments can organize open source cooperation. Contact Please contact the OSI if you are interested in having us help you develop, arrange, or conduct educational conferences, programs, courses of instruction, and/or online educational seminars relating to Open Source (non-proprietary) software. Our website has a contact form that can be used to reach us over the internet , or we can be contacted at our mailing address: Open Source Initiative 8605 Santa Monica Blvd PMB 63639 West Hollywood, CA 90069-4109 United States The Open Source Initiative’s IRS Tax ID Number (TIN) is 91-2037395. The Open Source Initiative’s EU Transparency Register Number 672028337929-77 In this Section: Board Staff Associations History International Authority & Recognition Trademark & Logo Page created on September 19, 2006 | Last modified on October 21, 2025 Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:30 |
https://stackoverflow.blog/data-science/ | data science - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. data science Related Tags AI data Code for a Living machine learning codecademy statistics Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed August 29, 2025 Open-source is for the people, by the people Travis Oliphant, creator of NumPy and SciPy, joins Ryan to explore the development of Python as a data science tool, the evolution of these foundational libraries, and the importance of community and collaboration in open-source projects, including Travis’ current work to support sustainable open-source through the OpenTeams Incubator. Phoebe Sajor 1 comment The Stack Overflow Podcast python data science Open Source May 9, 2025 Using AI to find patient zero in marketing campaigns Ben Popper chats with CTO Abby Kearns about how Alembic is using composite AI and lessons learned from contract tracing and epidemiology to help companies map customer journeys and understand the ROI of their marketing spend. Ben and Abby also talk about where open-source models have the edge and the challenges startups face in building trust with big companies and securing the resources they need to grow. Eira May 0 comment s The Stack Overflow Podcast AI Open Source startups data data science April 3, 2025 From training to inference: The new role of web data in LLMs Data has always been key to LLM success, but it's becoming key to inference-time performance as well. Or Lenchner 4 comment s data science generative AI data contributed April 2, 2025 Not all AI is generative: Efficient scheduling with mathematics Efficiently solving a complex scheduling problem using simulated annealing. Subbu Sailappan , Sidharth Kumar 2 comment s Sponsored Partner Content data science AI April 5, 2024 What a year building AI has taught Stack Overflow We sit down with Jessica Clark, a senior data scientist at Stack Overflow, to discuss how our company approaches generative AI and data quality. Ben Popper 0 comment s The Stack Overflow Podcast generative AI data science April 3, 2023 "Data driven" decisions aren't innovative decisions If you want to innovate new solutions, you can't rely on data about existing solutions. Chelsea Troy 2 comment s Code for a Living data science software development February 24, 2023 ML and AI consulting-as-a-service (Ep. 542) The home team talks with Jaclyn Rice Nelson, cofounder and CEO of Tribe AI, about the explosion of hype surrounding generative AI, what it’s like to work at a startup after working at Google, and how Tribe is leveraging the power of a specialist network. Eira May 0 comment s AI data science Engineering machine learning ML the stack overflow podcast The Stack Overflow Podcast tribe ai March 3, 2022 Stop aggregating away the signal in your data By aggregating our data in an effort to simplify it, we lose the signal and the context we need to make sense of what we’re seeing. Zan Armstrong 9 comment s Code for a Living data science visualization contributed January 12, 2022 Podcast 406: Making Agile work for data science Data scientists and engineers don’t always play well together. We discuss an approach to your tech stack that can bring them together. Ryan Donovan 0 comment s agile data science The Stack Overflow Podcast the stack overflow podcast December 30, 2021 How often do people actually copy and paste from Stack Overflow? Now we know. April Fool's may be over, but once we set up a system to react every time someone typed Command+C, we realized there was also an opportunity to learn about how people use our site. Here’s what we found. Ben Popper , David Gibson 101 comment s april fools Community copying code data science Insights November 15, 2021 Building a QA process for your deep learning pipeline in practice Deep learning models still need testing, but many of the common testing approaches don't apply. But with the right methods, you can still make sure your pipeline produces good results. Tobias Kupek 1 comment Code for a Living data science data testing machine learning testing September 13, 2021 Why your data needs a QA process At this point, most software engineers see the value of testing their software regularly. But are you testing your data engineering as well? Corissa E Haury 4 comment s Code for a Living data data science data testing March 9, 2021 Level Up: Mastering statistics with Python - part 5 Rather than dig into complex math or over-simplify by using a pre-written function, we'll write our own binomial test function, primarily using base Python. In the process, we'll learn more about how hypothesis testing works and build intuition for how to interpret a p-value. Ben Popper , Sophie Sommer 0 comment s Code for a Living codecademy data science level up python statistics February 23, 2021 Level Up: Mastering statistics with Python - part 2 Investigate a dataset with summary statistics and some basic data visualizations using the Python libraries NumPy, pandas, matplotlib, and Seaborn. Ben Popper , Sophie Sommer 0 comment s Code for a Living codecademy data science Engineering statistics February 16, 2021 Level Up: Mastering statistics with Python In today’s tech industry, statistics and data science are becoming increasingly important and valuable skills. Ben Popper 5 comment s Code for a Living codecademy data science education learning to code statistics October 12, 2020 How to put machine learning models into production The goal of building a machine learning model is to solve a problem, and a machine learning model can only do so when it is in production and actively in use by consumers. As such, model deployment is as important as model building. Rising Odegua 16 comment s Code for a Living data science machine learning tensorflow August 8, 2019 DEF CON and Stack Overflow: What Our Traffic Says About Cybersecurity Technologies Stack Overflow traffic during DEF CON shows what technologies are trending in the hacker community Julia Silge 10 comment s Announcements Bulletin cybersecurity data data science def con Insights Stackoverflow Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:30 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.