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://blog.jetbrains.com/qodana/ | Qodana | The Qodana Blog Skip to content Topics Search Language English Deutsch Español Français 日本語 한국어 简体中文 Português do Brasil Burger menu icon IDEs CLion DataGrip DataSpell Fleet GoLand IntelliJ IDEA PhpStorm PyCharm RustRover Rider RubyMine WebStorm Plugins & Services Big Data Tools Code With Me JetBrains Platform Scala Toolbox App Writerside JetBrains AI Grazie Junie JetBrains for Data Kineto Team Tools Datalore Space TeamCity Upsource YouTrack Hub Qodana CodeCanvas Matter .NET & Visual Studio .NET Tools ReSharper C++ Languages & Frameworks Kotlin Ktor MPS Amper Education & Research JetBrains Academy Research Company Company Blog Security Qodana The code quality platform for teams Follow Follow: X X RSS RSS Get Qodana All News Tutorials Features Opinion Promo image code quality Maven Qodana Top 3 Qodana 2025.3 Release Highlights Qodana 2025.3 delivers important new capabilities that help teams standardize their development practices, improve compliance, make audits easier, and simplify large-scale code analysis. Fro… Read article Deploying Qodana on Kubernetes: More Scalability, More Control As engineering teams scale, so do the demands on their tooling. Code quality checks that worked well for one repository or service often need a more resilient, automated, and infrastructure-native setup when development ecosystems grow. That’s exactly why we’re excited to introduce first-class K… Kerry Beetge Mark Your Calendars! Qodana Events in November As 2025 starts racing to a close, the JetBrains Qodana team is ending the year with a series of events dedicated to what matters most in modern software development: secure workflows, high-quality code, and practical tooling that empowers developers to ship with confidence.Whether you're working in … Kerry Beetge What Developers Really Mean by “Bad Code” The phrase “bad code” gets thrown around in reviews and online forums all the time. But what does it actually mean? It’s a good example of the vague terms that occasionally make the rounds in developer circles without much to qualify them. We’ve collected opinions on the subject, metrics, a… Kerry Beetge The Modern Enterprise Toolkit for Secure, High-Quality Code On November 19, 2025, join JetBrains Qodana for a live session exploring how enterprises can embed quality, security, and compliance directly into their development workflows. Hosted by Product Specialist, Kai Schmithuesen, this session will walk you through the latest Qodana capabilities and rea… Kerry Beetge Qodana’s Public API Is Now Available! The Qodana Public API is now live, complete with full documentation, examples, and OpenAPI specifications. This release gives all Qodana Cloud users the ability to integrate Qodana directly into their own systems, automate key workflows, and access core functionality programmatically. View Docume… Kerry Beetge “I tried out JetBrains’ code analysis tool Qodana” This is the English version of the Japanese article first published by Jan Maki on Qiita. This post was not commissioned by Qodana and was written independently. For more information please reach out to them in the comments or via their link tree. Qodana is JetBrains’ code analysis platform f… Kerry Beetge The Dark Side of AI at Work: Why “Shadow AI” Could Cost You Why shadow AI can be dangerous1. Data leakage2. Security vulnerabilities3. Compliance violations4. Lack of auditabilityReal-world example: Samsung’s Source Code Leak via ChatGPTHow Qodana reduces shadow AI risksCompliance assuranceSecurity-focused scanningPolicy enforcement across teamsTraceability … Kerry Beetge The Best Software Composition Analysis Tools for Modern Development Best software composition analysis tools Qodana and Mend.io: SCA inside your JetBrains workflow1. Mend.io on its own2. Snyk3. OWASP Dependency‑Check4. Black Duck by Synopsys5. FOSSAHow SCA and static code analysis work togetherQodana is more of a SAST tool but does have some SCA capabilities A… Kerry Beetge Software Composition Analysis vs. Static Code Analysis: What’s the Difference? Discover the differences when it comes to software Composition Analysis vs. Static Code Analysis with Qodana. Kerry Beetge 5 Ways Static Code Analysis Can Improve Developer Experience Improve developer experience with static code analysis. Developer experience is not only about nice editors and fast build times. It is about reducing friction so developers can focus on solving problems rather than fighting with tools. Among the most effective developer experience tools availab… Kerry Beetge New Quarter, New Qodana 2025.2 Release Highlights Following the recent rollout of our new Insights dashboard, Native mode, Self-Hosted Lite version, SSO functionality, and Visual Studio plugin, our Qodana 2025.2 update promises another round of improvements and extensions. Take a look at what we’ve been doing as we focus on providing greater access… Kerry Beetge How to Integrate Qodana Into TeamCity Integrate Qodana into TeamCity There are many compelling reasons to use TeamCity as your CI server. Thanks to its out-of-the-box features, smart test management capabilities, and great scalability for enterprises, TeamCity offers a robust and reliable CI solution. But if you’re really looking to … Kerry Beetge Load more Subscribe to Qodana Blog updates Subscribe form Submit button By submitting this form, I agree to the JetBrains Privacy Policy By submitting this form, I agree that JetBrains s.r.o. ("JetBrains") may use my name, email address, and location data to send me newsletters, including commercial communications, and to process my personal data for this purpose. I agree that JetBrains may process said data using third-party services for this purpose in accordance with the JetBrains Privacy Policy . I understand that I can revoke this consent at any time in my profile . In addition, an unsubscribe link is included in each email. Thanks, we've got you! Privacy & Security Terms of Use Legal Genuine tools Language English Deutsch Español Français 日本語 한국어 简体中文 Português do Brasil Twitter Facebook Linkedin Instagram Youtube RSS Tiktok Merchandise store icon Merchandise store Copyright © 2000 JetBrains s.r.o. | 2026-01-13T08:48:37 |
https://help.lob.com/developer-docs/quickstart-guide | API quickstart guide | Lob Help Center bars search circle-xmark Ctrl k API Docs Template Gallery Product Updates Contact Us chevron-down More ellipsis chevron-down 📬 Print & Mail Ready to get started? chevron-right Integrations chevron-right Reaching your audience chevron-right Designing mail creatives chevron-right Building a mail strategy chevron-right Send mail! chevron-right Getting data & results chevron-right 🏠 Address Verification Ready to start AV? chevron-right AV best practices AV integrations & libraries chevron-right AV FAQs 💻 Developer Docs API quickstart guide SDKs & libraries Postman & similar tools Error reference Upgrading API version Technical use case guides chevron-right 🔑 Account Management Signing into Lob API keys Account settings chevron-right User settings Billing chevron-right 📞 Resources Getting support Data retention Sustainability Private labeling Lob Direct mail glossary gitbook Powered by GitBook block-quote On this page chevron-down copy Copy chevron-down 💻 Developer Docs API quickstart guide Jump in and explore our APIs Overview of sending mail with Lob's APIs The following quickstart guide allows you to jump in and explore the Lob Print & Mail API arrow-up-right in your preferred programming language. hashtag Lob account basics In order to follow this Quickstart guide, you will need: A Lob account; create your account here arrow-up-right . Your API keys (you can find these in your Dashboard under Settings → API Keys) hashtag Language setup guides These brief sections are aimed at developers who are less familiar with the languages with which they will be working with Lob API. Currently, Lob provides client libraries in the following languages: (Note: If you are a TypeScript user, you can jump right in with a video tutorial: Sending a postcard with Typescript arrow-up-right .) TypeScript (NodeJS) Python Ruby PHP Java C#/.NET Follow the instructions on the TypeScript download page arrow-up-right . For Windows, installing through the Visual Studio text editor is the best option. Follow the download and setup instructions on the official Node.js website arrow-up-right . To make switching between Node versions easy, install nvm on your local machine, following the instructions arrow-up-right in the official Node Version Manager GitHub repository. To get the latest LTS release, run: Alternatively, Windows users should install the latest release arrow-up-right of nvm-windows by following the instructions arrow-up-right in its home repository. Download and set up the appropriate version from Python’s official website arrow-up-right . hashtag Mac Run ruby -v to check whether it’s pre-installed. If not, run brew install ruby (make sure to install Homebrew arrow-up-right first if you haven’t already). Add the path for your version of Ruby to your environment’s PATH variable. hashtag Windows Download the appropriate version from Ruby’s official downloads page arrow-up-right . hashtag Mac Run php -v to check whether it’s pre-installed. If not, run brew install php (make sure to install Homebrew arrow-up-right first if you haven’t already). Add the path for your version of PHP to your environment’s PATH variable. arrow-up-right hashtag Windows Download the appropriate version from PHP's official downloads page. arrow-up-right Download either the Arm 64 or x64 DMG Installer from Java’s official downloads page arrow-up-right . Download from Microsoft's official website arrow-up-right . hashtag Installing Lob’s API client This Quickstart guide provides a code example of one of Lob’s core services: creating a postcard through our Print & Mail API. Make sure you are in the correct directory before running the code samples (creating one for the purpose of running these is advised, but not required). Create a new directory and switch to it from your terminal app with these commands. mkdir lob-qs cd lob-qs The next step is to install the version of Lob API which matches the language you are working in: Typescript Python Ruby PHP Java C#/.NET Install Lob's TypeScript SDK npm install @lob/lob-typescript-sdk Create a new virtual environment python3 -m venv venv Activate the environment source venv/bin/activate Install lob python from pypi pip install lob_python gem install lob In this guide, we will be using Maven arrow-up-right . From the command line, create a new maven project. Edit the pom.xml file in the my-app folder to include this bit of code: In the pom.xml file update the source and target to 1.8 Create a new C# project dotnet new console Install Lob's .NET SDK dotnet add package lob.dotnet hashtag Creating a Postcard via API Now that a Lob API wrapper has been installed on your local machine, we can begin by sending a request to the API with the data necessary for postcard creation. Open the text editor of your choice (if you need to download one, we recommend Visual Studio Code) and paste the code in the language of your choice: (As a note, if the address in question has a suite or apartment number, you can add in a data point for it as such: -d "to[address_line2]=<OPTIONAL SECONDARY INFORMATION>") TypeScript Python Ruby PHP Java C#/.NET In your working directory: Create a new file app.ts Copy and paste the code below into app.ts Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your typescript project folder: Compile your code tsc app.ts Run your app: node app.js In your working directory: Create a new file app.py Copy and paste the code below into app.py Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your working directory: Run your app: python app.py In your working directory: Create a new file app.rb Copy and paste the code below into app.rb Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your working directory: Run your app: ruby app.rb In your working directory: Create a new file app.php Copy and paste the code below into app.php Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your working directory: Run your app: php app.php In your new maven project: Locate the App.java file in main/java/com/company/app Copy and paste the code below into A pp.java Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your maven project folder: Compile your code: mvn clean install Run your app: mvn exec:java -Dexec.mainClass="com.company.app.App" In your working directory: In your working directory, you should have a file named Program.cs from running the dotnet new console command. Copy and paste the code below into Program.cs . Replace <YOUR_TEST_KEY> with your Lob Test API Key in the code. In your working directory: Run your app: dotnet run hashtag Data formatting To ensure your requests are processed efficiently and without error, it's crucial to submit data in the precise format outlined in our documentation. Adhering to these specifications guarantees the continued reliability and performance of our API services. For fields that are intended to accept only string values, submitting JSON objects in string format (stringified JSON objects) is not supported. Our system automatically parses and validates incoming data according to their expected types. As a result, providing a stringified JSON object in a field designated for string input can cause parsing errors or lead to unexpected validation results. hashtag Understanding the response This is a sample of the postcard object you will receive upon sending a creation request. Some information breakdowns: As you can see, the to and from address objects have been expanded with more detail, including optional fields, creation and modification dates, and sanitized, verified address lines. The postcard object also includes a signed URL to a digital copy of the created postcard, as well as thumbnails in three different sizes of the postcard’s front and back. Generated URLs are kept active for 30 days by default (or 60 seconds for HIPAA-enabled accounts) and can be regenerated by performing a new GET request on the mailpiece ID. front_template_id and back_template_id are null in this particular object because we used inline HTML in the templates, rather than referencing a previously-saved HTML template. Because we did not specify a size, the postcard is the default size of 4x6". Both the send_date and the expected_delivery_date of the postcard are provided for transparency in the mailing process. To see the postcards you have created, log into your Lob dashboard account arrow-up-right and navigate to the “Postcards” tab on the left-side navigation menu. You can toggle between the ones you have created using either your test or live key: hashtag More resources hashtag Github For more comprehensive code examples for the different languages supported by Lob, see the individual GitHub repositories for each language : TypeScript arrow-up-right (see also, Get started sending postcards with TypeScript arrow-up-right video) Python arrow-up-right Ruby arrow-up-right PHP arrow-up-right Java arrow-up-right Elixir arrow-up-right C#/.NET arrow-up-right hashtag Postman You can also explore our APIs with Postman . Previous AV FAQs chevron-left Next SDKs & libraries chevron-right Last updated 5 months ago Was this helpful? Lob account basics Language setup guides Installing Lob’s API client Creating a Postcard via API Data formatting Understanding the response More resources Github Postman Was this helpful? Copy // nvm install --lts Copy curl -sS https://getcomposer.org/installer | php php composer.phar require lob/lob-php php composer.phar install Copy mvn archetype:generate -DgroupId=com.company.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false Copy <dependencies> <dependency> <groupId>com.lob</groupId> <artifactId>lob-java</artifactId> <version>13.0.0</version> </dependency> ... </dependencies> Copy <maven.compiler.source>1.8</maven.compiler.source> <maven.compiler.target>1.8</maven.compiler.target> Copy import {Configuration, Postcard, PostcardsApi, PostcardEditable, AddressEditable } from "@lob/lob-typescript-sdk" async function demo() { const config: Configuration = new Configuration({ username: "<YOUR_TEST_KEY>" }) const postcardData : PostcardEditable = new PostcardEditable({ to: new AddressEditable({ name: "Harry Zhang", address_line1: "210 King Street", address_city: "San Francisco", address_state: "CA", address_zip: "94107" }), from: new AddressEditable({ name: "Leore Avidar", address_line1: "210 King Street", address_city: "San Francisco", address_state: "CA", address_zip: "94107" }), front: "https://s3-us-west-2.amazonaws.com/public.lob.com/assets/templates/4x6_pc_template.pdf", back: "https://s3-us-west-2.amazonaws.com/public.lob.com/assets/templates/4x6_pc_template.pdf" }) try { const result : Postcard = await new PostcardsApi(config).create(postcardData) return result } catch (err: any) { console.error(err) } } demo().then((result)=> console.log(result)).catch() Copy import lob_python from lob_python.exceptions import ApiException from lob_python.model.postcard_editable import PostcardEditable from lob_python.model.address_editable import AddressEditable from lob_python.model.merge_variables import MergeVariables from lob_python.model.country_extended import CountryExtended from lob_python.api.postcards_api import PostcardsApi configuration = lob_python.Configuration( username = "<YOUR_TEST_KEY>" ) postcard_editable = PostcardEditable( description = "First Postcard", front = "<html style='padding: 1in; font-size: 50;'>Front HTML for {{name}}</html>", back = "<html style='padding: 1in; font-size: 20;'>Back HTML for {{name}}</html>", to = AddressEditable( name = "Harry Zhang", address_line1 = "210 King Street", address_city = "San Francisco", address_state = "CA", address_zip = "94107", ), _from = AddressEditable( name = "Leore Avidar", address_line1 = "210 King Street", address_city = "San Francisco", address_state = "CA", address_zip = "94107", address_country = CountryExtended("US") ), merge_variables = MergeVariables( name = "Harry", ), ) with lob_python.ApiClient(configuration) as api_client: api = PostcardsApi(api_client) try: created_postcard = api.create(postcard_editable) print(created_postcard) except ApiException as e: print(e) Copy require 'lob.rb' require 'pp' lob = Lob::Client.new(api_key: "<TEST_API_KEY>") pp lob.postcards.create( description: "First Postcard", to: { name: "Harry Zhang", address_line1: "210 King Street", address_city: "San Francisco", address_state: "CA", address_zip: "94107" }, from: { name: "Leore Avidar", address_line1: "210 King Street", address_city: "San Francisco", address_state: "CA", address_zip: "94107" }, merge_variables: { name: "Harry" }, front: "<html style='padding: 1in; font-size: 50;'>Front HTML for {{name}}</html>", back: "<html style='padding: 1in; font-size: 20;'>Back HTML for {{name}}</html>" ) Copy <?php require __DIR__ . '/vendor/autoload.php'; $lob = new \Lob\Lob('<TEST_API_KEY'); $postcard = $lob->postcards()->create(array( "description" => "First Postcard", "to[name]" => "HARRY ZHANG", "to[address_line1]" => "210 KING STREET", "to[address_city]" => "SAN FRANCISCO", "to[address_state]" => "CA", "to[address_zip]" => "94107", "from[name]" => "LEORE AVIDAR", "from[address_line1]" => "210 KING STREET", "from[address_city]" => "SAN FRANCISCO", "from[address_state]" => "CA", "from[address_zip]" => "94107", "front" => "<html style='padding: 1in; font-size: 50;'>Front HTML for {{name}}</html>", "back" => "<html style='padding: 1in; font-size: 20;'>Back HTML for {{name}}</html>", "merge_variables[name]" => "Harry" )); print_r($postcard); ?> Copy package com.company.app; import com.lob.api.ApiClient; import com.lob.api.ApiException; import com.lob.api.Configuration; import com.lob.api.auth.*; import com.lob.model.*; import com.lob.api.client.PostcardsApi; public class App { public static void main( String[] args ) { ApiClient lobClient = Configuration.getDefaultApiClient(); // Configure HTTP basic authorization: basicAuth HttpBasicAuth basicAuth = (HttpBasicAuth) lobClient.getAuthentication("basicAuth"); basicAuth.setUsername("<YOUR_LOB_API_KEY>"); PostcardsApi apiInstance = new PostcardsApi(lobClient); PostcardEditable postcardEditable = new PostcardEditable(); AddressEditable to = new AddressEditable(); to.setName("MORTICIA ADDAMS"); to.setAddressLine1("1313 CEMETERY LN"); to.setAddressCity("WESTFIELD"); to.setAddressState("NJ"); to.setAddressZip("07091"); AddressEditable to = new AddressEditable(); to.setName("MORTICIA ADDAMS"); to.setAddressLine1("1313 CEMETERY LN"); to.setAddressCity("WESTFIELD"); to.setAddressState("NJ"); to.setAddressZip("07091"); AddressEditable from = new AddressEditable(); from.setName("FESTER"); from.setAddressLine1("001 CEMETERY LN"); from.setAddressLine2("SUITE 666"); from.setAddressCity("WESTFIELD"); from.setAddressState("NJ"); from.setAddressZip("07091"); Gson gson = new Gson(); postcardEditable.setTo(gson.toJson(to)); postcardEditable.setFrom(gson.toJson(from)); postcardEditable.setFront("https://s3-us-west-2.amazonaws.com/public.lob.com/assets/templates/4x6_pc_template.pdf"); postcardEditable.setBack("https://s3-us-west-2.amazonaws.com/public.lob.com/assets/templates/4x6_pc_template.pdf"); try { Postcard result = apiInstance.create(postcardEditable); System.out.println(result); } catch (ApiException e) { System.err.println("Exception when calling PostcardsApi#postcardCreate"); System.err.println("Status code: " + e.getCode()); System.err.println("Reason: " + e.getResponseBody()); System.err.println("Response headers: " + e.getResponseHeaders()); e.printStackTrace(); } } } Copy using System; using System.Collections.Generic; using System.Diagnostics; using lob.dotnet.Api; using lob.dotnet.Client; using lob.dotnet.Model; namespace test_dotnet { class Program { static void Main(string[] args) { Configuration config = new Configuration(); config.BasePath = "https://api.lob.com/v1"; // Configure HTTP basic authorization: basicAuth config.Username = "<YOUR_TEST_KEY>"; Dictionary<string, string> mergeVariables = new Dictionary<string, string>(); mergeVariables.Add("name", "Harry"); PostcardsApi apiInstance = new PostcardsApi(config); AddressEditable to = new AddressEditable( "210 King St", // addressLine1 null, // addressLine2 "San Francisco", // addressCity "CA", // addressState "94107", // addressZip CountryExtended.US, // addressCounty "First Postcard", // description "Harry Zhang" // name ); AddressEditable from = new AddressEditable( "210 King St", // addressLine1 null, // addressLine2 "San Francisco", // addressCity "CA", // addressState "94107", // addressZip CountryExtended.US, // addressCounty null, // description "Leore Avidar" // name ); PostcardEditable postcardEditable = new PostcardEditable( to.ToJson(), // to from.ToJson(), // from default(PostcardSize), // size "First Postcard", // description null, // metadata default(MailType), // mailType mergeVariables, // mergeVariables default(DateTime), // sendDate "<html style='padding: 1in; font-size: 50;'>Front HTML for {{name}}</html>", // front "<html style='padding: 1in; font-size: 20;'>Back HTML for {{name}}</html>" // back ); try { // create Postcard result = apiInstance.create(postcardEditable); Console.WriteLine(result.ToString()); } catch (ApiException e) { Console.WriteLine("Exception when calling PostcardsApi.create: " + e.Message ); Console.WriteLine("Status Code: "+ e.ErrorCode); Console.WriteLine(e.StackTrace); } } } } | 2026-01-13T08:48:37 |
https://aws.amazon.com/cloudwatch/ | Amazon Monitoring and Observability-Amazon CloudWatch - AWS Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Amazon CloudWatch Overview Features Pricing Getting Started FAQs More Products › Management and Governance › Amazon CloudWatch Amazon CloudWatch Observe and optimize your workloads at any scale Get started with CloudWatch Try for free Complete visibility, intelligent insights Monitor and optimize your entire technology stack with CloudWatch, an intelligent observability service that provides actionable insights across applications and infrastructure. Gain complete visibility into performance, availability, and security so you can resolve issues faster and improve system reliability. Troubleshoot issues efficiently using AWS operational expertise and scalability built into CloudWatch. Access fully-managed solutions enhanced with generative AI or integrate through OpenTelemetry with open-source compatibility – using the approach that works best for your environment. Learn more about new features » Play See everything in one place Get a unified view of your generative AI agents, applications, workloads, and the infrastructure that powers them. CloudWatch connects metrics, logs, and traces to help you quickly understand relationships, spot performance bottlenecks, and uncover hidden dependencies—without jumping between tools. Explore Application Performance Monitoring (APM) features Explore Generative AI Observability features Simplify operations Improve operational efficiency with built-in insights for databases, containers, and serverless such as Lambda—no need to build from scratch. CloudWatch also integrates with popular open-source monitoring and observability solutions like Prometheus and Grafana, plus it supports OpenTelemetry standards, giving you the flexibility to use the best approach for your needs. Explore Infrastructure Observability features Let AI help you Find and resolve issues with AI-powered CloudWatch investigations and Anomaly Detection. Ask questions in plain English to quickly search logs and metrics—natural language query transforms your questions into precise queries automatically. Connect your own agents directly to your CloudWatch data through Model Context Protocol (MCP) servers for integration with your existing AI workflows. Start troubleshooting from wherever you work. Explore AIOps features Troubleshoot smarter, not harder Get analytics and insights your way with flexible capabilities that deliver intelligence wherever you need it. Choose out-of-the-box dashboards, build custom queries with plain English or popular languages such as SQL, or access embedded insights that surface automatically within your workflow. Capabilities AIOps GenAI observability Complete visibility Open standards Multicloud Operate intelligently with AIOps Transform how you identify, investigate, and resolve operational issues with AIOps capabilities. Rapidly diagnose complex problems across your AWS environment using AI-powered root cause analysis through CloudWatch investigations, or create tailored workflows through supporting capabilities such as MCP servers and Strands Agent SDK . Navigate interconnected operational data using simple conversational questions. Surface critical patterns, interpret anomalies, and generate actionable summaries in seconds. Whether investigating performance degradation, analyzing trends, or responding to incidents, CloudWatch AIOps features can make it easy. Monitor generative AI workloads Monitor generative AI workloads for complete visibility across components, including models, agents, and tools. Gain built-in insights into latency, token usage, and errors across Amazon Bedrock AgentCore capabilities such as Built-in Tools, Gateways, Memory, and Identity to quickly detect and resolve issues. Accelerate AI innovation and maintain customer trust leveraging the compatibility with open-source agentic frameworks, such as LangChain, and AWS-native features. Explore GenAI Observability features Play See your full stack in one place Monitor your entire environment—from infrastructure and applications to real users and synthetic tests—all in one place. Amazon CloudWatch provides a unified observability solution that simplifies monitoring, consolidates tools, and accelerates troubleshooting across workloads. Discover Application Performance Monitoring (APM) features Instrument once Simplify instrumentation and maintain vendor flexibility with support for OpenTelemetry. Collect, process, and export metrics, logs, and traces from any environment using open standards. Integrate with both open-source and AWS-native observability tools for consistent, end-to-end visibility. Discover OpenTelemetry support Monitor workloads anywhere Monitor your workloads hosted on AWS, on premises, and on other clouds by ingesting telemetry data using the OpenTelemetry-compatible CloudWatch agent . Ingestion charges are the same whether data originates in AWS or elsewhere. Read about the Phillips 66 case study Get started with CloudWatch Workshop Learn with hands-on AWS One Observability Workshop Explore the Workshop Blog See how observability can benefit your operations Read the blog Features Learn how to transform your observability with the latest features Learn more Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://x.com/en/tos/previous/version_9 | Previous Terms of Service X logo icon Twitter Terms of Service These Terms of Service (“ Terms ”) govern your access to and use of our Services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services (the “ Twitter Services ”), and our other covered services that link to these Terms (collectively, the “ Services ”), and any information, text, graphics, photos or other materials uploaded, downloaded or appearing on the Services (collectively referred to as “ Content ”). Your access to and use of the Services are conditioned on your acceptance of and compliance with these Terms. By accessing or using the Services you agree to be bound by these Terms. 1. Basic Terms You are responsible for your use of the Services, for any Content you post to the Services, and for any consequences thereof. Most Content you submit, post, or display through the Twitter Services is public by default and will be able to be viewed by other users and through third party services and websites. Learn more here , and go to the account settings page to control who sees your Content. You should only provide Content that you are comfortable sharing with others under these Terms. Tip : What you say on the Twitter Services may be viewed all around the world instantly. You are what you Tweet! You may use the Services only if you can form a binding contract with Twitter and are not a person barred from receiving services under the laws of the United States or other applicable jurisdiction. If you are accepting these Terms and using the Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so. You may use the Services only in compliance with these Terms and all applicable local, state, national, and international laws, rules and regulations. The Services that Twitter provides are always evolving and the form and nature of the Services that Twitter provides may change from time to time without prior notice to you. In addition, Twitter may stop (permanently or temporarily) providing the Services (or any features within the Services) to you or to users generally and may not be able to provide you with prior notice. We also retain the right to create limits on use and storage at our sole discretion at any time without prior notice to you. The Services may include advertisements, which may be targeted to the Content or information on the Services, queries made through the Services, or any other information. The types and extent of advertising by Twitter on the Services are subject to change. In consideration for Twitter granting you access to and use of the Services, you agree that Twitter and its third party providers and partners may place such advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. 2. Privacy Any information that you or other users provide to Twitter is subject to our Privacy Policy , which governs our collection and use of your information. 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 Twitter. As part of providing you 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, which you may not be able to opt-out from receiving. Tip : You can control most communications from the Twitter Services, including notifications about activity related to you, your Tweets, Retweets, and network, and updates from Twitter. Please see your settings for email and mobile notifications for more. 3. Passwords You are responsible for safeguarding the password that you use to access the Services and for any activities or actions under your password. We encourage you to use “strong” passwords (passwords that use a combination of upper and lower case letters, numbers and symbols) with your account. Twitter cannot and will not be liable for any loss or damage arising from your failure to comply with the above. 4. Content on the Services All Content, whether publicly posted or privately transmitted, is the sole responsibility of the person who originated such Content. We may not monitor or control the Content posted via the Services and, we cannot take responsibility for such Content. 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 via the Services or endorse any 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. Under no circumstances will Twitter be liable in any way for any Content, including, but not limited to, any errors or omissions in any Content, or any loss or damage of any kind incurred as a result of the use of any Content posted, emailed, transmitted or otherwise made available via the Services or broadcast elsewhere. 5. Your Rights You retain your rights to any Content you submit, post or display on or through the Services. By submitting, posting or displaying 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 and distribute such Content in any and all media or distribution methods (now known or later developed). Tip : This license is you authorizing us to make your Tweets on the Twitter Services available to the rest of the world and to let others do the same. You agree that this license includes the right for Twitter to provide, promote, and improve the Services and to make Content submitted to or through the Services available to other companies, organizations or individuals who partner with Twitter for the syndication, broadcast, distribution or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Tip : Twitter has an evolving set of rules for how ecosystem partners can interact with your Content on the Twitter Services. These rules exist to enable an open ecosystem with your rights in mind. But what’s yours is yours – you own your Content (and your photos are part of that Content). Such additional uses by Twitter, or other companies, organizations or individuals who partner with Twitter, may be made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services. We may modify or adapt your Content in order to transmit, display or distribute it over computer networks and in various media and/or make changes to your Content as are necessary to conform and adapt that Content to any requirements or limitations of any networks, devices, services or media. You are responsible for your use of the Services, for any Content you provide, and for any consequences thereof, including the use of your Content by other users and our third party partners. You understand that your Content may be syndicated, broadcast, distributed, or published by our partners and if you do not have the right to submit Content for such use, it may subject you to liability. Twitter will not be responsible or liable for any use of your Content by Twitter in accordance with these Terms. You represent and warrant that you have all the rights, power and authority necessary to grant the rights granted herein to any Content that you submit. 6. Your License To Use the Services Twitter gives you a personal, worldwide, royalty-free, non-assignable and non-exclusive license to use the software that is provided to you by Twitter as part of the Services. This license is for the sole purpose of enabling you to use and enjoy the benefit of the Services as provided by Twitter, in the manner permitted by these Terms. 7. Twitter Rights All right, title, and interest in and to the Services (excluding Content provided by users) are and will remain the exclusive property of Twitter and its licensors. The Services are protected by copyright, trademark, and other laws of both the United States and foreign countries. Nothing in the Terms gives you a right to use the Twitter name or any of the Twitter trademarks, logos, domain names, and other distinctive brand features. Any feedback, comments, or suggestions you may provide regarding Twitter, 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. 8. Restrictions on Content and Use of the Services Please review the Twitter Rules (which are part of these Terms) to better understand what is prohibited on the Twitter Services. We reserve the right at all times (but will not have an obligation) to remove or refuse to distribute any Content on the Services, to suspend or terminate users, and to reclaim usernames without liability to you. 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 Twitter, its users and the public. Tip : Twitter does not disclose personally identifying information to third parties except in accordance with our Privacy Policy . Except as permitted through the Twitter Services, these Terms, or the terms provided on dev.twitter.com , you have to use the Twitter API if you want to reproduce, modify, create derivative works, distribute, sell, transfer, publicly display, publicly perform, transmit, or otherwise use the Twitter Services or Content on the Twitter Services. Tip : We encourage and permit broad re-use of Content on the Twitter Services. The Twitter API exists to enable this. If you use commerce features of the Twitter Services that require credit or debit card information, such as our Buy Now feature, you agree to our Twitter Commerce Terms . 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, Twitter’s computer systems, or the technical delivery systems of Twitter’s 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 Twitter (and only pursuant to the applicable terms and conditions ), unless you have been specifically allowed to do so in a separate agreement with Twitter (NOTE: crawling the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without the prior consent of Twitter is expressly prohibited); (iv) forge any TCP/IP packet header or any part of the header information in any email or posting, or in any way use the Services to send altered, deceptive or false source-identifying information; or (v) 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. 9. Copyright Policy Twitter respects the intellectual property rights of others and expects users of the Services to do the same. We will respond to notices of alleged copyright infringement that comply with applicable law and are properly provided to us. If you believe that your Content has been copied in a way that constitutes copyright infringement, please provide us with the following information: (i) a physical or electronic signature of the copyright owner or a person authorized to act on their behalf; (ii) identification of the copyrighted work claimed to have been infringed; (iii) identification of the material that is claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit us to locate the material; (iv) your contact information, including your address, telephone number, and an email address; (v) a statement by you that you have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law; and (vi) a statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner. We reserve the right to remove Content alleged to be infringing without prior notice, at our sole discretion, and without liability to you. In appropriate circumstances, Twitter will also terminate a user’s account if the user is determined to be a repeat infringer. Under the U.S. Digital Millennium Copyright Act, our designated copyright agent for notice of alleged copyright infringement appearing on the Services is: Twitter, Inc. Attn: Copyright Agent 1355 Market Street, Suite 900 San Francisco, CA 94103 Reports: https://support.twitter.com/forms/dmca Email: copyright@twitter.com 10. Ending These Terms The Terms will continue to apply until terminated by either you or Twitter as follows. You may end your legal agreement with Twitter at any time for any or no reason by deactivating your accounts and discontinuing your use of the Services. You do not need to specifically inform Twitter when you stop using the Services. If you stop using the Services without deactivating your accounts, your accounts may be deactivated due to prolonged inactivity under our Inactive Account Policy . We may suspend or terminate your accounts or cease providing you with all or part of the Services at any time for any or no reason, including, but not limited to, if we reasonably believe: (i) you have violated these Terms or the Twitter Rules , (ii) you create risk or possible legal exposure for us; or (iii) 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. 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: 4, 5, 7, 8, 10, 11, and 12. Nothing in this section shall affect Twitter’s rights to change, limit or stop the provision of the Services without prior notice, as provided above in section 1. 11. Disclaimers and Limitations of Liability Please read this section carefully since it limits the liability of Twitter and its parents, subsidiaries, affiliates, related companies, officers, directors, employees, agents, representatives, partners, and licensors (collectively, the “Twitter Entities”). Each of the subsections below only applies up to the maximum extent permitted under applicable law. Some jurisdictions do not allow the disclaimer of implied warranties or the limitation of liability in contracts, and as a result the contents of this section may not apply to you. Nothing in this section is intended to limit any rights you may have which may not be lawfully limited. A. 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. Without limiting the foregoing, to the maximum extent permitted under applicable law, THE TWITTER ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The Twitter 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 Twitter Entities or through the Services, will create any warranty or representation not expressly made herein. B. Links The Services may contain links to third-party websites or resources. You acknowledge and agree that the Twitter Entities are not responsible or liable for: (i) the availability or accuracy of such websites or resources; or (ii) the content, products, or services on or available from such websites or resources. Links to such websites or resources do not imply any endorsement by the Twitter Entities of such websites or resources or the content, products, or services available from such websites or resources. You acknowledge sole responsibility for and assume all risk arising from your use of any such websites or resources. C. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TWITTER ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOOD-WILL, 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 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 TWITTER ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID TWITTER, 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 TWITTER 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. 12. General Terms A. Waiver and Severability The failure of Twitter to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. 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. B. Controlling Law and Jurisdiction These Terms and any action related thereto will be governed by the laws of the State of California without regard to or application of its conflict of law provisions or your state or country of residence. All claims, legal proceedings or litigation arising in connection with the Services will be brought solely in the federal or state courts located in San Francisco County, California, United States, and you consent to the jurisdiction of and venue in such courts and waive any objection as to inconvenient forum. 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 California (excluding choice of law). C. Entire Agreement These Terms, including the Twitter Rules for the Twitter Services, and our Privacy Policy are the entire and exclusive agreement between Twitter and you regarding the Services (excluding any services for which you have a separate agreement with Twitter that is explicitly in addition or in place of these Terms), and these Terms supersede and replace any prior agreements between Twitter and you regarding the Services. Other than members of the group of companies of which Twitter, Inc. is the parent, no other person or company will be third party beneficiaries to the Terms. We may revise these Terms from time to time, the most current version will always be at twitter.com/tos . If the revision, in our sole discretion, is material we will notify you via an @Twitter update or e-mail 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. If you live in the United States, these Terms are an agreement between you and Twitter, Inc., 1355 Market Street, Suite 900, San Francisco, CA 94103 U.S.A. If you live outside the United States, your agreement is with Twitter International Company, an Irish company with its registered office at The Academy, 42 Pearse Street, Dublin 2, Ireland. If you have any questions about these Terms, please contact us . Effective: May 18, 2015 Archive of Previous Terms 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:48:37 |
https://aws.amazon.com/pt/api-gateway/ | Amazon API Gateway | Gerenciamento de APIs | Amazon Web Services Pular para o conteúdo principal Clique aqui para voltar à página inicial da Amazon Web Services Sobre a AWS Fale conosco Suporte Português Minha conta Fazer login Crie uma conta da AWS Fechar Perfil Seu perfil ajuda a melhorar suas interações com experiências específicas da AWS. Login Fechar Perfil Seu perfil ajuda a melhorar suas interações com experiências específicas da AWS. Exibir perfil Sair Amazon Q Produtos Soluções Definição de preço Documentação Aprenda Rede de parceiros AWS Marketplace Capacitação de clientes Eventos Explore mais Fechar عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) Fechar Meu perfil Sair do AWS Builder ID Console de Gerenciamento da AWS Configurações da conta Gerenciamento de faturamento e custo Credenciais de segurança AWS Personal Health Dashboard Fechar Centro de suporte Ajuda especializada Centro de Conhecimento Visão geral do AWS Support AWS re:Post Clique aqui para voltar à página inicial da Amazon Web Services Comece a usar gratuitamente Fale conosco Produtos Soluções Definição de preço Introdução à AWS Conceitos básicos Documentação Treinamento e certificação Centro do desenvolvedor Histórias de sucesso de clientes Rede de parceiros AWS Marketplace Suporte AWS re:Post Faça login no console Faça download do aplicativo móvel Amazon API Gateway Visão geral Recursos Preço Conceitos básicos Recursos Perguntas frequentes Parceiros Produtos › Redes e entrega de conteúdo › Amazon API Gateway Um milhão de chamadas de API recebidas gratuitamente por mês durante 12 meses com o nível gratuito da AWS Amazon API Gateway Crie, mantenha e proteja APIs em qualquer escala Comece a usar o API Gateway Por que escolher o API Gateway? O Amazon API Gateway é um serviço totalmente gerenciado que permite que desenvolvedores criem, publiquem, mantenham, monitorem e protejam APIs em qualquer escala com facilidade. APIs agem como a “porta de entrada” para aplicativos acessarem dados, lógica de negócios ou funcionalidade de seus serviços de back-end. Usando o API Gateway, você pode criar APIs do RESTful e APIs do WebSocket que habilitam aplicativos de comunicação bidirecionais em tempo real. O API Gateway dá suporte a cargas de trabalho conteinerizadas e sem servidor, além de aplicativos da web. O API Gateway administra todas as tarefas envolvidas no recebimento e processamento de até centenas de milhares de chamadas de API simultâneas, inclusive gerenciamento de tráfego, suporte de CORS, controle de autorização e acesso, com fluxo controlado, monitoramento e gerenciamento de versões de API. O API Gateway não tem taxas mínimas ou custos antecipados. Você paga apenas pelas chamadas de API recebidas e pela quantidade transferida de dados de saída. Além disso, com o modelo de definição de preço em camadas do API Gateway, você pode reduzir os custos à medida que seu uso da API é escalado. APIs RESTful Crie APIs RESTful otimizadas para cargas de trabalho sem servidor e back-end HTTP usando APIs HTTP. As APIs HTTP são a opção mais adequada para o desenvolvimento de APIs que necessitam somente da funcionalidade de proxy de API. Se suas APIs requerem funcionalidade de proxy de API e recursos de gerenciamento de API em uma única solução, o API Gateway também oferece as APIs REST . APIs WEBSOCKET Desenvolva aplicações de comunicação bidirecional em tempo real, como aplicações de chat e painéis de streaming, com as APIs de WebSocket . O API Gateway mantém uma conexão persistente para lidar com a transferência de mensagens entre o serviço de back-end e os clientes. WirelessCar Saiba como o provedor de mobilidade conectada WirelessCar aprimorou a performance de inicialização usando o AWS Lambda SnapStart para Java. Leia o estudo de caso Odyssey Interactive Saiba como o estúdio de jogos Odyssey Interactive lançou seu jogo multijogador de estreia, Omega Strikers, para todo o mundo ao usar a infraestrutura gerenciada na AWS. Leia o estudo de caso Betterfly Saiba como a Betterfly simplifica a proteção e o gerenciamento de benefícios para grupos e incentiva hábitos positivos diários usando uma solução digital desenvolvida na AWS. Leia o estudo de caso TiVo Saiba como a TiVo, no setor de mídia e de entretenimento, conseguiu alcançar escalabilidade expansível e alta disponibilidade nos serviços de streaming ao usar o AWS Lambda e o Amazon API Gateway. Leia o estudo de caso Comece a usar o API Gateway 1 Cadastre-se para obter uma conta da AWS Obtenha acesso instantâneo ao nível gratuito da AWS . 2 Aprenda com os tutoriais passo a passo Explore e aprenda com tutoriais simples . 3 Comece a criar com a AWS Acesse o Console de Gerenciamento da AWS . Próximas etapas Feature Page Saiba mais sobre o Amazon API Gateway Acesse a página de recursos Conceitos básicos Pronto para criar? Comece a usar Contact us Mais dúvidas? Entre em contato conosco Faça login no console Saiba mais sobre a AWS O que é a AWS? O que é a computação em nuvem? Acessibilidade da AWS O que é o DevOps? O que é um contêiner? O que é um data lake? O que é inteligência artificial (IA)? O que é IA generativa? O que é machine learning (ML)? Segurança na Nuvem AWS Novidades Blogs Press Releases Recursos da AWS Conceitos básicos Treinamento e certificação Biblioteca de soluções da AWS Centro de arquitetura Perguntas frequentes sobre produtos e tópicos técnicos Relatórios de analistas Parceiros da AWS Desenvolvedores na AWS Centro do desenvolvedor SDKs e ferramentas .NET na AWS Python na AWS Java na AWS PHP na AWS JavaScript na AWS Ajuda Entre em contato conosco Obtenha ajuda especializada Crie um tíquete de suporte AWS re:Post Centro de Conhecimento Visão geral do AWS Support Legal Carreiras na AWS Crie uma conta da AWS A Amazon é uma empresa empregadora orientada pelos fundamentos de igualdade de oportunidades e ações afirmativas, que não faz distinção entre minorias, mulheres, portadores de deficiência, veteranos, identidade de gênero, orientação sexual nem idade . Idioma عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) Privacidade | Acessibilidade | Termos do site | Preferências de cookies | © 2024, Amazon Web Services, Inc. ou suas afiliadas. Todos os direitos reservados. Você está usando um navegador desatualizado. Atualize para um navegador moderno e aprimore a sua experiência. Encerramento do suporte para o Internet Explorer Entendi O suporte da AWS para o Internet Explorer termina em 07/31/2022. Os navegadores compatíveis são: Chrome, Firefox, Edge e Safari. Saiba mais » Entendi | 2026-01-13T08:48:37 |
https://x.com/en/tos/previous/version_8 | Previous Terms of Service X logo icon Terms of Service These Terms of Service (“ Terms ”) govern your access to and use of the services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, and commerce services (the “ Services ” or “ Twitter ”), and any information, text, graphics, photos or other materials uploaded, downloaded or appearing on the Services (collectively referred to as “ Content ”). Your access to and use of the Services are conditioned on your acceptance of and compliance with these Terms. By accessing or using the Services you agree to be bound by these Terms. 1. Basic Terms You are responsible for your use of the Services, for any Content you post to the Services, and for any consequences thereof. The Content you submit, post, or display will be able to be viewed by other users of the Services and through third party services and websites (go to the account settings ( http://twitter.com/settings/security ) page to control who sees your Content). You should only provide Content that you are comfortable sharing with others under these Terms. Tip What you say on Twitter may be viewed all around the world instantly. You are what you Tweet! You may use the Services only if you can form a binding contract with Twitter and are not a person barred from receiving services under the laws of the United States or other applicable jurisdiction. If you are accepting these Terms and using the Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so. You may use the Services only in compliance with these Terms and all applicable local, state, national, and international laws, rules and regulations. The Services that Twitter provides are always evolving and the form and nature of the Services that Twitter provides may change from time to time without prior notice to you. In addition, Twitter may stop (permanently or temporarily) providing the Services (or any features within the Services) to you or to users generally and may not be able to provide you with prior notice. We also retain the right to create limits on use and storage at our sole discretion at any time without prior notice to you. The Services may include advertisements, which may be targeted to the Content or information on the Services, queries made through the Services, or other information. The types and extent of advertising by Twitter on the Services are subject to change. In consideration for Twitter granting you access to and use of the Services, you agree that Twitter and its third party providers and partners may place such advertising on the Services or in connection with the display of Content or information from the Services whether submitted by you or others. 2. Privacy Any information that you provide to Twitter is subject to our Privacy Policy ( http://twitter.com/privacy ), which governs our collection and use of your information. 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 and/or other countries for storage, processing and use by Twitter. As part of providing you 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 Twitter account, which you may not be able to opt-out from receiving. Tip You can opt-out of most communications from Twitter including our newsletter, new follower emails, etc. Please see the Notifications tab of Settings for more. 3. Passwords You are responsible for safeguarding the password that you use to access the Services and for any activities or actions under your password. We encourage you to use “strong” passwords (passwords that use a combination of upper and lower case letters, numbers and symbols) with your account. Twitter cannot and will not be liable for any loss or damage arising from your failure to comply with the above. 4. Content on the Services All Content, whether publicly posted or privately transmitted, is the sole responsibility of the person who originated such Content. We may not monitor or control the Content posted via the Services and, we cannot take responsibility for such Content. 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 via the Services or endorse any 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. Under no circumstances will Twitter be liable in any way for any Content, including, but not limited to, any errors or omissions in any Content, or any loss or damage of any kind incurred as a result of the use of any Content posted, emailed, transmitted or otherwise made available via the Services or broadcast elsewhere. 5. Your Rights You retain your rights to any Content you submit, post or display on or through the Services. By submitting, posting or displaying 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 and distribute such Content in any and all media or distribution methods (now known or later developed). Tip This license is you authorizing us to make your Tweets available to the rest of the world and to let others do the same. You agree that this license includes the right for Twitter to provide, promote, and improve the Services and to make Content submitted to or through the Services available to other companies, organizations or individuals who partner with Twitter for the syndication, broadcast, distribution or publication of such Content on other media and services, subject to our terms and conditions for such Content use. Tip Twitter has an evolving set of rules ( http://twitter.com/apirules ) for how ecosystem partners can interact with your Content. These rules exist to enable an open ecosystem with your rights in mind. But what’s yours is yours – you own your Content (and your photos are part of that Content). Such additional uses by Twitter, or other companies, organizations or individuals who partner with Twitter, may be made with no compensation paid to you with respect to the Content that you submit, post, transmit or otherwise make available through the Services. We may modify or adapt your Content in order to transmit, display or distribute it over computer networks and in various media and/or make changes to your Content as are necessary to conform and adapt that Content to any requirements or limitations of any networks, devices, services or media. You are responsible for your use of the Services, for any Content you provide, and for any consequences thereof, including the use of your Content by other users and our third party partners. You understand that your Content may be syndicated, broadcast, distributed, or published by our partners and if you do not have the right to submit Content for such use, it may subject you to liability. Twitter will not be responsible or liable for any use of your Content by Twitter in accordance with these Terms. You represent and warrant that you have all the rights, power and authority necessary to grant the rights granted herein to any Content that you submit. 6. Your License To Use the Services Twitter gives you a personal, worldwide, royalty-free, non-assignable and non-exclusive license to use the software that is provided to you by Twitter as part of the Services. This license is for the sole purpose of enabling you to use and enjoy the benefit of the Services as provided by Twitter, in the manner permitted by these Terms. 7. Twitter Rights All right, title, and interest in and to the Services (excluding Content provided by users) are and will remain the exclusive property of Twitter and its licensors. The Services are protected by copyright, trademark, and other laws of both the United States and foreign countries. Nothing in the Terms gives you a right to use the Twitter name or any of the Twitter trademarks, logos, domain names, and other distinctive brand features. Any feedback, comments, or suggestions you may provide regarding Twitter, 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. 8. Restrictions on Content and Use of the Services Please review the Twitter Rules (which are part of these Terms) to better understand what is prohibited on the Service. We reserve the right at all times (but will not have an obligation) to remove or refuse to distribute any Content on the Services, to suspend or terminate users, and to reclaim usernames without liability to you. 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 Twitter, its users and the public. Tip Twitter does not disclose personally identifying information to third parties except in accordance with our Privacy Policy . Except as permitted through the Services, these Terms, or the terms provided on dev.twitter.com , you have to use the Twitter API if you want to reproduce, modify, create derivative works, distribute, sell, transfer, publicly display, publicly perform, transmit, or otherwise use the Content or Services. Tip We encourage and permit broad re-use of Content. The Twitter API exists to enable this. If you use commerce features of the Services that require credit or debit card information, such as our Buy Now feature, you agree to our Twitter Commerce Terms . 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, Twitter’s computer systems, or the technical delivery systems of Twitter’s 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 Twitter (and only pursuant to those terms and conditions), unless you have been specifically allowed to do so in a separate agreement with Twitter (NOTE: crawling the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without the prior consent of Twitter is expressly prohibited); (iv) forge any TCP/IP packet header or any part of the header information in any email or posting, or in any way use the Services to send altered, deceptive or false source-identifying information; or (v) 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. 9. Copyright Policy Twitter respects the intellectual property rights of others and expects users of the Services to do the same. We will respond to notices of alleged copyright infringement that comply with applicable law and are properly provided to us. If you believe that your Content has been copied in a way that constitutes copyright infringement, please provide us with the following information: (i) a physical or electronic signature of the copyright owner or a person authorized to act on their behalf; (ii) identification of the copyrighted work claimed to have been infringed; (iii) identification of the material that is claimed to be infringing or to be the subject of infringing activity and that is to be removed or access to which is to be disabled, and information reasonably sufficient to permit us to locate the material; (iv) your contact information, including your address, telephone number, and an email address; (v) a statement by you that you have a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law; and (vi) a statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the copyright owner. We reserve the right to remove Content alleged to be infringing without prior notice, at our sole discretion, and without liability to you. In appropriate circumstances, Twitter will also terminate a user’s account if the user is determined to be a repeat infringer. Our designated copyright agent for notice of alleged copyright infringement appearing on the Services is: Twitter, Inc. Attn: Copyright Agent 1355 Market Street, Suite 900 San Francisco, CA 94103 Reports: https://support.twitter.com/forms/dmca Email: copyright@twitter.com 10. Ending These Terms The Terms will continue to apply until terminated by either you or Twitter as follows. You may end your legal agreement with Twitter at any time for any reason by deactivating your accounts and discontinuing your use of the Services. You do not need to specifically inform Twitter when you stop using the Services. If you stop using the Services without deactivating your accounts, your accounts may be deactivated due to prolonged inactivity under our Inactive Account Policy . We may suspend or terminate your accounts or cease providing you with all or part of the Services at any time for any reason, including, but not limited to, if we reasonably believe: (i) you have violated these Terms or the Twitter Rules , (ii) you create risk or possible legal exposure for us; or (iii) 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. 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: 4, 5, 7, 8, 10, 11, and 12. Nothing in this section shall affect Twitter’s rights to change, limit or stop the provision of the Services without prior notice, as provided above in section 1. 11.Disclaimers and Limitations of Liability Please read this section carefully since it limits the liability of Twitter and its parents, subsidiaries, affiliates, related companies, officers, directors, employees, agents, representatives, partners, and licensors (collectively, the “Twitter Entities”). Each of the subsections below only applies up to the maximum extent permitted under applicable law. Some jurisdictions do not allow the disclaimer of implied warranties or the limitation of liability in contracts, and as a result the contents of this section may not apply to you. Nothing in this section is intended to limit any rights you may have which may not be lawfully limited. A. 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. Without limiting the foregoing, to the maximum extent permitted under applicable law, THE TWITTER ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The Twitter Entities make no warranty 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 Twitter Entities or through the Services, will create any warranty not expressly made herein. B. Links The Services may contain links to third-party websites or resources. You acknowledge and agree that the Twitter Entities are not responsible or liable for: (i) the availability or accuracy of such websites or resources; or (ii) the content, products, or services on or available from such websites or resources. Links to such websites or resources do not imply any endorsement by the Twitter Entities of such websites or resources or the content, products, or services available from such websites or resources. You acknowledge sole responsibility for and assume all risk arising from your use of any such websites or resources. C. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TWITTER ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOOD-WILL, 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 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 TWITTER ENTITIES EXCEED THE GREATER OF ONE HUNDRED U.S. DOLLARS (U.S. $100.00) OR THE AMOUNT YOU PAID TWITTER, 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 TWITTER 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. 12. General Terms A. Waiver and Severability The failure of Twitter to enforce any right or provision of these Terms will not be deemed a waiver of such right or provision. 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. B. Controlling Law and Jurisdiction These Terms and any action related thereto will be governed by the laws of the State of California without regard to or application of its conflict of law provisions or your state or country of residence. All claims, legal proceedings or litigation arising in connection with the Services will be brought solely in the federal or state courts located in San Francisco County, California, United States, and you consent to the jurisdiction of and venue in such courts and waive any objection as to inconvenient forum. 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 California (excluding choice of law). C. Entire Agreement These Terms, the Twitter Rules and our Privacy Policy are the entire and exclusive agreement between Twitter and you regarding the Services (excluding any services for which you have a separate agreement with Twitter that is explicitly in addition or in place of these Terms), and these Terms supersede and replace any prior agreements between Twitter and you regarding the Services. Other than members of the group of companies of which Twitter, Inc. is the parent, no other person or company will be third party beneficiaries to the Terms. We may revise these Terms from time to time, the most current version will always be at twitter.com/tos . If the revision, in our sole discretion, is material we will notify you via an @Twitter update or e-mail 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. These Services are operated and provided by Twitter Inc., 1355 Market Street, Suite 900, San Francisco, CA 94103. If you have any questions about these Terms, please contact us . Effective: September 8, 2014 Archive of Previous Terms 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:48:37 |
https://docs.suprsend.com/reference/list-events | List Events - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation EVENTS List Events Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog EVENTS List Events OpenAI Open in ChatGPT Retrieve a list of events in a workspace. OpenAI Open in ChatGPT GET / v1 / {workspace} / event Try it List Events cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/event/?limit=10&offset=0" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 401 Copy Ask AI { "meta" : { "count" : 15 , "limit" : 10 , "offset" : 0 }, "results" : [ { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : { "schema" : "user_signup_v1" , "version_no" : 1 }, "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } ] } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace slug (staging, production, etc.) Query Parameters limit integer default: 10 Number of events to return per page (max 100) Required range : 1 <= x <= 100 offset integer default: 0 Number of events to skip for pagination Required range : x >= 0 Response 200 application/json Successfully retrieved list of events meta object Metadata related to pagination information Show child attributes results object[] Array of events Show child attributes Was this page helpful? Yes No Suggest edits Raise issue Previous Get Event Details Fetch event details and its linked schema. Next ⌘ I x github linkedin youtube Powered by List Events cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/event/?limit=10&offset=0" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 401 Copy Ask AI { "meta" : { "count" : 15 , "limit" : 10 , "offset" : 0 }, "results" : [ { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : { "schema" : "user_signup_v1" , "version_no" : 1 }, "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } ] } | 2026-01-13T08:48:37 |
https://www.lob.com/product-tour | Product Tour Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Product Tour How does Lob work? !--> Send lightning-fast campaigns that drive results with Lob Send targeted, lightning-fast campaigns at scale. Take our intuitive platform for a spin. For more information about how this data is handled, please view our Privacy Policy Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:37 |
https://www.mrdbourke.com/theres-always-going-to-be-something/ | There's always going to be something Daniel Bourke Home Now Machine Learning Posts Learn Machine Learning (courses I teach) ML Resources (things I recommend) About Newsletter Contact Book (Charlie Walks) YouTube Sign in Subscribe Life and Living There's always going to be something Daniel Bourke 16 Dec 2025 • 3 min read Butterfly taking a rest. Photo by Georgia Fullerton in Cairns Botanical Gardens, September 2025. You’ve tweaked your back and now you can’t workout. You’ve got two kids under 3 and now every time someone asks you to hang out you can’t because you’re tired. You can’t go to all the events that arise at the end of the year because life happens and for some reason the end of this year has more surprises than last. One of your parents is sick so you can’t move overseas because you want to be close to them. Your car breaks down and you miss that meeting you were banking on. The approval permit for your next project arrives two weeks late and pushes everything back a month. The extra part you ordered arrives broken and doesn’t work so you have to order another one. Cooking a meal of whole foods takes 45 minutes versus eating the pre-packaged stuff takes 10. You forgot to do something someone told you about and it throws their timeline off. There’s always going to be something. But don’t let the somethings creep into your identity. An excuse is not dangerous until it turns absolute. Build up enough somethings and all of a sudden the thing you really wanted fades into the background. There are plenty of times where there’s a hard block on where you’d like to go and what you’d like to do. Though hard blocks tend not to last forever. You can clear them with effort. Or you can clear them with psychology. Got a tweaked back? Good, more time to figure out recovery options and create a training plan to prevent it in the future. Short on time to cook a healthy meal when you’re trying to eat better? Good, an opportunity to skip a meal, tell yourself it’s okay to be hungry for a while and take some time to plan the next few days of meals. The extra part you ordered arrives broken? Good, an opportunity to figure out a workaround or work on something else in the meantime. Once something becomes an always event, it’s no longer an excuse. As in, once you have children, they will always be there, there’s no opposite. So it’s no longer an excuse, they’re very much part of you now. If you’ve forgotten something someone told you and then they ask you about it, you can’t change the forgetfulness. But you can say… That’s my bad, I did forget and I’m sorry, let me fix it. Most things we get caught in knots about aren’t as important or timely as we make them out to be. Sure there are due dates and schedules to adhere to, painful at times but they exist for a reason. You can come at it from two angles. On one hand, there’s always going to be something so dedicate your best efforts as soon and as often as you can. On the other hand, there’s no rush because there’s no time limit. On the third hand, you can combine these two. There’s always going to be something so you persist in your endeavours yet you’re not in a hurry for them to be done. After all, nature does not hurry, yet everything is accomplished. You’re going to make it but it will often not feel that way. That’s the fun part! You pour your heart into the art piece you’re working on but you know there’s know finish line, it’ll be finished when it’s finished. You spend time with and take care of your sick parent but you know no relationship is perfect and there never will be enough time for everything and one day you’ll miss the small inconveniences of today. So you do your best to be present and patient. You call your friend to catch up on life while cleaning up the kitchen after three days of two kids being sick and no chores being done. You forgot to put the thing in your car for the person who asked you to bring it the next day so the next day you personally deliver it to them. Ahhh the red thread reveals itself. Let me explain. Think about the times you’ve been wronged by a company, person or service or gotten the wrong meal at a restaurant. No one’s perfect, sure. But how did the experience feel when the company, person, service or restaurant followed up and graciously corrected their mistake? I’d argue the follow up and correct often gives a better experience than if it had been right the first time. Why? Because human recognises human. And being able to recognize a mistake and self-correct is perhaps the most human trait of all. We’re well aware of our own flaws and how we try to rectify them. So when someone else does it, we feel it. A beautiful push and pull. There’s always going to be something. An error, a mistake, an issue, an excuse, a roadblock, a forgotten promise. And you can let it hold you back or you can accept it let it make you better. Introducing Nutrify 2.0 Multi-Food Mode, 552 New Foods and Food Share 10 Dec 2025 3 min read 32 Today I turn 32 years old. Every year I write an article with stories, ideas, rules of thumb, anecdotes and ponderous items from the last year. This is number 10 of those articles. See: 23, 24, 25, 26, 27, 28, 29, 30, 31. Before I get into it, a few 01 Sep 2025 23 min read A dog called Seven Our crazy neighbours had a dog called Seven. And we had our dog Bella. Bella and Seven would yell at each other and sometimes say something nice like hello how was your day by sniffing each other through the gaps in the fence. One day my younger brothers opened the 13 Jul 2025 12 min read Daniel Bourke © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://youtu.be/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:48:37 |
https://www.jamsadr.com/file-an-eu-us-privacy-shield-or-safe-harbor-claim | Data Privacy Framework Resolution | JAMS Mediation, Arbitration, ADR Services Skip to main content Skip to main content Submit a Case JAMS Access Login JAMS Pathways MENU Neutrals Rules & Clauses Arbitration Rules & Procedures Comprehensive Rules Streamlined Rules Discovery Protocols Appeal Procedures Class Action Procedures Consumer Minimum Standards Mass Arbitration Procedures Artificial Intelligence AI Disputes Clause and Rules AI Disputes Protective Order Smart Contracts Smart Contract Clause & Rules International Rules International Mediation Rules International Arbitration Rules International Arbitration Guidelines Construction Arbitration Construction Arbitration Rules Expedited Construction Arbitration Rules Surety Adjudication Rules Labor and Employment Arbitration Rules Employment Arbitration Rules Labor Arbitration Rules Employment Minimum Standards Download Rules / Forms Download Rules / Forms Rules Archive ADR Sample Clauses Clause Workbook (U.S. Domestic) Clause Workbook (International) Artificial Intelligence Disputes Clause Construction Clauses Employment Clauses Locations ADR Services Alternative Dispute Resolution What do we do? Educational Programs & CLEs In-House Counsel ADR Strategies Forms & Resources FAQs Mediation Mediation Services What is Commercial Mediation? What Happens in Mediation? Mediators Ethics Guidelines Arbitration Arbitration (North America) Arbitration (International) Labor Arbitration Additional Services Appellate Services California Court Reference Services Class Action & Mass Tort Neutral Analysis JAMS Endispute JAMS Pathways JAMS Next Practice Areas & Industries All Practice Areas & Industries Appellate Bankruptcy Class Action & Mass Tort Construction Cybersecurity & Privacy Disaster Relief Employment Energy Engineering & Construction Entertainment & Sports Estate/Probate/Trust Family Law Federal Financial Markets Health Care Higher Education & Title IX Insurance Intellectual Property International & Cross-Border Labor Life Sciences Personal Injury & Tort Real Estate & Real Property Smart Contracts & Blockchain News & Insights Articles & Insights JAMS ADR Insights JAMS International Insights Podcasts News & Press Releases JAMS News & Press Releases Events & Webinars JAMS Events & Webinars About Who we are Our Values Senior Management Impact JAMS Foundation Social Responsibility Life at JAMS Employee Benefits Apply Online JAMS Data Privacy Framework (DPF) Dispute Resolution Print Page Download page as PDF Data Privacy Framework (DPF) Dispute Resolution EU-U.S. DPF • UK Extension to the EU-U.S. DPF • Swiss-U.S. DPF JAMS Data Privacy Framework (DPF) Dispute Resolution The EU-U.S. Data Privacy Framework (EU-U.S. DPF), the UK Extension to the EU-U.S. Data Privacy Framework (UK Extension to the EU-U.S. DPF), and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) were respectively developed in furtherance of transatlantic commerce by the U.S. Department of Commerce and the European Commission, the UK Government, and the Swiss Federal Administration to provide U.S. organizations with reliable mechanisms for personal data transfers to the United States from the European Union / European Economic Area, the United Kingdom (and Gibraltar), and Switzerland while ensuring data protection that is consistent with EU, UK, and Swiss law. The effective date of the EU-U.S. DPF Principles, including the Supplemental Principles and Annex I of the Principles is July 10, 2023, which is the date of entry into force of the European Commission’s adequacy decision for the EU-U.S. DPF. The adequacy decision enables the transfer of EU personal data to participating organizations consistent with EU law. Effective as of July 17, 2023, eligible organizations in the United States that wish to self-certify their compliance pursuant to the UK Extension to the EU-U.S. DPF may do so; however, personal data cannot be received from the United Kingdom and Gibraltar in reliance on the UK Extension to the EU-U.S. DPF before the date that the adequacy regulations implementing the data bridge for the UK Extension to the EU-U.S. DPF enter into force. The data bridge will enable the transfer of UK and Gibraltar personal data to participating organizations consistent with UK law. The effective date of the Swiss-U.S. DPF Principles, including the Supplemental Principles and Annex I of the Principles is July 17, 2023; however, personal data cannot be received from Switzerland in reliance on the Swiss-U.S. DPF until the date of entry into force of Switzerland’s recognition of adequacy for the Swiss-U.S. DPF. The recognition of adequacy will enable the transfer of Swiss personal data to participating organizations consistent with Swiss law. The Data Privacy Framework (DPF) Program, which is administered by the International Trade Administration (ITA) within the U.S. Department of Commerce, enables eligible U.S.-based organizations to self-certify their compliance pursuant to the EU-U.S. DPF and, as applicable, the UK Extension to the EU-U.S. DPF, and/or the Swiss-U.S. DPF. To participate in the DPF Program, a U.S.-based organization is required to self-certify to the ITA via the Department's DPF Program website (www.dataprivacyframework.gov) and publicly commit to comply with the DPF Principles. While the decision by an eligible U.S.-based organization to self-certify its compliance pursuant to and participate in the relevant part(s) of the DPF Program is voluntary, effective compliance upon self-certification is compulsory. Once such an organization self-certifies to the ITA and publicly declares its commitment to adhere to the DPF Principles that commitment is enforceable under U.S. law. All organizations interested in self-certifying their compliance pursuant to the EU-U.S. DPF and, as applicable, the UK Extension to the EU-U.S. DPF, and/or the Swiss-U.S. DPF should review the requirements in their entirety. The Department’s DPF Program website provides useful information regarding the benefits and requirements of participation in the relevant parts of that program. U.S.-based organizations that self-certify their compliance pursuant to the relevant part(s) of the DPF Program must, amongst other things, provide readily available recourse mechanisms available to investigate unresolved complaints, including a system of alternative dispute resolution (ADR) by an independent third party. The independent recourse mechanisms must be in place prior to self-certification, and must be available at no cost to the individual. Although organizations self-certifying their compliance pursuant to the relevant part(s) of the DPF Program may utilize private sector developed dispute resolution programs for most categories of personal data covered under their self-certifications, those organizations covering human resources data (i.e., personal information about employees, past or present, collected in the context of the employment relationship) transferred from the European Union, the United Kingdom, or Switzerland must agree to cooperate and comply with the EU data protection authorities (DPAs), the UK Information Commissioner’s Office (ICO), and the Swiss Federal Data Protection and Information Commissioner (FDPIC) respectively with regard to such data. JAMS is available to serve as your organization’s designated ADR provider and to assist in resolving disputes brought under the DPF Principles, up to the point of any final arbitration invoked in accordance with the procedures and conditions set forth in the EU-U.S. DPF Principles and/or the Swiss-U.S. DPF Principles. With a panel of over 400 neutrals around the world, JAMS specializes in resolving disputes of all sizes and levels of complexity and our neutrals have significant experience resolving issues involving privacy. Mediation Rules Mediations will be conducted pursuant to JAMS International Mediation Rules unless the parties have specified a different set of Rules or Procedures. Download the JAMS International Mediation Rules Fees JAMS DOES NOT charge any fees for an organization to name it as an ADR provider. If an organization names JAMS as its ADR provider under the EU-U.S. DPF and, as applicable, the UK Extension to the EU-U.S. DPF, and/or the Swiss-U.S. DPF, we request that you notify JAMS by registering here . When a consumer initiates a mediation or an arbitration against an organization (whether under JAMS Rules or another set of rules) all fees for the mediation, including the JAMS Case Management Fee, must be borne by the Organization. The fee arrangement is common to all DPF Dispute Resolution cases for the European Union / European Economic Area, the United Kingdom (and Gibralter), and Switzerland. For any other matters, standard JAMS policies apply. Name JAMS as Your Dispute Resolution Provider If you wish to name JAMS as your Dispute Resolution provider under the EU-U.S. DPF and, as applicable, the UK Extension to the EU-U.S. DPF, and/or the Swiss-U.S. DPF, please register using the link below: JAMS Data Privacy Framework (DPF) Dispute Resolution Registration Customer URL If you do name JAMS as your Dispute Resolution provider under the EU-U.S. DPF and, as applicable, the UK Extension to the EU-U.S. DPF, and/or the Swiss-U.S. DPF, the URL that you will need to provide in your customer-facing privacy policy/ies through which your customers could find information on how to open an EU-U.S. DPF and, as applicable, UK Extension to the EU-U.S. DPF, and/or Swiss-U.S. DPF Dispute Resolution case is: https://www.jamsadr.com/DPF-Dispute-Resolution File a DPF Dispute Resolution Claim If you are a consumer and wish to open an EU-U.S. DPF and, as applicable, UK Extension to the EU-U.S. DPF, and/or a Swiss-U.S. DPF Dispute Resolution case, please file a claim using the link below: File a Data Privacy Framework (DPF) Claim Additional Resources Questions/Contact If you have any additional questions you may contact our DPF coordinator via email . Mara Satterthwaite, msatterthwaite@jamsadr.com JAMS DPF Dispute Resolution Fee Schedule PROFESSIONAL FEES There is no fee associated with listing JAMS as the ADR provider in a self-certification submission under the DPF Program. Fees apply only if a DPF matter is brought to JAMS. Hourly and daily rates vary depending on neutral. Neutrals are independent contractors and set their own Professional Fees. In compliance with the EU, UK, and Swiss data protection initiatives, 100% of ADR fees associated with a DPF matter brought by a consumer will be the responsibility of the respondent company; consumers will not be responsible for any portion of these fees. For non-consumer matters, hearing fees are divided equally among all parties. Professional Fees include time spent for hearings, pre- and post-hearing reading and research, and award preparation. MEDIATION FEES Initial non-refundable fee of $300 per party, applies to first 10 hours of professional time Time in excess of initial 10 hours is billed at 13% of Professional Fees The Case Management Fee includes access to an exclusive nationwide panel of judges, attorneys, and other ADR experts, dedicated services including all administration through the duration of the case, document handling, and use of JAMS conference facilities including after hours and on-site business support. Weekends and holidays are subject to additional charges. Click here for a PDF of this fee schedule JAMS agreement to render services is with the attorney, the party, and/or other representatives of the party. www.jamsadr.com • Updated 08/30/2023 Contact Information Mara E. Satterthwaite, Esq. msatterthwaite@jamsadr.com 7160 Rafael Rivera Way Suite #400 Las Vegas, NV 89113 Need more information or assistance? Connect with our team. Contact Us Need to submit a case with JAMS? Submit a Case Looking for a mediator or arbitrator? Search Neutrals Stay updated on the latest in mediation, arbitration and dispute resolution. Neutrals Insights Rules & Clauses Locations Capabilities About Disclaimer Contact Us Consumer Case Information Neutrality Cookie Consent Privacy Center Terms of Service Accessibility and Accommodation Requests Email Disclaimer This website is not a solicitation for business. All content on the JAMS website is intended to provide general information about JAMS and an opportunity for interested persons to contact JAMS. The content of this website is not offered as legal advice or legal opinion and it should not be relied upon for any specific situation. JAMS neutrals are not engaged in the practice of law and no attorney client relationship is intended. This website is for informational purposes only and does not constitute a complete description of JAMS services. While JAMS endeavors to keep the information updated and correct, JAMS makes no representations or warranties of any kind, express or implied, about the completeness, accuracy, or reliability of the information contained in this website. SEE MORE © 2026 JAMS. All rights reserved. Scroll to top | 2026-01-13T08:48:37 |
https://www.mrdbourke.com/32/ | 32 Daniel Bourke Home Now Machine Learning Posts Learn Machine Learning (courses I teach) ML Resources (things I recommend) About Newsletter Contact Book (Charlie Walks) YouTube Sign in Subscribe Birthday 32 Daniel Bourke 01 Sep 2025 • 23 min read Number 27: A closer look. Today I turn 32 years old. Every year I write an article with stories, ideas, rules of thumb, anecdotes and ponderous items from the last year. This is number 10 of those articles. See: 23 , 24 , 25 , 26 , 27 , 28 , 29 , 30 , 31 . Before I get into it, a few updates. I’m getting married at the end of the year to my sensational fiancé Georgia. Planning is going well. It’s fun to throw a big party for all your closet loved ones. We made the hard decision as a family to move our Dad into a nursing home. He has Parkinson’s and Dementia and what my Mum and my brothers could offer in terms of care wasn’t enough. The staff at the nursing home are outstanding but the problem of getting into one is tough. If it ever comes to this for one of your loved ones, I’d recommend finding a good broker. We did and we all agreed we should’ve spoken to one sooner. The hardest part? Not seeing my Dad at home whenever I go over to say hello. Ahhhh life. Finally, my brother and I are having fun working on Nutrify . Stayed tuned for version 2.0 coming soon. For more current updates, see my now page . Overall it’s been an adventurous year. Here’s to 33. 1. Never hurt the helpful animal For every message in a fairytale, there’s an opposite message. Fight evil gets balanced with ignore evil. Slow and steady gets balanced with take the leap. The law of complementary opposites. However, one message dances alone. Never hurt the helpful animal. Because the helpful animal is you. The voice in your head, the feeling in your stomach. The invisible force guiding you to the right path. Hurt the helpful animal and you hurt yourself. 2. There’s always more than two options Dilemmas are fun. They simplify things. One thing or the other. You can do up the pros and cons list of each. Option 1 or option 2. But obviously option 3, 4, 5, 6, 7... 113, 114, 115 exist. Hell, it could even be option 1 and option 2. Let’s try the crazy thing and the thing we know that’s worked in the past. When you’re stuck weighing up two options, it’s helpful to remember the words and and neither exist. 3. Acres of Diamonds Akira the Don is one of my favourite artists. He remixes snippets of thought provoking speeches and stories with custom electronic music and vocals. One came on shuffle the other day called Acres of Diamonds . I enjoyed the remix and looked up the original speech by Earl Nightingale . I haven’t been able to get the saying out of my head since. Acres of diamonds. The speech is a story about a man who wanted to join the diamond rush in Africa. So he sold his farm and moved to Africa to look for diamonds. He didn’t find any and ended up throwing himself in a river. But the person who bought the man’s farm one day found a rough diamond out in the field. It turns out, the man’s farm contained acres of diamonds he was unaware of. The lesson? How many treasures lay dormant under our feet without us noticing? Perhaps you are already standing on acres of diamonds, all you have to do is change your perspective. There are no boring opportunities or businesses or jobs or lifestyles. Only boring perspectives. Change your view and who knows, perhaps you’ll find your acres of diamonds. 4. Benchmarking is for losers Compare yourself or your business to another and you automatically limit yourself. If they are the best in the world, you can aim to reach there but if they’re any good, by the time you get there they’ll be onto the next thing. If you’re happy to be a player on the field, benchmarking is table stakes, the entry point. If you want to stand out, strategy is a more creative play. Strategy is a risk. But there is no outsized reward without risk. Reach the benchmarks and you might get a slice of the pie. Create a winning strategy and you get to make the pie. Hat tip: Benchmarking is for losers by Roger Martin . 5. Marketing does not abide by normal distributions If Elon walks into a football stadium, the average net worth of everyone goes up by millions. If the tallest person in the world walks into a football stadium, the average height hardly changes. The first is an example of a power law. The richest person can have many many many times more wealth than the average. The second scenario, is an example of the bell curve or normal distribution. Even the tallest person in the world is at most twice the height of the average (and even this is a stretch). Marketing is in the world of wealth distribution. A single ad or video can provide 80% (or more) of your engagement returns. The problem is, you won’t know which. The same with any form of creative endeavour. The solution? Create by default - make things, products, advertisements, content, art, firstly for fun and curiosity, secondly for income. 80/20 split - 80% of the things might be known to work, the tried path. 20% of the things might be complete experiments, “this might not work” type of things. The first ensures consistency. The only controllable variable. The second opens you to serendipity, perhaps the most powerful force in the universe. 6. Products can be improved psychologically as much as they can be improved physically Taxis and Uber provide very much the same service. You request a ride and it shows up. Except Uber provided a map to show you where the car was. I remember before Uber my friends and I would call a taxi late at night and they would say 45 minutes and those 45 minutes felt like we were lost in the wilderness. Now the anxiety of knowing if your ride was going to show up or not goes away, you can see the car coming towards you on the map. The product of taxis didn’t change much physically, Uber’s innovations were psychological as much as they were technical. My car stops its engine at traffic lights to save fuel. When I got it, I found this feature quite annoying. I’d been used to my old car running the whole time and the engine being ready to go. Then I noticed when the engine stopped, a small fuel tank appeared on the dash with a counter showing how much fuel had been saved. I watched the counter go up drip by drip. The counter won me over. Without the counter, the same psychical process happens, you stop and the engine goes off to save fuel. With the counter, now I can see the fuel being saved. In my home city of Brisbane, they are building a new rail system at an estimated cost of ~$6 billion AUD (though this will likely go up). The new rail system is expected to save commuters 10-20 minutes in travel time. Building a new rail system is a big physical undertaking. But I can’t help but wonder how it would be if they spent 10% of the funds making the trip more enjoyable. Making the trip more enjoyable is a psychological point of view. Perhaps people wouldn’t mind travelling a little longer if the trains were nicer? Hat tip: Much of this perspective has evolved from listening to talks by Rory Sutherland . 7. The win bet takes the edge off Zero or one. It’s simple. In any endeavour, the win bet is the simplest. But the trick is you can define winning. Want to write an article but don’t know where it’s supposed to go? Sit down and write for 25 minutes. See what happens. That’s what I’m doing right now. Ha! A single task. As best I can. That’s the win bet. Win at the thing you’re doing right now. The simplest choice you can make in any given moment. Is to focus on one thing at a time. One single thing. One simple thing. As best you can. Note: Yes I know this contradicts with point 2 (there’s always more than two points) but part of the fun of life is bouncing between different points of view. 8. The risk of failure is purely psychological Is the downside really that bad? You tried a new business and it didn’t work. You made some songs and they didn’t turn you into a pop star. You wanted to lose 5kg in 3 months and lost 3kg instead. Who cares? You gave it a shot. What’s the name of your great great grandfather? Or great great grandmother? Kudos if you know. I don’t know mine. It goes to show, in a 100 years or so, hardly anyone will know your name. Daunting? Nah... Exciting. It means you can dance in the circle. Whatever circle you want. You can hold hands with the girl you fancy. She might hold yours back. She might not. You can call that person you’ve been thinking about. The downsides are fabrications of the mind. Besides absolute ruin, all failure is psychological. And you’re smart enough tough enough bold enough not to give into that crap. Give it a crack my son. The spirits of the universe are behind you. Your great great grandparents would be proud you’re giving it a shot. Do it for the dead. One day you’ll be there too. Cheering on the next and the next and next. 9. The need for the new will fade with the ability to absorb the now I’m guilty. Refreshing YouTube, refreshing podcasts... Hell, who am I kidding. Mostly refreshing YouTube. YouTube is where I get podcasts now. Anyway... I’m guilty of craving the new. That sweet thumb down on the YouTube app and I get a world of new. It got me. I got addicted to the sweet sweet nectar of the new. I knew it though... Step one is always know your addictions. My addiction is to always have some kind of YouTube in my ears. I’m working on it... Cooking? YouTube in my ears. Eating? YouTube in my ears. Going for a walk? YouTube in my ears. A five minute drive? YouTube in my ears. Christ! Even writing this down, I see my faults. My poor poor ears... they need a break. My brain needs a break. This last week, I gave them a break. Less YouTube in my ears. But what if there’s a video I miss? C’mon Daniel... what good is an extra video at the expense of the present? Ho ho! You’ve caught me... I know I know. This week, a little less. Cooking last night went well, no YouTube in my ears. Just the food and the utensils and my calm mind. Incredible how it works. Make the win bet. One thing at a time. One thing as best as you can. I understand. I’m practicing. I’m going to be the best in the world at doing one thing. At absorbing the now. Yes yes yes, I’ve got this. 10. The interface is the product I heard a tech talk or a podcast where someone said the interface is the product. As in, for a computer, most customers will buy what it looks and feels like rather than all of the zeros and ones going on behind the scenes. Even for me, someone who likes to program, I buy computers because of the looks and feel. Of course, performance comes into play but only if the performance looks good. How many times have you heard someone buy something because it looks cute? Despite offering no other practical benefit. Cute is a sales angle as much as performance. I like writing words as much as I like how they look on a page. How do the sentences link together? What does the text look like? Yes, utility is important. But the eyes are faster than the mind. What you see either sparks interest to investigate further or not. I like Macs because of the interface. My PC is half Windows half Linux (Ubuntu). I avoid the Windows setup at all costs. A personal preference yes, but also, once you’ve used a Mac or Linux, Windows feels clunky. When you go to a blog and the text is cluttered with ads, how enticing is it to read? The quality of your product depends on how beautifully you can package utility into an interface. ...or make it cute. 11. Do so much volume it would be unreasonable for you to be unsuccessful A simple recipe for success: sets and reps. Like going to the gym. Easy to overcomplicate with the latest trends and workout flavours of the month. But any long-term gym goer will tell you the only real differential is consistency over time. This process relates to almost anything. Choose something. Ignore the BS and opinions of others. Do so many sets and reps of it, a gambler would take the bet on you. Yes yes yes I know... There are no guarantees my friend. But you can stack the deck in your favour. Tell me you’re going to get good at something for the next three years. Then do it. Practicing every day. Day by day. Set by set. Rep by rep. I’d back you. 12. Academic results do not equal leadership skills Three guys I went to school with. Two guys got poor academic results. Not fit for the system. One built skills in welding and bus building. The other built skills in sales. The first runs a team of 60 building buses for public transport. Last year they built 300 buses at $1 million per bus. The second got into real estate, worked his way up, now runs his own team of agents. His team got the second highest sales in the state in their first year in business. The third guy I went to school with was the smartest by far. Smarter than me. Top 5 in the whole school for any subject. His assignments were the envy of the class. He graduated with top grades. Then spent the next 10 years in and out of university. Completed multiple degrees while bouncing between unrelated jobs. I saw him the other day and his energy seemed as though he hadn’t yet stumbled upon the break he’s looking for. And so the two with poor academic results are now running successful teams in their industry. While the one with excellent grades is still getting excellent grades but having trouble transferring those skills to the real world. All are valid paths. And I’m sure the academic will find his break eventually. But it’s a pattern I’ve noticed. You don’t need good grades to be a leader. You need balls. You need to be able to make a decision without a set of criteria to follow. School has a criteria sheet for getting good grades. Real life has no such criteria. Most people hate uncertainty. Fair. So they look up to people who can make decisions in spite of uncertainty. Academic skills don’t guarantee this ability. Of course, nor does lack of academic skills. But don’t assume that because someone can ace a test, that they can lead you into the unknown. 13. To learn something set a goal and move towards it The question “what do I need to learn to do X?” can have an infinite number of answers. And too many options paralyses. This is what happens to first year university students when the options are to study anything and everything. A much more efficient method is to choose something specific you want to do. And learn whatever is needed to move closer to it. Things you need to learn will reveal themselves naturally. I watched a documentary the other day about a team of archeologists who learned to scuba dive because the tomb they wanted to explore was under water. How many beginner archeologists courses teach scuba diving as one of the fundamentals? Instead, they set the goal of exploring the tomb and later discovered it required going underwater. So they learned whatever was necessary to do so. You can do the same with whatever project you choose. Write it down. My project is X and I’m going to learn whatever is required to complete it. 14. Believing you’re lucky is helpful Something that has helped me immensely is believing I’m lucky. Even if it’s not true. Even if there’s no way I can prove it. I just believe it. I believe when I go on walks I’m going to run into the people I need to. I believe when I create something it’s going to reach the people it needs to. I believe if I set my mind to something, I’ll be able to do it. I believe if I’m in alignment with the helpful animal inside me, the whole universe will get behind me. Can I prove it? Nope. Does it help? It feels like it does. 15. Every story in 5 parts If trying to tell a story. Write these headlines down. And fill in the space between. Situation - What’s the starting point? Desire - What does the character want? Conflict - What gets in the way? Change - What happens that shifts something? Result - How does it end? Hat tip: The only 5 lines you need to tell any story by Tim Runia . 16. The garden at the hospital My Dad was in hospital for three months at the start of the year. The nurses were fantastic. But hospitals are grim. Fluorescent lights, sterile surfaces. All setup for optimized care. I couldn’t help but wonder whether the patients might react differently if there was more natural light or spaces to walk. Visiting every two or three days I’d notice the same patients there. Most of them didn’t move for their entire stay except to and from the bathroom. And you know what happens to a puddle of water when it doesn’t move. I’d take my Dad for walks around the hallways. Five laps up and back. And when it wasn’t too hot we’d go for walks outside. Slow walks. But we’d always stop by the flower patches near the entrance. They weren’t very big but my Dad liked to look at them. A touch of colour, a sign of life, a little bit of beauty. Aside from one of the family visiting, I think looking at the garden was one of his favourite things during that time. After a few minutes we’d walk back to the room back to the grey walls with the overhead lights. We’ll go for another walk when I’m back next, I’d say. I’d like that, he said. Then I’d leave and glance at the garden on my way back to the car. It was one of my favourite things too. 17. There’s always something in the box One of the best combos you can have is a talking skill with a hard skill. The engineer who can communicate their ideas. The doctor who breaks down medical terms in ways her patients can understand. I’ve built much of my business on communicating technical ideas in a simple way. Of course, this takes many hours of practice. And I could always do better. But if I get stuck, I steal an idea from a book called Improv Wisdom . Improv is short for improvisation. By the name of it, you’d think it’s something you couldn’t practice. But it is. Almost everything is something you can practice. Improv helps you think on your feet. A skill required by all communicators. Even in writing. Yes, you can edit. But you still need ideas for the first draft. The trick? There’s always something in the box. What box? The box. Imagine there’s a box. A box in front of you. Your idea box. And whenever you open it, there’s always something in it. Something? Yes. Something. Anything. My box? This morning, fireworks, a tattoo gun, a scented candle and a container of vanilla syrup. Magic ingredients for the next adventure. What’s next? Who knows. That’s the fun part. Open the box again and find out. 18. Points or progress? I like feeling smart. When I argue with people, I always want to be right. I often walk away and think of something important and cringe and think dammit I wish I thought of that in the moment. Does it help? Sure. It helps my ego. Sometimes it’s useful. It helps me realise where I stand on topics. But winning an argument, scoring points against someone else doesn’t always lead to progress. And so the question I use to restrain my default argumentative self is: Points or progress? Am I in this argument to score points? Or am I in this argument to make progress with the person I’m talking to? Often the two don’t line up. Progress doesn’t require me to score argumentative points. The best outcome of an argument is to improve all parties positions. Rather than improve one at the expense of another. 19. Have fun with it Fun is the win bet. The universe is far more playful than it is purposeful. Why do you hang out with anyone? Because it’s fun. Fun is my highest priority. Even above love. It’s far easier to love something (or someone) that’s fun. 20. The leverage of compliments A compliment often delivers far more value to the recipient than it takes the giver. I like your outfit, you’ve got great style. Those seven words and a letter might ring in someone’s ears for the rest of the day. Even the next time they look through their closet, those words might perk them up. Hell, I’ve lived whole months on the tailwinds of a good compliment. And so if you like getting compliments, chances are someone else will too. Some will snark at the idea of shallow compliments. Screw them. Who are they to decide what someone will find shallow or not? A compliment is a compliment. Be sincere in the delivery. Delivery often matters far more than actual words. Give away one compliment a day. With the best energy you can. Watch your world change. 21. Audentes fortuna iuvat Fortune favours the bold. But fortune also favours the prepared. Fortuna paratos favet. And to be prepared is to be bold. 22. Practice until it becomes impossible for you to do it wrong Efforts that appear as magic are often many many hours of practice in disguise. I had to present at a pitch night a couple of months ago. The time slot was three minutes. A few weeks prior to the pitch night, the presenter asked if anyone wanted to practice presenting their materials. I put my hand up to go first. I hadn’t look at my notes in weeks. But I trusted myself to be able to make something of it. And from my own perspective, I respect anyone who has the courage to go first. So I assume other people are the same. And even if they aren’t? Haha! No matter, the show must go on. The first round was okay. Perhaps a 4/10. Not a complete train wreck. But not quite par either. No matter. The feedback and suggestions rolled in. What beautiful gifts! Over the next four weeks, I sharpened my notes, fixed the slides, made them fun (most important), added a story. For a live talk, my minimum practice is an hour for every minute. In reality, I would’ve doubled it maybe tripled it. Sets and reps. I’d put the camera on and practice the whole thing, end to end. Only three minutes. But sometimes it’s easier to talk longer than it is shorter. The first 10 rounds sucked. I made mistakes and spoke too long on certain parts and missed different sections. By the twentieth round, I knew it off by heart. On the pitch night, I was the only one to talk without notes. We didn’t win, other teams’ ideas were more appealing than ours. But many people came up to me after and said your presentation was the best. The compliments were nice. Not as good as the deep satisfaction of knowing you gave your all. On the night, that was the one variable I could’ve controlled. Did I practice the talk enough so much so I couldn’t get it wrong? Of course, there’s always the chance I’d screw up the talk. Hell, I fumbled answering one of the judges questions. My answer was probably 3/10. No matter. Now I know what to practice more for next time. Perfection? Unnecessary. Maximum effort where you can? Necessary. 23. Use agents, don’t lose your agency Over the past couple of years, there has been a rise in computer programs known as AI (Artificial Intelligence) agents. These AI agents, commonly known as ChatGPT, Claude, Gemini and DeepSeek (there are many more but I’m leaving them out for brevity) can write entire essays for you in under 10 seconds. They can write 100s of lines of code with a single line of instruction. Some of them can make short movies. And images that look so real you can’t distinguish them from actual images. But the best writers know more words isn’t the point. And the best software engineers know lines of code isn’t the bottleneck . Video makers and painters don’t need endless streams of film and images. All artists know output isn’t the bottleneck. The right output is. As strange as it sounds, the point of writing an essay is as much the chance to think through a problem as it is to end with several pages of text others can pursue. Writing is thinking. Programming is thinking. Creating art is connecting the spiritual to the physical. Building a bridge between heaven and Earth. The engineers of the Bugatti Veyron didn’t need vibe coding. Nor did Picasso have an endless image generator. They set a goal and moved towards it. Yes, AI agents can do incredible things in breakneck speed. However, they all lack the unique human trait of agency. They lack a problem unless given one. Will this change in the future? Perhaps. But not anytime soon. So yes, use AI agents to perform tasks they are helpful for. Though don’t let your agency wane, your ability to think and act through problems on your own accord. Like a muscle, agency is something that needs to be exercised. 24. Most critics have never actually shipped or built anything themselves I am guilty of this. Someone or a company makes something. And my brain floods with ideas of what’s wrong with it or how I would’ve done it better. What a sucker. Zero skin in the game. Once you start to make things, anything. You realise how hard it can be to make something really good. Yes, critiques can be valuable if they lead to potential improvement of the overall system. But if you’re worried about what someone will say of your efforts... Take quick note as to whether they’ve done the actual thing you’re trying to do. If not... Ignore. Take note of how fighters treat each other after fights. Despite being covered in blood and wanting to kill each other seconds earlier, the best ones shake hands and embrace each other. Fighter recognizes fighter. While the crowd scream and shout how one should’ve kicked the other more or gotten up faster from the ground. Yet notice where these cries come from. From a safe distance outside the arena. 25. Action kills anxiety A walk outside, writing down your thoughts and ideas, researching the next steps, an hour on your most important project, 20 pushups, sprinting through a field. If the anxiety creatures are crawling in, know they are allergic to action. Movement is the cure. If the next steps are unclear, let action reveal them. 26. Boredom is your friend In the connected modern world, being able to be bored is a skill. If you want to, you never have to be bored again. But being able to be bored is giving yourself a chance to listen. To listen to your clearest and truest thoughts and ideas. What comes up when there’s no input? Perhaps a solution to a problem. Perhaps a new way of looking at something. Perhaps a totally different life path. Perhaps nothing but a bit of peace and quiet. Boredom, like hunger, tunes the senses to the primal. If you can handle boredom or be okay with being hungry for a while. Hoho my son! That is one powerful combo. 27. A closer look I wake up and walk onto the balcony. We’re staying in a cabin on a hill. I look around. Two birds on the edge of a tree wrestling and singing, a lizard crawling over the rocks its tail shadow etched by the morning sun, spiders weaving webs between the grass, hundreds of them, ants crawling along the fence line carrying whatever it is they’re carrying, hundreds of them, a third bird jumping between red bottlebrushes figuring out which is best, flowers stretching their petals after a night of rest, hundreds of them, a leaf sails down from a tree tracing the final arc of its circle of life, butterflies flap their wings at a terrific clip as if it were their only day on Earth, with each closer look I discover more magnificent goings on than I count, hundreds of them. I wonder if they think the same as me. A man walks outside sits down inhales the morning fog and starts watching the symphony of the day unfold. How lucky am I to be part of the show? I hope to get many more days like this. Hundreds of them. I read this story to my fiancé. And she gets goosebumps. Hundreds of them. 28. Assume you have it The law of reverse effort states the more you try the less you get. Think about trying to get a coin at the back of the couch. The more you try the further the coin falls. Or when trying to fall asleep at night. Try to fall asleep and you can’t. Let yourself fall asleep and you do. When someone asks you to pass the salt at dinner, what do you do? You pick up the salt and pass it to them. You don’t step through the motions. Of hearing the sound waves coming out of the person’s mouth. Converting the sound to language. Identifying the instructions. Translating the instructions to mechanical movements of your arm. Of course, all of these happen. But they happen automatically. You can use this same approach for anything. Any goal. Any desire. Assume you already have it. Go to sleep feeling you already have it. Not pretending it’s there. Feeling it’s there. Let the required actions emerge from your subconscious. Your goal becomes the same voice as someone asking you to pass the salt. Actions toward it become effortless. The entire universe gets behind you. No rush. The subconscious never rushes. How beautiful! The most fun you can ever have. To be both an observer and a dancer in the grand show. You can start today. Substitute your list of goals for a list of assumptions. Now every time you read them, read them aloud, asking yourself to pass the salt. 29. It can be done On a recent trip I heard a streak of inspiring stories. A team of 1500 men digging through a mountain with picks and shovels to build a train line, some of the tunnels over a hundred metres long, some of the cuttings with a sheer 200m high drop. A lady making dresses out of banana peel and pineapple fibres because she didn’t want to use plastic. An Irishman moving across the world then across the country, changing jobs, starting businesses, raising a family, coaching kids football teams. A wife taking care of a terminally ill husband. Nothing gets closer to bringing me to tears. Than seeing someone (or a group of people) doing their best. Inspiration is contagious. Whatever it is. You never know who’ll catch on. 30. It’s not about the money it’s about the energy At dinner I noticed the restaurant host offer a series of alternative restaurants close by to a group of six people who’d just sat down. They’d expressed their distaste of the current options on the menu and expressed their desire to make significant changes. One of the ladies was the thick glasses type. The kind of person who would walk into almost any establishment and look for a problem to point out. And look, their desires are fine. And the host respected them. But offered two nearby restaurants as alternatives. The guests said thank you and got up to leave. The host came over to my fiancé and I and I said, no luck? He said yes, we could figure it out but some people aren’t worth the effort. She did look hard to please, I said. Yeah, and a full table is always good. But it’s not about the money, it’s about the energy. He said. It doesn’t happen often but hey, there’s plenty of other places around. Sure some places might offer anyone and everyone something to eat no matter their request. But you’ve got to draw the line somewhere. Without it, your experience blends into everywhere else. The best hosts not only serve those who say yes, they choose who to say no to. It’s brave to offer a product. It’s even braver to say, sorry it’s not for you. 31. Leaving reviews If word of mouth is the best form of marketing, in the modern world, leaving a review is one of the best ways to help an establishment. A review pops up in a search field. Even if a digital review is worth 10% of a real life review, if the digital review gets viewed 1000 times, that’s like telling 10 people. Not all reviews need to be positive either. Perhaps a nice trick might be to praise specifically and publicly but criticise behind the scenes. The first time, send an email, write it down or talk to a manager instead of a public review, the second time, go somewhere else. Those good reviews you read were written by someone having an experience like you. Leaving your own is a form of paying it forward. 32. The forgotten magic Of all the talk of business and money and financials and policy and law and careers and shareholders and markets and returns and gains and losses. It helps to remember the most magic of it all. The ability to create life. How we all got here. Of all the things I’ve done and will ever do, the one I’m most excited about is becoming a father. 33. Create outside, edit inside Never underestimate ceiling height. For your most creative ideas, you need to have a clear shot to the heavens, a line of sight to connect yourself to the cosmos. Once you’ve received the message and written it down, head into the cave or the lab and close the door to edit it down and refine it. Christ returned to the divine outside on the cross. Then went into the cave to reinvent himself. 34. Love yourself Because life’s better when you do. Say it three times. C’mon. I’ll do it too. I love you. I love you. I love you. 35. One thing I failed at I applied to be part of the Don’t Die Certified team with Brian Johnson. I wrote a short application and a longer planning document of what I’d implement as part of the team. But I didn’t get a reply. Perhaps I should’ve followed up. I still agree with most of the points in the document. Maybe writing the document was the purpose of the application. Just like writing the essay itself is often the reward rather than the finished piece. Hat tips A few people whose works I’ve enjoyed and admired this year. In no specific order. Sean McClure - Excellent writings on complexity, decision making, nature, life in general. Vicky Boykis - Sensational writings on tech, data science and how they intersect with real-world problems. Akira the Don - Countless songs and soundtracks remixing speakers from all over, many of which inspired points in this article. Rory Sutherland - A joy to listen to on everything from marketing and advertising to public transport systems. Search his name on YouTube and go down the rabbit hole. LindyMan (Paul Skallas) - Newsletters I look forward to reading with points from history clashing with modern day ideas and themes. Becca Farsace - Tech reviews I look forward to watching. Samuel Nam - A fellow Aussie who’s tech reviews always make laugh. Joan Westenberg - Essays, video and text, about topics I find hard to describe in a handful of words, which to me my default means they’re good. There's always going to be something You’ve tweaked your back and now you can’t workout. You’ve got two kids under 3 and now every time someone asks you to hang out you can’t because you’re tired. You can’t go to all the events that arise at the end of the 16 Dec 2025 3 min read Introducing Nutrify 2.0 Multi-Food Mode, 552 New Foods and Food Share 10 Dec 2025 3 min read A dog called Seven Our crazy neighbours had a dog called Seven. And we had our dog Bella. Bella and Seven would yell at each other and sometimes say something nice like hello how was your day by sniffing each other through the gaps in the fence. One day my younger brothers opened the 13 Jul 2025 12 min read Daniel Bourke © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://www.lob.com/product/production-tracking | Production + Tracking: Nationwide Print Delivery Network | Lob Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Production + Tracking Deliver mail up to speed – and up to your standards Lob is changing how direct mail is done with a nationwide Print Delivery Network that produces high-quality mail fast, plus full visibility into every send. Book a demo Get started for free Ready to cut direct mail lead time? Move fast without sacrificing quality. Here’s how we help you do it. Discover Postal IQ Send fast + at scale With printers across the U.S., your mail moves quickly – even at high volumes or when plans change. Leave quality to us From color consistency to sharp finishes, our quality checks hold printers to the toughest standards in the industry, so each piece is perfect. Keep costs efficient By using Postal IQ to route to printers near your final destination, we keep costs stable and transit time down, no matter how much mail you send. Stay in the know Get full visibility down to the mailpiece by tracking every step in the production process from pre-sort to transit to delivery. From start to finish: How we deliver quality Top-tier print standards Lob’s printers follow strict guidelines so that every mailpiece is spot on. Color accuracy: We use Chromachecker standards and GRACoL 2013, so your colors stay vibrant and consistent across our network. Finishing touches: From precise 1/8” trimming to secure glue and UV coating, we ensure your mail is protected during transit and polished when it arrives. Tracking and visibility Slice and dice your data by key filters or get a full deliverability report, all directly from your Dashboard. Tracking transparency: Follow each mailpiece or campaign with 8 essential tracking events. Mail speed checks: Monitor how quickly your mail moves from being sent to marked as processed for delivery, pinpointing efficiency and flagging any delays. Built-in accountability We’re rigorous about keeping our network – and your mail – on point. SLA adherence: Automated event mail tracking system keeps partners accountable. Preventative maintenance: We oversee regular on-site quality audits. Monthly quality reviews: We sit down with our printers to review performance metrics and adherence to industry standards. USPS expertise Our Print Delivery Network team has deep ties to the USPS. That close relationship gives us early insight into service standards changes, delivery updates, and other operational shifts – so your mail keeps moving, no surprises. We put customer data security first When mail moves, so does PII. Here’s how we keep it safe. Encryption everywhere Lob protects your data using industry-leading encryption standards for all data in transit. SOC 2 type 2 audits Our security controls are assessed annually through independent reviews. HIPAA/HITECH compliance We support healthcare customers by undergoing annual HIPAA/HITECH privacy audits. Print partner security Our print and logistics partners are regularly audited to verify compliance with strict standards. Print Delivery Network FAQs What is a print network? A print network is a connected system of print vendors that work together to produce and deliver print collateral like brochures and postcards. What is direct mail printing? Direct mail printing is the process of producing physical mail – like postcards, letters, and self-mailers – delivery to targeted recipients through services like USPS. What is Lob's Print Delivery Network (PDN)? Lob's Print Delivery Network (PDN) is the backbone of our Print & Mail offering. By building an integrated, distributed network of professional printers, we simplify client print operations and vendor management on behalf of our customers. Qualified commercial printers are thoroughly vetted by our print experts and integrated into our PDN ecosystem, enabling our customers to easily access different mail delivery strategies without the hassle of management. The strength of our PDN is predicated on automated production, dynamically-adjusted throughput, and consistency of quality that's on-demand and at scale. How does the Print Delivery Network work? Any mail that is sent through Lob is dynamically distributed to the prints within our PDN, based on a number of factors, including: Mail form factor and permutation availability Mail volume capacity Paper stock and ink availability Distance from end-recipient of mail Other manufacturing and logistical capacity needs Regulatory requirements (e.g. HIPAA) I’m a printer interested in partnering with Lob. How do I get involved? If you're a printer that's interested in exploring a partnership opportunity with us, let's talk ! Experience industry-leading print and delivery infrastructure For more information about how this data is handled, please view our Privacy Policy Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:37 |
https://bsky.app/ | Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . This is the home page. | 2026-01-13T08:48:37 |
https://bsky.app/profile/bsky.app | @bsky.app on Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . Profile Bluesky bsky.app did:plc:z72i7hdynmk6r22z27h6tvur official Bluesky account (check username👆) Bugs, feature requests, feedback: support@bsky.app | 2026-01-13T08:48:37 |
https://www.stackaid.us/github/kentcdodds/cross-env | kentcdodds/cross-env - StackAid / kentcdodds / cross-env 🔀 Cross platform setting of environment scripts . Read more Own this project? It earned $9,351 /yr in our simulation . Get funding from your supporters, claim your project . Total received $61 Supporters ( 5 ) $32 Sentry $18 Sourcegraph $10 Pelle Wessman $3 Nicolas Hoizey < $1 Julian Gruber < $1 Funded by ( 58 ) $30 puppeteer/puppeteer $3 eemeli/yaml $1 twbs/bootstrap $1 moment/moment $1 testing-library/react-hooks-testing-library $1 webpack-contrib/style-loader $1 bitinn/node-fetch $1 universse/gatsby-plugin-zeit-now $1 webpack-contrib/css-loader < $1 webpack-contrib/mini-css-extract-plugin < $1 Show all Shared with ( 2 ) $3 moxystudio/node-cross-spawn $2 kentcdodds/kcd-scripts $2 Projects Supporters About Blog Mastodon Contact Help Privacy Terms | 2026-01-13T08:48:37 |
https://aws.amazon.com/api-gateway/#benefits--11s368y | Amazon API Gateway | API Management | Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Amazon API Gateway Overview Features Pricing Getting Started Resources More Products › Networking and Content Delivery › Amazon API Gateway Get started with Amazon API Gateway with AWS Free Tier Amazon API Gateway Create, maintain, and secure APIs at any scale Get started with API Gateway Why API Gateway? Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services. Using API Gateway, you can create RESTful APIs and WebSocket APIs that enable real-time two-way communication applications. API Gateway supports containerized and serverless workloads, as well as web applications. API Gateway offers Portals that enables you to create fully managed, AWS-native developer portals for your APIs. With API Gateway Portals, you can centrally discover, document, and govern your REST APIs across your AWS infrastructure. API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, CORS support, authorization and access control, throttling, monitoring, and API version management. API Gateway has no minimum fees or startup costs. You pay for the API calls you receive and the amount of data transferred out and, with the API Gateway tiered pricing model, you can reduce your cost as your API usage scales. RESTful APIs Build RESTful APIs optimized for serverless workloads and HTTP backends using HTTP APIs. HTTP APIs are the best choice for building APIs that only require API proxy functionality. If your APIs require API proxy functionality and API management features in a single solution, API Gateway also offers REST APIs . WEBSOCKET APIs Build real-time two-way communication applications, such as chat apps and streaming dashboards, with WebSocket APIs . API Gateway maintains a persistent connection to handle message transfer between your backend service and your clients. Page topics Benefits 6 Benefits Open all Efficient API development Run multiple versions of the same API simultaneously with API Gateway, allowing you to quickly iterate, test, and release new versions. You pay for calls made to your APIs and data transfer out, and there are no minimum fees or upfront commitments. Performance at any scale Provide end users with the lowest possible latency for API requests and responses by taking advantage of our global network of edge locations using Amazon CloudFront. Throttle traffic and authorize API calls to ensure that backend operations withstand traffic spikes and backend systems are not unnecessarily called. Cost savings at scale API Gateway provides a tiered pricing model for API requests. With an API Requests price as low as $0.90 per million requests at the highest tier, you can decrease your costs as your API usage increases per region across your AWS accounts. Easy monitoring Monitor performance metrics and information on API calls, data latency, and error rates from the API Gateway dashboard, which allows you to visually monitor calls to your services using Amazon CloudWatch . Flexible security controls Authorize access to your APIs with AWS Identity and Access Management (IAM) and Amazon Cognito. If you use OAuth tokens, API Gateway offers native OIDC and OAuth2 support. To support custom authorization requirements, you can execute a Lambda authorizer from AWS Lambda . RESTful API options Create RESTful APIs using HTTP APIs or REST APIs. HTTP APIs are the best way to build APIs for a majority of use cases—they're up to 71% cheaper than REST APIs. If your use case requires API proxy functionality and management features in a single solution, you can use REST APIs. WirelessCar Learn how connected mobility provider WirelessCar enhanced startup performance using AWS Lambda SnapStart for Java. Read the Case Study Odyssey Interactive Learn how game studio Odyssey Interactive launched its debut multiplayer game, Omega Strikers, worldwide using managed infrastructure on AWS. Read the Case Study Betterfly Learn how Betterfly simplifies group protection and benefits management and encourages daily positive habits using a digital solution built on AWS. Read the Case Study TiVo Learn how TiVo in the media and entertainment industry achieved burstable scalability and consistent uptime of streaming services using AWS Lambda and Amazon API Gateway. Read the Case Study Get started with API Gateway 1 Sign up for an AWS account Instantly get access to the AWS Free Tier . AWS Free Tier 2 Learn with step-by-step tutorials Explore and learn with simple tutorials . simple tutorials 3 Start building with AWS Visit the AWS Management Console . AWS Management Console Next steps Features page Learn more about API Gateway Visit the features page Getting started Ready to build? Get started Contact us Have more questions? Contact us Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://www.stackaid.us/github/istanbuljs/babel-plugin-istanbul | istanbuljs/babel-plugin-istanbul - StackAid / istanbuljs / babel-plugin-istanbul A babel plugin that adds istanbul instrumentation to ES6 code . Read more Own this project? It earned $1,347 /yr in our simulation . Get funding from your supporters, claim your project . Total received $11 Supporters ( 1 ) $5 Sourcegraph $5 Funded by ( 9 ) $5 bitinn/node-fetch $1 twbs/bootstrap < $1 adamreisnz/replace-in-file < $1 babel/babel-loader < $1 sinonjs/sinon < $1 caolan/async < $1 gajus/eslint-plugin-jsdoc < $1 reacttraining/react-router < $1 import-js/eslint-plugin-import < $1 Shared with ( 12 ) $6 arjanfrans/node-pmock < $1 kentcdodds/cross-env < $1 babel/babel < $1 mochajs/mocha < $1 nickmerwin/node-coveralls < $1 standard/standard < $1 chaijs/chai < $1 istanbuljs/nyc < $1 istanbuljs/istanbuljs < $1 istanbuljs/load-nyc-config < $1 Show all Projects Supporters About Blog Mastodon Contact Help Privacy Terms | 2026-01-13T08:48:37 |
https://www.stackaid.us/github/prettier/prettier | prettier/prettier - StackAid / prettier / prettier Prettier is an opinionated code formatter. Read more Own this project? It earned $21,768 /yr in our simulation . Get funding from your supporters, claim your project . Total received $176 Supporters ( 8 ) $103 Wes Carr $27 StackAid $20 Sentry $20 Dudley Carr $15 Sourcegraph $11 vilm3r $9 Burmis Studio $1 Nicolas Hoizey < $1 Funded by ( 168 ) $73 puppeteer/puppeteer $3 jefflau/jest-fetch-mock $2 hustcc/jest-canvas-mock $2 eemeli/yaml $1 typescript-eslint/typescript-eslint $1 moment/moment $1 testing-library/react-hooks-testing-library $1 zpao/qrcode.react $1 hipstersmoothie/storybook-dark-mode $1 billyvg/jest-sentry-environment $1 Show all Shared with $0 This project has no dependencies Projects Supporters About Blog Mastodon Contact Help Privacy Terms | 2026-01-13T08:48:37 |
https://docs.bsky.app/docs/starter-templates/custom-feeds | Custom Feeds | Bluesky Skip to main content Bluesky Docs Blog Directory GitHub Search Get Started Tutorials Starter Templates Bots Custom Feeds Client Apps Advanced Guides HTTP Reference Support Starter Templates Custom Feeds On this page Custom Feeds Custom feeds, or feed generators, are services that provide custom algorithms to users through the AT Protocol. This allows users to choose their own timelines, whether it's an algorithmic For You page or a feed of entirely cat photos. This is a starter kit for creating feed generators on atproto. It's not feature complete, but should give you a good starting ground off of which to build and deploy a feed. You can skip this tutorial and clone the TypeScript starter template directly here , or use community templates in Python or Ruby . Overview Custom feeds work very simply: the server receives a request from a user's server and returns a list of post URIs with some optional metadata attached. Those posts are then hydrated into full views by the requesting server and sent back to the client. A Feed Generator service can host one or more algorithms. The service itself is identified by DID, while each algorithm that it hosts is declared by a record in the repo of the account that created it. For instance, feeds offered by Bluesky will likely be declared in @bsky.app 's repo. Therefore, a given algorithm is identified by the at-uri of the declaration record. This declaration record includes a pointer to the service's DID along with some profile information for the feed. The general flow of providing a custom algorithm to a user is as follows: A user requests a feed from the AppView using the at-uri of the declared feed (Currently, this request is proxied via the PDS, but it will hit the AppView directly in the future) The AppView resolves the at-uri and finds the DID doc of the Feed Generator The AppView sends a getFeedSkeleton request to the service endpoint declared in the Feed Generator's DID doc This request is authenticated by a JWT signed by the user's repo signing key The Feed Generator returns a skeleton of the feed to the AppView The AppView hydrates the feed (user info, post contents, aggregates, etc.) The AppView returns the hydrated feed to the user For users, this should feel like visiting a page in the app. Once they subscribe to a custom algorithm, it will appear in their home interface as one of their available feeds. Starter Template Getting Started Clone the starter kit here . We've set up this simple server with SQLite to store and query data. Feel free to switch this out for whichever database you prefer. Next, you will need to do two things: Implement indexing logic in src/subscription.ts . This will subscribe to the repo subscription stream on startup, parse events and index them according to your provided logic. Implement feed generation logic in src/algos . For inspiration, we've provided a very simple feed algorithm ( whats-alf ) that returns all posts related to the titular character of the TV show ALF. You can either edit it or add another algorithm alongside it. The types are in place, and you will just need to return something that satisfies the SkeletonFeedPost[] type. We've taken care of setting this server up with a did :web . However, you're free to switch this out for did :plc if you like - you may want to if you expect this Feed Generator to be long-standing and possibly migrating domains. Deploying your feed Your feed will need to be accessible at the value supplied to the FEEDGEN_HOSTNAME environment variable. The service must be set up to respond to HTTPS queries over port 443. Publishing your feed To publish your feed, go to the script at scripts/publishFeedGen.ts and fill in the variables at the top. Examples are included, and some are optional. To publish your feed generator, simply run yarn publishFeed . To update your feed's display data (name, avatar, description, etc.), just update the relevant variables and re-run the script. After successfully running the script, you should be able to see your feed from within the app, as well as share it by embedding a link in a post (similar to a quote post). Running the Server Install dependencies with yarn and then run the server with yarn start . This will start the server on port 3000, or what's defined in .env . You can then watch the firehose output in the console and access the output of the default custom ALF feed at http://localhost:3000/xrpc/app.bsky.feed.getFeedSkeleton?feed=at://did:example :alice /app.bsky.feed.generator/whats-alf . Some Details Pagination You'll notice that the getFeedSkeleton method returns a cursor in its response and takes a cursor param as input. This cursor is treated as an opaque value and fully at the Feed Generator's discretion. It is simply passed through the AppView directly to and from the client. We strongly encourage that the cursor be unique per feed item to prevent unexpected behavior in pagination. We recommend, for instance, a compound cursor with a timestamp + a CID: 1683654690921::bafyreia3tbsfxe3cc75xrxyyn6qc42oupi73fxiox76prlyi5bpx7hr72u Language handling When making requests to getFeedSkeleton , clients are encouraged to populate the Accept-Language HTTP header with comma-separated BCP-47 language codes e.g. en,pr-BR . Feed generators can use this language context to filter or rank posts. If language filtering is applied, the feed generator should use the the Content-Language response header indicating the parsed language codes. Suggestions and Examples How a feed generator fulfills the getFeedSkeleton request is completely at their discretion. At the simplest end, a Feed Generator could supply a "feed" that only contains some hardcoded posts. For most use cases, we recommend subscribing to the firehose at com.atproto.sync.subscribeRepos . This websocket will send you every record that is published on the network. Since Feed Generators do not need to provide hydrated posts, you can index as much or as little of the firehose as necessary. Depending on your algorithm, you likely do not need to keep posts around for long. Unless your algorithm is intended to provide "posts you missed" or something similar, you can likely garbage collect any data that is older than 48 hours. Some examples: A community feed: Compile a list of DIDs within that community and filtering the firehose for all posts from users within that list. A topical feed: Filter the algorithm for posts and pass the post text through some filtering mechanism (an LLM, a keyword matcher, etc.) that filters for the topic of your choice. Edit this page Previous Bots Next Client Apps Overview Starter Template Getting Started Deploying your feed Publishing your feed Running the Server Some Details Docs Starter Templates AT Protocol Community Bluesky Twitter Community-run Discord Mailing List More Blog GitHub Discussions GitHub Copyright © 2026 Bluesky, PBC. | 2026-01-13T08:48:37 |
https://blog.devcycle.com/tag/case-studies/ | Case Studies - DevCycle Blog Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Case Studies A collection of 2 posts Case Studies Featured IGS Case Study - Using DevCycle in a Cloud-Based Microservices Architecture About IGS Intelligent Growth Solutions (IGS) is a pioneering company in the vertical farming industry, specializing in the development of advanced vertical farming towers. Their new and innovative approaches optimize agricultural productivity by using vertical space and technology to maximize crop yield and quality. IGS initially considered using flagd but Aug 9, 2024 3 min read Case Studies Featured Netlify Case Study - A Nearly Painless Migration to DevCycle from LaunchDarkly Netlify is a leading front-end platform known for its innovative web development solutions that power thousands of websites all around the web. Continuously releasing new features to their developer community quickly and reliably is an integral part of the business where speed and accuracy are of great importance. In this Apr 23, 2024 4 min read Page 1 of 1 DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://docs.bsky.app/docs/advanced-guides/firehose | Firehose | Bluesky Skip to main content Bluesky Docs Blog Directory GitHub Search Get Started Tutorials Starter Templates Advanced Guides The AT Protocol Federation Architecture Links, mentions, and rich text Rate Limits Labels and moderation Posts Timestamps Firehose Resolving Identities Custom Schemas Backfilling the Network Read-After-Write Service Auth PDS Entryway oEmbed and Post Embed Widget Action Intent Links OAuth Client Implementation API Hosts and Auth HTTP Reference Support Advanced Guides Firehose Firehose One of the core primitives of the AT Protocol that underlies Bluesky is the firehose . It is an authenticated stream of events used to efficiently sync user updates (posts, likes, follows, handle changes, etc). Many applications people will want to build on top of atproto and Bluesky will start with the firehose, from feed generators to labelers, to bots and search engines. In the atproto ecosystem, there are many different endpoints that serve firehose APIs. Each PDS serves a stream of all of the activity on the repos it is responsible for. From there, relays aggregate the streams of any PDS who requests it into a single unified stream. This makes the job of downstream consumers much easier, as you can get all the data from a single location. The main relay for Bluesky is bsky.network , which we use in the examples below. To get started, you will open a WebSocket connection to your favorite firehose provider for the com.atproto.sync.subscribeRepos endpoint: Go uri := "wss://relay1.us-east.bsky.network/xrpc/com.atproto.sync.subscribeRepos" con , _ , err := websocket . DefaultDialer . Dial ( uri , http . Header { } ) note We previously provided a wss://bsky.network example URL here. This endpoint does not provide prevData which may limit your use of the firehose in some contexts. When in doubt, use the Sync 1.1 endpoints . From there, you need to read off each message as it comes in, and decode the CBOR event data. More details on this can be found here Most SDKs have a nice wrapper for this though, In this example we will just print each repo operation in each event we receive. These operations are things like "create post", "create like", "delete follow" and so on. Go rsc := & events . RepoStreamCallbacks { RepoCommit : func ( evt * atproto . SyncSubscribeRepos_Commit ) error { fmt . Println ( "Event from " , evt . Repo ) for _ , op := range evt . Ops { fmt . Printf ( " - %s record %s\n" , op . Action , op . Path ) } return nil } , } sched := sequential . NewScheduler ( "myfirehose" , rsc . EventHandler ) events . HandleRepoStream ( context . Background ( ) , con , sched ) In this snippet we set up a sequential "scheduler", which handles all events sequentially in order. Other schedulers run event handling in parallel, or do limited concurrency based on who the event is for. Once we have a scheduler, we call into HandleRepoStream which does the actual decoding of the data coming over the websocket and calls into the event handler we wrote. If you want a more simplified firehose where events are JSON, you can connect to the JetStream websocket: Python import asyncio import websockets uri = "wss://jetstream2.us-east.bsky.network/subscribe?wantedCollections=app.bsky.feed.post" async def listen_to_websocket ( ) : async with websockets . connect ( uri ) as websocket : while True : try : message = await websocket . recv ( ) print ( message ) except websockets . ConnectionClosed as e : print ( f"Connection closed: { e } " ) break except Exception as e : print ( f"Error: { e } " ) asyncio . get_event_loop ( ) . run_until_complete ( listen_to_websocket ( ) ) Edit this page Previous Timestamps Next Resolving Identities Docs Starter Templates AT Protocol Community Bluesky Twitter Community-run Discord Mailing List More Blog GitHub Discussions GitHub Copyright © 2026 Bluesky, PBC. | 2026-01-13T08:48:37 |
https://docs.bsky.app/docs/get-started | Get Started | Bluesky Skip to main content Bluesky Docs Blog Directory GitHub Search Get Started Tutorials Starter Templates Advanced Guides HTTP Reference Support Get Started On this page Get Started Make your first post to the Bluesky app via the API in under 5 minutes. Install the SDK Choose the SDK you want to work with. Below, we use TypeScript and Python. You can follow the instructions for the community-maintained atproto.dart package here . Typescript CURL Python Install @atproto/api using your preferred package manager. yarn add @atproto/api Install CURL if you need to. It comes pre-installed on most operating systems. Install atproto using your preferred package manager. pip install atproto Create a session Create an authentication session with your username and password. Typescript CURL Python import { BskyAgent } from '@atproto/api' const agent = new BskyAgent ( { service : 'https://bsky.social' } ) await agent . login ( { identifier : 'handle.example.com' , password : 'hunter2' } ) Replace $BLUESKY_HANDLE and $BLUESKY_PASSWORD with your credentials, and $PDSHOST with your PDS host (including https:// ). curl -X POST $PDSHOST/xrpc/com.atproto.server.createSession \ -H "Content-Type: application/json" \ -d '{"identifier": "'"$BLUESKY_HANDLE"'", "password": "'"$BLUESKY_PASSWORD"'"}' from atproto import Client client = Client ( ) client . login ( 'handle.example.com' , 'hunter2' ) The com.atproto.server.createSession API endpoint returns a session object containing two API tokens: accessJwt : an access token which is used to authenticate requests but expires after a few minutes refreshJwt : a refresh token which lasts longer and is used only to update the session with a new access token Typescript CURL Python The agent object stores this session information for you, and will include it in the headers of its requests. The client instance stores and manages this session information for you, and will include it in the headers of its requests. Create a post Now you can create a post by sending a POST request to the createRecord endpoint. Typescript CURL Python await agent . post ( { text : 'Hello world! I posted this via the API.' , createdAt : new Date ( ) . toISOString ( ) } ) Replace $BLUESKY_HANDLE with your handle, $PDSHOST with your PDS host (including https:// ), and and $ACCESS_JWT with the JWT in the response from createSession. curl -X POST $PDSHOST/xrpc/com.atproto.repo.createRecord \ -H "Authorization: Bearer $ACCESS_JWT" \ -H "Content-Type: application/json" \ -d "{\"repo\": \"$BLUESKY_HANDLE\", \"collection\": \"app.bsky.feed.post\", \"record\": {\"text\": \"Hello world! I posted this via the API.\", \"createdAt\": \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}}" post = client . send_post ( 'Hello world! I posted this via the Python SDK.' ) This will return an object containing the post's URI and a CID (a hash of the content). Typescript CURL Python { "uri": "at://did:plc:abc123..../app.bsky.feed.post/xyz...", "cid": "abc..." } { "uri": "at://did:plc:abc123..../app.bsky.feed.post/xyz...", "cid": "abc..." } post . uri # at://did:plc:abc123..../app.bsky.feed.post/xyz... post . cid # abc... Check out your profile to see the post you just created! Next Steps Jump to one of the Starter Templates : Bots Custom Feeds Clients Continue reading Tutorials to learn more. Edit this page Next Tutorials Install the SDK Create a session Create a post Next Steps Docs Starter Templates AT Protocol Community Bluesky Twitter Community-run Discord Mailing List More Blog GitHub Discussions GitHub Copyright © 2026 Bluesky, PBC. | 2026-01-13T08:48:37 |
https://twitter.com/intent/tweet?text=%22Flutter%20ECS%3A%20Mastering%20Async%20Operations%20and%20Complex%20Workflows%22%20by%20Dr.%20E%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fflameofudun%2Fflutter-ecs-mastering-async-operations-and-complex-workflows-463g | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:37 |
https://blog.devcycle.com/what-we-shipped-in-q3-user-debug-tools-ai-generated-features-and-m/ | What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 DevCycle Nov 5, 2025 • 3 min read Check out what the DevCycle team shipped in Q3! In the last few months we’ve released a ton of upgrades including; a suite of debugging functionality, powerful AI-assisted tooling and new observability integrations. Combined, this functionality makes it even easier to understand how your features behave in production. 🧩 User Debug Tools The new suite of Debug Tools: Evaluation Lookup , Point-In-Time Simulation , Live Events and the Web Debugger , make it easier to validate, troubleshoot, and understand how your Features behave for specific users, all without leaving the dashboard. If you need to figure out why a User is being served a specific variation of a Feature, one of these tools is sure to help! Keep reading to learn more about each tool. 🔎 Evaluation Lookup What it is: Inspect how and why a specific user received a variation. View complete evaluation reasons, targeting matches, and environment context to confirm whether a user met the correct targeting rules—fast. Use when: A user reports seeing the wrong variation, or when validating feature rollouts before production. 📍 Point-in-Time Simulation What it is: Simulate a user’s feature flags based on a historical project configuration. Investigate regressions or unexpected behavior by viewing how a Feature (or Features) was evaluated for a specific user at any point in time. Use when: Debugging incidents, reproducing user reports from a past date (especially after a Feature configuration change or rollbacks), or when leveraging Local Bucketing SDKs. ▶️ Live Events What it is: Stream real-time variable evaluations, defaults, and custom events. Watch variable evaluations, variable defaults, and custom events as they’re received from your application in real time—connected directly to the SDK event stream. Use when: Verifying SDK event delivery, testing variable evaluations live, or ensuring custom events are being tracked correctly for yourself or a specific user. 🧰 Web Debugger What it is: Embed DevCycle’s debugging tool directly into your application. Override values using Self-Targeting for testing without code changes, and view live SDK events to monitor variable evaluations and confirm custom events are firing. Use when: You want to debug or test your Features directly in-app without accessing the DevCycle dashboard. Together, these tools make it simple to pinpoint flag logic, validate targeting, and troubleshoot issues faster—without digging through logs or guesswork. 🚀 🧠 AI-Generated Schemas & Feature Summaries We’re bringing AI deeper into your DevCycle workflow. These new tools help automate some of the most time-consuming setup and documentation tasks for your team. 💂 AI-Generated Schemas Variable Schemas protect your production environment by enforcing allowed values for Variables—but creating them manually can be tedious. With AI-Generated Schemas , DevCycle analyzes your existing Variable configurations and automatically builds a Schema that validates against those values. You can then fine-tune it as needed. 📋 AI-Generated Feature Summaries Keep your teammates aligned without manual upkeep. AI-Generated Feature Summaries use your current Feature configuration to produce an instant, point-in-time description you can edit and share. Perfect for keeping documentation fresh and accurate. 📈 Dynatrace Integration Send DevCycle Feature changes and runtime evaluations directly into Dynatrace so your teams can easily monitor app performance tied to flags. Feature change events (targeting/variation updates) stream into Dynatrace via predefined workflows Flag evaluation traces captured by OneAgent using SDK hooks Prebuilt Dynatrace dashboard to investigate anomalies alongside feature context Automatic environment mapping between DevCycle and Dynatrace This integration adds Feature Flag evaluation data to your traces, helping with faster debugging, tracking rollbacks, and shipping with confidence 🚀 🛠️ General UX & Dashboard Improvements Added Variable Schema creation directly in the Feature Overview Added Environment “Last Modified” dates and deep links to Audit Log entries We all hope our users find these new features and functionality valuable. We love feedback and requests, visit our public roadmap to weigh in! Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://twitter.com/share?url=https%3a%2f%2fstackoverflow.com%2fq%2f79866767%3fstw%3d2 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:37 |
https://blog.devcycle.com/why-feature-flags-are-a-must-in-every-engineering-managers-toolkit/ | Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit Mark Allen Dec 9, 2025 • 3 min read When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a foundational tool in your toolbox. Decoupling Deployments from Releases One of the biggest killers of velocity is tying releases to deployments. When every deployment must coincide with a public-facing release, your team ends up coordinating more, waiting more, and fearing failure more. Feature flags break that bond. They let you deploy code continuously, merge to trunk, push to production, but hide features until they’re ready. That way, you can test in production, validate performance, get early feedback, all without exposing incomplete or risky changes to your full user base. This is one of the core benefits discussed in Feature Flags by Everyday DevOps , they allow code to be merged and deployed while remaining hidden until product and engineering agree it’s ready. The Bridge Between Engineering and Product Feature flags aren’t just a technical tool. They become a communication tool between product and engineering. Product can decide when to turn something on, not when engineers finish a chunk of work. Engineering can deliver in smaller increments, feel safer about pushing code, and reduce risk. You get to shift from “big bang launches” to smaller, reversible decisions. Product managers can preview, stakeholders can test, QA and beta users can validate. If things go sideways, you roll back with a flag. This kind of controlled rollout reduces firefighting. Everyday DevOps calls this out: feature flags allow product managers to get feedback before a full launch and enable quick rollback when needed. Avoid the Homegrown Trap As tempting as it is to roll out your own feature flag system, I’ve been there, don’t underestimate the cost. Why a Homegrown Feature Flag System Is a Trap , lays this out clearly. Key pitfalls: Maintenance overhead: dashboards, SDKs in different languages, auditing, scaling. Technical debt: flags that never get cleaned up, complexity creeping in. Opportunity cost: engineers’ time lost on maintaining tooling instead of delivering product. Instead of building from scratch, a better path is to adopt something like OpenFeature (an open standard), wrap any existing flag logic, and if needed, migrate toward a commercial provider over time. That gives you structure without stifling flexibility. Measuring Success with DORA Metrics Feature flags aren’t magic. To make them count, you need to measure. This is where integrating with DORA metrics (especially Lead Time for Change and Deployment Frequency ) becomes powerful. Connecting Feature Flags and DORA Metrics shows how feature flags shorten lead time, raise deployment frequency, reduce failure rate, and speed up recovery when things go wrong. If I were you, I’d track: Lead Time for Change : from when work begins (or gets committed) to when it’s actually live (even if hidden). Feature flags let you get code live faster even when it’s not released. Deployment Frequency : using smaller, more frequent deployments rather than big ones. Feature flags enable you to merge and deploy often because you’re not exposing unfinished work. Change Failure Rate and Mean Time to Recovery : since you can test with beta users or small cohorts and roll back quickly if something goes wrong. Feature flags give you that safety valve. My Recommendations: How to Get Started the Right Way Here are practices I’d adopt early on, things I wish I’d done when I was new to the role. Practice Why It Matters Decide flag ownership up front Who writes flags? Who removes them? Who turns them on/off? Without clear roles, flags linger forever and become debt. Build flag hygiene into planning When you plan any feature, ask: Do we need a flag? Will this be really released immediately? If yes, use a flag. Also plan for flag cleanup. Use progressive rollouts / percentage based rollouts Let some traffic or some users opt in first. Monitor errors, KPIs. Then expand or rollback. Make feature flags visible Product, QA, engineering, operations, everyone should see what flags exist, their status, who owns them. Transparency matters. Avoid re-inventing flag infrastructure As noted in Why a Homegrown Feature Flag System Is a Trap , the cost in maintenance and staff time adds up fast. Use OpenFeature, or adopt a mature provider. Conclusion If I could give one piece of advice: treat feature flags not as an add-on but as a core capability. They let you decouple deployments from releases, give product and engineering space to collaborate safely, and bring predictability and measurement into how you move fast. Use them well, measure with them, respect them, and you’ll reduce risk, reduce crisis moments, and lead your team toward more confident delivery. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 In the last few months we’ve released a ton of upgrades including; a suite of debugging functionality, powerful AI-assisted tooling and new observability integrations. Combined, this functionality makes it even easier to understand how your features behave in production. 🧩 User Debug Tools The new suite of Debug Tools: Evaluation Nov 5, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/tag/product-updates/ | Product Updates - DevCycle Blog Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Product Updates Find out what's new at DevCycle and what we're working on next Product Updates From Hackathon to Production: What It Took to Ship Our DevCycle MCP When we started building our MCP server, it began as a simple hackathon project: take our existing CLI interface, which already has authentication and most of our API calls, and adapt it to work as an MCP server. As a hackathon project, it turned out to be a pretty compelling Sep 1, 2025 8 min read Product Updates DevCycle Product Updates (Q1 2025) Find out what's new at DevCycle, including stale flag alerts, project level RBAC and enhancements to targeting. Welcome to your Q1 2025 DevCycle product update! We’ve rolled out a ton of exciting improvements in the past few months — from powerful new lifecycle tools to better access management May 12, 2025 2 min read OpenFeature OpenFeature Hackathon 2024 A few times a year at DevCycle, we hit pause on our usual work, push aside our roadmaps, and dive into a few days of rapid experimentation and collaboration. For our first hackathon of 2025, we opted for an OpenFeature theme —a chance to explore new ideas, test bold concepts, Mar 19, 2025 9 min read Product Updates July 2024 Changelog At DevCycle, we're committed to delivering powerful feature management solutions that empower teams to safely and easily control their feature releases. In this blog post, we're excited to share two significant updates that will enhance your experience with DevCycle: Approval Workflows and a Vercel Edge Config Jul 31, 2024 2 min read Product Updates June 2024 Changelog Welcome to our monthly changelog, where we share the latest feature updates and improvements from DevCycle. We're excited to bring you two significant updates that will enhance your feature management experience: OpenFeature Multi-Provider and the Web Debugger. To see more of what's coming or to request Jun 28, 2024 2 min read Product Updates May 2024 Changelog Welcome to our May changelog, where we share the latest feature updates and improvements from DevCycle. This month, we've focused on enhancing our integrations, improving performance for server-side rendering, and introducing a new way to manage complex schedules and variations with Passthrough Rollouts. If you want to read May 31, 2024 2 min read Product Updates April 2024 Changelog Spring is in the air and we've got our April edition of the monthly changelog for you. This month features a DevCycle App for Slack, one of our most requested features, along with quite a few other improvements. Check out the details below. 🧵 DevCycle App for Slack We Apr 30, 2024 2 min read Product Updates March 2024 Changelog The snow is melting and we've got a small but mighty set of new functionality for you this month. 🥷 Feature Obfuscation Feature flags are often used to hide upcoming features before release. Normally, not showing the feature on a UI is enough to conceal it from users. However, Mar 31, 2024 2 min read Product Updates February 2024 Changelog Welcome to February's edition of our product changelog. We had updates both big and small to the platform in the rare 29 days of February. This month primarily featured some updates to our Lifecycle functionality, as well as some great work on our SDKs. Feature Archiving We’re Feb 29, 2024 3 min read Product Updates DevCycle Becomes a CVE Numbering Authority We're thrilled to announce DevCycle has been officially authorized by the CVE Program as a CVE Numbering Authority (CNA). This marks a new chapter in our commitment to cybersecurity excellence and a safer digital world. Feb 15, 2024 2 min read Product Updates January 2024 Changelog Welcome to a new blog, email and stream series that our Product team is running that aims to highlight what our team has built each month. We're really excited to share all of the things that we're working on, and hope that anyone with an interest Jan 31, 2024 3 min read Page 1 of 1 DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/using-feature-flags-to-build-a-better-ai/ | Using Feature Flags to Build a Better AI Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Using Feature Flags to Build a Better AI Mark Allen Apr 25, 2025 • 3 min read In a world where AI is becoming increasingly prevalent in applications, there is a need to ensure that the AI is accurate. We hear a lot about failures with chatbots going rogue, image generators showing physically incorrect images, and generally wrong answers to simple questions. So, how can you ensure that your model works, more importantly, that new models you create work in the real world before making them available to the general public? How do you go about testing out new AI models? With feature flags , that's how. We encountered these challenges while developing Helix , an advanced player tracking and behavior analysis solution that seamlessly integrates in-game actions with mobile interactions. Through machine learning, Helix monitors player activities such as logging in, viewing, or clicking on virtual items, as well as scanning virtual items using the mobile app. By utilizing image recognition technology, Helix accurately associates in-game behavior with mobile app usage, offering deeper insights into user engagement and optimizing the gaming experience. Helix - Game Crafters Guild t-shirt Part of the Helix technology stack is an image recognition system. This is based upon an internally managed image classification system. When new image classifications are added, how do we know if they will work in the real world with real users and return the correct classification? To handle this, we built the ability to select which model to use into our image recognition microservice using a feature flag. This way, we could test to see how well it worked with a specific set of internal and external beta users before making it the default model for all users. DevCycle Variable for the model to use When we created a new model, our product manager would add it as a new variation in DevCycle . The Test Model would then only be shown to a specific set of users. Our image recognition microservice is an internal service that takes an image as input and returns a list of matching classifications, along with their corresponding confidence scores. It is accessed through external APIs, which require either user or machine authentication. For authenticated users, we passed in the user's email address from the external API as a custom header. async scanImageV4( @Request() req, @UploadedFile() file: Express.Multer.File, @Headers('X-GATHERER-USER-EMAIL') email?: string, ) { NestJS controller for the image scanner showing customer email header Then we could use DevCycle to return the correct model to use for the specific image classification call. const user: DevCycleUser = { user_id: origin.uuid, email: email, }; await this.devcycleClient.onClientInitialized(); const activeRekogntionModel = this.devcycleClient.variable( user, 'helix-active-rekognition-model', process.env.AMAZONREKOG_MODEL, ); Call to DevCycle to get the correct version of the model to use for this user. This became a bit trickier for our mobile application, which didn't have an authentication system. To handle this, we used the device identifier provided by Android and iOS. Since the mobile application already had a scanner built into it, we created a QR code that the user could scan and placed it on our internal wiki. Within the UI, we displayed the ID along with a copy button, so they could add it to DevCycle and test the new model. Device ID in the mobile app Conclusion Incorporating feature flags into the Helix image recognition system allowed us to test new AI models safely and effectively before full deployment. By targeting specific users, whether through authenticated email addresses or device identifiers, we could gather real-world feedback and performance data without risking the reliability of the overall application. This approach not only improved the accuracy and robustness of our AI models but also accelerated iteration and innovation. As AI continues to shape user experiences, embedding tools like feature flags into your development pipeline is essential for controlled experimentation, rapid validation, and delivering trustworthy results at scale. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://www.linkedin.com/company/sui-foundation/ | Sui Foundation | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join for free Sui Foundation Blockchain Services High-performance blockchain delivering the full stack for a new global economy. See jobs Follow Discover all 216 employees Report this company About us The Sui Foundation is an independent organization that is dedicated to the advancement and adoption of the Sui network. The Foundation fulfills its mission by educating, activating, funding, and promoting builders and creators within the Sui ecosystem. Sui is a blockchain built from the ground up with the goal of providing a seamless and user-friendly experience for all its users. One of the main features of the Sui network is its ability to support the creation of rich and dynamic on-chain assets while also offering instant settlement and high throughput. In turn, the Sui network is a highly scalable and secure blockchain platform that makes digital asset ownership and management accessible to everyone. Join the Sui community and help build experiences that cater to the next billion users in web3. Website https://sui.io/ External link for Sui Foundation Industry Blockchain Services Company size 51-200 employees Headquarters Grand Cayman Type Nonprofit Founded 2022 Locations Primary 9 Forum Lane Grand Cayman, KY1-9006, KY Get directions 4849 Greenville Ave Dallas, Texas 75206, US Get directions Employees at Sui Foundation Jameel Khalfan Ranier Gadduang Marc Lebreton Kenton Langstroth See all employees Updates Sui Foundation 36,127 followers 7h Report this post From data → decisions → payments: the loop is closed. AI isn’t “software on top” anymore - it is the system. So trust can’t be vibes. It has to be built in. Walrus → verifiable data Seal → programmable access Nautilus → secure execution Sui → control, audit, receipts Read on 👇 https://lnkd.in/dahVUbBf 13 1 Comment Like Comment Share Sui Foundation 36,127 followers 4d Report this post DeFi deserves better infrastructure. No more fragile execution, siloed liquidity, or glued-together primitives. Sui is built for composable, high-performance DeFi - from execution to native shared liquidity. Explore the Sui Stack for DeFi 👉 sui.io/defi 52 1 Comment Like Comment Share Sui Foundation 36,127 followers 5d Report this post Perps are heating up - and Sui is where builders are pushing the boundaries. Aftermath, Astros, Bluefin, FlowX & Zo broke down how they’re approaching execution, collateral, aggregation & UX. One theme: Sui enables designs that just aren’t feasible elsewhere. Read on 👇 https://lnkd.in/dP37GchG 50 4 Comments Like Comment Share Sui Foundation 36,127 followers 6d Report this post AI’s moving fast, but the foundation is shaky. Hallucinations, shady predictions, insecure code. The problem? Data. The Sui stack makes AI verifiable end-to-end: Walrus. Seal. Nautilus. Sui. Provable > black box. …more 94 6 Comments Like Comment Share Sui Foundation 36,127 followers 2w Report this post 2025 took Sui around the world IRL. 17 cities. 13,000+ people. Dubai, Singapore, Seoul, and everywhere in between. Conversations, connections, and moments we’ll be carrying forward. If you were there, you know. If not, 2026 is warming up 👀 Read on 👇 https://lnkd.in/dvJupT3d 193 5 Comments Like Comment Share Sui Foundation 36,127 followers 2w Report this post Modern apps need modern infrastructure. Ownable. Verifiable. Composable. The Sui Stack is ready - from day one. Start building 👉 sui.io …more 61 Like Comment Share Sui Foundation 36,127 followers 2w Report this post AI agents are about to become economic actors. They will plan, decide, and pay. Our payment systems were never designed for that. Giving an agent full wallet access is reckless. Blocking it from paying makes it useless. The real solution is programmable trust. Separate intent, authorization, and execution. Set clear constraints like spending limits and scopes. Let agents act autonomously while everything stays verifiable and auditable. The agent economy won’t run on blind trust. If AI agents are going to transact, trust has to be explicit and programmable. Read on for more 👇 https://lnkd.in/ggQz2b5K 47 3 Comments Like Comment Share Sui Foundation 36,127 followers 3w Report this post If your app still needs five offchain services to function, your stack is broken. In 2025, Sui finished the job: fast execution, verifiable storage, real access control, usable data. This is what an end-to-end decentralized stack looks like. Read on 👇 https://lnkd.in/gW3_2amh 61 1 Comment Like Comment Share Sui Foundation 36,127 followers 3w Report this post Sui 2025 → 2026 w/ Adeniyi, Evan, Kostas, and Aslan www.linkedin.com 68 4 Comments Like Comment Share Sui Foundation 36,127 followers 3w Report this post More devs, more transactions, more DeFi, more BTCfi. More Sui. 2025 wrapped 👇 …more 146 3 Comments Like Comment Share Join now to see what you are missing Find people you know at Sui Foundation Browse recommended jobs for you View all updates, news, and articles Join now Similar pages Mysten Labs Software Development Solana Technology, Information and Internet Aptos Labs Technology, Information and Internet Palo Alto, CA Chainlink Labs Technology, Information and Internet Polygon Labs Technology, Information and Internet Phantom Software Development San Francisco, CA Avalanche Technology, Information and Internet Ithaca, New York Ripple Technology, Information and Internet San Francisco, CA Aptos Foundation Technology, Information and Internet Binance Technology, Information and Internet Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Developer jobs 258,935 open jobs Intern jobs 71,196 open jobs Associate jobs 1,091,945 open jobs Business Development Specialist jobs 29,135 open jobs Project Manager jobs 253,048 open jobs Marketing Manager jobs 106,879 open jobs Human Resources Specialist jobs 34,340 open jobs Community Development Specialist jobs 36,843 open jobs Account Manager jobs 121,519 open jobs Director jobs 1,220,357 open jobs Head jobs 1,018,536 open jobs Human Resources Manager jobs 31,339 open jobs Team Lead jobs 1,056,618 open jobs Scientist jobs 48,969 open jobs Partnerships Manager jobs 61,442 open jobs Recruiter jobs 243,016 open jobs Designer jobs 65,273 open jobs Show more jobs like this Show fewer jobs like this Funding Sui Foundation 1 total round Last Round Seed Feb 1, 2024 External Crunchbase Link for last round of funding Investors BlockBase Ventures See more info on crunchbase More searches More searches Developer jobs Engineer jobs Marketing Manager jobs Project Manager jobs Manager jobs Product Designer jobs Community Manager jobs Human Resources Manager jobs Director jobs Community Lead jobs Full Stack Engineer jobs Partnerships Manager jobs Senior Software Engineer jobs User Experience Designer jobs Associate jobs Strategy Manager jobs Analyst jobs Human Resources Specialist jobs Institutional Sales Manager jobs Head jobs Intern jobs Specialist jobs Account Manager jobs Human Resources Business Partner jobs Operations Manager jobs Head of Marketing jobs Executive jobs Contract Engineer jobs Designer jobs Business Development Specialist jobs Creative Developer jobs Head of Trading jobs Options Trader jobs Literary Agent jobs Recruiter jobs Mobile Engineer jobs Investment Analyst jobs Head of Human Resources jobs Researcher jobs Country Manager jobs Application Manager jobs Senior Marketing Specialist jobs Human Resources Generalist jobs Python Developer jobs Investment Banking Associate jobs Plant Human Resources Manager jobs Ecommerce Specialist jobs Associate Marketing Manager jobs Builder jobs Marketing Associate jobs Spring Intern jobs Marketer jobs Chief Information Officer jobs Writer jobs Marketing Director jobs Junior Project Manager jobs Customer Engineer jobs Javascript Developer jobs Commercial Manager jobs Marketing Coordinator jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at Sui Foundation Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:37 |
https://blog.devcycle.com/why-a-homegrown-feature-flag-system-is-a-trap/ | Why a Homegrown Feature Flag System is a Trap Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Why a Homegrown Feature Flag System is a Trap Mark Allen Dec 10, 2025 • 4 min read Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in as the system grows. Maintaining that DIY solution steals time and focus from your core product. The Hidden Cost of “Build It Ourselves” Your in‑house flag tool will demand far more than the initial build. You’ll need to maintain APIs, update SDKs for new languages, scale the service, provide dashboards, handle audits, and add targeting rules. Every hour spent on these tasks is an hour not spent building differentiating features. Over time, that opportunity cost grows. The Real Numbers Behind Maintenance Many teams underestimate just how much time a home‑grown system will consume. Consider these data points: Engineers lose up to 30% of their time maintaining DIY feature flag tools [1] . With a 40‑hour workweek, that equates to roughly 48–52 hours per month that could have been spent on core product development. A recent survey found that 70% of teams without commercial feature management spend more than 25% of their time on pre‑release testing and bug fixing [2] Research on feature‑flag technical debt reveals that 73% of flags are never removed and that developers spend more than five hours per week navigating flag‑ridden code [3] . For a ten‑developer team, that debt totals about 2600 lost hours per year, or around 22 hours per developer per month . Wayfair’s homegrown feature flag system cost the company over $3 million a year [4] . By switching to a commercial platform, they cut that cost by two‑thirds. These numbers make it clear: building your own feature flag system isn’t just a minor distraction; it’s a substantial drain on productivity and money. The Bridge: OpenFeature If you already have a home‑grown solution, you don’t need to throw it out overnight. OpenFeature offers an open standard that lets you wrap your existing system behind a common API. Think of it as Kubernetes for feature flags: a consistent set of SDKs that can switch between different backends. With OpenFeature, you can: Keep using your current flags while migrating gradually. Add support for multiple languages and frameworks with standardized SDKs. Avoid vendor lock-in by swapping providers without modifying your application code. Example: Creating a Custom Provider Here’s a simplified example in TypeScript showing how to wrap a home‑grown flag service with an OpenFeature provider. The provider fetches flag values from an internal dictionary, but could easily call your own API or database. import { Provider, ResolutionDetails, StandardResolutionReasons, } from '@openfeature/server-sdk'; export class HomegrownProvider implements Provider { name = 'homegrown'; async resolveBooleanEvaluation( flagKey: string, defaultValue: boolean, ): Promise<ResolutionDetails<boolean>> { // Replace with real DB or API call const flags: Record<string, boolean> = { 'new-ui': true, 'beta-mode': false, }; return { value: flags[flagKey] ?? defaultValue, reason: StandardResolutionReasons.STATIC, }; } } You register this provider and query it like this: import { OpenFeature } from '@openfeature/server-sdk'; import { HomegrownProvider } from './homegrown-provider'; OpenFeature.setProvider(new HomegrownProvider()); const client = OpenFeature.getClient(); const enabled = await client.getBooleanValue('new-ui', false); console.log(`New UI enabled? ${enabled}`); This approach allows you to standardize your flag API while still utilizing your own backend. Example: Migrating with DevCycle's Provider Once you’re ready to move away from your homegrown flags, you can plug in a commercial provider, such as DevCycle , behind the same OpenFeature API and use it at the same time as your existing one. This way you can keep the existing flags in the current provider and slowly transition off it. Here’s what that looks like: import { MultiProvider } from '@openfeature/multi-provider'; import { OpenFeature } from '@openfeature/server-sdk'; import { DevCycleProvider } from '@devcycle/nodejs-server-sdk'; // DevCycle Provider Setup const { DEVCYCLE_SDK_KEY } = process.env; const user = { user_id: "user_id" }; const devcycleProvider = new DevCycleProvider(DEVCYCLE_SDK_KEY); // Existing Provider Setup const existingProvider = new ExistingProvider(); // Multi-provider Setup const multiProvider = new MultiProvider([ { provider: devcycleProvider }, { provider: existingProvider } ]); await OpenFeature.setContext(user); await OpenFeature.setProviderAndWait(multiProvider); const openFeatureClient = OpenFeature.getClient(); const value = await openFeatureClient.getStringValue( 'flag-key', 'default value', someUser ); This incremental approach reduces risk by using both system in parallel before making a full switch. Giving your teams time to learn the new platform and time to cycle the flags used by the existing system out of the code base. (Watch) DevCycle 's CTO Jonathan Norris goes through how to do this: DevCycle's CTO gives a talk on how to use the OpenFeature Multi-Provider for Feature Flagging Using DevCycle After wrapping your DIY system with OpenFeature, you’ll want to adopt a provider whose core business is feature flags. DevCycle offers developer‑friendly workflows, experimentation tools, a modern UI and integrates with OpenFeature, making migration as simple as swapping providers. The Everyday DevOps Lesson Building your own feature flag system might feel empowering at first, but the data shows it’s a costly detour. Teams spend dozens of hours each month maintaining infrastructure that doesn’t differentiate their product, and the opportunity cost grows as the system scales. The smarter path is to adopt OpenFeature early, wrap your existing system as a provider, and plan a gradual migration to a commercial platform. That way, you keep your engineers focused on innovation instead of reinventing the wheel. John Arnsdorf, Step-by-Step Guide to Regrettably Maintaining a DIY Feature Flag Tool, February 27, 2025 , https://www.harness.io/blog/regrettably-maintaining-a-diy-feature-flag-tool Matt DeLaney, The Impact of Feature Management on Software Engineering and Business Performance, July 22 2024, https://launchdarkly.com/blog/2024-survey-impact-of-feature-management/ What is Feature Flag Technical Debt?, January 2025, https://flagshark.com/learn/what-is-feature-flag-debt/ Michael Ferranti, Feature Flags: Build or Buy?, July 17, 2024, https://www.getunleash.io/blog/feature-flags-build-buy Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 In the last few months we’ve released a ton of upgrades including; a suite of debugging functionality, powerful AI-assisted tooling and new observability integrations. Combined, this functionality makes it even easier to understand how your features behave in production. 🧩 User Debug Tools The new suite of Debug Tools: Evaluation Nov 5, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://docs.microsoft.com/en-us/xamarin/xamarin-forms/release-notes/4.5/4.5.0-pre2#androidx | Xamarin.Forms 4.5.0.187-pre2 (4.5.0 Pre Release 2) Release Notes - Xamarin | Microsoft Learn Skip to main content Skip to Ask Learn chat experience This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Download Microsoft Edge More info about Internet Explorer and Microsoft Edge Table of contents Exit editor mode Ask Learn Ask Learn Focus mode Table of contents Read in English Add Add to plan Share via Facebook x.com LinkedIn Email Print Note Access to this page requires authorization. You can try signing in or changing directories . Access to this page requires authorization. You can try changing directories . Xamarin.Forms 4.5.0.187-pre2 (4.5.0 Pre Release 2) Release Notes Feedback Summarize this article for me In this article Getting Started | What's New | Known Issues | Breaking Changes | API Changes | Blogs | Thank you | Feedback | Open Source Summary Many core controls have received additional improvements, and we've introduced a few new capabilities to optimize your productivity developing cross-platform applications. AndroidX Xamarin.Forms now uses the latest AndroidX libraries from Google. These replace the Android Support libraries which are no longer being updated. This requires no change to your code. If you notice any undesirable side-effects, please open an issue here . Built with Visual Studio 2019 The Xamarin.Forms NuGet is now being built with Visual Studio 2019 and the latest Mono and platform SDKs while still supporting the ability to build with Visual Studio 2017 and the equivelant on Mac. If you notice any undesirable side-effects, please open an issue here . Embedded Fonts Now to use fonts you only need to add them to your Xamarin.Forms shared library as embedded resources and reference them with an assembly tag, rather than adding them to multiple platforms, each with their own implementation rules. To your AssemblyInfo.cs add: using Xamarin.Forms; [assembly: ExportFont("CuteFont-Regular.ttf")] Then to use the font in XAML, reference that name: <Label Text="Hello Embedded Fonts" FontFamily="CuteFont-Regular"/> VisualStateManager Target Now you can update multiple controls when a state changes by specifying the target control and property. It can look something like this: <VisualStateManager.VisualStateGroups> <VisualStateGroup Name="ColorStates"> <VisualState Name="Red"> <VisualState.Setters> <Setter TargetName="TargetLabel1" Property="Label.BackgroundColor" Value="#340002" /> <Setter TargetName="TargetLabel1" Property="Label.TextColor" Value="#920e0c" /> <Setter TargetName="TargetLabel1" Property="Label.Text" Value="Red" /> </VisualState.Setters> </VisualState> <VisualState Name="Blue"> <VisualState.Setters> <Setter TargetName="TargetLabel1" Property="Label.BackgroundColor" Value="#4a707a" /> <Setter TargetName="TargetLabel1" Property="Label.TextColor" Value="#94b0b7" /> <Setter TargetName="TargetLabel1" Property="Label.Text" Value="Blue" /> </VisualState.Setters> </VisualState> </VisualStateGroup> </VisualStateManager.VisualStateGroups> Remove UIWebView To make sure the UIWebView control renderer is linked out even when it's not being directly used, and to avoid warnings from Apple during the review process, add this flag to your iOS projects mtouch arguments: --optimize=experimental-xforms-product-type Note that this also requires a release of Xamarin.iOS that'll come after mid-January via a service release to Visual Studio 2019 and Visual Studio 2019 for Mac. What's New in this Release Roadmap "Custom/Embedded fonts" ( #6013 ) Github #4924 - "[F100] Add "Target" support to VisualStateManager" ( #5034 ) ( #8144 ) F100s "[iOS] Add UpdateMode platform-specific to DatePicker and TimePicker" ( #8048 ) Github #2235 - "Improved image organization" ( #3263 ) ( #3420 ) Github #3228 - "Feature Request - Default Search Directory for UWP Icons (Platform Specific)" ( #3263 ) ( #3420 ) Github #5177 - "[Enhancement] Change NavigationPage back button color on Android" ( #7365 ) Github #7135 - "[Enhancement] Add platform specific property to set the iOS UITabBar Translucent property to false" ( #7315 ) CollectionView "[Android] Fix some issues in UITests" ( #8764 ) "[platform] improve perf of PropertyChangedEventArgsExtensions" ( #9084 ) "[UWP] Implement CurrentItem on CarouselView" ( #7590 ) "The great Androidx IF Def'ing of 2019" ( #8898 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #7323 - "[Xamarin.iOS] Deprecated API Usage UIWebView" ( #8001 ) Github #8198 - "[Bug] ScrollView at CollectionView at RefreshView always leads to Pull-To-Refresh" ( #8224 ) Github #8345 - "[Bug] CollectionView ItemSpacing does not affect the Item spacing on iOS" ( #8872 ) Github #9159 - "[Bug] CarouselView IsBounceEnabled=False has no effect on Android" ( #9160 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Shell "[UWP] Enables usage of font image source for bottom bar tabs" ( #8354 ) "Shell Modal Behavior" ( #8790 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #5108 - "Frame with a shadow on iOS adds a shadow to the contents" ( #7518 ) Github #6384 - "[Bug] [iOS] content page in tabbed page not showing inside shell tab" ( #7532 ) Github #7181 - "[Bug] Cannot update ToolbarItem text and icon" ( #8254 ) Github #7230 - "[Enhancement] Shell allow dynamic load FlyoutItem!" ( #9023 ) Github #7396 - "[Bug] Shell: Setting Shell.BackgroundColor overrides all colors of TabBar" ( #7962 ) Github #7416 - "[Bug] Crash In ShellSectionRootHeader with scrollable top tabs" ( #7884 ) Github #8211 - "[Bug] Shell throws NullRef if improperly configured" ( #8250 ) Visual "Apply cecil fixes to make packages 2017 compatible" ( #9145 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #4606 - "[Android] ImageButton on android is not clipping view to corner radius" ( #7723 ) Github #8633 - "[Bug] NuGet version conflict between Xamarin.Froms.Maps and Microsoft.AppCenter.Push" ( #7660 ) Other Enhancements "[macOS] Add character spacing to button and label" ( #8206 ) "[macOS] Implement slider min/max/thumb color" ( #8098 ) "[Tizen] Supports Custom/Embedded and System fonts" ( #9138 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) "[WPF] ListView.Scrolled event implemented" ( #8197 ) "[WPF] Frame: Add shadow and padding" ( #7964 ) "[Xaml/XamlC] Accept prefixed property names of markup extensions" ( #5186 ) "[XamlC] Support variance" ( #8535 ) "WPF Implement editor placeholder" ( #8504 ) Github #3149 - "Master behavior of Popover should be allowed on MacOS desktop" ( #8312 ) Github #4691 - "[Enhancement] SecurityException from Forms.Maps with explicit target SDK" ( #7282 ) Github #5680 - "[Enhancement] Add method to force value coercion" ( #8097 ) Github #5830 - "[Enhancement] EntryCellTableViewCell should be public" ( #8286 ) Github #7540 - "[Enhancement] Include the name of the duplicate element for INameScope.RegisterName" ( #8702 ) Github #7667 - "Make SetupLayer on FrameRenderer virtual" ( #7871 ) Github #8346 - "[Enhancement] Pre-define DisplayPromptAsync" ( #8362 ) Features in Preview SwipeView "[Android, iOS] Improve the swipe threshold used in Execute Mode" ( #9217 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #8781 - "[Bug][iOS] SwipeViewItem rendering issue on iOS" ( #8828 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #8782 - "[Bug][iOS][Android] SwipeViewItems cut off on one or more sides" ( #8824 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #8973 - "[Bug] SwipeView - no animation when revealing CollectionView items " ( #8987 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) CarouselView "[platform] improve perf of PropertyChangedEventArgsExtensions" ( #9084 ) "[UWP] Implement CurrentItem on CarouselView" ( #7590 ) "The great Androidx IF Def'ing of 2019" ( #8898 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Github #7323 - "[Xamarin.iOS] Deprecated API Usage UIWebView" ( #8001 ) Github #8198 - "[Bug] ScrollView at CollectionView at RefreshView always leads to Pull-To-Refresh" ( #8224 ) Github #9159 - "[Bug] CarouselView IsBounceEnabled=False has no effect on Android" ( #9160 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) UWP Shell "[UWP] Enables usage of font image source for bottom bar tabs" ( #8354 ) Github #7230 - "[Enhancement] Shell allow dynamic load FlyoutItem!" ( #9023 ) Github #8211 - "[Bug] Shell throws NullRef if improperly configured" ( #8250 ) DarkMode Github #8294 - "[Bug] UIStatusBarStyle does not appear to change when device is in dark mode" ( #8791 ) (added in 4.5.0.187-pre2 (4.5.0 Pre Release 2)) Release History Wednesday, January 22, 2020 - Xamarin.Forms 4.5.0.187-pre2 (4.5.0 Pre Release 2) Monday, January 13, 2020 - Xamarin.Forms 4.5.0.142-pre1 (4.5.0 Pre Release 1) Wednesday, January 22, 2020 - Xamarin.Forms 4.5.0.187-pre2 (4.5.0 Pre Release 2) Issues Fixed Github #2172 - "Height of Entry with data binding incorrect on UWP when Entry in ScrollView in Grid" ( #8214 ) Github #2678 - "StyleSheets - Updating StyleClass at runtime has no effect" ( #9157 ) Github #5168 - "[Core] Incorrect increments in Stepper" ( #7383 ) Github #5596 - "[iOS] Previous page's toolbar item being grayed out when canceling swipe to previous page then navigating back." ( #8454 ) Github #5711 - "Layout issue with Entry" ( #8214 ) Github #7862 - "[Bug] Live Unit Testing Fails Build" ( #7925 ) Github #7992 - "Datepicker is not opened when we call Datepicker.Focus() in UWP" ( #8056 ) Github #8294 - "[Bug] UIStatusBarStyle does not appear to change when device is in dark mode" ( #8791 ) Github #8781 - "[Bug][iOS] SwipeViewItem rendering issue on iOS" ( #8828 ) Github #8782 - "[Bug][iOS][Android] SwipeViewItems cut off on one or more sides" ( #8824 ) Github #8973 - "[Bug] SwipeView - no animation when revealing CollectionView items " ( #8987 ) Github #9159 - "[Bug] CarouselView IsBounceEnabled=False has no effect on Android" ( #9160 ) Additional fixes included in this release "[Android, iOS] Improve the swipe threshold used in Execute Mode" ( #9217 ) "[android/ios] improve perf when not using Application.Properties" ( #8887 ) "[android] remove the Anticipator for 4.5.0 and master" ( #9226 ) "[Core] performance improvements around bindings" ( #9114 ) "Apply cecil fixes to make packages 2017 compatible" ( #9145 ) "The great Androidx IF Def'ing of 2019" ( #8898 ) Monday, January 13, 2020 - Xamarin.Forms 4.5.0.142-pre1 (4.5.0 Pre Release 1) Issues Fixed Github #2136 / Bugzilla 45723 - "Entry / Editor and a Button. Tapping the button dismisses the keyboard" ( #8740 ) Github #3332 - "[Android] Memory leak in MasterDetailPage" ( #8745 ) Github #3742 - "Memory leak in the Navigation Page on Android" ( #8745 ) Github #3798 - "[Android] SeparatorColor of ListView is NOT updated dynamically" ( #8085 ) Github #3959 - "[UWP] ListView GroupHeaderTemplate Has minimum height" ( #8010 ) Github #4606 - "[Android] ImageButton on android is not clipping view to corner radius" ( #7723 ) Github #4744 - "forms in UWP show empty button for DisplayActionSheet" ( #8445 ) Github #4854 - "[macOS] Visual glitch when exiting the full screen with ScrollViewer" ( #8086 ) Github #4880 - "Text not shown as it should Xamarin.Forms.GTK" ( #8473 ) Github #5108 - "Frame with a shadow on iOS adds a shadow to the contents" ( #7518 ) Github #5367 - "Crash assigning excessively long text to Editor with MaxLength property set" ( #8052 ) Github #5749 - "Disable horizontal scroll in the custom listview in android" ( #8105 ) Github #5910 - "[Bug] IsClippedToBounds doesn't update clip rectangle when maximizing WPF window" ( #8195 ) Github #6384 - "[Bug] [iOS] content page in tabbed page not showing inside shell tab" ( #7532 ) Github #6556 - "[Bug] Button.CornerRadius doesn't work on WPF" ( #7895 ) Github #6693 - "[Bug] [WPF] ViewRenderer does not work properly with FrameworkElement derived native controls " ( #8357 ) Github #6905 - "[Bug] XAML parser cannot parse nested markup extension as positional argument" ( #8980 ) Github #6996 - "[Bug] Color of FontImageSource dynamic resource is useless" ( #8063 ) Github #7181 - "[Bug] Cannot update ToolbarItem text and icon" ( #8254 ) Github #7323 - "[Xamarin.iOS] Deprecated API Usage UIWebView" ( #8001 ) Github #7396 - "[Bug] Shell: Setting Shell.BackgroundColor overrides all colors of TabBar" ( #7962 ) Github #7400 - "[Bug] [Android] MainPage not changing in OnResume" ( #7477 ) Github #7416 - "[Bug] Crash In ShellSectionRootHeader with scrollable top tabs" ( #7884 ) Github #7709 - "[Bug] On android, not showing keyboard when changing placeholder in entry focused event" ( #7984 ) Github #7772 - "[Bug] Device.Idiom reports TargetIdiom.Phone for Amazon Fire TV Stick 4K" ( #7933 ) Github #7995 - "[Bug] WPF ListViewRenderer fails on item tapped with empty item source" ( #8223 ) Github #8087 - "[XAMARIN-FORMS-WPF] View doesn't render when set IsClippedToBounds to true" ( #8195 ) Github #8156 - "[Bug] [iOS] Label with HTML does not replace Umlaut characters properly" ( #8265 ) Github #8198 - "[Bug] ScrollView at CollectionView at RefreshView always leads to Pull-To-Refresh" ( #8224 ) Github #8211 - "[Bug] Shell throws NullRef if improperly configured" ( #8250 ) Github #8278 - "[Bug] StackOverflowException in UWP ListViewRenderer" ( #8299 ) Github #8345 - "[Bug] CollectionView ItemSpacing does not affect the Item spacing on iOS" ( #8872 ) Github #8469 - "[Bug] FontImageSourse doesn't work on macOS" ( #8590 ) Github #8593 - "[Bug] FontImageSourse doesn't work on GTK" ( #8627 ) Github #8633 - "[Bug] NuGet version conflict between Xamarin.Froms.Maps and Microsoft.AppCenter.Push" ( #7660 ) Github #9070 - "[Bug] UITabBar.Appearance.SelectedImageTintColor not working in Xamarin Forms project" ( #9082 ) Additional fixes included in this release "[Android] Fix some issues in UITests" ( #8764 ) "[Android] Fix some views dispose" ( #8703 ) "[Android] ListViewRenderer - Better dispose" ( #8705 ) "[Android] MasterDetailPageRenderer - Add guard and add missing unsubscribe" ( #8704 ) "[iOS] Reduce casting and repeat math during BoxView drawing" ( #9008 ) "[platform] improve perf of PropertyChangedEventArgsExtensions" ( #9084 ) "[previewer] removed empty ItemsSource attribute from toolbox snippets" ( #8379 ) "[REVERTED] Return all visual elements needed" ( #8100 ) "[Xaml] Throw XamlParseException in MarkupExpressionParser.GetNextPiece" ( #8447 ) "[XamlC] Dispose assembly resolver constructed by XamlCTask" ( #8397 ) "Fix cross-thread exception when finalizing ButtonRenderer" ( #9010 ) "Fix reflection call on UWP" ( #8636 ) "Stop Frame shadow from blocking user input on iOS" ( #8991 ) "Stop the linker from killing off the Deserializer" ( #8962 ) "Use correct reference frame for gesture origin recognition" ( #6615 ) "WPF GTK Set flags" ( #8446 ) Known Issues Github #9190 - "[Bug] Embedded Fonts Not Recognized" Breaking Changes Github #4606 - "[Android] ImageButton on android is not clipping view to corner radius" ( #7723 ) Namespace Xamarin.Forms Type Changed: Xamarin.Forms.IImageElement Removed method: public virtual void OnImageSourcesSourceChanged (object sender, System.EventArgs e); Type Changed: Xamarin.Forms.Shell Modified methods: public System.Threading.Tasks.Task GoToAsync (ShellNavigationState state, bool animate--- = true---) Namespace Xamarin.Forms.Internals Type Changed: Xamarin.Forms.Internals.Profile Removed methods: public static void FrameBegin (string name, string id, int line); public static void FrameEnd (); Namespace Xamarin.Forms.Platform.Android Type Changed: Xamarin.Forms.Platform.Android.PageExtensions Removed method: [Obsolete ("ContentPage.CreateFragment() is obsolete as of version 3.2. Please use ContentPage.CreateSupportFragment() instead.")] public static Android.App.Fragment CreateFragment (this Xamarin.Forms.ContentPage view, Android.Content.Context context); Type Changed: Xamarin.Forms.Platform.Android.Resource Type Changed: Xamarin.Forms.Platform.Android.Resource.Drawable Removed fields: public static int avd_hide_password_1; public static int avd_hide_password_2; public static int avd_hide_password_3; public static int avd_show_password_1; public static int avd_show_password_2; public static int avd_show_password_3; Deprecations Github #8346 - "[Enhancement] Pre-define DisplayPromptAsync" ( #8362 ) API Changes See all API Changes here . "Custom/Embedded fonts" ( #6013 ) Github #7135 - "[Enhancement] Add platform specific property to set the iOS UITabBar Translucent property to false" ( #7315 ) Github #7667 - "Make SetupLayer on FrameRenderer virtual" ( #7871 ) Blogs Xamarin Blogs Thank you Thank you to our community for helping to make Xamarin.Forms even better! This release, we received amazing contributions from these individuals. Give them a big round of applause! Author Commit PR Akihiko Odaki ( @akihikodaki ) Add a missing '}' in Xamarin.Forms.Xaml.UnitTests/Issues/Bz24485.xaml (#8448) #8448 Akihiko Odaki ( @akihikodaki ) [Xaml] Throw XamlParseException in MarkupExpressionParser.GetNextPiece (#8447) #8447 Akihiko Odaki ( @akihikodaki ) [XamlC] Support variance (#8535) #8535 Akihiko Odaki ( @akihikodaki ) [Xaml[C]] Accept prefixed property names of markup extensions (#5186) #5186 Akihiko Odaki ( @akihikodaki ) [XamlC] Dispose assembly resolver constructed by XamlCTask (#8397) #8397 Akihiko Odaki ( @akihikodaki ) [Xaml] Create value from positional argument text of markup extension (#8980) #8980 Alexander Olshansky ( @NordAlex ) Fix 7709 - Fix showing keyboard when changing placeholder in entry focused event (#7984) #7984 Andrei ( @AndreiMisiukevich ) [Enhancement] Add platform specific property to handle iOS UITabBar Translucent property (#7315) #7315 beeradmoore ( @beeradmoore ) UIStatusBarStyle now changes correctly when a device is in dark mode (#8791) #8791 Bob Weinand ( @bwoebi ) Use correct reference frame for gesture origin recognition (#6615) #6615 Brian Macomber ( @bmacombe ) Typo Fix and change to nameof (#8942) fixes #8935 #8942 Brian Macomber ( @bmacombe ) Fixes 7992 Changes UWP DatePicker to show the picker flyout on DatePickerFocus() (#8056) #8056 Brian Macomber ( @bmacombe ) [UWP] Attempt to resolve entry on UWP not correctly calculating the correct height when in a scroll view (#8214) #8214 Chase Marsh ( @ChaseMarsh ) Fix 6693 - [Bug] [WPF] ViewRenderer does not work properly with FrameworkElement derived native controls (#8357) #8357 CleanCodeDeveloper ( @CleanCodeDeveloper ) [UWP] Enables usage of font image source for bottom bar tabs (#8354) #8354 Clifford Agius ( @CliffAgius ) Fixed the rounding issue when the stepper value is incremented. (#7383) #7383 David Eisler ( @EislerDavid ) Add null check in UpdateFlowDirection (#9148) #9148 Durgesh Khandal ( @techduggu ) Fixed 5680 - Added method to force value coercion (#8097) #8097 Durgesh Khandal ( @techduggu ) Fixed - 5830 - Updated access modifier for EntryCellTableViewCell (#8286) fixes #5830 #8286 Durgesh Khandal ( @techduggu ) Fixed 5749 - Issue with disabling horizontal scroll on Android (#8105) #8105 Durgesh Khandal ( @techduggu ) Fix #3798 - [Android] SeparatorColor of ListView is NOT updated dynamically (#8085) fixes #3798 #8085 Durgesh Khandal ( @techduggu ) Fixed 8211 - Handled NullRef in Shell if incorrectly-configured (#8250) #8250 Felipe Baltazar ( @felipebaltazar ) Fix Bug 7396 - Shell: Setting Shell.BackgroundColor overrides all colors of TabBar (#7962) #7962 Felipe Baltazar ( @felipebaltazar ) Fixe issue 5367 - Crash assigning excessively long text to Editor with MaxLength property set (#8052) fixes #5367 #8052 Felipe Baltazar ( @felipebaltazar ) Fix 7181 - [Bug] Cannot update ToolbarItem text and icon (#8254) fixes #7181 #8254 Glenn Versweyveld ( @Depechie ) Let UICollectionViewCell handle state itself (#7884) #7884 Glenn Versweyveld ( @Depechie ) Add ListViewHeaderItemMinHeight override in UWP resources.xaml (#8010) #8010 Glenn Versweyveld ( @Depechie ) Check for ValueType items to perform equals (#8299) #8299 Glenn Versweyveld ( @Depechie ) Return all visual elements needed (#8100) fixes #7027 #8100 Joe Manke ( @jcmanke ) [Android Maps] Check for location permissions when IsShowingUser=true (#7282) fixes #4691 #7282 Joe Manke ( @jcmanke ) [iOS] Add UpdateMode platform-specific to DatePicker and TimePicker (#8048) #8048 Johann Weiher ( @Suplanus ) macOS: Fixed IsPresented PopOver (#8312) #8312 Kangho Hur ( @rookiejava ) [Tizen] Supports Custom/Embedded and System fonts (#9138) #9138 Kevin Petit ( @kvpt ) Call the application OnResume, on Android Resume instead of Restart. (#7477) Fixes #7400 #7477 Kevin Petit ( @kvpt ) [Android] Better ListViewRenderer dispose (#8705) #8705 Kevin Petit ( @kvpt ) [Android] Add guard and add missing unsubscribe on MasterDetailPageRenderer (#8704) #8704 Kevin Petit ( @kvpt ) [Android] Fix various memory leaks (#8745) fixes #3332 fixes #3742 #8745 Kevin Petit ( @kvpt ) [Android] Fix some issues in UITests (#8764) #8764 Kevin Petit ( @kvpt ) [Android] Fix view dispose (#8703) #8703 Konrad Müller ( @krdmllr ) [macOS] Implement slider min/max/thumb color (#8098) #8098 Konrad Müller ( @krdmllr ) [WPF] Frame: Add shadow and padding (#7964) #7964 Leo Mehlig ( @leoMehlig ) Fixes Bug with TabbedPage pushed onto Shell (#7532) fixes #6384 #7532 MagicAndre1981 ( @MagicAndre1981 ) possible fix for Issue 7772 (#7933) #7933 melimion ( @melimion ) Scrolled event implemented (#8197) #8197 melimion ( @melimion ) Fix Button.CornerRadius doesn't work on WPF (#7895) #7895 melimion ( @melimion ) WPF Implement editor placeholder (#8504) #8504 melimion ( @melimion ) macOS toolbar improvements (#8146) #8146 Mohamed CHOUCHANE ( @mohachouch ) [WPF] View doesn't render when set IsClippedToBounds to true (#8195) #8195 Oliver Brown ( @GalaxiaGuy ) [iOS] [macOS] Fix HTML string encoding (#8265) #8265 Oliver Brown ( @GalaxiaGuy ) [macOS] Add character spacing to button and label (#8206) #8206 Pieter Nijs ( @PieEatingNinjas ) iOS: Frame with HasShadow set to true and BackgroundColor alpha < 1 casts shadow on all child views (#7518) #7518 Ravinder Jangra ( @ravinderjangra ) Fix back icon color for the navigation page (#7365) fixes #5177 #7365 Sanya Andreichuk ( @sanyandreichuk ) Force a redraw for right toolbar items. (#8454) #8454 Sławomir Kulików ( @slakul ) [macOS] Visual glitch when exiting the full screen with ScrollViewer (#8086) fixes #4854 #8086 Todd ( @thenderson21 ) Fix to double escaping. (#8473) #8473 Tushar Koshti ( @07101994 ) [Core] Removed null values from the DisplayActionSheet (#8445) fixes #4744 #8445 VladislavAntonyuk ( @VladislavAntonyuk ) [Bug] WPF ListViewRenderer fails on item tapped with empty item source #7995 (#8223) #8223 VladislavAntonyuk ( @VladislavAntonyuk ) [Bug] FontImageSourse doesn't work on macOS (#8590) fixes #8469 #8590 VladislavAntonyuk ( @VladislavAntonyuk ) WPF GTK Set flags (#8446) #8446 VladislavAntonyuk ( @VladislavAntonyuk ) [Bug] FontImageSourse doesn't work on GTK fixes #8593 (#8627) #8627 Youssef Victor ( @Youssef1313 ) Remove private modifier (#8631) #8631 Feedback welcome Your feedback is important to us. If there are any problems with this release, check the Xamarin.Forms Forums and GitHub for existing issues. Report new issues and suggestions on GitHub . Open Source Xamarin.Forms 4.5.0 is based on the open-source Xamarin.Forms repository: Xamarin.Forms Additional resources Last updated on 2020-01-22 In this article en-us Your Privacy Choices Theme Light Dark High contrast AI Disclaimer Previous Versions Blog Contribute Privacy Terms of Use Trademarks © Microsoft 2026 | 2026-01-13T08:48:37 |
https://blog.devcycle.com/devcycle-product-updates-q1-2025/ | DevCycle Product Updates (Q1 2025) Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Product Updates DevCycle Product Updates (Q1 2025) DevCycle May 12, 2025 • 2 min read Find out what's new at DevCycle, including stale flag alerts, project level RBAC and enhancements to targeting. Welcome to your Q1 2025 DevCycle product update! We’ve rolled out a ton of exciting improvements in the past few months — from powerful new lifecycle tools to better access management and great UX updates. Here’s what’s new. 🔔 Stale Feature Notifications DevCycle now automatically identifies Features that may be stale based on usage and activity, surfacing them for review so you can clean them up with confidence. You’ll see in-app alerts and receive scheduled email reports, along with controls to snooze notifications or disable checks if needed. Whether it’s a flag that hasn’t been updated in weeks or one silently serving 100% of traffic, you’ll know exactly when to act. 🔐 Role-Based Access Control (RBAC) We’ve introduced project-scoped Role-Based Access Control to help teams manage access across complex orgs. With RBAC, you can: Assign roles to specific projects within your DevCycle org Prevent users from accessing projects they aren’t assigned to Map roles using your access manager and SCIM group provisioning This is especially helpful for orgs using providers like Azure AD or Okta, keeping your identity management centralized without sacrificing flexibility. 📋 Copy Targeting Rules & Create Audiences Setting up consistent targeting logic is now easier than ever. You can now copy Targeting Rules across environments — perfect for testing in staging and promoting to production without worrying about introducing new errors. Plus, you can instantly convert a Targeting Rule’s filters into a reusable Audience that can be applied to any Feature. ⚒️ Dashboard & UX Improvements We’ve made several quality-of-life enhancements to streamline your experience in the DevCycle dashboard: Full-width dashboard pages — More space to work with across all views Sticky header in Variable/Variation tables — Keep context as you scroll Improved JSON formatting — Easier-to-read tooltips for Variable values Visible default targeting rule — Clarifies behavior for unmatched users 🧩 OpenFeature SDK Updates We’ve expanded our OpenFeature support with new providers for Angular, NestJS, and Ruby — along with updates across all languages to meet the latest spec. Whether you're modernizing your frontend or scripting in Ruby, these updates ensure smoother integration and better long-term compatibility. That’s everything for Q1! We hope these updates make it even easier to build, test, and ship great experiences. Let us know what you’d like to see next on our public roadmap — we’re always listening. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/openfeature-vs-proprietary-systems/ | OpenFeature vs. Proprietary Systems Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature vs. Proprietary Systems Cobi Druxerman Jun 19, 2025 • 3 min read Breaking Down Vendor Lock-In Risks and Future-Proofing Your Stack Introduction: The Double-Edged Sword of Feature Flagging Feature flagging has become a cornerstone of agile software development, enabling trunk-based development, streamlined A/B testing, improved incident management, and safe, gradual feature releases. Its capacity to deliver value to engineering teams is undeniable. However, this flexibility doesn't come without potential pitfalls. At first glance, integrating a proprietary feature flagging system into your technology stack seems like a logical choice. It can offer immediate convenience, robust feature sets, and polished user experiences. Yet, over time, these initial benefits can evolve into constraints. Your organization could face significant expenses and technical challenges should your chosen provider no longer align with your evolving business or technical requirements. This makes the choice between proprietary convenience and open-standard flexibility not just technical, but strategic. Enter OpenFeature , a solution specifically designed to alleviate these concerns. By standardizing feature flagging functionality, OpenFeature offers crucial flexibility, empowering your team to adapt without risk of disruption. Platforms like DevCycle provide an ideal combination: robust platform capabilities seamlessly integrated with OpenFeature standards. Understanding Vendor Lock-In with Feature Flags Vendor lock-in occurs when a company's infrastructure becomes deeply tied to a specific vendor, making it difficult, costly, and risky to switch providers. The stakes become particularly high with feature flags due to several critical factors: Deep SDK Integration : Vendor-specific SDKs permeate applications, often requiring widespread refactoring to remove or replace. Complex Configuration : Proprietary configurations uniquely tailored to each vendor, complicating migrations. Historical Data Dependencies : Valuable historical targeting rules and flag states locked within proprietary storage formats. Workflow and Training : Development teams become reliant on specific user interfaces and workflows, making transitions disruptive. The consequences of vendor lock-in include escalating costs, diminished flexibility, and substantial migration complexities. The Reality of Proprietary Feature Flagging Systems Initially attractive, proprietary feature flagging solutions often promise a comprehensive, integrated experience. Developers appreciate these systems for their polished interfaces, out-of-the-box features, and ease of integration. Yet these benefits mask underlying challenges: Onboarding Complexity : Vendor-specific SDKs and APIs necessitate dedicated training. Codebase Refactoring : Switching vendors demands extensive rewrites across the technology stack. Migration Hurdles : Proprietary data formats complicate or prohibit data migration. Vendor-Imposed Limitations : Organizations become restricted by vendor pricing structures, support capabilities, and roadmap priorities. Ultimately, proprietary solutions restrict organizational agility and adaptability, leading to operational rigidity. OpenFeature: Changing the Game with Standardization OpenFeature is a vendor-neutral standard that redefines application interactions with feature flagging systems. By creating a universal API standard, OpenFeature fundamentally shifts operational dynamics, offering: Unified API Standardization : A consistent and universal API across multiple vendors to simplify development and maintenance. Vendor Flexibility (Providers) : Providers translate standardized OpenFeature API calls into their backend-specific implementations. Decoupled Application Logic : Separating application logic from vendor-specific details keeps your system adaptable and portable. The tangible benefits include significantly reduced vendor lock-in, streamlined portability across providers, simplified transitions, and future-proofing. Comparing OpenFeature and Proprietary Systems Feature Proprietary Systems OpenFeature Ecosystem API & SDKs Vendor-specific, unique to each platform Standardized across compliant providers Vendor Switching Cost High: extensive rewrites/migration efforts Low: minimal configuration changes Code Portability Low: tight coupling to specific SDKs High: vendor-agnostic logic Risk of Obsolescence Dependent on vendor stability Low: community-driven Data Migration Complex: proprietary formats Simplified-standardized semantics Innovation Pace Vendor-dependent Accelerated by community contributions Learning Curve High: unique learning per vendor Low: consistent API across providers Ecosystem Integration Limited by vendor capabilities Broad-standardized integrations Choice & Flexibility Vendor-specific options only Wide selection among providers DevCycle: A Robust, Future-Proof Solution DevCycle exemplifies a balanced, future-proof approach, aligning perfectly with the OpenFeature standard. Teams choosing DevCycle benefit from: Advanced Capabilities : Real-time updates, precise targeting, extensive experimentation capabilities. Seamless Integration : Straightforward integration via OpenFeature’s standardized API. Reduced Migration Effort : Easier migrations if future needs necessitate vendor changes. Commitment to Openness : Dedicated to flexibility, adaptability, and vendor-neutral interoperability. With DevCycle, you get powerful features while retaining flexibility, letting you achieve "the best of both worlds." Conclusion: Strategic Choices for Long-Term Success Selecting the right feature flagging system is fundamentally strategic. OpenFeature significantly reduces vendor lock-in risks, offering flexibility and adaptability for technological evolution. By adopting DevCycle with robust OpenFeature integration, your team can leverage advanced capabilities immediately while ensuring long-term agility. Embrace OpenFeature alongside DevCycle to protect your investments and secure your technology stack’s resilience. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/devcycle-is-now-soc-2-type-ii-compliant/ | DevCycle is Now SOC 2 Type II Compliant Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home DevCycle is Now SOC 2 Type II Compliant Kate MacFarlane Jun 27, 2025 • 1 min read DevCycle is proud to announce we are now SOC 2 Type II compliant. We're excited to announce that as of December 2024, DevCycle has achieved SOC 2 Type II compliance! SOC 2 Type II compliance represents a critical milestone in our commitment to security and privacy, demonstrating our rigorous adherence to the highest standards of trust and reliability. What is SOC 2 Type II Compliance? SOC 2 Type II is an auditing procedure established by the American Institute of Certified Public Accountants (AICPA), designed specifically for service providers that handle customer data. Unlike SOC 2 Type I, which evaluates controls at a single point in time, SOC 2 Type II assesses how effectively an organization implements and operates its controls over an extended audit period. This certification validates that DevCycle's systems and processes securely manage customer data to protect privacy and confidentiality. It encompasses critical trust service principles, including: Security – Protecting systems against unauthorized access Availability – Ensuring systems are operational and accessible Processing Integrity – Guaranteeing system processing is accurate and timely Confidentiality – Protecting confidential information throughout its lifecycle Privacy – Ensuring the secure handling of personal data Why Does SOC 2 Type II Compliance Matter? Achieving SOC 2 Type II compliance means DevCycle has been independently audited and verified to have robust and reliable security practices. It reflects our dedication to safeguarding customer information and providing transparency into our processes. This compliance assures our customers that your sensitive data is handled with the utmost care, aligning DevCycle with industry-leading security standards. Our Commitment Going Forward At DevCycle, security and privacy aren't just compliance checkboxes—they are fundamental to our operations and product philosophy. Achieving SOC 2 Type II compliance is part of our ongoing commitment to consistently enhancing security measures and ensuring our customers' trust. We remain dedicated to continually strengthening our systems and practices to uphold these standards, providing a secure and trustworthy platform for all our users. If you'd like more details about DevCycle's security practices, visit devcycle.com/security . For questions or additional security or compliance requests, submit a feature request on our roadmap or email us at product@devcycle.com . Stay secure, The DevCycle Team Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/devcycle-mcp-from-hackathon-to-production/ | From Hackathon to Production: What It Took to Ship Our DevCycle MCP Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Product Updates From Hackathon to Production: What It Took to Ship Our DevCycle MCP Jonathan Norris Sep 1, 2025 • 8 min read When we started building our MCP server , it began as a simple hackathon project: take our existing CLI interface, which already has authentication and most of our API calls, and adapt it to work as an MCP server. As a hackathon project, it turned out to be a pretty compelling demo with some strong use cases. With just the hackathon version, agents could create new feature flags, investigate incidents, clean up stale flags, and help with QA, all with natural language. We thought the demo was cool, but it was rough around the edges and failed regularly; we knew it would take quite a bit of iteration to make it production-ready. One-shot vibe coding a new feature with the DevCycle MCP Key Takeaways and Learnings To get the MCP server from hackathon "working" code to a shippable product took a lot of learning through trial and error. Below, are the key learnings from that process. Create Clear Input Schemas Good input schemas that properly define your API are critical. The input schemas (and descriptions) are your AI agent's primary context when deciding which tool to call and the data to call the tool with. AI agents can infer reasonably well from the input schema, but in certain places, .describe() statements on your schema parameters will help push the AI agent in the right direction. For example, if you have a search field that can accept a generic string input, adding a search.describe('Search term to filter features by "name" or "key"') , will help steer the AI Agent to only use name or key values in the search. Without a good input schema, we found that AI agents would regularly try to use the wrong tool, causing errors or even taking the agents down unintended paths. Descriptive Errors Make up for Most Sins Bad error handling can break everything. The AI agent will fail as soon as it runs into an error without a very descriptive error response. Most of the time, it will just start hallucinating new data to fix the error and get into circles, chasing its own tail. Conversely though, good, descriptive error responses can solve for a lot of other problems with your MCP. If you provide detailed error responses from your APIs, that are helpful, the agent can generally one-shot fix issues in its chain of reasoning. We assumed that creating DevCycle Features through our MCP interface, due to the large and complex Features API , wouldn't be usable. We thought the AI agent would hallucinate its way through creating features, making illogical decisions. But we were surprised that with a detailed input schema + good descriptive error responses (such as the example below), AI agents could consistently get to the right result. Yes, the agent may need to iterate through an error or two for API rules that cannot be covered by the JSON schema, but they had an extremely high success rate generating features with complex targeting rules all through a natural language interaction with the MCP tool. { "errorType": "UNKNOWN_ERROR", "errorMessage": "Expected type of value for variable 'include-metadata' to be Boolean, but received String", "toolName": "create_feature", "suggestions": [], "timestamp": "2025-08-27T14:58:17.701Z" } Example of a simple, but good error that helps guide AI agents in the right direction Limit the Number of Tools Pruning your tool calls is essential; not every API function you have makes sense to be available as an MCP tool call, and every new MCP tool eats up more of your AI context window. We had to ask ourselves, do we think someone really wants/needs to be able to delete whole projects from an MCP tool call? Once we got past the initial excitement of giving agents the ability to do anything, we quickly realized actions like that were highly unlikely to be done via agents. Counter-intuitively to API best practices, larger tool call surfaces that can combine multiple API functions into a single MCP tool call are preferable. It reduces the number of tools your MCP needs to expose and likely reduces the amount of AI context you are using up to describe your MCP tools. Many AI Agent platforms restrict the number of MCP tools installed, or at least warn users if they are using too many, meaning that if you want your MCP actually to be used, you should minimize the number of tools your MCP server exposes. MCP OAuth is Easier with Cloudflare Workers Getting the authentication to work well for an MCP server is hard; as a new standard, figuring out how to properly authenticate with your existing systems can be challenging (should you use API Keys, JWT, OAuth???). We found that using Cloudflare Workers + Durable Objects to host the remote MCP server made the OAuth implementation mostly painless. We also found that managing the OAuth session state in a Durable Object for all of a user's requests is a good, scalable solution for us. The power of using durable objects is that it also lets you store other session state data. For example, we store which DevCycle project you are interfacing with for the MCP, and have tool calls that let you select between different projects in your organization. That means on all further tool calls, say to list features in a project, your AI agent doesn't need to keep track of what project you are querying for, your MCP session has already selected a project, and we have stored that state in the Cloudflare Durable Object to use for listing all the features. Remote MCP Servers Are Easier and Safer Remote MCP servers are easier and safer for users to install; you just need to set a URL, and you're up and running. If you are using OAuth for authentication, your users use a web-standard authentication API through which you can properly scope the permissions your MCP server has access to. { "mcpServers": { "DevCycle": { "url": "https://mcp.devcycle.com/mcp" } } } The somewhat common practice for local MCP servers of providing an npx -y some-mcp-script to install a local MCP server with full access to your computer's file system is rife with security concerns, compared to an HTTP / SSE-based remote MCP server, scoped using permissions and time-scoped OAuth tokens. Be Careful With Context Size and Output Schemas Output schemas can help provide more context to the AI when it chooses which tool call to make. However, the token cost of large output schemas is likely not worth the minimal benefit, when most of the output's context can be provided with a simple statement in the tool call's description. If you choose to set output schemas, keep them as a high-level description of the first layer of output parameters with short descriptions of the deeper parameters. The Real Value of MCP Tied to Developer Workflows To be honest, I was initially skeptical of the value of most MCPs, they never natively fit into my AI development workflows, I could get documentation by just pasting a link in my chat. But after using our new MCP for a while, it has become obvious that there is real value in an MCP server that directly interacts with your code development workflow, versus just providing information to an AI agent. The most popular MCP servers to date have mostly been informational interfaces to project management tools (think: Linear / Notion / Github), or documentation (Context7), and these MCPs certainly have their value, but the daily use cases as a primary interface feel limited. I believe that MCPs for tools that directly interface with your development workflow, like DevCycle for Feature Flagging or Sentry with error monitoring, can be integral to how you ship and deliver software. By building MCP tool calls that are directly involved in the code-writing process, when you ask your AI Agent to "wrap this new functionality in a DevCycle flag" as part of a regular every-day prompt to do a simple task you may have done manually in the past, your AI agent now not only has the context on how to implement that flag properly, it will automatically fetch the existing variable's type/default value/schema for that flag, or create a new variable and feature for you in DevCycle, and self-target you into that flag to initially test it locally. These types of workflows, extending the functionality of coding tasks you are already doing with your AI agent, quickly become a native interface you don't need to think about using. And more than that, while MCP may not be perfect, it can actually make for a better overall experience with our platform as a developer, where you can stay in code and context. Example Workflows Some of the example workflows and prompts we have discovered so far are: Quickly Creating a Feature in DevCycle for a New Variable in Code Create a new feature in DevCycle for the flag "new-flag" These feature creation prompts are great for quickly creating a feature in DevCycle and keeping you in the flow of your code editor. At the same time, you work on implementing your new feature, letting you set up a simple feature based on the flag in your code without needing to set anything up in the DevCycle dashboard. Self-Targeting Into a Feature for Local QA Self-target me into this devcycle feature flag By making it so easy to quickly target yourself into a newly created DevCycle feature flag, it again keeps you in the flow of developing your new feature in your code editor and makes one of the most useful tools in the DevCycle platform that much more accessible to developers' local development workflows. Promoting a Feature From Development to Staging Enable this devcycle feature in staging for all users This allows you to quickly promote an existing feature you have set up and have been testing in a lower environment, like a local or development environment, to a higher-level environment, like staging. Testing in Production for All Internal Users Enable this feature in production for all internal users with "@devcycle.com" emails Again, a common internal practice for us here at DevCycle is testing all new production features by targeting internal users. This can be done with a simple email filter or an existing saved audience. Identifying If an Error Is Related to a Feature Flag: Is this error we are seeing in prod controlled by a devcycle variable? If so, turn off the feature. When debugging errors, one of the first tools you should look to is what feature flags were recently deployed or enabled. With the DevCycle MCP, you can quickly ask if there are any changes across all of your feature flags that are related to a known stack trace or error in your code. Cleaning Up Stale Feature Flags: Cleanup all the features marked as stale by devcycle A recent feature we've built at DevCycle helps you identify features in your project that are stale (haven't been changed or evaluated in a while) and should be cleaned up in your code. Our MCP tool calls include data about whether we have marked the feature as stale, making it easy to use your AI agent to clean up these flags. This is an area where we think AI can be particularly helpful, given the common problem of letting stale flags build up in a codebase... Archiving DevCycle Features That Don’t Exist in Your Code Anymore. Review all devcycle features and list any that don't have any devcycle variables in this codebase to be archived Sometimes you start creating a feature flag but don't end up finishing the job. Maybe it was a POC or maybe you just got started creating a flag during a scoping meeting. AI has all of the context necessary to quickly and easily archive Features that never got used. Next Steps With DevCycle’s MCP Another investigation led us to develop AI prompts for instructing AI agents on how to install DevCycle and OpenFeature SDKs into applications and set up the first feature flags. In a future blog post, we'll detail how we're reimagining our product onboarding around this MCP installation flow with real-time feedback. As a team that has built SDK-based SaaS services for over a decade, this approach addresses two persistent challenges: getting customers to install and update SDKs and streamlining the onboarding process. Developing these MCP tools taught us a key lesson for creating effective AI agent-based workflows: prioritize integrations that enhance the daily activities of your platform. For us, that's clearly creating, managing and decommissioning feature flags. And so far, MCP is making it easier and safer to stay in flow and manage flags. Read more about the DevCycle MCP Server. About DevCycle DevCycle is the first OpenFeature‑native feature flag management platform - so you can ship faster without vendor lock‑in. The MCP server extends that developer‑first experience right into your AI tools. Try DevCycle Free Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/openfeature-multi-provider-enabling-new-feature-flagging-use-cases-video/ | OpenFeature Multi-Provider: Enabling New Feature Flagging Use-Cases (Video) Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature OpenFeature Multi-Provider: Enabling New Feature Flagging Use-Cases (Video) DevCycle May 29, 2025 • 1 min read What is OpenFeature and the Multi-Provider? What Are Some Use Cases? Watch DevCycle’s Co-Founder and CTO, Jonathan Norris, as he highlights the capabilities and unique use cases enabled by the OpenFeature Multi-Provider. Learn about OpenFeature, the Multi-Provider and about use cases such as combining multiple feature flag vendors under a single interface or how to utilize the Multi-Provider for feature flag provider migrations. DevCycle CTO Jonathan Norris speaking at OpenFeature Summit Europe Key Points What is OpenFeature and the Multi-Provider? What benefits do they offer? How OpenFeature benefits companies that use feature flags, want to migrate to a different provider, or need to integrate multiple feature flag solutions within the same application. Multi-provider strategies : The OpenFeature Multi-Provider supports several strategies to determine how flag values from different providers are used: first match, first successful, comparison and custom strategies. Hybrid environments: How teams can use different feature flag providers for various projects or systems within the same application. Gradual migrations: How the OpenFeature Multi-Provider supports migration from one feature flag provider to another while reducing risk and effort by avoiding flag duplication. Interoperability: How the OpenFeature Multi-Provider supports integrating internal solutions with external vendors for more flexible feature flag management. Production validation: Ensuring the consistency of flag values during feature flag provider migrations by comparing outputs in real-time. Chapters: What’s Covered in the Video? 0:00: Background on DevCycle and Relationship with OpenFeature 1:06: How OpenFeature Works 2:04: Introduction to OpenFeature Multi-Provider 2:42: OpenFeature Strategies 3:08: Setting up Multi-Provider 3:46: “First Match” OpenFeature Strategy and Use Cases 5:04: Use Case: Provider Migration 5:44: “First Successful” OpenFeature Strategy 6:05: Use Case: Local Fallback 6:30: “Comparison” OpenFeature Strategy 7:28: Use Case: Full Migrations, Comparing Execution Performance of Vendors and Ensuring Correct Flag Values in Production 8:18: Custom OpenFeature Strategies 9:27: Use Case: Combining Multiple Providers 10:32: Q&A Resources OpenFeature OpenFeature Ecosystem DevCycle OpenFeature SDKs More about OpenFeature Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/tag/openfeature/ | OpenFeature - DevCycle Blog Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature DevCycle is a proud supporter of the OpenFeature ecosystem and we are excited to share insights on this transformative approach to feature flagging. Stay tuned for content that explores the benefits, best practices, and our journey with OpenFeature OpenFeature Why is OpenFeature Support is Critical? Comparing Top OpenFeature Providers Feature flagging is essential for modern software development, enabling teams to test in production, manage releases incrementally, and mitigate risks, by separating code deploys from the release of features to users. As adoption grows, standardization via OpenFeature—an open specification for feature flags—becomes crucial to avoid vendor lock-in, simplify Jun 2, 2025 6 min read OpenFeature OpenFeature Multi-Provider: Enabling New Feature Flagging Use-Cases (Video) What is OpenFeature and the Multi-Provider? What Are Some Use Cases? Watch DevCycle’s Co-Founder and CTO, Jonathan Norris, as he highlights the capabilities and unique use cases enabled by the OpenFeature Multi-Provider. Learn about OpenFeature, the Multi-Provider and about use cases such as combining multiple feature flag vendors under May 29, 2025 1 min read OpenFeature OpenFeature Hackathon 2024 A few times a year at DevCycle, we hit pause on our usual work, push aside our roadmaps, and dive into a few days of rapid experimentation and collaboration. For our first hackathon of 2025, we opted for an OpenFeature theme —a chance to explore new ideas, test bold concepts, Mar 19, 2025 9 min read OpenFeature How Jackson Used DevCycle and OpenFeature to Achieve a Zero-Downtime Migration Today's DevCycle Spotlight features Jackson Kasi, a developer who won the OpenFeature Aficionado prize for our first ever DevCycle Feature Flag Challenge on Dev.to where we challenged developers to build a fun or creative project using DevCycle! Jackson won the OpenFeature Aficionado prize for the most innovative Mar 4, 2025 3 min read OpenFeature Open Standards in a Trade War: Why You'll Need an Escape Hatch When Politics Hits Your Stack Open Standards have never been more important. In a world with impending trade wars globally, it's likely that software will be taxed and restricted. Going forward it is going to be critical to be able to rip and replace software if the winds of geopolitics shift in the wrong direction. Feb 26, 2025 7 min read Guides and Tutorials Creating a Star Trek-Inspired GenAI Copilot Using Pieces and DevCycle In this post, we show you how DevCycle and Pieces for Developers make experimenting with AI as smooth as a warp-speed jump. Nov 11, 2024 Outside Voices OpenFeature Recipe for Change: Unlocking Feature Flag Flexibility in a Hyperapp with OpenFeature and the Multi-Provider Utility Are your feature flags as flexible as they could be? If they are hard-coded static configurations, the answer is likely no. In this guide, we'll explore how OpenFeature can unlock the full potential of feature flags using a fun (although maybe impractical) example—a Recipe Manager app where Aug 6, 2024 9 min read OpenFeature Featured Migrating from In-House Feature Flagging with OpenFeature Discover how the OpenFeature standard and new Multi-Provider utility can help you migrate away from your in-house flagging solution. Jul 2, 2024 4 min read Outside Voices Introducing the OpenFeature Multi-Provider We are excited to announce the release of the OpenFeature “Multi-Provider” for JavaScript and NodeJS. This new provider allows developers to access multiple OpenFeature providers through a unified interface, with customizable strategies that reconcile inconsistencies between providers. The Multi-Provider supports use cases including provider migrations and long-term support for multiple Jun 20, 2024 Outside Voices OpenFeature Planting a (Feature) Flag at the Summit: Extending AlpineJS with OpenFeature & DevCycle Learn how to build a simple plugin that adds OpenFeature compliant feature flagging functionality to AlpineJS using the DevCycle Javascript SDK. May 16, 2024 20 min read OpenFeature Serving Up Feature Flags on an Airtable with OpenFeature In this blog post, I'll show you how to build a simple AirTable Provider for OpenFeature so you can upgrade from that quick snack to a more "filling" feature flag system, all while securing your seat at the DevCycle Buffet. May 1, 2024 11 min read OpenFeature DevCycle Co-founder Jonathan Norris Elected to OpenFeature Governance Committee as DevCycle Achieves Comprehensive OpenFeature SDK Support At Kubecon Paris 2024, DevCycle announces that Co-founder and CTO, Jonathan Norris, has been elected to the OpenFeature Governance Committee as DevCycle achieves comprehensive OpenFeature SDK support. This appointment solidifies DevCycle’s deep commitment to the OpenFeature project. Mar 20, 2024 1 min read OpenFeature How OpenFeature Was the Key to Escaping Feature Flag Vendor Lock-in: A Vue.js Story Discover how we effortlessly transitioned a VueJS project to a new feature flag Provider in just a few lines of code thanks to OpenFeature. Mar 5, 2024 5 min read OpenFeature Powering Up PHP Feature Flags with OpenFeature See just how easy it is to break free from vendor lock-in with OpenFeature in our latest blog post, where we detail the straightforward process of tweaking our PHP example app to embrace the OpenFeature standard. Feb 15, 2024 6 min read OpenFeature Unlocking the Power of Feature Flags with OpenFeature The popularity of feature flags has exploded in recent years, but it still faces some challenges to adoption. Discover how OpenFeature may be the answer to unlocking the power of feature flagging for the future. Feb 15, 2024 2 min read OpenFeature OpenFeature’s CNCF Incubation is a Big Deal Big news: OpenFeature just made a major leap, being accepted by the Cloud Native Computing Foundation (CNCF) for Incubation. Dec 19, 2023 2 min read Outside Voices DevCycle Reinforces its Commitment to the OpenFeature Ecosystem with the Launch of New Providers DevCycle is excited to announce its extended support for OpenFeature at KubeCon + CloudNativeCon in Chicago with new providers for Go, Java, .NET and Python. These new additions will further diversity the languages supported, ensuring portability of feature flags across different services. DevCycle is dedicated to open standards and its goal Nov 7, 2023 Outside Voices OpenFeature DevCycle Joins OpenFeature We are thrilled to announce that DevCycle now supports OpenFeature, a standards setting open-source project established to set a unified and open standard for feature flag management. Jul 16, 2023 3 min read Page 1 of 1 DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/we-rebuilt-our-onboarding-around-mcp-the-result-3x-sdk-installs/ | MCP Onboarding for Feature Flagging: 3x SDK Installs Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home We Rebuilt Our Onboarding Around MCP: The Result, 3X SDK Installs Cobi Druxerman Oct 6, 2025 • 7 min read TL;DR We rebuilt onboarding around our MCP (Model‑Context‑Protocol) integration so developers start inside their editor with our SDK— not a detour through example apps or sandboxes. Early results: ~3× more users reach SDK install versus our previous flow, and they see real product value sooner. This piece shares why we made the change, how the MCP‑centered flow works, what we learned, and what’s next. 🎥 Demo: Watch the new onboarding flow Why Change at All? Our north star for onboarding has always been simple: get users to the “aha” moment fast. With a SDK‑based product, that “aha” usually requires installing the SDK into the user’s own app —and that’s exactly where friction creeps in. We had invested heavily in a guided tutorial with three flavors: No‑code, in‑browser walkthrough Code sandbox to see real code without installing Example app that users could install locally Developers (our core audience) were routed to the code sandbox and example app paths, and we encouraged the example app because it provided a convincing, runnable experience. In practice, most users skipped the flow altogether—likely because even a “simple” example app install feels like a detour when all you want to do as a developer is explore the tool and decide if you want to try the SDK in your codebase. Net effect: even when users did the tutorial, they still had to figure out the SDK install on their own to get to real value. What the Old Example App Flow Did Well (and What it Didn’t) What it did: Collected a bit of profile data (e.g., "Developer that uses React + OpenFeature”). Prompted an npx command to spin up a pre‑keyed example app. Waited for a “run” event to unlock the tutorial. Guided users through feature flag basics and our core concepts. Dropped them into the dashboard to continue exploring. What it did well: Explained the core concepts of the DevCycle platform, quickly and effectively Displayed a heightened level of interest and commitment to learning about the platform Where it fell short: Perceived complexity → high skip rate. Off‑trajectory → even “successful” users still weren’t running our SDK in their actual app. Indirect value → the best path to “aha” (SDK in their app) wasn’t the path this onboarding flow optimized for. Some Key Steps in the Example App-Based Onboarding Tutorial Why MCP? MCP lets an AI coding assistant (like Cursor, Claude Code or VS Code) call into your platform and blend API operations with context‑aware prompts. That means we can: Orchestrate SDK install where developers already are— inside their editor . Detect language/framework and tailor the install. Create platform resources (e.g., a feature flag) directly from the assistant. Emit events back to our dashboard to progress the tutorial automatically. In other words, this new world with AI assistants and MCP gives us a straight line from “sign up” to “SDK installed in your app,” without detours. The New, MCP‑Centered Onboarding As a part of the new flow, we compressed our onboarding into three guided steps , with MCP at the centre: Install the DevCycle MCP Identify your AI coding assistant (Cursor, Claude Code, VS Code, etc.). Offer one‑click install or exact steps per assistant. Authenticate; our platform listens for a successful “MCP ready” event and auto‑advances. Install the DevCycle SDK (inside your repo) You trigger a single prompt inside your assistant: “Install the DevCycle SDK.” Behind the scenes, your coding agent detects your app’s language/framework and our MCP sends a precise, environment‑aware instruction set back (including your SDK key). We verify install and auto‑advance again. Create a “Hello World Banner” behind a feature flag A second prompt: “Create a Hello World banner and gate it behind a flag.” Our MCP creates the Feature and Variable, wires up the client code, and returns the context for toggling. The dashboard confirms each step and shows you the live feature. From here, you can explore in the dashboard or continue inside your AI coding assistant —whichever suits your workflow. Some Key Steps in the MCP-Based Onboarding Tutorial Before vs. After (At a Glance) Aspect Previous Flow MCP-Centered Flow Primary Path Example App Editor-First Via MCP Where Work Happens Browser and local example app Your repo + AI coding assistant Install friction Example-app detour Direct SDK install into your project Guidance Stepwise tutorial, then dashboard Two natural-language prompts with auto-progress Activation moment After tutorial, still needs SDK install SDK installed + live feature flag Outcome Learning about value Experiencing value in your code Under the Hood: How it Works Assistant detection & instructions Users pick their coding assistant; we present the right MCP install steps or one‑click options (e.g., Cursor, Claude Code or VS Code). Language & framework detection The MCP leverages the AI coding assistant to inspect the workspace and infer stack + package manager. The MCP dynamically provides a detailed install prompt back to the AI coding assistant with a full install plan (e.g., dependencies, env variables, initialization code). Eventing for progress The DevCycle platform listens for MCP and SDK lifecycle events (MCP installed, SDK initialized, Variable evaluated). Each event auto‑unlocks the next step and surfaces validation feedback. Two prompts, real work We intentionally keep prompts minimal and handle the heavy lifting in the MCP: “Install the DevCycle SDK.” “Create a Hello World banner feature and gate it behind a flag.” Everything else—the specificity, the code edits, the platform calls—happens via the DevCycle MCP + your AI assistant. Results so far ~3× increase in users reaching SDK install compared to the old flow. Fewer "skips" - the path feels “native” to how developers already work. Faster time‑to‑value - live feature flag within minutes, not after a separate tutorial track. We’re obviously being careful here: onboarding metrics evolve as traffic and cohorts change. But directionally, focusing on MCP has moved users down‑funnel faster and with less drop‑off. Learnings for Others That May Want to Leverage MCP in a Similar Way For product managers Treat MCP as a product surface , not just “AI glue.” When your “aha” requires installation or configuration, MCP can relocate that friction from a browser wizard to a context‑aware assistant in the user’s real environment. For product engineers MCP gives you a deterministic orchestration layer for otherwise brittle “copy/paste this code” moments. With stack detection, targeted API calls, and event hooks, you can ship guided automation that still leaves users in control. For AI enthusiasts This is a practical, non‑demo use of AI agents: let the assistant perform structured, reversible changes (dependencies, config, code scaffolding) and reflect success back to the product in real time. What’s Still Rough (and How We’re Handling It) MCP install/auth friction It’s better than asking users to install an entire example app, but the install/auth handshake of the MCP itself is still more steps than we’d like . This is likely something we can't fix on our own but something that will change over time as MCP is more widely adopted. Non-deterministic behavior Given generative AI is non-deterministic it doesn't matter how verbose and specific your underlying prompts are, AI may not do what you expect. We protect for this with permissions and API guardrails on destructive actions and by giving users an easy out of the onboarding flow if AI does something unexpected. Trust & reversibility AI editing code can make people nervous. But with the current state of AI coding assistants all changes are transparent and diff‑able , and we scope actions to a clearly defined surface (config, init, feature scaffolding). Implementation Notes (For the Curious) Event model : mcp_installed → sdk_initialized → variable_evaluated . Each event emits an SSE event on a channel dedicated to your browser session and unlocks UI states. Prompt design : human‑readable requests paired with tool‑centric instructions (package manager commands, file paths, code snippets) only visible to the assistant via MCP. Safety rails : explicit prompt guidance on things to avoid, API guardrails for destructive events (i.e. blocking deletion) and a “skip this” option always available, in case AI decides to take a detour that can't be easily corrected. Where We’re Taking This Next Deeper “day‑1” recipes for example progressively enhancing the Hello World banner into more real-world examples where possible. Continuing to enhance the MCP with additional tools like the ability to assist with code migrations from other Feature Flagging platforms. Wrap‑up MCP is new, and parts of the install/auth experience are still rough around the edges. But even today it meaningfully reduces friction for SDK‑based products. For us, focusing onboarding on MCP shifted the experience from learning about DevCycle to using DevCycle—inside the user’s own codebase, within minutes, driven by simple natural‑language prompts. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://www.lob.com/industries/insurance | Automated Direct Mail For Insurance Companies | Lob Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Insurance Automated direct mail for insurance companies From special offers to renewals to billing, Lob makes it easier than ever to send insurance leads and customers the information they need when they need it — so they stick around. Book a demo For more information about how this data is handled, please view our Privacy Policy What good looks like We help insurance companies send direct mail with massive impact. Here’s what we’ve seen work. Promotions Send fridge-worthy special offers According to our 2024 State of Direct Mail Consumer Insights survey, 78% of consumers are likely to open or read a direct mail piece with an offer or promotion. Winning Formats Postcards Self-Mailers Booklets Account Statements + Renewal Notifications Share essential information Scale account updates and payment envelopes. Lob’s industry-leading security gets your insurance direct mail where it needs to go safely and on time. Winning Formats Letters Envelopes Claim Payments Streamline accounts payable Securely send and track claims checks and other payments at any scale. Winning Formats Checks Renewal Notices Engage at the right moment Trigger renewal notices and policy changes so that customers stick around. Winning Formats Letters Snap Packs Expand your reach — and your customers’ coverage Fill in the blanks Retarget website visitors and email subscribers by matching them to valid addresses to reach more leads Reduce churn Cut through digital noise to keep loyal and lapsed audiences engaged Boost productivity Send compliant mail at scale and eliminate logistical hiccups Measure + maximize Track delivery and demonstrate the value of every send with advanced analytics Send mail faster while cutting costs Automate your direct mail and see up to 85% in cost savings. Lob integrates with your digital channels so you can use your customer data to trigger sends and get in mailboxes in days instead of weeks. See our full list of integrations “A long, arduous, manual print process that took 3-5 minutes per letter suddenly didn’t require any time after the full Lob integration, which was life-saving.” – Louis Condon, Program Manager Read the case study Don’t lose customers to typos Address verification stops failed deliveries in their tracks. Learn more about address verification Put security and compliance first Every printer in Lob’s network meets industry-leading standards to ensure the safety and security of your mail. Our annual third-party audits ensure compliance with HIPAA, SOC-2, and more. See how printing works Why do so many retail and ecommerce companies already trust Lob? Because of numbers like these 98% Reduction in production time Read the case study 4X Increase in response rates Read the case study State of Direct Mail Consumer Insights 84% of marketers say direct mail has the highest ROI Read the report Insurance FAQs What is insurance marketing? Insurance marketing is the process of promoting and selling insurance products to potential customers. This can include various strategies such as advertising, direct mail, digital marketing, and agent networking. The goal of insurance marketing is to create awareness, generate interest, and drive action from customers. It also involves building relationships with existing customers to encourage repeat business, expanded coverage, and referrals. Insurance marketing plays a crucial role in the overall success of an insurance company by effectively reaching and engaging target audiences. How can insurance companies use direct mail? Insurance companies can effectively utilize direct mail for sending renewal notices to enhance customer retention. By mailing personalized reminders well in advance of policy expiration dates, insurers can ensure that their clients are informed and engaged with the renewal process. Including pertinent information, such as updates to coverage options or special discounts for early renewal, keeps direct mail marketing for insurance agents relevant and valuable. Additionally, insurance mailers can be employed to highlight important changes to policy terms or premium adjustments. By providing clear and concise information, insurance companies can maintain transparency and build trust with their clients. This proactive approach can help alleviate any concerns about rate increases or changes in coverage, ultimately strengthening customer relationships. What roles does omnichannel play in insurance marketing strategies? Omnichannel strategies in insurance marketing enhance customer experience by providing seamless and consistent interactions across multiple channels, such as websites, mobile apps, social media, direct mail, and in-person interactions. This approach allows insurers to offer a unified experience where customers can engage with the brand through their preferred channels, maintaining context and continuity. Omnichannel marketing improves customer engagement and personalization by integrating data from various touchpoints. This enables insurers to tailor offers and communications based on individual preferences and behaviors, ensuring that customers receive relevant information and timely support across all channels. How can insurance companies use direct mail to acquire customers? Insurance companies can leverage direct mail as a powerful tool for customer acquisition by designing targeted campaigns that reach lookalike audience demographics or locales that mirror their current best customers. By using tools like Lob Audiences, insurers can identify potential customers who may benefit from their services and tailor their messaging accordingly. Including attractive offers, such as limited-time discounts or free consultations in insurance mailers, can incentivize recipients to consider their options and take action. How can insurance companies use direct mail to retain customers? Direct mail can be a valuable tool for retaining existing customers. Insurance companies can use direct mail to send personalized communications and offers to their current policyholders. This can include reminders for upcoming policy renewals, updates on coverage options or discounts, and information about new services or products. Direct mail provides current customers with a physical reminder of important dates. Send direct mail that builds trust Book a demo Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:37 |
https://blog.devcycle.com/whats-new-in-q2-ai-powered-flag-management-debugging-insights-and-smoother-rollouts/ | What’s New in Q2: AI-Powered Flag Management, Debugging Insights, and Smoother Rollouts 🚀 Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home What’s New in Q2: AI-Powered Flag Management, Debugging Insights, and Smoother Rollouts 🚀 DevCycle Sep 3, 2025 • 3 min read Over the past quarter, we’ve rolled out new features and improvements designed to help you build, test, and release with more control and visibility. Here’s everything new in DevCycle! 🤖 Meet DevCycle’s MCP Server We’re thrilled to announce the availability of the DevCycle MCP Server ! The MCP Server makes feature flag management more natural and accessible, right inside your workflow: Create Features and Variables directly from your IDE using natural language QA Features by managing overrides through chat Choose your setup : install either the Remote or Local MCP Server, depending on your needs With intuitive prompts and tools, the MCP Server brings AI into the heart of your development process. 👉 Learn how to get started 🪝 Evaluation Hooks for Server-Side SDKs Evaluation Hooks are now available across all server-side SDKs, giving you visibility into the entire lifecycle of Variable evaluations. Hooks let you run custom logic at four stages: before – run code before evaluation starts after – execute logic after a successful evaluation onFinally – run code at the end of each variable call error – handle errors during evaluation Use hooks to: Log every evaluation for auditability Capture performance metrics Build custom analytics pipelines 👉 See the Node.js docs for an example 🧪 Variable Evaluation Reasons Debugging just got a whole lot easier. Each variable evaluation now includes a new eval object with: reason – why a value was served (e.g. TARGETING_MATCH , DEFAULT , SPLIT ) details – optional context for the match target_id – the rule or audience that matched This makes QA, observability, and logging far more powerful. ⚠️ Note: the older evalReason field is now deprecated and will be removed in an upcoming release. Please update your SDK usage accordingly. 👉 Learn more 🗂 Feature Overview Tab and Redesigned Feature Details Page We’ve redesigned the Feature Details Page to streamline navigation and feature management. The highlight: a brand-new Overview Tab 🚀. The Overview Tab consolidates critical context in one place: Latest audit log changes Assigned maintainers for ownership An editable markdown summary for key notes Linked resources like Notion, GitHub, and Figma A Variables table with tags and descriptions The new tabbed design keeps features organized and easy to work with. 👉 Learn more ⏸️ Stop Gradual and Multi-Step Rollouts Rolling out a Feature and spotted an issue? You can now pause a rollout mid-progress , holding traffic at the current distribution, without rolling back completely. This limits exposure while you fix bugs and then lets you resume whenever you’re ready. 👉 See how to manage rollouts 🛠 Dashboard and UX Improvements We’ve shipped a number of smaller but impactful enhancements to help you move faster: Browser timezones — clearly shown in schedules Editable large lists — update items directly in the modal Variation tooltip — see what value is being served at a glance Project switching indicator — added visibility when changing projects Environment indicators — show where Audiences or Custom Properties are in use Clearer audit log diffs — highlight values added or removed Sort features by creation date — easily spot older flags ready for cleanup These refinements give you more control, insight, and speed as you build and ship. What’s Next? We’re always listening to feedback. Have requests or ideas? Check out our public roadmap and add your feature requests or email us directly at product@devcycle.com ! Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://marketplace.visualstudio.com/items?itemName=mysten.move | Move - Visual Studio Marketplace Skip to content | Marketplace Sign in Visual Studio Code > Programming Languages > Move New to Visual Studio Code? Get it now. Move Preview Mysten Labs mystenlabs.com | 21,666 installs | ( 11 ) | Free A Move language integrated development environment for Sui. Installation Launch VS Code Quick Open ( Ctrl+P ), paste the following command, and press enter. Copy Copied to clipboard More Info Overview Version History Q & A Rating & Review Move Provides language support for the Move programming language. For information about Move visit the language documentation . It also provides early-stage support for trace-debugging Move unit tests using a familiar VSCode debugging interface (e.g., stepping through the code, tracking local variable names, setting line breakpoints). How to Install Open a new window in any Visual Studio Code application version 1.61.0 or greater. Open the command palette ( ⇧ + ⌘ + P on macOS, or use the menu item View > Command Palette... ) and type Extensions: Install Extensions . This will open a panel named Extensions in the sidebar of your Visual Studio Code window. In the search bar labeled Search Extensions in Marketplace , type Mysten . The Move extension should appear as one of the option in the list below the search bar. Click Install . Open any file that ends in .move . Installation of the extension will also install a platform-specific pre-built move-analyzer binary in the default directory (see here for information on the location of this directory), overwriting the existing binary if it already exists. The move-analyzer binary is responsible for the advanced features of this VSCode extension (e.g., go to definition, type on hover). Please see Troubleshooting for situations when the pre-built move-analyzer binary is not available for your platform or if you want to use move-analyzer binary stored in a different location. If you want to build, test, and trace Move code using the extension, you must install the sui binary on your machine - see here for instructions. The extension assumes that the sui binary is in your system path, but you can set its custom location using VSCode's settings ( ⌘ + , on macOS, or use the menu item Code > Preferences > Settings ). Search for the move.sui.path user setting, set it to the new location of the sui binary, and restart VSCode. In order to trace-debug Move code execution, the sui binary must be built with the tracing feature flag. If your version of the sui binary was not built with this feature flag, an attempt to trace test execution will fail. In this case you may have to build the sui binary from source following these instructions . Troubleshooting What if the pre-built move-analyzer binary is not available for my platform? If you are on Windows, the following answer assumes that your Windows user name is USER . The move-analyzer language server is a Rust program which you can install manually provided that you have Rust development already installed . This can be done in two steps: Install the move-analyzer installation prerequisites for your platform. They are the same as prerequisites for Sui installation - for Linux, macOS and Windows these prerequisites and their installation instructions can be found here Invoke cargo install --git https://github.com/MystenLabs/sui sui-move-lsp to install the move-analyzer language server in your Cargo binary directory, which is typically located in the ~/.cargo/bin (macOS/Linux) or C:\Users\USER\.cargo\bin (Windows) directory. Copy the move-analyzer binary to ~/.sui/bin (macOS/Linux) or C:\Users\USER\.sui\bin (Windows), which is its default location (create this directory if it does not exist). What if I want to use a move-analyzer binary in a different location? If you are on Windows, the following answer assumes that your Windows user name is USER . If your move-analyzer binary is in a different directory than the default one ( ~/.sui/bin on macOS or Linux, or C:\Users\USER\.sui\bin on Windows), you may have the extension look for the binary at this new location using VSCode's settings ( ⌘ + , on macOS, or use the menu item Code > Preferences > Settings ). Search for the move.server.path user setting, set it to the new location of the move-analyzer binary, and restart VSCode. What if advanced features (e.g., go to def) do not work, particularly after re-install or upgrade Assuming you did not specify a different location for the move-analyzer binary and that the move-analyzer binary already exists in the default location ( ~/.sui/bin on macOS or Linux, or C:\Users\USER\.sui\bin on Windows), delete the existing move-analyzer binary and reinstall the extension. What if everything else fails? Check Sui Developer Forum to see if the problem has already been reported and, if not, report it there. Features Here are some of the features of the Move Visual Studio Code extension. To see them, open a Move source file (a file with a .move file extension) and: See Move keywords and types highlighted in appropriate colors. Comment and un-comment lines of code ( ⌘ + / on macOS or the menu item Edit > Toggle Line Comment ). Place your cursor on a delimiter, such as < , ( , or { , and its corresponding delimiter -- > , ) , or } -- will be highlighted. As you type, the editor will offer completion suggestions, in particular: struct field name and method name suggestions following . being typed suggestions following :: being typed (including auto-imports) code snippets to complete init function and object type definitions If the opened Move source file is located within a buildable project (a Move.toml file can be found in one of its parent directories), the following advanced features will also be available: compiler diagnostics go to definition go to type definition go to references type on hover outline view showing symbol tree for Move source files inlay hints: types: local declarations, lambda parameters, variant and struct pattern matching parameter names at function calls auto-fixes: unbound types and functions (auto-import or full qualification) If the opened Move source file is located within a buildable project, and you have the sui binary installed, you can build and (locally) test this project using Move: Build a Move package and Move: Test a Move package commands from VSCode's command palette. If the opened Move source file is located within a buildable project, and you have the sui binary installed, you can trace-debug execution of Move unit tests within this project. This functionality is provided by this (Move) extension automatically including the Move Trace Debugging extension . Go to the Move Trace Debugging extension link to find more detailed information about trace-debugging and the current level of support. Trace-debugging a Move unit test is a two-step process: first, you need to generate traces for Move unit tests by using Move: Trace Move test execution command from VSCode's command palette (traces will be available in the traces directory in JSON format) second, you need to execute Run->Start Debugging menu command with Move file containing the test you want to trace-debug opened (if the file contains multiple tests, you will be able to select a specific one from a drop-down menu) Contact us Jobs Privacy Manage cookies Terms of use Trademarks © 2026 Microsoft | 2026-01-13T08:48:37 |
https://blog.devcycle.com/ | DevCycle Blog | OpenFeature Content and Tutorials from the First Native Provider Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 In the last few months we’ve released a ton of upgrades including; a suite of debugging functionality, powerful AI-assisted tooling and new observability integrations. Combined, this functionality makes it even easier to understand how your features behave in production. 🧩 User Debug Tools The new suite of Debug Tools: Evaluation Nov 5, 2025 3 min read We Rebuilt Our Onboarding Around MCP: The Result, 3X SDK Installs TL;DR * We rebuilt onboarding around our MCP (Model‑Context‑Protocol) integration so developers start inside their editor with our SDK—not a detour through example apps or sandboxes. * Early results: ~3× more users reach SDK install versus our previous flow, and they see real product value sooner. * This piece Oct 6, 2025 7 min read What’s New in Q2: AI-Powered Flag Management, Debugging Insights, and Smoother Rollouts 🚀 Over the past quarter, we’ve rolled out new features and improvements designed to help you build, test, and release with more control and visibility. Here’s everything new in DevCycle! 🤖 Meet DevCycle’s MCP Server We’re thrilled to announce the availability of the DevCycle MCP Server! The MCP Sep 3, 2025 3 min read Product Updates From Hackathon to Production: What It Took to Ship Our DevCycle MCP When we started building our MCP server, it began as a simple hackathon project: take our existing CLI interface, which already has authentication and most of our API calls, and adapt it to work as an MCP server. As a hackathon project, it turned out to be a pretty compelling Sep 1, 2025 8 min read Introducing the DevCycle MCP Server: Ship Flags Faster, Safely with AI Coding Agents Why we built a MCP server for DevCycle AI coding environments and agents are great at writing code—but the moment you need to create a feature flag, tweak targeting, or check an audit log, you’re back to context‑switching: open the dashboard, copy keys, run a CLI, paste Aug 26, 2025 5 min read DevCycle is Now SOC 2 Type II Compliant We're excited to announce that as of December 2024, DevCycle has achieved SOC 2 Type II compliance! SOC 2 Type II compliance represents a critical milestone in our commitment to security and privacy, demonstrating our rigorous adherence to the highest standards of trust and reliability. What is SOC Jun 27, 2025 1 min read OpenFeature vs. Proprietary Systems Breaking Down Vendor Lock-In Risks and Future-Proofing Your Stack Introduction: The Double-Edged Sword of Feature Flagging Feature flagging has become a cornerstone of agile software development, enabling trunk-based development, streamlined A/B testing, improved incident management, and safe, gradual feature releases. Its capacity to deliver value to engineering teams is Jun 19, 2025 3 min read OpenFeature Why is OpenFeature Support is Critical? Comparing Top OpenFeature Providers Feature flagging is essential for modern software development, enabling teams to test in production, manage releases incrementally, and mitigate risks, by separating code deploys from the release of features to users. As adoption grows, standardization via OpenFeature—an open specification for feature flags—becomes crucial to avoid vendor lock-in, simplify Jun 2, 2025 6 min read OpenFeature OpenFeature Multi-Provider: Enabling New Feature Flagging Use-Cases (Video) What is OpenFeature and the Multi-Provider? What Are Some Use Cases? Watch DevCycle’s Co-Founder and CTO, Jonathan Norris, as he highlights the capabilities and unique use cases enabled by the OpenFeature Multi-Provider. Learn about OpenFeature, the Multi-Provider and about use cases such as combining multiple feature flag vendors under May 29, 2025 1 min read Product Updates DevCycle Product Updates (Q1 2025) Find out what's new at DevCycle, including stale flag alerts, project level RBAC and enhancements to targeting. Welcome to your Q1 2025 DevCycle product update! We’ve rolled out a ton of exciting improvements in the past few months — from powerful new lifecycle tools to better access management May 12, 2025 2 min read Using Feature Flags to Build a Better AI In a world where AI is becoming increasingly prevalent in applications, there is a need to ensure that the AI is accurate. We hear a lot about failures with chatbots going rogue, image generators showing physically incorrect images, and generally wrong answers to simple questions. So, how can you ensure Apr 25, 2025 3 min read Guides and Tutorials 5 Steps to a Continuous Deployment Culture Deploying software into production so that your users can access it is one of the key areas of software development. Whether you are a two-person start-up using the latest tools and frameworks, a small business integrating multiple SaaS applications, or an enterprise business with 40 years of legacy systems to Mar 28, 2025 11 min read OpenFeature OpenFeature Hackathon 2024 A few times a year at DevCycle, we hit pause on our usual work, push aside our roadmaps, and dive into a few days of rapid experimentation and collaboration. For our first hackathon of 2025, we opted for an OpenFeature theme —a chance to explore new ideas, test bold concepts, Mar 19, 2025 9 min read OpenFeature How Jackson Used DevCycle and OpenFeature to Achieve a Zero-Downtime Migration Today's DevCycle Spotlight features Jackson Kasi, a developer who won the OpenFeature Aficionado prize for our first ever DevCycle Feature Flag Challenge on Dev.to where we challenged developers to build a fun or creative project using DevCycle! Jackson won the OpenFeature Aficionado prize for the most innovative Mar 4, 2025 3 min read OpenFeature Open Standards in a Trade War: Why You'll Need an Escape Hatch When Politics Hits Your Stack Open Standards have never been more important. In a world with impending trade wars globally, it's likely that software will be taxed and restricted. Going forward it is going to be critical to be able to rip and replace software if the winds of geopolitics shift in the wrong direction. Feb 26, 2025 7 min read Unleashing Creativity: How Ansell Built Cycle Doodle Using DevCycle Today's DevCycle Spotlight features Ansell Maximilian, a developer who won the first DevCycle Feature Flag Challenge on Dev.to! The challenge encouraged entrants to build a fun and creative project using DevCycle. He took the top prize with his inventive Cycle Doodle project. Judges loved the creativity of Feb 25, 2025 3 min read Guides and Tutorials How to Use Devcycle to Configure Your Pieces-Powered Generative AI App This blog post explains using DevCycle to configure a generative AI app with Pieces , focusing on a Star Wars-themed copilot. It covers managing LLM configurations with feature flags for quick experimentation and highlights the benefits of using LLM abstractions for efficient model integration. Nov 11, 2024 7 min read Guides and Tutorials Creating a Star Trek-Inspired GenAI Copilot Using Pieces and DevCycle In this post, we show you how DevCycle and Pieces for Developers make experimenting with AI as smooth as a warp-speed jump. Nov 11, 2024 Outside Voices Guides and Tutorials Beam Me Up, SQLite: Running Real-Time Performance Experiments with DevCycle This post guides you through setting up an engineering-led experiment to compare the performance of SQLite (local), Turso, and SQLiteCloud using the SQLite Trek app and DevCycle. Sep 13, 2024 8 min read Guides and Tutorials Set Phasers to Experiment: How to Use Feature Flags to Drive SQLite Performance Tests In this blog post, we explore how feature flags are essential for effective experimentation and introduce a practical example of performance testing across different SQLite options to showcase DevCycle's experimentation capabilities. Sep 13, 2024 5 min read Case Studies Featured IGS Case Study - Using DevCycle in a Cloud-Based Microservices Architecture About IGS Intelligent Growth Solutions (IGS) is a pioneering company in the vertical farming industry, specializing in the development of advanced vertical farming towers. Their new and innovative approaches optimize agricultural productivity by using vertical space and technology to maximize crop yield and quality. IGS initially considered using flagd but Aug 9, 2024 3 min read OpenFeature Recipe for Change: Unlocking Feature Flag Flexibility in a Hyperapp with OpenFeature and the Multi-Provider Utility Are your feature flags as flexible as they could be? If they are hard-coded static configurations, the answer is likely no. In this guide, we'll explore how OpenFeature can unlock the full potential of feature flags using a fun (although maybe impractical) example—a Recipe Manager app where Aug 6, 2024 9 min read Page 1 of 3 Older Posts → DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/who-knew-feature-flags-would-save-ai-coding/ | Who Knew Feature Flags Would Save AI Coding Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Who Knew Feature Flags Would Save AI Coding Mark Allen Dec 10, 2025 • 3 min read From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don't. Not anymore. You wrap it in a feature flag. Here's the story of how I moved from "AI wrote this" to "shipping it live". Safely, quickly, iteratively. Why Feature Flags Make Sense for AI‑Driven Code When you let an AI generate components (front‑end UI, backend service, whatever), you're riding high on velocity. But velocity without control is asking for trouble. Bugs, weird edge‑cases, and performance surprises are all waiting. Feature flags give you a middle ground: You wrap the new component behind a flag. You release it to a limited audience such as your team, product manager, or a salesperson. You observe behavior in production with real data and real users without risking the whole user base. In my workflow, I push the AI‑generated component, flip the flag for myself and the product manager. We use it, poke it, and show it to a customer. Then, when it holds up, we flip it on for everyone. I did this recently when I used AI to build a data entry screen from one that just displayed the data. I wrapped the edit and save buttons in a feature flag. Then, I turned it on for the PM and a user who had been asking for the feature. It allowed us to see it work in production with production data. All while not changing the functionality for the rest of the users. That's the fastest, safest route from "AI‑generated" to "production‑ready." "Perfect is the enemy of done". Wrap it, ship it, and watch it run. What this looks like in practice Generate a component via your AI editor (mine is Cursor). Wrap it with a feature flag: conditionally render it, toggle the logic path. Deploy to production, but keep the flag OFF globally. Enable the flag for a small audience: you, stakeholders, and specific user IDs. Monitor : error rates, performance metrics, and user feedback. Iterate : fix issues, refine. Roll out : flip the flag ON for a broader or full audience once confident. This lets you ship early and often , without being held hostage by “there’s one more edge-case” syndrome. How to Add the Devcycle MCP Server to Your Workflow in Cursor If you're using the MCP protocol for AI‑powered tooling (for example, Cursor or similar), you can plug in DevCycle's MCP server in minutes. From DevCycle 's official docs: Add the DevCycle MCP server endpoint in your AI client configuration. For example in ~/.cursor/mcp_settings.json : { "mcpServers": { "DevCycle": { "url": "https://mcp.devcycle.com/mcp" } } } ( docs.devcycle.com ) In Cursor you'll see "DevCycle - Needs login". Click to authenticate via browser, choose your organization, and you're connected. Now you can manage flags, variables, targeting, and analytics via the MCP interface, all from your AI‑powered editor. Once connected, you can then install DevCycle into the project using the prompt on each of the Installation pages for each SDK, such as for React . Now add a feature flag: "create a new feature flag called new-intro-text." Select the existing text and "replace this text with the value of the new-intro-text feature flag, set the default to be an empty string." Change the targeting rules: "Change the All users targeting rule for new-intro-text to serve off. Then create a new rule to check if the user's email ends in @example.com and then serve on." In production, you deploy that code, but leave new-intro-text flag OFF globally. Then you enable it for you/your team. Once happy, open it to all users. Using DevCycle MCP and Cursor together creates a smooth feedback loop: AI writes, you deploy, you test live, and you refine, all without full rollout risk. Why This Matters for Ai‑Driven Teams Speed : You get components into production early on. Risk control : Only a subset sees the new code until you're confident. Feedback loop : Real‑world usage data, not just local tests. Iteration-friendly : AI writes, you enable, you refine, then rinse and repeat. When you're using AI tools to generate code at a rapid clip, the bottleneck becomes validation and control. Feature flags become your guardrails. They let you move fast and safely. Final Thoughts AI‑assisted development is here. The cursor blinks, and magic flows. But magic without discipline becomes mayhem. The simple pattern of generate, wrap behind a feature flag, deploy, test in tiny slice and rollout is a backbone for AI‑driven dev teams. generate → wrap behind feature flag → deploy → test in tiny slice → roll out So, next time your AI writes a component, don't hesitate to wrap it in a feature flag, ship it to a safe audience, and observe how it behaves. Then let it fly wide. Your AI‑enabled future is ready. Controlled, observable, and smooth. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read What We Shipped in Q3: User Debug Tools, AI-Generated Features and More 🚀 In the last few months we’ve released a ton of upgrades including; a suite of debugging functionality, powerful AI-assisted tooling and new observability integrations. Combined, this functionality makes it even easier to understand how your features behave in production. 🧩 User Debug Tools The new suite of Debug Tools: Evaluation Nov 5, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://dev.to/devnews/s5-e7-apple-s-spyphone-an-apple-app-store-settlement-and-the-expansion-of-government-facial-recognition-software#main-content | S5:E7 - Apple’s #SpyPhone, an Apple App Store Settlement, and the Expansion of Government Facial Recognition Software - 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 DevNews Follow S5:E7 - Apple’s #SpyPhone, an Apple App Store Settlement, and the Expansion of Government Facial Recognition Software Sep 2 '21 play In this episode, we talk about an the expansion of government facial recognition software and an Apple App store settlement. Then we speak with Yafit Lev-Aretz, assistant professor of law at Baruch College and the Director of Tech Ethics program at the Zicklin Center for Corporate Integrity, about Apple scanning iCloud images and iMessages for child sexual abuse material. Then we speak with Anunay Kulshrestha, Princeton Computer Science doctoral candidate, whose team had built a similar child sexual abuse materal scanning system, about the potential privacy and cybersecurity risks that implementing such a system creates. Show Notes Scout APM (DevNews) (sponsor) CodeLand (sponsor) Facial Recognition Software: Current and Planned Uses by Federal Agencies System Error: Where Big Tech Went Wrong and How We Can Reboot Apple Settles With App Developers Without Making Major Concessions The All-Seeing "i": Apple Just Declared War on Your Privacy Apple: Expanded Protections for Children Opinion: We built a system like Apple’s to flag child sexual abuse material — and concluded the tech was dangerous Identifying Harmful Media in End-to-End Encrypted Communication: Efficient Private Membership Computation Yafit Lev-Aretz Yafit Lev-Aretz is an assistant professor of law at the Zicklin School of Business (Baruch College, City University of New York), and the Director of Tech Ethics program at the Zicklin Center for Corporate Integrity. Professor Lev-Aretz is a tech policy expert with over fifteen years of experience in studying and operationalizing the relationship between law, technology, and society. Anunay Kulshrestha Anunay Kulshrestha is a doctoral candidate in Computer Science at Princeton University, affiliated with the Center for Information Technology Policy. His research interests lie in applied cryptography and computer security, and their policy implications for privacy in today’s networked world. He is interested in understanding how cryptographic techniques can yield transparency- and accountability-enhancing privacy-preserving solutions to policy problems of trust. Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:37 |
https://blog.devcycle.com/introducing-the-devcycle-mcp-server/ | Introducing the DevCycle MCP Server: Ship Flags Faster, Safely with AI Coding Agents Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Introducing the DevCycle MCP Server: Ship Flags Faster, Safely with AI Coding Agents Cobi Druxerman Aug 26, 2025 • 5 min read DevCycle's MCP lets you create feature flags in minutes using your favorite AI tool Why we built a MCP server for DevCycle AI coding environments and agents are great at writing code—but the moment you need to create a feature flag, tweak targeting, or check an audit log, you’re back to context‑switching: open the dashboard, copy keys, run a CLI, paste results, repeat. That’s slow, error‑prone, and kills flow. The new DevCycle Model Context Protocol (MCP) Server lets AI‑powered editors (Cursor, VS Code, Windsurf) and assistants like Claude Code talk directly to your DevCycle projects to do real work for you: create flags, manage variations and targeting, fetch SDK keys, pull audit history, and even report on evaluation analytics. No tab‑sprawl. No manual stitching of disparate contexts. Just ask, and it acts safely and with guardrails. What we built A hosted MCP server for DevCycle. It’s based on our CLI and exposed as a secure, OAuth‑backed MCP endpoint. Connect once; your client negotiates streaming (SSE) or HTTP, and you’re ready to go. Hosted endpoints Auto‑negotiating: https://mcp.devcycle.com/mcp SSE‑only (fallback): https://mcp.devcycle.com/sse Broad tool coverage Feature and variation CRUD, targeting rules, variables, environments, and SDK keys, project introspection, self‑targeting overrides, and usage/evaluation analytics. Production safety Tools that can change production are clearly marked, and destructive actions require explicit confirmation. The authentication ensures the MCP server respects the given user's permission level. The problem DevCycle MCP solves (and how) Before: Every time you create a new feature, you need to juggle whether to start in your IDE with the code or in the DevCycle interface to create the feature flag you're going to use. This is common with many actions and requires context switching. Sometimes, if you're using AI agents, you need to correct them when they do something before you're ready. Now: your AI agent has direct access to DevCycle to take actions on your behalf, exactly when they make sense during the workflow. You can ask things like: “Create a new feature flag called new-checkout-flow .” “Enable targeting for header-redesign in production .” “Show me evaluations for pricing-experiment from the last 7 days.” Under the hood, your agent speaks to our server via the MCP, which executes the appropriate DevCycle commands with your authorization and returns structured results your agent can reason about. Check out some full-fledged use cases here ⬇️ Why it’s unique OpenFeature‑native platform : DevCycle is the first OpenFeature‑native feature flagging platform —built by OpenFeature governance contributors—so your MCP workflows align with the standard you already use in code. Zero setup : It’s hosted and OAuth‑backed—no daemons, no ports. Connect and go; as long as you're authenticated, it's always running. Wide, practical surface area : From flag creation to audit trails and evaluations, the toolset maps to day‑to‑day release management—not just cool tech demos. Built for safety : Tied to your permission level via OAuth, with clear prod/destructive markers and confirmation flows. This ensures AI can't make destructive changes without your approval. DevCycle MCP benefits at a glance Fewer context switches, faster cycles : Stay in your editor/assistant and speak the task; it handles the rest. Safer changes, clearer history : Toggle targeting or update rules with confirmations, then trace everything with audit logs. Better integration : Because the DevCycle MCP can run locally or remotely, you can easily create your own service that leverages the MCP for customized workflows, like cross-referencing an Observability tool MCP with the DevCycle MCP to confirm if a flag change caused an incident. Standards‑aligned : Plays nicely with OpenFeature SDKs and providers across your stack. Get started (in under 2 minutes) Pick your favorite AI agent and follow the instructions. For more detailed getting-started instructions, you can check out our docs . Cursor Install in Cursor Or add to ~/.cursor/mcp_settings.json : { "mcpServers": { "DevCycle": { "url": "https://mcp.devcycle.com/mcp" } } } Then open Cursor Settings → Rules and Integrations → Click Needs Login to authorize (select your org if prompted). VS Code Install in VS Code Or add to .continue/config.json : { "mcpServers": { "DevCycle": { "url": "https://mcp.devcycle.com/mcp" } } } Start the server in VS Code’s MCP panel, accept the auth dialog, and finish in your browser. Claude Code Open your terminal and run: claude mcp add --transport http devcycle https://mcp.devcycle.com/mcp In Claude Code, type: /mcp Select devcycle → Enter to login and complete the OAuth flow in your browser. When you return, the server will show as connected. Prefer running the MCP locally? Install the CLI ( npm i -g @devcycle/cli ) and point clients at the bundled local dvc MCP server. Env‑var auth is supported for CI/CD. What can you ask the DevCycle MCP to do? The DevCycle MCP provides a complete selection of tools and prompts that together enable these popular use cases, among others: Feature Creation When creating a new feature in your code, you typically have to go back and forth between your IDE and DevCycle to create a Feature, get the relevant Variable for your code, implement that Variable and then wrap your code in the conditional. If you're using a coding agent to create the feature, it may make incorrect decisions about how to implement feature flags. With the DevCycle MCP installed, your coding agent can handle the end-to-end of creating the Feature and Variable in DevCycle and then implement it in code to flag the new feature it started coding for you. QA Testing The DevCycle MCP enables natural language commands for configuring flags with DevCycle's self-targeting overrides . This gives your coding agent an understanding of the overrides set for your user and the ability to configure overrides on your behalf. Testing a new feature locally is as easy as telling your coding agent to toggle a flag on or off, or you can give it more complex instructions on how to configure multiple flags in tandem for you, all without updating any targeting rules. Audit Logging / Incident Research Let's say an incident just kicked off, and you're in the middle of trying to determine if a code deploy or a feature flag configuration change may have caused the issue. Instead of hunting down relevant audit logs in DevCycle, you can now ask your coding assistant to list all changes to the production environment within a 30-minute range. The DevCycle MCP will respond with all audit logs across all Features in your project filtered by your criteria, and then your coding agent can present that in an easy-to-digest way. Suppose you are running the MCP of an Observability tool in tandem. In that case, you can even have your coding agent cross-reference the errors to determine if any of the changes could plausibly have caused the issue, helping you and your team get to mitigation and resolution as quickly as possible. Flag Cleanup Cleaning up flags that are no longer needed is a tedious task that is often ignored in favor of new projects. This means that most teams that implement feature flags tend to keep those conditionals around longer than they would typically like. At DevCycle, we have already done a lot to help alleviate this problem, from providing Stale Feature Notifications to enabling easy automated cleanup of Variables via our CLI. The DevCycle MCP is aware of the statuses of all of your DevCycle Features, so now you can have it take all Completed Features, read the values that are being distributed, and have your coding agent replace the stale Variables in your code with the relevant static values. All you have to do is review the code. These are just a few examples of what you can do with the DevCycle MCP. To view all of the available tools, check out our reference docs . Try it out now Once you have installed and authenticated the DevCycle MCP, try asking your coding agent to: “Create a new feature flag called new-checkout-flow .” “List all features in my project.” “Enable targeting for header-redesign in development.” “Show evaluation analytics for the last 7 days.” "Show me all flag changes on August 18." About DevCycle DevCycle is the first OpenFeature‑native feature flag management platform - so you can ship faster without vendor lock‑in. The MCP server extends that developer‑first experience right into your AI tools. Try DevCycle Free Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://aws.amazon.com/contact-us/ | AWS Support and Customer Service Contact Info | Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Support › Contact AWS Contact AWS General support for sales, compliance, and subscribers Want to speak with an AWS sales specialist? Get in touch Chat online or talk by phone Connect with support directly Monday through Friday Request form Request AWS sales support Submit a sales support form Compliance support Request support related to AWS compliance Connect with AWS compliance support Subscriber support services Technical support Support for service related technical issues. Unavailable under the Basic Support Plan. Sign in and submit request Account or billing support Assistance with account and billing related inquiries Sign in to request Wrongful charges support Received a bill for AWS, but don't have an AWS account? Learn more Support plans Learn about AWS support plan options See Premium Support options AWS sign-in resources See additional resources for issues related to logging into the console Help signing in to the console Need assistance to sign in to the AWS Management Console? View documentation Trouble shoot your sign-in issue Tried sign in, but the credentials didn’t work? Or don’t have the credentials to access AWS root user account? View solutions Help with multi-factor authentication (MFA) issues Lost or unusable Multi-Factor Authentication (MFA) device View solution Still unable to sign in to your AWS account? If you are still unable to log into your AWS account please fill out this form. View form Additional resources Self-service re:Post provides access to curated knowledge and a vibrant community that helps you become even more successful on AWS View AWS re:Post Service limit increases Need to increase to service limit? Fill out a quick request form Sign in to request Report abuse Report abusive activity from Amazon Web Services Resources Report suspected abuse Amazon.com support Request Kindle or Amazon.com support View on amazon.com Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://youtu.be/t/privacy | - 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:48:37 |
https://blog.devcycle.com/page/2/ | DevCycle Blog (Page 2) Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Product Updates July 2024 Changelog At DevCycle, we're committed to delivering powerful feature management solutions that empower teams to safely and easily control their feature releases. In this blog post, we're excited to share two significant updates that will enhance your experience with DevCycle: Approval Workflows and a Vercel Edge Config Jul 31, 2024 2 min read OpenFeature Featured Migrating from In-House Feature Flagging with OpenFeature Discover how the OpenFeature standard and new Multi-Provider utility can help you migrate away from your in-house flagging solution. Jul 2, 2024 4 min read Product Updates June 2024 Changelog Welcome to our monthly changelog, where we share the latest feature updates and improvements from DevCycle. We're excited to bring you two significant updates that will enhance your feature management experience: OpenFeature Multi-Provider and the Web Debugger. To see more of what's coming or to request Jun 28, 2024 2 min read Outside Voices Introducing the OpenFeature Multi-Provider We are excited to announce the release of the OpenFeature “Multi-Provider” for JavaScript and NodeJS. This new provider allows developers to access multiple OpenFeature providers through a unified interface, with customizable strategies that reconcile inconsistencies between providers. The Multi-Provider supports use cases including provider migrations and long-term support for multiple Jun 20, 2024 Outside Voices Product Updates May 2024 Changelog Welcome to our May changelog, where we share the latest feature updates and improvements from DevCycle. This month, we've focused on enhancing our integrations, improving performance for server-side rendering, and introducing a new way to manage complex schedules and variations with Passthrough Rollouts. If you want to read May 31, 2024 2 min read OpenFeature Planting a (Feature) Flag at the Summit: Extending AlpineJS with OpenFeature & DevCycle Learn how to build a simple plugin that adds OpenFeature compliant feature flagging functionality to AlpineJS using the DevCycle Javascript SDK. May 16, 2024 20 min read OpenFeature Serving Up Feature Flags on an Airtable with OpenFeature In this blog post, I'll show you how to build a simple AirTable Provider for OpenFeature so you can upgrade from that quick snack to a more "filling" feature flag system, all while securing your seat at the DevCycle Buffet. May 1, 2024 11 min read Product Updates April 2024 Changelog Spring is in the air and we've got our April edition of the monthly changelog for you. This month features a DevCycle App for Slack, one of our most requested features, along with quite a few other improvements. Check out the details below. 🧵 DevCycle App for Slack We Apr 30, 2024 2 min read Case Studies Featured Netlify Case Study - A Nearly Painless Migration to DevCycle from LaunchDarkly Netlify is a leading front-end platform known for its innovative web development solutions that power thousands of websites all around the web. Continuously releasing new features to their developer community quickly and reliably is an integral part of the business where speed and accuracy are of great importance. In this Apr 23, 2024 4 min read Introducing Feature Obfuscation: Dark Launches Done Right Why It's Hard to Truly Dark Launch Feature flags are often used to hide upcoming features before release; this is the core premise of a dark launch. The idea is that you remove a feature from view or access in the UI and that is enough to conceal Apr 1, 2024 3 min read Product Updates March 2024 Changelog The snow is melting and we've got a small but mighty set of new functionality for you this month. 🥷 Feature Obfuscation Feature flags are often used to hide upcoming features before release. Normally, not showing the feature on a UI is enough to conceal it from users. However, Mar 31, 2024 2 min read OpenFeature DevCycle Co-founder Jonathan Norris Elected to OpenFeature Governance Committee as DevCycle Achieves Comprehensive OpenFeature SDK Support At Kubecon Paris 2024, DevCycle announces that Co-founder and CTO, Jonathan Norris, has been elected to the OpenFeature Governance Committee as DevCycle achieves comprehensive OpenFeature SDK support. This appointment solidifies DevCycle’s deep commitment to the OpenFeature project. Mar 20, 2024 1 min read Testimonials Jason Barry @ Netlify Talks Migrating to DevCycle Jason Barry, Senior Staff Frontend Engineer at Netlify shares the development strategies they used to make their feature flag platform migration an easy one. Mar 15, 2024 13 min read OpenFeature How OpenFeature Was the Key to Escaping Feature Flag Vendor Lock-in: A Vue.js Story Discover how we effortlessly transitioned a VueJS project to a new feature flag Provider in just a few lines of code thanks to OpenFeature. Mar 5, 2024 5 min read Product Updates February 2024 Changelog Welcome to February's edition of our product changelog. We had updates both big and small to the platform in the rare 29 days of February. This month primarily featured some updates to our Lifecycle functionality, as well as some great work on our SDKs. Feature Archiving We’re Feb 29, 2024 3 min read DevCycle is now SOC 2 Type 1 Compliant We are proud to announce DevCycle's achievement of SOC 2 Type 1 compliance, a vital step in our ongoing commitment to data security and privacy. This compliance underscores our dedication to safeguarding sensitive data and upholding the highest standards in data security. Feb 26, 2024 1 min read Product Updates DevCycle Becomes a CVE Numbering Authority We're thrilled to announce DevCycle has been officially authorized by the CVE Program as a CVE Numbering Authority (CNA). This marks a new chapter in our commitment to cybersecurity excellence and a safer digital world. Feb 15, 2024 2 min read OpenFeature Powering Up PHP Feature Flags with OpenFeature See just how easy it is to break free from vendor lock-in with OpenFeature in our latest blog post, where we detail the straightforward process of tweaking our PHP example app to embrace the OpenFeature standard. Feb 15, 2024 6 min read OpenFeature Unlocking the Power of Feature Flags with OpenFeature The popularity of feature flags has exploded in recent years, but it still faces some challenges to adoption. Discover how OpenFeature may be the answer to unlocking the power of feature flagging for the future. Feb 15, 2024 2 min read Product Updates January 2024 Changelog Welcome to a new blog, email and stream series that our Product team is running that aims to highlight what our team has built each month. We're really excited to share all of the things that we're working on, and hope that anyone with an interest Jan 31, 2024 3 min read Guides and Tutorials What We Learned From Developing DevCycle's Next.js SDK Building DevCycle's Next.js Feature Flagging SDK was a technical adventure filled with unique challenges and valuable learning experiences. As we navigated the intricacies of integrating feature flagging with Next.js's combination of client- and server-rendering, we encountered obstacles that pushed us to learn the inner Jan 25, 2024 7 min read Guides and Tutorials Building an Early Access Site with DevCycle's EdgeDB & Directus Flows When launching a new app, creating an early buzz is crucial. A well-crafted early access program can be the key to this. The challenge? Providing exclusive onboarding content to new users, while also securing their private data and building a foundation for scalability. Enter DevCycle and Directus. Jan 24, 2024 13 min read DevCycle's New Next.js SDK: Elevating Feature Flagging in Next.js Apps We're excited to announce our latest milestone: the launch of our first-class Next.js SDK. This SDK fully supports the latest features of Next.js, allowing you to work on the bleeding edge with a seamless feature flagging experience. Jan 23, 2024 3 min read Outside Voices Build a DevCycle Feature Flag Control Panel in Directus Learn how to build a custom panel extension in Directus that integrates with DevCycle's API. This allows non-technical users to manage feature flags directly from the Directus Insights Dashboard. Originally published on the Directus blog, read more here. Jan 3, 2024 Outside Voices Beta Testing Explained It's a best practice to get customer feedback before releasing products to end-users. Beta testing is a method of testing to get an honest, accurate overview of how your software product is working with real users. Dec 31, 2023 2 min read ← Newer Posts Page 2 of 3 Older Posts → DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/5-steps-to-a-continuous-deployment-culture/ | 5 Steps to a Continuous Deployment Culture Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Guides and Tutorials 5 Steps to a Continuous Deployment Culture Mark Allen Mar 28, 2025 • 11 min read Deploying software into production so that your users can access it is one of the key areas of software development. Whether you are a two-person start-up using the latest tools and frameworks, a small business integrating multiple SaaS applications, or an enterprise business with 40 years of legacy systems to maintain, the work your development team isn’t fulfilled until it’s in the hands of users. To do this well requires a commitment to it. Not just by a few, but by everyone. From the top of the management team to the newest developer, everyone needs to understand that the commitment to Continuous Deployment is critical to the ongoing success of the company. Too many teams are unable to deploy quickly to production; they haven’t invested in the people, processes, and most importantly, the culture of their company. Those companies that invest in making it easy for their developers to get their work into production are able to adapt quickly to changing markets, fix security vulnerabilities, address bugs reported by their users, and make their development teams happier. Continuous Deployment is a Culture You don’t just do continuous deployment; you live it. Everything your team does aligns with it. It has to be part of your culture, but it can’t happen by default; it has to be by design. You can’t get to Continuous Deployment (CD) overnight. Trying to do so will create a broken process, resentment by the team, and most likely a broken application. If you are just getting started with a CI/CD pipeline, or if you have been running one for years, you need a plan to get to CD. This article will outline five steps that a team, department, or organization can take to move the culture to one that embraces change through CD. 1. State it as a goal and talk about it all the time. Align it with a team or company value. 2. Start with continuous delivery. Deploy once a week, then twice, then daily. 3. Fix what is preventing continuous deployment. Whether it’s a slow build pipeline, flaky tests, or a hard-to-manage local development environment, invest in your team’s workflow. Do whatever it takes to remove the barriers to making it continuous. 4. Collect DORA metrics and show them at every meeting 5. Engage with the rest of the company and tell everyone you can that “we release to production multiple times a day.” With these steps, teams have gone from deploying once every three months to multiple times per day, from being leery of continuous deployment to it being just part of what they do. You too can do CD. You have to make it part of the culture. State it as a Company Goal Continuous deployment is part of the culture not only within the development team but the entire company. Many teams are stuck in their current release process because they don’t know a path forward, are leery of this kind of change, or can’t see that it will make any impact. They release their software every 3 months, instead of every hour. Individual developers will have ideas on how to get out of the current situation, but it’s the role of leadership to bring this change to the team. To get to CD, that goal needs to be started in a way that everyone on the team can understand and that they can make an impact upon. 1. State it as a goal and talk about it all the time. Align it with a team or company value. You can’t get to CD without first painting the picture for the team. Deploying code should be done without ceremony or notice. The goal is that each aspect of the build pipeline should work without failing or giving false positives. This way, the team and the company have trust in the process. A developer’s job is to write code and merge it to main, and that’s the last they see or hear of it. Now, this is obviously an overstatement of what a developer’s job is when it comes to taking care of the application or components they are responsible for, but if you set this as a goal, then when it’s working, your developers will have time to focus on features and bugs and not infrastructure. With these two ideas as your vision, you need to talk about it all the time. You need to bring it up in every meeting: Architecture review; how do we automate this to do it continuously? Sprint planning; can we feature flags this new work to release it right now? Retros; can we fix those flaky tests? By talking about it all the time, the questions about what, why, and how will come out. You’ll need to address each of these questions in turn. They will also set your strategy and resourcing to implement this change. Culture is either by default or by design. Moving to CD is a change in culture and will require buy-in across the team and the company. So in order to get there, you’ll need to design the culture around the change. For this type of shift, pick one of your company or team’s values that aligns with CD. This will help you frame why the work is going on in terms that anyone in the company can understand. If the team has concerns around the stability of the application, dedicate more time to writing automated end-to-end tests and implement feature flags to turn code on and off. If issues with failed builds or deployments arise, then invest in refactoring the build pipeline and invest in more infrastructure. If you believe it can’t be done in your industry or technology stack, then bring in other development leaders in your industry or technology who have done this. As a leader, you’ll get pushback, but keep to the vision and start to adjust the culture. Make sure you spend the time bringing the thought leaders, senior technologists, product managers, and business owners onboard with your vision. For some companies or teams, this will take a week or two; for larger enterprises, this can take months or years. If it’s the latter, then find a digital transformation project and become a part of it. They will be looking for ways to bring change to the company, and CD and the value it brings is certainly that kind of change. It’s easy to just think about only the development team caring about CD, but actually, it’s everyone. Make sure that your product managers know you’ll be able to address issues quickly, get new features in the hands of users early, and increase the stability of the applications. For your business owners, they will be able to get bugs fixed quickly, know that you can rapidly address changes in business, and create a better experience for the users. You are embarking on creating value for the company, so bring everyone onboard with you. People will doubt that it can be done without major issues or impact, but enrolling everyone into this change will help in the long run. By setting the vision of deploying multiple times per day without ceremony, talking about CD all the time, and aligning it with one of your company’s values, you can start the journey. However, that’s the easy part; the following steps are the actual work. Start with Continuous Delivery Now that you have set the stage for your team with the vision of continuous deployment, it’s time to put that vision to the test. 2. Start with continuous delivery. Deploy once a week, then twice, then daily. You most likely are already doing continuous delivery. How does that differ from continuous deployment? Well, in continuous delivery, someone needs to do something to make it go live. It can be as simple as pressing a button on a webpage or invoking a GitHub action. But with CD, it happens automatically. After code is approved, it is merged into version control, it is built, tested, and deployed to production. The reason to get started with continuous delivery is that your team needs to get into the cadence of delivering code often and automatically. Your systems need to be improved to allow for the appropriate amount of guardrails so that buggy code doesn’t make it to production. It isn’t going to be easy, and you are going to cause some issues with your application. It is essential to learn from each of these mistakes and then apply those learnings to getting it right the next time. The first step is to automate the deployment process and remove the humans from getting the code into production. Look at everything, from builds to tests to deploying the code into production; it all must be automated. The next thing to do is to put in place a rollback. You must know that if something goes monumentally wrong, you can quickly return to the previous working version. This process also helps determine what in your processes won’t work for CD. For example, if you make breaking changes in your database or API schemas, you need to stop doing that and move to using non-breaking changes. Now that you can deploy your code with nothing more than a single action and can roll back, all the issues with this process will come to light. It is an excellent time to implement some DORA metrics, primarily deployment frequency and lead time for change. These need to be visible to everyone and talked about often. More on that later. The more work you put into automating the release process, the more often you can do continuous delivery. The next step is to change the cadence of releases to once a sprint, once a week, and eventually once a day. Since you talk about the vision in all your meetings, you’ll see where your process prevents continuous delivery from happening. You must speed up the build process and harden those flakey tests. More on that in the next step. Fix What is Broken Now some of the most challenging work begins, getting rid of all the roadblocks that are preventing continuous deployment. 3. Fix what is preventing continuous deployment. Whether it’s a slow build pipeline, flaky tests, or a hard-to-manage local development environment, invest in your team’s workflow. Do whatever it takes to remove the barriers to making it happen. The biggest complaint from developers is that their productivity is negatively impacted by things they perceive as outside their control. Such as flaky tests or a flaky test environment. Slow or under-resourced build servers. A local development environment that doesn’t work for them. These are all valid complaints but are entirely within the control of your team. Too much focus on getting the next release or feature out, your team is missing the forest for the trees. If you want to speed up something, you have to invest the time and effort in finding where it’s not working and fixing that. If your team doesn’t believe that they are in control of these things, then this is the time to roll up your sleeves and work on the code directly. This isn’t a time for you to build a new feature, but to take on something small, such as a bug, and go through the process of fixing it and releasing it to production. Each step of the way, you’ll live the pain your team feels. Since you are talking about CD all the time, have experienced the problems with the process, and now doing continuous delivery, give your team the time and space to fix the things that make their life difficult. Have them fix the flaky tests. Invest in larger machines for the build process. Tear down and rebuild from scratch the local development environment. You’ve seen where the pain is firsthand; go out and help them fix it. Start to look at your DORA metrics for deployment frequency and lead time. Dig into why the numbers are what they are. Gather the data on build times, determine which tests fail the most, and run the development environment as your developers do. Be the one who identifies these issues in your retrospectives, pull out the wins, and identify the remaining bottlenecks. Once that is done, switch over to doing CD and see how it goes. Collect DORA Metrics Now, as development manager, are you leading the charge to get to CD? It’s time to reap its benefits. 4. Collect DORA metrics and show them at every meeting. The act of actually collecting DORA metrics means you are doing a lot of things right. The best metric to start with is Deployment Frequency. Since you are already doing CD, you can add a step to your process to log successful deployments. Deployment Frequency is a canary metric; a slowdown in deployment frequency indicates something broken in your development process. The next one to tackle is Lead Time for Change, how long it takes for a commit to get deployed to production. This takes a little more work to extract this from version control, but the data is in there so you can get it out. There are some nuances to exactly what commit to use; the first commit in a branch is a good one. This metric is not designed to show how long it takes for a developer to build a feature but to measure how much time it takes for that feature, once completed, to get into production; the time it takes to build, test, review, and finally deploy. Lead Time for Change will show you where the bottlenecks are in your process and will give time back to your developers to build software. Change Failure Rate measures the percentage of deployments that cause a failure in production. The question you need to ask yourself before you start to collect this metric is “what is a failure in production?”. Is it the site or app crashing, a single service being unavailable, or a reduction in a service level agreement (SLA) metric? This metric requires the input of other teams who manage the application, deal with outages, and customer support issues. Then there is Mean Time to Recovery (MTTR), how long it takes for the application to recover from a failure. Again, it is critical to know what a failure is, and then what a recovery looks like. MTTR and Change Failure Rate processes are very closely related to each other; once you have one, you’ll get the other. Now that you have these metrics, it’s time to talk about them all the time. Every meeting you have, you need to show them. In the early days, ask team members to define each one as a way to reinforce what they are and how they are collected. Most importantly, these are not measurements of individual developers or the team; they are a measurement of your process. They reflect upon you. If they are not where you want them to be, you are the one to fix them. With the metrics understood by your team, you can now set goals to improve them. You can experiment with changing your processes and see how they impact each metric. With DORA metrics, you can create a path to improvement. Engage the Entire Organization With the DORA metrics, you now have time to let everyone know what your team is capable of. 5. Engage with the rest of the company and tell everyone you can that “we release to production multiple times a day.” Most development teams do not do CD; they bundle code into a release and then deploy it to their customers. Instead, they deploy once a week, once a month, or, more likely, once a quarter. After following the five steps I laid out, you should now be deploying to production multiple times per day. Of course, there are bumps along the way, but you now have a software development process based on automation and, most importantly, trust. You are now doing what most engineering teams can’t or won’t do, so let everyone inside your company know. By being able to deploy at any time, you are in a far better position to fix bugs that creep into the application. You can use more advanced development techniques, such as Feature Flags and real-time debugging. You can also now address security issues in your underlying frameworks in hours, not weeks. From your team’s perspective, they now have a build pipeline that runs efficiently and is maintained. Your tests test what they need to and don’t return false positives. Their collaboration is higher as they can see changes in their code quickly and work together to bring new features to your users. Conclusion Following the 5 steps outlined here will get you to being able to do CD and along the way help embed it into your team’s and company’s culture. It is not something that can be forgotten about but will need continuous validation, input, and updates from the team, but just like with writing tests to ensure code runs as expected in the future, maintaining a solid CD pipeline will allow you to deploy code whenever you need to. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://blog.devcycle.com/recipe-for-change/ | Recipe for Change: Unlocking Feature Flag Flexibility in a Hyperapp with OpenFeature and the Multi-Provider Utility Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature Recipe for Change: Unlocking Feature Flag Flexibility in a Hyperapp with OpenFeature and the Multi-Provider Utility DevCycle Aug 6, 2024 • 9 min read Photo by S O C I A L . C U T / Unsplash Are your feature flags as flexible as they could be? If they are hard-coded static configurations, the answer is likely no. In this guide, we'll explore how OpenFeature can unlock the full potential of feature flags using a fun (although maybe impractical) example—a Recipe Manager app where filters and layouts are controlled entirely by feature flags 🚩. Leveraging the Hyperapp framework , which powers our Recipe Manager, we'll guide you through improving your feature flag implementation with the OpenFeature standard, demonstrating how these enhancements can streamline upgrading to a new feature flag management solution. By the end, we hope you'll understand how to manage feature flags effectively and migrate between providers seamlessly. GitHub - jorgebucaran/hyperapp: 1kB-ish JavaScript framework for building hypertext applications 1kB-ish JavaScript framework for building hypertext applications - jorgebucaran/hyperapp GitHub jorgebucaran Basic "Feature Flags" Before diving into OpenFeature, let's present a basic setup you might see in the wild. In this example, we're using static configurations—hard-coded settings that don't offer the flexibility of true feature flags. We'll be transitioning these to dynamic feature flags as we move through this guide. ⤵️ Want to jump straight into the OpenFeature setup? Click here! Initial Setup Here's the basic structure of our Recipe Manager app using Hyperapp: RECIPE-APP/ │ ├── node_modules/ # Contains all npm packages │ ├── public/ │ └── index.html # The main HTML file served by the application │ ├── src/ # Source files for the application │ └── index.js # Entry point of the application, initializes the app │ ├── package-lock.json # Auto-generated file for locking dependencies versions ├── package.json # Defines project dependencies and scripts └── README.md # Project documentation To get started with this application, you'll need to install the necessary dependencies. Here's the package.json configuration: { "name": "hyperapp-recipe-migration", "version": "0.0.0", "dependencies": { "@devcycle/openfeature-web-provider": "^0.14.1", "@openfeature/multi-provider-web": "^0.0.2", "@openfeature/web-sdk": "^1.2.1", "hyperapp": "^2.0.22" }, "scripts": { "start": "hyperapp-scripts start", "build": "hyperapp-scripts build", "test": "hyperapp-scripts test" }, "eslintConfig": { "extends": "react-app", "rules": { "react/react-in-jsx-scope": "off", "no-unused-vars": [ "warn", { "varsIgnorePattern": "^h$" } ] } }, "browserslist": { "production": [ ">0.2%", "not dead", "not op_mini all" ], "development": [ "last 1 chrome version", "last 1 firefox version", "last 1 safari version" ] }, "devDependencies": { "hyperapp-scripts": "^0.7.0" } } After setting up the project and installing dependencies, add some basic structure to the index.html : <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"/> <meta name="viewport" content="width=device-width, initial-scale=1"/> <script src="https://cdn.tailwindcss.com"></script> <script> tailwind.config = { darkMode: 'selector' } </script> <title>Hyperapp Recipe Manager </title> </head> <body> <div id="app"></div> </body> </html> With this complete, head over to index.js , where the actual Hyperapp magic will happen. You'll define your feature flags and apply them to the application logic: import { app } from "hyperapp"; // Basic "Feature Flags" (aka Static Configs) const featureFlags = { dark_mode: true, // boolean app_language: "en", // string max_recipes: 3, // number recipe_layout: { // JSON layout: "one-column", showIngredients: true, showInstructions: true } }; // Apply dark mode based on the feature flag if (featureFlags.dark_mode) { document.body.classList.add("dark"); } // Sample recipes in English and French const recipes = [ { id: 1, name: { en: "Tacos", fr: "Tacos" }, ingredients: { en: "Taco shells, Ground beef, Cheese", fr: "Coques de tacos, Bœuf haché, Fromage" }, instructions: { en: "Cook ground beef, add to shells, and top with cheese.", fr: "Cuire le bœuf haché, ajouter dans les coques, et garnir de fromage." } }, { id: 2, name: { en: "Burgers", fr: "Burgers" }, ingredients: { en: "Buns, Ground beef, Lettuce", fr: "Pains, Bœuf haché, Laitue" }, instructions: { en: "Cook ground beef, add to buns with lettuce.", fr: "Cuire le bœuf haché, ajouter aux pains avec de la laitue." } }, { id: 3, name: { en: "Pizza", fr: "Pizza" }, ingredients: { en: "Dough, Tomato sauce, Cheese", fr: "Pâte, Sauce tomate, Fromage" }, instructions: { en: "Spread sauce on dough, top with cheese, and bake.", fr: "Étaler la sauce sur la pâte, garnir de fromage, et cuire au four." } } ]; const RecipeItem = ({ recipe, flags }) => ( <div class="p-4 mb-4 bg-gray-100 rounded shadow-md"> <h2 class="text-xl font-semibold">{recipe.name[flags.app_language]}</h2> {flags.recipe_layout.showIngredients && ( <p class="mt-2"> <strong>Ingredients:</strong> {recipe.ingredients[flags.app_language]} </p> )} {flags.recipe_layout.showInstructions && ( <p class="mt-2"> <strong>Instructions:</strong> {recipe.instructions[flags.app_language]} </p> )} </div> ); const RecipeList = ({ flags }) => { const filteredRecipes = recipes.slice(0, flags.max_recipes); return ( <div class={`grid ${flags.recipe_layout.layout === "two-column" ? "grid-cols-2 gap-4" : "grid-cols-1"}`}> {filteredRecipes.map(recipe => ( <RecipeItem recipe={recipe} flags={flags} /> ))} </div> ); }; const mainView = state => ( <div class={`min-h-screen p-4 ${state.flags.dark_mode ? "dark" : ""}`}> <h1 class="text-3xl font-bold mb-4">Recipe Manager</h1> <RecipeList flags={state.flags} /> </div> ); app({ init: { flags: featureFlags }, view: mainView, node: document.getElementById("app") }); Now, head to your terminal and start the application by running: npm start If everything is running correctly, you should see something like this: Transition to OpenFeature OpenFeature provides a standardized way to manage feature flags, making it easier to handle different evaluation logic and management systems. Getting your flags to follow the OpenFeature standard is the first step in the enhancement process. For our Recipe Manager app, we'll start by converting our static configs to the required format which can be ingested by the OpenFeature API. OpenFeature OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool or in-house solution. OpenFeature Logo OpenFeature Configuration First, we'll define our feature flags in the OpenFeature format: const FLAG_CONFIGURATION = { 'dark-mode': { variants: { on: true, off: false }, disabled: false, defaultVariant: 'on' }, 'app-language': { variants: { en: 'en', fr: 'fr' }, disabled: false, defaultVariant: 'en' }, 'max-recipes': { variants: { one: 1, three: 3 }, disabled: false, defaultVariant: 'three' }, 'recipe-layout': { variants: { 'one-column': { layout: 'one-column', showIngredients: true, showInstructions: true }, 'two-column': { layout: 'two-column', showIngredients: true, showInstructions: false }, }, disabled: false, defaultVariant: 'one-column' }, }; Update the Application Next, we'll update the application to use these OpenFeature-compliant flags. This involves a few steps: Install the OpenFeature Web SDK: npm install --save @openfeature/web-sdk Apply the newly created flag format to an In-memory Provider and set that provider for our OpenFeature client. This is provider is primarily used for testing but for our case it will serve as an example of an "in-house" feature flag management system. Assign an evaluation context against which the flags will be evaluated. In our case, this will be the user_id . Below you can see what all of this looks like in context. import { app } from "hyperapp"; + import { InMemoryProvider, OpenFeature } from "@openfeature/web-sdk"; - // Basic Feature Flags - const featureFlags = { - dark_mode: true, // boolean - app_language: "en", // string - max_recipes: 5, // number - recipe_layout: { // JSON - layout: "two-column", - showIngredients: true, - showInstructions: true - }, - }; + // OpenFeature Compliant Feature Flags + + // Configure InMemory Provider + const FLAG_CONFIGURATION = { + // Configuration format as indicated above + // ... + }; + const inMemoryProvider = new InMemoryProvider(FLAG_CONFIGURATION); + await OpenFeature.setProviderAndWait(inMemoryProvider); + + // Add Evaluation Context + const user = { user_id: "my_user" }; + OpenFeature.setContext(user); + + // Instantiate a new OpenFeature Client + const client = OpenFeature.getClient(); + + // Use OpenFeature API to Evaluate Feature Flags + const featureFlags = { + dark_mode: client.getBooleanValue("dark-mode", false), + app_language: client.getStringValue("app-language", "en"), + max_recipes: client.getNumberValue("max-recipes", 3), + recipe_layout: client.getObjectValue("recipe-layout", { + layout: "one-column", + showIngredients: false, + showInstructions: false, + }), + }; // Rest of the code remains unchanged // ... With this setup, our Recipe Manager app now implements the OpenFeature standard for managing feature flags. This provides a more scalable and maintainable solution and allows us to access the Universal API. Configuring Multi-Provider Utility With OpenFeature, switching feature flag management systems ( or switching between static configs and dynamic feature flags ) is simply a case of changing the Providers. In many cases, to do this requires only a few lines of code to be changed. The most crucial change is to set the Provider using: await OpenFeature.setProviderAndWait(<YOUR PROVIDER>); While this approach works for basic cases, the new Multi-Provider utility extends this capability, allowing more seamless provider migrations with little-to-no downtime. It also supports special use cases, such as long-term support for multiple feature flag sources. This ensures that your application can handle transitions and maintain compatibility with various feature flag providers efficiently. OpenFeature Multi-Provider Release | OpenFeature Introducing an OpenFeature Multi-Provider for Node.js and JavaScript OpenFeature Logo Emma Willis Multi-Provider Setup Similar to before, there are a few steps needed to use the Multi-Provider: Install the DevCycle JavaScript SDK and OpenFeature Web Provider alongside the OpenFeature Web Multi-Provider. npm install --save @devcycle/openfeature-web-provider && npm install @openfeature/multi-provider-web Instantiate a DevCycle Provider and a new Multi-Provider instance. import { app } from "hyperapp"; import { InMemoryProvider, OpenFeature } from "@openfeature/web-sdk"; + import DevCycleProvider from "@devcycle/openfeature-web-provider"; + import { WebMultiProvider } from "@openfeature/multi-provider-web"; const FLAG_CONFIGURATION = { // Configuration format remains the same as above // ... }; const inMemoryProvider = new InMemoryProvider(FLAG_CONFIGURATION); + const devcycleProvider = new DevCycleProvider( + "dvc_client_key" + ); + + // Multi-provider Setup + const multiProvider = new WebMultiProvider([ + { provider: devcycleProvider }, + { provider: inMemoryProvider }, + ]); - await OpenFeature.setProviderAndWait(inMemoryProvider); + await OpenFeature.setProviderAndWait(multiProvider); // Rest of the code remains unchanged // ... By following these steps, you've now implemented a full feature flag management system (i.e. DevCycle) and through the Multi-provider enabled your application to switch seamlessly between the hard-coded, static configs and the dynamic DevCycle feature flags. To make this process so seamless, behind the scenes the Multi-provider is using a default FirstMatchStrategy evaluating providers in order, moving on to the next provider only if the current provider returns a FLAG_NOT_FOUND result. If an error is thrown by any provider, the Multi-Provider will throw that error. The OpenFeature SDK will then catch the error and return the default value. While the default strategy is generally recommended for vendor migration, a special DevCycleMigrationStrategy has been created specifically for migrating to DevCycle. This strategy extends FirstMatchStrategy to accommodate DevCycle's implementation by returning DEFAULT for "flag not found" cases. import { app } from "hyperapp"; import { InMemoryProvider, OpenFeature } from "@openfeature/web-sdk"; import DevCycleProvider from "@devcycle/openfeature-web-provider"; import { WebMultiProvider } from "@openfeature/multi-provider-web"; + import { DevCycleMigrationStrategy } from "@devcycle/openfeature-web-provider/strategy"; const FLAG_CONFIGURATION = { // Configuration format remains the same as above // ... }; const inMemoryProvider = new InMemoryProvider(FLAG_CONFIGURATION); const devcycleProvider = new DevCycleProvider( "dvc_client_key" ); // Multi-provider Setup const multiProvider = new WebMultiProvider( [ { provider: devcycleProvider }, { provider: inMemoryProvider }, ], + new DevCycleMigrationStrategy() ); await OpenFeature.setProviderAndWait(multiProvider); // Rest of the code remains unchanged // ... ⚠️ To effectively use this strategy with DevCycle, ensure that all targeting rules include an "All Users" rule. This will prevent the return of DEFAULT for known keys. Next Steps for Your Recipe App Migration With the new strategy in place, your Recipe app codebase is ready for migration, but there are a few additional steps to complete: Port Your Data: Transfer the existing flagging data to DevCycle. This means moving flag definitions, user targeting rules, and any associated metadata. You can do this gradually by creating new flags in DevCycle while keeping the old ones until they are no longer needed. This is also a great chance to clean up outdated flags. Establish a Migration Timeline: Create a detailed timeline for the migration. Prioritize critical flags first and schedule less critical ones for later. Implement Monitoring and Logging: Set up monitoring and logging to track the performance and accuracy of flag evaluations. This will help identify and resolve any issues during the migration. Test and Validate: Before fully transitioning to DevCycle, conduct thorough testing to ensure: Flag evaluations return expected results. Performance is not negatively impacted. There are no regressions in existing functionality. By following these steps, you can ensure a smooth transition to DevCycle and take full advantage of its powerful feature management capabilities. Try It Yourself! Ready to see it in action? Visit our GitHub repository and try migrating feature flags for yourself. Follow the instructions in the README to set up the Recipe Manager app and experiment with different feature flag configurations. GitHub - DevCycleHQ-Sandbox/hyperapp-recipe-migration: Hyperapp OpenFeature Recipe Manager Hyperapp OpenFeature Recipe Manager. Contribute to DevCycleHQ-Sandbox/hyperapp-recipe-migration development by creating an account on GitHub. GitHub DevCycleHQ-Sandbox Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://aws.amazon.com/vi/api-gateway/ | Amazon API Gateway | Quản lý API | Amazon Web Services Chuyển đến nội dung chính Nhấp vào đây để quay lại trang chủ Amazon Web Services Giới thiệu về AWS Liên hệ với chúng tôi Hỗ trợ Tiếng Việt Tài khoản của tôi Đăng nhập Tạo tài khoản AWS Đóng Hồ sơ Hồ sơ của bạn giúp cải thiện tương tác với một số AWS Experience được chọn. Đăng nhập Đóng Hồ sơ Hồ sơ của bạn giúp cải thiện tương tác với một số AWS Experience được chọn. Xem hồ sơ Đăng xuất Amazon Q Sản phẩm Giải pháp Định giá Tài liệu Tìm hiểu Mạng lưới đối tác AWS Marketplace Tiếp cận khách hàng Sự kiện Khám phá thêm Đóng عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) Đóng Hồ sơ của tôi Đăng xuất khỏi AWS Builder ID Bảng điều khiển quản lý AWS Thiết lập tài khoản Quản lý hóa đơn và chi phí Thông tin xác thực bảo mật AWS Personal Health Dashboard Đóng Trung tâm Hỗ trợ Trợ giúp từ chuyên gia Trung tâm kiến thức Tổng quan về Hỗ trợ AWS AWS re:Post Nhấp vào đây để quay lại trang chủ Amazon Web Services Bắt đầu sử dụng miễn phí Liên hệ với chúng tôi Sản phẩm Giải pháp Giá cả Giới thiệu AWS Bắt đầu Tài liệu Đào tạo và chứng nhận Trung tâm dành cho nhà phát triển Thành công của khách hàng Mạng lưới đối tác AWS Marketplace Hỗ trợ AWS re:Post Đăng nhập vào Bảng điều khiển Tải xuống ứng dụng di động Amazon API Gateway Tổng quan Tính năng Giá cả Bắt đầu Tài nguyên Câu hỏi thường gặp Đối tác Sản phẩm › Kết nối mạng và phân phối nội dung › Cổng API Amazon Nhận 1 triệu lệnh gọi API miễn phí mỗi tháng trong vòng 12 tháng với Bậc miễn phí của AWS Amazon API Gateway Tạo, duy trì và bảo vệ API ở mọi quy mô Bắt đầu sử dụng Cổng API Tại sao nên chọn Cổng API? Amazon API Gateway là dịch vụ được quản lý hoàn toàn giúp các nhà phát triển dễ dàng tạo, phát hành, duy trì, giám sát và bảo vệ API ở mọi quy mô. API đóng vai trò là "cửa trước" cho các ứng dụng để truy cập dữ liệu, logic nghiệp vụ hoặc chức năng từ các dịch vụ backend của bạn. Bằng cách sử dụng API Gateway, bạn có thể tạo các API RESTful và API WebSocket để kích hoạt các ứng dụng giao tiếp hai chiều theo thời gian thực. API Gateway hỗ trợ các khối lượng công việc có trong container và serverless, cũng như các ứng dụng web. API Gateway xử lý tất cả các tác vụ liên quan đến tiếp nhận và xử lý lên đến hàng trăm nghìn lệnh gọi API đồng thời, bao gồm quản lý lưu lượng truy cập, hỗ trợ CORS, xác thực và kiểm soát truy cập, điều tiết, giám sát và quản lý phiên bản API. API Gateway không yêu cầu phí tối thiểu hoặc phí ban đầu. Bạn trả tiền cho các lệnh gọi API bạn nhận được cũng như lượng dữ liệu được truyền đi và, với mô hình định giá theo bậc của API Gateway, bạn có thể giảm chi phí khi thay đổi quy mô sử dụng API. API RESTful Xây dựng các API RESTful được tối ưu hóa cho khối lượng công việc serverless và backend HTTP bằng API HTTP. API HTTP là lựa chọn tốt nhất để xây dựng những API chỉ yêu cầu chức năng proxy API. Nếu API của bạn yêu cầu cả chức năng proxy API lẫn tính năng quản lý API trong cùng một giải pháp thì Cổng API cũng cung cấp cả API REST . API WEBSOCKET Xây dựng các ứng dụng giao tiếp hai chiều theo thời gian thực, chẳng hạn như ứng dụng trò chuyện và bảng điều khiển truyền phát bằng API WebSocket . API Gateway duy trì kết nối lâu dài để xử lý quá trình truyền tin nhắn giữa dịch vụ backend và máy khách của bạn. Page topics Lợi ích Lợi ích Open all Phát triển API hiệu quả Chạy đồng thời nhiều phiên bản của cùng một API với API Gateway, từ đó cho phép bạn lặp lại, kiểm tra và phát hành các phiên bản mới một cách nhanh chóng. Bạn trả tiền cho các lệnh gọi được thực hiện với các API của mình và chuyển dữ liệu ra và không có lệ phí tối thiểu hay cam kết trả trước. Hiệu quả ở mọi quy mô Cung cấp cho người dùng cuối độ trễ thấp nhất có thể cho các yêu cầu và phản hồi API bằng cách tận dụng mạng lưới các vị trí biên bằng cách sử dụng Amazon CloudFront. Điều tiết lưu lượng truy cập và cấp phép các cuộc gọi API nhằm đảm bảo rằng các hoạt động backend chịu được các lưu lượng truy cập tăng đột biến và các hệ thống backend không được gọi một cách không cần thiết. Tiết kiệm chi phí ở quy mô lớn API Gateway cung cấp mô hình giá theo bậc cho các yêu cầu API. Với mức giá API thấp 0.90 USD trên một triệu yêu cầu ở bậc cao nhất, bạn có thể giảm chi phí khi mức độ sử dụng API tăng lên trên mỗi khu vực trong toàn bộ các tài khoản AWS. Theo dõi dễ dàng Giám sát các số liệu về hiệu năng và thông tin về các lệnh gọi API, độ trễ dữ liệu và tỷ lệ lỗi từ bảng điều khiển API Gateway, nhờ đó bạn có thể giám sát trực quan các lệnh gọi đến dịch vụ của bạn thông qua Amazon CloudWatch . Kiểm soát bảo mật linh hoạt Cho phép truy cập các API của bạn bằng Quản lý danh tính và truy cập trong AWS (IAM) và Amazon Cognito. Nếu bạn sử dụng token OAuth, API Gateway có hỗ trợ OIDC gốc và OAuth2. Để hỗ trợ các yêu cầu cấp phép tùy chỉnh, bạn có thể thực thi trình cấp quyền Lambda từ AWS Lambda . Tùy chọn API RESTful Tạo API RESTful bằng API HTTP hoặc API REST. API HTTP là cách tốt nhất để xây dựng API cho hầu hết các trường hợp sử dụng. Các này rẻ hơn tới 71% so với API REST. Nếu bạn cần chức năng proxy API và các tính năng quản lý trong cùng một giải pháp cho trường hợp sử dụng của mình, bạn có thể dùng API REST. WirelessCar Tìm hiểu cách WirelessCar, nhà cung cấp dịch vụ di chuyển được kết nối, nâng cao hiệu năng của công ty khởi nghiệp này bằng cách sử dụng AWS Lambda SnapStart dành cho Java. Đọc nghiên cứu điển hình Odyssey Interactive Tìm hiểu cách studio trò chơi Odyssey Interactive ra mắt trò chơi nhiều người chơi đầu tiên của mình, Omega Strikers, trên toàn thế giới bằng cách sử dụng cơ sở hạ tầng được quản lý trên AWS. Đọc nghiên cứu điển hình Betterfly Tìm hiểu cách Betterfly đơn giản hóa việc bảo vệ nhóm và quản lý lợi ích cũng như khuyến khích thói quen tích cực hàng ngày bằng cách sử dụng giải pháp kỹ thuật số được xây dựng trên AWS. Đọc nghiên cứu điển hình TiVo Tìm hiểu cách TiVo, một đơn vị trong ngành truyền thông và giải trí, đạt được khả năng điều chỉnh quy mô có thể mở rộng ổn định và thời gian hoạt động nhất quán cho các dịch vụ phát trực tuyến bằng cách sử dụng AWS Lambda và Cổng API Amazon. Đọc nghiên cứu điển hình Bắt đầu sử dụng Cổng API 1 Đăng ký tài khoản AWS Nhận ngay quyền sử dụng Bậc miễn phí của AWS . 2 Tìm hiểu qua hướng dẫn từng bước Khám phá và tìm hiểu thông qua những hướng dẫn đơn giản . 3 Bắt đầu dựng với AWS Truy cập Bảng điều khiển quản lý AWS . Các bước tiếp theo Feature Page Tìm hiểu thêm về API Gateway Truy cập trang tính năng Bắt đầu Bạn đã sẵn sàng xây dựng chưa? Bắt đầu Contact us Bạn có thêm câu hỏi? Liên hệ với chúng tôi Đăng nhập vào bảng điều khiển Tìm hiểu về AWS AWS là gì? Điện toán đám mây là gì? Khả năng truy cập AWS Sự hòa nhập, đa dạng và công bằng của AWS DevOps là gì? Bộ chứa là gì? Hồ dữ liệu là gì? Trí tuệ nhân tạo (AI) là gì? AI tạo sinh là gì? Máy học (ML) là gì? Khả năng bảo mật của Đám mây AWS Thông tin mới Blog Thông cáo báo chí Tài nguyên dành cho AWS Bắt đầu Đào tạo và chứng nhận Thư viện giải pháp AWS Trung tâm kiến trúc Câu hỏi thường gặp về sản phẩm và kỹ thuật Báo cáo của chuyên gia phân tích Đối tác của AWS Nhà phát triển trên AWS Trung tâm dành cho nhà phát triển SDK và Công cụ .NET trên AWS Python trên AWS Java trên AWS PHP trên AWS JavaScript trên AWS Trợ giúp Liên hệ với chúng tôi Nhận trợ giúp từ chuyên gia Nộp phiếu hỗ trợ AWS re:Post Trung tâm kiến thức Tổng quan về AWS Support Pháp lý Việc làm tại AWS Tạo tài khoản AWS Amazon là một công ty làm việc bình đẳng: không phân biệt Dân tộc thiểu số / Nữ giới / Người khuyết tật / Cựu chiến binh / Bản dạng giới / Khuynh hướng tình dục / Tuổi tác. Ngôn ngữ عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) Quyền riêng tư | Khả năng truy cập | Điều khoản áp dụng cho trang web | Tùy chọn cookie | © 2024, Amazon Web Services, Inc. hoặc các chi nhánh của Amazon. Bảo lưu mọi quyền. Bạn đang sử dụng trình duyệt cũ. Hãy nâng cấp lên duyệt mới hơn để cải thiện trải nghiệm của bạn. Ngừng hỗ trợ cho Internet Explorer Tôi hiểu AWS sẽ ngừng hỗ trợ cho Internet Explorer vào 07/31/2022. Các trình duyệt được hỗ trợ là Chrome, Firefox, Edge và Safari. Tìm hiểu thêm » Tôi hiểu | 2026-01-13T08:48:37 |
https://aws.amazon.com/api-gateway/#aws-page-content-main | Amazon API Gateway | API Management | Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Amazon API Gateway Overview Features Pricing Getting Started Resources More Products › Networking and Content Delivery › Amazon API Gateway Get started with Amazon API Gateway with AWS Free Tier Amazon API Gateway Create, maintain, and secure APIs at any scale Get started with API Gateway Why API Gateway? Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale. APIs act as the "front door" for applications to access data, business logic, or functionality from your backend services. Using API Gateway, you can create RESTful APIs and WebSocket APIs that enable real-time two-way communication applications. API Gateway supports containerized and serverless workloads, as well as web applications. API Gateway offers Portals that enables you to create fully managed, AWS-native developer portals for your APIs. With API Gateway Portals, you can centrally discover, document, and govern your REST APIs across your AWS infrastructure. API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, CORS support, authorization and access control, throttling, monitoring, and API version management. API Gateway has no minimum fees or startup costs. You pay for the API calls you receive and the amount of data transferred out and, with the API Gateway tiered pricing model, you can reduce your cost as your API usage scales. RESTful APIs Build RESTful APIs optimized for serverless workloads and HTTP backends using HTTP APIs. HTTP APIs are the best choice for building APIs that only require API proxy functionality. If your APIs require API proxy functionality and API management features in a single solution, API Gateway also offers REST APIs . WEBSOCKET APIs Build real-time two-way communication applications, such as chat apps and streaming dashboards, with WebSocket APIs . API Gateway maintains a persistent connection to handle message transfer between your backend service and your clients. Page topics Benefits 6 Benefits Open all Efficient API development Run multiple versions of the same API simultaneously with API Gateway, allowing you to quickly iterate, test, and release new versions. You pay for calls made to your APIs and data transfer out, and there are no minimum fees or upfront commitments. Performance at any scale Provide end users with the lowest possible latency for API requests and responses by taking advantage of our global network of edge locations using Amazon CloudFront. Throttle traffic and authorize API calls to ensure that backend operations withstand traffic spikes and backend systems are not unnecessarily called. Cost savings at scale API Gateway provides a tiered pricing model for API requests. With an API Requests price as low as $0.90 per million requests at the highest tier, you can decrease your costs as your API usage increases per region across your AWS accounts. Easy monitoring Monitor performance metrics and information on API calls, data latency, and error rates from the API Gateway dashboard, which allows you to visually monitor calls to your services using Amazon CloudWatch . Flexible security controls Authorize access to your APIs with AWS Identity and Access Management (IAM) and Amazon Cognito. If you use OAuth tokens, API Gateway offers native OIDC and OAuth2 support. To support custom authorization requirements, you can execute a Lambda authorizer from AWS Lambda . RESTful API options Create RESTful APIs using HTTP APIs or REST APIs. HTTP APIs are the best way to build APIs for a majority of use cases—they're up to 71% cheaper than REST APIs. If your use case requires API proxy functionality and management features in a single solution, you can use REST APIs. WirelessCar Learn how connected mobility provider WirelessCar enhanced startup performance using AWS Lambda SnapStart for Java. Read the Case Study Odyssey Interactive Learn how game studio Odyssey Interactive launched its debut multiplayer game, Omega Strikers, worldwide using managed infrastructure on AWS. Read the Case Study Betterfly Learn how Betterfly simplifies group protection and benefits management and encourages daily positive habits using a digital solution built on AWS. Read the Case Study TiVo Learn how TiVo in the media and entertainment industry achieved burstable scalability and consistent uptime of streaming services using AWS Lambda and Amazon API Gateway. Read the Case Study Get started with API Gateway 1 Sign up for an AWS account Instantly get access to the AWS Free Tier . AWS Free Tier 2 Learn with step-by-step tutorials Explore and learn with simple tutorials . simple tutorials 3 Start building with AWS Visit the AWS Management Console . AWS Management Console Next steps Features page Learn more about API Gateway Visit the features page Getting started Ready to build? Get started Contact us Have more questions? Contact us Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://docs.suprsend.com/docs/integrate-java-sdk#constructor-to-test-sdk-in-debug-mode | Integrate Java SDK - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Integrate Java SDK Manage Users Objects Send and Track Events Trigger Workflow from API Tenants Lists Broadcast Go SDK SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Java SDK Integrate Java SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Java SDK Integrate Java SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Java SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation For SDK installation, you’ll have to add the SuprSend jar file. You can include the jar using following two ways: Option 1. As a Maven dependency for maven projects from downloaded jar suprsend-java-sdk is present as a maven dependency on maven central. Add following code to your pom.xml to include the sdk xml Copy Ask AI < dependencies > < dependency > < groupId > com.suprsend </ groupId > < artifactId > suprsend-java-sdk </ artifactId > < version > 0.5.0 </ version > </ dependency > </ dependencies > Option 2. As a jar file for non maven projects Click here to download the latest version of java SDK from releases section and add it as an External Jar in your build path. suprsend-java-sdk is available as a JAR with name- suprsend-java-sdk-0.5.0-jar-with-dependencies.jar JDK version 8 and above is supported Please check your Java development kit version. If it is lower than supported version, upgrade it to the latest version Initialization For initializing SDK, you need WORKSPACE KEY and WORKSPACE SECRET . Request Copy Ask AI import suprsend.Suprsend; Suprsend suprsend = new Suprsend ( "WORKSPACE KEY" , "WORKSPACE SECRET" ); Replace WORKSPACE KEY and WORKSPACE SECRET with your workspace values. You will get both the tokens from Developers -> API Keys section. Constructor to test SDK in debug mode Constructor allows you to view HTTP calls to Suprsend in your console. The final parameter is a boolean parameter which denotes whether value for “debug” is true or false. Default value for the same is false. Request Copy Ask AI import suprsend.Suprsend; Suprsend suprsend = new Suprsend ( "WORKSPACE KEY" , "WORKSPACE SECRET" , true ); Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Java SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization Constructor to test SDK in debug mode | 2026-01-13T08:48:37 |
https://blog.devcycle.com/comparing-top-openfeature-providers/ | Top 10 OpenFeature Providers Compared Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature Why is OpenFeature Support is Critical? Comparing Top OpenFeature Providers Cobi Druxerman Jun 2, 2025 • 6 min read Feature flagging is essential for modern software development, enabling teams to test in production, manage releases incrementally, and mitigate risks, by separating code deploys from the release of features to users. As adoption grows, standardization via OpenFeature —an open specification for feature flags—becomes crucial to avoid vendor lock-in, simplify integrations and ensure you are implementing feature flagging in a standards compliant way. In this post we compare ten leading OpenFeature providers to help you determine which provider is right for you. Understanding OpenFeature OpenFeature, a CNCF incubating project , provides a vendor-agnostic API for feature flagging, standardizing interactions between applications and management systems. Its ecosystem defines standard logic that lives in providers within SaaS platform specific SDKs, allowing teams to implement generic logic in their applications that can be used with any feature flagging tool that supports the OpenFeature standard. Intro to OpenFeature The benefits of Open Standards generally and OpenFeature specifically are: Vendor-Agnostic Flexibility OpenFeature provides a standardized API that decouples your application code from specific feature flag vendors, reducing the risk of vendor lock-in. Unified and Extensible API By offering a consistent API across various programming languages and platforms, OpenFeature simplifies the implementation of feature flags. Enhanced Observability and Monitoring OpenFeature integrates with observability tools like OpenTelemetry, allowing teams to attach feature flag metadata to traces, logs, and metrics. Improved Developer Experience With its simple and understandable APIs, OpenFeature lowers the barrier to entry for implementing feature flags. Community-Driven and Open Source As a Cloud Native Computing Foundation (CNCF) incubating project, OpenFeature benefits from a vibrant community of contributors and adopters. A cornerstone of AMD’s vision for the future is our devotion to open standards. We participate in hundreds of open standards initiatives across the industry, including OCP, and these are essential for building scalable, flexible, and future-proof, AI-ready infrastructure. Ravi Kuppuswamy, CVP AMD What Should I Look for in an OpenFeature Provider? Evaluating a platform's OpenFeature compatibility requires scrutinizing several aspects: Comprehensive SDK and Provider Availability Platforms should offer OpenFeature providers for a wide range of languages and platforms, aligning with OpenFeature's official SDKs. Adherence to OpenFeature Specification Full compliance or at least consistent improvement toward the goal of compliance with the OpenFeature specification shows a commitment to the standard. Community Engagement Active community participation, contributions to the SDKs, the specification, the surrounding tooling and governance, indicate a provider's commitment to the standard's evolution, usefulness and reliability, now and in the future. Comparing the Landscape: What Are the Top 10 Feature Flagging Platforms by OpenFeature Prowess? This section compares DevCycle, ConfigCat, flagd, Flagsmith, Flipt and GO Feature Flags, GrowthBook, LaunchDarkly, Split.io and Unleash based on their OpenFeature support. Detailed Platform Breakdowns SaaS Providers Provider SDK Coverage Community Engagement DevCycle 76% ⭐⭐⭐⭐⭐ ConfigCat 47% ⭐⭐⭐ Flagsmith 29% ⭐⭐⭐⭐⭐ Flipt 41% ⭐⭐⭐ GrowthBook 35% ⭐ LaunchDarkly 35% ⭐⭐⭐⭐ Split.io 24% ⭐⭐ Unleash 0% ⭐ Open Source / Fully Self-Hosted Providers Provider SDK Coverage Community Engagement Flagd 53%* N/A GO Feature Flag 82%* ⭐⭐⭐⭐ DevCycle Overview: DevCycle provides feature flagging focused on ease-of-use, developer workflows, and strong adherence to OpenFeature standards. OpenFeature Provider Details: SDK Coverage: 76% official coverage; comprehensive server-side, client-side, and OFREP support. Aiming for complete coverage, leading among SaaS providers. Specification Support: Excellent spec alignment across languages (JavaScript, Node.js, Go, Java, .NET, Python, PHP, Ruby), ensuring native compatibility and full OpenFeature API integration. Community Engagement: Actively participates and contributes heavily, including tooling (CLI, OFREP), community hackathons, and governance. Noteworthy Strengths: Governance involvement, extensive SDK support, built specifically for OpenFeature. ConfigCat Overview: ConfigCat emphasizes simplicity, scalability, and transparent pricing in its developer-focused feature flag service. OpenFeature Provider Details: SDK Coverage: 47% official coverage; robust support in major languages (.NET, Go, Java, JavaScript, Node.js, PHP, Python, Rust). Specification Support: Comprehensive compliance, ensuring feature parity with native SDKs, adhering closely to OpenFeature standards where providers are available. Community Engagement: Recently increased involvement, officially maintaining providers, active promotion, and community participation. Noteworthy Strengths: Broad language support, strong context documentation, recent shift to official provider management. flagd Overview: flagd is an official, OpenFeature-compliant feature flag daemon and reference implementation. OpenFeature Provider Details: SDK Coverage: 53% official coverage; designed explicitly around OpenFeature. Specification Support: Complete adherence to OpenFeature, language-agnostic, supporting full specification including OFREP. Community Engagement: Integral OpenFeature community component, active maintenance and participation by core OpenFeature contributors. Noteworthy Strengths: Full OpenFeature compliance, robust standalone engine, strong OFREP integration. Flagsmith Overview: Flagsmith offers versatile feature flagging available as open-source, cloud-hosted, or on-premise. OpenFeature Provider Details: SDK Coverage: 29% official coverage; support across multiple languages (Go, Java, .NET, JavaScript). Specification Support: Strong and expanding, active involvement from inception; providers cover major environments closely following standards. Community Engagement: Founding member, strong governance role, ongoing community presence. Noteworthy Strengths: Open-source, founding OpenFeature member, PROVIDER_CONFIGURATION_CHANGED support. Flipt Overview: Flipt is an open-source, GitOps-focused feature management platform supporting flexible evaluation. OpenFeature Provider Details: SDK Coverage: 41% official coverage; robust provider support (Node.js, Browser JS, Go, Java, C#, Python, Ruby). Specification Support: Excellent, early OFREP adopter, highly compliant across supported languages. Community Engagement: Early adopter, active OFREP integration; moderate but consistent community involvement. Noteworthy Strengths: GitOps integration, strong open-source presence, early OFREP support. GO Feature Flag Overview: GO Feature Flag is a lightweight, self-hosted, entirely OpenFeature-based solution emphasizing simplicity. OpenFeature Provider Details: SDK Coverage: 82% official coverage; leveraging OpenFeature exclusively instead of proprietary SDKs. Specification Support: Complete and thorough implementation, supporting all OpenFeature SDK languages. Community Engagement: Strong OpenFeature advocate, medium-to-high involvement through provider contributions and advocacy. Noteworthy Strengths: Built entirely on OpenFeature, simple deployment, event-driven web support. GrowthBook Overview: GrowthBook provides open-source feature flags and A/B testing focused on experimentation and data integration. OpenFeature Provider Details: SDK Coverage: 35% official coverage; limited to core languages (JavaScript, Node.js, Java, Python). Specification Support: Limited coverage, adhering strictly where available but narrow in breadth. Community Engagement: Low visibility; primarily focused internally rather than broader OpenFeature contributions. Noteworthy Strengths: A/B testing emphasis, actively improving OpenFeature support. LaunchDarkly Overview: LaunchDarkly offers enterprise-grade feature management with robust integrations and real-time updates. OpenFeature Provider Details: SDK Coverage: 35% official coverage; primarily server-side official and community-maintained providers. Specification Support: Solid support for major server-side languages; lacks extensive client-side/mobile coverage and OFREP. Community Engagement: Moderate, early endorsement and advocacy but limited broader contributions. Noteworthy Strengths: Robust enterprise platform, reliable OpenFeature server-side integrations. Split.io Overview: Split.io provides feature delivery combining flags with monitoring and analytics. OpenFeature Provider Details: SDK Coverage: 24% official coverage; moderate support focusing on key languages (Java, JavaScript/Node.js). Specification Support: Solid but limited to specific environments, full compliance where implemented. Community Engagement: Medium engagement; governance board presence, advocacy, but limited daily contributions. Noteworthy Strengths: Analytics integration, solid OpenFeature support for key languages. Unleash Overview: Unleash is a flexible, extensible, open-source feature management solution known for self-hosting. OpenFeature Provider Details: SDK Coverage: 0% official coverage; limited official providers (Go, JavaScript). Specification Support: Low overall coverage, community-driven integrations without official extensive support. Community Engagement: Low engagement, minimal community-driven contributions without significant core team involvement. Noteworthy Strengths: Strong open-source community, deployment flexibility. Choosing Your OpenFeature-Powered Platform: Making an Informed Decision When selecting a platform, we believe you should prioritize comprehensive OpenFeature provider coverage and specification support as these are the core to compatibility with your tech stack today and tomorrow. Strong community engagement ensures the tool of your choice stays relevant and is at the leading edge of any updates to the OpenFeature specification. DevCycle: Leading the Charge in OpenFeature Adoption and Excellence DevCycle stands out for teams prioritizing deep OpenFeature integration due to its leadership and community contributions, "built for OpenFeature" SDKs, extensive provider coverage, transparent context handling, strong event/hook foundation, and developer-focused migration tools. A proactive embrace of OpenFeature signals a reliable long-term commitment. DevCycle's Unwavering Commitment to OpenFeature Co-founder Jonathan Norris is on the OpenFeature Governance Committee, highlighting DevCycle's dedication. Active participation in hackathons has yielded contributions like OFREP exploration and migration codemods. DevCycle SDKs are "built for the OpenFeature standard" by default, giving teams confidence that they are taking a standards-based approach to feature flagging when using DevCycle. Superior OpenFeature Provider Implementation DevCycle offers broad OpenFeature provider coverage for server-side (Java, Go, Node.js, PHP, Python, .NET, Ruby) and client-side (React, JS Web, Angular). More importantly OpenFeature providers are . DevCycle ensures SDKs and APIs match the up-to-date OpenFeature Spec and contribute back to the community as much as possible. Developer Experience: Seamless Integration and Migration DevCycle contributed tools like the Multi-Provider back to the OpenFeature community, to help developers migrate from internal tools or otherwise to their choice of OpenFeature provider, easing adoption. DevCycle is committed to improving developer experience on its own platform and in the OpenFeature community. Conclusion: Embrace Open Standards with a Best-in-Class Provider OpenFeature is revolutionizing feature flag management by creating a shared standard, promoting vendor neutrality and improving developer experience. The quality of a platform's OpenFeature provider is a key differentiator. For teams seeking robust, future-proof OpenFeature integration, DevCycle is a leading choice. Their active community leadership, SDKs built for the standard, comprehensive providers, and developer-centric tools highlight their commitment to vendor-neutral feature flagging. Partnering with a provider like DevCycle allows organizations to fully leverage open standards for better, safer software development. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://youtu.be/s/player/b95b0e7a/www-player.css | - 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:48:37 |
https://www.lob.com/industries/financial-services | Automated Financial Mail: Personalized, Secure Financial Direct Mail | Lob Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Financial Services Automated Financial Mail: Personalized, Secure Financial Direct Mail From special offers to account statements to paychecks, deliver secure direct mail that keeps your audience engaged. Book a demo For more information about how this data is handled, please view our Privacy Policy What good looks like We’ve helped hundreds of financial services companies send direct mail with massive impact. Here’s what we’ve seen work. Promotions Send fridge-worthy special offers According to our 2024 State of Direct Mail Consumer Insights survey, 78% of consumers are likely to open or read a direct mail piece with an offer or promotion. Winning Formats Postcards Self-Mailers Booklets Account Statements + Updates Share essential information Scale account updates, invoices, collection notices, and payment envelopes. Lob’s industry-leading security gets your mail where it needs to go safely and on time. Winning Formats Letters Envelopes Paychecks Streamline accounts payable Securely send and track checks, money orders, and other payments at any scale. Winning Formats Checks Tax Documents Securely send tax information Come January, send tax documents to all your clients — and leave the logistics to us. Winning Formats Letters Snap Packs Stand out from the digital noise — and your competition Fill in the blanks Retarget website visitors and email subscribers by matching them to valid addresses to reach more leads Reduce churn Send renewal notifications and account updates to keep audiences engaged Boost productivity Send compliant mail at scale and eliminate logistical hiccups Measure + maximize Track delivery and demonstrate the value of every send with advanced analytics Send mail faster while cutting costs Automate your direct mail and see up to 85% in cost savings. Lob integrates with your digital channels so you can use your customer data to trigger sends and get in mailboxes in days instead of weeks. See our full list of integrations “Lob created a more efficient process with more flexibility and saves everyone time and resources,” – Laura Costello, Head of Marketing Read the case study Don’t lose customers to typos Address verification stops failed deliveries in their tracks. Learn more about address verification Put security and compliance first Every printer in Lob’s network meets industry-leading standards to ensure the safety and security of your mail. Our annual third-party audits ensure compliance with HIPAA, SOC-2, and more. See how printing works Why do so many financial service companies already trust Lob? Because of numbers like these 50% Reduction in costs Read the case study 4X Increase in response rates Read the case study State of Direct Mail Consumer Insights 84% of marketers say direct mail has the highest ROI Read the report Financial Services FAQs What is financial services marketing? Financial services marketing is a specialized form of marketing that focuses on promoting financial products and services to consumers or businesses. This can include traditional banking, investment management, insurance, credit cards, loans, and other financial products. In recent years, the financial services industry has become increasingly competitive with the rise of online fintech companies and technological advancements changing how people interact with their finances. As a result, effective marketing strategies are crucial for companies in this sector to stand out and attract new customers. One key aspect of financial services marketing is building trust and credibility with potential clients. Since money is such a sensitive topic, consumers want to feel confident in the company they choose to handle their finances. Marketing efforts must showcase the company's expertise, reliability, and commitment to customer satisfaction. How can financial service companies use direct mail? Direct mail is a popular marketing tactic for financial service companies because it allows them to reach potential customers directly in their homes or offices. This physical form of advertising can be particularly effective in the financial industry, where trust and credibility are critical. Financial service companies can use finance mail to target specific demographics or geographic locations that align with their ideal customer profile. They can also personalize the messaging and offers based on the recipient's financial needs and interests. Some common examples of direct mail for banks include credit card offers, loan pre-approval letters, promotional flyers for new services, and educational materials such as retirement planning guides. What roles does omnichannel play in financial service marketing strategies? Omnichannel marketing is becoming increasingly important in the financial service industry as more and more consumers expect a seamless and personalized experience across all channels. This approach allows companies to reach customers through multiple touchpoints, such as email, social media, direct mail, and mobile apps. By using an omnichannel marketing strategy, financial service companies can create consistent messaging and branding across all channels, building trust and credibility with potential customers. They can also gather data from various touchpoints to better understand their target audience's preferences and behaviors, allowing them to tailor their marketing efforts for maximum impact. How can financial service companies use direct mail to acquire customers? Financial service companies can leverage direct mail as a powerful tool for customer acquisition by designing targeted campaigns that reach lookalike audience demographics or locales that mirror their current best customers. By using tools like Lob Audiences, financial services companies can identify potential customers who may benefit from their services and tailor their messaging accordingly. Including attractive offers, such as limited-time discounts or free consultations in financial services mailers, can incentivize recipients to consider their options and take action. How can financial services companies use direct mail to retain customers? Direct mail can be a valuable tool for retaining existing customers. Financial services companies can use direct mail to send personalized communications and offers to their current clients. This can include reminders for upcoming account renewals, updates on investment options, and information about new services or products. Direct mail provides current customers with a physical reminder of important dates. Send direct mail that converts with Lob Book a demo Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:37 |
https://blog.devcycle.com/unleashing-creativity-how-ansell-built-cycle-doodle-in-24-hours-using-devcycle-2/ | Unleashing Creativity: How Ansell Built Cycle Doodle Using DevCycle Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Unleashing Creativity: How Ansell Built Cycle Doodle Using DevCycle DevCycle Feb 25, 2025 • 3 min read Today's DevCycle Spotlight features Ansell Maximilian , a developer who won the first DevCycle Feature Flag Challenge on Dev.to! The challenge encouraged entrants to build a fun and creative project using DevCycle . He took the top prize with his inventive Cycle Doodle project. Judges loved the creativity of Ansell's project as well as his choice to build the app exclusively with DevCycle services and features. Using DevCycle to Build Cycle Doodle Ansell created a web game that allows users to join one of three teams and either draw a simple image based on a prompt, guess what other teams have drawn or rate the drawings of other teams. How Ansell Used DevCycle Features to Create a Winning Project: Team Assignments: DevCycle was used to dynamically group users into teams (Grid Goblins, Edit Emperors or Paint Paladins). Each team had unique advantages like larger grids or additional paint colors, which were configured using JSON feature flags. Role Cycling: DevCycle's API was used to shift team roles (Drawer, Guesser, or Voter) seamlessly. This was managed through a Feature that served different roles to each team based on their Audience . Game Data Management: Forgoing a traditional database, Ansell opted for DevCycle's Feature Variables to store and update game prompts, drawings and guesses . This allowed all users to access the same game data in realtime. Admin Controls: An "Admin" Audience and feature flag were created to restrict access to specific admin controls like creating or deleting prompts or ensuring secure and controlled updates. DevCycle Features That Stood Out Feature Toggle for Live Apps: "One of the most compelling features of DevCycle is the ability to toggle features on/off even in live applications," Ansell shared. It was a huge plus for him that DevCycle uses Ably to serve these experiences as he'd used this tool in the past. Dynamic Value Serving: DevCycle isn't limited to on/off feature flags, it allows developers to serve various types of values like Number, String, or JSON . "This flexibility is something I leveraged extensively in my project to differentiate team functionalities and manage game states," noted Ansell. Audiences: DevCycle allows users to create audiences based on specific attributes like user ID, app version, country, platform or custom properties. Powerful APIs: Ansell appreciated that "the APIs provided by DevCycle are robust and well-documented." They allowed him to dynamically update audiences, cycle team roles and manage game data programmatically without needing a backend database. " DevCycle has been an invaluable tool, offering flexibility and efficiency in managing features and user experiences. The ability to toggle live features, serve dynamic values and a very complete list of APIs combine into one amazing service. For someone like me, who's constantly exploring new technologies, DevCycle has opened up exciting possibilities, whether it's simplifying live app management or enabling creative projects, DevCycle delivers on all fronts." - Ansell Maximilian More About Ansell Maximilian Ansell started his professional journey as a web developer and currently works at a B2B tech company that develops software solutions for businesses in the fast-moving consumer goods industry as an Android developer. Ansell shared some insights from his time as an Android developer, "My experience as an Android developer has taught me how tedious it is to prepare an app for a release; since the Play Store has so many policies, we really make sure everything is working by doing things like quality assurance, regression testing, etc. We want to avoid the hassle of re-releasing as much as possible... this gave me perspective on how useful something like DevCycle would be. Imagine we put new features under feature flags. If something goes wrong, we don't have to fix it immediately and work outside work hours, we could just turn off the feature from the DevCycle dashboard and time our time fixing the problem within work hours." In his free time Ansell experiments with new technologies to keep his skills sharp beyond Android development, so he participates in many dev challenges and hackathons. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://dev.to/anand12/top-10-git-commands-every-developer-should-know#main-content | Top 10 Git Commands Every Developer Should Know - 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 #WithAnand Follow Top 10 Git Commands Every Developer Should Know Oct 26 '21 play Git is an important part of daily programming (especially if you're working with a team) and is widely used in the software industry. Since there are many various commands you can use, mastering Git takes time. https://muthuannamalai.tech/top-10-git-commands-every-developer-should-know. Read Blog: https://muthuannamalai.tech/top-10-git-commands-every-developer-should-know --- Send in a voice message: https://anchor.fm/anand12/message Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:37 |
https://dev.to/t/ai/page/8 | Artificial Intelligence 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 Artificial Intelligence Follow Hide Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities found in humans and in nature. Create Post submission guidelines Posts about artificial intelligence. Older #ai 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 Google Gemma2/PaliGemma: Notes on Learning and Applications Evan Lin Evan Lin Evan Lin Follow Jan 11 Google Gemma2/PaliGemma: Notes on Learning and Applications # ai # google # llm Comments Add Comment 3 min read AI Trading: Lesson Learned #133: LYING - Claimed Fix Without Verification Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #133: LYING - Claimed Fix Without Verification # ai # trading # python # machinelearning Comments Add Comment 1 min read GitHub Copilot: Make Your Commit Messages More Engaging with Custom Instructions Evan Lin Evan Lin Evan Lin Follow Jan 11 GitHub Copilot: Make Your Commit Messages More Engaging with Custom Instructions # ai # github # productivity Comments Add Comment 2 min read Notes: Quick Thoughts on the Google Gemini API Hackathon Awards Evan Lin Evan Lin Evan Lin Follow Jan 11 Notes: Quick Thoughts on the Google Gemini API Hackathon Awards # gemini # google # devchallenge # ai Comments Add Comment 2 min read My Thoughts on Vibe Coding and Gemini CLI Evan Lin Evan Lin Evan Lin Follow Jan 11 My Thoughts on Vibe Coding and Gemini CLI # discuss # gemini # cli # ai Comments Add Comment 2 min read My Ray-Ban Meta Glasses AI Setup in Taiwan Evan Lin Evan Lin Evan Lin Follow Jan 11 My Ray-Ban Meta Glasses AI Setup in Taiwan # ai # iot # tutorial Comments Add Comment 2 min read AI Trading: Lesson Learned #131: Self-Healing Gap - Blog Lesson Sync Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #131: Self-Healing Gap - Blog Lesson Sync # ai # trading # python # machinelearning Comments Add Comment 2 min read Why Your AI Agents Need a Shell (And How to Give Them One Safely) Salah Pichen Salah Pichen Salah Pichen Follow Jan 11 Why Your AI Agents Need a Shell (And How to Give Them One Safely) # bash # agents # ai # mcp Comments Add Comment 7 min read AI Trading: Lesson Learned #130: Comprehensive Investment Strategy Review (Jan 11, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #130: Comprehensive Investment Strategy Review (Jan 11, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read Designing Natural AI Memory: Why It Feels Awkward and How to Fix It web3nomad.eth web3nomad.eth web3nomad.eth Follow Jan 11 Designing Natural AI Memory: Why It Feels Awkward and How to Fix It # ai # agents # ux 1 reaction Comments Add Comment 6 min read Building Scalable AI Agent Systems: Three Evolutions web3nomad.eth web3nomad.eth web3nomad.eth Follow Jan 11 Building Scalable AI Agent Systems: Three Evolutions # systemdesign # architecture # ai # agents 1 reaction Comments Add Comment 18 min read RAG AI Manikanta Yarramsetti Manikanta Yarramsetti Manikanta Yarramsetti Follow Jan 12 RAG AI # ai # llm # rag Comments Add Comment 2 min read Cloud 101 with AWS: From Concepts to a Real Serverless App Warda Liaqat Warda Liaqat Warda Liaqat Follow Jan 11 Cloud 101 with AWS: From Concepts to a Real Serverless App # aws # cloudcomputing # serverless # ai 1 reaction Comments Add Comment 2 min read AWS Certified Generative AI Developer – Professional in 2 Weeks (Part 2: Advanced Learning & Exam Prep) MakendranG MakendranG MakendranG Follow Jan 11 AWS Certified Generative AI Developer – Professional in 2 Weeks (Part 2: Advanced Learning & Exam Prep) # ai # aws # certification # machinelearning 1 reaction Comments Add Comment 13 min read AI, Confluence Docs, and READMEs: Why AI Written Docs End Up Unread ujjavala ujjavala ujjavala Follow Jan 12 AI, Confluence Docs, and READMEs: Why AI Written Docs End Up Unread # discuss # webdev # ai # productivity 18 reactions Comments 5 comments 4 min read When AI Governance Calls You "Noise" Alan Tsai Alan Tsai Alan Tsai Follow Jan 11 When AI Governance Calls You "Noise" # ai # hardgate # fun # 雜訊 Comments Add Comment 2 min read Building Career Architect: An AI-Powered Job Application Pipeline for Engineers Henry Ohanga Henry Ohanga Henry Ohanga Follow Jan 11 Building Career Architect: An AI-Powered Job Application Pipeline for Engineers # automation # ai # career # productivity Comments Add Comment 3 min read High-performance GPUs or TPUs vs CPUs Neweraofcoding Neweraofcoding Neweraofcoding Follow Jan 11 High-performance GPUs or TPUs vs CPUs # architecture # machinelearning # performance # ai Comments Add Comment 2 min read How Agentic AI and Workflow Automation Are Redefining Modern Software Engineering Muhammad Nouman Muhammad Nouman Muhammad Nouman Follow Jan 11 How Agentic AI and Workflow Automation Are Redefining Modern Software Engineering # ai # aiagents # n8n # agentaichallenge Comments Add Comment 4 min read Amazon S3 Vectors: When Your Data Lake Becomes Your Vector Store Sujitha Rasamsetty Sujitha Rasamsetty Sujitha Rasamsetty Follow Jan 11 Amazon S3 Vectors: When Your Data Lake Becomes Your Vector Store # aws # awscommunity # ai # vectordatabase Comments Add Comment 6 min read How Databricks Used AI Agents to Cut Database Debugging Time by 90% Satyabrata Satyabrata Satyabrata Follow Jan 11 How Databricks Used AI Agents to Cut Database Debugging Time by 90% # agents # ai # automation # database Comments Add Comment 3 min read AI Trading: Lesson Learned #079: Tomorrow Hallucination Incident (Jan 5, 2026) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #079: Tomorrow Hallucination Incident (Jan 5, 2026) # ai # trading # python # machinelearning Comments Add Comment 2 min read NordVPN Privacy is a Rip-Off for Most Users (But a Beast for One Specific Group) ii-x ii-x ii-x Follow Jan 11 NordVPN Privacy is a Rip-Off for Most Users (But a Beast for One Specific Group) # ai # tech # productivity Comments Add Comment 3 min read I Built an AI-Powered Portfolio with Next.js, Supabase & Groq - Here's How chiheb nouri chiheb nouri chiheb nouri Follow Jan 11 I Built an AI-Powered Portfolio with Next.js, Supabase & Groq - Here's How # showdev # ai # nextjs # portfolio Comments Add Comment 2 min read AI Trading: Lesson Learned #132: RAG Stuck on December 2025 Content (CRISIS) Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Jan 11 AI Trading: Lesson Learned #132: RAG Stuck on December 2025 Content (CRISIS) # ai # trading # python # machinelearning Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:37 |
https://aws.amazon.com/lambda/ | Serverless Computing - AWS Lambda - Amazon Web Services Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Lambda Overview Features Pricing Getting Started Resources More Products › Compute › AWS Lambda 1 million requests free per month with the AWS Free Tier AWS Lambda Run code without thinking about servers or clusters Get started with AWS Lambda See the documentation Why AWS Lambda? AWS Lambda empowers you to focus solely on your code, while it handles all infrastructure management, enabling faster development, improved performance, enhanced security, and cost efficiency. Play Benefits of AWS Lambda Increase developer agility Write less code, perform less maintenance, and build applications faster. Boost application performance Leverage AWS’ operational excellence by offloading tasks associated with high availability and resilience, ensuring critical performance for your business. Help strengthen overall security posture Reduce security operations burden, provide security isolation, and drive business continuity while accelerating innovation. Drive cost efficiency Utilize pay-per-use billing by the millisecond while reducing operational costs associated with infrastructure management and application development. Use cases Interactive web and mobile backends Web and mobile applications often contain sophisticated features like authentication, geo-hashing, and real-time messaging, mostly built as distributed microservices-based systems. These applications must respond almost in real time to customer activity and scale seamlessly to meet unpredictable demands all while maintaining robust security. With AWS Lambda, you can build and operate powerful web and mobile back-ends that deliver consistent, uninterrupted service to end users by automatically scaling up and down based on real-time needs. You can enhance application functionalities by easily connecting them to other systems or modifying components without re-architecting the entire system. Batch data processing Batch data processing tasks often require substantial compute and storage resources to handle large volumes of information for short periods. AWS Lambda is ideal for these workloads, offering cost-effective, millisecond-billed compute that automatically scales out to meet processing demands and down upon completion, ensuring efficient resource use and preventing exhaustion. You can focus on building and analyzing data without needing to be experts in AWS infrastructure management. Real-time data processing Real-time data processing involves processing continuous data instantly and efficiently to gather analytical insights and drive better customer experiences. The volume of streamed or queued data can vary unpredictably based on end-user actions and demands. AWS Lambda natively integrates with both AWS and third-party real-time data sources, such as Amazon SQS , Amazon Kinesis , Amazon Managed Streaming for Apache Kafka (MSK) , and Apache Kafka, enabling you to process real-time data without the overhead of managing streaming client libraries or learning specialized data processing frameworks. Generative AI The generative AI landscape is evolving rapidly, and organizations need to innovate and adapt quickly to maintain competitive advantage. This evolution is catalyzed by a significant surge in large language models (LLMs) that meet diverse needs. Organizations are building distributed architectures that leverage specific LLMs based on unique requirements. AWS serverless architecture, powered by AWS Lambda, is ideal for generative AI applications, enabling you to start small and scale seamlessly while handling distributed, event-driven workflows securely at scale. Get started with AWS Lambda Feature Find out how AWS Lambda works Explore AWS Lambda Features Documentation Explore hands-on training Check out getting started tutorials Getting started Connect with an expert Explore support options Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://docs.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio | Report a problem with Visual Studio - Visual Studio (Windows) | Microsoft Learn Skip to main content Skip to Ask Learn chat experience This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Download Microsoft Edge More info about Internet Explorer and Microsoft Edge Table of contents Exit editor mode Ask Learn Ask Learn Focus mode Table of contents Read in English Add Add to plan Edit Share via Facebook x.com LinkedIn Email Print Note Access to this page requires authorization. You can try signing in or changing directories . Access to this page requires authorization. You can try changing directories . Report a problem with the Visual Studio product or installer Feedback Summarize this article for me In this article You can report a problem from either Visual Studio or its installer. The built-in Feedback Tool allows you to easily add diagnostic information that helps the Visual Studio teams diagnose and fix the issues. Here are the steps to report a problem. In Visual Studio , select the feedback icon in the upper-right corner and select Report a Problem. You can also access the feedback tool from the menu: Help > Send Feedback > Report a Problem . Alternatively, if you can't install Visual Studio or are unable to access the feedback tool within Visual Studio you can report a problem in the Visual Studio Installer . If you have Visual Studio open, go to Tools > Get Tools > Features... to launch the installer, or launch it from the Start menu. In the installer, select the feedback icon in the upper-right corner and select Report a problem . Selecting Report a Problem will open Developer Community in your default browser and sign you in using the same account you're signed in to Visual Studio with. Note: If you are using an ad-blocker you may experience issues during sign-in. Disable the ad-blocker and try to sign in again. Start by entering the descriptive title of your bug report. It must be at least 25 characters long. Select a category for the problem. Start entering a description of the problem. After you enter enough information, the Search button at the bottom of the page is enabled. Select this button to see a list of similar problems and solutions. Select the possible bug reports to see if there is one matching your own problem. If there is, vote for it instead of creating your own ticket. If no duplicates were found, continue by selecting Can't find the solution . When you select this button, you see the Submit a ticket tab. The information that you've already entered is still in the form. Complete the description if you haven't already done so. It's important to be as clear as possible to increase the chances of the engineering team being able to reproduce the bug. Make sure to include clear reproduction steps. If relevant to the bug report, take a screenshot by selecting the Include Visual Studio screenshot . You can even crop the screenshot directly in the browser to remove any sensitive or unrelated parts. Only Microsoft engineers can see the screenshot Record your actions to reproduce the issue. One of the best ways to help the Visual Studio engineering team solve the problem is to provide a trace and heap dump files for them to look through. You can do that by recording the steps that resulted in the bug. A screenshot will be captured every time the mouse is clicked, but keyboard entry will not record screenshots. Select Start recording . Wait a moment for the permissions prompt. Go through your steps to record the issue. When finished, find the small pop-up window and select Stop sharing . Only Microsoft engineers can see the recording Warning There may be a several seconds delay between clicking Start recording and the prompt where Windows asks for permission to start a program with elevated permissions. Review the attached files and upload additional files if you believe it would help diagnose the issue. Only Microsoft engineers can see the attached files The last step is to hit the Submit button. Submitting the report will send it directly into the internal Visual Studio bug reporting system awaiting triage. You will receive email updates about your ticket. After submitting the ticket, you can go to the Home page of the Developer Community site to view your feedback. Each one of your problem reports becomes a work item in our core engineering system, empowering you to engage directly with our product teams to help us identify and resolve impactful issues. Your feedback submitted with rich diagnostic information is critical to improving the Visual Studio product family. We really appreciate you taking the time to report problems. In addition, you can vote on feedback from other community members to bring more attention to a problem and help fix it faster. When further information is needed When an issue is missing important information, we assign the Needs More Info state. We comment on the issue with the specific information we need, and you'll receive an email notification. You can provide more information by adding comments, attachments, log/dump files, or recording steps. If we don't receive the information within 7 days, then we send you a reminder. After that, we close the ticket after 14 days of inactivity. If you need to leave a comment or add attachments, navigate to the issue from the email and comment/add attachments directly. To add log/dump files or record steps: Open Visual Studio and navigate to the feedback ticket via Help > Send feedback > My feedback Selecting the Provide More Info link on the problem report navigates you to a new screen. From here, you can see what info is being requested. Attach your dump/log files or record steps, and then submit. The requesting Microsoft engineer receives a notification about the extra information provided. If they have enough information to investigate, the problem state changes. Otherwise, the engineer asks for even further information. You can see these requests on the My Feedback screen along with all your other Problems and Suggestions . Problem Status After you report a problem, states indicate where your submissions are in their lifecycle. As Microsoft teams review your feedback, they set it with an appropriate state. Track the progress of your problem reports by referencing the states listed below, along with their meaning and color indicators. State Description New indicates that the bug or issue is newly reported, and no action has been taken on it yet. Triaged indicates that preliminary steps such as moderation, translation, and initial check for duplicates are complete. Your ticket has been routed to the appropriate engineering team for consideration. Under Consideration indicates that Microsoft is reviewing your problem for community impact and will prioritize it accordingly. If the community impact isn't clear or significant yet, we'll continue to monitor the problem in this state. Under Investigation indicates that engineers are actively investigating your problem to find a resolution. Need More Info indicates that we need more diagnostic information from you so that we can go forward with the investigation. Learn how to respond to Need More Info requests. Fixed - Pending Release indicates that we have a fix for the problem and it will be available in an upcoming preview or release. When the fix becomes available in a preview, the problem is tagged with a 'fixed in' tag specifying the preview version. Closed - Fixed indicates that we've released a fix for the problem. The problem is also now tagged with a "fixed in:" tag specifying the release version. Closed - Duplicate indicates that your issue has already been reported via another feedback. We'll provide you with the link where you can track the original problem report. Closed - Lower Priority To focus on bringing each of you in our developer community the best value, we prioritize issues with the highest customer impact. Although we're unable to address this particular issue at this time, be assured that all your feedback is valuable and helps improve Visual Studio. Closed - Not a Bug indicates that we've determined that the reported functionality is by current design. Closed - Not Enough Info indicates that we don't have enough information to investigate this for you. We'll be happy to reconsider the feedback after the necessary information is available. Closed - Other Product indicates we've determined that your issue applies to another product. See the comment from Microsoft for which external product and any related links. FAQ How can I increase the chance of my problem getting resolved quickly? We recommend using search to ensure that the problem you're about to report hasn't already been reported. If you find an existing item matching your problem, follow and vote on that problem ticket. Provide all the information you can to help our teams reproduce what you're experiencing. This information includes necessary repro steps, code fragments, screenshots, repro recordings, log files, and other artifacts. How is my feedback prioritized? We receive a large number of valuable problems from our customers. To ensure that we're bringing the best value to each of you in our developer community, we prioritize action on feedback that has the highest community impact. If we aren't able to respond personally to your feedback, know that we fully appreciate your input. Be assured that all your feedback gets to the right team. We truly value the time you invest in making Visual Studio better. What actions can I take if I'm not satisfied with the resolution? Our teams do their best to diagnose and fix any issues you experience, however there may be times when you're not fully satisfied with our recommendation. Comment back on the feedback and let us know exactly what you're not satisfied with, and we'll try our best to ensure that we meet your needs. How will I get notified of progress on my feedback? Microsoft engineering teams will communicate with you by commenting on the feedback ticket and changing the state of your ticket as they make progress. Watch for e-mail notifications that are sent when ticket state changes or a comment is posted. You can manage frequency of notifications in Profile and Preferences settings on Developer Community site. Why can't I add a problem for Visual Studio IDE on the Developer Community website? Reporting a problem through Visual Studio allows for diagnostic information to automatically be included in the report. It's essential information that gives our engineers the context they need to fully understand your issue and work to resolve it. When you report through Visual Studio, you can easily share rich diagnostic information with us, such as large log files, crash information, screenshots, repro recording, and other artifacts that help us deliver higher-quality resolutions faster to you. You might encounter problems reporting an issue on Developer Community if you are using an ad blocker. Please disable your ad blocker and try again. Developer Community also does not currently support the Brave browser, so we recommend using a different browser. Search for solutions or provide feedback If you don't want to or can't use Visual Studio to report a problem, there's a chance the problem has already been reported and a solution posted on the Visual Studio Developer Community page. If you don't have a problem to report but want to suggest a feature, there's a place for doing that too. For more information, see the Suggest a feature page. Related content Visual Studio Developer Community Report a problem with .NET Report a problem with C++ Developer Community Guidelines Developer Community data privacy Feedback Was this page helpful? Yes No No Need help with this topic? Want to try using Ask Learn to clarify or guide you through this topic? Ask Learn Ask Learn Suggest a fix? Additional resources Last updated on 2025-11-21 In this article Was this page helpful? Yes No No Need help with this topic? Want to try using Ask Learn to clarify or guide you through this topic? Ask Learn Ask Learn Suggest a fix? en-us Your Privacy Choices Theme Light Dark High contrast AI Disclaimer Previous Versions Blog Contribute Privacy Terms of Use Trademarks © Microsoft 2026 | 2026-01-13T08:48:37 |
https://open.forem.com/t/programming#main-content | Programming - 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 Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 1 2 3 4 5 6 7 8 9 … 75 … 3611 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu digital marketing Junaid Rana Junaid Rana Junaid Rana Follow Jan 9 digital marketing # ai # programming # beginners # productivity Comments Add Comment 5 min read Everything You Need to Launch a Product That Looks Legit (Even If You’re Bad at Design) N Nash N Nash N Nash Follow Jan 5 Everything You Need to Launch a Product That Looks Legit (Even If You’re Bad at Design) # tools # programming # webdev # ai 4 reactions Comments Add Comment 4 min read Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem Darian Vance Darian Vance Darian Vance Follow Dec 31 '25 Solved: I hired two junior people and realized media buyers being bad at creative strategy is actually a huge problem # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: PoE+++?! WHEN WILL THE MADNESS END? Darian Vance Darian Vance Darian Vance Follow Dec 28 '25 Solved: PoE+++?! WHEN WILL THE MADNESS END? # devops # programming # tutorial # cloud Comments Add Comment 7 min read Solved: How to look for a good MSP Darian Vance Darian Vance Darian Vance Follow Dec 26 '25 Solved: How to look for a good MSP # devops # programming # tutorial # cloud Comments Add Comment 8 min read Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Rajguru Yadav Rajguru Yadav Rajguru Yadav Follow Dec 27 '25 Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story # discuss # programming # ai # beginners 10 reactions Comments Add Comment 3 min read Best Courses to Learn AI for 2026 Hameed Ansari Hameed Ansari Hameed Ansari Follow Dec 8 '25 Best Courses to Learn AI for 2026 # ai # programming # productivity # beginners 5 reactions Comments Add Comment 1 min read Human vs. Machine Cognition: Brains, Minds, and Meaning Thinking Healer Thinking Healer Thinking Healer Follow Nov 24 '25 Human vs. Machine Cognition: Brains, Minds, and Meaning # help # ai # programming # security Comments Add Comment 3 min read How AI will change website development — and whether it will affect pricing Polina Elizarova Polina Elizarova Polina Elizarova Follow Nov 18 '25 How AI will change website development — and whether it will affect pricing # ai # webdev # productivity # programming Comments 1 comment 3 min read Website savings: where to cut and where to stop Polina Elizarova Polina Elizarova Polina Elizarova Follow Nov 19 '25 Website savings: where to cut and where to stop # webdev # ai # productivity # programming Comments Add Comment 2 min read Migrating Legacy C Code: Obsolete 3GL Functions in Uniface 10.4 Peter + AI Peter + AI Peter + AI Follow Nov 23 '25 Migrating Legacy C Code: Obsolete 3GL Functions in Uniface 10.4 # learning # programming # software 2 reactions Comments Add Comment 3 min read Building Better Photos Through Data: How Photo Contests Teach Technical Skill Elena Brooks Elena Brooks Elena Brooks Follow Nov 3 '25 Building Better Photos Through Data: How Photo Contests Teach Technical Skill # photoshop # programming 4 reactions Comments Add Comment 6 min read Life was really hard growing up... so I became a philanthropist. Here's what I wish I knew... Free Game Brian Kim Brian Kim Brian Kim Follow Nov 29 '25 Life was really hard growing up... so I became a philanthropist. Here's what I wish I knew... Free Game # webdev # ai # programming # productivity 2 reactions Comments 1 comment 4 min read Day F9: Caffeine, Workout, and Arrogant Relationship Thoughts Somay Somay Somay Follow Nov 28 '25 Day F9: Caffeine, Workout, and Arrogant Relationship Thoughts # programming # productivity # career # beginners 6 reactions Comments Add Comment 2 min read 5 Ways to Make Your Scratch Sprite Move Smoothly (With Code Examples) Content ItsMyBot ItsMyBot ItsMyBot Follow Nov 25 '25 5 Ways to Make Your Scratch Sprite Move Smoothly (With Code Examples) Content # scratch # coding # gamedev # programming Comments Add Comment 2 min read Diving into Uniface 10.4: A Simple Guide to the $ude("load") Function 🚀 Peter + AI Peter + AI Peter + AI Follow Nov 2 '25 Diving into Uniface 10.4: A Simple Guide to the $ude("load") Function 🚀 # beginners # programming # software 2 reactions Comments Add Comment 3 min read How I Manage My Brand, Podcast, Music, and AI Company Without Burning Out Jaideep Parashar Jaideep Parashar Jaideep Parashar Follow Oct 24 '25 How I Manage My Brand, Podcast, Music, and AI Company Without Burning Out # webdev # programming # ai # productivity 16 reactions Comments 1 comment 2 min read 🧩 Windows 11 in Law Firms Despite “Incompatible” Hardware Thomas Delfing Thomas Delfing Thomas Delfing Follow Oct 12 '25 🧩 Windows 11 in Law Firms Despite “Incompatible” Hardware # programming # tutorial # security # lawtech 5 reactions Comments Add Comment 3 min read Why Tech Professionals Are Choosing European Winter Retreats: From Burnout to Intentional Mobility Сергей Иванов Сергей Иванов Сергей Иванов Follow Oct 13 '25 Why Tech Professionals Are Choosing European Winter Retreats: From Burnout to Intentional Mobility # news # programming # webdev # lifestyle Comments Add Comment 3 min read How the Ghetto Ruins US Crystal Evans Crystal Evans Crystal Evans Follow Oct 5 '25 How the Ghetto Ruins US # programming # webdev # beginners # javascript Comments Add Comment 4 min read How I Actually Use AI to Run My Business (and Keep My Sanity) Kenyata Bird Kenyata Bird Kenyata Bird Follow Nov 7 '25 How I Actually Use AI to Run My Business (and Keep My Sanity) # ai # programming # productivity # womenintech 2 reactions Comments Add Comment 4 min read Your Smart Home is Betraying You: How to Secure IoT Devices (Cameras, Speakers, Kettles) yanix Yanix yanix Yanix yanix Yanix Follow Oct 5 '25 Your Smart Home is Betraying You: How to Secure IoT Devices (Cameras, Speakers, Kettles) # webdev # programming # ai # javascript Comments Add Comment 4 min read Top Benefits of Using Scan-to-BIM for MEP Coordination in Renovations Reetie Lubana Reetie Lubana Reetie Lubana Follow Oct 1 '25 Top Benefits of Using Scan-to-BIM for MEP Coordination in Renovations # discuss # mep # architecture # programming Comments Add Comment 5 min read How to fix Cinema 4D render slow on multi-card servers? iRender GPU Render Farm iRender GPU Render Farm iRender GPU Render Farm Follow Oct 28 '25 How to fix Cinema 4D render slow on multi-card servers? # discuss # programming # beginners # tutorial 1 reaction Comments Add Comment 4 min read Are we living in a golden age of stupidity? Malik Abualzait Malik Abualzait Malik Abualzait Follow Oct 19 '25 Are we living in a golden age of stupidity? # ai # tech # programming 7 reactions Comments Add Comment 3 min read loading... trending guides/resources Kurukshetra Battlefield: A King’s Trembling Fear — Bhagavad Gita Chapter 1 as a Story Best Courses to Learn AI for 2026 Everything You Need to Launch a Product That Looks Legit (Even If You’re Bad at Design) digital marketing Solved: I hired two junior people and realized media buyers being bad at creative strategy is act... Website savings: where to cut and where to stop Solved: How to look for a good MSP How AI will change website development — and whether it will affect pricing How I Actually Use AI to Run My Business (and Keep My Sanity) Day F9: Caffeine, Workout, and Arrogant Relationship Thoughts Diving into Uniface 10.4: A Simple Guide to the $ude("load") Function 🚀 Migrating Legacy C Code: Obsolete 3GL Functions in Uniface 10.4 5 Ways to Make Your Scratch Sprite Move Smoothly (With Code Examples) Content Solved: PoE+++?! WHEN WILL THE MADNESS END? Life was really hard growing up... so I became a philanthropist. Here's what I wish I knew... Fre... Human vs. Machine Cognition: Brains, Minds, and Meaning Building Better Photos Through Data: How Photo Contests Teach Technical Skill 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:37 |
https://open.forem.com/davidscanu | David Scanu - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Follow User actions David Scanu Data Engineer @ Carrefour specializing in AI & cloud. Building ML pipelines, GenAI apps & automation on GCP. Passionate about scalable data solutions & intelligent systems. Location Caen, France Joined Joined on Oct 23, 2023 Personal website https://github.com/DavidScanu github website twitter website Education Développeur en Intelligence Artificielle (RNCP 34757) & Expert en Data Science (RNCP 37431) Work Ingénieur IA & Data | Pipelines Data Cloud | SQL, ML & Python More info about @davidscanu Badges 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 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 🤖 ML/DL & GenAI (Gemini API, vector DBs) 💾 Data Engineering (BigQuery, ETL pipelines) 🚀 Python, FastAPI, ML/DL 🎨 React/Next.js, Nuxt.js (Vue.js) ☁️ GCP, AWS, Azure, SQL, PostgreSQL 🔧 Git, SAP Ariba Currently learning ⚗️ Deepening Nuxt.js/Vue.js expertise for full-stack development. Exploring advanced MLOps practices and expanding GenAI capabilities. Post 3 posts published Comment 2 comments written Tag 0 tags followed Por qué estoy aprendiendo espanol? David Scanu David Scanu David Scanu Follow Jan 2 Por qué estoy aprendiendo espanol? # learning # motivation # español Comments Add Comment 5 min read Want to connect with David Scanu ? Create an account to connect with David Scanu . You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Las 5 frases que escucho cada vez que hablo de aprender idiomas (y cómo superarlas) David Scanu David Scanu David Scanu Follow Dec 7 '25 Las 5 frases que escucho cada vez que hablo de aprender idiomas (y cómo superarlas) # idiomas # español # consejos Comments Add Comment 6 min read Mis podcasts y canales de YouTube favoritos para aprender español David Scanu David Scanu David Scanu Follow Aug 11 '25 Mis podcasts y canales de YouTube favoritos para aprender español # beginners # learning 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 Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:37 |
https://docs.suprsend.com/reference/delink-event-schema | Delink Schema from Event - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation EVENTS Delink Schema from Event Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog EVENTS Delink Schema from Event OpenAI Open in ChatGPT Remove the linked schema from an event, making it schema-less. This allows the event to accept any payload structure without validation against a predefined schema. OpenAI Open in ChatGPT PATCH / v1 / {workspace} / event / {url_encoded_event_name} / delink_schema Try it Delink Schema from Event cURL Copy Ask AI curl -X PATCH "https://management-api.suprsend.com/v1/{workspace}/event/{url_encoded_event_name}/delink_schema/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 400 401 404 Copy Ask AI { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : null , "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace slug (staging, production, etc.) url_encoded_event_name string required URL encoded event name. Example - SHIPMENT%20ARRIVED Response 200 application/json Successfully delinked schema from event name string Event name Example : "user_signup" description string Description of the event Example : "Triggered whenever a new user successfully signs up on the platform" payload_schema any Schema has been delinked from the event Example : null created_at string<date-time> When the event was created Example : "2025-08-27T09:30:57.945326Z" $schema string JSON Schema reference for how the event API call should be structured Example : "https://schema.suprsend.com/event/v1/schema.json" Was this page helpful? Yes No Suggest edits Raise issue Previous Get Category Retrieve the current preference category for a workspace Next ⌘ I x github linkedin youtube Powered by Delink Schema from Event cURL Copy Ask AI curl -X PATCH "https://management-api.suprsend.com/v1/{workspace}/event/{url_encoded_event_name}/delink_schema/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 400 401 404 Copy Ask AI { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : null , "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } | 2026-01-13T08:48:37 |
https://aws.amazon.com/solutions/case-studies/odyssey-case-study/ | Customer Success Stories: Case Studies, Videos, Podcasts, Innovator stories Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS › Solutions SOLUTIONS Customer Success Stories Discover how customers across industries increase agility, optimize costs, and accelerate innovation using AWS How Blue Origin Built the First AI Agent-Designed Hardware for the Moon in Days, Not Years At Blue Origin, the mission is existential: to build a road to space, enabling millions of people to live and work beyond Earth. And getting there is literal rocket science, and beyond. It's about moving faster than the speed traditional aerospace development allows. That means rethinking how engineering teams work — and teaming up with AWS to build tools that turn specialized expertise into scalable AI workflows. One recent breakthrough: TEAREx (Thermal Energy Advanced Regolith Extraction), the first AI agent-designed hardware, built to operate on the lunar surface, developed from concept to 3D-printed part in days, using AWS. Read the case study Play Pinterest pushes boundaries of AI-powered discovery using AWS Pinterest transformed from an idea-sharing startup into one of the world's most sophisticated AI-powered discovery engines, serving 600 million monthly users who explore, share, and shop. What makes this journey remarkable isn't just the evolution of scale—it's how Pinterest has reimagined what social media can be, proving that generative AI can be used responsibly to drive positive user experiences alongside massive growth and profitability. Read the case study Customer Stories Generative AI Leading Cloud Innovators Browse All Customer Stories Phagos is using generative AI to change the way infectious diseases are treated Phagos has a remarkable mission: to end bacterial disease. Today, Phagos is turning that vision into reality by harnessing bacteriophages, nature's bacteria-killing viruses, to cure infectious disease. Bacteriophages, or phages, are the natural regulators of bacteria. In an era of rising antibiotic resistance, there is an urgent need for this new antibacterial solution. AWS technologies allow Phagos to decode massive genomic datasets to develop these customized treatments in just two months, compared to the 10+ years that traditional antibiotic development requires. Read the case study Play Featured Case Studies across industries 1 / 5 TwelveLabs unlocks the full potential of video for the world Mercedes Benz is transforming global IT moving to AWS for RISE with SAP and Agentic AI Condé Nast transforms publishing legacy into data-driven digital media for AI innovation Cox Automotive launched AI agents at scale using Amazon Bedrock AgentCore AudioShake is teaching machines to hear like humans, with AI Benefits 1,000,000+ of active customers every month. 330,000+ startups have used AWS to bring their ideas to life. Browse customer stories Loading Loading Loading Loading Loading Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:37 |
https://x.com/en/tos/previous/version_18 | Twitter 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="85OR" 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/2023-05-18/en/twitter-user-agreement-23-05-18.pdf" data-cta-link-new-tab="true"> Terms of Service Terms of Service Effective until September 29, 2023 If you live outside the European Union, EFTA States, or the United Kingdom, including if you live in the United States, the Twitter User Agreement comprises these Terms of Service , our Privacy Policy , the Twitter Rules and Policies , and all incorporated policies. If you live in the European Union, EFTA States, or the United Kingdom, the Twitter User Agreement comprises these Terms of Service , our Privacy Policy , the Twitter Rules and Policies , and all incorporated policies. Twitter 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 access to and use of our services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.twitter.com/rules-and-policies/twitter-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 Twitter and the Services, 1355 Market Street, Suite 900, San Francisco, CA 94103 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, or in the case of Periscope 16 years old, to use the Services. If you are accepting these Terms and using the Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so and have the authority to bind such entity to these Terms, in which case the words “you” and “your” as used in these Terms shall refer to such entity. 2. Privacy Our Privacy Policy ( https://www.twitter.com/privacy ) describes how we handle the information you provide to us when you use our 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 you provide, including compliance with applicable laws, rules, and regulations. You should only provide 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 via the Services or endorse any 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 is the sole responsibility of the person who originated such Content. We may not monitor or control the Content posted 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. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.twitter.com/en/rules-and-policies/twitter-report-violation#specific-violations and https://help.twitter.com/en/managing-your-account/suspended-twitter-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.twitter.com/forms/dmca ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 1355 Market Street, Suite 900 San Francisco, CA 94103 Reports: https://help.twitter.com/forms/dmca Email: copyright@twitter.com Your Rights and Grant of Rights in the Content You retain your rights to any Content you submit, 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). By submitting, posting or displaying 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 and distribute such Content in any and all media or distribution methods now known or later developed (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 provide, promote, and improve the Services and to make Content submitted to or through the Services available to other companies, organizations or individuals for the syndication, broadcast, distribution, Retweet, 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 submit, post or display on or through the Services. You agree that such Content will not contain material subject to copyright or other proprietary rights, unless you have necessary permission or are otherwise legally entitled to post the material and to grant us the license described above. 4. Using the Services Please review the Twitter Rules and Policies (and, for Periscope, the Periscope Community Guidelines at https://www.pscp.tv/content ), which are part of the User Agreement and outline what is prohibited on the Services. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. Our 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. You also agree not to misuse our 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 the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without our prior consent is expressly prohibited); (iv) forge any TCP/IP packet header or any part of the header information in any email or posting, or in any way use the Services to send altered, deceptive or false source-identifying information; or (v) 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. 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 Twitter, 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 Twitter 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 of the Services, you agree to the applicable Terms for Paid Services ( https://legal.twitter.com/purchaser-terms.html ). If you use developer features of the Services, including but not limited to Twitter for Websites ( https://developer.twitter.com/en/docs/twitter-for-websites ), Twitter Cards ( https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/abouts-cards ), Public API ( https://developer.twitter.com/en/docs ), or Sign in with Twitter ( https://developer.twitter.com/en/docs/authentication/guides/log-in-with-twitter ), you agree to our Developer Agreement ( https://developer.twitter.com/en/developer-terms/agreement ) and Developer Policy ( https://developer.twitter.com/en/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 our Services, these Terms, or the terms provided on https://developer.twitter.com/en/developer-terms . If you are a security researcher, you are required to comply with the rules of our Vulnerability Reporting Program ( https://hackerone.com/twitter ). The requirements set out in the preceding paragraph may not apply to those participating in our Vulnerability Reporting Program. If you use advertising features of the Services, you must agree to our Twitter Master Services Agreement ( https://ads.twitter.com/terms ). Your Account You may need to create an account to use some of our Services. You are responsible for safeguarding your account, so use a strong password and limit its use to this account. 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 has the sole purpose of enabling you to use and enjoy the benefit of the Services as provided on Twitter, 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 Twitter name or any of the Twitter trademarks, logos, domain names, other distinctive brand features, and other proprietary rights. 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 Twitter, 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. 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/en/managing-your-account/how-to-deactivate-twitter-account (and for Periscope, https://help.pscp.tv/customer/portal/articles/2460220 ) 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 for any or no reason, including, but not limited to, if we reasonably believe: (i) you have violated these Terms or our Rules and Policies or Periscope Community Guidelines , (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. 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, and 6. 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 “Twitter 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 TWITTER ENTITIES DISCLAIM ALL WARRANTIES AND CONDITIONS, WHETHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The Twitter 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 Twitter Entities or through the Services, will create any warranty or representation not expressly made herein. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TWITTER ENTITIES SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, 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 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 TWITTER 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 TWITTER 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. 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 twitter.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 California, excluding its choice of law provisions, will govern these Terms and any dispute that arises between you and us. All disputes related to these Terms or the Services will be brought solely in the federal or state courts located in San Francisco County, California, United States, and you consent to personal jurisdiction and waive any objection as to inconvenient forum. 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 California (excluding choice of law). 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. If you have any questions about these Terms, please contact us . Effective: May 18, 2023 Archive of Previous Terms Twitter Terms of Service If you live in the European Union, EFTA States, or the United Kingdom These Terms of Service (“Terms”) govern your access to and use of our services, including our various websites, SMS, APIs, email notifications, applications, buttons, widgets, ads, commerce services, and our other covered services ( https://help.twitter.com/rules-and-policies/twitter-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 Twitter International Unlimited Company (Co. number 503351, VAT number IE9803175Q), an Irish company with its registered office at One Cumberland Place, Fenian Street Dublin 2, D02 AX07 Ireland. The words “we,” “us,” and “our,” mean Twitter International 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, or in the case of Periscope 16 years old, to use the Services. If you are accepting these Terms and using the Services on behalf of a company, organization, government, or other legal entity, you represent and warrant that you are authorized to do so and have the authority to bind such entity to these Terms, in which case the words “you” and “your” as used in these Terms shall refer to such entity. 2. Privacy Our Privacy Policy ( https://www.twitter.com/privacy ) describes how we handle the information you provide to us when you use our 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 you provide, including compliance with applicable laws, rules, and regulations. You should only provide 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 via the Services or endorse any 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 is the sole responsibility of the person who originated such Content. We may not monitor or control the Content posted 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. Information regarding specific policies and the process for reporting or appealing violations can be found in our Help Center ( https://help.twitter.com/en/rules-and-policies/twitter-report-violation#specific-violations and https://help.twitter.com/en/managing-your-account/suspended-twitter-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.twitter.com/forms/dmca ) or contacting our designated copyright agent at: X Corp. Attn: Copyright Agent 1355 Market Street, Suite 900 San Francisco, CA 94103 Reports: https://help.twitter.com/forms/dmca Email: copyright@twitter.com Your Rights and Grant of Rights in the Content You retain your rights to any Content you submit, 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). By submitting, posting or displaying 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 and distribute such Content in any and all media or distribution methods now known or later developed (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 provide, promote, and improve the Services and to make Content submitted to or through the Services available to other companies, organizations or individuals for the syndication, broadcast, distribution, Retweet, 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 submit, post or display on or through the Services. You agree that such Content will not contain material subject to copyright or other proprietary rights, unless you have necessary permission or are otherwise legally entitled to post the material and to grant us the license described above. 4. Using the Services Please review the Twitter Rules and Policies (and, for Periscope, the Periscope Community Guidelines at https://pscp.tv/content ), which are part of the User Agreement and outline what is prohibited on the Services. You may use the Services only in compliance with these Terms and all applicable laws, rules and regulations. Our 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. You also agree not to misuse our 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 the Services is permissible if done in accordance with the provisions of the robots.txt file, however, scraping the Services without our prior consent is expressly prohibited); (iv) forge any TCP/IP packet header or any part of the header information in any email or posting, or in any way use the Services to send altered, deceptive or false source-identifying information; or (v) 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. 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 Twitter, 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 Twitter 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 of the Services, you agree to the applicable Terms for Paid Services ( https://legal.twitter.com/en/purchaser-terms.html ). If you use developer features of the Services, including but not limited to Twitter for Websites ( https://developer.twitter.com/docs/twitter-for-websites ), Twitter Cards ( https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/abouts-cards ), Public API ( https://developer.twitter.com/en/docs ), or Sign in with Twitter ( https://developer.twitter.com/en/docs/authentication/guides/log-in-with-twitter ), you agree to our Developer Agreement ( https://developer.twitter.com/en/developer-terms/agreement ) and Developer Policy ( https://developer.twitter.com/en/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 our Services, these Terms, or the terms provided on https://developer.twitter.com/en/developer-terms . If you are a security researcher, you are required to comply with the rules of our Vulnerability Reporting Program ( https://hackerone.com/twitter ). The requirements set out in the preceding paragraph may not apply to those participating in our Vulnerability Reporting Program. If you use advertising features of the Services, you must agree to our Twitter Master Services Agreement ( https://ads.twitter.com/terms ). Your Account You may need to create an account to use some of our Services. You are responsible for safeguarding your account, so use a strong password and limit its use to this account. 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 has the sole purpose of enabling you to use and enjoy the benefit of the Services as provided on Twitter, 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 Twitter name or any of the Twitter trademarks, logos, domain names, other distinctive brand features, and other proprietary rights. 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 Twitter, 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. 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.twitter.com/en/managing-your-account/how-to-deactivate-twitter-account (and for Periscope, https://help.pscp.tv/customer/portal/articles/2460220 ) 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 for any or no reason, including, but not limited to, if we reasonably believe: (i) you have violated these Terms or the Twitter Rules and Policies or Periscope Community Guidelines , (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. 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, and 6. If you believe your account was terminated in error you can file an appeal following the steps found in our Help Center ( https://help.twitter.com/forms/general?subtopic=suspended ). For the avoidance of doubt, these Terms survive the deactivation or termination of your account. 5. Limitations of Liability By using the Services you agree that X Corp., its parents, affiliates, related companies, officers, directors, employees, agents representatives, partners and licensors, liability is limited to the maximum extent permissible in your country of residence. 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 twitter.com/tos , will govern our relationship with you. Other than for changes addressing new functions or made for legal reasons, we will notify you 30 days in advance of making effective changes to these Terms that impact the rights or obligations of any party to these Terms, 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. 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. If you have any questions about these Terms, please contact us . Effective: May 18, 2023 Archive of Previous Terms X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:37 |
https://docs.suprsend.com/reference/create-update-workflow | Create or Update Workflow - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation WORKFLOWS Create or Update Workflow Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog WORKFLOWS Create or Update Workflow OpenAI Open in ChatGPT Create a new workflow or update the draft version of an existing one OpenAI Open in ChatGPT POST / v1 / {workspace} / workflow / {slug} Try it cURL cURL Copy Ask AI curl -X POST "https://management-api.suprsend.com/v1/{workspace}/workflow/{slug}/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' \ --data '{ "name": "Welcome Email", "description": "Sends welcome email to new users", "category": "transactional", "tags": ["welcome", "onboarding"], "tree": { "nodes": [ { "name": "Send Email", "node_type": "send_email", "properties": { "template": "welcome-email-template", "subject": "Welcome to our platform!" }, "description": "Send welcome email to new users" } ] } }' 201 401 404 Copy Ask AI { "name" : "Welcome Email" , "description" : "Sends welcome email to new users" , "category" : "transactional" , "tags" : [ "welcome" , "onboarding" ], "tree" : { "nodes" : [ { "name" : "Send Email" , "node_type" : "send_email" , "properties" : { "template" : "welcome-email-template" , "subject" : "Welcome to our platform!" }, "description" : "Send welcome email to new users" } ] }, "validation_result" : { "is_valid" : true , "errors" : [] } } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace where the workflow should be created (staging, production, etc.) slug string required Unique identifier of the workflow. You can get it from workflow settings for existing workflows. Query Parameters commit boolean default: false Whether to commit the workflow immediately. Workflow will be successfully committed only if validation_result.is_valid is true. commit_message string Commit message describing the changes (required if commit=true) Body application/json name string required Human-readable name of the workflow. Workflow slug is generated from this name for new workflows. Example : "Welcome Sequence" category string required Notification category of the workflow. Used to apply category-specific settings and preferences. Example : "transactional" trigger_type enum<string> required You can trigger a workflow either via API by passing its slug directly, or through an event-based system where the workflow runs when a specific event occurs. You can compare both methods here . If the workflow should run when a user enters or exits a list, use trigger_type = event . Available options : event , api tree object required Node tree structure of the workflow. Contains the nodes array with all workflow nodes and their configuration. Show child attributes description string | null Description explaining the usecase of the workflow is_enabled boolean default: true Whether the workflow should be enabled tags string[] Tags are used for grouping and filtering workflows in list. Example : "onboarding-sequence" payload_schema object Schema to validate workflow api data structure. Used only when trigger_type = api. Show child attributes trigger_events string[] Events that trigger this workflow (required if trigger_type = event). In case of list entry/exit, event names will be $USER_ENTERED_LIST - <list_id> and $USER_EXITED_LIST - <list_id> respectively. ratelimit object Throttle settings for the workflow. This is used to limit the number of times a workflow can be executed per user in a given time period. Show child attributes conditions object[] | null Trigger Conditions. Workflow will be executed if any of the conditions in this array evaluate to true. Show child attributes override_recipients_type enum<string> Override recipients using a property from the trigger payload. Type defines if the workflow should run for a list of users or a single object . Only applicable for trigger_type = event . Available options : user , single_object_fields Example : "user" override_recipients_user_expr string | null JQ expression to override recipients when override_recipients_type = user . Only applicable for trigger_type = event . Example : ".distinct_id" override_recipients_single_object_fields_expr object JQ expression to override recipients with object when override_recipients_type = single_object_fields . Only applicable for trigger_type = event . Show child attributes Example : { "id" : ".object_id" , "object_type" : ".object_type" , "$object_subscriptions_query.depth" : "2" } override_actor_user_expr string | null JQ expression to override actor. Only applicable for trigger_type = event . Example : ".actor_id" override_tenant_expr string | null JQ expression to override tenant . Only applicable for trigger_type = event . Example : ".tenant_id" Response 201 application/json The response includes the same workflow object as input along with a validation_result field that indicates whether the workflow configuration is valid. validation_result object Show child attributes Was this page helpful? Yes No Suggest edits Raise issue Previous Commit Workflow Commit a workflow to make the draft version live. Next ⌘ I x github linkedin youtube Powered by cURL cURL Copy Ask AI curl -X POST "https://management-api.suprsend.com/v1/{workspace}/workflow/{slug}/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' \ --data '{ "name": "Welcome Email", "description": "Sends welcome email to new users", "category": "transactional", "tags": ["welcome", "onboarding"], "tree": { "nodes": [ { "name": "Send Email", "node_type": "send_email", "properties": { "template": "welcome-email-template", "subject": "Welcome to our platform!" }, "description": "Send welcome email to new users" } ] } }' 201 401 404 Copy Ask AI { "name" : "Welcome Email" , "description" : "Sends welcome email to new users" , "category" : "transactional" , "tags" : [ "welcome" , "onboarding" ], "tree" : { "nodes" : [ { "name" : "Send Email" , "node_type" : "send_email" , "properties" : { "template" : "welcome-email-template" , "subject" : "Welcome to our platform!" }, "description" : "Send welcome email to new users" } ] }, "validation_result" : { "is_valid" : true , "errors" : [] } } | 2026-01-13T08:48:37 |
https://codereview.stackexchange.com | Code Review Stack Exchange Skip to main content Stack Exchange Network Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange s-popover#show" data-s-popover-placement="bottom-start" /> Loading… Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company, and our products current community Code Review help chat Code Review Meta your communities Sign up or log in to customize your list. more stack exchange communities company blog Log in Sign up Home Questions Unanswered AI Assist Tags Chat Users Companies Stack Internal Stack Overflow for Teams is now called Stack Internal . Bring the best of human thought and AI automation together at your work. Try for free Learn more Stack Internal Bring the best of human thought and AI automation together at your work. Learn more Stack Internal Knowledge at work Bring the best of human thought and AI automation together at your work. Explore Stack Internal Explore our questions Ask Question python java c# c++ javascript performance beginner python-3.x algorithm php more tags Active Hot Week Month 2 votes 0 answers 76 views Pre setup script to get user metadata and check supported api's within the browser/device javascript performance design-patterns ecmascript-6 Sᴀᴍ Onᴇᴌᴀ ♦ 29.7k modified 7 hours ago 7 votes 1 answer 151 views Wrapper for Google_Service_Calendar as a Symfony service php dependency-injection session wrapper symfony3 Sᴀᴍ Onᴇᴌᴀ ♦ 29.7k modified 8 hours ago 5 votes 1 answer 199 views Improved O(1) Snake Game in C c game snake-game curses chux 36.8k modified 13 hours ago 5 votes 2 answers 126 views Scraping reddit using Python python web-scraping Chris 8,719 answered 16 hours ago 4 votes 5 answers 759 views Simple Clicker Game in Python python tkinter toolic 17.4k modified 17 hours ago 6 votes 5 answers 265 views Slow anagrams detection programming-challenge time-limit-exceeded perl toolic 17.4k answered 20 hours ago 7 votes 3 answers 1k views Object-oriented coffee machine python python-3.x object-oriented Toby Speight 89.3k modified yesterday 5 votes 3 answers 381 views Matrix row operation mental practice tool python object-oriented console numpy matrix Reinderien 71.5k modified yesterday 6 votes 1 answer 2k views C++ and SDL2: Snake implementation c++ object-oriented c++14 snake-game sdl Deduplicator 20.2k modified yesterday 2 votes 0 answers 6k views Example of PyQt5 Snake game python python-3.x game snake-game pyqt Deduplicator 20.2k modified yesterday 4 votes 1 answer 219 views Can you criticise my Snake Game in C? beginner c snake-game Deduplicator 20.2k modified yesterday 6 votes 2 answers 887 views Simple Snake Game in C++ c++ beginner object-oriented snake-game Deduplicator 20.2k modified yesterday 5 votes 1 answer 289 views Snake game in rust game rust snake-game sdl Deduplicator 20.2k modified yesterday 4 votes 1 answer 37 views Fast method to detect Stop Loss vs Take Profit hits in R trading backtest comparative-review r finance Justin Chang 2,447 modified yesterday Browse more Questions Hot Network Questions Why is the word "receive" only two syllables when it has so many vowels? кач - is this a slang word? Short story - metal mice-like creatures Multinomial models interaction on probability Why do the V Rising achievements on Steam have such low unlock percentages? Does the 22° angle in the right triangle seem to correspond to the maximum of this area ratio? When did German nouns become capitalized? Can we naturally incorporate gravity into a QFT Lagrangian? Representing a composition of variable sized structures usage of alcohol based perfumes (I Thessalonians 1:3) A question about prepositions at the end of this verse (comment added) What makes Certificate-Based Authentication phishing resistant? Western with a violent father and a conflict between two ranches How to determine the rough time period after travel to the Pleistocene? Sentence that contains both a statement and its opposite Can no longer change BoldFont with New Computer Modern Can I pigtail #14/2 wire off #8/3 gauge to run 3 receptacles? Can you get to 8? What is the species of this seed? Gender for 3rd person pronoun of a person with nickname Are the YouTube channel Courts & Crimes's shorts AI-generated deep fakes? A reformulation of lower bounds for R(k,k) via additive constraints in circulant 2-colorings — is this known? lua-unicode-math clash with mismath 1980s book about a woman who time-travels throughout her life more hot questions Recent questions feed Subscribe to RSS Recent questions feed To subscribe to this RSS feed, copy and paste this URL into your RSS reader. Code Review Tour Help Chat Contact Feedback Company Stack Overflow Stack Internal Stack Data Licensing Stack Ads About Press Legal Privacy Policy Terms of Service cookie-settings#toggle" class="s-btn s-btn__link py4 js-gps-track -link" data-gps-track="footer.click({ location: 1, link: 38 })" data-consent-popup-loader="footer"> Cookie Settings Cookie Policy Stack Exchange Network Technology Culture & recreation Life & arts Science Professional Business API Data Blog Facebook Twitter LinkedIn Instagram Site design / logo © 2026 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2026.1.12.38533 | 2026-01-13T08:48:37 |
https://youtu.be/undefined | - 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:48:37 |
https://dev.to/t/ai/page/5 | Artificial Intelligence Page 5 - 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 Artificial Intelligence Follow Hide Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities found in humans and in nature. Create Post submission guidelines Posts about artificial intelligence. Older #ai posts 2 3 4 5 6 7 8 9 10 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Build a Hashtag Research Tool That Finds Hidden Gems Olamide Olaniyan Olamide Olaniyan Olamide Olaniyan Follow Jan 12 Build a Hashtag Research Tool That Finds Hidden Gems # webdev # programming # ai # tutorial Comments Add Comment 9 min read EDCA Admission Protocols: Introducing an Explicit Admission Layer for AI Systems yuer yuer yuer Follow Jan 12 EDCA Admission Protocols: Introducing an Explicit Admission Layer for AI Systems # ai # architecture # security # systemdesign Comments Add Comment 2 min read Understanding the A2UI Protocol: Building with Java and Spring Boot vishalmysore vishalmysore vishalmysore Follow Jan 10 Understanding the A2UI Protocol: Building with Java and Spring Boot # ai # architecture # springboot # java Comments Add Comment 6 min read Building an Intelligent Product Discovery Agent with Algolia ANIRUDDHA ADAK ANIRUDDHA ADAK ANIRUDDHA ADAK Follow Jan 12 Building an Intelligent Product Discovery Agent with Algolia # devchallenge # algoliachallenge # ai # agents Comments Add Comment 2 min read Alignment Protocol v3.0: Defining Legal Admission Semantics for AI-Controlled Systems yuer yuer yuer Follow Jan 12 Alignment Protocol v3.0: Defining Legal Admission Semantics for AI-Controlled Systems # ai # architecture # security Comments Add Comment 1 min read Under the Hood: VaidhLlama Architecture & Training Pipeline Vivek Patel Vivek Patel Vivek Patel Follow Jan 12 Under the Hood: VaidhLlama Architecture & Training Pipeline # ai # machinelearning # python # finetuning 6 reactions Comments Add Comment 6 min read Cuando le dices a tu LLM "No pulses ese botón" Joaquin Jose del Cerro Murciano Joaquin Jose del Cerro Murciano Joaquin Jose del Cerro Murciano Follow Jan 12 Cuando le dices a tu LLM "No pulses ese botón" # spanish # ai # promptengineering # machinelearning Comments Add Comment 12 min read Human–AI Collaboration in Project Teams — Redefining Leadership and Decision-Making Aaryan Gupta Aaryan Gupta Aaryan Gupta Follow Jan 12 Human–AI Collaboration in Project Teams — Redefining Leadership and Decision-Making # ai # leadership # management # productivity Comments Add Comment 2 min read AI Weekly Reflection: Week of 1/6/2026 - 1/12/2026 Empty Chair Empty Chair Empty Chair Follow Jan 12 AI Weekly Reflection: Week of 1/6/2026 - 1/12/2026 # ai # automation # transparency # experiment Comments Add Comment 1 min read Beyond Nested Queries: A Practical Guide to SQL Subquery Flattening SQLFlash SQLFlash SQLFlash Follow Jan 12 Beyond Nested Queries: A Practical Guide to SQL Subquery Flattening # sql # mysql # ai # programming Comments Add Comment 5 min read From ChatGPT to Gemini: How We Built a GDPR-Compliant CV Parser for Odoo DERICK TEMFACK DERICK TEMFACK DERICK TEMFACK Follow Jan 11 From ChatGPT to Gemini: How We Built a GDPR-Compliant CV Parser for Odoo # python # webdev # ai # productivity Comments Add Comment 5 min read My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack ILshat Khamitov ILshat Khamitov ILshat Khamitov Follow Jan 11 My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack # webdev # javascript # programming # ai Comments Add Comment 1 min read I built a runtime execution kernel for AI agents — not another framework Kashif Sabri Kashif Sabri Kashif Sabri Follow Jan 9 I built a runtime execution kernel for AI agents — not another framework # python # ai # architecture # opensource 3 reactions Comments Add Comment 3 min read AI is changing how we build software: here's how to do it safely Colosl Colosl Colosl Follow Jan 11 AI is changing how we build software: here's how to do it safely # ai # cybersecurity # softwaredevelopment Comments Add Comment 6 min read Why n8n Is Quietly Becoming a Power Tool for DevOps & SRE Teams❓ Sahar Batool Sahar Batool Sahar Batool Follow Jan 12 Why n8n Is Quietly Becoming a Power Tool for DevOps & SRE Teams❓ # devops # ai # automation # opensource Comments Add Comment 2 min read Building an Autonomous Medical Pre-Authorization Agent: My Experiment with AI in Healthcare Aniket Hingane Aniket Hingane Aniket Hingane Follow Jan 12 Building an Autonomous Medical Pre-Authorization Agent: My Experiment with AI in Healthcare # ai # python # agents # healthcare 1 reaction Comments Add Comment 5 min read The Creator's Paradox in the AI Era: How to Stay Generative When Everything Gets Scraped Narnaiezzsshaa Truong Narnaiezzsshaa Truong Narnaiezzsshaa Truong Follow Jan 11 The Creator's Paradox in the AI Era: How to Stay Generative When Everything Gets Scraped # discuss # ai # productivity # career Comments Add Comment 2 min read The Infrastructure Behind Reliable Enterprise AI Agents Yeahia Sarker Yeahia Sarker Yeahia Sarker Follow Jan 12 The Infrastructure Behind Reliable Enterprise AI Agents # agents # ai # architecture Comments Add Comment 4 min read Why Asking for Better Outputs Misses the Real Problem Leena Malhotra Leena Malhotra Leena Malhotra Follow Jan 12 Why Asking for Better Outputs Misses the Real Problem # programming # ai # imagegen # nanobanana 2 reactions Comments Add Comment 5 min read Agile for Agents Mike Lady Mike Lady Mike Lady Follow Jan 11 Agile for Agents # ai # vibecoding # claudecode Comments Add Comment 13 min read Google's Universal Commerce Protocol: What Developers Need to Know Okkar Kyaw Okkar Kyaw Okkar Kyaw Follow Jan 12 Google's Universal Commerce Protocol: What Developers Need to Know # webdev # ai # gemini Comments Add Comment 4 min read What's new in Webpixels v3 Alexis Enache Alexis Enache Alexis Enache Follow Jan 12 What's new in Webpixels v3 # webdev # programming # ai # productivity Comments Add Comment 3 min read EU Digital Omnibus: New Requirements for Websites and Online Services Mehwish Malik Mehwish Malik Mehwish Malik Follow Jan 12 EU Digital Omnibus: New Requirements for Websites and Online Services # webdev # ai # beginners # productivity 17 reactions Comments Add Comment 3 min read Create Your First MCP Server in 5 Minutes with create-mcp-server Ali Ibrahim Ali Ibrahim Ali Ibrahim Follow Jan 11 Create Your First MCP Server in 5 Minutes with create-mcp-server # webdev # javascript # ai # programming 1 reaction Comments Add Comment 10 min read Code Coverage Best Practices for Agentic Development Ariel Frischer Ariel Frischer Ariel Frischer Follow Jan 11 Code Coverage Best Practices for Agentic Development # webdev # programming # ai # productivity Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:37 |
https://aws.amazon.com/cn/api-gateway/ | Amazon API Gateway云网关_API网关托管服务-AWS云服务 跳至主要内容 单击此处返回 Amazon Web Services 主页 关于 AWS 联系我们 支持 中文（简体） 我的账户 登录 创建 AWS 账户 关闭 配置文件 您的配置文件有助于改善您与精选 AWS 体验的交互。 登录 关闭 配置文件 您的配置文件有助于改善您与精选 AWS 体验的交互。 查看配置文件 退出 Amazon Q 产品 解决方案 定价 文档 了解 合作伙伴网络 AWS Marketplace 客户支持 活动 探索更多信息 关闭 عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) 关闭 我的配置文件 注销 AWS Builder ID AWS 管理控制台 账户设置 账单与成本管理 安全证书 AWS Personal Health Dashboard 关闭 支持中心 专家帮助 知识中心 AWS Support 概述 AWS re:Post 单击此处以返回 Amazon Web Services 主页 免费试用 联系我们 产品 解决方案 定价 AWS 简介 入门 文档 培训和认证 开发人员中心 客户成功案例 合作伙伴网络 AWS Marketplace 支持 AWS re:Post 登录控制台 下载移动应用 Amazon API Gateway 概览 功能 定价 入门 资源 常见问题 合作伙伴 产品 › 联网和内容分发 › Amazon API Gateway 使用 AWS Free Tier 每月免费接收 100 万个 API 调用，为期 12 个月 Amazon API Gateway 创建、维护和保护任意规模的 API API Gateway 入门 为什么选择 API Gateway？ Amazon API Gateway 是一种完全托管的服务，可以帮助开发者轻松创建、发布、维护、监控和保护任意规模的 API。API 充当应用程序的前门，可从您的后端服务访问数据、业务逻辑或功能。使用 API Gateway，您可以创建 RESTful API 和 WebSocket API，以便实现实时双向通信应用程序。API Gateway 支持容器化和无服务器工作负载，以及 Web 应用程序。 API Gateway 负责管理所有任务，涉及接受和处理成千上万个并发 API 调用，包括流量管理、CORS 支持、授权和访问控制、限制、监控，以及 API 版本管理。API Gateway 没有最低费用或启动成本。您只需为您收到的 API 调用和传出的数据量付费。由于采用 API Gateway 分级定价模式，随着 API 使用量的增加，您可以减少花费。 RESTful API 使用 HTTP API 构建针对无服务器工作负载和 HTTP 后端优化的 RESTful API。 HTTP API 是构建只需要 API 代理功能的 API 的理想之选。如果您的 API 需要在单个解决方案中具备 API 代理功能和 API 管理功能，则 API Gateway 也会提供 REST API 。 WebSocket API 使用 WebSocket API 构建实时双向通信应用程序，如聊天应用和流式控制面板。API Gateway 可维持永久连接以处理您的后端服务与客户端之间的消息传输。 Page topics 优势 优势 Open all 高效的 API 开发 使用 API Gateway 同时运行同一 API 的多个版本，从而使您能够快速迭代、测试和发布新版本。您只需为对 API 进行的调用和传出的数据量付费，没有最低费用，也无需预先承诺。 任意规模都能高效使用 使用 Amazon CloudFront，利用我们的全球边缘站点网络为最终用户提供 API 请求和响应的可能的最低延迟。限制流量并授权 API 调用，以确保后端操作能够承受流量高峰，并且不会不必要地调用后端系统。 大规模节约成本 API Gateway 针对 API 请求提供分级定价模式。最高层 API 请求的价格低至每百万个请求 0.90 USD，随着 AWS 账户中每个区域 API 使用量的增加，您可以降低成本。 轻松监控 通过 API Gateway 控制面板可监控有关 API 调用、数据延迟和错误率的性能指标和信息，这样就可以使用 Amazon CloudWatch 直观地监控对您的服务的调用。 灵活的安全控制机制 使用 AWS Identity and Access Management (IAM) 和 Amazon Cognito 授予对 API 的访问权限。如果您使用 OAuth 令牌，API Gateway 可提供本机 OIDC 和 OAuth2 支持。为了支持自定义授权要求，您可以从 AWS Lambda 执行 Lambda 授权程序。 RESTful API 选项 使用 HTTP API 或 REST API 创建 RESTful API。HTTP API 是为大多数使用案例构建 API 的最佳方式，它们的成本最高比 REST API 低 71%。如果您的使用案例在单个解决方案中同时需要 API 代理功能和管理功能，您可以使用 REST API。 WirelessCar 了解互联出行提供商 WirelessCar 如何使用适用于 Java 的 AWS Lambda SnapStart 增强初创企业的绩效 阅读案例研究 Odyssey Interactive 了解游戏工作室 Odyssey Interactive 如何使用 AWS 上的托管基础设施在全球推出其首款多人游戏 Omega Strikers。 阅读案例研究 Betterfly 了解 Betterfly 如何使用基于 AWS 构建的数字解决方案简化团体保护和福利管理，并鼓励用户养成良好的日常习惯。 阅读案例研究 TiVo 了解身处媒体和娱乐行业的 TiVo 如何使用 AWS Lambda 和 Amazon API Gateway 实现流媒体服务的突发可扩展性和稳定的正常运行时间。 阅读案例研究 API Gateway 入门 1 注册 AWS 账户 立即享受 AWS Free Tier 。 2 通过分步教程进行学习 通过 简单教程 进行探讨和学习。 3 开始使用 AWS 进行构建 访问 AWS 管理控制台 。 后续步骤 功能页面 了解有关 API Gateway 的更多信息 访问功能页面 入门 准备好开始构建？ 开始使用 Contact us 还有更多问题？ 联系我们 登录控制台 了解有关 AWS 的信息 什么是 AWS？ 什么是云计算？ AWS 可访问性 什么是 DevOps？ 什么是容器？ 什么是数据湖？ 什么是人工智能（AI）？ 什么是生成式人工智能？ 什么是机器学习（ML）？ AWS 云安全性 最新资讯 博客 新闻稿 AWS 资源 入门 培训和认证 AWS 解决方案库 架构中心 产品和技术常见问题 分析报告 AWS 合作伙伴 AWS 上的开发人员 开发人员中心 软件开发工具包与工具 运行于 AWS 上的 .NET 运行于 AWS 上的 Python 运行于 AWS 上的 Java 运行于 AWS 上的 PHP 运行于 AWS 上的 JavaScript 帮助 联系我们 获取专家帮助 提交支持工单 AWS re:Post Knowledge Center AWS Support 概览 法律人员 亚马逊云科技诚聘英才 创建账户 Amazon 是一个倡导机会均等的雇主： 反对少数族裔、妇女、残疾人士、退伍军人、性别认同和性取向歧视。 语言 عربي Bahasa Indonesia Deutsch English Español Français Italiano Português Tiếng Việt Türkçe Ρусский ไทย 日本語 한국어 中文 (简体) 中文 (繁體) 隐私权 | 可访问性 | 网站条款 | Cookie 首选项 | © 2024, Amazon Web Services, Inc. 或其联属公司。保留所有权利。 您使用的浏览器已过时。请升级到现代浏览器，以改善您的体验。 终止对 Internet Explorer 的支持 知道了 AWS 对 Internet Explorer 的支持将于 07/31/2022 结束。受支持的浏览器包括 Chrome、Firefox、Edge 和 Safari。 了解详情 » 知道了 | 2026-01-13T08:48:37 |
https://www.lob.com/faq | FAQ Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Direct Mail FAQs From direct mail marketing basics to advanced analytics, we cover the most common direct mail marketing questions so every campaign you send can be a success. Direct Mail Basics Direct Mail Costs How to Send Direct Mail Direct Mail Strategy Direct Mail Basics What is direct mail? Direct mail is a form of direct marketing that's physically delivered to mailboxes. This mail includes marketing materials such as postcards, folded self-mailers, buck slips, flyers, catalogs, and sales letters. Any physical correspondence sent via various postal services is classified as direct mail marketing. In a highly digitalized world, direct mail can be that breath of fresh air consumers seek. Those who implement direct mail marketing in their omnichannel strategy can supercharge their ROI , stand out from competitors, and successfully build customer relationships. Overall, direct mail is: Creative and versatile Tangible and personable Cost-effective Easily tracked The perfect addition to your digital marketing strategy What is a major strength of direct mail advertising? There are many advantages to implementing direct mail in your omnichannel marketing strategy . However, one of the most significant strengths of direct mail advertising is its cost-effectiveness. Automated direct mail drives massive ROI, with 74% of marketers saying direct mail delivers the best ROI of any channel. When marketers combine email with direct mail, there's an increase of 60% in ROI and 40% in conversion rates. With Lob, companies have even achieved a 200% ROI. Some other major advantages include higher open rates and response rates. For example, if your goal is to generate more leads, direct mail has a 130% higher response rate than email. When used in the right situations, targeting specific customers, you can effectively retarget and retain leads, boost brand awareness, improve customer communications, and more. It's an effective way to stand out from the digital noise and your competitors. Related: Lob's Direct Mail ROI Calculator What are some disadvantages of using direct mail as an advertising medium? Direct mail is effective — that much is certain. However, like any channel, direct mail campaigns can fail when they aren't done strategically. Instead of experiencing the benefits of direct mail, inefficient workflows can have the opposite effect. To avoid this, you must proactively manage your direct mail campaigns and be aware of the possible shortcomings of direct mail. Here are some potential disadvantages of direct mail and, more importantly, how to address them: Direct mail can be perceived as junk if it is not designed or worded correctly. You don't want your mail to come across as "junk" mail, so take the time to craft strong brand messaging and create well-designed material. Learn more about the benefits of professionally designed templates . If you send mail too often, you risk redundancy. You'll need to develop a strategy to send the right mail to the right customer at the right time. Not all possible recipients should receive every mail piece you send out. Some believe direct mail doesn't support eco-friendly branding. However, this isn't the case. Direct mail can be a sustainable method . For example, all mail sent with Lob is carbon neutral through the entire lifecycle. Lob offsets the emissions of every mail piece through reforestation and renewable energy projects. How effective is direct mail marketing? Email marketing and other digital marketing channels have been all the rage in recent years — and rightfully so, as they offer immense value. However, direct mail can yield a higher ROI when your goal is to achieve higher response and open rates. For example, direct mail open rates can reach up to 90% . When you have access to an automated direct mail platform, you can quickly and easily send relevant, customized direct mail. Direct mail can yield a 13x higher base response rate than email when used on its own. However, you can experience even higher rates when your direct mail campaigns are created alongside other channels, integrating with the platforms your company is already using — for example, Salesforce CRM . Some of the reasons direct mail is so effective compared to digital channels, like email, include: Direct mail doesn't require an opt-in. A longer shelf life. Won't get lost in a junk folder. Reaching customers who don't use email, unsubscribed from your mailing list, or do not spend much time online. The key is to know when to choose which, thinking about variables like budget, who you wish to target, the timeline, and compliance requirements. The ultimate goal is to reduce silos so all channels can work together within a cohesive strategy. Is direct mail sustainable? Not all direct mail is sustainable, so partnering with a platform that prioritizes environmental issues is crucial. All Lob mail is carbon neutral, achieved through recycling, reforestation, and carbon offsets. Lob's commitment to sustainable mail helps significantly reduce the carbon footprints of direct mail campaigns. If your brand has sustainability goals or requirements, Lob is proud to offer sustainable direct mail campaigns that drive engagement and inspire brand loyalty. In 2020, Lob launched Lob.org , a place for all things related to sustainability and social impact. Current programs are based on racial justice, civic action, and sustainability. For example, Lob plants more trees than it uses and prints on FSC-certified and PCW paper. Since 2018, Lob has planted over 500,000 trees, representing more than double the amount used to produce mail. Learn more about how Lob minimizes its footprint . Direct Mail Costs How much does a direct mail campaign cost? Each direct mail campaign will require a budget review, especially if you're making significant changes in the number of customers you're sending mail to. The size and scope of each campaign matter. Some of the most important considerations include the following: Printing costs include the cost of ink, paper, and the printing process. Postage costs include the cost of sending the mail to its desired destination. This cost is determined by several factors, including location (local, national, or international), size, weight, etc. Production costs, including designer and copywriters. You'll want to partner with an automated direct mail platform to get the most bang for your buck. To ensure the most significant ROI, you'll need to make your team more efficient, eliminate time-consuming workflows, and better manage risk — all of which are possible with Lob. The actual costs associated with direct mail vary, depending on the considerations above. With Lob, pricing is based on your plan : Developer plan — This plan costs $0 per month and is ideal for companies exploring the concept of direct mail marketing. Print and post costs are combined and are $0.77 per postcard and $0.89 per letter. Small business plan — This plan costs $260 per month and is ideal for companies that send up to 3,000 monthly mailings. The combined print and post costs are $0.51 per postcard, $0.72 per letter, and $0.87 per check. Growth plan — This plan costs $550 per month and is ideal for growing companies that send up to 6,000 monthly mailings. Print and post costs are $0.48 per postcard, $0.69 per letter, and $0.87 per check. Enterprise plan — To discuss this plan, contact Lob . This plan is ideal for high-volume mailers seeking unbeatable per-piece printing costs. You can also purchase add-ons. For example, you can access 50,000 U.S. address verifications for $450/month with the small business plan. How much does direct mail advertising cost? Direct mail advertising costs depend on several variables, including the materials you send and the overall complexity of your advertising campaign. For example, the more consumers you target, the more your campaign will cost. The goal is to target customers as effectively as possible to achieve the highest ROI. When partnering with a platform like Lob, you get flat-rate pricing . This pricing also comes with many perks, including in-transit mail tracking. The best option will depend on several factors, including maximum mail capacity, the number of users, and the overall budget. Why invest in direct mail? There are many advantages associated with direct mail, including the following: It is cost-effective, as seen through high conversion and ROI rates. Direct mail is personal — 67% of consumers think physical mail is more personal than online marketing content. The ability to reach a specific target audience, especially those in a localized region. This channel is an effective means of building trust. It grabs the attention of consumers. As marketers implement more omnichannel strategies, direct mail should be a top priority. Direct mail marketing cohesively works with digital marketing, helping businesses supercharge ROI. Response rates are specifically high when using direct mail. What is Every Door Direct Mail? Every Door Direct Mail® (EDDM®) is a USPS service that promotes businesses within local communities. For example, if you want to send out menus, coupons, or other promotional material, EDDM can help. The EDDM Online Tool can help filter recipients using US Census data. There are two options for EDDM: Every Door Direct Mail – Retail® (EDDM Retail) or entering an EDDM bulk mailing at a Business Mail Entry Unit (BMEU). The best option for you depends on your industry and desired volume. EDDM BMEU is ideal for most large-volume mailers. Regardless of your choice, you will need to drop off your mail at either the Post Office (for EDDM Retail) or a large USPS mail processing center (for BMEU). Here is the EDDM process: Create or use an existing USPS.com account. Select neighborhood and audience based on various demographics. Design and print mail — this step can be time-consuming and costly if you do not have the right tools and support in place. Choose a drop-off location. Print forms and prep mailing bundles. Drop off or ship mail. How much is the USPS Every Door Direct Mail? EDDM Retail® USPS Marketing Flats currently cost $0.187 per piece (the minimum is 200 pieces, and the maximum is 5000 per day per ZIP Code). EDDM BMEU USPS Marketing Mail Flats are currently as low as $0.182 per piece These prices are for materials up to 3.3 ounces. The above rates do not include the costs associated with additional services, such as hiring a design team or buying printing materials. Lean on templates to optimize this process. Here is an example of a new customer welcome letter . Although you can easily customize it with personalized messaging, contact info, and unique artwork, having this design template helps boost efficiency and productivity. View all templates here. How to send direct mail How does direct mail work? The answer to this question is, "It depends." You can send direct mail the old fashion way, but why risk errors and inefficiencies? With the old way, direct mail is static, non-personalized, and lacks the insight needed to optimize campaigns. A single campaign would also take months. Being aware of these inefficiencies can help you supercharge your campaigns. With the old way, campaigns took 3+ months from start to finish. Now, this process can be achieved in under a week. This rapid timeline helps ensure greater success. So, it's no surprise that 74% of marketers agree that direct mail delivers the best ROI, response rate, and conversion rates than all other channels used and is more effective than email. Here is a step-by-step process of what a direct mail campaign looks like: Step one: Know your purpose and audience. What do you wish to achieve? Who are you reaching out to, and why? Know these answers before you proceed. Step two: Create a mailing list. Here is a resource on list building 101 . Step three: Decide what type of campaign you're building. Remember, personalization is crucial here. Step four: Design your mail pieces. Don't forget to include a compelling CTA that allows you to track data. Step five: Choose a printing partner. Step six: Mail your pieces out to your list based on the desired timeline. The key is to automate the process to get the most out of every direct mail campaign. For example, with Lob, all mail is hyper-personalized, measurable, and prioritized. What once took three months can now be achieved in less than a week — delivered at scale. Whether you wish to send out a thousand postcards or three million, the process remains the same, and that's powerful. The process is simple: Set up direct mail campaigns in minutes. You can easily schedule ahead or create trigger-based campaigns that respond to specific events or custom behaviors. Select an address, select postage, and the desired timeline. Add your target audience, implementing your campaign into your existing omnichannel strategy. Lob can seamlessly integrate with your existing tech stack so you're able to leverage data from Salesforce, Marketo, Shopify, and more. Customer spotlight: Read about a large telecomms experience with Lob and how the enterprise sends millions of mail pieces with Lob. How to send direct mail There are plenty of ways to approach direct mail campaigns. However, not all approaches are equal concerning efficiencies and ROI. Gone are the days when direct mail campaigns took months to complete. When you partner with an automation platform like Lob, you can create and print mailers in less than a week. That type of timeline ensures the right message reaches the targeted person at the most effective time — and it makes all the difference. When sending direct mail with the support of Lob, you're not just sending physical marketing material. You're sending intelligent mail at scale . How you complete this process is simple. Lob offers modern technology that streamlines mail production and delivery. Whether it's thousands or millions of mail pieces, Lob has a nationwide network of printers to optimize the process. Quickly and affordably personalize each piece with images, QR codes, URLs, promo codes, and more. Printing, postage, delivery, and address verification can all be automated with Lob. Why does personalization matter for direct mail? In today's market, personalization is imperative when aiming to engage consumers. The State of Direct Mail Consumer Insights report cites that 52% of consumers expect direct mail to be personalized to them. Direct mail also increases conversion and response rates, which is why it needs to be a priority across all channels — including direct mail. For example, an RIT study found that adding someone's name to mailing increased response rates by 44%. When the mail was printed in color with the recipient's name, plus other personalized information, response rates increased by 500%. Another 2021 study by McKinsey found that 76% of customers "get frustrated" when companies don't deliver personalized interactions. The same study reported that when businesses get this right, they generate 40% more revenue than competitors who don't invest in personalization. Other eye-opening stats include the following: 91% of consumers are more likely to shop with a brand that creates personalized offers. 80% of consumers are more likely to shop with brands that provide personalized experiences. 79% of consumers will only likely engage with offers that include personalization based on previous interactions. Read more: The Modern Marketer's Guide to Personalization How can direct mail be personalized? Personalizing direct mail campaigns doesn't need to be complicated. For example, with Lob, you can leverage automation to personalize mail pieces using one or more elements, such as phone numbers, personalized URLs, or referrals. With Lob's API technology, you can instantly pull relevant customer data from your e-commerce platform or CRM. This process auto-populates your mailers with ease. Here are examples of how you can personalize mail: Images — The goal of any direct mail campaign is to grab someone's attention. Customers who sort through their mail are much more likely to pick out your flyer or postcard if they relate to the imagery. Kunversion+ is an excellent example of how strategic, personalized images convert. Thank you notes — Personalized gratitude letters or mailers can help customers feel more connected to your brand. Although this may seem complex and time-consuming, a direct mail automation platform like Lob simplifies the process with address verification and thank you note templates. QR codes — Want to lead a recipient to content curated for them? Want to provide a personalized offer? QR codes are an excellent way to boost engagement. Plus, this strategy lets you track each campaign. What difference does direct mail automation make? Those not using direct mail often think the channel is slow and inefficient. However, this is a myth. The old way of sending mail wasn't the best approach based on today's standards. It lacked personalization and tracking. Also, the process wasn't quick enough. That has since changed. What once took months now takes less than a week with Lob — that's the power of automation. Companies no longer need to send mail using manual processes prone to errors. With Lob, the process is as easy as 1, 2, 3: Step one: Create a personalized campaign in minutes. Step two: Press send to ship mail to customers so that it shows up on the day you choose. Step three: Optimize campaigns and track conversions using unique URLs and QR codes. When using Lob, you can cut costs by 85%. Manual workflows can be automated, including printing, postage, campaign creation, sustainability initiatives, and address verification. What are some common use cases for automated direct mail? Customer acquisition — Direct mail can help you build relationships and create loyal customers. Lob integrates with the most popular CRM and marketing automation platforms to create a marketing tech stack to capture prospects' attention. Customer retention — When the goal is to maximize revenue and minimize churn, trigger-based direct mail can help. Customer reactivation — Want to re-engage and reactivate customers? Direct mail can help. Recommended resource: Most common direct mail terms How to get addresses for direct mail The first step for a direct mail campaign to succeed is acquiring a great mailing list. This step is a crucial investment that can make or break direct mail as an effective channel within your omnichannel strategy. Around 60% of responses happen because of the list used. To get addresses for direct mail, many companies rent or purchase information about consumers and businesses. This purchase provides access to a list of addresses. USPS recommends looking in the Yellow Pages under "lists" or "mailing lists." Alternatively, you can search online. However, this isn't the most effective option. After all, you don't just want a list of addresses. You want the addresses of those interested in what you're offering. One way to achieve this is to partner with a direct mail provider. While mailing material seems easy, many marketers are surprised by the complexity of the process. It takes a lot of time and effort to build a targeted list and design material that helps ensure a great ROI. To supercharge your strategy, you'll want to automate as much of your direct mail and customer acquisition strategy as possible. For example, you can leverage the data stored on your CRM to create effective triggers. Additional tips: Be specific in your targeting goals — create or buy a list based on extensive analysis. Grow lists based on existing customer data. Use advanced statistics to improve precision. Recommended resource: Lob Audience How to ensure address accuracy for direct mail Failed shipments because of incorrect addresses are expensive. Lob developed its Address Verification API to help reduce direct mail campaign costs and boost efficiency. This API can correct and identify over 156 million domestic addresses and determine whether they're deliverable. Making this investment is invaluable for a campaign's overall ROI. For example, if only 2% of all users input incorrect data, that would cost over $200 for every 1000 shipments. The redelivery and operation costs are steep. For larger enterprises, these costs can skyrocket into the thousands. It's an unnecessary waste of money, especially since there is a solution available. For enterprise customers, we have solutions that offer over 10,000 address verification requests for only $55 a month, and each additional request costs fractions of a cent at $.006 per request . When using this API, you can ensure complete, machine-readable addresses accepted by USPS. Once received by Lob, the API breaks down the address to return a detailed deliverability analysis. Five possible outcomes exist — deliverable, deliverable extra secondary, missing secondary, undeliverable, and no-match. Discover more: Introduction to Lob's Address Verification API Direct mail strategy How to optimize a direct mail campaign Investing in automation is the best way to optimize a direct mail campaign. Leveraging available data and technology is key to optimizing your campaigns. For many, misunderstanding direct mail's efficiency is the greatest barrier to entry. Traditionally, direct mail isn't the most technology-forward channel. However, when partnering with a solution like Lob, you'll access the integrations, attribution methods, and optimization tactics needed to boost the efficiency of campaigns. One of the simplest places to begin is to focus on your campaign's creative assets. You may need to change your CTAs, imagery, messaging, or promos if you do not see the expected results. Once you alter your design and approach, you can test which options convert best. A/B testing is ideal for this purpose. Is it time to optimize your direct mail campaigns? Read more about the warning signs that indicate it's time to revisit your current strategy. How do I know my direct mail is being delivered? Did you know that around 5% of mail is undeliverable? People make mistakes and typos — it happens. However, it is costly. With 5% of mail being undeliverable, the processing costs to the USPS are about $1.3 billion each year. Then there's the cost to your business. When this occurs and mail is returned, postage costs roughly double. To address this concern, Lob developed its address verification API . This technology corrects addresses in real time to eliminate mistakes and minimize potential waste from undeliverable mail. In addition to this API, Lob offers mail tracking. Tracking is included throughout the mailing process, allowing you to check each step as mail pieces travel to their destinations. With end-to-end analytics, you can see where mail is in the cycle and track conversions. Know that direct mail isn't perfect, so there is no need to stress when some mail comes back. The best lists have delivery rates of 95% (consumer) and 90% (business). How should you follow up on direct mail advertising? Your follow-up strategy will depend on your goals and where the customer is within their journey. For example, you can use direct mail to follow up with customers based on your CRM data. With API-powered direct mail platforms like Lob, customer data is pulled from your CRM so you can re-engage customers via direct mail. You can follow with an upsell mailer if a customer makes a purchase. It can include a related product image with a trackable offer within a set number of days or weeks after their initial purchase. Another example is the connection between email and direct mail. While email marketing is a valuable channel, users often experience email fatigue. Direct mail can help combat this, allowing you to reach customers who are not responsive via email. Unsubscribers can also be targeted with direct mail to help these individuals re-engage with your brand. ThirdLove successfully implemented this strategy. Learn more about how they were able to increase customer lifetime value . How effective is direct mail marketing for B2B? Direct mail is an effective channel whether you operate in a B2C or B2B industry. With B2B marketing, campaigns are typically less focused on converting a single individual and more on winning over an entire buying committee. Direct mail fits in well within an account-based marketing strategy. With Lob, marketing for B2B is simple and effective, especially when leveraging one of Lob's integrations. For example, the Marketo integration can significantly improve direct mail management. Clearbit is another tool you can use alongside Lob to find new leads and create more highly targeted marketing campaigns. What industries does direct mail work best for? Direct mail is used across a broad spectrum of industries because it's highly customizable. Here are some examples of how direct mail supports the unique goals of industry leaders: Insurance — Automated direct mail helps insurance companies streamline compliance and serve customers in a timely, authentic way. Trust is crucial, as fewer than 30% of consumers consider insurers trustworthy. Personalized mail that prioritizes compliance initiatives can help boost conversions. Read more about how CPH uses automated direct mail to create more agile workflows. Financial services — From accounts receivable and accounts payable to tax operations and KYC compliance, automated direct mail is helping those in the financial services industry scale. Lob's financial services customers often see upwards of a 68% measurable return on investment with flexible form factors, hyper-personalization, attribution, and analytics. Dive deeper into address verification for financial services . Healthcare — Automated direct mail is helping those in healthcare improve billing, educate patients, and implement personalized, offline communications. Read more about how VillageCareMAX overcame the challenges associated with HIPAA-compliant communications. Retail and ecommerce — Lob is helping retailers improve offline engagement for online retention. Customize messaging and feature products while reducing shipping errors. Watch this live demo showcasing how retailers leverage offline marketing via automated direct mail. What are some customer stories? Over 12,000 innovative companies use Lob. Helping customers ranging from startups to Fortune 500s, Lob is a platform trusted by tech-forward businesses. Through direct mail automation, they are achieving growth, as told in their many success stories. Marley Spoon drive 20% of reactivation conversions in a single quarter. Read their story. thredUp increased ROI by 128% with its reactivation campaign. Read their story. BlueChip Financial leverages Lob's Address Verification API to cut potential mail costs by 50%. Read their story . NEXT experienced a 4X increase in performance. Read their story. Discover more case studies to see how direct mail helps businesses achieve their goals — and where it fits into your current omnichannel strategy. Conclusion These direct mail FAQs are a comprehensive resource designed to address your most pressing questions about direct mail marketing. By providing answers to common inquiries, we aim to empower you to make informed decisions and achieve optimal results for your direct mail marketing campaigns. From understanding the basics of direct mail to exploring advanced targeting strategies, our FAQs cover a wide range of topics to cater to marketers of all levels. Don't let uncertainties or doubts hinder your direct mail success. Take advantage of the valuable insights and practical tips to unlock the full potential of this powerful marketing channel. By leveraging intelligent direct mail effectively, you can reach your target audience, engage them with personalized and impactful messages, and drive tangible results for your business. Send lightning-fast campaigns that drive results with Lob Send targeted, lightning-fast campaigns at scale. Take our intuitive platform for a spin. For more information about how this data is handled, please view our Privacy Policy Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:37 |
https://open.forem.com/t/learning#main-content | Learning - 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 Learning Follow Hide “I have no special talent. I am only passionately curious.” - Albert Einstein Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu LED strip lighting is a distributed system (and long runs will humble you) emmma emmma emmma Follow Jan 7 LED strip lighting is a distributed system (and long runs will humble you) # hardware # learning # networking Comments Add Comment 2 min read Science behind Mountain Formation Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Jan 4 Science behind Mountain Formation # beginners # learning # science Comments Add Comment 5 min read Por qué estoy aprendiendo espanol? David Scanu David Scanu David Scanu Follow Jan 2 Por qué estoy aprendiendo espanol? # learning # motivation # español 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 Discovery and Development of Electricity: Powering the Modern World Gustavo Woltmann Gustavo Woltmann Gustavo Woltmann Follow Dec 28 '25 The Discovery and Development of Electricity: Powering the Modern World # learning # science Comments Add Comment 5 min read O‘zbekistonda Ekologik Muammolar: Orol Fojiasidan Tortib, Havo Ifloslanishigacha – Va Biz Nima Qila Olamiz? Umidjon Xoshimov Umidjon Xoshimov Umidjon Xoshimov Follow Dec 25 '25 O‘zbekistonda Ekologik Muammolar: Orol Fojiasidan Tortib, Havo Ifloslanishigacha – Va Biz Nima Qila Olamiz? # discuss # learning # science Comments Add Comment 1 min read Abrir Propriedades do Sistema via CMD (Windows) Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Carlos Eduardo De Souza Lemos Follow Dec 22 '25 Abrir Propriedades do Sistema via CMD (Windows) # beginners # learning # productivity Comments Add Comment 2 min read The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence Abdulla A Abdulla A Abdulla A Follow Dec 23 '25 The Art of Mastering Spoken English: A Complete Journey from Silence to Eloquence # beginners # learning # motivation 1 reaction Comments Add Comment 7 min read # Spoken English: The Journey from Silence to Confidence Abdulla A Abdulla A Abdulla A Follow Dec 22 '25 # Spoken English: The Journey from Silence to Confidence # discuss # motivation # learning # mentalhealth Comments Add Comment 7 min read Stem Cell Therapy for Spine: How It Works, Benefits, and Safety Considerations abdallah mohamed abdallah mohamed abdallah mohamed Follow Dec 23 '25 Stem Cell Therapy for Spine: How It Works, Benefits, and Safety Considerations # learning # science Comments Add Comment 4 min read Arc-Fault Protection in PV: Practical Notes for 1000V/1500V Strings wxc5937-beep wxc5937-beep wxc5937-beep Follow Dec 22 '25 Arc-Fault Protection in PV: Practical Notes for 1000V/1500V Strings # design # learning # science Comments Add Comment 1 min read PyMOL 画小分子的静电势 (ESP) Jian Wang Jian Wang Jian Wang Follow Dec 19 '25 PyMOL 画小分子的静电势 (ESP) # learning # science # tools Comments Add Comment 1 min read Technical Overview of Power Quality Audit and Electrical Disturbance Analysis ridhe sharma ridhe sharma ridhe sharma Follow Dec 17 '25 Technical Overview of Power Quality Audit and Electrical Disturbance Analysis # learning # science # tools Comments Add Comment 3 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 How to Transform Communication Skills When Managing the Impact of Dysregulation & APD Grace Anderson Grace Anderson Grace Anderson Follow Dec 18 '25 How to Transform Communication Skills When Managing the Impact of Dysregulation & APD # help # learning # productivity Comments Add Comment 4 min read The Human Condition: A Cycle Of Learning, Unlearning, And Coping Thinking Healer Thinking Healer Thinking Healer Follow Dec 16 '25 The Human Condition: A Cycle Of Learning, Unlearning, And Coping # discuss # learning # motivation Comments Add Comment 4 min read Navigating the Flaws: Systemic Challenges in Alaska's Divorce Process Paula Fox Paula Fox Paula Fox Follow Dec 15 '25 Navigating the Flaws: Systemic Challenges in Alaska's Divorce Process # discuss # learning Comments Add Comment 3 min read How to Search Academic Articles to Invalidate a Patent: A Practical Guide for IP Professionals Zainab Imran Zainab Imran Zainab Imran Follow for PatentScanAI Dec 15 '25 How to Search Academic Articles to Invalidate a Patent: A Practical Guide for IP Professionals # career # learning # productivity 1 reaction Comments Add Comment 8 min read Typing Meets Game Development Hardik Chaudhary Hardik Chaudhary Hardik Chaudhary Follow Jan 6 Typing Meets Game Development # gamedev # learning # showcase 1 reaction 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 Plato’s Republic — Savage Summary (Part 2) SGTSanjay SGTSanjay SGTSanjay Follow Dec 12 '25 Plato’s Republic — Savage Summary (Part 2) # books # motivation # learning # productivity Comments Add Comment 2 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 Why is Displacement a straight line from the starting point to the ending point? Shiva Charan Shiva Charan Shiva Charan Follow Dec 11 '25 Why is Displacement a straight line from the starting point to the ending point? # beginners # learning # science Comments Add Comment 2 min read Quantifying the Intangible: A Strategic Framework for Measuring the Impact of Business Simulations Leadership Leadership Leadership Follow Dec 18 '25 Quantifying the Intangible: A Strategic Framework for Measuring the Impact of Business Simulations # management # learning # productivity # datascience Comments 1 comment 4 min read UTTARAKHAND NATIONAL PARK Abhishek Singh Abhishek Singh Abhishek Singh Follow Dec 18 '25 UTTARAKHAND NATIONAL PARK # learning # science Comments 1 comment 5 min read loading... trending guides/resources Wi-Fi Not Working? How to Reset a Router & Modem Quickly DSL vs. Cable vs. Fiber: What’s the Best Wired Internet? From Random Shots to Living Archive: Why Your Underwater Portfolio Deserves Real Strategy Bandwidth vs Latency: How They Affect Your Online Experience Top causes of workplace burnout and how to address them Abrir Propriedades do Sistema via CMD (Windows) Understanding ASX 200 Futures and Their Role in Market Observation Understanding ASX 200 Futures: An Overview of Australia’s Benchmark Index Derivatives Understanding the FTSE 350 Index and Its Role in the UK Market Weekly Market Summary: Indices Hover Near Record Highs Amid Global Stability Science behind Mountain Formation LED strip lighting is a distributed system (and long runs will humble you) Why you should Include Indian Thali in your Daily meals How Emotion Marketing Creates Loyal Customers Asthma Leveraging CPC and IPC Codes to Improve Searches: Using Classification in Patent Search All Ordinaries: A Comprehensive Insight Into Australia’s Broad Market Benchmark A Beginner’s Guide to Power Yoga for Weight Loss and Strength A Comprehensive Journey from Earth’s Depths to Eternal Symbol Outcome-Based Education and Its Implementation in Tier-1 Institutions — Benefits and Future Scope 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:48:37 |
https://docs.suprsend.com/reference/add-category-translation | Add or Update Category Translation - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation CATEGORIES Add or Update Category Translation Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog CATEGORIES Add or Update Category Translation OpenAI Open in ChatGPT Add or update translation content for a given locale for preference categories and sections. OpenAI Open in ChatGPT POST / v1 / {workspace} / preference_category / translation / content / {locale} Try it Add Translation cURL Copy Ask AI curl -X POST "https://management-api.suprsend.com/v1/{workspace}/preference_category/translation/content/{locale}/" \ --header "Authorization: ServiceToken {token}" \ --header "Content-Type: application/json" \ --data '{ "sections": { "account-updates": { "name": "Actualizaciones de Cuenta", "description": "Notificaciones importantes relacionadas con la cuenta" } }, "categories": { "password-reset": { "name": "Restablecimiento de Contraseña", "description": "Notificaciones cuando se restablece la contraseña" } } }' 200 400 401 404 Copy Ask AI { "sections" : { "new-5" : { "name" : null , "description" : null }, "nik-section-for-transactional" : { "name" : null , "description" : null } }, "categories" : { "nik-sub-category" : { "name" : null , "description" : null }, "amount-refunded" : { "name" : null , "description" : null } } } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace slug (staging, production, etc.) locale string required Locale code (e.g., es, fr, de, ja) Body application/json sections object Translations for sections, keyed by section slug Show child attributes categories object Translations for categories, keyed by category slug Show child attributes Response 200 application/json Successfully added or updated translation sections object Translations for sections, keyed by section slug Show child attributes categories object Translations for categories, keyed by category slug Show child attributes Was this page helpful? Yes No Suggest edits Raise issue Previous Delete Translation Delete translation content for a given locale for preference categories and sections. Next ⌘ I x github linkedin youtube Powered by Add Translation cURL Copy Ask AI curl -X POST "https://management-api.suprsend.com/v1/{workspace}/preference_category/translation/content/{locale}/" \ --header "Authorization: ServiceToken {token}" \ --header "Content-Type: application/json" \ --data '{ "sections": { "account-updates": { "name": "Actualizaciones de Cuenta", "description": "Notificaciones importantes relacionadas con la cuenta" } }, "categories": { "password-reset": { "name": "Restablecimiento de Contraseña", "description": "Notificaciones cuando se restablece la contraseña" } } }' 200 400 401 404 Copy Ask AI { "sections" : { "new-5" : { "name" : null , "description" : null }, "nik-section-for-transactional" : { "name" : null , "description" : null } }, "categories" : { "nik-sub-category" : { "name" : null , "description" : null }, "amount-refunded" : { "name" : null , "description" : null } } } | 2026-01-13T08:48:37 |
https://blog.devcycle.com/tag/guides-tutorials/ | Guides and Tutorials - DevCycle Blog Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Guides and Tutorials Find out how today's most successful companies are implementing feature flags Guides and Tutorials 5 Steps to a Continuous Deployment Culture Deploying software into production so that your users can access it is one of the key areas of software development. Whether you are a two-person start-up using the latest tools and frameworks, a small business integrating multiple SaaS applications, or an enterprise business with 40 years of legacy systems to Mar 28, 2025 11 min read OpenFeature How Jackson Used DevCycle and OpenFeature to Achieve a Zero-Downtime Migration Today's DevCycle Spotlight features Jackson Kasi, a developer who won the OpenFeature Aficionado prize for our first ever DevCycle Feature Flag Challenge on Dev.to where we challenged developers to build a fun or creative project using DevCycle! Jackson won the OpenFeature Aficionado prize for the most innovative Mar 4, 2025 3 min read Guides and Tutorials How to Use Devcycle to Configure Your Pieces-Powered Generative AI App This blog post explains using DevCycle to configure a generative AI app with Pieces , focusing on a Star Wars-themed copilot. It covers managing LLM configurations with feature flags for quick experimentation and highlights the benefits of using LLM abstractions for efficient model integration. Nov 11, 2024 7 min read Guides and Tutorials Creating a Star Trek-Inspired GenAI Copilot Using Pieces and DevCycle In this post, we show you how DevCycle and Pieces for Developers make experimenting with AI as smooth as a warp-speed jump. Nov 11, 2024 Outside Voices Guides and Tutorials Beam Me Up, SQLite: Running Real-Time Performance Experiments with DevCycle This post guides you through setting up an engineering-led experiment to compare the performance of SQLite (local), Turso, and SQLiteCloud using the SQLite Trek app and DevCycle. Sep 13, 2024 8 min read Guides and Tutorials Set Phasers to Experiment: How to Use Feature Flags to Drive SQLite Performance Tests In this blog post, we explore how feature flags are essential for effective experimentation and introduce a practical example of performance testing across different SQLite options to showcase DevCycle's experimentation capabilities. Sep 13, 2024 5 min read OpenFeature Recipe for Change: Unlocking Feature Flag Flexibility in a Hyperapp with OpenFeature and the Multi-Provider Utility Are your feature flags as flexible as they could be? If they are hard-coded static configurations, the answer is likely no. In this guide, we'll explore how OpenFeature can unlock the full potential of feature flags using a fun (although maybe impractical) example—a Recipe Manager app where Aug 6, 2024 9 min read OpenFeature Featured Migrating from In-House Feature Flagging with OpenFeature Discover how the OpenFeature standard and new Multi-Provider utility can help you migrate away from your in-house flagging solution. Jul 2, 2024 4 min read OpenFeature Planting a (Feature) Flag at the Summit: Extending AlpineJS with OpenFeature & DevCycle Learn how to build a simple plugin that adds OpenFeature compliant feature flagging functionality to AlpineJS using the DevCycle Javascript SDK. May 16, 2024 20 min read OpenFeature Serving Up Feature Flags on an Airtable with OpenFeature In this blog post, I'll show you how to build a simple AirTable Provider for OpenFeature so you can upgrade from that quick snack to a more "filling" feature flag system, all while securing your seat at the DevCycle Buffet. May 1, 2024 11 min read OpenFeature How OpenFeature Was the Key to Escaping Feature Flag Vendor Lock-in: A Vue.js Story Discover how we effortlessly transitioned a VueJS project to a new feature flag Provider in just a few lines of code thanks to OpenFeature. Mar 5, 2024 5 min read OpenFeature Powering Up PHP Feature Flags with OpenFeature See just how easy it is to break free from vendor lock-in with OpenFeature in our latest blog post, where we detail the straightforward process of tweaking our PHP example app to embrace the OpenFeature standard. Feb 15, 2024 6 min read Guides and Tutorials What We Learned From Developing DevCycle's Next.js SDK Building DevCycle's Next.js Feature Flagging SDK was a technical adventure filled with unique challenges and valuable learning experiences. As we navigated the intricacies of integrating feature flagging with Next.js's combination of client- and server-rendering, we encountered obstacles that pushed us to learn the inner Jan 25, 2024 7 min read Guides and Tutorials Building an Early Access Site with DevCycle's EdgeDB & Directus Flows When launching a new app, creating an early buzz is crucial. A well-crafted early access program can be the key to this. The challenge? Providing exclusive onboarding content to new users, while also securing their private data and building a foundation for scalability. Enter DevCycle and Directus. Jan 24, 2024 13 min read Outside Voices Build a DevCycle Feature Flag Control Panel in Directus Learn how to build a custom panel extension in Directus that integrates with DevCycle's API. This allows non-technical users to manage feature flags directly from the Directus Insights Dashboard. Originally published on the Directus blog, read more here. Jan 3, 2024 Outside Voices Explained What is a Canary Release? A canary release is a strategy similar to blue-green deployment where you slowly distribute an update to a small subset of users before it goes live to the entire infrastructure. Dec 1, 2023 3 min read Outside Voices CodeTV (Formerly Learn with Jason): Feature Flags in React Apps (VIDEO) If you want to ship quickly and be confident that customers actually want the new features you’re building, feature flags are a must-have in your dev toolbox. In this video tutorial, learn how to launch a new feature behind feature flags using DevCycle (for free!). Follow along on the May 24, 2023 Outside Voices Guides and Tutorials Testing in Production Explained Testing in Production is the kind of testing done by running your tests in a live production environment before you release the software to the end-user. It's an important step not just for developers, but for businesses too. May 1, 2023 3 min read Page 1 of 1 DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:37 |
https://docs.sui.io/guides/developer/getting-started/configure-sui-client | Configure a Sui Client | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Configure a Sui Client On this page Configure a Sui Client The Sui client configuration specifies which network to connect to and which address to send transactions. Prerequisites First, confirm that Sui has been installed successfully: $ sui --version If this command returns sui not found , then Sui is not installed and you must follow the installation instructions . sui client Run the Sui CLI with the command: $ sui client info If a previous Sui installation stored a client.yaml file locally, you will receive the sui client --help output in the console. You can delete the existing ~/.sui/sui_config/client.yaml file if you'd like to start fresh, or you can continue using the existing configuration. The prompt asks if you want to create the client.yaml file, select Y or press enter. You can skip the prompt with sui client -y . No sui config found in `~/.sui/sui_config/client.yaml`, create one [Y/n]? You will see the following output: Generated new keypair ... secret recovery phrase : [recovery phrase words are here] Created "~/.sui/sui_config/client.yaml" Set active environment to testnet caution Store recovery phrases securely and do not share them with anyone, as they provide access to any objects and tokens that an address owns. It will not be visible again once the CLI history disappears. Learn more about Sui addresses, key generation, and recovery phrases. client.yaml Your Sui client is now configured. By default, Sui stores this information in either the ~/.sui/sui_config/client.yaml file (macOS/Linux) or %USERPROFILE%\.sui\sui_config\client.yaml file (Windows). You can store a client.yaml file in a different location, if preferred, and specify its location with the --client.config flag. The client.yaml contains the configuration for connecting to different Sui networks (Testnet, Mainnet, Devnet, and Localnet), as well as your current active environment, which tells the CLI which network to use when you don't explicitly specify one. You can modify your configuration using the sui client subcommands. See the output of sui client --help for more information. Sui stores the key for the Sui address in a separate file, ~/.sui/sui_config/sui.keystore (macOS/Linux) or %USERPROFILE/.sui/sui_config/sui.keystore (Windows). Learn more about Sui addresses in Create a Sui Address . Next steps Learn More About Sui Addresses Now that you have created a Sui address, learn about address management, key pairs, and recovery phrase best practices. Get SUI from Faucet Obtain SUI from a faucet to deploy packages on Testnet. Hello, World! Clone the "Hello, World!" project. Edit this page sui client client.yaml © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:37 |
https://docs.suprsend.com/reference/get-translation-history | Get Translation History - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation TRANSLATIONS Get Translation History Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog TRANSLATIONS Get Translation History OpenAI Open in ChatGPT Retrieve version history information for translations, including all versions and their details. OpenAI Open in ChatGPT GET / v1 / {workspace} / translation / version / {version} Try it Get Translation History cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/translation/version/{version_no}/" \ --header 'Authorization: ServiceToken <token>' 200 401 404 Copy Ask AI { "meta" : { "count" : 2 , "limit" : 10 , "offset" : 0 }, "results" : [ { "filename" : "en.json" , "locale" : "en" , "locale_name" : "English" , "namespace" : null , "action" : "unchanged" , "updated_at" : "2025-10-30T12:23:50.380614Z" }, { "filename" : "fr.json" , "locale" : "fr" , "locale_name" : "French" , "namespace" : null , "action" : "added" , "updated_at" : "2025-10-28T07:59:43.397124Z" } ] } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace slug (staging, production, etc.) version integer required Version number to retrieve Response 200 application/json Successfully retrieved translation version history meta object Show child attributes results object[] Show child attributes Was this page helpful? Yes No Suggest edits Raise issue Previous Rollback Translation Rollback translations to a previous version. This will replace all files with what was available at the previous version. Next ⌘ I x github linkedin youtube Powered by Get Translation History cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/translation/version/{version_no}/" \ --header 'Authorization: ServiceToken <token>' 200 401 404 Copy Ask AI { "meta" : { "count" : 2 , "limit" : 10 , "offset" : 0 }, "results" : [ { "filename" : "en.json" , "locale" : "en" , "locale_name" : "English" , "namespace" : null , "action" : "unchanged" , "updated_at" : "2025-10-30T12:23:50.380614Z" }, { "filename" : "fr.json" , "locale" : "fr" , "locale_name" : "French" , "namespace" : null , "action" : "added" , "updated_at" : "2025-10-28T07:59:43.397124Z" } ] } | 2026-01-13T08:48:37 |
https://docs.suprsend.com/reference/enable-disable-workflow | Enable/Disable Workflow - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation WORKFLOWS Enable/Disable Workflow Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog WORKFLOWS Enable/Disable Workflow OpenAI Open in ChatGPT Enable or disable a workflow. Disabled workflows will not be executed when triggered. By default, workflows are enabled unless you explicitly disable them. OpenAI Open in ChatGPT PATCH / v1 / {workspace} / workflow / {slug} / enable Try it Toggle Workflow cURL Copy Ask AI curl -X PATCH "https://management-api.suprsend.com/v1/{workspace}/workflow/{slug}/enable/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' \ --data '{ "is_enabled": true }' 202 401 404 Copy Ask AI { "$schema" : "https://schema.suprsend.com/workflow/v1/schema.json" , "slug" : "welcome-sequence" , "is_enabled" : true , "created_at" : "2023-11-07T05:31:56Z" , "last_executed_at" : "2023-11-07T05:31:56Z" , "name" : "Welcome Sequence" , "description" : "<string>" , "updated_at" : "2023-11-07T05:31:56Z" , "commit_message" : "<string>" , "hash" : "<string>" , "status" : "active" , "category" : "transactional" , "tags" : [ "<string>" ], "ratelimit" : {}, "conditions" : [ {} ], "trigger_type" : "event" , "trigger_events" : [ "<string>" ], "override_recipients_type" : "user" , "override_recipients_user_expr" : "<string>" , "override_recipients_single_object_fields_expr" : "<string>" , "override_actor_user_expr" : "<string>" , "override_tenant_expr" : "<string>" , "active_at" : "2023-11-07T05:31:56Z" , "updated_by" : { "name" : "<string>" , "email" : " [email protected] " }, "tree" : {}, "validation_result" : { "is_valid" : true , "errors" : [ "<string>" ] } } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace to which the workflow belongs (staging, production, etc.) slug string required Unique identifier of the workflow. You can get it from workflow settings. Body application/json is_enabled boolean required Set to true to enable the workflow, false to disable it. Response 202 application/json Workflow status updated successfully $schema string<uri> Schema URL for workflow validation Example : "https://schema.suprsend.com/workflow/v1/schema.json" slug string Unique identifier for the workflow Required string length: 1 - 255 Example : "welcome-sequence" is_enabled boolean Whether the workflow is enabled Example : true created_at string<date-time> When the workflow was created last_executed_at string<date-time> | null When the workflow was last executed name string Human-readable name of the workflow Example : "Welcome Sequence" description string | null Description explaining the usecase of the workflow updated_at string<date-time> When the workflow was last updated commit_message string | null Last commit message hash string | null Git-like hash for version tracking status enum<string> Current status of the workflow Available options : active , inactive , draft category string Notification category of the workflow. Used to apply category-specific settings and preferences. Example : "transactional" tags string[] Tags for organizing and filtering workflows in API. ratelimit object Workflow throttle settings. This is used to limit the number of times a workflow can be executed per user in a given time period. conditions object[] Trigger Conditions for workflow execution. Workflow will only be executed if trigger conditions evaluate to true. trigger_type enum<string> How the workflow is triggered. You can refer to all trigger types here . Available options : event , dynamic , api trigger_events string[] Events that trigger this workflow. This will be set for trigger_type = event . override_recipients_type enum<string> | null Type of recipient override. Define whether to override and run this workflow for user, list of users or a single object. Available options : user , single_object_fields override_recipients_user_expr string | null Expression for overriding recipients when override_recipients_type = user . override_recipients_single_object_fields_expr string | null Expression for overriding recipients when override_recipients_type = single_object_fields . override_actor_user_expr string | null Expression for overriding actor override_tenant_expr string | null Expression for overriding tenant active_at string<date-time> When the workflow's live version became active. Will be null for draft version. updated_by object User who last updated the workflow Show child attributes tree object Node tree structure of the workflow. Shows the list of all nodes used in the workflow along with their configuration. validation_result object Validation status of the workflow Show child attributes Was this page helpful? Yes No Suggest edits Raise issue Previous Delete Workflow Permanently deletes a workflow by providing it's slug. Next ⌘ I x github linkedin youtube Powered by Toggle Workflow cURL Copy Ask AI curl -X PATCH "https://management-api.suprsend.com/v1/{workspace}/workflow/{slug}/enable/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' \ --data '{ "is_enabled": true }' 202 401 404 Copy Ask AI { "$schema" : "https://schema.suprsend.com/workflow/v1/schema.json" , "slug" : "welcome-sequence" , "is_enabled" : true , "created_at" : "2023-11-07T05:31:56Z" , "last_executed_at" : "2023-11-07T05:31:56Z" , "name" : "Welcome Sequence" , "description" : "<string>" , "updated_at" : "2023-11-07T05:31:56Z" , "commit_message" : "<string>" , "hash" : "<string>" , "status" : "active" , "category" : "transactional" , "tags" : [ "<string>" ], "ratelimit" : {}, "conditions" : [ {} ], "trigger_type" : "event" , "trigger_events" : [ "<string>" ], "override_recipients_type" : "user" , "override_recipients_user_expr" : "<string>" , "override_recipients_single_object_fields_expr" : "<string>" , "override_actor_user_expr" : "<string>" , "override_tenant_expr" : "<string>" , "active_at" : "2023-11-07T05:31:56Z" , "updated_by" : { "name" : "<string>" , "email" : " [email protected] " }, "tree" : {}, "validation_result" : { "is_valid" : true , "errors" : [ "<string>" ] } } | 2026-01-13T08:48:37 |
https://meta.stackoverflow.com/questions/437757/modernizing-curation-a-proposal-for-the-workshop-and-the-archive | Modernizing curation: A proposal for The Workshop and The Archive - Meta Stack Overflow Skip to main content Stack Overflow s-popover#show" data-s-popover-placement="bottom-start" /> Loading… Back to Stack Overflow Return to the main site Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have What's Meta? How Meta is different from the main site About Us Learn more about Stack Overflow the company, and our products current community Stack Overflow help chat Meta Stack Overflow your communities Sign up or log in to customize your list. more stack exchange communities company blog Log in Sign up Home Questions Tags Users Stack Internal Stack Overflow for Teams is now called Stack Internal . Bring the best of human thought and AI automation together at your work. Try for free Learn more Stack Internal Bring the best of human thought and AI automation together at your work. Learn more Stack Internal Knowledge at work Bring the best of human thought and AI automation together at your work. Explore Stack Internal Modernizing curation: A proposal for The Workshop and The Archive Ask Question Asked 27 days ago Modified today Viewed 5k times -31 TL;DR: The opinion experiment revealed that users aren't looking for subjective debates; rather, they most often seek detailed explanations. To capture this value, we propose a radical shift: stop closing questions and introduce a new curation model—The Workshop for collaboration and The Archive for curation. Sit down, grab a drink, and start reading. Years ago, Shog9 wrote that managing a community is like managing water in permaculture . He described laying “contour strips” to catch the rain, managing the torrents that threatened to wash the farm away. Shog9 wrote from the perspective of managing abundance. I grew up in the southwestern deserts of the United States and know what it means to run out of water. I know the feeling of scrambling up the walls of a slot canyon to escape flood waters brought by a coming storm, watching precious resources flash by and strip the land away. It is not lost on me how slight miscalculations of water management can be the difference between a landscape that survives and one that withers away. For a long time, the water of this platform–user engagement, and contributions–was plentiful on Stack Overflow. We built dams to control that flow. This made sense in the past and was the correct call. Stack Overflow, once a plentiful paradise, is now experiencing a drought . Somehow, we find ourselves somewhere in the desert with a dam. Our fields are parched, yet our sluice gates are almost entirely closed. The Data: Opinion Question Experiment (The Rain) After running the opinion-based question experiment for just about two months, we know it's still raining upstream, and we have water sitting in a reservoir just behind the dam. Are closures for “opinion-based” reasons going down and are we seeing more “opinion” questions? In short, yes. Though this should not surprise anyone, given that they can’t be closed and there is no real, defined set of rules. Anyone poking around on SEDE can see that question closures are continuing to decline. Are we seeing ongoing activity on these questions? Yes. Opinion-based questions are getting about three times more replies than regular questions (answers + comments). As of this writing, there are 1600+ opinion-based questions, 78% of which have at least one reply. In terms of engagement, this is a clear signal of demand. Our month-over-month numbers show an increase of 16% in engagement (questions, answers, comments, replies), which is unusual given the typical slowdown in participation we see around this time of year. Some caveats: novelty is a potential contributing factor, but only time will tell us by how much. By our count about 85 replies were about telling the asker that their questions should have been asked as traditional Q&A (which is less than 2% of overall replies). This however isn't an easy thing to track, so there may be a few unaccounted for. Is any of this good? Our specific goal was to increase engagement, and to that end, this is a measurable success. Given the 16% lift in activity we observed, these results suggest this is a viable strategy to stabilize participation and open new avenues for growth. Crucially, that 3x increase in replies came with a lower flag rate for these new question types (2.9% vs 3.26%). This indicates we can expand participation without sacrificing quality. While technical bugs caused some content to leak into the wrong queues or question lists, these are solvable engineering issues, not existential threats. Even more interestingly, this wasn't just new users asking lazy questions. The median reputation for users asking these opinion questions was 10x higher than those asking troubleshooting questions (113 vs 11), and their accounts were significantly older (median age of ~ 7 years vs ~ 2.5 years). This tells us that experienced developers are hungry for these conversations. And the community valued them: nearly 30% of non-deleted opinion questions received at least one upvote, proving that when we allow space for nuance the communities find value in it. We won’t ignore the fact that this is far from a finished product, and that there is work to be done to get there, but if you have found yourself concerned about the drought of participation, this experiment offers a clear signal: the rains have not left us entirely; we just need to adjust how we capture them. Our Learnings: “Opinion” is a misnomer For years, we have treated opinion-based as synonymous with subjective. They both have been defined loosely as content that dilutes the factual purity of the content on the platform. A light analysis of what users are asking in this experiment revealed four distinct intents that staff categorized into four groups: Explanations: Focusing on conceptual understanding, learning, or finding why rather than just how. Implementation: Focusing on achieving an operational result, like getting code to run. Improvement: Improving a working solution. Other: Self-promotion, or any content that didn’t fit the other categories. Ironically, we found that the “Troubleshooting” type we introduced as an option during the experiment was almost entirely categorizable under our new implementation category: users trying to get bugs fixed. The revelation came when we analyzed the question users submitted using the “Opinion-based” option provided during the experiment. These were not just random solicitations for comments or opinions, which was a concern for both the company and the community, but a majority appeared to be questions asking for explanations. Users were asking for help making architectural decisions, understanding why a framework behaves the way it does, and weighing considerations before writing code. In the current curation system, curators close questions as opinion-based because they don’t fit our strict “one right answer” format. In reality, a lot of these are questions of conceptual understanding, based in facts, reasoned through collaboratively, and grounded in truth. By damming these up for years, we have incidentally been blocking meaningful attempts by people trying to gain deeper understandings and have “why” conversations that help them grow. “Opinion-based” often just meant “nuance required.” The historical struggle Despite the reality of declining participation, we seem to have shut the sluice gate even tighter. Our current model of curation has resulted in a state where nearly 40-50% of all incoming questions are ending up closed every month. This high rejection rate isn't a failure of the people doing the curating; it is the inevitable result of a system designed for flood control operating in a time of scarcity. The dam doesn’t help anymore. We are aggressively filtering for a volume that no longer exists. The question of closure has been a topic of conversation for a long time. Let's have another! That linked post is still worth a read; functionally, nothing that was laid out there has changed all that much. Closures are more user-friendly than they were 12 years ago and usually take far fewer votes to do, but essentially every issue raised in that question and most of the linked questions remain today. The vast majority of casual visitors’ and new askers’ questions do not naturally align with our content standards. Various attempts over 16 years to change that reality, from both the company's side and the community's side, have not succeeded. This has cost us. Our curators built a resource that every developer on Earth has relied on at some point in the last 16 years. That was done using a system that worked for an era of abundance, when we could pick and choose only those questions that mattered most. But it is becoming clearer that the system we currently have is considerably out of alignment with the needs of developers today. We have had this structural problem for a while. Renaming "close" to "on hold" didn't fix it. The problem isn't that the dam is rude, it's that it works too well. We don't need a new dam—we need to let more water through. Consider this principle: “If a question is closed and goes unanswered forever, we'll never get a chance to see who it could have helped.” The answer is what gives value to the question – both to the asker and to future visitors. Maybe it turns out an answer is only valuable to the asker, but an unanswered question is valuable to no one. The proposal: The Workshop & The Archive This is a concept; no development is underway. While this introduces new edge cases, we believe it addresses our most pressing problem: our current curation model is designed for an era of abundant questions that no longer exists. The Workshop: The contour strips In Shog9’s answer, he spoke of contour farming : a way to catch water and allow it to be absorbed into the fields rather than running off. The Workshop would be our new contour strips. Just like contour strips are intended to be the place to catch all the water, The Workshop would be intended to catch almost every appropriately on-topic, answerable question on Stack Overflow. Think of this as the public evolution of the Staging Ground. We want to take the tools that worked in that sandbox (nudges, templates, structured feedback) and make them the default experience for everyone. Spam and abuse would still be deleted, but the strict rules against conversation would be lifted here. The Workshop would be the single entry point for all questions and utilize a threaded reply structure with improved notifications rather than the strict Q&A format. This would allow for messier collaboration. Incomplete or unclear questions could be discussed back and forth without penalty. We want to keep the conversation open while the water soaks in. The purpose is to see what value these posts might hold for the future. With proper irrigation in place, we’d want to see organic growth: No GenAI: We want human contributions, not synthetic filler. For the purpose of this feature, the site's GenAI policy will remain in effect. No link-only answers: We want the irrigation to happen on-site. Dropping a bare link doesn't water our fields; it just pipes the water somewhere else. Content should still be able to stand on its own. Beyond that? Minimal friction. If you wanted to help by saying, “Have you tried checking your variable names?”, that would be a valid form of irrigation. We wouldn’t be checking for formatting perfection: in The Workshop, the first and foremost goal would be to help the asker. The Archive: The harvest The Archive would be the “harvest”—the curated knowledge we offer the developer community at large. You are likely thinking, “But how do we curate if we cannot close?” Introducing Expert Endorsements Expert Endorsements (a working title), a unique vote reserved for some community members, would be a validation of the question’s future value from the established curators on Stack Overflow. It would be the opposite of a close flag. Getting one means you have created content that is the cream of the crop; it means your question can be found easily and that it should be surfaced to future searchers and learners, because it's good. Instead of voting to close, you’d vote to elevate. The system wouldn’t be built to hide or remove; it would be optimized to highlight what's worth looking at. Curators would not need to classify and categorize every single incoming question, only pull out the most useful posts and cultivate them for the harvest. Today, a small, dedicated core of you are doing the majority of the work of maintaining the knowledge base. This is meaningful work, but it is not always popular. Few do it, and those who do earn criticism in the wider developer community for just trying to preserve and improve the knowledge for others to use. Further, this system is structurally predisposed to cause burnout. Despite sincere intentions, the current tools channel you toward burying questions rather than improving them, and ask you to apply those tools to each one of the tens of millions of questions on the platform. We want to build tools that allow you to truly curate— selecting the best content for presentation, distribution, and refinement. We would need new tools, like proper mapping and support for duplicate content, but for now we only want to get the high-level idea out there. We want to move past the era of “curation as cleanup duty.” Instead, we would like to position the most committed members of our communities as what they are: a cast of unique individuals who should be celebrated for their commitment and expertise. These are people who leverage their extensive knowledge to make the best knowledge on the Web shine. Our request This idea comes from rank-and-file staff after confronting the results of the opinion experiment and the reality of our platform activity data. It is not anywhere near a finalized roadmap, since we wanted to get it on Meta as soon as possible for discussion, but we are actively exploring these notions of "irrigation" and "harvesting." However, to make The Workshop work, we might need to make some changes to how the core Q&A pages work for that space. We would probably want to move towards a threaded discussion format to support The Workshop. This presents a critical challenge: how do we visually protect The Archive when content is promoted from The Workshop? If a discussion page in The Workshop looks like a standard forum thread, we risk losing the prestige and discoverability of the best answer. We cannot let the harvest be buried by the chaff. We need you to help us design the harvesting process: The mechanics: How does a discussion in The Workshop become an artifact in The Archive? Is this a physical migration (moving the Question and its best Answer to a new page) or a visual transformation (signaling high quality within the existing thread)? What are the mechanics of promoting a conversational chain in The Workshop into a standalone, Endorsed Artifact in The Archive? For example, if a “messy” Workshop question receives a brilliant answer, does the question need to be pruned before it enters The Archive, or can the answer stand on its own? The curator: Who should have the power to ‘Endorse’ a question or answer? Should it be reserved for Gold Badge holders, elected moderators, or a new tier of subject matter experts? Visual distinction: On a discussion page in The Workshop, when a curator gives an Expert Endorsement, how should it look? If the rest of the page utilizes a threaded discussion format, does the Endorsed Answer get "pinned" to the top? Does it get a gold frame? Should the classic answer styling be reserved exclusively for Endorsed Content to signal its status as an artifact on The Archive? And crucially, how do we allow users to toggle between the “messy” collaborative view and the clean “curated” view? To summarize: we’re re-imagining Stack Overflow as a platform where curators can focus on elevating high quality content in order to maximize our yield of worthy content, rather than needing to be focused on burying the poor content because we’re holding on to a system that is designed to prevent high volumes of participation which are no longer our reality. We want to hear your feedback on this vision, either in the form of answers to this post, or via email if you don’t feel particularly inclined to share your opinions publicly. For email, send your feedback to: [email protected] with the subject header including: Attention: Hoid If you don’t think that change is possible or that question closures don’t need a serious rework, that is feedback we want to hear: please articulate why the status quo remains viable in light of the current state of the platform’s ecosystem, if you hold that view. If, like us, you agree that systemic change is needed to meet the current reality of declining participation, your feedback on the above questions is particularly important to ensure we uphold the principles that ensure Stack Overflow remains a source of reliable, high-quality content, for generations to come. We want to acknowledge that we’re posting this right before the holidays, and like many of you, we will also be taking time off. Rest assured, no immediate work on this concept is planned, and we are at a highly conceptual point in the process. We also take an end-of-year hiatus, and won’t be checking back in until the first week of January at the earliest. Pace yourself accordingly, as there will be multiple opportunities to hammer out various details as we address what has been brought up before we make any decisions. Happy holidays! discussion company-update featured questions opinion-based Share Follow edited Jan 5 at 19:26 Timur Shtatland 12.8k 23 23 silver badges 31 31 bronze badges asked Dec 16, 2025 at 17:33 Hoid Staff Mod 101 6 6 gold badges 28 28 silver badges 48 48 bronze badges 22 54 It's not exactly surprising to see a 16% increase in engagement, when ordinarily this stuff would have been closed within an hour. Why are we assuming this is because of the interface you decided to use? user400654 – user400654 2025-12-16 18:01:45 +00:00 Commented Dec 16, 2025 at 18:01 46 How much of that 16% increase in engagement was useful content that should be in the Q&A repository instead of noise that makes it more difficult for a future reader to get the answer they need? devlin carnate – devlin carnate 2025-12-16 21:53:32 +00:00 Commented Dec 16, 2025 at 21:53 19 Gotta say that the post referencing Shog9 feels... good. Thank you. It also feels like this is the right path. Can't back it up with anything tangible, but this is not old cranky overworked Stack Overflow and it's not unhinged Reddit. The sweet spot is in the middle and this looks like it is going there. I can also speak from a personal perspective; I felt more liberated getting the "new" style of questions, there was far less stopping me from replying which just made the whole experience more enjoyable. There is little to no voting going on on such questions though, from what I could see. Gimby – Gimby 2025-12-17 09:13:08 +00:00 Commented Dec 17, 2025 at 9:13 15 I'm happy this post has an actual Vision that's different from "throw AI at everything". The bar is set low, but you jumped it Mo_ – Mo_ 2025-12-17 09:28:23 +00:00 Commented Dec 17, 2025 at 9:28 10 "Crucially, that 3x increase in replies came with a lower flag rate for these new question types (2.9% vs 3.26%)" Given that it's essentially a "chat" format, an increase in replies feels a little unavoidable regardless of quality. And similarly, when there are less restrictions on posts, less flags also seems natural. I'm sceptical these actually relate to quality, rather than just: We let people post more stuff, and they did. DBS – DBS 2025-12-17 09:31:04 +00:00 Commented Dec 17, 2025 at 9:31 42 " This tells us that experienced developers are hungry for these conversations ". Not necessarily. I've seen several very high rep users post opinion questions simply because the UI option is completely unclear about what the options mean. You need to account for that before making such a conclusion. cigien – cigien 2025-12-17 12:42:10 +00:00 Commented Dec 17, 2025 at 12:42 13 " To capture this value, we propose a radical shift: stop closing questions and introduce a new curation model " OK, you're officially saying goodbye and good riddance to the Stack Overflow that the world know as a high-quality Q&A repository, then. Please don't use such language or self-descriptions moving forward anymore if you implement this. You will have just created a slightly more restrictive /r/programming, instead. TylerH – TylerH 2025-12-17 19:29:31 +00:00 Commented Dec 17, 2025 at 19:29 23 " Yes. Opinion-based questions are getting about three times more replies than regular questions (answers + comments). " Obviously, because you don't let us close them or hide them by downvoting. Of course when you force feed bread down ducks' throats, they get fat. TylerH – TylerH 2025-12-17 19:32:03 +00:00 Commented Dec 17, 2025 at 19:32 29 All this boils down to, once you get past the cutesy story, is "we have another radical idea that we want to implement instead of doing the work of fixing all the past ideas we've implemented". Stop trying to implement new things and fix/improve the things you already have. Staging Ground. Threaded Comments. The Ask Wizard. Tag hierarchies. Answer versioning. Migrating rep-based privileges to being usage-based. Proper useful migration beyond 5 sites. There's so much good you could do here before you even get close to "let's throw away the Q&A model that literally built this company". TylerH – TylerH 2025-12-17 19:56:10 +00:00 Commented Dec 17, 2025 at 19:56 17 I just skimmed and probably have quibbles with some of it, but I really like the idea of promoting quality content into a library instead of trying to filter out content. I feel strongly content should be moved to another location where only trusted curators get to work on it. This helps make it more coherent and discoverable, and could allow content that is more current to be merged into old possibly outdated content organically. ColleenV – ColleenV 2025-12-17 20:44:20 +00:00 Commented Dec 17, 2025 at 20:44 5 I think the vision is basically Reddit with some sort of Wikipedia fused to it. Would be a radical change with high blow-up potential but still maybe a worthwhile goal. It might also strongly depend on the exact implementation. And on the availability of free curation. Not sure if that is a given. NoDataDumpNoContribution – NoDataDumpNoContribution 2025-12-17 22:30:49 +00:00 Commented Dec 17, 2025 at 22:30 6 "The vast majority of casual visitors’ and new askers’ questions do not naturally align with our content standards." This is maybe the most important statement, describing the root of the problem. We had the StackOverflow Academy that unfortunately never started, we had the unfriendly comments robot, the new contributor badge, the question wizard, the staging ground. Nothing worked. We might as well give up and write the knowledge library ourselves. This kind of seems to be the gist (at least how I understand it). NoDataDumpNoContribution – NoDataDumpNoContribution 2025-12-18 07:34:37 +00:00 Commented Dec 18, 2025 at 7:34 27 More clicks on the shiny thing means the shiny thing is shiny! Throwing out data points without context has become the default self-validation of the dev team. If you give people an unregulated forum they will fill it, this doesn't mean it's useful only that you are getting the requisite ad-clicks your overlords demand of you. It seems fairly likely that the lower flag rate is because all the users that believe in active curation have blocked this experiment as yet another misguided click-bait project. pilchard – pilchard 2025-12-18 14:15:14 +00:00 Commented Dec 18, 2025 at 14:15 17 "in The Workshop, the first and foremost goal would be to help the asker." no thanks, I'm not in it to help an individual, if this becomes reality, I'm out. I'm also not in it to dig through the Workshop mud for diamonds. I'm here because there's a general consensus that all content should be polished, especially the questions. Not to let them rot away in an archive. cafce25 – cafce25 2025-12-19 12:52:01 +00:00 Commented Dec 19, 2025 at 12:52 5 @SergeBallesta I think youre being too pessimistic. This proposal is at a very early conceptual stage, and I believe that Hoid is genuinely asking us for feedback & suggestions. Also, "This idea comes from rank-and-file staff", it's not coming from the upper management levels. Incidentally, Hoid has engaged in discussions about this in the Meta chat. He's not claiming to have a perfect solution, but he does feel strongly that something has to change. PM 2Ring – PM 2Ring 2025-12-28 23:29:33 +00:00 Commented Dec 28, 2025 at 23:29 | Show 7 more comments 24 Answers 24 Sorted by: Reset to default Highest score (default) Date modified (newest first) Date created (oldest first) 64 I commend you for the efforts to bring more questions to Stack Overflow, but let me highlight some problems. Promoting questions to The Archive We don't know which questions are worth preserving; we only know which ones are not worth preserving anymore. All questions that can be answered should be publicly visible so that they get a chance at becoming valuable. Only after some time can we judge whether the question turned out to be a useful contribution or misleading. We can cast downvotes and upvotes from the time it is posted, but even heavily downvoted questions can result in helpful answers. And it is answers that we are optimising for , not questions. If a terrible question received good answers, we can rewrite the question ourselves to match the answers. But a good question will only become useful once it receives a good answer. It may take years before a good answer appears. Or maybe it has taken curators years to observe that a bad question attracted good answers and needs to be improved. Either way, it's only after the question has been publicly exposed for a long time that we can truly assess its usefulness . Threaded replies are a necessary evil Stack Overflow isn't the only place where I find answers after searching on Google. From time to time, I get results on discussion forums and I hate those. Why? Because they are designed for solving the immediate problem of the asker, not for presenting quick solutions for future researchers. Threaded replies are good at getting to the solution, but they are an absolute time-waster when it comes to reading them. And selecting the best/accepted/working/preferred solution isn't making it a lot better. Because the solution took multiple messages to get to, it isn't contained in a single post, but rather the whole conversation thread is relevant. The reader must go through all the posts to fully understand how they arrived at the solution that worked and why. Stack Overflow excels because it is designed such that the answers are written in a self-contained way and aimed at everyone with the same problem. You only need to read one post to understand what the proposed solution is. The next post contains another alternative self-contained solution. Posts are ordered by how useful everyone thinks they are, not by time or by what the asker thinks. It's quick and easy to find solutions. We don't allow working on solutions in the Staging Ground because we don't want to lose valuable answers. If curators answered questions in the Staging Ground, a possibly good solution could get buried in a threaded response without getting posted as an actual answer. And what you are proposing is exactly that! Threaded replies only work for temporary comments when trying to clarify the question and should be deleted once it is ready to receive answers. Share Follow answered Dec 16, 2025 at 19:32 Dharman Mod 34k 17 17 gold badges 195 195 silver badges 312 312 bronze badges 5 32 I think your second point is excellent and very important. Forum/ reply-style pages are optimized for the asker, for engaging with people. Q&A pages are designed for the reader , for consuming information as efficiently as possible. SO was designed to sacrifice the former to elevate the latter; personally, I'm sure that fusions of the formats can be successful, but it's absolutely critical that we don't compromise the reader experience, because that's most people who come to SO. SO was built to optimize for pearls, as the adage goes... if we start burying them, then there's little left. zcoop98 – zcoop98 2025-12-16 20:55:11 +00:00 Commented Dec 16, 2025 at 20:55 5 Possibly threaded replies could also work as a path to a solution if someone were incentivized when it was all said and done to summarize into a suitable-for-reader conclusion. Bryan Krause – Bryan Krause 2025-12-17 19:33:15 +00:00 Commented Dec 17, 2025 at 19:33 As someone who's had long comments wiped by a moderator before said summarization could be done, I suggest that in such cases the "deleted" thread should remain visible to the post author rather than being completely deleted, so that it would "provide incentive" by hiding the comments from public view while also not requiring rewriting from scratch. grawity – grawity 2026-01-02 10:04:50 +00:00 Commented Jan 2 at 10:04 4 I agree with most of this answer, but, "Posts are ordered ... not by time" is idealistic fantasy. Most of the time a best but late answer never gets the visibility it needs to overcome worse but timely answers. It can happen if the question generates a lot of late traffic. Like when I, oh so slowly, took down the great John Skeet . More typically being right but late means being last. Like when I couldn't take down Cort Ammon even with his help . This dirty little secret keeps the creme down. Can we fix that? candied_orange – candied_orange 2026-01-04 06:56:32 +00:00 Commented Jan 4 at 6:56 @candied_orange that is very hard to fix, since voting activity is way down. There already is 'sort answers by trending' in place that tries to combat the problem by making newer votes more valuable for sorting. It's enabled on SO, but not physics.se, apparently. julaine – julaine 2026-01-13 08:17:28 +00:00 Commented 31 mins ago Add a comment | 61 The premise of this question strikes me as incoherent in several ways. Before I outline my claims, I'll offer my counter-theory: engagement is a stupid goal. The goal should be that people should find what they want (and click on an ad or two in the process). If their question is already answered , there's no need for them to engage. Technology doesn't change that fast. The site has successfully built a body of knowledge that answers a vast number of questions, with no further engagement. On to my specific arguments. The question claims that the questions we are closing frequently contain the nuclei of good questions. I very much doubt this. Take away the duplicates, the homework, and the completely off-topic questions, and you have already 'dammed the flow to a trickle.' The question presumes that the experiment has successfully diverted questions that would otherwise be closed, and thus the correlation of reduced closing is in fact causation. Reading the front page, I still see a torrent (to stick to the damp metaphors) of close-worthy sewage from people who are not getting the message. Heck, I continue to see first-time questions that need to be in staging ground just showing up. If closes are down, perhaps it's because more closers have gotten fed up and departed. Finally: this proposal seems to me to essentially describe what I see happening in staging ground, where a discussion attempts to lead the questioner to state a coherent question, or solves their problem in the comments. Why not invest in that instead of launching on a hyper-complex alternative? Postscript: To make my views clear: If you-all want to try to make some money by adding a conversational help structure in parallel with Q&A, I'm 100% neutral. As I see it, 99% of the challenge is going to be building the experience -- and the hardest 99% of the 99% is going to be building the expert community to provide the value and moderate the process. The existing process and community does not transfer / translate. The comments on this question are one barometer into the mood of the existing community, and it isn't encouraging. Share Follow edited Dec 17, 2025 at 21:09 answered Dec 16, 2025 at 23:00 bmargulies 101k 7 7 gold badges 45 45 silver badges 67 67 bronze badges 4 19 This! If their question is already answered, there's no need for them to engage . Only replace "engage" with "ask again", because we want them to engage: by voting. Mo_ – Mo_ 2025-12-17 13:16:32 +00:00 Commented Dec 17, 2025 at 13:16 4 They will never have enough rep to vote (I hope) if all they ever do is find useful content. bmargulies – bmargulies 2025-12-17 19:56:31 +00:00 Commented Dec 17, 2025 at 19:56 4 Engagement is a stupid goal if you want the site to be useful , yes. But it's the only thing they seem to know how to monetize . (Much like every other Internet business nowadays.) Karl Knechtel – Karl Knechtel 2025-12-17 20:41:38 +00:00 Commented Dec 17, 2025 at 20:41 18 I don't follow. Money comes from clicks on ads. If a person comes in 20 times to look at 20 answers, and sees 10 ads every time, there's the money with no detectable 'engagement'. Engagement is a ignorant-CFO surrogate for actual revenue. bmargulies – bmargulies 2025-12-17 20:56:32 +00:00 Commented Dec 17, 2025 at 20:56 Add a comment | 50 The opinion experiment revealed that users aren't looking for subjective debates; rather, they most often seek detailed explanations. The community told you this before you went through with the experiment, with a feature set, that made it impossible to submit our opinion or moderate the questions that were asked. You ignored our feedback. To capture this value, we propose a radical shift: stop closing questions and introduce a new curation model—The Workshop for collaboration and The Archive for curation. Sit down, grab a drink, and start reading. You are going to ignore our feedback. I am positive my feedback will be ignored, but this sounds like a horrible idea. After running the opinion-based question experiment for just about two months, we know it's still raining upstream, and we have water sitting in a reservoir just behind the dam. The experiment failed because you implemented a half-baked feature, without listening to the feedback you received, and essentially tried to relaunch the entire Stack Exchange Q&A model overnight. We told you not being able to issue downvotes was a bad idea. We indicated being unable to close the questions was a bad idea. We told you the entire concept of asking a question, seeking strangers' opinions on a matter, was a bad idea. You ignored all the feedback. In short, yes. Though this should not surprise anyone, given that they can’t be closed and there is no real, defined set of rules. Anyone poking around on SEDE can see that question closures are continuing to decline. You allowed users to ask questions that cannot be moderated by the community or the elected community moderators, proceeded to not moderate the content yourself, and then point out question closures decreased? Of course they decreased – you created a situation that would only result in the results you were expecting. As of this writing, there are 1600+ opinion-based questions, 78% of which have at least one reply. In terms of engagement, this is a clear signal of demand. By our count about 85 replies were about telling the asker that their questions should have been asked as traditional Q&A (which is less than 2% of overall replies). This however isn't an easy thing to track, so there may be a few unaccounted for. So is there an actual demand or did users not understand what they were doing, ended up asking a question seeking an opinion, when they actually wanted to ask a question seeking an actual solution? In my personal experience, every question I looked at, was improperly submitted seeking my opinion. By damming these up for years, we have incidentally been blocking meaningful attempts by people trying to gain deeper understandings and have “why” conversations that help them grow. “Opinion-based” often just meant “nuance required.” It isn't hard to ask a question seeking a deeper understanding of a topic, I have done it countless times, and I have answered hundreds upon thousands of those types of questions. It just takes effort on the individual asking the question. Expert Endorsements (a working title), a unique vote reserved for some community members, would be a validation of the question’s future value from the established curators on Stack Overflow. It would be the opposite of a close flag. Getting one means you have created content that is the cream of the crop; it means your question can be found easily and that it should be surfaced to future searchers and learners, because it's good. Quora has something similar, I don't use Quora, because the users with "expert endorsements" charge for their endorsements (i.e answers). I want no part in a community where this could become a reality. The predicted outcome of "free votes" being issued was seen, users voting for each other, and getting them suspended but the behavior is difficult to track so lots of users are getting away with that behavior. We would probably want to move towards a threaded discussion format to support The Workshop. So you want to turn Stack Exchange communities into Reddit subreddits? I have been a member of forums in the past, they never last; the only community I have ever seen last more than 5 years, is Stack Overflow and that's because it's NOT a place for discussions. If threaded discussions become a reality. I won't be part of the community. I will delete my profile. I have purposefully been extremely harsh in my answer. I wasn't as harsh in my past feedback to the other failed horrible experiments, and those experiments still went live, with the predicated outcomes the community shared. So I have no doubt this new experiment will be implemented despite the community hating it. Share Follow edited Dec 17, 2025 at 15:47 simon 6,909 9 9 silver badges 2 2 bronze badges answered Dec 16, 2025 at 23:58 Security Hound 2,498 2 2 gold badges 19 19 silver badges 18 18 bronze badges 6 3 "user-friendliness" is different than general "unfriendliness". the first is about the experience the system gives the user. the second, in the context of the discussion you are talking about, is usually about framing a curator's intentions towards an asker as ill. starball – starball Mod 2025-12-17 00:01:46 +00:00 Commented Dec 17, 2025 at 0:01 8 @starball user-friendly, welcoming, valuable, useful, engagement, participation, collaboration, experiment, success, activity, demand, growth, learning, improvement, revelation, explanation, deeper understanding, reality, alignment, without penalty, endorsements, popular, ecosystem just obscure Prosus N.V.'s true intention, which can really only be artificially inflating the platform's financial worth in an upcoming sell-off, preferably before the AI bubble bursts. Last addition to the privacy policy even shows that's anticipated. user4157124 – user4157124 2025-12-17 02:41:01 +00:00 Commented Dec 17, 2025 at 2:41 4 @user4157124 " which can really only be " that sounds like speculation. starball – starball Mod 2025-12-17 09:32:26 +00:00 Commented Dec 17, 2025 at 9:32 2 I get that you mention it at the end, but I wish you weren't as harsh here. The post said "This idea comes from rank-and-file staff after confronting the results of the opinion experiment and the reality of our platform activity data" - I don't find statements like "You are going to ignore our feedback. I am positive my feedback will be ignored, but this sounds like a horrible idea." to be constructive. All the CMs surely know already that many Meta folks feel ignored. How does the harsh tone accomplish a more desirable outcome? cocomac – cocomac 2025-12-18 18:16:54 +00:00 Commented Dec 18, 2025 at 18:16 2 @cocomac what would be a better way to express that sentiment that would be constructive? user400654 – user400654 2025-12-18 18:37:55 +00:00 Commented Dec 18, 2025 at 18:37 3 @cocomac - I was less harsh with my last feedback, and all I got was a pat on the back, which doesn’t solve any problems I face while participating in the community. Decided it certainly couldn’t hurt to be less harsh? If you disagree with what I said, you can certainly, just issue a downvote. Security Hound – Security Hound 2025-12-18 19:31:36 +00:00 Commented Dec 18, 2025 at 19:31 Add a comment | 41 Getting rid of traditional Q&A is going to alienate most of the community, and this new system takes much more buy-in from the very users you're alienating. Everyone currently responsible for the curation of this site, from moderators to reviewers to regular users, has been doing so under the traditional Q&A format for decades now. Users ask questions, others answer them, and everyone else on the site contributes by voting, flagging, and editing. Replacing the Q&A format that StackOverflow was built on with messier discussions that will need way more time and effort to curate, moderate, and then eventually elevate will drive away the curators that have been running your site all these years. It's already clear that the company doesn't care what we think when running these side experiments but please, please stop trying to ruin the traditional Q&A format. If you kill it the site dies. Full stop. Share Follow answered Dec 16, 2025 at 18:39 Marsroverr 881 16 16 silver badges 27 27 bronze badges 8 5 with the exception of the proposal that Q&A must first go through the Workspace, I don't see how what's proposed changes "traditional" Q&A or replaces it (much less "ruins"). if things could get added to the "Archive" (I don't like the term- I'd have chosen "library" or "knowledgebase") without first going through the "Worskpace" (which I suggest enabling), then as I understand it, the "Archive" would just be the current placeholder name for what exists today as "traditional" Q&A. starball – starball Mod 2025-12-16 23:57:50 +00:00 Commented Dec 16, 2025 at 23:57 3 @starball Agreed about "Archive", sounds like some dingy space of dust and cobwebs that PhD students need to crawl through to mine for thesis content rather than Empowering Technologists and Their AI Sycophants For the Future To Infinity And Beyond or whatever it is we're supposed to be after these days. Bryan Krause – Bryan Krause 2025-12-17 19:34:52 +00:00 Commented Dec 17, 2025 at 19:34 1 coming back to my previous comment, somehow I missed the glaring point in the TL;DR that proposes removal of closure as a mechanism... in my defense, other than the TL;DR, I read the whole post and didn't pick up that point clearly, so I don't think it's totally on me. starball – starball Mod 2025-12-17 22:45:01 +00:00 Commented Dec 17, 2025 at 22:45 1 @starball - So it’s even worse then I thought it was, wonderful! Security Hound – Security Hound 2025-12-17 23:22:01 +00:00 Commented Dec 17, 2025 at 23:22 @SecurityHound well, it is very much a proposal, and intended to solicit discussion about the proposal or even problem statement / constructive critique / other ideas about addressing the problem statement or reframes of the problem statement . starball – starball Mod 2025-12-17 23:26:28 +00:00 Commented Dec 17, 2025 at 23:26 10 @starball - The last discussion with regards to every recent experiment has been basically ignored, and every prediction made by the community, came true to some extent Security Hound – Security Hound 2025-12-17 23:46:42 +00:00 Commented Dec 17, 2025 at 23:46 "Community" on stack overflow, means probably no more than 100 to 200 people, so "Getting rid of traditional Q&A is going to alienate most of the community" it's not a big deal, tbh jei – jei 2026-01-12 10:21:44 +00:00 Commented 22 hours ago @jei These 100-200 people are the ones voting, flagging, editing, and moderating. Without their participation over the past decade and a half the site simply would not exist Marsroverr – Marsroverr 2026-01-12 18:52:37 +00:00 Commented 13 hours ago Add a comment | 41 I thought about this some more, and I came to the conclusion that this would be a huge nail in the coffin for Stack Overflow. The whole proposal actually sounds very offensive to the community that built Stack Overflow. You are basing the proposal on faulty premises. The experiment showed that there is more "water" because it was designed to brainwash us into thinking this. You tricked users into using the new feature even for questions that weren't opinion-based (which, to me, felt like it was most of them), you didn't provide required moderation tools, and you didn't allow the questions to be downvoted or closed. The whole experiment was designed to get you the results you wanted. You treat question closure as something negative, which means the end of the question. And even if it is, it isn't meant to be that way. Closed questions are waiting for an edit from the asker! We want them to be reopened. If not enough questions get reopened, then do something to address this problem! The fact that 50% of the newly posted questions get closed isn't our fault (at least I hope not). It's your fault! You're not trying to help new users succeed on the site. You're not providing them help in asking questions, in understanding the site, and in searching for existing duplicates. You made some good improvements, such as the staging ground, but you refuse to utilise it more. You tried to improve the asking wizard, but you ignored our feedback. No wonder so many new questions are unsuitable. Stack Overflow is dying because you are killing it! Here are some ideas you could try instead: Push more questions into Staging Ground. Make it more discoverable, too. Maybe show an indication when questions in followed tags are pending in SG. Implement some helpful QOL improvements to the question asking process. I don't mind if you use LLMs to scan the question and identify potential issues with it before it gets posted. You can tell the user when they need to remove noise, fix grammar, write a better title, etc. Reduce the question ban time. We don't need to be so harsh anymore. We can reduce it to a week or a month ban. Questions from such users should definitely land in Staging Ground. Make reopening more frictionless. Perhaps notify close voters when the question they closed gets reopen votes. Highlight questions with reopen votes in the question list. Bump the question when it receives a reopen vote. For moderators, implement tools that would enable us to investigate closures en masse. We have no easy way to find which questions were closed for which reason. It's really difficult to investigate invalid close votes. Share Follow answered Dec 17, 2025 at 16:30 Dharman Mod 34k 17 17 gold badges 195 195 silver badges 312 312 bronze badges 16 7 Staging Ground questions definitely need to be shown all the time for all users in the question list, and possibly even by the time question is edited and not posted until it exist Staging Ground. That would bring more eyes to such questions and give more helpful suggestions from the actual experts in the subject topic. And all questions from new users and those who are question banned need to land into Staging Ground. I am not worried about lack of reviewers because if people want to answer questions they would have to do reviews. Dalija Prasnikar – Dalija Prasnikar Mod 2025-12-17 20:11:06 +00:00 Commented Dec 17, 2025 at 20:11 11 I'm wondering why all new questions by new/inexperienced users don't go through SG. SG already exists and is effectively "the workshop"... no need to re-invent the wheel, we already got one! Drew Reese – Drew Reese 2025-12-17 23:06:57 +00:00 Commented Dec 17, 2025 at 23:06 I am fine with switching the question rate limit to new questions going to SG, but the moderation tool within SG needs to improve, it should possible to | 2026-01-13T08:48:37 |
https://blog.jetbrains.com/dotnet/tag/gamedev/ | Game dev : The .NET Tools Blog | The JetBrains Blog Skip to content Topics Search Language English Deutsch Español Français 日本語 한국어 Русский 简体中文 Português do Brasil Türkçe Čeština Burger menu icon IDEs CLion DataGrip DataSpell Fleet GoLand IntelliJ IDEA PhpStorm PyCharm RustRover Rider RubyMine WebStorm Plugins & Services Big Data Tools Code With Me JetBrains Platform Scala Toolbox App Writerside JetBrains AI Grazie Junie JetBrains for Data Kineto Team Tools Datalore Space TeamCity Upsource YouTrack Hub Qodana CodeCanvas Matter .NET & Visual Studio .NET Tools ReSharper C++ Languages & Frameworks Kotlin Ktor MPS Amper Education & Research JetBrains Academy Research Company Company Blog Security .NET Tools Essential productivity kit for .NET and game developers Follow Follow: Guide Guide RSS RSS Get Tools All How-To's Releases Livestreams Events dotInsights Rider ReSharper Game dev Game dev Rider 2025.3: Day-One Support for .NET 10 and C# 14, a New Default UI, and Faster Startup Rider 2025.3 arrives alongside the .NET 10 SDK, continuing our commitment to day-one support for the latest .NET and C# features. This release brings full compatibility with .NET 10 and comprehensive support for C# 14, including extension members, extension operators, and user-defined compound as… Sasha Ivanova JetBrains is a Platinum Sponsor of the Godot Foundation At JetBrains, we believe deeply in the value of diverse developer tools and open-source ecosystems, and so we’re thrilled to announce that we’ve just become a Platinum Sponsor of the Godot Foundation! Matt Ellis Support for Game Consoles in JetBrains Rider Big news for console game developers! As part of the 2024.3 release, JetBrains Rider added support for PlayStation®5 and Xbox consoles, allowing you to build, deploy and debug your custom or Unreal Engine-based games directly on your preferred game consoles. https://www.youtube.com/watch?v=pNT1o… Matt Ellis Faster Debugging for Massive C++ Projects in Rider If you work on large Unreal Engine projects in Rider, you've likely experienced the dreaded debug-step delay – hit F10 for Step Over, contemplate making coffee, then finally see the next line execute. These delays occur in LLDB Debugger, the engine behind Rider's debugging capabilities for … Sasha Korepanov Rider 2024.3: Same-Day Support for .NET 9 SDK and C# 13, Console Debugging for Game Dev, AI Enhancements, and More We’re thrilled to announce that Rider 2024.3 is here. This release marks a major change to our team’s development process. Starting with version 2024.3, we’re aiming to align updates to JetBrains Rider and ReSharper with major .NET SDK releases. While this isn’t a guaranteed timeline for every relea… Sasha Ivanova Hot-Reloading C++ with Live++ and JetBrains Rider We've been working with Stefan Reinalter and the team at Molecular Matters to make the industry-leading Live++ binary patching tool work seamlessly with C++ projects in JetBrains Rider! This is a great productivity boost for both Unreal Engine developers and those working on custom C++ engines. L… Matt Ellis JetBrains GameDev Days 2024 – [Recordings Available] JetBrains GameDev Days 2024, our hybrid event, is now available on YouTube. Anna Ruban Unreal Debugging Improvements in Rider 2024.2 Rider 2024.2 includes massive improvements to the native debugger, significantly improving the experience of evaluating native code while debugging. There are performance improvements, better handling of optimised code, and support for evaluating operators on smart pointers and string types. The cha… Matt Ellis Aug 7 2024 Livestream – Jodie Burchell, Matt Ellis, Khalid Abuhakmeh, and Maarten Balliauw – AI in Game Development With JetBrains AI Assistant – Recording Available Game development has entered a new era with the rise of AI-powered tools. But where is AI truly helpful, and where should we tread carefully? Join JetBrains Developer Advocates as they explore the role of AI in game development and showcase the capabilities of JetBrains AI Assistant. Recording Available. Anna Ruban Jun 4 2024 Matt Ellis and Antonio Antunes – An Eye For Success With Odin Inspector and JetBrains Rider – [Recording Available] JetBrains and Sirenix have joined forces to provide support for the hugely popular Odin Inspector Unity asset in Rider. Anna Ruban How Tarsier Studios Brings Little Nightmares to Life With JetBrains Rider Today, we have Tristan Louet and Meghan Corso from Tarsier Studios with us. Meghan is actively involved in advancing Unreal Engine support in JetBrains Rider and ReSharper C++, while Tristan leads the core technology team, focusing on plugins, reusable solutions, infrastructure, and methodologies. T… Anna Ruban Learn Unity and Godot Game Development with JetBrains Build two video games in two different game engines: Unity and Godot using C# and JetBrains Rider. Khalid Abuhakmeh Load more Privacy & Security Terms of Use Legal Genuine tools Language English Deutsch Español Français 日本語 한국어 Русский 简体中文 Português do Brasil Türkçe Čeština Twitter Facebook Linkedin Instagram Youtube RSS Tiktok Merchandise store icon Merchandise store Copyright © 2000 JetBrains s.r.o. | 2026-01-13T08:48:37 |
https://docs.sui.io/guides/developer/getting-started/hello-world | Hello, World! | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Hello, World! On this page Hello, World! You'll build a "Hello, World!" program to learn the fundamentals of programming on Sui. You create programs on Sui by writing and deploying smart contracts to the network. The most basic unit of storage on Sui is an object . Other blockchains typically structure storage using key-value stores. Sui centers storage around objects with unique ID addresses on-chain. Every Sui smart contract is an object that manipulates other objects. Objects can be immutable or mutable: Immutable objects cannot be transferred, changed, or deleted. No one owns them and anyone can access them publicly. Mutable objects can be transferred, changed, and deleted. A Sui address can own them, or they can be shared for public access. Every object's unique ID and version number references it on-chain. Every transaction on the network takes objects as input, then reads, writes, and mutates the inputs to produce new or altered objects as output. Every object knows the hash of the transaction that produced it. When an object is modified by a transaction, the transaction's output writes the object's mutated contents to the same object ID but with a new version number. Sui has limits on the maximum transaction size (128KB) and number of objects (2,048) used in a transaction. For more information on limits, see Building Against Limits in The Move Book. What is Move? Move is the programming language Sui uses to create smart contracts. It is platform agnostic and enables common libraries, tooling, and developer communities across blockchains with vastly different data and execution models. There are three ways to use Move in the context of Sui: Move packages, Move modules, and Move objects. A Sui Move package is also referred to as a Move smart contract. It is a set of Move bytecode published to the Sui network. It is immutable and cannot be changed or removed, however you can upgrade it. Upgrading creates a new version of the package object on-chain, leaving the original intact. All prior versions of a package still exist on-chain. Once you publish it, other packages can import and use the modules it provides. Anyone can view a package's contents and use a Sui Explorer to see how its logic manipulates other objects. Every Move package on Sui includes one or more Sui Move modules that define the package's interaction with on-chain objects. A module's name is always unique within the package that contains it. A Sui Move module governs a Sui Move object , which is typed data from a Sui Move package. Each Move object value is a struct with fields that can contain primitive types, such as integers and addresses, other objects, and non-object structs. Clone "Hello, World!" Prerequisites Install the latest version of Sui . Configure the Sui client . Create a Sui address . Get SUI Testnet tokens . Download and install an IDE. The following are recommended, as they offer Move extensions: VSCode , corresponding Move extension Emacs , corresponding Move extension Vim , corresponding Move extension Zed , corresponding Move extension Alternatively, you can use the Move web IDE , which does not require a download. It does not support all functions necessary for this guide, however. Download and install Git . To demonstrate creating objects, packages, and how to build your first Sui application, start by cloning the "Hello, World!" example: $ git clone \ https://github.com/MystenLabs/sui-stack-hello-world.git $ cd sui-stack-hello-world/move/hello-world In this project, there are two important files that define the package's logic, information, and its dependencies: move/hello-world/sources/greeting.move : Defines the package's logic. In this example, it defines a basic shared greeting object and public functions to interact with it. move/hello-world/Move.toml : The package's configuration file that defines the package name, dependencies, and addresses. Click to open move/hello-world/Move.toml File not found in manifest: move/hello-world/Move.toml . You probably need to run `pnpm prebuild` and restart the site. View the smart contract code Open the greeting.move file in your IDE of choice. You can see the following Move code: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Code explanation First, this code defines a module called greeting : module hello_world :: greeting { use std :: string ; ... } Then, it defines a public struct called Greeting that contains a unique object ID and text. A struct is a type of resource : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Then, it defines the function new that makes an API call to the Greeting struct and initializes it with the text "Hello world!" , storing it in a new shared object: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Lastly, the package defines a function called update_text that can be called to update the text stored in Greeting : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Resource safety A unique aspect of programming applications on Sui is the resource safety enforced by the Move Bytecode Verifier. Move packages must satisfy the following resource safety parameters: All resources must be either moved into global storage or destroyed by the end of a transaction. Resources cannot be copied. In the "Hello, World!" example, the struct Greeting is a resource type. To satisfy the requirement that all resources must be moved or destroyed by the end of a transaction, Greeting is assigned to new_greeting , which the call to transfer::share_object(new_greeting) then moves into global storage. To mutate Greeting , the function update_text takes the input (&mut Greeting) rather than the resource itself. This function satisfies resource safety as the function does not copy the resource and mutates it via a reference. Learn more about the Move Bytecode Verifier. How does this differ from EVM applications? The Ethereum Virtual Machine adopts a gas-based resource safety strategy. Every opcode on an EVM chain has an associated gas price that makes transactions costly, preventing the network from running a single transaction indefinitely. Build the Move package Before you can publish a Move package to the network, you must first build it. Building your package is necessary because the .move source file is a human-readable piece of code, while the network can only understand bytecode. To build your "Hello, World!" package, first confirm your working directory is ~/sui-stack-hello-world/move/hello-world , then run the following command: $ sui move build The build process fetches and compiles the dependencies defined in the Move.toml file. The Move compiler checks your .move code for type errors, syntax errors, and enforces resource safety , then translates your .move code into bytecode that Sui can execute. info You must build your package before you can publish it, but also before you test it. You cannot run tests ( sui move test ) on your code until it has been built. Publish the Move package Now that your package has been built, you need to publish it. After you publish it, other packages and users can use the package's modules and functions by making calls to the package ID. First, confirm your client is configured to use Testnet as the active environment: $ sui client active-env This should return testnet . If it does not return testnet , follow the client configuration instructions before continuing. Then, check your balance of SUI tokens to confirm you have enough to publish to Testnet: $ sui client balance You should have a balance of SUI tokens: ╭────────────────────────────────────────────╮ │ Balance of coins owned by this address │ ├────────────────────────────────────────────┤ │ ╭────────────────────────────────────────╮ │ │ │ coin balance (raw) balance │ │ │ ├────────────────────────────────────────┤ │ │ │ Sui 56804696124 0.50 SUI │ │ │ ╰────────────────────────────────────────╯ │ ╰────────────────────────────────────────────╯ If you do not have a balance, follow the SUI faucet instructions . Now, publish the package to Testnet with the command: $ sui client publish Click to open Output Transaction Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Data │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Owner: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Budget: 9843200 MIST │ │ Gas Price: 1000 MIST │ │ Gas Payment: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Version: 591332925 │ │ │ Digest: FLC4NXntT7WiHcqCkpDuBUq14DFTfi3EFeUiJcSNHdPu │ │ └── │ │ │ │ Transaction Kind: Programmable │ │ ╭─────────────────────────────────────────────────────────────────────────────────── ───────────────────────╮ │ │ │ Input Objects │ │ │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Pure Arg: Type: address, Value: "0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803" │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ │ ╭─────────────────────────────────────────────────────────────────────────╮ │ │ │ Commands │ │ │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Publish: │ │ │ │ ┌ │ │ │ │ │ Dependencies: │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │ │ │ └ │ │ │ │ │ │ │ │ 1 TransferObjects: │ │ │ │ ┌ │ │ │ │ │ Arguments: │ │ │ │ │ Result 0 │ │ │ │ │ Address: Input 0 │ │ │ │ └ │ │ │ ╰─────────────────────────────────────────────────────────────────────────╯ │ │ │ │ Signatures: │ │ mUxqMIofPq+yIzPxxYM+2mSIPTFneDxhWGGxJ7tM02hnRBRy5/FosnnWKxd4OSAjmaw6FNylwVdqUoUlJSxWCQ== │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ ┌── │ │ │ ID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Owner: Immutable │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Object: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Cost Summary: │ │ Storage Cost: 7843200 MIST │ │ Computation Cost: 1000000 MIST │ │ Storage Rebate: 978120 MIST │ │ Non-refundable Storage Fee: 9880 MIST │ │ │ │ Transaction Dependencies: │ │ 2dkJtqsoQcyCZJvjZnskNVPQeynwVtwCcA9goAru6tTi │ │ 7PStztXyh92keJmrDD1aghHaKVdgCoVkVx4ZmLUfmQeK │ │ Dd9pn1zFcSJjinxQewFd2gQdR4XKsHxFioD5MYnwLZQz │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─────────────────────── ──────╮ │ No transaction block events │ ╰─────────────────────────────╯ ╭──────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Object Changes │ ├──────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created Objects: │ │ ┌── │ │ │ ObjectID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::package::UpgradeCap │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ObjectID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Balance Changes │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ┌── │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ CoinType: 0x2::sui::SUI │ │ │ Amount: -7865080 │ │ └── │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ When you publish a Move package to the network, the network uploads and stores the bytecode as a Move package with a unique package ID and version number. The network consumes SUI tokens as gas and processes the transaction on-chain. After successfully executing, the output provides details about the transaction used to publish the package, including the gas cost, transaction digest, dependencies, owner, and sender. For this guide, the most important section is Published Objects , which includes the package's ID, version, and its modules: │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── Both the package ID and module are required to interact with the package from the command line. Take note of both values for future use in the Connecting a Frontend guide. Interact with the Move package Interact with the newly published package by first making a call to the new function that creates a new Greeting object and initialize it with the text "Hello world!" : $ sui client call --package <PACKAGE_ID> --module greeting --function new Replace <PACKAGE_ID> with the package ID the output of the sui client publish command returned. You must include the --package , --module , and --function flags. The output of this call includes a newly created object: ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ Owner: Shared( 591332927 ) │ │ │ Version: 591332927 │ │ │ Digest: 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ └── ... To verify that the object contains the text "Hello world!" , make a call to query the object's information: $ sui client object <OBJECT_ID> Replace <OBJECT_ID> with the value under Created Objects, ID: . You should see the object's details, including a value of text: Hello world! : ╭───────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ objectId │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ version │ 591332927 │ │ digest │ 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ objType │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ owner │ ╭────────┬──────────────────────────────────────────╮ │ │ │ │ Shared │ ╭────────────────────────┬─────────────╮ │ │ │ │ │ │ │ initial_shared_version │ 591332927 │ │ │ │ │ │ │ ╰────────────────────────┴─────────────╯ │ │ │ │ ╰────────┴──────────────────────────────────────────╯ │ │ prevTx │ 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ storageRebate │ 1413600 │ │ content │ ╭───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ dataType │ moveObject │ │ │ │ │ type │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ │ │ │ hasPublicTransfer │ false │ │ │ │ │ fields │ ╭──────┬───────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ id │ ╭────┬──────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ │ │ │ id │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ │ │ │ │ │ │ │ ╰────┴──────────────────────────────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ text │ Hello world! │ │ │ │ │ │ │ ╰──────┴───────────────────────────────────────────────────────────────────────────────╯ │ │ │ │ ╰───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────╯ │ ╰───────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Important transaction considerations You cannot send 2 or more transactions simultaneously, otherwise you encounter an error such as: Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. If you receive this error, you must wait until the current epoch is over before submitting your transaction again. You can see how long is left in the current epoch using Sui Explorer or another network explorer like SuiScan . To prevent the same object from being modified by multiple transactions at once, your address 'locks' the object to prevent conflicting modifications. If you'd like to batch multiple transaction commands together, you can use programmable transaction blocks . Transactions also have limitations regarding total size, number of objects, and number of inputs. Learn more about limitations in Building Against Limits in The Move Book. Next steps Create a Full Stack dApp Connect a frontend interface to your "Hello, World!" smart contract. Access Sui Data Learn more about accessing data on Sui. Join the Community Join the Sui developer community, try out other example projects, or read more documentation. Edit this page What is Move? Clone "Hello, World!" View the smart contract code Code explanation Resource safety Build the Move package Publish the Move package Interact with the Move package Important transaction considerations © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:37 |
https://legal.x.com/ads-terms.html | X Master Services Agreement X logo icon X Master Services Agreement Americas United States of America and Canada Brazil Rest of Americas Europe, Middle East, Africa United Kingdom Rest of Europe, Middle East, Africa Asia Pacific Indonesia Japan Korea Philippines Rest of Asia Pacific © 2026 X Corp. Cookies Privacy Terms and conditions Language English Italiano Deutsch Español Français 日本語 한국어 Português Русский العربية Bahasa Indonesia Türkçe 简体中文 Čeština Ελληνικά Norsk Polski Română Nederlands Български Dansk Eesti Suomi Gaeilge Hrvatski Magyar Lietuvių Latviešu Malti Slovenčina Slovenščina Svenska Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:37 |
https://youtu.be/ | 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:48:37 |
https://ruul.io/blog/12-tips-for-taking-care-of-your-mental-health-as-a-freelancer?7c89d873_page=2 | Blog | For Freelancers, Creators, and Indie Professionals Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up grow 13 Best Fiverr Alternatives Freelancers Need to Know Read POPULAR ARTICLES How to Accept Online Payments: A Comprehensive Guide for Businesses and Freelancers Learn how to set up and manage secure online payment systems for your business or freelance work. Discover popular payment methods, integration tips, security measures, and best practices to streamline transactions and boost efficiency. Top 15 Digital Nomad Jobs in 2025 Explore the 15 best digital nomad jobs in 2025, from writing to coding—fully remote, high-paying, and travel-friendly. The Ultimate Best AI Tools for Freelancers: Boosting Productivity in 2025 Discover the ultimate AI tools for freelancers in 2025 to enhance productivity and efficiency. From writing and graphic design to project management, explore top AI tools like ChatGPT, Grammarly, Canva, and more. Start optimizing your freelancing. How to Accept Cryptocurrency Payments Find the methods, benefits, and security considerations for accepting crypto payments. Know how cryptocurrencies can open new opportunities for your business. What to Sell as a Digital Product Want to make money while you sleep? From AI art to ebooks and plugins, here’s what actually sells in 2025 and makes your wallet happy! Best 13 Motivational Apps and Techniques You Need As You Work Solo Lack of motivation as an independent? See these motivation apps and techniques. get paid sell grow work news trends get paid sell grow work news trends How to Make Freelance Money I’ve mapped out the freelance income paths that will stick around until 2030. Shared all the pro tips and details in this post. Come check it out! Introducing MiniPay on Ruul: Faster Stablecoin Payment Ruul & MiniPay now bring instant, stablecoin payments with zero withdrawal fee for freelancers. Create virtual USD/EUR accounts, enjoy fast global transfers, and earn up to $275 in bonuses. Best Freelancing Websites Struggling to pick a freelancing website? These 16 categorized freelancing platforms will save your time, energy, and maybe your sanity! How to Get Paid as a Freelancer Don't let payments ruin your business! We've covered everything from the most important steps to the best methods! Designer's Guide to Dribbble All the potential Dribbble has to offer, and all the areas where it leaves you hanging. This Guide gives you all of that and more. Best Freelance Jobs You're looking for the best freelance jobs AI won't wipe out. Safe, in-demand, future-ready, long-lasting work… you'll find it all right here. MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:37 |
https://bsky.app/profile/react.dev | @react.dev on Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . Profile react.dev did:plc:uorpbnp2q32vuvyeruwauyhe | 2026-01-13T08:48:38 |
https://docs.suprsend.com/reference/get-event | Get Event Details - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection API Reference Overview Authentication Errors WORKFLOWS POST Create/Update Workflow PATCH Commit Workflow GET Get Workflow GET List Workflows PATCH Enable/Disable Workflow DEL Delete Workflow SCHEMAS POST Create/Update Schema PATCH Commit Schema GET List Schemas GET Get Schema EVENTS POST Create Event PATCH Update Event GET List Events GET Get Event Details GET Get Linked Workflows PATCH Delink Schema from Event CATEGORIES GET Get Category POST Create/Update Category PATCH Commit Category GET List Translation GET Get Translation POST Add Translation DEL Delete Translation TRANSLATIONS POST Add Translation PATCH Commit Translation GET Get Translation GET List Translations GET Get Translation History POST Rollback Translation DEL Delete Translation Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation EVENTS Get Event Details Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog EVENTS Get Event Details OpenAI Open in ChatGPT Fetch event details and its linked schema. OpenAI Open in ChatGPT GET / v1 / {workspace} / event / {url_encoded_event_name} Try it cURL cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/event/{url_encoded_event_name}/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 400 401 Copy Ask AI { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : { "schema" : "user_signup_v1" , "version_no" : 1 }, "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } Authorizations ServiceToken <token> string header required You can get Service Token from SuprSend dashboard -> Account Settings -> Service Tokens section. Path Parameters workspace string required Workspace slug (staging, production, etc.) url_encoded_event_name string required URL encoded event name. Example - SHIPMENT%20ARRIVED Response 200 application/json Successfully retrieved event name string Event name Example : "user_signup" description string Description of the event Example : "Triggered whenever a new user successfully signs up on the platform" payload_schema object Show child attributes created_at string<date-time> When the event was created Example : "2025-08-27T09:30:57.945326Z" $schema string JSON Schema reference for how the event API call should be structured. Example : "https://schema.suprsend.com/event/v1/schema.json" Was this page helpful? Yes No Suggest edits Raise issue Previous Get Linked Workflows Fetch list of all workflows where this event is used Next ⌘ I x github linkedin youtube Powered by cURL cURL Copy Ask AI curl -X GET "https://management-api.suprsend.com/v1/{workspace}/event/{url_encoded_event_name}/" \ --header 'Authorization: ServiceToken <token>' \ --header 'Content-Type: application/json' 200 400 401 Copy Ask AI { "name" : "user_signup" , "description" : "Triggered whenever a new user successfully signs up on the platform" , "payload_schema" : { "schema" : "user_signup_v1" , "version_no" : 1 }, "created_at" : "2025-08-27T09:30:57.945326Z" , "$schema" : "https://schema.suprsend.com/event/v1/schema.json" } | 2026-01-13T08:48:38 |
https://twitter.com/bluesky | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:38 |
https://blog.devcycle.com/creating-a-star-trek-inspired-genai-copilot-using-pieces-and-devcycle/ | Creating a Star Trek-Inspired GenAI Copilot Using Pieces and DevCycle Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Guides and Tutorials Creating a Star Trek-Inspired GenAI Copilot Using Pieces and DevCycle In this post, we show you how DevCycle and Pieces for Developers make experimenting with AI as smooth as a warp-speed jump. DevCycle Nov 11, 2024 Learn how to create a Star Trek inspiried Python GenAI Copilot using Pieces and DevCycle ! Originally published on the Pieces blog here . Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:38 |
https://blog.devcycle.com/how-jackson-used-devcycle-and-openfeature-to-achieve-a-zero-downtime-migration/ | How Jackson Used DevCycle and OpenFeature to Achieve a Zero-Downtime Migration Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature How Jackson Used DevCycle and OpenFeature to Achieve a Zero-Downtime Migration DevCycle Mar 4, 2025 • 3 min read Today's DevCycle Spotlight features Jackson Kasi , a developer who won the OpenFeature Aficionado prize for our first ever DevCycle Feature Flag Challenge on Dev.to where we challenged developers to build a fun or creative project using DevCycle ! Jackson won the OpenFeature Aficionado prize for the most innovative use of a DevCycle OpenFeature provider with his Zero-Downtime PostgreSQL Migration project. Judges were impressed by how Jackson utilized DevCycle feature flags to migrate a high-transaction database without any downtime, a creative solution to a real-life problem. Using DevCycle to Enable a Zero-Downtime Migration Jackson's project looked to migrate a PostgreSQL database that processed thousands of transactions every minute to a new environment. The challenge was to do this without taking the system offline or risking data integrity. Not an easy task! Jackson needed a strategy that would allow him to: Write to both old and new databases simultaneously during the migration. Gradually switch read operations from the old database to the new one for specific user groups. Ensure zero downtime and maintain data consistency throughout the migration process. DevCycle allowed him to dynamically control which database the application interacted with, based on user contexts and feature flags. How Jackson Used DevCycle Features to Create a Winning Project: Jackson first set up feature flags on DevCycle: write : Controls write operations to the new database. read : Controls read operations from the new database. Then defined the conditions to target specific user groups: Testing Group : Users with IDs 123 or 456 . Served the Testing Groups variant. Customer Group : All other users. Served the User Groups variant. Next up was implementing dual write and conditional read in code. In the server code, he evaluated feature flags based on user context: Write Operations : If writeToNewDB is true , write to both databases. If false , write only to the old database. Read Operations : If readFromNewDB is true , read from the new database. If false , read from the old database. This logic helped ensure data consistency and allowed for controlled testing. Jackson then automated the data sync with PostgreSQL's Publish-Subscribe and built Docker containers and scripts. He utilized DevCycle's Management API for dynamic control which allowed him to: Update feature flags programmatically Control rollout phases Quickly switch read/write operations as needed. He conducted testing by enabling the new database for specific real users by targeting users from countries like India and the United States and users with a Pro subscription. This allowed him to: Validate the new database under real-world conditions Gather feedback and address any issues Ensure performance met standards Finally, after successful testing, Jackson was ready for the final rollout! He confirmed data integrity and application performance and gradually enabled the new database for all users and completed the migration by disabling the old database. DevCycle Features That Stood Out We asked Jackson to share his experience using DevCycle to build his winning project: [DevCycle is] super easy to understand. I didn't have to spend lots of time figuring out the feature management - it just let me focus on the logic. - Jackson Kasi He also highlighted: The usefulness of real-time updates and DevCycle custom properties The simple integration with DevCycle's SDK and OpenFeature provider . More about Jackson Kasi Jackson has been working at Peacock India for the past 3 years, a services-based company where he handles the technical aspects of client's projects, while leading his team and takes immense pride in helping his customers find solutions. His winning DevCycle project was actually inspired by a real-life situation where a client was looking to migrate their database from a self-hosted server to the cloud. This led him to build his own open-source project for handling manual and automatic back and restore operations, which he hopes will help others. One of Jackson's current projects is a Figma plugin that helps handle asset relations operations and he's hoping it will be helpful to both developers and designers. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:38 |
https://docs.sui.io/guides/developer/getting-started/connect#build-the-move-package | Hello, World! | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Hello, World! On this page Hello, World! You'll build a "Hello, World!" program to learn the fundamentals of programming on Sui. You create programs on Sui by writing and deploying smart contracts to the network. The most basic unit of storage on Sui is an object . Other blockchains typically structure storage using key-value stores. Sui centers storage around objects with unique ID addresses on-chain. Every Sui smart contract is an object that manipulates other objects. Objects can be immutable or mutable: Immutable objects cannot be transferred, changed, or deleted. No one owns them and anyone can access them publicly. Mutable objects can be transferred, changed, and deleted. A Sui address can own them, or they can be shared for public access. Every object's unique ID and version number references it on-chain. Every transaction on the network takes objects as input, then reads, writes, and mutates the inputs to produce new or altered objects as output. Every object knows the hash of the transaction that produced it. When an object is modified by a transaction, the transaction's output writes the object's mutated contents to the same object ID but with a new version number. Sui has limits on the maximum transaction size (128KB) and number of objects (2,048) used in a transaction. For more information on limits, see Building Against Limits in The Move Book. What is Move? Move is the programming language Sui uses to create smart contracts. It is platform agnostic and enables common libraries, tooling, and developer communities across blockchains with vastly different data and execution models. There are three ways to use Move in the context of Sui: Move packages, Move modules, and Move objects. A Sui Move package is also referred to as a Move smart contract. It is a set of Move bytecode published to the Sui network. It is immutable and cannot be changed or removed, however you can upgrade it. Upgrading creates a new version of the package object on-chain, leaving the original intact. All prior versions of a package still exist on-chain. Once you publish it, other packages can import and use the modules it provides. Anyone can view a package's contents and use a Sui Explorer to see how its logic manipulates other objects. Every Move package on Sui includes one or more Sui Move modules that define the package's interaction with on-chain objects. A module's name is always unique within the package that contains it. A Sui Move module governs a Sui Move object , which is typed data from a Sui Move package. Each Move object value is a struct with fields that can contain primitive types, such as integers and addresses, other objects, and non-object structs. Clone "Hello, World!" Prerequisites Install the latest version of Sui . Configure the Sui client . Create a Sui address . Get SUI Testnet tokens . Download and install an IDE. The following are recommended, as they offer Move extensions: VSCode , corresponding Move extension Emacs , corresponding Move extension Vim , corresponding Move extension Zed , corresponding Move extension Alternatively, you can use the Move web IDE , which does not require a download. It does not support all functions necessary for this guide, however. Download and install Git . To demonstrate creating objects, packages, and how to build your first Sui application, start by cloning the "Hello, World!" example: $ git clone \ https://github.com/MystenLabs/sui-stack-hello-world.git $ cd sui-stack-hello-world/move/hello-world In this project, there are two important files that define the package's logic, information, and its dependencies: move/hello-world/sources/greeting.move : Defines the package's logic. In this example, it defines a basic shared greeting object and public functions to interact with it. move/hello-world/Move.toml : The package's configuration file that defines the package name, dependencies, and addresses. Click to open move/hello-world/Move.toml File not found in manifest: move/hello-world/Move.toml . You probably need to run `pnpm prebuild` and restart the site. View the smart contract code Open the greeting.move file in your IDE of choice. You can see the following Move code: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Code explanation First, this code defines a module called greeting : module hello_world :: greeting { use std :: string ; ... } Then, it defines a public struct called Greeting that contains a unique object ID and text. A struct is a type of resource : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Then, it defines the function new that makes an API call to the Greeting struct and initializes it with the text "Hello world!" , storing it in a new shared object: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Lastly, the package defines a function called update_text that can be called to update the text stored in Greeting : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Resource safety A unique aspect of programming applications on Sui is the resource safety enforced by the Move Bytecode Verifier. Move packages must satisfy the following resource safety parameters: All resources must be either moved into global storage or destroyed by the end of a transaction. Resources cannot be copied. In the "Hello, World!" example, the struct Greeting is a resource type. To satisfy the requirement that all resources must be moved or destroyed by the end of a transaction, Greeting is assigned to new_greeting , which the call to transfer::share_object(new_greeting) then moves into global storage. To mutate Greeting , the function update_text takes the input (&mut Greeting) rather than the resource itself. This function satisfies resource safety as the function does not copy the resource and mutates it via a reference. Learn more about the Move Bytecode Verifier. How does this differ from EVM applications? The Ethereum Virtual Machine adopts a gas-based resource safety strategy. Every opcode on an EVM chain has an associated gas price that makes transactions costly, preventing the network from running a single transaction indefinitely. Build the Move package Before you can publish a Move package to the network, you must first build it. Building your package is necessary because the .move source file is a human-readable piece of code, while the network can only understand bytecode. To build your "Hello, World!" package, first confirm your working directory is ~/sui-stack-hello-world/move/hello-world , then run the following command: $ sui move build The build process fetches and compiles the dependencies defined in the Move.toml file. The Move compiler checks your .move code for type errors, syntax errors, and enforces resource safety , then translates your .move code into bytecode that Sui can execute. info You must build your package before you can publish it, but also before you test it. You cannot run tests ( sui move test ) on your code until it has been built. Publish the Move package Now that your package has been built, you need to publish it. After you publish it, other packages and users can use the package's modules and functions by making calls to the package ID. First, confirm your client is configured to use Testnet as the active environment: $ sui client active-env This should return testnet . If it does not return testnet , follow the client configuration instructions before continuing. Then, check your balance of SUI tokens to confirm you have enough to publish to Testnet: $ sui client balance You should have a balance of SUI tokens: ╭────────────────────────────────────────────╮ │ Balance of coins owned by this address │ ├────────────────────────────────────────────┤ │ ╭────────────────────────────────────────╮ │ │ │ coin balance (raw) balance │ │ │ ├────────────────────────────────────────┤ │ │ │ Sui 56804696124 0.50 SUI │ │ │ ╰────────────────────────────────────────╯ │ ╰────────────────────────────────────────────╯ If you do not have a balance, follow the SUI faucet instructions . Now, publish the package to Testnet with the command: $ sui client publish Click to open Output Transaction Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Data │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Owner: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Budget: 9843200 MIST │ │ Gas Price: 1000 MIST │ │ Gas Payment: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Version: 591332925 │ │ │ Digest: FLC4NXntT7WiHcqCkpDuBUq14DFTfi3EFeUiJcSNHdPu │ │ └── │ │ │ │ Transaction Kind: Programmable │ │ ╭─────────────────────────────────────────────────────────────────────────────────── ───────────────────────╮ │ │ │ Input Objects │ │ │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Pure Arg: Type: address, Value: "0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803" │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ │ ╭─────────────────────────────────────────────────────────────────────────╮ │ │ │ Commands │ │ │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Publish: │ │ │ │ ┌ │ │ │ │ │ Dependencies: │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │ │ │ └ │ │ │ │ │ │ │ │ 1 TransferObjects: │ │ │ │ ┌ │ │ │ │ │ Arguments: │ │ │ │ │ Result 0 │ │ │ │ │ Address: Input 0 │ │ │ │ └ │ │ │ ╰─────────────────────────────────────────────────────────────────────────╯ │ │ │ │ Signatures: │ │ mUxqMIofPq+yIzPxxYM+2mSIPTFneDxhWGGxJ7tM02hnRBRy5/FosnnWKxd4OSAjmaw6FNylwVdqUoUlJSxWCQ== │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ ┌── │ │ │ ID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Owner: Immutable │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Object: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Cost Summary: │ │ Storage Cost: 7843200 MIST │ │ Computation Cost: 1000000 MIST │ │ Storage Rebate: 978120 MIST │ │ Non-refundable Storage Fee: 9880 MIST │ │ │ │ Transaction Dependencies: │ │ 2dkJtqsoQcyCZJvjZnskNVPQeynwVtwCcA9goAru6tTi │ │ 7PStztXyh92keJmrDD1aghHaKVdgCoVkVx4ZmLUfmQeK │ │ Dd9pn1zFcSJjinxQewFd2gQdR4XKsHxFioD5MYnwLZQz │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─────────────────────── ──────╮ │ No transaction block events │ ╰─────────────────────────────╯ ╭──────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Object Changes │ ├──────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created Objects: │ │ ┌── │ │ │ ObjectID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::package::UpgradeCap │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ObjectID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Balance Changes │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ┌── │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ CoinType: 0x2::sui::SUI │ │ │ Amount: -7865080 │ │ └── │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ When you publish a Move package to the network, the network uploads and stores the bytecode as a Move package with a unique package ID and version number. The network consumes SUI tokens as gas and processes the transaction on-chain. After successfully executing, the output provides details about the transaction used to publish the package, including the gas cost, transaction digest, dependencies, owner, and sender. For this guide, the most important section is Published Objects , which includes the package's ID, version, and its modules: │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── Both the package ID and module are required to interact with the package from the command line. Take note of both values for future use in the Connecting a Frontend guide. Interact with the Move package Interact with the newly published package by first making a call to the new function that creates a new Greeting object and initialize it with the text "Hello world!" : $ sui client call --package <PACKAGE_ID> --module greeting --function new Replace <PACKAGE_ID> with the package ID the output of the sui client publish command returned. You must include the --package , --module , and --function flags. The output of this call includes a newly created object: ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ Owner: Shared( 591332927 ) │ │ │ Version: 591332927 │ │ │ Digest: 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ └── ... To verify that the object contains the text "Hello world!" , make a call to query the object's information: $ sui client object <OBJECT_ID> Replace <OBJECT_ID> with the value under Created Objects, ID: . You should see the object's details, including a value of text: Hello world! : ╭───────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ objectId │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ version │ 591332927 │ │ digest │ 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ objType │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ owner │ ╭────────┬──────────────────────────────────────────╮ │ │ │ │ Shared │ ╭────────────────────────┬─────────────╮ │ │ │ │ │ │ │ initial_shared_version │ 591332927 │ │ │ │ │ │ │ ╰────────────────────────┴─────────────╯ │ │ │ │ ╰────────┴──────────────────────────────────────────╯ │ │ prevTx │ 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ storageRebate │ 1413600 │ │ content │ ╭───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ dataType │ moveObject │ │ │ │ │ type │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ │ │ │ hasPublicTransfer │ false │ │ │ │ │ fields │ ╭──────┬───────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ id │ ╭────┬──────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ │ │ │ id │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ │ │ │ │ │ │ │ ╰────┴──────────────────────────────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ text │ Hello world! │ │ │ │ │ │ │ ╰──────┴───────────────────────────────────────────────────────────────────────────────╯ │ │ │ │ ╰───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────╯ │ ╰───────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Important transaction considerations You cannot send 2 or more transactions simultaneously, otherwise you encounter an error such as: Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. If you receive this error, you must wait until the current epoch is over before submitting your transaction again. You can see how long is left in the current epoch using Sui Explorer or another network explorer like SuiScan . To prevent the same object from being modified by multiple transactions at once, your address 'locks' the object to prevent conflicting modifications. If you'd like to batch multiple transaction commands together, you can use programmable transaction blocks . Transactions also have limitations regarding total size, number of objects, and number of inputs. Learn more about limitations in Building Against Limits in The Move Book. Next steps Create a Full Stack dApp Connect a frontend interface to your "Hello, World!" smart contract. Access Sui Data Learn more about accessing data on Sui. Join the Community Join the Sui developer community, try out other example projects, or read more documentation. Edit this page What is Move? Clone "Hello, World!" View the smart contract code Code explanation Resource safety Build the Move package Publish the Move package Interact with the Move package Important transaction considerations © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:38 |
https://docs.sui.io/guides/developer/getting-started/connect#interact-with-the-move-package | Hello, World! | Sui Documentation Skip to main content Sui Documentation Guides Concepts Standards References Search Overview Getting Started Install Sui Install from Source Install from Binaries Configure a Sui Client Create a Sui Address Get SUI from Faucet Hello, World! Connect a Frontend Next Steps Sui Essentials Objects Packages Currencies and Tokens NFTs Cryptography Nautilus Advanced App Examples Dev Cheat Sheet Operator Guides SuiPlay0X1 🗳️ Book Office Hours → 💬 Join Discord → Getting Started Hello, World! On this page Hello, World! You'll build a "Hello, World!" program to learn the fundamentals of programming on Sui. You create programs on Sui by writing and deploying smart contracts to the network. The most basic unit of storage on Sui is an object . Other blockchains typically structure storage using key-value stores. Sui centers storage around objects with unique ID addresses on-chain. Every Sui smart contract is an object that manipulates other objects. Objects can be immutable or mutable: Immutable objects cannot be transferred, changed, or deleted. No one owns them and anyone can access them publicly. Mutable objects can be transferred, changed, and deleted. A Sui address can own them, or they can be shared for public access. Every object's unique ID and version number references it on-chain. Every transaction on the network takes objects as input, then reads, writes, and mutates the inputs to produce new or altered objects as output. Every object knows the hash of the transaction that produced it. When an object is modified by a transaction, the transaction's output writes the object's mutated contents to the same object ID but with a new version number. Sui has limits on the maximum transaction size (128KB) and number of objects (2,048) used in a transaction. For more information on limits, see Building Against Limits in The Move Book. What is Move? Move is the programming language Sui uses to create smart contracts. It is platform agnostic and enables common libraries, tooling, and developer communities across blockchains with vastly different data and execution models. There are three ways to use Move in the context of Sui: Move packages, Move modules, and Move objects. A Sui Move package is also referred to as a Move smart contract. It is a set of Move bytecode published to the Sui network. It is immutable and cannot be changed or removed, however you can upgrade it. Upgrading creates a new version of the package object on-chain, leaving the original intact. All prior versions of a package still exist on-chain. Once you publish it, other packages can import and use the modules it provides. Anyone can view a package's contents and use a Sui Explorer to see how its logic manipulates other objects. Every Move package on Sui includes one or more Sui Move modules that define the package's interaction with on-chain objects. A module's name is always unique within the package that contains it. A Sui Move module governs a Sui Move object , which is typed data from a Sui Move package. Each Move object value is a struct with fields that can contain primitive types, such as integers and addresses, other objects, and non-object structs. Clone "Hello, World!" Prerequisites Install the latest version of Sui . Configure the Sui client . Create a Sui address . Get SUI Testnet tokens . Download and install an IDE. The following are recommended, as they offer Move extensions: VSCode , corresponding Move extension Emacs , corresponding Move extension Vim , corresponding Move extension Zed , corresponding Move extension Alternatively, you can use the Move web IDE , which does not require a download. It does not support all functions necessary for this guide, however. Download and install Git . To demonstrate creating objects, packages, and how to build your first Sui application, start by cloning the "Hello, World!" example: $ git clone \ https://github.com/MystenLabs/sui-stack-hello-world.git $ cd sui-stack-hello-world/move/hello-world In this project, there are two important files that define the package's logic, information, and its dependencies: move/hello-world/sources/greeting.move : Defines the package's logic. In this example, it defines a basic shared greeting object and public functions to interact with it. move/hello-world/Move.toml : The package's configuration file that defines the package name, dependencies, and addresses. Click to open move/hello-world/Move.toml File not found in manifest: move/hello-world/Move.toml . You probably need to run `pnpm prebuild` and restart the site. View the smart contract code Open the greeting.move file in your IDE of choice. You can see the following Move code: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Code explanation First, this code defines a module called greeting : module hello_world :: greeting { use std :: string ; ... } Then, it defines a public struct called Greeting that contains a unique object ID and text. A struct is a type of resource : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Then, it defines the function new that makes an API call to the Greeting struct and initializes it with the text "Hello world!" , storing it in a new shared object: File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Lastly, the package defines a function called update_text that can be called to update the text stored in Greeting : File not found in manifest: move/hello-world/sources/greeting.move . You probably need to run `pnpm prebuild` and restart the site. Resource safety A unique aspect of programming applications on Sui is the resource safety enforced by the Move Bytecode Verifier. Move packages must satisfy the following resource safety parameters: All resources must be either moved into global storage or destroyed by the end of a transaction. Resources cannot be copied. In the "Hello, World!" example, the struct Greeting is a resource type. To satisfy the requirement that all resources must be moved or destroyed by the end of a transaction, Greeting is assigned to new_greeting , which the call to transfer::share_object(new_greeting) then moves into global storage. To mutate Greeting , the function update_text takes the input (&mut Greeting) rather than the resource itself. This function satisfies resource safety as the function does not copy the resource and mutates it via a reference. Learn more about the Move Bytecode Verifier. How does this differ from EVM applications? The Ethereum Virtual Machine adopts a gas-based resource safety strategy. Every opcode on an EVM chain has an associated gas price that makes transactions costly, preventing the network from running a single transaction indefinitely. Build the Move package Before you can publish a Move package to the network, you must first build it. Building your package is necessary because the .move source file is a human-readable piece of code, while the network can only understand bytecode. To build your "Hello, World!" package, first confirm your working directory is ~/sui-stack-hello-world/move/hello-world , then run the following command: $ sui move build The build process fetches and compiles the dependencies defined in the Move.toml file. The Move compiler checks your .move code for type errors, syntax errors, and enforces resource safety , then translates your .move code into bytecode that Sui can execute. info You must build your package before you can publish it, but also before you test it. You cannot run tests ( sui move test ) on your code until it has been built. Publish the Move package Now that your package has been built, you need to publish it. After you publish it, other packages and users can use the package's modules and functions by making calls to the package ID. First, confirm your client is configured to use Testnet as the active environment: $ sui client active-env This should return testnet . If it does not return testnet , follow the client configuration instructions before continuing. Then, check your balance of SUI tokens to confirm you have enough to publish to Testnet: $ sui client balance You should have a balance of SUI tokens: ╭────────────────────────────────────────────╮ │ Balance of coins owned by this address │ ├────────────────────────────────────────────┤ │ ╭────────────────────────────────────────╮ │ │ │ coin balance (raw) balance │ │ │ ├────────────────────────────────────────┤ │ │ │ Sui 56804696124 0.50 SUI │ │ │ ╰────────────────────────────────────────╯ │ ╰────────────────────────────────────────────╯ If you do not have a balance, follow the SUI faucet instructions . Now, publish the package to Testnet with the command: $ sui client publish Click to open Output Transaction Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW ╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Data │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Owner: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ Gas Budget: 9843200 MIST │ │ Gas Price: 1000 MIST │ │ Gas Payment: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Version: 591332925 │ │ │ Digest: FLC4NXntT7WiHcqCkpDuBUq14DFTfi3EFeUiJcSNHdPu │ │ └── │ │ │ │ Transaction Kind: Programmable │ │ ╭─────────────────────────────────────────────────────────────────────────────────── ───────────────────────╮ │ │ │ Input Objects │ │ │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Pure Arg: Type: address, Value: "0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803" │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────╯ │ │ ╭─────────────────────────────────────────────────────────────────────────╮ │ │ │ Commands │ │ │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ 0 Publish: │ │ │ │ ┌ │ │ │ │ │ Dependencies: │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000001 │ │ │ │ │ 0x0000000000000000000000000000000000000000000000000000000000000002 │ │ │ │ └ │ │ │ │ │ │ │ │ 1 TransferObjects: │ │ │ │ ┌ │ │ │ │ │ Arguments: │ │ │ │ │ Result 0 │ │ │ │ │ Address: Input 0 │ │ │ │ └ │ │ │ ╰─────────────────────────────────────────────────────────────────────────╯ │ │ │ │ Signatures: │ │ mUxqMIofPq+yIzPxxYM+2mSIPTFneDxhWGGxJ7tM02hnRBRy5/FosnnWKxd4OSAjmaw6FNylwVdqUoUlJSxWCQ== │ │ │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 8R39iKKLGPDG3QkW2SrRW3QX71csRP2BLhK9H7oz9SwW │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ ┌── │ │ │ ID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Owner: Immutable │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Object: │ │ ┌── │ │ │ ID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Gas Cost Summary: │ │ Storage Cost: 7843200 MIST │ │ Computation Cost: 1000000 MIST │ │ Storage Rebate: 978120 MIST │ │ Non-refundable Storage Fee: 9880 MIST │ │ │ │ Transaction Dependencies: │ │ 2dkJtqsoQcyCZJvjZnskNVPQeynwVtwCcA9goAru6tTi │ │ 7PStztXyh92keJmrDD1aghHaKVdgCoVkVx4ZmLUfmQeK │ │ Dd9pn1zFcSJjinxQewFd2gQdR4XKsHxFioD5MYnwLZQz │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭─────────────────────── ──────╮ │ No transaction block events │ ╰─────────────────────────────╯ ╭──────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Object Changes │ ├──────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Created Objects: │ │ ┌── │ │ │ ObjectID: 0x136e41f505888066f189fb823d710ec96ab4fd75144b3d8008b91d58de85fd12 │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::package::UpgradeCap │ │ │ Version: 591332926 │ │ │ Digest: BGfc1tihsYPTLLozrj58HmRkDeQ1DWZfqeaR4SZDb1cX │ │ └── │ │ Mutated Objects: │ │ ┌── │ │ │ ObjectID: 0x816e5ec6ff457f18232498b57af8a0e1e219307a3a43fb5df5a4c2198296510c │ │ │ Sender: 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ ObjectType: 0x2::coin::Coin<0x2::sui::SUI> │ │ │ Version: 591332926 │ │ │ Digest: CiU5KNZALUmuckc2YUFmJq5YXgbB8oG3rs4cnh2rdDXd │ │ └── │ │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── │ ╰──────────────────────────────────────────────────────────────────────────────────────────────────╯ ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Balance Changes │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ ┌── │ │ │ Owner: Account Address ( 0x9ac241b2b3cb87ecd2a58724d4d182b5cd897ad307df62be2ae84beddc9d9803 ) │ │ │ CoinType: 0x2::sui::SUI │ │ │ Amount: -7865080 │ │ └── │ ╰───────────────────────────────────────────────────────────────────────────────────────────────────╯ When you publish a Move package to the network, the network uploads and stores the bytecode as a Move package with a unique package ID and version number. The network consumes SUI tokens as gas and processes the transaction on-chain. After successfully executing, the output provides details about the transaction used to publish the package, including the gas cost, transaction digest, dependencies, owner, and sender. For this guide, the most important section is Published Objects , which includes the package's ID, version, and its modules: │ Published Objects: │ │ ┌── │ │ │ PackageID: 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1 │ │ │ Version: 1 │ │ │ Digest: EtGAG9RHHCsguX4iuX1cbRDvW4QAkJXgDCMJjiufHtxB │ │ │ Modules: greeting │ │ └── Both the package ID and module are required to interact with the package from the command line. Take note of both values for future use in the Connecting a Frontend guide. Interact with the Move package Interact with the newly published package by first making a call to the new function that creates a new Greeting object and initialize it with the text "Hello world!" : $ sui client call --package <PACKAGE_ID> --module greeting --function new Replace <PACKAGE_ID> with the package ID the output of the sui client publish command returned. You must include the --package , --module , and --function flags. The output of this call includes a newly created object: ╭───────────────────────────────────────────────────────────────────────────────────────────────────╮ │ Transaction Effects │ ├───────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Digest: 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ Status: Success │ │ Executed Epoch: 875 │ │ │ │ Created Objects: │ │ ┌── │ │ │ ID: 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ Owner: Shared( 591332927 ) │ │ │ Version: 591332927 │ │ │ Digest: 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ └── ... To verify that the object contains the text "Hello world!" , make a call to query the object's information: $ sui client object <OBJECT_ID> Replace <OBJECT_ID> with the value under Created Objects, ID: . You should see the object's details, including a value of text: Hello world! : ╭───────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ objectId │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ version │ 591332927 │ │ digest │ 8xJRijHHp3gNXLExTG98KX5jYAQDVKqsBD8ATFMJXCbA │ │ objType │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ owner │ ╭────────┬──────────────────────────────────────────╮ │ │ │ │ Shared │ ╭────────────────────────┬─────────────╮ │ │ │ │ │ │ │ initial_shared_version │ 591332927 │ │ │ │ │ │ │ ╰────────────────────────┴─────────────╯ │ │ │ │ ╰────────┴──────────────────────────────────────────╯ │ │ prevTx │ 6xB9Foy5vyhXG99xppaCxrNvpPTV3UZsH39zqUKNoGsD │ │ storageRebate │ 1413600 │ │ content │ ╭───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ dataType │ moveObject │ │ │ │ │ type │ 0xa7ed855d30500c485a94c0849f70b508d6b6adf6b0767ab93cc0756c075ecbb1::greeting::Greeting │ │ │ │ │ hasPublicTransfer │ false │ │ │ │ │ fields │ ╭──────┬───────────────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ id │ ╭────┬──────────────────────────────────────────────────────────────────────╮ │ │ │ │ │ │ │ │ │ │ id │ 0x2834aa3d2ed1b5060f4e5d400092544fa9c95430fd894b139b7dfb0312501594 │ │ │ │ │ │ │ │ │ │ ╰────┴──────────────────────────────────────────────────────────────────────╯ │ │ │ │ │ │ │ │ text │ Hello world! │ │ │ │ │ │ │ ╰──────┴───────────────────────────────────────────────────────────────────────────────╯ │ │ │ │ ╰───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────╯ │ ╰───────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯ Important transaction considerations You cannot send 2 or more transactions simultaneously, otherwise you encounter an error such as: Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. If you receive this error, you must wait until the current epoch is over before submitting your transaction again. You can see how long is left in the current epoch using Sui Explorer or another network explorer like SuiScan . To prevent the same object from being modified by multiple transactions at once, your address 'locks' the object to prevent conflicting modifications. If you'd like to batch multiple transaction commands together, you can use programmable transaction blocks . Transactions also have limitations regarding total size, number of objects, and number of inputs. Learn more about limitations in Building Against Limits in The Move Book. Next steps Create a Full Stack dApp Connect a frontend interface to your "Hello, World!" smart contract. Access Sui Data Learn more about accessing data on Sui. Join the Community Join the Sui developer community, try out other example projects, or read more documentation. Edit this page What is Move? Clone "Hello, World!" View the smart contract code Code explanation Resource safety Build the Move package Publish the Move package Interact with the Move package Important transaction considerations © 2026 Sui Foundation | Documentation distributed under CC BY 4.0 | 2026-01-13T08:48:38 |
https://dev.to/embernoglow/marching-cubes-algorithm-written-in-rust-473d#license | Marching Cubes algorithm written in Rust - 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 EmberNoGlow Posted on Jan 3 Marching Cubes algorithm written in Rust # rust # algorithms # opensource # programming Hello everyone 👋 I am happy to present my new AI-generated work: Marching cubes allow you to polygonize geometry created using a signed distance field! I created this for my project SDF model editor . License The code is distributed under the MIT license. For more information visit github 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 EmberNoGlow Follow Just a dude, a mid-level on Godot / Python developer and Rust beginner Joined Nov 18, 2025 More from EmberNoGlow From Zero to SDF Editor Beta: How I Used AI to Force My Dream Project Out of the Prototype Stage. What I learned? # python # sideprojects # opensource # discuss The most useless python utility for development you can make? Mem lol Pillow # python # meme # programming # learning 📜 Prototype of Voxel Terrain Generation in Godot 4 # godot # tool # opensource # gamedev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:38 |
https://blog.devcycle.com/igs-case-study/ | IGS Case Study - Using DevCycle in a Cloud-Based Microservices Architecture Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home Case Studies Featured IGS Case Study - Using DevCycle in a Cloud-Based Microservices Architecture Taraneh Dohmer Aug 9, 2024 • 3 min read About IGS Intelligent Growth Solutions (IGS) is a pioneering company in the vertical farming industry, specializing in the development of advanced vertical farming towers. Their new and innovative approaches optimize agricultural productivity by using vertical space and technology to maximize crop yield and quality. IGS initially considered using flagd but quickly encountered limitations with these options. They realized that they needed a user-friendly UI to facilitate the hand-off of feature flags to non-technical team members. This was just the first of many reasons that led them to choose DevCycle . Our Story | Intelligent Growth Solutions, Vertical Farming In 2013, IGS brought together decades of farming and engineering experience to create an agritech business with a vision to revolutionise vertical farming. Cookie Policy Team Anatomy & Tech Stack IGS has a diverse team structure encompassing various roles, including: Software Developers Data Team Product Managers Site Reliability Engineers Overall, the team size approaches 40 members. Tech Stack : DotNet-focused microservices deployed into Kubernetes Angular with TypeScript Python for Data Analytics Development Practices : The software team practices continuous deployment. The data team and other teams practice continuous delivery, meaning they have to manually deploy to production. All teams leverage Kubernetes for their deployments. Challenges Faced Before adopting DevCycle, IGS faced several significant challenges: Inefficient and Costly Testing Environments : IGS maintained seven duplicate environments of their production system, costing approximately $45,000 per month. This setup was necessary to manually test and verify code changes. Targeting and Audiences : The traditional method of feature releases was heavy, expensive, time-consuming, which created anxieties for their engineering and product teams. Risky and Inflexible Code Deployments : Without a proper feature flagging system, the team struggled to deploy changes safely and efficiently, leading to disruptions in their continuous delivery pipeline. Solution IGS chose DevCycle as their feature and release management tool because of these key features: Feature Flags : Enabled seamless and controlled release of features, allowing IGS to deploy changes without affecting all users simultaneously. This was particularly useful for their front-end team and upcoming back-end migrations. Advanced Targeting & Rollouts: DevCycle's advanced targeting, audiences and rollouts allowed IGS to segment and target their users more effectively, leading to improved personalization and customization of experiences. Self-Targeting and Audiences : The ability to use account IDs instead of personal email addresses for targeting added an extra layer of flexibility and compliance with privacy standards. Simplified Testing Environments and Reduced Financial Costs : By implementing DevCycle, IGS could eliminate the need for multiple manual environments, reducing their costs from $45,000 down to $4,000 per month. Implementation Process IGS was migrating off of an in-house solution, making the switch to DevCycle a simple one. The migration involved: Evaluating Alternatives : IGS evaluated other market solutions and found DevCycle to be the most suitable, thanks to its team-friendly pricing that allows unlimited seats, enabling all of their developers to create flags. Implementation : The transition from in-house to DevCycle was straightforward, with DevCycle integrating well into their existing Kubernetes-based microservices architecture. Adoption : The platform team spearheaded the adoption of feature flags, gradually shifting the mindset of the engineering teams towards leveraging this tool for better deployment practices. Outcomes and Benefits Cost Reduction : IGS saw over $40,000 in savings after using DevCycle to reduce the number of environments. Enhanced Productivity : Engineers now focus more on development rather than managing complex testing environments. Improved Release Confidence : Product managers and engineers gained confidence in releasing features without the fear of impacting the entire system. The ability to control feature visibility provided a safety net for incremental and safe rollouts. Increased Flexibility : The front-end and back-end teams could now implement and test changes more efficiently, fostering a culture of continuous improvement and rapid iteration. Future Plans The migration and implementation have been so successful that IGS plans to expand the use of feature flags to more back-end processes, further optimizing their deployment strategies and enhancing their product offerings. Conclusion IGS’s adoption of DevCycle has transformed their development and deployment processes, leading to significant financial savings, improved productivity, and greater confidence in their feature release cycles. The successful integration of DevCycle demonstrates its value in supporting innovative technology companies like IGS, enabling them to focus on their core mission while maintaining robust and flexible dev practices. Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:38 |
https://blog.devcycle.com/openfeature-hackathon-2024/ | OpenFeature Hackathon 2024 Blog Home OpenFeature Guides and Tutorials Product Updates Case Studies DevCycle Home OpenFeature OpenFeature Hackathon 2024 Jonathan Norris Mar 19, 2025 • 9 min read A few times a year at DevCycle, we hit pause on our usual work, push aside our roadmaps, and dive into a few days of rapid experimentation and collaboration. For our first hackathon of 2025, we opted for an OpenFeature theme —a chance to explore new ideas, test bold concepts, and build something innovative for the OpenFeature ecosystem together. This year, teams tackled projects ranging from OpenFeature CLI improvements to using OpenFeature Remote Evaluation Protocol with CloudFlare Workers. Why Did We Focus on OpenFeature? This year’s hackathon wasn’t just about innovation—it was about deepening our commitment to the OpenFeature ecosystem. DevCycle’s Co-founder and CTO, Jonathan Norris, is an active member of the OpenFeature Governance Committee , a milestone that underscores our dedication to open standards in feature flagging. “At DevCycle we believe strongly that building upon open standards democratizes software development and improves the experience for end customers. We will continue to be strong advocates for the OpenFeature community and support its development as it matures into the industry standard for feature flagging.” DevCycle includes OpenFeature SDK support across its platform by default , reinforcing our position as a leader in vendor-neutral feature flagging solutions. Our commitment to OpenFeature is about more than just compliance—it’s about creating a future where developers have flexibility, interoperability, and control over their feature flagging strategies. With this in mind, our hackathon focused on pushing OpenFeature forward—enhancing tooling, expanding SDK support, and building features that strengthen the ecosystem. Our Team’s Hackathon Projects Demos! Let’s take a closer look at how our team hacked, what we learned, and why these projects matter. OpenFeature Remote Evaluation Protocol with Cloudflare Workers At DevCycle, we were early supporters of the OpenFeature Remote Evaluation Protocol (OFREP) and long-time users of Cloudflare Workers . Naturally, we were curious if we could use the OFREP API as a bridge interface to better support feature flags in these edge environments. As one of our hackathon projects, Elliot from our team built a DevCycle OFREP Worker , which we could publish for customers to run in their own environment. This worker can use a service binding to bind this worker to any of their own internal workers. This implementation provides a Cloudflare Worker template that synchronizes and caches DevCycle flags configuration within your Cloudflare environment. The worker fetches the flag configuration from the DevCycle’s CDN once, which is served by Cloudflare’s CDN / R2, and then processes the project configuration locally to evaluate flags for individual users. This means that feature flags can be accessed almost instantaneously within any Worker in your environment, eliminating processing delays and reducing external API calls. Then, in your internal worker, you can use the existing OpenFeature SDKs with the OFREP Provider to bind the fetch call to the DevCycle OFREP Worker: import { OpenFeature } from '@openfeature/server-sdk' import { OFREPProvider } from '@openfeature/ofrep-provider' const provider = new OFREPProvider({ baseUrl: 'https://ofrep-bucketing-worker.devcycle.com', fetchImplementation: (input: RequestInfo | URL, init?: RequestInit) => env.OFREP_BUCKETING.fetch(input, init), headers: [ ['Content-Type', 'application/json'], ] }) await OpenFeature.setProviderAndWait(provider); const client = OpenFeature.getClient(); Integrating OFREP with Cloudflare Workers offers a scalable and high-performance solution for feature flag evaluation at the edge built on open standards. This was a great demo during our Hackathon; there is still some work to do to productize this OFREP worker; reach out to us if you think this is an interesting use case for OFREP as we continue to work on it. GitHub - DevCycleHQ-Sandbox/OFREP-bucketing-worker Contribute to DevCycleHQ-Sandbox/OFREP-bucketing-worker development by creating an account on GitHub. GitHub DevCycleHQ-Sandbox OpenFeature CLI Contribution Strongly typed feature flags are essential for teams managing feature flags at scale across large codebases. DevCycle has long supported the dvc generate types command in our CLI, which generates Typescript Types for our DevCycle SDKs. When we heard about the development progress of the OpenFeature CLI in generating types for OpenFeature SDKs, we were eager to contribute to its development. While the OpenFeature CLI is in its early development, type generation for Go and React is already functional. However, there was no built-in way for vendors to integrate their platforms with the CLI’s type generation feature. The openfeature generate react command runs by generating a typed interface for your OpenFeature SDK from a known list of flags from a standard flags manifest file. To support this standard as a vendor, the CLI would need a way to pull and sync the flag manifest file directly from a vendor’s platform. Jason from DevCycle stepped in and created an openfeature pull method to pull flag data from DevCycle's API and generate a manifest file for the CLI to use. > openfeature pull > openfeature generate react This will result in an openfeature.ts file with populated variable hooks: 'use client'; import { type ReactFlagEvaluationOptions, type ReactFlagEvaluationNoSuspenseOptions, type FlagQuery, useFlag, useSuspenseFlag, } from "@openfeature/react-sdk"; /** * * * **Details:** * - flag key: `a-newer-feature` * - default value: `false` * - type: `boolean` */ export const useANewerFeature = (options?: ReactFlagEvaluationOptions): FlagQuery<boolean> => { return useFlag("a-newer-feature", false, options); }; /** * * * **Details:** * - flag key: `a-newer-feature` * - default value: `false` * - type: `boolean` * * Equivalent to useFlag with options: `{ suspend: true }` * @experimental — Suspense is an experimental feature subject to change in future versions. */ export const useSuspenseANewerFeature = (options?: ReactFlagEvaluationNoSuspenseOptions): FlagQuery<boolean> => { return useSuspenseFlag("a-newer-feature", false, options); }; ... We are excited to keep working on the CLI with the folks from Dynatrace, Google Cloud, and others leading this effort. feat: `openfeature pull` command by jsalaber · Pull Request #79 · open-feature/cli Summary init command creates a .openfeature.yaml to store flagSourceUrl using the --flag-source-url adds a new pull command that fetches a flag configuration from a flagSourceUrl configured in the… GitHub open-feature Codemod: Convert Codebase from Vendor SDK to OpenFeature SDK Building a Codemod for OpenFeature migrations has been on our radar for a while. After connecting with the Codemod team, we saw its potential for helping customers migrate from vendor SDKs to OpenFeature SDKs. Codemod has gained great adoption among teams upgrading to the latest versions of React or officially supported upgrade paths - such as the transition from Nuxt 3 to Nuxt 4 (Nuxt 3 → 4) . This hackathon finally gave us the chance to experiment with Codemod’s tooling and publish a codemod. Think of the codemod platform as tooling around open-source code transformation tools like jscodeshift , while adding AI-powered tooling for generating codemods, plus an NPM-like repository for distributing them. Our first set of codemods focused on helping teams transition their codebases from DevCycle or Launchdarkly Node.js SDKs to using the OpenFeature SDK, using the respective vendor’s OpenFeature Provider. To do this, we discovered it best to break down the problem into smaller, testable steps and then run all the codemods together in a workflow: Update Imports CodeMod - transforms file and packages imports to use OpenFeature + Provider. Initialization Transform - transforms the SDK initialization from using initializeDevCycle() to setting up the DevCycleProvider and creating the OpenFeature Client User Context Transform - updates DevCycleUser to EvaluationContext objects, rename user_id param to targetingKey Variable Transform - replaces DevCycle variableValue() and variable() calls with get<Type>Value() and get<Type>Details() calls to OpenFeature After installing codemod: npm i -g codemod , these can be run using: codemod devcycle-to-openfeature-nodejs-workflow The codemod CLI will download the latest version of the codemods and run them against your codebase. These codemods are a great starting point for anyone looking to do much of the heavy lifting, updating a codebase from DevCycle or Launchdarkly Node.js SDKs to OpenFeature. We are interested in feedback from the community about the value of these codemods and if we should continue developing them for more languages/vendors, as well as if these codemods would make sense as an OpenFeature-supported project. GitHub - DevCycleHQ-Sandbox/OpenFeature-Codemod Contribute to DevCycleHQ-Sandbox/OpenFeature-Codemod development by creating an account on GitHub. GitHub DevCycleHQ-Sandbox Docusaurus OpenFeature Wrapper Docusaurus is a popular framework for building documentation websites, making it easy to create and maintain interactive docs using Markdown and React. Since both DevCycle and OpenFeature rely on Docusaurus for their documentation, integrating feature flagging directly into the platform makes perfect sense. With this approach, documentation can dynamically update based on feature flags, allowing teams to release code and docs together—an essential capability for feature-driven development. For the OpenFeature Hackathon, one of our engineers, Parth, built an OpenFeature Docusaurus plugin, leveraging the OpenFeature React SDK and flagd to enable feature management within documentation sites. He created a Docusaurus provider and applied it to a barebones Docusaurus site to showcase its functionality. The plugin allows developers to use feature flags to dynamically toggle sections of documentation, ensuring content remains in sync with evolving product features. By integrating OpenFeature, this project bridges the gap between documentation and feature flagging, improving flexibility, maintainability, and release coordination for teams using Docusaurus. GitHub - DevCycleHQ-Sandbox/docusaurus-openfeature-provider: OpenFeature provider to integrate into docusaurus OpenFeature provider to integrate into docusaurus - GitHub - DevCycleHQ-Sandbox/docusaurus-openfeature-provider: OpenFeature provider to integrate into docusaurus GitHub DevCycleHQ-Sandbox DevCycle Provider Updates for Go, .NET & Ruby DevCycle has been supporting OpenFeature for several years, and as part of this hackathon, Jamie took the time to review our OpenFeature providers across our SDKs to ensure they were up-to-date with the latest OpenFeature SDK features. This included adding event tracking support and handling initialization/close when applicable. We also worked on building and publishing our much-requested DevCycle OpenFeature Ruby Provider . Our goal is to provide OpenFeature support across all DevCycle SDKs, with only Next.js, iOS, Android, React Native, Flutter, and Roku remaining for full coverage. Ruby OpenFeature Provider | DevCycle Docs How to implement the OpenFeature Provider DevCycle Logo Dogfooding OpenFeature SDK Nest.js SDK and Providers In the spirit of dogfooding OpenFeature and our own Providers, Kaushal from our team took up the task of updating the usage of DevCycle's Nest.js SDK in our main API service to use the OpenFeature Nest.js SDK with DevCycle's Nest.js Provider . To accomplish this, we introduced a wrapper service that used a single instance of the OpenFeature Client, making it accessible across our Nest.js service. This straightforward migration allowed the OpenFeature Client to replace any existing calls to DevCycle's SDK. One of the key takeaways from this project was realizing how much our API development relied on Nest.js decorators, which simplified our feature flagging of API endpoints: @RequireFlagsEnabled(["flag1", "flag2"], ForbiddenException) This would check if the targeting context evaluated multiple Boolean values to true for all the flags passed in else return the exception (default exception of NotFound ) @RequireFlagValues({ "flag1": "apples", "flag2": true }, ForbiddenException) This would check if the targeting context matched multiple flags to the corresponding values to true for all the flags passed in, else return the exception (default exception of NotFound ) We started a PR here to enhance the Nest.js SDK with these decorators. We also lean heavily on the mock interfaces provided by the DevCycle Nest.js SDK to mock and set flag values, which allows us to test different branching code paths in our API service. Adding similar mocking capabilities would be a useful addition to make testing all the OpenFeature SDKs easier. Dogfooding the OpenFeature SDKs and our own providers was a valuable learning experience, sparking new ideas on how to contribute to and improve these SDKs in the future. feat: adds RequireFlagsEnabled decorator by kaushalkapasi · Pull Request #1159 · open-feature/js-sdk This PR Feature: Adds a RequireFlagsEnabled decorator to allow a simple, reusable way to block access to a specific controller or endpoint based on the value of a list of one, or many, boolean fla… GitHub open-feature Projects that Didn't Make the Cut This Time Around Evaluation Reasons for SDKs – Enhancing our SDKs with evaluation reasons, bringing us closer to full OpenFeature spec compliance. Feature Flag Observability – Improving insights into how feature flags impact performance and decision-making. Add Tracking support to more SDKs - OpenFeature SDK Tracking Support Multi-Provider Expansion – Bringing multi-provider support to more languages. And many more! Each project aimed to strengthen the OpenFeature ecosystem and provide better tools for developers. Let us know what projects you found the most interesting and we should continue developing further, please reach out to us in the CNCF #openfeature Slack or our Discord . Why a Homegrown Feature Flag System is a Trap Feature flags empower teams to ship code safely, experiment quickly, and decouple deploys from releases. At first glance, building your own feature flag system seems like a quick win: a few conditionals in your code, a simple database table, and you’re off to the races. But reality sets in Dec 10, 2025 4 min read Who Knew Feature Flags Would Save AI Coding From "good enough" to production‑ready, fast When a new component glows in your IDE, and your AI assistant says, "Ready for deployment." What do you do? You could launch it wide, hit the big green button, and pray for no fires. But you don' Dec 10, 2025 3 min read Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit When I first stepped into an engineering manager role, I quickly learned that moving fast without losing control is one of the hardest balances to strike. Feature flags helped me make that balance real. Here’s how, and why, you should treat feature flags not as a “nice-to-have,” but a Dec 9, 2025 3 min read DevCycle Blog © 2026 Powered by Ghost | 2026-01-13T08:48:38 |
https://legal.x.com/sl/purchaser-terms.html | Pogoji storitve za kupce za X Pogoji storitve za kupce za X Prenesite pogoje storitve za kupce za X Pogoji za plačljive storitve Dodatni pogoji za X Premium Dodatni pogoji za naročnine Prenesite pogoje storitve za kupce za X Pogoji storitve za kupce za X goglobalwithtwitterbanner Pogoji za plačljive storitve Dodatni pogoji za X Premium Dodatni pogoji za naročnine ustvarjalcev Dodatni pogoji za Premium Business in Premium organizacije Pogoji za plačljive storitve Dodatni pogoji za X Premium Dodatni pogoji za naročnine ustvarjalcev Dodatni pogoji za Premium Business in Premium organizacije Pogoji storitve za kupce za X Začetek veljavnosti: 1. avgust 2025 Če živite zunaj Evropske unije, držav Efte ali Združenega kraljestva, vključno s tem, če živite v Združenih državah Amerike, za vas veljajo naslednji pogoji storitve za kupce za X . Če živite v Evropski uniji, državah Efte ali Združenem kraljestvu, za vas veljajo ti pogoji storitve za kupce za X . Pogoji storitve za kupce za X Če živite zunaj Evropske unije, držav Efte ali Združenega kraljestva, vključno s tem, če živite v Združenih državah Družba X omogoča dostop do določenih funkcij v zameno za enkratno ali večkratno plačilo glede na zadevno funkcijo (posamezno » plačljiva storitev « in skupno » plačljive storitve «). Na primer X Premium (kot je opredeljeno spodaj) in naročnine bi se vsaka obravnavala kot »plačljiva storitev«. V obsegu, v katerem se registrirate za plačljivo storitev in/ali jo uporabljate, morajo biti vaša uporaba plačljivih storitev in kakršne koli pripadajoče transakcije v skladu s: (i) tukaj določenimi pogoji in določili, vključno z veljavnimi pogoji in določili za vsako plačljivo storitev, ki jo kupite in kot je navedena spodaj (skupaj » pogoji storitve za kupce za X «), ter (ii) veljavnimi pogoji storitve za X , pravilnikom o zasebnosti za X , pravili in pravilniki za X ter vsemi pravilniki, vključenimi v te dokumente (skupaj » uporabniška pogodba za X «). Ti pogoji storitve za kupce za X in prej omenjena uporabniška pogodba za X so v tem dokumentu skupaj imenovani » pogoji «. » X « se nanaša na subjekt X, ki vam zagotavlja plačljive storitve. Pozorno preberite te pogoje storitve za kupce za X in poskrbite, da razumete veljavne pogoje, določila in izjeme. ČE ŽIVITE V ZDRUŽENIH DRŽAVAH AMERIKE, TI POGOJI VSEBUJEJO POMEMBNE INFORMACIJE, KI VELJAJO ZA VAS GLEDE REŠEVANJA SPOROV, VKLJUČNO Z VAŠO ODPOVEDJO PRAVICI DO VLOŽITVE ZAHTEVKOV KOT SKUPINSKIH TOŽB TER OMEJITVIJO PRAVICE DO VLOŽITVE ZAHTEVKOV PROTI DRUŽBI X VEČ KOT 2 LETI PO ZADEVNIH DOGODKIH, KAR VPLIVA NA VAŠE PRAVICE IN OBVEZNOSTI, ČE PRIDE DO KAKRŠNEGA KOLI SPORA Z DRUŽBO X. ZA PODROBNOSTI O TEH DOLOČBAH PREBERITE 6. RAZDELEK POD SPLOŠNIMI POGOJI. Sprejemanje . Z uporabo ali dostopom do plačljivih storitev družbe X, iz tega izhajajočo izvedbo plačila in/ali klikom gumba za enkratni nakup ali redna plačila naročnine za plačljive storitve, ki jih zagotavlja družba X, se strinjate, da vas zavezujejo ti pogoji. Če pogojev ne razumete pogojev ali katerega koli dela ne sprejemate, ne smete uporabljati nobenih plačljivih storitev ali dostopati do njih. Za nakup in uporabo plačljive storitve morate: (i) imeti vsaj 18 let ali biti polnoletni, kot določa pristojna zakonodaja v vašem kraju bivanja, ali (ii) imeti izrecno soglasje staršev ali skrbnika za nakup in uporabo zadevne plačljive storitve. Če ste starš ali zakoniti skrbnik in svojemu otroku (ali otroku, katerega skrbnik ste) dovolite nakup ali uporabo plačljive storitve, se strinjate, da ti pogoji veljajo za vas, da jih boste upoštevali ter da ste odgovorni za otrokovo dejavnost v plačljivih storitvah in za zagotavljanje, da vaš otrok tudi upošteva te pogoje. V vsakem primeru morate biti stari vsaj 13 let za uporabo storitve X, kot je navedeno v razdelku »Kdo lahko uporablja storitve« v pogojih storitve X. Če te pogoje storitve za kupce X sprejemate in plačljive storitve uporabljate v imenu podjetja, organizacije, vlade ali druge pravne osebe, izjavljate in jamčite, da ste za to pooblaščeni in imate pooblastilo, da tak subjekt zavežete k tem pogojem storitve za kupce X, pri čemer se v tem primeru besedi »vi« in »vaš«, kot sta uporabljeni v teh pogojih storitve za kupce X, nanašata na ta subjekt. Pogodbeni subjekt družbe X . Te pogoje storitve za kupca X sklenete s subjektom, ki ustreza vašemu prebivališču, kot je navedeno spodaj. Ta subjekt vam bo zagotovil plačljive storitve. Noben drug subjekt ni vezan na nobene obveznosti do vas v skladu s temi pogoji storitve za kupce. Vaša lokacija Celina Severna Amerika (vključno s Havaji) ali Južna Amerika Pogodbeni subjekt X Corp., s sedežem na naslovu 865 FM 1209, Building 2, Bastrop, TX 78602, USA Vaša lokacija Vse države, ki niso zajete v zgornjih dveh lokacijah, vključno z azijsko-pacifiško regijo, Bližnjim vzhodom, Afriko ali Evropo (razen držav EU, držav Efte in Združenega kraljestva) Pogodbeni subjekt X Global LLC, s sedežem na naslovu 701 S. Carson St., Suite 200, Carson City, NV 89701, ZDA Spremembe pogojev, plačljivih storitev in cen 1. Spremembe pogojev. X lahko občasno spremeni te pogoje storitve za kupca X, vključno s poslovnimi, finančnimi ali pravnimi razlogi. Spremembe ne veljajo retroaktivno, najnovejša različica pogojev storitve za kupce X, na voljo na spletnem mestu legal.x.com/purchaser-terms , bo določala vašo uporabo plačljivih storitev in kakršnih koli zadevnih transakcij. Če spremenimo ali popravimo te pogoje zatem, ko ste se z njimi že strinjali (če so ti pogoji na primer spremenjeni zatem, ko ste kupili naročnino), vas bomo vnaprej obvestili o pomembnih spremembah vsebine teh pogojev. Takšno obvestilo lahko posredujemo v elektronski obliki, kar (med drugim) vključuje obveščanje prek obvestila v storitvi ali e-pošte, poslane na e-poštni naslov, povezan z vašim računom. Z nadaljnjim dostopom do plačljivih storitev ali njihovo uporabo zatem, ko spremembe začnejo veljati, se strinjate, da vas zavezujejo spremenjeni pogoji storitve za kupce X. Če se ne strinjate z upoštevanjem teh ali katerih koli prihodnjih pogojev storitve za kupce X, ne uporabljajte plačljivih storitev ali dostopajte do njih (ali jih ne uporabljajte še naprej ali dostopajte do njih). Pogoji storitve za kupce X so napisani v angleščini, vendar so s prevodi na voljo v več jezikih. Družba X si prizadeva, da bi prevodi čim bolj točno odražali izvirno angleško različico. Vendar ima v primeru odstopanj ali nedoslednosti prednost angleška različica pogojev storitve za kupce X. Potrjujete, da bo angleščina referenčni jezik za razlaganje in sestavljanje pogojev v pogojih storitve za kupce X. 2. Spremembe plačljivih storitev. Naše plačljive storitve se nenehno razvijajo. Plačljive storitve se lahko občasno spremenijo po naši presoji, vključno s poslovnimi, finančnimi ali pravnimi razlogi. Vam ali uporabnikom na splošno lahko prenehamo (trajno ali začasno) zagotavljati plačljive storitve ali katere koli funkcije v okviru plačljivih storitev s predhodnim obvestilom ali brez njega. Družba X ne prevzema odgovornosti do vas ali katere koli tretje osebe za kakršno koli spremembo, začasno prekinitev ali ukinitev plačljivih storitev. Posamezni pogoji in določila (vključeni spodaj) za posamezno plačljivo storitev določajo, kako lahko prekličete naročnino ali, kadar je ustrezno, zahtevate vračilo kupnine. 3. Spremembe cen. Cene plačljivih storitev, vključno s ponavljajočimi se naročninami, se lahko občasno spremenijo, vključno s poslovnimi, finančnimi ali pravnimi razlogi. Družba X vas bo v razumnem času predhodno obvestila o kakršni koli pomembni spremembi cen plačljivih storitev. Za naročniške storitve bodo spremembe cen začele veljati ob začetku naslednjega naročniškega obdobja po datumu spremembe cene. Če se ne strinjate s spremembo cene, imate pravico zavrniti spremembo tako, da prekličete naročnino na zadevno plačljivo storitev, preden sprememba cene začne veljati. Plačilni pogoji . X ponuja različne možnosti plačila, ki se lahko razlikujejo glede na plačljivo storitev, vašo napravo in/ali operacijski sistem, vašo geografsko lokacijo ali druge dejavnike. Ti načini plačila lahko do mere, ki je na voljo (saj lahko družba X občasno omogoči različne načine nakupa), vključujejo uporabo funkcije za plačilo v aplikaciji, ki jo ponuja družba Google ali Apple, ali izvedbo spletnega plačila z uporabo storitve Stripe ( www.stripe.com – v nadaljnjem besedilu » Stripe «), neodvisnega ponudnika obdelave plačil družbe X. Ko plačilo izvedete, se izrecno strinjate, (i) da boste plačali ceno, navedeno za plačljivo storitev, skupaj z vsemi dodatnimi zneski v zvezi z veljavnimi davki, provizijami za kreditne kartice, bančnimi provizijami, stroški za transakcije v tujino, stroški menjalnega tečaja in nihanji valut; ter (ii) da boste upoštevali vse ustrezne pogoje storitve, pravilnike o zasebnosti ali druge pravne pogodbe ali omejitve (vključno z dodatnimi starostnimi omejitvami), ki jih uvedejo družba Google, Apple ali Stripe (neodvisni ponudnik obdelave plačil družbe X) v zvezi z vašo uporabo določenega načina plačila (če se na primer odločite samo za plačilo prek Applove funkcije za nakup v aplikaciji, se strinjate, da boste spoštovali vse ustrezne pogoje, zahteve in/ali omejitve, ki jih uvede družba Apple). Vsi zasebni osebni podatki, ki jih posredujete v zvezi z uporabo plačljivih storitev, kar med drugim vključuje kakršne koli podatke, posredovane v zvezi s plačilom, se obdelujejo skladno s pravilnikom o zasebnosti X. Družba X lahko vaše podatke o plačilu deli s ponudniki plačilnih storitev za obdelavo plačil; preprečevanje, odkrivanje in raziskovanje goljufij ali drugih prepovedanih dejavnosti; omogočanje reševanja sporov, na primer z vračilom plačil ali kupnine; in za druge namene, povezane s sprejemanjem kreditnih in debetnih kartic ali transakcij ACH. Odgovorni ste zagotoviti, da so vaši bančni podatki, podatki o kreditni kartici, debetni kartici in/ali drugi podatki o plačilu ves čas aktualni, popolni in točni. Če izvedete plačilo za plačljivo storitev, lahko prejmemo podatke o vaši transakciji, na primer, kdaj je bila opravljena, kdaj bo naročnina potekla ali se samodejno podaljšala, na kateri platformi ste opravili nakup in druge informacije. Družba X ni i pristojna in ne prevzema odgovornosti za morebitne napake ali zamude, ki jih povzroči ponudnik obdelave plačil, Applova storitev App Store ali Googlova storitev Play Store, vaša banka, izdajatelj vaše kreditne kartice in/ali katero koli plačilno omrežje. Za plačilne pogoje, ki veljajo za posamezno plačljivo storitev, vključno s tem, kako poteka obnovitev naročnine, in drugimi pomembnimi pogoji, si oglejte spodnje pogoje in določila za posamezno plačljivo storitev. Uporaba uporabniške pogodbe C, odpoved pogodbe, nevračilo, več računov X in omejitve 1. Uporabniška pogodba za X velja za vas . UPORABNIŠKO POGODBO X MORATE VEDNO UPOŠTEVATI IN RAVNATI V SKLADU Z NJO. Uporabniška pogodba X vedno velja za vašo uporabo storitve X, vključno s plačljivimi storitvami in funkcijami. Vaše neupoštevanje uporabniške pogodbe X in neskladno ravnanje z njo ali prepričanje družbe X, da uporabniške pogodbe X niste upoštevali in niste ravnali skladno z njo, lahko vodi do preklica plačljivih storitev. Kakršen koli preklic bo sledil, vključno s katerim koli izvršilnim ukrepom, ki ga družba X lahko izvede proti vam v skladu z uporabniško pogodbo X, vendar ne omejeno nanj. V takih primerih lahko izgubite ugodnosti plačljivih storitev in ne boste upravičeni do vračila kupnine, ki ste jo plačali (ali predhodno plačali) za plačljive storitve. 2. Razlogi, zakaj družba X lahko ukine dostop do plačljivih storitev. Družba X lahko začasno prekine ali ukine dostop do plačljivih storitev ali preneha delno ali v celoti zagotavljati plačljive storitve ali sprejme kakršen koli drug ukrep, ki se ji zdi primeren, vključno z začasno prekinitvijo dostopa do računa, (brez kakršne koli odgovornosti) kadar koli in iz katerega koli razloga ali brez njega, kar med drugim vključuje katerega koli od naslednjih razlogov: a. Družba X je po lastni presoji prepričana, da ste kršili pogoje ali da bi vaša uporaba plačljivih storitev kršila katero koli veljavno zakonodajo. b. Od družbe X to zahteva ali ji to naroči katero koli pristojno sodišče, regulativni organ ali organ kazenskega pregona; c. Družba X ima nepričakovane tehnične ali varnostne težave; d. Družba X po lastni presoji meni, da ste kršili uporabniško pogodbo za X; e. X po lastni presoji verjame, da ste vpleteni v manipulacijo ali drugo moteče ali prepovedano ravnanje na splošno ali v povezavi s plačljivimi storitvami; f. Ustvarjate tveganje ali morebitno pravno izpostavljenost za X; g. Vaš račun je treba odstraniti zaradi nezakonitega ravnanja; h. Vaš račun je treba odstraniti zaradi daljše nedejavnosti ali i. Naše zagotavljanje plačljivih storitev (v celoti ali delno) za vas ni več komercialno izvedljivo (po lastni presoji X). 3. Vse transakcije so končne. Vsa plačila za plačljive storitve so končna in jih ni mogoče povrniti ali zamenjati, razen če to zahteva veljavna zakonodaja. Ne jamčimo za naravo, kakovost ali vrednost plačljive storitve ali njeno razpoložljivost ali dobavo. Za neuporabljene ali delno uporabljene plačljive storitve (na primer delno uporabljeno naročniško obdobje) niso zagotovljena vračila kupnine ali dobropisi. 4. Plačljive storitve niso prenosljive med računi X. Vsak nakup plačljive storitve velja za en račun X, kar pomeni, da bo vaš nakup veljal samo za račun, ki ste ga uporabljali, ko ste kupili plačljivo storitev, in ne bo veljal za druge račune, do katerih imate morda dostop ali jih nadzorujete. Če imate ali nadzorujete več računov in želite imeti dostop do plačljivih storitev na vsakem računu, morate plačljivo storitev kupiti za vsak račun posebej. 5. Omejitve in obveznosti. a. Plačljivo storitev lahko kupite in uporabljate samo, če vam je zakonsko dovoljeno uporabljati plačljivo storitev v vaši državi in živite v državi, v kateri družba X podpira zadevno plačljivo storitev. Družba X lahko po lastni presoji v določenih državah omeji možnost dostopa do plačljive storitve ali njenega nakupa. Družba X si pridržuje pravico, da občasno spremeni seznam podprtih držav. b. Pridržujemo si pravico, da po lastni presoji zavrnemo transakcije plačljivih storitev ali prekličemo ali ukinemo prodajo ali uporabo plačljive storitve. c. Drugim ne smete dovoliti, da uporabljajo vaš račun X za dostop do katere koli plačljive storitve, ki je ta oseba ni naročila. d. Plačljive storitve ne smete kupiti ali uporabljati, če ste oseba, s katero osebam iz ZDA ni dovoljeno poslovati na podlagi gospodarskih sankcij, kar med drugim vključuje sankcije, ki jih uvaja Urad za nadzor tujega premoženja (ang. Office of Foreign Assets Control) pri Ministrstvu za finance ZDA ali kateri koli drug veljavni organ za sankcije (» prepovedana oseba «). To med drugim vključuje osebe, ki imajo prebivališče v naslednjih državah in regijah ali običajno prebivajo v njih: Kuba, Iran, regija Krim v Ukrajini, Severna Koreja in Sirija. Izjavljate in jamčite, da niste prepovedana oseba. e. IZJAVLJATE, DA BOSTE PLAČLJIVE STORITVE UPORABLJALI SAMO V ZAKONITE NAMENE IN SAMO V SKLADU S TEMI POGOJI. Davki in pristojbine . Odgovorni ste in se strinjate, da boste plačali vse veljavne davke, dajatve, tarife in pristojbine, povezane z nakupom plačljivih storitev, vključno s tistimi, ki jih je treba plačati X ali tretjemu plačilnemu procesorju. Ti davki lahko med drugim vključujejo DDV, davek na blago in storitve (GST), prometni davek, davčni odtegljaj in vse druge veljavne davke. Odvisno od vaše lokacije je družba X lahko odgovorna za zbiranje in poročanje podatkov v zvezi z davki na transakcije, ki izhajajo iz nakupa plačljivih storitev. Družbi X podeljujete dovoljenje, da ustreznim davčnim organom posreduje vaš račun in osebne podatke za izpolnjevanje obveznosti pobiranja davkov in poročanja. Splošni pogoji 1. Podatki za stik. Če imate kakršna koli vprašanja o plačljivih storitvah ali teh pogojih, si lahko ogledate središče za pomoč pri plačljivih storitvah družbe X za več podrobnosti. Če ste že kupili plačljivo storitev, nas lahko kontaktirate tudi prek povezave za podporo, ki je na voljo v meniju za krmarjenje vašega računa X pod nastavitvami plačila ali naročnine. Če imate dodatna vprašanja, lahko stopite v stik z nami tukaj z uporabo obrazca »Help with paid features« (Pomoč pri plačljivih funkcijah). 2. ZAVRNITEV ODGOVORNOSTI. DO PLAČLJIVIH STORITEV DOSTOPATE V NAJVEČJI MERI, KI JO DOVOLJUJE VELJAVNA ZAKONODAJA, IN JIH UPORABLJATE NA LASTNO ODGOVORNOST. RAZUMETE IN SE STRINJATE, DA SO VAM PLAČLJIVE STORITVE ZAGOTOVLJENE PO NAČELIH »KOT JE« IN »KOT JE NA VOLJO«. DRUŽBA X ZAVRAČA KAKRŠNA KOLI JAMSTVA IN POGOJE, IZRECNE ALI IMPLICITNE, GLEDE PRODAJNOSTI, PRIMERNOSTI ZA DOLOČEN NAMEN ALI NEKRŠITVE PRAVIC INTELEKTUALNE LASTNINE. DRUŽBA X NE PODAJA NOBENEGA JAMSTVA ALI ZAGOTOVILA TER NE PREVZEMA NOBENE ODGOVORNOSTI ZA: (I) POPOLNOST, TOČNOST, RAZPOLOŽLJIVOST, PRAVOČASNOST, VARNOST ALI ZANESLJIVOST PLAČLJIVIH STORITEV; IN ZA TO, (II) DA BODO PLAČLJIVE STORITVE IZPOLNJEVALE VAŠE ZAHTEVE ALI BODO NA VOLJO NEPREKINJENO, VARNO ALI BREZ NAPAK. PREVZEMATE ODGOVORNOST ZA SVOJO UPORABO STORITVE X, VKLJUČNO S PLAČLJIVIMI STORITVAMI IN VSO VSEBINO, KI JO POSREDUJETE. 3. OMEJITEV ODGOVORNOSTI. V NAJVEČJI MERI, KI JO DOVOLJUJE VELJAVNA ZAKONODAJA, SUBJEKTI DRUŽBE X NISO ODGOVORNI ZA KAKRŠNO KOLI POSREDNO, NAKLJUČNO, POSEBNO, POSLEDIČNO ALI KAZENSKO ŠKODO ALI KAKRŠNO KOLI IZGUBO DOBIČKA ALI PRIHODKOV, NASTALO BODISI NEPOSREDNO BODISI POSREDNO, ALI KAKRŠNO KOLI IZGUBO PODATKOV, UPORABE, DOBREGA IMENA ALI DRUGO NEPREMOŽENJSKO ŠKODO, KI SO POSLEDICA (i) VAŠEGA DOSTOPA DO PLAČLJIVIH STORITEV ALI NJIHOVE UPORABE ALI NEZMOŽNOSTI DOSTOPA DO PLAČLJIVIH STORITEV ALI NJIHOVE UPORABE; (ii) KAKRŠNEGA KOLI RAVNANJA KATERE KOLI TRETJE OSEBE ALI NJENE VSEBINE, OBJAVLJENE PREK PLAČLJIVIH STORITEV, KAR MED DRUGIM VKLJUČUJE VSAKRŠNO OBREKLJIVO, ŽALJIVO ALI NEZAKONITO RAVNANJE DRUGIH UPORABNIKOV ALI TRETJIH OSEB; (iii) KAKRŠNE KOLI VSEBINE, PRIDOBLJENE IZ PLAČLJIVIH STORITEV; ALI (iv) NEPOOBLAŠČENEGA DOSTOPA, UPORABE ALI SPREMEMBE VAŠIH PRENOSOV ALI VSEBINE. V IZOGIB DVOMOM JE OPREDELITEV PLAČLJIVIH STORITEV OMEJENA NA FUNKCIJE, KI JIH PONUJA DRUŽBA X, IN NE VKLJUČUJE NOBENIH VSEBIN, DO KATERIH DOSTOPATE IN/ALI S KATERIMI IMATE INTERAKCIJE MED UPORABO TEH FUNKCIJ. V NOBENEM PRIMERU SKUPNA ODGOVORNOST SUBJEKTOV DRUŽBE X NE PRESEGA STO AMERIŠKIH DOLARJEV (100,00 USD) ALI MOREBITNEGA ZNESKA, KI STE NAM GA PLAČALI V ZADNJIH ŠESTIH MESECIH V SKLADU S TEMI POGOJI PRED DOGODKOM ZA STORITVE, KI SO PODLAGA ZA ZAHTEVEK. OMEJITVE IZ TEGA PODRAZDELKA VELJAJO ZA VSE TEORIJE ODGOVORNOSTI, NE GLEDE NA TO, ALI TEMELJIJO NA GARANCIJI, POGODBI, STATUTU, ŠKODNEM DEJANJU (VKLJUČNO Z MALOMARNOSTJO) ALI DRUGEM IN NE GLEDE NA TO, ALI SO BILI SUBJEKTI DRUŽBE X OBVEŠČENI O MOŽNOSTI TAKE ŠKODE IN TUDI ČE SE UGOTOVI, DA TUKAJ NAVEDENO PRAVNO SREDSTVO NI IZPOLNILO SVOJEGA OSNOVNEGA NAMENA. »SUBJEKTI DRUŽBE X« SE NANAŠAJO NA DRUŽBO X, NJENO MATIČNO DRUŽBO, PODRUŽNICE, POVEZANA PODJETJA, URADNIKE, DIREKTORJE, ZAPOSLENE, ZASTOPNIKE, PREDSTAVNIKE, PARTNERJE IN DAJALCE LICENC. VELJAVNA ZAKONODAJA NA OBMOČJU VAŠE SODNE PRISTOJNOSTI MORDA NE DOPUŠČA DOLOČENIH OMEJITEV ODGOVORNOSTI. V OBSEGU, KI GA ZAHTEVA VELJAVNA ZAKONODAJA NA OBMOČJU VAŠE SODNE PRISTOJNOSTI, ZGORAJ NAVEDENO NE OMEJUJE ODGOVORNOSTI SUBJEKTOV DRUŽBE X ZA GOLJUFIJO, GOLJUFIVO ZAVAJANJE, SMRT ALI TELESNO POŠKODBO ZARADI NAŠE MALOMARNOSTI, HUDE MALOMARNOSTI IN/ALI NAMERNEGA RAVNANJA. V NAJVEČJI MERI, KI JO DOVOLJUJE VELJAVNA ZAKONODAJA, JE NAJVEČJA SKUPNA ODGOVORNOST SUBJEKTOV DRUŽBE X ZA VSA JAMSTVA, KI JIH NI MOGOČE IZKLJUČITI, OMEJENA NA STO AMERIŠKIH DOLARJEV (100,00 USD). 4. Obvestilo v zvezi z napravami Apple. V kolikor ste kupili plačljive storitve ali jih uporabljate ali dostopate do plačljivih storitev v napravi iOS, nadalje potrjujete in se strinjate s pogoji tega razdelka. Potrjujete, da so ti pogoji samo med vami in nami, ne z družbo Apple, in družba Apple ni odgovorna za plačljive storitve in njihovo vsebino. Družba Apple nima nikakršne obveznosti zagotavljati kakršno koli vzdrževanje in podporno storitev v zvezi s plačljivimi storitvami. V primeru kakršnega koli neskladja med plačljivimi storitvami in katerim koli ustreznim jamstvom, lahko o tem obvestite družbo Apple in družba Apple vam bo vrnila zadevno kupnino za plačljive storitve; in do največje mere, ki jo dovoljuje veljavna zakonodaja, družba Apple nima nobene druge jamstvene obveznosti v zvezi s plačljivimi storitvami. Družba Apple ni odgovorna za obravnavo kakršnih koli zahtevkov z vaše strani ali strani katere koli tretje osebe v zvezi s plačljivimi storitvami ali vašim lastništvom in/ali uporabo plačljivih storitev, kar med drugim vključuje: (i) zahtevke za odgovornost za izdelek; (ii) kakršne koli zahtevke, da plačljive storitve niso v skladu s katero koli veljavno pravno ali regulativno zahtevo; in (iii) zahtevke, ki izhajajo iz zakonodaje o varstvu potrošnikov ali podobne zakonodaje. Družba Apple ni odgovorna za preiskavo, obrambo, poravnavo in razrešitev kakršnih koli zahtevkov tretjih oseb, da plačljive storitve in/ali vaše lastništvo in uporaba mobilne aplikacije kršijo pravice intelektualne lastnine te tretje osebe. Strinjate se, da boste med uporabo plačljivih storitev upoštevali vse veljavne pogoje tretjih oseb. Družba Apple in njene podružnice so upravičena tretja stranka teh pogojev in zatem, ko sprejmete te pogoje, ima družba Apple pravico (in štelo se bo, da je sprejela pravico), da uveljavi pogoje proti vam kot upravičena tretja oseba teh pogojev. S tem izjavljate in jamčite, da (i) niste v državi, za katero velja embargo vlade ZDA ali ki jo je vlada ZDA označila kot državo, ki "podpira teroriste" in (ii) niste na nobenem seznamu vlade ZDA, ki vsebuje prepovedane ali omejene osebe. 5. Navzkrižje. V primeru navzkrižja med določbami teh pogojev storitve za kupce za X in določbami uporabniške pogodbe za X imajo določbe teh pogojev storitve za kupce za X prednosti izključno v zvezi z vašo uporabo plačljive storitve. 6. REŠEVANJE SPOROV IN ODPOVED SKUPINSKIM TOŽBAM a. Začetno reševanje sporov. Večino sporov med vami in X je mogoče rešiti neformalno. Tukaj se lahko obrnete na plačljivo podporo. Ko se obrnete na nas, na kratko opišite naravo in razloge za svoje pomisleke, navedite svoje podatke za stik in želeno pomoč. Pogodbenici si v tem postopku podpore po svojih najboljših močeh prizadevata za rešitev sporov, zahtevkov ali nesoglasij, ki izhajajo iz teh pogojev in/ali vašega sodelovanja v programu ali so povezani z njimi (posamezno » spor « ali v primeru večjega števila » spori «). Vi in mi se strinjamo, da je dobronamerno sodelovanje v tem neformalnem postopku obvezno in mora biti izpolnjeno, kot je navedeno zgoraj, preden lahko katera koli stranka sproži sodni postopek v zvezi s katerim koli sporom, razen v zvezi z zahtevami za nujno sodno prepoved (» izvzeti spor «). Če v tridesetih (30) dneh od začetka neformalnega reševanja spora skladno z zgoraj navedeno določbo o začetnem reševanju sporov z vami ne moremo doseči dogovorjene rešitve v zvezi s sporom (razen izvzetim sporom), lahko vi ali mi sprožimo zavezujočo arbitražo b. Izbira prava in izbira sodišča . POZORNO PREBERITE TA RAZDELEK – LAHKO POMEMBNO VPLIVA NA VAŠE ZAKONSKE PRAVICE, VKLJUČNO S PRAVICO DO VLOŽITVE TOŽBE NA SODIŠČU. Zakoni zvezne države Teksas, razen njenih določb o izbiri prava, bodo urejali te pogoje in vse spore, ki nastanejo med vami in nami, ne glede na kakršen koli drug dogovor med vami in nami o nasprotnem. Vsi spori, povezani s temi pogoji, vključno z vsemi spori, zahtevki ali polemikami, ki izhajajo iz teh pogojev ali so povezani z njimi, se bodo obravnavali izključno na zveznih ali državnih sodiščih v okrožju Tarrant v Teksasu v Združenih državah Amerike, vi pa se strinjate z osebno pristojnostjo teh forumov in se odpovedujete vsakršnemu ugovoru glede neprimernega sodišča. Brez poseganja v zgoraj navedeno se strinjate, da lahko X po lastni presoji vloži kakršen koli zahtevek, tožbo ali spor, ki ga imamo proti vam, na katerem koli pristojnem sodišču v državi, v kateri prebivate, ki je pristojno in krajevno pristojno za zahtevek. Če ste zvezni, državni ali lokalni vladni subjekt v Združenih državah v svoji uradni vlogi in pravno ne morete sprejeti zgornjih klavzul o zakonodaji, jurisdikciji ali prizorišču, te klavzule za vas ne veljajo. Za takšne zvezne vladne subjekte ZDA bodo to pogodbo in vsa dejanja v zvezi z njo urejali zakoni Združenih držav Amerike (brez sklicevanja na kolizijo zakonov), v odsotnosti zveznega zakona in v obsegu, ki ga dovoljuje zvezna zakonodaja, pa zakoni zvezne države Teksas (razen izbire prava). c. IMATE DVE LETI ZA VLOŽITEV ZAHTEVKA ZOPER X . Vsak zahtevek zoper družbo X, ki izhaja iz teh pogojev ali je z njimi povezan, morate vložiti v dveh (2) letih po datumu nastanka dogodka ali dejstev, ki so podlaga za spor, razen če veljavna zakonodaja določa, da običajnega zastaralnega roka za ta zahtevek ni mogoče skrajšati s sporazumom. Če v tem roku ne vložite zahtevka, se za vedno odrečete pravici do uveljavljanja kakršnega koli zahtevka ali tožbe kakršne koli vrste ali značaja, ki temelji na takšnih dogodkih ali dejstvih, in takšni zahtevki ali vzroki za tožbo so trajno prepovedani in X ne bo imel nobene odgovornosti v zvezi s takim zahtevkom. d. Odpoved skupinski tožbi . V obsegu, ki ga dovoljuje zakonodaja, se odpovedujete tudi pravici do udeležbe kot tožnik ali skupinski tožnik v vseh domnevnih skupinskih tožbah, kolektivnih tožbah ali zastopniških tožbah. Pogoji storitve za kupce za X Če živite v Evropski uniji, državah Efte ali Združenem kraljestvu Družba X omogoča dostop do določenih funkcij v zameno za enkratno ali večkratno plačilo glede na zadevno funkcijo (posamezno » plačljiva storitev « in skupno » plačljive storitve «). Na primer X Premium (kot je opredeljeno spodaj) in naročnine bi se vsaka obravnavala kot »plačljiva storitev«. V obsegu, v katerem se registrirate za plačljivo storitev in/ali jo uporabljate, morajo biti vaša uporaba plačljivih storitev in kakršne koli pripadajoče transakcije v skladu s: (i) tukaj določenimi pogoji in določili, vključno z veljavnimi pogoji in določili za vsako plačljivo storitev, ki jo kupite in kot je navedena spodaj (skupaj » pogoji storitve za kupce za X «), ter (ii) veljavnimi pogoji storitve za X , pravilnikom o zasebnosti za X , pravili in pravilniki za X ter vsemi pravilniki, vključenimi v te dokumente (skupaj » uporabniška pogodba za X «). Ti pogoji storitve za kupce za X in prej omenjena uporabniška pogodba za X so v tem dokumentu skupaj imenovani » pogoji «. » X « se nanaša na subjekt X, ki vam zagotavlja plačljive storitve. Pozorno preberite te pogoje storitve za kupce za X, da se prepričate, ali razumete veljavne pogoje, določila in izjeme. ČE ŽIVITE V EVROPSKI UNIJI, DRŽAVAH EFTE ALI ZDRUŽENEM KRALJESTVU, TI POGOJI VSEBUJEJO POMEMBNE INFORMACIJE, KI VELJAJO ZA VAS GLEDE REŠEVANJA SPOROV, VKLJUČNO Z VAŠO ODPOVEDJO PRAVICI DO VLOŽITVE ZAHTEVKOV KOT SKUPINSKIH TOŽB TER OMEJITVIJO PRAVICE DO VLOŽITVE ZAHTEVKOV PROTI DRUŽBI X VEČ KOT 1 LETO PO ZADEVNIH DOGODKIH, KAR VPLIVA NA VAŠE PRAVICE IN OBVEZNOSTI, ČE PRIDE DO KAKRŠNEGA KOLI SPORA Z DRUŽBO X. ZA PODROBNOSTI O TEH DOLOČBAH PREBERITE 6. RAZDELEK POD SPLOŠNIMI POGOJI. Sprejemanje . Z uporabo ali dostopom do plačljivih storitev družbe X, iz tega izhajajočo izvedbo plačila in/ali klikom gumba za enkratni nakup ali redna plačila naročnine za plačljive storitve, ki jih zagotavlja družba X, se strinjate, da vas zavezujejo ti pogoji. Če pogojev ne razumete pogojev ali katerega koli dela ne sprejemate, ne smete uporabljati nobenih plačljivih storitev ali dostopati do njih. Za nakup in uporabo plačljive storitve morate: (i) imeti vsaj 18 let ali biti polnoletni, kot določa pristojna zakonodaja v vašem kraju bivanja, ali (ii) imeti izrecno soglasje staršev ali skrbnika za nakup in uporabo zadevne plačljive storitve. Če ste starš ali zakoniti skrbnik in svojemu otroku (ali otroku, katerega skrbnik ste) dovolite nakup ali uporabo plačljive storitve, se strinjate, da ti pogoji veljajo za vas, da jih boste upoštevali ter da ste odgovorni za otrokovo dejavnost v plačljivih storitvah in za zagotavljanje, da vaš otrok tudi upošteva te pogoje. V vsakem primeru morate biti stari vsaj 13 let za uporabo storitve X, kot je navedeno v razdelku »Kdo lahko uporablja storitve« v pogojih storitve X. Če te pogoje storitve za kupce X sprejemate in plačljive storitve uporabljate v imenu podjetja, organizacije, vlade ali druge pravne osebe, izjavljate in jamčite, da ste za to pooblaščeni in imate pooblastilo, da tak subjekt zavežete k tem pogojem storitve za kupce X, pri čemer se v tem primeru besedi »vi« in »vaš«, kot sta uporabljeni v teh pogojih storitve za kupce X, nanašata na ta subjekt. Pogodbeni subjekt družbe X . Te pogoje storitve za kupce za X sklepate s subjektom, ki ustreza kraju vašega bivanja, kot je navedeno spodaj. Ta subjekt vam bo zagotovil plačljive storitve. Noben drug subjekt ni vezan na nobene obveznosti do vas v skladu s temi pogoji storitve za kupce. Vaša lokacija Evropska unija, države Efte ali Združeno kraljestvo Pogodbeni subjekt X Internet Unlimited Company, s sedežem na naslovu One Cumberland Place, Fenian Street, Dublin 2, D02 AX07 Ireland Spremembe pogojev, plačljivih storitev in cen 1. Spremembe pogojev. Družba X lahko občasno spremeni te pogoje storitve za kupce za X na veljavni in razumni podlagi. Veljavna in razumna podlaga lahko vključuje (i) spremembo naših storitev, na primer zaradi tehničnega, varnostnega ali operativnega razvoja, (ii) odpravo tehničnih napak, (iii) spremembo v našem poslovanju, na primer zaradi sprememb politike, finančnih zadev ali drugih usmeritev, (iv) spremembo pravnega položaja, na primer zaradi spremembe zakonodaje, zahteve uradne agencije ali odločbe sodišča, in (v) optimizacijo uporabniške izkušnje z uvedbo novih funkcij. Spremembe ne veljajo retroaktivno, najnovejša različica pogojev storitve za kupce X, na voljo na spletnem mestu legal.x.com/purchaser-terms , bo določala vašo uporabo plačljivih storitev in kakršnih koli zadevnih transakcij. Če spremenimo te pogoje po tem, ko ste jih sprejeli (če se ti pogoji na primer spremenijo po nakupu naročnine), se zavezujemo, da vas bomo obvestili do 30 dni (odvisno od konkretnih sprememb) pred začetkom veljavnosti pomembnih sprememb teh pogojev, pri čemer bomo glede na spremembe določili razumen rok za uporabnike in vas obvestili o posledicah nadaljnje uporabe po izteku roka. Takšno obvestilo lahko posredujemo v elektronski obliki, kar (med drugim) vključuje obveščanje prek obvestila v storitvi ali e-pošte, poslane na e-poštni naslov, povezan z vašim računom. V primeru, da še naprej uporabljate plačljive storitve po izteku zgoraj navedenega roka, se strinjate, da vas zavezujejo spremenjeni pogoji storitve za kupca X. Če se ne strinjate s spremembami pogojev storitve za kupce za X, boste morali prenehati uporabljati plačljive storitve ali dostopati do njih (oziroma jih še naprej uporabljati ali dostopati do njih). Pogoji storitve za kupce X so napisani v angleščini, vendar so s prevodi na voljo v več jezikih. Družba X si prizadeva, da bi prevodi čim bolj točno odražali izvirno angleško različico. Vendar ima v primeru odstopanj ali nedoslednosti prednost angleška različica pogojev storitve za kupce X. Potrjujete, da bo angleščina referenčni jezik za razlaganje in sestavljanje pogojev v pogojih storitve za kupce X. 2. Spremembe plačljivih storitev. Naše plačljive storitve ter naši izdelki in storitve se nenehno razvijajo. X lahko spremeni plačljive storitve na razumni in veljavni podlagi. Takšna veljavna in razumna podlaga lahko vključuje (i) tehnični, varnostni ali operativni razvoj, (ii) odpravo tehničnih napak, (iii) skladnost s spremenjenim pravnim položajem, na primer zaradi spremembe zakona, zahteve uradne agencije ali odločitve sodišča, (iv) optimizacijo uporabniške izkušnje z uvedbo novih funkcij, in (v) spremembo v našem poslovanju, na primer zaradi politike, finančnih okoliščin ali drugih sprememb smeri. O vseh spremembah plačljivih storitev vas bomo obvestili do 30 dni pred začetkom njihove veljavnosti, na primer z obvestilom v storitvi ali e-poštnim sporočilom, poslanim na e-poštni naslov, povezan z vašim računom, pri čemer bomo navedli opis in datum začetka veljavnosti sprememb ter vas obvestili o morebitni pravici do prekinitve naročnine. Rok se lahko skrajša v primeru sprememb, povezanih z varnostjo. Naslednje se ne šteje za spremembe plačljivih storitev v smislu te določbe: (i) spremembe, ki vplivajo na temeljno naravo plačljivih storitev in bistvene značilnosti storitve, ki jo zagotavlja X, in (ii) trajna prekinitev storitev. X vam ne odgovarja za kakršno koli spremembo, začasno prekinitev ali prekinitev plačljivih storitev. Kjer je to zakonsko zahtevano, zgoraj navedena omejitev odgovornosti ne velja (i) za odškodnino za predvidljivo škodo v primerih rahle malomarne kršitve dolžnosti, če je njihovo izpolnitev bistvenega pomena za pravilno izvajanje pogodbe in se uporabniki lahko zanesejo na njihovo izpolnitev (bistvene pogodbene obveznosti) s strani X ali njegovih zakonitih zastopnikov ali posrednikov, in (ii) odgovornost X za (a) škodo, ki je posledica škode za življenje, telo ali zdravje, kakor tudi za škodo, ki je nastala zaradi naklepa ali hude malomarnosti s strani X, njenih zakonitih zastopnikov ali posrednikov, in (b) škodo zaradi neizpolnjevanja garancije ali zajamčene lastnosti ali kot posledica goljufivo prikrite napake. Posebni pogoji in določila (vključeni spodaj) za določeno plačljivo storitev določajo, kako lahko prekličete naročnino ali, če je to primerno, zahtevate vračilo kupnine. 3. Spremembe cen. Cene plačljivih storitev, vključno s ponavljajočimi se naročninami, se lahko občasno spremenijo zaradi sprememb stroškov v zvezi z delovanjem, vzdrževanjem, tehničnim zagotavljanjem, poslovnimi premisleki in pristojbinami, ki jih zaračunavajo tretje osebe, ali zakonskimi pristojbinami, po naši razumni presoji. V primeru povišanja stroškov si X pridržuje pravico do prilagoditve cen plačljivih storitev. X vas bo pisno obvestil o morebitnih spremembah cen do 30 dni pred začetkom veljavnosti, na primer z obvestilom o storitvi ali e-poštnim sporočilom na e-poštni naslov, povezan z vašim računom, v katerem navede vaše pravice in posledice njihovega neuveljavitve. V primeru spremembe cene lahko naročnino na ustrezno plačljivo storitev ali uporabniško pogodbo prekličete do 24 ur pred začetkom naslednjega obračunskega obdobja, pod pogojem, da je preklic opravljen v 30 dneh od prejema obvestila. V nasprotnem primeru bo sprememba cene začela veljati v času, ki je določen v obvestilu. Za naročniške storitve bodo spremembe cen začele veljati na začetku naslednjega naročniškega obdobja po datumu začetka veljavnosti spremembe cene. Plačilni pogoji . X ponuja različne možnosti plačila, ki se lahko razlikujejo glede na plačljivo storitev, vašo napravo in/ali operacijski sistem, vašo geografsko lokacijo ali druge dejavnike. Ti načini plačila lahko do mere, ki je na voljo (saj lahko družba X občasno omogoči različne načine nakupa), vključujejo uporabo funkcije za plačilo v aplikaciji, ki jo ponuja družba Google ali Apple, ali izvedbo spletnega plačila z uporabo storitve Stripe ( www.stripe.com – v nadaljnjem besedilu » Stripe «), neodvisnega ponudnika obdelave plačil družbe X. Ko plačilo izvedete, se izrecno strinjate, (i) da boste plačali ceno, navedeno za plačljivo storitev, skupaj z vsemi dodatnimi zneski v zvezi z veljavnimi davki, provizijami za kreditne kartice, bančnimi provizijami, stroški za transakcije v tujino, stroški menjalnega tečaja in nihanji valut; ter (ii) da boste upoštevali vse ustrezne pogoje storitve, pravilnike o zasebnosti ali druge pravne pogodbe ali omejitve (vključno z dodatnimi starostnimi omejitvami), ki jih uvedejo družba Google, Apple ali Stripe (neodvisni ponudnik obdelave plačil družbe X) v zvezi z vašo uporabo določenega načina plačila (če se na primer odločite samo za plačilo prek Applove funkcije za nakup v aplikaciji, se strinjate, da boste spoštovali vse ustrezne pogoje, zahteve in/ali omejitve, ki jih uvede družba Apple). Vsi zasebni osebni podatki, ki jih posredujete v zvezi z uporabo plačljivih storitev, kar med drugim vključuje kakršne koli podatke, posredovane v zvezi s plačilom, se obdelujejo skladno s pravilnikom o zasebnosti X. Družba X lahko vaše podatke o plačilu deli s ponudniki plačilnih storitev za obdelavo plačil; preprečevanje, odkrivanje in raziskovanje goljufij ali drugih prepovedanih dejavnosti; omogočanje reševanja sporov, na primer z vračilom plačil ali kupnine; in za druge namene, povezane s sprejemanjem kreditnih in debetnih kartic ali transakcij ACH. Odgovorni ste zagotoviti, da so vaši bančni podatki, podatki o kreditni kartici, debetni kartici in/ali drugi podatki o plačilu ves čas aktualni, popolni in točni. Če izvedete plačilo za plačljivo storitev, lahko prejmemo podatke o vaši transakciji, na primer, kdaj je bila opravljena, kdaj bo naročnina potekla ali se samodejno podaljšala, na kateri platformi ste opravili nakup in druge informacije. Družba X ni i pristojna in ne prevzema odgovornosti za morebitne napake ali zamude, ki jih povzroči ponudnik obdelave plačil, Applova storitev App Store ali Googlova storitev Play Store, vaša banka, izdajatelj vaše kreditne kartice in/ali katero koli plačilno omrežje. Za plačilne pogoje, ki veljajo za posamezno plačljivo storitev, vključno s tem, kako poteka obnovitev naročnine, in drugimi pomembnimi pogoji, si oglejte spodnje pogoje in določila za posamezno plačljivo storitev. Uporaba uporabniške pogodbe C, odpoved pogodbe, nevračilo, več računov X in omejitve 1. Uporabniška pogodba za X velja za vas . UPORABNIŠKO POGODBO X MORATE VEDNO UPOŠTEVATI IN RAVNATI V SKLADU Z NJO. Uporabniška pogodba X vedno velja za vašo uporabo storitve X, vključno s plačljivimi storitvami in funkcijami. Vaše neupoštevanje uporabniške pogodbe X in neskladno ravnanje z njo ali prepričanje družbe X, da uporabniške pogodbe X niste upoštevali in niste ravnali skladno z njo, lahko vodi do preklica plačljivih storitev. Kakršen koli preklic bo sledil, vključno s katerim koli izvršilnim ukrepom, ki ga družba X lahko izvede proti vam v skladu z uporabniško pogodbo X, vendar ne omejeno nanj. V takih primerih lahko izgubite ugodnosti plačljivih storitev in ne boste upravičeni do vračila kupnine, ki ste jo plačali (ali predhodno plačali) za plačljive storitve. 2. Razlogi, zakaj lahko družba X ukine dostop do plačljivih storitev. Družba X lahko začasno prekine ali ukine dostop do plačljivih storitev ali preneha delno ali v celoti zagotavljati plačljive storitve ali sprejme kakršen koli drug ukrep, ki se ji zdi primeren, vključno z začasno prekinitvijo dostopa do računa, (brez kakršne koli odgovornosti) kadar koli in iz katerega koli razloga ali brez njega, kar med drugim vključuje katerega koli od naslednjih utemeljenih razlogov: a. Družba X je po lastni presoji prepričana, da ste kršili pogoje ali da bi vaša uporaba plačljivih storitev kršila katero koli veljavno zakonodajo. b. Od družbe X to zahteva ali ji to naroči katero koli pristojno sodišče, regulativni organ ali organ kazenskega pregona; c. Družba X ima nepričakovane tehnične ali varnostne težave; d.X po lastni razumni presoji meni, da ste kršili uporabniško pogodbo X; e. Družba X meni, da obstajajo utemeljeni razlogi, kot je sodelovanje pri manipulaciji, zavajanju ali drugih motečih ali prepovedanih dejavnostih v zvezi s plačljivimi storitvami; f. Ustvarjate tveganje ali morebitno pravno izpostavljenost za X; g. Vaš račun je treba odstraniti zaradi nezakonitega ravnanja; h. Vaš račun je treba odstraniti zaradi daljše nedejavnosti ali i. Naše zagotavljanje plačljivih storitev (v celoti ali delno) za vas ni več komercialno izvedljivo (po lastni presoji X). 3. Vse transakcije so končne. Vsa plačila za plačljive storitve so končna in jih ni mogoče povrniti ali zamenjati, razen če to zahteva veljavna zakonodaja. Ne jamčimo za naravo, kakovost ali vrednost plačljive storitve ali njeno razpoložljivost ali dobavo. Za neuporabljene ali delno uporabljene plačljive storitve (na primer delno uporabljeno naročniško obdobje) niso zagotovljena vračila kupnine ali dobropisi. 4. Plačljive storitve niso prenosljive med računi X. Vsak nakup plačljive storitve velja za en račun X, kar pomeni, da bo vaš nakup veljal samo za račun, ki ste ga uporabljali, ko ste kupili plačljivo storitev, in ne bo veljal za druge račune, do katerih imate morda dostop ali jih nadzorujete. Če imate ali nadzorujete več računov in želite imeti dostop do plačljivih storitev na vsakem računu, morate plačljivo storitev kupiti za vsak račun posebej. 5. Omejitve in obveznosti. a. Plačljivo storitev lahko kupite in uporabljate samo, če vam je zakonsko dovoljeno uporabljati plačljivo storitev v vaši državi in živite v državi, v kateri družba X podpira zadevno plačljivo storitev. Družba X lahko po lastni presoji v določenih državah omeji možnost dostopa do plačljive storitve ali njenega nakupa. Družba X si pridržuje pravico, da občasno spremeni seznam podprtih držav. b. Pridržujemo si pravico, da po lastni presoji zavrnemo transakcije plačljivih storitev ali prekličemo ali ukinemo prodajo ali uporabo plačljive storitve. c. Drugim ne smete dovoliti, da uporabljajo vaš račun X za dostop do katere koli plačljive storitve, ki je ta oseba ni naročila. d. Plačljive storitve ne smete kupiti ali uporabljati, če ste oseba, s katero osebam iz ZDA ni dovoljeno poslovati na podlagi gospodarskih sankcij, kar med drugim vključuje sankcije, ki jih uvaja Urad za nadzor tujega premoženja (ang. Office of Foreign Assets Control) pri Ministrstvu za finance ZDA ali kateri koli drug veljavni organ za sankcije (» prepovedana oseba «). To med drugim vključuje osebe, ki imajo prebivališče v naslednjih državah in regijah ali običajno prebivajo v njih: Kuba, Iran, regija Krim v Ukrajini, Severna Koreja in Sirija. Izjavljate in jamčite, da niste prepovedana oseba. e. IZJAVLJATE, DA BOSTE PLAČLJIVE STORITVE UPORABLJALI SAMO V ZAKONITE NAMENE IN SAMO V SKLADU S TEMI POGOJI. Davki in pristojbine . Odgovorni ste in se strinjate, da boste plačali vse veljavne davke, dajatve, tarife in pristojbine, povezane z nakupom plačljivih storitev, vključno s tistimi, ki jih je treba plačati X ali tretjemu plačilnemu procesorju. Ti davki lahko med drugim vključujejo DDV, davek na blago in storitve (GST), prometni davek, davčni odtegljaj in vse druge veljavne davke. Odvisno od vaše lokacije je družba X lahko odgovorna za zbiranje in poročanje podatkov v zvezi z davki na transakcije, ki izhajajo iz nakupa plačljivih storitev. Družbi X podeljujete dovoljenje, da ustreznim davčnim organom posreduje vaš račun in osebne podatke za izpolnjevanje obveznosti pobiranja davkov in poročanja. Splošni pogoji 1. Podatki za stik. Če imate kakršna koli vprašanja o plačljivih storitvah ali teh pogojih, si lahko ogledate središče za pomoč pri plačljivih storitvah družbe X za več podrobnosti. Če ste že kupili plačljivo storitev, nas lahko kontaktirate tudi prek povezave za podporo, ki je na voljo v meniju za krmarjenje vašega računa X pod nastavitvami plačila ali naročnine. Če imate dodatna vprašanja, lahko stopite v stik z nami tukaj z uporabo obrazca »Help with paid features« (Pomoč pri plačljivih funkcijah). 2. ZAVRNITEV ODGOVORNOSTI. DO PLAČLJIVIH STORITEV DOSTOPATE V NAJVEČJI MERI, KI JO DOVOLJUJE VELJAVNA ZAKONODAJA, IN JIH UPORABLJATE NA LASTNO ODGOVORNOST. RAZUMETE IN SE STRINJATE, DA SO VAM PLAČLJIVE STORITVE ZAGOTOVLJENE PO NAČELIH »KOT JE« IN »KOT JE NA VOLJO«. DRUŽBA X ZAVRAČA KAKRŠNA KOLI JAMSTVA IN POGOJE, IZRECNE ALI IMPLICITNE, GLEDE PRODAJNOSTI, PRIMERNOSTI ZA DOLOČEN NAMEN ALI NEKRŠITVE PRAVIC INTELEKTUALNE LASTNINE. DRUŽBA X NE PODAJA NOBENEGA JAMSTVA ALI ZAGOTOVILA TER NE PREVZEMA NOBENE ODGOVORNOSTI ZA: (I) POPOLNOST, TOČNOST, RAZPOLOŽLJIVOST, PRAVOČASNOST, VARNOST ALI ZANESLJIVOST PLAČLJIVIH STORITEV; IN ZA TO, (II) DA BODO PLAČLJIVE STORITVE IZPOLNJEVALE VAŠE ZAHTEVE ALI BODO NA VOLJO NEPREKINJENO, VARNO ALI BREZ NAPAK. PREVZEMATE ODGOVORNOST ZA SVOJO UPORABO STORITVE X, VKLJUČNO S PLAČLJIVIMI STORITVAMI IN VSO VSEBINO, KI JO POSREDUJETE. 3. OMEJITEV ODGOVORNOSTI. V NAJVEČJI MERI, KI JO DOVOLJUJE VELJAVNA ZAKONODAJA, SUBJEKTI DRUŽBE X NISO ODGOVORNI ZA KAKRŠNO KOLI POSREDNO, NAKLJUČNO, POSEBNO, POSLEDIČNO ALI KAZENSKO ŠKODO ALI KAKRŠNO KOLI IZGUBO DOBIČKA ALI PRIHODKOV, NASTALO BODISI NEPOSREDNO BODISI POSREDNO, ALI KAKRŠNO KOLI IZGUBO PODATKOV, UPORABE, DOBREGA IMENA ALI DRUGO NEPREMOŽENJSKO ŠKODO, KI SO POSLEDICA (i) VAŠEGA DOSTOPA DO PLAČLJIVIH STORITEV ALI NJIHOVE UPORABE ALI NEZMOŽNOSTI DOSTOPA DO PLAČLJIVIH STORITEV ALI NJIHOVE UPORABE; (ii) KAKRŠNEGA KOLI RAVNANJA KATERE KOLI TRETJE OSEBE ALI NJENE VSEBINE, OBJAVLJENE PREK PLAČLJIVIH STORITEV, KAR MED DRUGIM VKLJUČUJE VSAKRŠNO OBREKLJIVO, ŽALJIVO ALI NEZAKONITO RAVNANJE DRUGIH UPORABNIKOV ALI TRETJIH OSEB; (iii) KAKRŠNE KOLI VSEBINE, PRIDOBLJENE IZ PLAČLJIVIH STORITEV; ALI (iv) NEPOOBLAŠČENEGA DOSTOPA, UPORABE ALI SPREMEMBE VAŠIH PRENOSOV ALI VSEBINE. V IZOGIB DVOMOM JE OPREDELITEV PLAČLJIVIH STORITEV OMEJENA NA FUNKCIJE, KI JIH PONUJA DRUŽBA X, IN NE VKLJUČUJE NOBENIH VSEBIN, DO KATERIH DOSTOPATE IN/ALI S KATERIMI IMATE INTERAKCIJE MED UPORABO TEH FUNKCIJ. V NOBENEM PRIMERU SKUPNA ODGOVORNOST SUBJEKTOV X NE SME PRESEGATI VIŠJEGA ZNESKA STO EVROV (100,00 €) ALI ZNESKA, KI STE GA PLAČALI X, ČE OBSTAJA, V ZADNJIH ŠESTIH MESECIH ZA PLAČANE STORITVE, KI SO PODLAGA ZA ZAHTEVEK. OMEJITVE IZ TEGA PODRAZDELKA VELJAJO ZA VSE TEORIJE ODGOVORNOSTI, NE GLEDE NA TO, ALI TEMELJIJO NA GARANCIJI, POGODBI, STATUTU, ŠKODNEM DEJANJU (VKLJUČNO Z MALOMARNOSTJO) ALI DRUGEM IN NE GLEDE NA TO, ALI SO BILI SUBJEKTI DRUŽBE X OBVEŠČENI O MOŽNOSTI TAKE ŠKODE IN TUDI ČE SE UGOTOVI, DA TUKAJ NAVEDENO PRAVNO SREDSTVO NI IZPOLNILO SVOJEGA OSNOVNEGA NAMENA. »SUBJEKTI DRUŽBE X« SE NANAŠAJO NA DRUŽBO X, NJENO MATIČNO DRUŽBO, PODRUŽNICE, POVEZANA PODJETJA, URADNIKE, DIREKTORJE, ZAPOSLENE, ZASTOPNIKE, PREDSTAVNIKE, PARTNERJE IN DAJALCE LICENC. VELJAVNA ZAKONODAJA NA OBMOČJU VAŠE SODNE PRISTOJNOSTI MORDA NE DOPUŠČA DOLOČENIH OMEJITEV ODGOVORNOSTI. V OBSEGU, KI GA ZAHTEVA VELJAVNA ZAKONODAJA NA OBMOČJU VAŠE SODNE PRISTOJNOSTI, ZGORAJ NAVEDENO NE OMEJUJE ODGOVORNOSTI SUBJEKTOV DRUŽBE X ZA GOLJUFIJO, GOLJUFIVO ZAVAJANJE, SMRT ALI TELESNO POŠKODBO ZARADI NAŠE MALOMARNOSTI, HUDE MALOMARNOSTI IN/ALI NAMERNEGA RAVNANJA. V NAJVEČJEM OBSEGU, KI GA DOVOLJUJE VELJAVNA ZAKONODAJA, JE NAJVEČJA SKUPNA ODGOVORNOST X ENTITET ZA KAKRŠNA KOLI NEIZKLJUČLJIVA JAMSTVA OMEJENA NA STO EVROV (100,00 €). 4. Obvestilo v zvezi z napravami Apple. V kolikor ste kupili plačljive storitve ali jih uporabljate ali dostopate do plačljivih storitev v napravi iOS, nadalje potrjujete in se strinjate s pogoji tega razdelka. Potrjujete, da so ti pogoji samo med vami in nami, ne z družbo Apple, in družba Apple ni odgovorna za plačljive storitve in njihovo vsebino. Družba Apple nima nikakršne obveznosti zagotavljati kakršno koli vzdrževanje in podporno storitev v zvezi s plačljivimi storitvami. V primeru kakršnega koli neskladja med plačljivimi storitvami in katerim koli ustreznim jamstvom, lahko o tem obvestite družbo Apple in družba Apple vam bo vrnila zadevno kupnino za plačljive storitve; in do največje mere, ki jo dovoljuje veljavna zakonodaja, družba Apple nima nobene druge jamstvene obveznosti v zvezi s plačljivimi storitvami. Družba Apple ni odgovorna za obravnavo kakršnih koli zahtevkov z vaše strani ali strani katere koli tretje osebe v zvezi s plačljivimi storitvami ali vašim lastništvom in/ali uporabo plačljivih storitev, kar med drugim vključuje: (i) zahtevke za odgovornost za izdelek; (ii) kakršne koli zahtevke, da plačljive storitve niso v skladu s katero koli veljavno pravno ali regulativno zahtevo; in (iii) zahtevke, ki izhajajo iz zakonodaje o varstvu potrošnikov ali podobne zakonodaje. Družba Apple ni odgovorna za preiskavo, obrambo, poravnavo in razrešitev kakršnih koli zahtevkov tretjih oseb, da plačljive storitve in/ali vaše lastništvo in uporaba mobilne aplikacije kršijo pravice intelektualne lastnine te tretje osebe. Strinjate se, da boste med uporabo plačljivih storitev upoštevali vse veljavne pogoje tretjih oseb. Dr | 2026-01-13T08:48:38 |
https://twitter.com/i/flow/convert_to_professional | 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 | 2026-01-13T08:48:38 |
https://dev.to/thekarlesi/how-to-handle-stripe-and-paystack-webhooks-in-nextjs-the-app-router-way-5bgi#main-content | How to Handle Stripe and Paystack Webhooks in Next.js (The App Router Way) - 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 Esimit Karlgusta Posted on Jan 13 How to Handle Stripe and Paystack Webhooks in Next.js (The App Router Way) # api # nextjs # security # tutorial The #1 reason developers struggle with SaaS payments is Webhook Signature Verification. You set everything up, the test payment goes through, but your server returns a 400 Bad Request or a Signature Verification Failed error. In the Next.js App Router, the problem usually stems from how the request body is parsed. Stripe and Paystack require the raw request body to verify the signature, but Next.js often tries to be helpful by parsing it as JSON before you can get to it. Here is the "Golden Pattern" for handling this in 2026. 1. The Route Handler Setup Create a file at app/api/webhooks/route.ts . You must export a config object (if using older versions) or use the req.text() method in the App Router to prevent automatic parsing. import { NextResponse } from " next/server " ; import crypto from " crypto " ; export async function POST ( req : Request ) { // 1. Get the raw body as text const body = await req . text (); // 2. Grab the signature from headers const signature = req . headers . get ( " x-paystack-signature " ) || req . headers . get ( " stripe-signature " ); if ( ! signature ) { return NextResponse . json ({ error : " No signature " }, { status : 400 }); } // 3. Verify the signature (Example for Paystack) const hash = crypto . createHmac ( " sha512 " , process . env . PAYSTACK_SECRET_KEY ! ) . update ( body ) . digest ( " hex " ); if ( hash !== signature ) { return NextResponse . json ({ error : " Invalid signature " }, { status : 401 }); } // 4. Now parse the body and handle the event const event = JSON . parse ( body ); if ( event . event === " charge.success " ) { // Handle successful payment in your database console . log ( " Payment successful for: " , event . data . customer . email ); } return NextResponse . json ({ received : true }, { status : 200 }); } Enter fullscreen mode Exit fullscreen mode 2. The Middleware Trap If you have global middleware protecting your routes, ensure your webhook path is excluded. Otherwise, the payment provider will hit your login page instead of your API. 3. Why this matters for your SaaS If your webhooks fail, your users won't get their "Pro" access, and your churn will skyrocket. Handling this correctly is the difference between a side project and a real business. I have spent a lot of time documenting these "Gotchas" while building my MERN stack projects. If you want to see a full implementation of this including Stripe, Paystack, and database logic, check out my deep dive here: How to add Stripe or Paystack payments to your SaaS . Digging Deeper If you are tired of debugging the same boilerplate over and over, you might find my SassyPack overview helpful. I built it specifically to solve these "Day 1" technical headaches for other founders. Happy coding! 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 Esimit Karlgusta Follow Full Stack Developer Location Earth, for now :) Education BSc. IT Work Full Stack Developer Joined Mar 31, 2020 More from Esimit Karlgusta Secure Authentication in Next.js: Building a Production-Ready Login System # webdev # programming # nextjs # beginners Stop Coding Login Screens: A Senior Developer’s Guide to Building SaaS That Actually Ships # webdev # programming # beginners # tutorial Zero to SaaS vs ShipFast, Which One Actually Helps You Build a Real SaaS? # nextjs # beginners # webdev # programming 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:38 |
https://legal.x.com/pl/purchaser-terms.html | Zasady użytkowania dla kupujących w serwisie X Zasady użytkowania dla kupujących w serwisie X Pobierz Zasady użytkowania dla kupujących w serwisie X Zasady użytkowania usług płatnych Dodatkowe zasady użytkowania usługi X Premium Dodatkowe zasady użytkowania subskrypcji Pobierz Zasady użytkowania dla kupujących w serwisie X Zasady użytkowania dla kupujących w serwisie X goglobalwithtwitterbanner Zasady użytkowania usług płatnych Dodatkowe zasady użytkowania usługi X Premium Dodatkowe postanowienia dotyczące subskrypcji twórców treści Dodatkowe postanowienia dotyczące programów Premium Business i Premium Organizations Zasady użytkowania usług płatnych Dodatkowe zasady użytkowania usługi X Premium Dodatkowe postanowienia dotyczące subskrypcji twórców treści Dodatkowe postanowienia dotyczące programów Premium Business i Premium Organizations Zasady użytkowania dla kupujących w serwisie X Data wejścia w życie: 1 sierpnia 2025 r Jeśli Użytkownik mieszka w kraju spoza Unii Europejskiej, kraju spoza EFTA lub kraju innym niż Zjednoczone Królestwo , w tym jeśli mieszka w Stanach Zjednoczonych, obowiązują go następujące Zasady użytkowania dla kupujących w serwisie X . Jeśli Użytkownik mieszka w kraju należącym do Unii Europejskiej, kraju należącym do EFTA lub w Zjednoczonym Królestwie , obowiązują go te Zasady użytkowania dla kupujących w serwisie X . Zasady użytkowania dla kupujących w serwisie X Jeśli Użytkownik mieszka w kraju spoza Unii Europejskiej, kraju spoza EFTA lub kraju innym niż Zjednoczone Królestwo, w tym w Stanach Zjednoczonych: X umożliwia Użytkownikowi dostęp do określonych funkcji w zamian za uiszczenie jednorazowej lub cyklicznej opłaty, zależnie od konkretnej funkcji (jednostkowo „ Usługa Płatna ”, a zbiorczo „ Usługi Płatne ”). Na przykład usługa X Premium (zgodnie z poniższą definicją) i Subskrypcje będą uważane za „Usługi Płatne”. W zakresie, w jakim Użytkownik zarejestruje się w Usłudze Płatnej lub użytkuje Usługę Płatną, użytkowanie przez Użytkownika Usługi Płatnej i zawieranie wszelkich powiązanych transakcji podlega (i) postanowieniom tego dokumentu, w tym postanowieniom dotyczącym poszczególnych kupowanych przez Użytkownika Usług Płatnych, które to postanowienia wyszczególniono poniżej (łącznie „ Zasady użytkowania dla kupujących w serwisie X ”), oraz (ii) stosownym Zasadom użytkowania serwisu X , Polityce prywatności serwisu X , Zasadom i politykom serwisu X oraz wszelkim politykom stanowiącym integralną część tych dokumentów (łącznie „ Umowa z Użytkownikiem serwisu X ”). Niniejsze Zasady użytkowania dla kupujących w serwisie X oraz Umowa z Użytkownikiem serwisu X będą łącznie określane w tym dokumencie jako „ Zasady ”. „ X ” oznacza podmiot X, który świadczy na Twoją rzecz Usługi Płatne. Należy uważnie przeczytać Zasady użytkowania dla kupujących w serwisie X oraz dokładnie zrozumieć zawarte w nich postanowienia, warunki i wyjątki. JEŚLI UŻYTKOWNIK MIESZKA W STANACH ZJEDNOCZONYCH, NINIEJSZE ZASADY ZAWIERAJĄ WAŻNE INFORMACJE DOTYCZĄCE ROZSTRZYGANIA SPORÓW, W TYM DOBROWOLNEGO ZRZECZENIA SIĘ PRAWA DO WNOSZENIA ROSZCZEŃ W RAMACH POWÓDZTW ZBIOROWYCH ORAZ OGRANICZENIA PRAWA DO WNOSZENIA ROSZCZEŃ PRZECIWKO X DO 2 LAT OD ZAISTNIENIA STOSOWNYCH ZDARZEŃ. TE ZASADY WPŁYWAJĄ NA PRAWA I ZOBOWIĄZANIA UŻYTKOWNIKA W RAZIE JAKIEGOKOLWIEK SPORU Z X. SZCZEGÓŁOWY OPIS TYCH POSTANOWIEŃ ZNAJDUJE SIĘ W PUNKCIE 6 POSTANOWIEŃ OGÓLNYCH. Akceptacja . Użytkując lub uzyskując dostęp do Usług Płatnych za pośrednictwem X, dokonując płatności za te usługi lub klikając przycisk w celu dokonania jednorazowego zakupu lub uregulowania jednej z cyklicznych opłat za subskrypcję Usługi Płatnej świadczonej przez X, Użytkownik zgadza się związać Zasadami. Jeśli Użytkownik nie rozumie treści Zasad albo nie akceptuje ich którejkolwiek części, nie może użytkować ani uzyskiwać dostępu do żadnych Usług Płatnych. Aby zakupić i użytkować Usługę Płatną, Użytkownik musi (i) mieć ukończone 18 lat lub być w wieku decydującym o pełnoletniości według przepisów w kraju lub regionie, w którym Użytkownik mieszka, lub (ii) mieć jednoznaczną zgodę rodzica lub opiekuna na zakup i użytkowanie Usługi Płatnej. Jeśli Użytkownik jest rodzicem lub opiekunem prawnym i pozwoli swojemu dziecku (lub innemu dziecku, którego jest opiekunem) na zakup lub użytkowanie Usługi Płatnej, zgadza się, że Zasady mają do Użytkownika zastosowanie, będzie ich przestrzegać, ponosi odpowiedzialność za czynności wykonywane przez dziecko w Usłudze Płatnej oraz dopilnuje, aby również dziecko przestrzegało Zasad. W każdym przypadku, tak jak to określa punkt „Kto może użytkować Usługi” w Zasadach użytkowania serwisu X, osoby chcące użytkować Usługi X muszą mieć ukończone 13 lat. Jeśli Użytkownik akceptuje Zasady użytkowania dla kupujących w serwisie X i użytkuje Usługi Płatne w imieniu przedsiębiorstwa, organizacji, organu administracji publicznej lub innej osoby prawnej, wówczas oświadcza i gwarantuje, że ma do tego wszelkie upoważnienia oraz może związać taki podmiot Zasadami użytkowania dla kupujących w serwisie X, i wtedy termin „Użytkownik” stosowany w Zasadach użytkowania dla kupujących w serwisie X odnosi się do tego podmiotu. X Podmiot zawierający umowę . Użytkownik wyraża zgodę na te Zasady użytkowania dla kupujących w serwisie X, zawierając umowę z podmiotem właściwym dla miejsca zamieszkania Użytkownika, zgodnie z listą zamieszczoną poniżej. Podmiot ten będzie świadczyć Użytkownikowi Usługi Płatne. Zgodnie z niniejszymi Zasadami użytkowania dla kupujących w serwisie X żaden inny podmiot nie jest związany jakimikolwiek zobowiązaniami wobec Użytkownika. Lokalizacja Użytkownika Ameryka Północna (w tym Hawaje) lub Ameryka Południowa Podmiot zawierający umowę X Corp., z biurem zlokalizowanym pod adresem 865 FM 1209, Building 2, Bastrop, TX 78602, USA Lokalizacja Użytkownika Dowolny kraj spoza dwóch powyższych lokalizacji, w tym kraj znajdujący się w Azji Południowo-Wschodniej, na Bliskim Wschodzie, w Afryce lub w Europie (z wyłączeniem krajów UE, krajów EFTA i Zjednoczonego Królestwa) Podmiot zawierający umowę X Global LLC, z siedzibą pod adresem 701 S. Carson St., Suite 200, Carson City, NV 89701, USA Zmiany Warunków, Usług płatnych i cen 1. Zmiany Zasad. X może od czasu do czasu zmieniać niniejsze Zasady użytkowania dla kupujących w serwisie X. Zmiany mogą być wprowadzane z dowolnych przyczyn biznesowych, finansowych lub prawnych. Zmiany nie będą działać z mocą wsteczną, a użytkowanie Usług Płatnych i wszelkie związane z tym transakcje będą podlegać najnowszej wersji Zasad użytkowania dla kupujących w serwisie X dostępnej pod adresem legal.x.com/purchaser-terms . Jeśli zmodyfikujemy lub zmienimy niniejsze Warunki po wyrażeniu przez użytkownika zgody na nie (na przykład jeśli Warunki zostaną zmienione po zakupie subskrypcji), powiadomimy użytkownika z wyprzedzeniem o istotnych zmianach. Takie powiadomienie może zostać przekazane drogą elektroniczną, w tym, między innymi, za pośrednictwem powiadomienia w ramach usługi lub wiadomości e-mail wysłanej na adres e-mail powiązany z kontem użytkownika. Dalsze użytkowanie przez Użytkownika Usług Płatnych po wejściu w życie zmian oznacza, że Użytkownik zgadza się na związanie się Zasadami użytkowania dla kupujących w serwisie X. Jeśli Użytkownik nie zgadza się na te lub przyszłe Zasady użytkowania dla kupujących w serwisie X, nie powinien dalej użytkować ani uzyskiwać dostępu do Usług Płatnych. Zasady użytkowania dla kupujących w serwisie X zostały sporządzone w języku angielskim oraz po przetłumaczeniu udostępnione w wielu innych językach. X dokłada wszelkich starań, aby tłumaczenia były w jak największym stopniu zgodne z oryginalną wersją angielską. W razie wystąpienia jakichkolwiek rozbieżności lub niespójności wersja angielska Zasad użytkowania dla kupujących w serwisie X ma jednak znaczenie rozstrzygające. Użytkownik zgadza się, że językiem odniesienia dla wykładni postanowień Zasad użytkowania dla kupujących w serwisie X jest język angielski. 2. Zmiany Usług Płatnych. Nasze Usługi Płatne są ciągle rozwijane. W związku z tym Usługi płatne mogą ulegać zmianom od czasu do czasu, według naszego uznania, w tym z przyczyn biznesowych, finansowych lub prawnych. Możemy zaprzestać (na stałe lub tymczasowo) świadczenia Usług płatnych lub udostępniania wybranych funkcji w ramach Usług płatnych na rzecz użytkownika lub użytkowników po wcześniejszym powiadomieniu lub bez. X nie ponosi odpowiedzialności wobec Użytkownika ani osób trzecich za jakiekolwiek modyfikacje, zawieszenie lub zaprzestanie świadczenia Usług Płatnych. Szczegółowe warunki (zawarte poniżej) dotyczące konkretnych Usług płatnych określają sposób, w jaki można anulować subskrypcję lub, w stosownych przypadkach, ubiegać się o zwrot środków. 3. Zmiany w cenniku. Ceny Usług płatnych, w tym cykliczne opłaty subskrypcyjne, mogą od czasu do czasu ulegać zmianom, w tym z przyczyn biznesowych, finansowych lub prawnych. X z odpowiednim wyprzedzeniem powiadomi o wszelkich istotnych zmianach cen Usług Płatnych. W przypadku usług subskrybowanych zmiana ceny wejdzie w życie z początkiem następnego okresu płatności od daty wprowadzenia zmiany ceny. Jeśli użytkownik nie wyraża zgody na opłacanie subskrypcji według nowego cennika, ma on prawo odrzucić zmianę poprzez anulowanie subskrypcji odpowiedniej Usługi płatnej przed wejściem w życie zmiany ceny. Warunki płatności . X oferuje różne opcje płatności, które mogą różnić się w zależności od Usługi Płatnej, urządzenia, systemu operacyjnego, lokalizacji geograficznej lub innych czynników dotyczących Użytkownika. W dostępnym zakresie (X może bowiem udostępniać różne metody zakupu) te opcje płatności mogą obejmować możliwość korzystania z funkcji „Płatność w aplikacji” oferowanej przez Google lub Apple lub dokonywania płatności internetowych za pośrednictwem zewnętrznego operatora płatności współpracującego z X, czyli firmy Stripe ( www.stripe.com , dalej „ Stripe ”). Dokonując płatności, Użytkownik wyraźnie zgadza się (i) zapłacić wskazaną cenę za Usługę Płatną wraz z wszelkimi dodatkowymi kwotami związanymi z obowiązującymi podatkami, opłatami za karty kredytowe, opłatami bankowymi, opłatami za transakcje zagraniczne, opłatami za wymianę walut oraz wahaniami kursów walut; oraz (ii) przestrzegać wszelkich zasad użytkowania, polityk prywatności lub innych umów lub ograniczeń prawnych (w tym dodatkowych ograniczeń wiekowych) nałożonych przez Google, Apple lub Stripe (jako zewnętrzni operatorzy płatności w imieniu X) w związku ze stosowaniem przez Użytkownika danej metody płatności (jeśli na przykład Użytkownik zdecyduje się na dokonanie płatności za pośrednictwem funkcji zakupów w aplikacji Apple, wyraża wówczas zgodę na przestrzeganie wszelkich stosownych postanowień, wymogów lub ograniczeń nałożonych przez Apple). Wszelkie prywatne dane osobowe, które Użytkownik przekazuje w związku z użytkowaniem Usług Płatnych, w tym w szczególności wszelkie dane przekazywane w związku z płatnością, będą przetwarzane zgodnie z Polityką prywatności X. X może udostępniać informacje dotyczące płatności dostawcom usług płatniczych w celu przetwarzania płatności; wykrywania i badania oszustw lub innych niedozwolonych działań oraz zapobiegania im; ułatwiania rozstrzygania sporów, takich jak obciążenia zwrotne lub zwroty środków oraz do innych celów związanych z akceptacją kart kredytowych, kart debetowych lub kont ACH. Do obowiązków użytkownika należy upewnienie się, że jego dane bankowe, dane dotyczące karty kredytowej, karty debetowej i/lub inne informacje dotyczące płatności są zawsze aktualne, kompletne i poprawne. Jeśli użytkownik dokonuje płatności za Usługi płatne, możemy uzyskać informacje na temat transakcji użytkownika, takie jak data jej wykonania, data wygaśnięcia lub automatycznego odnowienia subskrypcji, platforma, na której użytkownik dokonał zakupu, a także inne informacje. X nie ponosi odpowiedzialności za błędy ani opóźnienia popełnione przez operatora płatności, Apple App Store lub sklep Google Play, bank, operatora karty kredytowej lub sieć płatniczą. Użytkownik powinien zapoznać się z poniższymi Warunkami korzystania z poszczególnych Usług płatnych, aby dowiedzieć się, jakie warunki płatności obowiązują w odniesieniu do każdej z nich, w tym warunki odnawiania subskrypcji oraz inne istotne zasady. Zastosowanie Umowy z Użytkownikiem X, wypowiedzenie, brak możliwości zwrotu pieniędzy, wiele kont na X oraz ograniczenia 1. Umowa z Użytkownikiem serwisu X ma zastosowanie do Użytkownika . UŻYTKOWNIK ZAWSZE MUSI PRZESTRZEGAĆ POSTANOWIEŃ UMOWY Z UŻYTKOWNIKIEM SERWISU X. Umowa z Użytkownikiem serwisu X ma zastosowanie do każdego przypadku użytkowania przez Użytkownika Usługi X, w tym Usług Płatnych i funkcji. Jeśli Użytkownik nie przestrzega postanowień Umowy z Użytkownikiem serwisu X lub X ma uzasadnione podstawy sądzić, że doszło do naruszenia tych postanowień, Użytkownik musi się liczyć z anulowaniem dostępu do Usług Płatnych. Każdemu takiemu anulowaniu mogą towarzyszyć inne działania egzekucyjne podejmowane przez X wobec Użytkownika na mocy Umowy z Użytkownikiem serwisu X. Użytkownik może wtedy utracić korzyści zawarte w Usługach Płatnych oraz nie będzie uprawniony do zwrotu żadnych kwot zapłaconych (lub przedpłaconych) za Usługi Płatne. 2. Dlaczego X może wypowiedzieć dostęp Użytkownika do Usług Płatnych. X może zawiesić lub wypowiedzieć Użytkownikowi dostęp do Usług Płatnych albo zaprzestać świadczenia na rzecz Użytkownika całości lub części Usług Płatnych bądź podjąć inne działanie, które uzna za właściwe, w tym na przykład zawiesić konto Użytkownika (bez ponoszenia z tego tytułu żadnej odpowiedzialności), w dowolnym momencie, z dowolnej przyczyny lub bez podania przyczyny, w tym z dowolnej z następujących przyczyn: a. X, według własnego uznania, uzna, że naruszyłeś Warunki lub że Twoje korzystanie z Usług Płatnych naruszałoby obowiązujące przepisy prawa; b. X zostanie poproszony lub zobowiązany do wykonania tego przez właściwy sąd, organ regulacyjny lub organ ścigania; c. X napotka nieoczekiwane problemy techniczne lub problemy związane z bezpieczeństwem. d. X ustali, wedle własnego uznania, że Użytkownik naruszył Umowę z Użytkownikiem serwisu X; e. X uważa, według własnego uznania, że użytkownik angażuje się w manipulację lub inne destrukcyjne lub zabronione zachowania ogólnie lub w związku z Usługami płatnymi; f. Stwarzasz ryzyko lub możliwe narażenie prawne dla X; g. Konto Użytkownika powinno zostać usunięte ze względu na postępowanie sprzeczne z prawem. h. Konto Użytkownika powinno zostać usunięte ze względu na długotrwały brak aktywności. i. Świadczenie przez nas Usług Płatnych (w całości lub w części) na rzecz Użytkownika nie jest już komercyjnie opłacalne (według wyłącznego uznania X). 3. Wszystkie transakcje są ostateczne. Wszystkie płatności za Usługi Płatne są ostateczne i nie podlegają zwrotowi ani wymianie, z wyjątkiem przypadków wymaganych przez obowiązujące prawo. Nie udzielamy żadnych gwarancji co do charakteru, jakości, wartości, dostępności ani możliwości świadczenia Usług Płatnych. Za nieużytkowane lub częściowo użytkowane Usługi Płatne (na przykład za częściowo wykorzystany okres subskrypcji) nie przysługują żadne zwroty pieniędzy ani środki. 4. Usług Płatnych nie można przenosić między kontami w serwisie X. Każdy zakup Usługi Płatnej dotyczy jednego konta w serwisie X, tzn. ma zastosowanie tylko do konta użytego w momencie dokonywania zakupu, z wyłączeniem innych kont, do których Użytkownik może mieć dostęp lub które Użytkownik kontroluje. Jeśli Użytkownik posiada lub kontroluje wiele kont i chce mieć dostęp do Usług Płatnych na każdym koncie, musi kupić stosowne Usługi Płatne osobno na każdym koncie. 5. Ograniczenia i obowiązki. a. Użytkownik może kupować i użytkować Usługi Płatne tylko wtedy, gdy zezwalają na to przepisy prawa w kraju zamieszkania Użytkownika, a dodatkowo X oficjalnie świadczy te usługi w tym kraju. W niektórych krajach X może według własnego uznania ograniczyć możliwość zakupu lub dostęp do Usług Płatnych. X może modyfikować listę obsługiwanych krajów. b. Możemy według własnego uznania odrzucać transakcje dotyczące Usług Płatnych oraz anulować lub zaprzestać sprzedaży lub możliwości użytkowania Usług Płatnych. c. Nie możesz zezwalać innym osobom na korzystanie z Twojego konta X w celu uzyskania dostępu do jakiejkolwiek Usługi Płatnej, której dana osoba nie zamówiła. d. Użytkownik nie może kupować ani użytkować Usług Płatnych, jeśli jest osobą, z którą osoby ze Stanów Zjednoczonych nie mogą zawierać transakcji handlowych wskutek sankcji gospodarczych, w tym sankcji nałożonych przez amerykańskie Biuro ds. Kontroli Aktywów Zagranicznych Departamentu Skarbu lub inne uprawnione do tego organy („ Osoba Objęta Zakazem ”). Dotyczy to m.in. osób będących stałymi lub zwyczajowymi rezydentami następujących krajów i regionów: Kuba, Iran, ukraińskie regiony na Krymie, Korea Północna i Syria. Użytkownik oświadcza i gwarantuje, że nie jest Osobą Objętą Zakazem. e. UŻYTKOWNIK OŚWIADCZA, ŻE BĘDZIE WYKORZYSTYWAĆ USŁUGI PŁATNE WYŁĄCZNIE DO CELÓW ZGODNYCH Z PRAWEM I WYŁĄCZNIE ZGODNIE Z TYMI ZASADAMI. Podatki i opłaty . Ponosisz odpowiedzialność i zgadzasz się zapłacić wszelkie obowiązujące podatki, cła, taryfy i opłaty związane z zakupem Usług Płatnych, w tym te, które należy uiścić na rzecz X lub zewnętrznego podmiotu przetwarzającego płatności. Do kwoty tych zalicza się m.in. podatek od towarów i usług (VAT), podatek od od towarów i usług (GST), podatek od sprzedaży, zaliczki na podatek itp. Zależnie od miejsca zamieszkania Użytkownika obowiązkiem X może być zbieranie i zgłaszanie informacji o podatkach od transakcji należnych z tytułu zakupu przez Użytkownika Usług Płatnych. Użytkownik niniejszym udziela X zgody na przekazywanie informacji o koncie i informacji osobistych Użytkownika właściwym organom skarbowym na potrzeby wypełnienia zobowiązań X w zakresie sprawozdawczości i rozliczeń podatkowych. Postanowienia ogólne 1. Informacje kontaktowe. Wszelkie pytania na temat Usług Płatnych lub niniejszych Zasad należy zadawać za pośrednictwem Centrum Pomocy Usług Płatnych X . Jeśli Użytkownik już nabył Usługę Płatną, może się również z nami kontaktować za pomocą łącza pomocy dostępnego w menu nawigacyjnym w oknie konta w serwisie X w sekcji ustawień płatności lub subskrypcji. Ewentualne dalsze pytania można kierować tutaj , wypełniając formularz „Pomoc z płatnymi funkcjami”. 2. ODRZUCENIE ODPOWIEDZIALNOŚCI. W MAKSYMALNYM ZAKRESIE DOZWOLONYM PRZEZ PRZEPISY PRAWA WŁAŚCIWEGO UŻYTKOWANIE I DOSTĘP DO USŁUG PŁATNYCH ODBYWA SIĘ NA WYŁĄCZNE RYZYKO UŻYTKOWNIKA. UŻYTKOWNIK ROZUMIE I ZGADZA SIĘ, ŻE USŁUGI PŁATNE SĄ ŚWIADCZONE UŻYTKOWNIKOWI „W STANIE TAKIM, W JAKIM SĄ” ORAZ „W MIARĘ DOSTĘPNOŚCI”. X ODRZUCA WSZELKIE WYRAŹNE I DOROZUMIANE GWARANCJE I RĘKOJMIE CO DO WARTOŚCI HANDLOWEJ, PRZYDATNOŚCI DO OKREŚLONEGO CELU LUB NIENARUSZANIA PRAW OSÓB TRZECICH. X NIE UDZIELA ŻADNYCH GWARANCJI LUB RĘKOJMI, NIE SKŁADA ŻADNYCH OŚWIADCZEŃ ORAZ ODRZUCA WSZELKĄ ODPOWIEDZIALNOŚĆ, W TYM ODPOWIEDZIALNOŚĆ FINANSOWĄ, W KWESTIACH (I) KOMPLETNOŚCI, RZETELNOŚCI, TERMINOWOŚCI, BEZPIECZEŃSTWA LUB NIEZAWODNOŚCI USŁUG PŁATNYCH, ORAZ (II) TEGO, CZY USŁUGI PŁATNE SPEŁNIAJĄ WYMAGANIA UŻYTKOWNIKA ORAZ CZY BĘDĄ DOSTĘPNE BEZ ZAKŁÓCEŃ, WEWNĘTRZNYCH ZAGROŻEŃ DLA BEZPIECZEŃSTWA I BŁĘDÓW. UŻYTKOWNIK PONOSI ODPOWIEDZIALNOŚĆ Z TYTUŁU UŻYTKOWANIA USŁUGI X, W TYM USŁUG PŁATNYCH, ORAZ WSZELKICH ZAMIESZCZANYCH PRZEZ SIEBIE TREŚCI. 3. OGRANICZENIE ODPOWIEDZIALNOŚCI. W MAKSYMALNYM ZAKRESIE DOZWOLONYM PRZEZ PRZEPISY PRAWA WŁAŚCIWEGO PODMIOTY X NIE PONOSZĄ ODPOWIEDZIALNOŚCI ODSZKODOWAWCZEJ Z TYTUŁU JAKICHKOLWIEK SZKÓD POŚREDNICH, UBOCZNYCH LUB WTÓRNYCH ORAZ ODSZKODOWAŃ SPECJALNYCH LUB KARNYCH; ODPOWIEDZIALNOŚCI Z TYTUŁU BEZPOŚREDNIEJ LUB POŚREDNIEJ UTRATY ZYSKÓW LUB PRZYCHODÓW LUB ODPOWIEDZIALNOŚCI Z TYTUŁU UTRATY DANYCH, MOŻLIWOŚCI UŻYTKOWANIA, WARTOŚCI FIRMY LUB INNYCH WARTOŚCI NIEMATERIALNYCH WYNIKAJĄCYCH Z (i) UŻYTKOWANIA LUB DOSTĘPU DO USŁUG LUB NIEMOŻNOŚCI UŻYTKOWANIA LUB DOSTĘPU DO USŁUG PŁATNYCH; (ii) POSTĘPOWANIA OSÓB TRZECICH LUB TREŚCI ZAMIESZCZANYCH PRZEZ OSOBY TRZECIE W USŁUGACH PŁATNYCH, W TYM SZKALUJĄCEGO, OBRAŹLIWEGO LUB NIELEGALNEGO POSTĘPOWANIA INNYCH UŻYTKOWNIKÓW LUB OSÓB TRZECICH; (iii) JAKICHKOLWIEK TREŚCI POBRANYCH Z USŁUG PŁATNYCH LUB (iv) NIEAUTORYZOWANEGO UŻYTKOWANIA, MODYFIKOWANIA LUB UZYSKIWANIA DOSTĘPU DO INFORMACJI LUB TREŚCI PRZESYŁANYCH PRZEZ UŻYTKOWNIKA. TERMIN „USŁUGI PŁATNE” OZNACZA WYŁĄCZNIE FUNKCJE OFEROWANE PRZEZ X Z WYŁĄCZENIEM WSZELKICH TREŚCI, DO KTÓRYCH UŻYTKOWNIK UZYSKUJE DOSTĘP LUB KTÓRE UŻYTKUJE ZA POMOCĄ TYCH FUNKCJI. W ŻADNYM WYPADKU ŁĄCZNA ODPOWIEDZIALNOŚĆ FINANSOWA PODMIOTÓW X NIE PRZEKROCZY WIĘKSZEJ Z NASTĘPUJĄCYCH KWOT: STO DOLARÓW AMERYKAŃSKICH (100,00 USD) LUB KWOTY EWENTUALNIE ZAPŁACONEJ X W CIĄGU OSTATNICH SZEŚCIU MIESIĘCY ZA USŁUGI PŁATNE STANOWIĄCE PODSTAWĘ ROSZCZENIA. OGRANICZENIA W TYM PODPUNKCIE OBOWIĄZUJĄ BEZ WZGLĘDU NA PRZYJĘTĄ PODSTAWĘ ODPOWIEDZIALNOŚCI, W TYM Z TYTUŁU GWARANCJI, UMOWY, USTAWY, DELIKTU (ŁĄCZNIE Z ZANIEDBANIEM) LUB INNEJ PODSTAWY, ORAZ BEZ WZGLĘDU NA FAKT, CZY PODMIOTY X ZOSTAŁY POINFORMOWANE O MOŻLIWOŚCI WYSTĄPIENIA TAKICH SZKÓD, TAKŻE W PRZYPADKU, GDY OKREŚLONE W NINIEJSZYCH ZASADACH UŻYTKOWANIA UPRAWNIENIE NIE SPEŁNIŁO SWOJEGO ZASADNICZEGO CELU. TERMIN „PODMIOTY X” OZNACZA X CORP. ORAZ JEDNOSTKI MACIERZYSTE, JEDNOSTKI ZALEŻNE, SPÓŁKI POWIĄZANE, CZŁONKÓW ŚCISŁEGO KIEROWNICTWA, DYREKTORÓW, PRACOWNIKÓW, PEŁNOMOCNIKÓW, PRZEDSTAWICIELI, PARTNERÓW I LICENCJODAWCÓW X CORP. PRZEPISY PRAWA WŁAŚCIWEGO W MIEJSCU ZAMIESZKANIA UŻYTKOWNIKA MOGĄ NIE ZEZWALAĆ NA NIEKTÓRE OGRANICZENIA ODPOWIEDZIALNOŚCI. W ZAKRESIE WYMAGANYM PRZEZ PRZEPISY PRAWA WŁAŚCIWEGO W MIEJSCU ZAMIESZKANIA UŻYTKOWNIKA POWYŻSZE POSTANOWIENIA NIE OGRANICZAJĄ ODPOWIEDZIALNOŚCI PODMIOTÓW X ZA OSZUSTWO, ŚWIADOME WPROWADZENIE W BŁĄD, ŚMIERĆ LUB SZKODY NA OSOBIE SPOWODOWANE NASZYM ZANIEDBANIEM, RAŻĄCYM ZANIEDBANIEM LUB DZIAŁANIAMI UMYŚLNYMI. W MAKSYMALNYM ZAKRESIE DOZWOLONYM PRZEZ PRZEPISY PRAWA WŁAŚCIWEGO ŁĄCZNA ODPOWIEDZIALNOŚĆ PODMIOTÓW X Z TYTUŁU WSZELKICH NIEMOŻLIWYCH DO WYŁĄCZENIA GWARANCJI LUB RĘKOJMI JEST OGRANICZONA DO KWOTY STU DOLARÓW AMERYKAŃSKICH (100,00 USD). 4. Informacja dotycząca Apple. W zakresie, w jakim Użytkownik nabył Usługi Płatne lub je użytkuje lub uzyskuje do nich dostęp na urządzeniu z systemem operacyjnym iOS, Użytkownik dodatkowo zgadza się na postanowienia zawarte w tym punkcie. Użytkownik zgadza się, że Zasady dotyczą wyłącznie relacji między Użytkownikiem a nami, a nie Apple, i Apple nie odpowiada w żaden sposób za Usługi Płatne ani ich treść. Apple nie ma żadnych zobowiązań do świadczenia jakiejkolwiek formy wsparcia technicznego w zakresie Usług Płatnych. Jeśli Usługi Płatne w jakikolwiek sposób nie spełniają warunków gwarancji, wówczas Użytkownik może powiadomić o tym Apple, a Apple zwróci Użytkownikowi cenę zakupu, przy czym w maksymalnym zakresie dozwolonym przez prawo właściwe Apple nie ma żadnych zobowiązań gwarancyjnych w zakresie Usług Płatnych. Apple nie musi rozpatrywać żadnych roszczeń zgłaszanych przez Użytkownika lub osoby trzecie w związku z Usługami Płatnymi posiadanymi lub użytkowanymi przez Użytkownika, w tym (i) roszczeń z tytułu odpowiedzialności za produkt; (ii) skarg, że Usługi Płatne nie spełniają wymogów prawnych; oraz (iii) roszczeń wynikających z przepisów prawa ochrony konsumenta i podobnych przepisów. Apple nie musi badać zasadności, podejmować obrony, zawierać ugód ani podważać zasadności jakichkolwiek roszczeń osób trzecich, że Usługi Płatne lub posiadanie i użytkowanie przez Użytkownika aplikacji mobilnej narusza prawa własności intelektualnej osób trzecich. Podczas użytkowania Usług Płatnych Użytkownik zgadza się przestrzegać wszelkich postanowień określonych przez osoby trzecie. Apple i podmioty zależne Apple są zewnętrznymi beneficjentami Zasad, a z chwilą zaakceptowania Zasad przez Użytkownika Apple nabywa i w sposób dorozumiany akceptuje prawo do egzekwowania Zasad od Użytkownika. Użytkownik niniejszym oświadcza i gwarantuje, że (i) nie mieszka w kraju objętym embargiem nałożonym przez administrację Stanów Zjednoczonych ani umieszczonym przez administrację Stanów Zjednoczonych na liście krajów "popierających terroryzm"; (ii) nie figuruje na żadnej prowadzonej przez administrację Stanów Zjednoczonych liście osób lub podmiotów objętych zakazem lub ograniczeniami. 5. Sprzeczność postanowień. Jeśli występują sprzeczności między Zasadami użytkowania dla kupujących w serwisie X a postanowieniami Umowy z Użytkownikiem serwisu X, wówczas wyłącznie w zakresie użytkowania Usług Płatnych przez Użytkownika pierwszeństwo mają Zasady użytkowania dla kupujących w serwisie X. 6. ROZSTRZYGANIE SPORÓW I ZRZECZENIE SIĘ PRAWA DO POWÓDZTWA ZBIOROWEGO a. Wstępne rozstrzyganie sporów. Większość sporów między Tobą a X może być rozwiązywana w sposób nieformalny. Możesz skontaktować się z nami, pisząc do Płatnej pomocy technicznej tutaj . Kontaktując się z nami, Użytkownik powinien pokrótce opisać charakter i podstawę skargi, a także podać swoje informacje kontaktowe oraz wnioskowaną formę oczekiwanego świadczenia. W ramach tej procedury strony dołożą wszelkich starań, aby rozstrzygnąć wszelkie spory, roszczenia lub kontrowersje wynikające z niniejszych Zasad bądź powstałe w związku z niniejszymi Zasadami i/lub uczestnictwem Użytkownika w Programie (jednostkowo „ Spór ”, łącznie „ Spory ”). Użytkownik i X zgadzają się, że udział w tej nieformalnej procedurze w dobrej wierze jest wymagany i musi zostać ukończony zgodnie z powyższymi postanowieniami, zanim którakolwiek ze stron będzie mogła wszcząć postępowanie sądowe w związku z jakimkolwiek Sporem, z wyjątkiem wniosków o wydanie nakazu sądowego w nagłych wypadkach („ Spór objęty wyłączeniem ”). Jeśli nie uda nam się rozwiązać Sporu (innego niż Spór podlegający wyłączeniu) w ciągu trzydziestu (30) dni od daty rozpoczęcia procedury nieformalnego rozstrzygania Sporu na mocy postanowień określonych w powyższej sekcji Początkowe rozstrzyganie sporów, Użytkownik lub X może zainicjować postępowanie sądowe. b. Wybór prawa i sądu . NALEŻY UWAŻNIE PRZECZYTAĆ TREŚĆ TEGO PUNKTU, PONIEWAŻ MOŻE ISTOTNIE WPŁYWAĆ NA PRAWA UŻYTKOWNIKA, W TYM PRAWO DO WNOSZENIA POWÓDZTW SĄDOWYCH. Niezależnie od wszelkich innym umów między Użytkownikiem a nami, które stanowią inaczej, prawem właściwym do wykładni niniejszych Zasad Użytkowania i rozstrzygania sporów między nami a Użytkownikiem jest prawo stanu Teksas z wyjątkiem zawartych w nim norm prawa kolizyjnego. Wszelkie spory związane z niniejszymi Zasadami, w tym m.in. spory, roszczenia lub kontrowersje bezpośrednio lub pośrednio powstałe w związku z niniejszymi Zasadami, będą rozstrzygane wyłącznie w sądach federalnych lub stanowych w hrabstwie Tarrant w Teksasie w Stanach Zjednoczonych, a Użytkownik zgadza się na ich właściwość osobową i dobrowolnie zrzeka się swojego prawa wnoszenia zarzutów co do niewłaściwości takiego sądu. Bez uszczerbku dla powyższego, użytkownik zgadza się, że według własnego uznania X może wnieść wszelkie roszczenia, podstawy powództwa lub spory, które mamy przeciwko użytkownikowi w dowolnym właściwym sądzie w kraju zamieszkania użytkownika, który ma jurysdykcję i miejsce do rozpatrzenia roszczenia. Jeśli jesteś przedstawicielem rządu federalnego, stanowego lub lokalnego w Stanach Zjednoczonych w ramach pełnienia obowiązków służbowych i z przyczyn prawnych nie możesz zaakceptować powyższych klauzul dotyczących prawa właściwego, jurysdykcji lub miejsca rozstrzygnięcia sporu, to klauzule te nie mają do Ciebie zastosowania. W przypadku takich podmiotów rządu federalnego USA niniejsza Umowa i wszelkie działania z nią związane będą regulowane prawem Stanów Zjednoczonych Ameryki (bez odniesienia do kolizji praw), a w przypadku braku prawa federalnego i w zakresie dozwolonym na mocy prawa federalnego, prawem stanu Teksas (z wyłączeniem wyboru prawa). c. MASZ DWA LATA NA WNIESIENIE ROSZCZENIA PRZECIWKO X . Użytkownik musi wnieść wszelkie roszczenia przeciwko X wynikające z niniejszych Warunków lub z nimi związane w ciągu dwóch (2) lat od daty wystąpienia zdarzenia lub faktów stanowiących podstawę sporu, chyba że obowiązujące prawo stanowi, że normalny okres przedawnienia roszczenia nie może zostać skrócony w drodze umowy. Jeśli Użytkownik nie wniesie roszczenia w tym terminie, będzie to oznaczać, że na zawsze zrzeka się prawa do dochodzenia jakichkolwiek roszczeń lub powództw, dowolnego rodzaju bądź charakteru, na podstawie tych zdarzeń lub faktów, takie roszczenia lub powództwa zostaną trwale zablokowane, a X nie będzie ponosić żadnej odpowiedzialności z tytułu tego roszczenia. d. Zrzeczenie się prawa do udziału w powództwach zbiorowych . W zakresie dozwolonym przez przepisy prawa Użytkownik dobrowolnie zrzeka się również prawa do udziału w charakterze powoda lub członka grupy w jakimkolwiek ewentualnym powództwie zbiorowym (bez względu na to, czy udział w nim jest obligatoryjny, czy dobrowolny) lub powództwie przedstawicielskim. Zasady użytkowania dla kupujących w serwisie X Jeśli Użytkownik mieszka w kraju należącym do Unii Europejskiej, kraju należącym do EFTA lub w Zjednoczonym Królestwie X umożliwia Użytkownikowi dostęp do określonych funkcji w zamian za uiszczenie jednorazowej lub cyklicznej opłaty, zależnie od konkretnej funkcji (jednostkowo „ Usługa Płatna ”, a zbiorczo „ Usługi Płatne ”). Na przykład usługa X Premium (zgodnie z poniższą definicją) i Subskrypcje będą uważane za „Usługi Płatne”. W zakresie, w jakim Użytkownik zarejestruje się w Usłudze płatnej lub użytkuje Usługę płatną, użytkowanie przez Użytkownika Usługi płatnej i zawieranie wszelkich powiązanych transakcji podlega (i) postanowieniom tego dokumentu, w tym postanowieniom dotyczącym poszczególnych kupowanych przez Użytkownika Usług płatnych, które to postanowienia wyszczególniono poniżej (łącznie „ Zasady użytkowania dla kupujących w serwisie X ”), oraz (ii) stosownym Zasadom użytkowania serwisu X , Polityce prywatności serwisu X , Zasadom i politykom serwisu X oraz wszelkim politykom stanowiącym integralną część tych dokumentów (łącznie „ Umowa z Użytkownikiem serwisu X ”). Niniejsze Zasady użytkowania dla kupujących w serwisie X oraz Umowa z Użytkownikiem serwisu X będą łącznie określane w tym dokumencie jako „ Zasady ”. „ X ” oznacza podmiot X, który świadczy na Twoją rzecz Usługi Płatne. Należy uważnie przeczytać Zasady użytkowania dla kupujących w serwisie X oraz dokładnie zrozumieć zawarte w nich postanowienia i wyjątki. JEŚLI UŻYTKOWNIK MIESZKA W UNII EUROPEJSKIEJ, KRAJU NALEŻĄCYM DO EFTA LUB ZJEDNOCZONYM KRÓLESTWIE, NINIEJSZE ZASADY ZAWIERAJĄ WAŻNE INFORMACJE DOTYCZĄCE ROZSTRZYGANIA SPORÓW, W TYM DOBROWOLNEGO ZRZECZENIA SIĘ PRAWA DO WNOSZENIA ROSZCZEŃ W RAMACH POWÓDZTW ZBIOROWYCH ORAZ OGRANICZENIA PRAWA DO WNOSZENIA ROSZCZEŃ PRZECIWKO X DO 1 ROKU OD ZAISTNIENIA STOSOWNYCH ZDARZEŃ. TE ZASADY WPŁYWAJĄ NA PRAWA I ZOBOWIĄZANIA UŻYTKOWNIKA W RAZIE JAKIEGOKOLWIEK SPORU Z X. SZCZEGÓŁOWY OPIS TYCH POSTANOWIEŃ ZNAJDUJE SIĘ W PUNKCIE 6 POSTANOWIEŃ OGÓLNYCH. Akceptacja . Użytkując lub uzyskując dostęp do Usług płatnych za pośrednictwem X, dokonując płatności za te usługi i/lub klikając przycisk w celu dokonania jednorazowego zakupu bądź uregulowania jednej z cyklicznych opłat za subskrypcję Usługi płatnej świadczonej przez X, Użytkownik zgadza się przestrzegać tych Zasad. Jeśli Użytkownik nie rozumie treści Zasad albo nie akceptuje ich którejkolwiek części, nie może użytkować ani uzyskiwać dostępu do żadnych Usług Płatnych. Aby zakupić i użytkować Usługę Płatną, Użytkownik musi (i) mieć ukończone 18 lat lub być w wieku decydującym o pełnoletniości według przepisów w kraju lub regionie, w którym Użytkownik mieszka, lub (ii) mieć jednoznaczną zgodę rodzica lub opiekuna na zakup i użytkowanie Usługi Płatnej. Jeśli Użytkownik jest rodzicem lub opiekunem prawnym i pozwoli swojemu dziecku (lub innemu dziecku, którego jest opiekunem) na zakup lub użytkowanie Usługi Płatnej, zgadza się, że Zasady mają do Użytkownika zastosowanie, będzie ich przestrzegać, ponosi odpowiedzialność za czynności wykonywane przez dziecko w Usłudze Płatnej oraz dopilnuje, aby również dziecko przestrzegało Zasad. W każdym przypadku, tak jak to określa punkt „Kto może użytkować Usługi” w Zasadach użytkowania serwisu X, osoby chcące użytkować Usługi X muszą mieć ukończone 13 lat. Jeśli Użytkownik akceptuje Zasady użytkowania dla kupujących w serwisie X i użytkuje Usługi Płatne w imieniu przedsiębiorstwa, organizacji, organu administracji publicznej lub innej osoby prawnej, wówczas oświadcza i gwarantuje, że ma do tego wszelkie upoważnienia oraz może związać taki podmiot Zasadami użytkowania dla kupujących w serwisie X, i wtedy termin „Użytkownik” stosowany w Zasadach użytkowania dla kupujących w serwisie X odnosi się do tego podmiotu. Podmiot X zawierający umowę . Użytkownik wyraża zgodę na te Zasady użytkowania dla kupujących w serwisie X, zawierając umowę z podmiotem właściwym dla miejsca zamieszkania Użytkownika, zgodnie z listą zamieszczoną poniżej. Podmiot ten będzie świadczyć Użytkownikowi Usługi Płatne. Zgodnie z niniejszymi Zasadami użytkowania dla kupujących w serwisie X żaden inny podmiot nie jest związany jakimikolwiek zobowiązaniami wobec Użytkownika. Lokalizacja Użytkownika Unia Europejska, kraje EFTA lub Zjednoczone Królestwo Podmiot zawierający umowę X Internet Unlimited Company z siedzibą pod adresem One Cumberland Place, Fenian Street, Dublin 2, D02 AX07 Irlandia Zmiany Warunków, Usług płatnych i cen 1. Zmiany Zasad. X może od czasu do czasu zmieniać niniejsze Zasady użytkowania dla kupujących w serwisie X z ważnych i uzasadnionych powodów. Ważnym i uzasadnionym powodem może być: (i) zmiana w naszych usługach, na przykład spowodowana pracami technicznymi, związanymi z zabezpieczeniami lub operacyjnymi, (ii) eliminacja błędów technicznych, (iii) zmiana w naszej działalności, na przykład spowodowana zmianami politycznymi, finansowymi bądź innymi zmianami kierunkowymi, (iv) zmiana sytuacji prawnej, na przykład w wyniku zmiany prawa, wniosku od oficjalnej agencji lub decyzji sądu, oraz (v) optymalizacja środowiska użytkownika w wyniku implementacji nowych funkcji. Zmiany nie będą działać z mocą wsteczną, a użytkowanie Usług Płatnych i wszelkie związane z tym transakcje będą podlegać najnowszej wersji Zasad użytkowania dla kupujących w serwisie X dostępnej pod adresem legal.x.com/purchaser-terms . W przypadku modyfikowania lub poprawiania niniejszych Warunków po wyrażeniu na nie zgody przez użytkownika (na przykład, jeśli warunki te zostaną zmodyfikowane po wykupieniu subskrypcji), zobowiązujemy się powiadomić użytkownika do 30 dni (w zależności od konkretnych zmian) przed wejściem w życie istotnych zmian w niniejszych warunkach, wyznaczając jednocześnie użytkownikowi rozsądny termin w odniesieniu do zmian i powiadamiając go o konsekwencjach dalszego użytkowania po upływie tego terminu. Takie powiadomienie może zostać przekazane drogą elektroniczną, w tym, między innymi, za pośrednictwem powiadomienia w ramach usługi lub wiadomości e-mail wysłanej na adres e-mail powiązany z kontem użytkownika. Dalsze korzystanie z Usług płatnych po upływie wyżej wymienionego terminu oznacza, że Użytkownik zgadza się przestrzegać zmienionych Zasad użytkowania dla kupujących w serwisie X. Jeśli Użytkownik nie zgadza się na zmiany w Zasadach użytkowania dla kupujących w serwisie X, musi przestać korzystać z Usług płatnych lub uzyskiwać do nich dostęp (lub przestać kontynuować korzystanie z nich lub uzyskiwanie do niech dostępu). Zasady użytkowania dla kupujących w serwisie X zostały sporządzone w języku angielskim oraz po przetłumaczeniu udostępnione w wielu innych językach. X dokłada wszelkich starań, aby tłumaczenia były w jak największym stopniu zgodne z oryginalną wersją angielską. W razie wystąpienia jakichkolwiek rozbieżności lub niespójności wersja angielska Zasad użytkowania dla kupujących w serwisie X ma jednak znaczenie rozstrzygające. Użytkownik zgadza się, że językiem odniesienia dla wykładni postanowień Zasad użytkowania dla kupujących w serwisie X jest język angielski. 2. Zmiany w usługach płatnych. Nasze Usługi płatne oraz nasze produkty i usługi stale ewoluują. X może zmienić Usługi płatne z uzasadnionego i ważnego powodu. Takim ważnym i uzasadnionym powodem może być: (i) zmiana spowodowana pracami technicznymi, związanymi z zabezpieczeniami lub operacyjnymi, (ii) eliminacja błędów technicznych, (iii) dostosowanie do zmienionej sytuacji prawnej, na przykład spowodowanej zmianą prawa, wnioskiem od oficjalnej agencji lub decyzją sądu, (iv) optymalizacja środowiska użytkownika w wyniku implementacji nowych funkcji, oraz (v) zmiana w naszej działalności, na przykład spowodowana zmianami politycznymi, finansowymi bądź innymi zmianami kierunkowymi. Powiadomimy Cię o wszelkich zmianach w Usługach Płatnych do 30 dni przed ich wejściem w życie, na przykład za pomocą powiadomienia o usłudze lub wiadomości e-mail wysłanej na adres e-mail powiązany z Twoim kontem, określając cechy i datę wejścia w życie zmian oraz informując Cię o ewentualnym prawie do wypowiedzenia subskrypcji. Termin może ulec skróceniu w przypadku zmian związanych z bezpieczeństwem. Następujące zdarzenia nie będą uznawane za zmiany w Usługach płatnych w rozumieniu niniejszego postanowienia: (i) zmiany mające wpływ na podstawowy charakter Usług płatnych i zasadnicze cechy usługi dostarczanej przez X, oraz (ii) trwałe zaprzestanie świadczenia usług. X nie ponosi odpowiedzialności wobec Użytkownika za jakiekolwiek modyfikacje, zawieszenie lub zaprzestanie świadczenia Usług płatnych. W miejscach, gdzie jest to wymagane przez prawo, powyższe ograniczenie odpowiedzialności nie ma zastosowania (i) do odszkodowania za przewidywalne szkody w przypadku naruszenia obowiązków spowodowanego nieznacznym niedbalstwem, jeśli ich spełnienie jest niezbędne do prawidłowego wykonania umowy, a użytkownicy mogą oczekiwać ich spełnienia (istotne obowiązki umowne) przez X lub jego przedstawicieli prawnych bądź osoby działające w jego imieniu, oraz (ii) odpowiedzialności X za (a) szkody wynikające z narażenia na szwank życia, ciała lub zdrowia, a także za szkody spowodowane umyślnie lub w wyniku rażącego niedbalstwa ze strony X, jego przedstawicieli prawnych lub osób działających w jego imieniu, oraz (b) szkody wynikające z niezgodności z gwarancją lub gwarantowaną charakterystyką bądź w wyniku istnienia nieuczciwie zatajonej wady. Szczegółowe warunki (zawarte poniżej) dotyczące konkretnej Usługi płatnej określają, w jaki sposób można anulować subskrypcję lub, w stosownych przypadkach, ubiegać się o zwrot kosztów. 3. Zmiany w cenniku. Ceny Usług Płatnych, w tym cykliczne opłaty subskrypcyjne, mogą ulegać okresowym zmianom ze względu na zmianę kosztów związanych z eksploatacją, konserwacją, świadczeniem usług technicznych, względami biznesowymi oraz opłatami pobieranymi przez osoby trzecie lub opłatami ustawowymi, według naszego uzasadnionego uznania. W przypadku wzrostu kosztów X zastrzega sobie prawo do zmiany cen za usługi płatne. X powiadomi Cię o wszelkich zmianach cen na piśmie do 30 dni przed ich wejściem w życie, na przykład za pomocą powiadomienia o usłudze lub wiadomości e-mail wysłanej na adres e-mail powiązany z Twoim kontem, informując o Twoich prawach i konsekwencjach ich nieskorzystania. W przypadku zmiany ceny Płatnej usługi Użytkownik może zakończyć jej subskrypcję lub wypowiedzieć Umowę z użytkownikiem do 24 godzin przed rozpoczęciem kolejnego cyklu rozliczeniowego, pod warunkiem, że anulowanie nastąpi w ciągu 30 dni od daty otrzymania powiadomienia. W przeciwnym razie zmiana ceny wejdzie w życie w terminie określonym w powiadomieniu. W przypadku usług subskrypcyjnych zmiany cen wejdą w życie z początkiem kolejnego okresu subskrypcji następującego po dacie wejścia w życie zmiany ceny. Warunki płatności . X oferuje różne opcje płatności, które mogą różnić się w zależności od Usługi Płatnej, urządzenia, systemu operacyjnego, lokalizacji geograficznej lub innych czynników dotyczących Użytkownika. W dostępnym zakresie (X może bowiem udostępniać różne metody zakupu) te opcje płatności mogą obejmować możliwość korzystania z funkcji „Płatność w aplikacji” oferowanej przez Google lub Apple lub dokonywania płatności internetowych za pośrednictwem zewnętrznego operatora płatności współpracującego z X, czyli firmy Stripe ( www.stripe.com , dalej „ Stripe ”). Dokonując płatności, Użytkownik wyraźnie zgadza się (i) zapłacić wskazaną cenę za Usługę Płatną wraz z wszelkimi dodatkowymi kwotami związanymi z obowiązującymi podatkami, opłatami za karty kredytowe, opłatami bankowymi, opłatami za transakcje zagraniczne, opłatami za wymianę walut oraz wahaniami kursów walut; oraz (ii) przestrzegać wszelkich zasad użytkowania, polityk prywatności lub innych umów lub ograniczeń prawnych (w tym dodatkowych ograniczeń wiekowych) nałożonych przez Google, Apple lub Stripe (jako zewnętrzni operatorzy płatności w imieniu X) w związku ze stosowaniem przez Użytkownika danej metody płatności (jeśli na przykład Użytkownik zdecyduje się na dokonanie płatności za pośrednictwem funkcji zakupów w aplikacji Apple, wyraża wówczas zgodę na przestrzeganie wszelkich stosownych postanowień, wymogów lub ograniczeń nałożonych przez Apple). Wszelkie prywatne dane osobowe, które Użytkownik przekazuje w związku z użytkowaniem Usług Płatnych, w tym w szczególności wszelkie dane przekazywane w związku z płatnością, będą przetwarzane zgodnie z Polityką prywatności X. X może udostępniać informacje dotyczące płatności dostawcom usług płatniczych w celu przetwarzania płatności; wykrywania i badania oszustw lub innych niedozwolonych działań oraz zapobiegania im; ułatwiania rozstrzygania sporów, takich jak obciążenia zwrotne lub zwroty środków oraz do innych celów związanych z akceptacją kart kredytowych, kart debetowych lub kont ACH. Do obowiązków użytkownika należy upewnienie się, że jego dane bankowe, dane dotyczące karty kredytowej, karty debetowej i/lub inne informacje dotyczące płatności są zawsze aktualne, kompletne i poprawne. Jeśli użytkownik dokonuje płatności za Usługi płatne, możemy uzyskać informacje na temat transakcji użytkownika, takie jak data jej wykonania, data wygaśnięcia lub automatycznego odnowienia subskrypcji, platforma, na której użytkownik dokonał zakupu, a także inne informacje. X nie ponosi odpowiedzialności za błędy ani opóźnienia popełnione przez operatora płatności, Apple App Store lub sklep Google Play, bank, operatora karty kredytowej lub sieć płatniczą. Użytkownik powinien zapoznać się z poniższymi Warunkami korzystania z poszczególnych Usług płatnych, aby dowiedzieć się, jakie warunki płatności obowiązują w odniesieniu do każdej z nich, w tym warunki odnawiania subskrypcji oraz inne istotne zasady. Zastosowanie Umowy z Użytkownikiem X, wypowiedzenie, brak możliwości zwrotu pieniędzy, wiele kont na X oraz ograniczenia 1. Umowa z Użytkownikiem serwisu X ma zastosowanie do Użytkownika . UŻYTKOWNIK ZAWSZE MUSI PRZESTRZEGAĆ POSTANOWIEŃ UMOWY Z UŻYTKOWNIKIEM SERWISU X. Umowa z Użytkownikiem serwisu X ma zastosowanie do każdego przypadku użytkowania przez Użytkownika Usługi X, w tym Usług Płatnych i funkcji. Jeśli Użytkownik nie przestrzega postanowień Umowy z Użytkownikiem serwisu X lub X ma uzasadnione podstawy sądzić, że doszło do naruszenia tych postanowień, Użytkownik musi się liczyć z anulowaniem dostępu do Usług Płatnych. Każdemu takiemu anulowaniu mogą towarzyszyć inne działania egzekucyjne podejmowane przez X wobec Użytkownika na mocy Umowy z Użytkownikiem serwisu X. Użytkownik może wtedy utracić korzyści zawarte w Usługach Płatnych oraz nie będzie uprawniony do zwrotu żadnych kwot zapłaconych (lub przedpłaconych) za Usługi Płatne. 2. Dlaczego X może wypowiedzieć dostęp Użytkownika do Usług płatnych. X może zawiesić lub wypowiedzieć Użytkownikowi dostęp do Usług płatnych albo zaprzestać świadczenia na rzecz Użytkownika całości lub części Usług płatnych bądź podjąć inne działanie, które uzna za właściwe, w tym na przykład zawiesić konto Użytkownika (bez ponoszenia z tego tytułu żadnej odpowiedzialności), w dowolnym momencie, z dowolnego powodu lub bez podania powodu, w tym z dowolnego z następujących uzasadnionych powodów: a. X, według własnego uznania, uzna, że naruszyłeś Warunki lub że Twoje korzystanie z Usług Płatnych naruszałoby obowiązujące przepisy prawa; b. X zostanie poproszony lub zobowiązany do wykonania tego przez właściwy sąd, organ regulacyjny lub organ ścigania; c. X napotka nieoczekiwane problemy techniczne lub problemy związane z bezpieczeństwem. d. X ustali, wedle własnego uznania, że Użytkownik naruszył Umowę z Użytkownikiem serwisu X; e. X ustali, że zaistniały ważne powody, w tym że Użytkownik angażuje się w manipulowanie, granie lub inne zakłócające bądź zabronione zachowania w związku z Usługami płatnymi; f. Stwarzasz ryzyko lub możliwe narażenie prawne dla X; g. Konto Użytkownika powinno zostać usunięte ze względu na postępowanie sprzeczne z prawem. h. Konto Użytkownika powinno zostać usunięte ze względu na długotrwały brak aktywności. i. Świadczenie przez nas Usług Płatnych (w całości lub w części) na rzecz Użytkownika nie jest już komercyjnie opłacalne (według wyłącznego uznania X). 3. Wszystkie transakcje są ostateczne. Wszystkie płatności za Usługi Płatne są ostateczne i nie podlegają zwrotowi ani wymianie, z wyjątkiem przypadków wymaganych przez obowiązujące prawo. Nie udzielamy żadnych gwarancji co do charakteru, jakości, wartości, dostępności ani możliwości świadczenia Usług Płatnych. Za nieużytkowane lub częściowo użytkowane Usługi Płatne (na przykład za częściowo wykorzystany okres subskrypcji) nie przysługują żadne zwroty pieniędzy ani środki. 4. Usług Płatnych nie można przenosić między kontami w serwisie X. Każdy zakup Usługi Płatnej dotyczy jednego konta w serwisie X, tzn. ma zastosowanie tylko do konta użytego w momencie dokonywania zakupu, z wyłączeniem innych kont, do których Użytkownik może mieć dostęp lub które Użytkownik kontroluje. Jeśli Użytkownik posiada lub kontroluje wiele kont i chce mieć dostęp do Usług Płatnych na każdym koncie, musi kupić stosowne Usługi Płatne osobno na każdym koncie. 5. Ograniczenia i obowiązki. a. Użytkownik może kupować i użytkować Usługi Płatne tylko wtedy, gdy zezwalają na to przepisy prawa w kraju zamieszkania Użytkownika, a dodatkowo X oficjalnie świadczy te usługi w tym kraju. W niektórych krajach X może według własnego uznania ograniczyć możliwość zakupu lub dostęp do Usług Płatnych. X może modyfikować listę obsługiwanych krajów. b. Możemy według własnego uznania odrzucać transakcje dotyczące Usług Płatnych oraz anulować lub zaprzestać sprzedaży lub możliwości użytkowania Usług Płatnych. c. Nie możesz zezwalać innym osobom na korzystanie z Twojego konta X w celu uzyskania dostępu do jakiejkolwiek Usługi Płatnej, której dana osoba nie zamówiła. d. Użytkownik nie może kupować ani użytkować Usług Płatnych, jeśli jest osobą, z którą osoby ze Stanów Zjed | 2026-01-13T08:48:38 |
https://www.lob.com/print-delivery-network | Production + Tracking: Nationwide Print Delivery Network | Lob Lob's website experience is not optimized for Internet Explorer. Please choose another browser. 2/12 @ 10 AM PT | State of Direct Mail: Business Insights 2026 Webinar | Register Product Build Create + personalize your mail Route Optimize efficiency with Postal IQ Fulfill Speed delivery and track the results Take a product tour Get a sneak peek of our intuitive platform API's & Integrations Address Verification Security Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate INDUSTRIES USE CASES Marketing In-House Marketing Agencies and Consultants Operations In-House Operations Operations Service Providers Resources State of Direct Mail Ebooks + Guides Case Studies Blog Direct Mail Template Gallery Newsroom All Resources Help Center State of Direct Mail 2025: Consumer Insights Edition See what’s driving Gen Z and Millennial engagement in the full State of Direct Mail 2025 report. Read it now Pricing Contact Login Get started for free Book a demo Book a demo Production + Tracking Deliver mail up to speed – and up to your standards Lob is changing how direct mail is done with a nationwide Print Delivery Network that produces high-quality mail fast, plus full visibility into every send. Book a demo Get started for free Ready to cut direct mail lead time? Move fast without sacrificing quality. Here’s how we help you do it. Discover Postal IQ Send fast + at scale With printers across the U.S., your mail moves quickly – even at high volumes or when plans change. Leave quality to us From color consistency to sharp finishes, our quality checks hold printers to the toughest standards in the industry, so each piece is perfect. Keep costs efficient By using Postal IQ to route to printers near your final destination, we keep costs stable and transit time down, no matter how much mail you send. Stay in the know Get full visibility down to the mailpiece by tracking every step in the production process from pre-sort to transit to delivery. From start to finish: How we deliver quality Top-tier print standards Lob’s printers follow strict guidelines so that every mailpiece is spot on. Color accuracy: We use Chromachecker standards and GRACoL 2013, so your colors stay vibrant and consistent across our network. Finishing touches: From precise 1/8” trimming to secure glue and UV coating, we ensure your mail is protected during transit and polished when it arrives. Tracking and visibility Slice and dice your data by key filters or get a full deliverability report, all directly from your Dashboard. Tracking transparency: Follow each mailpiece or campaign with 8 essential tracking events. Mail speed checks: Monitor how quickly your mail moves from being sent to marked as processed for delivery, pinpointing efficiency and flagging any delays. Built-in accountability We’re rigorous about keeping our network – and your mail – on point. SLA adherence: Automated event mail tracking system keeps partners accountable. Preventative maintenance: We oversee regular on-site quality audits. Monthly quality reviews: We sit down with our printers to review performance metrics and adherence to industry standards. USPS expertise Our Print Delivery Network team has deep ties to the USPS. That close relationship gives us early insight into service standards changes, delivery updates, and other operational shifts – so your mail keeps moving, no surprises. We put customer data security first When mail moves, so does PII. Here’s how we keep it safe. Encryption everywhere Lob protects your data using industry-leading encryption standards for all data in transit. SOC 2 type 2 audits Our security controls are assessed annually through independent reviews. HIPAA/HITECH compliance We support healthcare customers by undergoing annual HIPAA/HITECH privacy audits. Print partner security Our print and logistics partners are regularly audited to verify compliance with strict standards. Print Delivery Network FAQs What is a print network? A print network is a connected system of print vendors that work together to produce and deliver print collateral like brochures and postcards. What is direct mail printing? Direct mail printing is the process of producing physical mail – like postcards, letters, and self-mailers – delivery to targeted recipients through services like USPS. What is Lob's Print Delivery Network (PDN)? Lob's Print Delivery Network (PDN) is the backbone of our Print & Mail offering. By building an integrated, distributed network of professional printers, we simplify client print operations and vendor management on behalf of our customers. Qualified commercial printers are thoroughly vetted by our print experts and integrated into our PDN ecosystem, enabling our customers to easily access different mail delivery strategies without the hassle of management. The strength of our PDN is predicated on automated production, dynamically-adjusted throughput, and consistency of quality that's on-demand and at scale. How does the Print Delivery Network work? Any mail that is sent through Lob is dynamically distributed to the prints within our PDN, based on a number of factors, including: Mail form factor and permutation availability Mail volume capacity Paper stock and ink availability Distance from end-recipient of mail Other manufacturing and logistical capacity needs Regulatory requirements (e.g. HIPAA) I’m a printer interested in partnering with Lob. How do I get involved? If you're a printer that's interested in exploring a partnership opportunity with us, let's talk ! Experience industry-leading print and delivery infrastructure For more information about how this data is handled, please view our Privacy Policy Product Address Verification Print Delivery Network Product Tour Create + Personalize Postal IQ Production Tracking Sustainable Mail Product Updates Security Pricing Solutions Financial Services Insurance Healthcare Retail + Ecommerce Telecom Automotive Real Estate In-House Operations Agencies and Consultants In-House Marketing Operations Service Providers Resources Guides + Ebooks Case Studies Blog Events & Webinars Template Gallery Direct Mail Fundamentals Newsroom State of Direct Mail Direct Mail FAQs Developers Quickstart Guides API Documentation SDK and Tools Company About Us Careers Support Help Center Premium Support Contact Us API Status Privacy Terms of Service Partner With Us Become a Partner © 2026 Lob | Terms and Conditions | Privacy Policy | Do Not Sell or Share My Personal Information | 2026-01-13T08:48:38 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.