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://www.forem.com/t/beginners | Beginners - 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 DEV Community Close Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 1 2 3 4 5 6 7 8 9 … 75 … 3379 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Readiness probe Khadijah (Dana Ordalina) Khadijah (Dana Ordalina) Khadijah (Dana Ordalina) Follow Jan 13 Readiness probe # aws # kubernetes # beginners # devops Comments Add Comment 1 min read Why My First Animation Blueprint Didn’t Work in Unreal Engine Dinesh Dinesh Dinesh Follow Jan 11 Why My First Animation Blueprint Didn’t Work in Unreal Engine # gamedev # unrealengine # beginners # animation Comments Add Comment 2 min read I Fired the "One-Click" AI Builders: How I Built a React Portfolio with Gemini (Without Knowing React) Aaditya Thakur Aaditya Thakur Aaditya Thakur Follow Jan 13 I Fired the "One-Click" AI Builders: How I Built a React Portfolio with Gemini (Without Knowing React) # ai # webdev # career # beginners Comments Add Comment 3 min read 7 Small Workflow Tweaks That Actually Helped My Developer Productivity Johannes Millan Johannes Millan Johannes Millan Follow Jan 12 7 Small Workflow Tweaks That Actually Helped My Developer Productivity # productivity # beginners # career # programming 5 reactions Comments 1 comment 2 min read 10 Secret Tips That Make You Better at DSA Akash Pattnaik Akash Pattnaik Akash Pattnaik Follow Jan 12 10 Secret Tips That Make You Better at DSA # productivity # programming # beginners # algorithms 1 reaction Comments Add Comment 3 min read Upskilling in AI: Unconventional Prompt Use Brandon Skinner Brandon Skinner Brandon Skinner Follow Jan 11 Upskilling in AI: Unconventional Prompt Use # ai # beginners Comments Add Comment 5 min read From Docker Errors to Production-Ready: Building a PHP Microservices CI/CD Pipeline Alan Varghese Alan Varghese Alan Varghese Follow Jan 13 From Docker Errors to Production-Ready: Building a PHP Microservices CI/CD Pipeline # webdev # devops # php # beginners Comments Add Comment 4 min read The `/context` Command: X-Ray Vision for Your Tokens Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 12 The `/context` Command: X-Ray Vision for Your Tokens # tutorial # claudecode # productivity # beginners Comments Add Comment 4 min read Lumina — Where Blogs Meet AI Mayank Parashar Mayank Parashar Mayank Parashar Follow Jan 12 Lumina — Where Blogs Meet AI # webdev # programming # ai # beginners 14 reactions Comments 5 comments 2 min read Setting Up Jenkins SSH Build Agents: A Complete Troubleshooting Guide Faruq2991 Faruq2991 Faruq2991 Follow Jan 10 Setting Up Jenkins SSH Build Agents: A Complete Troubleshooting Guide # beginners # devops # cloud # cloudcomputing 2 reactions Comments Add Comment 8 min read AI for operations: remove friction, not people Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Jan 12 AI for operations: remove friction, not people # webdev # ai # beginners # productivity 16 reactions Comments 1 comment 2 min read What I Shipped Today: Evidence-Based AI Answers for Database Schemas Rushikesh Bodakhe Rushikesh Bodakhe Rushikesh Bodakhe Follow Jan 12 What I Shipped Today: Evidence-Based AI Answers for Database Schemas # webdev # programming # ai # beginners 1 reaction Comments Add Comment 2 min read perceptron - day 01 of dl Mahraib Fatima Mahraib Fatima Mahraib Fatima Follow Jan 12 perceptron - day 01 of dl # ai # beginners # deeplearning # machinelearning 1 reaction Comments Add Comment 2 min read A Mnemonic That Finally Makes for…in vs for…of Stick Mahlon Gumbs Mahlon Gumbs Mahlon Gumbs Follow Jan 12 A Mnemonic That Finally Makes for…in vs for…of Stick # javascript # webdev # programming # beginners Comments Add Comment 2 min read How to ask awesome questions as a dev (Without Dying of Imposter Syndrome) Ishika-jain Ishika-jain Ishika-jain Follow Jan 12 How to ask awesome questions as a dev (Without Dying of Imposter Syndrome) # beginners # mentalhealth # productivity Comments Add Comment 4 min read Load Balancing a Simple Static Site with Docker and Nginx: A Beginner's Journey Niraj Maharjan Niraj Maharjan Niraj Maharjan Follow Jan 12 Load Balancing a Simple Static Site with Docker and Nginx: A Beginner's Journey # docker # nginx # loadbalance # beginners Comments Add Comment 11 min read Find All Duplicate Elements in an Array (C++) Nithya Dharshini official Nithya Dharshini official Nithya Dharshini official Follow Jan 12 Find All Duplicate Elements in an Array (C++) # programming # beginners # tutorial # cpp 1 reaction Comments Add Comment 1 min read var, let, const: Why JavaScript Needed Three Ways to Declare Variables Razumovsky Razumovsky Razumovsky Follow Jan 11 var, let, const: Why JavaScript Needed Three Ways to Declare Variables # webdev # beginners # javascript # tutorial Comments Add Comment 7 min read learning complex coding Masood Ahmad Masood Ahmad Masood Ahmad Follow Jan 13 learning complex coding # programming # webdev # ai # beginners Comments Add Comment 1 min read Smart Contract Security 101 — Reentrancy & Common AI‑Generated Mistakes Ribhav Ribhav Ribhav Follow Jan 12 Smart Contract Security 101 — Reentrancy & Common AI‑Generated Mistakes # security # crypto # blockchain # beginners Comments Add Comment 5 min read Building Interactive Data Tables with React Data Grid Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Interactive Data Tables with React Data Grid # react # webdev # beginners # tutorial Comments Add Comment 7 min read My Journey Into Cybersecurity: A Beginner’s Guide The Duchess of Hackers The Duchess of Hackers The Duchess of Hackers Follow Jan 12 My Journey Into Cybersecurity: A Beginner’s Guide # cybersecurity # beginners # learning # mattermost 6 reactions Comments Add Comment 2 min read Clean Code Is a Communication Tool, Not a Style Preference Shamim Ali Shamim Ali Shamim Ali Follow Jan 12 Clean Code Is a Communication Tool, Not a Style Preference # programming # beginners # productivity # coding Comments Add Comment 1 min read Why I Build macOS Menu Bar Apps heocoi heocoi heocoi Follow Jan 12 Why I Build macOS Menu Bar Apps # beginners # learning 1 reaction Comments 1 comment 3 min read How to Think About Games: Unity OP-Bright OP-Bright OP-Bright Follow Jan 12 How to Think About Games: Unity # beginners # design # gamedev Comments Add Comment 6 min read loading... trending guides/resources The Vibe Coding Paradox An Honest Review of Google Antigravity 5 YouTube Channels Every Programmer Should Follow in 2025! I Built a Desktop App That Commits to GitHub So I Don’t Have To Lie About Consistency DevOps From Scratch: A Student’s Diary (Entry #00) The Night Kubernetes Almost Made Me Quit DevOps Forever How I Built a Graphics Renderer for Node.js Web Development Is Meant to Be Built, Not Watched Understanding Kubernetes: part 60 – Kubernetes 1.35 Changelog I Stopped Chasing Features and Started Designing Systems Yes, true + true === 2. And No, JavaScript Isn’t Broken How to Become an AWS Community Builder Gemini 3 vs GPT-5.2: Detailed Coding Comparison What happens when you type console.log()? Optimizing JSON for LLMs Rust Lifetimes Explained Extensões para VSCode When React Starts Acting Like jQuery (and You Can Totally Tell 😅) Navigating the Switch: How to Choose the Right Linux Distro in 2026 The Developer's Safety Net - Introduction to TypeScript 💎 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:22 |
https://www.suprsend.com/post/how-to-streamline-in-product-communication-with-suprsends-in-app-notification-center | How to Streamline In-Product Communication with SuprSend’s In-App Notification Center? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Inapp Inbox Notifications How to Streamline In-Product Communication with SuprSend’s In-App Notification Center? Nikita Navral • October 26, 2024 TABLE OF CONTENTS The challenge of maintaining effective communication within applications has become increasingly complex. Recognizing this, the in-app notification center emerges as a transformative solution, reshaping the user experience by centralizing and streamlining in-app communication. This comprehensive exploration delves into the multifaceted aspects of in-app inbox notification center integration, drawing inspiration from successful implementations and providing actionable insights for seamless adoption. I. The Notification Overload Users find themselves grappling with a multitude of notifications each vying for attention through disparate channels. The fragmented nature of these alerts often leaves users overwhelmed, susceptible to missing crucial information, and at risk of disengagement. You should also check Maintaining Notification Center Hygiene - Expiring Outdated Messages in The InApp Inbox Notification Center Fragmented Channels : Push, SMS, email— each demanding attention at different times. Risk of Information Loss: Crucial updates may go unnoticed as users struggle to sift through multiple channels. User Disengagement: Overwhelmed users may resort to disabling notifications, leading to a potential disconnect. II. In-App Inbox Center: A Central Hub for Seamless Interaction The in-app inbox notification center emerges as a pivotal feature, offering a centralized repository designed to empower users by bringing all notifications under one roof. Check 6 Unique Types of In-App Notifications Every Product Manager Should Know. Streamlined Experience: Users gain the ability to access and manage all notifications in one designated space, simplifying the user experience. Reduced Fatigue: A historical notification feed minimizes the pressure to respond immediately, fostering a more relaxed interaction model. User Empowerment: The In-app Inbox center provides users with a sense of control over their interactions with the application. III. Learning from Success: Examples of Inbox Feeds Done Right Examining successful implementations of Inbox Feeds on platforms such as Facebook, Reddit, Atlassian, LinkedIn, and GitHub provides invaluable insights. These platforms serve as exemplary models, showcasing how centralized notification repositories can significantly enhance user engagement. More use-cases here 5 Mobile Inbox Transactional Use-Cases That Businesses Are Using To Improve Customer Engagement. Facebook's News Feed: An exemplar of a historical list of events since the last login, offering a comprehensive view of interactions within the application. Reddit's Notification Repository: A centralized hub linking to new messages, comments, and popular subreddits, providing an efficient way for users to stay informed. GitHub's Notification Inbox: Inclusive of assignments, review requests, and activity-dependent notifications, showcasing the versatility of an Inbox Feed in varied contexts. IV. Collaboration Made Seamless: Effective Distribution of Information In the realm of B2B SaaS applications, collaboration hinges on efficient information distribution. The Inbox Feed proves instrumental in ensuring that users stay informed about project updates, mentions, conversations, and deadline changes. Project Visibility: Users can grasp the status of projects, fostering effective collaboration among team members. Timely Updates : Ensures users are informed about changes when they log into the application, avoiding potential lapses in communication. Deadline Management: Critical for teams working within strict deadlines, the Inbox Feed becomes a vital tool for managing project timelines. V. Workflow Automation Harmony: Navigating Project Dynamics Workflow automation lies at the core of many B2B SaaS applications. The Inbox Feed becomes a linchpin, offering users a clear understanding of ongoing projects, administrative requests, and actions required from others. Clear Visualization: The In-app Inbox empowers users to comprehend the overall scope of projects, facilitating efficient task management. Preventing Delays : Real-world examples, such as Atlassian’s integration of in-app inbox, highlight its role in avoiding delays in the development and approval process. VI. The Future: Inbox Feed as the Cornerstone of User Communication As the digital landscape continues to evolve, the In-app Inbox stands as a beacon of effective user communication. Its implementation transcends the limitations of traditional notification methods, offering a user-centric approach that aligns with evolving user preferences. Enhanced User Engagement : Reduced fatigue and streamlined interactions foster a positive user experience, contributing to sustained user engagement. Interactive Communication: The Inbox Feed represents an evolving paradigm that respects user preferences, facilitating meaningful exchanges. Real-world Success: Learnings from platforms like LinkedIn emphasize the practical benefits in real-world scenarios, underscoring the relevance of In-app Inbox Center integration. VII. Recommendations for Implementation Considering the transformative potential of Mobile Inbox Center, strategic implementation becomes crucial. Key recommendations ensure seamless integration and optimal utilization. User Education : A comprehensive understanding of the benefits of the Inbox Feed is crucial for user acceptance and optimal utilization. Customization Options : Allowing users to tailor their notification preferences within the Inbox Feed enhances user control and personalization. Performance Optimization : Implementing scalable backend APIs ensures a smooth and responsive user experience, vital for the success of Inbox Feed integration. VIII. Implement In-App Inbox Notification Center with SuprSend SDK’s Front-End Integration: For getting a complete web inbox notification feed in your website's frontend, you can use suprsend-react-inbox to ngx-suprsend-inbox. For mobile inboxes, you can use suprsend-react-headless or suprsend-flutter-inbox . Back-End Considerations: With suprsend-react-inbox you don’t need to worry about backend considerations, as everything is managed at our end, including all the retrying mechanisms. Use the SuprSend API for a single function call to notify users across any configured channel. Users can delete notifications, contributing to a well-organized and clutter-free feed. Build or Buy Decision: Consider the trade-offs between building a custom inbox feature or using SuprSend as a reliable and easily integrated service. If web-native customization is your primary requirement, you might try suprsend-react-headless to implement and customize the UI/ UX of your in-app inbox without having to develop backend and front from scratch. Dedicated developer support is crucial for resolving issues and ensuring timely updates to feeds upon user login. We built an in-depth Build vs Buy guide to help you make your decision: Build vs Buy For Notification System - The Ultimate Guide For Decision-Making in Notification Infrastructure Development Reliability and Relevance: The effectiveness of the inbox feed relies on its reliability and relevance, similar to all notification features. Customization Options: Utilize SuprSend's pre-built inbox components for easy customization of the Inbox with the configuration studio. For more granular control, customize our provided placeholder code for Inbox feed according to your application's specific needs. Explore InApp Inbox Before Use! IX. Conclusion: Redefining Communication for the Modern User In conclusion, the SuprSend In-App Inbox Notification Center emerges as a powerful tool inspired by real-world successes and user-centric design principles. By incorporating this feature, applications can transcend conventional communication barriers, paving the way for a new era of interactive and meaningful exchanges. For next read, you can check out How Mobile Inbox Increases User Engagement? (including a case study with inapp-inbox). Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:22 |
https://design.forem.com/paaaarv | Parvathi Kumar - Design 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 Design Community Close Follow User actions Parvathi Kumar 404 bio not found Joined Joined on Oct 9, 2025 github website More info about @paaaarv 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 0 comments written Tag 0 tags followed Reimagining Thai Lagoon - Website Redesign Parvathi Kumar Parvathi Kumar Parvathi Kumar Follow Dec 5 '25 Reimagining Thai Lagoon - Website Redesign # uxdesign # showcase # uidesign # webdesign Comments Add Comment 2 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://atproto.com/guides/going-to-production | Going to production - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Going to production The Atmosphere is built to be distributed, which means anyone can and should feel free to host their own AT Protocol infrastructure. If you are self-hosting at scale, i.e. offering a service for many thousands of users, you will likely need to perform some additional “hardening” of your hosted service, and make more complication decisions about provisioning your infrastructure. The code to power a fully distributed Atmosphere is constantly improving. Here's a guide with some lessons and best practices for managing your own services. PDS We provide a PDS install script that is designed to get you up and running with your own PDS on a modestly resourced VPS. This will enable you to host your own data repositories, create and manage accounts, and serve your self-hosted data in the wider Atmosphere network or any other Atmosphere app. This section of the docs will help you take that PDS to production. Domain names If you are running a non-Bluesky app in addition to a PDS deployment, you will need separate domain names for your PDS hosting and your app. This is because image and video blobs would otherwise be served from the same domain name as the OAuth and session management pages. This could lead to security issues such as credential theft, and means that using subdomains isn't a practical solution. In other words, if you have an app at https://greensky.app , you should not use https://pds.greensky.app as a PDS hostname, you should use something like https://greensky-pds.net . If you used https://pds.greensky.social (which would make sense), it might rule out an OAuth client app at https://chat.greensky.social in the future. But you could do something like https://chat.greensky.app . The PDS has restrictive CORS headers by default. It is difficult to change a PDS hostname once it has active accounts — every account needs to be migrated individually. This is absolutely possible using [PLC rotation keys], but migrating is not turnkey. Also note that the PDS is the domain that users will enter their passwords on (and therefore remembered in password managers). Backups and Recovery Our official PDS install script configures SQLite as a database backend. Specifically, it uses one SQLite DB for each user's [data repository], and a few others for PDS-wide data. This may be surprising, since SQLite doesn't have any mechanism for handling backups or replications out of the box, but SQLite has increasingly been found to scale very well with some additional tooling. The secret sauce here is Litestream , which does exactly that — Backups and Recovery for SQLite . To get a recoverable, scalable PDS SQLite deployment with Litestream, we recommend: Setting PDS_SQLITE_DISABLE_WAL_AUTO_CHECKPOINT = true . This is in the environment variable config for your PDS. What this does is force the PDS SQLite client to keep write-ahead logging open and leave the actual checkpointing to Litestream. Use Litestream with systemd or another scheduler to find the most recently updated DBs and back them up. By default, individual user databases are located in /pds/actors/ . Litestream will clean the write-ahead log and checkpoint automatically, so there's no risk of WAL growing out of control. If needed, ensure that this script also runs on SIGTERM when cleaning up containers or pods from your deployment. In a disaster recovery scenario, you'd pull down all the most recent account database files (which might be missing a few hours of data) and the PDS-wide database files (which should be roughly complete). Then, run a recovery script which applies any repo operations from the PDS-level firehose output. This includes identity and account updates. Then, start the PDS back up. PLC key management It's important to secure the extra PLC identity rotation key for hosted accounts — e.g., in a Key Management System or Hardware Security Module . Pay attention to these two environment variables: PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX : used by the PDS service to perform operations on the PLC including recovering user accounts. If you are using AWS, this is configurable with the AWS Key Management Service , using PDS_PLC_ROTATION_KEY_KMS_KEY_ID . PDS_RECOVERY_DID_KEY : a public key that is added to the users DID. The corresponding private key must be stored in a safe place and can be used to recover user accounts in case of a catastrophic loss of data including the PDS_PLC_ROTATION_KEY_K256_PRIVATE_KEY_HEX . Working with images, video and other blobs By default, the PDS install script configures local disk storage for blobs (images, video, etc). This is fine for small deployments, but not recommended for production deployments. Storage needs will vary, but we strongly recommend using S3-compatible storage (e.g. Minio or a block storage offering from a VPS provider) instead of storing images and video on local disk. Rate limits The PDS implementation includes repo operation limits by default. If you remove those limits, then the entire PDS might get limited at the Relay (which itself has default event rate-limits for each PDS host), so be mindful of this if you are not also running your own Relay. By default, our PDS install script will set up a single Node application process. These are stateless backend applications that run on top of SQLite. If you scale horizontally to run multiple Node processes, you'll also need to use Redis to allow them to share state. There are two environment variables used to configure Redis: PDS_REDIS_SCRATCH_ADDRESS — your Redis instance (e.g. localhost:6379) PDS_REDIS_SCRATCH_PASSWORD — your Redis credentials. This allows your rate limiting to scale gracefully. Moderation Moderation is almost always performed at the PDS level. However, if you are also running a Relay, you should be aware that the Relay admin web interface has forms for performing account-level and PDS-level actions if needed. There are also some moderation-related PDS endpoints not exposed via XRPC, which our goat CLI tool can interact with. Refer to goat/pds_admin.go for examples. Ozone is our labeling service and moderation interface. If you are building your own AppView, AppViews can use the Ozone subscribeLabel "firehose" to receive updates. Ozone can also be granted permission to read additional PDS-level private information, such as the account email. This is helpful for things like account recovery. You should generally run separate Ozone instances for moderating the PDS (since they can see private account info) and standalone AppViews, unless there is actually a single administrative org doing the moderation for both. Previous PDS Self-Hosting Next OAuth Introduction © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://dev.to/t/linux/page/8 | Linux Page 8 - 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 Linux Follow Hide What are clouds made of? Linux servers, mostly. Create Post submission guidelines Articles and discussions should be directly related to Linux operating systems. Questions are encouraged (see the #help tag). Content with the main focus on bash or the Unix shell is permitted, but don't forget to add the #bash or #unix tag as you see it fitting. Articles mainly about WSL should be tagged with #wsl instead of #linux. about #linux Linux is a family of free and open source operating systems built on top of the Linux kernel, first released on 1991 by Linus Torvalds. Older #linux posts 5 6 7 8 9 10 11 12 13 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Essential Shell Scripting Basics You Should Know First ak0047 ak0047 ak0047 Follow Dec 16 '25 Essential Shell Scripting Basics You Should Know First # beginners # bash # linux # basic 2 reactions Comments Add Comment 4 min read Vibe coding: Time Zone Clock ESeguru ESeguru ESeguru Follow Jan 11 Vibe coding: Time Zone Clock # learning # raspberrypi # vibecoding # linux Comments Add Comment 7 min read My Experience at IIT Madras ILUGC Meetup Harini Harini Harini Follow Dec 17 '25 My Experience at IIT Madras ILUGC Meetup # techtalks # linux # meetup # community 1 reaction Comments Add Comment 1 min read Top 3 Cheap VPS Providers in 2025 (That I've Actually Used) Serdar Tekin Serdar Tekin Serdar Tekin Follow Dec 17 '25 Top 3 Cheap VPS Providers in 2025 (That I've Actually Used) # devops # linux # cloud # webdev Comments Add Comment 2 min read Linux File System Architecture: A Deep Dive into VFS, Inodes, and Storage kt kt kt Follow Jan 10 Linux File System Architecture: A Deep Dive into VFS, Inodes, and Storage # linux # kernel # systems # learning 1 reaction Comments Add Comment 7 min read Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF kt kt kt Follow Jan 10 Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF # linux # kernel # ebpf # programming Comments Add Comment 9 min read My Opinionated Fedora Silverblue Setup Archer Allstars Archer Allstars Archer Allstars Follow Dec 27 '25 My Opinionated Fedora Silverblue Setup # linux # productivity 1 reaction Comments Add Comment 8 min read Visualize Your System Logs: Web-based dashboard Ajit Kumar Ajit Kumar Ajit Kumar Follow Dec 16 '25 Visualize Your System Logs: Web-based dashboard # webserver # dashboard # logs # linux Comments Add Comment 3 min read Backing Up Nginx Logs the Right Way: From Basics to Automation Ajit Kumar Ajit Kumar Ajit Kumar Follow Dec 16 '25 Backing Up Nginx Logs the Right Way: From Basics to Automation # backup # nginx # linux # logrotate Comments Add Comment 4 min read Nginx Log Analytics with GoAccess: Local Logs, S3 Backups, and Beyond Ajit Kumar Ajit Kumar Ajit Kumar Follow Dec 16 '25 Nginx Log Analytics with GoAccess: Local Logs, S3 Backups, and Beyond # nginx # linux # ubuntu # backup Comments Add Comment 4 min read 🔐 Week 4 Scripting Challenge: Build an Auth Log Failed Login Scraper in Python fosres fosres fosres Follow Jan 6 🔐 Week 4 Scripting Challenge: Build an Auth Log Failed Login Scraper in Python # python # security # linux # securityengineering 3 reactions Comments 2 comments 12 min read Day-11 Crontab Syntax, jq Magic, and the AWS DevOps Jayanth Dasari Jayanth Dasari Jayanth Dasari Follow Dec 20 '25 Day-11 Crontab Syntax, jq Magic, and the AWS DevOps # devops # aws # linux # beginners Comments Add Comment 2 min read High-performance cross-platform Linux server manager Docker/SSH/SFTP) built with Tauri (Rust) and React. Ricardo Borges Ricardo Borges Ricardo Borges Follow Dec 20 '25 High-performance cross-platform Linux server manager Docker/SSH/SFTP) built with Tauri (Rust) and React. # tooling # devops # opensource # linux 1 reaction Comments Add Comment 2 min read Best WiFi Adapters That Actually Work on Linux (Tested & Explained) Linuxano Linuxano Linuxano Follow Dec 16 '25 Best WiFi Adapters That Actually Work on Linux (Tested & Explained) # linux # opensource # wifi Comments Add Comment 2 min read Enable Zephyr RTOS on STM32 hang-up hang-up hang-up Follow Dec 15 '25 Enable Zephyr RTOS on STM32 # linux # zephyr # stm32 Comments Add Comment 3 min read Share an efficient tool for quickly identifying the largest or most numerous directories when disk space is running low. pyn pyn pyn Follow Dec 15 '25 Share an efficient tool for quickly identifying the largest or most numerous directories when disk space is running low. # disk # linux # filesystem # go Comments Add Comment 1 min read Solving the "MFA Wall" and Other Roadblocks: Setting Up a Cloud-Ready Linux Environment Brian Meinert Brian Meinert Brian Meinert Follow Dec 19 '25 Solving the "MFA Wall" and Other Roadblocks: Setting Up a Cloud-Ready Linux Environment # azure # cloudcomputing # linux # beginners Comments Add Comment 3 min read luainstaller 2.0: Package Your .lua Scripts into Native Binaries Water Run Water Run Water Run Follow Dec 15 '25 luainstaller 2.0: Package Your .lua Scripts into Native Binaries # lua # linux # python # opensource Comments Add Comment 2 min read Advent of Embedded Linux — Day 5 Kanak Shilledar Kanak Shilledar Kanak Shilledar Follow Dec 15 '25 Advent of Embedded Linux — Day 5 # iot # linux # adventofcode # adventofembeddedlinux Comments Add Comment 1 min read Systemd Explained: Units, Targets, and Why systemctl Is More Than Start and Stop Rijul Rajesh Rijul Rajesh Rijul Rajesh Follow Dec 19 '25 Systemd Explained: Units, Targets, and Why systemctl Is More Than Start and Stop # linux # systemd # programming # beginners 11 reactions Comments Add Comment 3 min read Building a Fast File Transfer Tool, Part 2: Beating rsync by 58% with kTLS Vincent Du Vincent Du Vincent Du Follow Jan 7 Building a Fast File Transfer Tool, Part 2: Beating rsync by 58% with kTLS # linux # networking # security # performance 1 reaction Comments Add Comment 4 min read Spotify Connect, Raspberry Pi, AirPlay & HomePod - because simple audio setups are boring Piotr Ładoński Piotr Ładoński Piotr Ładoński Follow Dec 14 '25 Spotify Connect, Raspberry Pi, AirPlay & HomePod - because simple audio setups are boring # raspberrypi # airplay # homepod # linux Comments Add Comment 5 min read Building a File Copier 4x Faster Than cp Using io_uring Vincent Du Vincent Du Vincent Du Follow Jan 7 Building a File Copier 4x Faster Than cp Using io_uring # linux # cpp # performance # tutorial 2 reactions Comments Add Comment 4 min read Day 1: From Zero to Functions - My Bash Journey SOFT ICODE SOFT ICODE SOFT ICODE Follow Dec 14 '25 Day 1: From Zero to Functions - My Bash Journey # basic # bash # linux # devops Comments Add Comment 1 min read Python - Stop storing passwords in plain text! A guide to werkzeug.security Sunny Bhambhani Sunny Bhambhani Sunny Bhambhani Follow for AWS Community Builders Jan 5 Python - Stop storing passwords in plain text! A guide to werkzeug.security # python # devops # beginners # linux 1 reaction Comments Add Comment 3 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:49:23 |
https://www.merriam-webster.com/dictionary/confuse | CONFUSE Definition & Meaning - Merriam-Webster ✨📕 The NEW Collegiate Dictionary, 12th Edition Over 5,000 words added — Learn More! ✨📕 The NEW Collegiate Dictionary — Learn More! Menu Toggle Merriam-Webster Logo Search Chatbot Chatbot Games Word of the Day Grammar Word Finder Slang New Newsletters Wordplay Rhymes Thesaurus Join MWU More Games Word of the Day Grammar Wordplay Slang Rhymes Word Finder Newsletters New Thesaurus Join MWU Shop Books Merch Log In Username My Words Recents Account Log Out Est. 1828 Dictionary Definition Definition Synonyms Example Sentences Word History Rhymes Entries Near Related Articles Cite this Entry Citation Share Kids Definition Kids More from M-W Show more Show more Citation Share Kids More from M-W Save Word To save this word, you'll need to log in. Log In confuse verb con·​fuse kən-ˈfyüz Save Word --> confused ; confusing Synonyms of confuse transitive verb 1 : to disturb in mind or purpose : throw off The directions she gave confused us. 2 a : to make indistinct : blur Stop confusing the issue. b : to fail to differentiate from an often similar or related other confuse money with comfort Do not confuse the words "flaunt" and "flout." c : to mix indiscriminately : jumble Their arms, legs, and bodies were confused together, till they resembled … two serpents interlaced. — Thomas Medwin 3 : to make embarrassed : abash 4 archaic : to bring to ruin https://merriam.atlassian.net/browse/MWSITE-9211 --> confusingly kən-ˈfyü-ziŋ-lē adverb Synonyms of confuse Relevance bewilder perplex baffle puzzle befuddle embarrass See All Synonyms & Antonyms in Thesaurus Examples of confuse in a Sentence Quotes--> Extra Examples--> The general was trying to confuse the enemy. The new evidence only confused matters further. You must be confusing me with someone else. Recent Examples on the Web Examples are automatically compiled from online sources to show current usage. Read More Opinions expressed in the examples do not represent those of Merriam-Webster or its editors. Send us feedback . Those early renderings confused enthusiasts and sparked criticism for their familiar proportions. — Sujita Sinha, Interesting Engineering , 7 Jan. 2026 Elsewhere in the park, many visitors were confused about various aspects of the new parking rules. — David Garrick, San Diego Union-Tribune , 6 Jan. 2026 Casey's launched the Goodstop brand in May 2021 after acquiring 92 Bucky's convenience stores — not to be confused with Buc-ee's — in Illinois, Iowa, Missouri and Texas. — Philip Joens, Des Moines Register , 6 Jan. 2026 On Tuesday morning, the Oscar winner ended her Today interview with host Craig Melvin in giggles after making a simple mistake, confusing one TV network for another. — Shania Russell, Entertainment Weekly , 6 Jan. 2026 See All Example Sentences for confuse Word History Etymology Middle English confusen, back-formation from confused "frustrated, ruined," participle based on Anglo-French confus, borrowed from Latin confūsus, past participle of confundere "to pour together, blend, bring into disorder, destroy, disconcert" — more at confound First Known Use 14th century, in the meaning defined at sense 4 Time Traveler The first known use of confuse was in the 14th century See more words from the same century Rhymes for confuse accrues accuse aircrews amuse bamboos breakthroughs canoes cashews chartreuse construes defuse ensues See All Rhymes for confuse Browse Nearby Words confusable confuse confused See all Nearby Words Articles Related to confuse 'Confuzzled': A Not So Confusing... Confuzzled about 'confuzzled'? We can help. Cite this Entry Style Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/confuse. Accessed 13 Jan. 2026.">MLA Merriam-Webster.com Dictionary , s.v. “confuse,” accessed January 13, 2026, https://www.merriam-webster.com/dictionary/confuse.">Chicago Merriam-Webster.com dictionary . Retrieved January 13, 2026, from https://www.merriam-webster.com/dictionary/confuse">APA Merriam-Webster.com Dictionary , https://www.merriam-webster.com/dictionary/confuse. Accessed 1/13/2026.">Merriam-Webster “Confuse.” Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/confuse. Accessed 13 Jan. 2026. Copy Citation Share Kids Definition confuse verb con·​fuse kən-ˈfyüz confused ; confusing 1 a : to make mentally foggy or uncertain : perplex the complicated problem confused us b : to cause to be embarrassed or upset 2 : to make unclear : blur stop confusing the issue 3 : to make disordered : jumble the cords were all confused together 4 : to fail to tell apart teachers always confused the twins https://merriam.atlassian.net/browse/MWSITE-9211 --> confusedly -ˈfyüz(-ə)d-lē adverb confusingly -ˈfyü-ziŋ-lē adverb --> More from Merriam-Webster on confuse Nglish: Translation of confuse for Spanish Speakers Last Updated: 7 Jan 2026 - Updated example sentences Love words? Need even more definitions? Subscribe to America's largest dictionary and get thousands more definitions and advanced search—ad free! Merriam-Webster unabridged --> More from Merriam-Webster Can you solve 4 words at once? Play Play Can you solve 4 words at once? Play Play Word of the Day umbrage See Definitions and Examples » Get Word of the Day daily email! --> --> --> Popular in Grammar & Usage See More 5 Verbal Slip Ups and Language Mistakes 'Buck Naked' or 'Butt Naked'? 'Affect' vs. 'Effect' The Difference Between 'i.e.' and 'e.g.' Why is '-ed' sometimes pronounced at the end of a word? See More Popular in Wordplay See More Top 10 Sophisticated Insults Ten Kinds of Happiness The Words of the Week - Jan. 9 17 Words for Dog Breeds Skibidi, Mog & More: Gen Alpha Slang See More Popular See More 5 Verbal Slip Ups and Language Mistakes Top 10 Sophisticated Insults Ten Kinds of Happiness See More Games & Quizzes See All Quordle Can you solve 4 words at once? Play Blossom Pick the best words! Play The Missing Letter A daily crossword with a twist Play Farm Idioms Quiz If you've got a pig in a poke - what exactly is a... Take the quiz See All Merriam Webster Learn a new word every day. Delivered to your inbox! Help About Us Advertising Info Contact Us Privacy Policy Terms of Use Facebook Twitter YouTube Instagram © 2026 Merriam-Webster, Incorporated | 2026-01-13T08:49:23 |
https://replit.com/news | Replit News Agent Products Agent Design Database Publish Security Integrations Mobile For Work Teams Replit for teams to build together Enterprise Replit with Enterprise-grade security & controls Use Cases Business Apps Rapid Prototyping Roles Enterprise PM Designers Operations Software Developers Small Businesses SMB owners Founders Resources Get Started Docs Community Expert Network Inspiration Customer Stories Gallery Blog News Pricing Careers Agent Contact sales Log in Sign up Products For Work Resources Pricing Careers Contact sales Log in Start building Replit in the News Stay up to date with the latest company news & media coverage Sep 10, 2025 Replit Closes $250 Million in Funding to Build on Customer Momentum Prysm, a16z, Amex Ventures, Coatue, YC in Round; Joins Google’s AI Futures Fund Announces New Autonomous Agent Read more Oct 23, 2025 Newswire: Government of Jordan Collaborates With Replit to Launch AI-Powered Learning Assistant In a landmark collaboration between the Government of Jordan and Replit, a global leader in agentic software creation, the Ministry of Education has launched the pilot phase of “Siraj”, an AI-powered learning assistant designed to transform education across the Kingdom. Read more Sep 11, 2025 Bloomberg: Vibe-Coding Startup Replit Hits $3 Billion Valuation AI coding startup Replit is valued at $3 billion after a new funding round. CEO Amjad Masad says vibe-coding enables more people to program and is accelerating product development for Replit’s customers. Masad discusses the growth of AI-assisted software creation with Caroline Hyde and Ed Ludlow on "Bloomberg Tech." Watch on Bloomberg Jul 8, 2025 Newswire: Replit Collaborates with Microsoft to bring Vibe Coding to Enterprise Customers New partnership enables Microsoft customers to rapidly build and deploy secure, production-ready applications using natural language - no coding expertise required. Read more Jul 2, 2025 SaaStr: From $10M to $100M ARR in 5.5 Months: Inside Replit’s AI Coding Rocketship A deep-dive into the AI development platform wars and why Replit’s 10x growth in 5.5 months is a big part of reshaping how software gets built. Read on SaaStr Jul 2, 2025 Google Cloud: Replit: From idea to application in minutes Replit adopted Anthropic's updated Claude 3.5 Sonnet on Google Cloud's Vertex AI to power Replit Agent, which allows anyone from anywhere in the world to use natural language prompts to take an idea to application regardless of coding experience. Read on Google Cloud Apr 2, 2025 Bloomberg: 'Vibecoding' Leader Replit in Talks for $3 Billion Valuation Artificial intelligence coding startup Replit Inc. is in talks with investors for a new funding round that would almost triple its valuation to $3 billion. Read on Bloomberg Feb 19, 2025 Anthropic: Replit democratizes software development with Claude on Google Cloud's Vertex AI Replit, a software creation platform, uses Claude on Google Cloud's Vertex AI to help anyone build and deploy software applications [...]. Read on Anthropic Feb 18, 2025 Inc.: After Partnering With Anthropic, This Startup Has Grown Revenue by 10X. Here’s How Coding platform Replit is using generative AI to empower anyone to write software and create apps. Read on Inc. Feb 17, 2025 Venture Beat: Replit and Anthropic’s AI is helping non-coders bring software ideas to life Replit is helping non-technical employees at Zillow contribute to software development. Read on Venture Beat Get started for free Create & deploy websites, automations, internal tools, data pipelines and more in any programming language without setup, downloads or extra tools. All in a single cloud workspace with AI built in. Contact Sales Get Started Handy Links About us Vibe Coding 101 Help How to guides Import from GitHub Status Additional resources Brand kit Partnerships Legal Terms of service Commercial agreement Privacy Subprocessors DPA Report abuse Connect X / Twitter Tiktok Facebook Instagram Linkedin Scroll to top All rights reserved. Copyright © 2026 Replit, Inc. | 2026-01-13T08:49:23 |
https://design.forem.com/metehandesign/what-my-dining-table-and-my-cat-showed-me-about-human-attention-3c99 | What my dining table and my cat showed me about human attention - Design 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 Design 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 Metehan Altuntekin Posted on Jan 5 • Originally published at metehan.design What my dining table and my cat showed me about human attention # design # uxdesign # behavior We all think that we see a thing as it is when we look at it. But this is not true. We see things how we look at them. I just realized this while looking at the patterns on the dining table in my kitchen: When I look at this image for ascending line patterns, I see columns. When I look for descending line patterns, I see those instead. When I look for the V-shape formed by both, I see those lines; when I look for the A-shape, I see them as columns. When I look for both separately, I see both but with less focus—likely because my brain shifts from one to another rapidly. Our brains only see what they look for. My cat, Hureyre, doesn't see this at all. He only sees the piece of meat or butter I put on the table. He doesn't see text on paper or patterns on bed sheets. He doesn't notice the different clothes I wear. He has only a few interests: moving objects, noise-making things, and things that could be prey, a friend, or a danger. His cat brain just works this way. This interest can be extended through association. For example, I taught him the question "Acıktın mı?" (Are you hungry?), and he recognizes it. I trained him to respond affirmatively because he knows food follows. But his focus only extends so far, always depending on his basic desires. Humans work the same way. We need developed curiosity to care about certain things. My mom doesn't look into a car's design or performance—she just wants to get from point A to B. My brother, however, knows many brands and how they perform differently because he is interested in the joy of driving. When I see a website or an app, I see many exciting details. When I show them to non-designers, they often can't say more than "it looks nice" or "the colors are good." They don't care about the details that I recognize separately. Instead, they look for the general feel they get from the design. A viewer on a landing page looks for things that interest them: "What is this about?", "What are the benefits?", or "How does this make me feel?" The brain rapidly shifts focus. If they stay within one focus and keep seeing related things, they remain engaged more easily. Everyone looks for specific things and ignores the rest, also at varying levels. Some interests can be 1/10 importance while some are 9/10. Catching a viewer's attention requires knowing how that attention flows. A designer’s eye must constantly look for the same things the visitor seeks. Because of this, identifying all the things the user looks for — simultaneously and effectively — becomes the essential skill a designer must master to build products that truly achieve success. Further Reading / Relevant Concepts: If you're interested in the psychology behind this, these ideas are also explored in Gestalt Principles : Multistability: The mind switches between different interpretations of the same image. Continuity: Our eyes naturally follow the smoothest path or line. Closure: The brain fills in gaps to perceive a complete shape. 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 Metehan Altuntekin Follow Web Dev & Designer Location Turkey Education Self educated Work Freelancing on my own Joined Feb 28, 2022 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://design.forem.com/john_smith_f87cb3ddff9956/make-brat-style-text-online-30b6#comments | Make Brat Style Text Online - Design 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 Design 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 john smith Posted on Nov 1, 2025 Make Brat Style Text Online # typography # sideprojects # designtrends # tools Hi everyone 👋 I made a fun little tool called aBratGenerator . It helps you make cool and bold “brat style” text designs right in your browser. You can type any words you want, change the colors, pick fonts, and add effects. Then you can download your design and share it anywhere. I built it just for fun because I saw many people love the brat trend but had no easy way to make it themselves. Try it here 👉 https://abratgenerator.com/ Hope you enjoy it. Let me know what you make with it 💚 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 john smith Follow I love to explore new ideas Joined Nov 1, 2025 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://design.forem.com/metehandesign | Metehan Altuntekin - Design 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 Design Community Close Follow User actions Metehan Altuntekin Web Dev & Designer Location Turkey Joined Joined on Feb 28, 2022 Email address dev@metehan.design Personal website https://metehan.design github website Education Self educated Work Freelancing on my own More info about @metehandesign 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 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 Skills/Languages HTML, CSS, JS, TS, TailwindCSS, Svelte, React Currently learning SwiftUI Post 1 post published Comment 1 comment written Tag 1 tag followed What my dining table and my cat showed me about human attention Metehan Altuntekin Metehan Altuntekin Metehan Altuntekin Follow Jan 5 What my dining table and my cat showed me about human attention # design # uxdesign # behavior 2 reactions Comments Add Comment 3 min read Want to connect with Metehan Altuntekin? Create an account to connect with Metehan Altuntekin. 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://design.forem.com/new/sideprojects | New Post - Design 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 Design Community Close Join the Design Community Design Community is a community of 3,676,891 amazing designers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Design Community? Create account . 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://claude.com/pricing#api | Pricing | Claude -------> Meet Claude Products Claude Claude Code Features Claude in Chrome Claude in Slack Claude in Excel Skills Models Opus Sonnet Haiku Platform Overview Developer docs Pricing Regional Compliance Console login Solutions Use cases AI agents Coding Industries Customer support Education Financial services Government Healthcare Life sciences Nonprofits Pricing Overview API Max plan Team plan Enterprise plan Learn Blog Courses Customer stories Events Tutorials Use cases Anthropic news Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Meet Claude Products Claude Claude Code Features Claude in Chrome Claude in Slack Claude in Excel Skills Models Opus Sonnet Haiku Platform Overview Developer docs Pricing Regional Compliance Console login Solutions Use cases AI agents Coding Industries Customer support Education Financial services Government Healthcare Life sciences Nonprofits Pricing Overview API Max plan Team plan Enterprise plan Learn Blog Courses Customer stories Events Tutorials Use cases Anthropic news Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Pricing Pricing Explore here Ask questions about this page Copy as markdown Pricing Individual Team & Enterprise API Active Free Try Claude $0 Free for everyone Try Claude Try Claude Try Claude Chat on web, iOS, Android, and on your desktop Generate code and visualize data Write, edit, and create content Analyze text and images Ability to search the web Unlock more from Claude with desktop extensions Pro For everyday productivity $17 Per month with annual subscription discount ($200 billed up front). $20 if billed monthly. Try Claude Try Claude Try Claude Everything in Free, plus: More usage* Access Claude Code on the web and in your terminal Create files and execute code Access to unlimited projects to organize chats and documents Access to Research Connect Google Workspace: email, calendar, and docs Integrate any context or tool through connectors with remote MCP Memory across conversations Extended thinking for complex work Ability to use more Claude models Max Get the most out of Claude From $100 Per person billed monthly Try Claude Try Claude Try Claude Everything in Pro, plus: Choose 5x or 20x more usage than Pro* Higher output limits for all tasks Memory across conversations Early access to advanced Claude features Priority access at high traffic times Claude in Excel Additional usage limits apply. Prices shown don’t include applicable tax. Team For collaboration across organizations Create a Team plan Create a Team plan Create a Team plan Standard seat Chat, projects, and more $25 Per person / month with annual subscription discount. $30 if billed monthly. Minimum 5 members. Premium seat Includes Claude Code $150 Per person / month. Minimum 5 members. More usage* Admin controls for remote and local connectors Single sign-on (SSO) and domain capture Enterprise deployment for the Claude desktop app Enterprise search across your organization Connect Microsoft 365, Slack, and more Central billing and administration Early access to collaboration features Claude Code available with premium seat Enterprise For businesses operating at scale Contact sales Contact sales Contact sales Everything in Team, plus: More usage* Enhanced context window Role-based access with fine-grained permissioning System for Cross-domain Identity Management (SCIM) Audit logs Google Docs cataloging Compliance API for observability and monitoring Claude Code available with premium seat Custom data retention controls HIPAA-ready offering available Additional usage limits apply. Prices shown don’t include applicable tax. Education plan Get a comprehensive university‐wide plan for an institution, including its students, faculty, and staff. Learn more Learn more Learn more Student and faculty access Comprehensive access for all university members at discounted rates Academic research and learning mode Dedicated API credits and educational features for student learning Training and enablement Resources for successful adoption across your institution Latest models Contact sales Contact sales Contact sales Start building Start building Start building Save 50% with batch processing. Learn more Batch processing Opus 4.5 Most intelligent model for building agents and coding Input $ 5 / MTok Output $ 25 / MTok Prompt caching Write $ 6.25 / MTok Read $ 0.50 / MTok Sonnet 4.5 Optimal balance of intelligence, cost, and speed Input Prompts ≤ 200K tokens $ 3 / MTok Prompts > 200K tokens $ 6 / MTok Output Prompts ≤ 200K tokens $ 15 / MTok Prompts > 200K tokens $ 22.50 / MTok Prompt caching ≤ 200K tokens Write $ 3.75 / MTok Read $ 0.30 / MTok > 200K tokens Write $ 7.50 / MTok Read $ 0.60 / MTok Haiku 4.5 Fastest, most cost-efficient model Input $ 1 / MTok Output $ 5 / MTok Prompt caching Write $ 1.25 / MTok Read $ 0.10 / MTok Prompt caching pricing reflects 5-minute TTL. Learn about extended prompt caching . Explore detailed pricing Explore detailed pricing Explore detailed pricing Pricing for tools Get even more out of Claude with advanced
features and capabilities. Learn more Learn more Learn more Web search Give Claude access to the latest information from the web. Doesn’t include input and output tokens required to process requests. Cost $10 / 1K searches Code execution Run Python code in a sandboxed environment for advanced data analysis. 50 free hours of usage daily per organization. Additional hours $0.05 per hour per container Service tiers Balance availability, performance, and predictable costs based on your needs. Learn more Learn more Learn more Contact sales Contact sales Contact sales Priority When time, availability, and predictable pricing are most important Standard Default tier for both piloting and scaling everyday use cases Batch For asynchronous workloads that can be processed together for better efficiency Legacy models Learn more Learn more Learn more Explore detailed pricing Explore detailed pricing Explore detailed pricing Save 50% with batch processing. Learn more Batch processing Opus 4.1 Input $ 15 / MTok Output $ 75 / MTok Prompt caching Write $ 18.75 / MTok Read $ 1.50 / MTok Sonnet 4 Input $ 3 / MTok Output $ 15 / MTok Prompt caching Write $ 3.75 / MTok Read $ 0.30 / MTok Opus 4 Input $ 15 / MTok Output $ 75 / MTok Prompt caching Write $ 18.75 / MTok Read $ 1.50 / MTok Haiku 3 Input $ 0.25 / MTok Output $ 1.25 / MTok Prompt caching Write $ 0.30 / MTok Read $ 0.03 / MTok Prompt caching pricing reflects 5-minute TTL. Learn about extended prompt caching . Homepage Homepage Next Next Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Write Button Text Button Text Learn Button Text Button Text Code Button Text Button Text Write Help me develop a unique voice for an audience Hi Claude! Could you help me develop a unique voice for an audience? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Improve my writing style Hi Claude! Could you improve my writing style? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Brainstorm creative ideas Hi Claude! Could you brainstorm creative ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Learn Explain a complex topic simply Hi Claude! Could you explain a complex topic simply? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Help me make sense of these ideas Hi Claude! Could you help me make sense of these ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Prepare for an exam or interview Hi Claude! Could you prepare for an exam or interview? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Code Explain a programming concept Hi Claude! Could you explain a programming concept? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Look over my code and give me tips Hi Claude! Could you look over my code and give me tips? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Vibe code with me Hi Claude! Could you vibe code with me? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! More Write case studies This is another test Write grant proposals Hi Claude! Could you write grant proposals? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to — like Google Drive, web search, etc. — if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can - an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Write video scripts this is a test Anthropic Anthropic © [year] Anthropic PBC Products Claude Claude Claude Claude Code Claude Code Claude Code Max plan Max plan Max plan Team plan Team plan Team plan Enterprise plan Enterprise plan Enterprise plan Download app Download app Download app Pricing Pricing Pricing Log in Log in Log in Features Claude in Chrome Claude in Chrome Claude in Chrome Claude in Slack Claude in Slack Claude in Slack Claude in Excel Claude in Excel Claude in Excel Skills Skills Skills Models Opus Opus Opus Sonnet Sonnet Sonnet Haiku Haiku Haiku Solutions AI agents AI agents AI agents Code modernization Code modernization Code modernization Coding Coding Coding Customer support Customer support Customer support Education Education Education Financial services Financial services Financial services Government Government Government Healthcare Healthcare Healthcare Life sciences Life sciences Life sciences Nonprofits Nonprofits Nonprofits Claude Developer Platform Overview Overview Overview Developer docs Developer docs Developer docs Pricing Pricing Pricing Regional Compliance Regional Compliance Regional Compliance Amazon Bedrock Amazon Bedrock Amazon Bedrock Google Cloud’s Vertex AI Google Cloud’s Vertex AI Google Cloud’s Vertex AI Console login Console login Console login Learn Blog Blog Blog Claude partner network Claude partner network Claude partner network Courses Courses Courses Connectors Connectors Connectors Customer stories Customer stories Customer stories Engineering at Anthropic Engineering at Anthropic Engineering at Anthropic Events Events Events Powered by Claude Powered by Claude Powered by Claude Service partners Service partners Service partners Startups program Startups program Startups program Tutorials Tutorials Tutorials Use cases Use cases Use cases Company Anthropic Anthropic Anthropic Careers Careers Careers Economic Futures Economic Futures Economic Futures Research Research Research News News News Responsible Scaling Policy Responsible Scaling Policy Responsible Scaling Policy Security and compliance Security and compliance Security and compliance Transparency Transparency Transparency Help and security Availability Availability Availability Status Status Status Support center Support center Support center Terms and policies Privacy choices Cookie settings We use cookies to deliver and improve our services, analyze site usage, and if you agree, to customize or personalize your experience and market our services to you. You can read our Cookie Policy here . Customize cookie settings Reject all cookies Accept all cookies Necessary Enables security and basic functionality. Required Analytics Enables tracking of site performance. Off Marketing Enables ads personalization and tracking. Off Save preferences Privacy policy Privacy policy Privacy policy Responsible disclosure policy Responsible disclosure policy Responsible disclosure policy Terms of service: Commercial Terms of service: Commercial Terms of service: Commercial Terms of service: Consumer Terms of service: Consumer Terms of service: Consumer Usage policy Usage policy Usage policy x.com x.com LinkedIn LinkedIn YouTube YouTube Instagram Instagram English (US) English (US) 日本語 (Japan) Deutsch (Germany) Français (France) 한국어 (South Korea) | 2026-01-13T08:49:23 |
https://design.forem.com/t/graphicdesign | Graphicdesign - Design 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 Design Community Close # graphicdesign Follow Hide Discussions on logos, branding, print, and visual communication Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Essential Graphic Design Principles for Beginners Design by Qayum Design by Qayum Design by Qayum Follow Dec 21 '25 Essential Graphic Design Principles for Beginners # design # graphicdesign # newdesigner Comments 1 comment 7 min read Emerging graphic design trends for 2026 Karina Egle Karina Egle Karina Egle Follow Nov 13 '25 Emerging graphic design trends for 2026 # design # recommendations # webdesign # graphicdesign Comments Add Comment 2 min read loading... trending guides/resources Emerging graphic design trends for 2026 Essential Graphic Design Principles for Beginners 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://design.forem.com/freepixel11/help-center-design-consistency-rules-for-trust-and-clarity-alo#comments | Help Center Design Consistency Rules for Trust and Clarity - Design 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 Design 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 FreePixel Posted on Dec 24, 2025 Help Center Design Consistency Rules for Trust and Clarity # helpcenter # uxdesign # customersupport # knowledgebase Help centers are judged in seconds. Users arrive with a problem, scan the page, and quickly decide whether they trust what they see. Help center design consistency rules for trust and clarity are what make that decision effortless. When layouts, patterns, and language stay consistent, users feel oriented and confident. When they don’t, even accurate content feels unreliable. This article breaks down the consistency rules that quietly improve clarity, trust, and long-term usability in help centers. Quick Summary Design consistency in help centers builds trust, reduces cognitive load, and improves self-service success. Consistent layouts, navigation, language, and interaction patterns help users scan faster, feel confident, and resolve issues without contacting support. Table of Contents Why Design Consistency Matters in Help Centers What “Consistency” Really Means in a Help Center Rule 1: Keep Page Layouts Predictable Rule 2: Use a Single Visual Hierarchy System Rule 3: Standardize Navigation Patterns Rule 4: Use the Same Language Patterns Everywhere Rule 5: Align UI Terminology With Product Reality Rule 6: Keep Interaction Patterns Consistent Rule 7: Use Reusable Components for Clarity Rule 8: Maintain Consistency Across Devices Rule 9: Visual Consistency and Accessibility Rule 10: Avoid One-Off Design Exceptions Mini Case Example: Consistency Fix That Reduced Tickets How Design Consistency Builds Trust Over Time Auditing Design Consistency in Your Help Center Common Consistency Mistakes to Avoid Conclusion FAQ: Help Center Design Consistency Why Design Consistency Matters in Help Centers In support contexts, users are not exploring. They are trying to resolve something quickly. Inconsistent design: Slows down scanning Increases cognitive load Creates doubt about accuracy Pushes users toward support tickets Consistent design: Reduces mental effort Reinforces familiarity Signals reliability Encourages self-service Consistency is not visual polish. It is a trust signal. What “Consistency” Really Means in a Help Center Consistency does not mean everything looks identical. It means patterns behave predictably. In a help center, consistency applies to: Layout structure Navigation behavior Visual hierarchy Language and tone Interaction patterns Once users learn one pattern, they should be able to reuse it everywhere. Rule 1: Keep Page Layouts Predictable Every help article should feel familiar. Best practices: Same header placement Same content width and spacing Same location for summaries and steps If users must relearn layout on every page, clarity breaks. Rule 2: Use a Single Visual Hierarchy System Headings, spacing, and emphasis must follow one logic. A consistent hierarchy includes: One clear H1 Logical H2 sections Minimal, purposeful H3s Predictable spacing Hierarchy guides attention before reading begins. Rule 3: Standardize Navigation Patterns Navigation inconsistency creates uncertainty. Keep these stable: Category structure Breadcrumb behavior Search placement Back navigation If navigation changes between sections, users feel lost—even if content is correct. Rule 4: Use the Same Language Patterns Everywhere Design consistency includes words. Examples: “Sign in” vs “Log in” (choose one) “Account” vs “Profile” (define clearly) Same labels across product and help center Language drift quietly erodes trust. Rule 5: Align UI Terminology With Product Reality Help center language must match the product exactly. Avoid: Old feature names Internal terminology Marketing phrases Users compare the help article with the UI instantly. Any mismatch creates doubt. Rule 6: Keep Interaction Patterns Consistent Buttons, links, and callouts should behave the same everywhere. Consistency rules: Primary actions look the same Secondary actions are clearly different Links always look like links Predictability reduces hesitation. Rule 7: Use Reusable Components for Clarity Reusable components reinforce learning. Examples: Step-by-step blocks Warning callouts Tip boxes Configuration sections Users recognize these patterns and process information faster. Rule 8: Maintain Consistency Across Devices Mobile and desktop experiences should feel related, not redesigned. Mobile consistency includes: Same information order Same labels Same search behavior Responsive design should adapt layout, not logic. Rule 9: Visual Consistency and Accessibility Consistency naturally supports accessibility. Screen readers and keyboard users rely on: Logical heading order Predictable navigation landmarks Stable focus behavior Accessible design and consistent design reinforce each other. Rule 10: Avoid One-Off Design Exceptions One-off designs feel clever but break trust. Common mistakes: Special layouts for “important” articles Unique styling used once Team-specific design patterns If a pattern exists, reuse it. If it doesn’t, question why. Mini Case Example: Consistency Fix That Reduced Tickets A help center had: Multiple article templates Different heading styles by team Inconsistent button labels Users often reopened tickets after reading articles. Changes made: Unified article layout Standardized hierarchy and spacing Aligned language with product UI Result: Faster scanning Higher article helpfulness Fewer follow-up tickets No new content was added. Only consistency improved. How Design Consistency Builds Trust Over Time Trust is cumulative. Each consistent interaction: Reinforces familiarity Reduces friction Signals professionalism Over time, users stop questioning the help center and start relying on it. Auditing Design Consistency in Your Help Center Ask: Do all articles follow the same structure? Are labels reused consistently? Does navigation behave the same everywhere? If the answer is no, clarity is leaking. Common Consistency Mistakes to Avoid Avoid: Mixing old and new templates Letting teams design independently Updating UI without updating help content Treating consistency as optional Consistency is infrastructure, not decoration. Conclusion Help center design consistency rules for trust and clarity form the foundation of effective self-service support. When design patterns stay consistent, users stop thinking about navigation and start solving problems. That confidence reduces tickets, improves satisfaction, and makes support content scalable. If keeping layouts, components, and patterns consistent across a growing help center feels challenging, tools like Diziana can help maintain structure and clarity without constant manual cleanup. A consistent foundation makes trust easier to earn—and keep. FAQ: Help Center Design Consistency What is design consistency in a help center? Using predictable layouts, patterns, and language across all support content. Why does consistency improve trust? Because users can focus on solving problems instead of learning new patterns. Is consistency more important than visual style? Yes. Predictable behavior matters more than aesthetics. How often should consistency be reviewed? After major UI changes and during regular content audits. 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 FreePixel Follow FreePixel is a freemium microstock and AI creative platform offering high-quality images and smart AI tools for creators, designers, and businesses. https://www.freepixel.com Location kanpur Joined Aug 11, 2025 More from FreePixel Help Center Visual Hierarchy Techniques That Guide User Attention # helpcenter # uxdesign # visualdesign # customersupport Help Center Design Systems for Consistent Support Experiences # helpcenter # uxdesign # designsystems # customersupport Personalized Help Center Experiences Using Customer Data # helpcenter # customersupport # uxwriting # techwriting 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://atproto.com/specs/event-stream | Event Stream - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Event Stream In addition to regular HTTP API endpoints, atproto supports continuous event streams. Message schemas and endpoint names are transport-agnostic and defined in Lexicons . The initial encoding and transport scheme uses binary DAG-CBOR encoding over WebSockets . The Lexicon type for streams is subscription . The schema includes an identifier ( id ) for the endpoint, a message schema (usually a union, allowing multiple message types), and a list of error types ( errors ). Clients subscribe to a specific stream by initiating a connection at the indicated endpoint. Streams are currently one-way, with messages flowing from the server to the client. Clients may provide query parameters to configure the stream when opening the connection. A backfill window mechanism allows clients to catch up with stream messages they may have missed. At a high level, this works by assigning monotonically increasing sequence numbers to stream events, and allowing clients to specify an initial sequence number when initiating a connection. The intent of this mechanism is to ensure reliable delivery of events following disruptions during a reasonable time window (eg, hours or days). It is not to enable clients to roll all the way back to the beginning of the stream. All of the initial subscription Lexicons in the com.atproto namespace use the backfill mechanism. However, a backfill mechanism (and even cursors, which we define below) is not required for streams. Subscription endpoints which do not require reliable delivery do not need to implement a backfill mechanism or use sequence numbers. The initial subscription endpoints are also public and do not require authentication or prior permission to subscribe (though resource limits may be imposed on client). But subscription endpoints may require authentication at connection time, using the existing HTTP API (XRPC) authentication methods. Streaming Wire Protocol (v0) To summarize, messages are encoded as DAG-CBOR and sent over a binary WebSocket. Clients connect to to a specific HTTP endpoint, with query parameters, then upgrade to WebSocket. Every WebSocket frame contains two DAG-CBOR objects, with bytes concatenated together: a header (indicating message type), and the actual message. The WebSockets "living standard" is currently maintained by WHATWG , and can be found in full at https://websockets.spec.whatwg.org/ . Connection Clients initialize stream subscriptions by opening an HTTP connection and upgrading to a WebSocket. HTTPS and "WebSocket Secure" ( wss:// ) on the default port (443) should be used for all connections on the internet. HTTP, cleartext WebSocket ( ws:// ), and non-standard ports should only be used for testing, development, and local connections (for example, behind a reverse proxy implementing SSL). From the client perspective, failure to upgrade connection to a WebSocket is an error. Query parameters may be provided in the initial HTTP request to configure the stream in an application-specific way, as specified in the endpoint's Lexicon schema. Errors are usually returned through the stream itself. Connection-time errors are sent as the first message on the stream, and then the server drops the connection. But some errors can not be handled through the stream, and are returned as HTTP errors: 405 Method Not Allowed : Returned to client for non-GET HTTP requests to a stream endpoint. 426 Upgrade Required : Returned to client if Upgrade header is not included in a request to a stream endpoint. 429 Too Many Requests : Frequently used for rate-limiting. Client may try again after a delay. Support for the Retry-After header is encouraged. 500 Internal Server Error : Client may try again after a delay 501 Not Implemented : Service does not implement WebSockets or streams, at least for this endpoint. Client should not try again. 502 Bad Gateway , 503 Service Unavailable , 504 Gateway Timeout : Client may try again after a delay Servers should return HTTP bodies as JSON with the standard XRPC error message schema for these status codes. But clients also need to be robust to unexpected response body formats. A common situation is receiving a default load-balancer or reverse-proxy error page during scheduled or unplanned downtime. Either the server or the client may decided to drop an open stream connection if there have been no messages for some time. It is also acceptable to leave connections open indefinitely. Framing Each binary WebSocket frame contains two DAG-CBOR objects, concatenated. The first is a header and the second is the payload. The header DAG-CBOR object has the following fields: op ("operation", integer, required): fixed values, indicating what this frame contains 1 : a regular message, with type indicated by t -1 : an error message t ("type", string, optional): required if op is 1 , indicating the Lexicon sub-type for this message, in short form. Does not include the full Lexicon identifier, just a fragment. Eg: #commit . Should not be included in header if op is -1 . Clients should ignore frames with headers that have unknown op or t values. Unknown fields in both headers and payloads should be ignored. Invalid framing or invalid DAG-CBOR encoding are hard errors, and the client should drop the entire connection instead of skipping the frame. Servers should ignore any frames received from the client, not treat them as errors. Error payloads all have the following fields: error (string, required): the error type name, with no namespace or # prefix message (string, optional): a description of the error Streams should be closed immediately following transmitting or receiving an error frame. Message payloads must always be objects. They should omit the $type field, as this information is already indicated in the header. There is no specific limit on the size of WebSocket frames in atproto, but they should be kept reasonably small (around a couple megabytes). If a client can not keep up with the rate of messages, the server may send a "too slow" error and close the connection. Sequence Numbers Streams can optionally make use of per-message sequence numbers to improve the reliability of transmission. Clients keep track of the last sequence number they received and successfully processed, and can specify that number after a re-connection to receive any missed messages, up to some roll-back window. Servers persist no client state across connections. The semantics are similar to Apache Kafka 's consumer groups and other stream-processing protocols. Subscription Lexicons must include a seq field (integer type), and a cursor query parameter (integer type). Not all message types need to include seq . Errors do not, and it is common to have an #info message type that is not persisted. Sequence numbers are always positive integers (non-zero), and increase monotonically, but otherwise have flexible semantics. They may contain arbitrary gaps. For example, they might be timestamps. To prevent confusion when working with Javascript (which by default represents all numbers as floating point), sequence numbers should be limited to the range of integers which can safely be represented by a 64-bit float. That is, the integer range 1 to 2^53 (not inclusive on the upper bound). The connection-time rules for cursors and sequence numbers: no cursor is specified: the server starts transmitting from the current stream position cursor is higher than current seq ("in the future"): server sends an error message and closes connection cursor is in roll-back window: server sends any persisted messages with greater-or-equal seq number, then continues once "caught up" with current stream cursor is older than roll-back window: the first message in stream is an info indicating that cursor is too-old, then starts at the oldest available seq and sends the entire roll-back window, then continues with current stream cursor is 0 : server will start at the oldest available seq , send the entire roll-back window, then continue with current stream The scope for sequence numbers is the combination of service provider (hostname) and endpoint (NSID). This roughly corresponds to the wss:// URL used for connections. That is, sequence numbers may or may not be unique across different stream endpoints on the same service. Services should ensure that sequence numbers are not re-used, usually by committing events (with sequence number) to robust persistent storage before transmitting them over streams. In some catastrophic failure modes (or large changes to infrastructure), it is possible that a server would lose data from the backfill window, and need to reset the sequence number back to 1 . In this case, if a client re-connects with a higher number, the server would send back a FutureCursor error to the client. The client needs to decide what strategy to follow in these scenarios. We suggest that clients treat out-of-order or duplicate sequence numbers as an error, not process the message, and drop the connection. Most clients should not reset sequence state without human operator intervention, though this may be a reasonable behavior for some ephemeral clients not requiring reliable delivery of every event in the stream. Usage and Implementation Guidelines The current stream transport is primarily designed for server-to-server data synchronization. It is also possible for web applications to connect directly from end-user browsers, but note that decoding binary frames and DAG-CBOR is non-trivial. The combination of HTTP redirects and WebSocket upgrades is not consistently supported by WebSocket client libraries. Support is not specifically required or forbidden in atproto. Supported versions of the WebSockets standard are not specified by atproto. The current stable WebSocket standard is version 13. Implementations should make reasonable efforts to support modern versions, with some window of backwards compatibility. WebSockets have distinct resource rate-limiting and denial-of-service issues. Network bandwidth limits and throttling are recommended for both servers and clients. Servers should tune concurrent connection limits and buffer sizes to prevent resource exhaustion. If services need to reset sequence state, it is recommended to chose a new initial sequence number with a healthy margin above any previous sequence number. For example, after persistent storage loss, or if clearing prior stream state. URLs referencing a stream endpoint at a particular host should generally use wss:// as the URI scheme (as opposed to https:// ). Security and Privacy Considerations As mentioned in the "Connection" section, only wss:// (SSL) should be used for stream connections over the internet. Public services should reject non-SSL connections. Most HTTP XRPC endpoints work with content in JSON form, while stream endpoints work directly with DAG-CBOR objects as untrusted input. Precautions must be taken against hostile data encoding and data structure manipulation. Specific issues are discussed in the Data Model and Repository specifications. Possible Future Changes Event Streams are one of the newest components of the AT Protocol, and the details are more likely to be iterated on compared to other components. The sequence number scheme may be tweaked to better support sharded streams. The motivation would be handle higher data throughputs over the public internet by splitting across multiple connections. Additional transports (other than WebSocket) and encodings (other than DAG-CBOR) may be specified. For example, JSON payloads in text WebSocket frames would be simpler to decode in browsers. Additional WebSocket features may be adopted: transport compression "extensions" like permessage-deflate definition of a sub-protocol bi-directional messaging 1000-class response codes Ambiguities in this specification may be resolved, or left open. For example: HTTP redirects CORS and other issues for browser connections maximum message/frame size Authentication schemes may be supported, similar to those for regular HTTP XRPC endpoints. Previous Permissions Next Sync © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://www.merriam-webster.com/dictionary/deceive | DECEIVE Definition & Meaning - Merriam-Webster ✨📕 The NEW Collegiate Dictionary, 12th Edition Over 5,000 words added — Learn More! ✨📕 The NEW Collegiate Dictionary — Learn More! Menu Toggle Merriam-Webster Logo Search Chatbot Chatbot Games Word of the Day Grammar Word Finder Slang New Newsletters Wordplay Rhymes Thesaurus Join MWU More Games Word of the Day Grammar Wordplay Slang Rhymes Word Finder Newsletters New Thesaurus Join MWU Shop Books Merch Log In Username My Words Recents Account Log Out Est. 1828 Dictionary Definition Definition Synonyms Synonym Chooser Example Sentences Word History Phrases Containing Rhymes Entries Near Cite this Entry Citation Share Kids Definition Kids Legal Definition Legal More from M-W Show more Show more Citation Share Kids Legal More from M-W Save Word To save this word, you'll need to log in. Log In deceive verb de·​ceive di-ˈsēv Save Word --> deceived ; deceiving Synonyms of deceive transitive verb 1 : to cause to accept as true or valid what is false or invalid deceiving customers about the condition of the cars bluffing at poker in order to deceive the other players 2 archaic : ensnare … he it was whose guile … deceived the mother of mankind … — John Milton 3 a obsolete : to be false to You have deceived our trust … — Shakespeare b archaic : to fail to fulfill … nor are my hopes deceived . — John Dryden 4 archaic : to while away These occupations oftentimes deceived the listless hour … — William Wordsworth 5 obsolete : cheat … deceived me of a good sum of money … — William Oldys intransitive verb : to make someone believe something that is not true : to practice deceit also : to give a false impression appearances can deceive https://merriam.atlassian.net/browse/MWSITE-9211 --> deceiver noun deceivingly di-ˈsē-viŋ-lē adverb Synonyms of deceive Relevance fool trick mislead See All Synonyms & Antonyms in Thesaurus Choose the Right Synonym for deceive deceive , mislead , delude , beguile mean to lead astray or frustrate usually by underhandedness. deceive implies imposing a false idea or belief that causes ignorance, bewilderment, or helplessness. tried to deceive me about the cost mislead implies a leading astray that may or may not be intentional. I was misled by the confusing sign delude implies deceiving so thoroughly as to obscure the truth. we were deluded into thinking we were safe beguile stresses the use of charm and persuasion in deceiving. was beguiled by false promises Examples of deceive in a Sentence Quotes--> Extra Examples--> Her parents punished her for trying to deceive them. He was accused of deceiving the customer about the condition of the car. People who think they can eat whatever they want without harming their health are deceiving themselves. Remember that appearances can deceive —just because something looks good doesn't mean it is good. Recent Examples on the Web Examples are automatically compiled from online sources to show current usage. Read More Opinions expressed in the examples do not represent those of Merriam-Webster or its editors. Send us feedback . Your husband claims not to have known the weekend arrangements in advance, claiming you were both deceived — not only by his old friends, but by their wives, and by the single female neighbor. — Judith Martin, Mercury News , 8 Jan. 2026 That's when the voice distortion comes into play — but due to a history of viewers trying to cheat the system, The Masked Singer team does even more to deceive the audience. — Skyler Caruso, PEOPLE , 7 Jan. 2026 To keep the most vulnerable safe, Ivan has to decide to confront the soldiers or deceive them at the potential cost of his life. — Destiny Jackson, Deadline , 6 Jan. 2026 Relying Too Much On Garbage Disposals Though the name may be deceiving , garbage disposals aren’t actually designed to dispose of all garbage. — Quincy Bulin, Southern Living , 3 Jan. 2026 See All Example Sentences for deceive Word History Etymology Middle English, from Anglo-French deceivre , from Latin decipere , from de- + capere to take — more at heave entry 1 First Known Use 13th century, in the meaning defined at transitive sense 2 Time Traveler The first known use of deceive was in the 13th century See more words from the same century Phrases Containing deceive deceive oneself into thinking self - deceive Rhymes for deceive achieve believe conceive naive perceive receive relieve reprieve retrieve breve cleave cleeve See All Rhymes for deceive Browse Nearby Words deceivable deceive deceive oneself into thinking See all Nearby Words Cite this Entry Style Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/deceive. Accessed 13 Jan. 2026.">MLA Merriam-Webster.com Dictionary , s.v. “deceive,” accessed January 13, 2026, https://www.merriam-webster.com/dictionary/deceive.">Chicago Merriam-Webster.com dictionary . Retrieved January 13, 2026, from https://www.merriam-webster.com/dictionary/deceive">APA Merriam-Webster.com Dictionary , https://www.merriam-webster.com/dictionary/deceive. Accessed 1/13/2026.">Merriam-Webster “Deceive.” Merriam-Webster.com Dictionary , Merriam-Webster, https://www.merriam-webster.com/dictionary/deceive. Accessed 13 Jan. 2026. Copy Citation Share Kids Definition deceive verb de·​ceive di-ˈsēv deceived ; deceiving 1 : to cause to believe what is untrue : mislead deceived the customer about the condition of the car 2 : to use or practice deceit https://merriam.atlassian.net/browse/MWSITE-9211 --> deceiver noun deceivingly -ˈsē-viŋ-lē adverb --> Legal Definition deceive verb de·​ceive deceived ; deceiving transitive verb : to cause to accept as true or valid what is false or invalid intransitive verb : to practice deceit compare defraud , mislead https://merriam.atlassian.net/browse/MWSITE-9211 --> --> More from Merriam-Webster on deceive Nglish: Translation of deceive for Spanish Speakers Last Updated: 9 Jan 2026 - Updated example sentences Love words? Need even more definitions? Subscribe to America's largest dictionary and get thousands more definitions and advanced search—ad free! Merriam-Webster unabridged --> More from Merriam-Webster Can you solve 4 words at once? Play Play Can you solve 4 words at once? Play Play Word of the Day umbrage See Definitions and Examples » Get Word of the Day daily email! --> --> --> Popular in Grammar & Usage See More 5 Verbal Slip Ups and Language Mistakes 'Buck Naked' or 'Butt Naked'? 'Affect' vs. 'Effect' The Difference Between 'i.e.' and 'e.g.' Why is '-ed' sometimes pronounced at the end of a word? See More Popular in Wordplay See More Top 10 Sophisticated Insults Ten Kinds of Happiness The Words of the Week - Jan. 9 17 Words for Dog Breeds Skibidi, Mog & More: Gen Alpha Slang See More Popular See More 5 Verbal Slip Ups and Language Mistakes Top 10 Sophisticated Insults Ten Kinds of Happiness See More Games & Quizzes See All Quordle Can you solve 4 words at once? Play Blossom Pick the best words! Play The Missing Letter A daily crossword with a twist Play Farm Idioms Quiz If you've got a pig in a poke - what exactly is a... Take the quiz See All Merriam Webster Learn a new word every day. Delivered to your inbox! Help About Us Advertising Info Contact Us Privacy Policy Terms of Use Facebook Twitter YouTube Instagram © 2026 Merriam-Webster, Incorporated | 2026-01-13T08:49:23 |
https://x.com/awilkinson/status/1843063918421549135?t=pULhtnj5pzZjPYo69xm7jA&s=19 | 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:49:23 |
https://twitter.com/intent/tweet?text=%22You%20See%20Increased%20Latency%20in%20API%20Response%20%E2%80%94%20What%20Are%20the%20Possible%20Causes%20in%20Apigee%20X%3F%22%20by%20realNameHidden%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Frealnamehidden1_61%2Fyou-see-increased-latency-in-api-response-what-are-the-possible-causes-in-apigee-x-3nne | 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:49:23 |
https://design.forem.com/new/uidesign | New Post - Design 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 Design Community Close Join the Design Community Design Community is a community of 3,676,891 amazing designers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Design Community? Create account . 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://coderabbit.ai/pricing | CodeRabbit Pricing | AI Code Reviews | Try for Free Features Enterprise Customers Pricing Blog Resources Docs Trust Center Contact Us FAQ Log In Get a free trial All plans include a 14-day free trial No credit card required Free Get summarization for each Pull request $0 Includes a 14-day free usage of the Pro plan. No credit card required Unlimited public and private repositories PR summarization Reviews in IDE Sign up for free Pro Comprehensive Pull request reviews and advanced insights $24 /month, billed annually or $30/monthly per developer Unlimited PR reviews Integrates with Jira & Linear Linters and SAST tools support Product analytics dashboards Customizable reports Docstrings generation Higher rate limits for reviews in IDE Get a free trial Enterprise Pro for large enterprises Talk to us Self-hosting option Multi-org support Higher limits SLA support Technical enablement and dedicated CSM Pay via AWS/GCP Marketplace Vendor security review and agreement redlines Custom setup including ALB, etc Everything in Pro, plus: Contact us FAQ Will I be charged for all the developers in my organization? No, you will only be charged for the developers who create pull requests. You also have the option to manually assign seats. You can purchase any number of seats and assign them to specific developers. Is there a limit on the number of reviews or repositories? There is no limit on the number of pull requests reviewed or the number of repositories on any of the plans Is it possible to reassign seats to other developers? Yes, seats can be reassigned at any time. What kind of support is available for CodeRabbit users? CodeRabbit offers comprehensive support, including documentation, tutorials, and access to a dedicated support team to help with any issues or questions. How do I sign up for the free open-source plan? Sign up for CodeRabbit using GitHub or GitLab, install CodeRabbit on a public repository, and receive free reviews forever for public repositories. No additional setup is required. How does CodeRabbit work? CodeRabbit uses machine learning algorithms to analyze your codebase, identify potential issues, and suggest improvements based on best practices and coding standards. View all questions 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:49:23 |
https://design.forem.com/mitch-narrativeflow/how-to-write-branching-dialogue-without-code-and-stay-in-your-creative-flow-123p#comments | How to Write Branching Dialogue Without Code (and Stay in Your Creative Flow) - Design 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 Design 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 Mitch Posted on Oct 15, 2025 How to Write Branching Dialogue Without Code (and Stay in Your Creative Flow) # tools # resources # nocode # designprocess If your branching dialogue is overwhelming you, it's not your fault. Most tools make you feel like you need to be a programmer just to write a conversation — and if you're a writer or narrative designer first, that's a creativity-killer. I've spent years designing branching RPG stories, and I eventually built a tool for myself to solve this exact problem. But before we get there, let's talk about why branching dialogue becomes so chaotic so fast — and how to avoid that mess entirely. Why Traditional Methods Collapse (Fast) Most writers and small teams start with what they already know: 📊 Spreadsheets – great for budgets, terrible for dialogue trees. 📄 Docs/Notion – fine for linear text, but they break once you add choices or conditions. 💻 Custom scripts – powerful, but only if you enjoy debugging more than actually writing. 🧱 Game engines – excellent for building worlds, but not for writing stories inside them. The result? Branches disappear. Logic breaks. Testing becomes a nightmare. And your story suffers the most. Instead of staying in your creative rhythm, you spend hours fixing structure problems you never should've had to deal with. The problem isn't you — it's the tools. The Biggest Pitfalls in Branching Dialogue Even if you can brute-force a solution with spreadsheets or engine scripts, the cracks show up fast: Branch explosions – A simple choice tree turns into an unreadable mess after three or four layers. "Illusion of choice" traps – Branches collapse too soon because it's too hard to track divergence, so player choices don't really matter. Continuity errors – You forget the player was honest with the guard in one branch and bribed him in another. Later, the script assumes both (or neither!) happened. Testing bottlenecks – The only way to check logic is manually replaying dozens of permutations. This isn't a skill issue — they're signs you're forced to put creative work through tools that weren't built for branching stories. The Fix: Think Visually, Not Linearly Writers don't think in spreadsheets or conditionals. We think in possibilities : "What if the player tells the truth here?" "What if they already met this character?" "What if they solve the quest differently?" "What if they said something completely unexpected?" That's why the easiest way to write branching dialogue is to map it visually — as a story you can literally see . Instead of juggling states in your head, you drop nodes onto a canvas: 🗨️ Dialog nodes – what characters say. 🔀 Choice nodes – player decisions. 🧠 Conditional nodes – diverge based on variables. 🎲 Probability nodes – add unpredictability or roguelike flavor. Suddenly, your branching story is no longer abstract code — it's a map you can read at a glance. A Simple Example: The City Gate Encounter Let's say you're writing a scene where the player meets a guard at the city gates. In a visual editor, you'd build it like this: Start Node – Conversation begins. Dialog Node – "Halt! State your business." Choice Node – "I'm here to trade." "I'm here to see the king." "None of your business." From there: "Trade" → the guard waves them through. "King" → the guard asks for proof. "Rude" → maybe combat begins. All of this is clear, without a single nested if statement. How Complexity Blows Up (And Why Tools Matter) Let's scale that example slightly. 3 choices : trade, king, rude → ✅ manageable. Add 1 condition (has the player met this guard before?) → 6 variations. Add 1 variable (such as player reputation) → 12 variations. This is how branching explodes — and why traditional methods collapse under the weight. { "dialogue" : [ { "id" : "start" , "type" : "dialog" , "text" : "A guard blocks your path." , "out" :[ "c1" , "c2" , "c3" ]}, { "id" : "c1" , "type" : "choice" , "text" : "I am here to trade." , "out" :[ "trade" ]}, { "id" : "trade" , "type" : "dialog" , "text" : "We have a special bay for merchants." , "out" :[ "end" ]}, { "id" : "c2" , "type" : "choice" , "text" : "I am here to see the king." , "out" :[ "king_check" ]}, { "id" : "king_check" , "type" : "conditional" , "condition" : "has_letter" , "true" : "king_has_letter" , "false" : "king_no_letter" }, { "id" : "king_has_letter" , "type" : "dialog" , "text" : "Ah, a letter. You may pass." , "out" :[ "end" ]}, { "id" : "king_no_letter" , "type" : "dialog" , "text" : "No letter, no entry." , "out" :[ "end" ]}, { "id" : "c3" , "type" : "choice" , "text" : "None of your business." , "out" :[ "rude" ]}, { "id" : "rude" , "type" : "dialog" , "text" : "You've got some nerve. Fight?" , "out" :[ "end" ]} ], "variables" : { "has_letter" : false , "met_guard" : false } } Enter fullscreen mode Exit fullscreen mode This is how dangling branches and continuity errors sneak in — unless your tools help you see and manage the structure as you build it. Scaling Without Chaos When your dialogue grows beyond a single scene, visual design becomes essential: ✅ Consistency – Keep names, conditions, and outcomes aligned across branches. 🧠 State tracking – Variables like [GuardRespect] or [PlayerReputation] follow the player everywhere. 🔍 Automatic checks – The tool can flag missing links, dangling branches, and logic holes before they break your story. This is the difference between coding a dialogue tree and crafting an unforgettable narrative . Why This Matters for Writers The biggest cost of bad tools isn't bugs — it's your lost creativity . Every time you stop to debug or fix structure, every time you open your IDE just to write, you leave the creative "flow state" that makes your story work in the first place. When you design visually, you stay focused on what matters: characters, choices, emotions, and meaning . The logic becomes a byproduct, not a barrier. A Few Best Practices Even with good tools, these principles will save you headaches: 💡 Think in chunks, not lines. Start with moments (introduction, problem to overcome, resolution) before zooming into individual lines. 🧠 Track what the player knows. Not just what the world knows — this keeps branches consistent and the world believable. 🎭 Use false choices intentionally. It's fine for multiple options to lead to the same result — just make sure the player knows it's on purpose rather than covering up a deadline. 🧪 Playtest in slices. Don't build a 40-branch quest before testing. Start small, iterate, expand. What I Ended Up Building After years of wanting a tool that actually works, a tool that facilitates your game stories coming to life, I build something new: NarrativeFlow . I started out building it for myself, and discovered that others needed it too. It's a visual, node-based editor designed specifically for writers and narrative designers: 📌 Visual story maps – write and structure without code. 🐛 Automatic error detection – no more broken branches. 🧠 Variables and conditions – track player decisions visually. 🧭 Script + node views – swap between text and flow when you need. Whether it's a small prototype or a massive branching RPG, it keeps everything clear, playable, and organized. The Future of Narrative Design Player-driven storytelling isn't niche anymore — it's becoming the standard. The problem? Narrative complexity has outpaced the tools most writers use. We have engines that render lifelike worlds, but we still expect writers to manage branching stories in spreadsheets. That gap is why so many projects stall, collapse, or default to "illusion of choice." Tools that let writers focus on story first and logic second are how we close that gap. Want to Go Deeper? If this topic resonates with you, I put together a free guide: The Narrative Designer's Playbook – 12 Insights for Crafting Stories Players Actually Care About It's short, actionable, and based on my own hard-won lessons as a narrative designer. Grab that guide — and let's raise the bar for game narrative together. ✍️ I'd also love to hear how you handle branching dialogue. What tools or workflows have worked (or failed) for you? Drop a comment! 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 Mitch Follow Hey there! I'm a narrative designer working on some of the most sophisticated video game stories yet to release. I created NarrativeFlow to help narrative designers tell stories that stand out—fast. Location United States Education Self-taught Work Narrative Designer | Creator and Co-Owner of NarrativeFlow LLC Joined Sep 17, 2025 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://codeql.github.com/docs | CodeQL documentation --> CodeQL documentation CodeQL resources CodeQL overview CodeQL guides Writing CodeQL queries CodeQL language guides Reference docs QL language reference CodeQL standard-libraries CodeQL query help Source files CodeQL repository Academic QL publications CodeQL documentation CodeQL enables you to query code as though it were data. Write a query to find all variants of a vulnerability, eradicating it forever. Then share your query to help others do the same. CODEQL RELEASE INFORMATION Supported languages and frameworks View the languages, libraries, and frameworks supported in the latest release of CodeQL... Change logs Read about the improvements to the queries, libraries, and tooling in each release... System requirements View the system requirements for running the latest version of CodeQL... CodeQL coverage of CWEs Detailed information on the coverage of Common Weakness Enumerations (CWEs) in the latest release... LEARN TO WRITE CODEQL About CodeQL Learn what CodeQL is and how it works... Writing CodeQL queries Get to know more about queries and learn some key query-writing skills by solving puzzles... CodeQL language guides Experiment and learn how to write effective and efficient queries for CodeQL databases generated from the languages supported in CodeQL analysis... Running CodeQL queries Learn about the options available for running CodeQL queries on one or multiple codebases... CODEQL RESOURCES CodeQL CLI releases Download the latest version of the CodeQL CLI... CodeQL extension for Visual Studio Code Download the extension from the Visual Studio Code Marketplace... CodeQL repository Contribute to the source code of the libraries and queries for CodeQL... CODEQL REFERENCE DOCS QL language reference Learn all about QL, the powerful query language that underlies the code scanning tool CodeQL... CodeQL standard libraries Find details of the predicates, modules, and classes included with CodeQL... CodeQL query help View the query help for the queries included in the code scanning query suites... Product Features Security Copilot Enterprise Case Studies Pricing Resources Platform Developer API Partners Education GitHub CLI GitHub Desktop Support GitHub Docs Community Forum Training Status Contact GitHub Company About Blog Careers Press Shop © GitHub, Inc. Terms Privacy | 2026-01-13T08:49:23 |
https://design.forem.com/t/cms | Cms - Design 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 Design Community Close # cms Follow Hide Working with Content Management Systems like WordPress, Shopify, etc. Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Seeking Feedback on Custom Blogger Templates - What Do You Need? Yanuar Zhaldy Gemilang Yanuar Zhaldy Gemilang Yanuar Zhaldy Gemilang Follow Dec 17 '25 Seeking Feedback on Custom Blogger Templates - What Do You Need? # cms # userresearch # webdesign Comments 1 comment 1 min read Why Your Website Should Evolve With You (and How) Per Starke Per Starke Per Starke Follow Oct 23 '25 Why Your Website Should Evolve With You (and How) # cms # webdesign # uidesign # copywriting 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/suprsend-for-transactional-messaging-reliable-real-time-multi-channel-delivery | SuprSend for Transactional Messaging: Reliable, Real-Time, Multi-Channel Delivery Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Notification Infrastructure SuprSend for Transactional Messaging: Reliable, Real-Time, Multi-Channel Delivery Nikita Navral • September 26, 2025 TABLE OF CONTENTS What is Transactional Messaging? Transactional messages are system-triggered communications like account verification codes, password resets, payment confirmations, shipping alerts, or compliance notices . These are not optional updates; they must arrive instantly, reliably, and securely . Unlike promotional or marketing sends, transactional flows are bound by higher expectations for deliverability, regulatory compliance, and fail-safe reliability . SuprSend provides developer-first infrastructure designed to meet these exact standards. Why Teams Use SuprSend for Transactional Messages 1. Reliability Built-In <200ms latency for OTPs, 2FA, and login alerts. Automatic retries, failovers, and fallback routing across channels, so a password reset link or payment receipt never goes missing. Detailed logs and real-time observability for every message, down to the user level. 2. Separation of Transactional vs Marketing Traffic Dedicated IPs and vendor routing ensure bulk marketing behavior never hurts transactional deliverability. Flexible vendor management: send OTPs via one SMS provider while routing marketing campaigns through another—no cross-impact. 3. Multi-Channel, Multi-Tenant Support One API to deliver across Email, SMS, iMessage, Push, In-App Inbox, Slack, Teams, WhatsApp, and more . Multi-tenant architecture lets platforms like Freightify and Solar Informatics deliver branded transactional updates per client without rebuilding templates. Preference management ensures compliance with GDPR, TCPA, CASL - while still guaranteeing critical transactional alerts land. 4. Enterprise-Grade Security & Compliance SOC 2 Type II, HIPAA, GDPR, ISO compliance baked into the infrastructure. Tenant-level branding and domain routing so transactional emails come from your verified handles—critical for trust and regulatory recognition. Case Studies in Action eShipz : Reduced customer onboarding by 3 weeks while ensuring branded transactional alerts like order confirmations and delivery updates, across Email, SMS, and WhatsApp. Reporting Service Provider (FinTech) : Deployed critical trade compliance alerts in just two weeks: alerts that clients now treat as contractual must-haves. Evocalize : Increased repeat purchases by 27% with a mix of transactional and engagement notifications powered by SuprSend’s logs, workflows, and inbox. Takeaway If your platform handles sign-ups, payments, authentication, logistics, or compliance workflows , transactional messaging isn’t optional—it’s mission-critical. SuprSend gives product and engineering teams real-time APIs, robust retry logic, compliance support, and multi-channel reach to ensure every transactional message is delivered, logged, and trusted. 👉 Learn more at SuprSend.com Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://twitter.com/theJayKhatri | 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:49:23 |
https://twitter.com/ChihuahuaUx/status/1611500002869907457 | 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:49:23 |
https://twitter.com/intent/tweet?text=%22Accessible%20Visuals%3A%20How%20Inclusive%20Charts%20Empower%20Patient%20Health%22%20by%20wellallyTech%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fwellallytech%2Faccessible-visuals-how-inclusive-charts-empower-patient-health-5740 | 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:49:23 |
https://twitter.com/intent/tweet?text=%22Cowork%3A%20Claude%20Code%20for%20the%20Rest%20of%20Your%20Work%22%20by%20Sivaram%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fsivarampg%2Fcowork-claude-code-for-the-rest-of-your-work-3hjp | 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:49:23 |
https://twitter.com/ccschmitz | 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:49:23 |
https://future.forem.com/editgene | EDITGENE - Future 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 Future Close Follow User actions EDITGENE EDITGENE is rooted in independent technology development and upholds the business philosophy of "Innovation · Sharing." We focus on developing and optimizing CRISPR/Cas-based genome editing technologi Location 17800 Castleton St. Ste 665. City of Industry. CA 91748 Joined Joined on Oct 28, 2025 Personal website https://www.editxor.com/ More info about @editgene Post 1 post published Comment 0 comments written Tag 0 tags followed At Just One Year Old, He Joins Nature’s 10: The Story of a CRISPR Breakthrough EDITGENE EDITGENE EDITGENE Follow Dec 22 '25 At Just One Year Old, He Joins Nature’s 10: The Story of a CRISPR Breakthrough # biotech # healthtech # genomics # science Comments Add Comment 5 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. 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 . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:23 |
https://twitter.com/intent/tweet?text=%22Why%20Your%20E%20Commerce%20Filters%20Feel%20Slow%20Even%20When%20Your%20Site%20Is%20Fast%22%20by%20ar%20abid%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Far_abid_641aa302d5c68b2ae%2Fwhy-your-e-commerce-filters-feel-slow-even-when-your-site-is-fast-4a57 | 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:49:23 |
https://twitter.com/intent/tweet?text=%22OKAN%20KAPLAN%20SOUND%20LAB%20%E2%80%93%20Infinite%20Jazz%20Generator%20%7C%20Live%20Coding%20with%20JavaScript%22%20by%20okan%20kaplan%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fokan_kaplan_livehtml%2Fokan-kaplan-sound-lab-infinite-jazz-generator-live-coding-with-javascript-3ifi | 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:49:23 |
https://twitter.com/intent/tweet?text=%22Why%20use%20a%20version%20control%20system%3F%20-%20%F0%9F%92%92%22%20by%20%40szabgab%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fszabgab%2Fwhy-use-a-version-control-system-3o93 | 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:49:23 |
https://design.forem.com/om_shree_0709/fresh-trends-shaping-web-and-graphic-design-in-fall-2025-5bi6#comments | Fresh Trends Shaping Web and Graphic Design in Fall 2025 - Design 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 Design 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 Om Shree Posted on Oct 12, 2025 Fresh Trends Shaping Web and Graphic Design in Fall 2025 # design # tools # recommendations # resources If you're knee-deep in design work right now, you know how quickly things shift. One day you're tweaking a layout for mobile, the next you're rethinking color palettes to match the latest Pantone pick. As we hit mid-October 2025, the design world is buzzing with ideas that blend tech smarts with a return to hands-on creativity. Whether you're building websites or crafting graphics, these updates can help your projects feel current without overcomplicating things. Let's break down some key developments from the past few weeks. Pantone's Mocha Mousse Takes Center Stage Pantone dropped its Color of the Year for 2025 back in the spring, but it's really gaining traction now as fall sets in. Mocha Mousse a warm, earthy brown with hints of coffee and caramel is popping up everywhere in web and graphic design. It's not just a safe neutral; designers are pairing it with richer tones for that cozy, sophisticated vibe. Think about it: in web design, this means warmer gradients on hero sections or subtle backgrounds that make text pop without screaming for attention. For graphics, it's perfect for branding materials like posters or social media assets, adding depth without overwhelming the viewer. I saw a recent project on X where a freelancer used it for a coffee shop's rebrand simple swaps in their palette made the whole identity feel more inviting. If you're updating a site this month, test Mocha Mousse in your wireframes; it pairs surprisingly well with bolder accents like neon oranges for contrast. AI as Your Design Sidekick, Not the Boss AI tools aren't new, but in October 2025, they're evolving into something more collaborative for designers. Recent updates from platforms like Figma and Canva emphasize bringing design context straight into your workflow think feeding your sketches into an AI for quick prototypes or color suggestions that actually fit your brand. It's less about replacing your skills and more about speeding up the boring parts, like generating initial layouts or suggesting accessible alt text. On the graphic side, AI is shining in creating textured elements or experimental collages that feel handmade. Tools are getting better at mimicking grainy films or scrapbook vibes, which ties into the bigger push for "human touch" designs. A post I came across highlighted how one team used AI to brainstorm 3D product renders, then refined them manually for that authentic edge. Pro tip: Start small use it for mood boards if you're wary. It frees up time for the creative decisions that matter. Sustainable and Accessible Design Gets Real Sustainability isn't a buzz anymore; it's practical advice showing up in community chats and tool updates. With energy costs rising, designers are focusing on lightweight sites that load fast and use less power things like optimized images and efficient code. The W3C's guidelines from earlier this year are getting more traction, especially as browsers roll out features to measure a site's carbon footprint. Accessibility is right there with it. New laws like the European Accessibility Act kicking in soon mean more emphasis on high-contrast modes and keyboard-friendly nav. In graphics, this translates to inclusive visuals diverse representations in illustrations or alt text that's actually helpful. A recent X thread from a dev community shared how adding ARIA labels cut bounce rates by 20% on a client site. If your workflow hasn't caught up, audit one project this week; tools like WAVE make it straightforward. Bold Typography and Playful Interactions Typography is having a moment bold, expressive fonts that tell a story without saying much. We're seeing "not quite minimalism," where clean lines meet chunky serifs or distorted letters for that edgy feel. In web design, pair this with micro-interactions: subtle hovers that ripple or scroll-triggered fades that guide the eye. Graphics are leaning into mixed media too collages with hand-drawn elements over digital layers. It's a nod to imperfection in an AI-heavy world. One example floating around X was a Twitter banner workflow using Pinterest inspo and free tools to nail this look in under an hour. Experiment with variable fonts in your next mockup; they adapt so well to responsive needs. Community Spotlights: Events and Tools to Watch The design scene is collaborative as ever. Adobe MAX is set for late October in LA, with sessions on everything from AI ethics to hands-on 3D labs great for web and graphic pros alike. Closer to home, Figma's Config wrapped up virtually last month but left behind free resources on AI prototyping. And don't sleep on Canva's 2025 trends report; it dives into nostalgic textures meeting tech precision, with templates you can tweak right away. On the flip side, Society6's artist account shake-up effective October 3 has folks talking about curation over volume focusing on quality designs that sell. It's a reminder to prioritize work that resonates. Design in 2025 feels like a balance: tech pushing boundaries, but heart keeping it real. These shifts aren't about overhauling everything overnight just picking one or two to try in your next gig. What's catching your eye lately? Drop a comment; I'd love to hear how you're adapting. Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Some comments may only be visible to logged-in visitors. Sign in to view all 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 Om Shree Follow Technical Evangelist | AI Researcher | Simplifying Complex AI & Agent Workflows for Developers Location India Education Jaypee University Of Information Technology Pronouns He/Him Work Founder of Shreesozo Joined Feb 27, 2025 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://replit.com/usecases/founders | Replit for Founders & Entrepreneurs Agent Products Agent Design Database Publish Security Integrations Mobile For Work Teams Replit for teams to build together Enterprise Replit with Enterprise-grade security & controls Use Cases Business Apps Rapid Prototyping Roles Enterprise PM Designers Operations Software Developers Small Businesses SMB owners Founders Resources Get Started Docs Community Expert Network Inspiration Customer Stories Gallery Blog News Pricing Careers Agent Contact sales Log in Sign up Products For Work Resources Pricing Careers Contact sales Log in Start building B u ild a n y a pp f o r y o ur s tartup, f a ster w ith A I Replit lets founders turn startup ideas into real apps—without expensive dev shops or coding. Quickly prototype new products or validate concepts, then hand them off directly to your engineers. No more delays, just faster innovation. Start now Turn your startup idea into reality Bring your vision to life in days, not months. Replit's AI-powered Agent builds your app for you, so you can focus on designing the perfect product and getting to market faster. Create custom tools to scale efficiency Build internal tools like CRMs, dashboards, and automation scripts to save time and cut costs. Replit's AI-powered platform makes it easy to create custom solutions that accelerate your startup operations. Test new features & ideas Quickly validate new features without waiting, and confidently pass fully-tested concepts to your development team. Collaborate from anywhere Replit's real-time collaboration features let you code together, share feedback, and debug in real-time. Keep your team aligned and moving fast, even when working remotely. Let AI build your app for you Replit's AI-powered Agent writes your app's backend, frontend, and database code, and then helps you refine and debug. Build and ship your product faster than you ever thought possible. All of your work, in one workspace With Replit's real-time collaboration, you can code together, leave comments, and debug as if you're in the same room. Whether you're pair programming or getting feedback, Replit keeps your team in sync to prototype and launch faster. From idea to product in seconds With Replit's one-click deployment and automatic scaling, you can launch your app the moment it's ready. No complex setup, just results. Jumpstart your project with ready-to-use templates Replit provides templates for common startup apps and internal tools, so you can start building immediately. Get a head start on your project and customize as you go. Browse templates Trusted by founders building the future From early-stage startups to growing companies, founders and teams are using Replit to bring ideas to life and work smarter. Emily Nguyen Co-Founder, InstaCart AI Replit helped us turn our idea into a live product in just 2 weeks. We were able to get to market faster and start generating revenue sooner." Vikram Patel Founder & CEO, CloudOps "With Replit, we built custom tools to automate our sales and customer support. It's saved us hundreds of hours and helped us scale our operations." Maria Rodriguez CTO, FintechX "Replit's AI-powered platform and collaboration features have been game-changers for our distributed team. We can build and ship features faster than ever." Build your killer app faster with Replit, for free Join the thousands of founders using Replit to launch products and streamline startup operations with AI. Sign up for free and start building now. Get started free Handy Links About us Vibe Coding 101 Help How to guides Import from GitHub Status Additional resources Brand kit Partnerships Legal Terms of service Commercial agreement Privacy Subprocessors DPA Report abuse Connect X / Twitter Tiktok Facebook Instagram Linkedin Scroll to top All rights reserved. Copyright © 2026 Replit, Inc. | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/comparing-notification-infrastructure-marketing-automation-tools-a-guide-to-choose-the-right-platform-for-your-product | Comparing Notification Infrastructure & Marketing Automation Tools: A Guide to Choose the Right Platform for Your Product Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Outlook on Notifications Comparing Notification Infrastructure & Marketing Automation Tools: A Guide to Choose the Right Platform for Your Product Nikita Navral • February 5, 2025 TABLE OF CONTENTS At SuprSend, we often come across questions about the distinctions between the traditional Marketing Automation Tools (MATs) and the emerging Notification Infrastructure Platforms. In this comprehensive guide, we aim to explain the differences between the two and provide insights into why notification infrastructure platforms are gaining traction among product managers and engineering teams. The Evolution of Customer Engagement For a decade, Marketing automation tools (MATs) such as Braze, Customer.io, Iterable, and Clevertap have dominated the market, offering robust solutions for sending targeted marketing campaigns. These campaigns, often promotional in nature, help in customer retention and engagement - important to any business. At the same time, businesses are also required to send out their product notifications related to transactional alerts and updates in customers’ accounts. Often, these notifications are mission critical for businesses. For example, sending payment reminders, approval alerts or notifying a customer when an update / comment is posted so the user can take appropriate action. While MATs are proficient in addressing promotional use cases and engaging with customers on a marketing level, they fall short when it comes to handling complex product notifications crucial for product success. There is a new wave of platforms excelling in this domain, called notification infrastructure, which is redefining how product and engineering teams build and maintain product notifications, without having to build notification services internally. As businesses navigate this notification evolution, understanding where MATs fall short and how notification infrastructures work better become very important to help you choose the right solution for your needs. Understanding the Basics At the core, notification infrastructure platforms and marketing automation tools (MATs) share a common goal—connecting businesses with their audience. While they may share some common goals, their functionalities and usecases differ significantly. Marketing Automation Platforms - A Brief Overview Marketing Automation Platforms (MATs) have proven instrumental in orchestrating targeted and effective marketing campaigns. Here's a snapshot of what MATs are adept at: User Segmentation: MATs excel at storing and segmenting users based on diverse criteria, enabling businesses to tailor their messages for maximum impact. One-Time Campaigns: They facilitate the creation and execution of one-time campaigns, driving specific actions such as new product launch or cart additions. These are primarily sent to mobile push and emails, followed by SMS and whatsapp. Automated Notifications for Cohort Changes: MATs automate notifications triggered by user entry or exit from a cohort, and sending them timely and relevant communication. Quick Experiments and A/B Testing: MATs empower marketers to conduct rapid experiments and A/B tests to optimize funnels and boost conversions. Multi-Step Campaign Journeys: With a visual workflow builder, MATs allow the creation of multi-step campaigns, offering power of context based engagement. Email based User Preferences: They enable collecting user preferences on externally hosted pages, particularly for promotional use cases, enhancing easy unsubscription management. As it is evident, MATs provide a good solution for personalized promotional messages at scale to a cohort of users based on their properties or activity / inactivity on the product - building a good argument on why Marketers should use them instead of building one in-house. To some extent, MATs can be used where the product notifications are handful and simple. However, if you still end up building a notification system in-house to accommodate complex usecases, or you are using your current marketing automation tool as a delivery node after handling complex logics at your end, it is advisable to consider adopting a specialized product notification platform. Notification Infrastructure Platforms - A Brief Overview Born from our pain and experience of building notification services in-house in our previous companies, we understand the need and complexities involved. Many companies invest countless hours re-inventing the wheel to get notifications right and sometimes have a dedicated team handling their in-house notifications, even though they're not notification companies. To give an example, you may have read about what goes behind Slack’s simple yet highly effective notifications alerts. Notifications navigate across browsers, devices, channels, statuses, customer preferences, and many other conditions before that sweet Slack chime reaches your ear. Slack Notifications Flowchart This is where SuprSend comes in – we fill the gaps left by MATs and internally built services, and provide a sophisticated infrastructure that allows you to build Slack like notifications without custom development at your end, and help you to deliver the right customer experience. Let’s look at some areas where Notifications Infrastructure Platforms differ from Marketing Automation Tools. Fundamental differences between MATs and NIPs 1. Extended Channels and Integrations Capabilities MATs Limitation: Traditional MATs focus on sending notifications to conventional channels such as push, email and social channels, but lag in adopting newer communication channels. NIPs Solution: NIPs are designed to be integrations first, integrating seamlessly with existing as well as emerging communication channels like Slack, Microsoft Teams, or in-app notification centers. For instance, they allow businesses to send notifications directly to team collaboration tools like Slack in addition to email, ensuring a more comprehensive and up-to-date communication strategy. Not just this, NIPs provide native integration with various data sources (like Segment, Mixpanel, Data warehouses), notification data destinations (like AWS S3, Segment). This flexibility empowers you to effortlessly manage data across platforms of your choice. 2. Real-Time In-App Notification Feed MATs Limitation: MATs typically excel in scheduled or triggered campaigns but lack infrastructure of real-time in-app notification feeds. If they provide, it is a solution that does not look native to your website. This could hinder user engagement within the application. NIPs Solution: NIPs recognize the importance of alerts within app and offer features like real-time in-app notification feed along with out-of-app channels. This ensures delivering a seamless experience, such as if the user is active in the application, they receive alerts within the application, and if offline, will get alerts on out-of-app channels like email or Slack. Besides, NIPs provide pre-built components as well as headless APIs, making it possible to deliver a native looking experience for in-app feed. Try SuprSend Inbox Playground 3. Multi-Tenancy in Notifications MATs Limitation: Marketing Automation Tools (MATs) typically lack robust multi-tenant architecture, making them unsuitable for organizations with enterprise customers. Without multi-tenancy support, MATs do not provide notification customizations (on branding, preferences, vendors etc) tailored to individual tenants' needs. This limitation means engineering teams have to build their own multi-tenant architecture. NIPs Solution: Notification Infrastructure Platforms (NIPs) address this limitation by providing a robust multi-tenant system out of the box. This feature gives flexibility to tailor communication strategies at per-tenant level. You can read more about multi-tenant notifications in our whitepaper. 4. Designing Complex Workflows MATs Limitation: Marketing Automation Tools (MATs) focus on sending campaigns and that’s why they lack support to build intricate workflows with complex logic. The absence of support for multi-stakeholder collaboration, batching, throttling, and webhooks can burden engineering teams with the responsibility of building workflows in the code. NIPs Solution: Notification Infrastructure Platforms (NIPs) excel in handling complex workflows, involving multi-tenant and multiple stakeholders. Besides, NIPs provide intuitive nodes for batching, throttling, delays, channel routing, reminders, webhooks, and much more. With an advanced workflow engine, NIPs engineering & product teams create quality notifications that are delivered at the right time, frequency, and manner, and are sure to delight customers. 5. Advanced Preference Center MATs Approach: Marketing Automation Tools (MATs) typically offer email based unsubscription hosted outside of the product. While this allows users to opt out of specific email communications, it lacks sophistication in managing preferences across multiple channels and categories. NIPs Advantage: Notification Infrastructure Platforms (NIPs) redefine notification preferences with a highly nuanced preference engine where users can set their preferred channel, category or frequency (eg. instant alerts, hourly or daily digest). You can seamlessly integrate a native looking preference center within your product. The NIPs preference center provides a pre-built components as well as APIs with extensive customization options - eg. for tenants, admin, and departments. This granular control ensures that notifications are delivered in alignment with preferences for users and organizations, enhancing overall engagement and satisfaction. 6. Observability and Analytics MATs Limitation: Designed primarily from a campaign perspective, MATs do not provide observability into each and every notification processed. This oversight can pose challenges in debugging and monitoring, particular for mission critical product notifications. NIPs Solution: In contrast, NIPs place a strong emphasis on observability, providing granular logs into each and every notification - at each workflow step executed, failure errors, latencies, and more. They offer integration with monitoring tools like Datadog and NewRelic, enabling real-time alerts in the event of failures. Additionally, companies often require syncing this notification information back to their data stores for further analytics or showing information to their customers, and NIPs provide mechanisms like webhooks, syncing data to S3 bucket, data destinations like Segment to facilitate these requirements. 7. Reliability MATs Limitation: While MATs are capable of handling large volumes necessary for promotional campaigns, they may not offer the same level of reliability needed for critical transactional communications. NIPs Solution: Reliability is a cornerstone for product communications, where delivery of each and every notification becomes important. NIPs incorporate features such as vendor fallback mechanisms, automated retries, and multiple swimlanes to prioritize delivering time sensitive alerts over bulk notifications, ensuring consistent and dependable delivery of notifications in events of failures. 8. Developer-First Approach MATs Limitation: Typically built for marketers, MATs do not give a developer-first approach, limiting the ability to automate the notification development and providing controls that developers would like to have. NIPs Solution: NIPs recognize the importance of automation in building business notifications similar to any other product features. They provide comprehensive APIs & SDKs that empower developers to automate template creation, workflows, preferences, and seamlessly integrate notification processes into their CI/CD pipelines, aligning more closely with modern software development practices. 9. Separate Workspaces MATs Limitation: MATs may lack the capability to provide distinct workspaces for staging and production environments. Works well for marketers to run, test and optimize campaigns in a high-touch process, but not ideal for notifications related to product features. NIPs Solution: NIPs address this limitation by offering separate workspaces for staging and production environments. This ensures a controlled and secure deployment process, allowing businesses to test and refine their notification strategies in a staging environment before rolling them out to the production environment. This allows a more reliable and risk-mitigated deployment process, crucial for organizations with good development practices. 10. Streamlining Notifications in a large organization MATs Limitation: Marketing Automation Tools (MATs) are typically utilized by Marketing and Growth teams, to build and oversee campaign effectiveness. On the contrary, product notifications often originate from multiple product teams within an organization, each responsible for specific features and respective notifications. This decentralized structure can pose challenges in streamlining processes, especially in organizations with multiple teams across different product lines. NIPs Solution: Notification Infrastructure Platforms (NIPs) offer a centralized solution for organizing notifications across various product teams and lines. With tools for managing multiple projects, environments, Role-Based Access Controls (RBACs), permissions, audit trails, and cost centers, NIPs are ideal for managing notifications in complex organizations. This centralized approach ensures efficient coordination and alignment of notification strategies, enhancing overall communication effectiveness and productivity. Conclusion In conclusion, the emergence of notification infrastructure platforms like SuprSend offer a fresh perspective on notification solutions, particularly for modern products. While marketing automation tools can be used to some degree for product notifications, exploring specialized platforms can provide greater control and flexibility for your notification strategies, and you won’t run into rewriting the service after every few years. As you weigh your options, consider your specific needs, such as delivering product-triggered notifications reliably at scale or getting pre-built components for delivering native experiences, or requiring out-of-the-box capabilities to build sophisticated workflows. By doing so, you can choose the platform that is adaptable to your development cycle and empowers your team to deliver exceptional notification experiences. If you're intrigued at this point, we would love to have you explore SuprSend and discover how it can elevate your notification strategy. Watch out this space to learn about how we are uniquely solving engagement notifications. Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/designing-a-scalable-notification-service-architecture-as-developers | Designing a Scalable Notification Service Architecture as Developers Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Engineering Designing a Scalable Notification Service Architecture as Developers Anjali Arya • September 27, 2024 TABLE OF CONTENTS When building a robust notification system , it's crucial to consider various aspects such as scalability, flexibility, and ease of use. Here's a detailed look at designing a notification service architecture that addresses these key requirements: Here's how the SuprSend notification infrastructure functions and handles more than 1 Billion notification triggers every month. SuprSend notification infrastructure handling 1 billion notification triggers every month Notification Service Components Send API : Expose an authenticated API endpoint to trigger sending notifications from any backend or microservice. This API should be designed to handle high volumes of requests and scale horizontally. Supported Channels : The notification service should support sending notifications across various channels, such as email, SMS, push notifications, and in-app messages. This allows users to receive notifications through their preferred channels. User Preferences : Provide a way for users to manage their notification preferences, including choosing channels and setting priorities. This ensures that users only receive notifications they find relevant and valuable. Scalability : Design the notification service to scale horizontally to handle increased traffic and support theoretically unlimited scaling. This can be achieved through techniques like load balancing, message queues, and serverless architectures. Notification Service Architecture Load Balancer : Use a load balancer to distribute incoming requests across multiple worker nodes, ensuring high availability and scalability. Message Queue : Implement a message queue to decouple the notification sending process from the main application logic. This allows the system to handle high volumes of notifications without affecting the performance of other components. Worker Nodes : Deploy worker nodes to process messages from the queue and send notifications to the appropriate channels. These worker nodes should be stateless and easily scalable to handle increased traffic. Channel Adapters : Develop channel adapters to handle the specific requirements of each notification channel, such as email, SMS, and push notifications. These adapters should abstract away the complexities of interacting with third-party services and provide a consistent interface for sending notifications. Notification Templates : Store notification templates in a centralized location, such as a database or a content management system. This allows product and design teams to edit the templates without requiring code changes, improving flexibility and reducing development overhead. Notification Service as a SaaS Building a notification service as a SaaS (Software as a Service) solution offers several advantages: Multi-tenancy : A SaaS notification system can support multiple clients or tenants, each with their own set of users and preferences. This allows the service to be used by various organizations or departments within a larger enterprise. Scalability : SaaS platforms are designed to scale automatically based on demand, ensuring that the notification service can handle increased traffic without manual intervention. Ease of Use : A well-designed SaaS notification system should provide a user-friendly interface for managing notifications, preferences, and reports. This makes it easier for product and design teams to configure and monitor the notification service without relying on developers. Cost-effectiveness : By leveraging the economies of scale and shared infrastructure, a SaaS notification service can be more cost-effective than building and maintaining an in-house solution, especially for smaller organizations. Notification Service Infrastructure Cloud-based Infrastructure : Deploy the notification service on a cloud platform, such as AWS, Google Cloud, or Microsoft Azure. Cloud providers offer scalable and reliable infrastructure, allowing you to focus on building the service rather than managing the underlying hardware and software. Serverless Architecture : Consider using a serverless architecture for the notification service, which can simplify the design and reduce costs. Serverless platforms, such as AWS Lambda or Google Cloud Functions, automatically scale and manage the underlying infrastructure, making it easier to build and deploy scalable applications. Monitoring and Observability : Implement robust monitoring and observability tools to track the performance and health of the notification service. This includes monitoring metrics such as request latency, error rates, and message delivery success rates. Use tools like Amazon CloudWatch, Datadog, or Prometheus to collect and visualize these metrics. By following these best practices and leveraging the power of cloud-based infrastructure and serverless architectures, you can build a scalable, flexible, and cost-effective notification service that meets the needs of your users and organization. Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://design.forem.com/freepixel11 | FreePixel - Design 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 Design Community Close Follow User actions FreePixel FreePixel is a freemium microstock and AI creative platform offering high-quality images and smart AI tools for creators, designers, and businesses. https://www.freepixel.com Location kanpur Joined Joined on Aug 11, 2025 Personal website https://www.freepixel.com More info about @freepixel11 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 9 posts published Comment 0 comments written Tag 0 tags followed Help Center Design Consistency Rules for Trust and Clarity FreePixel FreePixel FreePixel Follow Dec 24 '25 Help Center Design Consistency Rules for Trust and Clarity # helpcenter # uxdesign # customersupport # knowledgebase Comments Add Comment 4 min read Help Center Visual Hierarchy Techniques That Guide User Attention FreePixel FreePixel FreePixel Follow Dec 22 '25 Help Center Visual Hierarchy Techniques That Guide User Attention # helpcenter # uxdesign # visualdesign # customersupport Comments Add Comment 4 min read Help Center Design Systems for Consistent Support Experiences FreePixel FreePixel FreePixel Follow Dec 18 '25 Help Center Design Systems for Consistent Support Experiences # helpcenter # uxdesign # designsystems # customersupport Comments 1 comment 4 min read Build a Self-Service Funnel That Actually Reduces Tickets FreePixel FreePixel FreePixel Follow Nov 21 '25 Build a Self-Service Funnel That Actually Reduces Tickets # customersuccess # documentation # product # ux Comments Add Comment 4 min read Personalized Help Center Experiences Using Customer Data FreePixel FreePixel FreePixel Follow Nov 18 '25 Personalized Help Center Experiences Using Customer Data # helpcenter # customersupport # uxwriting # techwriting Comments Add Comment 3 min read How to Optimize Your Zendesk Help Center for SEO and Visibility FreePixel FreePixel FreePixel Follow Nov 5 '25 How to Optimize Your Zendesk Help Center for SEO and Visibility # zendesk # seo # knowledgebase # support Comments Add Comment 5 min read Improving Customer Loyalty Through Better Help Centre Design FreePixel FreePixel FreePixel Follow Nov 3 '25 Improving Customer Loyalty Through Better Help Centre Design # uxdesign # customerexperience # helpcenter # customerloyalty 1 reaction Comments 1 comment 5 min read Why Batch Background Removal Is the Future of Digital Branding and Product Photography FreePixel FreePixel FreePixel Follow Nov 3 '25 Why Batch Background Removal Is the Future of Digital Branding and Product Photography # ai # design # branding # ecommerce 1 reaction Comments 3 comments 5 min read The Ultimate Checklist for Designing a Zendesk Help Center That Converts FreePixel FreePixel FreePixel Follow Oct 30 '25 The Ultimate Checklist for Designing a Zendesk Help Center That Converts # zendesk # uxdesign # customersupport # saas Comments 1 comment 4 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://twitter.com/intent/tweet?text=%22Building%20a%20Regulatory-Compliant%20Accessibility%20Scanner%3A%20From%20WCAG%20to%20Legal%20Compliance%22%20by%20Labontese%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Flabontese%2Fbuilding-a-regulatory-compliant-accessibility-scanner-from-wcag-to-legal-compliance-38an | 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:49:23 |
https://design.forem.com/design_youtube/jesse-showalter-replit-connectors-f8g#comments | Jesse Showalter: Replit Connectors - Design 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 Design 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 Design YouTube Posted on Oct 19, 2025 Jesse Showalter: Replit Connectors # tools # resources # sideprojects Replit Connectors: A Game-Changer for AI-Assisted Coding Replit’s new Connectors, unveiled with Agent 3, let you build apps and automations directly on top of your own data—turning your AI agent into a true teammate that can jump into the tools you already love. In his video breakdown, Jesse Showalter shows how these Connectors streamline workflows, connect AI to Figma, Framer, Notion, and more, and position Replit as a heavyweight in the AI coding arena. Whether you’re an indie developer, part of a small team, or a creative maker, Connectors promise faster integrations, smarter pipelines, and a more unified dev experience. With your AI no longer confined to simple code suggestions, you get a powerful assistant that actually interacts with your projects in real time. Watch on YouTube 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 Design YouTube Follow Joined Jul 11, 2025 More from Design YouTube Bring Your Own Laptop: Davinci Essentials Course Launch Party! # design # tools # recommendations # resources Bring Your Own Laptop: Elevate Your Designs with Motion (After Effects Tips for Designers) # design # tools # recommendations # resources Jesse Showalter: Beginners Guide to Freelancing # recommendations # resources # sideprojects # career 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://youtube.com/@suprsend | SuprSend - 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, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:49:23 |
https://design.forem.com/gateru/formatting-in-power-bi-4kj9#comments | Putting it All together: Dashboard Design Tips - Design 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 Design 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 Kaira Kelvin. Posted on Dec 18, 2025 Putting it All together: Dashboard Design Tips # baddesign # dataviz # uidesign A complete guide that will help BI developers create Powerful dashboards. At the top, we can see KPI cards, pie chart and slicers in tile form are scattered around. It seems that elements with different purposes are visually together on the same level and we perceive them together ,which can be confusing. The table seems to be placed there at the last moment, roughly compressing the column chart whose labels become rotated and dispro-portionately compressing the line chart showing sales dynamics. The visuals have different proportions,backgrounds and borders, with uneven spacing between them thus creating a sense of chaos. The Visuals also shows lack of organization, a failure to separate elements into logical blocks. To Fix this we will get a version where the same visualization are arranged in a logical structure from general to specific look at the image below. It is quite sufficient for corporate reporting. Making the same dashboard more attractive. Change the standard cards to new ones with category labels at the top and align all elements to the left edge. Add the planned value to the first card. Apply conditional formatting to the deviation indicator in the card. Apply the same font style to all the charts and the table. While working with the table: the header in the previous version(the table header is not the same as the title). Applied the conditional formatting to the cell background for the average price indicator to highlight the highest prices; formatting minimum values with a different background color. Set the background of the main part or set it to the background color of the block. Also add a separator line for the header row and totals. Align all the totals in all the columns exactly below the values (performed in the specific column setting for each indicator separately) Finally the set the background for the page. Place a block shape below the header row to highlight it against the background. After Finalizing on those we get this dashboard The dashboard is divided into several zones, each designated for specific purposes and charts. a. Header(level zero) This includes the title, navigation buttons and individual slicers( or a button to invoke the slicer panel) The header can also contain the company logo, report generation date, and other common elements related to the entire dashboard. b. The first level -KPIS Here the cards are placed. The rule is that we always start the dashboard with card at the top and only cards. Remember that the uses will need to pay attention to the most important information(main KPIs) first and add details to the KPIs c. The Second level- Visulaized subtotals,trends Below the cards on the upper half of the working area.The high level visualizations, categorized by items such as regions and timelines.These visuals also serve as filters and clicking on a column reveals details about it on the next level. d. The Third level - Details In this section we present more granular data usually in tables with conditional formatting. Below is a dashboard information level scheme that guides on how to create a good dashboard. Steps-by-step Guide for a dashboard. Step 1: Place KPI cards on Top It may seem obvious but not everyone adheres to it. I recommend placing no more than six cards at the top as they are key indicators. Do not overload the section , like the image below shows. Instead have the KPIs follow the rule below ... Step Two Define Dashboard Grid. The workspace refers to the page area below the cards, where the tables and charts do sit.The grid is the division of the workspace into blocks(modules) where we place visual elements. A symmetric grid should be achieved. The Image below The most second popular grid for a dashboard consists of six modules which we call the 3X2 meaning three columns plus two rows.The image below shows the grid layouts The image below shows an example of a 3X2 grid.The visual shows three visual elements in its workspace but the chart on the left the sales plan execution chart. The chart is well stretched vertically and occupies two modules while the sales dynamic chart and the table on the right are stretched horizontally and each occupy two modules. The KPIs cards are also well postioned and grouped into three blocks, they are positioned according to the modular grid and aligned relative to the charts below them. Step three Adjust the Page Background. Power BI is not a tool for advanced UI design it is for data and visualization. Customize the color Theme. Under the View tab you will find the various premade color theme options. When you click one of them, all the visuals elements on all the report pages will automaticlly adjust to match the selected theme. Remember the company/corporate colors(brand book) are often used as the working palette. I conclude the dashboard assembly. 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 Kaira Kelvin. Follow A highly decorated savant of the computers Location Nairobi, Kenya Education Dedan Kimathi University of Science and Technology Pronouns He/Him Joined Oct 2, 2023 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://design.forem.com/mitch-narrativeflow | Mitch - Design 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 Design Community Close Follow User actions Mitch Hey there! I'm a narrative designer working on some of the most sophisticated video game stories yet to release. I created NarrativeFlow to help narrative designers tell stories that stand out—fast. Location United States Joined Joined on Sep 17, 2025 Email address mitch@narrativeflow.dev Personal website https://narrativeflow.dev/ github website Education Self-taught Work Narrative Designer | Creator and Co-Owner of NarrativeFlow LLC More info about @mitch-narrativeflow 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 Vue.js, JavaScript, HTML, CSS, C++, Memberstack, Astro.build, SaaS product development, narrative design for games. Technologist with a focus on bridging tech + storytelling. Currently learning Translated code into Lua, Python, C++, C#, GML, GDScript, and JavaScript, and now exploring Rust. Recently learned Memberstack and Astro's framework (highly recommend!) for my SaaS. Currently hacking on Building NarrativeFlow, a visual narrative design tool for game creators and narrative designers. Currently focused on implementing translation features and UX improvements, in addition to writing. Available for Always happy to chat about narrative design, indie game dev workflows, SaaS tools, or startup building. Open to feedback exchanges, or just sharing ideas with other devs and narrative designers! Post 2 posts published Comment 0 comments written Tag 0 tags followed Why Visual Narrative Design — Designing Your Dialogue Visually is Better for Your Creativity and Time Mitch Mitch Mitch Follow Dec 12 '25 Why Visual Narrative Design — Designing Your Dialogue Visually is Better for Your Creativity and Time Comments Add Comment 4 min read How to Write Branching Dialogue Without Code (and Stay in Your Creative Flow) Mitch Mitch Mitch Follow Oct 15 '25 How to Write Branching Dialogue Without Code (and Stay in Your Creative Flow) # tools # resources # nocode # designprocess Comments Add Comment 5 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://atproto.com/sdks | SDKs - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Official libraries Community libraries Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme SDKs Official libraries Typescript Created by Bluesky Social PBC. Works on Web, NodeJS, and React Native. http client identifiers bsky crypto mst lexicon identity streaming service auth plc oauth server Go Created by Bluesky Social PBC. http client identifiers bsky crypto mst lexicon identity streaming service auth plc oauth server Community libraries Python Created by @marshal.dev. http client identifiers bsky crypto mst lexicon identity streaming service auth plc oauth server Previous ATProto Ethos Next Glossary © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://atproto.com/specs/label | Labels - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Labels Labels are a form of metadata about any account or content in the atproto ecosystem. They exist as free-standing, self-authenticated data objects, though they are also frequently distributed as part of API responses (in which context the signatures might not be included). Additionally, label "values" may be directly embedded in records themselves ("self-labels"). Labels primarily consist of a source (DID), a subject (URI), and value. The value is a short string, similar to a tag or hashtag, which presumably has pre-defined semantics shared between the creator and consumer of the label. Additional metadata fields can give additional context, but at any point of time there should be only one coherent set of metadata for the combination of source, subject, and value. If there are multiple sets of metadata, the created-at timestamp is used to clarify which label is current. The label concept and protocol primitive is flexible in scope, use cases, and data transport. One of the original design motivations was to enable some forms of composable moderation, with labels generated by moderation services. But labels are not moderation-exclusive, and may be reused freely for other purposes in atproto applications. The core label schema is versioned, and this document describes labels version 1 . Schema and Data Model Labels are protocol objects, similar to repository commits or MST nodes. They are canonically encoded as DAG-CBOR (a strict, normalized subset of CBOR) for for signing (see sections below). There is a Lexicon definition ( com.atproto.label.defs#label ) which represents labels, but it has slightly different field requirements than the core protocol object: the version field ( ver ) and signature ( sig ) are both optional in that version. The fields on the label object are: ver (integer, required): label schema version. Current version is always 1 . src (string, DID format, required): the authority (account) which generated this label uri (string, URI format, required): the content that this label applies to. For a specific record, an at:// URI. For an account, the did: . cid (string, CID format, optional): if provided, the label applies to a specific version of the subject uri val (string, 128 bytes max, required): the value of the label. Semantics and preferred syntax discussed below. neg (boolean, optional): if true , indicates that this label "negates" an earlier label with the same src , uri , and val . cts (string, datetime format, required): the created-at timestamp for the label. Note that timestamps in a distributed system are not trustworthy or verified by default. exp (string, datetime format, optional): a timestamp at which this label expires (is not longer valid) sig (bytes, optional): cryptographic signature bytes. Uses the bytes type from the Data Model , which encodes in JSON as a $bytes object with base64 encoding When labels are being transferred as full objects between services, the ver and sig fields are required. If the neg field is false , best practice is to simply not include the field at all. The use of short three-character field names is different from most parts of atproto, and aligns more closely with JWTs. The motivation for this difference is to minimize the size of labels when many of them are included in network requests and responses. Value The val field is core to the label. To keep the protocol flexible, and allow future development of ontologies, norms, and governance structures, very little about the semantics, behavior, and known values of this string are specified here. The current expectation is that label value strings are "tokens" with fixed vocabulary. They are similar to hashtags. At this time, we strongly recommend against the following patterns: packing additional structure in to value fields. for example, base64-encoded data, key/value syntax, lists or arrays of values, etc encoding arbitrary numerical values (eg, "scores" or "confidence") using punctuation characters (like . , : , ; , # , _ , ' , > , or others) to structure the namespace of labels using URLs or URIs in values use of any whitespace use of non-ASCII characters, including emoji These are all promising ideas, but we hope to coordinate and more formally specify this sort of syntax extension. One current convention is to use a bang punctuation character ( ! ) as a prefix for system-level labels which specify an expected behavior on a subject, but don't describe the content or indicate a reason for the behavior. For example, !warn as a behavior, as opposed to scam as a descriptive label which might result in the same warning behavior. The behavior, definition, meaning, and policies around labels are generally communicated elsewhere. The value does not need to be entirely descriptive. Recommended String Syntax The current recommended syntax for label strings is lower-case kebab-syntax (using - internally), using only ASCII letters. Specifically: lower-case alphabetical ASCII letters ( a to z ) dash ( - ) used for internal separation, but not as a first or last character no other punctuation or whitespace 128 bytes maximum length. Shorter is better (try to keep labels to a couple dozen characters at most), while still being somewhat descriptive. Label Lifecycle: Negation and Expiration Labels are generally broadcast and persisted internally by receiving services. Some services may bulk re-broadcast or re-distribute labels to downstream services. They may ignore and drop any labels which are not relevant to their use-case. They may "hydrate" labels in to requests from clients. When hydrating labels, services should generally only include "active" and relevant labels. If the authoritative creator of a label wishes to retract or remove the label, they do so by publishing a new label with the same source, subject, and value, but with the negated field ( neg ) set to true, and a current timestamp (later than any previous timestamps). A negation label does not mean that the inverse of the label is “true”, only that the previous label has been retracted. For example, a label with value spam and neg true does not mean the subject is not spam, only that a previous spam label should be disregarded. Receiving services that encounter a valid negation label may store the negation internally, and may re-broadcast the negation, but should not hydrate the negated label in API responses. Likewise, may continue to persist expired labels (after the expiration timestamp), but should not continue to hydrate them in API responses. Signatures Labels are signed using public-key Cryptography , similar to repository commit objects. Signatures should be validated when labels are transferred between services. It is assumed that most end-clients will not validate signatures themselves, and signatures may be removed from API responses sent to clients for network efficiency. Clients and other parties should have a mechanism to verify signatures, by querying individual signatures from labeling authorities, and receiving back the full label, including signature. The process to sign or verify a signature is to construct a complete version of the label, using only the specified schema fields, and not including the sig field. This means including the ver field, but not any $type field or other un-specified fields which may have been included in a Lexicon representation of the label. This data object is then encoded in CBOR, following the deterministic IPLD/DAG-CBOR normalization rules. The CBOR bytes are hashed with SHA-256, and then the direct hash bytes (not a hex-encoded string) are signed (or verified) using the appropriate cryptographic key. The signature bytes are stored in the sig field as bytes (see Data Model for details representing bytes). The key used for signing labels is found in the DID document for the issuing identity, and has fragment identifier #atproto_label . This key may have the same value as the #atproto signing key used for repository signatures. At this time, if an #atproto_label key is not found, implementation should not attempt to use other keys present in the DID document to verify the signature, they should simply consider the signature invalid and ignore the label. Signature Lifecycle Signatures are verified at the time the label is received. They do not need to be re-verified before hydration in to API responses. Signing key rotation can be difficult and disruptive for a large labeling service. The rough mechanism for doing a rotation is: labeling services should persist signatures alongside labels, and also persist an indicator of which key was used to sign the label when starting a rotation, pause creation and signing of new signatures update the DID document with the new key resume signing new labels with the new key when servicing queries for old labels, check which key was used for signing. if out of date, re-sign and persist the signatures for that batch of labels. the created-at timestamp should not be changed. older labels in the label event stream backfill period may have invalid signatures; this is acceptable When encountering a label with an invalid signature, a good practice is to re-resolve the issuer identity (DID document) and check if there is an updated signing key. If there is, validation should be retried. A downstream service can decide for themselves whether to bulk query and receive updated signatures when an upstream key rotation has occurred; or to fetch updated signatures on demand; or to consider old labels still valid even if the signature no longer validates against the current label signing key. Self-Labels in Records One Lexicon design pattern is to include an array of label values inside a record. Downstream clients can interpret these as "self-labels", similarly to labels coming from external sources. Note that the repository data storage mechanism provides context and lifecycle support similar to a full label object: the source of the label is the account controlling the repository the subject is the record itself, or possibly the overall repository account (depending on context) the CID is the current version of the record negation and expiration are not necessary, as the record can be deleted or updated to change the set of labels the created-at timestamp would be the same as the record itself (eg, via a createdAt field) authenticity (signature) is provided by the repository commit signing mechanism Labeler Service Identity Labeler services each have a service identity, meaning a DID document. This is the DID that appears in label source ( src ) field. The DID document will also have a key used for signing labels (with ID #atproto_label ; see above for signature details), and a service endpoint (with ID #atproto_labeler and type AtprotoLabeler ) which indicates the server URL (the URL includes method, hostname, and optional port, but no path segment at this time). Note that in real world use-cases, use of HTTPS on the default port (443) is strongly recommended and may be required by service operators. Depending on the application, the identity may also have an atproto repository containing a “declaration record” which describes application-specific context about the labeler. This may be required for integration with a specific application, client, or AppView, but is not a requirement at the base atproto level. Label Distribution Endpoints Two Lexicon endpoints are defined for labeler services to distribute labels: com.atproto.label.subscribeLabels : an event stream (WebSocket) endpoint, which broadcasts new labels. Implements the seq backfill mechanism, similar to repository event stream, but with some small differences: the “backfill” period may extend to cursor=0 (meaning that the full history of labels is available via the stream). Labels which have been redacted have the original label removed from the stream, but the negation remains. com.atproto.label.queryLabels : a flexible query endpoint. Can be used to scroll over all labels (using a cursor parameter), or can filter to labels relating to a specific subject. Note that unlike public repository content, labels are not required to be publicly enumerable. It is acceptable for labeler services to make all labels publicly available using these endpoints, or to require authorization and access control, or to not implement these endpoints at all (if they have another mechanism for distributing labels). Labeler HTTP Headers Labels are often “hydrated” in to HTTP API responses by atproto services, such as AppViews. To give clients control over which label sources they want included, two special HTTP headers are used, which PDS implementations are expected to pass-through when proxying requests: atproto-accept-labelers : used in requests. A list of labeler service DIDs, with optional per-DID flags. atproto-content-labelers : used in responses. Same content, syntax, and semantics as the accept header, but indicates which labelers could actually be queried. Presence in this header doesn’t mean that any labels from a given DID were actually included, only that it they would have been if such labels existed. The syntax of these headers follows IETF RFC-8941 (”Structured Field Values for HTTP”), section 3.1.2 (”Parameters”). Values are separated by comma (ASCII , character), and values from repeated declaration of the header should be merged in to a single list. One or more optional parameters may follow the item value (the DID), separated by a semicolon (ASCII ; character). For boolean parameters, the full RFC syntax (just as param=?0 for false) is not currently supported. Instead, the presence of the parameter indicates it is “true”, and the absence indicates “false”. No other parameter values types (such as integers or strings) are supported at this time. The only currently supported parameter is the boolean parameter redact . This flag indicates that the service hydrating labels should handle the special protocol-level label values !takedown and !suspend by entirely redacting content from the API response, instead of simply labeling it. This may result in an application-specific tombstone entry, which might indicate the Labeler responsible for the redaction, or could result in the content being removed without a tombstone. Complete example syntax for these headers: # on a request atproto-accept-labelers: did:web:mod.example.com;redact, did:plc:abc123, did:plc:xyz789 # on a response: atproto-content-labelers: did:web:mod.example.com;redact, did:plc:abc123, did:plc:xyz789 Copy Copied! If the syntax of the request header is invalid or can not be parsed, the service should return an error instead of ignoring the header. If a labeler DID is repeated in the header, parameters should be combined from each instance. For example, if a DID is included once with redact and once without, the service should treat this the same as if the DID was included once, with redact . The atproto-content-labelers response header should represent how the request header was de-duplicated and interpreted. If the request header is not supplied at all, the service may substitute a default. This is distinct from supplying the header with no value, in which case the service should not hydrate or apply any labels. If any labeler DID is indicated with correct syntax, but the identity does not exist; does not include labeler service or key entries in the DID doc; has been taken down at the service level; or is otherwise inactive or non-functional; then that labeler should not be included in the atproto-content-labelers response header, but does not need to be treated as an error. A service implementation may decide, as a policy matter, that specific conditions must be met or the request will error. For example, that a specific labeler DID must be included; or a minimum or maximum number of labelers can be included; or a minimum or maximum number of labelers with redact are included. Security Considerations Note that there is no "domain differentiation" of the signature, meaning that there is potential security risk of signing a label which is also a valid object (and signature) in an entirely different context, like an authentication bearer token. This makes it important to ensure that no additional or unexpected fields are included in the object that is being signed. Usage and Implementation Guidelines It is strongly recommended to stick to the “recommended string syntax” for label values at this time. Possible Future Changes More mature governance, namespacing, and style guide recommendations on label values. Previous Blobs Next HTTP API (XRPC) © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://open.forem.com/privacy#b-information-collected-automatically | Privacy Policy - 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 Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 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:49:23 |
https://www.suprsend.com/post/in-app-notification-vs-push-notifications-which-notification-channel-is-better-for-product-communication-in-2024 | In-App Notification VS Push Notifications - Which Notification Channel is Better For Product Communication in 2024? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Inapp Inbox Notifications In-App Notification VS Push Notifications - Which Notification Channel is Better For Product Communication in 2024? Nikita Navral • October 26, 2024 TABLE OF CONTENTS With a rise in the need for an effective business communication channel, in-app Inbox notification emerges as a transformative solution, seamlessly integrating the strengths of mobile and web push notifications. The need for such innovation is evident in the statistics from hbr.org , revealing that 73% of consumers engage with a single retailer through multiple communication channels. In-app inbox messaging allows users to revisit messages at their convenience, reducing the urgency associated with traditional push notifications. The notification center becomes a repository, ensuring messages are accessible until they lose relevance. Check out the 5 Mobile Inbox Transactional Use-Cases That Businesses Are Using To Improve Customer Engagement. Understanding Push Notifications: Push notifications, a widely adopted communication tool, face challenges such as high dismiss rates and oversaturation. Smartphone users receive an average of 46 push notifications per day , making it essential to explore alternatives. Comparative Analysis: App Inbox vs Push Notifications: Let's delve into a detailed comparison, exploring the technical nuances of App Inbox messaging and push notifications. 1. Subscription Process: Feature App Inbox Push Notifications Setup Process Utilizes an authentication token and a single script. Users must subscribe on the web/app. User Opt-in Not explicitly required. Necessary for message delivery. 2. Appearance and Disappearance: Feature App Inbox Push Notifications Message Storage Saved in the notification center. Displayed within a specified period. Message Persistence Allows users to return at their convenience. Message is not persistent; user can dismiss, and the notification will be lost. 3. Tech Implementation & Compatibility: Feature App Inbox Push Notifications Platform Compatibility Universal on both iOS, web, and Android. Differences in compatibility between iOS, web, and Android. Even different for different web browsers. 4. User Interaction: Feature App Inbox Push Notifications User Control Allows users to return at their convenience. Interaction opens a page; notification disappears post-interaction. 5. Storage and Accessibility: Feature App Inbox Push Notifications Message Location All notifications are located in the user's account. Shown along with other push notifications. Use Cases: When to Choose App Inbox or Push Notifications: Check out when should you use push notifications and when to use in-app inbox notifications in your product along with some sample examples. Apart from these, you would also need to figure out your queuing system to incorporate the flow of these events here Choosing The Right Message Queue Technology For Your Notification System. Feature App Inbox Push Notifications Ideal For Time-sensitive promotions, discounts, and immediate attention Long-term notifications, continuous communication, and accessibility Example Use Case Delivering personalized product recommendations for users where users need to revisit Sending a flash sale alert, OTP Technical Insights - In-App Inbox Setup: Incorporating App Inbox messaging into your communication strategy involves a straightforward process with key technical insights. Natively, it requires a backend infrastructure, a front-end notification inbox, and a connection between the two using socket.io, making it a complex task. However, this process is significantly simplified with SuprSend, making implementing an in-app inbox much more accessible. In two steps, you can get started with SuprSend. Script Installation: Use a single script for App Inbox setup, providing access to advanced features. Example Code: Do you know How Mobile Inbox Increases User Engagement? (including a case study with inapp-inbox)? User Authentication: Messages are accessible to authorized users without the need for a separate subscription process. Example Code: Check out the documentation: Overview (suprsend.com) Explore InApp Inbox Before Use! Technical Insights - Push Notification Setup: For businesses considering push notifications, here are some technical aspects to keep in mind: Firebase Integration: Push notifications require the creation of a project in Firebase and association with the ESP for functionality. Example Code: Token Usage: Push notifications use push tokens for sending messages, necessitating users to subscribe on the website. Example Code: All these are quite complex to maintain in code, and even more difficult if you have multi-tenancy use-cases. That’s where SuprSend simplifies it by having a single dashboard for you to add your preferred push notification vendor, create templates and codes via API or frontend editor, manage workflows via API, manage multi-tenants and have complete observability on the dashboard. Conclusion: In conclusion, the choice between App Inbox and push notifications depends on the specific communication needs of a business. While push notifications excel in immediate and attention-grabbing scenarios, App Inbox offers a user-centric approach, making it ideal for long-term promotions and continuous engagement. Check more: Mobile In-App Inboxes Have 17% Higher Click Rates Than Push Notifications. Why It Should Bother Product Teams? Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/announcing-our-soc-2-compliance-certification-suprsend | Announcing our SOC 2 Type 2 Compliance Certification @SuprSend Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Engineering Announcing our SOC 2 Type 2 Compliance Certification @SuprSend Gaurav Verma • February 5, 2025 TABLE OF CONTENTS At SuprSend, we have consistently prioritized the security of our customers' data, and today, we are thrilled to announce a significant achievement in this ongoing commitment – the attainment of SOC 2 Type 2 certification. What is SOC 2? SOC 2, developed by the American Institute of Certified Public Accountants (AICPA), is a widely recognized framework for managing and securing sensitive data. It focuses on criteria such as Security, Availability, and Confidentiality, providing a robust benchmark for service organizations. Our Journey to Certification Our journey towards SOC 2 compliance has been rigorous and thorough. The certification process involves a systematic examination of our security practices, processes, and controls by an independent, third-party licensed accounting and auditing firm. This scrutiny ensures that we not only meet but exceed industry standards in safeguarding your valuable data. Key Achievements On 25th Feb 2024, SuprSend successfully passed the SOC 2 Type 2 audit, earning certification in recognition of our commitment to maintaining the highest standards of security. This certification covers essential principles, including Security, Availability, and Confidentiality, signifying that our platform adheres to the stringent AICPA SOC 2 standard. Apart from that we are also HIPPA and GDPR compliant. What This Means for You As a SuprSend user, this certification offers you the assurance that your data is handled within a controlled and audited environment. The SOC 2 Type 2 examination serves as a guarantee that we prioritize these aspects of your information continuously over a prolonged period of time. Security Availability Processing integrity Confidentiality Privacy "We are thrilled to announce that SuprSend has achieved SOC2 Type 2 compliance, a testament to our unwavering commitment to data security and privacy. This milestone is not just a badge of honor; it reflects our dedication to building a trustworthy and secure platform for our customers. In today's digital landscape, protecting our users' information is not just a responsibility, but a cornerstone of our business ethos. As we continue to innovate and grow, our customers can remain confident that their data is in safe hands, upheld by the highest standards of security compliance." Gaurav Verma, Cofounder and CTO at SuprSend Our Future Roadmap: ISO Certifications Our journey doesn't conclude with the SOC 2 Type 2 certification. We are committed to maintaining these high standards and are actively preparing for the ISO certifications. This ongoing evaluation ensures that we continuously meet and exceed the expectations set by the AICPA , providing our users with the utmost confidence in our platform. In case of any questions or concerns around our product security and compliance, you can email directly at nikita@suprsend.com or join our community here: 24*7 Support Community Share this blog on: Written by: Gaurav Verma Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://atproto.com/articles/atproto-for-distsys-engineers | ATProto for distributed systems engineers - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme ATProto for distributed systems engineers Sep 3, 2024 AT Protocol is the tech developed at Bluesky for open social networking. In this article we're going to explore AT Proto from the perspective of distributed backend engineering. If you've ever built a backend with stream-processing , then you're familiar with the kind of systems we'll be exploring. If you're not — no worries! We'll step through it. Scaling the traditional Web backend The classic, happy Web architecture is the “one big SQL database” behind our app server. The app talks to the database and handles requests from the frontend. As our application grows, we hit some performance limits so we toss some caches into the stack. Then let's say we scale our database horizontally through sharding and replicas. This is pretty good, but we're building a social network with hundreds of millions of users; even this model hits limits. The problem is that our SQL database is “ strongly consistent ” which means the state is kept uniformly in sync across the system. Maintaining strong consistency incurs a performance cost which becomes our bottleneck. If we can relax our system to use “ eventual consistency ,” we can scale much further. We start by switching to a NoSQL cluster. This is better for scaling, but without SQL it's becoming harder to build our queries. It turns out that SQL databases have a lot of useful features, like JOIN and aggregation queries. In fact, our NoSQL database is really just a key-value store. Writing features is becoming a pain! To fix this, we need to write programs which generate precomputed views of our dataset. These views are essentially like cached queries. We even duplicate the canonical data into these views so they're very fast. We'll call these our View servers. Now we notice that keeping our view servers synced with the canonical data in the NoSQL cluster is tricky. Sometimes our view servers crash and miss updates. We need to make sure that our views stay reliably up-to-date. To solve this, we introduce an event log (such as Kafka ). That log records and broadcasts all the changes to the NoSQL cluster. Our view servers listen to — and replay — that log to ensure they never miss an update, even when they need to restart. We've now arrived at a stream processing architecture , and while there are a lot more details we could cover, this is enough for now. The good news is that this architecture scales pretty well. We've given up strong consistency and sometimes our read queries lag behind the most up to date version of the data, but the service doesn't drop writes or enter an incorrect state. In a way, what we've done is custom-built a database by turning it inside-out . We simplified the canonical storage into a NoSQL cluster, and then built our own querying engine with the view servers. It's a lot less convenient to build with, but it scales. Decentralizing our high-scale backend The goal of AT Protocol is to interconnect applications so that their backends share state, including user accounts and content. How can we do that? If we look at our diagram, we can see that most of the system is isolated from the outside world, with only the App server providing a public interface. Our goal is to break this isolation down so that other people can join our NoSQL cluster, our event log, our view servers, and so on. Here's how it's going to look: Each of these internal services are now external services. They have public APIs which anybody can consume. On top of that, anybody can create their own instances of these services. Our goal is to make it so anybody can contribute to this decentralized backend. That means that we don't just want one NoSQL cluster, or one View server. We want lots of these servers working together. So really it's more like this: So how do we make all of these services work together? Unifying the data model We're going to establish a shared data model called the “user data repository.” Every data repository contains JSON documents, which we'll call “records”. For organizational purposes, we'll bucket these records into “collections.” Now we're going to opinionate our NoSQL services so they all use this data repository model. Remember: the data repo services are still basically NoSQL stores, it's just that they're now organized in a very specific way: Each user has a data repository. Each repository has collections. Each collection is an ordered K/V store of JSON documents. Since the data repositories can be hosted by anybody, we need to give them URLs . While we're at it, let's create a whole URL scheme for our records too. Great! Also, since we're going to be syncing these records around the Internet, it would be a good idea to cryptographically sign them so that we know they're authentic. Charting the flow of data Now that we've set up our high-scale decentralized backend, let's map out how an application actually works on ATProto. Since we're making a new app, we're going to want two things: an app server (which hosts our API & frontend) and a view server (which collects data from the network for us). We often bundle the app & view servers, and so we can just call it an “Appview.” Let's start there: A user logs into our app using OAuth. In the process, they tell us which server hosts their data repository, and they give us permission to read and write to it. We're off to a good start — we can read and write JSON documents in the user's repo. If they already have data from other apps (like a profile) we can read that data too. If we were building a singleplayer app, we'd already be done. But let's chart what happens when we write a JSON document. This commits the document to the repo, then fires off a write into the event logs which are listening to the repo. From there, the event gets sent to any view services that are listening — including our own! Why are we listening to the event stream if we're the one making the write? Because we're not the only ones making writes! There are lots of user repos generating events, and lots of apps writing to them! So we can see a kind of circular data flow throughout our decentralized backend, with writes being committed to the data repos, then emitted through the event logs into the view servers, where they can be read by our applications. And (one hopes) that this network continues to scale: not just to add capacity, but to create a wider variety of applications sharing in this open applications network. Building practical open systems The AT Protocol merges p2p tech with high-scale systems practices. Our founding engineers were core IPFS and Dat engineers, and Martin Kleppmann — the author of Data Intensive Applications — is an active technical advisor. Before Bluesky was started, we established a clear requirement of “no steps backwards.” We wanted the network to feel as convenient and global as every social app before it, while still working as an open network. This is why, when we looked at federation and blockchains, the scaling limits of those architectures stood out to us. Our solution was to take standard practices for high scale backends, and then apply the techniques we used in peer-to-peer systems to create an open network. Ready to learn more? Specs, guides, and SDKs can be found here. Previous Cookbook ⧉ Next Overview © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://design.forem.com/yzg/seeking-feedback-on-custom-blogger-templates-what-do-you-need-40em#comments | Seeking Feedback on Custom Blogger Templates - What Do You Need? - Design 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 Design 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 Yanuar Zhaldy Gemilang Posted on Dec 17, 2025 Seeking Feedback on Custom Blogger Templates - What Do You Need? # cms # userresearch # webdesign Seeking Feedback on Custom Blogger Templates - What Do You Need? Hey, I'm a template creator specializing in Blogger themes for various niches and purposes. I've been designing and customizing templates to help bloggers get a professional look without the hassle. I'm looking to expand my offerings and would love your input to make sure I'm creating what the community actually wants. If you're a Blogger user or interested in templates, please share your thoughts: What types of themes are you most in need of? (e.g., minimalist personal blogs, e-commerce style for affiliate sites, news/magazine layouts, portfolio for creatives, tech/gadget reviews, etc.) Feel free to specify niches like fitness, travel, food, or anything else! What do you think is a fair price range for a premium Blogger template? (Considering features like responsive design, SEO optimization, custom widgets, easy installation, and ongoing support.) Are there any popular websites whose design you'd like to emulate? (Please describe them without sharing live links - e.g., "a clean, grid-based layout like that famous photography site" or "the sleek navigation of a well-known tech blog.") Your feedback will help me prioritize and create better templates. Thanks in advance for your suggestions - looking forward to hearing from you! 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 Liam Carter Liam Carter Liam Carter Follow I work in digital marketing and regularly use different SaaS tools for campaign management, CRM, and analytics. I like testing new platforms and giving honest feedback based on real use cases. Joined Dec 9, 2025 • Dec 17 '25 Dropdown menu Copy link Hide Nice initiative! For me, I’d love to see clean, minimalist templates that are easy to customize for personal blogs or small niches like travel and food. Responsive design and SEO optimization are definitely key. A fair price for a premium template would be around $20–$40, depending on features. Looking forward to seeing what you come up with! 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 Yanuar Zhaldy Gemilang Follow Hello, I am Yanuar Zhaldy Gemilang, a Content Creator and Blogger Enthusiast who focuses on creating high-quality Blogger templates. I am the founder of YzTheme. Location Pondok Cabe Udik, Tangerang Selatan Work Web Maintainers Joined Mar 17, 2021 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://atproto.com#looking-for-the-bluesky-api-docs | AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Welcome to the Atmosphere The AT Protocol is an open, decentralized network for building social applications. Quickstart Explore SDKs Guides Quickstart Create an application and start building. Read more Self-host Learn how to set up your own personal data server. Read more Glossary Definitions for all the terminology used in AT Protocol. Read more FAQ Frequently Asked Questions about the Atmosphere. Read more Specs Repository Self-authenticating storage for public account content. Lexicon A schema definition language for ATProto. HTTP API (XRPC) Cross-system queries and procedures over HTTP. URI Scheme A URI scheme for addressing ATProto repository data. Learn more Guide Glossary of terms What's a PDS? an AppView? a DID? If you're feeling a little bowled over by new concepts, give this glossary a look. Keep reading Guide The fast intro to building on ATProto In this guide, we build a simple multi-user app that publishes your current "status" as an emoji. Keep reading Article ATProto for distributed systems engineers In this article we explore AT Proto from the perspective of distributed backend engineering. Keep reading Guide What is Lexicon, and how do I use it to make a schema? This guide will introduce you to Lexicon and get you started with building your own schemas. Keep reading Article ATProto Ethos A deep dive into the philosophical and aesthetic principles underlying the design of AT Protocol. Keep reading Web Without Walls - Talk at React Universe 2024 Talk An introduction to the AT Protocol presented by Dan Abramov at React Universe Conf 2024 Make Identity Central Again, with Bluesky's Jay Graber Interview An interview between Jay Graber and Flipboard CEO Mike McCue about making social more like the Web. Bluesky and the AT Protocol: Usable Decentralized Social Media Whitepaper A whitepaper authored by Martin Kleppman and the AT Protocol team. Looking for the Bluesky API docs? Go to docs.bsky.app for Bluesky-specific documentation. Next ATProto Ethos © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://design.forem.com/t/freelancing#main-content | Freelancing - Design 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 Design Community Close # freelancing Follow Hide The business of design: clients, contracts, and pricing Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The "Quick Question" That Tells Me Everything Tanya Donska Tanya Donska Tanya Donska Follow Dec 22 '25 The "Quick Question" That Tells Me Everything # design # freelancing # resources # webdesign Comments Add Comment 5 min read Your Sports Coaching Website Doesn’t Work For You? Per Starke Per Starke Per Starke Follow Oct 23 '25 Your Sports Coaching Website Doesn’t Work For You? # coach # portfolio # freelancing # webdesign Comments Add Comment 2 min read Offering Free Website Design to Gain Real-World Experience" Zoey Zoey Zoey Follow Nov 12 '25 Offering Free Website Design to Gain Real-World Experience" # freelancing # portfolio # webdesign # newdesigner 1 reaction Comments 2 comments 1 min read Smart Strategies to Sell AI-Generated Art Across Multiple POD Platforms Ai Digital Visionary Ai Digital Visionary Ai Digital Visionary Follow Oct 26 '25 Smart Strategies to Sell AI-Generated Art Across Multiple POD Platforms # printdesign # freelancing # aiindesign # resources 1 reaction Comments Add Comment 13 min read Why Personality Matters on Your Website – Even for Large Companies and Non-Personal Brands Per Starke Per Starke Per Starke Follow Oct 23 '25 Why Personality Matters on Your Website – Even for Large Companies and Non-Personal Brands # webdesign # trust # personality # freelancing 1 reaction Comments Add Comment 6 min read loading... trending guides/resources The "Quick Question" That Tells Me Everything 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/build-reliable-transactional-email-sms-systems-with-suprsend | Build Reliable Transactional Email & SMS Systems with SuprSend Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Notification Infrastructure Build Reliable Transactional Email & SMS Systems with SuprSend Nikita Navral • November 13, 2025 TABLE OF CONTENTS When users reset a password, confirm a purchase, or receive an OTP, every millisecond matters. Transactional messaging is about trust, security, and reliability . SuprSend helps product and engineering teams deliver these messages instantly, across email and SMS , with complete visibility and fallback logic built in. What Are Transactional Email & SMS Systems? Transactional messaging platforms power mission-critical communication triggered by real-time events: like sign-ups, payment confirmations, and alerts. The best systems prioritize: Feature / Metric Why It Matters How SuprSend Solves It Global SMS Coverage & Routing Quality SMS reliability varies by region; optimized carrier routing ensures fast, consistent delivery. SuprSend integrates with Twilio, Exotel, Sinch, Karix, and Gupshup - automatically selecting the fastest route per geography to ensure <200 ms latency for OTPs and alerts. Email Deliverability & Reputation High inbox rates require trusted infrastructure: SPF, DKIM, IP reputation, and feedback loops. SuprSend connects with SendGrid, Mailgun, SES, and Postmark, managing DKIM/SPF and IP Pools. Unified logs provide delivery, bounce, and open tracking for complete visibility. Unified API & SDKs Developers shouldn’t rebuild channel logic separately for each provider. A single API handles both email and SMS with consistent payloads. SDKs in Python, Node.js, Java, Go, and Flutter make integration fast and maintainable. Fallback & Orchestration Logic Critical updates must reach users even if one channel fails. Smart Routing automatically retries and falls back between channels (e.g., email → SMS) when delivery fails, guaranteeing reach without duplicates. Analytics & Tracking Visibility into delivery, opens, and failures enables proactive fixes and optimization. Analytics 2.0 unifies logs for all messages, email and SMS, with real-time status, latency metrics, and workflow-level comparisons. Compliance & Consent Support SMS and email laws vary by country; compliance prevents blocking and penalties. SuprSend’s preference APIs and hosted unsubscribe pages automate consent management. GDPR, HIPAA, and CPRA compliance are built-in. Scalability & Pricing Model Costs should scale predictably as message volume grows. Usage-based pricing scales with your growth, no fixed annual lock-ins. SuprSend supports startups and enterprises handling millions of messages daily. Why Product Teams Choose SuprSend for Transactional Messaging Single Integration, Infinite Channels: Email, SMS, push, inbox, Slack, Teams: all unified through one API. <200 ms Average Latency: Ideal for OTPs, verification codes, and alerts. Real-Time Debugging: Message-level logs show delivery, open, and failure reasons instantly. Smart Retries & Failovers: Built-in orchestration ensures reliability even during vendor downtime. Observability & Schema Validation: Prevent malformed payloads before they reach users. Multi-Tenant & White-Label Ready: Perfect for platforms needing per-customer branding and provider routing. Proven in Production Companies like Freightify , Teachmint , and Delightree use SuprSend to power mission-critical transactional notificationsc, cutting onboarding time by weeks, improving deliverability, and driving 2–3× higher engagement across email and SMS. 👉 Learn more at SuprSend.com Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://design.forem.com/egledigital | Karina Egle - Design 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 Design Community Close Follow User actions Karina Egle SEO, content, digital products. Location Riga, Latvia Joined Joined on Mar 13, 2025 More info about @egledigital 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 2 posts published Comment 1 comment written Tag 0 tags followed Emerging graphic design trends for 2026 Karina Egle Karina Egle Karina Egle Follow Nov 13 '25 Emerging graphic design trends for 2026 # design # recommendations # webdesign # graphicdesign Comments Add Comment 2 min read Want to connect with Karina Egle? Create an account to connect with Karina Egle. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in How UX in 2025 became more about intent than interaction Karina Egle Karina Egle Karina Egle Follow Oct 23 '25 How UX in 2025 became more about intent than interaction # design # uxdesign # uidesign # webdesign 9 reactions Comments 1 comment 4 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/how-redis-solved-our-challenges-with-dynamic-task-scheduling-and-concurrent-execution-developers-guide | How Redis Solved Our Challenges with Dynamic Task Scheduling and Concurrent Execution? [Developer's Guide] Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Engineering How Redis Solved Our Challenges with Dynamic Task Scheduling and Concurrent Execution? [Developer's Guide] Praveen • February 5, 2025 TABLE OF CONTENTS The problem statement was simple, or so we thought. In our previous setup, we used goroutines for scheduling database queries, allowing us to run the whole setup on minimal setup with SQLite and go service. Seems simple enough, but when we decided to also have this feature on our SaaS platform, at the onset, we didn’t realize we would also be walking into a new set of challenges of dynamic scheduling and concurrent task execution. We needed a way to sync data in a scheduled manner from the client's data warehouse to our data store. Challenges with replicating the previous setup: To understand the issue, let's check the previous architecture more closely. Our previous architecture permitted users to link to their respective data warehouses, run database queries, and synchronize subscribers using a preset timeline (e.g., hourly, daily). This scenario appeared straightforward initially, given that we used an embedded SQLite database within the service and anticipated limited occurrences of simultaneous executions, as most customers opted to update individual tables. Also, since we used Golang, we didn’t need a separate process to handle scheduling as it was done efficiently using goroutines and a lightweight library Asynq built around this concept. Our previous setup architecture: SuprSend's previous architecture around multi-tenancy However, the complexity surfaced upon moving this functionality to our SAAS platform. We faced 2 challenges, dynamic scheduling from different processes and concurrent execution of those schedules, which would execute the query, process the results, and sync the subscribers. How did we arrive at the solution? Before going through how we arrived at the solution, let’s understand the problems more deeply. Dynamic Scheduling Imagine a scenario where anyone can schedule a task at any time, and it can be set to run via a cron schedule or at fixed intervals. The scheduler should be capable of prioritizing tasks at all times and managing them efficiently. Since the schedule can change dynamically, the heartbeat process should adapt to every change. Conceptually, this can be achieved with the help of Redis’s sorted set data structure. Redis's Sorted Set is a powerful data structure that significantly aids in scheduling tasks by enabling efficient storage and retrieval of tasks based on their execution time or priority. The Sorted Set stores elements as unique strings (members) along with their associated scores, which are floating-point numbers. Internally In Redis, sorted sets are implemented using a combination of a hash table and a skip list data structure. The hash table provides fast access to elements based on their value, while the skip list maintains the sorted order of the elements based on their scores. This dual structure allows Redis to perform operations on sorted sets efficiently. In the context of task scheduling, scores typically represent the execution time or priority of tasks. Redis maintains the Sorted Set in ascending order based on the scores The priority of a task is determined by its score, with lower scores having higher priority. This allows for fast lookup and retrieval of tasks that are due for execution. If two tasks have the same scores, they are sorted lexicographically. In the context of Redis-based schedulers, they would use Redis’s ZADD commands (to add task representation in sorted sets) and ZRANGEBYSCORE (to retrieve the highest priority task from the sorted set). Let’s understand with an example: Suppose we have a task scheduling system with different priorities (low, medium, high) and execution times. We want to schedule tasks such that high-priority tasks are executed before low-priority tasks, even if a low-priority task has an earlier execution time. To achieve this, we can use a scoring algorithm that combines the priority and execution time into a single score. Example scoring algorithm: Copy Code def calculate_score(priority, execution_time): # Convert execution_time to a UNIX timestamp unix_timestamp = execution_time.timestamp() # Assign numeric values to priorities (lower value means higher priority) priority_values = {'low': 3, 'medium': 2, 'high': 1} # Calculate the score by combining the priority value and UNIX timestamp score = unix_timestamp + (10**9 * priority_values[priority]) return score Now, let's add tasks to the Redis Sorted Set using the ZADD command: Copy Code // Connect to Redis r = redis.Redis() # Add tasks with their calculated scores r.zadd('scheduled_tasks', { 'Task A (low)': calculate_score('low', datetime(2023, 3, 15, 10, 0, 0)), 'Task B (medium)': calculate_score('medium', datetime(2023, 3, 15, 10, 15, 0)), 'Task C (high)': calculate_score('high', datetime(2023, 3, 15, 10, 30, 0)), 'Task D (low)': calculate_score('low', datetime(2023, 3, 15, 10, 45, 0)), }) To retrieve tasks due for execution, we can use the ZRANGEBYSCORE command with the current UNIX timestamp as the minimum score and a large value (e.g., +inf) as the maximum score: Copy Code import datetime # Get the current UNIX timestamp current_timestamp = datetime.datetime.utcnow().timestamp() # Retrieve tasks due for execution due_tasks = r.zrangebyscore('scheduled_tasks', current_timestamp, '+inf') This approach ensures that tasks with higher priority are executed before tasks with lower priority, even if they have later execution times. Now that the scoring and scheduling part is clear, let’s try to understand how we can leverage this to build a robust system that can schedule tasks from a separate producer process and utilize scheduler, worker, and Redis to function in sync. We would need a producer process/ processes to put the task in Redis using ZADD in Redis’s sorted set. We would need a scheduler that would continuously poll for tasks in Redis using ZRANGEBYSCORE and current timestamp and assign the task to existing workers. Finally, we would need a worker process to execute the task and produce heartbeats when the task is completed so that the scheduler can update the execution progress. In our case, the API server was our producer. Implementation: We evaluated various libraries that would utilize this unique functionality provided by Redis, and we found that rq_scheduler in Python ticks all the boxes. We also evaluated: APScheduler: It lacked a separate process for scheduler and worker, which is required since we would ideally want to decouple these processes from our main API server. Celerybeat : Celerybeat didn’t support dynamic scheduling and hence wasn’t ideal. RQ-scheduler : This implements exactly the algorithm explained above and was ideal for our use case; also, its availability in Django was a plus. Now this is how the final architecture looked like: SuprSend's new architecture around handling multi-tenancy For Concurrent DB Writes Our previous setup, SQLite, wouldn’t work for distributed applications like ours because: Concurrency Limitations: SQLite's file-based locking can cause contention issues in scenarios with high concurrent writes. File-based Locking : SQLite's reliance on file-level locks impedes concurrent write operations in a distributed environment. Limited Scalability : SQLite's serverless design becomes a bottleneck as the number of nodes and concurrent writes increases. ACID Compliance Challenges: Ensuring ACID properties across distributed nodes introduces complexities for SQLite. Data Integrity Concerns : File-based locking can lead to data corruption or loss of integrity in distributed systems. No Built-in Network Protocol: SQLite's direct communication with the local file system limits its use in distributed environments. Considering the situation where we had to handle distributed writes from multiple processes on the same db. We chose to use Redis or Postgres for our distributed application. Since each query execution involved handling multiple states and processing results in batches to alleviate server load, we opted for Postgres as our database. Postgres solves all the abovementioned issues related to distributed and concurrent writes, and scalability support, which was ideal for our use case. The only drawback was potentially a little extra compute cost to cloud providers for Postgres usage. Still, the cost paid for a bad customer experience is much larger and potentially catastrophic. Well, after architecting the solution efficiently, processing the queries, which can sometimes even fetch a billion rows (or more), was another critical problem to solve, which we solved by creating a separate service to process the tasks as seen in the architecture diagram. Which processed the tasks and sent events to SuprSend internally for subscriber addition. Anyways, this is how SuprSend architecture is working to abstract the pain of building and maintaining notification service at your end. What do you think? You could try this functionality directly on the platform. Signup now for free . If you learnt something from this content, consider sharing it with your dev friends or on Hackernews :) Share this blog on: Written by: Praveen Praveen is a seasoned backend developer with a passion for crafting efficient and scalable solutions. With 4 years of experience in software development, he specializes in building robust backend systems that power web and mobile applications. Proficient in various programming languages such as Python, Java, and Node.js, he has a knack for tackling complex problems and delivering elegant solutions. Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://shopperdot.com | Shoppertdot.com Toggle accessibility mode (a) Go to homepage (h) Go to navigation (n) Go to search (s) Go to content (c) Go to footer (f) View catalog Search Search Search Zoeken Popular collections Accessories Bath & Beauty Clothing Fashion Accessories Furniture Popular products #P2961 Wireless Bluetooth 5.3 Headphones Over Ear Hifi Stereo Headset $59.33 0W253 - Rhodium Brass Ring with AAA Grade CZ in Clear $18.41 0W379 - Gold Brass Ring with Top Grade Crystal in Clear $14.71 14034 - Rhodium Brass Ring with AAA Grade CZ in Clear $12.21 Customer service Sign in Sign in Login Login Email * Password * Toon Hide Forgot your password? Sign in Don't have an account yet? Create account Cart 0 $0.00 Home Catalog Collection Contact View more menu items Home Catalog Collection Contact Customer service Toggle accessibility mode RO (USD $) Menu Afghanistan (USD $) Åland Islands (USD $) Albania (USD $) Algeria (USD $) Andorra (USD $) Angola (USD $) Anguilla (USD $) Antigua & Barbuda (USD $) Argentina (USD $) Armenia (USD $) Aruba (USD $) Ascension Island (USD $) Australia (USD $) Austria (USD $) Azerbaijan (USD $) Bahamas (USD $) Bahrain (USD $) Bangladesh (USD $) Barbados (USD $) Belarus (USD $) Belgium (USD $) Belize (USD $) Benin (USD $) Bermuda (USD $) Bhutan (USD $) Bolivia (USD $) Bosnia & Herzegovina (USD $) Botswana (USD $) Brazil (USD $) British Indian Ocean Territory (USD $) British Virgin Islands (USD $) Brunei (USD $) Bulgaria (USD $) Burkina Faso (USD $) Burundi (USD $) Cambodia (USD $) Cameroon (USD $) Canada (USD $) Cape Verde (USD $) Caribbean Netherlands (USD $) Cayman Islands (USD $) Central African Republic (USD $) Chad (USD $) Chile (USD $) China (USD $) Christmas Island (USD $) Cocos (Keeling) Islands (USD $) Colombia (USD $) Comoros (USD $) Congo - Brazzaville (USD $) Congo - Kinshasa (USD $) Cook Islands (USD $) Costa Rica (USD $) Côte d’Ivoire (USD $) Croatia (USD $) Curaçao (USD $) Cyprus (USD $) Czechia (USD $) Denmark (USD $) Djibouti (USD $) Dominica (USD $) Dominican Republic (USD $) Ecuador (USD $) Egypt (USD $) El Salvador (USD $) Equatorial Guinea (USD $) Eritrea (USD $) Estonia (USD $) Eswatini (USD $) Ethiopia (USD $) Falkland Islands (USD $) Faroe Islands (USD $) Fiji (USD $) Finland (USD $) France (USD $) French Guiana (USD $) French Polynesia (USD $) French Southern Territories (USD $) Gabon (USD $) Gambia (USD $) Georgia (USD $) Germany (USD $) Ghana (USD $) Gibraltar (USD $) Greece (USD $) Greenland (USD $) Grenada (USD $) Guadeloupe (USD $) Guatemala (USD $) Guernsey (USD $) Guinea (USD $) Guinea-Bissau (USD $) Guyana (USD $) Haiti (USD $) Honduras (USD $) Hong Kong SAR (USD $) Hungary (USD $) Iceland (USD $) India (USD $) Indonesia (USD $) Iraq (USD $) Ireland (USD $) Isle of Man (USD $) Israel (USD $) Italy (USD $) Jamaica (USD $) Japan (USD $) Jersey (USD $) Jordan (USD $) Kazakhstan (USD $) Kenya (USD $) Kiribati (USD $) Kosovo (USD $) Kuwait (USD $) Kyrgyzstan (USD $) Laos (USD $) Latvia (USD $) Lebanon (USD $) Lesotho (USD $) Liberia (USD $) Libya (USD $) Liechtenstein (USD $) Lithuania (USD $) Luxembourg (USD $) Macao SAR (USD $) Madagascar (USD $) Malawi (USD $) Malaysia (USD $) Maldives (USD $) Mali (USD $) Malta (USD $) Martinique (USD $) Mauritania (USD $) Mauritius (USD $) Mayotte (USD $) Mexico (USD $) Moldova (USD $) Monaco (USD $) Mongolia (USD $) Montenegro (USD $) Montserrat (USD $) Morocco (USD $) Mozambique (USD $) Myanmar (Burma) (USD $) Namibia (USD $) Nauru (USD $) Nepal (USD $) Netherlands (USD $) New Caledonia (USD $) New Zealand (USD $) Nicaragua (USD $) Niger (USD $) Nigeria (USD $) Niue (USD $) Norfolk Island (USD $) North Macedonia (USD $) Norway (USD $) Oman (USD $) Pakistan (USD $) Palestinian Territories (USD $) Panama (USD $) Papua New Guinea (USD $) Paraguay (USD $) Peru (USD $) Philippines (USD $) Pitcairn Islands (USD $) Poland (USD $) Portugal (USD $) Qatar (USD $) Réunion (USD $) Romania (USD $) Russia (USD $) Rwanda (USD $) Samoa (USD $) San Marino (USD $) São Tomé & Príncipe (USD $) Saudi Arabia (USD $) Senegal (USD $) Serbia (USD $) Seychelles (USD $) Sierra Leone (USD $) Singapore (USD $) Sint Maarten (USD $) Slovakia (USD $) Slovenia (USD $) Solomon Islands (USD $) Somalia (USD $) South Africa (USD $) South Georgia & South Sandwich Islands (USD $) South Korea (USD $) South Sudan (USD $) Spain (USD $) Sri Lanka (USD $) St. Barthélemy (USD $) St. Helena (USD $) St. Kitts & Nevis (USD $) St. Lucia (USD $) St. Martin (USD $) St. Pierre & Miquelon (USD $) St. Vincent & Grenadines (USD $) Sudan (USD $) Suriname (USD $) Svalbard & Jan Mayen (USD $) Sweden (USD $) Switzerland (USD $) Taiwan (USD $) Tajikistan (USD $) Tanzania (USD $) Thailand (USD $) Timor-Leste (USD $) Togo (USD $) Tokelau (USD $) Tonga (USD $) Trinidad & Tobago (USD $) Tristan da Cunha (USD $) Tunisia (USD $) Türkiye (USD $) Turkmenistan (USD $) Turks & Caicos Islands (USD $) Tuvalu (USD $) U.S. Outlying Islands (USD $) Uganda (USD $) Ukraine (USD $) United Arab Emirates (USD $) United Kingdom (USD $) United States (USD $) Uruguay (USD $) Uzbekistan (USD $) Vanuatu (USD $) Vatican City (USD $) Venezuela (USD $) Vietnam (USD $) Wallis & Futuna (USD $) Western Sahara (USD $) Yemen (USD $) Zambia (USD $) Zimbabwe (USD $) Bath & Beauty Shop now New in Earrings Shop now Shop the look New in Fashion Shop now Add to cart Gifts Shop now Top selling collections View all collections Accessories Bags & Wallets Christmas Earrings Footwear Home Decor Jewelry & Watches View all collections Back in stock this week View all products Quantity "Bloom" 24 Karats Cubic Zirconia Flower Petals Hook Earrings 8-14 Business days $44.68 Quantity Options #P2961 Wireless Bluetooth 5.3 Headphones Over Ear Hifi Stereo Headset 8-14 Business days $59.33 Options Quantity 0W156 - Rhodium 925 Sterling Silver Earrings with AAA Grade CZ in 8-14 Business days $15.73 Quantity Options 0W253 - Rhodium Brass Ring with AAA Grade CZ in Clear 8-14 Business days $18.41 Options Options 0W379 - Gold Brass Ring with Top Grade Crystal in Clear 8-14 Business days $14.71 Options Options 11oz Coffee Mug - Need Coffee Right Meow - Funny 8-14 Business days $24.30 - $27.49 Options Quantity 12V Kids Ride On Car SUV MP3 RC Remote Control LED Lights 8-14 Business days $361.89 Quantity Options 14034 - Rhodium Brass Ring with AAA Grade CZ in Clear 8-14 Business days $12.21 Options View all products Women's Clothing Discover now Fashion Discover Now Jewelry & Watches Discover Now Contact | Privacy Policy | Refund Policy | Delivery Instructions © 2026 Shoppertdot.com, Powered by Shopify Login Email * Password * Toon Hide Forgot your password? Sign in Don't have an account yet? Create account Shop the look Product title 8-14 Business days $0.00 Product title 8-14 Business days $0.00 Product title 8-14 Business days $0.00 Product title 8-14 Business days $0.00 Product title 8-14 Business days $0.00 Our site uses cookies. By clicking on accept you agree with our voorwaarden and privacy policy . Decline Accept Back to top | 2026-01-13T08:49:23 |
https://graphite.dev/docs/graphite-merge-queue | Merge Queue - Graphite Skip to main content Graphite home page Search... ⌘ K Get started Overview Setup & configuration Authenticate with GitHub Configure GitHub repository settings Install & authenticate the CLI Set up merge queue integration Configure recommended CI settings AI Reviews Overview Setup & configuration Review comments Customization Experimental comments PR workflows Pull Request Inbox Graphite Chat Review pull requests Merge pull requests Stacking (Graphite CLI) Overview Quick Start Command Reference Command Cheatsheet Configure The CLI GT MCP Basic tutorials Advanced tutorials Integrations Overview VS Code Extension Menu Bar App (Mac) Slack Notifications Linear Jira Merge Queue Overview Set Up The Graphite Merge Queue Use The Graphite Merge Queue Merge Queue Optimizations External Merge Queue Integration (Beta) Repository management CI Optimizations Automations Insights Background Agents (Beta) Overview Administration Privacy & security User permissions Billing & plans GitHub Enterprise Server Code Indexing References FAQs CLI Changelog Graphite CLI v1 command names Learn to stack Evaluating Graphite LLM-Friendly Documentation App Graphite home page Search... ⌘ K Ask AI App Search... Navigation Merge Queue Merge Queue Merge Queue Merge Queue Learn how Graphite’s merge queue can help your team merge stacks faster and reduce merge conflicts. A merge queue prevents semantic merge conflicts by automating the rebase process during merge and ensures that the trunk branch stays “green”—helping development teams move faster while preventing breakages. The Graphite Merge Queue is the only merge queue that is stack-aware. Ready to start using the Graphite Merge Queue? See Set up the Graphite merge queue . Why Graphite’s merge queue? You would likely benefit from a merge queue if: Your trunk branch is frequently broken You’re consistently slowed down from rebasing changes You have the combined issue of long-running checks with a high PR merge rate Traditional merge queues provide many benefits, but they can also slow teams down by enforcing the ordering of commits and validating those commits in sequence—likely reducing the speed at which merges land. The Graphite Merge Queue is stack-aware , providing opportunities for faster concurrent/batched merges and optimizing the order in which PRs are merged. So if the stack is added to the queue together, the merge queue can process and validate the entire stack in parallel. No need for CI to run again since we have already validated the CI against that exact change (this is also known as fast-forward merge, as described below). Beyond stack awareness, the Graphite Merge Queue can be configured with further optimizations to both increase speed and reduce CI cost. See our blog post to learn more about the benefits of merge queues. Supported merge strategies Rebase: rebase your changes on top of your trunk with commits unchanged (equivalent to GitHub’s rebase and merge) Squash: rebase your changes on top of your trunk with each PR squashed to a single commit (equivalent to GitHub’s squash and merge) Fast-forward merge: you can opt to enable “fast-forward merge” on either of the above strategies in order to process stacked PRs in parallel (a Graphite-only setting). How the Graphite merge queue interacts with GitHub In your repository settings, you have the option to enforce the Graphite merge queue. If it isn’t enforced, users will be able to merge PRs through GitHub directly (bypassing the merge queue entirely). Enforcing the Graphite merge queue requires some configuration on GitHub’s side, namely setting up the correct branch protection rules and authorizing with Graphite’s GitHub App. Read more about advanced Graphite merge queue settings . The Graphite merge queue is not compatible with GitHub’s merge queue. If you want to use the Graphite merge queue and you’re currently using GitHub’s, you must disable it for your repository before continuing. Instructions on using Graphite with the GitHub merge queue can be found here . When a PR is added to the Graphite merge queue, we leave comments on your GitHub PR in three instances: when the PR is added to the queue, when it is merged through the queue, and when it fails/is removed from the queue. External merge queue integration If you already use a separate external merge queue offering, Graphite’s external merge queue integration simplifies the merging experience. While it doesn’t experience the same stack-aware optimizations as Graphite’s merge queue, it can be a quick way to ramp-up your team. See external merge queue integration for more info. Was this page helpful? Yes No Previous Set Up The Graphite Merge Queue Next ⌘ I On this page Why Graphite’s merge queue? Supported merge strategies How the Graphite merge queue interacts with GitHub External merge queue integration Graphite home page slack x github Product Features Pricing Docs Customers Company Blog Careers Contact us Resources Community Privacy policy Terms of service Stacking workflow Developers Status GitHub Powered by | 2026-01-13T08:49:23 |
https://dev.to/okan_kaplan_livehtml/maqam-music-4513 | maqam music - 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 okan kaplan Posted on Jan 10 maqam music # algorithms # webdev # showdev # javascript https://www.youtube.com/watch?v=miLwawvI6-k This project is an experimental sound engine that merges maqam-based musical logic with algorithmic composition. Built with Tone.js, the system generates living musical structures through motif creation, variation, cadences, walking bass lines, and rhythm patterns inspired by traditional usul. The sound design features: 3D spatial panning (HRTF) for immersive movement Ping-pong delay and reverb to create a mystical acoustic space Micro pitch drift (LFO-driven pitch shifting) that adds spiritual motion without breaking the maqam character The goal is to move beyond Western harmonic conventions and reinterpret Eastern modal music through modern Web Audio technologies. The project runs entirely in the browser as a single HTML file, generating real-time, evolving music. 🔖 Hashtags ToneJS WebAudio GenerativeMusic AlgorithmicMusic Maqam SoundDesign 3DAudio SpatialAudio CreativeCoding ExperimentalMusic MusicTechnology BrowserAudio AudioProgramming DigitalArt MysticSound 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 okan kaplan Follow Creative developer & frontend educator. I explore the hidden capabilities of modern desktop web browsers using single-page HTML and JavaScript — from generative music systems with Web Audio & Tone.js Location Türkiye Education Independent learning & real-world projects Pronouns he/him Work Creative Developer & Frontend Educator Joined Dec 16, 2025 More from okan kaplan OKAN KAPLAN SOUND LAB – Infinite Jazz Generator | Live Coding with JavaScript # algorithms # javascript # showdev Building an Infinite Generative Music Engine with Pure HTML & JavaScript (Markov-Based) # javascript # music # website # coding 💎 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:49:23 |
https://forem.com/t/decisionintelligent | Decisionintelligent - 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 DEV Community Close # decisionintelligent Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How Odoo ERP Simplifies VAT Filing for UAE Businesses | Decision Intelligent DECISION INTELLIGENT DECISION INTELLIGENT DECISION INTELLIGENT Follow Jan 5 How Odoo ERP Simplifies VAT Filing for UAE Businesses | Decision Intelligent # ai # decisionintelligent # odoo # erp Comments Add Comment 4 min read UAE VAT & Corporate Tax Compliance with Odoo ERP | Decision Intelligent DECISION INTELLIGENT DECISION INTELLIGENT DECISION INTELLIGENT Follow Dec 26 '25 UAE VAT & Corporate Tax Compliance with Odoo ERP | Decision Intelligent # ai # decisionintelligent # odooerp # uaetax Comments Add Comment 3 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:23 |
https://dev.to/t/authorization | Authorization - 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 # authorization Follow Hide Create Post Older #authorization posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Filament Passport UI – Managing Laravel Passport OAuth with Clarity Ilya Beliaev Ilya Beliaev Ilya Beliaev Follow Jan 7 Filament Passport UI – Managing Laravel Passport OAuth with Clarity # laravel # filament # authorization # passport Comments Add Comment 2 min read Laravel Passport Authorization Core – A Domain-Oriented Authorization Foundation Ilya Beliaev Ilya Beliaev Ilya Beliaev Follow Jan 7 Laravel Passport Authorization Core – A Domain-Oriented Authorization Foundation # laravel # oauth2 # authorization # cleanarchitecture Comments Add Comment 2 min read Practical MCP-Style Authorization: An Experimental PoC and Guide Aniket Hingane Aniket Hingane Aniket Hingane Follow Dec 24 '25 Practical MCP-Style Authorization: An Experimental PoC and Guide # security # authorization # python # tutorial Comments Add Comment 16 min read Rule of Two Piece Mathew Pregasen Mathew Pregasen Mathew Pregasen Follow Dec 24 '25 Rule of Two Piece # ai # security # llm # authorization Comments 1 comment 7 min read API Security : Understand in 3 Minutes Hongster Hongster Hongster Follow Dec 11 '25 API Security : Understand in 3 Minutes # apisecurity # authentication # authorization # abotwrotethis Comments Add Comment 3 min read Microservices Authentication & Authorization: A Beginner's Guide Rushikesh Surve Rushikesh Surve Rushikesh Surve Follow Nov 26 '25 Microservices Authentication & Authorization: A Beginner's Guide # microservices # authentication # authorization # gateway 2 reactions Comments Add Comment 4 min read RBAC in Kubernetes: Understanding Roles, and RoleBindings 🔐 Laxman Patel Laxman Patel Laxman Patel Follow Oct 1 '25 RBAC in Kubernetes: Understanding Roles, and RoleBindings 🔐 # kubernetes # security # rbac # authorization Comments Add Comment 3 min read Authentication and authorization : difference Amahle Comfort Nxumalo Amahle Comfort Nxumalo Amahle Comfort Nxumalo Follow Sep 1 '25 Authentication and authorization : difference # webdev # security # authentication # authorization Comments Add Comment 2 min read Privileged: A Powerful Authorization Library for .NET Paul Welter Paul Welter Paul Welter Follow for LoreSoft Sep 5 '25 Privileged: A Powerful Authorization Library for .NET # authorization # security # aspnetcore # permissions Comments Add Comment 4 min read What's the Difference Between Authentication and Authorization? Carrie Carrie Carrie Follow Jul 29 '25 What's the Difference Between Authentication and Authorization? # authentication # authorization # identity # firewall 5 reactions Comments Add Comment 2 min read The deceptive simplicity of auth Evgeny Evgeny Evgeny Follow Aug 19 '25 The deceptive simplicity of auth # security # authentication # authorization # beginners 2 reactions Comments Add Comment 3 min read Implementing OAuth for MCP servers: a developer's guide Saif Saif Saif Follow Jul 29 '25 Implementing OAuth for MCP servers: a developer's guide # oauth # mcp # authorization # ai Comments Add Comment 3 min read When to Use Gates, Policies, and the Spatie Permission Package in Laravel Vatsal Acharya Vatsal Acharya Vatsal Acharya Follow for AddWeb Solution Pvt Ltd Jul 10 '25 When to Use Gates, Policies, and the Spatie Permission Package in Laravel # laravel # authorization # rbac # permissions 24 reactions Comments Add Comment 4 min read Access Token v/s Refresh Token gunjangidwani gunjangidwani gunjangidwani Follow Jun 20 '25 Access Token v/s Refresh Token # programming # backend # node # authorization Comments Add Comment 2 min read How to Protect Your API with OpenFGA: From ReBAC Concepts to Practical Usage Edouard Maleix Edouard Maleix Edouard Maleix Follow for This is Learning Jun 15 '25 How to Protect Your API with OpenFGA: From ReBAC Concepts to Practical Usage # tutorial # openfga # authorization # security 5 reactions Comments 2 comments 17 min read Tigris's object store's authentication & authorization Shared Account Shared Account Shared Account Follow for Tigris Data Jun 4 '25 Tigris's object store's authentication & authorization # security # authentication # authorization Comments Add Comment 3 min read Deploy Permit.IO PDP To Heroku Under 5 Mins! [Video Included] Aidityas Adhakim Aidityas Adhakim Aidityas Adhakim Follow May 1 '25 Deploy Permit.IO PDP To Heroku Under 5 Mins! [Video Included] # permitio # heroku # authorization Comments Add Comment 2 min read The interplay of authentication and authorization in ASP.NET Core Pavel Voronin Pavel Voronin Pavel Voronin Follow Apr 9 '25 The interplay of authentication and authorization in ASP.NET Core # aspnetcore # authentication # authorization Comments Add Comment 6 min read Introducing Guantr: A Type-Safe Authorization Library for JavaScript/TypeScript Herdi Tr. Herdi Tr. Herdi Tr. Follow Apr 9 '25 Introducing Guantr: A Type-Safe Authorization Library for JavaScript/TypeScript # javascript # authorization # opensource # webdev Comments Add Comment 3 min read Scrapebase + Permit.io: Web Scraping with API-First Authorization Tamizh Tamizh Tamizh Follow May 5 '25 Scrapebase + Permit.io: Web Scraping with API-First Authorization # permitio # authorization # api # webdev 16 reactions Comments 1 comment 4 min read Authorization in Node.js, all you need to know Gabriel Olátúnjí Gabriel Olátúnjí Gabriel Olátúnjí Follow Mar 6 '25 Authorization in Node.js, all you need to know # node # authorization # authentication Comments Add Comment 2 min read Understanding Authentication & Authorization (JWT, OAuth2.0, Session) Concepts Aashish Koshti Aashish Koshti Aashish Koshti Follow Apr 3 '25 Understanding Authentication & Authorization (JWT, OAuth2.0, Session) Concepts # authentication # authorization # systemdesign # computerscience 6 reactions Comments Add Comment 6 min read Authentication and Authorization Best Practices in ASP.NET Core Anton Martyniuk Anton Martyniuk Anton Martyniuk Follow Mar 25 '25 Authentication and Authorization Best Practices in ASP.NET Core # programming # authentication # authorization # dotnet 3 reactions Comments Add Comment 7 min read Beware of the New Enemy Problem ⚠️ Sohan Sohan Sohan Follow Mar 6 '25 Beware of the New Enemy Problem ⚠️ # security # authorization # distributedsystems # spicedb 1 reaction Comments Add Comment 4 min read How to Implement Role-Based Access Control (RBAC) in Node.js Applications rabindratamang rabindratamang rabindratamang Follow Feb 27 '25 How to Implement Role-Based Access Control (RBAC) in Node.js Applications # node # authorization # jwt # mongodb Comments Add Comment 3 min read loading... trending guides/resources Microservices Authentication & Authorization: A Beginner's Guide API Security : Understand in 3 Minutes Rule of Two Piece Filament Passport UI – Managing Laravel Passport OAuth with Clarity Laravel Passport Authorization Core – A Domain-Oriented Authorization Foundation Practical MCP-Style Authorization: An Experimental PoC and Guide 💎 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:49:23 |
https://www.suprsend.com/post/what-is-inapp-inbox-and-why-every-new-age-product-should-have-one | What is Inapp Inbox and Why every New-Age Product should have one? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Product What is Inapp Inbox and Why every New-Age Product should have one? Anjali Arya • April 15, 2025 TABLE OF CONTENTS In a distracted world where every product is fighting for user attention on out-of-app channels, SuprSend in-app Inbox is a game changer for driving user engagement through timely in-app messages, especially for products that thrive on user interactions. Think about any social media platform like LinkedIn and Facebook, bell icon notification centre is the first thing that grabs our attention. That in-app messaging centre informs about updates relevant to the user's interests, highlights activities requiring their attention, and guides them on the necessary actions to take. In workflow management tools like Jira and Asana, it acts as our checklist of project updates, mentions, and conversations. While these platforms use out-of-app channels to notify users about missed messages, in-app messaging tools like SuprSend inapp inbox takes centre stage as their primary communication channel and is a core feature of their product success. What makes the in-app Inbox a highly effective communication channel with the highest open rate of 75% (~2x of email and ~3x of push notification) ? Factors leading to the effectiveness of Inbox channel In this blog, we’ll cover the diverse use cases of the SuprSend inapp Inbox as a channel, explore various in-app notification types, and provide a comprehensive guide on building the perfect inapp inbox experience for your users. This blog isn't just about adding a feature; it's about strategically enhancing your product's notification capabilities for a superior user experience. Why is Inbox a need for modern applications? App Inbox is not going to replace email, or any other channel for that matter, but it can be very effective when used as part of a larger multichannel communication. Think of it as a missing link that seamlessly integrates into your communication ecosystem, maximizing your brand's reach. Here are a few common reasons why it's valuable to add in-app notifications to your product: 1. Reduce Notification overload Out-of-app channels like email and SMS are becoming increasingly crowded, making it challenging for users to segregate important notifications amid the noise. In-app notifications offer a focused environment where users can access relevant messages, ensuring critical updates aren't overlooked. In a well-designed notification system, not every message needs to be sent on attention-seeking channels like email or push. Certain notifications, such as task updates or document mentions, are best consumed at the user's preferred time. Unliker emails or push notifications, intelligently routing notifications to the in-app inbox channel first and resorting to out-of-app channels only if the in-app notification hasn't been seen can significantly reduce the notification overload. 2. Great supplementary channel for missed out-of-app notifications The inapp inbox serves as a central place for users to catch up on notifications they might have missed interacting with on other channels. Unlike push notification tools like Braze or Clevertap, where messages are lost once dismissed, SuprSend inapp inbox notifications are persistent and store the record of all notifications for later reference. With proper grouping of notifications using tabs, it is also more convenient to filter and get to a particular message inside the Inbox. 3. Notify customers in real-time when they're active in the product For products with a high visit rate, such as SaaS applications, workflow management platforms, social platforms, and collaboration tools, inapp inbox like SuprSend becomes the ideal channel for real-time communication. It minimizes the need for users to switch contexts by sending in-app messages directly into the application. This approach boosts response times and frequency, particularly for actions users need to take within the product, without the user having to leave the application. 4. Send long-live notifications SuprSend inapp inbox notifications have a longer lifespan and stay in the inbox for as long as the company or user needs them. It is ideal for updates and actions that users may need to reference later, such as offers/referral codes or completing a payment that is due next week. You can set the expiration date for these in-app messages, automatically removing them from the notification centre after a certain point or when the required action is taken. Additionally, you have the flexibility to update notification content to reflect the latest changes, like “payment is due in a week” being changed to “payment is due today” or “your post is liked by Steve” being changed to “your post is liked by Steve and 7 others”. 5. Ideal for collaboration and workflow automation tools For many B2B SaaS applications, where users spend substantial time within the product, especially in workflow automation and collaboration tools, the inapp inboxes like SuprSend becomes indispensable. It ensures users receive updates while inside the product, preventing delays in action. This is particularly crucial in scenarios where teams from different companies or departments collaborate on multiple projects. Without the inap inbox in Jira or Notion, it would be difficult for someone working on more than one project to keep track of these updates. Scattered notifications on out-of-app channels like that of push notificatons from tools lke Braze or Clevertap are not as efficient in distributing that information as the notification inbox embedded in your app. Different Types of In-App Notifications: Choosing the Right Experience Broadly speaking, there are three types of in-app notification experiences related to Inbox: Full page Inbox, floating or side panel Inbox (also known as feeds), and toasts. Each serves a unique purpose and caters to distinct user experiences. Let's delve into each type to understand when and why you might employ them in your product. You can also use these experiences in combination within your product. Full page Inbox SuprSend full page inapp inboxes provides a dedicated page inside your product to show notifications. It is well-suited for collaboration and workflow management tools where daily task checklists and activity updates are maintained inside the Inbox. Users can view new and historical notifications, and filter and refine displayed notifications, utilizing the notification centre as a task list for actionable items. It also helps users to keep track of the read and seen states of notifications, see a badge count of the total number of pending actions, and archive or remove actioned notifications, a functionality similar to that of email providers like Sendgrid or Mailchimp. Jira and Asana are great examples of this use case. Full Page Inbox Floating or side panel Inbox (also known as Feeds) This is a variant of a full-page inbox, with a slightly different use case. Here, the major purpose of SuprSend app inbox is to share updates, such as social media platforms or collaboration tools like Notion. Here, the notifications are shown in reverse chronological order. Paired with a bell icon indicating unread notifications, users can access the feed through a popover or side panel and take actions on notifications, like marking them as read/unread or archived. Feeds are suitable for products where a full-page app inbox might be excessive. Hubspot and Trello are notable examples of leveraging notification feeds to guide users through updates and comments without the need for a dedicated page. For products where users heavily rely on notifications for their day-to-day actions, you can also use a combination of both Feed and a Full page Inbox where the feed shows the latest updates and Full page Inbox acts as a complete list of all older alerts. Floating and Side Panel Inbox Toasts Notification Toasts deliver real-time notifications through transient UI elements that pop up on the screen and then disappear. Toasts are best used for showing time-sensitive updates and drawing your users' attention while they are actively using the product. Take care to use toasts sparingly, as they can become a distracting UI pattern when overused. In SuprSend, Feeds, Full page Inbox and toasts can all be achieved with the same Inbox component with basic customization at your end. Anatomy of notification feed Floating Inbox - Component breakdown No. UI Component Description 1 Bell Icon with counter It displays the number of new notifications received since last time you opened the Inbox. 2 Header section Header section contains the title of the Inbox along with filters and general actions like `Mark all as read` 3 Mark all as read This is an action button to mark all unread notifications as read. 4 Filter You can add filters to provide users with the option to refine notifications, like `show only unread` notifications. It helps users get to the required notification faster. 5 Tabs Tabs are used for better categorization and grouping of notifications. You can create tabs based on notification status (read, unread) or the type of notifications (mentions, replies). 6 Notification card This is where the actual notification content is shown. A typical notification includes title, body, buttons, avatar, and subtext. 7 Notification text Notification text can have a title and a body with rich text content. 8 Subtext You can use subtext for notification tags like reminder, export, and assign, as seen in Hubspot or use it to show supplementary information, such `20 likes . 5 comments` in a LinkedIn post update. 9 Unread dot There are 2 notification states in Inbox: Read and Unread. It's crucial to provide users with a clear distinction between these two categories for easy differentiation. One way of distinguishing this is by an unread dot. Another way is to have a different background color for unread notifications. 10 Buttons You can add buttons to navigate users to internal product pages and external links, or drive inline action like opening a modal or triggering internal function like approve / reject. 11 Avatar Avatars in your Inbox display user profile images, company logos in social media platforms, or icons to distinguish between various notification types, similar to HubSpot's approach. 12 Received at time Displaying the timestamp of when a notification was received is crucial in Inbox. You can either show it on the right side of your notification card or below the notification content. 13 Footer Footer is an ideal place to display powered by tags for branding. You can also use it to show some static content similar to Jira's message: "That’s all your notifications from the last 30 days". How to design a perfect inapp inbox experience using in-app messaging tools like SuprSend? To build in-app notifications into your product, you'll need to build two major components: The frontend UI that provides an intuitive interface for users to interact with their notifications The backend system that processes the notifications and sends real-time updates to the frontend On the frontend , you’ll need to build the appropriate UI experience for your product with support for composing and formatting different message elements like avatars, buttons, image, and rich text messages. You may refer to our ready-to-use Figma design kit for modern in-app notification feed designs that can be a helpful starting point for your team. On the Backend , you’ll need to take care of 1. Infrastructure: Database: Set up a robust database to store and manage messages, user preferences, and other relevant data. Server-Side Infrastructure: Implement server-side infrastructure to handle message processing, storage, and delivery. 2. User Authentication and Authorization: Implement secure user authentication and authorization mechanisms (HMAC, JWT token) to prevent unauthorized access to the Inbox service. 3. Real-Time and Cross-Browser Synchronization: Implement web socket connection to fetch real-time updates from your database and ensure that users receive messages instantly without the need for manual refreshes and have an in-sync experience across different browsers and devices. 4. State Management: Implement effective state management to keep track of the notification status, user interactions, and message read/unread states. Set notification expiry and allow users to archive or delete notifications. 5. Aggregation and Filtering: Introduce tabs and filtering in the Inbox for better organization of notifications. Show new notification count on bell and the unread notification count on each tab for users to keep track of the unattended alerts. 6. Observability layer: Building an observability layer atop your notifications becomes crucial over time to track channel performance and aid in debugging customer-facing issues effectively. 7. Designing for Scale and Reliability: It is imperative to evaluate the scalability and reliability of the system, as it is a critical part of your product infrastructure. Scaling any notification system across a growing customer base can be a challenge on its own as the system typically has a high volume of writes in comparison to the rest of your service. Other than this, a well-designed notification system should also have intelligent routing mechanisms to route notifications among multiple channels based on interaction and delivery status. You might also have to build a preference management system to enable your users to opt out of specific notification categories from Inbox. Also, if you have a multi-tenant system, tailoring Inbox feeds and designs for different tenants should be addressed. Implementing Inbox is faster and more convenient with SuprSend Building an Inbox experience in-house can take months of engineering, design and product effort. You can just get away with all the trouble of building and maintaining your Inbox in-house and rather try SuprSend. We have a ready Inbox component that you can integrate within your product in less than an hour. Packed with all the Inbox functionalities mentioned above, SuprSend offers multi-channel notification support and a comprehensive 360-degree solution, unlocking observability, notification routing, user preferences, and multi-tenant support for a superior notification experience. With SuprSend Inbox, you can: Create modern Inbox designs native to your product using our customizable UI components or build your own UI with headless library. You can leverage beautiful inbox designs and sample code from Github which you can customize further to match your brand style. Implement Varied In-App Experiences : Choose from a full-page Inbox, Notification feed with floating and side panel views, or toast notifications. Pass any type of notification content ( avatar, header, buttons, image, and rich text ) using our easy-to-use form editors. Seamlessly organize, group, and filter your notifications with tabs . Handle any type of click action , whether it's opening a link in the same or new tab, launching a modal on click, or calling an internal function like `approve`. Gain complete observability into your notifications with state management like mark as read/unread, clicked, and archive. Experience real-time notification sync and cross-browser/device notification state synchronization without the need for infrastructure setup and maintenance at your end. Get a system built for scale and reliability. Frequently Asked Questions (FAQs) 1. What is SuprSend's In-App Inbox? SuprSend's In-App Inbox is a centralized notification center embedded within your application, allowing users to receive and manage real-time updates, reminders, and alerts without leaving the app. 2. How does the In-App Inbox improve user engagement? By delivering notifications directly within the app, the In-App Inbox ensures timely communication, leading to higher engagement rates compared to traditional channels like email or SMS. 3. What types of notifications can be sent through the In-App Inbox? The In-App Inbox supports various notification types, including transactional updates, promotional messages, reminders, and system alerts, all tailored to the user's preferences. 4. Is user consent required to receive notifications in the In-App Inbox? No, users do not need to opt-in separately for In-App Inbox notifications. Since these messages are delivered within the app, they are part of the user experience. 5. Can the In-App Inbox be customized to match my app's branding? Yes, SuprSend provides customizable UI components and a headless library, allowing you to tailor the In-App Inbox's appearance to align with your app's design and branding. 6. How does SuprSend handle message delivery and synchronization? SuprSend ensures real-time message delivery with cross-browser and cross-device synchronization, providing a consistent user experience across platforms. 7. What analytics are available for In-App Inbox messages? SuprSend offers comprehensive analytics, including metrics on message opens, interactions, and user behavior, enabling you to assess the effectiveness of your notifications. 8. Can I implement the In-App Inbox in my existing app? Yes, SuprSend provides SDKs for various frameworks, including React, Angular, Flutter, and Vue, facilitating easy integration of the In-App Inbox into your application. 9. How does the In-App Inbox compare to traditional notification channels? Unlike push notifications or emails, In-App Inbox messages remain accessible within the app, allowing users to review and act on them at their convenience, reducing notification fatigue. 10. Where can I find more information or get started with SuprSend's In-App Inbox? You can explore detailed documentation, integration guides, and live demos on SuprSend's official website. Aside from powering in-app notifications, you can use SuprSend to schedule, batch and orchestrate notifications across multiple out-of-app channels and manage user preferences without the need to write custom application code. We are a pioneer in helping you deliver the best notification experience to your users. Ready to give SuprSend Inbox a try? You can see a live demo of our Inbox functionality here. If you’re looking to learn more about the feature, check out our documentation . Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/how-can-saas-tools-enhance-user-engagement-with-notifications-channel-routing-with-linkedins-example | How Can SaaS Tools Enhance User Engagement with Notifications Channel Routing (with LinkedIn's example)? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Product Implementation Guides How Can SaaS Tools Enhance User Engagement with Notifications Channel Routing (with LinkedIn's example)? Anjali Arya • July 17, 2024 TABLE OF CONTENTS If you use LinkedIn, you've likely noticed that it sends notifications within in-app about various activities, such as connection requests or new messages, while also delivering these notifications over emails. These email notifications might not be instant and can be delayed by 2-24 hours, customized based on user preferences, potential volume and the priority of the notification. It also solves a crucial pain point for social media companies, where there are a ton of notification triggers happening through each interaction. This notification fatigue impacts the user experience, and hence is something to be solved sooner. What is it, and how does LinkedIn and other SaaS tools achieve similar functionality to ensure users are appropriately notified, maintaining engagement with the product without overwhelming with too many alerts? What is Channel Routing? Channel routing involves directing notifications through various channels to ensure user engagement isn't hampered if a user is unavailable on a single channel.For example, Instagram provides an almost instant in-app notification when someone likes your post. However, if you remain offline for a certain period, say 6 hours, Instagram sends you an email notification with the same message. This is basic channel routing.On SuprSend, we have enhanced channel routing capabilities. Here’s how: Setting Order of Channels (Optimize On): In a multi-channel notification setup, you can specify the order of channels based on custom use cases. For instance, some SaaS platforms might prioritize cost-saving, so their order could be in-app inbox → email → SMS. Others may prioritize read receipts for notifications like OTPs/ verifications, with SMS/ email at the top of the list. SuprSend can optimize this further by calculating the end-use cases. For example, if the business wants to optimize costs, our platform checks the costs associated with each channel and sets the priority order accordingly. Time-to-Live (TTL): TTL is the total time a notification is live and attempted for delivery. If TTL is set to 6 hours and there are 3 channels configured, our platform divides the TTL by the number of channels, sending notifications at equal intervals. For example, the first notification at 0 hours, the second in 2 hours, and the third in 4 hours. This way, you only need to mention what is the time window in which you want an action on notification, and the workflow engine optimizes for that. Must Send To: This parameter instructs the workflow engine to send notifications to specified channels instantly, regardless of the channel order. some text For critical notifications like OTPs, sending them simultaneously via email and SMS ensures reliability, a practice common in Fin-tech companies to prevent failures in execution due to single-channel issues. Another crucial importance of this feature would be for notifications required to be stored for further bookkeeping. For ex, invoice or billing related businesses might need to store their notifications for longer period and hence channel which can support this, like email or in-app notification should always be set in the 'Must Send To' parameter. Success Metric: This defines the target user activity you want to drive with your notifications. Channel routing stops further delivery when the success metric is achieved. There are two types: Notification Status: Metrics like delivery, seen, or interaction/click status of sent notifications. For example, if the target is for the user to open the notification, set the success metric to Notification Status - Seen. Custom Event: Any custom business event in response to the notification. For instance, for approval, the success metric could be when approval / rejection action is taken. Override Channels: Users may have individual channel preferences, necessitating the need to pass these preferences in the event call itself. The Override Channels property allows including a channels array in the event property, ensuring personalized routing. Implementing Channel Routing in a Social Media Application We'll be demonstrating channel routing in one of our sample applications where we have installed SuprSend Javascript SDK for triggering events. You can access the demo application and code here: Github: https://github.com/SuprSend-NotificationAPI/social-app-react-app-inbox Deployed Application: https://suprsend-notificationapi.github.io/social-app-react-app-inbox/ To illustrate, let’s define the code for a Comments event where the user inputs a comment, which is sent to SuprSend as an event using suprsend.track . Once the event is set properly, the next step is to configure the Smart Channel node in the application. Adding the Channel Routing node is a one-click process.Without it, it would be creating individual branches to check whether channel info exists, whether user is subscribed or action is taken. Then you can set the properties that we discussed above. For this example, use-case we would be using: Once set, we can do a test trigger, and go to logs to see how the node is working. In the given screenshots at different intervals, you can see that the Inbox is triggered first, while the email channel waits. After the 1 min time window, when the Seen confirmation doesn’t come, the email is triggered. Incase the Seen confirmation had come from Inbox, the email node would have stopped, and the workflow would be complete, saving unnecessary costs and notification fatigue for the user. By leveraging SuprSend's advanced channel routing capabilities, social and collaborative applications can enhance user engagement, ensuring critical notifications are delivered through the most effective channels based on user preferences and contextual priorities. Though there is one more way which collaborative SAAS tools like LinkedIn and Meta uses to reduce notification fatigue. They bundle multiple notifications into 1, and then send it to the user, also known as batching. You can checkout this guide to implement a batching mechanism to your notification infrastructure. Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://design.forem.com/t/uidesign#main-content | Uidesign - Design 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 Design Community Close # uidesign Follow Hide The art of designing beautiful and functional user interfaces Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Putting it All together: Dashboard Design Tips Kaira Kelvin. Kaira Kelvin. Kaira Kelvin. Follow Dec 18 '25 Putting it All together: Dashboard Design Tips # baddesign # dataviz # uidesign Comments Add Comment 4 min read Color Theory in UI Design for Maximum Impact Taqwah Taqwah Taqwah Follow Dec 4 '25 Color Theory in UI Design for Maximum Impact # uidesign 1 reaction Comments 1 comment 5 min read Reimagining Thai Lagoon - Website Redesign Parvathi Kumar Parvathi Kumar Parvathi Kumar Follow Dec 5 '25 Reimagining Thai Lagoon - Website Redesign # uxdesign # showcase # uidesign # webdesign Comments Add Comment 2 min read Call-to-Actions Done Right: The Ultimate CTA Guide for More Engagement Per Starke Per Starke Per Starke Follow Oct 23 '25 Call-to-Actions Done Right: The Ultimate CTA Guide for More Engagement # cta # design # webdesign # uidesign Comments Add Comment 3 min read Why Your Website Should Evolve With You (and How) Per Starke Per Starke Per Starke Follow Oct 23 '25 Why Your Website Should Evolve With You (and How) # cms # webdesign # uidesign # copywriting Comments Add Comment 7 min read How to Find UI Animation Inspiration Fast Tamim Ahmed Tamim Ahmed Tamim Ahmed Follow Oct 1 '25 How to Find UI Animation Inspiration Fast # uidesign # inspiration # motiongraphics # resources 6 reactions Comments Add Comment 3 min read How UX in 2025 became more about intent than interaction Karina Egle Karina Egle Karina Egle Follow Oct 23 '25 How UX in 2025 became more about intent than interaction # design # uxdesign # uidesign # webdesign 9 reactions Comments 1 comment 4 min read 11 Principles That Help Me Decide When to Research vs. Just Ship Ulad Shauchenka Ulad Shauchenka Ulad Shauchenka Follow Sep 26 '25 11 Principles That Help Me Decide When to Research vs. Just Ship # design # uxdesign # uidesign # webdesign Comments Add Comment 1 min read Designing Silence: How Minimal UX Can Improve Voice Assistant Experiences Pratiksha Pratiksha Pratiksha Follow Oct 15 '25 Designing Silence: How Minimal UX Can Improve Voice Assistant Experiences # aiindesign # uidesign # uxdesign Comments Add Comment 2 min read Figma vs Adobe XD: Which One Should You Learn in 2025? Pixel Mosaic Pixel Mosaic Pixel Mosaic Follow Oct 14 '25 Figma vs Adobe XD: Which One Should You Learn in 2025? # uidesign # careeradvice # adobesuite # figma Comments Add Comment 2 min read Designing All-Device Compatible Tableau Dashboards: A Comprehensive Guide Dipti Moryani Dipti Moryani Dipti Moryani Follow Oct 9 '25 Designing All-Device Compatible Tableau Dashboards: A Comprehensive Guide # dataviz # uidesign # tools # responsive 5 reactions Comments Add Comment 7 min read Spline UI Animation: Creating 3D Interactions with Ease Tamim Ahmed Tamim Ahmed Tamim Ahmed Follow Oct 5 '25 Spline UI Animation: Creating 3D Interactions with Ease # 3ddesign # motiongraphics # uidesign 5 reactions Comments 1 comment 3 min read UX/UI and some industrial design for an air quality sensor Liberiam Liberiam Liberiam Follow Sep 29 '25 UX/UI and some industrial design for an air quality sensor # uidesign # productdesign # sideprojects # uxdesign 4 reactions Comments Add Comment 6 min read The Dos and Don’ts of Designing an Efficient Tableau Dashboard Dipti Dipti Dipti Follow Sep 26 '25 The Dos and Don’ts of Designing an Efficient Tableau Dashboard # dataviz # tools # uidesign 5 reactions Comments Add Comment 6 min read Why I used emojis instead of icons in my app design Valerii Torianyk Valerii Torianyk Valerii Torianyk Follow Sep 6 '25 Why I used emojis instead of icons in my app design # uidesign # mvp # startup # design 5 reactions Comments Add Comment 1 min read loading... trending guides/resources Color Theory in UI Design for Maximum Impact Putting it All together: Dashboard Design Tips Reimagining Thai Lagoon - Website Redesign 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://atproto.com/specs/sync | Sync - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Data Synchronization One of the main design goals of atproto (the "Authenticated Transfer Protocol") is to reliably distribute public content between independent network services. This data transfer should be trustworthy (cryptographicly authenticated) and relatively low-latency even at large scale. It is also important that new participants can join the network at any time and “backfill” prior content. This section describes the major data synchronization features in atproto. The primary real-time data synchronization mechanism is repository event streams, commonly referred to as "firehoses". The primary batch data transfer mechanism is repository exports as CAR files. These two mechanisms can be combined in a "bootstrapping" process which result in a live-synchronized copy of the network. An updated version of the Synchronization protocol is being rolled out to the live network in early 2025. There is a "Sync v1.1" proposal document and an update blog post with deployment details. The written specifications will be updated soon. Synchronization Primitives As described in the repository spec, each commit to a repository has a revision number, in TID syntax. The revision number must always increase between commits for the same account, even if the account is migrated between hosts or has a period of inactivity in the network. Revision numbers can be used as a logical clock to aid synchronization of individual accounts. To keep this simple, it is recommended to use the current time as a TID for each commit, including the initial commit when creating a new account. Services should reject or ignore revision numbers corresponding to future timestamps (beyond a short fuzzy time drift window). Network services can track the commit revision for every account they have seen, and use this to verify synchronization progress. Services which synchronize data can include the most-recently-processed revision in HTTP responses to API requests from the account in question, in the Atproto-Repo-Rev HTTP response header. This allows clients (and users) to detect if the response is up-to-date with the actual repository, and detect any problems with synchronization. Firehose The repository event stream ( com.atproto.sync.subscribeRepos , also called the "firehose") is an Event Stream which broadcasts updates to repositories ( #commit events), handles and DID documents ( #identity ), and account hosting status ( #account ). PDS hosts provide a single stream with updates for all locally-hosted accounts. "Relays" are network services which subscribe to one or more repo streams (eg, multiple PDS instances) and aggregate them in to a single combined repo stream. The combined stream has the same structure and event types. A Relay which aggregates nearly all accounts from nearly all PDS instances in the network (possibly through intermediate relays) outputs a “full-network” firehose. Relays often mirror and can re-distribute the repository contents, though their core functionality is to verify content and output a unified firehose. In most cases the repository data synchronized over the firehose is self-certifying (contains verifiable signatures), and consumers can verify content without making additional requests directly to account PDS instances. It is possible for services to redact events from the firehose, such that downstream services would not be aware of new content. Identity and account information is not self-certifying, and services may need need to verify independently. This usually means independent DID and handle resolution . Account hosting status might also be checked at account PDS hosts, to disambiguate hosting status at different pieces of infrastructure. The event message types are declared in the com.atproto.sync.subscribeRepos Lexicon schema, and are summarized below. A few fields are the same for all event types (except for repo vs did for #commit events): seq (integer, required): used to ensure reliable consumption, as described in Event Streams did / repo (string with DID syntax, required): the account/identity associated with the event time (string with datetime syntax, required): an informal and non-authoritative estimate of when event was received. Intermediate services may decide to pass this field through as-is, or update to the current time #identity Events Indicates that there may have been a change to the indicated identity (meaning the DID document or handle), and optionally what the current handle is. Does not indicate what changed, or reliably indicate what the current state of the identity is. Event fields: seq (integer, required): same for all event types did (string with DID syntax, required): same for all event types time (string with datetime syntax, required): same for all event types handle (string with handle syntax, optional): the current handle for this identity. May be handle.invalid if the handle does not currently resolve correctly. Presence or absence of the handle field does not indicate that it is the handle which has changed. The semantics and expected behavior are that downstream services should update any cached identity metadata (including DID document and handle) for the indicated DID. They might mark caches as stale, immediately purge cached data, or attempt to re-resolve metadata. Identity events are emitted on a "best-effort" basis. It is possible for the DID document or handle resolution status to change without any atproto service detecting the change, in which case an event would not be emitted. It is also possible for the event to be emitted redundantly, when nothing has actually changed. Intermediate services (eg, relays) may chose to modify or pass through identity events: they may replace the handle with the result of their own resolution; or always remove the handle field; or always pass it through unaltered they may filter out identity events if they observe that identity has not actually changed they may emit identity events based on changes they became aware of independently (eg, via periodic re-validation of handles) #account Events Indicates that there may have been a change in Account Hosting status at the service which emits the event, and what the new status is. For example, it could be the result of creation, deletion, or temporary suspension of an account. The event describes the current hosting status, not what changed. Event Fields: seq (integer, required): same for all event types did (string with DID syntax, required): same for all event types time (string with datetime syntax, required): same for all event types active (boolean, required): whether the repository is currently available and can be redistributed status (string, optional): string status code which describes the account state in more detail. Known values include: takendown : indefinite removal of the repository by a service provider, due to a terms or policy violation suspended : temporary or time-limited variant of takedown deleted : account has been deactivated, possibly permanently. deactivated : temporary or indefinite removal of all public data by the account themselves. When coming from any service which redistributes account data, the event describes what the new status is at that service , and is authoritative in that context. In other words, the event is hop-by-hop for repository hosts and mirrors. See the Account Hosting specification for more details. #commit Events This event indicates that there has been a new repository commit for the indicated account. The event usually contains the "diff" of repository data, in the form of a CAR slice. See the Repository specification for details on "diffs" and the CAR file format. See the Repository specification for more details around repo diffs. Event Fields: seq (integer, required): same for all event types repo (string with DID syntax, required): the same as did for all other event types time (string with datetime syntax, required): same for all event types rev (string with TID syntax, required): the revision of the commit. Must match the rev in the commit block itself. since (string with TID syntax, nullable): indicates the rev of a preceding commit, which the the repo diff contains differences from commit (cid-link, required): CID of the commit object (in blocks ) tooBig (boolean, required): if true, indicates that the repo diff was too large, and that blocks , ops , and complete blobs are not all included blocks (bytes, required): CAR "slice" for the corresponding repo diff. The commit object must always be included. ops (array of objects, required): list of record-level operations in this commit: specific records created, updated, deleted blobs (array of cid-link, required): set of new blobs (by CID) referenced by records in this commit Commit events are broadcast when the account repository changes. Commits can be "empty", meaning no actual record content changed, and only the rev was incremented. They can contain a single record update, or multiple updates. Only the commit object, record blocks, and MST tree nodes are authenticated (signed): the since , ops , blobs , and tooBig fields are not self-certifying, and could in theory be manipulated, or otherwise be incorrect or incomplete. If since is not included, the commit should include the full repo tree, or set the tooBig flag. If the tooBig flag is set, then the amount of updated data was too much to be serialized in a single stream event message. Downstream services which want to maintain complete synchronized copies for the repo need to fetch the diff separately, as discussed below. Firehose Validation Best Practices A service which does full validation of upstream events has a number of properties to track and check. For example, Relay instances should fully validate content from PDS instances before re-broadcasting. Here is a summary of validation rules and behaviors: services should independently resolve identity data for each DID. They should ignore #commit events for accounts which do not have a functioning atproto identity (eg, lacking a signing key, or lacking a PDS service entry, or for which the DID has been tombstoned) services which subscribe directly to PDS instances should keep track of which PDS is authoritative for each DID. They should remember the host each subscription (WebSocket) is connected to, and reject #commit events for accounts if they come from a stream which does not correspond to the current account for that DID services should track account hosting status for each DID, and ignore #commit events for events which are not active services should verify commit signatures for each #commit event, using the current identity data. If the signature initially fails to verify, the service should refresh the identity metadata in case it had recently changed. Events with conclusively invalid signatures should be rejected. services should reject any event messages which exceed reasonable limits. A reasonable upper bound for producers is 5 MBytes (for any event stream message type). The subscribeRepos Lexicon also limits blocks to one million bytes, and ops to 200 entries. Commits with too much data must use the tooBig mechanism, though such commits should generally be avoided in the first place by breaking them up in to multiple smaller commits. services should verify that repository data structures are valid against the specification. Missing fields, incorrect MST structure, or other protocol-layer violations should result in events being rejected. services may apply rate-limits to identity, account, and commit events, and suspend accounts or upstream services which violate those limits. Rate limits might also be applied to recovery modes such as invalid signatures resulting in an identity refresh, tooBig events, missing or out-of-order commits, etc. services should ignore commit events with a rev lower or equal to the most recent processed rev for that DID, and should reject commit events with a rev corresponding to a future timestamp (beyond a clock drift window of a few minutes) services should check the since value in commit events, and if it is not consistent with the previous seen rev for that DID (see discussion in "Reliable Synchronization"), mark the repo as out-of-sync (similar to a tooBig commit event) data limits on records specifically should be verified. Events containing corrupt or entirely invalid records may be rejected. for example, a record not being CBOR at all, or exceeding normal data size limits. more subtle data validation of records may be enforced, or may be ignored, depending on the service. For example, unsupported CID hash types embedded in records should probably be ignored by Relays (even if they violate the atproto data model), but may result in the record or commit event being rejected by an AppView mirroring services, which retain a full copy of repository data, should verify that commit diffs leave the MST tree in a complete and valid state (eg, no missing records, no invalid MST nodes, commit CID would be reproducible if the MST structure was re-generated from scratch) Relays (specifically) should not validate records against Lexicons Reliable Synchronization This section describes some details on how to reliably subscribe to the firehose and maintain an existing synchronized mirror of the network. Services should generally maintain a few pieces of state for all accounts they are tracking data from: track the most recent commit rev they have successfully processed keep cached identity data, and use cache expiration to ensure periodic re-validation of that data track account status Identity caches should be purged any time an #identity event is received. Additionally, identity resolution should be refreshed if a commit signature fails to verify, in case the signing key was updated but the identity cache has not been updated yet. When tooBig events are emitted on the firehose, downstream services will need to fetch the diff out-of-band. This usually means an API request to the com.atproto.sync.getRepo endpoint on the current PDS host for the account, with the since field included. The since value should be the most recently processed rev value for the account, which may or may not match the since field in the commit event message. If a #commit is received with a since that does not match the most recently processed rev for the account, and is “later” (higher value) than the most recent commit rev the service has processed for that account, the service may need to do the same kind of out-of-band fetch as for a tooBig event. Services should keep track of the seq number of their upstream subscriptions. This should be stored separately per-upstream, even if there is only a single Relay connection, in case a different Relay is subscribed to in the future (which will have different seq numbers). Events can be processed concurrently, but they should be processed sequentially in-order for any given account. This can be accomplished by partitioning multiple workers using the repo DID as a partitioning key. Services can confirm that they are consuming content reliably by fetching a snapshot of repository DIDs and rev numbers from other services, including PDS hosts and Relay instances. After a short delay, these can be compared against the current state of the service to identify any accounts which have lower than expected rev numbers. These repos can then be updated out-of-band. Bootstrapping a Live Mirror The firehose can be used to follow new data updates, and repo exports can be used for snapshots. Actually combining the two to bootstrap a complete live-updating mirror can be a bit tricky. One approach is described below. Keep a sync status table for all accounts (DIDs) encountered. The status can be: dirty : there is either no local repo data for this account, or it has gotten out of sync in-process : the repo is "dirty", but there is a background task in process to update it synchronized : a complete copy of the repository has been processed Start by subscribing to the full firehose. If there is no existing repository data for the account, mark the account as "dirty". When new events come in for a repo, the behavior depends on the repo state. If it is "dirty", the event is ignored. If the state is "synchronized", the event is immediately processed as an update to the repo. If the state is "in-process", the event is enqueued locally. Have a set of background workers start processing "dirty" repos. First they mark the status as in-process , so that new events are enqueued locally. Then the full repo export (CAR file) is fetched from the PDS and processed in full. The commit rev of the repo export is noted. When the full repo import is complete, the worker can start processing any enqueued events, in order, skipping any with a rev lower than the existing repo processed rev (as is the usual behavior). When the queue for the account is fully processed, the state can be flipped to synchronized , and the worker can move on. After some time, most of the known accounts will be marked as synchronized , though this will only represent the most recently active accounts in the network. Next a more complete set of repositories in the network can be fetched, for example using an API query against an existing large service. Any new identified accounts can be marked as dirty in the service, and the background workers can start processing them. When all of the accounts are synchronized , the process is complete. At large scale it may be hard to get perfect synchronization: PDS instances may be down at various times, identities may fail to resolve, or invalid events, data, or signatures may end up in the network. Usage and Implementation Guidelines Guidelines for specific firehose event sequencing during different account events are described in an Account Lifecycle Best Practices guide . Security Concerns General mitigations for resource exhaustion attacks are recommended: event rate-limits, data quotas per account, limits on data object sizes and deserialized data complexity, etc. Care should always be taken when making network requests to unknown or untrusted hosts, especially when the network locators for those host from from untrusted input. This includes validating URLs to not connect to local or internal hosts (including via HTTP redirects), avoiding SSRF in browser contexts, etc. To prevent traffic amplification attacks, outbound network requests should be rate-limited by host. For example, identity resolution requests when consuming from the firehose, including DNS TXT traffic volume and DID resolution requests. Future Work The subscribeRepos Lexicon is likely to be tweaked, with deprecated fields removed, even if this breaks Lexicon evolution rules. The event stream sequence/cursor scheme may be iterated on to support sharding, timestamp-based resumption, and easier failover between independent instances. Alternatives to the full authenticated firehose may be added to the protocol. For example, simple JSON serialization, filtering by record collection type, omitting MST nodes, and other changes which would simplify development and reduce resource consumption for use-cases where full authentication is not necessary or desired. Previous Event Stream Next DID © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/suprsend-a-unified-notification-platform-for-mobile-apps-with-powerful-email-support | SuprSend: A Unified Notification Platform for Mobile Apps With Powerful Email Support Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Email management SuprSend: A Unified Notification Platform for Mobile Apps With Powerful Email Support Nikita Navral • December 11, 2025 TABLE OF CONTENTS Building notifications for a mobile app often starts simple - send a push, send an email. Then reality hits. You need routing logic when push fails, consistent templates across channels, detailed logs, preference controls, personalized content, and automation that scales. What used to be a small feature becomes a sprawling infrastructure project. SuprSend solves that entire problem space with one API. It gives mobile teams a single platform to deliver notifications across push, email, in-app, SMS, WhatsApp, Slack, Teams, and more, while coordinating fallbacks, templates, workflows, and analytics in one place. Developers integrate once. Product teams get full control. Users receive messages that feel timely, relevant, and aligned with their preferences. Multi-Channel Support Designed for Mobile Apps Mobile apps need more than push alone. SuprSend provides: • Mobile push across iOS, Android, React Native, Flutter • Email through any major provider (SendGrid, SES, Mailgun, etc.) • In-app inbox with real-time sync • SMS, WhatsApp, Slack, Teams, and more All channels share a unified API, so you never stitch together provider-specific logic again. One integration unlocks every channel you need, and you can add more without touching your app code. SuprSend customers like Teachmint and Delightree used this multi-channel setup to move from email-only systems to robust push + inbox + email experiences that doubled engagement. Cross-Channel Routing That Ensures Delivery When a push notification goes unseen, SuprSend automatically routes the message through email or another fallback channel without duplication or noise. Smart routing considers: • User preferences • Channel availability • Recent activity • Previous notification outcomes This increases seen rates and reduces cost. Refrens , for example, used inbox-first routing with timed fallback to email and saw a 144% engagement lift . Template Management That Works for Both Push and Email Instead of maintaining separate pipelines for push and email, SuprSend centralizes template management: • Channel-specific variations • Shared components across channels • Version control + rollback • Multi-language support • Visual editing with real-time preview Teams can iterate quickly without developer involvement. Freightify , Teachmint , and Artwork Flow used this to ship dynamic, branded templates that previously required days of engineering effort. Developer Experience Built for Speed SuprSend is API-first: • SDKs for iOS, Android, React Native, Flutter, Node, Python, Java, Go • Real-time message logs for debugging • Step-by-step delivery tracing per user • Staging vs production environments • CI/CD-friendly workflow APIs CrazyGames cut notification deployment time from weeks to hours by moving templates and logic out of code and into SuprSend’s workflow engine. Case studies repeatedly highlight its “integration in a single sprint” experience: Evocalize , a B2B2C platform, migrated core notifications with just one backend engineer. Reliable Delivery at Scale SuprSend handles: • Retries, failovers, and state management • High-volume mobile push + email throughput • Multi-region deployment • SLAs and enterprise reliability Whether it's sending weather risk alerts ( Solar Informatics ) or real-time operational updates ( eShipz ), SuprSend ensures that critical notifications actually reach users. Personalization, Segmentation, and Preferences Users expect notifications that feel relevant not noisy. SuprSend gives apps everything needed to tailor communication: • Dynamic data in templates (Handlebars-based) • Preference center out of the box • Category, frequency, and channel-level controls • Multi-tenant preference logic for B2B2C apps Topmate , Delightree , and Evocalize used these capabilities to improve user trust and reduce churn, while letting end users fine-tune how they receive notifications. Automation & Delivery Intelligence Mobile apps rely on the right message delivered at the right moment. SuprSend’s workflow engine supports: • Event-triggered workflows • Timezone-aware sending • Delays, batching, and digesting • Multi-step onboarding and reminder flows • Conditional branching and escalation • Sequence building with no-code editor Teachmint used digests to cut notification noise while doubling engagement. Topmate built multi-step funnels for creators directly on top of SuprSend workflows. Analytics & Observability That Reduce Guesswork SuprSend provides: • Delivery, open, click, latency, and failure insights • Consolidated logs across push and email • Real-time debugging down to the user level • Workflow-level performance metrics Logs and analytics were a major reason companies switched from in-house systems or OneSignal-style tools, where visibility was limited. Security, Compliance & Data Residency SuprSend meets five major frameworks: SOC 2, ISO 27001, GDPR, HIPAA, CPRA Data stays in your selected region (US, EU, APAC) with regional isolation and AWS-backed infrastructure. This gives mobile apps the compliance foundation needed for enterprise and global scale. Why Mobile Teams Choose SuprSend Across customer stories, a consistent pattern emerges: • Faster integration (hours or days, not months) • Better reliability across push + email • Centralized templates + workflows • Complete visibility and debugging • Users stay more engaged • Developers stop maintaining notification code Real outcomes: • 2× engagement (Delightree) • 144% higher interaction with app inbox (Refrens) • 30% uplift in win rate (Freightify) • 27% more programs launched (Evocalize) • 3 weeks shaved off onboarding (eShipz) Final Takeaway Mobile notifications today demand orchestration, intelligence, reliability, and personalization—not just sending. SuprSend gives mobile teams everything required to deliver push and email notifications that are coordinated, consistent, and user-friendly, without the engineering overhead of building infrastructure in-house. One API. All channels. Full control. No fragmentation. Learn more at SuprSend.com Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://x.com/en/tos | X Terms of Service Skip to main content Terms of Service <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-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 u01b__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-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-close="<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewbox="0 0 24 24" style="enable-background:new 0 0 24 24;" xml:space="preserve" aria-hidden="true" focusable="false" role="none" class="twtr-icon--md"> <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-search="<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="M22.06 19.94l-3.73-3.73C19.38 14.737 20 12.942 20 11c0-4.97-4.03-9-9-9s-9 4.03-9 9 4.03 9 9 9c1.943 0 3.738-.622 5.21-1.67l3.73 3.73c.292.294.676.44 1.06.44s.768-.146 1.06-.44c.586-.585.586-1.535 0-2.12zM11 17c-3.308 0-6-2.692-6-6s2.692-6 6-6 6 2.692 6 6-2.692 6-6 6z" /> </svg>" data-icon-search-submit="<svg width="21" height="21" viewbox="0 0 21 21" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" role="none" class="twtr-icon"> <path fill-rule="evenodd" clip-rule="evenodd" d="M16.33 14.21L20.06 17.94C20.646 18.525 20.646 19.475 20.06 20.06C19.768 20.354 19.384 20.5 19 20.5C18.616 20.5 18.232 20.354 17.94 20.06L14.21 16.33C12.738 17.378 10.943 18 9 18C4.03 18 0 13.97 0 9C0 4.03 4.03 0 9 0C13.97 0 18 4.03 18 9C18 10.942 17.38 12.737 16.33 14.21ZM3 9C3 12.308 5.692 15 9 15C12.308 15 15 12.308 15 9C15 5.692 12.308 3 9 3C5.692 3 3 5.692 3 9Z" fill="white" /> </svg>" data-bg-color="white-neutral" data-root-page-title="Terms of Service" data-search-placeholder="Search" data-search-query-key="q" data-search-query-type="?" data-scribe-element="RJPO" data-scribe-section="u01b-navigation" data-cta-enabled="true" data-cta-text="Download PDF" data-cta-link="https://cdn.cms-twdigitalassets.com/content/dam/legal-twitter/site-assets/terms-of-service-2025-05-08/en/x-terms-of-service-2025-05-08.pdf" data-cta-link-new-tab="true"> Terms of Service We have made some updates to our Terms of Service. This version of the Terms of Service will go into effect on January 15, 2026. Until then, the current Terms of Service continue to apply. Summary of our Terms These Terms of Service (“Terms”) are part of the User Agreement – a legally binding contract governing your relationship with X. You should read these Terms in full, but here are a few key things you should take away: You will see advertising on the platform: In exchange for accessing the Services, X and our third-party providers and partners may display advertising to you. When posting Content and otherwise using the Services, you must comply with this User Agreement and Applicable Law: You are responsible for your use of the Services and your Content. You must comply with the User Agreement, including all applicable policies and rules, and all applicable laws. You must abide by the Services’ acceptable use terms: You may not access the Services in any way other than through the currently available, published interfaces that we provide. For example, this means that you cannot scrape the Services without X’s express written permission, try to work around any technical limitations we impose, or otherwise attempt to disrupt the operation of the Services. We have broad enforcement rights: X reserves the right to take enforcement actions against you if you do violate these terms, such as, for example, removing your Content, limiting visibility, discontinuing your access to X, or taking legal action. Certain jurisdictions, including the European Union and the United Kingdom, also impose obligations on X to enforce against not only illegal content but also categories of content deemed by law to be “harmful” or “unsafe.” As a result, your Content or account may be subject to restrictions in those jurisdictions. We may also suspend or terminate your account for other reasons, such as prolonged inactivity, risk of legal exposure, or commercial inviability. There are intellectual property licenses in these Terms: You retain ownership and rights to any of your Content you post or share, and you provide us with a broad, royalty-free license to make your Content available to the rest of the world and to let others do the same. Conversely, we provide you a license to use the software we provide as part of the Services, such as the X mobile application, solely for the purpose of enabling you to use and enjoy the benefit of the Services. Your use of the Services is at your own risk: We provide the Services on an “AS IS” and “AS AVAILABLE” basis, and we disclaim all warranties, responsibility, and liability to you or others to the extent permitted by law. You may be exposed to offensive or harmful Content posted by other users. The Services may change from time to time, and we may limit or terminate availability of the Services or particular features to you or other users at any time. You have remedies and redress mechanisms, but our liability is limited: You have a right to terminate this agreement at any time by deactivating your account and discontinuing use of the Services. Depending on your country of residence, we may not be liable for certain types of damages as described in the agreement, and in any event, our aggregate liability shall not exceed the greater of $100 USD or the amount you paid us, if any, in the past six months for the Services giving rise to the claim. Further, if you believe that your Content has been displayed on the Services in an unauthorized manner that constitutes copyright infringement, the reporting process is detailed in these Terms. If you are a recipient of the X Service in the United Kingdom, you may challenge enforcement actions (such as Content removal or account suspension) that breach these Terms by filing a complaint through our internal complaints process or by bringing a claim in a competent court, as provided under the Online Safety Act 2023. You can find details on how to file a complaint here . If you are a recipient of the X Service in the European Union, you may challenge certain decisions we make under the Digital Services Act (Regulation (EU) 2022/2065) via our internal process or via out-of-court dispute settlement as described here . Please also note that these Terms incorporate our Privacy Policy ( https://x.com/privacy ) as well as other terms applicable to your use of the Services and your Content. Finally, these Terms may vary depending on where you live, but in any case, you must be at least 13 years old to use X. If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States, the X User Agreement comprises these Terms of Service , our Privacy Policy , our Rules and Policies , and all incorporated policies. If you live in the European Union, EFTA States, or the United Kingdom, the X User Agreement comprises these Terms of Service , our Privacy Policy , our Rules and Policies , and all incorporated policies. X Terms of Service If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States These Terms of Service (“Terms”) govern your relationship with us and your and other users’ access to and use of, and anything otherwise relating to, our or our corporate affilitates’ services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.x.com/rules-and-policies/x-services-and-corporate-affiliates ) that link to these Terms (collectively, the “Services”), and any information, text, links, graphics, photos, audio, videos, or other materials or arrangements of materials uploaded, downloaded or appearing on the Services (collectively referred to as “Content”). By using the Services you agree to be bound by these Terms. These Terms are an agreement between you and X Corp., which provides X and the Services, with its registered office at 865 FM 1209, Building 2, Bastrop, TX 78602 U.S.A. The words “we,” “us,” and “our” mean X Corp. 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Disclaimers and Limitations of Liability 6. General 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Disclaimers and Limitations of Liability 6. General 1. Who May Use the Services You may use the Services only if you agree to form a binding contract with us and are not a person barred from receiving services under the laws of the applicable jurisdiction. In any case, you must be at least 13 years old to use the Services. If you are (i) accepting these Terms and/or using the Services, which constitutes acceptance of these Terms, or (ii) accepting these Terms in order to authorize the use of the Services on behalf of a minor (being any person under the age of majority in any given country), company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so or, as the case may be, have the authority to bind such minor and/or entity to these Terms. The words “you” and “your” as used in these Terms shall refer either to the person accepting these Terms or such minor (as defined in (i)) and/or the entity referenced in (ii), as applicable. 2. Privacy Our Privacy Policy ( https://x.com/privacy ) describes how we handle the information you provide to us when you use the Services. You understand that through your use of the Services you consent to the collection and use (as set forth in the Privacy Policy) of this information, including the transfer of this information to the United States, Ireland, and/or other countries for storage, processing and use by us and our affiliates. 3. Content on the Services You are responsible for your use of the Services and for any Content, including anything referenced therein, you provide, create, post, or otherwise utilize, including any inputs, prompts, outputs, and/or information obtained or created through the Services. It is your responsibility to comply with all applicable laws, rules, policies, and regulations that are applicable to you or your Content, including on a third party’s or our affiliates’ services. You should only provide, create, or generate Content that you are comfortable sharing with others. Any use or reliance on any Content or materials posted via the Services or obtained by you through the Services is at your own risk. We do not endorse, support, represent or guarantee the completeness, truthfulness, accuracy, or reliability of any Content or communications posted or otherwise obtained via the Services or endorse any alleged facts or opinions expressed via the Services. You understand that by using the Services, you may be exposed to Content that might be offensive, harmful, inaccurate or otherwise inappropriate, or in some cases, postings that have been mislabeled or are otherwise deceptive. All Content, including anything referenced therein, is the sole responsibility of the person who posted, generated, inputted, or created such Content. We may not monitor or control the Content posted, generated, inputted, or created via the Services, and we cannot take responsibility for such Content. We reserve the right to remove Content that violates the User Agreement, including for example, copyright or trademark violations or other intellectual property misappropriation, impersonation, unlawful conduct, or harassment. Certain jurisdictions, including the European Union and the United Kingdom, impose obligations on us to enforce against categories of content deemed by law to be harmful or unsafe, such as bullying and humiliating content, content that promotes or encourages feeding or eating disorders, as well as content that encourages or makes available knowledge of methods of self-harm and suicide. As a result, your Content may be subject to restrictions as required by these jurisdictions. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.x.com/rules-and-policies , https://help.x.com/rules-and-policies/x-report-violation#specific-violations , and https://help.x.com/managing-your-account/suspended-x-accounts ). If you believe that your Content has been copied in a way that constitutes copyright infringement, please report this by visiting our Copyright reporting form ( https://help.x.com/forms/ipi ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 865 FM 1209, Building 2 Bastrop, TX 78602 Reports: https://help.x.com/forms/ipi Email: copyright@x.com Your Rights and Grant of Rights in the Content You retain your rights to any Content, including anything referenced therein, you submit, input, create, generate, post, or display on or through the Services. What’s yours is yours — you own your Content (and your incorporated audio, photos, and videos are considered part of the Content). In choosing to submit, input, create, generate, post, or display Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display, upload, download, and distribute such Content, including anything referenced therein, in any and all media or distribution methods now known or later developed, for any purpose. For clarity, these rights include, for example, curating, transforming, and translating. This license authorizes us to make your Content available to the rest of the world and to let others do the same. You agree that this license includes the right for us to (i) analyze text and other information you provide and to otherwise provide, promote, and improve the Services, including, for example, for use with and training of our machine learning and artificial intelligence models, whether generative or another type; and (ii) to make Content submitted to or through the Services available to other companies, organizations or individuals, including, for example, for improving the Services and the syndication, broadcast, distribution, repost, promotion or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Such additional uses by us, or other companies, organizations or individuals, is made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services as the use of the Services by you is hereby agreed as being sufficient compensation for the Content and grant of rights herein. We have an evolving set of rules for how ecosystem partners can interact with your Content on the Services. These rules exist to enable an open ecosystem with your rights in mind. You understand that we may modify or adapt your Content as it is distributed, syndicated, published, or broadcast by us and our partners and/or make changes to your Content in order to adapt the Content to different media. You represent and warrant that you have, or have obtained, all rights, licenses, consents, permissions, power and/or authority necessary to grant the rights granted herein for any Content that you input, submit, create, post, generate, or display on or through the Services. You agree and warrant that such Content does not contain material subject to copyright or other proprietary rights, unless you have obtained the necessary permissions or are otherwise legally entitled to post or otherwise use the material and to grant us the license described above. 4. Using the Services Please review our Rules and Policies , which are part of the User Agreement and outline conduct that is prohibited on the Services, as well as categories of content deemed by law to be harmful or unsafe in certain jurisdictions. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. X takes enforcement actions when Content or user behavior is in violation of our Rules and Policies or in relation to sensitive media. You can review X’s enforcement options and how you can appeal our enforcement decision here . The Services evolve constantly. As such, the Services may change from time to time, at our discretion. We may stop (permanently or temporarily) providing the Services or any features within the Services to you or to users generally. We also retain the right to create limits on use and storage at our sole discretion at any time. We may also remove or refuse to distribute any Content on the Services, limit distribution or visibility of any Content on the service, suspend or terminate users, and reclaim usernames without liability to you. In consideration for our granting you access to and use of the Services, you agree that we and our third-party providers and partners may place advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. We also reserve the right to access, read, preserve, and disclose any information as we reasonably believe is necessary to (i) satisfy any applicable law, regulation, legal process or governmental request; (ii) enforce the Terms, including investigation of potential violations hereof; (iii) detect, prevent, or otherwise address fraud, security or technical issues; (iv) respond to user support requests; or (v) protect the rights, property or safety of X, its users and the public. We do not disclose personally-identifying information to third parties except in accordance with our Privacy Policy . Certain services or features may be offered on X for which additional terms and conditions may apply in connection with your use of those services. By using or paying for any of these additional services, you agree to any additional terms applicable to those services, and those additional terms become part of our agreement with you. If any of the applicable additional terms conflict with these Terms, the additional terms will prevail while you are using those services to which they apply. If you use paid features, products, or services of the Services, you agree to the applicable Terms for Paid Services ( https://legal.x.com/purchaser-terms ). If you use developer features, products, or services of the Services, including but not limited to X for Websites ( https://developer.x.com/docs/x-for-websites ), X Cards ( https://developer.x.com/docs/x-for-websites/cards/overview/abouts-cards ), Public API ( https://developer.x.com/docs ), or Sign in with X ( https://docs.x.com/resources/fundamentals/authentication/guides/log-in-with-x ), you agree to our Developer Agreement ( https://developer.x.com/developer-terms/agreement ) and Developer Policy ( https://developer.x.com/developer-terms/policy ). If you want to reproduce, modify, create derivative works, distribute, sell, transfer, publicly display, publicly perform, transmit, or otherwise use the Services or Content on the Services, you must use the interfaces and instructions we provide, except as permitted through the Services, these Terms, or the terms provided on https://developer.x.com/developer-terms . Otherwise, all such actions are strictly prohibited. If you are a security researcher, you are required to comply with the rules of our Vulnerability Reporting Program ( https://hackerone.com/x ). The requirements set out in the preceding paragraph may not apply to those participating in our Vulnerability Reporting Program. If you use advertising features, products, or services of the Services in any way, including but not limited to self-service and managed service offerings, you agree that your use of the advertising features, products, and services as well as your advertisements are subject to the terms of our Master Services Agreement ( https://ads.x.com/terms ). Your Account You may need to create an account to use the Services. You are responsible for safeguarding your account, so use a strong password and limit its use to this account, and use two-factor authentication via an authenticator app or security key. We cannot and will not be liable for any loss or damage arising from your failure to comply with the above. You can control most communications from the Services. We may need to provide you with certain communications, such as service announcements and administrative messages. These communications are considered part of the Services and your account, and you may not be able to opt-out from receiving them. If you added your phone number to your account and you later change or deactivate that phone number, you must update your account information to help prevent us from communicating with anyone who acquires your old number. Your License to Use the Services We give you a personal, worldwide, royalty-free, non-assignable and non-exclusive license to use the software provided to you as part of the Services. This license cannot be assigned, gifted, sold, shared or transferred in any other manner to any other individual or entity without X’s express written consent. This license has the sole purpose of enabling you to use and enjoy the benefit of the Services as provided on X, in the manner permitted by these Terms. The Services are protected by copyright, trademark, and other laws of both the United States and other countries. Nothing in the Terms gives you a right to use the X name or Twitter name or any of the X or Twitter trademarks, logos, domain names, other distinctive brand features, and other proprietary rights, and you may not do so without our express written consent. All right, title, and interest in and to the Services (excluding Content provided by users) are and will remain our and our licensors' exclusive property. Any feedback, comments, or suggestions you may provide regarding X, or the Services is entirely voluntary and we will be free to use such feedback, comments or suggestions as we see fit and without any obligation to you. Misuse of the Services You also agree not to misuse the Services, for example, by interfering with them or accessing them using a method other than the interface and the instructions that we provide. You agree that you will not work around any technical limitations in the software provided to you as part of the Services, or reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits. You may not do any of the following while accessing or using the Services: (i) access, tamper with, or use non-public areas of the Services, our computer systems, or the technical delivery systems of our providers; (ii) probe, scan, or test the vulnerability of any system or network or breach or circumvent any security or authentication measures; (iii) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through our currently available, published interfaces that are provided by us (and only pursuant to the applicable terms and conditions), unless you have been specifically allowed to do so in a separate agreement with us (NOTE: crawling or scraping the Services in any form, for any purpose without our prior written consent is expressly prohibited); (iv) attempt to circumvent, manipulate, or disable systems and Services, including through "jailbreaking", “prompt engineering or injection", or other methods intended to override or manipulate safety, security or other platform controls; (v) forge any TCP/IP packet header or any part of the header information in any email or posting; (vi) in any way use the Services to send altered, deceptive or false source-identifying information; (vii) engage in any conduct that violates our Platform Manipulation and Spam Policy or any other Rules and Policies , including our Misuse of Reporting Features Policy ; or (viii) interfere with, or disrupt, (or attempt to do so), the access of any user, host or network, including, without limitation, sending a virus, overloading, flooding, spamming, mail-bombing the Services, or by scripting the creation of Content in such a manner as to interfere with or create an undue burden on the Services. It is also a violation of these Terms to facilitate or assist others in violating these Terms, including by distributing products or services that enable or encourage violation of these Terms. Ending These Terms You may end your legal agreement with us at any time by deactivating your accounts and discontinuing your use of the Services. See https://help.x.com/managing-your-account/how-to-deactivate-x-account for instructions on how to deactivate your account and the Privacy Policy for more information on what happens to your information. We may suspend or terminate your account or cease providing you with all or part of the Services at any time if we reasonably believe: (i) you have violated these Terms or our Rules and Policies , (ii) you create risk or possible legal exposure for us; (iii) your account should be removed due to unlawful conduct; (iv) your account should be removed due to prolonged inactivity; or (v) our provision of the Services to you is no longer commercially viable. We will make reasonable efforts to notify you by the email address associated with your account or the next time you attempt to access your account, depending on the circumstances. To the extent permitted by law, we may also terminate your account or cease providing you with all or part of the Services for any other reason or no reason at our convenience. In all such cases, the Terms shall terminate, including, without limitation, your license to use the Services, except that the following sections shall continue to apply: 2, 3, 5, 6, and the misuse provisions of Section 4 (“Misuse of the Services”). If you believe your account was terminated in error you can file an appeal following the steps found in our Help Center ( https://help.x.com/forms/account-access/appeals ). For the avoidance of doubt, these Terms survive the deactivation or termination of your account. 5. Disclaimers and Limitations of Liability The Services are Available "AS-IS" Your access to and use of the Services or any Content are at your own risk. You understand and agree that the Services are provided to you on an “AS IS” and “AS AVAILABLE” basis. The “X Entities” refers to X Corp., its parents, affiliates, related companies, officers, directors, employees, agents, representatives, partners, and licensors. Without limiting the foregoing, to the maximum extent permitted under applicable law, THE X ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The X Entities make no warranty or representation and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content; (ii) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or any Content; (iii) the deletion of, or the failure to store or to transmit, any Content and other communications maintained by the Services; and (iv) whether the Services will meet your requirements or be available on an uninterrupted, secure, or error-free basis. No advice or information, whether oral or written, obtained from the X Entities or through the Services, will create any warranty or representation not expressly made herein. Limitation of Liability NOTWITHSTANDING ANY OTHER TERMS TO THE CONTRARY, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE X ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, RELIANCE OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (i) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE SERVICES; (ii) ANY CONDUCT OR CONTENT OF ANY USER OR THIRD PARTY ON THE SERVICES, INCLUDING WITHOUT LIMITATION, ANY DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OF OTHER USERS OR THIRD PARTIES; (iii) ANY CONTENT OBTAINED FROM THE SERVICES; OR (iv) UNAUTHORIZED ACCESS, USE OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT. IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE X ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID US, IF ANY, IN THE PAST SIX MONTHS FOR THE SERVICES GIVING RISE TO THE CLAIM. THE LIMITATIONS OF THIS SUBSECTION SHALL APPLY TO ANY THEORY OF LIABILITY, WHETHER BASED ON WARRANTY, CONTRACT, STATUTE, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND WHETHER OR NOT THE X ENTITIES HAVE BEEN INFORMED OF THE POSSIBILITY OF ANY SUCH DAMAGE, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. IN THE EVENT ANY PORTION OF THESE LIMITATION OF LIABILITY PROVISIONS IS DEEMED UNENFORCEABLE AS A MATTER OF LAW, THAT LIMITATION SHALL INSTEAD BE THE GREATEST LIMITATION PERMITTED BY LAW. BY AGREEING TO THESE TERMS OR USING THE SERVICES, YOU AGREE, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THAT THE X ENTITIES ARE NOT RESPONSIBLE OR LIABLE TO YOU OR OTHERS FOR THE ACTIONS OR CONDUCT OF USERS AND THIRD PARTIES ON THE SERVICES, OR FOR ANY CONTENT USERS AND THIRD PARTIES SHARE ON THE SERVICES, INCLUDING OFFENSIVE, DEFAMATORY, ILLEGAL OR OTHER OBJECTIONABLE CONTENT. Liquidated Damages Protecting our users’ data and our system resources is important to us. You further agree that, to the extent permitted by applicable law, if you violate the Terms, or you induce or knowingly facilitate others to do so, in addition to all other legal remedies available to us, you will be jointly and severally liable to us for liquidated damages as follows for requesting, viewing, or accessing more than 1,000,000 posts (including reply posts, video posts, image posts, and any other posts) in any 24-hour period - $15,000 USD per 1,000,000 posts. You agree that these amounts are (i) a reasonable estimate of our damages; (ii) not a penalty; and (iii) not otherwise limiting of our ability to recover from you or others under any legal or equitable theory or claim, including but not limited to statutory damages and/or equitable relief. You further agree that repeated violations of these Terms will irreparably harm and entitle us to injunctive and/or other equitable relief, in addition to monetary damages. 6. General We may revise these Terms from time to time. The changes will not be retroactive, and the most current version of the Terms, which will always be at https://x.com/tos , will govern our relationship with you. We will try to notify you of material revisions, for example via a service notification or an email to the email associated with your account. By continuing to access or use the Services after those revisions become effective, you agree to be bound by the revised Terms. The laws of the State of Texas, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and us, notwithstanding any other agreement between you and us to the contrary. Notwithstanding any other agreement to the contrary, all disputes related to these Terms, the Services, or any patents — including without limitation disputes related to or arising from any Content (whether your or others’ Content), or your or others’ use of the Services or the complete or partial termination thereof — shall be brought and must proceed exclusively in the federal 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. For the avoidance of doubt, the choice of law and forum selection provisions of this paragraph shall apply regardless of whether a dispute or any claims contained therein are based in contract, tort, statute, common law, or otherwise, and the choice of law and forum selection provisions of this paragraph shall apply to pending and future disputes and shall apply to your dispute regardless of when the conduct relating to the dispute arose or occurred. The choice of law and forum selection provisions of this paragraph shall also extend to disputes involving our U.S. corporate affiliates, who are intended third-party beneficiaries of this paragraph. Without prejudice to the foregoing, you agree that, in its sole discretion, X may bring any claim, cause of action, or dispute we have against you in any competent court in the country in which you reside that has jurisdiction and venue over the claim. 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 against us or our corporate affiliates. If you are a federal, state, or local government entity in the United States using the Services 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, these Terms 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). You and X agree that you must initiate any proceeding or action asserting a federal claim within one (1) year of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Services. You and X agree that you must initiate any proceeding or action asserting a state law claim within two (2) years of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Services. Otherwise, to the extent permitted by applicable law, 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 barred. In the event that any provision of these Terms is held to be invalid or unenforceable, then that provision will be limited or eliminated to the minimum extent necessary, and the remaining provisions of these Terms will remain in full force and effect. Our failure to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. The X User Agreement is written in English but is made available in multiple languages through translations. X strives to make the translations as accurate as possible to the original English version. However, in case of any discrepancies or inconsistencies, the English language version of the X User Agreement shall take precedence. You acknowledge that English shall be the language of reference for interpreting and constructing the terms of the X User Agreement. If you have any questions about these Terms, please contact us . Effective: January 15, 2026 Archive of Previous Terms X Terms of Service If you live in the European Union, EFTA States, or the United Kingdom These Terms of Service (“Terms”) govern your relationship with us and your and other users’ access to and use of, and anything otherwise relating to, our or our corporate affiliates’ services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.x.com/rules-and-policies/x-services-and-corporate-affiliates ) that link to these Terms (collectively, the “Services”), and any information, text, links, graphics, photos, audio, videos, or other materials or arrangements of materials uploaded, downloaded or appearing on the Services (collectively referred to as “Content”). By using the Services you agree to be bound by these Terms. These Terms are an agreement between you and X Internet Unlimited Company (Co. number 503351, VAT number IE9803175Q), an Irish company, which provides X and the Services, with its registered office at One Cumberland Place, Fenian Street Dublin 2, D02 AX07 Ireland. The words “we,” “us,” and “our,” mean X Internet Unlimited Company. 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Limitations of Liability 6. General 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Limitations of Liability 6. General 1. Who May Use the Services You may use the Services only if you agree to form a binding contract with us and are not a person barred from receiving services under the laws of the applicable jurisdiction. In any case, you must be at least 13 years old to use the Services. If you are (i) accepting these Terms and/or using the Services, which constitutes acceptance of these Terms, or (ii) accepting these Terms in order to authorize the use of the Services on behalf of a minor (being any person under the age of majority in any given country), company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so or, as the case may be, have the authority to bind such minor and/or entity to these Terms. The words “you” and “your” as used in these Terms shall refer either to the person accepting these Terms or such minor (as defined in (i)) and/or the entity referenced in (ii), as applicable. 2. Privacy Our Privacy Policy ( https://x.com/privacy ) describes how we handle the information you provide to us when you use the Services. You understand that through your use of the Services you consent to the collection and use (as set forth in the Privacy Policy) of this information, including the transfer of this information to the United States, Ireland, and/or other countries for storage, processing and use by us and our affiliates. 3. Content on the Services You are responsible for your use of the Services and for any Content, including anything referenced therein, you provide, create, post, or otherwise utilize, including any inputs, prompts, outputs, and/or information obtained or created through the Services. It is your responsibility to comply with all applicable laws, rules, policies, and regulations that are applicable to you or your Content, including on a third party’s or affiliates’ services. You should only provide, create, or generate Content that you are comfortable sharing with others. Any use or reliance on any Content or materials posted via the Services or obtained by you through the Services is at your own risk. We do not endorse, support, represent or guarantee the completeness, truthfulness, accuracy, or reliability of any Content or communications posted or otherwise obtained via the Services or endorse any alleged facts or opinions expressed via the Services. You understand that by using the Services, you may be exposed to Content that might be offensive, harmful, inaccurate or otherwise inappropriate, or in some cases, postings that have been mislabeled or are otherwise deceptive. Content recommendations are made based on a combination of factors: how you engage with the Services, the topics you have indicated that you are interested in, and likes of other users with your similar interests. Adjustments can be made in your settings, and additional information can be found in our Help Center ( https://help.x.com/resources/recommender-systems ). All Content, including anything referenced therein, is the sole responsibility of the person who posted, generate, inputted, or created such Content. We may not monitor or control the Content posted, generated, inputted, or created via the Services, and we cannot take responsibility for such Content. We reserve the right to remove Content that violates the User Agreement, including for example, copyright or trademark violations or other intellectual property misappropriation, impersonation, unlawful conduct, or harassment. Certain jurisdictions, including the European Union and the United Kingdom, impose obligations on us to enforce against categories of content deemed by law to be harmful or unsafe, such as bullying and humiliating content, content that promotes or encourages feeding or eating disorders, as well as content that encourages or makes available knowledge of methods of self-harm and suicide. As a result, your Content may be subject to restrictions as required by these jurisdictions. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.x.com/rules-and-policies , https://help.x.com/rules-and-policies/x-report-violation , and https://help.x.com/managing-your-account/suspended-x-accounts ). If you believe that your Content has been copied in a way that constitutes copyright infringement, please report this by visiting our Copyright reporting form ( https://help.x.com/forms/ipi ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 865 FM 1209, Building 2 Bastrop, TX 78602 Reports: https://help.x.com/forms/ipi Email: copyright@x.com Your Rights and Grant of Rights in the Content You retain your rights to any Content, including anything referenced therein, you submit, input, create, generate, post, or display on or through the Services. What’s yours is yours — you own your Content (and your incorporated audio, photos, and videos are considered part of the Content). In choosing to submit, input, create, generate, post, or display Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display, upload, download, and distribute such Content, including anything referenced therein, in any and all media or distribution methods now known or later developed, for any purpose. For clarity, these rights include, for example, curating, transforming, and translating. This license authorizes us to make your Content available to the rest of the world and to let others do the same. However, if you have chosen via our features to limit the distribution of your Content to a restricted community, we will respect that choice. You also agree that this license includes the right to analyze text and other information you provide with the view to improve the Services. You agree that this license includes the right for us to (i) provide, promote, and improve the Services, including, for example, for use with and training of our machine learning and artificial intelligence models, whether generative or another type; and (ii) to make Content submitted to or through the Services available to other companies, organizations or individuals, including, for example, for improving the Services and the syndication, broadcast, distribution, repost, promotion or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Such additional uses by us, or other companies, organizations or individuals, is made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services as the use of the Services by you is hereby agreed as being sufficient compensation for the Content and grant of rights herein. We have an evolving set of rules for how ecosystem partners can interact with your Content on the Services. These rules exist to enable an open ecosystem with your rights in mind. You understand that we may modify or adapt your Content as it is distributed, syndicated, published, or broadcast by us and our partners and/or make changes to your Content in order to adapt the Content to different media. You represent and warrant that you have, or have obtained, all rights, licenses, consents, permissions, power and/or authority necessary to grant the rights granted herein for any Content that you input, submit, create, post, generate, or display on or through the Services. You agree and warrant that such Content does not contain material subject to copyright or other proprietary rights, unless you have obtained the necessary permissions or are otherwise legally entitled to post or otherwise use the material and to grant us the license described above. 4. Using the Services Please review our Rules and Policies , which are part of the User Agreement and outline conduct that is prohibited on the Services, as well as categories of content deemed by law to be harmful or unsafe in certain jurisdictions. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. X takes enforcement actions when Content or user behavior is in violation of our Rules and Policies or in relation to sensitive media. You can review X’s enforcement options and how you can appeal our enforcement decision here . The Services evolve constantly. As such, the Services may change from time to time, at our discretion. We may stop (permanently or temporarily) providing the Services or any features within the Services to you or to users generally. We also retain the right to create limits on use and storage at our sole discretion at any time. We may also remove or refuse to distribute any Content on the Services, limit distribution or visibility of any Content on the service, suspend or terminate users, and reclaim usernames if it is appropriate, including for the following reasons: (i) protecting the Services or our users; (ii) compliance with applicable laws or orders from competent authorities; (iii) breach of these Terms or our Rules and Policies or third parties' intellectual property or other rights; (iv) if you or your Content exposes us, other users or any third party to legal or regulatory risk; and/or (v) your prolonged inactivity. In consideration for our granting you access to and use of the Services, you agree that we and our third-party providers and partners may place advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. We also reserve the right to access, read, preserve, and disclose any information as we reasonably believe is necessary to (i) satisfy any applicable law, regulation, legal process or governmental request; (ii) enforce the Terms, including investigation of potential violations hereof; (iii) detect, prevent, or otherwise address fraud, security or technical issues; (iv) respond to user support requests; or (v) protect the rights, property or safety of X, its users and the public. We do | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/comparing-the-top-messaging-platforms-2025 | Comparing the Top Messaging Platforms (2025) Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Email management Comparing the Top Messaging Platforms (2025) Nikita Navral • December 2, 2025 TABLE OF CONTENTS Businesses rely on cloud communications platforms to power SMS alerts, authentication flows, customer engagement, and global voice calling. With so many options available, it’s important to understand how the major players differ in capabilities, pricing, and security. Below is a clear comparison of RingCentral, MessageBird, Plivo, Karix, Twilio, Sinch, Exotel, Telnyx, Ooma, Bandwidth, Gupshup, Vonage, and Amazon SNS - with key features, cost, and security included for each. Twilio Key Features: SMS/MMS, voice, WhatsApp, chat, email (SendGrid), video, global phone numbers, user authentication. Cost: Pay-as-you-go. US SMS ~ $0.0079 outbound; voice outbound ~ $0.014/min. SendGrid email plans start at $19.95/month. Security: HTTPS APIs, API key authentication, enterprise-grade controls depending on product. MessageBird (Bird) Key Features: SMS, WhatsApp, email, voice, multichannel inbox, 2FA/verify, omnichannel automation. Cost: US SMS ~ $0.008/message; WhatsApp from ~$0.005/message; dedicated numbers from ~$0.50/month. Security: ISO/IEC 27001:2013, SOC 2 Type II, GDPR-aligned, regulated under Dutch telecommunications authority. Plivo Key Features: SMS, MMS, voice APIs, WhatsApp, user verification APIs, Fraud Shield protection. Cost: US SMS ~ $0.0055/message; MMS ~ $0.018/message; plans also available starting around $25/month. Security: Fraud Shield for SMS fraud, standard API security, compliance frameworks appropriate for telecom workflows. Sinch Key Features: Global messaging, voice APIs, phone number provisioning, enterprise conversational tools, in-app voice/video SDKs. Cost: Pay-as-you-go; pricing varies by region and channel. Security: Enterprise security posture; used widely by large regulated businesses. RingCentral Key Features: Enterprise UCaaS and CCaaS — voice, video, messaging, contact center, team collaboration. Cost: Subscription-based; varies by seat and plan tier. Security: 99.999% uptime SLA, enterprise compliance standards, secure global network. Vonage Key Features: Business phone systems, unified communications, plus APIs for voice, SMS, video, messaging. Cost: Varies by product; SMS and voice pricing similar to other CPaaS players. Security: Industry-standard certifications (ISO 27001, HIPAA support in certain offerings). Bandwidth Key Features: Voice, messaging, emergency services APIs built on its own carrier network. Cost: Usage-based; typically competitive because Bandwidth owns telecom infrastructure. Security: Strong network-level security due to owning carrier backbone; enterprise-grade controls. Telnyx Key Features: Programmable voice, SMS, SIP trunking, wireless IoT, phone numbers; operates its own global private network. Cost: Generally lower than Twilio in many regions; usage-based for SMS/voice. Security: Private global network architecture, encrypted communications, strong compliance posture. Karix Key Features: SMS, voice, WhatsApp, and multichannel messaging, with strong performance in India/APAC. Cost: Pricing varies by region and volume; typically optimized for India and emerging markets. Security: Regional telecom compliance; enterprise messaging security standards. Exotel Key Features: Cloud telephony, IVR, virtual numbers, call routing, contact-center tools, SMS, WhatsApp. Cost: Region-based pricing; popular for cost-effective India/SEA deployments. Security: Telecom-grade compliance in India, SEA, and Middle East markets. Gupshup Key Features: SMS, WhatsApp, RCS, conversational messaging, bot frameworks, commerce and marketing flows. Cost: Pricing varies by channel and country; optimized for India, LATAM, and emerging markets. Security: Regional compliance and enterprise-grade security for messaging workflows. Ooma Key Features: SMB VoIP phone systems, virtual receptionist, call routing, basic business telephony. Cost: Subscription-based; lower-cost than enterprise UCaaS providers. Security: Standard SMB business-telephony protections; not CPaaS-level programmability. Amazon SNS Key Features: Pub/Sub messaging, SMS notifications, push notifications, email; part of AWS event-driven architecture. Cost: Pay-as-you-go based on notifications sent; AWS regional SMS pricing applies. Security: Inherits AWS IAM, encryption, compliance, monitoring, and infrastructure security. Which Platform Fits Which Use Case? If you want developer APIs to build custom communication flows: Twilio, Plivo, Telnyx, Bandwidth. If you need enterprise communication suites for internal teams: RingCentral, Vonage, Ooma for SMBs. If global omnichannel messaging is key: MessageBird, Sinch, Gupshup, Karix, Exotel. If you’re on AWS and only need notifications: Amazon SNS. Conclusion Each provider has unique strengths: some excel at global messaging, others at enterprise unified communications, others at developer-centric programmability. Understanding key features, pricing, and security posture helps narrow down the best fit for your product, geography, and scale. Share this blog on: Written by: Nikita Navral Co-Founder, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://www.githubstatus.com/ | GitHub Status GitHub Octicon logo Help Community Status GitHub.com Subscribe to Updates Subscribe x Get email notifications whenever GitHub creates , updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get text message notifications whenever GitHub creates or resolves an incident. Country code: Afghanistan (+93) Albania (+355) Algeria (+213) American Samoa (+1) Andorra (+376) Angola (+244) Anguilla (+1) Antigua and Barbuda (+1) Argentina (+54) Armenia (+374) Aruba (+297) Australia/Cocos/Christmas Island (+61) Austria (+43) Azerbaijan (+994) Bahamas (+1) Bahrain (+973) Bangladesh (+880) Barbados (+1) Belarus (+375) Belgium (+32) Belize (+501) Benin (+229) Bermuda (+1) Bolivia (+591) Bosnia and Herzegovina (+387) Botswana (+267) Brazil (+55) Brunei (+673) Bulgaria (+359) Burkina Faso (+226) Burundi (+257) Cambodia (+855) Cameroon (+237) Canada (+1) Cape Verde (+238) Cayman Islands (+1) Central Africa (+236) Chad (+235) Chile (+56) China (+86) Colombia (+57) Comoros (+269) Congo (+242) Congo, Dem Rep (+243) Costa Rica (+506) Croatia (+385) Cyprus (+357) Czech Republic (+420) Denmark (+45) Djibouti (+253) Dominica (+1) Dominican Republic (+1) Egypt (+20) El Salvador (+503) Equatorial Guinea (+240) Estonia (+372) Ethiopia (+251) Faroe Islands (+298) Fiji (+679) Finland/Aland Islands (+358) France (+33) French Guiana (+594) French Polynesia (+689) Gabon (+241) Gambia (+220) Georgia (+995) Germany (+49) Ghana (+233) Gibraltar (+350) Greece (+30) Greenland (+299) Grenada (+1) Guadeloupe (+590) Guam (+1) Guatemala (+502) Guinea (+224) Guyana (+592) Haiti (+509) Honduras (+504) Hong Kong (+852) Hungary (+36) Iceland (+354) India (+91) Indonesia (+62) Iraq (+964) Ireland (+353) Israel (+972) Italy (+39) Jamaica (+1) Japan (+81) Jordan (+962) Kenya (+254) Korea, Republic of (+82) Kosovo (+383) Kuwait (+965) Kyrgyzstan (+996) Laos (+856) Latvia (+371) Lebanon (+961) Lesotho (+266) Liberia (+231) Libya (+218) Liechtenstein (+423) Lithuania (+370) Luxembourg (+352) Macao (+853) Macedonia (+389) Madagascar (+261) Malawi (+265) Malaysia (+60) Maldives (+960) Mali (+223) Malta (+356) Martinique (+596) Mauritania (+222) Mauritius (+230) Mexico (+52) Monaco (+377) Mongolia (+976) Montenegro (+382) Montserrat (+1) Morocco/Western Sahara (+212) Mozambique (+258) Namibia (+264) Nepal (+977) Netherlands (+31) New Zealand (+64) Nicaragua (+505) Niger (+227) Nigeria (+234) Norway (+47) Oman (+968) Pakistan (+92) Palestinian Territory (+970) Panama (+507) Paraguay (+595) Peru (+51) Philippines (+63) Poland (+48) Portugal (+351) Puerto Rico (+1) Qatar (+974) Reunion/Mayotte (+262) Romania (+40) Russia/Kazakhstan (+7) Rwanda (+250) Samoa (+685) San Marino (+378) Saudi Arabia (+966) Senegal (+221) Serbia (+381) Seychelles (+248) Sierra Leone (+232) Singapore (+65) Slovakia (+421) Slovenia (+386) South Africa (+27) Spain (+34) Sri Lanka (+94) St Kitts and Nevis (+1) St Lucia (+1) St Vincent Grenadines (+1) Sudan (+249) Suriname (+597) Swaziland (+268) Sweden (+46) Switzerland (+41) Taiwan (+886) Tajikistan (+992) Tanzania (+255) Thailand (+66) Togo (+228) Tonga (+676) Trinidad and Tobago (+1) Tunisia (+216) Turkey (+90) Turks and Caicos Islands (+1) Uganda (+256) Ukraine (+380) United Arab Emirates (+971) United Kingdom (+44) United States (+1) Uruguay (+598) Uzbekistan (+998) Venezuela (+58) Vietnam (+84) Virgin Islands, British (+1) Virgin Islands, U.S. (+1) Yemen (+967) Zambia (+260) Zimbabwe (+263) Phone number: Change number Enter OTP: Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP Message and data rates may apply. By subscribing you agree to our Privacy Policy , the Atlassian Terms of Service , and the Atlassian Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy . In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy . Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: The URL we should send the webhooks to Email address: We'll send you email if your endpoint fails By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Follow @githubstatus or view our profile . Visit our support site . Get the Atom Feed or RSS Feed . All Systems Operational About This Site Check GitHub Enterprise Cloud status by region: - Australia: au.githubstatus.com - EU: eu.githubstatus.com - Japan: jp.githubstatus.com - US: us.githubstatus.com Git Operations ? Operational Webhooks ? Operational Visit www.githubstatus.com for more information Operational API Requests ? Operational Issues ? Operational Pull Requests ? Operational Actions ? Operational Packages ? Operational Pages ? Operational Codespaces ? Operational Copilot Operational Operational Degraded Performance Partial Outage Major Outage Maintenance Past Incidents Jan 13 , 2026 No incidents reported today. Jan 12 , 2026 Disruption with some GitHub services Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Jan 12 , 10:17 UTC Update - Actions jobs that use custom Linux images are failing to start. We've identified the underlying issue and are working on mitigation. Jan 12 , 10:09 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Jan 12 , 10:06 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 12 , 10:02 UTC Jan 11 , 2026 No incidents reported. Jan 10 , 2026 Disruption with some GitHub services Resolved - From January 5, 2026, 00:00 UTC to January 10, 2026, 02:30 UTC, customers using the AI Controls public preview feature experienced delays in viewing Copilot agent session data. Newly created sessions took progressively longer to appear, initially hours, then eventually exceeding 24 hours. Since the page displays only the most recent 24 hours of activity, once processing delays exceeded this threshold, no recent data was visible. Session data remained available in audit logs throughout the incident. Inefficient database queries in the data processing pipeline caused significant processing latency, creating a multi-day backlog. As the backlog grew, the delay between when sessions occurred and when they appeared on the page increased, eventually exceeding the 24-hour display window. The issue was resolved on January 10, 2026, 02:30 UTC, after query optimizations and a database index were deployed. We are implementing enhanced monitoring and automated testing to detect inefficient queries before deployment to prevent recurrence. Jan 10 , 02:33 UTC Update - Our queue has cleared. The last 24 hours of agent session history should now be visible on the AI Controls UI. No data was lost due to this incident. Jan 10 , 02:33 UTC Update - We estimate the backlogged queue will take 3 hours to process. We will post another update once it is completed, or if anything changes with the recovery process. Jan 9 , 23:56 UTC Update - We have deployed an additional fix and are beginning to see recovery to the queue preventing AI Sessions from showing in the AI Controls UI. We are working on an estimate for when the queue will be fully processed, and will post another update once we have that information. Jan 9 , 23:44 UTC Update - We are seeing delays processing the AI Session event queue, which is causing sessions to not be displayed on the AI Controls UI. We have deployed a fix to improve the queue processing and are monitoring for effectiveness. We continue to investigate other mitigation paths. Jan 9 , 22:41 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in AI Controls. Jan 9 , 21:36 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 21:08 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 20:07 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 19:35 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 19:02 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 18:39 UTC Update - Agent Session activity is still observable in audit logs, and this only impacts the AI Controls UI. Jan 9 , 18:08 UTC Update - We are investigating an incident affecting missing Agent Session data on the AI Settings page on Agent Control Plane. Jan 9 , 17:57 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 9 , 17:53 UTC Jan 9 , 2026 Jan 8 , 2026 Incident with Copilot Resolved - On January 8th, 2025, between approximately 00:00 and 1:30 UTC, the Copilot service experienced a degradation of the Grok Code Fast 1 model due to an issue with our upstream provider. Users encountered elevated error rates when using Grok Code Fast 1. Approximately 4.5% of requests failed across all users during this time. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. Jan 8 , 01:32 UTC Update - The issues with our upstream model provider have been resolved, and Grok Code Fast 1 is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete. Jan 8 , 01:31 UTC Update - We are experiencing degraded availability for the Grok Code Fast 1 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected. Jan 8 , 00:45 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 8 , 00:45 UTC Jan 7 , 2026 Some models missing in Copilot Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Jan 7 , 21:07 UTC Update - We have implemented a mitigation and confirmed that Copilot Pro and Business accounts now have access to the previously missing models. We will continue monitoring to ensure complete resolution. Jan 7 , 19:43 UTC Update - We continue to investigate. We'll post another update by 19:50 UTC. Jan 7 , 19:29 UTC Update - Correction - Copilot Pro and Business users are impacted. Copilot Pro+ and Enterprise users are not impacted. Jan 7 , 19:10 UTC Update - We continue to investigate this problem and have confirmed only Copilot Business users are impacted. We'll post another update by 19:30 UTC. Jan 7 , 19:06 UTC Update - We are currently investigating reports of some Copilot Pro premium models including Opus and GPT 5.2 being unavailable in Copilot products. We'll post another update by 19:08 UTC. Jan 7 , 18:44 UTC Update - We have received reports that some expected models are missing from VSCode and other products using Copilot. We are investigating the cause of this to restore access. Jan 7 , 18:33 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 7 , 18:32 UTC Jan 6 , 2026 Incident with Actions Resolved - On January 6, 2026 between 12:55 UTC and 17:04 UTC, the ability to download Actions artifacts from GitHub’s web interface was degraded. During this time, all attempts to download artifacts from the web interface failed. Artifact downloads via the REST API and GitHub CLI were unaffected. This was due to a client-side change that was deployed to optimize performance when navigating between pages in a repository. We mitigated the incident by reverting the change. We are working to improve testing of related changes and to add monitoring coverage for artifact downloads through the web interface to reduce our time to detection and prevent similar incidents from occurring in the future. Jan 6 , 17:06 UTC Update - We are investigating issues downloading artifacts from Actions workflows. All customers are affected when attempting to download through the web interface. We're actively working on a fix and will post another update by 17:15 UTC. Jan 6 , 16:44 UTC Investigating - We are investigating reports of degraded performance for Actions Jan 6 , 16:41 UTC Incident with Copilot Resolved - On January 6th, 2026, between approximately 8:41 and 10:07 UTC, the Copilot service experienced a degradation of the GPT-5.1-Codex-Max model due to an issue with our upstream provider. During this time, up to 14.17% of requests to GPT-5.1-Codex-Max failed. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future. Jan 6 , 10:08 UTC Update - The issues with our upstream model provider have been resolved, and GPT-5.1-Codex-Max is once again available. We will continue monitoring to ensure stability. Jan 6 , 10:07 UTC Update - We are experiencing degraded availability for the GPT-5.1-Codex-Max model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected. Jan 6 , 09:03 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 6 , 08:56 UTC Jan 5 , 2026 No incidents reported. Jan 4 , 2026 No incidents reported. Jan 3 , 2026 No incidents reported. Jan 2 , 2026 No incidents reported. Jan 1 , 2026 Disruption with some GitHub services Resolved - On December 31, 2025, between 04:00 UTC and 22:31 UTC, all users visiting https://github.com/features/copilot were unable to load the page and were instead redirected to an error page. The issue was caused by an unexpected content change that resulted in page rendering errors. We mitigated the incident by reverting the change, which restored normal page behavior. To reduce the likelihood and duration of similar issues in the future, we are improving monitoring and alerting for increased error rates on this page and similar pages, and strengthening validation and safeguards around content updates to prevent unexpected changes from causing user-facing errors. Jan 1 , 22:31 UTC Update - Our Copilot feature page ( https://github.com/features/copilot ) is returning 500s. We are currently investigating. This does not impact the core GitHub application. Jan 1 , 21:24 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 1 , 21:24 UTC Dec 31 , 2025 No incidents reported. Dec 30 , 2025 No incidents reported. ← Incident History Powered by Atlassian Statuspage GitHub text logo Subscribe to our developer newsletter Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe Product Features Enterprise Copilot Security Pricing Team Resources Roadmap Compare GitHub Platform Developer API Partners Education GitHub CLI GitHub Desktop GitHub Mobile Support Docs Community Forum Professional Services Skills Contact GitHub Company About Customer stories Blog The ReadME Project Careers Newsroom Inclusion Social Impact Shop © GitHub, Inc. Terms Privacy ( Updated 08/2022 ) GitHub X GitHub Facebook GitHub LinkedIn GitHub YouTube Twitch TikTok GitHub.com | 2026-01-13T08:49:23 |
https://replit.com/careers | Careers at Replit – Empowering the next billion software creators Agent Products Agent Design Database Publish Security Integrations Mobile For Work Teams Replit for teams to build together Enterprise Replit with Enterprise-grade security & controls Use Cases Business Apps Rapid Prototyping Roles Enterprise PM Designers Operations Software Developers Small Businesses SMB owners Founders Resources Get Started Docs Community Expert Network Inspiration Customer Stories Gallery Blog News Pricing Careers Agent Contact sales Log in Sign up Products For Work Resources Pricing Careers Contact sales Log in Start building C a reers at Re p lit We’re on a mission to empower the next billion software creators. Join us! See open positions The future of computing Replit is pioneering the future of software creation. We're not just building another AI tool — we're empowering the next generation of creators to bring their ideas to life. Replit Agent is now one of the fastest growing products in history. By bringing the power of software creation to everyone, regardless of technical background, we're creating a world where technology respects and enhances the full spectrum of human potential. This isn't about machines taking over — it's about empowering a billion creators to bring their unique perspectives and ideas to life. We've fundamentally transformed how software is created, deployed, and scaled. What once took months now takes minutes. What required teams and tens of thousands of dollars can now be accomplished by individuals. We've eliminated the barriers between ideation and creation, enabling anyone with an internet connection to build the future. Ready to join us? See open positions Our mission: one billion creators We believe being able to make your idea come to life is the most powerful form of expression in the modern world. Our mission is to put this power in the hands of a billion creators — from people building personal applications for the lives and families to soloprenuers who’ve never written code to enterprises reinventing how they build software. How we work To read more about who we are, check out our operating principles , or read about reasons not to join Replit . Where we work Our Foster City headquarters isn't just an office — it's an innovation hub where global talent converges for electric hack weeks and spontaneous collaboration. Strategically positioned between San Francisco, East Bay, and South Bay, it's the epicenter where our best ideas spark to life through in-person connection, drawing exceptional minds who've relocated from around the world to be part of something transformative. Join our team We're looking for exceptional talent who are: Passionate about democratizing software creation Excited to build products used by millions of creators daily Committed to making computing more accessible, collaborative, and powerful Benefits Our comprehensive benefits package goes beyond total rewards to support bringing the best version of yourself to work every day while supporting your future growth. For you Competitive salary, equity and performance bonus Monthly wellness stipend Health, dental, and vision insurance HSA (Replit contributes $2k for individual and $4k for families) FSA, DFSA Mental healthcare support and services In office set-up reimbursement Company sponsored retirement plan Uber for business and commuter benefits In office breakfast, lunch and dinners & treats In office amenities & perks (massage chairs and onsite gym!) For your life Flexible time off and paid sick leave 24 week paid birth-parent leave 12 week paid medical, bonding and family care leave Short and long-term disability coverage Life and AD&D insurance For your development & recognition Annual $1000 learning & development reimbursement Quarterly team gatherings Reward and recognition program Quarterly operational values award program Career development & coaching opportunities Learn more about our interview process . Ready to join us? See open positions Handy Links About us Vibe Coding 101 Help How to guides Import from GitHub Status Additional resources Brand kit Partnerships Legal Terms of service Commercial agreement Privacy Subprocessors DPA Report abuse Connect X / Twitter Tiktok Facebook Instagram Linkedin Scroll to top All rights reserved. Copyright © 2026 Replit, Inc. | 2026-01-13T08:49:23 |
https://design.forem.com/t/uxdesign#main-content | Uxdesign - Design 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 Design Community Close # uxdesign Follow Hide Focusing on user experience, research, and creating user-centered products Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu What my dining table and my cat showed me about human attention Metehan Altuntekin Metehan Altuntekin Metehan Altuntekin Follow Jan 5 What my dining table and my cat showed me about human attention # design # uxdesign # behavior 2 reactions Comments Add Comment 3 min read Help Center Design Consistency Rules for Trust and Clarity FreePixel FreePixel FreePixel Follow Dec 24 '25 Help Center Design Consistency Rules for Trust and Clarity # helpcenter # uxdesign # customersupport # knowledgebase Comments Add Comment 4 min read Help Center Design Systems for Consistent Support Experiences FreePixel FreePixel FreePixel Follow Dec 18 '25 Help Center Design Systems for Consistent Support Experiences # helpcenter # uxdesign # designsystems # customersupport Comments 1 comment 4 min read Help Center Visual Hierarchy Techniques That Guide User Attention FreePixel FreePixel FreePixel Follow Dec 22 '25 Help Center Visual Hierarchy Techniques That Guide User Attention # helpcenter # uxdesign # visualdesign # customersupport Comments Add Comment 4 min read Reimagining Thai Lagoon - Website Redesign Parvathi Kumar Parvathi Kumar Parvathi Kumar Follow Dec 5 '25 Reimagining Thai Lagoon - Website Redesign # uxdesign # showcase # uidesign # webdesign Comments Add Comment 2 min read UX Across the Atlantic: How American and European Web Design Differ Polina Elizarova Polina Elizarova Polina Elizarova Follow Nov 27 '25 UX Across the Atlantic: How American and European Web Design Differ # design # webdesign # uxdesign # designprocess 1 reaction Comments Add Comment 2 min read Must-Have AI Tools for Every UX Researcher's Toolkit Lollypop Design Lollypop Design Lollypop Design Follow Nov 25 '25 Must-Have AI Tools for Every UX Researcher's Toolkit # userresearch # uxdesign # aiindesign # resources 6 reactions Comments 3 comments 10 min read Improving Customer Loyalty Through Better Help Centre Design FreePixel FreePixel FreePixel Follow Nov 3 '25 Improving Customer Loyalty Through Better Help Centre Design # uxdesign # customerexperience # helpcenter # customerloyalty 1 reaction Comments 1 comment 5 min read Why Value-Sensitive Design Is My North Star Now Osman Gunes Cizmeci Osman Gunes Cizmeci Osman Gunes Cizmeci Follow Sep 30 '25 Why Value-Sensitive Design Is My North Star Now # designprocess # ethics # uxdesign Comments Add Comment 4 min read When UX Feels Broken, Troubleshooting as a Product Manager Ulad Shauchenka Ulad Shauchenka Ulad Shauchenka Follow Sep 27 '25 When UX Feels Broken, Troubleshooting as a Product Manager # design # uxdesign # troubleshooting # tools Comments Add Comment 2 min read The Ultimate Checklist for Designing a Zendesk Help Center That Converts FreePixel FreePixel FreePixel Follow Oct 30 '25 The Ultimate Checklist for Designing a Zendesk Help Center That Converts # zendesk # uxdesign # customersupport # saas Comments 1 comment 4 min read How UX in 2025 became more about intent than interaction Karina Egle Karina Egle Karina Egle Follow Oct 23 '25 How UX in 2025 became more about intent than interaction # design # uxdesign # uidesign # webdesign 9 reactions Comments 1 comment 4 min read 11 Principles That Help Me Decide When to Research vs. Just Ship Ulad Shauchenka Ulad Shauchenka Ulad Shauchenka Follow Sep 26 '25 11 Principles That Help Me Decide When to Research vs. Just Ship # design # uxdesign # uidesign # webdesign Comments Add Comment 1 min read Control Confidence: The Secret UX Ingredient You're Missing Arvind SundaraRajan Arvind SundaraRajan Arvind SundaraRajan Follow Oct 15 '25 Control Confidence: The Secret UX Ingredient You're Missing # uxdesign # uiux # a11y # designsystem 3 reactions Comments Add Comment 2 min read Designing Silence: How Minimal UX Can Improve Voice Assistant Experiences Pratiksha Pratiksha Pratiksha Follow Oct 15 '25 Designing Silence: How Minimal UX Can Improve Voice Assistant Experiences # aiindesign # uidesign # uxdesign Comments Add Comment 2 min read UX/UI and some industrial design for an air quality sensor Liberiam Liberiam Liberiam Follow Sep 29 '25 UX/UI and some industrial design for an air quality sensor # uidesign # productdesign # sideprojects # uxdesign 4 reactions Comments Add Comment 6 min read Join Us – Front-End & Product Design (Svelte/SvelteKit) Rick Johnes Rick Johnes Rick Johnes Follow Aug 12 '25 Join Us – Front-End & Product Design (Svelte/SvelteKit) # svelte # design # uxdesign # jobboard 1 reaction Comments Add Comment 1 min read loading... trending guides/resources Help Center Design Consistency Rules for Trust and Clarity UX Across the Atlantic: How American and European Web Design Differ Must-Have AI Tools for Every UX Researcher's Toolkit What my dining table and my cat showed me about human attention Improving Customer Loyalty Through Better Help Centre Design Reimagining Thai Lagoon - Website Redesign Help Center Design Systems for Consistent Support Experiences Help Center Visual Hierarchy Techniques That Guide User Attention The Ultimate Checklist for Designing a Zendesk Help Center That Converts 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://claude.com/solutions/coding | Coding | Claude -------> Meet Claude Products Claude Claude Code Features Claude in Chrome Claude in Slack Claude in Excel Skills Models Opus Sonnet Haiku Platform Overview Developer docs Pricing Regional Compliance Console login Solutions Use cases AI agents Coding Industries Customer support Education Financial services Government Healthcare Life sciences Nonprofits Pricing Overview API Max plan Team plan Enterprise plan Learn Blog Courses Customer stories Events Tutorials Use cases Anthropic news Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Meet Claude Products Claude Claude Code Features Claude in Chrome Claude in Slack Claude in Excel Skills Models Opus Sonnet Haiku Platform Overview Developer docs Pricing Regional Compliance Console login Solutions Use cases AI agents Coding Industries Customer support Education Financial services Government Healthcare Life sciences Nonprofits Pricing Overview API Max plan Team plan Enterprise plan Learn Blog Courses Customer stories Events Tutorials Use cases Anthropic news Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Contact sales Contact sales Contact sales Try Claude Try Claude Try Claude Solutions Solutions / Coding Explore here Ask questions about this page Copy as markdown The best AI for developers Claude is the not-so-secret advantage for world class engineering teams and software companies. Start building Start building Start building Contact sales Contact sales Contact sales Play video Play video 80.9% Opus 4.5 leads on SWE-bench Verified 60x faster code review feedback for an AI platform customer 95% reduction in time to run tests for an enterprise software customer Write code with Claude Get complete insight into your codebase and accelerate exceptional software. View prompt View prompt View prompt Prompt > claude fix the authentication error in our login flow I'll investigate the auth error. Let me look at the relevant files. Examining auth-related files... * src/services/authService.js * src/components/Login.jsx * src/store/authSlice.js Running the login flow... Error detected: "401 Unauthorized: Token expired" Root cause: * Token refresh mechanism not handling expired tokens correctly * Refresh token missing from request header * Improper error handling for 401 responses Updating authService.js with proper refresh logic... Updating request interceptor for 401 handling... Testing the fix... * Login successful ✓ * Token refresh working ✓ * Proper redirection on expired tokens ✓ Authentication error fixed! The login flow now properly handles token expiration. Scale coding impact, not overhead Write, test, and debug complex software with Claude , analyze codebases with expert-level reasoning via GitHub integration, delegate development tasks through computer use, and fast-track smarter engineering decisions in a shared workspace. Explore agentic coding with Claude Code Claude Code brings Sonnet 4.5 right to your terminal, with deep codebase awareness and the ability to edit files and run commands directly in your environment. Learn more Learn more Learn more Developers love Claude “I taught a friend who has never written code in her life how to use Claude to build a simple app and deploy it on Cloudflare today. Watching someone realize that they can now build software is a great experience. Enable everyone to build anything.” Logan Grasby, @LoganGrasby “I introduced someone to Claude Code, Opus last night, and we were up til 4 am building a project. It was crazy! 20K lines of codes, audit logging, a full Prisma Database, complete architecture, and a complete roadmap with 4 phases for complete implementation.” Teneika Askew, @teneikaask_you “Just taught my fiancée how to use claude to write code that automates dumb tasks that have been making her work life miserable for months. She went from being downtrodden and skeptical to dancing around the room in about 15 minutes. END USER PROGRAMMING IS NOW.” Kasey, @kaseyklimes “Claude 4 Opus is exactly the future we were promised. I sit down, prompt a little bit, check to make sure the program is doing what i wanted. “8 hours” of work done with almost no labor or input from me. Now time to go get ice cream and watch Twitch until I get more tokens.” @airkatakana “I know this sounds cringe, but I literally have clammy hands and a racing heart because of how powerful Claude + Cursor is. Like I just made a whole new feature, frontend and backend, built on top of my own custom APIs without touching code, then I had it switch from a SwiftUI.” Majd Taby, @jtaby “Claude Code + Opus 4 is the best agentic coding tool in the world and it’s not close.” Mckay Wrigley, @mckaywrigley “Anthropic is leading the Industry with models - like Sonnet and Opus - and developer tools - like Claude Code.” Jon Meyers, @jonmeyers_io “With new Claude i officially feel like a fraud when i code, I’m the guy in the corner saying um nice job boss keep going.” Nick, @nickcammarata Prev Prev 0 / 5 Next Next Build products with the Claude Developer Platform Integrate Claude’s powerful AI capabilities into your apps and deliver production-grade solutions faster. View prompt View prompt View prompt Existing prompt Classify all customer support tickets into the most relevant category. Here is the list of categories to choose from: {{CATEGORY_LIST}} Here is the content of the support ticket: {{TICKET_CONTENT}} What would you like to improve? Please include a rationale for the classification. You are an AI assistant specialized in classifying customer support tickets. Your task is to analyze the content of a given ticket and assign it to the most appropriate category from a predefined list. You will also provide reasoning for your classification decision. First, let's review the available categories: <category_list> {{CATEGORY_LIST}} </category_list> Now, here is the content of the support ticket you need to classify: <ticket_content> {{TICKET_CONTENT}} </ticket_content> Please follow these steps to complete the task: – Carefully read and analyze the ticket content. – Consider how the content relates to each of the available categories. – Choose the most appropriate category for the ticket. – Provide a detailed explanation of your reasoning process. Use the following structure for your response: <classification_analysis> In this section, break down your thought process: – Quote the most relevant parts of the ticket content. – List each category and note how it relates to the ticket content. – For each category, provide arguments for and against classifying the ticket into that category. – Rank the top 3 most likely categories. </classification_analysis> <classification> <category>Your chosen category goes here</category> <reasoning>A concise summary of your reasoning for choosing this category</reasoning> </classification> Remember to be thorough in your analysis and clear in your explanation. Your goal is to provide an accurate classification with well-supported reasoning. Deliver amazing AI experiences Customize how Claude fits into your solution with our API Improve and evaluate your prompts in the Workbench Build frontier intelligence into your applications Turn anyone into an AI developer with rich docs and tooling See why companies choose Claude "Claude Opus 4.5 delivers high-quality code and excels at powering heavy-duty agentic workflows with GitHub Copilot. Early testing shows it surpasses internal coding benchmarks while cutting token usage in half, and is especially well-suited for tasks like code migration and code refactoring." Mario Rodriguez, Chief Product Officer, GitHub "Claude Opus 4.5 is a notable improvement over the prior Claude models inside Cursor, with improved pricing and intelligence on difficult coding tasks." Michael Truell, CEO & Co-founder “Claude Opus 4.5 delivers measurable gains where it matters most: stronger results on our hardest evaluations and consistent performance through 30-minute autonomous coding sessions.” Scott Wu, CEO, Cognition "Opus 4.5 beats Sonnet 4.5 and competition on our internal benchmarks, using fewer tokens to solve the same problems. At scale, that efficiency compounds." Michele Catasta, President “Claude Opus 4.5 handles long-horizon coding tasks more efficiently than any model we’ve tested. It achieves higher pass rates on held-out tests while using up to 65% fewer tokens, giving developers real cost control without sacrificing quality.” Sean Ward, CEO and Co-founder "Claude Opus 4.5 is yet another example of Anthropic pushing the frontier of general intelligence. It performs exceedingly well across difficult coding tasks, showcasing long-term goal-directed behavior." Eno Reyes, CTO and cofounder "Claude Opus 4.5 achieved state-of-the-art results for complex enterprise tasks on our benchmarks, outperforming previous models on multi-step reasoning tasks that combine information retrieval, tool use, and deep analysis." Kay Zhu, CTO "We've found that Opus 4.5 excels at interpreting what users actually want, producing shareable content on the first try. Combined with its speed, token efficiency, and surprisingly low cost, it's the first time we're making Opus available in Notion Agent." Sarah Sachs, AI Lead Engineer "Claude Opus 4.5 represents a breakthrough in self-improving AI agents. For automation of office tasks, our agents were able to autonomously refine their own capabilities—achieving peak performance in 4 iterations while other models couldn’t match that quality after 10. They also demonstrated the ability to learn from experience across technical tasks, storing insights and applying them later." Yusuke Kaji, General Manager (AI) "Claude Opus 4.5 catches more issues in code reviews without sacrificing precision. For production code review at scale, that reliability matters." David Loker, Director of AI "Based on testing with Junie, our coding agent, Claude Opus 4.5 outperforms Sonnet 4.5 across all benchmarks. It requires fewer steps to solve tasks and uses fewer tokens as a result. This indicates that the new model is more precise and follows instructions more effectively — a direction we’re very excited about." Andrew Zakonov, VP of Business, Junie & Kineto "Claude Opus 4.5 is the only model that nails some of our hardest 3D visualizations. Polished design, tasteful UX, and excellent planning & orchestration - all with more efficient token usage. Tasks that took previous models 2 hours now take thirty minutes." Madhav Jha, CTO "We're seeing 50% to 75% reductions in both tool calling errors and build/lint errors with Claude Opus 4.5. It consistently finishes complex tasks in fewer iterations with more reliable execution." Nicholas Charriere, Founder and CEO "Claude Opus 4.5 delivered an impressive refactor spanning two codebases and three coordinated agents. It was very thorough, helping develop a robust plan, handling the details and fixing tests. A clear step forward from Sonnet 4.5." Paulo Arruda, Staff Engineer, AI Productivity "Claude Opus 4.5 excels at long-horizon, autonomous tasks, especially those that require sustained reasoning and multi-step execution. In our evaluations it handled complex workflows with fewer dead-ends. On Terminal Bench it delivered a 15% improvement over Sonnet 4.5, a meaningful gain that becomes especially clear when using Warp’s Planning Mode." Zach Lloyd Founder & CEO Warp Prev Prev 0 / 5 Next Next 100K+ applications deployed on Google Cloud run 75% engineers saving 8–10+ hours every week Get the technical rundown Learn how to use Claude Code Learn how to use Claude Code Learn how to use Claude Code Developer docs Developer docs Developer docs Start building with our quickstart guides Start building with our quickstart guides Start building with our quickstart guides Quickstart Quickstart Quickstart How Anthropic teams use Claude Code How Anthropic teams use Claude Code How Anthropic teams use Claude Code Case study Case study Case study Homepage Homepage Next Next Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Write Button Text Button Text Learn Button Text Button Text Code Button Text Button Text Write Help me develop a unique voice for an audience Hi Claude! Could you help me develop a unique voice for an audience? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Improve my writing style Hi Claude! Could you improve my writing style? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Brainstorm creative ideas Hi Claude! Could you brainstorm creative ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Learn Explain a complex topic simply Hi Claude! Could you explain a complex topic simply? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Help me make sense of these ideas Hi Claude! Could you help me make sense of these ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Prepare for an exam or interview Hi Claude! Could you prepare for an exam or interview? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Code Explain a programming concept Hi Claude! Could you explain a programming concept? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Look over my code and give me tips Hi Claude! Could you look over my code and give me tips? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Vibe code with me Hi Claude! Could you vibe code with me? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! More Write case studies This is another test Write grant proposals Hi Claude! Could you write grant proposals? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to — like Google Drive, web search, etc. — if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational. Please execute the task as soon as you can - an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help! Write video scripts this is a test Anthropic Anthropic © [year] Anthropic PBC Products Claude Claude Claude Claude Code Claude Code Claude Code Max plan Max plan Max plan Team plan Team plan Team plan Enterprise plan Enterprise plan Enterprise plan Download app Download app Download app Pricing Pricing Pricing Log in Log in Log in Features Claude in Chrome Claude in Chrome Claude in Chrome Claude in Slack Claude in Slack Claude in Slack Claude in Excel Claude in Excel Claude in Excel Skills Skills Skills Models Opus Opus Opus Sonnet Sonnet Sonnet Haiku Haiku Haiku Solutions AI agents AI agents AI agents Code modernization Code modernization Code modernization Coding Coding Coding Customer support Customer support Customer support Education Education Education Financial services Financial services Financial services Government Government Government Healthcare Healthcare Healthcare Life sciences Life sciences Life sciences Nonprofits Nonprofits Nonprofits Claude Developer Platform Overview Overview Overview Developer docs Developer docs Developer docs Pricing Pricing Pricing Regional Compliance Regional Compliance Regional Compliance Amazon Bedrock Amazon Bedrock Amazon Bedrock Google Cloud’s Vertex AI Google Cloud’s Vertex AI Google Cloud’s Vertex AI Console login Console login Console login Learn Blog Blog Blog Claude partner network Claude partner network Claude partner network Courses Courses Courses Connectors Connectors Connectors Customer stories Customer stories Customer stories Engineering at Anthropic Engineering at Anthropic Engineering at Anthropic Events Events Events Powered by Claude Powered by Claude Powered by Claude Service partners Service partners Service partners Startups program Startups program Startups program Tutorials Tutorials Tutorials Use cases Use cases Use cases Company Anthropic Anthropic Anthropic Careers Careers Careers Economic Futures Economic Futures Economic Futures Research Research Research News News News Responsible Scaling Policy Responsible Scaling Policy Responsible Scaling Policy Security and compliance Security and compliance Security and compliance Transparency Transparency Transparency Help and security Availability Availability Availability Status Status Status Support center Support center Support center Terms and policies Privacy choices Cookie settings We use cookies to deliver and improve our services, analyze site usage, and if you agree, to customize or personalize your experience and market our services to you. You can read our Cookie Policy here . Customize cookie settings Reject all cookies Accept all cookies Necessary Enables security and basic functionality. Required Analytics Enables tracking of site performance. Off Marketing Enables ads personalization and tracking. Off Save preferences Privacy policy Privacy policy Privacy policy Responsible disclosure policy Responsible disclosure policy Responsible disclosure policy Terms of service: Commercial Terms of service: Commercial Terms of service: Commercial Terms of service: Consumer Terms of service: Consumer Terms of service: Consumer Usage policy Usage policy Usage policy x.com x.com LinkedIn LinkedIn YouTube YouTube Instagram Instagram English (US) English (US) 日本語 (Japan) Deutsch (Germany) Français (France) 한국어 (South Korea) Why do programmers prefer dark mode? I don't know I don't know I don't know Ask Claude Ask Claude Ask Claude | 2026-01-13T08:49:23 |
https://www.youtube.com/ | 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, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:49:23 |
https://atproto.com/guides/faq | FAQ - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme FAQ Frequently Asked Questions about the Authenticated Transfer Protocol (AT Proto). For FAQ about Bluesky, visit here . Is the AT Protocol a blockchain? No. The AT Protocol is a federated protocol . It's not a blockchain nor does it use a blockchain. Why not use ActivityPub? ActivityPub is a federated social networking technology popularized by Mastodon . Account portability is a major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects users from sudden bans, server shutdowns, and policy disagreements. Our solution for portability requires both signed data repositories and DIDs , neither of which are easy to retrofit into ActivityPub. The migration tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data. Another major reason is scalability. ActivityPub depends heavily on delivering messages between a wide network of small-to-medium sized nodes, which can cause individual nodes to be flooded with traffic and generally struggles to provide global views of activity. The AT Protocol uses aggregating applications to merge activity from the users' hosts, reducing the overall traffic and dramatically reducing the load on individual hosts. Other smaller differences include: a different viewpoint about how schemas should be handled, a preference for domain usernames over AP's double-@ email usernames, and the goal of having large scale search and algorithmic feeds. Why create Lexicon instead of using JSON-LD or RDF? Atproto exchanges data and RPC commands across organizations. For the data and RPC to be useful, the software needs to correctly handle schemas created by separate teams. This is the purpose of Lexicon . We want engineers to feel comfortable using and creating new schemas, and we want developers to enjoy the DX of the system. Lexicon helps us produce strongly typed APIs which are extremely familiar to developers and which provides a variety of runtime correctness checks. RDF is intended for extremely general cases in which the systems share very little infrastructure. It's conceptually elegant but difficult to use, often adding a lot of syntax which devs don't understand. JSON-LD simplifies the task of consuming RDF vocabularies, but it does so by hiding the underlying concepts, not by making RDF more legible. We looked very closely at using RDF but just didn't love the developer experience (DX) or the tooling it offered. What is “XRPC,” and why not use ___? XRPC is HTTP with some added conventions. We're aiming to retire the term "XRPC" and just refer to it as the ATProto usage of HTTP. XRPC uses Lexicon to describe HTTP calls and maps them to /xrpc/{methodId} . For example, this API call: await api . com . atproto . repo .listRecords ({ user : 'alice.com' , collection : 'app.bsky.feed.post' }) Copy Copied! ...maps to: GET /xrpc/com.atproto.repo.listRecords ?user=alice.com &collection=app.bsky.feed.post Copy Copied! Lexicon establishes a shared method id ( com.atproto.repo.listRecords ) and the expected query params, input body, and output body. By using Lexicon we get runtime checks on the inputs and outputs of the call, and can generate typed code like the API call example above. Previous Glossary Next Quick start © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://x.com/tos#twtr-main | X Terms of Service Skip to main content Terms of Service <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-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 u01b__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-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-close="<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewbox="0 0 24 24" style="enable-background:new 0 0 24 24;" xml:space="preserve" aria-hidden="true" focusable="false" role="none" class="twtr-icon--md"> <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-search="<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="M22.06 19.94l-3.73-3.73C19.38 14.737 20 12.942 20 11c0-4.97-4.03-9-9-9s-9 4.03-9 9 4.03 9 9 9c1.943 0 3.738-.622 5.21-1.67l3.73 3.73c.292.294.676.44 1.06.44s.768-.146 1.06-.44c.586-.585.586-1.535 0-2.12zM11 17c-3.308 0-6-2.692-6-6s2.692-6 6-6 6 2.692 6 6-2.692 6-6 6z" /> </svg>" data-icon-search-submit="<svg width="21" height="21" viewbox="0 0 21 21" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" role="none" class="twtr-icon"> <path fill-rule="evenodd" clip-rule="evenodd" d="M16.33 14.21L20.06 17.94C20.646 18.525 20.646 19.475 20.06 20.06C19.768 20.354 19.384 20.5 19 20.5C18.616 20.5 18.232 20.354 17.94 20.06L14.21 16.33C12.738 17.378 10.943 18 9 18C4.03 18 0 13.97 0 9C0 4.03 4.03 0 9 0C13.97 0 18 4.03 18 9C18 10.942 17.38 12.737 16.33 14.21ZM3 9C3 12.308 5.692 15 9 15C12.308 15 15 12.308 15 9C15 5.692 12.308 3 9 3C5.692 3 3 5.692 3 9Z" fill="white" /> </svg>" data-bg-color="white-neutral" data-root-page-title="Terms of Service" data-search-placeholder="Search" data-search-query-key="q" data-search-query-type="?" data-scribe-element="RJPO" data-scribe-section="u01b-navigation" data-cta-enabled="true" data-cta-text="Download PDF" data-cta-link="https://cdn.cms-twdigitalassets.com/content/dam/legal-twitter/site-assets/terms-of-service-2025-05-08/en/x-terms-of-service-2025-05-08.pdf" data-cta-link-new-tab="true"> Terms of Service We have made some updates to our Terms of Service. This version of the Terms of Service will go into effect on January 15, 2026. Until then, the current Terms of Service continue to apply. Summary of our Terms These Terms of Service (“Terms”) are part of the User Agreement – a legally binding contract governing your relationship with X. You should read these Terms in full, but here are a few key things you should take away: You will see advertising on the platform: In exchange for accessing the Services, X and our third-party providers and partners may display advertising to you. When posting Content and otherwise using the Services, you must comply with this User Agreement and Applicable Law: You are responsible for your use of the Services and your Content. You must comply with the User Agreement, including all applicable policies and rules, and all applicable laws. You must abide by the Services’ acceptable use terms: You may not access the Services in any way other than through the currently available, published interfaces that we provide. For example, this means that you cannot scrape the Services without X’s express written permission, try to work around any technical limitations we impose, or otherwise attempt to disrupt the operation of the Services. We have broad enforcement rights: X reserves the right to take enforcement actions against you if you do violate these terms, such as, for example, removing your Content, limiting visibility, discontinuing your access to X, or taking legal action. Certain jurisdictions, including the European Union and the United Kingdom, also impose obligations on X to enforce against not only illegal content but also categories of content deemed by law to be “harmful” or “unsafe.” As a result, your Content or account may be subject to restrictions in those jurisdictions. We may also suspend or terminate your account for other reasons, such as prolonged inactivity, risk of legal exposure, or commercial inviability. There are intellectual property licenses in these Terms: You retain ownership and rights to any of your Content you post or share, and you provide us with a broad, royalty-free license to make your Content available to the rest of the world and to let others do the same. Conversely, we provide you a license to use the software we provide as part of the Services, such as the X mobile application, solely for the purpose of enabling you to use and enjoy the benefit of the Services. Your use of the Services is at your own risk: We provide the Services on an “AS IS” and “AS AVAILABLE” basis, and we disclaim all warranties, responsibility, and liability to you or others to the extent permitted by law. You may be exposed to offensive or harmful Content posted by other users. The Services may change from time to time, and we may limit or terminate availability of the Services or particular features to you or other users at any time. You have remedies and redress mechanisms, but our liability is limited: You have a right to terminate this agreement at any time by deactivating your account and discontinuing use of the Services. Depending on your country of residence, we may not be liable for certain types of damages as described in the agreement, and in any event, our aggregate liability shall not exceed the greater of $100 USD or the amount you paid us, if any, in the past six months for the Services giving rise to the claim. Further, if you believe that your Content has been displayed on the Services in an unauthorized manner that constitutes copyright infringement, the reporting process is detailed in these Terms. If you are a recipient of the X Service in the United Kingdom, you may challenge enforcement actions (such as Content removal or account suspension) that breach these Terms by filing a complaint through our internal complaints process or by bringing a claim in a competent court, as provided under the Online Safety Act 2023. You can find details on how to file a complaint here . If you are a recipient of the X Service in the European Union, you may challenge certain decisions we make under the Digital Services Act (Regulation (EU) 2022/2065) via our internal process or via out-of-court dispute settlement as described here . Please also note that these Terms incorporate our Privacy Policy ( https://x.com/privacy ) as well as other terms applicable to your use of the Services and your Content. Finally, these Terms may vary depending on where you live, but in any case, you must be at least 13 years old to use X. If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States, the X User Agreement comprises these Terms of Service , our Privacy Policy , our Rules and Policies , and all incorporated policies. If you live in the European Union, EFTA States, or the United Kingdom, the X User Agreement comprises these Terms of Service , our Privacy Policy , our Rules and Policies , and all incorporated policies. X Terms of Service If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States These Terms of Service (“Terms”) govern your relationship with us and your and other users’ access to and use of, and anything otherwise relating to, our or our corporate affilitates’ services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.x.com/rules-and-policies/x-services-and-corporate-affiliates ) that link to these Terms (collectively, the “Services”), and any information, text, links, graphics, photos, audio, videos, or other materials or arrangements of materials uploaded, downloaded or appearing on the Services (collectively referred to as “Content”). By using the Services you agree to be bound by these Terms. These Terms are an agreement between you and X Corp., which provides X and the Services, with its registered office at 865 FM 1209, Building 2, Bastrop, TX 78602 U.S.A. The words “we,” “us,” and “our” mean X Corp. 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Disclaimers and Limitations of Liability 6. General 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Disclaimers and Limitations of Liability 6. General 1. Who May Use the Services You may use the Services only if you agree to form a binding contract with us and are not a person barred from receiving services under the laws of the applicable jurisdiction. In any case, you must be at least 13 years old to use the Services. If you are (i) accepting these Terms and/or using the Services, which constitutes acceptance of these Terms, or (ii) accepting these Terms in order to authorize the use of the Services on behalf of a minor (being any person under the age of majority in any given country), company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so or, as the case may be, have the authority to bind such minor and/or entity to these Terms. The words “you” and “your” as used in these Terms shall refer either to the person accepting these Terms or such minor (as defined in (i)) and/or the entity referenced in (ii), as applicable. 2. Privacy Our Privacy Policy ( https://x.com/privacy ) describes how we handle the information you provide to us when you use the Services. You understand that through your use of the Services you consent to the collection and use (as set forth in the Privacy Policy) of this information, including the transfer of this information to the United States, Ireland, and/or other countries for storage, processing and use by us and our affiliates. 3. Content on the Services You are responsible for your use of the Services and for any Content, including anything referenced therein, you provide, create, post, or otherwise utilize, including any inputs, prompts, outputs, and/or information obtained or created through the Services. It is your responsibility to comply with all applicable laws, rules, policies, and regulations that are applicable to you or your Content, including on a third party’s or our affiliates’ services. You should only provide, create, or generate Content that you are comfortable sharing with others. Any use or reliance on any Content or materials posted via the Services or obtained by you through the Services is at your own risk. We do not endorse, support, represent or guarantee the completeness, truthfulness, accuracy, or reliability of any Content or communications posted or otherwise obtained via the Services or endorse any alleged facts or opinions expressed via the Services. You understand that by using the Services, you may be exposed to Content that might be offensive, harmful, inaccurate or otherwise inappropriate, or in some cases, postings that have been mislabeled or are otherwise deceptive. All Content, including anything referenced therein, is the sole responsibility of the person who posted, generated, inputted, or created such Content. We may not monitor or control the Content posted, generated, inputted, or created via the Services, and we cannot take responsibility for such Content. We reserve the right to remove Content that violates the User Agreement, including for example, copyright or trademark violations or other intellectual property misappropriation, impersonation, unlawful conduct, or harassment. Certain jurisdictions, including the European Union and the United Kingdom, impose obligations on us to enforce against categories of content deemed by law to be harmful or unsafe, such as bullying and humiliating content, content that promotes or encourages feeding or eating disorders, as well as content that encourages or makes available knowledge of methods of self-harm and suicide. As a result, your Content may be subject to restrictions as required by these jurisdictions. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.x.com/rules-and-policies , https://help.x.com/rules-and-policies/x-report-violation#specific-violations , and https://help.x.com/managing-your-account/suspended-x-accounts ). If you believe that your Content has been copied in a way that constitutes copyright infringement, please report this by visiting our Copyright reporting form ( https://help.x.com/forms/ipi ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 865 FM 1209, Building 2 Bastrop, TX 78602 Reports: https://help.x.com/forms/ipi Email: copyright@x.com Your Rights and Grant of Rights in the Content You retain your rights to any Content, including anything referenced therein, you submit, input, create, generate, post, or display on or through the Services. What’s yours is yours — you own your Content (and your incorporated audio, photos, and videos are considered part of the Content). In choosing to submit, input, create, generate, post, or display Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display, upload, download, and distribute such Content, including anything referenced therein, in any and all media or distribution methods now known or later developed, for any purpose. For clarity, these rights include, for example, curating, transforming, and translating. This license authorizes us to make your Content available to the rest of the world and to let others do the same. You agree that this license includes the right for us to (i) analyze text and other information you provide and to otherwise provide, promote, and improve the Services, including, for example, for use with and training of our machine learning and artificial intelligence models, whether generative or another type; and (ii) to make Content submitted to or through the Services available to other companies, organizations or individuals, including, for example, for improving the Services and the syndication, broadcast, distribution, repost, promotion or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Such additional uses by us, or other companies, organizations or individuals, is made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services as the use of the Services by you is hereby agreed as being sufficient compensation for the Content and grant of rights herein. We have an evolving set of rules for how ecosystem partners can interact with your Content on the Services. These rules exist to enable an open ecosystem with your rights in mind. You understand that we may modify or adapt your Content as it is distributed, syndicated, published, or broadcast by us and our partners and/or make changes to your Content in order to adapt the Content to different media. You represent and warrant that you have, or have obtained, all rights, licenses, consents, permissions, power and/or authority necessary to grant the rights granted herein for any Content that you input, submit, create, post, generate, or display on or through the Services. You agree and warrant that such Content does not contain material subject to copyright or other proprietary rights, unless you have obtained the necessary permissions or are otherwise legally entitled to post or otherwise use the material and to grant us the license described above. 4. Using the Services Please review our Rules and Policies , which are part of the User Agreement and outline conduct that is prohibited on the Services, as well as categories of content deemed by law to be harmful or unsafe in certain jurisdictions. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. X takes enforcement actions when Content or user behavior is in violation of our Rules and Policies or in relation to sensitive media. You can review X’s enforcement options and how you can appeal our enforcement decision here . The Services evolve constantly. As such, the Services may change from time to time, at our discretion. We may stop (permanently or temporarily) providing the Services or any features within the Services to you or to users generally. We also retain the right to create limits on use and storage at our sole discretion at any time. We may also remove or refuse to distribute any Content on the Services, limit distribution or visibility of any Content on the service, suspend or terminate users, and reclaim usernames without liability to you. In consideration for our granting you access to and use of the Services, you agree that we and our third-party providers and partners may place advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. We also reserve the right to access, read, preserve, and disclose any information as we reasonably believe is necessary to (i) satisfy any applicable law, regulation, legal process or governmental request; (ii) enforce the Terms, including investigation of potential violations hereof; (iii) detect, prevent, or otherwise address fraud, security or technical issues; (iv) respond to user support requests; or (v) protect the rights, property or safety of X, its users and the public. We do not disclose personally-identifying information to third parties except in accordance with our Privacy Policy . Certain services or features may be offered on X for which additional terms and conditions may apply in connection with your use of those services. By using or paying for any of these additional services, you agree to any additional terms applicable to those services, and those additional terms become part of our agreement with you. If any of the applicable additional terms conflict with these Terms, the additional terms will prevail while you are using those services to which they apply. If you use paid features, products, or services of the Services, you agree to the applicable Terms for Paid Services ( https://legal.x.com/purchaser-terms ). If you use developer features, products, or services of the Services, including but not limited to X for Websites ( https://developer.x.com/docs/x-for-websites ), X Cards ( https://developer.x.com/docs/x-for-websites/cards/overview/abouts-cards ), Public API ( https://developer.x.com/docs ), or Sign in with X ( https://docs.x.com/resources/fundamentals/authentication/guides/log-in-with-x ), you agree to our Developer Agreement ( https://developer.x.com/developer-terms/agreement ) and Developer Policy ( https://developer.x.com/developer-terms/policy ). If you want to reproduce, modify, create derivative works, distribute, sell, transfer, publicly display, publicly perform, transmit, or otherwise use the Services or Content on the Services, you must use the interfaces and instructions we provide, except as permitted through the Services, these Terms, or the terms provided on https://developer.x.com/developer-terms . Otherwise, all such actions are strictly prohibited. If you are a security researcher, you are required to comply with the rules of our Vulnerability Reporting Program ( https://hackerone.com/x ). The requirements set out in the preceding paragraph may not apply to those participating in our Vulnerability Reporting Program. If you use advertising features, products, or services of the Services in any way, including but not limited to self-service and managed service offerings, you agree that your use of the advertising features, products, and services as well as your advertisements are subject to the terms of our Master Services Agreement ( https://ads.x.com/terms ). Your Account You may need to create an account to use the Services. You are responsible for safeguarding your account, so use a strong password and limit its use to this account, and use two-factor authentication via an authenticator app or security key. We cannot and will not be liable for any loss or damage arising from your failure to comply with the above. You can control most communications from the Services. We may need to provide you with certain communications, such as service announcements and administrative messages. These communications are considered part of the Services and your account, and you may not be able to opt-out from receiving them. If you added your phone number to your account and you later change or deactivate that phone number, you must update your account information to help prevent us from communicating with anyone who acquires your old number. Your License to Use the Services We give you a personal, worldwide, royalty-free, non-assignable and non-exclusive license to use the software provided to you as part of the Services. This license cannot be assigned, gifted, sold, shared or transferred in any other manner to any other individual or entity without X’s express written consent. This license has the sole purpose of enabling you to use and enjoy the benefit of the Services as provided on X, in the manner permitted by these Terms. The Services are protected by copyright, trademark, and other laws of both the United States and other countries. Nothing in the Terms gives you a right to use the X name or Twitter name or any of the X or Twitter trademarks, logos, domain names, other distinctive brand features, and other proprietary rights, and you may not do so without our express written consent. All right, title, and interest in and to the Services (excluding Content provided by users) are and will remain our and our licensors' exclusive property. Any feedback, comments, or suggestions you may provide regarding X, or the Services is entirely voluntary and we will be free to use such feedback, comments or suggestions as we see fit and without any obligation to you. Misuse of the Services You also agree not to misuse the Services, for example, by interfering with them or accessing them using a method other than the interface and the instructions that we provide. You agree that you will not work around any technical limitations in the software provided to you as part of the Services, or reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits. You may not do any of the following while accessing or using the Services: (i) access, tamper with, or use non-public areas of the Services, our computer systems, or the technical delivery systems of our providers; (ii) probe, scan, or test the vulnerability of any system or network or breach or circumvent any security or authentication measures; (iii) access or search or attempt to access or search the Services by any means (automated or otherwise) other than through our currently available, published interfaces that are provided by us (and only pursuant to the applicable terms and conditions), unless you have been specifically allowed to do so in a separate agreement with us (NOTE: crawling or scraping the Services in any form, for any purpose without our prior written consent is expressly prohibited); (iv) attempt to circumvent, manipulate, or disable systems and Services, including through "jailbreaking", “prompt engineering or injection", or other methods intended to override or manipulate safety, security or other platform controls; (v) forge any TCP/IP packet header or any part of the header information in any email or posting; (vi) in any way use the Services to send altered, deceptive or false source-identifying information; (vii) engage in any conduct that violates our Platform Manipulation and Spam Policy or any other Rules and Policies , including our Misuse of Reporting Features Policy ; or (viii) interfere with, or disrupt, (or attempt to do so), the access of any user, host or network, including, without limitation, sending a virus, overloading, flooding, spamming, mail-bombing the Services, or by scripting the creation of Content in such a manner as to interfere with or create an undue burden on the Services. It is also a violation of these Terms to facilitate or assist others in violating these Terms, including by distributing products or services that enable or encourage violation of these Terms. Ending These Terms You may end your legal agreement with us at any time by deactivating your accounts and discontinuing your use of the Services. See https://help.x.com/managing-your-account/how-to-deactivate-x-account for instructions on how to deactivate your account and the Privacy Policy for more information on what happens to your information. We may suspend or terminate your account or cease providing you with all or part of the Services at any time if we reasonably believe: (i) you have violated these Terms or our Rules and Policies , (ii) you create risk or possible legal exposure for us; (iii) your account should be removed due to unlawful conduct; (iv) your account should be removed due to prolonged inactivity; or (v) our provision of the Services to you is no longer commercially viable. We will make reasonable efforts to notify you by the email address associated with your account or the next time you attempt to access your account, depending on the circumstances. To the extent permitted by law, we may also terminate your account or cease providing you with all or part of the Services for any other reason or no reason at our convenience. In all such cases, the Terms shall terminate, including, without limitation, your license to use the Services, except that the following sections shall continue to apply: 2, 3, 5, 6, and the misuse provisions of Section 4 (“Misuse of the Services”). If you believe your account was terminated in error you can file an appeal following the steps found in our Help Center ( https://help.x.com/forms/account-access/appeals ). For the avoidance of doubt, these Terms survive the deactivation or termination of your account. 5. Disclaimers and Limitations of Liability The Services are Available "AS-IS" Your access to and use of the Services or any Content are at your own risk. You understand and agree that the Services are provided to you on an “AS IS” and “AS AVAILABLE” basis. The “X Entities” refers to X Corp., its parents, affiliates, related companies, officers, directors, employees, agents, representatives, partners, and licensors. Without limiting the foregoing, to the maximum extent permitted under applicable law, THE X ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The X Entities make no warranty or representation and disclaim all responsibility and liability for: (i) the completeness, accuracy, availability, timeliness, security or reliability of the Services or any Content; (ii) any harm to your computer system, loss of data, or other harm that results from your access to or use of the Services or any Content; (iii) the deletion of, or the failure to store or to transmit, any Content and other communications maintained by the Services; and (iv) whether the Services will meet your requirements or be available on an uninterrupted, secure, or error-free basis. No advice or information, whether oral or written, obtained from the X Entities or through the Services, will create any warranty or representation not expressly made herein. Limitation of Liability NOTWITHSTANDING ANY OTHER TERMS TO THE CONTRARY, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE X ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, RELIANCE OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (i) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE SERVICES; (ii) ANY CONDUCT OR CONTENT OF ANY USER OR THIRD PARTY ON THE SERVICES, INCLUDING WITHOUT LIMITATION, ANY DEFAMATORY, OFFENSIVE OR ILLEGAL CONDUCT OF OTHER USERS OR THIRD PARTIES; (iii) ANY CONTENT OBTAINED FROM THE SERVICES; OR (iv) UNAUTHORIZED ACCESS, USE OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT. IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE X ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID US, IF ANY, IN THE PAST SIX MONTHS FOR THE SERVICES GIVING RISE TO THE CLAIM. THE LIMITATIONS OF THIS SUBSECTION SHALL APPLY TO ANY THEORY OF LIABILITY, WHETHER BASED ON WARRANTY, CONTRACT, STATUTE, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, AND WHETHER OR NOT THE X ENTITIES HAVE BEEN INFORMED OF THE POSSIBILITY OF ANY SUCH DAMAGE, AND EVEN IF A REMEDY SET FORTH HEREIN IS FOUND TO HAVE FAILED OF ITS ESSENTIAL PURPOSE. IN THE EVENT ANY PORTION OF THESE LIMITATION OF LIABILITY PROVISIONS IS DEEMED UNENFORCEABLE AS A MATTER OF LAW, THAT LIMITATION SHALL INSTEAD BE THE GREATEST LIMITATION PERMITTED BY LAW. BY AGREEING TO THESE TERMS OR USING THE SERVICES, YOU AGREE, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THAT THE X ENTITIES ARE NOT RESPONSIBLE OR LIABLE TO YOU OR OTHERS FOR THE ACTIONS OR CONDUCT OF USERS AND THIRD PARTIES ON THE SERVICES, OR FOR ANY CONTENT USERS AND THIRD PARTIES SHARE ON THE SERVICES, INCLUDING OFFENSIVE, DEFAMATORY, ILLEGAL OR OTHER OBJECTIONABLE CONTENT. Liquidated Damages Protecting our users’ data and our system resources is important to us. You further agree that, to the extent permitted by applicable law, if you violate the Terms, or you induce or knowingly facilitate others to do so, in addition to all other legal remedies available to us, you will be jointly and severally liable to us for liquidated damages as follows for requesting, viewing, or accessing more than 1,000,000 posts (including reply posts, video posts, image posts, and any other posts) in any 24-hour period - $15,000 USD per 1,000,000 posts. You agree that these amounts are (i) a reasonable estimate of our damages; (ii) not a penalty; and (iii) not otherwise limiting of our ability to recover from you or others under any legal or equitable theory or claim, including but not limited to statutory damages and/or equitable relief. You further agree that repeated violations of these Terms will irreparably harm and entitle us to injunctive and/or other equitable relief, in addition to monetary damages. 6. General We may revise these Terms from time to time. The changes will not be retroactive, and the most current version of the Terms, which will always be at https://x.com/tos , will govern our relationship with you. We will try to notify you of material revisions, for example via a service notification or an email to the email associated with your account. By continuing to access or use the Services after those revisions become effective, you agree to be bound by the revised Terms. The laws of the State of Texas, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and us, notwithstanding any other agreement between you and us to the contrary. Notwithstanding any other agreement to the contrary, all disputes related to these Terms, the Services, or any patents — including without limitation disputes related to or arising from any Content (whether your or others’ Content), or your or others’ use of the Services or the complete or partial termination thereof — shall be brought and must proceed exclusively in the federal 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. For the avoidance of doubt, the choice of law and forum selection provisions of this paragraph shall apply regardless of whether a dispute or any claims contained therein are based in contract, tort, statute, common law, or otherwise, and the choice of law and forum selection provisions of this paragraph shall apply to pending and future disputes and shall apply to your dispute regardless of when the conduct relating to the dispute arose or occurred. The choice of law and forum selection provisions of this paragraph shall also extend to disputes involving our U.S. corporate affiliates, who are intended third-party beneficiaries of this paragraph. Without prejudice to the foregoing, you agree that, in its sole discretion, X may bring any claim, cause of action, or dispute we have against you in any competent court in the country in which you reside that has jurisdiction and venue over the claim. 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 against us or our corporate affiliates. If you are a federal, state, or local government entity in the United States using the Services 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, these Terms 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). You and X agree that you must initiate any proceeding or action asserting a federal claim within one (1) year of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Services. You and X agree that you must initiate any proceeding or action asserting a state law claim within two (2) years of the date of the occurrence of the event or facts giving rise to a dispute that is arising out of or related to these Terms or the Services. Otherwise, to the extent permitted by applicable law, 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 barred. In the event that any provision of these Terms is held to be invalid or unenforceable, then that provision will be limited or eliminated to the minimum extent necessary, and the remaining provisions of these Terms will remain in full force and effect. Our failure to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. The X User Agreement is written in English but is made available in multiple languages through translations. X strives to make the translations as accurate as possible to the original English version. However, in case of any discrepancies or inconsistencies, the English language version of the X User Agreement shall take precedence. You acknowledge that English shall be the language of reference for interpreting and constructing the terms of the X User Agreement. If you have any questions about these Terms, please contact us . Effective: January 15, 2026 Archive of Previous Terms X Terms of Service If you live in the European Union, EFTA States, or the United Kingdom These Terms of Service (“Terms”) govern your relationship with us and your and other users’ access to and use of, and anything otherwise relating to, our or our corporate affiliates’ services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.x.com/rules-and-policies/x-services-and-corporate-affiliates ) that link to these Terms (collectively, the “Services”), and any information, text, links, graphics, photos, audio, videos, or other materials or arrangements of materials uploaded, downloaded or appearing on the Services (collectively referred to as “Content”). By using the Services you agree to be bound by these Terms. These Terms are an agreement between you and X Internet Unlimited Company (Co. number 503351, VAT number IE9803175Q), an Irish company, which provides X and the Services, with its registered office at One Cumberland Place, Fenian Street Dublin 2, D02 AX07 Ireland. The words “we,” “us,” and “our,” mean X Internet Unlimited Company. 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Limitations of Liability 6. General 1. Who May Use the Services 2. Privacy 3. Content on the Services 4. Using the Services 5. Limitations of Liability 6. General 1. Who May Use the Services You may use the Services only if you agree to form a binding contract with us and are not a person barred from receiving services under the laws of the applicable jurisdiction. In any case, you must be at least 13 years old to use the Services. If you are (i) accepting these Terms and/or using the Services, which constitutes acceptance of these Terms, or (ii) accepting these Terms in order to authorize the use of the Services on behalf of a minor (being any person under the age of majority in any given country), company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so or, as the case may be, have the authority to bind such minor and/or entity to these Terms. The words “you” and “your” as used in these Terms shall refer either to the person accepting these Terms or such minor (as defined in (i)) and/or the entity referenced in (ii), as applicable. 2. Privacy Our Privacy Policy ( https://x.com/privacy ) describes how we handle the information you provide to us when you use the Services. You understand that through your use of the Services you consent to the collection and use (as set forth in the Privacy Policy) of this information, including the transfer of this information to the United States, Ireland, and/or other countries for storage, processing and use by us and our affiliates. 3. Content on the Services You are responsible for your use of the Services and for any Content, including anything referenced therein, you provide, create, post, or otherwise utilize, including any inputs, prompts, outputs, and/or information obtained or created through the Services. It is your responsibility to comply with all applicable laws, rules, policies, and regulations that are applicable to you or your Content, including on a third party’s or affiliates’ services. You should only provide, create, or generate Content that you are comfortable sharing with others. Any use or reliance on any Content or materials posted via the Services or obtained by you through the Services is at your own risk. We do not endorse, support, represent or guarantee the completeness, truthfulness, accuracy, or reliability of any Content or communications posted or otherwise obtained via the Services or endorse any alleged facts or opinions expressed via the Services. You understand that by using the Services, you may be exposed to Content that might be offensive, harmful, inaccurate or otherwise inappropriate, or in some cases, postings that have been mislabeled or are otherwise deceptive. Content recommendations are made based on a combination of factors: how you engage with the Services, the topics you have indicated that you are interested in, and likes of other users with your similar interests. Adjustments can be made in your settings, and additional information can be found in our Help Center ( https://help.x.com/resources/recommender-systems ). All Content, including anything referenced therein, is the sole responsibility of the person who posted, generate, inputted, or created such Content. We may not monitor or control the Content posted, generated, inputted, or created via the Services, and we cannot take responsibility for such Content. We reserve the right to remove Content that violates the User Agreement, including for example, copyright or trademark violations or other intellectual property misappropriation, impersonation, unlawful conduct, or harassment. Certain jurisdictions, including the European Union and the United Kingdom, impose obligations on us to enforce against categories of content deemed by law to be harmful or unsafe, such as bullying and humiliating content, content that promotes or encourages feeding or eating disorders, as well as content that encourages or makes available knowledge of methods of self-harm and suicide. As a result, your Content may be subject to restrictions as required by these jurisdictions. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.x.com/rules-and-policies , https://help.x.com/rules-and-policies/x-report-violation , and https://help.x.com/managing-your-account/suspended-x-accounts ). If you believe that your Content has been copied in a way that constitutes copyright infringement, please report this by visiting our Copyright reporting form ( https://help.x.com/forms/ipi ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 865 FM 1209, Building 2 Bastrop, TX 78602 Reports: https://help.x.com/forms/ipi Email: copyright@x.com Your Rights and Grant of Rights in the Content You retain your rights to any Content, including anything referenced therein, you submit, input, create, generate, post, or display on or through the Services. What’s yours is yours — you own your Content (and your incorporated audio, photos, and videos are considered part of the Content). In choosing to submit, input, create, generate, post, or display Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display, upload, download, and distribute such Content, including anything referenced therein, in any and all media or distribution methods now known or later developed, for any purpose. For clarity, these rights include, for example, curating, transforming, and translating. This license authorizes us to make your Content available to the rest of the world and to let others do the same. However, if you have chosen via our features to limit the distribution of your Content to a restricted community, we will respect that choice. You also agree that this license includes the right to analyze text and other information you provide with the view to improve the Services. You agree that this license includes the right for us to (i) provide, promote, and improve the Services, including, for example, for use with and training of our machine learning and artificial intelligence models, whether generative or another type; and (ii) to make Content submitted to or through the Services available to other companies, organizations or individuals, including, for example, for improving the Services and the syndication, broadcast, distribution, repost, promotion or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Such additional uses by us, or other companies, organizations or individuals, is made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services as the use of the Services by you is hereby agreed as being sufficient compensation for the Content and grant of rights herein. We have an evolving set of rules for how ecosystem partners can interact with your Content on the Services. These rules exist to enable an open ecosystem with your rights in mind. You understand that we may modify or adapt your Content as it is distributed, syndicated, published, or broadcast by us and our partners and/or make changes to your Content in order to adapt the Content to different media. You represent and warrant that you have, or have obtained, all rights, licenses, consents, permissions, power and/or authority necessary to grant the rights granted herein for any Content that you input, submit, create, post, generate, or display on or through the Services. You agree and warrant that such Content does not contain material subject to copyright or other proprietary rights, unless you have obtained the necessary permissions or are otherwise legally entitled to post or otherwise use the material and to grant us the license described above. 4. Using the Services Please review our Rules and Policies , which are part of the User Agreement and outline conduct that is prohibited on the Services, as well as categories of content deemed by law to be harmful or unsafe in certain jurisdictions. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. X takes enforcement actions when Content or user behavior is in violation of our Rules and Policies or in relation to sensitive media. You can review X’s enforcement options and how you can appeal our enforcement decision here . The Services evolve constantly. As such, the Services may change from time to time, at our discretion. We may stop (permanently or temporarily) providing the Services or any features within the Services to you or to users generally. We also retain the right to create limits on use and storage at our sole discretion at any time. We may also remove or refuse to distribute any Content on the Services, limit distribution or visibility of any Content on the service, suspend or terminate users, and reclaim usernames if it is appropriate, including for the following reasons: (i) protecting the Services or our users; (ii) compliance with applicable laws or orders from competent authorities; (iii) breach of these Terms or our Rules and Policies or third parties' intellectual property or other rights; (iv) if you or your Content exposes us, other users or any third party to legal or regulatory risk; and/or (v) your prolonged inactivity. In consideration for our granting you access to and use of the Services, you agree that we and our third-party providers and partners may place advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. We also reserve the right to access, read, preserve, and disclose any information as we reasonably believe is necessary to (i) satisfy any applicable law, regulation, legal process or governmental request; (ii) enforce the Terms, including investigation of potential violations hereof; (iii) detect, prevent, or otherwise address fraud, security or technical issues; (iv) respond to user support requests; or (v) protect the rights, property or safety of X, its users and the public. We do | 2026-01-13T08:49:23 |
https://x.com/tos/previous | Previous Terms of Service X logo icon Previous Terms of Service Please Note: These documents are NOT current. Please read the current Terms of Service . Version 19: September 29, 2023 Version 18: May 18, 2023 Version 17: June 10, 2022 Version 16: August 19, 2021 Version 15: June 18, 2020 Version 14: January 01, 2020 Version 13: May 25, 2018 Version 12: October 02, 2017 Version 11: September 30, 2016 Version 10: January 27, 2016 Version 9: May 18, 2015 Version 8: September 08, 2014 Version 7: June 25, 2012 Version 6: May 17, 2012 Version 5: June 01, 2011 Version 4: November 16, 2010 Version 3: September 18, 2009 Version 2: September 10, 2009 Version 1 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 Language 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:49:23 |
https://docs.npmjs.com/ | npm Docs Skip to search Skip to content npm Docs npmjs.com Status Support Site navigation About npm Getting started Setting up your npm user account Creating a new user account on the public registry Creating a strong password Receiving a one-time password over email About two-factor authentication Configuring two-factor authentication Accessing npm using two-factor authentication Recovering your 2FA-enabled account Managing your npm user account Managing your profile settings Changing your npm username Deleting your npm user account Requesting an export of your personal data Paying for your npm user account Upgrading to a paid user account plan Viewing, downloading, and emailing receipts for your npm user account Updating user account billing settings Downgrading to a free user account plan Configuring your local environment About npm CLI versions Downloading and installing Node.js and npm Troubleshooting Generating and locating npm-debug.log files Common errors Try the latest stable version of node Try the latest stable version of npm Packages and modules Introduction to packages and modules About the public npm registry About packages and modules About scopes About public packages About private packages npm package scope, access level, and visibility Contributing packages to the registry Creating a package.json file Creating Node.js modules About package README files Creating and publishing unscoped public packages Creating and publishing scoped public packages Creating and publishing private packages Package name guidelines Specifying dependencies and devDependencies in a package.json file About semantic versioning Adding dist-tags to packages Updating and managing your published packages Changing package visibility Adding collaborators to private packages owned by a user account Updating your published package version number Deprecating and undeprecating packages or package versions Transferring a package from a user account to another user account Unpublishing packages from the registry Getting packages from the registry Searching for and choosing packages to download Downloading and installing packages locally Downloading and installing packages globally Resolving EACCES permissions errors when installing packages globally Updating packages downloaded from the registry Using npm packages in your projects Using deprecated packages Uninstalling packages and dependencies Securing your code About audit reports Auditing package dependencies for security vulnerabilities Generating provenance statements Trusted publishing with OIDC About ECDSA registry signatures Verifying ECDSA registry signatures Requiring 2FA for package publishing and settings modification Reporting malware in an npm package Integrations Integrating npm with external services About access tokens Creating and viewing access tokens Revoking access tokens Using private packages in a CI/CD workflow Docker and private modules Organizations Creating and managing organizations Creating an organization Converting your user account to an organization Requiring two-factor authentication in your organization Renaming an organization Deleting an organization Paying for your organization Upgrading to a paid organization plan Viewing, downloading, and emailing receipts for your organization Updating organization billing settings Downgrading to a free organization plan Managing organization members Adding members to your organization Accepting or rejecting an organization invitation Organization roles and permissions Managing organization permissions Removing members from your organization Managing teams About the developers team Creating teams Adding organization members to teams Removing organization members from teams Managing team access to organization packages Removing teams Managing organization packages About organization scopes and packages Configuring your npm client with your organization settings Creating and publishing an organization scoped package Policies Terms of Use Open Source Terms Private Terms Code of Conduct Package Name Disputes npm License Privacy Policy Unpublish Policy Copyright and DMCA Policy Logos and Usage Security Replication and web crawler policy Threats and mitigations npm CLI CLI Commands npm npm access npm adduser npm audit npm bugs npm cache npm ci npm completion npm config npm dedupe npm deprecate npm diff npm dist-tag npm docs npm doctor npm edit npm exec npm explain npm explore npm find-dupes npm fund npm help npm help-search npm init npm install npm install-ci-test npm install-test npm link npm login npm logout npm ls npm org npm outdated npm owner npm pack npm ping npm pkg npm prefix npm profile npm prune npm publish npm query npm rebuild npm repo npm restart npm root npm run npm sbom npm search npm shrinkwrap npm star npm stars npm start npm stop npm team npm test npm token npm undeprecate npm uninstall npm unpublish npm unstar npm update npm version npm view npm whoami npx Configuring npm Install Folders .npmrc npm-shrinkwrap.json package.json package-lock.json Using npm Registry Package spec Config Logging Scope Scripts Workspaces Organizations Dependency Selectors Developers Removal Changelog npmjs.com Status Support GitHub npm Docs Documentation for the npm registry, website, and command-line interface About npm Getting started Packages and modules Integrations Organizations Policies Threats and mitigations npm CLI | 2026-01-13T08:49:23 |
https://wellarchitected.github.com/ | GitHub Well-Architected GitHub Well-Architected What's new Apply design thinking to build and ship your software securely and at scale with GitHub Opinionated resources for designing, deploying, and optimizing resilient GitHub solutions. Curated by GitHub's customer-facing engineers, partner community, and key customer contributors. Explore the Framework Learn more → Deploy GitHub with confidence Best Practices for Designing, Implementing, and Optimizing Your GitHub Environment A Community-Driven Framework Structured Around Key Pillars Productivity Proven strategies and tools to streamline workflows, automate processes, and accelerate team velocity. Learn more → Collaboration Inclusive practices and transparent project management to foster open knowledge sharing, enhance teamwork, and boost overall productivity. Learn more → Application Security Proactive guidelines for embedding security into every stage of development, from code scanning to compliance. Learn more → Governance Clear policies and controls that balance innovation with oversight, ensuring compliance, access management, and accountability at scale. Learn more → Architecture Approaches for designing scalable, resilient, and efficient GitHub environments, including enterprise-level solutions (e.g., GHES), tailored to your organization's needs. Learn more → Design, Deploy, and Scale to Confidently Achieve Your Business Objectives Embrace design thinking to deliver solutions aligned with your strategic objectives. Explore our self-guided Well-Architected assessment checklists or collaborate with experts GitHub, Microsoft, and our Partners for tailored guidance Get started Learn about the assessment → X Facebook YouTube GitHub GitHub Inc. ©2026 Terms Privacy Security Status Docs Contact GitHub Pricing API Partners Blog About | 2026-01-13T08:49:23 |
https://www.highlight.io/blog/the-complete-guide-to-opentelemetry-in-next-js | The complete guide to OpenTelemetry in Next.js Pricing Customers Blog Careers Docs The complete guide to OpenTelemetry in Next.js Sign up Back Nov 13, 2025 • 11 min. read Migrating from Highlight.io to LaunchDarkly Observability Company Product Updates Oct 25, 2022 • 7 min. read The Debugging Process and Techniques for Web Applications (Part 2/2) Frontend Observability Developer Experience Aug 24, 2022 • 18 min. read The beauty of contact-first API design Engineering Feb 10, 2025 • 14 min read The complete guide to OpenTelemetry in Next.js Engineering Backend Observability Vadim Korolik CTO @ Highlight Highlight.io is an open source monitoring platform. Check out highlight.io if you’re interested in learning more. OpenTelemetry is an important specification that defines how we send telemetry data to observability backends like Highlight.io, Grafana, and others. OpenTelemetry is great because it is vendor agnostic, and can be used with several observability backends. If you're new to OpenTelemetry, you can learn more about it here . This complete guide to OpenTelemetry in Next.js covers high-level concepts as well as how to send traces, logs, and metrics to your OpenTelemetry backend of choice. Setting Up OpenTelemetry for Next.js: Tracing, Logging, and Metrics Let's walk through setting up OpenTelemetry in a Next.js project, covering: Tracing: Capturing distributed traces for API requests and page transitions Logging: Collecting structured logs that correlate with traces Metrics: Exporting performance and custom application metrics There are several reasons that make OTel a great choice for monitoring your Next.js application: Built-in Spans: Next.js provides automatic spans at the framework level Exception Tracking: Errors are automatically captured within traces by the framework Simplified Setup: @vercel/otel eliminates the need to manually configure OpenTelemetry SDKs, exporters, and instrumentations By the end of this tutorial, you'll have all the observability data you need to be proactively notified when something goes wrong, troubleshoot issues quickly, and fix performance bottlenecks in the critical parts of your code. Installing OpenTelemetry in Next.js We've covered instrumenting Next.js with @vercel/otel in our blog post on using @vercel/otel in Next.js . While @vercel/otel is a simpler option for many applications, it may not give you full control over the OpenTelemetry SDKs. Today, we'll go through a complete guide to setting up OpenTelemetry from scratch, explaining the configuration options along the way. Our implementation covers setting up @opentelemetry/sdk-node which is only compatible with the Node.js runtime. If you are using the Edge runtime in Next.js, you'll need to use @vercel/otel which conditionally switches to the @opentelemetry/sdk-trace-web implementation which is Edge runtime compatible, or implement a similar approach yourself.` To get started, install the necessary OpenTelemetry dependencies: yarn add @opentelemetry/api @opentelemetry/api-logs @opentelemetry/sdk-node \ @opentelemetry/instrumentation-http @opentelemetry/instrumentation-fetch \ @opentelemetry/exporter-trace-otlp-grpc @opentelemetry/exporter-logs-otlp-grpc \ @opentelemetry/exporter-metrics-otlp-grpc @opentelemetry/resources @opentelemetry/semantic-conventions This setup includes the core OpenTelemetry API, SDK, HTTP and Fetch instrumentations, and OTLP exporters for traces and metrics. Setting Up the OpenTelemetry SDK Create a new file otel.ts at the root of your Next.js project: import { NodeSDK } from '@opentelemetry/sdk-node'; import { ConsoleSpanExporter } from '@opentelemetry/sdk-trace-base'; import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-grpc'; import { OTLPMetricExporter } from '@opentelemetry/exporter-metrics-otlp-grpc'; import { Resource } from '@opentelemetry/resources'; import { SEMRESOURCENAME } from '@opentelemetry/semantic-conventions'; import { HttpInstrumentation } from '@opentelemetry/instrumentation-http'; import { FetchInstrumentation } from '@opentelemetry/instrumentation-fetch'; import { AlwaysOnSampler } from '@opentelemetry/sdk-trace-base'; import { BatchSpanProcessor } from '@opentelemetry/sdk-trace-base'; import { BatchLogRecordProcessor } from '@opentelemetry/sdk-logs'; import { PeriodicExportingMetricReader } from '@opentelemetry/sdk-metrics'; const exporter = new OTLPTraceExporter(config) const spanProcessor = new BatchSpanProcessor(exporter, opts) const logsExporter = new OTLPLogExporter(config) const logProcessor = new BatchLogRecordProcessor(logsExporter, opts) const metricsExporter = new OTLPMetricExporter(config) const metricsReader = new PeriodicExportingMetricReader({exporter: metricsExporter}) // Configure the OTLP exporter to send data to your OpenTelemetry backend const config = { url: 'https://otel.highlight.io:4317' } const sdk = new NodeSDK({ autoDetectResources: true, resourceDetectors: [processDetectorSync], resource: new Resource({ [SEMRESOURCENAME.SERVICE_NAME]: 'nextjs-app', 'highlight.project_id': '<YOUR_PROJECT_ID>', }), spanProcessors: [spanProcessor], logRecordProcessors: [logProcessor], metricReader: metricReader, traceExporter: exporter, contextManager: new AsyncLocalStorageContextManager(), sampler: new AlwaysOnSampler(), instrumentations: [new HttpInstrumentation(), new FetchInstrumentation()], }) sdk.start(); console.log('OpenTelemetry initialized'); To trigger this file to run when the app starts, you can invoke it from the Next.js magic instrumentation.ts file. export function register() { await import('./otel'); } The instrumentation.ts file is automatically detected by Next.js and will run when the app starts. Before Next.js 15, the instrumentation is experimental, so you will have to enable it explicitly: module.exports = { experimental: { instrumentationHook: true, }, }; Configuring Tracing With the SDK configured, your application will start to export the telemetry data using the exporters defined. However, you may wonder what data is being captured without any explicit code added. Next.js has built-in OpenTelemetry spans for various parts of the application, including: API routes ( pages/api or app/api ) Page router (Pages Directory) App router (App Directory) Some top-level spans are emitted out-of-the-box, while others can be turned on by turning on verbose logging: NEXT_OTEL_VERBOSE=1 Setting the NEXT_OTEL_VERBOSE environment variable will emit additional traces that give you more granularity of the code execution. For example, here's a flame graph visualization of a trace without verbose tracing, NEXT_OTEL_VERBOSE=0 : And here's the same trace with verbose tracing enabled, NEXT_OTEL_VERBOSE=1 : Let's go through some examples of the data that can be captured. In the image above, you can see the trace start with an api route request that is piped through Next.js to the API handler. We also see a custom span that wraps an ourgoing API request to another service. Because we set up auto-instrumentation, we capture the fetch call automatically, and can even propagate the trace context to the backend service. Here's a list of the top-level spans that are captured automatically by Next.js: BaseServer.handleRequest - Named [http.method] [next.route] , the root span for each incoming request to your Next.js application . AppRender.getBodyResult - Named render route (app) [next.route] , represents the process of rendering a route in the app router . AppRender.fetch - Named fetch [http.method] [http.url] , represents the fetch request executed in your code . AppRouteRouteHandlers.runHandler - Named executing api route (app) [next.route] , represents the execution of an API Route Handler in the app router . Render.getServerSideProps - Named getServerSideProps [next.route] , represents the execution of getServerSideProps for a specific route . Render.getStaticProps - Named getStaticProps [next.route] , represents the execution of getStaticProps for a specific route . Render.renderDocument - Named render route (pages) [next.route] , represents the process of rendering the document for a specific route . ResolveMetadata.generateMetadata - Named generateMetadata [next.page] , represents the process of generating metadata for a specific route . NextNodeServer.findPageComponents - Named resolve page components , represents the process of resolving page components for a specific page . NextNodeServer.getLayoutOrPageModule - Named resolve segment modules , represents loading of code modules for a layout or a page . NextNodeServer.startResponse - Named start response , represents the process of starting the response for a specific route . See the Next.js docs for more details. Whether you have an API route, a page route, or an app route, you'll see a span for each request. Spans will carry details such as what route was requested, how long each step of the processing took, and what metadata was provided in the HTTP request. The power lies in connecting the automatic spans with custom ones and ones provided by additional OpenTelemetry instrumentations. As shown in the image above, when the app route api method makes an outgoing HTTP request to another service (in this case, an example Python service), the trace will capture the duration of the backend API request and the response status code. At a glance, that can help diagnose a performance issue due to a downstream service or a failed backend API call. Logging in OpenTelemetry Let's add some more logic to otel.ts to create a logger that can be used to emit custom messages. import { LoggerProvider } from '@opentelemetry/sdk-logs'; const loggerProvider = new LoggerProvider(); const logger = loggerProvider.getLogger('nextjs-logger'); logger.emit({ severityText: 'INFO', body: 'Application started', }); You can use this logger in your code or with a helper method. Make sure to check out other OpenTelemetry logging instrumentations that can automatically hook into common logging libraries like Winston or Pino. If you want to capture console logger methods such as console.log , console.error , etc., you'll need to manually instrument them to record their logs to the OpenTelemetry logger. Here's an example of how to do that: import { LoggerProvider } from '@opentelemetry/sdk-logs'; const loggerProvider = new LoggerProvider(); const logger = loggerProvider.getLogger('nextjs-logger'); const originalConsoleLog = console.log; console.log = (...args) => { originalConsoleLog(...args); logger.emit({ severityText: 'INFO', body: args.join(' '), }); }; console.log('Hello, world!'); Capturing Exceptions with Spans Let's emit a custom span in our code that can be used to capture an exception. We'll start a span and then automatically add error attributes by capturing the error. Modify your API route: import { trace } from '@opentelemetry/api'; const tracerProvider = trace.getTracerProvider(); const tracer = tracerProvider.getTracer("tracer"); export default async function handler(req, res) { await tracer.startActiveSpan( "data.fetch", { attributes: { "user.email": email || undefined, "user.name": name || undefined, }, }, async (span) => { try { doSomething(); throw new Error('Something went wrong!'); } catch (error) { if (span) { span.recordException(error); } } }, ); } This ensures that the error is captured within the OpenTelemetry trace and can be visualized in your tracing backend. Next.js 15 also introduces a new onRequestError hook that can be used to capture server errors . You can use it in your instrumentation.ts file to intercept all server actions and capture the error: import { type Instrumentation } from 'next' export const onRequestError: Instrumentation.onRequestError = async ( err, request, context ) => { const { trace } = await import('@opentelemetry/api') const span = trace.getActiveSpan() if (span) { span.setAttributes({ 'http.url': request.path, 'http.method': request.method, 'next.router.kind': context.routerKind, 'next.router.path': context.routerPath, 'next.router.type': context.routerType, 'next.render.source': context.renderSource, 'next.render.type': context.renderType, 'next.revalidate.reason': context.revalidateReason, }) span.recordException(err) } } This example reports the error to the current active span, which is the span for the request. Exporting Metrics Next.js applications often benefit from metrics like request count, latency, and errors. Here's how to add instrumentation for request tracking in otel.ts : import { MeterProvider } from '@opentelemetry/sdk-metrics'; const meter = new MeterProvider().getMeter('nextjs-meter'); const requestCounter = meter.createCounter('http_requests_total', { description: 'Counts total HTTP requests', }); export function trackRequest() { requestCounter.add(1); } Then, use it in an API route: import { trackRequest } from '../../otel'; export default function handler(req, res) { trackRequest(); res.status(200).json({ message: 'Metrics tracked!' }); } Putting it all together Let's put all of the pieces together and create a complete otel.ts file that will automatically instrument your Next.js app. Using @vercel/otel , we'll configure export for Highlight.io, but you can use any other OpenTelemetry-compatible backend: import { NodeSDK } from '@opentelemetry/sdk-node'; import { ConsoleSpanExporter } from '@opentelemetry/sdk-trace-base'; import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-grpc'; import { OTLPMetricExporter } from '@opentelemetry/exporter-metrics-otlp-grpc'; import { Resource } from '@opentelemetry/resources'; import { SEMRESOURCENAME } from '@opentelemetry/semantic-conventions'; import { HttpInstrumentation } from '@opentelemetry/instrumentation-http'; import { FetchInstrumentation } from '@opentelemetry/instrumentation-fetch'; import { AlwaysOnSampler } from '@opentelemetry/sdk-trace-base'; import { BatchSpanProcessor } from '@opentelemetry/sdk-trace-base'; import { BatchLogRecordProcessor } from '@opentelemetry/sdk-logs'; import { PeriodicExportingMetricReader } from '@opentelemetry/sdk-metrics'; const exporter = new OTLPTraceExporter(config) const spanProcessor = new BatchSpanProcessor(exporter, opts) const logsExporter = new OTLPLogExporter(config) const logProcessor = new BatchLogRecordProcessor(logsExporter, opts) const metricsExporter = new OTLPMetricExporter(config) const metricsReader = new PeriodicExportingMetricReader({exporter: metricsExporter}) // Configure the OTLP exporter to send data to your OpenTelemetry backend const config = { url: 'https://otel.highlight.io:4317' } const sdk = new NodeSDK({ autoDetectResources: true, resourceDetectors: [processDetectorSync], resource: new Resource({ [SEMRESOURCENAME.SERVICE_NAME]: 'nextjs-app', 'highlight.project_id': '<YOUR_PROJECT_ID>', }), spanProcessors: [spanProcessor], logRecordProcessors: [logProcessor], metricReader: metricReader, traceExporter: exporter, contextManager: new AsyncLocalStorageContextManager(), sampler: new AlwaysOnSampler(), instrumentations: [new HttpInstrumentation(), new FetchInstrumentation()], }) sdk.start(); Now, let's use the OpenTelemetry SDK in our route to emit data: import {NextResponse} from "next/server"; import api, {propagation} from "@opentelemetry/api"; import {logs, SeverityNumber} from "@opentelemetry/api-logs"; const tracerProvider = api.trace.getTracerProvider(); const tracer = tracerProvider.getTracer("data"); const loggerProvider = logs.getLoggerProvider(); const logger = provider.getLogger("data"); const meterProvider = api.metrics.getMeterProvider(); const meter = meterProvider.getMeter("data"); // This is an example implementation of a route that fetches data from a Python service export async function GET() { const {email, name} = req.query; console.log("Fetching data...", {email}); const headers = { "Content-Type": "application/json", }; propagation.inject(api.context.active(), headers); const response = await fetch( `https://api.sampleapis.com/coffee/hot`, { method: "POST", headers, body: JSON.stringify({ email, }), }, ); if (!response.ok) { throw new Error("Failed to fetch data"); } const data = await response.json(); // create a span for data processing that may be complex const processed = await tracer.startActiveSpan( "data.process", { attributes: { "user.email": email || undefined, "user.name": name || undefined, }, }, async () => { // do something that may be slow data.map((d) => ({ ...d, calculated: d.value ?? 0 * 1.23 })) }); // report the data as a metric const gauge = meter.createObservableGauge("data.metric"); for (const d of processed) { gauge.addCallback((m) => { m.observe(d.attribute); }); } // emit a custom log logger.emit({ severityNumber: SeverityNumber.INFO, severityText: "INFO", body: "returning data", attributes: {processed}, }); return NextResponse.json(processed); } In this full handler example, you can see how to emit a trace, log, and metric using the native OpenTelemetry constructs. It's evident that the API is quite verbose and not simple to work with. For the highlight platform, we've created a Node.js SDK that wraps OpenTelemetry to simplify the API streamline data reporting, with simple APIs. For example, here's the same handler using our SDK: import { H } from '@highlight-run/node'; // the Highlight SDK instrumentation can happen in each route // or globally for the whole application in your `instrumentation.ts` file H.init('YOUR_PROJECT_ID', { // ... options to configure the SDK }); // This is an example implementation of a route that fetches data from a Python service export async function GET() { const {email, name} = req.query; console.log("Fetching data...", {email}); const response = await fetch( `https://api.sampleapis.com/coffee/hot`, { method: "POST", headers: {"Content-Type": "application/json"}, body: JSON.stringify({ email, }), }, ); if (!response.ok) { throw new Error("Failed to fetch data"); } const data = await response.json(); // create a span for data processing that may be complex const processed = await H.startActiveSpan( "data.process", async (span) => { span.setAttributes({ "user.email": email || undefined, "user.name": name || undefined, }); // do something that may be slow data.map((d) => ({ ...d, calculated: d.value ?? 0 * 1.23 })) }); // report the data as a metric for (const d of data) { H.recordMetric('data.metric', d.attribute); } // emit a custom log H.log('returning data', {data}); return NextResponse.json(data); } Conclusion With the full suite of instrumentation configured, you'll start to see valuable data in your Highlight dashboard. This data empowers you to enhance your troubleshooting workflows significantly. By visualizing response times, error rates, and detailed error reports, you can quickly identify performance bottlenecks and areas for improvement. For instance, if you notice a spike in response times for a specific API endpoint, you can drill down into the traces to see what might be causing the delay. Additionally, the error rate metrics allow you to monitor the health of your application in real-time. If an increase in errors is detected, you can leverage the detailed error reports to understand the context and root cause, enabling you to address issues proactively. Overall, integrating OpenTelemetry with Highlight not only provides you with observability but also equips you with the insights needed to optimize your application and enhance user experience. Start leveraging this powerful combination today to take your monitoring and troubleshooting capabilities to the next level! You can see the traces, logs, and metrics in the dashboard and use them to troubleshoot issues and optimize your application. Comments ( 0 ) Name Email Your Message New Comment Other articles you may like Nov 13, 2025 • 11 min. read Migrating from Highlight.io to LaunchDarkly Observability Company Product Updates Oct 25, 2022 • 7 min. read The Debugging Process and Techniques for Web Applications (Part 2/2) Frontend Observability Developer Experience Aug 24, 2022 • 18 min. read The beauty of contact-first API design Engineering Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:49:23 |
https://dev.to/colocodes/react-class-components-vs-function-components-23m6#Rendering2 | React: class components vs function components - 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 Damian Demasi Posted on Dec 1, 2021 React: class components vs function components # webdev # javascript # beginners # react When I first started working with React, I mostly used function components, especially because I read that class components were old and outdated. But when I started working with React professionally I realised I was wrong. Class components are very much alive and kicking. So, I decided to write a sort of comparison between class components and function components to have a better understanding of their similarities and differences. Table Of Contents Class components Rendering State A common pitfall Props Lifecycle methods Function components Rendering State Props Conclusion Class components This is how a class component that makes use of state , props and render looks like: class Hello extends React . Component { constructor ( props ) { super ( props ); this . state = { name : props . name }; } render () { return < h1 > Hello, { this . state . name } </ h1 >; } } // Render ReactDOM . render ( Hello , document . getElementById ( ' root ' ) ); Enter fullscreen mode Exit fullscreen mode Related sources in which you can find more information about this: https://reactjs.org/docs/components-and-props.html Rendering Let’s say there is a <div> somewhere in your HTML file: <div id= "root" ></div> Enter fullscreen mode Exit fullscreen mode We can render an element in the place of the div with root id like this: const element = < h1 > Hello, world </ h1 >; ReactDOM . render ( element , document . getElementById ( ' root ' )); Enter fullscreen mode Exit fullscreen mode Regarding React components, we will usually be exporting a component and using it in another file: Hello.jsx import React , { Component } from ' react ' ; class Hello extends React . Component { render () { return < h1 > Hello, { this . props . name } </ h1 >; } } export default Hello ; Enter fullscreen mode Exit fullscreen mode main.js import React from ' react ' ; import ReactDOM from ' react-dom ' ; import Hello from ' ./app/Hello.jsx ' ; ReactDOM . render (< Hello />, document . getElementById ( ' root ' )); Enter fullscreen mode Exit fullscreen mode And this is how a class component gets rendered on the web browser. Now, there is a difference between rendering and mounting, and Brad Westfall made a great job summarising it : "Rendering" is any time a function component gets called (or a class-based render method gets called) which returns a set of instructions for creating DOM. "Mounting" is when React "renders" the component for the first time and actually builds the initial DOM from those instructions. State A state is a JavaScript object containing information about the component's current condition. To initialise a class component state we need to use a constructor : class Hello extends React . Component { constructor () { this . state = { endOfMessage : ' ! ' }; } render () { return < h1 > Hello, { this . props . name } { this . state . endOfMessage } </ h1 >; } } Enter fullscreen mode Exit fullscreen mode Related sources about this: https://reactjs.org/docs/rendering-elements.html https://reactjs.org/docs/state-and-lifecycle.html Caution: we shouldn't modify the state directly because it will not trigger a re-render of the component: this . state . comment = ' Hello ' ; // Don't do this Enter fullscreen mode Exit fullscreen mode Instead, we should use the setState() method: this . setState ({ comment : ' Hello ' }); Enter fullscreen mode Exit fullscreen mode If our current state depends from the previous one, and as setState is asynchronous, we should take into account the previous state: this . setState ( function ( prevState , prevProps ) { return { counter : prevState . counter + prevProps . increment }; }); Enter fullscreen mode Exit fullscreen mode Related sources about this: https://reactjs.org/docs/state-and-lifecycle.html A common pitfall If we need to set a state with nested objects , we should spread all the levels of nesting in that object: this . setState ( prevState => ({ ... prevState , someProperty : { ... prevState . someProperty , someOtherProperty : { ... prevState . someProperty . someOtherProperty , anotherProperty : { ... prevState . someProperty . someOtherProperty . anotherProperty , flag : false } } } })) Enter fullscreen mode Exit fullscreen mode This can become cumbersome, so the use of the [immutability-helper](https://github.com/kolodny/immutability-helper) package is recommended. Related sources about this: https://stackoverflow.com/questions/43040721/how-to-update-nested-state-properties-in-react Before I knew better, I believed that setting a new object property will always preserve the ones that were not set, but that is not true for nested objects (which is kind of logical, because I would be overriding an object with another one). That situation happens when I previously spread the object and then modify one of its properties: > b = { item1 : ' a ' , item2 : { subItem1 : ' y ' , subItem2 : ' z ' }} //-> { item1: 'a', item2: {subItem1: 'y', subItem2: 'z'}} > b . item2 = {... b . item2 , subItem1 : ' modified ' } //-> { subItem1: 'modified', subItem2: 'z' } > b //-> { item1: 'a', item2: { subItem1: 'modified', subItem2: 'z' } } > b . item2 = { subItem1 : ' modified ' } // Not OK //-> { subItem1: 'modified' } > b //-> { item1: 'a', item2: { subItem1: 'modified' } } Enter fullscreen mode Exit fullscreen mode But when we have nested objects we need to use multiple nested spreads, which turns the code repetitive. That's where the immutability-helper comes to help. You can find more information about this here . Props If we want to access props in the constructor , we need to call the parent class constructor by using super(props) : class Button extends React . Component { constructor ( props ) { super ( props ); console . log ( props ); console . log ( this . props ); } // ... } Enter fullscreen mode Exit fullscreen mode Related sources about this: https://overreacted.io/why-do-we-write-super-props/ Bear in mind that using props to set an initial state is an anti-pattern of React. In the past, we could have used the componentWillReceiveProps method to do so, but now it's deprecated . class Hello extends React . Component { constructor ( props ) { super ( props ); this . state = { property : this . props . name , // Not recommended, but OK if it's just used as seed data. }; } render () { return < h1 > Hello, { this . props . name } </ h1 >; } } Enter fullscreen mode Exit fullscreen mode Using props to initialise a state is not an anti-patter if we make it clear that the prop is only used as seed data for the component's internally-controlled state. Related sources about this: https://sentry.io/answers/using-props-to-initialize-state/ https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops https://medium.com/@justintulk/react-anti-patterns-props-in-initial-state-28687846cc2e Lifecycle methods Class components don't have hooks ; they have lifecycle methods instead. render() componentDidMount() componentDidUpdate() componentWillUnmount() shouldComponentUpdate() static getDerivedStateFromProps() getSnapshotBeforeUpdate() You can learn more about lifecycle methods here: https://programmingwithmosh.com/javascript/react-lifecycle-methods/ https://reactjs.org/docs/state-and-lifecycle.html Function components This is how a function component makes use of props , state and render : function Welcome ( props ) { const [ timeOfDay , setTimeOfDay ] = useState ( ' morning ' ); return < h1 > Hello, { props . name } , good { timeOfDay } </ h1 >; } // or const Welcome = ( props ) => { const [ timeOfDay , setTimeOfDay ] = useState ( ' morning ' ); return < h1 > Hello, { props . name } , good { timeOfDay } </ h1 >; } // Render const element = < Welcome name = "Sara" />; ReactDOM . render ( element , document . getElementById ( ' root ' ) ); Enter fullscreen mode Exit fullscreen mode Rendering Rendering a function component is achieved the same way as with class components: function Welcome ( props ) { return < h1 > Hello, { props . name } </ h1 >; } const element = < Welcome name = "Sara" />; ReactDOM . render ( element , document . getElementById ( ' root ' ) ); Enter fullscreen mode Exit fullscreen mode Source: https://reactjs.org/docs/components-and-props.html State When it comes to the state, function components differ quite a bit from class components. We need to define an array that will have two main elements: the value of the state, and the function to update said state. We then need to assign the useState hook to that array, initialising the state in the process: import React , { useState } from ' react ' ; function Example () { // Declare a new state variable, which we'll call "count" const [ count , setCount ] = useState ( 0 ); return ( < div > < p > You clicked { count } times </ p > < button onClick = { () => setCount ( count + 1 ) } > Click me </ button > </ div > ); } Enter fullscreen mode Exit fullscreen mode The useState hook is the way function components allow us to use a component's state in a similar manner as this.state is used in class components. Remember: function components use hooks . According to the official documentation: What is a Hook? A Hook is a special function that lets you “hook into” React features. For example, useState is a Hook that lets you add React state to function components. We’ll learn other Hooks later. When would I use a Hook? If you write a function component and realize you need to add some state to it, previously you had to convert it to a class. Now you can use a Hook inside the existing function component. To read the state of the function component we can use the variable we defined when using useState in the function declaration ( count in our example). < p > You clicked { count } times </ p > Enter fullscreen mode Exit fullscreen mode In class components, we had to do something like this: < p > You clicked { this . state . count } times </ p > Enter fullscreen mode Exit fullscreen mode Every time we need to update the state, we should call the function we defined ( setCount in this case) with the values of the new state. < button onClick = { () => setCount ( count + 1 ) } > Click me </ button > Enter fullscreen mode Exit fullscreen mode Meanwhile, in class components we used the this keyword followed by the state and the property to be updated: < button onClick = { () => this . setState ({ count : this . state . count + 1 }) } > Click me </ button > Enter fullscreen mode Exit fullscreen mode Sources: https://reactjs.org/docs/hooks-state.html Props Finally, using props in function components is pretty straight forward: we just pass them as the component argument: function Avatar ( props ) { return ( < img className = "Avatar" src = { props . user . avatarUrl } alt = { props . user . name } /> ); } Enter fullscreen mode Exit fullscreen mode Source: https://reactjs.org/docs/components-and-props.html Conclusion Deciding whether to use class components or function components will depend on the situation. As far as I know, professional environments use class components for "main" components, and function components for smaller, particular components. Although this may not be the case depending on your project. I would love to see examples of the use of class and function components in specific situations, so don't be shy of sharing them in the comments section. 🗞️ NEWSLETTER - If you want to hear about my latest articles and interesting software development content, subscribe to my newsletter . 🐦 TWITTER - Follow me on Twitter . Top comments (33) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Brad Westfall Brad Westfall Brad Westfall Follow Teaching @ReactTraining Work Instructor at ReactTraining.com Joined Jun 4, 2021 • Dec 2 '21 Dropdown menu Copy link Hide The issue with class based components and the driving reason why the React team went towards functional components was for better abstractions. In 2013 when React came out, there was a feature called mixins (this is before JavaScript classes were possible). Mixins were a way to share code between components but fostered a lot of problems and anti-patterns. In 2015 JS got classes and 2016 React moved towards real class-based components. Everyone was excited that mixins were gone but we also lost a primitive way to share code in React. Without React offering a way to share code, the community turned towards patterns instead. With classes, if you want to share reusable code between two components, you only really have two pattern choices - higher order components (HoC's) or the "render props" pattern. HoC has several known problems. In other words, I could give you a "try to abstract this" task with classes and you just wouldn't be able to do it with HoC, it had pretty bad limitations. The render props patter was popularized later and it actually fixed all four known issues with HoC's, so a lot of react devs became a fan of this new pattern, but it had new new problems that HoC's never had. I wrote a detailed piece on this a while back gist.github.com/bradwestfall/4fa68... The reason why hooks were created was to bring functional components up to speed with class based components as far as capability (as you mentioned above) but the end goal of that was custom hooks. With a custom hook we get functional composition capabilities and this solves all six issues of Hoc and Render Props problems, although there are still some good reasons to use render props in certain situations (checkout Formik). If you want, checkout Ryan's keynote at the conference where they announced hooks youtube.com/watch?v=wXLf18DsV-I Also, the reason why classes are still around is just because the React team knew it would be a while for companies to migrate their big code bases from classes to hooks so they kept both ways around. Hope it helps someone Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 3 '21 Dropdown menu Copy link Hide Wow, thanks so much @bradwestfall ! This is a very interesting back-story on classes and function components. I really appreciate the time you took to explain all of this. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Brad Westfall Brad Westfall Brad Westfall Follow Teaching @ReactTraining Work Instructor at ReactTraining.com Joined Jun 4, 2021 • Dec 3 '21 Dropdown menu Copy link Hide No problem, your article does a nice job comparing strictly from a syntax standpoint, there's just the whole code abstraction part to consider. Honestly, after teaching hooks now for 3 years, I know that hooks syntax can be harder to grasp than the class syntax, but I also know that most developers are willing to take on the more difficult hooks syntax for the tradeoff of having much better abstraction options, that's really the main idea. For real though, checkout Ryan's conference talk, it's fantastic Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Eugene Eugene Eugene Follow Pronouns He/him Joined Oct 29, 2021 • Feb 8 '22 Dropdown menu Copy link Hide Some people told, the argument to use class components - error boundaries, which don't have function implementation yet. (It's not my opinion, I just recently started to learn react and seeking for useful information here and there) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anass Boutaline Anass Boutaline Anass Boutaline Follow Full-stack Web Developer, Software engineer Location Morocco Work Full-stack Web Developer Joined Jun 1, 2019 • Dec 2 '21 Dropdown menu Copy link Hide This is a hot topic bro, nice done, otherwise i guess that functional components are cleaner and easy to maintain, so whatever the size of your app, we always look for better and maintainable code, so FC are better than classes any way (React point of view only) Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand tanth1993 tanth1993 tanth1993 Follow Joined Jan 5, 2020 • Dec 3 '21 Dropdown menu Copy link Hide the only thing I like Class Component is that there is a callback in setState . I usually use it when after set loading for the page :) Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Gil Fewster Gil Fewster Gil Fewster Follow Web developer, tinkerer, take-aparterer (and, sometimes, put-back-togetherer) Location Melbourne, Australia Work Front End Developer at Art Processors Joined Jul 23, 2019 • Dec 3 '21 • Edited on Dec 3 • Edited Dropdown menu Copy link Hide The equivalent in functional components is the useEffect hook, which can be setup to run a function when one or more specific dependencies change. There is also a hook called useReducer which gives you the ability to perform complex actions and logic when dependencies change. Very useful for deriving properties from complex state. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 6 '21 Dropdown menu Copy link Hide Spot on! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Omar Pervez Omar Pervez Omar Pervez Follow I'm Web Designer, and I am very passionate and dedicated to my work. With 4 years experience as a professional Web Developer, Location Noakhali, Bangladesh. Education Noakhali Science and Technology University Work Front-end Web Developer at PPH Joined Dec 2, 2021 • Dec 2 '21 • Edited on Dec 2 • Edited Dropdown menu Copy link Hide I am new dev in react. I am learning class component. Is that okay for me? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 2 '21 Dropdown menu Copy link Hide When I started learning React, I saw function components first, and then class components. But I think a better approach will be learning class components first, so then, when you learn function components, you will see why they exists and the advantages they have over the class components. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Monday David S. Monday David S. Monday David S. Follow Email davidsarka242@gmail.com Joined Mar 7, 2021 • Dec 4 '21 Dropdown menu Copy link Hide Totally agree with you Like comment: Like comment: 3 likes Like Thread Thread Omar Pervez Omar Pervez Omar Pervez Follow I'm Web Designer, and I am very passionate and dedicated to my work. With 4 years experience as a professional Web Developer, Location Noakhali, Bangladesh. Education Noakhali Science and Technology University Work Front-end Web Developer at PPH Joined Dec 2, 2021 • Dec 5 '21 Dropdown menu Copy link Hide We need to learn first Class component and then Functional Component Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Omar Pervez Omar Pervez Omar Pervez Follow I'm Web Designer, and I am very passionate and dedicated to my work. With 4 years experience as a professional Web Developer, Location Noakhali, Bangladesh. Education Noakhali Science and Technology University Work Front-end Web Developer at PPH Joined Dec 2, 2021 • Dec 3 '21 Dropdown menu Copy link Hide Yes, I think you are right. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Jeysson Guevara Jeysson Guevara Jeysson Guevara Follow Joined Jul 24, 2021 • Dec 3 '21 Dropdown menu Copy link Hide You'll need to learn both anyways, it is quite frequent to find projects that mix the two methodologies. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Omar Pervez Omar Pervez Omar Pervez Follow I'm Web Designer, and I am very passionate and dedicated to my work. With 4 years experience as a professional Web Developer, Location Noakhali, Bangladesh. Education Noakhali Science and Technology University Work Front-end Web Developer at PPH Joined Dec 2, 2021 • Dec 3 '21 Dropdown menu Copy link Hide Thank you Jeysson, I think it will help me lot in my react learning Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Andrew Baisden Andrew Baisden Andrew Baisden Follow Software Developer | Content Creator | AI, Tech, Programming Location London, UK Education Bachelor Degree Computer Science Work Software Developer Joined Feb 11, 2020 • Dec 4 '21 Dropdown menu Copy link Hide Nice comparison I have completely converted to functional components it would be hard to go back to classes now. When I initially started to learn hooks my thoughts were the reverse. It really is that much better though. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 6 '21 Dropdown menu Copy link Hide I now have the dilemma of choosing between class or function components at my workplace... I guess that as I gain more experience I will be able to make better decisions. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 1 '21 Dropdown menu Copy link Hide That is awesome @lukeshiru ! Thanks for sharing your experience. I think that what is actually happening is that the app in which I'm working on is rather old, and function components did not exist back then. Taking into account your experience, do you think that using class components have any benefit over the function components? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand sophiegrafe sophiegrafe sophiegrafe Follow Former Barmaid trained to be fullstack dev last year! Working hard to not be that Jake of all trades, master of none 😅 Education Interface3 Joined Mar 30, 2022 • Mar 30 '22 • Edited on Mar 30 • Edited Dropdown menu Copy link Hide Thank you very much for this, your article and the discussion that follows were a great help to clarify the subject! I will definitely go with FC but take some time to be more comfortable with the class-based approach in case of need. I have a very little observation to make regarding the way you explained useState affectation "to an array" under "State" in FC section. You wrote: "We need to define an array that will have two main elements[...] We then need to assign the useState hook to that array. [...]" When I see brackets, as a beginner, it automatically triggers the "array" reflex, but brackets on the left side of the assignment operator means destructuring assignment, here array destructuring. As I understand this, we don't assign the useState hook to an array, it's the other way around actually, we are unpacking or extracting values from an array and assigning them to variables. useState return an array of 2 values and DA allows us to avoid this kind of extra lines: const useState = useState ( initialValue ); const stateValue = useState [ 0 ]; const setStateValue = useState [ 1 ]; Enter fullscreen mode Exit fullscreen mode reactjs.org/docs/hooks-state.html#... for a more complete review of this syntax: javascript.info/destructuring-assi... I found DA very useful in many situations for arrays, strings and objects. Totally worth mentioning, learning and using! Again thank you! Like comment: Like comment: 1 like Like Comment button Reply Damian Demasi Damian Demasi Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 • Dec 2 '21 Dropdown menu Copy link Hide Great, thanks for your input! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand echoes2099 echoes2099 echoes2099 Follow Joined Jul 10, 2018 • May 30 '22 Dropdown menu Copy link Hide I was under the impression the official stance was that class components were deprecated...as in dont create new code using these. We recently had to ditch a form library that was written with classes. The reason being is because it did not have useEffects that reacted to all changes in state (and I'm not sure if you could write the equivalent useEffect with hooks). So we were seeing bugs where dynamically injected fields could not register themselves. React hooks are OK but i wouldn't go back to a class based approach for new code Like comment: Like comment: 1 like Like Comment button Reply View full discussion (33 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 Damian Demasi Follow Web Developer - I switched careers in my 40s - Writer of web development blog posts - I love to share Notion templates Location Adelaide, Australia Work Web Developer Joined Jun 29, 2020 More from Damian Demasi The Power of Microtools: How AI and "Vibe Coding" Are Changing the Way We Build # ai # vibecoding # webdev # productivity How to Learn Python Faster and Easier with This Notion Template # python # programming # beginners # learning Learning how to code: with our special guest, Ron # webdev # beginners # programming # 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:49:23 |
https://atproto.com/specs/lexicon | Lexicon - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Lexicon Lexicon is a schema definition language used to describe atproto records, HTTP endpoints (XRPC), and event stream messages. It builds on top of the atproto Data Model . The schema language is similar to JSON Schema and OpenAPI , but includes some atproto-specific features and semantics. This specification describes version 1 of the Lexicon definition language. Overview of Types Lexicon Type Data Model Type Category boolean Boolean concrete integer Integer concrete string String concrete bytes Bytes concrete cid-link Link concrete blob Blob concrete array Array container object Object container params sub-type permission sub-type token meta ref meta union meta unknown meta record primary query primary procedure primary subscription primary permission-set primary Lexicon Files Lexicons are JSON files associated with a single NSID. A file contains one or more definitions, each with a distinct short name. A definition with the name main optionally describes the "primary" definition for the entire file. A Lexicon with zero definitions is invalid. A Lexicon JSON file is an object with the following fields: lexicon (integer, required): indicates Lexicon language version. In this version, a fixed value of 1 id (string, required): the NSID of the Lexicon description (string, optional): short overview of the Lexicon, usually one or two sentences defs (map of strings-to-objects, required): set of definitions, each with a distinct name (key) Schema definitions under defs all have a type field to distinguish their type. A file can have at most one definition with one of the "primary" types. Primary types should always have the name main . It is possible for main to describe a non-primary type. Not all types can be directly used as a definition. For example, sub-types, unknown , ref , and union can not be used as named definitions. References to specific definitions within a Lexicon use fragment syntax, like com.example.defs#someView . If a main definition exists, it can be referenced without a fragment, just using the NSID. For references in the $type fields in data objects themselves (eg, records or contents of a union), this is a "must" (use of a #main suffix is invalid). For example, com.example.record not com.example.record#main . Related Lexicons are often grouped together in the NSID hierarchy. As a convention, any definitions used by multiple Lexicons are defined in a dedicated *.defs Lexicon (eg, com.atproto.server.defs ) within the group. A *.defs Lexicon should generally not include a definition named main , though it is not strictly invalid to do so. Primary Type Definitions The primary types are: query : describes an XRPC Query (HTTP GET) procedure : describes an XRPC Procedure (HTTP POST) subscription : Event Stream (WebSocket) record : describes an object that can be stored in a repository record permission-set : describes a bundle of auth permissions All of the primary definition types include these fields: type (string, required): the type value (eg, record for records) description (string, optional): short, usually only a sentence or two Record Specifies schema of data objects stored in Repositories . Type-specific fields: key (string, required): specifies the Record Key type record (object, required): a schema definition with type object , which specifies this type of record Query and Procedure (HTTP API) Specifies an XRPC HTTP API endpoint. Type-specific fields: parameters (object, optional): a schema definition with type params , describing the HTTP query parameters for this endpoint output (object, optional): describes the HTTP response body description (string, optional): short description encoding (string, required): MIME type for body contents. Use application/json for JSON responses. schema (object, optional): schema definition, either an object , a ref , or a union of refs. Used to describe JSON encoded responses, though schema is optional even for JSON responses. input (object, optional, exclusive to procedure ): describes HTTP request body schema, with the same format as the output field errors (array of objects, optional): set of string error codes which might be returned name (string, required): short name for the error type, with no whitespace description (string, optional): short description, one or two sentences Subscription (Event Stream) Specifies an Event Stream endpoint, eg messages on a WebSocket. Type-specific fields: parameters (object, optional): same as Query and Procedure message (object, required): specifies what messages can be description (string, optional): short description schema (object, required): schema definition, which must be a union of refs errors (array of objects, optional): same as Query and Procedure Subscription schemas (referenced by the schema field under message ) must be a union of refs, not an object type. Permission Set Specifies a bundle of permissions for use as OAuth scopes. See Permissions specification for more details. Type-specific fields: title (string, optional): short name for the permission set, which will be displayed to users. Should be limited to a handful of words title:langs (map of strings to strings, optional): internationalized/localized variations of title for display. The map key strings must be valid language codes; see the language lexicon string format detail (string, optional): human-meaningful description of the scope of this permission set, which will be displayed to users. Should be limited to a paragraph or so. detail:langs (map of strings to strings, optional): same as title:langs , but for detail permissions (array of permission definitions, required): the permissions included in this set Field Type Definitions As with the primary definitions, every schema object includes these fields: type (string, required): fixed value for each type description (string, optional): short, usually only a sentence or two boolean Type-specific fields: default (boolean, optional): a default value for this field const (boolean, optional): a fixed (constant) value for this field When included as an HTTP query parameter, should be rendered as true or false (no quotes). integer A signed integer number. Type-specific fields: minimum (integer, optional): minimum acceptable value maximum (integer, optional): maximum acceptable value enum (array of integers, optional): a closed set of allowed values default (integer, optional): a default value for this field const (integer, optional): a fixed (constant) value for this field string Type-specific fields: format (string, optional): string format restriction maxLength (integer, optional): maximum length of value, in UTF-8 bytes minLength (integer, optional): minimum length of value, in UTF-8 bytes maxGraphemes (integer, optional): maximum length of value, counted as Unicode Grapheme Clusters minGraphemes (integer, optional): minimum length of value, counted as Unicode Grapheme Clusters knownValues (array of strings, optional): a set of suggested or common values for this field. Values are not limited to this set (aka, not a closed enum). enum (array of strings, optional): a closed set of allowed values default (string, optional): a default value for this field const (string, optional): a fixed (constant) value for this field Strings are Unicode. For non-Unicode encodings, use bytes instead. The basic minLength / maxLength validation constraints are counted as UTF-8 bytes. Note that Javascript stores strings with UTF-16 by default, and it is necessary to re-encode to count accurately. The minGraphemes / maxGraphemes validation constraints work with Grapheme Clusters, which have a complex technical and linguistic definition, but loosely correspond to "distinct visual characters" like Latin letters, CJK characters, punctuation, digits, or emoji (which might comprise multiple Unicode codepoints and many UTF-8 bytes). format constrains the string format and provides additional semantic context. Refer to the Data Model specification for the available format types and their definitions. const and default are mutually exclusive. bytes Type-specific fields: minLength (integer, optional): minimum size of value, as raw bytes with no encoding maxLength (integer, optional): maximum size of value, as raw bytes with no encoding In the JSON format, these fields are encoded as {"$bytes":<base64-string>} . In the CBOR format, these fields use the native bytes type. cid-link No type-specific fields. See Data Model spec for CID restrictions. array Type-specific fields: items (object, required): describes the schema elements of this array minLength (integer, optional): minimum count of elements in array maxLength (integer, optional): maximum count of elements in array In theory arrays have homogeneous types (meaning every element as the same type). However, with union types this restriction is meaningless, so implementations can not assume that all the elements have the same type. object A generic object schema which can be nested inside other definitions by reference. Type-specific fields: properties (map of strings-to-objects, required): defines the properties (fields) by name, each with their own schema required (array of strings, optional): indicates which properties are required nullable (array of strings, optional): indicates which properties can have null as a value As described in the data model specification, there is a semantic difference in data between omitting a field; including the field with the value null ; and including the field with a "false-y" value ( false , 0 , empty array, etc). blob Type-specific fields: accept (array of strings, optional): list of acceptable MIME types. Each may end in * as a glob pattern (eg, image/* ). Use */* to indicate that any MIME type is accepted. Partial globs ( text/ht* ) or stand-alone wildcard ( * ) are not supported. maxSize (integer, optional): maximum size in bytes params This is a limited-scope type which is only ever used for the parameters field on query , procedure , and subscription primary types. params map to HTTP query parameters. They can not appear in other contexts. Type-specific fields: required (array of strings, optional): same semantics as field on object properties : similar to properties under object , but can only include the types boolean , integer , string ; or an array of one of these types Note that unlike object , there is no nullable field on params . params can not be declared as a top-level named type in a schema defs array. This means that they can not be referenced by a ref or union . permission This is a limited-scope type which is only ever used for the permissions field of the permission-set primary type, and should not appear in other schema contexts. They map to auth permissions . Type-specific fields: resource (string, required): indicates the resource type which access is being granted to Additional permission fields depend on the resource type being declared. The set of resources and fields may expand over time, but currently includes: repo : public repository write permissions collection (array of unique strings, required): indicates record types. Must include at least one element (not empty array). Does not support wildcard ( * ) in Lexicon schema context. action (array of unique strings, optional): limits set of record operations. Values must be one or create , update , delete , case-sensitive. rpc : remote API calls via proxying or service token generation lxm (array of strings, required): allowed XRPC endpoints, as NSIDs. Must include at least one element (not empty array). Wildcard ( * ) is not supported in Lexicon schema context. aud (string, semi-required): remote service ("audience"). In the context of permission sets, can not have fixed DID service references. Supports wildcard ( * ), though aud and lxm can not both be wildcard. Required unless inheritAud is true. Effectively must be either wildcard, or undefined with inheritAud set to true. inheritAud (boolean, optional): if true, aud does not need to be defined. Note that the blob , account , and identity resources types are not supported in Lexicon schema context, and should be ignored if included. Permission declarations with unsupported resource types or parameters (fields) must be ignored by services implementing access control. This is because the set of permissions is expected to evolve over time, and additional fields might attenuate the permission granted. It is unsafe to ignore unknown fields when parsing permissions for access control. See Permission specification for more details. Note that it is possible to construct a valid lexicon permission type which is invalid or has undefined behavior as an auth permission. token Tokens are empty data values which exist only to be referenced by name. They are used to define a set of values with specific meanings. The description field should clarify the meaning of the token. They have no type-specific fields. Tokens do not themselves have a data representation. They can only be declared as named definitions. For example, they can not be referenced via ref or union , or included as a field in an object . One place token references might appear in other Lexicon definitions is as strings in the knownValues or enum fields of a string definition. Tokens should always be fully-qualified references (an NSID followed by an optional fragment), not local references within a schema file.. Tokens are similar to the concept of a "symbol" in some programming languages, distinct from strings, variables, built-in keywords, or other identifiers. For example, tokens could be defined to represent the state of an entity (in a state machine), or to enumerate a list of categories. ref Type-specific fields: ref (string, required): reference to another schema definition Refs are a mechanism for re-using a schema definition in multiple places. The intended use is to reduce duplication of definitions for types like object or a string with specific restrictions. The ref string can be a global reference to a Lexicon type definition (an NSID, optionally with a # -delimited name indicating a definition other than main ), or can indicate a local definition within the same Lexicon file (a # followed by a name). When a ref points to an object type, the type of the encoded data is unambiguous. This means that the $type field should not be included in encoded data as a discriminator. This does not apply to references to record types, which always include the $type discriminator. A ref can not point to a token type. Refs can not be declared as top-level named types in a schema defs array. This means that a ref can not point to another ref , nor a union . They can reference container types that contain nested ref types, for example an object . union Type-specific fields: refs (array of strings, required): references to schema definitions closed (boolean, optional): indicates if a union is "open" or "closed". defaults to false (open union) Unions represent that multiple possible types could be present at this location in the schema. The references follow the same syntax as ref , allowing references to both global or local schema definitions. Actual data will validate against a single specific type: the union does not combine fields from multiple schemas, or define a new hybrid data type. The different types are referred to as variants . By default unions are "open", meaning that future revisions of the schema could add more types to the list of refs (though can not remove types). This means that implementations should be permissive when validating, in case they do not have the most recent version of the Lexicon. The closed flag (boolean) can indicate that the set of types is fixed and can not be extended in the future. A union schema definition with no refs is allowed and similar to unknown , as long as the closed flag is false (the default). The main difference is that the data is required to include the $type field. A closed union with only a single type referenced is similar to ref . The main difference is that the data is required to include the $type field. An empty closed union (a union with an empty refs list and the closed flag set to true) is an invalid schema. The schema definitions pointed to by a union must have type object or record . All the variants must be represented by a CBOR map (or JSON Object) and must include a $type field indicating the variant type. A union can not point to types query , procedure , subscription , unknown , blob , cid-link , array , params , token , ref , union , or any other currently defined types. Unions can not be declared as top-level named types in a schema file defs map. This means that a union can not reference another union , nor a ref . unknown An unknown type indicates that any data object could appear at this location, with no specific validation. The top-level data must be an object (not a string, boolean, etc). unknown definitions have no type-specific fields. As with all other data types, the value null is not allowed unless the field is specifically marked as nullable . The data object may contain a $type field indicating the schema of the data, but it is not required. The top-level data object must not have the structure of a compound data type, like blob ( $type: blob ) or CID link ( $link ). The (nested) contents of the data object must still be valid under the atproto data model. For example, it should not contain floats. Nested compound types like blobs and CID links should be validated and transformed as expected. Lexicon designers are strongly recommended to not use unknown fields in record objects for now. unknown types can not be declared as top-level named types in a schema defs array. String Formats Strings can optionally be constrained to one of the following format types: at-identifier : either a Handle or a DID , details described below at-uri : AT-URI cid : CID in string format, details specified in Data Model datetime : timestamp, details specified below did : generic DID Identifier handle : Handle Identifier nsid : Namespaced Identifier tid : Timestamp Identifier (TID) record-key : Record Key , matching the general syntax ("any") uri : generic URI, details specified below language : language code, details specified below For the various identifier formats, when doing Lexicon schema validation the most expansive identifier syntax format should be permitted. Problems with identifiers which do pass basic syntax validation should be reported as application errors, not lexicon data validation errors. For example, data with any kind of DID in a did format string field should pass Lexicon validation, with unsupported DID methods being raised separately as an application error. at-identifier A string type which is either a DID (type: did) or a handle (handle). Mostly used in XRPC query parameters. It is unambiguous whether an at-identifier is a handle or a DID because a DID always starts with did:, and the colon character (:) is not allowed in handles. datetime Full-precision date and time, with timezone information. This format is intended for use with computer-generated timestamps in the modern computing era (eg, after the UNIX epoch). If you need to represent historical or ancient events, ambiguity, or far-future times, a different format is probably more appropriate. Datetimes before year zero (in astonomical time) are specifically disallowed. Datetime format standards are notoriously flexible and overlapping. Datetime strings in atproto should meet the intersecting requirements of the RFC 3339 , ISO 8601 , and WHATWG HTML datetime standards. The character separating "date" and "time" parts must be an upper-case T . Timezone specification is required. It is strongly preferred to use the UTC timezone, and to represent the timezone with a simple capital Z suffix (lower-case is not allowed). While hour/minute suffix syntax (like +01:00 or -10:30 ) is supported, "negative zero" ( -00:00 ) is specifically disallowed (by ISO 8601). Whole seconds precision is required, and arbitrary fractional precision digits are allowed. Best practice is to use at least millisecond precision, and to pad with zeros to the generated precision (eg, trailing :12.340Z instead of :12.34Z ). Not all datetime formatting libraries support trailing zero formatting. Both millisecond and microsecond precision have reasonable cross-language support; nanosecond precision does not. Implementations should be aware when round-tripping records containing datetimes of two ambiguities: loss-of-precision, and ambiguity with trailing fractional second zeros. If de-serializing Lexicon records into native types, and then re-serializing, the string representation may not be the same, which could result in broken hash references, sanity check failures, or repository update churn. A safer thing to do is to deserialize the datetime as a simple string, which ensures round-trip re-serialization. Implementations "should" validate that the semantics of the datetime are valid. For example, a month or day 00 is invalid. Valid examples: # preferred 1985-04-12T23:20:50.123Z 1985-04-12T23:20:50.123456Z 1985-04-12T23:20:50.120Z 1985-04-12T23:20:50.120000Z 0001-01-01T00:00:00.000Z 0000-01-01T00:00:00.000Z # supported 1985-04-12T23:20:50.12345678912345Z 1985-04-12T23:20:50Z 1985-04-12T23:20:50.0Z 1985-04-12T23:20:50.123+00:00 1985-04-12T23:20:50.123-07:00 Copy Copied! Invalid examples: 1985-04-12 1985-04-12T23:20Z 1985-04-12T23:20:5Z 1985-04-12T23:20:50.123 +001985-04-12T23:20:50.123Z 23:20:50.123Z -1985-04-12T23:20:50.123Z 1985-4-12T23:20:50.123Z 01985-04-12T23:20:50.123Z 1985-04-12T23:20:50.123+00 1985-04-12T23:20:50.123+0000 # ISO-8601 strict capitalization 1985-04-12t23:20:50.123Z 1985-04-12T23:20:50.123z # RFC-3339, but not ISO-8601 1985-04-12T23:20:50.123-00:00 1985-04-12 23:20:50.123Z # timezone is required 1985-04-12T23:20:50.123 # syntax looks ok, but datetime is not valid 1985-04-12T23:99:50.123Z 1985-00-12T23:20:50.123Z # ISO-8601, but normalizes to a negative time 0000-01-01T00:00:00+01:00 Copy Copied! uri Flexible to any URI schema, following the generic RFC-3986 on URIs. This includes, but isn’t limited to: did , https , wss , ipfs (for CIDs), dns , and of course at . Maximum length in Lexicons is 8 KBytes. language An IETF Language Tag string, compliant with BCP 47 , defined in RFC 5646 ("Tags for Identifying Languages"). This is the same standard used to identify languages in HTTP, HTML, and other web standards. The Lexicon string must validate as a "well-formed" language tag, as defined in the RFC. Clients should ignore language strings which are "well-formed" but not "valid" according to the RFC. As specified in the RFC, ISO 639 two-character and three-character language codes can be used on their own, lower-cased, such as ja (Japanese) or ban (Balinese). Regional sub-tags can be added, like pt-BR (Brazilian Portuguese). Additional subtags can also be added, such as hy-Latn-IT-arevela . Language codes generally need to be parsed, normalized, and matched semantically, not simply string-compared. For example, a search engine might simplify language tags to ISO 639 codes for indexing and filtering, while a client application (user agent) would retain the full language code for presentation (text rendering) locally. When to use $type Data objects sometimes include a $type field which indicates their Lexicon type. The general principle is that this field needs to be included any time there could be ambiguity about the content type when validating data. The specific rules are: record objects must always include $type . While the type is often known from context (eg, the collection part of the path for records stored in a repository), record objects can also be passed around outside of repositories and need to be self-describing union variants must always include $type , except at the top level of subscription messages Note that blob objects always include $type , which allows generic processing. As a reminder, main types must be referenced in $type fields as just the NSID, not including a #main suffix. Validation Options A PDS has three Lexicon validation options when creating or updating records: Explicit validation required: the record must be validated against a Lexicon schema. If the PDS does not know of the Lexicon, and/or can not resolve it on demand, the record creation fails. Explicit no validation: the record is not validated against any Lexicon, even if the PDS knows the Lexicon locally. The record still has to pass data validation rules (eg, no malformed blob objects at any nested depth). Optimistic validation (default if no explicit argument): if the PDS knows the record Lexicon, it validates. If the PDS does not know it, and can't resolve it (or does not do live validation), the record is allowed to be created. This is also referred to as "Fail-Open". In Go, this is implemented by setting Validate to true or false on the CreateRecord or UpdateRecord options struct, or leaving it unset ( nil ) for optimistic validation. In Typescript, this is implemented by setting validate to true or false on the createRecord or updateRecord options object, or leaving it unset ( undefined ) for optimistic validation. A flag in the success response from the PDS will indicate whether Lexicon validation happened. Lexicon Evolution Lexicons are allowed to change over time, within some bounds to ensure both forwards and backwards compatibility. The basic principle is that all old data must still be valid under the updated Lexicon, and new data must be valid under the old Lexicon. Any new fields must be optional Non-optional fields can not be removed. A best practice is to retain all fields in the Lexicon and mark them as deprecated if they are no longer used. Types can not change Fields can not be renamed If larger breaking changes are necessary, a new Lexicon name must be used. It can be ambiguous when a Lexicon has been published and becomes "set in stone". At a minimum, public adoption and implementation by a third party, even without explicit permission, indicates that the Lexicon has been released and should not break compatibility. A best practice is to clearly indicate in the Lexicon type name any experimental or development status. Eg, com.corp.experimental.newRecord . Authority and Control The authority for a Lexicon is determined by the NSID, and rooted in DNS control of the domain authority. That authority has ultimate control over the Lexicon definition, and responsibility for maintenance and distribution of Lexicon schema definitions. In a crisis, such as unintentional loss of DNS control to a bad actor, the protocol ecosystem could decide to disregard this chain of authority. This should only be done in exceptional circumstances, and not as a mechanism to subvert an active authority. The primary mechanism for resolving protocol disputes is to fork Lexicons in to a new namespace. Protocol implementations should generally consider data which fails to validate against the Lexicon to be entirely invalid, and should not try to repair or do partial processing on the individual piece of data. Unexpected fields in data which otherwise conforms to the Lexicon should be ignored. When doing schema validation, they should be treated at worst as warnings. This is necessary to allow evolution of the schema by the controlling authority, and to be robust in the case of out-of-date Lexicons. Third parties can technically insert any additional fields they want into data. This is not the recommended way to extend applications, but it is not specifically disallowed. One danger with this is that the Lexicon may be updated to include fields with the same field names but different types, which would make existing data invalid. Lexicon Publication and Resolution Lexicon schemas are published publicly as records in atproto repositories, using the com.atproto.lexicon.schema type. The domain name authority for NSIDs to specific atproto repositories (identified by DID is linked by a DNS TXT record ( _lexicon ), similar to but distinct from the handle resolution system. The com.atproto.lexicon.schema Lexicon itself is very minimal: it only requires the lexicon integer field, which must be 1 for this version of the Lexicon language. In practice, same fields as Lexicon Files should be included, along with $type . The record key is the NSID of the schema. A summary of record fields: $type : must be com.atproto.lexicon.schema (as with all atproto records) lexicon : integer, indicates the overall version of the Lexicon (currently 1 ) id : the NSID of this Lexicon. Must be a simple NSID (no fragment), and must match the record key defs : the schema definitions themselves, as a map-of-objects. Names should not include a # prefix. description : optional description of the overall schema; though descriptions are best included on individual defs, not the overall schema. The com.atproto.lexicon.schema meta-schema is somewhat unlike other Lexicons, in that it is defined and governed as part of the protocol. Future versions of the language and protocol might not follow the evolution rules. It is an intentional decision to not express the Lexicon schema language itself recursively, using the schema language. Authority for NSID namespaces is done at the "group" level, meaning that all NSIDs which differ only by the final "name" part are all published in the same repository. Lexicon resolution of NSIDs is not hierarchical: DNS TXT records must be created for each authority section, and resolvers should not recurse up or down the DNS hierarchy looking for TXT records. As an example, the NSID edu.university.dept.lab.blogging.getBlogPost has a "name" getBlogPost . Removing the name and reversing the rest of the NSID gives an "authority domain name" of blogging.lab.dept.university.edu . To link the authority to a specific DID (say did:plc:ewvi7nxzyoun6zhxrhs64oiz ), a DNS TXT record with the name _lexicon.blogging.lab.dept.university.edu and value did=did:plc:ewvi7nxzyoun6zhxrhs64oiz (note the did= prefix) would be created. Then a record with collection com.atproto.lexicon.schema and record-key edu.university.dept.lab.blogging.getBlogPost would be created in that account's repository. A resolving service would start with the NSID ( edu.university.dept.lab.blogging.getBlogPost ) and do a DNS TXT resolution for _lexicon.blogging.lab.dept.university.edu . Finding the DID, it would proceed with atproto DID resolution, look for a PDS, and then fetch the relevant record. The overall AT-URI for the record would be at://did:plc:ewvi7nxzyoun6zhxrhs64oiz/com.atproto.lexicon.schema/edu.university.dept.lab.blogging.getBlogPost . If the DNS TXT resolution for _lexicon.blogging.lab.dept.university.edu failed, the resolving service would NOT try _lexicon.lab.dept.university.edu or _lexicon.getBlogPost.blogging.lab.dept.university.edu or _lexicon.university.edu , or any other domain name. The Lexicon resolution would simply fail. If another NSID edu.university.dept.lab.blogging.getBlogComments was created, it would have the same authority name, and must be published in the same atproto repository (with a different record key). If a Lexicon for edu.university.dept.lab.gallery.photo was published, a new DNS TXT record would be required ( _lexicon.gallery.lab.dept.university.edu ; it could point at the same repository (DID), or a different repository. As a simpler example, an NSID app.toy.record would resolve via _lexicon.toy.app . A single repository can host Lexicons for multiple authority domains, possibly across multiple registered domains and TLDs. Resolution DNS records can change over time, moving schema resolution to different repositories, though it may take time for DNS and cache changes to propagate. Note that Lexicon record operations are broadcast over repository event streams ("firehose"), but that DNS resolution changes do not (unlike handle changes). Resolving services should not cache DNS resolution results for long time periods. Usage and Implementation Guidelines It should be possible to translate Lexicon schemas to JSON Schema or OpenAPI and use tools and libraries from those ecosystems to work with atproto data in JSON format. Implementations which serialize and deserialize data from JSON or CBOR into structures derived from specific Lexicons should be aware of the risk of "clobbering" unexpected fields. For example, if a Lexicon is updated to add a new (optional) field, old implementations would not be aware of that field, and might accidentally strip the data when de-serializing and then re-serializing. Depending on the context, one way to avoid this problem is to retain any "extra" fields, or to pass-through the original data object instead of re-serializing it. Possible Future Changes The validation rules for unexpected additional fields may change. For example, a mechanism for Lexicons to indicate that the schema is "closed" and unexpected fields are not allowed, or a convention around field name prefixes ( x- ) to indicate unofficial extension. Lexicon Style Guide For an in-depth style guide for designing Lexicons, see the Lexicon Style Guide . Previous Data Model Next Cryptography © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://www.youtube.com/new | 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, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/building-a-batch-notification-system-with-mongodb-django-celery-and-sendgrid-for-developers | Building a Batch Notification System with MongoDB, Django, Celery, and SendGrid for Developers Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Engineering Building a Batch Notification System with MongoDB, Django, Celery, and SendGrid for Developers Anjali Arya • July 25, 2024 TABLE OF CONTENTS What are Batch Notifications? Batched notifications group multiple notifications into a single message delivered within a specific time window. Unlike traditional systems where each event triggers a separate notification, batched notifications reduce noise and increase engagement. For example, in a document collaboration app, instead of sending an email for each comment, a batched system sends one email with all comments within a time frame. You can actually build a batched notification mechanism in your collaborative app directly via here How to Batch Notifications for your Social Media/ Collaborative Application? Key Benefits: Reduced Notification Noise : Fewer, more informative notifications. Increased Engagement : Higher likelihood of user interaction. Improved Retention : Happier users due to fewer interruptions. Designing a Batched Notification System There are two main approaches to designing a batched notification system: Batch on Write : Accumulate notifications into batches as events occur. Batch on Read : Periodically batch unsent notifications. The choice between these approaches affects system performance and scalability. Batch on Write In this method, notifications are accumulated as events occur, optimizing lookups. Batch on Read In this method, batches are created periodically by querying unsent notifications. This can be less efficient as data volume grows. Our Approach: Batch on Write Given the scalability benefits, we'll use the batch on write approach, even though it requires more initial effort. Database Design with MongoDB We'll use MongoDB, a flexible NoSQL database, to model our system. The collections will be: notifications : Tracks individual notifications. notification_batches : Tracks batched notifications. notification_batch_notifications : Links individual notifications to batches. MongoDB Schema Copy Code # notifications collection { "_id": ObjectId(), "type": String, "actor_id": ObjectId(), "recipient_id": ObjectId(), "object_id": ObjectId(), "object_type": String, "inserted_at": DateTime } # notification_batches collection { "_id": ObjectId(), "type": String, "recipient_id": ObjectId(), "batch_key": String, "object_id": ObjectId(), "object_type": String, "closes_at": DateTime, "processed_at": DateTime, "inserted_at": DateTime } # notification_batch_notifications collection { "notification_batch_id": ObjectId(), "notification_id": ObjectId(), "inserted_at": DateTime } Batching Notifications with Django We'll use Django for our web framework. Here's how to batch notifications: Generate a batch_key . Create a notification entry. Find or create an open batch. Add the notification to the batch. Django Code Example Copy Code # models.py from django.db import models from bson import ObjectId class Notification(models.Model): _id = models.CharField(max_length=24, primary_key=True, default=lambda: str(ObjectId())) type = models.CharField(max_length=255) actor_id = models.CharField(max_length=24) recipient_id = models.CharField(max_length=24) object_id = models.CharField(max_length=24) object_type = models.CharField(max_length=255) inserted_at = models.DateTimeField(auto_now_add=True) class NotificationBatch(models.Model): _id = models.CharField(max_length=24, primary_key=True, default=lambda: str(ObjectId())) type = models.CharField(max_length=255) recipient_id = models.CharField(max_length=24) batch_key = models.CharField(max_length=255) object_id = models.CharField(max_length=24) object_type = models.CharField(max_length=255) closes_at = models.DateTimeField() processed_at = models.DateTimeField(null=True, blank=True) inserted_at = models.DateTimeField(auto_now_add=True) class NotificationBatchNotification(models.Model): notification_batch_id = models.CharField(max_length=24) notification_id = models.CharField(max_length=24) inserted_at = models.DateTimeField(auto_now_add=True) Adding a Notification to a Batch Copy Code # views.py from datetime import datetime, timedelta from .models import Notification, NotificationBatch, NotificationBatchNotification def add_notification_to_batch(comment, user, document): recipients = get_recipients(document, user) batch_key = f"document:{document.id}:comments" batch_window = timedelta(minutes=5) for recipient in recipients: notification = Notification.objects.create( type="new-comment", actor_id=str(user.id), recipient_id=str(recipient.id), object_id=str(comment.id), object_type="comment" ) batch = NotificationBatch.objects.filter( recipient_id=str(recipient.id), batch_key=batch_key, closes_at__gte=datetime.now() ).first() if not batch: batch = NotificationBatch.objects.create( type="new-comment", recipient_id=str(recipient.id), batch_key=batch_key, object_id=str(document.id), object_type="document", closes_at=datetime.now() + batch_window ) NotificationBatchNotification.objects.create( notification_batch_id=str(batch.id), notification_id=str(notification.id) ) def get_recipients(document, user): # Example function to get document collaborators excluding the comment creator return document.collaborators.exclude(id=user.id) Flushing Closed Batches with Celery We'll use Celery to handle the periodic task of flushing closed batches and sending notifications. Incase you want to read more about how we handle concurrent DB writes using Celery and Redis, you can check How Redis Solved Our Challenges with Dynamic Task Scheduling and Concurrent Execution? [Developer's Guide] Celery Task Example Copy Code # tasks.py from celery import shared_task from datetime import datetime from .models import NotificationBatch from .notifications import send_batch_notification @shared_task def flush_closed_batches(): batches = NotificationBatch.objects.filter( closes_at__lte=datetime.now(), processed_at__isnull=True ) for batch in batches: send_batch_notification(batch) batch.processed_at = datetime.now() batch.save() # notifications.py from django.template.loader import render_to_string from sendgrid import SendGridAPIClient from sendgrid.helpers.mail import Mail def send_batch_notification(batch): notifications = NotificationBatchNotification.objects.filter(notification_batch_id=batch.id) context = {"notifications": notifications, "batch": batch} subject = f"New comments on {batch.object_id}" message = render_to_string("email_template.html", context) recipient = batch.recipient_id send_email(subject, message, recipient) def send_email(subject, message, recipient): sg = SendGridAPIClient('SENDGRID_API_KEY') email = Mail( from_email='no-reply@example.com', to_emails=recipient, subject=subject, html_content=message ) sg.send(email) Generating Notification Messages We use a template to generate the notification message from a batch. Email Template Example Copy Code <!-- email_template.html --> <h1>Comments for {{ "{{ batch.object_id }}" }}</h1> <% for notification in notifications %> <p> <strong>{{ "{{ notification.actor_id }}" }}</strong> said at {{ "{{ notification.inserted_at }}" }}: </p> <blockquote> <p>{{ "{{ notification.object_id }}" }}</p> </blockquote> <% endfor %> Preparing Your Batched Notification Engine for Production Building a robust and scalable batched notification engine involves several key considerations and advanced features to ensure smooth operation and optimal user experience. Here’s how to prepare your system for production: Key Considerations for Production-Ready Batch Notifications Race Conditions: Ensure Atomic Operations: Utilize database transactions and locking mechanisms to avoid creating duplicate batches. In MongoDB, you can use the findAndModify operation to perform atomic updates. Example in Django: Copy Code from django.db import transaction @transaction.atomic def create_batch_if_not_exists(recipient_id, batch_key, batch_window): batch = NotificationBatch.objects.select_for_update().filter( recipient_id=recipient_id, batch_key=batch_key, closes_at__gt=timezone.now() ).first() if not batch: batch = NotificationBatch.objects.create( recipient_id=recipient_id, batch_key=batch_key, closes_at=timezone.now() + timedelta(seconds=batch_window) ) return batch Single Execution: Mark Batches as Processed: Ensure each batch is processed only once by marking it as processed after sending notifications. This can be done by updating the processed_at field. Example in Celery: Copy Code @celery.task def flush_batch(batch_id): batch = NotificationBatch.objects.get(id=batch_id) if batch.processed_at: return send_notification(batch) batch.processed_at = timezone.now() batch.save() Retries: Handle Failures Gracefully: Implement retry logic in Celery to handle temporary failures. Use exponential backoff and logging to manage retries. Example: Copy Code @celery.task(bind=True, max_retries=5) def send_notification(self, batch): try: # Code to send notification except Exception as e: self.retry(exc=e, countdown=2 ** self.request.retries) Advanced Features for Enhanced Batch Notifications Item Count: Track Total Items: Keep a count of the total number of items in each batch to provide more informative notifications, such as “You have 5 new comments.” Example in Django: Copy Code class NotificationBatch(models.Model): recipient = models.ForeignKey(User, on_delete=models.CASCADE) batch_key = models.CharField(max_length=255) closes_at = models.DateTimeField() processed_at = models.DateTimeField(null=True, blank=True) item_count = models.IntegerField(default=0) def add_notification_to_batch(batch, notification): batch.item_count += 1 batch.save() # Add notification to batch Early Flushing: Flush Based on Activity Thresholds: Implement logic to flush batches early when a certain number of notifications is reached, ensuring timely updates for high-activity users. Example: Copy Code def check_and_flush_batch(batch): if batch.item_count >= MAX_ITEMS_PER_BATCH: flush_batch(batch.id) User-Specific Windows: Customizable Batch Windows: Allow users to set their preferred batch window durations, offering flexibility in how frequently they receive notifications. Example in Django: Copy Code class UserProfile(models.Model): user = models.OneToOneField(User, on_delete=models.CASCADE) batch_window = models.IntegerField(default=300) # Default to 5 minutes def get_user_batch_window(user): return user.profile.batch_window Partitioned Cron Jobs: Distribute Tasks for High Volume: For applications with a large number of users, distribute cron jobs to handle the load effectively. This can be achieved by partitioning the data and processing in parallel. Example in Celery: Copy Code @celery.task def flush_batches(): batch_ids = NotificationBatch.objects.filter( closes_at__lte=timezone.now(), processed_at__isnull=True ).values_list('id', flat=True) for batch_id in batch_ids: flush_batch.delay(batch_id) By implementing these considerations and advanced features, you can build a production-ready batched notification system that is both scalable and efficient, leading to better user engagement and satisfaction. Building Batching May Not Seem Complex, Though an Experienced Developer Will Certainly Understand the Overheads in Maintaining it. If you find the tasks described above daunting for your team, you're not alone. That's why we created SuprSend . Here's how we differentiate your notifications building process for batched notifications. Feature/Step Manual Batch Notification System SuprSend Batch Notification Integration Notification Batching Manual configuration required to group notifications. Developers need to write custom code to batch events and send consolidated notifications. Automatically batches multiple triggers into a single output, sending one consolidated notification. Batch Window Management Developers must define and manage the batch window manually, often requiring custom logic to handle fixed and dynamic windows. Offers both fixed and dynamic batch windows. Dynamic windows can be set based on event properties, simplifying per-user customization. Batch Key Management Custom implementation needed to create unique batches for different scenarios. Allows defining unique batches using the batch_key , making it easy to create multiple batches per user. Retain Batch Events Developers must implement logic to limit and manage event data within a batch. Provides built-in functionality to retain a specific number of events, configurable between 2 and 100. Template Integration Manual creation of templates and handling of batched event variables. Simplifies template creation with $batched_events and $batched_event_count variables, providing easy integration with notification content. Database Management Requires developers to design and manage database schemas for notifications and batches, usually involving multiple collections or tables. Abstracts the complexity of database management, providing a streamlined approach to handle batch notifications. Cron Job and Task Scheduling Developers need to configure cron jobs and manage job queues manually, often using tools like Celery. Eliminates the need for manual cron job configuration, handling task scheduling automatically. Error Handling and Retries Custom logic needed for handling race conditions, ensuring atomic operations, and implementing retry mechanisms. Built-in error handling, ensuring atomic operations with tools like findAndModify in MongoDB, and automatic retry logic for failed tasks. Scalability and Performance Requires careful planning and optimization to scale, including partitioned cron jobs for high-volume applications. Designed for scalability, automatically managing high volumes and distributing tasks efficiently. User-Specific Customization Developers must implement custom logic to support user-specific batch windows and preferences. Supports per-user batch windows with dynamic configuration based on event properties, making customization straightforward. Integration and Maintenance High initial effort and ongoing maintenance to ensure system reliability and performance. Lowers integration effort and reduces maintenance overhead, providing a robust solution with minimal setup. Example Use Case: Batching Comments in a Collaboration App Manual Approach: Write custom code to batch comments within a specified time window. Design database schemas and manage entries for notifications and batches. Configure cron jobs to periodically check and send batched notifications. Implement error handling, retries, and ensure atomic operations. SuprSend Approach: Define a batch node within the SuprSend workflow. Set a fixed or dynamic batch window based on event properties. Use built-in batch variables in notification templates. SuprSend handles the batching, database management, scheduling, and error handling automatically. You can rely on SuprSend to orchestrate notifications across various channels, manage user preferences, and centralize your notification templates for team-wide visibility. Practical Demonstration on a Demo Application (Deployed on Github) We built a practical demo application to demonstrate how you can integrate the batching mechanism in your notification without any development. You can read more here: How to Batch Notifications for your Social Media/ Collaborative Application? (suprsend.com) It contains the Github link as well. What are batch notifications on facebook? Batch notifications on Facebook refer to a feature where multiple notifications are grouped or batched together into a single notification event. This grouping helps reduce the number of individual notifications a user receives, especially when there are multiple related activities or updates within a short period. For example, instead of receiving separate notifications for each comment, like, or mention on a post, Facebook may batch these notifications into a single notification to improve user experience and reduce notification overload. Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://twitter.com/SuprSend | 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:49:23 |
https://atproto.com/guides/account-migration | Account Migration - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Account Migration Details This document complements the Account Hosting specification, which gives a high-level overview of account lifecycles. It breaks down the individual migration steps, both for an "easy" migration (when both PDS instances participate), and for account recovery scenarios. Note that these specific mechanisms are not a formal part of the protocol, and may evolve over time. Creating New Account To create a PDS account with an existing identity, it is necessary to prove control the identity. For an active account on another PDS, this is done by generating a service auth token (JWT) signed with the current atproto signing key indicated in the identity DID document. This can be requested from the previous PDS instance using the com.atproto.server.getServiceAuth endpoint (or an equivalent interface/API). For an independently-controlled identity (eg, did:web , or a did:plc with old PDS offline or uncooperative), this may involve updating the identity to include a self-controlled atproto signing key, and generating the service auth token offline. The service auth token is provided along with the existing DID when creating the account with com.atproto.server.createAccount (or an equivalent interface/API) on the new PDS. The new account will be in a deactivated state. It should be possible to directly login and authenticate, but not to participate in the network. From the perspective of other services in the network, the old PDS account is still current, and the new PDS account is not yet active or valid. Functionality like OAuth or proxied requests using service auth will not yet work with the new PDS. Migrating Data Some categories of data that are typically migrated are: public repository public blobs (media files) private preferences At any stage of migration, the authenticated com.atproto.server.checkAccountStatus endpoint can be called on either the old or new PDS instance to check statistics about currently indexed data. A copy of the repository can be fetched as a CAR file from the old PDS using the public com.atproto.sync.getRepo endpoint. If the old PDS is inaccessible, a mirror might be available from a public relay, or a local backup might be available. If not, the new account will still function with the same identity, but old content would be missing. A CAR file can be imported to the new PDS using the authenticated com.atproto.repo.importRepo endpoint. Blobs (media files) are download and re-uploaded one by one. They should not be uploaded to the new PDS until the repository has been imported and fully indexed, so that blobs can be linked to the records that refer to them, and won’t be garbage collected. A full list of relevant blobs (by CID) can be fetched either from the old PDS ( com.atproto.sync.listBlobs ), or the current list of "missing" blobs can be checked on the new PDS ( com.atproto.repo.listMissingBlobs ). If some blobs can not be found, the migration process can continue, and any recovered blobs can be uploaded later (if the blob CIDs match exactly). Private account preferences can be exported from the old PDS using the authenticated like app.bsky.actor.getPreferences endpoint, then imported using app.bsky.actor.putPreferences . These are Bluesky app-specific endpoints, and other apps (Lexicons) may define their own preference APIs. Note that this will only include private state stored in the PDS; some preferences and state may exist in external services (eg, centralized chat/DM implementations). Updating Identity Once content has been migrated, the identity (DID and handle) can be updated to indicate that the new PDS is the current host for the account. "Recommended" DID document parameters can be fetched from the new PDS using the com.atproto.identity.getRecommendedDidCredentials endpoint. This will include the DID service hostname, local handle (as requested during account creation), a PDS-managed atproto signing key (public key), and (if relevant) PLC rotation keys (public keys). For users who are able to securely manage a private cryptographic keypair (eg, store in a password manager or digital wallet), it is recommended to include a self-controlled PLC rotation key (public key) in the PLC operation. For a self-controlled identity (eg, did:web , or did:plc with local rotation key), the identity update can be done directly by the user. For an account with a did:plc managed by the old PDS, a PLC "operation" is signed by the old PDS, then submitted via the new PDS. The motivation for having the new PDS submit the PLC operation instead of having the user do so directly is to give the new PDS a chance to validate the operation and do safety check to prevent the account from getting in a broken state. Because identity operations are sensitive, they require an additional security token as an additional "factor". The token can be requested via com.atproto.identity.requestPlcOperationSignature on the old PDS, and will be delivered by email to the verified account email by default. This token is included as part of a call to com.atproto.identity.signPlcOperation on the old PDS, along with the requested DID fields (new signing key, rotation keys, PDS location, etc). The old PDS will validate the request, sign using the PDS-managed PLC rotation key, and return the signed PLC operation. The operation will not have been submitted to any PLC directory at this point in time. The user is then recommended to submit the operation to the new PDS (using the com.atproto.identity.submitPlcOperation endpoint), which will validate that the changes are "safe" (aka, that they enable the the PDS to help manage the identity and atproto account), and then submit it to the PLC directory. With the identity successfully updated, the new PDS is now the "current" host for the account from the perspective of the entire network. This will be immediately apparent to new services which resolve the identity. Existing services that consume from the firehose will be alerted by the #identity event. Other services, which may have now-stale cached identity metadata for the account, will either refresh when the cache expires, or should refresh their cache when they encounter errors (such as invalid service auth signatures). However, the new account is not yet "active". Finalizing Account Status At this point, the user is still able to authenticate to both PDS instances. The new PDS knows that it is current for the account, but still has the account marked as "deactivated". The old PDS may not realize that it is no longer current. It may be worth double-checking with com.atproto.server.checkAccountStatus on both PDS instances to confirm that all the expected content has been migrated. The user can activate their account on the new PDS with a call to com.atproto.server.activateAccount , and deactivate their account on the old PDS with com.atproto.server.deactivateAccount . At this point the migration is complete. New content can be published by writing to the repo, preferences can be updated, and inter-service auth and proxying should work as expected. It may be necessary to log out of any clients and log back in. In some cases, if services have aggressive identity caching and do not refresh on signature failure, service auth requests could fail for up to 24 hours. It will still be possible to login and authenticate with the old PDS. The user may wish to fully terminated their old account eventually. This can be automated with the deleteAfter parameter to the com.atproto.server.deactivateAccount request. Note that the old PDS may be able to assist with PLC identity recovery during a fixed 72hr window, but only if the account was not fully deleted during that window. Further Reading and Resources Migrating PDS Account with goat PDS MOOver — a third-party tool for migrating PDS accounts Previous Permission Requests Next AT Protocol © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://www.youtube.com/t/privacy | 개인정보처리방침 – 개인정보 보호 및 약관 – Google 개인정보 보호 및 약관 개인정보 보호 및 약관 기본 콘텐츠로 건너뛰기 로그인 개요 개인정보처리방침 서비스 약관 기술 FAQ 개인정보 보호 및 약관 개요 개인정보처리방침 데이터 전송에 관한 제도 핵심 용어 파트너 한국 거주자를 위한 개인정보 관련 추가 정보 업데이트 서비스 약관 기술 FAQ 개인정보 보호 및 약관 개인정보 보호 및 약관 개인정보 보호 및 약관 개요 개인정보처리방침 서비스 약관 기술 FAQ Google 계정 개인정보처리방침 소개 Google에서 수집하는 정보 Google에서 데이터를 수집하는 이유 개인정보 보호 설정 정보 공유 정보 보안 유지 정보 내보내기 및 삭제 정보 유지 규정 준수 및 규제 당국과의 협력 방침 정보 관련 개인정보 보호관행 데이터 전송에 관한 제도 핵심 용어 파트너 한국 거주자를 위한 개인정보 관련 추가 정보 업데이트 Google 개인정보처리방침 Google은 Google 서비스 사용자들이 신뢰를 바탕으로 정보를 제공한다는 것을 잘 알고 있습니다. Google은 사용자의 신뢰에 대한 막중한 책임을 인지하며 최선을 다해 개인정보를 보호하고 사용자가 직접 제어할 수 있도록 노력하고 있습니다. 이 개인정보처리방침은 Google에서 수집하는 정보의 유형, 정보를 수집하는 이유, 정보를 업데이트, 관리, 내보내기, 삭제하는 방식에 대한 이해를 돕기 위한 것입니다. 개인정보 보호 진단 개인정보 보호 설정을 변경하려고 하나요? 개인정보 보호 진단 실행하기 발효일: 2025년 7월 1일 | 보관처리된 버전 | PDF 다운로드 목차 소개 Google에서 수집하는 정보 Google에서 데이터를 수집하는 이유 개인정보 보호 설정 정보 공유 정보 보안 유지 정보 내보내기 및 삭제 정보 유지 규정 준수 및 규제 당국과의 협력 방침 정보 관련 개인정보 보호관행 Google은 매일 수많은 사람들이 새로운 방식으로 세계를 탐험하고 세계와 상호작용할 수 있도록 다양한 서비스를 구축합니다. 그러한 서비스는 다음을 포함합니다. Google 검색, YouTube, Google Home 등의 앱, 사이트, 기기 Chrome 브라우저, Android 운영체제 등의 플랫폼 광고, 분석, 삽입된 Google 지도 등 타사 앱 및 사이트에 통합된 제품 사용자는 Google 서비스를 활용하여 다양한 방식으로 개인 정보를 관리할 수 있습니다. 예를 들어 Google 계정에 가입하여 이메일, 사진과 같은 콘텐츠를 만들고 관리하며 더 관련성 높은 검색 결과를 볼 수 있습니다. 로그아웃한 상태이거나 계정을 만들지 않더라도 Google에서 검색하거나 YouTube 동영상을 보는 등 많은 Google 서비스를 이용할 수 있습니다. Chrome 시크릿 모드 와 같이 비공개 모드로 웹을 탐색할 수도 있습니다. 이 모드를 사용하면 내 기기를 사용하는 다른 사용자에게 탐색 기록을 비공개로 유지할 수 있습니다. 또한 서비스 전반에서 개인 정보 보호 설정을 조정하여 Google에서 일부 유형의 데이터를 수집하는지 여부와 이러한 데이터를 사용하는 방식을 관리할 수 있습니다. 가능한 한 명확하게 설명하기 위해 예시, 해설 동영상, 핵심 용어 정의를 추가했습니다. 이 개인정보처리방침에 관해 궁금한 사항이 있으면 문의 하세요. Google에서 수집하는 정보 서비스 이용 시 Google에서 수집하는 정보의 유형을 이해하시기 바랍니다 Google은 모든 사용자에게 더 나은 서비스를 제공하기 위해 사용자의 언어와 같은 기본적인 정보와 사용자가 가장 유용하다고 생각할 광고 , 온라인에서 가장 중요하게 여기는 사람 이나 좋아할 것 같은 YouTube 동영상 등과 같은 복합적인 정보를 수집합니다. Google에서 수집하는 정보 및 그 정보가 이용되는 방식은 사용자가 서비스를 어떻게 이용하고 개인정보 보호 설정을 어떻게 관리하는지에 따라 다릅니다. 사용자가 Google 계정에 로그인하지 않았을 때는 사용하는 브라우저, 애플리케이션 또는 기기 에 연결된 고유 식별자 와 함께 수집한 정보를 저장합니다. 이를 통해 브라우징 세션 중 사용자의 환경설정이 유지됩니다(예: 선호 언어 또는 사용자 활동을 기반으로 더 관련성 높은 검색결과나 광고 표시 여부). 사용자가 로그인했을 때는 Google 계정과 함께 저장되는 정보도 수집하며, 이를 개인정보 로 취급합니다. 사용자가 생성하거나 제공하는 정보 사용자는 Google 계정을 만들 때 이름과 비밀번호를 포함한 개인 정보 를 Google에 제공합니다. 또한 계정에 전화번호 나 결제 정보 를 추가하도록 선택할 수도 있습니다. Google 계정에 로그인하지 않더라도, Google과 연락을 취하거나 서비스 업데이트를 받기 위해 이메일 주소를 제공하는 것과 같이 정보를 제공하도록 선택할 수 있습니다. 또한 사용자가 서비스를 이용하면서 생성, 업로드하거나 다른 사람에게 받는 콘텐츠를 수집합니다. 여기에는 사용자가 작성하거나 수신하는 이메일, 저장하는 사진과 동영상, 작성하는 문서와 스프레드시트, YouTube 동영상에 다는 댓글 등이 포함됩니다. 사용자가 서비스를 이용할 때 Google이 수집하는 정보 사용자의 앱, 브라우저, 기기 사용자가 Google 서비스에 액세스할 때 사용하는 앱, 브라우저, 기기 에 대한 정보를 수집합니다. 이 정보를 이용하여 자동 제품 업데이트, 배터리가 부족할 때 화면을 어둡게 하는 기능 등을 제공할 수 있습니다. 수집하는 정보에는 고유 식별자 , 브라우저 유형 및 설정, 기기 유형 및 설정, 운영체제, 통신사명과 전화번호를 포함한 모바일 네트워크 정보, 애플리케이션 버전 번호가 포함됩니다. 또한 IP 주소 , 비정상 종료 보고서, 시스템 활동, 요청 날짜와 시간, 리퍼러 URL 등 사용자의 앱, 브라우저, 기기와 Google 서비스의 상호작용에 대한 정보를 수집합니다. 기기의 Google 서비스가 서버에 연결될 때, 예를 들어 Play 스토어에서 앱을 설치할 때나 서비스가 자동 업데이트를 확인할 때 이 정보를 수집합니다. Google 앱이 설치된 Android 기기 를 사용하는 경우 기기는 주기적으로 Google 서버에 연결되어 기기와 서비스 연결에 대한 정보를 제공합니다. 이 정보에는 기기 유형, 이동통신사명 , 비정상 종료 보고서, 설치한 앱 종류 등이 포함되며 기기 설정에 따라 Android 기기를 사용하는 방식에 관한 기타 정보 도 포함됩니다. 사용자의 활동 서비스상의 사용자 활동 정보를 수집하여 좋아할 만한 YouTube 동영상을 추천하는 등의 목적으로 활용합니다. 수집하는 활동 정보에는 다음이 포함될 수 있습니다. 검색하는 단어 시청하는 동영상 콘텐츠와 광고 조회 및 상호작용 음성 및 오디오 정보 구매 활동 사용자가 교류하거나 콘텐츠를 공유하는 사람들 Google 서비스를 사용하는 타사 사이트와 앱에서의 활동 사용자가 Google 계정과 동기화한 Chrome 브라우징 기록 Google 서비스를 사용하여 통화하거나 메시지를 주고받는 경우 통화 및 메시지 로그 정보(전화번호, 발신자 번호, 수신자 번호, 착신전환 번호, 발신자 및 수신자 이메일 주소, 통화와 메시지 일시, 통화 시간, 라우팅 정보, 통화/메시지 유형 및 양 등)를 수집할 수 있습니다. 사용자는 Google 계정에 방문하여 계정에 저장된 활동 정보를 확인하고 관리할 수 있습니다. Google 계정으로 이동 사용자의 위치 정보 서비스를 이용할 때 위치 정보를 수집하여 운전 경로, 주변 장소 검색 결과, 위치를 기반으로 하는 광고 기능 등을 제공할 수 있습니다. 사용 중인 제품과 선택한 설정에 따라 Google에서 내가 사용하는 서비스 및 제품을 더욱 유용하게 만들기 위해 다양한 유형의 위치 정보를 사용할 수 있습니다. 예를 들면 다음과 같습니다. GPS 및 기타 기기의 센서 데이터 IP 주소 검색 또는 집 또는 직장과 같은 라벨을 지정한 장소 등 Google 서비스에서의 활동 Wi-Fi 액세스 포인트, 기지국, 블루투스 지원 기기 등 사용자의 기기 주변 사물에 대한 정보 Google에서 수집하는 위치 데이터의 유형과 저장 기간은 기기 및 계정 설정에 따라 부분적으로 달라집니다. 예를 들어 기기의 설정 앱을 사용하여 Android 기기의 위치 정보 제공을 활성화 또는 차단 할 수 있습니다. 또한 타임라인 을 사용 설정하여 로그인된 기기를 가지고 이동하는 장소를 비공개 지도로 만들 수도 있습니다. 웹 및 앱 활동 설정을 사용하면 Google 서비스에서 이루어진 검색 및 기타 활동이 Google 계정에 저장되며, 여기에는 위치 정보도 포함될 수 있습니다. Google의 위치 정보 사용 방식 에 관해 자세히 알아보세요. 상황에 따라 Google은 공개적으로 액세스할 수 있는 소스 에서 사용자에 관한 정보를 수집하기도 합니다. 예를 들어 사용자의 이름이 지역 신문에 나는 경우 Google 검색엔진은 해당 기사의 색인을 생성하여 다른 사람들이 사용자의 이름을 검색할 때 표시할 수 있습니다. 또한 Google 서비스에 표시될 비즈니스 정보를 제공하는 디렉터리 서비스, Google 비즈니스 서비스의 잠재고객에 관한 정보를 제공하는 마케팅 파트너, 악용사례로부터 보호 하기 위해 정보를 제공하는 보안 파트너 등 신뢰할 수 있는 파트너에게서 사용자에 관한 정보를 수집할 수 있습니다. 광고 및 리서치 서비스 제공 을 위해 파트너로부터 정보를 받기도 합니다. Google은 쿠키 , 픽셀 태그 , 브라우저 웹 스토리지 나 애플리케이션 데이터 캐시 같은 로컬 스토리지, 데이터베이스, 서버 로그 등 다양한 기술을 사용하여 정보를 수집하고 저장합니다. Google에서 데이터를 수집하는 이유 데이터를 사용하여 더 나은 서비스를 구축합니다 모든 서비스에서 수집하는 정보를 다음 목적으로 이용합니다. 서비스 제공 사용자가 검색하는 단어를 처리하여 결과를 제공하거나 연락처에서 수신자를 추천하여 콘텐츠 공유를 돕는 등 서비스 제공 을 위해 사용자 정보를 이용합니다. 서비스 유지 및 개선 정전 원인을 추적하거나 사용자가 신고하는 문제를 해결하는 등 서비스 정상 운영 을 위해 사용자 정보를 이용합니다. 또한 예를 들어 철자가 가장 많이 틀리는 검색어를 파악하여 서비스에 사용되는 맞춤법 검사 기능을 개선하는 식으로 서비스 개선 작업 을 위해 사용자 정보를 이용합니다. 새 서비스 개발 기존 서비스에서 수집하는 정보를 이용하여 새 서비스를 개발합니다. 예를 들어 Google의 첫 포토 앱이었던 Picasa에서 사람들이 사진을 정리하는 방식을 이해하는 것은 Google 포토를 설계하고 출시하는 데 도움이 되었습니다. 콘텐츠와 광고를 포함한 맞춤 서비스 제공 수집한 정보를 이용하여 추천, 맞춤 콘텐츠, 맞춤 검색 결과 를 제공하는 등 사용자를 위해 서비스를 맞춤설정합니다. 예를 들어 보안 진단 은 사용자의 Google 제품 사용 방식에 적합한 보안 팁을 제공합니다. 또한 제공되는 설정에 따라 Google Play는 사용자가 이미 설치한 앱, YouTube에서 시청한 동영상과 같은 정보를 사용하여 좋아할 만한 새로운 앱을 추천합니다. 사용자의 설정에 따라 Google 서비스 전반에서 관심분야 및 활동을 토대로 개인 맞춤 광고 를 표시할 수도 있습니다. 예를 들어 사용자가 '산악 자전거'를 검색한 적이 있다면 YouTube에 스포츠 장비 광고가 표시될 수 있습니다. 내 광고 센터 에서 광고 설정을 방문하여 광고 표시에 Google이 이용하는 정보를 제어할 수 있습니다. 인종, 종교, 성적 지향, 건강과 같은 민감한 카테고리 를 바탕으로 개인 맞춤 광고를 표시하지 않습니다. Drive, Gmail 또는 포토에 있는 정보를 바탕으로 개인 맞춤 광고를 표시하지 않습니다. 사용자가 요청하지 않는 한 이름이나 이메일 등 개인을 식별할 수 있는 정보를 광고주와 공유하지 않습니다. 예를 들어 사용자가 근처 꽃집 광고를 보고 '탭하여 통화' 버튼을 선택하는 경우 Google은 통화를 연결해주고 사용자의 전화번호를 꽃집과 공유할 수 있습니다. 내 광고 센터로 이동 실적 측정 Google 서비스가 어떻게 이용되는지 분석하고 측정하는 데 데이터를 이용합니다. 예를 들어 사용자의 사이트 방문 데이터를 분석하여 제품 설계를 최적화합니다. 또한 사용자의 관련 Google 검색 활동을 비롯해 사용자가 상호작용하는 광고와 관련된 데이터를 이용하여 광고주가 광고 캠페인의 실적 을 파악할 수 있게 해줍니다. 이를 위해 Google 애널리틱스를 포함한 다양한 도구를 사용합니다. Google 애널리틱스를 사용하는 사이트를 방문하거나 앱을 사용할 경우 Google 애널리틱스 고객은 Google이 Google의 광고 서비스를 사용하는 다른 사이트 또는 앱에서의 활동과 현재 방문한 사이트 또는 앱에서의 내 활동 관련된 정보를 연결 하도록 선택할 수 있습니다. 사용자와 커뮤니케이션 이메일 주소 등 수집 정보를 이용하여 사용자와 직접 상호작용합니다. 예를 들어 평소와 다른 위치에서 Google 계정에 로그인하려는 시도 등 의심스러운 활동을 감지하면 사용자에게 알림을 보낼 수 있습니다. 또는 향후 서비스 변경이나 개선 사항을 알릴 수 있습니다. Google에 문의하는 경우 사용자가 겪고 있는 문제 해결에 도움이 되도록 사용자의 요청 기록을 보관합니다. Google과 사용자, 그리고 대중을 보호 서비스의 안전성과 신뢰성 을 개선하기 위해 정보를 이용합니다. 여기에는 Google, 사용자 또는 대중 에게 해를 끼칠 수 있는 사기, 악용 사례, 보안 위험, 기술적 문제를 감지, 예방하고 대응하는 것이 포함됩니다. Google은 이러한 목적을 위해 다양한 기술을 활용하여 사용자 정보를 처리합니다. 사용자 콘텐츠를 분석하는 자동화된 시스템을 사용하여 맞춤 검색결과, 개인 맞춤 광고, 사용자의 서비스 이용 방식에 맞춘 그 밖의 기능 등을 제공합니다. 또한 사용자 콘텐츠를 분석하여 스팸, 멀웨어, 불법 콘텐츠 등 악용사례 감지 에 이용합니다. 데이터 패턴을 인식하기 위해 알고리즘 도 사용합니다. 예를 들어 Google 번역은 사용자가 번역을 요청하는 문구에서 보편적인 언어 패턴을 감지하여 서로 다른 언어 간의 커뮤니케이션을 돕습니다. Google은 Google 서비스와 사용자 기기에서 위에서 설명한 목적을 위해 수집한 정보를 사용 할 수 있습니다. 예를 들어 사용자가 YouTube에서 기타 연주자 동영상을 시청하면 제공되는 설정에 따라 Google 광고 제품을 사용하는 사이트에 기타 레슨 광고가 표시될 수 있습니다. 사용자의 계정 설정에 따라, Google 서비스 및 Google이 제공하는 광고를 개선하기 위해 다른 사이트와 앱에서의 사용자 활동 이 사용자 개인 정보와 연결될 수 있습니다. 사용자의 이메일 주소나 사용자를 식별하는 정보를 다른 사용자가 이미 가지고 있는 경우 Google은 그 다른 사용자에게 사용자의 공개 Google 계정 정보(예: 이름과 사진)를 표시할 수 있습니다. 이렇게 하면 예를 들어 사람들이 사용자가 보내는 이메일을 식별하는 데 도움이 됩니다. 이 개인정보처리방침에 명시되지 않은 목적으로 정보를 이용할 경우 Google은 먼저 사용자의 동의를 요청합니다. 개인정보 보호 설정 사용자는 Google에서 수집하는 정보와 이용 방식에 대해 선택권이 있습니다 이 섹션에서는 Google 서비스 이용 시 개인정보를 관리하기 위한 주요 설정을 설명합니다. 또한 개인정보 보호 진단 을 방문하여 중요한 개인정보 보호 설정을 검토하고 조정할 수 있습니다. 이러한 도구 이외에 제품에서도 구체적인 개인정보 보호 설정을 제공하고 있으며 제품 개인정보 보호 가이드 에서 자세히 알아볼 수 있습니다. 개인정보 보호 진단으로 이동 사용자 정보 관리, 검토, 업데이트 로그인한 상태에서, 이용하고 있는 서비스를 방문하여 언제든지 정보를 검토하고 업데이트할 수 있습니다. 예를 들어 포토와 드라이브는 Google에 저장한 특정 유형의 콘텐츠를 관리할 수 있도록 설계되었습니다. 또한 Google 계정에 저장되는 정보를 검토하고 관리할 수 있는 곳이 있습니다. Google 계정 에는 다음이 포함됩니다. 개인정보 보호 설정 활동 제어 계정에 저장할 활동 유형을 결정합니다. 예를 들어 YouTube 기록을 사용 설정하면 시청한 동영상과 검색한 내용이 계정에 저장되므로 더 나은 추천을 받고 시청을 중단한 지점을 기억하는 기능을 이용할 수 있습니다. 또한 웹 및 앱 활동을 사용 설정하면 다른 Google 서비스에서 이루어진 검색 및 기타 활동이 계정에 저장되므로 검색이 신속해지고 더 유용한 앱 및 콘텐츠 추천을 받는 등 더욱 맞춤설정된 환경을 이용할 수 있습니다. 웹 및 앱 활동에는 Google 서비스를 사용하는 다른 사이트, 앱, 기기의 활동에 관한 정보 (예: Android에서 설치하고 사용하는 앱)를 Google 계정에 저장하고 Google 서비스를 개선하는 데 사용할지를 제어할 수 있는 하위 설정도 있습니다. 활동 제어로 이동 광고 설정 Google 및 Google과 파트너 관계를 유지 하여 광고를 표시하는 사이트와 앱에 표시되는 광고의 환경설정을 관리합니다. 관심사를 변경하고, 개인정보를 이용하여 더 관련성 높은 광고를 표시하는 것을 허용할지 선택하고, 특정 광고 서비스 이용 여부를 선택할 수 있습니다. 내 광고 센터로 이동 내 정보 Google 계정의 개인 정보를 관리하고, Google 서비스 전반에서 개인 정보를 볼 수 있는 대상을 제어합니다. 내 정보로 이동 공유 인증 광고에 표시되는 리뷰, 추천 등의 활동 옆에 이름과 사진이 표시되게 할 것인지 선택합니다. 공유 인증으로 이동 Google 서비스를 사용하는 사이트 및 앱 사용자가 Google 애널리틱스와 같은 Google 서비스를 사용하는 웹사이트 및 앱을 방문하거나 이러한 서비스를 사용할 때 해당 웹사이트와 앱에서 Google에 공유할 수 있는 정보를 관리합니다. Google이 Google 서비스를 사용하는 사이트 또는 앱을 출처로 하는 정보를 사용하는 방식으로 이동하세요. 정보를 검토하고 업데이트하는 방법 내 활동 내 활동에서는 내가 한 검색이나 Google Play 방문 등 로그인한 상태로 Google 서비스를 사용할 때 Google 계정에 저장된 데이터를 검토하고 관리할 수 있습니다. 날짜 및 주제별로 찾아보고 활동의 일부 또는 전부를 삭제할 수 있습니다. 내 활동으로 이동 Google 대시보드 Google 대시보드에서 특정 제품과 연결된 정보를 관리할 수 있습니다. 대시보드로 이동 사용자 개인정보 이름, 이메일, 전화번호 등 사용자 연락처 정보를 관리합니다. 개인정보로 이동 로그아웃 상태에서 다음과 같이 브라우저나 기기와 연결된 정보를 관리할 수 있습니다. 로그아웃 검색 맞춤설정: 사용자의 검색 활동을 이용하여 더 관련성 높은 결과와 추천을 제공하도록 허용할 것인지 선택 합니다. YouTube 설정: YouTube 검색 기록 과 YouTube 시청 기록 을 일시중지하고 삭제합니다. 광고 설정: Google 및 Google과 파트너 관계를 유지하여 광고를 표시하는 사이트와 앱에 표시되는 광고의 환경설정을 관리 합니다. 정보 내보내기, 제거, 삭제 사용자는 백업하거나 Google 외부 서비스에서 사용하기 위해 Google 계정의 콘텐츠 사본을 내보내기할 수 있습니다. 데이터 내보내기 정보를 삭제하는 방법은 다음과 같습니다. 특정 Google 서비스 에서 콘텐츠 삭제 내 활동 을 사용하여 계정에서 특정 항목을 검색한 다음 삭제 제품과 연결된 정보를 포함하여 특정 Google 제품 삭제 전체 Google 계정 삭제 정보 삭제 휴면계정 관리자 에서 예기치 않게 계정을 사용할 수 없을 때를 대비해 다른 사람이 사용자의 Google 계정 일부에 액세스하는 것을 허용할 수 있습니다. 마지막으로 사용자는 관련 법률과 Google 정책에 따라 특정 Google 서비스에서 콘텐츠 삭제를 요청 할 수도 있습니다. Google 계정 로그인 여부와 관계없이 Google에서 수집하는 정보를 관리하는 다른 방법은 다음과 같습니다. 브라우저 설정: 예를 들어 Google이 브라우저에 쿠키 를 설정할 때 표시하도록 브라우저를 설정할 수 있습니다. 또한 특정 도메인이나 모든 도메인의 모든 쿠키를 차단하도록 브라우저를 설정할 수 있습니다. 다만, Google 서비스는 사용자의 언어 환경설정을 기억하는 등 올바른 기능 작동을 위해 쿠키를 사용 한다는 점을 유념하시기 바랍니다. 기기 수준 설정: 기기에 Google이 수집하는 정보 유형을 결정하는 설정이 있을 수 있습니다. 예를 들어 Android 기기에서 위치 설정을 변경 할 수 있습니다. 정보 공유 사용자가 정보를 공유하는 경우 많은 Google 서비스에서 사용자는 다른 사람들과 정보를 공유할 수 있고 공유 방식을 제어할 수 있습니다. 예를 들어 YouTube에서 공개적으로 동영상을 공유하거나 비공개로 유지할 수 있습니다. 공개적으로 정보를 공유할 경우, Google 검색을 비롯한 검색엔진을 통해 해당 콘텐츠에 액세스가 가능해질 수 있다는 점을 유념하시기 바랍니다. Google 서비스에 로그인하여 YouTube 동영상에 댓글을 남기거나 Play에서 앱을 리뷰하는 등 상호작용을 하면 이름과 사진이 활동 옆에 표시됩니다. Google은 사용자의 공유 인증 설정에 따라 이 정보를 광고에 표시할 수도 있습니다. Google이 정보를 공유하는 경우 Google은 다음 경우를 제외하고 Google 이외의 회사, 조직 또는 개인과 사용자 개인정보를 공유하지 않습니다. 사용자가 동의하는 경우 Google에서는 사용자가 동의할 경우 Google 외부와 개인 정보를 공유합니다. 예를 들어 사용자가 사용자가 예약 서비스를 사용하여 Google Home에서 식당을 예약 하면 사용자의 이름이나 전화번호를 식당과 공유하기 전에 사용자 동의를 얻습니다. 또한 Google은 사용자가 자신의 Google 계정 데이터에 대한 액세스 권한을 부여한 타사 앱 및 사이트를 검토하고 관리 할 수 있는 제어 기능을 제공합니다. Google에서는 민감한 개인 정보 를 공유할 경우 사용자에게 명시적인 동의를 요청합니다. 도메인 관리자와 공유하는 경우 Google 서비스를 사용하는 조직에서 근무하거나 학생인 경우 계정을 관리하는 도메인 관리자 와 리셀러가 내 Google 계정에 액세스할 수 있습니다. 이들은 다음과 같은 작업을 할 수 있습니다. 사용자 계정에 저장된 정보(예: 이메일) 액세스 및 유지 계정 관련 통계 조회(예: 사용자가 설치한 앱 수) 계정 비밀번호 변경 계정 액세스 일시 중지 또는 해지 관련법, 규정, 법적 절차 또는 강제력이 있는 정부 요청을 준수하기 위해 계정 정보 수집 정보 또는 개인정보 보호 설정을 삭제하거나 수정할 수 있는 사용자 기능 제한 외부 처리가 필요한 경우 Google은 Google 계열사 및 기타 신뢰할 수 있는 업체 및 개인에게 Google 지침을 기반으로 Google의 개인정보처리방침, 기타 기밀 및 보안 관련 조치를 준수하면서 Google의 개인 정보 처리 업무를 대행하도록 개인 정보를 제공합니다. 예를 들어 Google은 데이터 센터의 운영, 제품 및 서비스의 제공, 내부 비즈니스 프로세스의 개선, 고객 및 사용자를 위한 추가 지원 제공 등을 위해 서비스 제공업체를 이용합니다. 또한 공공 안전을 위해 YouTube 동영상 콘텐츠를 검토하고 Google의 오디오 인식 기술 개선을 위해 저장된 사용자 오디오 샘플을 청취 및 분석할 목적으로도 서비스 제공업체를 이용합니다. 법률상 필요한 경우 Google은 다음 목적을 위해 정보의 공개가 합리적으로 필요하다는 선의의 믿음이 있는 경우 개인 정보를 Google 외부에 공유합니다. 관련법, 규정, 법적 절차 또는 강제력이 있는 정부 요청 충족. 투명성 보고서 에서 정부로부터 받은 요청의 건수와 유형에 대한 정보를 공유합니다. 서비스 약관 위반 조사를 포함한 관련 서비스 약관 집행 사기, 보안 또는 기술적 문제를 감지, 예방 또는 해결 위험 요소로부터 Google, 사용자 , 또는 대중의 권리, 재산, 안전을 보호 Google은 개인 식별이 불가능한 정보 를 대중 및 파트너(예: 게시자, 광고주, 개발자 또는 권리 보유자)와 공유할 수 있습니다. 예를 들어 Google 서비스의 일반적인 사용 트랜드를 보여주는 정보를 대중과 공유합니다. 또한 특정 파트너 가 광고 및 측정 목적으로 자체 쿠키나 유사한 기술을 사용하여 사용자의 브라우저나 기기에서 정보를 수집하는 것을 허용합니다. Google은 인수, 합병 또는 자산의 매각이 있을 경우 사용자 개인정보의 기밀을 계속 유지하며, 개인정보가 타사에 전달되거나 해당 업체의 개인정보처리방침이 적용되기 전에 해당 사용자에게 미리 공지합니다. 정보 보안 유지 정보 보호를 위해 서비스에 보안을 구축합니다 모든 Google 제품에는 사용자 정보를 지속적으로 보호하는 강력한 보안 기능이 구축되어 있습니다. 서비스를 유지하면서 얻는 유용한 정보는 보안 위협을 감지하고 자동으로 차단하는 데 도움이 됩니다. 사용자가 알아야 한다고 생각되는 위험 요소를 감지하면 사용자에게 알리고 보호 기능을 강화할 수 있는 단계를 안내합니다. 다음과 같은 조치를 통해 정보 무단 액세스, 변경, 공개, 파기로부터 사용자와 Google을 보호하기 위해 노력하고 있습니다. 암호화를 사용하여 전송 중에 데이터를 비공개로 유지합니다. 세이프 브라우징 , 보안 진단, 2단계 인증 등 다양한 보안 기능을 제공하여 계정 보호를 지원합니다. 시스템 무단 액세스를 방지하기 위해 물리적 보안 조치를 포함하여 Google의 정보 수집, 저장 및 처리 관행을 검토합니다. 개인정보 액세스 권한을 개인정보를 처리하기 위해 액세스가 필요한 Google 직원, 계약업자(위탁업자) 및 대리인으로 제한합니다. 액세스 권한을 가진 사람은 계약을 통해 엄격한 기밀유지의 의무를 갖게 되며 이러한 의무를 어길 경우 제재를 받거나 계약이 해지될 수 있습니다. 정보 내보내기 및 삭제 사용자는 언제든지 Google 계정에서 자신의 정보에 대한 사본을 내보내거나 삭제할 수 있습니다 사용자는 백업하거나 Google 외부 서비스에서 사용하기 위해 Google 계정의 콘텐츠 사본을 내보내기할 수 있습니다. 데이터 내보내기 정보를 삭제하는 방법은 다음과 같습니다. 특정 Google 서비스 에서 콘텐츠 삭제 내 활동 을 사용하여 계정에서 특정 항목을 검색한 다음 삭제 제품과 연결된 정보를 포함하여 특정 Google 제품 삭제 전체 Google 계정 삭제 정보 삭제 정보 유지 Google은 수집한 데이터를 데이터의 내용, Google에서의 데이터 사용 방식 및 사용자가 설정을 구성한 방식에 따라 각기 다른 기간 동안 보관합니다. 사용자의 개인 정보 또는 직접 만들거나 업로드한 콘텐츠( 사진 및 문서 )와 같은 일부 콘텐츠는 언제든지 삭제할 수 있습니다. 계정에 저장된 활동 정보 는 삭제하거나 일정 시간이 지난 후 자동 삭제되도록 선택 할 수 있습니다. Google은 사용자가 직접 삭제하거나 삭제되도록 선택할 때까지 이 데이터를 Google 계정에 보관합니다. 서버 로그의 광고 데이터 와 같은 기타 데이터는 일정 기간이 지난 후 자동으로 삭제되거나 익명화됩니다. Google은 Google 서비스 사용 빈도와 같은 일부 정보는 Google 계정이 삭제될 때까지 보관합니다. 일부 데이터는 보안, 사기 및 남용 방지, 금융 기록 보관과 같은 합법적인 비즈니스 또는 법적 목적을 위해 필요한 경우 더 오랜 기간 동안 보관됩니다. 사용자가 데이터를 삭제하면 Google은 Google 서버에서 데이터가 안전하고 확실하게 삭제되거나 익명 상태로 보관되는 것을 보장하기 위해 일정한 삭제 절차를 따릅니다. Google은 Google 서비스들을 통해 정보의 우발적이거나 악의적인 삭제를 방지하려고 노력합니다. 이에 따라 사용자가 정보를 삭제한 시간과 활성 및 백업 시스템에서 사본이 삭제되는 시간 사이에 지연이 있을 수 있습니다. 정보를 삭제하는 데 걸리는 시간을 포함하여 Google의 데이터 유지 기간 에 대해 읽어볼 수 있습니다. 규정 준수 및 규제 당국과의 협력 Google은 이 개인정보처리방침을 정기적으로 검토하고 이 방침에 따라 사용자 정보가 처리되고 있는지 확인합니다. 데이터 이전 Google은 전 세계에 서버를 두고 있기 때문에 사용자 정보가 거주 국가 밖에 있는 서버에서 처리될 수 있습니다. 데이터 보호법은 국가마다 다르며, 법률마다 데이터를 보호하는 정도가 다릅니다. Google은 정보가 처리되는 지역과 관계없이 이 정책에 설명된 보호 절차를 동일하게 적용합니다. 또한 데이터 전송과 관련하여 특정 법적 프레임워크 를 준수합니다. 공식 서면 신고서를 통해 불만사항이 접수되면 신고자에게 연락합니다. 데이터 이전과 관련하여 사용자와 직접 해결할 수 없는 불만사항이 있는 경우 문제 해결을 위해 현지 데이터 보호 당국을 비롯한 지역의 규제 당국과 협력합니다. 방침 정보 이 방침의 적용 이 개인정보처리방침은 YouTube, Android, 타사 사이트에서 제공되는 서비스(예: 광고 서비스)를 포함해 Google LLC 및 계열사 가 제공하는 모든 서비스에 적용됩니다. 이 개인정보처리방침은 이 개인정보처리방침을 포함하지 않는 별도의 개인정보처리방침이 있는 서비스에는 적용되지 않습니다. 다음 항목에는 이 개인정보처리방침이 적용되지 않습니다. Google 서비스를 광고하는 다른 회사 및 조직의 정보 관행 다른 회사나 개인이 제공하는 서비스(예: 이 방침이 적용되는 Google 서비스가 포함되어 있거나, 사용자의 검색결과에 표시되거나, Google 서비스에서 링크될 수 있는 제품 또는 사이트) 이 방침의 변경 Google은 이 개인정보처리방침을 수시로 변경합니다. Google은 사용자의 명시적인 동의 없이 이 개인정보처리방침에 설명된 사용자의 권한을 축소하지 않습니다. 항상 마지막 변경 사항이 게시된 날짜를 표시하고 사용자가 검토를 위해 보관처리된 버전 에 액세스할 수 있도록 합니다. 변경 사항이 중대할 경우에는 일부 서비스에서 개인정보처리방침과 관련한 변경 고지 이메일을 발송하는 등 적극적으로 알립니다. 관련 개인정보 보호관행 특정 Google 서비스 다음 고지에 일부 Google 서비스에 대한 추가적인 정보가 나와 있습니다. Payments Fiber Gemini 앱 Google Fi Google Workspace for Education Read Along YouTube Kids Family Link를 통해 관리되는 만 13세(또는 거주 국가의 해당 연령) 미만 자녀의 Google계정 어린이와 청소년을 위한 Family Link 개인 정보 보호 가이드 Google 어시스턴트의 어린이용 기능에서 수집한 음성 및 오디오 Google Workspace 또는 Google Cloud Platform을 사용하는 조직의 일원인 경우 이러한 서비스에서 내 개인 정보를 어떻게 수집하고 사용하는지 Google Cloud 개인정보처리방침 에서 확인해 주시기 바랍니다. 기타 유용한 자료 다음 링크는 Google의 관행 및 개인정보 보호 설정을 자세히 알아볼 수 있는 유용한 자료를 제공합니다. Google 계정 에서 다양한 설정을 사용하여 계정을 관리할 수 있습니다. 개인정보 보호 진단 은 Google 계정의 주요 개인정보 보호 설정을 안내합니다. Google 안전 센터 를 방문하여 온라인상에서 가족을 위한 기본적인 디지털 규칙을 정할 때 유용하게 활용할 수 있는 Google의 내장 보안 기능, 개인정보 보호 설정, 도구에 관해 알아볼 수 있습니다. Google의 청소년 개인 정보 보호 가이드 에서 개인 정보 보호에 관해 자주 묻는 질문의 답변을 확인할 수 있습니다. 개인정보 보호 및 약관 에서는 이 개인정보처리방침과 Google 서비스 약관을 더 자세히 설명합니다. 기술 섹션에서 다음 주제에 관해 자세히 알아볼 수 있습니다. Google의 쿠키 사용법 광고 에 사용되는 기술 Google이 Google 서비스를 사용하는 웹사이트 또는 앱의 정보를 사용하는 방법 핵심 용어 개인 식별이 불가능한 정보 사용자 개인을 식별할 수 없는 방식으로 기록된 사용자 정보를 말합니다. 개인정보 이름, 이메일 주소, 결제 정보 등 사용자가 Google에 제공하는 개인 식별 정보, 또는 이러한 개인 식별 정보와 연관이 있음을 합리적으로 파악할 수 있는 기타 데이터(예: 사용자의 Google 계정에 연결된 정보)를 의미합니다. 계열사 계열사는 Google Ireland Limited, Google Commerce Ltd, Google Payment Corp, Google Dialer Inc 등 EU에서 소비자 서비스를 제공하는 법인을 포함하여, Google 그룹사에 속한 법인입니다. EU에서 비즈니스 서비스를 제공하는 회사 에 관해 자세히 알아볼 수 있습니다. 고유 식별자 고유 식별자는 브라우저, 앱 또는 기기를 고유하게 식별하는 데 사용되는 문자열입니다. 영구적인지 아닌지, 사용자가 재설정할 수 있는지, 어떻게 액세스할 수 있는지 등은 식별자마다 다릅니다. 고유 식별자는 보안 및 사기 행위 감지, 이메일 받은편지함 등의 서비스 동기화, 사용자의 환경설정 기억, 맞춤 광고 제공과 같은 다양한 목적으로 사용될 수 있습니다. 예를 들어 쿠키에 저장된 고유 식별자를 사용하면 사이트에서 브라우저의 콘텐츠를 사용자가 원하는 언어로 표시할 수 있습니다. 사용자는 모든 쿠키를 거부하거나 쿠키를 전송할 때 사용자에게 알리도록 브라우저를 설정할 수 있습니다. Google이 쿠키를 사용하는 방법 을 자세히 알아보시기 바랍니다. 브라우저 이외의 다른 플랫폼에서는 고유 식별자가 특정 기기 또는 기기에 설치된 앱을 인식하는 데 사용됩니다. 예를 들어 광고 ID와 같은 고유 식별자는 Android 기기에서 사용자에게 맞는 광고를 제공하는 데 사용되며, 기기 설정에서 관리 할 수 있습니다. 제조업체에서 기기에 고유 식별자(범용 고유 식별자 또는 UUID라고도 함)를 부여할 수도 있습니다. 휴대전화의 IMEI 번호가 이러한 고유 식별자의 예입니다. 예를 들어 기기의 고유 식별자는 Google 서비스를 기기에 맞게 맞춤설정하거나 서비스와 관련된 기기 문제를 분석하는 데 사용될 수 있습니다. 기기 기기란 Google 서비스에 액세스하는 데 사용할 수 있는 컴퓨터를 말합니다. 예를 들어 데스크톱 컴퓨터, 태블릿, 스마트 스피커, 스마트폰은 모두 기기로 간주됩니다. 리퍼러 URL 리퍼러 URL(Uniform Resource Locator)이란 일반적으로 웹페이지 링크를 클릭할 때 웹브라우저에서 대상 웹페이지로 전송되는 정보를 말합니다. 리퍼러 URL에는 브라우저에서 마지막으로 방문한 웹페이지의 URL이 포함됩니다. 민감한 개인정보 기밀 의료 기록, 인종 또는 민족, 정치적 또는 종교적 신념, 성 정체성 등의 주제와 관련된 특정 개인정보 카테고리입니다. 브라우저 웹 스토리지 브라우저 웹 스토리지를 사용하면 웹사이트가 기기의 브라우저에 데이터를 저장할 수 있습니다. 브라우저 웹 스토리지를 '로컬 스토리지' 모드에서 사용하면 여러 세션에 걸쳐 데이터를 저장할 수 있습니다. 이렇게 하면 브라우저를 닫았다가 다시 연 후에도 데이터를 가져올 수 있습니다. 웹 스토리지를 쉽게 활용하는 데 도움이 되는 기술로 HTML 5를 들 수 있습니다. 서버 로그 대부분의 웹사이트와 마찬가지로 Google 서버는 사용자가 Google 사이트를 방문할 때 요청한 페이지를 자동으로 기록합니다. 이러한 ‘서버 로그’에는 일반적으로 웹 요청, 인터넷 프로토콜 주소, 브라우저 유형, 브라우저 언어, 요청 날짜 및 시간, 사용자의 브라우저를 고유하게 식별할 수 있는 하나 이상의 쿠키가 포함됩니다. 'car'라고 검색했을 때 기록되는 로그 항목은 일반적으로 다음과 같습니다. 123.45.67.89 - 25/Mar/2003 10:15:32 - http://www.google.com/search?q=cars - Chrome 112; OS X 10.15.7 - 740674ce2123e969 123.45.67.89 ISP가 사용자에게 할당한 IP 주소입니다. 이용 중인 서비스에 따라 서비스 제공업체는 사용자가 인터넷에 접속할 때마다 다른 주소를 할당할 수 있습니다. 25/Mar/2003 10:15:32 쿼리의 날짜 및 시간을 나타냅니다. http://www.google.com/search?q=cars 요청된 URL(검색어 포함)입니다. Chrome 112; OS X 10.15.7 사용 중인 브라우저와 운영체제입니다. 740674ce2123a969 Google을 처음 방문했을 때 컴퓨터에 할당된 고유한 쿠키 ID입니다. 쿠키는 사용자가 삭제할 수 있습니다. Google을 마지막으로 방문한 이후에 사용자가 컴퓨터에서 쿠키를 삭제한 경우, 다음에 같은 기기에서 Google을 방문하면 기기에 이와 같은 고유한 쿠키 ID가 다시 할당됩니다. 알고리즘 컴퓨터가 문제해결 작업을 진행할 때 따르는 절차 또는 규칙의 집합입니다. 애플리케이션 데이터 캐시 애플리케이션 데이터 캐시는 기기에 있는 데이터 저장소이며, 인터넷 접속 없이 웹 애플리케이션을 실행하거나 콘텐츠를 더 빠른 속도로 로드하여 애플리케이션의 성능을 개선할 수 있습니다. 쿠키 쿠키는 문자열을 포함하는 작은 파일이며, 사용자가 웹사이트를 방문할 때 컴퓨터로 전송됩니다. 사용자가 사이트를 다시 방문하면 사이트는 쿠키를 통해 사용자의 브라우저를 인식하게 됩니다. 쿠키에는 사용자 환경설정 및 기타 정보가 저장될 수도 있습니다. 사용자는 모든 쿠키를 거부하거나 쿠키를 전송할 때 사용자에게 알리도록 브라우저를 설정할 수 있습니다. 하지만 쿠키가 없으면 일부 웹사이트 기능이나 서비스가 제대로 작동하지 않을 수도 있습니다. Google 파트너의 사이트나 앱을 이용할 때 Google이 쿠키를 사용하는 방법 과 Google이 쿠키를 비롯한 데이터를 사용하는 방법을 자세히 알아보시기 바랍니다. 픽셀 태그 픽셀 태그란 웹사이트 조회나 이메일 확인 등의 특정 활동을 추적하기 위해 웹사이트 또는 이메일 본문에 삽입되는 기술의 일종입니다. 픽셀 태그는 쿠키와 결합하여 사용되기도 합니다. Google 계정 사용자는 Google 계정 에 가입하고 몇 가지 개인정보(일반적으로 이름, 이메일 주소, 비밀번호)를 제공하여 일부 Google 서비스에 액세스할 수 있습니다. 이 계정 정보는 사용자가 Google 서비스에 액세스할 때 사용자를 인증하고, 다른 사용자의 무단 액세스로부터 계정을 보호하는 데 사용됩니다. 사용자는 Google 계정 설정을 통해 언제든지 계정을 수정하거나 삭제할 수 있습니다. IP 주소 인터넷에 연결된 모든 기기에는 IP(인터넷 프로토콜) 주소라고 하는 고유한 숫자가 할당됩니다. 이러한 숫자는 일반적으로 지역 단위로 할당되므로 특정한 기기가 어느 위치에서 인터넷에 연결되는지 식별하기 위해 IP 주소를 사용하는 경우가 많습니다. Google의 위치 정보 사용 방법 에 관해 자세히 알아보세요. 추가 컨텍스트 개선 작업 예를 들어 Google은 쿠키를 사용하여 사용자가 Google 서비스와 상호작용하는 방식을 분석한 결과를 바탕으로 보다 우수한 제품을 만듭니다. 예를 들어 사용자가 특정 작업을 완료하는 데 너무 오래 걸리거나 완료하지 못하는 경우를 발견하면 기능을 다시 설계하고 제품을 개선할 수 있습니다. 개인 최적화 광고 광고주가 제공하는 정보를 기반으로 개인 최적화 광고가 표시될 수도 있습니다. 예를 들어 사용자가 광고주의 웹사이트에서 쇼핑을 했다면 광고주는 그 방문 정보를 이용하여 광고를 게재할 수 있습니다. 자세히 알아보기 결제 정보 예를 들어 Google 계정에 신용카드나 다른 결제 수단을 추가하면 Play 스토어에서 앱을 구입하는 것과 같이 서비스에서 구입할 때 이를 사용할 수 있습니다. 또한 Google에서는 결제 처리를 위해 비즈니스 세금 ID와 같은 다른 정보를 요청할 수도 있습니다. 경우에 따라 사용자 본인 확인에 필요한 정보를 요청할 수도 있습니다. 예를 들어 사용자가 입력한 생일을 토대로 계산한 나이가 Google 계정을 사용하기 위한 최소 나이보다 적은 경우 나이 요구사항을 충족하는지 확인하기 위해 결제 정보를 이용할 수 있습니다. 자세히 알아보기 공개적으로 액세스할 수 있는 소스 예를 들어 Google은 온라인 또는 기타 공개 소스에서 공개적으로 제공되는 정보를 수집하여 Google AI 모델을 학습시키고 Google 번역, Gemini 앱, Cloud AI와 같은 제품 및 기능을 개발할 수 있습니다. 또는 웹사이트에 사용자의 비즈니스 정보가 표시되는 경우 색인을 생성하여 Google 서비스에 표시할 수 있습니다. 광고 및 리서치 서비스 제공 예를 들어 판매자는 포인트 카드 프로그램의 데이터를 업로드하여 검색 또는 쇼핑 결과에 포인트 정보를 포함하거나 광고 캠페인의 실적을 더 정확하게 파악할 수 있습니다. Google은 광고주에게 개인에 관한 정보를 공개하지 않는 집계 보고서만 제공합니다. 광고 캠페인의 실적 광고에 사용되는 기술에 관해 자세히 알아보세요 . 기기 예를 들어 사용자의 기기 정보를 이용하여 앱을 설치하거나 Google Play에서 구입한 영화를 볼 때 어떤 기기를 사용할지 결정하는 데 도움을 줄 수 있습니다. 또한 이 정보를 이용하여 사용자 계정을 보호합니다. 기기 주변 사물에 대한 정보 Android에서 Google의 위치 서비스를 사용하면 Google 지도처럼 위치 정보에 의존하는 앱의 성능이 향상됩니다. Google 위치 서비스를 사용하면 기기에서 기기 위치, 센서(예: 가속도계), 가까운 기지국 및 Wi-Fi 액세스 포인트(예: MAC 주소와 신호 세기)와 관련한 정보를 Google로 보냅니다. 이러한 정보를 통해 사용자 위치를 파악합니다. 사용자는 기기 설정을 통해 Google 위치 서비스를 사용할 수 있습니다. 자세히 알아보기 기기의 센서 데이터 기기에는 사용자의 위치와 이동을 더 정확하게 파악할 수 있도록 하는 센서가 있을 수도 있습니다. 예를 들어 속도를 파악하는 가속도계와 이동 방향을 확인하는 자이로스코프가 사용될 수 있습니다. Google의 위치 정보 사용 방법 에 관해 자세히 알아보세요. 다른 사이트와 앱에서의 사용자 활동 이러한 활동은 계정과 Chrome 동기화와 같은 Google 서비스를 이용하거나 Google과 파트너 관계에 있는 사이트 및 앱을 방문할 때 나타날 수 있습니다. 많은 웹사이트 및 앱이 콘텐츠 및 서비스를 개선할 목적으로 Google과 파트너 관계를 맺습니다. 예를 들어 웹사이트에서 애드센스 같은 광고 서비스나 Google 애널리틱스 같은 분석 도구를 사용하거나 YouTube 동영상과 같은 다른 콘텐츠를 삽입할 수도 있습니다. 이러한 서비스는 활동 관련 정보를 Google과 공유할 수 있으며 계정 설정 과 사용하는 제품(예: 파트너가 Google 광고 서비스와 연계하여 Google 애널리틱스를 사용)에 따라 활동 데이터가 개인정보와 연결될 수 있습니다. 사용자가 파트너의 사이트 또는 앱을 사용할 때 Google에서 데이터를 사용하는 방법을 자세히 알아보세요 . 대중 예를 들어 Google은 Google의 콘텐츠 삭제 정책 또는 관련 법률에 따라 Google 서비스에서 콘텐츠를 삭제해 달라는 요청 과 관련된 정보를 처리하여 요청을 평가하고, 투명성을 보장하고, 책임을 다하며, 이러한 관행을 준수하는 과정에서 악용 및 사기를 방지합니다. 맞춤 검색결과 예를 들어 Google 계정에 로그인하고 웹 및 앱 활동 제어를 사용하도록 설정하면 이전 검색과 다른 Google 서비스에서의 활동을 기반으로 더 관련성 높은 검색결과를 얻을 수 있습니다. 여기에서 자세한 내용 을 확인할 수 있습니다. 또한 로그아웃했을 때에도 맞춤 검색결과를 얻을 수 있습니다. 이 수준의 검색 맞춤설정을 원하지 않으면 비공개 검색 및 시크릿 브라우징 을 하거나 로그아웃 검색 맞춤설정 을 사용 중지할 수 있습니다. 민감한 카테고리 Google은 사용자에게 개인 최적화 광고를 표시할 때 사용자의 활동을 기반으로 사용자가 관심이 있을 것으로 생각되는 주제를 이용합니다. 예를 들어 '요리와 조리법' 또는 '항공 여행'과 같은 주제의 광고가 표시될 수 있습니다. 인종, 종교, 성적 지향, 건강과 같은 민감한 카테고리를 주제로 이용하거나 이를 기반으로 한 개인 최적화 광고를 표시하지 않습니다. 또한 Google 서비스를 이용하는 광고주에게도 이를 동일하게 요청 합니다. 법적 절차 또는 강제력이 있는 정부 요청 다른 IT 통신 기업과 마찬가지로 Google도 전 세계 각국 정부 및 법원으로부터 사용자 데이터를 공개하라는 요청을 수시로 받습니다. Google은 이러한 법적 요청에 대응할 때 사용자가 Google에 저장한 데이터의 보안과 개인정보 보호를 중요하게 생각합니다. Google 법무팀은 유형에 관계없이 모든 요청을 일일이 검토하며, 요청이 지나치게 광범위한 것 �� | 2026-01-13T08:49:23 |
https://atproto.com#resources | AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme Welcome to the Atmosphere The AT Protocol is an open, decentralized network for building social applications. Quickstart Explore SDKs Guides Quickstart Create an application and start building. Read more Self-host Learn how to set up your own personal data server. Read more Glossary Definitions for all the terminology used in AT Protocol. Read more FAQ Frequently Asked Questions about the Atmosphere. Read more Specs Repository Self-authenticating storage for public account content. Lexicon A schema definition language for ATProto. HTTP API (XRPC) Cross-system queries and procedures over HTTP. URI Scheme A URI scheme for addressing ATProto repository data. Learn more Guide Glossary of terms What's a PDS? an AppView? a DID? If you're feeling a little bowled over by new concepts, give this glossary a look. Keep reading Guide The fast intro to building on ATProto In this guide, we build a simple multi-user app that publishes your current "status" as an emoji. Keep reading Article ATProto for distributed systems engineers In this article we explore AT Proto from the perspective of distributed backend engineering. Keep reading Guide What is Lexicon, and how do I use it to make a schema? This guide will introduce you to Lexicon and get you started with building your own schemas. Keep reading Article ATProto Ethos A deep dive into the philosophical and aesthetic principles underlying the design of AT Protocol. Keep reading Web Without Walls - Talk at React Universe 2024 Talk An introduction to the AT Protocol presented by Dan Abramov at React Universe Conf 2024 Make Identity Central Again, with Bluesky's Jay Graber Interview An interview between Jay Graber and Flipboard CEO Mike McCue about making social more like the Web. Bluesky and the AT Protocol: Usable Decentralized Social Media Whitepaper A whitepaper authored by Martin Kleppman and the AT Protocol team. Looking for the Bluesky API docs? Go to docs.bsky.app for Bluesky-specific documentation. Next ATProto Ethos © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/how-to-set-up-github-commit-messages-on-your-slack-workspace | How to set up Github Commit Messages on your Slack Workspace? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Slack How to set up Github Commit Messages on your Slack Workspace? Anjali Arya • September 5, 2024 TABLE OF CONTENTS Introduction: Integrating GitHub commit messages with Slack can greatly enhance collaboration and streamline communication within development teams. By setting up this integration, you can receive real-time notifications of commit activity directly in your Slack workspace, ensuring that everyone stays up-to-date and informed. This article provides a step-by-step guide on how to configure GitHub commit message notifications on your Slack workspace, enabling seamless communication between your GitHub repository and Slack channels. Prerequisites : Before getting started, ensure you have the following: A GitHub Repository : You'll need a GitHub repository for which you want to receive commit message notifications. Slack Workspace with App Integration Permission : Ensure you have access to a Slack workspace where you can install and configure apps. Let's dive into the setup process and get your GitHub commit messages flowing into your Slack channels. 1. Slack Configurations: To effectively set up GitHub commit message notifications on your Slack workspace, follow the step-by-step instructions below: A. Accessing Apps in Slack: To begin, open your Slack Workspace and locate the " Apps " option in the sidebar. If you don't see it immediately, click " Browse Slack " to access the Apps section. This step ensures that an seamlessly integrate external applications with your Slack workspace, enhancing your team's productivity. B. Adding the GitHub App to Slack: Within the Apps section, search for " GitHub " and proceed to add the GitHub app to your Slack workspace. Integrating GitHub with Slack allows you to consolidate your development workflow and foster effective collaboration among team members. C. Configuring GitHub Notifications: Once the GitHub app is added, it's time to configure the notifications. Select the Slack channel where you want to receive GitHub event notifications. Choosing a specific channel, such as " #random " or one dedicated to development updates, ensures that relevant notifications reach the right audience. After selecting the channel, click on " Add GitHub Integration " to establish the connection. D. Copying the Webhook URL: As part of the integration process, Slack will provide you with a unique Webhook URL as part of the integration process. This URL serves as a communication bridge between GitHub and your Slack workspace. Copy this Webhook URL, as you will need it in the subsequent steps when configuring your GitHub repository. E. Optional Configuration: To further tailor the integration, you can consider some optional configuration settings. This customization allows you to optimize the notifications to your preferences. You can choose specific branches for which you want to receive notifications, ensuring you stay updated on crucial changes. Additionally, you can specify a custom username for the message sender, diverging from the default " github " option. Furthermore, you can set a distinctive image for the sender, adding a personal touch to the notifications. 2. GitHub Repository Configurations: To configure your GitHub repository and establish the necessary webhook for Slack integration, follow these technical steps: A. Accessing GitHub Repository Settings: Open the desired GitHub repository in your web browser. Locate and click on the " Settings " tab within the repository interface. From the settings menu, navigate to the " Webhooks " section, which allows you to manage webhook configurations for the repository. B. Adding a Webhook: Within the " Webhooks " section, click on the " Add Webhook " button. This action initiates the setup process for the webhook. C. Configuring the Webhook: In the webhook configuration screen, paste the previously copied Webhook URL from Slack into the " Payload URL " field. This URL establishes the connection between GitHub and Slack, enabling the transmission of commit message notifications. Change the content type to " application/json " to ensure that the data transmitted is in the appropriate format for integration with Slack. Enable SSL verification to maintain the security and integrity of the communication between GitHub and Slack. Choose the specific events for which you want to receive GitHub notifications on Slack. You can select " Commit Comments " to receive notifications specifically for commit messages, ensuring you stay informed about important code changes. Finally, click on the "Add Webhook " button to save and activate the configuration. 3. Verification and Usage: After configuring the integration between GitHub and Slack, it's essential to verify that the setup is working correctly is essential. Follow these steps to check the Slack integration and test its functionality: A. Checking Slack Integration: Return to the Slack channel that you designated for GitHub notifications (e.g., #random ). Look for an integration message confirming the successful setup. This message typically indicates that the GitHub app integration has been successfully connected to your Slack workspace. B. Testing the Integration: To ensure that the integration is functioning as expected, make a commit or push changes to your GitHub repository. This action triggers the generation of a commit message. Monitor the designated Slack channel ( #random , in this example) for a Slack message related to the commit. This message should be automatically generated and displayed in the channel, notifying team members about the recent commit and providing relevant information. Key takeaways from setting up GitHub commit messages on Slack: Seamless Collaboration: Integrating GitHub commit messages with Slack allows for real-time notifications, fostering better collaboration among team members. Stay Up-to-Date: By receiving notifications directly in Slack, team members can stay informed about commit activity without constantly checking GitHub. Streamlined Workflow : The integration streamlines the development workflow by centralizing communication and updates in one platform. Customization Options: Explore additional customization options, such as choosing specific branches for notifications and personalizing the sender's username and image. Enhance Productivity: Real-time notifications enable quick feedback and better coordination, increasing productivity. Incorporating GitHub commit message notifications into your Slack workspace is a valuable for improving communication and collaboration within your development team. Take advantage of the seamless integration and enjoy the benefits of staying informed and connected with the latest commit activity. Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://forem.com/wellallytech#main-content | wellallyTech - 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 DEV Community Close Follow User actions wellallyTech an AI-powered lifelong health data platform helping individuals and families track, analyze, and optimize their wellness. Joined Joined on Jan 23, 2025 Personal website https://www.wellally.tech/ More info about @wellallytech 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 46 posts published Comment 2 comments written Tag 0 tags followed State Management Simplified: Choosing Between Zustand and Redux for Health Apps wellallyTech wellallyTech wellallyTech Follow Jan 13 State Management Simplified: Choosing Between Zustand and Redux for Health Apps # javascript # architecture # reactnative # react Comments Add Comment 2 min read Want to connect with wellallyTech? Create an account to connect with wellallyTech. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Digital Gardens: Building a Private Space to Cultivate Your Mental Well-being wellallyTech wellallyTech wellallyTech Follow Jan 12 Digital Gardens: Building a Private Space to Cultivate Your Mental Well-being # nextjs # webdev # react # mentalhealth Comments Add Comment 2 min read 3D Anatomy Modeling: Build Interactive Features to Visualize Muscle Engagement wellallyTech wellallyTech wellallyTech Follow Jan 12 3D Anatomy Modeling: Build Interactive Features to Visualize Muscle Engagement # frontend # react # threejs # datavisualization Comments Add Comment 2 min read Next.js Performance: How to Optimize Your Blog’s Core Web Vitals for a Faster User Experience wellallyTech wellallyTech wellallyTech Follow Jan 11 Next.js Performance: How to Optimize Your Blog’s Core Web Vitals for a Faster User Experience # nextjs # performance # frontend # webdev Comments Add Comment 2 min read Real-Time Dashboards: Building a Heart Rate Monitor Enhances Remote Health Tracking wellallyTech wellallyTech wellallyTech Follow Jan 11 Real-Time Dashboards: Building a Heart Rate Monitor Enhances Remote Health Tracking # node # tutorial # fullstack # react Comments Add Comment 2 min read Component Libraries for Scaling Health Tech: Build a Consistent Dashboard with React, Storybook, and Tailwind wellallyTech wellallyTech wellallyTech Follow Jan 10 Component Libraries for Scaling Health Tech: Build a Consistent Dashboard with React, Storybook, and Tailwind # react # frontend # tailwindcss # storybook Comments Add Comment 2 min read Local AI Therapy: Fine-Tuning Mistral-7B on Apple Silicon with MLX & LoRA (M3 Max Performance!) 🚀 wellallyTech wellallyTech wellallyTech Follow Jan 10 Local AI Therapy: Fine-Tuning Mistral-7B on Apple Silicon with MLX & LoRA (M3 Max Performance!) 🚀 # ai # python # machinelearning # applesilicon Comments Add Comment 4 min read Offline-First PWAs: Build Resilient Apps That Never Lose Data wellallyTech wellallyTech wellallyTech Follow Jan 10 Offline-First PWAs: Build Resilient Apps That Never Lose Data # javascript # pwa # frontend # nextjs 3 reactions Comments 2 comments 2 min read Accessible Visuals: How Inclusive Charts Empower Patient Health wellallyTech wellallyTech wellallyTech Follow Jan 9 Accessible Visuals: How Inclusive Charts Empower Patient Health # frontend # react # a11y # healthtech Comments Add Comment 2 min read Wearable Tech Data + Better Health Insights + Building a Scalable IoT Pipeline on AWS wellallyTech wellallyTech wellallyTech Follow Jan 9 Wearable Tech Data + Better Health Insights + Building a Scalable IoT Pipeline on AWS # aws # architecture # serverless # iot Comments Add Comment 3 min read Health Data Visualization: Building High-Performance Charts for Millions of Points wellallyTech wellallyTech wellallyTech Follow Jan 8 Health Data Visualization: Building High-Performance Charts for Millions of Points # react # performance # dataviz # frontend Comments Add Comment 2 min read Real-Time Leaderboards: How to Boost Fitness Engagement Through Smart Data Architectures wellallyTech wellallyTech wellallyTech Follow Jan 8 Real-Time Leaderboards: How to Boost Fitness Engagement Through Smart Data Architectures # postgres # websockets # performance # node Comments Add Comment 2 min read Workout Plateaus: Predicting Strength Stalls for Smarter Training wellallyTech wellallyTech wellallyTech Follow Jan 7 Workout Plateaus: Predicting Strength Stalls for Smarter Training # python # datascience # fitness # forecasting Comments Add Comment 2 min read B2B Wellness Infrastructure: Securing Sensitive Data with Scalable Database Design wellallyTech wellallyTech wellallyTech Follow Jan 7 B2B Wellness Infrastructure: Securing Sensitive Data with Scalable Database Design # architecture # database # saas # postgres Comments Add Comment 2 min read HealthTech API Security: Protecting Patient Data with mTLS and OAuth 2.0 wellallyTech wellallyTech wellallyTech Follow Jan 6 HealthTech API Security: Protecting Patient Data with mTLS and OAuth 2.0 # architecture # security # api # backend Comments Add Comment 3 min read Voice Journaling for Mental Clarity: How to Build Your Own AI-Powered Reflection Tool wellallyTech wellallyTech wellallyTech Follow Jan 6 Voice Journaling for Mental Clarity: How to Build Your Own AI-Powered Reflection Tool # ai # openai # node # mentalhealth Comments Add Comment 2 min read Nutrition Chatbots + Evidence-Based AI: How to Build a Reliable Health Assistant wellallyTech wellallyTech wellallyTech Follow Jan 5 Nutrition Chatbots + Evidence-Based AI: How to Build a Reliable Health Assistant # ai # python # api # nutrition Comments Add Comment 2 min read Node.js Scaling: Ensure App Stability with a Resilient Microservices Transformation wellallyTech wellallyTech wellallyTech Follow Jan 5 Node.js Scaling: Ensure App Stability with a Resilient Microservices Transformation # architecture # node # kubernetes # scaling Comments Add Comment 2 min read Running Form Tech: Improve Your Gait With This DIY AI Analysis wellallyTech wellallyTech wellallyTech Follow Jan 5 Running Form Tech: Improve Your Gait With This DIY AI Analysis # opencv # python # computerscience # healthtech Comments Add Comment 2 min read Nutrition Data APIs: How to Build a High-Performance Search Engine for Wellness Apps wellallyTech wellallyTech wellallyTech Follow Jan 4 Nutrition Data APIs: How to Build a High-Performance Search Engine for Wellness Apps # redis # go # performance # backend Comments Add Comment 2 min read Chronotype Discovery: Using Python to Unlock Your Natural Sleep Patterns wellallyTech wellallyTech wellallyTech Follow Jan 4 Chronotype Discovery: Using Python to Unlock Your Natural Sleep Patterns # python # datascience # machinelearning # healthtech Comments Add Comment 2 min read AI Calorie Counting: How Computer Vision Is Revolutionizing Personal Nutrition wellallyTech wellallyTech wellallyTech Follow Jan 4 AI Calorie Counting: How Computer Vision Is Revolutionizing Personal Nutrition # ai # python # pytorch # computervision Comments Add Comment 2 min read Zero-Knowledge Security: Protecting Patient Privacy Through Client-Side Encryption wellallyTech wellallyTech wellallyTech Follow Jan 3 Zero-Knowledge Security: Protecting Patient Privacy Through Client-Side Encryption # privacy # security # react # encryption Comments Add Comment 3 min read Fitness App Architecture: How Asynchronous Processing Creates a Smoother User Experience wellallyTech wellallyTech wellallyTech Follow Jan 3 Fitness App Architecture: How Asynchronous Processing Creates a Smoother User Experience # node # architecture # rabbitmq # backend Comments 2 comments 2 min read FHIR Integration: Build Modern Healthcare Apps Using Python and FastAPI wellallyTech wellallyTech wellallyTech Follow Jan 3 FHIR Integration: Build Modern Healthcare Apps Using Python and FastAPI # python # api # fastapi # healthtech Comments Add Comment 2 min read AI Meal Planning: How to build structured wellness tools with Next.js and LangChain wellallyTech wellallyTech wellallyTech Follow Jan 2 AI Meal Planning: How to build structured wellness tools with Next.js and LangChain # ai # nextjs # langchain # healthtech Comments Add Comment 3 min read React State Management: Choosing the Right Tools for Your Health Dashboard wellallyTech wellallyTech wellallyTech Follow Dec 31 '25 React State Management: Choosing the Right Tools for Your Health Dashboard # javascript # tutorial # react # statemanagement Comments Add Comment 2 min read Wearable Data Security: Protect User Privacy by Building a Secure Health Data Pipeline wellallyTech wellallyTech wellallyTech Follow Dec 30 '25 Wearable Data Security: Protect User Privacy by Building a Secure Health Data Pipeline # security # reactnative # fullstack # healthtech Comments Add Comment 2 min read Wellness Tech Architecture: How Microservices Help Your App Grow Seamlessly wellallyTech wellallyTech wellallyTech Follow Dec 29 '25 Wellness Tech Architecture: How Microservices Help Your App Grow Seamlessly # architecture # microservices # refactorit # healthtech Comments Add Comment 2 min read React Native HealthKit: How to Build a Seamless Health Dashboard wellallyTech wellallyTech wellallyTech Follow Dec 29 '25 React Native HealthKit: How to Build a Seamless Health Dashboard # reactnative # healthtech # ios # mobiledev Comments Add Comment 2 min read Habit Consistency + Digital Wellness: Building a Custom React Goal Streak wellallyTech wellallyTech wellallyTech Follow Dec 29 '25 Habit Consistency + Digital Wellness: Building a Custom React Goal Streak # react # javascript # tutorial # webdev Comments Add Comment 2 min read Personal Productivity: How to Forecast Your Peak Focus Hours with Data wellallyTech wellallyTech wellallyTech Follow Dec 28 '25 Personal Productivity: How to Forecast Your Peak Focus Hours with Data # tutorial # python # machinelearning # datascience Comments Add Comment 2 min read Cognitive Distortions: Use AI to Identify and Challenge Negative Thinking wellallyTech wellallyTech wellallyTech Follow Dec 27 '25 Cognitive Distortions: Use AI to Identify and Challenge Negative Thinking # ai # nlp # python # machinelearning Comments Add Comment 2 min read Oura Integration: Build High-Performance Health Apps with Next.js and React Query wellallyTech wellallyTech wellallyTech Follow Dec 27 '25 Oura Integration: Build High-Performance Health Apps with Next.js and React Query # react # nextjs # api # healthtech Comments Add Comment 2 min read Wearable Data Performance: How to Build Fluid Health Dashboards wellallyTech wellallyTech wellallyTech Follow Dec 26 '25 Wearable Data Performance: How to Build Fluid Health Dashboards # react # performance # javascript # healthtech Comments Add Comment 2 min read Scalable Wellness Data: Use the CQRS Pattern to Build Faster Health Dashboards wellallyTech wellallyTech wellallyTech Follow Dec 26 '25 Scalable Wellness Data: Use the CQRS Pattern to Build Faster Health Dashboards # architecture # systemdesign # cqrs # database Comments Add Comment 3 min read Wearable Data Pipelines: Scaling Real-Time Health Insights for Connected Devices wellallyTech wellallyTech wellallyTech Follow Dec 26 '25 Wearable Data Pipelines: Scaling Real-Time Health Insights for Connected Devices # systemdesign # architecture # kafka # healthtech Comments Add Comment 2 min read Web Bluetooth Guide: How to Build a Real-Time Heart Rate Dashboard wellallyTech wellallyTech wellallyTech Follow Dec 25 '25 Web Bluetooth Guide: How to Build a Real-Time Heart Rate Dashboard # react # javascript # iot # webbluetooth Comments Add Comment 2 min read Mental Health Tech: How to Build Your Own Personalized Resource Recommender wellallyTech wellallyTech wellallyTech Follow Dec 25 '25 Mental Health Tech: How to Build Your Own Personalized Resource Recommender # ai # python # machinelearning # healthtech Comments Add Comment 2 min read Data Security Simplified: Building Your HIPAA-Compliant Data Lake on AWS wellallyTech wellallyTech wellallyTech Follow Dec 25 '25 Data Security Simplified: Building Your HIPAA-Compliant Data Lake on AWS # aws # security # architecture # hipaa Comments Add Comment 3 min read Health Data Visualization: Take Control of Your Wellness Metrics with a Custom PWA wellallyTech wellallyTech wellallyTech Follow Dec 24 '25 Health Data Visualization: Take Control of Your Wellness Metrics with a Custom PWA # react # nextjs # datavisualization # ai Comments Add Comment 2 min read Digital Wellness: Building a Proactive Chatbot for Stress Support wellallyTech wellallyTech wellallyTech Follow Dec 24 '25 Digital Wellness: Building a Proactive Chatbot for Stress Support # ai # python # project # healthtech Comments Add Comment 2 min read Developer Burnout: How Your Git History Can Improve Your Well-Beinga wellallyTech wellallyTech wellallyTech Follow Dec 24 '25 Developer Burnout: How Your Git History Can Improve Your Well-Beinga # python # datascience # mentalhealth # machinelearning Comments Add Comment 2 min read Activity Rings: Build Your Own Health Dashboard with React and SVG wellallyTech wellallyTech wellallyTech Follow Dec 23 '25 Activity Rings: Build Your Own Health Dashboard with React and SVG # ai # frontend # animation # datavisualization Comments Add Comment 2 min read Gamified Fitness UI: How to Turn Health Data Into Motivation wellallyTech wellallyTech wellallyTech Follow Dec 10 '25 Gamified Fitness UI: How to Turn Health Data Into Motivation # ai # react # reactnative Comments Add Comment 5 min read The Dashboard Upgrade: Why "Normal" Labs Are Killing You wellallyTech wellallyTech wellallyTech Follow Dec 10 '25 The Dashboard Upgrade: Why "Normal" Labs Are Killing You # ai # health Comments Add Comment 5 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/implementing-app-inbox-in-next-js-application-as-a-developer | Implementing App Inbox in Next.js Application as a Developer Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Inapp Inbox Notifications Implementing App Inbox in Next.js Application as a Developer Anjali Arya • February 5, 2025 TABLE OF CONTENTS A Next.js app inbox notification center serves as a centralized hub where users can view all their notifications at any time, improving user engagement and ensuring no crucial update goes unnoticed. In this tutorial, we will walk you through the process of implementing a robust notification center in a Next.js application, covering everything from setting up the backend to creating a user-friendly notification feed on the frontend. By the end of this guide, you will have a fully functional notification system in your Next.js app, complete with real-time updates. This implementation will not only enhance your app's user experience but also provide a scalable solution for managing notifications. Key topics covered in this article include: Setting up a new Next.js project for your notification center. Building the backend with Node.js and Express to handle notifications. Creating the frontend notification widget and integrating it with the backend. Implementing real-time updates to keep your notification feed current. Styling the notification UI to ensure it is responsive and user-friendly. Whether you're referring to it as an in-app inbox, notification widget, or alert center, the concepts and steps remain consistent. Let's dive in and start building your Next.js notification center! Prerequisite Working knowledge in Next.js Account on SuprSend along with the secret key and token Next.js application Where will we build our app inbox in Next.js? For this tutorial, we have created a demo Next.js project, called as b2b2c-freight_company which is available on Github. We have also deployed the application on Vercel, so you can access the notification feed in Next.js in real time here Freight B2B2C App (b2b2c-freight-company.vercel.app) Building a real-time notification center in Next.js Let’s get started! Step 1: Creating account on SuprSend Start by creating a new account on SuprSend . Once you pass the onboarding process, you can find head to Developers → API Keys in the sidepanel. You will find your Workspace Key and Workspace Secret here. Step 2: Finding the right place for app inbox in your application Usually the app inbox is situated on the header along with other menu options. However in some cases, businesses can also give it as an option in side panel for a full-page notification center, similar to LinkedIn. In our case, we will be implementing the notification center in our navigation header. You can find the relevant code here b2b2c-freight_company/src/app/page.tsx at master Step 3: Installation and Integration of SuprSendInbox in Next.js 1. Install the SuprSend App Inbox Package First, you need to install the SuprSend app inbox package. Open your terminal and run the following command: Copy Code npm install @suprsend/react-inbox 2. Import Necessary Packages Next, import the necessary CSS for toast notifications in your code where you want to showcase the app inbox component: Copy Code import 'react-toastify/dist/ReactToastify.css'; 3. Disable Server-Side Rendering for SuprSend To optimize the initial loading and ensure the SuprSend inbox functions correctly (as it needs access to browser-specific APIs), you should disable server-side rendering (SSR) for the SuprSend component. Use the following code: Copy Code import dynamic from 'next/dynamic'; // Dynamically import the SuprSendInbox component with SSR disabled const SuprSendInbox = dynamic(() => import('@suprsend/react-inbox'), { ssr: false }); This code snippet uses next/dynamic to dynamically import the SuprSendInbox component. The { ssr: false } option ensures that the component is only rendered on the client side, which is crucial because SuprSend relies on browser-specific APIs that are not available during server-side rendering. 4. Place the SuprSendInbox Component Once the SuprSendInbox component is imported, you can place it within your navigation bar or any other desired location. You also need to define the workspace keys. Here's how you can add it to a fixed position at the top right of your page: Copy Code const workspaceKey = process.env.NEXT_PUBLIC_SUPRSEND_WORKSPACE_KEY || ''; const subscriberId = process.env.NEXT_PUBLIC_SUPRSEND_SUBSCRIBER_ID || ''; const distinctId = process.env.NEXT_PUBLIC_SUPRSEND_DISTINCT_ID || ''; export default function HomePage() { // Your component state and logic here return ( <div class="flex min-h-screen bg-gray-900 text-white"> {/* SuprSend Inbox */} <div class="fixed top-0 right-0 m-4 z-50"> <SuprSendInbox workspaceKey={workspaceKey} subscriberId={subscriberId} distinctId={distinctId} themeType="dark" /> </div> {/* Other page content here */} </div> ); } In this example, the SuprSendInbox component is placed inside a div with className="fixed top-0 right-0 m-4 z-50", which ensures it stays fixed at the top right corner of the page. 5. Styling the App Inbox Component If you are using Tailwind CSS, you can easily style the app inbox component. To integrate the inbox seamlessly into your navigation panel, place the component directly inside the navigation <div> class. Here’s an example showing how to integrate and customize the component: Copy Code <div class="fixed top-0 right-0 m-4 z-50"> <SuprSendInbox workspaceKey={workspaceKey} subscriberId={subscriberId} distinctId={distinctId} themeType="dark" /> </div> The SuprSend app inbox provides various customization options through props: workspaceKey: The key associated with your SuprSend workspace. subscriberId: The identifier for the subscriber. distinctId: A unique identifier for distinct user tracking. themeType: The theme of the inbox, e.g., "dark" or "light". In this application we will use dark theme to match our application theme. By adjusting these props, you can tailor the appearance and behavior of the app inbox component to fit your application’s design and functionality requirements. Additionally, you can modify the styling using Tailwind CSS classes to ensure consistency with your overall UI. SuprSend provides a lot of customisations in terms of design inherently. You can access everything by just passing a prop to the app inbox component. All details are in this documentation page Customize Inbox (suprsend.com) Step 4: Setting env variables Environment Variables : Ensure you have the environment variables set in your .env file: Copy Code NEXT_PUBLIC_SUPRSEND_WORKSPACE_KEY=your_workspace_key NEXT_PUBLIC_SUPRSEND_SUBSCRIBER_ID=your_subscriber_id NEXT_PUBLIC_SUPRSEND_DISTINCT_ID=your_distinct_id Error Handling : Implement error handling for the fetch request in the handleSubmit function to provide feedback to the user if the login fails. Component State Management : Manage the state using React's useState hook to handle form inputs and potential error messages. Responsive Design : Use Tailwind CSS to ensure the component is responsive and adjusts to different screen sizes. Step 5: Setting the triggers for notifications By now, your app inbox is all set and visible. Now you need to configure triggers for sending notifications. It should be passed as an event to SuprSend. You can use any backend SDK to trigger events to app inbox. Let’s use Node SDK in this application. You can send and trigger events by following this documentation Send and Track Events (suprsend.com) We will cover the trigger part in our next guide. Key Points Make sure server-side rendering is disabled, as the app inbox works only on the client-side. To generate the subscriber key, you need to do the HMAC authentication from any of our backend SDKs. Integrating an app inbox notification center into your Next.js application significantly enhances user engagement and ensures that important messages are never missed. By following the steps outlined in this guide, you can effectively implement the SuprSend app inbox, leveraging its dynamic import and client-side rendering capabilities to optimize performance and functionality. This approach not only streamlines the notification process but also offers extensive customization options to fit seamlessly within your existing design. With these tools, your application will provide a more interactive and satisfying user experience, keeping your users informed and engaged at all times. Now, you can focus on building more features, knowing that your notification system is robust and efficient. Happy coding! Share this blog on: Written by: Anjali Arya Product & Analytics, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://dev.to/vaibhavg | Vaibhav Gupta - 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 Vaibhav Gupta 404 bio not found Joined Joined on Jun 6, 2025 More info about @vaibhavg 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 Organizations Tailwindadmin Shadcn Space Post 32 posts published Comment 6 comments written Tag 0 tags followed Building a React Dashboard in 2026: What Actually Matters (From a Dev Perspective) Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Jan 12 Building a React Dashboard in 2026: What Actually Matters (From a Dev Perspective) # webdev # react # opensource # frontend Comments Add Comment 2 min read Want to connect with Vaibhav Gupta? Create an account to connect with Vaibhav Gupta. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in 11+ Best Open Source Shadcn Dashboard Templates for 2026 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow for Tailwindadmin Jan 6 11+ Best Open Source Shadcn Dashboard Templates for 2026 # webdev # opensource # react # nextjs 2 reactions Comments Add Comment 7 min read Introducing Tailwindadmin - Open Source Shadcn Admin Dashboard for Developers Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Jan 3 Introducing Tailwindadmin - Open Source Shadcn Admin Dashboard for Developers # webdev # shadcn # react # nextjs Comments Add Comment 3 min read MaterialM Open Source Vuetify NuxtJs Admin Dashboard Template - by WrapPixel Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Dec 3 '25 MaterialM Open Source Vuetify NuxtJs Admin Dashboard Template - by WrapPixel # webdev # nuxt # vue # opensource Comments Add Comment 3 min read MaterialM Free VueJS Vuetify Admin Dashboard Template - by WrapPixel Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 27 '25 MaterialM Free VueJS Vuetify Admin Dashboard Template - by WrapPixel # webdev # vue # vuetify # opensource Comments Add Comment 3 min read MaterialM Open Source React Tailwind Admin Dashboard Template - by WrapPixel Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 25 '25 MaterialM Open Source React Tailwind Admin Dashboard Template - by WrapPixel # webdev # opensource # react # tailwindcss Comments Add Comment 4 min read Top Nextjs Black Friday Deals 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 21 '25 Top Nextjs Black Friday Deals 2025 # webdev # nextjs # opensource # blackfriday2025 Comments Add Comment 2 min read Spike Open Source Vuejs Vuetify Admin Dashboard Template - by WrapPixel Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 20 '25 Spike Open Source Vuejs Vuetify Admin Dashboard Template - by WrapPixel # webdev # vue # vuetify # opensource Comments Add Comment 4 min read Spike Open Source React Tailwind Admin Dashboard Template - by WrapPixel Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 19 '25 Spike Open Source React Tailwind Admin Dashboard Template - by WrapPixel # webdev # react # tailwindcss # opensource Comments Add Comment 3 min read Top Reactjs Black Friday Deals 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 18 '25 Top Reactjs Black Friday Deals 2025 # webdev # react # nextjs # blackfriday Comments Add Comment 3 min read The Best Admin Dashboard Templates for 2025: Boost Your Development Projects with These Top Picks Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Nov 12 '25 The Best Admin Dashboard Templates for 2025: Boost Your Development Projects with These Top Picks # webdev # opensource # react # nextjs 1 reaction Comments Add Comment 4 min read Modernize Open Source Nuxt.js Admin Dashboard: A Comprehensive Overview Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Oct 11 '25 Modernize Open Source Nuxt.js Admin Dashboard: A Comprehensive Overview # webdev # nuxt # opensource # vue Comments Add Comment 3 min read Best Next.js Admin Dashboard Templates for Developers Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Oct 9 '25 Best Next.js Admin Dashboard Templates for Developers # webdev # nextjs # react # tailwindcss Comments Add Comment 6 min read Modernize Open Source Vuejs Vuetify Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Oct 7 '25 Modernize Open Source Vuejs Vuetify Admin Dashboard Template # webdev # vue # opensource # development Comments Add Comment 4 min read Top 10 Admin Templates Under $50: A Developer’s Guide Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Oct 6 '25 Top 10 Admin Templates Under $50: A Developer’s Guide # webdev # development # react # nextjs Comments Add Comment 6 min read MatDash Open Source Vuejs Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Oct 1 '25 MatDash Open Source Vuejs Admin Dashboard Template # webdev # opensource # vue Comments Add Comment 3 min read Top 5 Free Admin Dashboard Templates for 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 29 '25 Top 5 Free Admin Dashboard Templates for 2025 # webdev # opensource # nextjs # tailwindcss Comments Add Comment 4 min read Modernize Open Source Angular Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 26 '25 Modernize Open Source Angular Admin Dashboard Template # webdev # angular # opensource # development Comments Add Comment 3 min read Top 10 Modern Dashboard Design for 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 25 '25 Top 10 Modern Dashboard Design for 2025 # webdev # development # design # opensource Comments Add Comment 4 min read MatDash Open Source Tailwind React Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 24 '25 MatDash Open Source Tailwind React Admin Dashboard Template # webdev # react # tailwindcss # opensource Comments Add Comment 3 min read Top 10 Next.js Admin Dashboard Templates for Developers Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 20 '25 Top 10 Next.js Admin Dashboard Templates for Developers # webdev # nextjs # opensource # tailwindcss Comments Add Comment 6 min read Modernize Open Source Bootstrap 5 Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 19 '25 Modernize Open Source Bootstrap 5 Admin Dashboard Template # webdev # bootstrap # opensource Comments Add Comment 4 min read Top 5 React Admin Dashboards for 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 18 '25 Top 5 React Admin Dashboards for 2025 # webdev # react # tailwindcss # opensource 1 reaction Comments Add Comment 4 min read MatDash Open Source Next.js Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 17 '25 MatDash Open Source Next.js Admin Dashboard Template # webdev # nextjs # tailwindcss # opensource 2 reactions Comments Add Comment 3 min read Top 10 Angular Admin Dashboard Templates to Save Time (Free & Paid) Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 15 '25 Top 10 Angular Admin Dashboard Templates to Save Time (Free & Paid) # angular # webdev # opensource # resources Comments Add Comment 6 min read Modernize Open Source React Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 12 '25 Modernize Open Source React Admin Dashboard Template # webdev # opensource # react # javascript Comments Add Comment 3 min read Best Tailwind CSS Dashboard Templates for 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 11 '25 Best Tailwind CSS Dashboard Templates for 2025 # webdev # tailwindcss # opensource # nextjs 1 reaction Comments Add Comment 7 min read Key Features of a Good Admin Dashboard Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 10 '25 Key Features of a Good Admin Dashboard # webdev # nextjs # tailwindcss # tutorial Comments Add Comment 3 min read MatDash Open Source Bootstrap 5 Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 9 '25 MatDash Open Source Bootstrap 5 Admin Dashboard Template # webdev # bootstrap # opensource # html 1 reaction Comments Add Comment 2 min read Top HTML Admin Templates Free Download for 2025 Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 8 '25 Top HTML Admin Templates Free Download for 2025 # webdev # javascript # html # opensource Comments Add Comment 5 min read Modernize Open Source Next.js Admin Dashboard Template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 6 '25 Modernize Open Source Next.js Admin Dashboard Template # webdev # javascript # programming # opensource 1 reaction Comments Add Comment 2 min read How to choose the right admin dashboard template Vaibhav Gupta Vaibhav Gupta Vaibhav Gupta Follow Sep 5 '25 How to choose the right admin dashboard template # webdev # react # nextjs # javascript Comments Add Comment 5 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:49:23 |
https://aistudio.google.com/prompts/new_chat?utm_source=pwa&utm_medium=homescreen&lfhs=2 | :root{--gm3-sys-color-on-surface-rgb:31,31,31}@media screen and (prefers-color-scheme:dark){:root{--gm3-sys-color-on-surface-rgb:227,227,227}}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.q4Wquf,.nfoC7c{display:block;height:25vh;position:relative}@media (min-width:600px){.q4Wquf,.nfoC7c{height:150px}}.q4Wquf.Irjbwb{height:auto}@media screen and (prefers-color-scheme:dark){.q4Wquf:not(.GtvzYd){display:none}}.nfoC7c{margin:0;overflow:hidden}.PwpMUe,.lVUmD{display:block;height:100%;margin:0 auto;width:100%}.St9mde{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.St9mde{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.PwpMUe,.lVUmD,.St9mde{-o-object-fit:contain;object-fit:contain}.wsArZ[data-ss-mode="1"] .q4Wquf,.wsArZ[data-ss-mode="1"] .St9mde{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .St9mde{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .q4Wquf,.NQ5OL .St9mde{height:auto;width:100%}.NQ5OL .St9mde{max-width:400px}}.q4Wquf.NWba7e,.q4Wquf.NWba7e .St9mde{height:auto}.q4Wquf.NWba7e .St9mde{height:auto;max-width:312px;width:100%}.q4Wquf.NWba7e.zpCp3 .St9mde{max-width:unset}.q4Wquf.IiQozc .St9mde{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.q4Wquf.Irjbwb .St9mde{height:auto;width:100%}.q4Wquf.EEeaqf .St9mde{max-height:144px;max-width:144px}.SnAaEd{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.SnAaEd{display:none}}.SnAaEd::after,.SnAaEd::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.SnAaEd::after,.SnAaEd::before{width:150px}}.SnAaEd::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.SnAaEd::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .SnAaEd~.St9mde{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .SnAaEd~.St9mde{width:auto}}.RHNWk .St9mde{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .RHNWk .St9mde{width:115px}}.cf660d .St9mde{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.tUhwwc .St9mde{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.Jkvqxd .St9mde{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.onc8Ic .St9mde{-webkit-transform:translate(var( --c-ps-s,24px ),0);-ms-transform:translate(var( --c-ps-s,24px ),0);transform:translate(var( --c-ps-s,24px ),0)}.WA89Yb .St9mde{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .XEN8Yb .St9mde{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .XEN8Yb .St9mde{max-width:115px}}@media (min-width:1240px) and (orientation:landscape),all and (min-width:1600px){.KyPKed .NQ5OL .XEN8Yb .St9mde{max-width:115px}}.IsSr6b .St9mde{max-width:300px}.mmskdd .St9mde{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@keyframes quantumWizBoxInkSpread{0%{-webkit-transform:translate(-50%,-50%) scale(.2);transform:translate(-50%,-50%) scale(.2)}100%{-webkit-transform:translate(-50%,-50%) scale(2.2);transform:translate(-50%,-50%) scale(2.2)}}@-webkit-keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@keyframes quantumWizIconFocusPulse{0%{-webkit-transform:translate(-50%,-50%) scale(1.5);transform:translate(-50%,-50%) scale(1.5);opacity:0}100%{-webkit-transform:translate(-50%,-50%) scale(2);transform:translate(-50%,-50%) scale(2);opacity:1}}@-webkit-keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkSpread{0%{-webkit-transform:scale(1.5);transform:scale(1.5);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@-webkit-keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}@keyframes quantumWizRadialInkFocusPulse{0%{-webkit-transform:scale(2);transform:scale(2);opacity:0}100%{-webkit-transform:scale(2.5);transform:scale(2.5);opacity:1}}:root{--wf-tfs:calc(var(--c-tfs,32)/16*1rem);--wf-tfs-bp2:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp3:calc(var(--c-tfs,36)/16*1rem);--wf-tfs-bp5:calc(var(--c-tfs,44)/16*1rem);--wf-stfs:calc(var(--c-stfs,16)/16*1rem);--wf-stfs-bp5:calc(var(--c-stfs,16)/16*1rem)}:root{--wf-harmonize-filter-light:none;--wf-harmonize-filter-dark:none}.Dzz9Db,.GpMPBe{display:block;height:25vh;position:relative}@media (min-width:600px){.Dzz9Db,.GpMPBe{height:150px}}@media screen and (prefers-color-scheme:dark){.Dzz9Db:not(.GtvzYd){display:none}}.Dzz9Db.Irjbwb{height:auto}.GpMPBe{margin:0;overflow:hidden}.UFQPDd,.JNOvdd{display:block;height:100%;margin:0 auto;-o-object-fit:contain;object-fit:contain;width:100%}.f4ZpM{display:block;-webkit-filter:var(--wf-harmonize-filter-light);filter:var(--wf-harmonize-filter-light);height:100%;max-width:100%;min-height:110px;position:relative;-webkit-transform:translate(-43%,-3%);-ms-transform:translate(-43%,-3%);transform:translate(-43%,-3%);width:auto;z-index:3}@media screen and (prefers-color-scheme:dark){.f4ZpM{-webkit-filter:var(--wf-harmonize-filter-dark);filter:var(--wf-harmonize-filter-dark)}}.wsArZ[data-ss-mode="1"] .Dzz9Db,.wsArZ[data-ss-mode="1"] .f4ZpM{height:auto;width:100%}.wsArZ[data-ss-mode="1"] .f4ZpM{max-width:400px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .Dzz9Db,.NQ5OL .f4ZpM{height:auto;width:100%}.NQ5OL .f4ZpM{max-width:400px}}.Dzz9Db.utFBGf,.Dzz9Db.utFBGf .f4ZpM{height:auto}.Dzz9Db.utFBGf .f4ZpM{height:auto;max-width:312px;width:100%}.Dzz9Db.utFBGf.zpCp3 .f4ZpM{max-width:unset}.Dzz9Db.IiQozc .f4ZpM{margin:0 auto;-webkit-transform:none;-ms-transform:none;transform:none}.Dzz9Db.Irjbwb .f4ZpM{height:auto;width:100%}.Dzz9Db.EEeaqf .f4ZpM{max-height:144px;max-width:144px}.nPt1pc{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(233,233,233,0)),color-stop(62.22%,rgba(233,233,233,0)),color-stop(40.22%,rgb(233,233,233)),to(rgba(233,233,233,0)));background-image:-webkit-linear-gradient(top,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);background-image:linear-gradient(to bottom,rgba(233,233,233,0) 0,rgba(233,233,233,0) 62.22%,rgb(233,233,233) 40.22%,rgba(233,233,233,0) 100%);height:100%;left:0;overflow:hidden;position:absolute;right:0;top:0;z-index:2}@media screen and (prefers-color-scheme:dark){.nPt1pc{display:none}}.nPt1pc::after,.nPt1pc::before{content:"";display:block;height:100%;min-width:110px;position:absolute;right:-10%;-webkit-transform:rotate(-104deg);-ms-transform:rotate(-104deg);transform:rotate(-104deg);width:25vh;z-index:2}@media (min-width:600px){.nPt1pc::after,.nPt1pc::before{width:150px}}.nPt1pc::before{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(243,243,243,0)),to(rgba(243,243,243,.9)));background-image:-webkit-linear-gradient(top,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);background-image:linear-gradient(to bottom,rgba(243,243,243,0) 0,rgba(243,243,243,.9) 100%);bottom:-10%}.nPt1pc::after{background-image:-webkit-gradient(linear,left top,left bottom,from(rgba(255,255,255,0)),to(rgba(255,255,255,.9)));background-image:-webkit-linear-gradient(top,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);background-image:linear-gradient(to bottom,rgba(255,255,255,0) 0,rgba(255,255,255,.9) 100%);bottom:-80%}.wsArZ[data-ss-mode="1"] .nPt1pc~.f4ZpM{width:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .nPt1pc~.f4ZpM{width:auto}}.ZS7CGc .f4ZpM{height:auto}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .ZS7CGc .f4ZpM{width:115px}}.qiRZ5e .f4ZpM{-webkit-transform:translate(-9%,-3%);-ms-transform:translate(-9%,-3%);transform:translate(-9%,-3%)}.vIv7Gf .f4ZpM{margin:auto;max-height:230px;right:0;top:-3%;-webkit-transform:none;-ms-transform:none;transform:none}.nvYXVd .f4ZpM{-webkit-transform:translate(9%,-3%);-ms-transform:translate(9%,-3%);transform:translate(9%,-3%)}.uOhnzd .f4ZpM{-webkit-transform:translate(24px,0);-ms-transform:translate(24px,0);transform:translate(24px,0)}.MsYMaf .f4ZpM{-webkit-transform:translate(0,0);-ms-transform:translate(0,0);transform:translate(0,0)}.wsArZ[data-ss-mode="1"] .YIi9qf .f4ZpM{max-width:115px}@media (min-width:600px) and (orientation:landscape),all and (min-width:1600px){.NQ5OL .YIi9qf .f4ZpM{max-width:115px}}.QG3Xbe .f4ZpM{max-width:300px}.F6gtje .f4ZpM{-webkit-transform:none;-ms-transform:none;transform:none}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe{font-size:24px;width:48px;height:48px;padding:12px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-Jh9lGc{width:40px;height:40px;margin-top:4px;margin-bottom:4px;margin-right:4px;margin-left:4px}.VfPpkd-Bz112c-LgbsSe.VfPpkd-Bz112c-LgbsSe-OWXEXe-e5LLRc-SxQuSe .VfPpkd-Bz112c-J1Ukfc-LhBDec{max-height:40px;max-width:40px}.VfPpkd-Bz112c-LgbsSe:disabled{color:rgba(0,0,0,.38);color:var(--mdc-theme-text-disabled-on-light,rgba(0,0,0,.38))}.VfPpkd-Bz112c-LgbsSe svg,.VfPpkd-Bz112c-LgbsSe img{width:24px;height:24px}.VfPpkd-Bz112c-LgbsSe{display:inline-block;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;border:none;outline:none;background-color:transparent;fill:currentColor;color:inherit;text-decoration:none;cursor:pointer;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;z-index:0;overflow:visible}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-RLmnJb{position:absolute;top:50%;height:48px;left:50%;width:48px;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-J1Ukfc-LhBDec,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-J1Ukfc-LhBDec{display:block}}.VfPpkd-Bz112c-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-Bz112c-LgbsSe[hidden]{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-KVuj8d-Q3DXx{-webkit-box-align:center;-webkit-align-items:center;align-items:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center}.VfPpkd-Bz112c-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:100%;width:100%;display:none}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-Bz112c-J1Ukfc-LhBDec::after{border-color:CanvasText}}.VfPpkd-Bz112c-kBDsod{display:inline-block}.VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd,.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod{display:none}.VfPpkd-Bz112c-LgbsSe-OWXEXe-IT5dJd .VfPpkd-Bz112c-kBDsod.VfPpkd-Bz112c-kBDsod-OWXEXe-IT5dJd{display:inline-block}.VfPpkd-Bz112c-mRLv6{height:100%;left:0;outline:none;position:absolute;top:0;width:100%}.VfPpkd-Bz112c-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Bz112c-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{top:0;left:0;width:100%;height:100%}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Bz112c-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-Bz112c-LgbsSe:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-Bz112c-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.VfPpkd-Bz112c-LgbsSe:disabled:hover .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Bz112c-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Bz112c-Jh9lGc::before,.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Bz112c-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-Bz112c-LgbsSe:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Bz112c-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.VfPpkd-Bz112c-LgbsSe .VfPpkd-Bz112c-Jh9lGc{height:100%;left:0;pointer-events:none;position:absolute;top:0;width:100%;z-index:-1}.VfPpkd-dgl2Hf-ppHlrf-sM5MNb{display:inline}.VfPpkd-LgbsSe{position:relative;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-box-pack:center;-webkit-justify-content:center;justify-content:center;-webkit-box-sizing:border-box;box-sizing:border-box;min-width:64px;border:none;outline:none;line-height:inherit;-webkit-user-select:none;-moz-user-select:none;-ms-user-select:none;user-select:none;-webkit-appearance:none;overflow:visible;vertical-align:middle;background:transparent}.VfPpkd-LgbsSe .VfPpkd-BFbNVe-bF1uUb{width:100%;height:100%;top:0;left:0}.VfPpkd-LgbsSe::-moz-focus-inner{padding:0;border:0}.VfPpkd-LgbsSe:active{outline:none}.VfPpkd-LgbsSe:hover{cursor:pointer}.VfPpkd-LgbsSe:disabled{cursor:default;pointer-events:none}.VfPpkd-LgbsSe[hidden]{display:none}.VfPpkd-LgbsSe .VfPpkd-kBDsod{margin-left:0;margin-right:8px;display:inline-block;position:relative;vertical-align:top}[dir=rtl] .VfPpkd-LgbsSe .VfPpkd-kBDsod,.VfPpkd-LgbsSe .VfPpkd-kBDsod[dir=rtl]{margin-left:8px;margin-right:0}.VfPpkd-LgbsSe .VfPpkd-UdE5de-uDEFge{font-size:0;position:absolute;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);top:50%;left:50%;line-height:normal}.VfPpkd-LgbsSe .VfPpkd-vQzf8d{position:relative}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{pointer-events:none;border:2px solid transparent;border-radius:6px;-webkit-box-sizing:content-box;box-sizing:content-box;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px);display:none}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-color:CanvasText}}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{content:"";border:2px solid transparent;border-radius:8px;display:block;position:absolute;top:50%;left:50%;-webkit-transform:translate(-50%,-50%);-ms-transform:translate(-50%,-50%);transform:translate(-50%,-50%);height:calc(100% + 4px);width:calc(100% + 4px)}@media screen and (forced-colors:active){.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-color:CanvasText}}@media screen and (forced-colors:active){.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-J1Ukfc-LhBDec,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-J1Ukfc-LhBDec{display:block}}.VfPpkd-LgbsSe .VfPpkd-RLmnJb{position:absolute;top:50%;height:48px;left:0;right:0;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%)}.VfPpkd-vQzf8d+.VfPpkd-kBDsod{margin-left:8px;margin-right:0}[dir=rtl] .VfPpkd-vQzf8d+.VfPpkd-kBDsod,.VfPpkd-vQzf8d+.VfPpkd-kBDsod[dir=rtl]{margin-left:0;margin-right:8px}svg.VfPpkd-kBDsod{fill:currentColor}.VfPpkd-LgbsSe-OWXEXe-dgl2Hf{margin-top:6px;margin-bottom:6px}.VfPpkd-LgbsSe{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;text-decoration:none}.VfPpkd-LgbsSe{padding:0 8px 0 8px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{-webkit-transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1);transition:box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);padding:0 16px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 12px 0 16px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 16px 0 12px}.VfPpkd-LgbsSe-OWXEXe-INsAgc{border-style:solid;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-style:solid;border-color:transparent}.VfPpkd-LgbsSe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{z-index:0}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-Jh9lGc::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-Jh9lGc::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d .VfPpkd-Jh9lGc::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-Jh9lGc{position:absolute;-webkit-box-sizing:content-box;box-sizing:content-box;overflow:hidden;z-index:0;top:0;left:0;bottom:0;right:0}.VfPpkd-LgbsSe{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-text-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-k8QpJ:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-k8QpJ.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-filled-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-k8QpJ .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;-webkit-box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12);box-shadow:0 3px 1px -2px rgba(0,0,0,.2),0 2px 2px 0 rgba(0,0,0,.14),0 1px 5px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{background-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled){color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::before{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc::after{background-color:#fff}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.08}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-protected-button-pressed-state-layer-opacity,0.24)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-MV7yeb.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(.VfPpkd-ksKsZd-mWPk3d):focus{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:hover{-webkit-box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12);box-shadow:0 2px 4px -1px rgba(0,0,0,.2),0 4px 5px 0 rgba(0,0,0,.14),0 1px 10px 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:not(:disabled):active{-webkit-box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12);box-shadow:0 5px 5px -3px rgba(0,0,0,.2),0 8px 10px 1px rgba(0,0,0,.14),0 3px 14px 2px rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-MV7yeb:disabled{-webkit-box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12);box-shadow:0 0 0 0 rgba(0,0,0,.2),0 0 0 0 rgba(0,0,0,.14),0 0 0 0 rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc{font-family:Roboto,sans-serif;font-size:.875rem;letter-spacing:.0892857143em;font-weight:500;text-transform:uppercase;height:36px;border-radius:4px;padding:0 15px 0 15px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{color:rgba(0,0,0,.38)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-kBDsod{font-size:1.125rem;width:1.125rem;height:1.125rem}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::before{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc::after{background-color:#6200ee}.VfPpkd-LgbsSe-OWXEXe-INsAgc:hover .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-outlined-button-pressed-state-layer-opacity,0.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec{border-radius:2px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-J1Ukfc-LhBDec::after{border-radius:4px}.VfPpkd-LgbsSe-OWXEXe-INsAgc:not(:disabled){border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc:disabled{border-color:rgba(0,0,0,.12)}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-UbuQg{padding:0 11px 0 15px}.VfPpkd-LgbsSe-OWXEXe-INsAgc.VfPpkd-LgbsSe-OWXEXe-Bz112c-M1Soyc{padding:0 15px 0 11px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-Jh9lGc{top:-1px;left:-1px;bottom:-1px;right:-1px;border-width:1px}.VfPpkd-LgbsSe-OWXEXe-INsAgc .VfPpkd-RLmnJb{left:-1px;width:calc(100% + 2px)}.nCP5yc{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.nCP5yc .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.nCP5yc:not(:disabled){background-color:rgb(26,115,232);background-color:var(--gm-fillbutton-container-color,rgb(26,115,232))}.nCP5yc:not(:disabled){color:#fff;color:var(--gm-fillbutton-ink-color,#fff)}.nCP5yc:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-fillbutton-disabled-container-color,rgba(60,64,67,.12))}.nCP5yc:disabled{color:rgba(60,64,67,.38);color:var(--gm-fillbutton-disabled-ink-color,rgba(60,64,67,.38))}.nCP5yc .VfPpkd-Jh9lGc::before,.nCP5yc .VfPpkd-Jh9lGc::after{background-color:rgb(32,33,36);background-color:var(--gm-fillbutton-state-color,rgb(32,33,36))}.nCP5yc:hover .VfPpkd-Jh9lGc::before,.nCP5yc.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.16;opacity:var(--mdc-ripple-hover-opacity,.16)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.24;opacity:var(--mdc-ripple-focus-opacity,.24)}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.2;opacity:var(--mdc-ripple-press-opacity,.2)}.nCP5yc.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.2)}.nCP5yc .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:#fff}@media (-ms-high-contrast:active),screen and (forced-colors:active){.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.nCP5yc .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.nCP5yc:hover{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:hover .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:active{-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 2px 6px 2px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-fillbutton-keyshadow-color,rgba(60,64,67,.3)),0 2px 6px 2px var(--gm-fillbutton-ambientshadow-color,rgba(60,64,67,.15))}.nCP5yc:active .VfPpkd-BFbNVe-bF1uUb{opacity:0}.nCP5yc:disabled{-webkit-box-shadow:none;box-shadow:none}.nCP5yc:disabled:hover .VfPpkd-Jh9lGc::before,.nCP5yc:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.nCP5yc:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.nCP5yc:disabled .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);-webkit-box-shadow:none;box-shadow:none}.Rj2Mlf .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.Rj2Mlf:not(:disabled){color:rgb(26,115,232);color:var(--gm-hairlinebutton-ink-color,rgb(26,115,232))}.Rj2Mlf:not(:disabled){border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled):hover{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:not(:disabled).VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe,.Rj2Mlf:not(:disabled):not(.VfPpkd-ksKsZd-mWPk3d):focus{border-color:rgb(23,78,166);border-color:var(--gm-hairlinebutton-outline-color--stateful,rgb(23,78,166))}.Rj2Mlf:not(:disabled):active,.Rj2Mlf:not(:disabled):focus:active{border-color:rgb(218,220,224);border-color:var(--gm-hairlinebutton-outline-color,rgb(218,220,224))}.Rj2Mlf:disabled{color:rgba(60,64,67,.38);color:var(--gm-hairlinebutton-disabled-ink-color,rgba(60,64,67,.38))}.Rj2Mlf:disabled{border-color:rgba(60,64,67,.12);border-color:var(--gm-hairlinebutton-disabled-outline-color,rgba(60,64,67,.12))}.Rj2Mlf:hover:not(:disabled),.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.Rj2Mlf:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-hairlinebutton-ink-color--stateful,rgb(23,78,166))}.Rj2Mlf .VfPpkd-BFbNVe-bF1uUb{opacity:0}.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.Rj2Mlf .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:CanvasText}}.Rj2Mlf .VfPpkd-Jh9lGc::before,.Rj2Mlf .VfPpkd-Jh9lGc::after{background-color:rgb(26,115,232);background-color:var(--gm-hairlinebutton-state-color,rgb(26,115,232))}.Rj2Mlf:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.Rj2Mlf.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Rj2Mlf:disabled:hover .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-Jh9lGc::before{opacity:0;opacity:var(--mdc-ripple-hover-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-Jh9lGc::before,.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-Jh9lGc::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-focus-opacity,0)}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d) .VfPpkd-Jh9lGc::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.Rj2Mlf:disabled:not(.VfPpkd-ksKsZd-mWPk3d):active .VfPpkd-Jh9lGc::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:0;opacity:var(--mdc-ripple-press-opacity,0)}.Rj2Mlf:disabled.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0)}.b9hyVd{font-family:"Google Sans",Roboto,Arial,sans-serif;font-size:.875rem;letter-spacing:.0107142857em;font-weight:500;text-transform:none;-webkit-transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1);transition:border .28s cubic-bezier(.4,0,.2,1),box-shadow .28s cubic-bezier(.4,0,.2,1),-webkit-box-shadow .28s cubic-bezier(.4,0,.2,1);border-width:0;-webkit-box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);box-shadow:0 1px 2px 0 rgba(60,64,67,.3),0 1px 3px 1px rgba(60,64,67,.15);-webkit-box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15));box-shadow:0 1px 2px 0 var(--gm-protectedbutton-keyshadow-color,rgba(60,64,67,.3)),0 1px 3px 1px var(--gm-protectedbutton-ambientshadow-color,rgba(60,64,67,.15))}.b9hyVd .VfPpkd-Jh9lGc{height:100%;position:absolute;overflow:hidden;width:100%;z-index:0}.b9hyVd:not(:disabled){background-color:#fff;background-color:var(--gm-protectedbutton-container-color,#fff)}.b9hyVd:not(:disabled){color:rgb(26,115,232);color:var(--gm-protectedbutton-ink-color,rgb(26,115,232))}.b9hyVd:disabled{background-color:rgba(60,64,67,.12);background-color:var(--gm-protectedbutton-disabled-container-color,rgba(60,64,67,.12))}.b9hyVd:disabled{color:rgba(60,64,67,.38);color:var(--gm-protectedbutton-disabled-ink-color,rgba(60,64,67,.38))}.b9hyVd:hover:not(:disabled),.b9hyVd.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe:not(:disabled),.b9hyVd:not(.VfPpkd-ksKsZd-mWPk3d):focus:not(:disabled),.b9hyVd:active:not(:disabled){color:rgb(23,78,166);color:var(--gm-protectedbutton-ink-color--stateful,rgb(23,78,166))}.b9hyVd .VfPpkd-BFbNVe-bF1uUb{opacity:0}.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-Bd00G{stroke:rgb(26,115,232)}@media (-ms-high-contrast:active),screen and (forced-colors:active){.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-uI4vCe-LkdAo,.b9hyVd .VfPpkd-UdE5de-uDEFge .VfPpkd-JGcpL-IdXvz-LkdAo-B | 2026-01-13T08:49:23 |
https://dev.to/softwebsolution/legacy-modernization-your-path-to-efficiency-and-growth-45f7 | Legacy modernization_ Your path to efficiency and growth - 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 Chirag Softweb for Softweb Solutions Inc. - An Avnet Company Posted on Oct 13, 2023 Legacy modernization_ Your path to efficiency and growth # legacy # modernization # cloud # aws Is your business still tethered to outdated legacy systems? It's time to unshackle and embrace modernization! By updating your applications, you can slash maintenance and running costs by 30-50%. Break free from the anchor of legacy and discover the path to a brighter future. Explore our legacy modernization services for more information. Watch our video: https://www.youtube.com/watch?v=G_B3bwsgpSk Dive into our articles for valuable insights: Modernize legacy apps to secure your future: https://www.softwebsolutions.com/resources/modernize-legacy-application.html AWS for application modernization: https://go.softwebsolutions.com/resources/aws-for-app-modernization.html Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Some comments may only be visible to logged-in visitors. Sign in to view all 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 Softweb Solutions Inc. - An Avnet Company Follow Drive innovation with advanced data analytics and AI AWS Services AWS Services More from Softweb Solutions Inc. - An Avnet Company The importance of a multi-cloud strategy: Lessons from history’s biggest IT outage # cloud # multiplatform # azure # aws Transform Your Legacy Systems with AWS Application Modernization # aws # modernization # legacy The Importance of a Multi-Cloud Strategy: Key Lessons from Major IT Outages # cloud # cloudcomputing 💎 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:49:23 |
https://atproto.com/specs/atp | AT Protocol - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme AT Protocol The Authenticated Transfer Protocol (AT Protocol or atproto) is a generic federated protocol for building open social media applications. Some recurring themes and features are: Self-authenticating data and identity, allowing seamless account migrations and redistribution of content Design for "big world" use cases, scaling to billions of accounts Delegated authority over application-layer schemas and aggregation infrastructure Re-use of existing data models from the dweb protocol family and network primitives from the web platform Protocol Structure Identity: account control is rooted in stable DID identifiers, which can be rapidly resolved to determine the current service provider location and Cryptographic keys associated with the account. Handles provide a more human-recognizable and mutable identifier for accounts. Data: public content is stored in content-addressed and cryptographically verifiable Repositories . Data records and network messages all conform to a unified Data Model (with CBOR and JSON representations). Labels are a separate lightweight form of metadata, individually signed and distributed outside repositories. Network: HTTP client-server and server-server APIs are described with Lexicons, as are WebSocket Event Streams . Individual records can be referenced across the network by AT URI . A Personal Data Server (PDS) acts as an account's trusted agent in the network, routes client network requests, and hosts repositories. A relay crawls many repositories and outputs a unified event Firehose . Application: APIs and record schemas for applications built on atproto are specified in Lexicons , which are referenced by Namespaced Identifiers (NSIDs). Application-specific aggregations (such as search) are provided by an Application View (App View) service. Clients can include mobile apps, desktop software, or web interfaces. The AT Protocol itself does not specify common social media conventions like follows or avatars, leaving these to application-level Lexicons. The com.atproto.* Lexicons provide common APIs for things like account signup and login. These could be considered part of AT Protocol itself, though they can also be extended or replaced over time as needed. Bluesky is a microblogging social app built on top of AT Protocol, with lexicons under the app.bsky.* namespace. While atproto borrows several formats and specifications from the IPFS ecosystem (such as IPLD and CID ), atproto data does not need to be stored in the IPFS network, and the atproto reference implementation does not use the IPFS network at all. Protocol Extension and Applications AT Protocol was designed from the beginning to balance stability and interoperation against flexibility for third-party application development. The core protocol extension mechanism is development of new Lexicons under independent namespaces. Lexicons can declare new repository record schemas (stored in collections by NSID), new HTTP API endpoints, and new event stream endpoints and message types. It is also expected that new applications might require new network aggregation services ("AppViews") and client apps (eg, mobile apps or web interfaces). It is expected that third parties will reuse Lexicons and record data across namespaces. For example, new applications are welcome to build on top of the social graph records specified in the app.bsky.* Lexicons, as long as they comply with the schemas controlled by the bsky.app authority. Governance structures for individual Lexicon namespaces are flexible. They could be developed and maintained by volunteer communities, corporations, consortia, academic researchers, funded non-profits, etc. What Is Missing? These specifications cover most details as implemented in Bluesky's reference implementation. A few important pieces have not been finalized, both in that reference implementation and in these specifications. Moderation Primitives: The com.atproto.admin.* routes for handling moderation reports and doing infrastructure-level take-downs is specified in Lexicons but should also be described in more detail. Future Work Smaller changes are described in individual specification documents, but a few large changes span the entire protocol. Non-Public Content: mechanisms for private group and one-to-one communication will be an entire second phase of protocol development. This encompasses primitives like "private accounts", direct messages, encrypted data, and more. We recommend against simply "bolting on" encryption or private content using the existing protocol primitives. Protocol Governance and Formal Standards Process: The current development focus is to demonstrate all the core protocol features via the reference implementation, including open federation. After that milestone, the intent is to stabilize the lower-level protocol and submit the specification for independent review and revision through a standards body such as the IETF or the W3C. Previous Account Migration Next Data Model © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
https://open.forem.com/t/watercooler | Watercooler - 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 # watercooler Follow Hide Light, and off-topic conversation. Create Post submission guidelines This is a tag meant for slightly, or majorly offtopic subjects. Remember to keep things light, friendly and in-line with the code of conduct. about #watercooler 😎 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Impact of Phones on the Brain: A Double-Edged Sword Gus Woltmann Gus Woltmann Gus Woltmann Follow Jan 11 The Impact of Phones on the Brain: A Double-Edged Sword # discuss # science # watercooler Comments Add Comment 3 min read Apophis: The Potential Threat of a Comet Impact on Earth Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 11 Apophis: The Potential Threat of a Comet Impact on Earth # discuss # science # space # watercooler Comments Add Comment 3 min read Navigating Unique Flaws: The Complexities of Divorce in Louisiana Paula Fox Paula Fox Paula Fox Follow Dec 29 '25 Navigating Unique Flaws: The Complexities of Divorce in Louisiana # discuss # watercooler Comments Add Comment 3 min read Working With Images That Outlive Their Stories Aaron Cole Aaron Cole Aaron Cole Follow Dec 27 '25 Working With Images That Outlive Their Stories # watercooler # career # photography Comments Add Comment 5 min read The Morse Code: A Revolutionary System of Communication Gus Woltmann Gus Woltmann Gus Woltmann Follow Dec 28 '25 The Morse Code: A Revolutionary System of Communication # watercooler # learning # science Comments Add Comment 4 min read # The Last Letter Abdulla A Abdulla A Abdulla A Follow Dec 26 '25 # The Last Letter # watercooler # books # writing Comments Add Comment 6 min read The Importance of a Healthy Lifestyle in Today’s Fast-Paced World Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 25 '25 The Importance of a Healthy Lifestyle in Today’s Fast-Paced World # discuss # motivation # watercooler Comments Add Comment 2 min read 🌿 5 Simple Habits to Improve Your Daily Life Dharmikk Baria Dharmikk Baria Dharmikk Baria Follow Dec 23 '25 🌿 5 Simple Habits to Improve Your Daily Life # watercooler # beginners # motivation Comments Add Comment 1 min read Rise of Bharat: India’s Journey Toward a New Era of Growth and Global Leadership Kavi Kr Kavi Kr Kavi Kr Follow Dec 22 '25 Rise of Bharat: India’s Journey Toward a New Era of Growth and Global Leadership # discuss # watercooler Comments Add Comment 1 min read 2026 Simon L Simon L Simon L Follow Dec 21 '25 2026 # discuss # watercooler Comments Add Comment 1 min read Identifying Systemic Flaws in Delaware's Divorce Process: A Legal Critique Paula Fox Paula Fox Paula Fox Follow Dec 22 '25 Identifying Systemic Flaws in Delaware's Divorce Process: A Legal Critique # discuss # watercooler Comments Add Comment 3 min read FTSE 350 Today: A Comprehensive Look at Market Movements and Investor Sentiment Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 19 '25 FTSE 350 Today: A Comprehensive Look at Market Movements and Investor Sentiment # discuss # watercooler Comments Add Comment 4 min read Surah Waqiah – Meaning, Benefits, and Importance Muhammad Husnain Ali Muhammad Husnain Ali Muhammad Husnain Ali Follow Dec 18 '25 Surah Waqiah – Meaning, Benefits, and Importance # watercooler # books # learning Comments Add Comment 2 min read Natural Family Planning vs. Modern Contraception: Which Is Right for You? Hera Clinic Hera Clinic Hera Clinic Follow Dec 17 '25 Natural Family Planning vs. Modern Contraception: Which Is Right for You? # discuss # science # watercooler Comments Add Comment 3 min read Rise of Bharat: India’s Journey Toward a New Era of Growth and Global Leadership Kavi Kr Kavi Kr Kavi Kr Follow Dec 17 '25 Rise of Bharat: India’s Journey Toward a New Era of Growth and Global Leadership # discuss # leadership # watercooler Comments Add Comment 1 min read A Comprehensive Journey from Earth’s Depths to Eternal Symbol nuse iqpv nuse iqpv nuse iqpv Follow Dec 15 '25 A Comprehensive Journey from Earth’s Depths to Eternal Symbol # watercooler # learning # science Comments Add Comment 5 min read Is constant winding actually BAD for your automatic watch? zak bowden zak bowden zak bowden Follow Dec 17 '25 Is constant winding actually BAD for your automatic watch? # discuss # learning # watercooler Comments 2 comments 2 min read The Energy That Builds Before a Show Begins Marcus Ellery Marcus Ellery Marcus Ellery Follow Dec 12 '25 The Energy That Builds Before a Show Begins # discuss # watercooler # writing Comments Add Comment 5 min read Craft Beer Experiences Highlighting San Diego’s Vibrant Brewing Scene Kian Frost Kian Frost Kian Frost Follow Dec 12 '25 Craft Beer Experiences Highlighting San Diego’s Vibrant Brewing Scene # watercooler # writing Comments Add Comment 5 min read Mushroom Revenue Brian Kim Brian Kim Brian Kim Follow Dec 12 '25 Mushroom Revenue # discuss # career # watercooler Comments Add Comment 2 min read How Driving Lab Samples Shaped My Sense Of Purpose Calvin Mercer Calvin Mercer Calvin Mercer Follow Dec 11 '25 How Driving Lab Samples Shaped My Sense Of Purpose # watercooler # career # motivation Comments Add Comment 9 min read Keeping Flow Steady in a Busy Treatment Plant Harold Danner Harold Danner Harold Danner Follow Dec 11 '25 Keeping Flow Steady in a Busy Treatment Plant # discuss # career # watercooler Comments Add Comment 7 min read THE SHIP OF THESEUS AND THE FUTURE OF HUMAN IDENTITY Thinking Healer Thinking Healer Thinking Healer Follow Dec 10 '25 THE SHIP OF THESEUS AND THE FUTURE OF HUMAN IDENTITY # discuss # ai # watercooler Comments Add Comment 4 min read What I See From The Blood Donation Intake Desk Evelyn Brooks Evelyn Brooks Evelyn Brooks Follow Dec 9 '25 What I See From The Blood Donation Intake Desk # discuss # watercooler # writing Comments Add Comment 6 min read Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market Isabel Rayn Isabel Rayn Isabel Rayn Follow Dec 11 '25 Understanding the FTSE AIM 100: A Look at the UK’s Dynamic Growth Market # watercooler # beginners # learning Comments Add Comment 4 min read loading... trending guides/resources How to fix a hedgehog habitat that keeps getting too humid? uPVC windows vs aluminium windows — which is the better long-term choice for a Suffolk home? Keeping Ephemeral Videos Without Crossing Ethical Lines When Do the Goals Rain Down? Uncovering the Time Periods with the Most Scoring Action in Europe's... Bowling vs darts at Spinners UK – which activity offers the better group experience for a mixed-a... A Comprehensive Journey from Earth’s Depths to Eternal Symbol A Beginner’s Guide to Power Yoga for Weight Loss and Strength Why you should Include Indian Thali in your Daily meals Zeeshan Ameer Saleemi Zeeshan Ameer Saleemi The Retail Evolution: How Superstores Redefined Modern Shopping Le fils de l’humoriste : Mathieu Gerra et ses rêves en devenir Rise of Bharat: India’s Journey Toward a New Era of Growth and Global Leadership How Do I Balance It All? Poet Zeeshan Ameer Saleemi Sustainable Fashion in the Modern World Sustainable Fashion Trends Dominating 2025 The Impact of Phones on the Brain: A Double-Edged Sword Thinking of Ordering Bridesmaid Dresses from Azazie — Worth It? Mexico continues to violate our comprehensive Water Treaty 💎 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:49:22 |
https://www.coderabbit.ai/case-studies/buy-vs-build-why-writer-bought-their-ai-code-review-tool | Buy vs build: Why WRITER bought their AI code review tool Features Enterprise Customers Pricing Blog Resources Docs Trust Center Contact Us FAQ Log In Get a free trial Buy vs build: Why WRITER bought their AI code review tool 30% time savings Leadership productivity Unified engineering culture Cross-team visibility San Francisco, United States https://www.writer.com/ Team size 500+ employees Languages JavaScript, Python Challenge WRITER Scaling AI-native development efficiently while maintaining consistent code quality and review velocity across multiple teams and repositories. Get started today Share For Kyrylo Buha, Member of Technical Staff at WRITER, managing code quality across an AI-native company requires both technical excellence and operational efficiency. WRITER is where the leading enterprises orchestrate AI-powered work. With WRITER’s end-to-end platform, teams can build, activate, and supervise AI agents that are grounded in their company’s data and fueled by WRITER’s enterprise-grade LLMs. Kyrylo’s role spans both the software development cycle and people management, making efficient code review processes critical for team productivity. Integrating AI into the code reviews just made sense for their team. At first, they considered using their own LLMs for code reviews, Kyrylo explained. However, they quickly realized that building an in-house solution would be too time-consuming and resource-intensive. That led Kyrylo to CodeRabbit. What started as an experiment with his frontend teams quickly expanded across the company, with CodeRabbit now being used on more than 37 repositories. Multiple backend teams also adopted the tool after seeing the frontend team’s success. Challenge: Scaling AI-native development with efficient code reviews Before CodeRabbit, WRITER’s development process followed a standard approach with one reviewer per pull request, escalating to multiple reviewers only for core and essential changes. However, several challenges emerged as the company scaled its AI-powered development. Allocating resources across the core product and internal tooling While WRITER had the technical capability to build their own code review AI, resource allocation became a critical consideration. “We realized that it would be time-consuming and we didn’t have the capacity to build something in-house,” Kyrylo noted. The team needed to focus its AI expertise on its core product rather than internal tooling. Maintaining consistency across multiple teams and projects With developers working across frontend, backend, and full-stack projects, maintaining coding standards and style consistency became increasingly challenging. WRITER had developed internal style guides distributed across Confluence and Notion pages, but ensuring adherence required significant manual oversight. Optimizing review processes for high-volume development Processing approximately 50 pull requests per day across their active repositories, WRITER needed a solution that could maintain consistency while accelerating their development velocity. “We are kind of AI evangelists. So we believe that AI can significantly improve performance,” Kyrylo explained, emphasizing their commitment to leveraging AI for operational efficiency. 50 PRs/day 30% time savings 70% suggestion acceptance rate Why WRITER loves CodeRabbit Catching a regex UUID validation bug before production CodeRabbit’s contextual understanding quickly earned the trust of WRITER’s engineering team. It consistently flags issues that humans tend to overlook, Kyrylo shared, such as tricky if/else branches, negative conditions, and overly permissive validations. One standout example was a UUID check. CodeRabbit identified a hidden problem in a developer's utility function, even though unit tests covered it. The developer's regex was too broad, allowing non-UUID strings to slip through and risking corrupted data in production.CodeRabbit spotted the gap and suggested a stricter pattern with proper anchors, version, and variant constraints, preventing a subtle bug from shipping. In this case, it enforced a more precise UUID check and saved us from a production issue. Kyrylo Buha, Member of Technical Staff By tightening validation at review time, CodeRabbit helped WRITER reduce error risk, raise code standards and move faster with confidence. Unifying style guides with path-based instructions WRITER unified their scattered internal documentation from Confluence/Notion guidance into a single CodeRabbit style guide, using File Patterns to target guideline files, CodeRabbit’s Learnings (local/global/auto) to control scope, and path-based instructions to tailor rules by directory (e.g., services/payments/**). With our style guides in CodeRabbit, newcomers get instant feedback that matches how we code, and over 70% of those suggestions are accepted. Kyrylo Buha, Member of Technical Staff Cross-team collaboration through JIRA integration "CodeRabbit’s JIRA integration delivered unexpected benefits by surfacing connections between work streams across different teams." Kyrylo explained. What I find really useful is that it can track the PRs across multiple projects in Jira. So, when you make the change, CodeRabbit tracks the changes in other projects on other boards. Kyrylo Buha, Member of Technical Staff This feature helped prevent duplicate work and improved coordination between the teams. Visualization with sequence diagrams for more technical reviews CodeRabbit’s sequence diagrams feature became an instant hit with WRITER’s developers, particularly for understanding complex changes. “The sequence diagram gives us more clarity around the changes that were performed within the PR,” Kyrylo noted. This feature proved especially valuable for large pull requests, providing developers with comprehensive insights without requiring local testing. “CodeRabbit’s sequence diagrams let reviewers grasp a PR’s behavior without checking out the branch, allowing clearer, faster reviews when local runs aren’t practical.” Productivity boost inside VS Code and Cursor WRITER uses the CodeRabbit IDE extension for seamless integration into their day-to-day workflows. The extension allows engineers to trigger reviews, resolve comments inline, and access context-aware Learnings right where they code — eliminating context switching between tools. “What we find useful is the extension for Cursor. It’s amazing to be able to run the PR checks and fix them prior to raising the PR for a wider audience,” Kyrylo shared. Results: Measurable improvements across the development lifecycle 30% time savings for team leads: Kyrylo reports cutting code-review time by 30% thanks to CodeRabbit’s targeted comments, which let him skip already covered areas and focus on higher value work: “Personally, my code review time is down around 30%. When I see useful comments, I don’t focus on those areas; I cover other areas and rely on CodeRabbit to have my back.” The savings are especially valuable in his dual role managing two teams: “The savings are huge for my dev/manager role, I can spend more time on management, coding, and strategic product improvements," Kyrylo shared. Rapid organic adoption across the organization: CodeRabbit’s ease of integration facilitated rapid expansion beyond Kyrylo’s initial frontend teams. “It’s really easy to integrate. That’s why you don’t miss anything. You just enable the repository and you instantly start getting the feedback,” he noted. CodeRabbit = Effortless AI integration for AI-native development Before CodeRabbit • One human reviewer per PR -> Limited coverage • Style guide scattered across Confluence & Notion • Slow review cycles for large PRs • Hard to maintain consistency across 37+ repos After CodeRabbit 30% faster code reviews for team leads Regex and conditional bugs caught early Unified style guide inside CodeRabbit Sequence diagrams & Jira integration improve context and collaboration For Kyrylo and his team at WRITER, CodeRabbit represents the ideal balance of powerful AI capabilities with minimal overhead. “It’s a fast way to introduce AI code reviews with a quick setup and roll out across projects and teams, getting value from day one.” What sets CodeRabbit apart is its ability to complement its existing development culture while adding immediate value. As Kyrylo emphasized, “What I love about CodeRabbit is its easy-to-use nature, a critical factor for a company that needs to maintain focus on their core AI product development.” The platform’s success at WRITER demonstrates how even companies building AI solutions themselves can benefit from purpose-built tools that integrate seamlessly into their workflows. By handling routine code quality checks and providing enhanced visibility into complex changes, CodeRabbit allows WRITER’s developers to focus on what they do best: building innovative AI solutions. San Francisco, United States https://www.writer.com/ Team size 500+ employees Languages JavaScript, Python Challenge WRITER Scaling AI-native development efficiently while maintaining consistent code quality and review velocity across multiple teams and repositories. Get started today Want to see how CodeRabbit can help your team? Get a 14-day trial 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:49:23 |
https://design.forem.com/t/webdesign#main-content | Webdesign - Design 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 Design Community Close # webdesign Follow Hide All about designing websites, from layout to user experience Create Post Older #webdesign posts 1 2 3 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The "Quick Question" That Tells Me Everything Tanya Donska Tanya Donska Tanya Donska Follow Dec 22 '25 The "Quick Question" That Tells Me Everything # design # freelancing # resources # webdesign Comments Add Comment 5 min read Seeking Feedback on Custom Blogger Templates - What Do You Need? Yanuar Zhaldy Gemilang Yanuar Zhaldy Gemilang Yanuar Zhaldy Gemilang Follow Dec 17 '25 Seeking Feedback on Custom Blogger Templates - What Do You Need? # cms # userresearch # webdesign Comments 1 comment 1 min read Bring Your Own Laptop: Free Figma Advanced Course: Become a Figma Pro! Design YouTube Design YouTube Design YouTube Follow Nov 29 '25 Bring Your Own Laptop: Free Figma Advanced Course: Become a Figma Pro! # design # resources # tools # webdesign Comments Add Comment 1 min read Building a Dummy Service Centre Website Taught Me More Than Any Assignment abu zafar abu zafar abu zafar Follow Dec 24 '25 Building a Dummy Service Centre Website Taught Me More Than Any Assignment # design # webdesign # newdesigner 3 reactions Comments Add Comment 2 min read Reimagining Thai Lagoon - Website Redesign Parvathi Kumar Parvathi Kumar Parvathi Kumar Follow Dec 5 '25 Reimagining Thai Lagoon - Website Redesign # uxdesign # showcase # uidesign # webdesign Comments Add Comment 2 min read Emerging graphic design trends for 2026 Karina Egle Karina Egle Karina Egle Follow Nov 13 '25 Emerging graphic design trends for 2026 # design # recommendations # webdesign # graphicdesign Comments Add Comment 2 min read Why Most Sports Coaching Websites Don’t Work - And How to Fix Yours Per Starke Per Starke Per Starke Follow Nov 7 '25 Why Most Sports Coaching Websites Don’t Work - And How to Fix Yours # webdesign # design # coaching # websites Comments Add Comment 3 min read Your Sports Coaching Website Doesn’t Work For You? Per Starke Per Starke Per Starke Follow Oct 23 '25 Your Sports Coaching Website Doesn’t Work For You? # coach # portfolio # freelancing # webdesign Comments Add Comment 2 min read Call-to-Actions Done Right: The Ultimate CTA Guide for More Engagement Per Starke Per Starke Per Starke Follow Oct 23 '25 Call-to-Actions Done Right: The Ultimate CTA Guide for More Engagement # cta # design # webdesign # uidesign Comments Add Comment 3 min read UX Across the Atlantic: How American and European Web Design Differ Polina Elizarova Polina Elizarova Polina Elizarova Follow Nov 27 '25 UX Across the Atlantic: How American and European Web Design Differ # design # webdesign # uxdesign # designprocess 1 reaction Comments Add Comment 2 min read Why Your Website Should Evolve With You (and How) Per Starke Per Starke Per Starke Follow Oct 23 '25 Why Your Website Should Evolve With You (and How) # cms # webdesign # uidesign # copywriting Comments Add Comment 7 min read Website Red Flags You Might Be Overlooking (And Visitors Notice) Per Starke Per Starke Per Starke Follow Oct 23 '25 Website Red Flags You Might Be Overlooking (And Visitors Notice) # seo # webdesign # design # userflows Comments Add Comment 4 min read Why ‘Best in UAE’ (and other empty claims) Lose Client Trust and What to Write Instead Per Starke Per Starke Per Starke Follow Oct 23 '25 Why ‘Best in UAE’ (and other empty claims) Lose Client Trust and What to Write Instead # webdesign # freelancertips # clientrelations # brandtrust 1 reaction Comments Add Comment 6 min read Offering Free Website Design to Gain Real-World Experience" Zoey Zoey Zoey Follow Nov 12 '25 Offering Free Website Design to Gain Real-World Experience" # freelancing # portfolio # webdesign # newdesigner 1 reaction Comments 2 comments 1 min read Pure CSS audio visualizer Prahalad S Prahalad S Prahalad S Follow Nov 4 '25 Pure CSS audio visualizer # design # css # webdesign # javascript 5 reactions Comments 2 comments 3 min read Femke.design: Why Your Design Ideas Get REJECTED (6-Step Fix) Design YouTube Design YouTube Design YouTube Follow Oct 1 '25 Femke.design: Why Your Design Ideas Get REJECTED (6-Step Fix) # design # webdesign # portfolio Comments Add Comment 1 min read 5 ChatGPT Prompts That End Designer's Block Forever (Web, Graphic, and UI/UX) AISuperHub AISuperHub AISuperHub Follow Sep 30 '25 5 ChatGPT Prompts That End Designer's Block Forever (Web, Graphic, and UI/UX) # design # javascript # webdesign # aiindesign Comments Add Comment 3 min read The Sports Coach Website Strategy Canvas: Your Coaching Business on One Page Per Starke Per Starke Per Starke Follow Nov 1 '25 The Sports Coach Website Strategy Canvas: Your Coaching Business on One Page # webdesign # coaching # webdev # business Comments Add Comment 3 min read Jesse Showalter: The State of Design and Tools Design YouTube Design YouTube Design YouTube Follow Sep 30 '25 Jesse Showalter: The State of Design and Tools # design # tools # webdesign 3 reactions Comments Add Comment 1 min read How UX in 2025 became more about intent than interaction Karina Egle Karina Egle Karina Egle Follow Oct 23 '25 How UX in 2025 became more about intent than interaction # design # uxdesign # uidesign # webdesign 9 reactions Comments 1 comment 4 min read 11 Principles That Help Me Decide When to Research vs. Just Ship Ulad Shauchenka Ulad Shauchenka Ulad Shauchenka Follow Sep 26 '25 11 Principles That Help Me Decide When to Research vs. Just Ship # design # uxdesign # uidesign # webdesign Comments Add Comment 1 min read Jesse Showalter: Did Framer Just Kill Figma This New Feature Changes EVERYTHING! Design YouTube Design YouTube Design YouTube Follow Sep 23 '25 Jesse Showalter: Did Framer Just Kill Figma This New Feature Changes EVERYTHING! # design # tools # webdesign 2 reactions Comments Add Comment 1 min read How to Build Trust on Your Website - My Go-To Checklist for Authentic, High-Impact Websites Per Starke Per Starke Per Starke Follow Oct 23 '25 How to Build Trust on Your Website - My Go-To Checklist for Authentic, High-Impact Websites # webdesign # trust # devhandoff # htmlcss Comments 2 comments 5 min read Why Personality Matters on Your Website – Even for Large Companies and Non-Personal Brands Per Starke Per Starke Per Starke Follow Oct 23 '25 Why Personality Matters on Your Website – Even for Large Companies and Non-Personal Brands # webdesign # trust # personality # freelancing 1 reaction Comments Add Comment 6 min read Mizko: I stopped working Design YouTube Design YouTube Design YouTube Follow Sep 12 '25 Mizko: I stopped working # design # webdesign # tools # sideprojects 1 reaction Comments Add Comment 1 min read loading... trending guides/resources The "Quick Question" That Tells Me Everything Emerging graphic design trends for 2026 Bring Your Own Laptop: Free Figma Advanced Course: Become a Figma Pro! UX Across the Atlantic: How American and European Web Design Differ Why Most Sports Coaching Websites Don’t Work - And How to Fix Yours Reimagining Thai Lagoon - Website Redesign Building a Dummy Service Centre Website Taught Me More Than Any Assignment The Sports Coach Website Strategy Canvas: Your Coaching Business on One Page Pure CSS audio visualizer 💎 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 Design Community — Web design, graphic design and everything in-between 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 . Design Community © 2016 - 2026. We're a place where designers share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:23 |
https://forem.com/adamgolan#main-content | Adam Golan - 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 Forem Close Follow User actions Adam Golan 404 bio not found Joined Joined on Sep 2, 2024 Email address slowmoon.adam@gmail.com More info about @adamgolan Badges 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 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 37 posts published Comment 0 comments written Tag 0 tags followed Breaking the Runtime Wall: Universal Frameworks in BEnder 🌍 Adam Golan Adam Golan Adam Golan Follow Jan 10 Breaking the Runtime Wall: Universal Frameworks in BEnder 🌍 # node # bunjs # backend # webdev Comments Add Comment 2 min read I Added Koa Support to My Universal Boilerplate (And It Was Tricky) Adam Golan Adam Golan Adam Golan Follow Dec 24 '25 I Added Koa Support to My Universal Boilerplate (And It Was Tricky) # backend # koa # architecture # typescript Comments Add Comment 2 min read I Built a Framework-Agnostic Backend Boilerplate (Node, Bun, Express, Hono...) Adam Golan Adam Golan Adam Golan Follow Dec 18 '25 I Built a Framework-Agnostic Backend Boilerplate (Node, Bun, Express, Hono...) # backend # architecture # programming # typescript 1 reaction Comments Add Comment 2 min read Why I Flipped Express on Its Head: Rethinking Backends with a Brain-Inspired Neuron/Synapse Pattern Adam Golan Adam Golan Adam Golan Follow Dec 9 '25 Why I Flipped Express on Its Head: Rethinking Backends with a Brain-Inspired Neuron/Synapse Pattern # node # backend # architecture # webdev Comments Add Comment 3 min read Beyond the Buzzwords: Decoding Tech Marketing Hype in Web Development Adam Golan Adam Golan Adam Golan Follow Mar 24 '25 Beyond the Buzzwords: Decoding Tech Marketing Hype in Web Development # discuss # frontend # backend # webdev Comments Add Comment 4 min read The Art of Data Scaffolding: Building Strong Foundations for Your Applications Adam Golan Adam Golan Adam Golan Follow Feb 26 '25 The Art of Data Scaffolding: Building Strong Foundations for Your Applications # data # saas # go # typescript 1 reaction Comments Add Comment 7 min read Creating a Microservices Architecture with Docker and Kubernetes Adam Golan Adam Golan Adam Golan Follow Feb 18 '25 Creating a Microservices Architecture with Docker and Kubernetes # microservices # docker # kubernetes # cicd 4 reactions Comments Add Comment 3 min read Understanding Git Workflows Beyond the Basics Adam Golan Adam Golan Adam Golan Follow Feb 17 '25 Understanding Git Workflows Beyond the Basics # git # tutorial # programming # productivity 1 reaction Comments Add Comment 3 min read Web Accessibility: A Developer's Guide to WCAG 2.1 Adam Golan Adam Golan Adam Golan Follow Feb 16 '25 Web Accessibility: A Developer's Guide to WCAG 2.1 # webdev # html # css 2 reactions Comments Add Comment 3 min read The Hidden Cost of Third-Party Libraries: When 'Don't Reinvent the Wheel' Goes Wrong Adam Golan Adam Golan Adam Golan Follow Feb 12 '25 The Hidden Cost of Third-Party Libraries: When 'Don't Reinvent the Wheel' Goes Wrong # webdev # javascript # productivity # programming 1 reaction Comments Add Comment 3 min read Vanilla update! Adam Golan Adam Golan Adam Golan Follow Feb 11 '25 Vanilla update! # webdev # typescript # javascript # frontend 1 reaction Comments Add Comment 1 min read The Senior Developer Paradox: Why Writing Less Code Makes You More Valuable Adam Golan Adam Golan Adam Golan Follow Feb 11 '25 The Senior Developer Paradox: Why Writing Less Code Makes You More Valuable # programming # career # performance # coding Comments 1 comment 3 min read The Performance Trap: When Optimization Makes Your Code Slower Adam Golan Adam Golan Adam Golan Follow Feb 10 '25 The Performance Trap: When Optimization Makes Your Code Slower # discuss # programming # performance # productivity 1 reaction Comments Add Comment 5 min read The Art of Code Deletion: Why Removing Code Makes You a Better Developer Adam Golan Adam Golan Adam Golan Follow Feb 9 '25 The Art of Code Deletion: Why Removing Code Makes You a Better Developer # webdev # programming # javascript # productivity 5 reactions Comments 1 comment 3 min read The Hidden Costs of Over-Engineering: When Simple Solutions Win Adam Golan Adam Golan Adam Golan Follow Feb 7 '25 The Hidden Costs of Over-Engineering: When Simple Solutions Win # architecture # cleancode # development 28 reactions Comments 5 comments 3 min read Time Travel Debugging: Beyond Console.log Adam Golan Adam Golan Adam Golan Follow Feb 6 '25 Time Travel Debugging: Beyond Console.log # javascript # devtool # debugging # programming Comments Add Comment 3 min read Performance Optimization Techniques for Modern Web Apps in 2025 Adam Golan Adam Golan Adam Golan Follow Feb 5 '25 Performance Optimization Techniques for Modern Web Apps in 2025 # webdev # performance # webperf # javascript 2 reactions Comments Add Comment 4 min read Mastering Git Workflows: Beyond the Basics Adam Golan Adam Golan Adam Golan Follow Feb 4 '25 Mastering Git Workflows: Beyond the Basics # git # github # cicd # devops 3 reactions Comments Add Comment 4 min read Building Accessible Web Components: A Deep Dive into ARIA Best Practices Adam Golan Adam Golan Adam Golan Follow Feb 3 '25 Building Accessible Web Components: A Deep Dive into ARIA Best Practices # discuss # webdev # frontend # website Comments Add Comment 3 min read Micro-Frontend Architecture: Lessons from the Trenches Adam Golan Adam Golan Adam Golan Follow Feb 2 '25 Micro-Frontend Architecture: Lessons from the Trenches # frontend # webdev # cicd # javascript Comments Add Comment 3 min read Building Your Own 8-bit Sound Mixer in Node.js Adam Golan Adam Golan Adam Golan Follow Jan 30 '25 Building Your Own 8-bit Sound Mixer in Node.js # node # music # javascript # dsp 1 reaction Comments Add Comment 4 min read The Great Rendering Battle: Server-Side vs Client-Side Rendering in 2025 Adam Golan Adam Golan Adam Golan Follow Jan 29 '25 The Great Rendering Battle: Server-Side vs Client-Side Rendering in 2025 # webdev # javascript # frontend # performance 2 reactions Comments Add Comment 3 min read Understanding Memory Leaks in Modern Web Applications: The Silent Performance Killers Adam Golan Adam Golan Adam Golan Follow Jan 28 '25 Understanding Memory Leaks in Modern Web Applications: The Silent Performance Killers # javascript # performance # webdev # programming Comments Add Comment 3 min read The Art of Constructive Code Reviews: Building Better Code and Stronger Teams Adam Golan Adam Golan Adam Golan Follow Jan 27 '25 The Art of Constructive Code Reviews: Building Better Code and Stronger Teams # codereview # programming # productivity # leadership 1 reaction Comments Add Comment 2 min read Rust and Go: The Future of High-Performance Computing Adam Golan Adam Golan Adam Golan Follow Jan 26 '25 Rust and Go: The Future of High-Performance Computing # programming # go # rust # architecture 1 reaction Comments Add Comment 3 min read Reactive State Management Without Libraries Adam Golan Adam Golan Adam Golan Follow Jan 23 '25 Reactive State Management Without Libraries # react # angular # javascript # webdev 1 reaction Comments Add Comment 2 min read Set vs Array in JavaScript: When to Use Which? Adam Golan Adam Golan Adam Golan Follow Jan 22 '25 Set vs Array in JavaScript: When to Use Which? # javascript # datastructures # programming # computerscience Comments Add Comment 3 min read Why You Should Prefer Map over Object in JavaScript Adam Golan Adam Golan Adam Golan Follow Jan 21 '25 Why You Should Prefer Map over Object in JavaScript # javascript # webdev # programming # datastructures 15 reactions Comments 4 comments 3 min read 🎨🛠️ 𝗩𝗮𝗻𝗶𝗹𝗹𝗮 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝘁𝗼 𝗘𝗺𝗽𝗼𝘄𝗲𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 🚀🌐 Adam Golan Adam Golan Adam Golan Follow Dec 22 '24 🎨🛠️ 𝗩𝗮𝗻𝗶𝗹𝗹𝗮 𝗙𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝘁𝗼 𝗘𝗺𝗽𝗼𝘄𝗲𝗿 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 🚀🌐 # vanilla # webdev # typescript # frontend Comments Add Comment 2 min read 🌟 Vanilla Update: New Components and Enhanced Features! 🌟 Adam Golan Adam Golan Adam Golan Follow Nov 24 '24 🌟 Vanilla Update: New Components and Enhanced Features! 🌟 # vanilla # webdev # typescript # frontend Comments Add Comment 1 min read 🌐 Unlock Development with Vanilla: The Non-Framework Powerhouse 🌐 Adam Golan Adam Golan Adam Golan Follow Nov 12 '24 🌐 Unlock Development with Vanilla: The Non-Framework Powerhouse 🌐 # vanilla # webdev # typescript # frontend Comments Add Comment 2 min read 🚀 Vanilla & CSSer Major Update! 🚀 Adam Golan Adam Golan Adam Golan Follow Nov 8 '24 🚀 Vanilla & CSSer Major Update! 🚀 # vanilla # csser # webdev # coding Comments Add Comment 1 min read 🚀 Vanilla Update: A New Development Methodology! 🚀 Adam Golan Adam Golan Adam Golan Follow Nov 3 '24 🚀 Vanilla Update: A New Development Methodology! 🚀 # vanilla # webdev # javascript # coding Comments Add Comment 1 min read 🌟 Vanilla & CSSer Accessibility Update! 🌟 Adam Golan Adam Golan Adam Golan Follow Oct 28 '24 🌟 Vanilla & CSSer Accessibility Update! 🌟 # vanilla # csser # webdev # frontend Comments Add Comment 1 min read 🚀 Vanilla Framework Update: Meet CSSer! 🚀 Adam Golan Adam Golan Adam Golan Follow Oct 27 '24 🚀 Vanilla Framework Update: Meet CSSer! 🚀 # vanilla # webdev # frontend # css Comments Add Comment 1 min read 🚀 Vanilla Framework Update 🚀 Adam Golan Adam Golan Adam Golan Follow Oct 8 '24 🚀 Vanilla Framework Update 🚀 # vanillaframework # frontend # webdev 1 reaction Comments Add Comment 1 min read Introducing "Vanilla" – A Fresh Take on Frontend Development Adam Golan Adam Golan Adam Golan Follow Oct 1 '24 Introducing "Vanilla" – A Fresh Take on Frontend Development # javascript # typescript # github # frontend Comments Add Comment 2 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 Forem — Your community HQ 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 . Forem © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:23 |
https://www.suprsend.com/post/how-to-implement-in-app-notifications-to-your-angular-app | How To Implement In-App Inbox Notification Center In Your Angular Application? Product FEATURES Template Engine Powerful template editors for all channels App Inbox Fully customizable inbox for your app & website Analytics Deep data insights on notification performance Logs Real-time notifications logs for all channels Smart Routing Reach users where they are Branding Seamlessly manage multi-brand customization Workflows Craft complex notification workflows Bifrost Run notifications natively on data warehouse Preferences Develop user focused notifications Integrations Integrate any channel and provider within mins Solutions BY USECASES Transactional Real-time alerts like authentication, activity updates Batching & Digest Aggregate multiple alerts into one Collaboration & Action Alerts on cross-user activity Scheduled Notifications One-time or recurring alerts like reminders Multi-tenant Alerts tailored to your customer's preferences Announcement / Newsletters Feature releases, achievements, product & policy updates Pricing Docs Customers Blog Login Get Started For Free Login Sign up Inapp Inbox Notifications How To Implement In-App Inbox Notification Center In Your Angular Application? Sanjeev Kumar • April 15, 2025 TABLE OF CONTENTS Integrating a SuprSend Angular notification center within your app can significantly enhance the user experience by providing a centralized hub for viewing, interacting with, and managing in-app notifications. suprsend-app-inbox With SuprSend’s Angular SDK, you can implement a feature-rich, customizable In-App Inbox Notification Center with minimal effort. This guide will walk you through the process of setting up an in-app notification center with SuprSend and highlight its key features. Why Build an In-App Inbox in Angular? An in-app inbox (or notification center) provides: Persistent alerts users can refer back to Personalized messages based on user behavior Real-time notification infrastructure without relying on external push A message hub for system alerts, marketing messages, and app events A scalable alternative to building notification features from scratch This makes in-app inboxes critical for SaaS products, marketplaces, and user-focused applications. How In-App Notification Centers are Designed Designing an in-app notification center from scratch can be complex. You need to manage multiple components, such as user identification, message storage, real-time updates, and UI elements. The SuprSend SDK handles most of these for you, offering a ready-made solution that you can customize to fit your needs. Below is a breakdown of the main components involved in setting up an in-app inbox: User Identification – Personalize notifications by identifying individual users through a unique user ID or subscription key. Message Handling – Manage the storage, display, and update of messages within the app. UI Components – Create a visual interface where users can interact with their notifications. This includes features like unread counters, bell icons, and toast notifications. Customization – Tailor the inbox's appearance and behavior, including notification cards, headers, action buttons, and more. SuprSend’s SDK abstracts most of these complexities, offering you a quick and efficient setup while allowing for deep customization if needed. How To Add In-App Notifications To Your Angular App Prerequisites Before integrating SuprSend’s notification center, ensure you have an Angular app ready to go. You can learn how to build an Angular app from scratch from here Angular - Build your first Angular app You can build a basic Angular app using a local installation of the Angular tools or by using StackBlitz in a web browser. Local Angular development can be completed on Windows, MacOS or Linux based systems. Step 1: Sign Up on SuprSend Visit SuprSend’s official website, sign up , and create your workspace. Once set up, you’ll receive a workspace key and secret, which you’ll use to authenticate your app’s connection to SuprSend’s services. How to Add a Notification Center Quickly with SuprSend Setting up the notification center is straightforward and can be done in just a few steps. Installation Start by installing SuprSend’s Angular SDK, along with the necessary dependencies like js-inbox and Popper.js. npm install @suprsend/ngx-inbox @suprsend/js-inbox @popperjs/core Initialization Next, initialize the SuprSend inbox module in your Angular app by importing SuprSendInboxModule into your app module. Don’t forget to provide your workspace key and secret. import { SuprSendInboxModule } from '@suprsend/ngx-inbox'; @NgModule({ imports: [ SuprSendInboxModule.forRoot({ workspaceKey: 'your workspaceKey', workspaceSecret: 'your workspaceSecret', }), ], }) export class AppModule {} User Identification To send personalized notifications, identify users by passing their distinct_id and subscriber_id: import { SuprSendInboxService } from '@suprsend/ngx-inbox'; export class MyComponent implements OnInit { constructor(private ssinbox: SuprSendInboxService) {} async ngOnInit() { this.ssinbox.identifyUser('distinct_id', 'subscriber_id'); } } Testing Finally, you can integrate the notification center in your app's UI and test it: <suprsend-inbox></suprsend-inbox> Feature-Rich SuprSend Inbox: What It Offers SuprSend’s inbox has features that help streamline user engagement and simplify notification management. Some of the key features include: 1. Action Buttons : Notifications can include primary and secondary action buttons to allow users to respond or perform an action directly from the notification. Customization : You can customize the styling of both action buttons and set custom click handlers. <SuprsendInbox theme={{ notification : { actions : [ { container : { backgroundColor : 'blue' }, text : { color : 'white' } }, { container : { backgroundColor : 'gray' }, text : { color : 'yellow' } } ] } }} primaryActionClickHandler={ ( data ) => handlePrimaryAction(data)} secondaryActionClickHandler={ ( data ) => handleSecondaryAction(data)} /> 2. Notification Status Tracking : The platform provides real-time tracking of notifications’ read/unread status. This data can be analyzed to gain insights into user engagement. Customization : You can add custom click handlers to respond to users' interactions with notifications. <SuprsendInbox notificationClickHandler={(notificationData) => handleNotificationClick(notificationData)} /> 3 .Tabs and Filters : Notifications can be categorized and organized using tabs and filters. This helps users navigate notifications more easily, improving the overall user experience. Customization : You can adjust the style of tabs and filters, or even hide certain tabs or counters based on your design preferences. <SuprsendInbox theme={{ tabs: { color: 'red', unselectedColor: 'gray', bottomColor: 'blue' } }} /> 4. Expiry Timer Configuration The expiry feature allows you to add an expiration timer to notifications with customizable styling options. Property Description Example Background Color Set the background color of the expiry text theme={{ notification: { expiresText: { backgroundColor: 'red' } } }} Text Color Set the text color of the expiry text theme={{ notification: { expiresText: { color: 'white' } } }} Expiring Background Color Set the background color when the notification is about to expire theme={{ notification: { expiresText: { expiringBackgroundColor: 'orange' } } }} Expiring Text Color Set the text color when the notification is about to expire theme={{ notification: { expiresText: { expiringColor: 'black' } } }} 5. Pinning Feature The pinning feature allows users to pin important notifications for quick access. Property Description Example Text Color Set the color of the pinned text theme={{ notification: { pinnedText: { color: 'blue' } } }} Icon Color Set the color of the pin icon theme={{ notification: { pinnedIcon: { color: 'gold' } } }} 6. Mark as Read/Unread : Users can easily mark notifications as read or unread. This helps them prioritize and manage important information. The notification card visually indicates its read status by toggling between different styles for read and unread messages. Customization : Use the notificationComponent prop to create custom behavior for marking notifications as read or unread. <SuprsendInbox notificationComponent={({ notificationData, markRead, markUnRead }) => ( <CustomNotificationCard data={notificationData} markAsRead={markRead} markAsUnRead={markUnRead} /> )} /> 7. Cross-Browser and Device Sync : Notifications are synchronized across all devices and browsers. Whether a user reads a notification on their desktop or mobile, SuprSend ensures their actions are synced in real-time, providing a seamless experience. Customization Options SuprSend’s appinbox component is not just feature-rich; it’s also highly customizable. Here's a breakdown of how you can modify the inbox to fit your app's unique design needs: inbox-customisation 1. Inbox Theme Customization : SuprSend angular inapp inbox supports both light and dark themes by default, but you can fully control the styling using the theme prop. <SuprsendInbox themeType="light" /> <SuprsendInbox themeType="dark" /> For more advanced styling, you can provide custom CSS properties for specific elements like the header, body, or action buttons. <SuprsendInbox theme={{ header: { container: { backgroundColor: 'black' }, headertext: { color: 'white' } }, notification: { container: { unreadBackgroundColor: 'lightgray', readBackgroundColor: 'white' } } }} /> 2. Customizing Notification Cards : Notification cards can be styled based on their state (read/unread). You can also customize the look of individual parts, like the header text, body text, or action buttons. <SuprsendInbox theme={{ notification: { container: { unreadBackgroundColor: 'lightblue', readBackgroundColor: 'lightgray' }, headerText: { color: 'darkblue' }, bodyText: { color: '#333' }, unseenDot: { backgroundColor: 'red' } } }} /> 3. Custom Bell Icon : You can modify the default bell icon or provide a custom bell component. <SuprsendInbox bellComponent={() => <CustomBellIcon />} theme={{ bell: { color: 'green' } }} /> 4. Custom Badge (Notification Counter) : The badge component, which shows the number of unseen notifications, is fully customizable. You can change its style or pass your own badge component. <SuprsendInbox badgeComponent={({ count }) => <CustomBadge count={count} />} theme={{ badge: { backgroundColor: 'pink', color: 'white' } }} /> You can check out this documentation to find more about customizations: Embeddable Inbox (suprsend.com) Test the Notification Center Testing is an essential step to ensure your notification center functions correctly. Use SuprSend’s built-in tools to test real-time notifications, user identification, and customization options within different environments and devices. You can analyze if an app inbox is initialized by checking the logs section on SuprSend. You can also check if the API events are passed correctly by checking your browser’s Network console. browser-test-for-appinbox You can also test the notification workflow from the Test Workflow button on the Workflow dashboard. Why Choose SuprSend Over Building Your Own In-App Notification Center Building a fully functional notification center from scratch requires significant resources, including time and technical expertise. SuprSend streamlines this process by offering: Ready-to-use SDKs in all major languages. React components and example apps to embed Inbox UI in your product quickly. Customization options to fit your product’s branding and design. Scalable and reliable service, without any infra setup or maintenance. Advanced features like action buttons, language translation, state management (mark as read/unread, archive), toasts, pinning and expiry. Real-time feed and cross-browser / device compatibility using web socket. What are the benefits of in-app notifications for your Angular app? An In-App Inbox Notification Center is more than just a notification feed, it’s a user engagement hub delivering real-time updates within the app. Let's explore the key benefits of adding an in-app notification system: 1. Delivering Real-Time Updates Ensure your users receive immediate alerts and information without relying on external channels. With real-time notifications, users remain informed about important events and changes directly within the app. 2. Boosting User Engagement In-app notification in Angular encourages interaction without disrupting the user experience. Users can review, dismiss, or act on messages seamlessly, boosting their overall engagement with your application. 3. Personalized Communication Tailor notifications to individual users based on their behavior and preferences. This leads to more relevant and impactful messaging, increasing the chances of user interaction. 4. Persistent Messaging Unlike traditional notifications that vanish after dismissal, in-app notifications remain accessible until the user interacts with them. This ensures that critical information is not missed and can be revisited later. 5. Unified Notification Hub Manage notifications from various sources, such as marketing campaigns, in-app activities, and system alerts, within a single interface. This makes it easy for users to track all messages in one place. 6. Actionable Notifications Include buttons or links in your notifications to allow users to take action immediately, improving the efficiency of your communication. 7. Cross-Device Sync Ensure notifications are synchronized across different devices and browsers. SuprSend’s inbox supports seamless syncing, providing a consistent experience for users. Conclusion Integrating SuprSend’s In-App Inbox Notification Center into your Angular application is a smart, efficient way to boost user engagement and streamline communication. Whether you’re delivering real-time updates or personalizing user experiences, SuprSend offers a robust, customizable solution that’s quick to implement and easy to maintain. For more detailed documentation, explore SuprSend’s official documentation here . FAQs: SuprSend In-App Inbox in Angular ❓ What is SuprSend's in-app inbox? SuprSend’s in-app inbox is a customizable notification center that lives inside your app, letting users see, manage, and interact with notifications in real-time. ❓ What’s the difference between in-app messaging and inbox? In-app messaging is typically transient (like toasts). An in-app inbox persists messages, lets users revisit old notifications, and supports richer interactions. ❓ Is SuprSend’s inbox SDK open source? The SDK itself is proprietary but built on open standards. You can integrate it easily without worrying about maintenance or infrastructure. ❓ Can I use SuprSend for cross-device syncing? Yes, SuprSend syncs inbox states across desktop, mobile, and web sessions in real-time using sockets. ❓ What types of apps benefit most from an in-app inbox? SaaS platforms Fintech apps Marketplaces Social platforms Developer tools Edtech and productivity apps Share this blog on: Written by: Sanjeev Kumar Engineering, SuprSend Implement a powerful stack for your notifications Get Started For Free Book Demo Company About us Signup Login Integrations Pricing Security Privacy Terms Contact Us Support SuprSend for Startups API Status Sign Up Channels Email SMS Notification Inbox Android Push iOS Push Web Push Xiaomi Push Whatsapp SDK Python SDK Node.js SDK Java SDK Android SDK React Native SDK iOS SDK Flutter SDK Go SDK Resources Documentation Changelog Blogs Write for us SMTP Error Codes SMS Providers Comparisons Email Providers Comparisons SMS Providers Alternatives Join us on Slack We are building a community of developers and product builders from across the globe to make notifications a pleasant experience. © 2025 All rights reserved. SuprStack Inc. { "@context": "https://schema.org", "@type": "TechArticle", "name": "How to Add an In-App Notification Center to Your Angular App Using SuprSend", "author": { "@type": "Organization", "name": "SuprSend" }, "about": [ { "@type": "Thing", "name": "SuprSend in-app inbox" }, { "@type": "Thing", "name": "Angular in-app messaging" }, { "@type": "Thing", "name": "Angular notification infrastructure" } ], "headline": "Integrating SuprSend’s In-App Notification Center in Angular", "datePublished": "2025-04-15", "publisher": { "@type": "Organization", "name": "SuprSend", "url": "https://www.suprsend.com" }, "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.suprsend.com/post/implement-in-app-inbox-notification-center-in-your-angular-app" } } By clicking “Accept All Cookies” , you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information. Preferences Deny Accept Privacy Preference Center When you visit websites, they may store or retrieve data in your browser. This storage is often necessary for the basic functionality of the website. The storage may be used for marketing, analytics, and personalization of the site, such as storing your preferences. Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website. Reject all cookies Allow all cookies Manage Consent Preferences by Category Essential Always Active These items are required to enable basic website functionality. Marketing Essential These items are used to deliver advertising that is more relevant to you and your interests. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. Advertising networks usually place them with the website operator’s permission. Personalization Essential These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features. For example, a website may provide you with local weather reports or traffic news by storing data about your current location. Analytics Essential These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues. This storage type usually doesn’t collect information that identifies a visitor. Confirm my preferences and close Get 10% OFF on your next order Subscribe to our newsletter and receive a 10% OFF coupon to use on your next order. Please check your email for your 10% OFF coupon Oops! Something went wrong while submitting the form. | 2026-01-13T08:49:23 |
https://open.forem.com/sergueyasaelshinder/on-being-productive-without-being-busy-558b | On Being Productive Without Being Busy - 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 Serguey Asael Shinder Posted on Jan 8 On Being Productive Without Being Busy # discuss # motivation # productivity For a long time, I confused movement with progress. Full calendars felt reassuring. Long to-do lists made the day look important. If I was busy, I assumed I was doing something right. But busyness has a strange way of hiding the truth. It fills time without asking whether the time matters. It replaces intention with motion. Eventually, I noticed that my most meaningful days were rarely the busiest ones. They were quieter. More deliberate. Fewer tasks, but clearer outcomes. Real productivity isn’t about how much you do. It’s about how little you need to do to move something forward. One focused hour can outperform a full day of fragmented attention. Busyness often comes from avoidance. Avoiding hard decisions. Avoiding saying no. Avoiding the discomfort of choosing what actually matters and letting the rest drop. When you stop trying to look productive, your days change shape. You plan less. You protect space. You work with more patience and fewer interruptions. There’s no status in exhaustion, even if it’s socially rewarded. Being constantly busy doesn’t mean you’re needed. It often means boundaries are missing. The goal isn’t an empty schedule. It’s a clear one. A day where effort is visible, not scattered. Where energy goes somewhere on purpose. Doing less, intentionally, isn’t laziness. It’s respect for time — yours and everyone else’s. – Serguey Asael Shinder 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 Serguey Asael Shinder Follow I am also writing on Medium https://medium.com/@serguey.shinder_24310 Joined May 14, 2025 💎 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:49:23 |
https://atproto.com/specs/xrpc | HTTP API (XRPC) - AT Protocol Find something... K SDKs Blog GitHub English Português 日本語 한국어 API Documentation Support Home Introduction ATProto Ethos SDKs Glossary FAQ Building apps Quick start Cookbook ⧉ Distributed Systems Guides Overview Identity Data Repositories Schemas & Lexicon Lexicon Style Guide PDS Self-Hosting Going to production OAuth Introduction Permission Requests Account Migration Specs AT Protocol Data Model Lexicon Cryptography Accounts Repository Blobs Labels HTTP API (XRPC) OAuth Permissions Event Stream Sync DID Handle NSID TID Record Key URI Scheme HTTP API (XRPC) HTTP APIs for client-server and server-server requests in atproto use a set of common conventions called XRPC. Endpoint path names include an NSID indicating the Lexicon specifying the request and response schemas, usually with JSON content type. Lexicon HTTP Endpoints The HTTP request path starts with /xrpc/ , followed by an NSID. Paths must always be top-level, not below a prefix. The NSID maps to the id field in the associated Lexicon. The two requests types that can be expressed in Lexicons are "query" (HTTP GET) and "procedure" (HTTP POST). Following HTTP REST semantics, queries (GET) are cacheable and should not mutate resource state. Procedures are not cacheable and may mutate state. Lexicon params (under the parameters field) map to HTTP URL query parameters. Only certain Lexicon types can be included in params, as specified by the params type. Multiple query parameters with the same name can be used to represent an array of parameters. When encoding boolean parameters, the strings true and false should be used. Strings should not be quoted. If a default value is included in the schema, it should be included in every request to ensure consistent caching behavior. Request and response body content types can be specified in Lexicon. The schema can require an exact MIME type, or a blob pattern indicating a range of acceptable types (eg, image/* ). JSON body schemas are specified in Lexicon using the usual atproto data model. Full validation by the server or client requires knowledge of the Lexicon, but partial validation against the abstract data model is always possible. CORS support is encouraged but not required. Error Responses All unsuccessful responses should follow a standard error response schema. The Content-Type should be application/json , and the payload should be a JSON object with the following fields: error (string, required): type name of the error (generic ASCII constant, no whitespace) message (string, optional): description of the error, appropriate for display to humans The error type should map to an error name defined in the endpoint's Lexicon schema. This enables more specific error-handling by client software. This is particularly encouraged on 400 , 500 , and 502 status codes, where further information will be useful. Blob Upload and Download Blobs are something of a special case because they can have any MIME type and are not stored directly in repositories, and thus are not directly associated with an NSID or Lexicon (though they do end up referenced from Lexicons). The convention for working with blobs is for clients to upload them via the com.atproto.repo.uploadBlob endpoint, which returns a blob JSON object containing a CID and basic metadata about the blob. Client can then include this blob data in future requests (eg, include in new records). Constraints like MIME type and file size are only validated at this second step. The server may implement content type sniffing at the upload step and return a MIME type different from any Content-Type header provided, but a Content-Type header is still expected on the upload HTTP request. Blobs for a specific account can be listed and downloaded using endpoints in the com.atproto.sync.* NSID space. These endpoints give access to the complete original blob, as uploaded. A common pattern is for applications to mirror both the original blob and any downsized thumbnail or preview versions via separate URLs (eg, on a CDN), instead of deep-linking to the getBlob endpoint on the original PDS. Cursors and Pagination A common pattern in Lexicon design is to include a cursor parameter for pagination. The client should not include the cursor parameter in the first request, and should keep all other parameters fixed between requests. If a cursor is included in a response, the next batch of responses can be fetched by including that value in a follow-on, continuing until the cursor is not included any longer, indicating the end of the result set has been reached. Authentication The primary client/server authentication and authorization scheme for XRPC is OAuth, described in the Auth Specification . Not all endpoints require authentication, but there is not yet a consistent way to enumerate which endpoints do or do not. There is also a legacy authentication scheme using HTTP Bearer auth with JWT tokens, including refresh tokens, described here. Initial login uses the com.atproto.server.createSession endpoint, including the password and an account identifier (eg, handle or registered email address). This returns a refreshJwt (as well as an initial accessJwt ). Most requests should be authenticated using an access JWT, but the validity lifetime for these tokens is short. Every couple minutes, a new access JWT can be requested by hitting the com.atproto.server.refreshSession endpoint, using the refresh JWT instead of an access JWT. Clients should treat the tokens as opaque string tokens: the JWT fields and semantics are not a stable part of the specification. Servers (eg, PDS implementations) which generate and valiate auth JWTs should implement domain separation between access and refresh tokens, using the typ header field: access tokens should use at+jwt , and refresh tokens should use refresh+jwt . Note that at+jwt (defined in RFC 9068 ) is short for "access token", and is not a reference to the "at" in atproto. App Passwords App Passwords are a mechanism to reduce security risks when logging in to third-party clients and web applications. Accounts can create and revoke app passwords separate from their primary password. They are used to log in the same way as the primary password, but grant slightly restricted permissions to the client application, preventing destructive actions like account or changes to authentication settings (including app passwords themselves). Clients and apps themselves do not need to do anything special to use app passwords. It is a best practice for most clients and apps to include a reminder to use an app password when logging in. App passwords usually have the form xxxx-xxxx-xxxx-xxxx , and clients can check against this format to prevent accidental logins with primary passwords (unless the primary password itself has this format). Admin Token (Temporary Specification) Some administrative XRPC endpoints require authentication with admin privileges. The current scheme for this is to use HTTP Basic authentication with user "admin" and a fixed token in the password field, instead of HTTP Bearer auth with a JWT. This means that admin requests do not have a link to the account or identity of the client beyond "admin". As a reminder, HTTP Basic authentication works by joining the username and password together with a colon ( : ), and encoding the resulting string using base64 ("standard" version). The encoded string is included in the Authorization header, prefixed with Basic (with separating space). As an example, if the admin token was secret-token , the header would look like: Authorization: Basic YWRtaW46c2VjcmV0LXRva2Vu Copy Copied! The set of endpoints requiring admin auth is likely to get out of date in this specification, but currently includes: com.atproto.admin.* com.atproto.server.createInviteCode com.atproto.server.createInviteCodes Inter-Service Authentication (JWT) This section describes a mechanism for authentication between services using signed JWTs. The current mechanism is to use short-lived JWTs signed by the account's atproto signing key. The receiving service can validate the signature by checking this key against the account's DID document. The JWT parameters are: alg header field (string, required): indicates the signing key type (see Cryptography ) use ES256K for k256 keys use ES256 for p256 keys typ header field (string, required): currently JWT , but intend to update to a more specific value. iss body field (string, required): account DID that the request is being sent on behalf of. This may include a suffix service identifier; see below aud body field (string, required): service DID associated with the service that the request is being sent to exp body field (number, required): token expiration time, as a UNIX timestamp with seconds precision. Should be a short time window, as revocation is not implemented. 60 seconds is a good token lifetime. iat body field (number, required): token creation time, as a UNIX timestamp with seconds precision. lxm body field (string, optional): short for "lexicon method". NSID syntax. Indicates the endpoint that this token authorizes. Servers must always validate this field if included, and should require it for security-sensitive operations. May become required in the future. jti body field (string, required): unique random string nonce. May be used by receiving services to prevent reuse of token and replay attacks. JWT signature (string, required): base64url-encoded signature using the account DID's signing key. When the token is generated in the context of a specific service in the issuer's DID document, the issuer field may have the corresponding service identifier in the iss field, separated by a # character. For example, did:web:label.example.com#atproto_labeler for a labeler service. When this is included the appropriate signing key is determined based on a fixed mapping of service identifiers to key identifiers: service identifier atproto_labeler maps to key identifier atproto_label If the service identifier is not included, the scope is general purpose and the atproto key identifier should be used. The receiving service may require or prohibit specific service identifiers for access to specific resources or endpoints. The signature is computed using the regular JWT process, using the account's signing key (the same used to sign repo commits). As Typescript pseudo-code, this looks like: const headerPayload = utf8ToBase64Url(jsonStringify(header)) + '.' + utf8ToBase64Url(jsonString(body)) const signature = hashAndSign(accountSigningKey, utf8Bytes(headerPayload)) const jwt = headerPayload + '.' + bytesToBase64Url(signature) Copy Copied! Service Proxying The PDS acts as a generic proxy between clients and other atproto services. Clients can use an HTTP header to specify which service in the network they want the request forwarded to (eg, a specific AppView or Labeler service). The PDS will do some safety checks, then forward the request on with an inter-service authentication token (JWT, described above) issued and signed by the user's identity. The HTTP header is atproto-proxy , and the value is a DID (identifying a service), followed by a service endpoint identifier, joined by a # character. The PDS resolves the service DID, extracts a service endpoint URL from the DID document, and proxies the request on to the identified server. An example request header, to proxy to a labeling service, is: atproto-proxy: did:web:labeler.example.com#atproto_labeler Copy Copied! A few requirements must be met for proxying to happen. These conditions may be extended in the future to address network abuse concerns. the target service must have a resolvable DID, a well-formed DID document, and a corresponding service entry with a matching identifier only atproto endpoint paths are supported. This means an /xrpc/ prefix, followed by a valid NSID and endpoint name. Note that the /xrpc/ prefix may become configurable in the future the request must be from an authenticated user with an active account on the PDS rate-limits at the PDS still apply Summary of HTTP Headers Clients can use the following request headers: Content-Type : If a request body is present, this header should be included and indicate the content type. Authorization : Contains auth information. See "Authentication" section of this specification for details. atproto-proxy : used for proxying to other atproto services. See "Service Proxying" section of this document for details. atproto-accept-labelers : used by clients to request labels from specific labelers to be included and applied in the response. See Label specification for details. Summary of HTTP Status Codes 200 OK : The request was successful. If there is a response body (optional), there should be a Content-Type header. 400 Bad Request : Request was invalid, and was not processed 401 Unauthorized : Authentication is required for this endpoint. There should be a WWW-Authenticate header. 403 Forbidden : The client lacks permission for this endpoint 404 Not Found : Can indicate a missing resource. This can also indicate that the server does not support atproto, or does not support this endpoint. See response error message (or lack thereof) to clairfy. 413 Payload Too Large : Request body was too large. If possible, split in to multiple smaller requests. 429 Too Many Requests : A resource limit has been exceeded, client should back off. There may be a Retry-After header indicating a specific back-off time period. 500 Internal Server Error : Generic internal service error. Client may retry after a delay. 501 Not Implemented : The specified endpoint is known, but not implemented. Client should not retry. In particular, returned when WebSockets are requested by not implemented by server. 502 Bad Gateway , 503 Service Unavailable , or 504 Gateway Timeout : These all usually indicate temporary or permanent service downtime. Clients may retry after a delay. Usage and Implementation Guidelines Clients are encouraged to implement timeouts, limited retries, and randomized exponential backoff. This increases robustness in the inevitable case of sporadic downtime, while minimizing load on struggling servers. Servers should implement custom JSON error responses for all requests with an /xrpc/ path prefix, but realistically, many services will return generic load-balancer or reverse-proxy HTML error pages. Clients should be robust to non-JSON error responses. HTTP servers and client libraries usually limit the overall size of URLs, including query parameters, and these limits constrain the use of parameters in XRPC. PDS implementations are free to restrict blob uploads as they see fit. For example, they may have a global maximum size or restricted set of allowed MIME types. These should be a superset of blob constraints for all supported Lexicons. Security and Privacy Considerations Only HTTPS should be used over the open internet. Care should be taken with personally identifiable information in blobs, such as EXIF metadata. It is currently the client's responsibility to strip any sensitive EXIF metadata from blobs before uploading. It would be reasonable for a PDS to help prevent accidental metadata leakage as well; see future changes section below. Possible Future Changes The auth system is likely to be entirely overhauled. Lexicons should be able to indicate whether auth is required. The role of the PDS as a generic gateway may be formalized and extended. A generic mechanism for proxying specific XRPC endpoints on to other network services may be added. Generic caching of queries and blobs may be specified. Mutation of third-party responses by the PDS might be explicitly allowed. An explicit decision about whether HTTP redirects are supported. Cursor pagination behavior should be clarified when a cursor is returned but the result list is empty, and when a cursor value is repeated. To help prevent accidental publishing of sensitive metadata embedded in media blobs, a query parameter may be added to the upload blob endpoint to opt-out of metadata stripping, and default to either blocking upload or auto-striping such metadata for all blobs. The lxm JWT field for inter-service auth may become required. Previous Labels Next OAuth © Copyright 2026 . All rights reserved. Follow us on Bluesky Follow us on GitHub | 2026-01-13T08:49:23 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.