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://opensource.org/license/cern-ohl-w | CERN Open Hardware Licence Version 2 – Weakly Reciprocal – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Special Purpose CERN Open Hardware Licence Version 2 – Weakly Reciprocal Version 2 Submitted: June 29, 2020 Submitter: Andrew Katz Approved: January 15, 2021 Board minutes SPDX short identifier: CERN-OHL-W-2.0 Steward: CERN Link to license steward's version Preamble CERN has developed this licence to promote collaboration among hardware designers and to provide a legal tool which supports the freedom to use, study, modify, share and distribute hardware designs and products based on those designs. Version 2 of the CERN Open Hardware Licence comes in three variants: CERN-OHL-P (permissive); and two reciprocal licences: this licence, CERN-OHL-W (weakly reciprocal) and CERN-OHL-S (strongly reciprocal). The CERN-OHL-W is copyright CERN 2020. Anyone is welcome to use it, in unmodified form only. Use of this Licence does not imply any endorsement by CERN of any Licensor or their designs nor does it imply any involvement by CERN in their development. 1 Definitions 1.1 ‘Licence’ means this CERN-OHL-W. 1.2 ‘Compatible Licence’ means a) any earlier version of the CERN Open Hardware licence, or b) any version of the CERN-OHL-S or the CERN-OHL-W, or c) any licence which permits You to treat the Source to which it applies as licensed under CERN-OHL-S or CERN-OHL-W provided that on Conveyance of any such Source, or any associated Product You treat the Source in question as being licensed under CERN-OHL-S or CERN-OHL-W as appropriate. 1.3 ‘Source’ means information such as design materials or digital code which can be applied to Make or test a Product or to prepare a Product for use, Conveyance or sale, regardless of its medium or how it is expressed. It may include Notices. 1.4 ‘Covered Source’ means Source that is explicitly made available under this Licence. 1.5 ‘Product’ means any device, component, work or physical object, whether in finished or intermediate form, arising from the use, application or processing of Covered Source. 1.6 ‘Make’ means to create or configure something, whether by manufacture, assembly, compiling, loading or applying Covered Source or another Product or otherwise. 1.7 ‘Available Component’ means any part, sub-assembly, library or code which: a) is licensed to You as Complete Source under a Compatible Licence; or b) is available, at the time a Product or the Source containing it is first Conveyed, to You and any other prospective licensees i) with sufficient rights and information (including any configuration and programming files and information about its characteristics and interfaces) to enable it either to be Made itself, or to be sourced and used to Make the Product; or ii) as part of the normal distribution of a tool used to design or Make the Product. 1.8 ‘External Material’ means anything (including Source) which: a) is only combined with Covered Source in such a way that it interfaces with the Covered Source using a documented interface which is described in the Covered Source; and b) is not a derivative of or contains Covered Source, or, if it is, it is solely to the extent necessary to facilitate such interfacing. 1.9 ‘Complete Source’ means the set of all Source necessary to Make a Product, in the preferred form for making modifications, including necessary installation and interfacing information both for the Product, and for any included Available Components. If the format is proprietary, it must also be made available in a format (if the proprietary tool can create it) which is viewable with a tool available to potential licensees and licensed under a licence approved by the Free Software Foundation or the Open Source Initiative. Complete Source need not include the Source of any Available Component, provided that You include in the Complete Source sufficient information to enable a recipient to Make or source and use the Available Component to Make the Product. 1.10 ‘Source Location’ means a location where a Licensor has placed Covered Source, and which that Licensor reasonably believes will remain easily accessible for at least three years for anyone to obtain a digital copy. 2 Applicability 2.1 This Licence governs the use, copying, modification, Conveying of Covered Source and Products, and the Making of Products. By exercising any right granted under this Licence, You irrevocably accept these terms and conditions. 2.2 This Licence is granted by the Licensor directly to You, and shall apply worldwide and without limitation in time. 2.3 You shall not attempt to restrict by contract or otherwise the rights granted under this Licence to other Licensees. 2.4 This Licence is not intended to restrict fair use, fair dealing, or any other similar right. 3 Copying, Modifying and Conveying Covered Source 3.1 You may copy and Convey verbatim copies of Covered Source, in any medium, provided You retain all Notices. 3.2 You may modify Covered Source, other than Notices, provided that You irrevocably undertake to make that modified Covered Source available from a Source Location should You Convey a Product in circumstances where the recipient does not otherwise receive a copy of the modified Covered Source. In each case subsection 3.3 shall apply. You may only delete Notices if they are no longer applicable to the corresponding Covered Source as modified by You and You may add additional Notices applicable to Your modifications. 3.3 You may Convey modified Covered Source (with the effect that You shall also become a Licensor) provided that You: a) retain Notices as required in subsection 3.2; b) add a Notice to the modified Covered Source stating that You have modified it, with the date and brief description of how You have modified it; c) add a Source Location Notice for the modified Covered Source if You Convey in circumstances where the recipient does not otherwise receive a copy of the modified Covered Source; and d) license the modified Covered Source under the terms and conditions of this Licence (or, as set out in subsection 8.3, a later version, if permitted by the licence of the original Covered Source). Such modified Covered Source must be licensed as a whole, but excluding Available Components contained in it or External Material to which it is interfaced, which remain licensed under their own applicable licences. 4 Making and Conveying Products 4.1 You may Make Products, and/or Convey them, provided that You either provide each recipient with a copy of the Complete Source or ensure that each recipient is notified of the Source Location of the Complete Source. That Complete Source includes Covered Source and You must accordingly satisfy Your obligations set out in subsection 3.3. If specified in a Notice, the Product must visibly and securely display the Source Location on it or its packaging or documentation in the manner specified in that Notice. 4.2 Where You Convey a Product which incorporates External Material, the Complete Source for that Product which You are required to provide under subsection 4.1 need not include any Source for the External Material. 4.3 You may license Products under terms of Your choice, provided that such terms do not restrict or attempt to restrict any recipients’ rights under this Licence to the Covered Source. 5 Research and Development You may Convey Covered Source, modified Covered Source or Products to a legal entity carrying out development, testing or quality assurance work on Your behalf provided that the work is performed on terms which prevent the entity from both using the Source or Products for its own internal purposes and Conveying the Source or Products or any modifications to them to any person other than You. Any modifications made by the entity shall be deemed to be made by You pursuant to subsection 3.2. 6 DISCLAIMER AND LIABILITY 6.1 DISCLAIMER OF WARRANTY — The Covered Source and any Products are provided ‘as is’ and any express or implied warranties, including, but not limited to, implied warranties of merchantability, of satisfactory quality, non-infringement of third party rights, and fitness for a particular purpose or use are disclaimed in respect of any Source or Product to the maximum extent permitted by law. The Licensor makes no representation that any Source or Product does not or will not infringe any patent, copyright, trade secret or other proprietary right. The entire risk as to the use, quality, and performance of any Source or Product shall be with You and not the Licensor. This disclaimer of warranty is an essential part of this Licence and a condition for the grant of any rights granted under this Licence. 6.2 EXCLUSION AND LIMITATION OF LIABILITY — The Licensor shall, to the maximum extent permitted by law, have no liability for direct, indirect, special, incidental, consequential, exemplary, punitive or other damages of any character including, without limitation, procurement of substitute goods or services, loss of use, data or profits, or business interruption, however caused and on any theory of contract, warranty, tort (including negligence), product liability or otherwise, arising in any way in relation to the Covered Source, modified Covered Source and/or the Making or Conveyance of a Product, even if advised of the possibility of such damages, and You shall hold the Licensor(s) free and harmless from any liability, costs, damages, fees and expenses, including claims by third parties, in relation to such use. 7 Patents 7.1 Subject to the terms and conditions of this Licence, each Licensor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in subsections 7.2 and 8.4) patent licence to Make, have Made, use, offer to sell, sell, import, and otherwise transfer the Covered Source and Products, where such licence applies only to those patent claims licensable by such Licensor that are necessarily infringed by exercising rights under the Covered Source as Conveyed by that Licensor. 7.2 If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Covered Source or a Product constitutes direct or contributory patent infringement, or You seek any declaration that a patent licensed to You under this Licence is invalid or unenforceable then any rights granted to You under this Licence shall terminate as of the date such process is initiated. 8 General 8.1 If any provisions of this Licence are or subsequently become invalid or unenforceable for any reason, the remaining provisions shall remain effective. 8.2 You shall not use any of the name (including acronyms and abbreviations), image, or logo by which the Licensor or CERN is known, except where needed to comply with section 3, or where the use is otherwise allowed by law. Any such permitted use shall be factual and shall not be made so as to suggest any kind of endorsement or implication of involvement by the Licensor or its personnel. 8.3 CERN may publish updated versions and variants of this Licence which it considers to be in the spirit of this version, but may differ in detail to address new problems or concerns. New versions will be published with a unique version number and a variant identifier specifying the variant. If the Licensor has specified that a given variant applies to the Covered Source without specifying a version, You may treat that Covered Source as being released under any version of the CERN-OHL with that variant. If no variant is specified, the Covered Source shall be treated as being released under CERN-OHL-S. The Licensor may also specify that the Covered Source is subject to a specific version of the CERN-OHL or any later version in which case You may apply this or any later version of CERN-OHL with the same variant identifier published by CERN. You may treat Covered Source licensed under CERN-OHL-W as licensed under CERN-OHL-S if and only if all Available Components referenced in the Covered Source comply with the corresponding definition of Available Component for CERN-OHL-S. 8.4 This Licence shall terminate with immediate effect if You fail to comply with any of its terms and conditions. 8.5 However, if You cease all breaches of this Licence, then Your Licence from any Licensor is reinstated unless such Licensor has terminated this Licence by giving You, while You remain in breach, a notice specifying the breach and requiring You to cure it within 30 days, and You have failed to come into compliance in all material respects by the end of the 30 day period. Should You repeat the breach after receipt of a cure notice and subsequent reinstatement, this Licence will terminate immediately and permanently. Section 6 shall continue to apply after any termination. 8.6 This Licence shall not be enforceable except by a Licensor acting as such, and third party beneficiary rights are specifically excluded. Donate to the OSI The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and public institutions. The Open Source Initiative (OSI) is a 501(c)3 public benefit corporation, founded in 1998. --> Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://www.facebook.com/login/ | Facebook에 로그인 Facebook에 로그인 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://www.npopov.com/2012/01/19/Careful-XDebug-can-skew-your-performance-numbers.html | Careful: XDebug can skew your performance numbers Blog by nikic . Find me on GitHub , StackOverflow , Twitter and Mastodon . Learn more about me . « Back to article overview. Careful: XDebug can skew your performance numbers 19. January 2012 XDebug is a great tool and a really big aid in debugging. But running it incurs a certain overhead on many common operations - like calling functions. Due to this having XDebug enabled can skew your benchmarking and profiling numbers. (“Enabled” here means just enabled, no debugging going on or such.) This has an important implication: If you optimize a script while XDebug is enabled it can actually turn out that it gets slower on your production server (as you hopefully don’t have XDebug enabled there). An example: “Optimizing” a lexer wrapper For my PHP parser I need a smaller wrapper around PHP’s token_get_all function. This wrapper (called PHPParser_Lexer ) only does nothing more than a little bit of normalization, filtering and mapping on the tokens. There are basically two ways how this wrapper can work: For every source code to be parsed a new Lexer instance is created and passed into the parser, which then does multiple calls to ->lex() to fetch one token at a time. A Lexer is creates once and reused for all source codes. Always only a single call to ->lex() is made, which then returns all the tokens at once. So, what I did is implement both approaches and see how much time is spent lexing the whole Symfony tree. I got the following results: Scenario 1 on 5.3.8 with XDebug enabled: 16.939509868622 seconds Scenario 2 on 5.3.8 with XDebug enabled: 6.104107856751 seconds That’s an impressive saving of 10 seconds (aka 60%) right there! is what I though. But then I tried the same thing without XDebug: Scenario 1 on 5.3.8 with XDebug disabled: 3.656718969345 seconds Scenario 2 on 5.3.8 with XDebug disabled: 3.195748090744 seconds Now that XDebug is disabled the numbers are drastically lower and also much closer. The 17 seconds from above are only 3.7 seconds now. The time for the 6 seconds case halved. Why is there such a drastic change on the first number, and a less pronounced one on the second? The first scenario needs approximately 70000 ->lex() calls, whereas the second one only needs 2000. XDebug adds a quite large overhead to function calls, so the scenario with 70000 calls is impacted much more. Finally, let’s look at the numbers for PHP 5.4.0 without XDebug: Scenario 1 on 5.4.0 with XDebug disabled: 2.8629820346832 seconds Scenario 2 on 5.4.0 with XDebug disabled: 3.0883010864258 seconds And here the numbers are now actually turned around. PHP 5.4 got some optimizations that made the seconds variant slower. Another example: Micro benchmarking As pointless as they are, people still love micro benchmarks, I do too. You’ll find lots of blog posts comparing the performance of something vs. something else. The problem is: Most of these are done on development machines, with XDebug enabled. As an example this recent blog post about the performance of exceptions will serve. Here are the numbers the author measured for exceptions on PHP 5.3/5.4 for a certain script: PHP 5.3: 1.1479668617249 PHP 5.4: 0.1864490332 Looking at those you might say: Damn, that’s a pretty impressive improvement! Well, not really: Seeing these numbers I immediately had the suspicion that the author actually measured two different things: 5.3 with XDebug and 5.4 without it. So I tested both versions without XDebug and got 0.14 seconds for PHP 5.3 and 0.09 seconds for PHP 5.4, i.e. a much smaller difference. You can find more detailed results in edorian’s blog post on the topic. I think many micro benchmarking posts you’ll find on the net are affected by this. I was also trapped by this multiple times (e.g. see this question I asked about function call performance ). Conclusion The conclusion from the above is: If you do benchmarking, benchmark on a machine that’s configured like your production machine. Otherwise you might actually be anti-optimizing. Also: Low level optimizations like function inlining may actually measurably improve performance on your development machine (like in my case), but have little effect in the production environment. So, you can safely go for clean code with small functions and not fear about performance degradation. If you liked this article, you may want to browse my other articles or follow me on Twitter or Mastodon . | 2026-01-13T08:49:47 |
https://www.facebook.com/allactivity?privacy_source=activity_log_top_menu | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 가입하기 Notice 계속하려면 로그인해주세요. Facebook에 로그인 로그인 계정을 잊으셨나요? 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://dev.to/cotter/localstorage-vs-cookies-all-you-need-to-know-about-storing-jwt-tokens-securely-in-the-front-end-15id#cookies | LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michelle Marcelline for Cotter Posted on Jul 21, 2020 • Edited on Aug 1, 2020 • Originally published at blog.cotter.app LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End # security # webdev # javascript OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI JWT Tokens are awesome, but how do you store them securely in your front-end? We'll go over the pros and cons of localStorage and Cookies. We went over how OAuth 2.0 works in the last post and we covered how to generate access tokens and refresh tokens. The next question is: how do you store them securely in your front-end? A Recap about Access Token & Refresh Token Access tokens are usually short-lived JWT Tokens, signed by your server, and are included in every HTTP request to your server to authorize the request. Refresh tokens are usually long-lived opaque strings stored in your database and are used to get a new access token when it expires. Where should I store my tokens in the front-end? There are 2 common ways to store your tokens: in localStorage or cookies. There are a lot of debate on which one is better and most people lean toward cookies for being more secure. Let's go over the comparison between localStorage . This article is mainly based on Please Stop Using Local Storage and the comments to this post. Local Storage Pros: It's convenient. It's pure JavaScript and it's convenient. If you don't have a back-end and you're relying on a third-party API, you can't always ask them to set a specific cookie for your site. Works with APIs that require you to put your access token in the header like this: Authorization Bearer ${access_token} . Cons: It's vulnerable to XSS attacks. An XSS attack happens when an attacker can run JavaScript on your website. This means that the attacker can just take the access token that you stored in your localStorage . An XSS attack can happen from a third-party JavaScript code included in your website, like React, Vue, jQuery, Google Analytics, etc. It's almost impossible not to include any third-party libraries in your site. Cookies Pros: The cookie is not accessible via JavaScript; hence, it is not as vulnerable to XSS attacks as localStorage . If you're using httpOnly and secure cookies, that means your cookies cannot be accessed using JavaScript. This means, even if an attacker can run JS on your site, they can't read your access token from the cookie. It's automatically sent in every HTTP request to your server. Cons: Depending on the use case, you might not be able to store your tokens in the cookies. Cookies have a size limit of 4KB. Therefore, if you're using a big JWT Token, storing in the cookie is not an option. There are scenarios where you can't share cookies with your API server or the API requires you to put the access token in the Authorization header. In this case, you won't be able to use cookies to store your tokens. About XSS Attack Local storage is vulnerable because it's easily accessible using JavaScript and an attacker can retrieve your access token and use it later. However, while httpOnly cookies are not accessible using JavaScript, this doesn't mean that by using cookies, you are safe from XSS attacks involving your access token. If an attacker can run JavaScript in your application, then they can just send an HTTP request to your server and that will automatically include your cookies. It's just less convenient for the attacker because they can't read the content of the token although they rarely have to. It might also be more advantageous for the attacker to attack using victim's browser (by just sending that HTTP Request) rather than using the attacker's machine. Cookies and CSRF Attack CSRF Attack is an attack that forces a user to do an unintended request. For example, if a website is accepting an email change request via: POST /email/change HTTP / 1.1 Host : site.com Content-Type : application/x-www-form-urlencoded Content-Length : 50 Cookie : session=abcdefghijklmnopqrstu email=myemail.example.com Enter fullscreen mode Exit fullscreen mode Then an attacker can easily make a form in a malicious website that sends a POST request to https://site.com/email/change with a hidden email field and the session cookie will automatically be included. However, this can be mitigated easily using sameSite flag in your cookie and by including an anti-CSRF token . Conclusion Although cookies still have some vulnerabilities, it's preferable compared to localStorage whenever possible. Why? Both localStorage and cookies are vulnerable to XSS attacks but it's harder for the attacker to do the attack when you're using httpOnly cookies. Cookies are vulnerable to CSRF attacks but it can be mitigated using sameSite flag and anti-CSRF tokens . You can still make it work even if you need to use the Authorization: Bearer header or if your JWT is larger than 4KB. This is also consistent with the recommendation from the OWASP community: Do not store session identifiers in local storage as the data are always accessible by JavaScript. Cookies can mitigate this risk using the httpOnly flag. OWASP: HTML5 Security Cheat Sheet So, how do I use cookies to persists my OAuth 2.0 tokens? As a recap, here are the different ways you can store your tokens: Option 1: Store your access token in localStorage : prone to XSS. Option 2: Store your access token in httpOnly cookie: prone to CSRF but can be mitigated, a bit better in terms of exposure to XSS. Option 3: Store the refresh token in httpOnly cookie: safe from CSRF, a bit better in terms of exposure to XSS. We'll go over how Option 3 works as it is the best out of the 3 options. Store your access token in memory and store your refresh token in the cookie Why is this safe from CSRF? Although a form submit to /refresh_token will work and a new access token will be returned, the attacker can't read the response if they're using an HTML form. To prevent the attacker from successfully making a fetch or AJAX request and read the response, this requires the Authorization Server's CORS policy to be set up correctly to prevent requests from unauthorized websites. So how does this set up work? Step 1: Return Access Token and Refresh Token when the user is authenticated. After the user is authenticated, the Authorization Server will return an access_token and a refresh_token . The access_token will be included in the Response body and the refresh_token will be included in the cookie. Refresh Token cookie setup: Use the httpOnly flag to prevent JavaScript from reading it. Use the secure=true flag so it can only be sent over HTTPS. Use the SameSite=strict flag whenever possible to prevent CSRF. This can only be used if the Authorization Server has the same site as your front-end. If this is not the case, your Authorization Server must set CORS headers in the back-end or use other methods to ensure that the refresh token request can only be done by authorized websites. Step 2: Store the access token in memory Storing the token in-memory means that you put this access token in a variable in your front-end site. Yes, this means that the access token will be gone if the user switches tabs or refresh the site. That's why we have the refresh token. Step 3: Renew access token using the refresh token When the access token is gone or has expired, hit the /refresh_token endpoint and the refresh token that was stored in the cookie in step 1 will be included in the request. You'll get a new access token and can then use that for your API Requests. This means your JWT Token can be larger than 4KB and you can also put it in the Authorization header. That's It! This should cover the basics and help you secure your site. This post is written by the team at Cotter – we are building lightweight, fast, and passwordless login solution for websites and mobile apps. If you're building a login flow for your website or mobile app, these articles might help: What On Earth Is OAuth? A Super Simple Intro to OAuth 2.0, Access Tokens, and How to Implement it in your Site Passwordless Login with Email and JSON Web Token (JWT) Authentication using Next.js Here's How to Integrate Cotter's Magic Link to Your Webflow Site in Less Than 15 minutes! References We referred to several articles when writing this blog, especially from these articles: Please Stop Using Local Storage The Ultimate Guide to handling JWTs on front-end clients (GraphQL) Cookies vs Localstorage for sessions – everything you need to know Questions & Feedback If you need help or have any feedback, feel free to comment here or ping us on Cotter's Slack Channel ! We're here to help. Ready to use Cotter? If you enjoyed this post and want to integrate Cotter into your website or app, you can create a free account and check out our documentation . OAuth 2.0, JWT Tokens, and How to Store Them Securely (3 Part Series) 1 What on Earth Is OAuth? ASuper Simple Intro to OAuth 2.0, Access Tokens, and How to Implement It in Your Site 2 LocalStorage vs Cookies: All You Need To Know About Storing JWT Tokens Securely in The Front-End 3 OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI Top comments (46) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 22 '20 • Edited on Jul 24 • Edited Dropdown menu Copy link Hide The part of this discussion I always stumble over is when it is recommended to "just" use anti-CSRF tokens. This is a non-trivial requirement. It is easy for one server -- most of them have built-in libs just like with JWT authentication. However, unlike JWT authentication it is a stateful process. So once you go beyond a single API server (including a fail-over scenario) you have to externalize the issued CSRF tokens into something like Redis (or a DB if you don't mind even more added latency). So all servers can be aware of the issued tokens. This adds another infrastructure piece that needs to be maintained and scaled for load. Edit: I guess people already using session servers are thinking "So what, we already have Redis to track user sessions." But with JWT, user sessions are stateless (just the token they provide and you validate) so this extra infrastructure isn't needed. That's a maintenance cost eliminated. As far as local storage being vulnerable to XSS attacks, OWASP also puts out an XSS Prevention Cheat Sheet . The main attack vector for XSS is when you allow users to directly input HTML/JS and then execute it. Most major frameworks already santize user inputs to prevent this. Modern JavaScript frameworks have pretty good XSS protection built in. OWASP XSS Prevention Cheat Sheet The less common threat that you mentioned was NPM libraries becoming subverted to include XSS attacks. NPM has added auditing tools to report this and warn users. (Edit: Fair point is that people sometimes still use JS libs from CDNs, which may have less scrutiny.) And also Content Security Policy is supported in all major browsers and can prevent attacks and the exfil of token/data even if a script on your site gets compromised. It does not necessarily prevent the compromised script from making calls to your own API. But they would have to be targeting your API specifically to accomplish much. I completely understand the recommendation to use cookies + Secure + HttpOnly + anti-forgery tokens from a security perspective. And as far as I am aware it is superior security to JWT in local storage. But it also has pretty significant constraints. And local storage is not bad, security-wise. It is isolated by domain. XSS attacks are already heavily mitigated by just using a modern JS framework and paying attention to NPM audit warnings. Throw in CSP for good measure. And of course not going out of your way to evaluate user-entered data as HTML/JS/CSS. (If your site functionality requires this, then you probably should use cookie auth and CSP.) Like comment: Like comment: 37 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Kasey, thanks for your comment! I do agree that localStorage is not bad at all, and considering how XSS attacks are already heavily mitigated as you mentioned, it's a valid option. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Kasey Speakman Kasey Speakman Kasey Speakman Follow collector of ideas. no one of consequence. Location Huntsville, AL Joined Apr 5, 2017 • Jul 23 '20 Dropdown menu Copy link Hide Hey thanks for the response! Best wishes. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Great article. Thanks for the in depth research and clear tutorial. Logic was very concise. 😃 Like comment: Like comment: 9 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Happy to help! Feel free to ping me if you have any questions/concerns :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Todd Matheson Todd Matheson Todd Matheson Follow I'm current a student in frontend dev. I love learning new things, especially in the realm of web development. Also, becoming well acquainted with Rust's borrow checker. Location Bay Area, California Education Current Web Development Student Work Full stack web developer Joined Jan 2, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Was in a long search for this clarification. Thanks Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Anshul! Let me know if you want me to discuss any other topics related to Authentication :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Anshul Negi Anshul Negi Anshul Negi Follow Hello there... I Consider Myself A Budding Programmer, Learning Things At Own Pace & Celebrating The Learning Curve. Email anshul.negi.tc@gmail.com Location India Education B.Tech(Computer Science) Work MERN developer at Anshul Negi Joined Dec 14, 2019 • Jul 23 '20 Dropdown menu Copy link Hide For sure As for now, this article clears most of the doubts maybe in future if I lost around something related to authentication, will let you know. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lucien glue Lucien glue Lucien glue Follow full stack web developer Joined Jul 19, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Thanks for this article, it helped me a lot! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Lucien! Let me know if you have any questions :) Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide If you use Express, then it could be worth looking at Express Session and the option to save the data to Redis: app.use( session({ name: 'sessionForApplication', secret: process.env.SESSION_SECRET, saveUninitialized: true, resave: true, cookie: { expires: expiryDate, domain: process.env.APP_DOMAIN }, store: new RedisStore(optionsForRedis) }) ) Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 10 likes Like Comment button Reply Collapse Expand Hemant Joshi Hemant Joshi Hemant Joshi Follow Your Friendly Neighbourhood Developer. Location Nainital, India Education Birla Institue Of Apllied Sciences; Work Learning... Joined Mar 31, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Yes, redis is the best one🙂, also cookies would be my second option for JWT based storage Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Wayne, Putri here – Michelle's cofounder. This is very helpful, Express Session with Redis is definitely a great option. Thanks for the comment! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Wayne Smallman Wayne Smallman Wayne Smallman Follow Addicted to learning everything there is (except tax law and OAuth), often to be found contemplating the infinite when not building the Under Cloud. Location Yorkshire, England. Work Owner & Founder at Under Cloud Joined Jun 30, 2019 • Jul 23 '20 Dropdown menu Copy link Hide A pleasure, and glad to help. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand m4r4v m4r4v m4r4v Follow I am who I am Location Earth Education Software Engineer, Cibersecurity Analyst, GNU/Linux SysAdmin Work Consultant Joined Jul 7, 2020 • Jul 22 '20 Dropdown menu Copy link Hide Very descriptive and helpful article. Thanks!!! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Michelle Marcelline Cotter Michelle Marcelline Cotter Michelle Marcelline Follow I post about my journey as an immigrant female founder • prev. Typedream (acq. beehiiv) • Y Combibnator W20 • Forbes U30 Location San Francisco Work Co-Founder at The Prompting Company Joined Jun 19, 2020 • Jul 22 '20 • Edited on Jul 23 • Edited Dropdown menu Copy link Hide Thanks Jorge! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 22 '20 • Edited on Jul 22 • Edited Dropdown menu Copy link Hide Hi Michelle, really great article! What always confused me about httpOnly cookies and JWT is that the frontend app is missing a big benefit of JWT, which is the payload containing claims and possibly other custom data from the backend. This is most often the user's role, which then the app uses to render privileged parts of the UI and so on, or the token expiry information. With httpOnly, this benefit is not utilised - but the cost in increased packet size is still being paid! There are strategies which take option 3 to the extreme, and people have already written great articles about this in details, that the JWT token itself should be split into 2 parts, it's signature in httpOnly, and the rest in a normal JS-accessible cookie. This ofcourse increases the complexity of the backend as well, which now needs to piece together the final JWT from two different incoming sources. I guess this could be option 4. It seems to me, that in order to make good secure use of JWT, considerable complexity on both stacks must be considered. Alternatives are either insecure, or not utilizing the benefits of JWT, which would then just be better off using bearer tokens. Again, thanks for the great article. It really got me thinking about these things and I think a great discussion could be made about the topic. What is your take on splitting the token into two cookies? Does the added complexity justify the security gained? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Marko, Putri here – Michelle's cofounder. That's an interesting suggestion! I don't quite understand how the frontend would miss being able to read the claims/custom data in the JWT using option 3. By storing the access token in memory, you can decode and read the claims in the frontend whenever the access token is available. When the access token is not available in memory (after a refresh/change tab), you can use a function that will refresh the access token, and now you have the access token available again in memory and you can read/decode it in the frontend. Splitting the JWT might be a useful option if the above solution doesn't help. Let me know what you think :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Marko Kruljac Marko Kruljac Marko Kruljac Follow Hello world Location Zagreb Joined Feb 27, 2020 • Jul 23 '20 Dropdown menu Copy link Hide By storing the token in memory, you risk compromising it by means of xss. The damage is contained since the token is short-lived, but still a window of opportunity exists. We can either accept this risk or add considerable complexity to reduce it. What do you think? Like comment: Like comment: 1 like Like Thread Thread Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide That's true, storing in memory is still prone to XSS attack, it's just harder for the attacker to find it than localStorage. Splitting the JWT into 2 cookies where the signature is in an httpOnly cookie, but the rest of the JWT is accessible to JavaScript makes sense. This means that the frontend can still access JWT except for the signature. I think it's up to the website to determine what kind of attack factor that they're trying to mitigate against to decide whether they need the upgrade in security. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Pacharapol Withayasakpunt Pacharapol Withayasakpunt Pacharapol Withayasakpunt Follow Currently interested in TypeScript, Vue, Kotlin and Python. Looking forward to learning DevOps, though. Location Thailand Education Yes Joined Oct 30, 2019 • Jul 28 '20 • Edited on Jul 28 • Edited Dropdown menu Copy link Hide I just wonder what is actually accessible by document.cookie ? Secondly would be the implementation. I am interested in all processes from highly-accessible sign-in, to protecting the API endpoint, and the server knows requesters' credentials (for attaching userId in database queries). I currently use Firebase / firebase-admin for these reasons, but I have trouble implementing storing token in cookies . I fear that it might be backend dependent... I will consider your product. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Aug 4 '20 Dropdown menu Copy link Hide Hi Pacharapol! Cookies that are marked httpOnly are not accessible from document.cookie , otherwise you can access the cookie from document.cookie . source With our JS SDK (from yarn add cotter ), we actually handle storing the access token in memory and the refresh token in the cookie for you. In short, you can just call: cotter . tokenHandler . getAccessToken () Enter fullscreen mode Exit fullscreen mode and it will: grab the access token from memory if not expired, or automatically refreshes the access token by calling Cotter's refresh token endpoint (where the cookie is included) and return to you a new access token. If you're interested, shoot me a message on Slack and I can help you with any questions. You can find our documentation here . Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Jaytonic Jaytonic Jaytonic Follow Joined Jan 14, 2020 • Mar 18 '22 Dropdown menu Copy link Hide Nice article, thank you! One thing I'm not sure I totally understood: About "Store your access token in memory and store your refresh token in the cookie". Doesn't that make us again vulnerable to XSS attacks? Because your in-memory token would be available by some injected javascript, no? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 22 '20 Dropdown menu Copy link Hide Hi, I am so excited about this article, But what if the refresh token takes more than 4KB? Is there any way to increase the space of Cookie? Cookie is reling on the type of Browser? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Putri Karunia Cotter Putri Karunia Cotter Putri Karunia Follow Co-founder of Cotter.app, web dev & design enthusiast. Email putri@typedream.com Location San Francisco Education UC Berkeley Work CTO at Typedream Joined Jun 18, 2020 • Jul 23 '20 Dropdown menu Copy link Hide Hi Pony, refresh tokens are usually opaque random strings stored in your database, so they shouldn't take more than 4KB. I don't think that there's a way to increase the space, but you might be able to split a large cookie into 2. However some browser limits cookie size per domain, so that wouldn't work. Here's a nice list about cookie limits per browser browsercookielimits.squawky.net/ . Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jonyx jonyx jonyx Follow Senior Software Engineer Joined Nov 8, 2019 • Jul 23 '20 Dropdown menu Copy link Hide Thank you for your kind support Love to wait for your next post Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Matt Ellen-Tsivintzeli Follow Ultra-fullstack software developer. Python, JavaScript, C#, C. Location Earth Education I am a master of science Pronouns He/him/his/his Work Software Engineer Joined May 2, 2017 • Sep 9 '21 Dropdown menu Copy link Hide Hi Putri, Just to let you know that the link in your reply is now dead. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (46 comments) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Cotter Follow One-Tap Passwordless Login for your App Are you building a website or an app that needs user signups/logins? Learn how to build user-friendly authentication in just a few minutes . Get Started More from Cotter The Simplest Way to Authorize Github OAuth Apps with Next.js and Cotter # javascript # webdev # github # security How to Make an Interactive Todo List CLI using Python with an Easy Login Mechanism # python # tutorial # security OAuth 2.0 - Before You Start: Pick the Right Flow for Your Website, SPA, Mobile App, TV App, and CLI # javascript # security # webdev # react 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:47 |
https://dev.to/sunny7899/documenting-the-journey-preparing-for-a-senior-ui-engineer-role-at-servicenow-81a#5-a-real-challenge-not-a-perfect-story | Documenting the Journey: Preparing for a Senior UI Engineer Role at ServiceNow - 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 Neweraofcoding Posted on Dec 29, 2025 Documenting the Journey: Preparing for a Senior UI Engineer Role at ServiceNow # devjournal # interview # career # ui There’s a moment in every engineering career where you pause—not because you’re stuck, but because you’re leveling up . This blog is about one of those moments for me. Recently, I started preparing for a Senior Software Engineer – UI role at ServiceNow . Instead of rushing through prep, I decided to slow down and document the journey —the prompts, the reflections, and the story behind my work. This post is both a record for myself and a guide for anyone preparing for a similar transition. Why I Decided to Document This Interview prep can feel transactional: Memorize answers Practice talking points Hope it clicks But this role made me realize something: This wasn’t just interview prep. This was a reflection of my career so far. ServiceNow’s focus on AI-powered UX, observability, scale, and craftsmanship forced me to connect dots across my experience—from building dashboards and APIs to integrating ML and designing for trust. So instead of just “preparing answers,” I framed everything as a story . The Prompts That Shaped the Story These were the prompts I worked through—and honestly, they map really well to how senior engineers think. 1. Short Introduction (2 minutes) This wasn’t about listing tools. It was about answering: What problems do I enjoy solving? How does my work create impact? Why does my experience make sense now ? I focused on: Building customer-facing UI Turning complex systems into simple experiences Using AI not as a buzzword , but as a practical tool The goal wasn’t to sound impressive—it was to sound clear . 2. What Do I Know About ServiceNow? (30 seconds) This forced me to zoom out. Not just: “They do workflow automation.” But: They connect people, systems, and processes They’re investing deeply in AI-native experiences Observability isn’t just metrics—it’s insight and action This helped me align my past work with where the platform is going. 3. Why This Role, Why Now? This was one of the most important reflections. I realized I wasn’t leaving my current role because of dissatisfaction. I was leaving because I wanted: More product-driven engineering More scale A place where UI, AI, and platform thinking intersect That clarity alone boosted my confidence. 4. What I Want in My Next Opportunity This wasn’t about perks or titles. I wrote down three things: Ownership from idea to delivery Strong engineering culture (reviews, quality, reliability) Space to grow—technically and as a mentor Simple. Honest. Grounded. 5. A Real Challenge (Not a Perfect Story) Instead of a “hero story,” I picked a messy one: Inconsistent data Tight timelines Evolving requirements Cross-team friction I talked about: Trade-offs Decisions What broke What I learned That reflection reminded me: Senior engineering isn’t about avoiding problems—it’s about navigating them calmly. 6. Questions I Ask Them This flipped the dynamic. Instead of trying to impress, I got curious: What problems matter most right now? How does AI actually show up in the product? How do teams collaborate end-to-end? It made the conversation feel mutual—not one-sided. What This Process Taught Me A few things really stood out: Good interviews are storytelling exercises AI experience matters most when tied to user trust UI engineering at scale is about empathy, not pixels Preparation is confidence—not memorization Most importantly, I realized I already had the experience. I just needed to frame it clearly. Why I’m Keeping This Documented Careers are long. It’s easy to forget: Why you chose certain paths How much you’ve learned What kind of engineer you’re becoming This blog is a checkpoint. Whether or not this specific role works out, the process itself already paid off. I’m sharper, clearer, and more intentional than I was before. And that’s a win. Final Thought If you’re preparing for a senior role: Don’t just study the job description Study your own journey There’s more alignment there than you think. End of entry. 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 Neweraofcoding Follow Expert Front end developer with Angular, and React experience Location Delhi India Joined Nov 4, 2020 More from Neweraofcoding Apertre 3.0: An Open-Source Program Empowering the Next Generation of Developers # codenewbie # career # learning # opensource The Agentic Leap: Key Announcements and Demos from the Google I/O 2025 Developer Keynote # webdev # ai # career # productivity What is the Microsoft MVP Award and its benefits? # career # leadership # microsoft 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:47 |
https://www.facebook.com/pages/create/?ref_type=site_footer | Facebook Facebook Facebook 가입 또는 로그인 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 로그인 Facebook에 가입하시겠어요? 가입하기 가입하기 페이지 만들기 비즈니스, 본인 또는 비영리 단체를 나타내는 페이지를 만들어 전 세계 사람들과 소통해보세요. 시작하려면 페이지 카테고리를 선택하세요. | 2026-01-13T08:49:47 |
https://www.npopov.com/2012/01/28/htmlspecialchars-improvements-in-PHP-5-4.html | htmlspecialchars() improvements in PHP 5.4 Blog by nikic . Find me on GitHub , StackOverflow , Twitter and Mastodon . Learn more about me . « Back to article overview. htmlspecialchars() improvements in PHP 5.4 28. January 2012 There has been lots of buzz about many of the new features in PHP 5.4, like the traits support, the short array syntax and all those other syntax improvements. But one set of changes that I think is particularly important was largely overlooked: For PHP 5.4 cataphract ( Artefacto on StackOverflow) heroically rewrote large parts of htmlspecialchars thus fixing various quirks and adding some really nice new features. (The changes discussed here apply not only to htmlspecialchars , but also to the related htmlentities and in parts to htmlspecialchars_decode , html_entity_decode and get_html_translation_table .) Here a quick summary of the most important changes: UTF-8 as the default charset Improved error handling ( ENT_SUBSTITUTE ) Doctype handling ( ENT_HTML401 , …) UTF-8 as the default charset As you hopefully know the third argument for htmlspecialchars is the character set. Thing is: Most people just leave that argument out, thus falling back to the default charset. This default charset was ISO-8859-1 before PHP 5.4 and as such did not match the UTF-8 encoding most people use. PHP 5.4 fixes this by making UTF-8 the default. Improved error handling Error handling in htmlspecialchars before PHP 5.4 was … uhm, let’s call it “unintuitive”: If you passed a string containing an “invalid code unit sequence” (which is Unicode slang for “not encoded correctly”) htmlspecialchars would return an empty string. Well, okay, so far so good. The funny thing was that it additionally would throw an error, but only if error display was disabled . So it would only error if errors are hidden. Nice, innit? This basically meant that on your development machine you wouldn’t see any errors, but on your production machine the error log would be flooded with them. Awesome. So, as of PHP 5.4 thankfully this behavior is gone . The error will not be generated anymore. Additionally there are two options that allow you to specify an alternative to just returning an empty string: ENT_IGNORE : This option (which isn’t actually new, it was there in PHP 5.3 already) will just drop all invalid code unit sequences. This is bad for two reasons: First, you won’t notice invalid encoding because it’ll be simply dropped. Second, this imposes a certain security risk (for more info see the Unicode Security Considerations ). ENT_SUBSTITUTE : This new alternative option takes a much more sensible approach at the problem: Instead of just dropping the code units they will be replaced by a Unicode Replacement Character (U+FFFD). So invalid code unit sequences will be replaced by � characters. Let’s have a look at the different behaviors: // "\80" is invalid UTF-8 in this context var_dump ( htmlspecialchars ( "a \x80 b" )); // string(0) "" var_dump ( htmlspecialchars ( "a \x80 b" , ENT_IGNORE )); // string(2) "ab" var_dump ( htmlspecialchars ( "a \x80 b" , ENT_SUBSTITUTE )); // string(5) "a�b" Clearly, you want the last behavior. In your real code it will probably look like this: // this goes into the bootstrap (or where appropriate) to make the code // not throw a notice on PHP 5.3 if ( ! defined ( 'ENT_SUBSTITUTE' )) { define ( 'ENT_SUBSTITUTE' , 0 ); // if you want the empty string behavior on 5.3 // or define ( 'ENT_SUBSTITUTE' , ENT_IGNORE ); // if you want the char removal behavior on 5.3 // (don't forget about the security issues though!) } // don't forget to specify the charset! Otherwise you'll get the old default charset on 5.3. $escaped = htmlspecialchars ( $string , ENT_QUOTES | ENT_SUBSTITUTE , 'UTF-8' ); Doctype handling In PHP 5.4 there are four additional flags for specifying the used doctype: ENT_HTML401 (HTML 4.01) => this is the default ENT_HTML5 (HTML 5) ENT_XML1 (XML 1) ENT_XHTML (XHTML) Depending on which doctype you specify htmlspecialchars (and the other related functions) will use different entity tables. You can see this in the following example: var_dump ( htmlspecialchars ( "'" , ENT_HTML401 )); // string(6) "&#039;" var_dump ( htmlspecialchars ( "'" , ENT_HTML5 )); // string(6) "&apos;" So for HTML 5 an &apos; entity will be generated, whereas for HTML 4.01 - which does not yet support &apos; - a numerical &#039; entity is returned. The difference becomes more evident when using htmlentities , because the differences are larger there. You can easily see this by having a look at the raw translation tables: To do this, we can use the get_html_translation_table function. Here first an example for the XML 1 doctype: var_dump ( get_html_translation_table ( HTML_ENTITIES , ENT_QUOTES | ENT_XML1 )); The result will look like this: array(5) { ["""]=> string(6) "&quot;" ["&"]=> string(5) "&amp;" ["'"]=> string(6) "&apos;" ["<"]=> string(4) "&lt;" [">"]=> string(4) "&gt;" } This matches our expectations: XML by itself defines only the five basic entities. Now try the same thing for HTML 5 and you’ll see something like this: array(1510) { [" "]=> string(5) "&Tab;" [" "]=> string(9) "&NewLine;" ["!"]=> string(6) "&excl;" ["""]=> string(6) "&quot;" ["#"]=> string(5) "&num;" ["$"]=> string(8) "&dollar;" ["%"]=> string(8) "&percnt;" ["&"]=> string(5) "&amp;" ["'"]=> string(6) "&apos;" // ... } So HTML 5 defines a vast number of entities - 1510 to be precise. You can also try HTML 4.01 and XHTML; they both define 253 entities. Also affected by the chosen doctype is another new error handling flag which I did not mention above: ENT_DISALLOWED . This flag will replace characters with a Unicode Replacement Character, which formally are a valid code unit sequences, but are invalid in the given doctype. This way you can ensure that the returned string is always well formed regarding encoding (in the given doctype). I’m not sure though how much sense it makes to use this flag. The browser will handle invalid characters gracefully anyways, so this seems unnecessary to me (though I’m probably wrong). There is other stuff too… … but I don’t want to list everything here. I think the three changes mentioned above are the most important improvements. htmlspecialchars ( "< \x80 The End \xef\xbf\xbf >" , ENT_QUOTES | ENT_HTML5 | ENT_DISALLOWED | ENT_SUBSTITUTE , 'UTF-8' ); If you liked this article, you may want to browse my other articles or follow me on Twitter or Mastodon . | 2026-01-13T08:49:47 |
https://open.forem.com/emma-suntech/led-strip-lighting-is-a-distributed-system-and-long-runs-will-humble-you-2bb7#comments | LED strip lighting is a distributed system (and long runs will humble you) - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse emmma Posted on Jan 7 LED strip lighting is a distributed system (and long runs will humble you) # hardware # learning # networking I used to think LED strips were “stick + power + done.” Then I built a longer run (ceiling cove / hallway line / shelf edge) and watched the far end dim, “white” shift warm, and—on addressable effects—animations start to stutter. That’s when it clicked: a long LED strip install behaves like a tiny distributed system. Power is your infrastructure. Data (if addressable) is your network link. Optics is the UI layer. The three failure modes you’ll actually see 1) Power (voltage drop) End of strip is visibly dimmer RGB “white” shifts yellow/pink toward the far end Effects look uneven at higher brightness 2) Data integrity (addressable strips) Random flicker / wrong colors on some pixels “Works on the bench, fails installed” Breaks after N pixels 3) Perception bugs Hotspots make the install look cheap Dimming feels jumpy at low levels Gradients band instead of fading smoothly What consistently works (and scales) Power first, layout second Design for worst case: full brightness / full white Leave headroom on the PSU (don’t run at the edge) Don’t rely on one power input for long runs—plan injection points early Wire gauge matters more than people expect (connectors too) Make the source invisible A diffuser channel is the fastest “DIY → architectural” upgrade If hotspots persist, increasing LED-to-diffuser distance often helps more than “better plastic” Treat data like a comms link Common ground is mandatory Keep the first data lead short Avoid routing data alongside high-current power runs Buffer/differential methods beat “hope and prayer” when distances grow A quick debugging model When something looks wrong, ask: Does it worsen toward the end? → power Random pixels/glitches? → data Looks mathematically smooth but visually harsh? → optics/gamma/perception 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 emmma Follow I am from China Location 中国 Pronouns led lover Joined Sep 10, 2025 More from emmma What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Battling Winter Darkness: How Better Lighting Saved My Productivity (No Ceiling Lights Allowed) # hardware # productivity # beginners 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:49:47 |
https://www.npopov.com/2012/03/28/Understanding-PHPs-internal-array-implementation.html | Understanding PHP's internal array implementation (PHP's Source Code for PHP Developers - Part 4) Blog by nikic . Find me on GitHub , StackOverflow , Twitter and Mastodon . Learn more about me . « Back to article overview. Understanding PHP's internal array implementation (PHP's Source Code for PHP Developers - Part 4) 28. March 2012 Welcome back to the fourth part of the “PHP’s Source Code for PHP Developers” series, in which we’ll cover how PHP arrays are internally represented and used throughout the code base. In case you missed them, here are the previous parts of this series: Part 1: Structure of the source code and introduction to C Part 2: Finding and understanding PHP’s internal function definitions Part 3: PHP’s internal value representation: The zval Everything is a hash table! Basically, everything in PHP is a hash table. Not only are hash tables used in the underlying implementation of PHP arrays, they are also used to store object properties and methods, functions, variables and pretty much everything else. And because the hash table is so fundamental to PHP, it is worth having a deeper look into how it works. So, what is a hash table? Remember that in C arrays are basically chunks of memory, which you can access by index. Thus arrays in C only have integer keys and have to be continuous (i.e. you can’t have a key 0 and the next key is 1332423442 ). There is no such thing as an associative array. And this is where hash tables come in: They convert string keys into normal integer keys using a hash function. The result can then be used as an index into a normal C array (aka chunk of memory). The problem here obviously is that the hash function can have collisions, i.e. multiple string keys can yield the same hash. For example in a PHP array with up to 64 elements the strings "foo" and "oof" would have the same hash. This problem is solved by not storing the value directly at the generated index, but storing a linked list of possible values instead. HashTable and Bucket So, after the basic concept of hash tables is clear, let’s have a look at the structures actually used in PHP’s hash table implementation: The first one is the HashTable : typedef struct _hashtable { uint nTableSize; uint nTableMask; uint nNumOfElements; ulong nNextFreeElement; Bucket *pInternalPointer; Bucket *pListHead; Bucket *pListTail; Bucket **arBuckets; dtor_func_t pDestructor; zend_bool persistent; unsigned char nApplyCount; zend_bool bApplyProtection; #if ZEND_DEBUG int inconsistent; #endif } HashTable; Let’s quickly go through it: nNumOfElements specifies how many values are currently stored in the array. This is also the number that count($array) returns. nTableSize specifies the size of the internal C array. It is always the next power of 2 greater or equal to nNumOfElements . E.g. if an array stores 32 elements, the internal C array also has a size of 32. But if one more element is added, i.e. the array then contains 33 elements, the internal C array is resized to 64 elements. This is done to always keep the hash table efficient in space and time. It is clear that if the internal array is too small there will be many collisions and the performance will degrade. If the internal array is too big on the other hand, we’d be wasting memory. The power-of-2 size is a good compromise. nTableMask is the table size minus one. This mask is used to adjust the generated hashes for the current table size. For example the actual hash for "foo" (through the DJBX33A hashing function ) is 193491849. If we currently have a table size of 64, we obviously can’t use that as an index into the array. Instead we only take the lower bits of the hash by applying the table mask: hash | 193491849 | 0b1011100010000111001110001001 & mask | & 63 | & 0b0000000000000000000000111111 --------------------------------------------------------- = index | = 9 | = 0b0000000000000000000000001001 nNextFreeElement is the next free integer key, which is used when you append to an array using $array[] = xyz . pInternalPointer stores the current position in the array. This is used for foreach iteration and can be accessed using the reset() , current() , key() , next() , prev() and end() functions. pListHead and pListTail specify the first and last element of the array. Remember: PHP arrays have an order. E.g. ['foo' => 'bar', 'bar' => 'foo'] and ['bar' => 'foo', 'foo' => 'bar'] contain the same elements, but have a different order. arBuckets is the “internal C array” we were always talking about. It’s defined as a Bucket ** , so it can be seen as an array of bucket pointers (we’ll get to what exactly a Bucket is in a minute). pDestructor is the destructor for the values. If a value is removed from the HT this function will be called on it. For a normal array the destructor function is zval_ptr_dtor . zval_ptr_dtor will reduce the reference count of the zval and, if it reaches 0, destroy and free it. The last four properties aren’t really of interest to us. So let’s just say that persistent specifies that the hash table can live between multiple requests, nApplyCount and bApplyProtection are used to prevent infinite recursion in some places and inconsistent is used to catch incorrect uses of hash tables in debug mode. Let’s move on to the second important structure: Bucket : typedef struct bucket { ulong h; uint nKeyLength; void *pData; void *pDataPtr; struct bucket *pListNext; struct bucket *pListLast; struct bucket *pNext; struct bucket *pLast; const char *arKey; } Bucket; h is the hash (without the table mask applied). arKey is used to save string keys. nKeyLength is the corresponding length. For integer keys those two aren’t used. pData or pDataPtr is used to store the actual value. For PHP arrays that value is a zval (but it’s also used for other things internally.) Don’t bother with the fact that there are two properties for this. The difference between them is who is responsible for freeing the value. pListNext and pListLast specify the order of the array elements. If PHP wants to traverse the array it starts off at the pListHead bucket (specified in the HashTable struct) and then always takes the pListNext bucket. The same works in reverse, by starting at pListTail and always following pListLast . (You can do this in userland by calling end() and then always calling prev() .) pNext and pLast form the “linked list of possible values” I mentioned above. The arBuckets array stores a pointer to the first possible bucket. If that bucket hasn’t the right key, PHP will look at the bucket which pNext points to. This is done until the right bucket is found. pLast can be used to do the same in reverse. As you can see PHP’s hash table implementation is fairly complex. This is the price one has to pay for its ultra-flexible array type. How are hash tables used? The Zend Engine defines a large number of API functions for the work with hash tables. An overview of low-level hash table functions can be found in zend_hash.h . Additionally the ZE defines a set of slightly higher level APIs in zend_API.h . We don’t have time to go through all of these, but we can look at a sample function to see at least some of them in action. We’ll use array_fill_keys as that sample function. Using the technique outlined in the second part you should be able to find the function definition in ext/standard/array.c easily. Let’s quickly walk through it now. As always there’s a set of variable declarations and a zend_parse_parameters call at the top: zval *keys, *val, **entry; HashPosition pos; if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "az", &keys, &val) == FAILURE) { return; } The az obviously means that the first parameter is an a rray (fetched into the keys variable) and the second one is an arbitrary z val (fetched into the val variable). After the parameters are parsed the array to be returned is initialized: /* Initialize return array */ array_init_size(return_value, zend_hash_num_elements(Z_ARRVAL_P(keys))); This line contains already three important parts of the array API: The Z_ARRVAL_P macro fetches the hash table from a zval . zend_hash_num_elements fetches the number of elements in a hash table (the nNumOfElements property). array_init_size initializes an array with a size hint. So this line initializes an array into return_value with the same size as the keys array. The size hint here is just an optimization. The function could have also called just array_init(return_value) , in which case PHP would have to do multiple resizes as more and more elements are added to the array. By specifying an explicit size, PHP allocates the right amount of memory from the start. After the return array initialization the function loops through the keys array using a while loop with roughly this structure: zend_hash_internal_pointer_reset_ex(Z_ARRVAL_P(keys), &pos); while (zend_hash_get_current_data_ex(Z_ARRVAL_P(keys), (void **)&entry, &pos) == SUCCESS) { // some code zend_hash_move_forward_ex(Z_ARRVAL_P(keys), &pos); } This can be translated to PHP code easily: reset($keys); while (null !== $entry = current($keys)) { // some code next($keys); } Which is the same as: foreach ($keys as $entry) { // some code } The only real difference is that the C iteration doesn’t use the internal array pointer, but uses it’s own pos variable to store the current position. The code within the loop has two branches: One for integer keys and one for other keys. The integer key branch contains only two lines: zval_add_ref(&val); zend_hash_index_update(Z_ARRVAL_P(return_value), Z_LVAL_PP(entry), &val, sizeof(zval *), NULL); This is pretty straightforward: First the refcount of the value is increased (adding the value to the hash table means adding another reference to it) and then the value is actually inserted into the hash table. The arguments of the zend_hash_index_update macro are the hash table to update Z_ARRVAL_P(return_value) , the integer index Z_LVAL_PP(entry) , the value &val , the size of the value sizeof(zval *) and the destination pointer (which we don’t care about, thus NULL ). The non-integer-key branch is slightly more complicated: zval key, *key_ptr = *entry; if (Z_TYPE_PP(entry) != IS_STRING) { key = **entry; zval_copy_ctor(&key); convert_to_string(&key); key_ptr = &key; } zval_add_ref(&val); zend_symtable_update(Z_ARRVAL_P(return_value), Z_STRVAL_P(key_ptr), Z_STRLEN_P(key_ptr) + 1, &val, sizeof(zval *), NULL); if (key_ptr != *entry) { zval_dtor(&key); } First the key is converted to a string (unless it already is one) using convert_to_string . But before this can be done the entry has to be copied into a new key variable. The key = **entry line takes care of that. Additionally zval_copy_ctor has to be called, otherwise complex structures (like strings or arrays) won’t be copied correctly. The copy is necessary to ensure that the cast doesn’t change the original array. Without the copy the cast would modify not only our local variable, but also the element in the keys array (which obviously would be quite unexpected to the user). Obviously the copy has to be removed again after the loop, which is what the zval_dtor(&key) line does. The difference between zval_ptr_dtor and zval_dtor is that zval_ptr_dtor only destroys the zval if the refcount reaches 0, whereas zval_dtor destroys it always, regardless of the refcount. That’s why you’ll find zval_ptr_dtor used with “normal” values and zval_dtor with temporary variables, which aren’t used anywhere else anyways. Also zval_ptr_dtor frees the zval after destroying it, while zval_dtor does not. As we never malloc() d anything, we also don’t have to free() , so zval_dtor is the right choice in this respect too. Now, let’s look at the last two lines left (the important ones ^^): zval_add_ref(&val); zend_symtable_update(Z_ARRVAL_P(return_value), Z_STRVAL_P(key_ptr), Z_STRLEN_P(key_ptr) + 1, &val, sizeof(zval *), NULL); Those are very similar to what was done in the integer-key branch. The difference is that now zend_symtable_update is called instead of zend_hash_index_update and the string key and it’s length are passed in. The Symtable The “normal” function for inserting string keys into a hash table is zend_hash_update , but here zend_symtable_update is used instead. What’s the difference? A symtable basically is a special type of hash table, which is used for arrays. The difference to the ordinary hash table is how it handles numeric string keys: In a symtable the keys "123" and 123 are considered identical. So if you store a value in $array["123"] , you can then retrieve it using $array[123] . The underlying implementation could use two ways: Either save both 123 and "123" using the "123" key or save both using the 123 key. PHP obviously chooses the latter option (as integers are smaller and faster than strings). You can have a little bit of fun with symtables, if you manage to somehow insert the "123" key without it being cast to 123 . One way is to exploit the array to object cast: $obj = new stdClass ; $obj -> { 123 } = "foo" ; $arr = ( array ) $obj ; var_dump ( $arr [ 123 ]); // Undefined offset: 123 var_dump ( $arr [ "123" ]); // Undefined offset: 123 Object properties are always saved under string keys, even if they are numbers. So the $obj->{123} = 'foo' line actually saves "foo" under the "123" index, not the 123 index. When doing the array cast this is not changed. But as both $arr[123] and $arr["123"] try to access the 123 index (not the "123" index that actually exists), both throw an error. So, congratulations, you’ve created a hidden array element! In the next part The next part will again be published on ircmaxell’s blog . It will analyze how objects and classes work internally. If you liked this article, you may want to browse my other articles or follow me on Twitter or Mastodon . | 2026-01-13T08:49:47 |
https://discuss.opensource.org/c/general/4 | General - OSI Discuss OSI Discuss General Topic Replies Views Activity Welcome to the OSI community! :wave: 0 1184 January 11, 2024 About the General category 0 92 January 11, 2024 Open Policy Alliance Welcomes the Open Source Technology Improvement Fund as New Member 0 12 January 8, 2026 Proposal to Clarify the Spirit and Purpose of the Open Source Definition 5 188 January 7, 2026 Seeking brief perspectives from contributors on ethics of open-source commercialization (student research) 0 24 January 5, 2026 Top Open Source licenses in 2025 1 96 December 28, 2025 Celebrating Generosity and Growth in the OSI Community 0 42 December 12, 2025 Open Source Without Borders: Reflections from COSCon'25 0 47 December 10, 2025 DPGA’s Annual Members Meeting: Advancing Open Source & DPGs for the Public Good 0 41 December 6, 2025 Patents and Open Source: Understanding the Risks and Available Solutions 0 29 December 4, 2025 OFA Symposium 2025 and the Launch of the Open Technology Research Network (OTRN) 0 47 December 3, 2025 Open Source: A global commons to enable digital sovereignty 0 72 November 24, 2025 Sustaining Open Source: The Next 25 Years Depend on What We Do Together Now 0 67 November 18, 2025 Is it possible to create a license based on 0BSD + extra development duties? regulation , clearlydefined , standards , question 0 47 November 16, 2025 Opensource Licensing: Prevent hijacking question 1 105 November 7, 2025 Must-See Recordings Now Available 0 55 November 6, 2025 Help us improve the EU Cyber Resilience Act Standards! 0 40 November 5, 2025 State of the Source at ATO 2025: State of the “Open” AI 0 47 November 5, 2025 State of the Source at ATO 2025: AI and Data Governance 0 40 November 4, 2025 State of the Source at ATO 2025: Cybersecurity 0 32 November 4, 2025 State of the Source at ATO 2025: Sustaining the Open Source Ecosystem 0 38 November 3, 2025 State of the Source at ATO 2025: Licensing 201 0 29 October 31, 2025 The Open Source Community and U.S. Public Policy 0 48 October 30, 2025 Open Source Initiative now accepting your application for Executive Director 0 52 October 27, 2025 Participate in the 2026 State of Open Source Survey 0 65 October 22, 2025 Open Source Initiative Executive Director search begins 0 55 October 10, 2025 Open Source Congress 2025 and Stakeholder Day: building a global agenda for Open Source 0 73 October 7, 2025 Hacktoberfest and the OSI: Growing Open Source adoption 0 52 October 2, 2025 BASIC is now Open Source 0 103 September 5, 2025 ClearlyDefined at SAP: enhancing Open Source license compliance through Open Source data 0 73 August 12, 2025 next page → Home Categories Guidelines Terms of Service Privacy Policy Powered by Discourse , best viewed with JavaScript enabled | 2026-01-13T08:49:47 |
https://www.npopov.com/2021/10/13/How-opcache-works.html | How opcache works Blog by nikic . Find me on GitHub , StackOverflow , Twitter and Mastodon . Learn more about me . « Back to article overview. How opcache works 13. October 2021 The opcache PHP extension implements various functionality to speed up PHP in a transparent manner. As the name indicates, its origin and primary purpose is opcode caching, but nowadays it also contains an optimizer and just-in-time compiler. However, this blog post will focus only on the opcode caching aspect. Opcache has three layers of caches: The original shared memory cache, the file cache introduced in PHP 7, and the preloading functionality added in PHP 7.4. We’ll discuss all of these in turn. While opcache is nominally an independent extension, its functionality is tightly dependent on engine implementation details, and modifications to the engine often require changes to opcache as well. As such, the way opcache works differs significantly between PHP versions. This article describes the state as of PHP 8.1 and highlights some of the changes in this version. Shared memory The primary purposes of opcache is to cache compilation artifacts in shared memory, to avoid the need to recompile PHP scripts on every execution. On Unix-like systems, a single fixed-size shared memory (SHM) segment is allocated on startup. To handle requests, PHP will then either fork additional processes or spawn additional threads. These processes/threads will see the SHM segment at the same address. As Windows does not support forking, it is common to instead spawn entirely separate PHP processes, which do not have any shared address space. This is a big problem for opcache, because it requires the SHM segment to be mapped at the same address in each process. Otherwise, pointers into SHM would not be valid across processes. To make this work, opcache stores the SHM base address, and tries to map the segment at the same address in other processes. If this fails, opcache falls back to using the file cache. However, even if it succeeds, there are limitations: While this guarantees the same address for the SHM segment, the addresses of internal functions/classes may differ between processes due to ASLR. This means that on Windows, it’s not possible for cached artifacts to depend on internal functions/classes etc. Windows is the only platform where two unrelated PHP processes can share the same opcache SHM. For example, it’s possible for two concurrent CLI invocations to share the same cache, which is not possible on other operating systems. The opcache.cache_id setting exists to force a different cache in this case. Because maintaining the separate behavior for Windows is something of a pain, opcache may drop support for reattachment from unrelated processes in the future, which means that on Windows, the use of a thread-based rather than process-based SAPI would be required. Locking and immutability When shared memory is in play, it is always important to consider your access model. As we do not want to perform any fine-grained locking operations or atomic reference counting at runtime, opcache’s memory model ends up being very simple: Shared memory is immutable. Opcache essentially only has two locks: One is a write lock, which can be held only by one process allowed to modify SHM. While the write lock is held, other processes are still allowed to read SHM. As such, holding the write lock generally only allows you to allocate new memory in the SHM segment and write to it, but not to modify already allocated and potentially used shared memory (with some exceptions). The opcache.protect_memory option can be used to mprotect the whole SHM segment whenever the write lock is not held, which is useful to detect violations of the immutability invariant (but should not be enabled in production for performance reasons). The other lock is a read lock that is acquired when a request makes use of SHM for the first time. It does not track what is being used and whether it stops being used. The only purpose is to record that the cache is being used somehow in this request. The purpose of this lock is to facilitate opcache restarts: Because we don’t track which parts of the cache are being used in a fine-grained manner, it’s not possible to ever remove anything from the opcode cache. When the cache runs full, a restart is scheduled instead. If a restart is scheduled, then newly started requests will not use the SHM cache (but may fall back to the file cache). When the number of users drops to zero, the entire cache is cleared and we can start from scratch. If the number of users does not drop to zero within opcache.force_restart_timeout , then opcache will kill remaining users. Map pointers Some of the structures stored in the SHM cache need (or at least want) to reference per-request data. For example, while a function definition is generally immutable, it may contain static variables, which will be different for each request. Similarly, functions use a run-time cache to cache request-specific symbol resolutions. As we can’t store per-request information in the immutable shared memory cache, we use a “map pointer” indirection instead. Rather than storing a pointer to the static variables, we instead store a reference to where the static variables are going to be stored. In the current implementation, a map pointer takes one of two forms: Either it is a plain pointer to the actual storage of the pointer, which is the representation used when the structure is not cached in SHM. The indirection pointer is typically arena allocated. Alternatively, the map pointer only stores an offset from a base address, where the base address is going to be different for each request. This is the representation used for immutable structures in shared memory. We track how large the used map pointer area needs to be and zero it on each request. For mutable memory: map_ptr & 1 == 0 map pointer ----> indirection pointer -----> static variables (arena allocated) For immutable memory: map_ptr & 1 == 1 map base pointer: slot 0 slot 1 + map offset: slot 2 -----> static variables slot 3 While it’s clear why we need the indirection in the second case (separate map pointer area for each request), one may wonder what the purpose of the indirection pointer in the first case is: As the memory is mutable, we could store the static variables pointer directly. This is indeed just a historical artifact, and the unnecessary indirection will likely be gone in PHP 8.2. Interned strings At this point, let’s take a brief aside to discuss interned strings. Strings in PHP are represented as a reference-counted structure that stores the string length, its contents and its hash. While strings may be shared, there may also be multiple strings with the same content, if they are created independently. Interned strings are deduplicated: There will only be one interned string with a given content. This saves memory and can make comparison more efficient, because the pointer equality fast-path is more likely to trigger. Interned strings in PHP are also immutable by dint of not being reference-counted. Without opcache, PHP separates interned strings into persistent and per-request. Persistent interned strings are created during startup, for example for the names of internal classes/functions. Per-request strings are created for symbols and literals in PHP scripts (if no persistent interned string for them exists yet) and discarded at the end of the request. When opcache is enabled, interned strings are stored in SHM, so they are deduplicated across processes and can be referenced by structures cached in SHM. On startup, opcache will copy persistent interned strings into SHM on a best-effort basis (it may not know about all pointers that are stored somewhere), but this is not important for correctness. Additionally, creation of interned strings during the request is disabled. Normal, non-interned strings are created instead. Only when the compiled script is cached (and the SHM write lock acquired) do strings get converted into SHM interned strings. Class entry cache PHP scripts contain a lot of references to classes in string form, e.g. new Foo or a Foo $param type. As the actual identity of Foo might differ between requests, it’s not possible to compile these down to a direct class reference. Fetching a class entry from the class name is relatively expensive for how common it is: We need to lower case the string and look it up in the class hash table. For references like new Foo this lookup is cached in the function run time cache. However, it’s not always possible to use the run time cache. For example, property type checks can’t make use of the run time cache and prior to PHP 8.1 used to instead replace a string name with a class entry directly inside the type, which means that the type couldn’t live in SHM. PHP 8.1 introduced a class entry cache, which combines interned strings with map pointers. For interned strings used in certain positions (class declarations and type names) a map pointer slot is allocated, which stores the resolved class entry for this name. To avoid increasing the string size, this uses a trick: Normally, interned strings always have a reference count of 2. However, the actual reference count doesn’t matter, it only needs to be larger than 1 to ensure the string gets duplicated on modification. Strings with refcount 1 can be modified in place. As such, we can use the refcount field to store a map pointer offset to use as the class entry cache. This does come with some limitations, because it is bound to the interned string mechanism. For example, if opcache is enabled but a script is not cached, then interned strings won’t be used and consequently the class entry cache will not be available. One of the nice things about the class entry cache is that it is fairly generic and not bound to specific language constructs (like the run-time cache). If you write new ReflectionClass(Foo::class) , the class lookup can be cached, even though it happens dynamically. Persist The actual persistence of scripts into shared memory is relatively straightforward. The script is first compiled as usual, apart from some options to make sure no cross-file dependencies are used during compilation. The compilation result is moved out of the global function/class tables into a self-contained persistent script structure. Then the size of the required shared memory segment is calculated. This step must mirror the logic of the actual persist step exactly, but (mostly) doesn’t modify the script. If the shared memory allocation fails, we can still bypass opcache and execute it as usual. The only modification the “persist calc” step does is to convert strings into SHM interned strings if possible, as interned strings are stored in a fixed size segment that is separate from the persisted script. Strings that are successfully interned do not count towards the script size. Finally, the persist step copies the script into shared memory and frees the original script. To do so it keeps track of an xlat table, which maps the original pointers to the new pointers in shared memory. This allows resolving repeated uses of the same pointer. Inheritance cache Classes internally come in two forms. Unlinked classes represent a class declaration as you would write it in the code: It contains the methods declared in that class and references dependencies (parent class, interfaces, traits) as strings. Linked classes represent a class declaration that has successfully finished inheritance. It contains inherited methods/properties/etc and references dependencies as resolved class entries. When looking at a single script, classes usually exist in unlinked form (unless they happen to have no dependencies). Linking classes requires looking at classes in other files. However, the used class declaration might differ from one request to the next. Prior to PHP 8.1, this meant that only the unlinked class template was cached, and inheritance still has to be performed on each request. As inheritance is a fairly expensive process, this had a non-trivial performance impact. PHP 8.1 addresses this with the introduction of the inheritance cache. The inheritance cache stores the linked inheritance result for a given set of dependencies. When inheritance is requested at run-time, the class name dependencies are resolved into class entries and if a cache entry for this set of dependencies already exists, it is used. While dependencies can differ between requests, in practice they will usually be the same, so inheritance only needs to be performed once. If no cache entry exists, the unlinked class is copied from SHM into mutable per-process memory and the inheritance process is performed on it (in-place). The result is persisted into the inheritance cache using essentially the normal persistence process, together with the dependencies for which this cache entry is valid. Preloading Preloading is a more radical solution to the inheritance problem: Anything loaded by the preload script will survive across requests. As such, it is safe to make use of cross-script dependencies in this case. The disadvantage is that the preload state cannot be changed without restarting PHP. Some of the preloading benefit has likely been obsoleted by the inheritance cache in PHP 8.1, though preloading still has some advantages: Classes are available in fully inherited form at the start of the request. The only per-request cost of preloading is clearing the map pointer area. Normal opcache usage still requires going through autoloading, looking up persistent scripts, registering entries in global hash tables, looking up and checking dependencies for the inheritance cache, etc. Preloading can operate in two modes: When classes are simply loaded using require , inheritance will happen as it usually does and preloading can support classes with arbitrarily complex inheritance scenarios (including variance cycles). This also makes it easy to ensure that any necessary dependencies are provided by an autoloader. Alternatively, it is possible to preload files using opcache_compile_file() . In this case opcache will try to preload the class if all dependencies for it are also available. Otherwise, it will throw a warning and cache the script the old-fashioned way. Prior to PHP 8.1 the “all dependencies” requirement was rather problematic. In earlier PHP versions, unlinked classes were persisted in two parts: One actually immutable one, and another that had to be copied into per-request memory, because it may be modified at run-time. This included property types as well as constant/property initializers. If these could not be fully resolved during preloading, the class couldn’t be preloaded, because we cannot perform per-request copies in that case. In PHP 8.1 all remaining run-time modifiable parts were switched to map pointers, thus relaxing the constraint on what counts as a “dependency”. Now this only includes parents/interfaces/traits, as well as types necessary to perform variance checks. The variance checks are another problem: Whether or not an argument/return type is required to perform variance checks is very hard to determine in advance. This depends on whether a method is actually an override (which is non-obvious in the presence of traits) and whether the subtyping relationship can be determined without loading the class (e.g. if the types in the parent and child method are exactly the same). Previous PHP versions solved this heuristically, requiring more dependencies than necessary. PHP 8.1 instead will simply attempt inheritance on a copy of the class and discard it if it fails. This means that opcache_compile_file() based preloading should be a lot more predictable in PHP 8.1. File cache The file cache introduced in PHP 7 can be used either standalone ( opcache.file_cache_only ) or in conjunction with the SHM cache as a second-level cache. In the latter case, it will be used on a cold start, or when the SHM cache is unavailable during an opcache restart. On Windows, the file cache fallback is enabled by default, to make sure that at least some caching is available if SHM reattachment fails. File cache serialization starts from the persisted representation of the script, either in SHM (second-level) or in a temporary memory region (standalone), but created using the usual persistence mechanism. The actual serialization then replaces all pointers with offsets into the memory region (“pointer unswizzling”). This allows efficient unserialization by adding the new base pointer to all pointers. The primary complication in this model are interned strings, as these are the only pointers that do not point into the persisted memory region. Referenced interned strings are instead serialized into a separate memory region. On unserialization, an attempt is made to convert these back to SHM interned strings. Unserialization works by copying the file contents (including the serialized script and the interned string area) into a buffer. In standalone mode, this buffer is non-temporary and unserialization (pointer swizzling) occurs directly in this buffer. In second-level mode, this buffer is usually temporary. Instead a SHM allocation is made, into which the serialized script is copied and where it is unserialized. In this case all interned strings also need to be converted into SHM interned strings. The temporary buffer can then be discarded. However, if not all interned strings can be inserted due to an interned string buffer overflow, then the SHM segment is abandoned and a per-request unserialization as in the standalone case is performed. If you liked this article, you may want to browse my other articles or follow me on Twitter or Mastodon . | 2026-01-13T08:49:47 |
https://docs.python.org/3/whatsnew/3.14.html#pep-734-multiple-interpreters-in-the-standard-library | What’s new in Python 3.14 — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents What’s new in Python 3.14 Summary – Release highlights New features PEP 649 & PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template string literals PEP 768 : Safe external debugger interface A new type of interpreter Free-threaded mode improvements Improved error messages PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Other language changes Built-ins Command line and environment PEP 758: Allow except and except* expressions without brackets PEP 765: Control flow in finally blocks Incremental garbage collection Default interactive shell New modules Improved modules argparse ast asyncio calendar concurrent.futures configparser contextvars ctypes curses datetime decimal difflib dis errno faulthandler fnmatch fractions functools getopt getpass graphlib heapq hmac http imaplib inspect io json linecache logging.handlers math mimetypes multiprocessing operator os os.path pathlib pdb pickle platform pydoc re socket ssl struct symtable sys sys.monitoring sysconfig tarfile threading tkinter turtle types typing unicodedata unittest urllib uuid webbrowser zipfile Optimizations asyncio base64 bdb difflib gc io pathlib pdb textwrap uuid zlib Removed argparse ast asyncio email importlib.abc itertools pathlib pkgutil pty sqlite3 urllib Deprecated New deprecations Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.17 Pending removal in Python 3.18 Pending removal in Python 3.19 Pending removal in future versions CPython bytecode changes Pseudo-instructions C API changes Python configuration C API New features in the C API Limited C API changes Removed C APIs Deprecated C APIs Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.18 Pending removal in future versions Build changes build-details.json Discontinuation of PGP signatures Free-threaded Python is officially supported Binary releases for the experimental just-in-time compiler Porting to Python 3.14 Changes in the Python API Changes in annotations ( PEP 649 and PEP 749 ) Implications for annotated code Implications for readers of __annotations__ Related changes from __future__ import annotations Changes in the C API Notable changes in 3.14.1 Previous topic What’s New in Python Next topic What’s New In Python 3.13 This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » What’s New in Python » What’s new in Python 3.14 | Theme Auto Light Dark | What’s new in Python 3.14 ¶ Editors : Adam Turner and Hugo van Kemenade This article explains the new features in Python 3.14, compared to 3.13. Python 3.14 was released on 7 October 2025. For full details, see the changelog . See also PEP 745 – Python 3.14 release schedule Summary – Release highlights ¶ Python 3.14 is the latest stable release of the Python programming language, with a mix of changes to the language, the implementation, and the standard library. The biggest changes include template string literals , deferred evaluation of annotations , and support for subinterpreters in the standard library. The library changes include significantly improved capabilities for introspection in asyncio , support for Zstandard via a new compression.zstd module, syntax highlighting in the REPL, as well as the usual deprecations and removals, and improvements in user-friendliness and correctness. This article doesn’t attempt to provide a complete specification of all new features, but instead gives a convenient overview. For full details refer to the documentation, such as the Library Reference and Language Reference . To understand the complete implementation and design rationale for a change, refer to the PEP for a particular new feature; but note that PEPs usually are not kept up-to-date once a feature has been fully implemented. See Porting to Python 3.14 for guidance on upgrading from earlier versions of Python. Interpreter improvements: PEP 649 and PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template strings PEP 758 : Allow except and except* expressions without brackets PEP 765 : Control flow in finally blocks PEP 768 : Safe external debugger interface for CPython A new type of interpreter Free-threaded mode improvements Improved error messages Incremental garbage collection Significant improvements in the standard library: PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Syntax highlighting in the default interactive shell , and color output in several standard library CLIs C API improvements: PEP 741 : Python configuration C API Platform support: PEP 776 : Emscripten is now an officially supported platform , at tier 3 . Release changes: PEP 779 : Free-threaded Python is officially supported PEP 761 : PGP signatures have been discontinued for official releases Windows and macOS binary releases now support the experimental just-in-time compiler Binary releases for Android are now provided New features ¶ PEP 649 & PEP 749 : Deferred evaluation of annotations ¶ The annotations on functions, classes, and modules are no longer evaluated eagerly. Instead, annotations are stored in special-purpose annotate functions and evaluated only when necessary (except if from __future__ import annotations is used). This change is designed to improve performance and usability of annotations in Python in most circumstances. The runtime cost for defining annotations is minimized, but it remains possible to introspect annotations at runtime. It is no longer necessary to enclose annotations in strings if they contain forward references. The new annotationlib module provides tools for inspecting deferred annotations. Annotations may be evaluated in the VALUE format (which evaluates annotations to runtime values, similar to the behavior in earlier Python versions), the FORWARDREF format (which replaces undefined names with special markers), and the STRING format (which returns annotations as strings). This example shows how these formats behave: >>> from annotationlib import get_annotations , Format >>> def func ( arg : Undefined ): ... pass >>> get_annotations ( func , format = Format . VALUE ) Traceback (most recent call last): ... NameError : name 'Undefined' is not defined >>> get_annotations ( func , format = Format . FORWARDREF ) {'arg': ForwardRef('Undefined', owner=<function func at 0x...>)} >>> get_annotations ( func , format = Format . STRING ) {'arg': 'Undefined'} The porting section contains guidance on changes that may be needed due to these changes, though in the majority of cases, code will continue working as-is. (Contributed by Jelle Zijlstra in PEP 749 and gh-119180 ; PEP 649 was written by Larry Hastings.) See also PEP 649 Deferred Evaluation Of Annotations Using Descriptors PEP 749 Implementing PEP 649 PEP 734 : Multiple interpreters in the standard library ¶ The CPython runtime supports running multiple copies of Python in the same process simultaneously and has done so for over 20 years. Each of these separate copies is called an ‘interpreter’. However, the feature had been available only through the C-API . That limitation is removed in Python 3.14, with the new concurrent.interpreters module. There are at least two notable reasons why using multiple interpreters has significant benefits: they support a new (to Python), human-friendly concurrency model true multi-core parallelism For some use cases, concurrency in software improves efficiency and can simplify design, at a high level. At the same time, implementing and maintaining all but the simplest concurrency is often a struggle for the human brain. That especially applies to plain threads (for example, threading ), where all memory is shared between all threads. With multiple isolated interpreters, you can take advantage of a class of concurrency models, like Communicating Sequential Processes (CSP) or the actor model, that have found success in other programming languages, like Smalltalk, Erlang, Haskell, and Go. Think of multiple interpreters as threads but with opt-in sharing. Regarding multi-core parallelism: as of Python 3.12, interpreters are now sufficiently isolated from one another to be used in parallel (see PEP 684 ). This unlocks a variety of CPU-intensive use cases for Python that were limited by the GIL . Using multiple interpreters is similar in many ways to multiprocessing , in that they both provide isolated logical “processes” that can run in parallel, with no sharing by default. However, when using multiple interpreters, an application will use fewer system resources and will operate more efficiently (since it stays within the same process). Think of multiple interpreters as having the isolation of processes with the efficiency of threads. While the feature has been around for decades, multiple interpreters have not been used widely, due to low awareness and the lack of a standard library module. Consequently, they currently have several notable limitations, which are expected to improve significantly now that the feature is going mainstream. Current limitations: starting each interpreter has not been optimized yet each interpreter uses more memory than necessary (work continues on extensive internal sharing between interpreters) there aren’t many options yet for truly sharing objects or other data between interpreters (other than memoryview ) many third-party extension modules on PyPI are not yet compatible with multiple interpreters (all standard library extension modules are compatible) the approach to writing applications that use multiple isolated interpreters is mostly unfamiliar to Python users, for now The impact of these limitations will depend on future CPython improvements, how interpreters are used, and what the community solves through PyPI packages. Depending on the use case, the limitations may not have much impact, so try it out! Furthermore, future CPython releases will reduce or eliminate overhead and provide utilities that are less appropriate on PyPI. In the meantime, most of the limitations can also be addressed through extension modules, meaning PyPI packages can fill any gap for 3.14, and even back to 3.12 where interpreters were finally properly isolated and stopped sharing the GIL . Likewise, libraries on PyPI are expected to emerge for high-level abstractions on top of interpreters. Regarding extension modules, work is in progress to update some PyPI projects, as well as tools like Cython, pybind11, nanobind, and PyO3. The steps for isolating an extension module are found at Isolating Extension Modules . Isolating a module has a lot of overlap with what is required to support free-threading , so the ongoing work in the community in that area will help accelerate support for multiple interpreters. Also added in 3.14: concurrent.futures.InterpreterPoolExecutor . (Contributed by Eric Snow in gh-134939 .) See also PEP 734 PEP 750 : Template string literals ¶ Template strings are a new mechanism for custom string processing. They share the familiar syntax of f-strings but, unlike f-strings, return an object representing the static and interpolated parts of the string, instead of a simple str . To write a t-string, use a 't' prefix instead of an 'f' : >>> variety = 'Stilton' >>> template = t 'Try some {variety} cheese!' >>> type ( template ) <class 'string.templatelib.Template'> Template objects provide access to the static and interpolated (in curly braces) parts of a string before they are combined. Iterate over Template instances to access their parts in order: >>> list ( template ) ['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!'] It’s easy to write (or call) code to process Template instances. For example, here’s a function that renders static parts lowercase and Interpolation instances uppercase: from string.templatelib import Interpolation def lower_upper ( template ): """Render static parts lowercase and interpolations uppercase.""" parts = [] for part in template : if isinstance ( part , Interpolation ): parts . append ( str ( part . value ) . upper ()) else : parts . append ( part . lower ()) return '' . join ( parts ) name = 'Wenslydale' template = t 'Mister {name} ' assert lower_upper ( template ) == 'mister WENSLYDALE' Because Template instances distinguish between static strings and interpolations at runtime, they can be useful for sanitising user input. Writing a html() function that escapes user input in HTML is an exercise left to the reader! Template processing code can provide improved flexibility. For instance, a more advanced html() function could accept a dict of HTML attributes directly in the template: attributes = { 'src' : 'limburger.jpg' , 'alt' : 'lovely cheese' } template = t '<img {attributes} >' assert html ( template ) == '<img src="limburger.jpg" alt="lovely cheese" />' Of course, template processing code does not need to return a string-like result. An even more advanced html() could return a custom type representing a DOM-like structure. With t-strings in place, developers can write systems that sanitise SQL, make safe shell operations, improve logging, tackle modern ideas in web development (HTML, CSS, and so on), and implement lightweight custom business DSLs. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) See also PEP 750 . PEP 768 : Safe external debugger interface ¶ Python 3.14 introduces a zero-overhead debugging interface that allows debuggers and profilers to safely attach to running Python processes without stopping or restarting them. This is a significant enhancement to Python’s debugging capabilities, meaning that unsafe alternatives are no longer required. The new interface provides safe execution points for attaching debugger code without modifying the interpreter’s normal execution path or adding any overhead at runtime. Due to this, tools can now inspect and interact with Python applications in real-time, which is a crucial capability for high-availability systems and production environments. For convenience, this interface is implemented in the sys.remote_exec() function. For example: import sys from tempfile import NamedTemporaryFile with NamedTemporaryFile ( mode = 'w' , suffix = '.py' , delete = False ) as f : script_path = f . name f . write ( f 'import my_debugger; my_debugger.connect( { os . getpid () } )' ) # Execute in process with PID 1234 print ( 'Behold! An offering:' ) sys . remote_exec ( 1234 , script_path ) This function allows sending Python code to be executed in a target process at the next safe execution point. However, tool authors can also implement the protocol directly as described in the PEP, which details the underlying mechanisms used to safely attach to running processes. The debugging interface has been carefully designed with security in mind and includes several mechanisms to control access: A PYTHON_DISABLE_REMOTE_DEBUG environment variable. A -X disable-remote-debug command-line option. A --without-remote-debug configure flag to completely disable the feature at build time. (Contributed by Pablo Galindo Salgado, Matt Wozniski, and Ivona Stojanovic in gh-131591 .) See also PEP 768 . A new type of interpreter ¶ A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individual Python opcodes, rather than one large C case statement. For certain newer compilers, this interpreter provides significantly better performance. Preliminary benchmarks suggest a geometric mean of 3-5% faster on the standard pyperformance benchmark suite, depending on platform and architecture. The baseline is Python 3.14 built with Clang 19, without this new interpreter. This interpreter currently only works with Clang 19 and newer on x86-64 and AArch64 architectures. However, a future release of GCC is expected to support this as well. This feature is opt-in for now. Enabling profile-guided optimization is highly recommendeded when using the new interpreter as it is the only configuration that has been tested and validated for improved performance. For further information, see --with-tail-call-interp . Note This is not to be confused with tail call optimization of Python functions, which is currently not implemented in CPython. This new interpreter type is an internal implementation detail of the CPython interpreter. It doesn’t change the visible behavior of Python programs at all. It can improve their performance, but doesn’t change anything else. (Contributed by Ken Jin in gh-128563 , with ideas on how to implement this in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.) Free-threaded mode improvements ¶ CPython’s free-threaded mode ( PEP 703 ), initially added in 3.13, has been significantly improved in Python 3.14. The implementation described in PEP 703 has been finished, including C API changes, and temporary workarounds in the interpreter were replaced with more permanent solutions. The specializing adaptive interpreter ( PEP 659 ) is now enabled in free-threaded mode, which along with many other optimizations greatly improves its performance. The performance penalty on single-threaded code in free-threaded mode is now roughly 5-10%, depending on the platform and C compiler used. From Python 3.14, when compiling extension modules for the free-threaded build of CPython on Windows, the preprocessor variable Py_GIL_DISABLED now needs to be specified by the build backend, as it will no longer be determined automatically by the C compiler. For a running interpreter, the setting that was used at compile time can be found using sysconfig.get_config_var() . The new -X context_aware_warnings flag controls if concurrent safe warnings control is enabled. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. A new thread_inherit_context flag has been added, which if enabled means that threads created with threading.Thread start with a copy of the Context() of the caller of start() . Most significantly, this makes the warning filtering context established by catch_warnings be “inherited” by threads (or asyncio tasks) started within that context. It also affects other modules that use context variables, such as the decimal context manager. This flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Sam Gross, Matt Page, Neil Schemenauer, Thomas Wouters, Donghee Na, Kirill Podoprigora, Ken Jin, Itamar Oren, Brett Simmers, Dino Viehland, Nathan Goldbaum, Ralf Gommers, Lysandros Nikolaou, Kumar Aditya, Edgar Margffoy, and many others. Some of these contributors are employed by Meta, which has continued to provide significant engineering resources to support this project.) Improved error messages ¶ The interpreter now provides helpful suggestions when it detects typos in Python keywords. When a word that closely resembles a Python keyword is encountered, the interpreter will suggest the correct keyword in the error message. This feature helps programmers quickly identify and fix common typing mistakes. For example: >>> whille True : ... pass Traceback (most recent call last): File "<stdin>" , line 1 whille True : ^^^^^^ SyntaxError : invalid syntax. Did you mean 'while'? While the feature focuses on the most common cases, some variations of misspellings may still result in regular syntax errors. (Contributed by Pablo Galindo in gh-132449 .) elif statements that follow an else block now have a specific error message. (Contributed by Steele Farnsworth in gh-129902 .) >>> if who == "me" : ... print ( "It's me!" ) ... else : ... print ( "It's not me!" ) ... elif who is None : ... print ( "Who is it?" ) File "<stdin>", line 5 elif who is None: ^^^^ SyntaxError: 'elif' block follows an 'else' block If a statement is passed to the Conditional expressions after else , or one of pass , break , or continue is passed before if , then the error message highlights where the expression is required. (Contributed by Sergey Miryanov in gh-129515 .) >>> x = 1 if True else pass Traceback (most recent call last): File "<string>" , line 1 x = 1 if True else pass ^^^^ SyntaxError : expected expression after 'else', but statement is given >>> x = continue if True else break Traceback (most recent call last): File "<string>" , line 1 x = continue if True else break ^^^^^^^^ SyntaxError : expected expression before 'if', but statement is given When incorrectly closed strings are detected, the error message suggests that the string may be intended to be part of the string. (Contributed by Pablo Galindo in gh-88535 .) >>> "The interesting object " The important object " is very important" Traceback (most recent call last): SyntaxError : invalid syntax. Is this intended to be part of the string? When strings have incompatible prefixes, the error now shows which prefixes are incompatible. (Contributed by Nikita Sobolev in gh-133197 .) >>> ub 'abc' File "<python-input-0>" , line 1 ub 'abc' ^^ SyntaxError : 'u' and 'b' prefixes are incompatible Improved error messages when using as with incompatible targets in: Imports: import ... as ... From imports: from ... import ... as ... Except handlers: except ... as ... Pattern-match cases: case ... as ... (Contributed by Nikita Sobolev in gh-123539 , gh-123562 , and gh-123440 .) Improved error message when trying to add an instance of an unhashable type to a dict or set . (Contributed by CF Bolz-Tereick and Victor Stinner in gh-132828 .) >>> s = set () >>> s . add ({ 'pages' : 12 , 'grade' : 'A' }) Traceback (most recent call last): File "<python-input-1>" , line 1 , in <module> s . add ({ 'pages' : 12 , 'grade' : 'A' }) ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError : cannot use 'dict' as a set element (unhashable type: 'dict') >>> d = {} >>> l = [ 1 , 2 , 3 ] >>> d [ l ] = 12 Traceback (most recent call last): File "<python-input-4>" , line 1 , in <module> d [ l ] = 12 ~^^^ TypeError : cannot use 'list' as a dict key (unhashable type: 'list') Improved error message when an object supporting the synchronous context manager protocol is entered using async with instead of with , and vice versa for the asynchronous context manager protocol. (Contributed by Bénédikt Tran in gh-128398 .) PEP 784 : Zstandard support in the standard library ¶ The new compression package contains modules compression.lzma , compression.bz2 , compression.gzip and compression.zlib which re-export the lzma , bz2 , gzip and zlib modules respectively. The new import names under compression are the preferred names for importing these compression modules from Python 3.14. However, the existing modules names have not been deprecated. Any deprecation or removal of the existing compression modules will occur no sooner than five years after the release of 3.14. The new compression.zstd module provides compression and decompression APIs for the Zstandard format via bindings to Meta’s zstd library . Zstandard is a widely adopted, highly efficient, and fast compression format. In addition to the APIs introduced in compression.zstd , support for reading and writing Zstandard compressed archives has been added to the tarfile , zipfile , and shutil modules. Here’s an example of using the new module to compress some data: from compression import zstd import math data = str ( math . pi ) . encode () * 20 compressed = zstd . compress ( data ) ratio = len ( compressed ) / len ( data ) print ( f "Achieved compression ratio of { ratio } " ) As can be seen, the API is similar to the APIs of the lzma and bz2 modules. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) See also PEP 784 . Asyncio introspection capabilities ¶ Added a new command-line interface to inspect running Python processes using asynchronous tasks, available via python -m asyncio ps PID or python -m asyncio pstree PID . The ps subcommand inspects the given process ID (PID) and displays information about currently running asyncio tasks. It outputs a task table: a flat listing of all tasks, their names, their coroutine stacks, and which tasks are awaiting them. The pstree subcommand fetches the same information, but instead renders a visual async call tree, showing coroutine relationships in a hierarchical format. This command is particularly useful for debugging long-running or stuck asynchronous programs. It can help developers quickly identify where a program is blocked, what tasks are pending, and how coroutines are chained together. For example given this code: import asyncio async def play_track ( track ): await asyncio . sleep ( 5 ) print ( f '🎵 Finished: { track } ' ) async def play_album ( name , tracks ): async with asyncio . TaskGroup () as tg : for track in tracks : tg . create_task ( play_track ( track ), name = track ) async def main (): async with asyncio . TaskGroup () as tg : tg . create_task ( play_album ( 'Sundowning' , [ 'TNDNBTG' , 'Levitate' ]), name = 'Sundowning' ) tg . create_task ( play_album ( 'TMBTE' , [ 'DYWTYLM' , 'Aqua Regia' ]), name = 'TMBTE' ) if __name__ == '__main__' : asyncio . run ( main ()) Executing the new tool on the running process will yield a table like this: python -m asyncio ps 12345 tid task id task name coroutine stack awaiter chain awaiter name awaiter id ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1935500 0x7fc930c18050 Task-1 TaskGroup._aexit -> TaskGroup.__aexit__ -> main 0x0 1935500 0x7fc930c18230 Sundowning TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fa50 TMBTE TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fdf0 TNDNBTG sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32510 Levitate sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32890 DYWTYLM sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 1935500 0x7fc93161ec30 Aqua Regia sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 or a tree like this: python -m asyncio pstree 12345 └── ( T ) Task-1 └── main example.py:13 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) Sundowning │ └── album example.py:8 │ └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 │ └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 │ ├── ( T ) TNDNBTG │ │ └── play example.py:4 │ │ └── sleep Lib/asyncio/tasks.py:702 │ └── ( T ) Levitate │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) TMBTE └── album example.py:8 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) DYWTYLM │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) Aqua Regia └── play example.py:4 └── sleep Lib/asyncio/tasks.py:702 If a cycle is detected in the async await graph (which could indicate a programming issue), the tool raises an error and lists the cycle paths that prevent tree construction: python -m asyncio pstree 12345 ERROR: await-graph contains cycles - cannot print a tree! cycle: Task-2 → Task-3 → Task-2 (Contributed by Pablo Galindo, Łukasz Langa, Yury Selivanov, and Marta Gomez Macias in gh-91048 .) Concurrent safe warnings control ¶ The warnings.catch_warnings context manager will now optionally use a context variable for warning filters. This is enabled by setting the context_aware_warnings flag, either with the -X command-line option or an environment variable. This gives predictable warnings control when using catch_warnings combined with multiple threads or asynchronous tasks. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Neil Schemenauer and Kumar Aditya in gh-130010 .) Other language changes ¶ All Windows code pages are now supported as ‘cpXXX’ codecs on Windows. (Contributed by Serhiy Storchaka in gh-123803 .) Implement mixed-mode arithmetic rules combining real and complex numbers as specified by the C standard since C99. (Contributed by Sergey B Kirpichev in gh-69639 .) More syntax errors are now detected regardless of optimisation and the -O command-line option. This includes writes to __debug__ , incorrect use of await , and asynchronous comprehensions outside asynchronous functions. For example, python -O -c 'assert (__debug__ := 1)' or python -O -c 'assert await 1' now produce SyntaxError s. (Contributed by Irit Katriel and Jelle Zijlstra in gh-122245 & gh-121637 .) When subclassing a pure C type, the C slots for the new type are no longer replaced with a wrapped version on class creation if they are not explicitly overridden in the subclass. (Contributed by Tomasz Pytel in gh-132284 .) Built-ins ¶ The bytes.fromhex() and bytearray.fromhex() methods now accept ASCII bytes and bytes-like objects . (Contributed by Daniel Pope in gh-129349 .) Add class methods float.from_number() and complex.from_number() to convert a number to float or complex type correspondingly. They raise a TypeError if the argument is not a real number. (Contributed by Serhiy Storchaka in gh-84978 .) Support underscore and comma as thousands separators in the fractional part for floating-point presentation types of the new-style string formatting (with format() or f-strings ). (Contributed by Sergey B Kirpichev in gh-87790 .) The int() function no longer delegates to __trunc__() . Classes that want to support conversion to int() must implement either __int__() or __index__() . (Contributed by Mark Dickinson in gh-119743 .) The map() function now has an optional keyword-only strict flag like zip() to check that all the iterables are of equal length. (Contributed by Wannes Boeykens in gh-119793 .) The memoryview type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-126012 .) Using NotImplemented in a boolean context will now raise a TypeError . This has raised a DeprecationWarning since Python 3.9. (Contributed by Jelle Zijlstra in gh-118767 .) Three-argument pow() now tries calling __rpow__() if necessary. Previously it was only called in two-argument pow() and the binary power operator. (Contributed by Serhiy Storchaka in gh-130104 .) super objects are now copyable and pickleable . (Contributed by Serhiy Storchaka in gh-125767 .) Command line and environment ¶ The import time flag can now track modules that are already loaded (‘cached’), via the new -X importtime=2 . When such a module is imported, the self and cumulative times are replaced by the string cached . Values above 2 for -X importtime are now reserved for future use. (Contributed by Noah Kim and Adam Turner in gh-118655 .) The command-line option -c now automatically dedents its code argument before execution. The auto-dedentation behavior mirrors textwrap.dedent() . (Contributed by Jon Crall and Steven Sun in gh-103998 .) -J is no longer a reserved flag for Jython , and now has no special meaning. (Contributed by Adam Turner in gh-133336 .) PEP 758: Allow except and except* expressions without brackets ¶ The except and except* expressions now allow brackets to be omitted when there are multiple exception types and the as clause is not used. For example: try : connect_to_server () except TimeoutError , ConnectionRefusedError : print ( 'The network has ceased to be!' ) (Contributed by Pablo Galindo and Brett Cannon in PEP 758 and gh-131831 .) PEP 765: Control flow in finally blocks ¶ The compiler now emits a SyntaxWarning when a return , break , or continue statement have the effect of leaving a finally block. This change is specified in PEP 765 . In situations where this change is inconvenient (such as those where the warnings are redundant due to code linting), the warning filter can be used to turn off all syntax warnings by adding ignore::SyntaxWarning as a filter. This can be specified in combination with a filter that converts other warnings to errors (for example, passing -Werror -Wignore::SyntaxWarning as CLI options, or setting PYTHONWARNINGS=error,ignore::SyntaxWarning ). Note that applying such a filter at runtime using the warnings module will only suppress the warning in code that is compiled after the filter is adjusted. Code that is compiled prior to the filter adjustment (for example, when a module is imported) will still emit the syntax warning. (Contributed by Irit Katriel in gh-130080 .) Incremental garbage collection ¶ The cycle garbage collector is now incremental. This means that maximum pause times are reduced by an order of magnitude or more for larger heaps. There are now only two generations: young and old. When gc.collect() is not called directly, the GC is invoked a little less frequently. When invoked, it collects the young generation and an increment of the old generation, instead of collecting one or more generations. The behavior of gc.collect() changes slightly: gc.collect(1) : Performs an increment of garbage collection, rather than collecting generation 1. Other calls to gc.collect() are unchanged. (Contributed by Mark Shannon in gh-108362 .) Default interactive shell ¶ The default interactive shell now highlights Python syntax. The feature is enabled by default, save if PYTHON_BASIC_REPL or any other environment variable that disables colour is set. See Controlling color for details. The default color theme for syntax highlighting strives for good contrast and exclusively uses the 4-bit VGA standard ANSI color codes for maximum compatibility. The theme can be customized using an experimental API _colorize.set_theme() . This can be called interactively or in the PYTHONSTARTUP script. Note that this function has no stability guarantees, and may change or be removed. (Contributed by Łukasz Langa in gh-131507 .) The default interactive shell now supports import auto-completion. This means that typing import co and pressing <Tab> will suggest modules starting with co . Similarly, typing from concurrent import i will suggest submodules of concurrent starting with i . Note that autocompletion of module attributes is not currently supported. (Contributed by Tomas Roun in gh-69605 .) New modules ¶ annotationlib : For introspecting annotations . See PEP 749 for more details. (Contributed by Jelle Zijlstra in gh-119180 .) compression (including compression.zstd ): A package for compression-related modules, including a new module to support the Zstandard compression format. See PEP 784 for more details. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) concurrent.interpreters : Support for multiple interpreters in the standard library. See PEP 734 for more details. (Contributed by Eric Snow in gh-134939 .) string.templatelib : Support for template string literals (t-strings). See PEP 750 for more details. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) Improved modules ¶ argparse ¶ The default value of the program name for argparse.ArgumentParser now reflects the way the Python interpreter was instructed to find the __main__ module code. (Contributed by Serhiy Storchaka and Alyssa Coghlan in gh-66436 .) Introduced the optional suggest_on_error parameter to argparse.ArgumentParser , enabling suggestions for argument choices and subparser names if mistyped by the user. (Contributed by Savannah Ostrowski in gh-124456 .) Enable color for help text, which can be disabled with the optional color parameter to argparse.ArgumentParser . This can also be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-130645 .) ast ¶ Add compare() , a function for comparing two ASTs. (Contributed by Batuhan Taskaya and Jeremy Hylton in gh-60191 .) Add support for copy.replace() for AST nodes. (Contributed by Bénédikt Tran in gh-121141 .) Docstrings are now removed from an optimized AST in optimization level 2. (Contributed by Irit Katriel in gh-123958 .) The repr() output for AST nodes now includes more information. (Contributed by Tomas Roun in gh-116022 .) When called with an AST as input, the parse() function now always verifies that the root node type is appropriate. (Contributed by Irit Katriel in gh-130139 .) Add new options to the command-line interface: --feature-version , --optimize , and --show-empty . (Contributed by Semyon Moroz in gh-133367 .) asyncio ¶ The function and methods named create_task() now take an arbitrary list of keyword arguments. All keyword arguments are passed to the Task constructor or the custom task factory. (See set_task_factory() for details.) The name and context keyword arguments are no longer special; the name should now be set using the name keyword argument of the factory, and context may be None . This affects the following function and methods: asyncio.create_task() , asyncio.loop.create_task() , asyncio.TaskGroup.create_task() . (Contributed by Thomas Grainger in gh-128307 .) There are two new utility functions for introspecting and printing a program’s call graph: capture_call_graph() and print_call_graph() . See Asyncio introspection capabilities for more details. (Contributed by Yury Selivanov, Pablo Galindo Salgado, and Łukasz Langa in gh-91048 .) calendar ¶ By default, today’s date is highlighted in color in calendar ’s command-line text output. This can be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-128317 .) concurrent.futures ¶ Add a new executor class, InterpreterPoolExecutor , which exposes multiple Python interpreters in the same process (‘subinterpreters’) to Python code. This uses a pool of independent Python interpreters to execute calls asynchronously. This is separate from the new interpreters module introduced by PEP 734 . (Contributed by Eric Snow in gh-124548 .) On Unix platforms other than macOS, ‘forkserver’ is now the default start method for ProcessPoolExecutor (replacing ‘fork’ ). This change does not affect Windows or macOS, where ‘spawn’ remains the default start method. If the threading incompatible fork method is required, you must explicitly request it by supplying a multiprocessing context mp_context to ProcessPoolExecutor . See forkserver restrictions for information and differences with the fork method and how this change may affect existing code with mutable global shared variables and/or shared objects that can not be automatically pickled . (Contributed by Gregory P. Smith in gh-84559 .) Add two new methods to ProcessPoolExecutor , terminate_workers() and kill_workers() , as ways to terminate or kill all living worker processes in the given pool. (Contributed by Charles Machalow in gh-130849 .) Add the optional buffersize parameter to Executor.map to limit the number of submitted tasks whose results have not yet been yielded. If the buffer is full, iteration over the iterables pauses until a result is yielded from the buffer. (Contributed by Enzo Bonnal and Josh Rosenberg in gh-74028 .) configparser ¶ configparser will no longer write config files it cannot read, to improve security. Attempting to write() keys containing delimiters or beginning with the section header pattern will raise an InvalidWriteError . (Contributed by Jacob Lincoln in gh-129270 .) contextvars ¶ Support the context manager protocol for Token objects. (Contributed by Andrew Svetlov in gh-129889 .) ctypes ¶ The layout of bit fields in Structure and Union objects is now a closer match to platform defaults (GCC/Clang or MSVC). In particular, fields no longer overlap. (Contributed by Matthias Görgens in gh-97702 .) The Structure._layout_ class attribute can now be set to help match a non-default ABI. (Contributed by Petr Viktorin in gh-97702 .) The class of Structure / Union field descriptors is now available as CField , and has new attributes to aid debugging and introspection. (Contributed by Petr Viktorin in gh-128715 .) On Windows, the COMError exception is now public. (Contributed by Jun Komoda in gh-126686 .) On Windows, the CopyComPointer() function is now public. (Contributed by Jun Komoda in gh-127275 .) Add memoryview_at() , a function to create a memoryview object that refers to the supplied pointer and length. This works like ctypes.string_at() except it avoids a buffer copy, and is typically useful when implementing pure Python callback functions that are passed dynamically-sized buffers. (Contributed by Rian Hunter in gh-112018 .) Complex types, c_float_complex , c_double_complex , and c_longdouble_complex , are now available if both the compiler and the libffi library support complex C types. (Contributed by Sergey B Kirpichev in gh-61103 .) Add ctypes.util.dllist() for listing the shared libraries loaded by the current process. (Contributed by Brian Ward in gh-119349 .) Move ctypes.POINTER() types cache from a global internal cache ( _pointer_type_cache ) to the _CData.__pointer_type__ attribute of the corresponding ctypes types. This will stop the cache from growing without limits in some situations. (Contributed by Sergey Miryanov in gh-100926 .) The py_object type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-132168 .) ctypes now supports free-threading builds . (Contributed by Kumar Aditya and Peter Bierma in gh-127945 .) curses ¶ Add the assume_default_colors() function, a refinement of the use_default_colors() function which allows changing the color pair 0 . (Contributed by Serhiy Storchaka in gh-133139 .) datetime ¶ Add the strptime() method to the datetime.date and datetime.time classes. (Contributed by Wannes Boeykens in gh-41431 .) decimal ¶ Add Decimal.from_number() as an alternative constructor for Decimal . (Contributed by Serhiy Storchaka in gh-121798 .) Expose IEEEContext() to support creation of contexts corresponding to the IEEE 754 (2008) decimal interchange formats. (Contributed by Sergey B Kirpichev in gh-53032 .) difflib ¶ Comparison pages with highlighted changes generated by the HtmlDiff class now support ‘dark mode’. (Contributed by Jiahao Li in gh-129939 .) dis ¶ Add support for rendering full source location information of instructions , rather than only the line number. This feature is added to the following interfaces via the show_positions keyword argument: dis.Bytecode dis.dis() dis.distb() dis.disassemble() This feature is also exposed via dis --show-positions . (Contributed by Bénédikt Tran in gh-123165 .) Add the dis --specialized command-line option to show specialized bytecode. (Contributed by Bénédikt Tran in gh-127413 .) errno ¶ Add the EHWPOISON error code constant. (Contributed by James Roy in gh-126585 .) faulthandler ¶ Add support for printing the C stack trace on systems that support it via the new dump_c_stack() function or via the c_stack argument in faulthandler.enable() . (Contributed by Peter Bierma in gh-127604 .) fnmatch ¶ Add filterfalse() , a function to reject names matching a given pattern. (Contributed by Bénédikt Tran in gh-74598 .) fractions ¶ A Fraction object may now be constructed from any object with the as_integer_ratio() method. (Contributed by Serhiy Storchaka in gh-82017 .) Add Fraction.from_number() as an alternative constructor for Fraction . (Contributed by Serhiy Storchaka in gh-121797 .) functools ¶ Add the Placeholder sentinel. This may be used with the partial() or partialmethod() functions to reserve a place for positional arguments in the returned partial object . (Contributed by Dominykas Grigonis in gh-119127 .) Allow the initial parameter of reduce() to be passed as a keyword argument. (Contributed by Sayandip Dutta in gh-125916 .) getopt ¶ Add support for options with optional arguments. (Contributed by Serhiy Storchaka in gh-126374 .) Add support for returning intermixed options and non-option arguments in order. (Contributed by Serhiy Storchaka in gh-126390 .) getpass ¶ Support keyboard feedback in the getpass() function via the keyword-only optional argument echo_char . Placeholder characters are rendered whenever a character is entered, and removed when a character is deleted. (Contributed by Semyon Moroz in gh-77065 .) graphlib ¶ Allow TopologicalSorter.prepare() to be called more than once as long as sorting has not started. (Contributed by Daniel Pope in gh-130914 .) heapq ¶ The heapq module has improved support for working with max-heaps, via the following new functions: heapify_max() heappush_max() heappop_max() heapreplace_max() heappushpop_max() hmac ¶ Add a built-in implementation for HMAC ( RFC 2104 ) using formally verified code from the HACL* project. This implementation is used as a fallback when the OpenSSL implementation of HMAC is not available. (Contributed by Bénédikt Tran in gh-99108 .) http ¶ Directory lists and error pages generated by the http.server module allow the browser to apply its default dark mode. (Contributed by Yorik Hansen in gh-123430 .) The http.server module now supports serving over HTTPS using the http.server.HTTPSServer class. This functionality is exposed by the command-line interface ( python -m http.server ) through the following options: --tls-cert <path> : Path to the TLS certificate file. --tls-key <path> : Optional path to the private key file. --tls-password-file <path> : Optional path to the password file for the private key. (Contributed by Semyon Moroz in gh-85162 .) imaplib ¶ Add IMAP4.idle() , implementing the IMAP4 IDLE command as defined in RFC 2177 . (Contributed by Forest in gh-55454 .) inspect ¶ signature() takes a new argument annotation_format to control the annotationlib.Format used for representing annotations. (Contributed by Jelle Zijlstra in gh-101552 .) Signature.format() takes a new argument unquote_annotations . If true, string annotations are displayed without surrounding quotes. (Contributed by Jelle Zijlstra in gh-101552 .) Add function ispackage() to determine whether an object is a package or not. (Contributed by Zhikang Yan in gh-125634 .) io ¶ Reading text from a non-blocking stream with read may now raise a BlockingIOError if the operation cannot immediately return bytes. (Contributed by Giovanni Siragusa in gh-109523 .) Add the Reader and Writer protocols as simpler alternatives to the pseudo-protocols typing.IO , typing.TextIO , and typing.BinaryIO . (Contributed by Sebastian Rittau in gh-127648 .) json ¶ Add exception notes for JSON serialization errors that allow identifying the source of the error. (Contributed by Serhiy Storchaka in gh-122163 .) Allow using the json module as a script using the -m switch: python -m json . This is now preferred to python -m json.tool , which is soft deprecated . See the JSON command-line interface documentation. (Contributed by Trey Hunner in gh-122873 .) By default, the output of the JSON command-line interface is highlighted in color. This can be controlled by environment variables . (Contributed by Tomas Roun in gh-131952 .) linecache ¶ getline() can now retrieve source code for frozen modules. (Contributed by Tian Gao in gh-131638 .) logging.handlers ¶ QueueListener objects now support the context manager protocol. (Contributed by Charles Machalow in gh-132106 .) QueueListener.start now raises a RuntimeError if the listener is already started. (Contributed by Charles Machalow in gh-132106 .) math ¶ Added more detailed error messages for domain errors in the module. (Contributed by Charlie Zhao and Sergey B Kirpichev in gh-101410 .) mimetypes ¶ Add a public command-line for the module, invoked via python -m mimetypes . (Contributed by Oleg Iarygin and Hugo van Kemenade in gh-93096 .) Add several new MIME types based on RFCs and common usage: Microsoft and RFC 8081 MIME types for fonts Embedded OpenType: application/vnd.ms-fontobject OpenType Layout (OTF) font/otf TrueType: font/ttf WOFF 1.0 font/woff WOFF 2.0 font/woff2 RFC 9559 | 2026-01-13T08:49:47 |
https://docs.python.org/3/whatsnew/3.14.html#whatsnew314-pyrepl-highlighting | What’s new in Python 3.14 — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents What’s new in Python 3.14 Summary – Release highlights New features PEP 649 & PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template string literals PEP 768 : Safe external debugger interface A new type of interpreter Free-threaded mode improvements Improved error messages PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Other language changes Built-ins Command line and environment PEP 758: Allow except and except* expressions without brackets PEP 765: Control flow in finally blocks Incremental garbage collection Default interactive shell New modules Improved modules argparse ast asyncio calendar concurrent.futures configparser contextvars ctypes curses datetime decimal difflib dis errno faulthandler fnmatch fractions functools getopt getpass graphlib heapq hmac http imaplib inspect io json linecache logging.handlers math mimetypes multiprocessing operator os os.path pathlib pdb pickle platform pydoc re socket ssl struct symtable sys sys.monitoring sysconfig tarfile threading tkinter turtle types typing unicodedata unittest urllib uuid webbrowser zipfile Optimizations asyncio base64 bdb difflib gc io pathlib pdb textwrap uuid zlib Removed argparse ast asyncio email importlib.abc itertools pathlib pkgutil pty sqlite3 urllib Deprecated New deprecations Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.17 Pending removal in Python 3.18 Pending removal in Python 3.19 Pending removal in future versions CPython bytecode changes Pseudo-instructions C API changes Python configuration C API New features in the C API Limited C API changes Removed C APIs Deprecated C APIs Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.18 Pending removal in future versions Build changes build-details.json Discontinuation of PGP signatures Free-threaded Python is officially supported Binary releases for the experimental just-in-time compiler Porting to Python 3.14 Changes in the Python API Changes in annotations ( PEP 649 and PEP 749 ) Implications for annotated code Implications for readers of __annotations__ Related changes from __future__ import annotations Changes in the C API Notable changes in 3.14.1 Previous topic What’s New in Python Next topic What’s New In Python 3.13 This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » What’s New in Python » What’s new in Python 3.14 | Theme Auto Light Dark | What’s new in Python 3.14 ¶ Editors : Adam Turner and Hugo van Kemenade This article explains the new features in Python 3.14, compared to 3.13. Python 3.14 was released on 7 October 2025. For full details, see the changelog . See also PEP 745 – Python 3.14 release schedule Summary – Release highlights ¶ Python 3.14 is the latest stable release of the Python programming language, with a mix of changes to the language, the implementation, and the standard library. The biggest changes include template string literals , deferred evaluation of annotations , and support for subinterpreters in the standard library. The library changes include significantly improved capabilities for introspection in asyncio , support for Zstandard via a new compression.zstd module, syntax highlighting in the REPL, as well as the usual deprecations and removals, and improvements in user-friendliness and correctness. This article doesn’t attempt to provide a complete specification of all new features, but instead gives a convenient overview. For full details refer to the documentation, such as the Library Reference and Language Reference . To understand the complete implementation and design rationale for a change, refer to the PEP for a particular new feature; but note that PEPs usually are not kept up-to-date once a feature has been fully implemented. See Porting to Python 3.14 for guidance on upgrading from earlier versions of Python. Interpreter improvements: PEP 649 and PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template strings PEP 758 : Allow except and except* expressions without brackets PEP 765 : Control flow in finally blocks PEP 768 : Safe external debugger interface for CPython A new type of interpreter Free-threaded mode improvements Improved error messages Incremental garbage collection Significant improvements in the standard library: PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Syntax highlighting in the default interactive shell , and color output in several standard library CLIs C API improvements: PEP 741 : Python configuration C API Platform support: PEP 776 : Emscripten is now an officially supported platform , at tier 3 . Release changes: PEP 779 : Free-threaded Python is officially supported PEP 761 : PGP signatures have been discontinued for official releases Windows and macOS binary releases now support the experimental just-in-time compiler Binary releases for Android are now provided New features ¶ PEP 649 & PEP 749 : Deferred evaluation of annotations ¶ The annotations on functions, classes, and modules are no longer evaluated eagerly. Instead, annotations are stored in special-purpose annotate functions and evaluated only when necessary (except if from __future__ import annotations is used). This change is designed to improve performance and usability of annotations in Python in most circumstances. The runtime cost for defining annotations is minimized, but it remains possible to introspect annotations at runtime. It is no longer necessary to enclose annotations in strings if they contain forward references. The new annotationlib module provides tools for inspecting deferred annotations. Annotations may be evaluated in the VALUE format (which evaluates annotations to runtime values, similar to the behavior in earlier Python versions), the FORWARDREF format (which replaces undefined names with special markers), and the STRING format (which returns annotations as strings). This example shows how these formats behave: >>> from annotationlib import get_annotations , Format >>> def func ( arg : Undefined ): ... pass >>> get_annotations ( func , format = Format . VALUE ) Traceback (most recent call last): ... NameError : name 'Undefined' is not defined >>> get_annotations ( func , format = Format . FORWARDREF ) {'arg': ForwardRef('Undefined', owner=<function func at 0x...>)} >>> get_annotations ( func , format = Format . STRING ) {'arg': 'Undefined'} The porting section contains guidance on changes that may be needed due to these changes, though in the majority of cases, code will continue working as-is. (Contributed by Jelle Zijlstra in PEP 749 and gh-119180 ; PEP 649 was written by Larry Hastings.) See also PEP 649 Deferred Evaluation Of Annotations Using Descriptors PEP 749 Implementing PEP 649 PEP 734 : Multiple interpreters in the standard library ¶ The CPython runtime supports running multiple copies of Python in the same process simultaneously and has done so for over 20 years. Each of these separate copies is called an ‘interpreter’. However, the feature had been available only through the C-API . That limitation is removed in Python 3.14, with the new concurrent.interpreters module. There are at least two notable reasons why using multiple interpreters has significant benefits: they support a new (to Python), human-friendly concurrency model true multi-core parallelism For some use cases, concurrency in software improves efficiency and can simplify design, at a high level. At the same time, implementing and maintaining all but the simplest concurrency is often a struggle for the human brain. That especially applies to plain threads (for example, threading ), where all memory is shared between all threads. With multiple isolated interpreters, you can take advantage of a class of concurrency models, like Communicating Sequential Processes (CSP) or the actor model, that have found success in other programming languages, like Smalltalk, Erlang, Haskell, and Go. Think of multiple interpreters as threads but with opt-in sharing. Regarding multi-core parallelism: as of Python 3.12, interpreters are now sufficiently isolated from one another to be used in parallel (see PEP 684 ). This unlocks a variety of CPU-intensive use cases for Python that were limited by the GIL . Using multiple interpreters is similar in many ways to multiprocessing , in that they both provide isolated logical “processes” that can run in parallel, with no sharing by default. However, when using multiple interpreters, an application will use fewer system resources and will operate more efficiently (since it stays within the same process). Think of multiple interpreters as having the isolation of processes with the efficiency of threads. While the feature has been around for decades, multiple interpreters have not been used widely, due to low awareness and the lack of a standard library module. Consequently, they currently have several notable limitations, which are expected to improve significantly now that the feature is going mainstream. Current limitations: starting each interpreter has not been optimized yet each interpreter uses more memory than necessary (work continues on extensive internal sharing between interpreters) there aren’t many options yet for truly sharing objects or other data between interpreters (other than memoryview ) many third-party extension modules on PyPI are not yet compatible with multiple interpreters (all standard library extension modules are compatible) the approach to writing applications that use multiple isolated interpreters is mostly unfamiliar to Python users, for now The impact of these limitations will depend on future CPython improvements, how interpreters are used, and what the community solves through PyPI packages. Depending on the use case, the limitations may not have much impact, so try it out! Furthermore, future CPython releases will reduce or eliminate overhead and provide utilities that are less appropriate on PyPI. In the meantime, most of the limitations can also be addressed through extension modules, meaning PyPI packages can fill any gap for 3.14, and even back to 3.12 where interpreters were finally properly isolated and stopped sharing the GIL . Likewise, libraries on PyPI are expected to emerge for high-level abstractions on top of interpreters. Regarding extension modules, work is in progress to update some PyPI projects, as well as tools like Cython, pybind11, nanobind, and PyO3. The steps for isolating an extension module are found at Isolating Extension Modules . Isolating a module has a lot of overlap with what is required to support free-threading , so the ongoing work in the community in that area will help accelerate support for multiple interpreters. Also added in 3.14: concurrent.futures.InterpreterPoolExecutor . (Contributed by Eric Snow in gh-134939 .) See also PEP 734 PEP 750 : Template string literals ¶ Template strings are a new mechanism for custom string processing. They share the familiar syntax of f-strings but, unlike f-strings, return an object representing the static and interpolated parts of the string, instead of a simple str . To write a t-string, use a 't' prefix instead of an 'f' : >>> variety = 'Stilton' >>> template = t 'Try some {variety} cheese!' >>> type ( template ) <class 'string.templatelib.Template'> Template objects provide access to the static and interpolated (in curly braces) parts of a string before they are combined. Iterate over Template instances to access their parts in order: >>> list ( template ) ['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!'] It’s easy to write (or call) code to process Template instances. For example, here’s a function that renders static parts lowercase and Interpolation instances uppercase: from string.templatelib import Interpolation def lower_upper ( template ): """Render static parts lowercase and interpolations uppercase.""" parts = [] for part in template : if isinstance ( part , Interpolation ): parts . append ( str ( part . value ) . upper ()) else : parts . append ( part . lower ()) return '' . join ( parts ) name = 'Wenslydale' template = t 'Mister {name} ' assert lower_upper ( template ) == 'mister WENSLYDALE' Because Template instances distinguish between static strings and interpolations at runtime, they can be useful for sanitising user input. Writing a html() function that escapes user input in HTML is an exercise left to the reader! Template processing code can provide improved flexibility. For instance, a more advanced html() function could accept a dict of HTML attributes directly in the template: attributes = { 'src' : 'limburger.jpg' , 'alt' : 'lovely cheese' } template = t '<img {attributes} >' assert html ( template ) == '<img src="limburger.jpg" alt="lovely cheese" />' Of course, template processing code does not need to return a string-like result. An even more advanced html() could return a custom type representing a DOM-like structure. With t-strings in place, developers can write systems that sanitise SQL, make safe shell operations, improve logging, tackle modern ideas in web development (HTML, CSS, and so on), and implement lightweight custom business DSLs. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) See also PEP 750 . PEP 768 : Safe external debugger interface ¶ Python 3.14 introduces a zero-overhead debugging interface that allows debuggers and profilers to safely attach to running Python processes without stopping or restarting them. This is a significant enhancement to Python’s debugging capabilities, meaning that unsafe alternatives are no longer required. The new interface provides safe execution points for attaching debugger code without modifying the interpreter’s normal execution path or adding any overhead at runtime. Due to this, tools can now inspect and interact with Python applications in real-time, which is a crucial capability for high-availability systems and production environments. For convenience, this interface is implemented in the sys.remote_exec() function. For example: import sys from tempfile import NamedTemporaryFile with NamedTemporaryFile ( mode = 'w' , suffix = '.py' , delete = False ) as f : script_path = f . name f . write ( f 'import my_debugger; my_debugger.connect( { os . getpid () } )' ) # Execute in process with PID 1234 print ( 'Behold! An offering:' ) sys . remote_exec ( 1234 , script_path ) This function allows sending Python code to be executed in a target process at the next safe execution point. However, tool authors can also implement the protocol directly as described in the PEP, which details the underlying mechanisms used to safely attach to running processes. The debugging interface has been carefully designed with security in mind and includes several mechanisms to control access: A PYTHON_DISABLE_REMOTE_DEBUG environment variable. A -X disable-remote-debug command-line option. A --without-remote-debug configure flag to completely disable the feature at build time. (Contributed by Pablo Galindo Salgado, Matt Wozniski, and Ivona Stojanovic in gh-131591 .) See also PEP 768 . A new type of interpreter ¶ A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individual Python opcodes, rather than one large C case statement. For certain newer compilers, this interpreter provides significantly better performance. Preliminary benchmarks suggest a geometric mean of 3-5% faster on the standard pyperformance benchmark suite, depending on platform and architecture. The baseline is Python 3.14 built with Clang 19, without this new interpreter. This interpreter currently only works with Clang 19 and newer on x86-64 and AArch64 architectures. However, a future release of GCC is expected to support this as well. This feature is opt-in for now. Enabling profile-guided optimization is highly recommendeded when using the new interpreter as it is the only configuration that has been tested and validated for improved performance. For further information, see --with-tail-call-interp . Note This is not to be confused with tail call optimization of Python functions, which is currently not implemented in CPython. This new interpreter type is an internal implementation detail of the CPython interpreter. It doesn’t change the visible behavior of Python programs at all. It can improve their performance, but doesn’t change anything else. (Contributed by Ken Jin in gh-128563 , with ideas on how to implement this in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.) Free-threaded mode improvements ¶ CPython’s free-threaded mode ( PEP 703 ), initially added in 3.13, has been significantly improved in Python 3.14. The implementation described in PEP 703 has been finished, including C API changes, and temporary workarounds in the interpreter were replaced with more permanent solutions. The specializing adaptive interpreter ( PEP 659 ) is now enabled in free-threaded mode, which along with many other optimizations greatly improves its performance. The performance penalty on single-threaded code in free-threaded mode is now roughly 5-10%, depending on the platform and C compiler used. From Python 3.14, when compiling extension modules for the free-threaded build of CPython on Windows, the preprocessor variable Py_GIL_DISABLED now needs to be specified by the build backend, as it will no longer be determined automatically by the C compiler. For a running interpreter, the setting that was used at compile time can be found using sysconfig.get_config_var() . The new -X context_aware_warnings flag controls if concurrent safe warnings control is enabled. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. A new thread_inherit_context flag has been added, which if enabled means that threads created with threading.Thread start with a copy of the Context() of the caller of start() . Most significantly, this makes the warning filtering context established by catch_warnings be “inherited” by threads (or asyncio tasks) started within that context. It also affects other modules that use context variables, such as the decimal context manager. This flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Sam Gross, Matt Page, Neil Schemenauer, Thomas Wouters, Donghee Na, Kirill Podoprigora, Ken Jin, Itamar Oren, Brett Simmers, Dino Viehland, Nathan Goldbaum, Ralf Gommers, Lysandros Nikolaou, Kumar Aditya, Edgar Margffoy, and many others. Some of these contributors are employed by Meta, which has continued to provide significant engineering resources to support this project.) Improved error messages ¶ The interpreter now provides helpful suggestions when it detects typos in Python keywords. When a word that closely resembles a Python keyword is encountered, the interpreter will suggest the correct keyword in the error message. This feature helps programmers quickly identify and fix common typing mistakes. For example: >>> whille True : ... pass Traceback (most recent call last): File "<stdin>" , line 1 whille True : ^^^^^^ SyntaxError : invalid syntax. Did you mean 'while'? While the feature focuses on the most common cases, some variations of misspellings may still result in regular syntax errors. (Contributed by Pablo Galindo in gh-132449 .) elif statements that follow an else block now have a specific error message. (Contributed by Steele Farnsworth in gh-129902 .) >>> if who == "me" : ... print ( "It's me!" ) ... else : ... print ( "It's not me!" ) ... elif who is None : ... print ( "Who is it?" ) File "<stdin>", line 5 elif who is None: ^^^^ SyntaxError: 'elif' block follows an 'else' block If a statement is passed to the Conditional expressions after else , or one of pass , break , or continue is passed before if , then the error message highlights where the expression is required. (Contributed by Sergey Miryanov in gh-129515 .) >>> x = 1 if True else pass Traceback (most recent call last): File "<string>" , line 1 x = 1 if True else pass ^^^^ SyntaxError : expected expression after 'else', but statement is given >>> x = continue if True else break Traceback (most recent call last): File "<string>" , line 1 x = continue if True else break ^^^^^^^^ SyntaxError : expected expression before 'if', but statement is given When incorrectly closed strings are detected, the error message suggests that the string may be intended to be part of the string. (Contributed by Pablo Galindo in gh-88535 .) >>> "The interesting object " The important object " is very important" Traceback (most recent call last): SyntaxError : invalid syntax. Is this intended to be part of the string? When strings have incompatible prefixes, the error now shows which prefixes are incompatible. (Contributed by Nikita Sobolev in gh-133197 .) >>> ub 'abc' File "<python-input-0>" , line 1 ub 'abc' ^^ SyntaxError : 'u' and 'b' prefixes are incompatible Improved error messages when using as with incompatible targets in: Imports: import ... as ... From imports: from ... import ... as ... Except handlers: except ... as ... Pattern-match cases: case ... as ... (Contributed by Nikita Sobolev in gh-123539 , gh-123562 , and gh-123440 .) Improved error message when trying to add an instance of an unhashable type to a dict or set . (Contributed by CF Bolz-Tereick and Victor Stinner in gh-132828 .) >>> s = set () >>> s . add ({ 'pages' : 12 , 'grade' : 'A' }) Traceback (most recent call last): File "<python-input-1>" , line 1 , in <module> s . add ({ 'pages' : 12 , 'grade' : 'A' }) ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError : cannot use 'dict' as a set element (unhashable type: 'dict') >>> d = {} >>> l = [ 1 , 2 , 3 ] >>> d [ l ] = 12 Traceback (most recent call last): File "<python-input-4>" , line 1 , in <module> d [ l ] = 12 ~^^^ TypeError : cannot use 'list' as a dict key (unhashable type: 'list') Improved error message when an object supporting the synchronous context manager protocol is entered using async with instead of with , and vice versa for the asynchronous context manager protocol. (Contributed by Bénédikt Tran in gh-128398 .) PEP 784 : Zstandard support in the standard library ¶ The new compression package contains modules compression.lzma , compression.bz2 , compression.gzip and compression.zlib which re-export the lzma , bz2 , gzip and zlib modules respectively. The new import names under compression are the preferred names for importing these compression modules from Python 3.14. However, the existing modules names have not been deprecated. Any deprecation or removal of the existing compression modules will occur no sooner than five years after the release of 3.14. The new compression.zstd module provides compression and decompression APIs for the Zstandard format via bindings to Meta’s zstd library . Zstandard is a widely adopted, highly efficient, and fast compression format. In addition to the APIs introduced in compression.zstd , support for reading and writing Zstandard compressed archives has been added to the tarfile , zipfile , and shutil modules. Here’s an example of using the new module to compress some data: from compression import zstd import math data = str ( math . pi ) . encode () * 20 compressed = zstd . compress ( data ) ratio = len ( compressed ) / len ( data ) print ( f "Achieved compression ratio of { ratio } " ) As can be seen, the API is similar to the APIs of the lzma and bz2 modules. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) See also PEP 784 . Asyncio introspection capabilities ¶ Added a new command-line interface to inspect running Python processes using asynchronous tasks, available via python -m asyncio ps PID or python -m asyncio pstree PID . The ps subcommand inspects the given process ID (PID) and displays information about currently running asyncio tasks. It outputs a task table: a flat listing of all tasks, their names, their coroutine stacks, and which tasks are awaiting them. The pstree subcommand fetches the same information, but instead renders a visual async call tree, showing coroutine relationships in a hierarchical format. This command is particularly useful for debugging long-running or stuck asynchronous programs. It can help developers quickly identify where a program is blocked, what tasks are pending, and how coroutines are chained together. For example given this code: import asyncio async def play_track ( track ): await asyncio . sleep ( 5 ) print ( f '🎵 Finished: { track } ' ) async def play_album ( name , tracks ): async with asyncio . TaskGroup () as tg : for track in tracks : tg . create_task ( play_track ( track ), name = track ) async def main (): async with asyncio . TaskGroup () as tg : tg . create_task ( play_album ( 'Sundowning' , [ 'TNDNBTG' , 'Levitate' ]), name = 'Sundowning' ) tg . create_task ( play_album ( 'TMBTE' , [ 'DYWTYLM' , 'Aqua Regia' ]), name = 'TMBTE' ) if __name__ == '__main__' : asyncio . run ( main ()) Executing the new tool on the running process will yield a table like this: python -m asyncio ps 12345 tid task id task name coroutine stack awaiter chain awaiter name awaiter id ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1935500 0x7fc930c18050 Task-1 TaskGroup._aexit -> TaskGroup.__aexit__ -> main 0x0 1935500 0x7fc930c18230 Sundowning TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fa50 TMBTE TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fdf0 TNDNBTG sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32510 Levitate sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32890 DYWTYLM sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 1935500 0x7fc93161ec30 Aqua Regia sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 or a tree like this: python -m asyncio pstree 12345 └── ( T ) Task-1 └── main example.py:13 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) Sundowning │ └── album example.py:8 │ └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 │ └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 │ ├── ( T ) TNDNBTG │ │ └── play example.py:4 │ │ └── sleep Lib/asyncio/tasks.py:702 │ └── ( T ) Levitate │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) TMBTE └── album example.py:8 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) DYWTYLM │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) Aqua Regia └── play example.py:4 └── sleep Lib/asyncio/tasks.py:702 If a cycle is detected in the async await graph (which could indicate a programming issue), the tool raises an error and lists the cycle paths that prevent tree construction: python -m asyncio pstree 12345 ERROR: await-graph contains cycles - cannot print a tree! cycle: Task-2 → Task-3 → Task-2 (Contributed by Pablo Galindo, Łukasz Langa, Yury Selivanov, and Marta Gomez Macias in gh-91048 .) Concurrent safe warnings control ¶ The warnings.catch_warnings context manager will now optionally use a context variable for warning filters. This is enabled by setting the context_aware_warnings flag, either with the -X command-line option or an environment variable. This gives predictable warnings control when using catch_warnings combined with multiple threads or asynchronous tasks. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Neil Schemenauer and Kumar Aditya in gh-130010 .) Other language changes ¶ All Windows code pages are now supported as ‘cpXXX’ codecs on Windows. (Contributed by Serhiy Storchaka in gh-123803 .) Implement mixed-mode arithmetic rules combining real and complex numbers as specified by the C standard since C99. (Contributed by Sergey B Kirpichev in gh-69639 .) More syntax errors are now detected regardless of optimisation and the -O command-line option. This includes writes to __debug__ , incorrect use of await , and asynchronous comprehensions outside asynchronous functions. For example, python -O -c 'assert (__debug__ := 1)' or python -O -c 'assert await 1' now produce SyntaxError s. (Contributed by Irit Katriel and Jelle Zijlstra in gh-122245 & gh-121637 .) When subclassing a pure C type, the C slots for the new type are no longer replaced with a wrapped version on class creation if they are not explicitly overridden in the subclass. (Contributed by Tomasz Pytel in gh-132284 .) Built-ins ¶ The bytes.fromhex() and bytearray.fromhex() methods now accept ASCII bytes and bytes-like objects . (Contributed by Daniel Pope in gh-129349 .) Add class methods float.from_number() and complex.from_number() to convert a number to float or complex type correspondingly. They raise a TypeError if the argument is not a real number. (Contributed by Serhiy Storchaka in gh-84978 .) Support underscore and comma as thousands separators in the fractional part for floating-point presentation types of the new-style string formatting (with format() or f-strings ). (Contributed by Sergey B Kirpichev in gh-87790 .) The int() function no longer delegates to __trunc__() . Classes that want to support conversion to int() must implement either __int__() or __index__() . (Contributed by Mark Dickinson in gh-119743 .) The map() function now has an optional keyword-only strict flag like zip() to check that all the iterables are of equal length. (Contributed by Wannes Boeykens in gh-119793 .) The memoryview type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-126012 .) Using NotImplemented in a boolean context will now raise a TypeError . This has raised a DeprecationWarning since Python 3.9. (Contributed by Jelle Zijlstra in gh-118767 .) Three-argument pow() now tries calling __rpow__() if necessary. Previously it was only called in two-argument pow() and the binary power operator. (Contributed by Serhiy Storchaka in gh-130104 .) super objects are now copyable and pickleable . (Contributed by Serhiy Storchaka in gh-125767 .) Command line and environment ¶ The import time flag can now track modules that are already loaded (‘cached’), via the new -X importtime=2 . When such a module is imported, the self and cumulative times are replaced by the string cached . Values above 2 for -X importtime are now reserved for future use. (Contributed by Noah Kim and Adam Turner in gh-118655 .) The command-line option -c now automatically dedents its code argument before execution. The auto-dedentation behavior mirrors textwrap.dedent() . (Contributed by Jon Crall and Steven Sun in gh-103998 .) -J is no longer a reserved flag for Jython , and now has no special meaning. (Contributed by Adam Turner in gh-133336 .) PEP 758: Allow except and except* expressions without brackets ¶ The except and except* expressions now allow brackets to be omitted when there are multiple exception types and the as clause is not used. For example: try : connect_to_server () except TimeoutError , ConnectionRefusedError : print ( 'The network has ceased to be!' ) (Contributed by Pablo Galindo and Brett Cannon in PEP 758 and gh-131831 .) PEP 765: Control flow in finally blocks ¶ The compiler now emits a SyntaxWarning when a return , break , or continue statement have the effect of leaving a finally block. This change is specified in PEP 765 . In situations where this change is inconvenient (such as those where the warnings are redundant due to code linting), the warning filter can be used to turn off all syntax warnings by adding ignore::SyntaxWarning as a filter. This can be specified in combination with a filter that converts other warnings to errors (for example, passing -Werror -Wignore::SyntaxWarning as CLI options, or setting PYTHONWARNINGS=error,ignore::SyntaxWarning ). Note that applying such a filter at runtime using the warnings module will only suppress the warning in code that is compiled after the filter is adjusted. Code that is compiled prior to the filter adjustment (for example, when a module is imported) will still emit the syntax warning. (Contributed by Irit Katriel in gh-130080 .) Incremental garbage collection ¶ The cycle garbage collector is now incremental. This means that maximum pause times are reduced by an order of magnitude or more for larger heaps. There are now only two generations: young and old. When gc.collect() is not called directly, the GC is invoked a little less frequently. When invoked, it collects the young generation and an increment of the old generation, instead of collecting one or more generations. The behavior of gc.collect() changes slightly: gc.collect(1) : Performs an increment of garbage collection, rather than collecting generation 1. Other calls to gc.collect() are unchanged. (Contributed by Mark Shannon in gh-108362 .) Default interactive shell ¶ The default interactive shell now highlights Python syntax. The feature is enabled by default, save if PYTHON_BASIC_REPL or any other environment variable that disables colour is set. See Controlling color for details. The default color theme for syntax highlighting strives for good contrast and exclusively uses the 4-bit VGA standard ANSI color codes for maximum compatibility. The theme can be customized using an experimental API _colorize.set_theme() . This can be called interactively or in the PYTHONSTARTUP script. Note that this function has no stability guarantees, and may change or be removed. (Contributed by Łukasz Langa in gh-131507 .) The default interactive shell now supports import auto-completion. This means that typing import co and pressing <Tab> will suggest modules starting with co . Similarly, typing from concurrent import i will suggest submodules of concurrent starting with i . Note that autocompletion of module attributes is not currently supported. (Contributed by Tomas Roun in gh-69605 .) New modules ¶ annotationlib : For introspecting annotations . See PEP 749 for more details. (Contributed by Jelle Zijlstra in gh-119180 .) compression (including compression.zstd ): A package for compression-related modules, including a new module to support the Zstandard compression format. See PEP 784 for more details. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) concurrent.interpreters : Support for multiple interpreters in the standard library. See PEP 734 for more details. (Contributed by Eric Snow in gh-134939 .) string.templatelib : Support for template string literals (t-strings). See PEP 750 for more details. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) Improved modules ¶ argparse ¶ The default value of the program name for argparse.ArgumentParser now reflects the way the Python interpreter was instructed to find the __main__ module code. (Contributed by Serhiy Storchaka and Alyssa Coghlan in gh-66436 .) Introduced the optional suggest_on_error parameter to argparse.ArgumentParser , enabling suggestions for argument choices and subparser names if mistyped by the user. (Contributed by Savannah Ostrowski in gh-124456 .) Enable color for help text, which can be disabled with the optional color parameter to argparse.ArgumentParser . This can also be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-130645 .) ast ¶ Add compare() , a function for comparing two ASTs. (Contributed by Batuhan Taskaya and Jeremy Hylton in gh-60191 .) Add support for copy.replace() for AST nodes. (Contributed by Bénédikt Tran in gh-121141 .) Docstrings are now removed from an optimized AST in optimization level 2. (Contributed by Irit Katriel in gh-123958 .) The repr() output for AST nodes now includes more information. (Contributed by Tomas Roun in gh-116022 .) When called with an AST as input, the parse() function now always verifies that the root node type is appropriate. (Contributed by Irit Katriel in gh-130139 .) Add new options to the command-line interface: --feature-version , --optimize , and --show-empty . (Contributed by Semyon Moroz in gh-133367 .) asyncio ¶ The function and methods named create_task() now take an arbitrary list of keyword arguments. All keyword arguments are passed to the Task constructor or the custom task factory. (See set_task_factory() for details.) The name and context keyword arguments are no longer special; the name should now be set using the name keyword argument of the factory, and context may be None . This affects the following function and methods: asyncio.create_task() , asyncio.loop.create_task() , asyncio.TaskGroup.create_task() . (Contributed by Thomas Grainger in gh-128307 .) There are two new utility functions for introspecting and printing a program’s call graph: capture_call_graph() and print_call_graph() . See Asyncio introspection capabilities for more details. (Contributed by Yury Selivanov, Pablo Galindo Salgado, and Łukasz Langa in gh-91048 .) calendar ¶ By default, today’s date is highlighted in color in calendar ’s command-line text output. This can be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-128317 .) concurrent.futures ¶ Add a new executor class, InterpreterPoolExecutor , which exposes multiple Python interpreters in the same process (‘subinterpreters’) to Python code. This uses a pool of independent Python interpreters to execute calls asynchronously. This is separate from the new interpreters module introduced by PEP 734 . (Contributed by Eric Snow in gh-124548 .) On Unix platforms other than macOS, ‘forkserver’ is now the default start method for ProcessPoolExecutor (replacing ‘fork’ ). This change does not affect Windows or macOS, where ‘spawn’ remains the default start method. If the threading incompatible fork method is required, you must explicitly request it by supplying a multiprocessing context mp_context to ProcessPoolExecutor . See forkserver restrictions for information and differences with the fork method and how this change may affect existing code with mutable global shared variables and/or shared objects that can not be automatically pickled . (Contributed by Gregory P. Smith in gh-84559 .) Add two new methods to ProcessPoolExecutor , terminate_workers() and kill_workers() , as ways to terminate or kill all living worker processes in the given pool. (Contributed by Charles Machalow in gh-130849 .) Add the optional buffersize parameter to Executor.map to limit the number of submitted tasks whose results have not yet been yielded. If the buffer is full, iteration over the iterables pauses until a result is yielded from the buffer. (Contributed by Enzo Bonnal and Josh Rosenberg in gh-74028 .) configparser ¶ configparser will no longer write config files it cannot read, to improve security. Attempting to write() keys containing delimiters or beginning with the section header pattern will raise an InvalidWriteError . (Contributed by Jacob Lincoln in gh-129270 .) contextvars ¶ Support the context manager protocol for Token objects. (Contributed by Andrew Svetlov in gh-129889 .) ctypes ¶ The layout of bit fields in Structure and Union objects is now a closer match to platform defaults (GCC/Clang or MSVC). In particular, fields no longer overlap. (Contributed by Matthias Görgens in gh-97702 .) The Structure._layout_ class attribute can now be set to help match a non-default ABI. (Contributed by Petr Viktorin in gh-97702 .) The class of Structure / Union field descriptors is now available as CField , and has new attributes to aid debugging and introspection. (Contributed by Petr Viktorin in gh-128715 .) On Windows, the COMError exception is now public. (Contributed by Jun Komoda in gh-126686 .) On Windows, the CopyComPointer() function is now public. (Contributed by Jun Komoda in gh-127275 .) Add memoryview_at() , a function to create a memoryview object that refers to the supplied pointer and length. This works like ctypes.string_at() except it avoids a buffer copy, and is typically useful when implementing pure Python callback functions that are passed dynamically-sized buffers. (Contributed by Rian Hunter in gh-112018 .) Complex types, c_float_complex , c_double_complex , and c_longdouble_complex , are now available if both the compiler and the libffi library support complex C types. (Contributed by Sergey B Kirpichev in gh-61103 .) Add ctypes.util.dllist() for listing the shared libraries loaded by the current process. (Contributed by Brian Ward in gh-119349 .) Move ctypes.POINTER() types cache from a global internal cache ( _pointer_type_cache ) to the _CData.__pointer_type__ attribute of the corresponding ctypes types. This will stop the cache from growing without limits in some situations. (Contributed by Sergey Miryanov in gh-100926 .) The py_object type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-132168 .) ctypes now supports free-threading builds . (Contributed by Kumar Aditya and Peter Bierma in gh-127945 .) curses ¶ Add the assume_default_colors() function, a refinement of the use_default_colors() function which allows changing the color pair 0 . (Contributed by Serhiy Storchaka in gh-133139 .) datetime ¶ Add the strptime() method to the datetime.date and datetime.time classes. (Contributed by Wannes Boeykens in gh-41431 .) decimal ¶ Add Decimal.from_number() as an alternative constructor for Decimal . (Contributed by Serhiy Storchaka in gh-121798 .) Expose IEEEContext() to support creation of contexts corresponding to the IEEE 754 (2008) decimal interchange formats. (Contributed by Sergey B Kirpichev in gh-53032 .) difflib ¶ Comparison pages with highlighted changes generated by the HtmlDiff class now support ‘dark mode’. (Contributed by Jiahao Li in gh-129939 .) dis ¶ Add support for rendering full source location information of instructions , rather than only the line number. This feature is added to the following interfaces via the show_positions keyword argument: dis.Bytecode dis.dis() dis.distb() dis.disassemble() This feature is also exposed via dis --show-positions . (Contributed by Bénédikt Tran in gh-123165 .) Add the dis --specialized command-line option to show specialized bytecode. (Contributed by Bénédikt Tran in gh-127413 .) errno ¶ Add the EHWPOISON error code constant. (Contributed by James Roy in gh-126585 .) faulthandler ¶ Add support for printing the C stack trace on systems that support it via the new dump_c_stack() function or via the c_stack argument in faulthandler.enable() . (Contributed by Peter Bierma in gh-127604 .) fnmatch ¶ Add filterfalse() , a function to reject names matching a given pattern. (Contributed by Bénédikt Tran in gh-74598 .) fractions ¶ A Fraction object may now be constructed from any object with the as_integer_ratio() method. (Contributed by Serhiy Storchaka in gh-82017 .) Add Fraction.from_number() as an alternative constructor for Fraction . (Contributed by Serhiy Storchaka in gh-121797 .) functools ¶ Add the Placeholder sentinel. This may be used with the partial() or partialmethod() functions to reserve a place for positional arguments in the returned partial object . (Contributed by Dominykas Grigonis in gh-119127 .) Allow the initial parameter of reduce() to be passed as a keyword argument. (Contributed by Sayandip Dutta in gh-125916 .) getopt ¶ Add support for options with optional arguments. (Contributed by Serhiy Storchaka in gh-126374 .) Add support for returning intermixed options and non-option arguments in order. (Contributed by Serhiy Storchaka in gh-126390 .) getpass ¶ Support keyboard feedback in the getpass() function via the keyword-only optional argument echo_char . Placeholder characters are rendered whenever a character is entered, and removed when a character is deleted. (Contributed by Semyon Moroz in gh-77065 .) graphlib ¶ Allow TopologicalSorter.prepare() to be called more than once as long as sorting has not started. (Contributed by Daniel Pope in gh-130914 .) heapq ¶ The heapq module has improved support for working with max-heaps, via the following new functions: heapify_max() heappush_max() heappop_max() heapreplace_max() heappushpop_max() hmac ¶ Add a built-in implementation for HMAC ( RFC 2104 ) using formally verified code from the HACL* project. This implementation is used as a fallback when the OpenSSL implementation of HMAC is not available. (Contributed by Bénédikt Tran in gh-99108 .) http ¶ Directory lists and error pages generated by the http.server module allow the browser to apply its default dark mode. (Contributed by Yorik Hansen in gh-123430 .) The http.server module now supports serving over HTTPS using the http.server.HTTPSServer class. This functionality is exposed by the command-line interface ( python -m http.server ) through the following options: --tls-cert <path> : Path to the TLS certificate file. --tls-key <path> : Optional path to the private key file. --tls-password-file <path> : Optional path to the password file for the private key. (Contributed by Semyon Moroz in gh-85162 .) imaplib ¶ Add IMAP4.idle() , implementing the IMAP4 IDLE command as defined in RFC 2177 . (Contributed by Forest in gh-55454 .) inspect ¶ signature() takes a new argument annotation_format to control the annotationlib.Format used for representing annotations. (Contributed by Jelle Zijlstra in gh-101552 .) Signature.format() takes a new argument unquote_annotations . If true, string annotations are displayed without surrounding quotes. (Contributed by Jelle Zijlstra in gh-101552 .) Add function ispackage() to determine whether an object is a package or not. (Contributed by Zhikang Yan in gh-125634 .) io ¶ Reading text from a non-blocking stream with read may now raise a BlockingIOError if the operation cannot immediately return bytes. (Contributed by Giovanni Siragusa in gh-109523 .) Add the Reader and Writer protocols as simpler alternatives to the pseudo-protocols typing.IO , typing.TextIO , and typing.BinaryIO . (Contributed by Sebastian Rittau in gh-127648 .) json ¶ Add exception notes for JSON serialization errors that allow identifying the source of the error. (Contributed by Serhiy Storchaka in gh-122163 .) Allow using the json module as a script using the -m switch: python -m json . This is now preferred to python -m json.tool , which is soft deprecated . See the JSON command-line interface documentation. (Contributed by Trey Hunner in gh-122873 .) By default, the output of the JSON command-line interface is highlighted in color. This can be controlled by environment variables . (Contributed by Tomas Roun in gh-131952 .) linecache ¶ getline() can now retrieve source code for frozen modules. (Contributed by Tian Gao in gh-131638 .) logging.handlers ¶ QueueListener objects now support the context manager protocol. (Contributed by Charles Machalow in gh-132106 .) QueueListener.start now raises a RuntimeError if the listener is already started. (Contributed by Charles Machalow in gh-132106 .) math ¶ Added more detailed error messages for domain errors in the module. (Contributed by Charlie Zhao and Sergey B Kirpichev in gh-101410 .) mimetypes ¶ Add a public command-line for the module, invoked via python -m mimetypes . (Contributed by Oleg Iarygin and Hugo van Kemenade in gh-93096 .) Add several new MIME types based on RFCs and common usage: Microsoft and RFC 8081 MIME types for fonts Embedded OpenType: application/vnd.ms-fontobject OpenType Layout (OTF) font/otf TrueType: font/ttf WOFF 1.0 font/woff WOFF 2.0 font/woff2 RFC 9559 | 2026-01-13T08:49:47 |
https://news.apache.org/foundation/entry/celebrating-10000-committers-the-people-who-power-apache-software-projects | Celebrating 10,000 Committers: The People Who Power Apache Software Projects - The ASF Blog Skip to content Community Contributor Getting Started Becoming a Committer Code of Conduct Community Resources Community Over Code Events Projects Projects Incubator Projects Projects Directory Mailing Lists Report a Vulnerability Downloads Distributions Releases Infrastructure Status Infrastructure Statistics Learn Blog How the ASF Works The Apache Way Legal & Trademark Licenses Glossary FAQ Resource & Tools Developer Information Wiki Issues Slack Self Serve Portal Self Serve Portal Infrastructure Whimsy Brand Guidelines Project Logos About About Our Sponsors Corporate Sponsorship Individual Supporters Leadership Members Diversity & Inclusion Newsroom Contact Sponsor Community Contributor Getting Started Becoming a Committer Code of Conduct Community Resources Community Over Code Events Projects Projects Incubator Projects Projects Directory Mailing Lists Report a Vulnerability Downloads Distributions Releases Infrastructure Status Infrastructure Statistics Learn Blog How the ASF Works The Apache Way Legal & Trademark Licenses Glossary FAQ Resource & Tools Developer Information Wiki Issues Slack Self Serve Portal Self Serve Portal Infrastructure Whimsy Brand Guidelines Project Logos About About Our Sponsors Corporate Sponsorship Individual Supporters Leadership Members Diversity & Inclusion Newsroom Contact Sponsor Celebrating 10,000 Committers: The People Who Power Apache Software Projects Published on December 5, 2025 By The ASF Back to Blog By: Brian Proffitt, Vice President, Marketing & Publicity The Apache Software Foundation has come a long way since its founding in 1999, shepherding over 300 projects and incubating podlings. On December 5, the ASF reached another significant milestone: the addition of its 10,000th committer. Within ASF projects, committers are project contributors who have demonstrated their benefit to the project over time, and, because of their contributions, they can be given this status by other committers within the project. Committers are given the responsibility by the community to help create a product that will outlive the interest of any particular volunteer. While not full ASF members (who have voting rights within the foundation), committers still have a range of responsibilities to their project, including: Deciding on release plans and releases Applying patches Helping users Monitoring commits and issues Assigning the role of committer is taken seriously within the ASF, so reaching 10,000 committers is a very important milestone for the growth and lasting endurance of The ASF and the Apache Way. It also reflects the emphasis The ASF has had on community, according to Dirk-Willem van Gulik, one of The ASF’s founding members, and current VP, Public Policy. “[The ASF is about] finding, first and foremost, a very welcoming community, and a code base only second,” Gulik commented. “When reflecting on [The ASF’s] history, I think of a culture of jointly making things better. I’d observe this is just as true today.“ “For all the AI-enabled software development tools we have today, it’s still humans determining what that software should do, specifying how, writing tests, reviewing code, debugging the result, pushing patches upstream, and integrating pull requests from downstream. The myth of the solo developer may be romantic, but the reality is that real software engineering is as much a social endeavor as a technical one,” ASF co-founder Brian Behlendorf added. “The Apache Software Foundation was the first organization to recognize the primary importance of a well-organized and healthy collective of humans building software together – one where, if you get it right and with some luck, high quality software is a natural byproduct.” But for Behlendorf, the milestone is also notable for its size for another reason. “Ten thousand developers is a brilliant milestone to hit – but it’s equally impressive how much production-quality software so central to how the modern world works was written by only ten thousand all-volunteer developers working together. Kudos are due to every one of them,” he concluded. As we conclude the calendar year, reflecting on this milestone is a great way to cap off a year of change and growth for The ASF. “Crossing the 10,000 committer mark is a milestone that celebrates the strength and success of community over code and the Apache Way. Each of those people has helped shape a space where collaboration for a shared purpose–software for the public good–thrives,” Ruth Suehle, President of the ASF stated. “Today we’ll take a moment to reflect on that history and express our gratitude to each of those 10,000 for the thousands yet to come.” Related Articles The Apache Software Foundation Announces Apache Geode® 2.0 The ASF January 12, 2026 Wilmington, DE – January 12, 2026 – The Apache Software Foundation (ASF), the global home of open source software the world relies on, today... Read Post ALC Taipei: Igniting the Apache Open Source Movement in Taiwan The ASF December 9, 2025 By: Chia-Ping Tsai (ALC Taipei Lead) We are absolutely thrilled to announce the official launch of the Apache Local Community (ALC) Taipei, established with... Read Post ASF Project Spotlight: Apache Geode The ASF November 18, 2025 Can you tell us a bit about the project?Apache Geode is an in-memory data grid that provides real-time, consistent access to data-intensive applications at... Read Post Subscribe to ASF Plus One, Our Monthly Newsletter Email Address Subscribe Apache and the Apache logo are trademarks of The Apache Software Foundation. The Apache® Software Foundation is a 501(c)(3) nonprofit organization. Tax ID # 47-0825376 Donate Community Contributor Getting Started Becoming a Committer Code of Conduct Community Resources Community Over Code Events Learn Blog How the ASF Works The Apache Way Legal & Trademark Licenses Glossary FAQ Projects Projects Incubator Projects Projects Directory Mailing Lists Report a Vulnerability Resources Developer Information Wiki Issues Slack Self Serve Portal Infrastructure Whimsy Brand Guidelines Project Logos Downloads Distributions Releases Infrastructure Status Infrastructure Statistics About About Our Sponsors Corporate Sponsorship Individual Supporters Leadership Members Diversity & Inclusion Newsroom Contact Privacy Policy Copyright © 2025 The Apache Software Foundation, Licensed under the Apache License, Version 2.0 . | 2026-01-13T08:49:47 |
https://twitter.com/intent/tweet?text=%22The%20First%20Week%20at%20a%20Startup%20Taught%20Me%20More%20Than%20I%20Expected%22%20by%20%40aryanc193%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fitsugo%2Fthe-first-week-at-a-startup-taught-me-more-than-i-expected-158a | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:47 |
https://docs.suprsend.com/changelog?_gl=1*12fhh1c*_gcl_au*MTk4MjY1MzcwOC4xNzM3MjcwMDQwLjE2MTg0OTAwOC4xNzQyNDY0NTg3LjE3NDI0NjQ1ODY.*_ga*MTEwNDU5MzYxMC4xNzI5NDkxODI3*_ga_PPDYBESP2L*MTc0MjYzMDUxMC4yMDguMS4xNzQyNjMwNjM2LjIuMC4w#getting-started | Product Updates - 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 Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:47 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fzeroday.forem.com%2Fagardnerit%2Fosquery-opentelemetry--55c | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjwebsite-go%252Freadiness-probe-3co0%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | 登录 Facebook Notice 登录后才能继续。 登录 Facebook 登录后才能继续。 登录 忘记账户了？ 或 创建新账户 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T08:49:47 |
https://docs.suprsend.com/changelog?_gl=1*12fhh1c*_gcl_au*MTk4MjY1MzcwOC4xNzM3MjcwMDQwLjE2MTg0OTAwOC4xNzQyNDY0NTg3LjE3NDI0NjQ1ODY.*_ga*MTEwNDU5MzYxMC4xNzI5NDkxODI3*_ga_PPDYBESP2L*MTc0MjYzMDUxMC4yMDguMS4xNzQyNjMwNjM2LjIuMC4w#what-you-can-do-with-suprsend-mcp | Product Updates - 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 Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:47 |
https://opensource.org/license/category/superseded | Superseded – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home Blog Superseded Category: Superseded Search Licenses You've searched for: ‘ ’ clear search Search for: Search Categories International Non-Reusable Other/Miscellaneous Popular / Strong Community Redundant with more popular Special Purpose Superseded Uncategorized Voluntarily retired clear categories View All Licenses Posts pagination 1 2 Column headers with buttons are sortable License Name SPDX ID Category The European Union Public License, version 1.1 EUPL-1.1 Superseded Unicode, Inc. License Agreement – Data Files and Software Unicode-DFS-2015 Special Purpose Superseded Artistic License (Perl) 1.0 Artistic-1.0-Perl Superseded GNU General Public License, version 1 Superseded Open Software License 2.1 OSL-2.1 Superseded Eclipse Public License -v 1.0 EPL-1.0 Superseded Common Public License Version 1.0 CPL-1.0 Superseded Open Software License, version 1.0 OSL-1.0 Superseded Apache Software License, version 1.1 Apache-1.1 Superseded Artistic License 1.0 Artistic-1.0 Superseded Educational Community License, Version 1.0 ECL-1.0 Superseded Eiffel Forum License, version 1 EFL-1.0 Superseded Posts pagination 1 2 Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://dev.to/sunny7899/documenting-the-journey-preparing-for-a-senior-ui-engineer-role-at-servicenow-81a#6-questions-i-ask-them | Documenting the Journey: Preparing for a Senior UI Engineer Role at ServiceNow - 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 Neweraofcoding Posted on Dec 29, 2025 Documenting the Journey: Preparing for a Senior UI Engineer Role at ServiceNow # devjournal # interview # career # ui There’s a moment in every engineering career where you pause—not because you’re stuck, but because you’re leveling up . This blog is about one of those moments for me. Recently, I started preparing for a Senior Software Engineer – UI role at ServiceNow . Instead of rushing through prep, I decided to slow down and document the journey —the prompts, the reflections, and the story behind my work. This post is both a record for myself and a guide for anyone preparing for a similar transition. Why I Decided to Document This Interview prep can feel transactional: Memorize answers Practice talking points Hope it clicks But this role made me realize something: This wasn’t just interview prep. This was a reflection of my career so far. ServiceNow’s focus on AI-powered UX, observability, scale, and craftsmanship forced me to connect dots across my experience—from building dashboards and APIs to integrating ML and designing for trust. So instead of just “preparing answers,” I framed everything as a story . The Prompts That Shaped the Story These were the prompts I worked through—and honestly, they map really well to how senior engineers think. 1. Short Introduction (2 minutes) This wasn’t about listing tools. It was about answering: What problems do I enjoy solving? How does my work create impact? Why does my experience make sense now ? I focused on: Building customer-facing UI Turning complex systems into simple experiences Using AI not as a buzzword , but as a practical tool The goal wasn’t to sound impressive—it was to sound clear . 2. What Do I Know About ServiceNow? (30 seconds) This forced me to zoom out. Not just: “They do workflow automation.” But: They connect people, systems, and processes They’re investing deeply in AI-native experiences Observability isn’t just metrics—it’s insight and action This helped me align my past work with where the platform is going. 3. Why This Role, Why Now? This was one of the most important reflections. I realized I wasn’t leaving my current role because of dissatisfaction. I was leaving because I wanted: More product-driven engineering More scale A place where UI, AI, and platform thinking intersect That clarity alone boosted my confidence. 4. What I Want in My Next Opportunity This wasn’t about perks or titles. I wrote down three things: Ownership from idea to delivery Strong engineering culture (reviews, quality, reliability) Space to grow—technically and as a mentor Simple. Honest. Grounded. 5. A Real Challenge (Not a Perfect Story) Instead of a “hero story,” I picked a messy one: Inconsistent data Tight timelines Evolving requirements Cross-team friction I talked about: Trade-offs Decisions What broke What I learned That reflection reminded me: Senior engineering isn’t about avoiding problems—it’s about navigating them calmly. 6. Questions I Ask Them This flipped the dynamic. Instead of trying to impress, I got curious: What problems matter most right now? How does AI actually show up in the product? How do teams collaborate end-to-end? It made the conversation feel mutual—not one-sided. What This Process Taught Me A few things really stood out: Good interviews are storytelling exercises AI experience matters most when tied to user trust UI engineering at scale is about empathy, not pixels Preparation is confidence—not memorization Most importantly, I realized I already had the experience. I just needed to frame it clearly. Why I’m Keeping This Documented Careers are long. It’s easy to forget: Why you chose certain paths How much you’ve learned What kind of engineer you’re becoming This blog is a checkpoint. Whether or not this specific role works out, the process itself already paid off. I’m sharper, clearer, and more intentional than I was before. And that’s a win. Final Thought If you’re preparing for a senior role: Don’t just study the job description Study your own journey There’s more alignment there than you think. End of entry. 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 Neweraofcoding Follow Expert Front end developer with Angular, and React experience Location Delhi India Joined Nov 4, 2020 More from Neweraofcoding Apertre 3.0: An Open-Source Program Empowering the Next Generation of Developers # codenewbie # career # learning # opensource The Agentic Leap: Key Announcements and Demos from the Google I/O 2025 Developer Keynote # webdev # ai # career # productivity What is the Microsoft MVP Award and its benefits? # career # leadership # microsoft 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:47 |
https://docs.suprsend.com/changelog?_gl=1*12fhh1c*_gcl_au*MTk4MjY1MzcwOC4xNzM3MjcwMDQwLjE2MTg0OTAwOC4xNzQyNDY0NTg3LjE3NDI0NjQ1ODY.*_ga*MTEwNDU5MzYxMC4xNzI5NDkxODI3*_ga_PPDYBESP2L*MTc0MjYzMDUxMC4yMDguMS4xNzQyNjMwNjM2LjIuMC4w#compatible-ai-tools | Product Updates - 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 Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:47 |
https://gitconnected.com/learn/python | Resume Builder Tutorials Find a Job Blog Sign In Get Started Home Coding Tutorials Python Learn Python - Tutorials, Courses, and Books Learn Python for free. Find Python tutorials submitted by developers with the best content rising to the top, voted on by the programmers that use them. Learn Python online with the best Python tutorials and courses. View All Categories Build Your Developer Resume Create a professional resume that showcases your Python skills Generate Resume 112 Tutorials 2 Python Tutorial | AlphaCodingSkills ( alphacodingskills.com ) Python Tutorials - Learn about Python Tutorial and various other topics of Python - explained with well thought examples - edit & run examples online and learn by examples. AlphaCodingSkills View Tutorial 1 Python Network Programming ( udemy.com ) Scripting TCP/IP network tools & packets, with Scapy & Python for network engineers, Ethical Hacking, Protocol Testing 1.5 hours Udemy View Tutorial 1 Python Tutorial For Beginners - Full Course ( youtube.com ) This video on Python will take you through all the basics and advanced concepts present in Python programming language. You will learn about data types, vari... YouTube View Tutorial 1 Matplotlib Tutorial (A Python Plotting Library) ( javatpoint.com ) Matplotlib Tutorial with Data Visualization, Why need Data Visualization, Benefits, Architecture of Matplotlib, General Concept of Matplotlib, Installing Matplotlib, subplot, functions of Matplotlib etc. www.javatpoint.com View Tutorial 1 Python for Data Science Training Course ( intellipaat.com ) Enroll for Python for Data Science training Course training and master Python library & Python packages such as like SciPy, NumPy, MatPlotLib, Lambda function and more. Be a Python for Data Science Certification Course Expert! ✓39 Hrs Learning ✓ 24 Hrs Projects ✓ Life Time Access ✓ 24 X 7 Support ✓ … Intellipaat View Tutorial 1 Python Matplotlib Tutorial: Plotting Data And Customisation ( blog.quantinsti.com ) In this tutorial on Python Matplotlib, we will understand how to install and create plots using the functions present in the Matplotlib package. QuantInsti View Tutorial 1 Python Tutorial – Learn Python 3 Programming Online ( intellipaat.com ) In this python tutorial for beginners, you can learn python programming 3 with hands on exercises. Learn python programming online from python experts Intellipaat Blog View Tutorial 1 Python for Absolute Beginners ( udemy.com ) Learn Python and programming fundamentals with this Python tutorial for absolute beginners. 32 mins Udemy View Tutorial 1 Python in Depth: Hands-on Python Programming with Projects ( udemy.com ) Python programming course to have Python 3 skills for projects/interview questions. Includes advanced Python topics 17.5 hours Udemy View Tutorial 1 Python Pandas Tutorial: Installation, Series and DataFrame ( blog.quantinsti.com ) In this article on Python Pandas, we will see how to install Python Pandas and the Pandas data structures Series as well as DataFrame and their functions QuantInsti View Tutorial 1 Python Pandas Data operations ( javatpoint.com ) Python Pandas | Python Pandas Tutorial, Python Pandas Introduction, What is Python Pandas, Data Structures, Reading Multiple Files, Null values, Multiple index, Application, Application Basics, Resampling, Plotting the data, Moving windows functions, Series, Read the file, Data operations, Filter Da… www.javatpoint.com View Tutorial 1 Python for Beginners: Master Python Programming from Scratch ( udemy.com ) Python Programming Complete Course absolutely for beginnners, Learn Python from scratch and build your own Programs 2 hours Udemy View Tutorial 1 Python Course for Beginners ( youtube.com ) Here is a complete course on Python which takes you through everything from writing a “Hello World” program to making predictions using Python. All demos are... YouTube View Tutorial 1 Python Tutorial for Beginners ( youtube.com ) ?Intellipaat Python for Data Science training course: https://intellipaat.com/python-for-data-science-training/ ? Read complete Python tutorial here: https:/... YouTube View Tutorial 1 Python Succinctly ( syncfusion.com ) Learn to use the Python language to create programs of all kinds. Author Jason Cannon will guide you from complete unfamiliarity with Python to creating practical applications. With Python Succinctly, lack of experience isn’t an obstacle to programming language mastery. View Tutorial 1 Python for Trading ( quantra.quantinsti.com ) Courses on Algorithmic and Quantitative Trading View Tutorial 1 Python for Beginners: A Step-By-Step Guide ( courses.tetranoodle.com ) learn Python language Tutorial For Beginners: Step-By-Step Hands-On Guide TetraNoodle - Online Courses On DevOps, Cloud Computing, Machine Learning, Cyber Security, Mobile View Tutorial 1 The Quick Python Book, Third Edition ( manning.com ) Naomi’s book epitomizes what it is to be Pythonic: beautiful is better than ugly, simple is better than complex, and readability counts. Manning Publications View Tutorial 1 Exploring Python Basics ( manning.com ) placing your order... Manning Publications View Tutorial 1 Introducing Data Science ( manning.com ) Read this book if you want to get a quick overview of data science, with lots of examples to get you started! Manning Publications View Tutorial 1 Data Science with Python and Dask ( manning.com ) The most comprehensive coverage of Dask to date, with real-world examples that made a difference in my daily work. Manning Publications View Tutorial 1 The Art of Data Usability ( manning.com ) Data is only valuable if it’s useful. If you’re responsible for making meaningful data available to business stakeholders, researchers, or even the general public, you need a predictable process for discerning the users’ needs and delivering the right data in the right way. So how do you establish t… Manning Publications View Tutorial 1 Practices of the Python Pro ( manning.com ) Exactly what I’d hoped for in a book with this title. Manning Publications View Tutorial 1 Learn Quantum Computing with Python and Q# ( manning.com ) A great introduction to the exciting new world of quantum computing. Manning Publications View Tutorial 1 Python Workout ( manning.com ) The book is a great adaptation of a face-to-face training at a fraction of the cost. It is like having a master instructor right next to you as you work through different problems. Manning Publications View Tutorial 2 Classic Computer Science Problems in Python ( manning.com ) Whether you’re a novice or a seasoned professional, there’s an Aha! moment in this book for everyone. Manning Publications View Tutorial 2 Mastering Large Datasets with Phyton ( manning.com ) It’s a joy to read with examples that will help you learn the topic. Manning Publications View Tutorial 1 Python Programming Language ( geeksforgeeks.org ) This page contains all topics of Python with clear explanations & examples. It also contains job interview questions,MCQ quizzes and output based questions. GeeksforGeeks View Tutorial 1 A Layman's guide to Python ( udemy.com ) Learn Python from the basics. 12 hours Udemy View Tutorial 1 The Complete Python Programming Course for Beginners ( codewithmosh.com ) Learn Python for AI, Machine Learning, Data Science and App Development Code with Mosh View Tutorial 1 Python for Everybody - Full Course with Dr. Chuck ( youtube.com ) This Python 3 tutorial course aims to teach everyone the basics of programming computers using Python. The course has no pre-requisites and avoids all but th... YouTube View Tutorial 1 Building GUI Apps with Python ( learnpyqt.com ) The hands-on guide to building PyQt5 apps. Rapid GUI development with Python. Learn PyQt View Tutorial 2 Practical Python Course for Beginners ( pythonprinciples.com ) Learn the Basics of Python Programming online with Python Principles. Helpful community, example-based learning, and 100+ coding exercises. Python Principles View Tutorial 1 A Smarter Way to Learn Python ( amazon.com ) A Smarter Way to Learn Python: Learn it faster. Remember it longer. - Kindle edition by Mark Myers. Download it once and read it on your Kindle device, PC, phones or tablets. Use features like bookmarks, note taking and highlighting while reading A Smarter Way to Learn Python: Learn it faster. Remem… Amazon View Tutorial 1 Master Python: Complete Beginners Course ( youtube.com ) YouTube View Tutorial 2 Learn Python Step by Step ( techbeamers.com ) Python tutorial for beginners to start learning from simple to advanced concepts of Python programming language in quick and easy steps. Best Programming and Testing Help for Beginners View Tutorial 3 Python Programming Tutorials ( youtube.com ) Here is all of my Python Programming high quality tutorials! YouTube View Tutorial 3 Learn Python, Break Python ( learnpythonbreakpython.com ) Learn Python, Break Python View Tutorial 5 Developing Scalable Apps in Python ( udacity.com ) You will learn about challenges of building applications that can serve hundreds of thousands of users, and how you can prepare for them as a developer. Udacity View Tutorial 2 Practice Python Online - Interactive Coding Game ( py.checkio.org ) py.CheckiO - Python practice online. Improve your coding skills by solving coding challenges and exercises online with your friends in a fun way. Exchanges experience with other users online through fun coding activities. py.CheckiO - Python coding challenges and exercises with solutions for beginners and advanced View Tutorial 2 Full Speed Python ( github.com ) Full Speed Python: a book for self-learners. Contribute to joaoventura/full-speed-python development by creating an account on GitHub. GitHub View Tutorial 2 Pytudes ( github.com ) Python programs to practice or demonstrate skills. - norvig/pytudes GitHub View Tutorial 2 Full Stack Python ( fullstackpython.com ) Full Stack Python explains programming concepts in plain language and provides links to the best tutorials for those topics. View Tutorial 2 Mastering Object-oriented Python ( packtpub.com ) If you want to master object-oriented Python programming this book is a must-have. With 750 code samples and a relaxed tutorial, it’s a seamless route to programming Python. Learn Spring for Android Application Development View Tutorial 1 The Python Bible: Everything You Need to Program in Python ( udemy.com ) Build 11 Projects and go from Beginner to Pro in Python with the World's Most Fun Project-Based Python Course! 9 hours Udemy View Tutorial 2 The Coder's Apprentice: Learning Programming with Python 3 ( spronck.net ) The Coder’s Apprentice is a Python 3 course book, written by Pieter Spronck, aimed at students and teenagers who are completely new to programming. This book presumes no previous programming experience and contains numerous exercises. home View Tutorial 2 The Ultimate Python Programming Tutorial ( udemy.com ) Python Programming tutorial for beginners. This Python Training Course Comes with Certification of Completion 6 hours Udemy View Tutorial 2 Computer Programming using Python (by University of Waterloo) ( cscircles.cemc.uwaterloo.ca ) View Tutorial 2 Introduction to Python ( realpython.com ) An overview of the contents of the Real Python Course Bundle. With our courses you will learn Python programming through hands-on, interesting examples that are useful and fun. Launch your development career with a proven program, written by Python professionals. View Tutorial 2 Wikibooks Python Programming ( en.wikibooks.org ) This book describes Python, an open-source general-purpose interpreted programming language available for a broad range of operating systems. There are currently three major implementations: the standard implementation written in C, Jython written in Java, and IronPython written in C# for the .NET e… Wikibooks, open books for an open world View Tutorial 3 Get Programming with Python in Motion ( manning.com ) Provides an easy to follow introduction to both computer programming and the Python language. Manning Publications View Tutorial 2 Learning with Python 3 ( openbookproject.net ) View Tutorial 2 Python Programming Tutorials ( youtube.com ) Our Python Tutorials will help you learn Python quickly and thoroughly. We start with “Hello World” and then move on to data structures (sets, lists, tuples ... YouTube View Tutorial 1 Python Training ( mindmajix.com ) Learn Python Programming & Become JOB READY ✓ 24*7 Support ✓ Instructor-Led /Self-Paced Training ✓ Live Projects & Material ✓ Python Certification ✓ Free DEMO! Mindmajix View Tutorial 1 Python Programming ( software-skills-training.com ) This Python programming course shows how to rapidly develop and maintain effective Python programs. The training course includes thorough coverage of Python syntax, built in data types and control constructs. Extensive hands on exercises are used throughout to reinforce learning and develop real c… View Tutorial 1 Ultimate Guide on Data Science - Learn to Make Python Data Structures ( bitdegree.org ) Want to learn python data structures? Start your journey in data science - follow this course to learn python data structures & the pandas dataframe! Copyright © 2019 BitDegree.org | [email protected] View Tutorial 1 Learn Python Basics ( bitdegree.org ) Interested in python projects for beginners? This course is the best way to learn python basics through hands-on coding examples. Start today! Copyright © 2019 BitDegree.org | [email protected] View Tutorial 1 Python Web Development (Flask, PostgreSQL, Heroku) ( udemy.com ) Learn to build scalable Python Web Applications with Flask, PostgreSQL, SQLAlchemy, git, and Heroku With Awesome Project 5.5 hours Udemy View Tutorial 1 Advanced Business Analytics ( manipalprolearn.com ) Manipal ProLearn, offers Advanced Business Analytics with ‘Python’ programming language Online Certification Training / Tutorial with exams for working professionals in India. Enroll Now to upgrade your skills. Manipal ProLearn View Tutorial 3 Python Video Tutorials by PySide ( youtube.com ) Learn how to create simple GUI window application using Python Pyside. YouTube View Tutorial 1 Web Scraping with Python (BeautifulSoup, Requests, Selenium) ( udemy.com ) Web Scraping and Crawling with Python: Beautiful Soup, Requests & Selenium 8 hours Udemy View Tutorial 1 Learn Scrapy for Python Web Crawling and Scraping ( udemy.com ) Python Scrapy Tutorial - Learn how to scrape websites and build a powerful web crawler using Scrapy and Python 9 hours Udemy View Tutorial 1 Mastering Python ( packtpub.com ) Unlock the power of Python by learning effective application development strategies Learn Spring for Android Application Development View Tutorial 1 Python 3 programming tutorial ( youtube.com ) Facebook - https://www.facebook.com/TheNewBoston-464114846956315/ GitHub - https://github.com/buckyroberts Google+ - https://plus.google.com/+BuckyRoberts… YouTube View Tutorial 1 Learn More Python 3 the Hard Way ( amazon.com ) Learn More Python 3 the Hard Way: The Next Step for New Python Programmers (Zed Shaw’s Hard Way Series): 9780134123486: Computer Science Books @ Amazon.com Amazon View Tutorial 1 Wikibooks Non-Programmer's Tutorial for Python 3 ( en.wikibooks.org ) This is a conversion of the Non-Programmer’s Tutorial for Python 2.6 to Python 3. Wikibooks, open books for an open world View Tutorial 1 Learn Python ( codeschool.com ) Python is an interpreted object-oriented programming language. It is open source, so the interpreter and source are freely available and distributable in binary form. Python has many built-in high-level data structures and utilizes dynamic typing and binding, making it an excellent choice for both s… Pluralsight View Tutorial 1 Intro to Python for Data Science ( datacamp.com ) DataCamp’s Intro to Python course teaches you how to use Python programming for data science with interactive video tutorials. Start learning Python today! DataCamp View Tutorial 2 Python for Data Science ( youtube.com ) YouTube View Tutorial 155 Python Class by Google ( developers.google.com ) Assorted educational materials provided by Google. Google Developers View Tutorial 4 The Hitchhiker’s Guide to Python ( docs.python-guide.org ) An opinionated guide to the Python programming language and a best practice handbook to the installation, configuration, and usage of Python on a daily basis. View Tutorial 123 The Complete Python Bootcamp ( udemy.com ) Learn Python like a Professional! Start from the basics and go all the way to creating your own applications and games! 24 hours Udemy View Tutorial 101 Interactive Python Tutorial ( codecademy.com ) Learn Python, a powerful language used by sites like YouTube and Dropbox. Learn the fundamentals of programming to build web apps and manipulate data. Master Python loops to deepen your knowledge. Codecademy View Tutorial 6 Python For Everybody ( coursera.org ) Python for Everybody from University of Michigan. This Specialization builds on the success of the Python for Everybody course and will introduce fundamental programming concepts including data structures, networked application program ... Coursera View Tutorial 1 Getting Started with Python ( coursera.org ) Programming for Everybody (Getting Started with Python) from University of Michigan. This course aims to teach everyone the basics of programming computers using Python. We cover the basics of how one constructs a program from a series of simple ... Coursera View Tutorial 1 An Introduction to Interactive Programming in Python ( coursera.org ) An Introduction to Interactive Programming in Python (Part 1) from Rice University. This two-part course is designed to help students with very little or no computing background learn the basics of building simple interactive applications. Our ... Coursera View Tutorial 89 Learn Python - Python Study Path for Beginner, Intermediate, or Advanced ( pluralsight.com ) Python is an interpreted object-oriented programming language. It is open source, so the interpreter and source are freely available and distributable in binary form. Python has many built-in high-level data structures and utilizes dynamic typing and binding, making it an excellent choice for both s… Pluralsight View Tutorial 6 Learn Python from Scratch ( eduonix.com ) Learn python programming and become a complete python professional from scratch. Enroll in our Free python course at Eduonix now www.eduonix.com View Tutorial 1 Python Programming Track ( datacamp.com ) A Python Programmer uses their programming skills to wrangle data and build tools for data analysis. View Tutorial 48 Learn Python the Hard Way ( learnpythonthehardway.org ) This is a free sample of Learn Python 2 The Hard Way with 8 exercises and Appendix A available for you to review. This purchase includes a PDF, paid HTML view you can access from anywhere, and videos covering every exercise for Windows, Linux, and macOS. There is a new version of t… Learn Python the Hard Way View Tutorial 23 Automate the Boring Stuff with Python ( automatetheboringstuff.com ) View Tutorial 53 The Official Python Tutorial ( docs.python.org ) View Tutorial 67 Automate the Boring Stuff with Python Programming ( udemy.com ) A practical programming course for office workers, academics, and administrators who want to improve their productivity. 9.5 hours Udemy View Tutorial 31 The Complete Python Masterclass ( udemy.com ) This Python For Beginners Course Teaches You The Python Language Fast. Includes Python Online Training With Python 3 42 hours Udemy View Tutorial 32 Introduction to Programming with Python ( mva.microsoft.com ) Get Python training from the experts. Take free MVA course that gives you the basics of programming with Python – and start writing your own programs. Microsoft Virtual Academy View Tutorial 21 A Byte of Python ( swaroopch.com ) View Tutorial 26 Think Python 2 ( greenteapress.com ) Think Python 2nd Edition by Allen B. Downey Green Tea Press Free books by Allen B. Downey Menu and widgets View Tutorial 13 Python for You and Me ( pymbook.readthedocs.io ) Logo View Tutorial 75 Python Class by Google (Video) ( youtube.com ) Google Python Class YouTube View Tutorial 12 Build 10 Real World Python Applications ( udemy.com ) Start Python from the basics and learn how to create 10 amazing and professional Python programs used in the real world! 24 hours Udemy View Tutorial 14 Dive Into Python 3 ( diveintopython3.net ) View Tutorial 3 Invent with Python ( inventwithpython.com ) Invent with Python View Tutorial 8 Introduction To Python Programming ( udemy.com ) A Quick and Easy Intro into Python Programming 4.5 hours Udemy View Tutorial 5 Python for Informatics: Exploring Information ( pythonlearn.com ) View Tutorial 8 Test-Driven Development with Python ( chimera.labs.oreilly.com ) Gain technology and business knowledge and hone your skills with learning resources created and curated by O’Reilly’s experts: live online training, video, books, conferences, our platform has content from 200+ of the world’s best publishers. O'Reilly home View Tutorial 7 Python 3.4 Programming Tutorials ( youtube.com ) Official playlist for thenewboston Python 3.4 Programming Tutorials! YouTube View Tutorial 6 Practice Python Coding Challenges ( practicepython.org ) View Tutorial 4 Learn Python from Scratch ( udemy.com ) Python course for beginners, Learn Python Programming , Python Web Framework Django, Flask, Web scraping and a lot more. 24 hours Udemy View Tutorial 4 Introduction to Python for Data Science ( academy.vertabelo.com ) Are you interested in data programming? Or maybe you’re a beginner data scientist or you take classes in data analysis? This course is just for you! Start now and become a master in analysing and presenting data! Vertabelo Academy View Tutorial 6 The Python Guru ( thepythonguru.com ) Start learning python from the basics to pro level. Everything you need to become proficient in python The Python Guru View Tutorial 8 Python Programming Beginner Tutorials ( youtube.com ) In these Python Beginner Tutorials, we will be learning the fundamentals of Python programming from the ground up. We will be learning how to: install/setup ... YouTube View Tutorial 2 The Hacker's Guide to Python ( thehackerguidetopython.com ) View Tutorial 4 Python Practice Book ( anandology.com ) Welcome to Python Practice Book. View Tutorial 4 Python for You and Me ( pymbook.readthedocs.org ) Logo View Tutorial 3 Learn Programming in 7 Days ( guru99.com ) Python is an object-oriented programming language created by Guido Rossum. In this interactive tutorial learn python programming from basics concepts to advanced with python 2 and 3 examples. © Copyright - Guru99 2019 Privacy Policy © Copyright - Guru99 2019 Privacy Policy View Tutorial 3 Anaconda Training ( anaconda.com ) Anaconda Training helps people master the technical obstacles to data analysis, ask better questions of their data, and solve actual, real-world problems. Anaconda View Tutorial 4 Beginner Course for Python Programming ( dataquest.io ) Learn Python and R for data science. Learn by coding and working with data in your browser. Build your portfolio with projects and become a data scientist. Dataquest View Tutorial 3 Python Web App Course ( udemy.com ) Build Python Web Applications from Beginner to Expert using Python and Flask 16.5 hours Udemy View Tutorial 3 The Python Workbook: Solve 100 Exercises ( udemy.com ) Boost your Python skills by solving 100 Python code assignments ranging from easy to expert level. Solutions included! 3 hours Udemy View Tutorial 3 Using Python ( usingpython.com ) GCSE Computing Python Resources -- Learn Python by developing programming solutions to fun and exciting real-world problems. Using Python View Tutorial 2 Python from Scratch ( open.cs.uwaterloo.ca ) Python from scratch View Tutorial 5 Python Cookbook ( chimera.labs.oreilly.com ) Gain technology and business knowledge and hone your skills with learning resources created and curated by O’Reilly’s experts: live online training, video, books, conferences, our platform has content from 200+ of the world’s best publishers. O'Reilly home View Tutorial What is Python Python is a dynamic, general programming language utilized in many fields, including web development, data science, scientific computing, application interfaces, and many more. Python supports many programming paradigms, such as object-oriented programming, imperative programming, and functional programming. Python is most notable for its code readability and making whitespace significant. Community is a key part of Python, with many of its most popular packages being built open source by individual contributors. Why learn Python Python is recognized as one of the most loved programming languages by developers. The love for Python has created mass adoption both within the technology industry as well as academia. The language also has broad applications, giving you the ability to utilize it numerous ways. Python was created almost thirty years ago, but it is still continuing to grow in popularity with time. The broad applications of the language and ease of learning make it an ideal choice for any programmer, from beginner to advanced. Before learning Python Python’s focus is on readability for the developers. This aspect makes learning the language perfect for beginners. You can begin learning Python with no programming background. Many universities teach it as the first language in their computer science programs or across disciplines in other departments. Python makes sense to learn from day one but remains useful as you progress as a software engineer. How gitconnected help you learn Python and find the best tutorials gitconnected offers a huge selection of Python tutorials, from beginner to advanced. We have courses for any learning style - you can follow along with interactive programming courses, learn Python from videos, or find books and articles teaching the Python programming language. gitconnected enables you find the best free Python tutorials or to discover paid courses. Python tutorials are submitted and ranked by developers, ensuring you are always learning from the best Python content. Python has applications including web development, data science, scripting, and application programming, and gitconnected gives you the ability to learn Python for whichever track fits your interests. Follow all the Python updates using the news feed on the gitconnected.com home page. Search Tutorials Filter by Tag Level Beginner ( 162 ) Advanced ( 23 ) Cost Free ( 153 ) Paid ( 83 ) Content Video ( 69 ) Interactive Coding ( 38 ) Book ( 49 ) Version Python 3 ( 7 ) Python 2 ( 2 ) Subcategory Data Science ( 24 ) Anaconda ( 7 ) PySide ( 8 ) Recently Viewed You have not viewed any tutorials this session Join our Community Connect with other developers learning Python in our Slack community Join Slack - @treyhuffine Find a Job Career Growth Tools Learn to Code About | 2026-01-13T08:49:47 |
https://youtu.be/s/player/b75a8e80/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:49:47 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjwebsite-go%252Freadiness-probe-3co0%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Iniciar sesión en Facebook Notice Debes iniciar sesión para continuar. Iniciar sesión en Facebook Debes iniciar sesión para continuar. Iniciar sesión ¿Olvidaste tu cuenta? o Crear cuenta nueva Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T08:49:47 |
https://dev.to/kashifsoofi | Kashif Soofi - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Kashif Soofi 404 bio not found Joined Joined on Dec 4, 2020 github website Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close 16 Week Writing Streak You are a writing star! You've written at least one post per week for 16 straight weeks. Congratulations! Got it Close 8 Week Writing Streak The streak continues! You've written at least one post per week for 8 consecutive weeks. Unlock the 16-week badge next! Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close Hacktoberfest 2021 Awarded for successful completion of the 2021 Hacktoberfest challenge. Got it Close More info about @kashifsoofi Post 36 posts published Comment 1 comment written Tag 14 tags followed GTK4 DropDown with .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Jan 8 GTK4 DropDown with .NET # dotnet # tutorial # ui Comments Add Comment 5 min read Want to connect with Kashif Soofi? Create an account to connect with Kashif Soofi. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in GTK4 `dotnet new` Project Template Kashif Soofi Kashif Soofi Kashif Soofi Follow Apr 10 '24 GTK4 `dotnet new` Project Template # dotnet # gtk4 1 reaction Comments Add Comment 2 min read GTK4 ColumnView with .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Mar 28 '24 GTK4 ColumnView with .NET # dotnet # gtk4 Comments Add Comment 4 min read GTK 4 GridView with .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Feb 28 '24 GTK 4 GridView with .NET # dotnet # gtk4 2 reactions Comments Add Comment 4 min read GTK 4 ListView with .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Feb 21 '24 GTK 4 ListView with .NET # dotnet # gtk4 2 reactions Comments Add Comment 4 min read Entity Framework Core Owned Entity Kashif Soofi Kashif Soofi Kashif Soofi Follow Feb 15 '24 Entity Framework Core Owned Entity # dotnet # efcore 7 reactions Comments Add Comment 8 min read Counter App with GTK4 CompositeTemplate and Rust Kashif Soofi Kashif Soofi Kashif Soofi Follow Feb 1 '24 Counter App with GTK4 CompositeTemplate and Rust # rust # gtk4 1 reaction Comments Add Comment 5 min read Choose Font with GTK4 and .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Jan 25 '24 Choose Font with GTK4 and .NET # dotnet # csharp # gtk4 Comments Add Comment 3 min read Counter App with GTK4 and .NET Kashif Soofi Kashif Soofi Kashif Soofi Follow Jan 18 '24 Counter App with GTK4 and .NET # dotnet # csharp # gtk4 1 reaction Comments Add Comment 3 min read Choose Font with GTK4 and Rust Kashif Soofi Kashif Soofi Kashif Soofi Follow Jan 11 '24 Choose Font with GTK4 and Rust # rust # gtk4 Comments Add Comment 4 min read Counter App with GTK4 and Rust Kashif Soofi Kashif Soofi Kashif Soofi Follow Jan 4 '24 Counter App with GTK4 and Rust # gtk4 # rust Comments Add Comment 3 min read Integration Test SQL Server Store with testcontainers-go Kashif Soofi Kashif Soofi Kashif Soofi Follow Oct 12 '23 Integration Test SQL Server Store with testcontainers-go # testing # sqlserver # githubactions # go 1 reaction Comments Add Comment 5 min read Integration Test SQL Server Store (Go) Kashif Soofi Kashif Soofi Kashif Soofi Follow Oct 5 '23 Integration Test SQL Server Store (Go) # testing # sqlserver # githubactions # go 2 reactions Comments 1 comment 11 min read Integration Test MySQL Store with testcontainers-go Kashif Soofi Kashif Soofi Kashif Soofi Follow Sep 28 '23 Integration Test MySQL Store with testcontainers-go # testing # mysql # githubactions # go 3 reactions Comments Add Comment 4 min read Integration Test MySQL Store (Go) Kashif Soofi Kashif Soofi Kashif Soofi Follow Sep 21 '23 Integration Test MySQL Store (Go) # testing # mysql # githubactions # go 1 reaction Comments 1 comment 11 min read Integration Test Postgres Store with testcontainers-go Kashif Soofi Kashif Soofi Kashif Soofi Follow Sep 14 '23 Integration Test Postgres Store with testcontainers-go # testing # postgres # githubactions # go 1 reaction Comments 1 comment 7 min read Integration Test Postgres Store (Go) Kashif Soofi Kashif Soofi Kashif Soofi Follow Sep 7 '23 Integration Test Postgres Store (Go) # testing # postgres # githubactions # go 2 reactions Comments 1 comment 10 min read Integration Test SQL Server with testcontainers-dotnet Kashif Soofi Kashif Soofi Kashif Soofi Follow Sep 1 '23 Integration Test SQL Server with testcontainers-dotnet # testing # sqlserver # githubactions 4 reactions Comments Add Comment 5 min read Integration Test SQL Server Store Kashif Soofi Kashif Soofi Kashif Soofi Follow Aug 25 '23 Integration Test SQL Server Store # testing # sqlserver # githubactions 2 reactions Comments Add Comment 10 min read Integration Test MySQL with testcontainers-dotnet Kashif Soofi Kashif Soofi Kashif Soofi Follow Aug 18 '23 Integration Test MySQL with testcontainers-dotnet # testing # mysql # ci 6 reactions Comments Add Comment 5 min read Integration Testing MySQL Store Kashif Soofi Kashif Soofi Kashif Soofi Follow Aug 11 '23 Integration Testing MySQL Store # testing # mysql # githubactions 1 reaction Comments Add Comment 10 min read Integration Test Postgres using testcontainers-net and GitHub Actions Kashif Soofi Kashif Soofi Kashif Soofi Follow Aug 4 '23 Integration Test Postgres using testcontainers-net and GitHub Actions # testing # githubactions # postgres 1 reaction Comments Add Comment 3 min read Integration Test Postgres using docker-compose and GitHub Actions Kashif Soofi Kashif Soofi Kashif Soofi Follow Jul 28 '23 Integration Test Postgres using docker-compose and GitHub Actions # testing # ci # githubactions # postgres 1 reaction Comments Add Comment 3 min read Integration Test Postgres using GitHub Actions Kashif Soofi Kashif Soofi Kashif Soofi Follow Jul 21 '23 Integration Test Postgres using GitHub Actions # testing # ci # githubactions # postgres 3 reactions Comments Add Comment 4 min read Integration Test Postgres with testcontainers-dotnet Kashif Soofi Kashif Soofi Kashif Soofi Follow Jul 14 '23 Integration Test Postgres with testcontainers-dotnet # postgres # testing # csharp 1 reaction Comments Add Comment 5 min read REST API with Go, Chi and MongoDB Kashif Soofi Kashif Soofi Kashif Soofi Follow Jul 7 '23 REST API with Go, Chi and MongoDB # go # rest # api # mongodb 11 reactions Comments Add Comment 6 min read REST API with Go, Chi, SQL Server and sqlx Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 30 '23 REST API with Go, Chi, SQL Server and sqlx # rest # api # go # sql 4 reactions Comments Add Comment 8 min read REST API with Go, Chi, MySQL and sqlx Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 23 '23 REST API with Go, Chi, MySQL and sqlx # rest # go # mysql # api 17 reactions Comments 2 comments 7 min read REST API with Go, Chi, Postgres and sqlx Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 16 '23 REST API with Go, Chi, Postgres and sqlx # rest # api # go # postgres 7 reactions Comments Add Comment 7 min read REST API with Go, Chi and InMemory Store Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 9 '23 REST API with Go, Chi and InMemory Store # go # rest # api 8 reactions Comments 2 comments 14 min read Integration Testing Postgres Store Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 2 '23 Integration Testing Postgres Store # csharp # testing # integrationtest # dotnet 2 reactions Comments Add Comment 9 min read REST API with ASP.NET Core and MongoDB Kashif Soofi Kashif Soofi Kashif Soofi Follow Jun 1 '23 REST API with ASP.NET Core and MongoDB # rest # csharp # api # mongodb 2 reactions Comments Add Comment 5 min read REST API with ASP.NET Core 7 and SQL Server Kashif Soofi Kashif Soofi Kashif Soofi Follow May 31 '23 REST API with ASP.NET Core 7 and SQL Server # rest # api # csharp # sql 13 reactions Comments 1 comment 7 min read REST API with ASP.NET Core and MySql Kashif Soofi Kashif Soofi Kashif Soofi Follow May 24 '23 REST API with ASP.NET Core and MySql # rest # csharp # api # mysql 7 reactions Comments Add Comment 6 min read REST API with ASP.NET Core 7 and Postgres Kashif Soofi Kashif Soofi Kashif Soofi Follow May 18 '23 REST API with ASP.NET Core 7 and Postgres # rest # csharp # api # postgres 7 reactions Comments Add Comment 7 min read REST API with ASP.NET Core and InMemory Store Kashif Soofi Kashif Soofi Kashif Soofi Follow May 16 '23 REST API with ASP.NET Core and InMemory Store # rest # csharp # dotnet # api 4 reactions Comments Add Comment 6 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:47 |
https://www.algolia.com/de/developers/integrations | Integrate backend, front end or frameworks with Algolia | Algolia Niket --> Deutsch English français News DevCon2025 | October 1-2 Learn more Unternehmen Partners Einloggen Login Logout Algolia mark white Algolia logo white Lösungen Search Show users what they're looking for with AI-driven resuts. Search Show users what they're looking for with AI-driven resuts. Recommendations Use behavioral cues to drive higher engagement. Recommendations Use behavioral cues to drive higher engagement. Personalization Show each user what they need across their journey. Personalization Show each user what they need across their journey. Analytics All your insights in one dashboard. Analytics All your insights in one dashboard. Browse Move customers down the funnel with curated category pages. Browse Move customers down the funnel with curated category pages. Agent Studio Create, test, and deploy AI agents, fast. Agent Studio Create, test, and deploy AI agents, fast. Generative Experiences Build conversational solutions with retrieval augmented generation (RAG). Generative Experiences Build conversational solutions with retrieval augmented generation (RAG). Ask AI Deliver conversational answers—right from your search bar. Ask AI Deliver conversational answers—right from your search bar. MCP Server Search, analyze, or monitor your index within your agentic workflow. MCP Server Search, analyze, or monitor your index within your agentic workflow. Data Enrichment Modify, enhance, or restructure data as it’s indexed for search. Data Enrichment Modify, enhance, or restructure data as it’s indexed for search. Data Transformation Streamline data preparation and enhance data quality. Data Transformation Streamline data preparation and enhance data quality. Integrations Connect to your existing stack via pre-built libraries and APIs. Integrations Connect to your existing stack via pre-built libraries and APIs. Data Centers Choose from 70+ data centers across 17 regions. Data Centers Choose from 70+ data centers across 17 regions. Security & Compliance Built for peace of mind. Security & Compliance Built for peace of mind. Branchen Ecommerce Ecommerce B2B Commerce B2B Commerce Fashion Fashion Grocery Grocery Media Media Marketplaces Marketplaces SaaS SaaS Higher Education Higher Education Documentation search Documentation search Enterprise search Enterprise search Headless commerce Headless commerce Image search Image search Mobile & App search Mobile & App search Retail Media Network Retail Media Network Site search Site search Visual search Visual search Voice search Voice search Digital Experience Digital Experience Ecommerce Ecommerce Engineering Engineering Merchandising Merchandising Product Management Product Management Preise Entwickler GET STARTED Developer Hub Developer Hub Dokumentation Dokumentation Integrationen Integrationen UI-Komponenten UI-Komponenten Autocomplete Autocomplete RESOURCES Code Exchange Code Exchange Engineering Blog Engineering Blog MCP MCP Discord Discord Webinars & Events Webinars & Events QUICK LINKS Schnellstartanleitung Schnellstartanleitung Für Open Source Für Open Source API Status API Status Support Support Resources INSPIRATION Algolia Blog Algolia Blog Resource Center Resource Center Kundengeschichten Kundengeschichten Webinars & Events Webinars & Events Newsroom Newsroom LEARN Customer Hub Customer Hub What's New What's New AI Search Grader AI Search Grader Documentation Documentation Algolia Academy Algolia Academy Professional Services Professional Services Quick Access Unternehmen Partners Einloggen Login Logout Request demo Get started Search Algolia Close Request demo Get started Other Types Filter --> Clear All Filters Filters Looking for our logo? We got you covered! Brand guidelines Download logo pack Skalieren mit Integrationen Nutzen Sie Integrationen und vorgefertigte Bibliotheken, um skalierbare Sucherlebnisse zu entwickeln. --> --> --> No Products Found!!! „Suche spielt eine riesige Rolle im Nutzererlebnis. Heutzutage möchte niemand mehr durch eine hierarchische Navigation klicken, um Inhalte zu finden. Wenn Sie in eine Bibliothek gehen, suchen Sie nicht zuerst die Abteilung Fiktion und graben sich dann durch, um Game of Thrones zu finden. Das funktioniert nicht. Sie gehen zum Such-Tool, tippen game of thrones ein – und finden das Buch sofort!“ Saravana Kumar CEO @ Document360 „Die API- und SDK-Optionen sind wirklich großartig – ebenso die Fähigkeit, Traffic im großen Maßstab zu bewältigen. Wir haben ein hohes Volumen und Algolia ist sehr schnell – es kann mit unserem Traffic-Level problemlos mithalten.“ Matt Goorley Engineering Manager @ LTK „Die leistungsstarke SaaS-Lösung von Algolia übernimmt die Schwerstarbeit für unser kleines Entwicklungsteam. Indexing-APIs und andere Funktionen sind extrem hilfreich bei Promo-Änderungen, Preis-Updates oder Ranking-Anpassungen. Außerdem bietet Algolias UI-Integration out of the box eine großartige Basis, um komplexe UI-Anwendungsfälle zu entwickeln.“ Hector Almaguer CTO @ Blindster „Das Schöne an Algolia ist, dass ich den Ranking-Algorithmus und die Benutzeroberfläche ändern kann, ohne Unterstützung von Entwicklern zu benötigen“, sagt Cho. „Oder ich kann verschiedene Regeln implementieren. Zum Beispiel: Wenn der Nutzer YOSEM eingibt, wird Yosemite National Park immer als erstes Ergebnis angezeigt. Das sind Dinge, die ich schnell umsetzen und direkt in Aktion sehen kann.“ Sydney Cho Senior Product Manager @ AllTrails Schneller und besser bauen KI-Suche leicht gemacht. Indexieren Sie Ihre Inhalte mit unseren API-Clients oder Partnerintegrationen, optimieren Sie Ihre Rankings und starten Sie mit unseren UI-Komponenten. Alles in wenigen Minuten. Front-end Back-end Analytics Dropdown JavaScript React Android Vue Angular IOS Ruby Rails Python Django Php Symfony Laravel JavaScript java Scala Go C# Kotlin Swift Php Ruby JavaScript Python Swift Android C# Java Go Scala <div id="searchbox"></div> <div id="refinement"></div> <div id="hits"></div> <script> const { searchBox, hits } = instantsearch.widgets; search.addWidgets([ searchBox({ container: "#searchbox" }), hits({ container: "#hits" }), refinementList({ container: "#refinement", attribute: "company" }), ]); search.start(); </script> Build with JavaScript const App = () => ( <InstantSearch> <SearchBox /> <Hits /> <Pagination /> <RefinementList attribute="company" /> </InstantSearch> ); Build with React <RelativeLayout xmlns:algolia="http://schemas.android.com/apk/res-auto" xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent"> <com.algolia.instantsearch.ui.views.SearchBox android:id="@+id/search_box" android:layout_width="match_parent" android:layout_height="wrap_content"/> <com.algolia.instantsearch.ui.views.Stats android:id="@+id/search_box" android:layout_width="match_parent" android:layout_height="wrap_content"/> <com.algolia.instantsearch.ui.views.Hits android:layout_width="match_parent" android:layout_height="wrap_content" algolia:itemLayout="@layout/hits_item"/> </RelativeLayout> Build with Android <ais-instant-search> <ais-search-box /> <ais-refinement-list attribute="company" /> <ais-hits /> <ais-pagination /> </ais-instant-search> Build with Vue <ais-instantsearch> <ais-search-box></ais-search-box> <ais-refinement-list [attribute]="company" ></ais-refinement-list> <ais-hits></ais-hits> </ais-instantsearch> Build with Angular import InstantSearch override func viewDidLoad() { super.viewDidLoad() let searchBar = SearchBarWidget(frame: ...) let statsWidget = StatsLabelWidget(frame: ...) self.view.addSubview(searchBar) self.view.addSubview(statsWidget) InstantSearch.shared.registerAllWidgets(in: self.view)} Build with IOS my_index = client.init_index('contacts') my_index.save_object({ firstname: "Jimmie", lastname: "Barninger", company: "California Paint" }) Build with Ruby class Contact < ActiveRecord::Base include AlgoliaSearch algoliasearch do attribute :firstname, :lastname, :company end end Build with Rails myIndex = apiClient.init_index("contacts") myIndex.save_object({ "firstname": "Jimmie", "lastname": "Barninger", "company": "California Paint" }) Build with Python from algoliasearch_django import AlgoliaIndex from algoliasearch_django.decorators import register @register(YourModel) class YourModelIndex(AlgoliaIndex): fields = ('firstname', 'lastname', 'company') Build with Django $myIndex = $apiClient->initIndex("contacts"); $myIndex->saveObject([ "firstname" => "Jimmie", "lastname" => "Barninger", "company" => "California Paint", ]); Build with Php /** * @ORM\Entity */ class Contact { /** * @var string * * @ORM\Column(name="firstname", type="string") * @Group({searchable}) */ protected $firstname; /** * @var string * * @ORM\Column(name="lastname", type="string") * @Group({searchable}) */ protected $lastname; /** * @var string * * @ORM\Column(name="company", type="string") * @Group({searchable}) */ protected $company; } Build with Symfony use Illuminate\Database\Eloquent\Model; use Laravel\Scout\Searchable; class Contact extends Model { use Searchable; } Build with Laravel const myIndex = apiClient .initIndex('contacts'); myIndex.saveObject({ firstname: 'Jimmie', lastname: 'Barninger', company: 'California Paint', }); Build with JavaScript Index<Contact> index = client .initIndex("contacts", Contact.class); index.saveObject( new Contact() .setFirstname("Jimmie") .setLastname("Barninger") .setCompany("California Paint") ); Build with java import algolia.AlgoliaDsl._ import scala.concurrent.ExecutionContext.Implicits.global case class Contact( firstname: String, lastname: String, company: String ) val indexing: Future[Indexing] = client.execute { index into "contacts" `object` Contact( "Jimmie", "Barninger", "California Paint" ) } Build with Scala object := map[string]string{ "firstname": "Jimmie", "lastname": "Barninger", "company": "California Paint" } res, err := index.SaveObject(object) Build with Go SearchIndex index = client.InitIndex("contacts"); var contact = new Contact { FirstName = "Jimmie", LastName = "Barninger", Company = "California Paint" }; index.SaveObject(contact); Build with C# val index = client.initIndex(IndexName("contacts")) val json = json { "firstname" to "Jimmie" "lastname" to "Barninger" "company" to "California Paint" } index.saveObject(json) Build with Kotlin let myIndex = apiClient.getIndex("contacts") let n = [ "firstname": "Jimmie", "lastname": "Barninger", "company": "California Paint" ] myIndex.saveObject(n) Build with Swift Insights.register( appId: "ALGOLIA_APP_ID", apiKey: "ALGOLIA_API_KEY", userToken: "user-123456" ) Insights.shared?.clickedAfterSearch( eventName: "Product Clicked", indexName: "products", objectIDs: ["9780545139700"], positions: [7], queryID: "cba8245617aeace44" ) Build with Php insights = Algolia::Insights::Client.create('ALGOLIA_APP_ID', 'ALGOLIA_API_KEY') insights.user('user-123456').clicked_object_ids_after_search( 'Product Clicked', 'products', ['9780545139700'], [7], 'cba8245617aeace44' ) Build with Ruby // This requires installing the search-insights separate library: // https://github.com/algolia/search-insights.js // https://www.npmjs.com/package/search-insights aa('clickedObjectIDsAfterSearch', { userToken: 'user-123456', eventName: 'Product Clicked', index: 'products', queryID: 'cba8245617aeace44', objectIDs: ['9780545139700'], positions: [7], }); Build with JavaScript insights = client.init_insights_client().user('user-123456') insights.clicked_object_ids_after_search( 'Product Clicked', 'products', ['9780545139700'], [7], 'cba8245617aeace44' ) Build with Python Insights.register( appId: "ALGOLIA_APP_ID", apiKey: "ALGOLIA_API_KEY", userToken: "user-123456" ) Insights.shared?.clickedAfterSearch( eventName: "Product Clicked", indexName: "products", objectIDs: ["9780545139700"], positions: [7], queryID: "cba8245617aeace44" ) Build with Swift Insights.register( context, "ALGOLIA_APP_ID", "ALGOLIA_API_KEY", "user-123456" ) Insights.shared?.clickedAfterSearch( "Product Clicked", "products", "cba8245617aeace44", EventObjects.IDs("9780545139700"), listOf(7) ) Build with Android var insights = new InsightsClient( "ALGOLIA_APP_ID", "ALGOLIA_API_KEY" ).User("user-123456"); insights.ClickedObjectIDsAfterSearch( "Product Clicked", "products", new List<string> { "9780545139700" }, new List<uint> { 7 }, "cba8245617aeace44" ); Build with C# AsyncUserInsightsClient insights = new AsyncInsightsClient( "ALGOLIA_APP_ID", "ALGOLIA_API_KEY", client ).user("user-123456"); insights.clickedObjectIDsAfterSearch( "Product Clicked", "products", Arrays.asList("9780545139700"), new ArrayList<>(Arrays.asList(7l)), "cba8245617aeace44" ); Build with Java client := insights.NewClient( "ALGOLIA_APP_ID", "ALGOLIA_API_KEY", ).User("user-123456") res, err := client.ClickedObjectIDsAfterSearch( "Product Clicked", "products", []string{"9780545139700"}, []int{7}, "cba8245617aeace44", ) Build with Go client.execute { send event ClickedObjectIDsAfterSearch( "user-123456", "Product Clicked", "products", Seq("9780545139700"), Seq(7), "cba8245617aeace44" ) } Build with Scala Dokumentation 0 Profitieren Sie von ausführlicher Entwicklerdokumentation, um Suche und Discovery in Ihrem Ökosystem zu implementieren. Mehr erfahren Developer Hub 0 Entdecken Sie alle API-Clients, UI-Komponenten und Integrationen, um Such- und Discovery-Erlebnisse zu entwickeln. Mehr erfahren Code Exchange 0 Starten Sie schneller mit den Bausteinen von Algolia: Backend-Tools, komponierbare UI und Beispielanwendungen. Mehr erfahren Developer Discord 0 Treten Sie anderen Entwicklern bei, die auf der Algolia-Plattform aufbauen, und diskutieren Sie über die Entwicklung großartiger Sucherlebnisse. Mehr erfahren Mit Google anmelden Mit GitHub anmelden Enable anyone to build great Search & Discovery Get a demo Start Free Lösungen Überblick AI Search AI Browse AI Recommendations Ask AI Intelligent Data Kit Anwendungsfälle Überclick Enterprise Suche Headless commerce Mobile Suche Sprachgesteuerte Suche Bildersuche OEM Bildersuche Entwickler Developer Hub Dokumentation Integrationen Engineering Blog Discord community API status DocSearch Für Open Source Demos GDPR AI Act Integrationen Salesforce Commerce Cloud B2C Shopify Adobe Commerce Netlify Commercetools BigCommerce Verteilt und Sicher Globale infrastruktur Sicherheit & Konformität Azure AWS Branchen Überclick B2C-E-Commerce B2B-E-Commerce Marktplätze SaaS Medien Startups Fashion Tools Search Grader Ecommerce Search Audit Unternehmen Über Algolia Karriere Newsroom Events Leitung Soziale Wirkung Kontact Kontact Kontact Soziales netwerk Entwickler Developer Hub Dokumentation Integrationen Engineering Blog Discord community API status DocSearch Für Open Source Demos GDPR AI Act Branchen Überclick B2C-E-Commerce B2B-E-Commerce Marktplätze SaaS Medien Startups Fashion Tools Search Grader Ecommerce Search Audit Lösungen Überblick AI Search AI Browse AI Recommendations Ask AI Intelligent Data Kit Anwendungsfälle Überclick Enterprise Suche Headless commerce Mobile Suche Sprachgesteuerte Suche Bildersuche OEM Bildersuche Integrationen Salesforce Commerce Cloud B2C Shopify Adobe Commerce Netlify Commercetools BigCommerce Verteilt und Sicher Globale infrastruktur Sicherheit & Konformität Azure AWS Unternehmen Über Algolia Karriere Newsroom Events Leitung Soziale Wirkung Kontact Kontact Kontact Soziales netwerk Algolia mark white ©2026 Algolia - All rights reserved. Cookie settings Datenschutzrichtlinie Nutzungsbedingungen Richtlinien zur akzeptablen Nutzung | 2026-01-13T08:49:47 |
https://opensource.org/blog/celebrating-generosity-and-growth-in-the-osi-community#content | Celebrating Generosity and Growth in the OSI Community – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu December 12, 2025 Newsletter archive Nick Vidal Celebrating Generosity and Growth in the OSI Community Members Newsletter – December 2025 Dear OSI supporters, As we reach the final weeks of the year, I find myself reflecting on a season that invites both gratitude and giving, two values that feel especially resonant for our community. Serving as Interim Executive Director these past months has only deepened my appreciation for the people who make Open Source possible: the volunteers who share their expertise, the contributors who show up with curiosity and conviction, the board members who devote their time and energy to stewarding OSI’s mission. As for me personally, 2025 has marked my thirty years of engagement and contribution with the Open Source community, not possible without the help of many colleagues and friends made along the way in understanding how and where I might best make an impact. This month, I’m particularly grateful for the thoughtful leadership shown by OSI board members who have recently offered their insights through new blog posts. Ruth Suehle explores how we can sustain what we’ve built, Thierry Carrez warns about the fallacy of “regional Open Source,” and McCoy Smith provided an important and accessible guide to managing patent risk in Open Source projects — all pieces I encourage everyone to read if you haven’t already. These contributions exemplify the generosity that defines our community: expertise freely shared for the benefit of all. As you’ll see in the news that follows, this spirit of contribution and collaboration is reflected in the work OSI undertook globally this past month. At the Digital Public Goods Alliance Annual Members Meeting in Brasília, OSI helped lead a year-long effort culminating in a multisector discussion on data governance and public-interest AI, an essential step toward making AI systems more open, equitable, and globally accessible. We also joined OpenForum Europe and the Open Knowledge Foundation in Rio de Janeiro for the 2025 OpenForum Academy Symposium, where the announcement of the Open Technology Research Network marked a milestone in strengthening the research foundations needed for better policymaking around open technologies. OSI is proud to be part of this new partnership, which will shape an evidence-driven understanding of openness for years to come. In a season defined by giving, these accomplishments remind me that OSI’s impact is possible only because so many of you contribute what you can — your time, your expertise, your advocacy, and yes, your financial support. As we prepare for a new year filled with opportunity and challenge, I invite you to explore ways to support OSI through our new “ Get Involved ” page. Your involvement ensures that the values of transparency, inclusion, and collaboration remain at the heart of the technologies shaping our world. Thank you for being part of this vibrant and generous community. May the close of your year be restful, and may the new one bring renewed possibilities for OSI, for Open Source, and for all who rely on the freedoms it sustains. With gratitude, Deborah Bryant Interim Executive Director, OSI News from the OSI Open letter: Harnessing open source AI to advance digital sovereignty Joint letter prepared in collaboration with Mozilla and other organizations. Europe is at a crossroads. The Summit on European Digital Sovereignty marks an important milestone for the EU and its member states in aligning on a shared strategy for achieving real and lasting European digital sovereignty. As the EU pursues the goal of digital sovereignty, we urge you to harness open source — that is, technology that is free to use, inspect, adapt, and share — as a key enabler of this strategy. OSI Board articles Patents and Open Source: Understanding the Risks and Available Solutions (McCoy Smith) Open Source: A global commons to enable digital sovereignty (Thierry Carrez) Sustaining Open Source: The Next 25 Years Depend on What We Do Together Now (Ruth Suehle) Event updates Open Source Without Borders: Reflections from COSCon’25 DPGA’s Annual Members Meeting: Advancing Open Source & DPGs for the Public Good OFA Symposium 2025 and the Launch of the Open Technology Research Network (OTRN) Other news OSI in the news DHH & Open Source (Matt Mullenweg) ‘Source available’ is not open source (and that’s okay) (Dries Buytaert) Read all press mentions from this past month News from OSI affiliates and partners Apereo: Open Source in Higher Ed: Early Findings from Apereo’s OSSHE Study — and How You Can Get Involved APELL : Declaration of Digital Independence ASF : Celebrating 10,000 Committers: The People Who Power Apache Software Projects DPGA : Reflections from the 2025 Annual Members Meeting in Brasília Drupal Association : DrupalCon Vienna 2025: A Celebration of Open Source and Community Impact Eclipse Foundation : 2025 Open Source Congress Report Eclipse Foundation : Understanding Open Source Stewards and the Cyber Resilience Act Free Software Foundation : Hundreds of free software supporters tuned in for FSF40 hackathon Joomla (Open Source Matters) : Joomla Now Officially Recognized as a Digital Public Good Let’s Encrypt : 10 Years of Let’s Encrypt Certificates Linux Foundation : Collective Wisdom: Why the Future of AI Must Be Built in the Open Linux Foundation : Revealing the Hidden Economics of Open Models in the AI Era Mozilla Foundation : Open letter: Harnessing open source AI to advance digital sovereignty Mozilla Foundation : Rewiring Mozilla: Doing for AI what we did for the web OpenForum Europe : OpenForum Europe, Open Source Initiative, and Open Knowledge Foundation Announce Strategic Partnership to Advance Open Technology Research Open Future : Digital Commons on the EU’s Digital Sovereignty Agenda OpenSSF : Recap: Open Source Security Week in Belgium – Highlights from Ghent to Brussels Open Source Group Japan : Public Proposal for Building an Open AI Society and Digital Sovereignty Based on Open Source AI Python Software Foundation : Sovereign Tech Agency and PSF Security Partnership WordPress Foundation : State of the Word 2025: Innovation Shaped by Community Surveys Vertical Standards for the CRA As the deadline for the application of the CRA draws closer, the OSI is happy to announce the beginning of an Open consultation on many of the vertical standards. 2026 State of Open Source Survey Perforce OpenLogic and Zend, in collaboration with OSI and Eclipse Foundation, is seeking responses from OSS users to gather data for the next State of Open Source Report . Events Upcoming events FOSDEM (January 31 – February 1 – Brussels) SCALE (March 5-8 – Pasadena) All Things AI (March 23-24 – Durham) OCX (April 21-23 – Brussels) Thanks to our sponsors New sponsors and renewals Google Cisco Block See all sponsors Interested in sponsoring, or partnering with, the OSI? Please see our Sponsorship Prospectus and our Annual Report . Please contact the OSI to find out more about how your company can promote open source development, communities and software. Support OSI by becoming a full member Hundreds of individuals and organizations worldwide join as members and support as donors or sponsors of the OSI. They trust in our neutral stewardship of open source licensing and our role in enabling a global community. Get involved! Open Source Without Borders: Reflections from COSCon’25 Top Open Source licenses in 2025 Keep up with Open Source Please leave this field empty. Δ We’ll never share your details and you can unsubscribe with a click! Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://docs.python.org/3/whatsnew/3.14.html#pep-758-allow-except-and-except-expressions-without-brackets | What’s new in Python 3.14 — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents What’s new in Python 3.14 Summary – Release highlights New features PEP 649 & PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template string literals PEP 768 : Safe external debugger interface A new type of interpreter Free-threaded mode improvements Improved error messages PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Other language changes Built-ins Command line and environment PEP 758: Allow except and except* expressions without brackets PEP 765: Control flow in finally blocks Incremental garbage collection Default interactive shell New modules Improved modules argparse ast asyncio calendar concurrent.futures configparser contextvars ctypes curses datetime decimal difflib dis errno faulthandler fnmatch fractions functools getopt getpass graphlib heapq hmac http imaplib inspect io json linecache logging.handlers math mimetypes multiprocessing operator os os.path pathlib pdb pickle platform pydoc re socket ssl struct symtable sys sys.monitoring sysconfig tarfile threading tkinter turtle types typing unicodedata unittest urllib uuid webbrowser zipfile Optimizations asyncio base64 bdb difflib gc io pathlib pdb textwrap uuid zlib Removed argparse ast asyncio email importlib.abc itertools pathlib pkgutil pty sqlite3 urllib Deprecated New deprecations Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.17 Pending removal in Python 3.18 Pending removal in Python 3.19 Pending removal in future versions CPython bytecode changes Pseudo-instructions C API changes Python configuration C API New features in the C API Limited C API changes Removed C APIs Deprecated C APIs Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.18 Pending removal in future versions Build changes build-details.json Discontinuation of PGP signatures Free-threaded Python is officially supported Binary releases for the experimental just-in-time compiler Porting to Python 3.14 Changes in the Python API Changes in annotations ( PEP 649 and PEP 749 ) Implications for annotated code Implications for readers of __annotations__ Related changes from __future__ import annotations Changes in the C API Notable changes in 3.14.1 Previous topic What’s New in Python Next topic What’s New In Python 3.13 This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » What’s New in Python » What’s new in Python 3.14 | Theme Auto Light Dark | What’s new in Python 3.14 ¶ Editors : Adam Turner and Hugo van Kemenade This article explains the new features in Python 3.14, compared to 3.13. Python 3.14 was released on 7 October 2025. For full details, see the changelog . See also PEP 745 – Python 3.14 release schedule Summary – Release highlights ¶ Python 3.14 is the latest stable release of the Python programming language, with a mix of changes to the language, the implementation, and the standard library. The biggest changes include template string literals , deferred evaluation of annotations , and support for subinterpreters in the standard library. The library changes include significantly improved capabilities for introspection in asyncio , support for Zstandard via a new compression.zstd module, syntax highlighting in the REPL, as well as the usual deprecations and removals, and improvements in user-friendliness and correctness. This article doesn’t attempt to provide a complete specification of all new features, but instead gives a convenient overview. For full details refer to the documentation, such as the Library Reference and Language Reference . To understand the complete implementation and design rationale for a change, refer to the PEP for a particular new feature; but note that PEPs usually are not kept up-to-date once a feature has been fully implemented. See Porting to Python 3.14 for guidance on upgrading from earlier versions of Python. Interpreter improvements: PEP 649 and PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template strings PEP 758 : Allow except and except* expressions without brackets PEP 765 : Control flow in finally blocks PEP 768 : Safe external debugger interface for CPython A new type of interpreter Free-threaded mode improvements Improved error messages Incremental garbage collection Significant improvements in the standard library: PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Syntax highlighting in the default interactive shell , and color output in several standard library CLIs C API improvements: PEP 741 : Python configuration C API Platform support: PEP 776 : Emscripten is now an officially supported platform , at tier 3 . Release changes: PEP 779 : Free-threaded Python is officially supported PEP 761 : PGP signatures have been discontinued for official releases Windows and macOS binary releases now support the experimental just-in-time compiler Binary releases for Android are now provided New features ¶ PEP 649 & PEP 749 : Deferred evaluation of annotations ¶ The annotations on functions, classes, and modules are no longer evaluated eagerly. Instead, annotations are stored in special-purpose annotate functions and evaluated only when necessary (except if from __future__ import annotations is used). This change is designed to improve performance and usability of annotations in Python in most circumstances. The runtime cost for defining annotations is minimized, but it remains possible to introspect annotations at runtime. It is no longer necessary to enclose annotations in strings if they contain forward references. The new annotationlib module provides tools for inspecting deferred annotations. Annotations may be evaluated in the VALUE format (which evaluates annotations to runtime values, similar to the behavior in earlier Python versions), the FORWARDREF format (which replaces undefined names with special markers), and the STRING format (which returns annotations as strings). This example shows how these formats behave: >>> from annotationlib import get_annotations , Format >>> def func ( arg : Undefined ): ... pass >>> get_annotations ( func , format = Format . VALUE ) Traceback (most recent call last): ... NameError : name 'Undefined' is not defined >>> get_annotations ( func , format = Format . FORWARDREF ) {'arg': ForwardRef('Undefined', owner=<function func at 0x...>)} >>> get_annotations ( func , format = Format . STRING ) {'arg': 'Undefined'} The porting section contains guidance on changes that may be needed due to these changes, though in the majority of cases, code will continue working as-is. (Contributed by Jelle Zijlstra in PEP 749 and gh-119180 ; PEP 649 was written by Larry Hastings.) See also PEP 649 Deferred Evaluation Of Annotations Using Descriptors PEP 749 Implementing PEP 649 PEP 734 : Multiple interpreters in the standard library ¶ The CPython runtime supports running multiple copies of Python in the same process simultaneously and has done so for over 20 years. Each of these separate copies is called an ‘interpreter’. However, the feature had been available only through the C-API . That limitation is removed in Python 3.14, with the new concurrent.interpreters module. There are at least two notable reasons why using multiple interpreters has significant benefits: they support a new (to Python), human-friendly concurrency model true multi-core parallelism For some use cases, concurrency in software improves efficiency and can simplify design, at a high level. At the same time, implementing and maintaining all but the simplest concurrency is often a struggle for the human brain. That especially applies to plain threads (for example, threading ), where all memory is shared between all threads. With multiple isolated interpreters, you can take advantage of a class of concurrency models, like Communicating Sequential Processes (CSP) or the actor model, that have found success in other programming languages, like Smalltalk, Erlang, Haskell, and Go. Think of multiple interpreters as threads but with opt-in sharing. Regarding multi-core parallelism: as of Python 3.12, interpreters are now sufficiently isolated from one another to be used in parallel (see PEP 684 ). This unlocks a variety of CPU-intensive use cases for Python that were limited by the GIL . Using multiple interpreters is similar in many ways to multiprocessing , in that they both provide isolated logical “processes” that can run in parallel, with no sharing by default. However, when using multiple interpreters, an application will use fewer system resources and will operate more efficiently (since it stays within the same process). Think of multiple interpreters as having the isolation of processes with the efficiency of threads. While the feature has been around for decades, multiple interpreters have not been used widely, due to low awareness and the lack of a standard library module. Consequently, they currently have several notable limitations, which are expected to improve significantly now that the feature is going mainstream. Current limitations: starting each interpreter has not been optimized yet each interpreter uses more memory than necessary (work continues on extensive internal sharing between interpreters) there aren’t many options yet for truly sharing objects or other data between interpreters (other than memoryview ) many third-party extension modules on PyPI are not yet compatible with multiple interpreters (all standard library extension modules are compatible) the approach to writing applications that use multiple isolated interpreters is mostly unfamiliar to Python users, for now The impact of these limitations will depend on future CPython improvements, how interpreters are used, and what the community solves through PyPI packages. Depending on the use case, the limitations may not have much impact, so try it out! Furthermore, future CPython releases will reduce or eliminate overhead and provide utilities that are less appropriate on PyPI. In the meantime, most of the limitations can also be addressed through extension modules, meaning PyPI packages can fill any gap for 3.14, and even back to 3.12 where interpreters were finally properly isolated and stopped sharing the GIL . Likewise, libraries on PyPI are expected to emerge for high-level abstractions on top of interpreters. Regarding extension modules, work is in progress to update some PyPI projects, as well as tools like Cython, pybind11, nanobind, and PyO3. The steps for isolating an extension module are found at Isolating Extension Modules . Isolating a module has a lot of overlap with what is required to support free-threading , so the ongoing work in the community in that area will help accelerate support for multiple interpreters. Also added in 3.14: concurrent.futures.InterpreterPoolExecutor . (Contributed by Eric Snow in gh-134939 .) See also PEP 734 PEP 750 : Template string literals ¶ Template strings are a new mechanism for custom string processing. They share the familiar syntax of f-strings but, unlike f-strings, return an object representing the static and interpolated parts of the string, instead of a simple str . To write a t-string, use a 't' prefix instead of an 'f' : >>> variety = 'Stilton' >>> template = t 'Try some {variety} cheese!' >>> type ( template ) <class 'string.templatelib.Template'> Template objects provide access to the static and interpolated (in curly braces) parts of a string before they are combined. Iterate over Template instances to access their parts in order: >>> list ( template ) ['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!'] It’s easy to write (or call) code to process Template instances. For example, here’s a function that renders static parts lowercase and Interpolation instances uppercase: from string.templatelib import Interpolation def lower_upper ( template ): """Render static parts lowercase and interpolations uppercase.""" parts = [] for part in template : if isinstance ( part , Interpolation ): parts . append ( str ( part . value ) . upper ()) else : parts . append ( part . lower ()) return '' . join ( parts ) name = 'Wenslydale' template = t 'Mister {name} ' assert lower_upper ( template ) == 'mister WENSLYDALE' Because Template instances distinguish between static strings and interpolations at runtime, they can be useful for sanitising user input. Writing a html() function that escapes user input in HTML is an exercise left to the reader! Template processing code can provide improved flexibility. For instance, a more advanced html() function could accept a dict of HTML attributes directly in the template: attributes = { 'src' : 'limburger.jpg' , 'alt' : 'lovely cheese' } template = t '<img {attributes} >' assert html ( template ) == '<img src="limburger.jpg" alt="lovely cheese" />' Of course, template processing code does not need to return a string-like result. An even more advanced html() could return a custom type representing a DOM-like structure. With t-strings in place, developers can write systems that sanitise SQL, make safe shell operations, improve logging, tackle modern ideas in web development (HTML, CSS, and so on), and implement lightweight custom business DSLs. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) See also PEP 750 . PEP 768 : Safe external debugger interface ¶ Python 3.14 introduces a zero-overhead debugging interface that allows debuggers and profilers to safely attach to running Python processes without stopping or restarting them. This is a significant enhancement to Python’s debugging capabilities, meaning that unsafe alternatives are no longer required. The new interface provides safe execution points for attaching debugger code without modifying the interpreter’s normal execution path or adding any overhead at runtime. Due to this, tools can now inspect and interact with Python applications in real-time, which is a crucial capability for high-availability systems and production environments. For convenience, this interface is implemented in the sys.remote_exec() function. For example: import sys from tempfile import NamedTemporaryFile with NamedTemporaryFile ( mode = 'w' , suffix = '.py' , delete = False ) as f : script_path = f . name f . write ( f 'import my_debugger; my_debugger.connect( { os . getpid () } )' ) # Execute in process with PID 1234 print ( 'Behold! An offering:' ) sys . remote_exec ( 1234 , script_path ) This function allows sending Python code to be executed in a target process at the next safe execution point. However, tool authors can also implement the protocol directly as described in the PEP, which details the underlying mechanisms used to safely attach to running processes. The debugging interface has been carefully designed with security in mind and includes several mechanisms to control access: A PYTHON_DISABLE_REMOTE_DEBUG environment variable. A -X disable-remote-debug command-line option. A --without-remote-debug configure flag to completely disable the feature at build time. (Contributed by Pablo Galindo Salgado, Matt Wozniski, and Ivona Stojanovic in gh-131591 .) See also PEP 768 . A new type of interpreter ¶ A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individual Python opcodes, rather than one large C case statement. For certain newer compilers, this interpreter provides significantly better performance. Preliminary benchmarks suggest a geometric mean of 3-5% faster on the standard pyperformance benchmark suite, depending on platform and architecture. The baseline is Python 3.14 built with Clang 19, without this new interpreter. This interpreter currently only works with Clang 19 and newer on x86-64 and AArch64 architectures. However, a future release of GCC is expected to support this as well. This feature is opt-in for now. Enabling profile-guided optimization is highly recommendeded when using the new interpreter as it is the only configuration that has been tested and validated for improved performance. For further information, see --with-tail-call-interp . Note This is not to be confused with tail call optimization of Python functions, which is currently not implemented in CPython. This new interpreter type is an internal implementation detail of the CPython interpreter. It doesn’t change the visible behavior of Python programs at all. It can improve their performance, but doesn’t change anything else. (Contributed by Ken Jin in gh-128563 , with ideas on how to implement this in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.) Free-threaded mode improvements ¶ CPython’s free-threaded mode ( PEP 703 ), initially added in 3.13, has been significantly improved in Python 3.14. The implementation described in PEP 703 has been finished, including C API changes, and temporary workarounds in the interpreter were replaced with more permanent solutions. The specializing adaptive interpreter ( PEP 659 ) is now enabled in free-threaded mode, which along with many other optimizations greatly improves its performance. The performance penalty on single-threaded code in free-threaded mode is now roughly 5-10%, depending on the platform and C compiler used. From Python 3.14, when compiling extension modules for the free-threaded build of CPython on Windows, the preprocessor variable Py_GIL_DISABLED now needs to be specified by the build backend, as it will no longer be determined automatically by the C compiler. For a running interpreter, the setting that was used at compile time can be found using sysconfig.get_config_var() . The new -X context_aware_warnings flag controls if concurrent safe warnings control is enabled. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. A new thread_inherit_context flag has been added, which if enabled means that threads created with threading.Thread start with a copy of the Context() of the caller of start() . Most significantly, this makes the warning filtering context established by catch_warnings be “inherited” by threads (or asyncio tasks) started within that context. It also affects other modules that use context variables, such as the decimal context manager. This flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Sam Gross, Matt Page, Neil Schemenauer, Thomas Wouters, Donghee Na, Kirill Podoprigora, Ken Jin, Itamar Oren, Brett Simmers, Dino Viehland, Nathan Goldbaum, Ralf Gommers, Lysandros Nikolaou, Kumar Aditya, Edgar Margffoy, and many others. Some of these contributors are employed by Meta, which has continued to provide significant engineering resources to support this project.) Improved error messages ¶ The interpreter now provides helpful suggestions when it detects typos in Python keywords. When a word that closely resembles a Python keyword is encountered, the interpreter will suggest the correct keyword in the error message. This feature helps programmers quickly identify and fix common typing mistakes. For example: >>> whille True : ... pass Traceback (most recent call last): File "<stdin>" , line 1 whille True : ^^^^^^ SyntaxError : invalid syntax. Did you mean 'while'? While the feature focuses on the most common cases, some variations of misspellings may still result in regular syntax errors. (Contributed by Pablo Galindo in gh-132449 .) elif statements that follow an else block now have a specific error message. (Contributed by Steele Farnsworth in gh-129902 .) >>> if who == "me" : ... print ( "It's me!" ) ... else : ... print ( "It's not me!" ) ... elif who is None : ... print ( "Who is it?" ) File "<stdin>", line 5 elif who is None: ^^^^ SyntaxError: 'elif' block follows an 'else' block If a statement is passed to the Conditional expressions after else , or one of pass , break , or continue is passed before if , then the error message highlights where the expression is required. (Contributed by Sergey Miryanov in gh-129515 .) >>> x = 1 if True else pass Traceback (most recent call last): File "<string>" , line 1 x = 1 if True else pass ^^^^ SyntaxError : expected expression after 'else', but statement is given >>> x = continue if True else break Traceback (most recent call last): File "<string>" , line 1 x = continue if True else break ^^^^^^^^ SyntaxError : expected expression before 'if', but statement is given When incorrectly closed strings are detected, the error message suggests that the string may be intended to be part of the string. (Contributed by Pablo Galindo in gh-88535 .) >>> "The interesting object " The important object " is very important" Traceback (most recent call last): SyntaxError : invalid syntax. Is this intended to be part of the string? When strings have incompatible prefixes, the error now shows which prefixes are incompatible. (Contributed by Nikita Sobolev in gh-133197 .) >>> ub 'abc' File "<python-input-0>" , line 1 ub 'abc' ^^ SyntaxError : 'u' and 'b' prefixes are incompatible Improved error messages when using as with incompatible targets in: Imports: import ... as ... From imports: from ... import ... as ... Except handlers: except ... as ... Pattern-match cases: case ... as ... (Contributed by Nikita Sobolev in gh-123539 , gh-123562 , and gh-123440 .) Improved error message when trying to add an instance of an unhashable type to a dict or set . (Contributed by CF Bolz-Tereick and Victor Stinner in gh-132828 .) >>> s = set () >>> s . add ({ 'pages' : 12 , 'grade' : 'A' }) Traceback (most recent call last): File "<python-input-1>" , line 1 , in <module> s . add ({ 'pages' : 12 , 'grade' : 'A' }) ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError : cannot use 'dict' as a set element (unhashable type: 'dict') >>> d = {} >>> l = [ 1 , 2 , 3 ] >>> d [ l ] = 12 Traceback (most recent call last): File "<python-input-4>" , line 1 , in <module> d [ l ] = 12 ~^^^ TypeError : cannot use 'list' as a dict key (unhashable type: 'list') Improved error message when an object supporting the synchronous context manager protocol is entered using async with instead of with , and vice versa for the asynchronous context manager protocol. (Contributed by Bénédikt Tran in gh-128398 .) PEP 784 : Zstandard support in the standard library ¶ The new compression package contains modules compression.lzma , compression.bz2 , compression.gzip and compression.zlib which re-export the lzma , bz2 , gzip and zlib modules respectively. The new import names under compression are the preferred names for importing these compression modules from Python 3.14. However, the existing modules names have not been deprecated. Any deprecation or removal of the existing compression modules will occur no sooner than five years after the release of 3.14. The new compression.zstd module provides compression and decompression APIs for the Zstandard format via bindings to Meta’s zstd library . Zstandard is a widely adopted, highly efficient, and fast compression format. In addition to the APIs introduced in compression.zstd , support for reading and writing Zstandard compressed archives has been added to the tarfile , zipfile , and shutil modules. Here’s an example of using the new module to compress some data: from compression import zstd import math data = str ( math . pi ) . encode () * 20 compressed = zstd . compress ( data ) ratio = len ( compressed ) / len ( data ) print ( f "Achieved compression ratio of { ratio } " ) As can be seen, the API is similar to the APIs of the lzma and bz2 modules. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) See also PEP 784 . Asyncio introspection capabilities ¶ Added a new command-line interface to inspect running Python processes using asynchronous tasks, available via python -m asyncio ps PID or python -m asyncio pstree PID . The ps subcommand inspects the given process ID (PID) and displays information about currently running asyncio tasks. It outputs a task table: a flat listing of all tasks, their names, their coroutine stacks, and which tasks are awaiting them. The pstree subcommand fetches the same information, but instead renders a visual async call tree, showing coroutine relationships in a hierarchical format. This command is particularly useful for debugging long-running or stuck asynchronous programs. It can help developers quickly identify where a program is blocked, what tasks are pending, and how coroutines are chained together. For example given this code: import asyncio async def play_track ( track ): await asyncio . sleep ( 5 ) print ( f '🎵 Finished: { track } ' ) async def play_album ( name , tracks ): async with asyncio . TaskGroup () as tg : for track in tracks : tg . create_task ( play_track ( track ), name = track ) async def main (): async with asyncio . TaskGroup () as tg : tg . create_task ( play_album ( 'Sundowning' , [ 'TNDNBTG' , 'Levitate' ]), name = 'Sundowning' ) tg . create_task ( play_album ( 'TMBTE' , [ 'DYWTYLM' , 'Aqua Regia' ]), name = 'TMBTE' ) if __name__ == '__main__' : asyncio . run ( main ()) Executing the new tool on the running process will yield a table like this: python -m asyncio ps 12345 tid task id task name coroutine stack awaiter chain awaiter name awaiter id ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1935500 0x7fc930c18050 Task-1 TaskGroup._aexit -> TaskGroup.__aexit__ -> main 0x0 1935500 0x7fc930c18230 Sundowning TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fa50 TMBTE TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fdf0 TNDNBTG sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32510 Levitate sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32890 DYWTYLM sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 1935500 0x7fc93161ec30 Aqua Regia sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 or a tree like this: python -m asyncio pstree 12345 └── ( T ) Task-1 └── main example.py:13 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) Sundowning │ └── album example.py:8 │ └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 │ └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 │ ├── ( T ) TNDNBTG │ │ └── play example.py:4 │ │ └── sleep Lib/asyncio/tasks.py:702 │ └── ( T ) Levitate │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) TMBTE └── album example.py:8 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) DYWTYLM │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) Aqua Regia └── play example.py:4 └── sleep Lib/asyncio/tasks.py:702 If a cycle is detected in the async await graph (which could indicate a programming issue), the tool raises an error and lists the cycle paths that prevent tree construction: python -m asyncio pstree 12345 ERROR: await-graph contains cycles - cannot print a tree! cycle: Task-2 → Task-3 → Task-2 (Contributed by Pablo Galindo, Łukasz Langa, Yury Selivanov, and Marta Gomez Macias in gh-91048 .) Concurrent safe warnings control ¶ The warnings.catch_warnings context manager will now optionally use a context variable for warning filters. This is enabled by setting the context_aware_warnings flag, either with the -X command-line option or an environment variable. This gives predictable warnings control when using catch_warnings combined with multiple threads or asynchronous tasks. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Neil Schemenauer and Kumar Aditya in gh-130010 .) Other language changes ¶ All Windows code pages are now supported as ‘cpXXX’ codecs on Windows. (Contributed by Serhiy Storchaka in gh-123803 .) Implement mixed-mode arithmetic rules combining real and complex numbers as specified by the C standard since C99. (Contributed by Sergey B Kirpichev in gh-69639 .) More syntax errors are now detected regardless of optimisation and the -O command-line option. This includes writes to __debug__ , incorrect use of await , and asynchronous comprehensions outside asynchronous functions. For example, python -O -c 'assert (__debug__ := 1)' or python -O -c 'assert await 1' now produce SyntaxError s. (Contributed by Irit Katriel and Jelle Zijlstra in gh-122245 & gh-121637 .) When subclassing a pure C type, the C slots for the new type are no longer replaced with a wrapped version on class creation if they are not explicitly overridden in the subclass. (Contributed by Tomasz Pytel in gh-132284 .) Built-ins ¶ The bytes.fromhex() and bytearray.fromhex() methods now accept ASCII bytes and bytes-like objects . (Contributed by Daniel Pope in gh-129349 .) Add class methods float.from_number() and complex.from_number() to convert a number to float or complex type correspondingly. They raise a TypeError if the argument is not a real number. (Contributed by Serhiy Storchaka in gh-84978 .) Support underscore and comma as thousands separators in the fractional part for floating-point presentation types of the new-style string formatting (with format() or f-strings ). (Contributed by Sergey B Kirpichev in gh-87790 .) The int() function no longer delegates to __trunc__() . Classes that want to support conversion to int() must implement either __int__() or __index__() . (Contributed by Mark Dickinson in gh-119743 .) The map() function now has an optional keyword-only strict flag like zip() to check that all the iterables are of equal length. (Contributed by Wannes Boeykens in gh-119793 .) The memoryview type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-126012 .) Using NotImplemented in a boolean context will now raise a TypeError . This has raised a DeprecationWarning since Python 3.9. (Contributed by Jelle Zijlstra in gh-118767 .) Three-argument pow() now tries calling __rpow__() if necessary. Previously it was only called in two-argument pow() and the binary power operator. (Contributed by Serhiy Storchaka in gh-130104 .) super objects are now copyable and pickleable . (Contributed by Serhiy Storchaka in gh-125767 .) Command line and environment ¶ The import time flag can now track modules that are already loaded (‘cached’), via the new -X importtime=2 . When such a module is imported, the self and cumulative times are replaced by the string cached . Values above 2 for -X importtime are now reserved for future use. (Contributed by Noah Kim and Adam Turner in gh-118655 .) The command-line option -c now automatically dedents its code argument before execution. The auto-dedentation behavior mirrors textwrap.dedent() . (Contributed by Jon Crall and Steven Sun in gh-103998 .) -J is no longer a reserved flag for Jython , and now has no special meaning. (Contributed by Adam Turner in gh-133336 .) PEP 758: Allow except and except* expressions without brackets ¶ The except and except* expressions now allow brackets to be omitted when there are multiple exception types and the as clause is not used. For example: try : connect_to_server () except TimeoutError , ConnectionRefusedError : print ( 'The network has ceased to be!' ) (Contributed by Pablo Galindo and Brett Cannon in PEP 758 and gh-131831 .) PEP 765: Control flow in finally blocks ¶ The compiler now emits a SyntaxWarning when a return , break , or continue statement have the effect of leaving a finally block. This change is specified in PEP 765 . In situations where this change is inconvenient (such as those where the warnings are redundant due to code linting), the warning filter can be used to turn off all syntax warnings by adding ignore::SyntaxWarning as a filter. This can be specified in combination with a filter that converts other warnings to errors (for example, passing -Werror -Wignore::SyntaxWarning as CLI options, or setting PYTHONWARNINGS=error,ignore::SyntaxWarning ). Note that applying such a filter at runtime using the warnings module will only suppress the warning in code that is compiled after the filter is adjusted. Code that is compiled prior to the filter adjustment (for example, when a module is imported) will still emit the syntax warning. (Contributed by Irit Katriel in gh-130080 .) Incremental garbage collection ¶ The cycle garbage collector is now incremental. This means that maximum pause times are reduced by an order of magnitude or more for larger heaps. There are now only two generations: young and old. When gc.collect() is not called directly, the GC is invoked a little less frequently. When invoked, it collects the young generation and an increment of the old generation, instead of collecting one or more generations. The behavior of gc.collect() changes slightly: gc.collect(1) : Performs an increment of garbage collection, rather than collecting generation 1. Other calls to gc.collect() are unchanged. (Contributed by Mark Shannon in gh-108362 .) Default interactive shell ¶ The default interactive shell now highlights Python syntax. The feature is enabled by default, save if PYTHON_BASIC_REPL or any other environment variable that disables colour is set. See Controlling color for details. The default color theme for syntax highlighting strives for good contrast and exclusively uses the 4-bit VGA standard ANSI color codes for maximum compatibility. The theme can be customized using an experimental API _colorize.set_theme() . This can be called interactively or in the PYTHONSTARTUP script. Note that this function has no stability guarantees, and may change or be removed. (Contributed by Łukasz Langa in gh-131507 .) The default interactive shell now supports import auto-completion. This means that typing import co and pressing <Tab> will suggest modules starting with co . Similarly, typing from concurrent import i will suggest submodules of concurrent starting with i . Note that autocompletion of module attributes is not currently supported. (Contributed by Tomas Roun in gh-69605 .) New modules ¶ annotationlib : For introspecting annotations . See PEP 749 for more details. (Contributed by Jelle Zijlstra in gh-119180 .) compression (including compression.zstd ): A package for compression-related modules, including a new module to support the Zstandard compression format. See PEP 784 for more details. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) concurrent.interpreters : Support for multiple interpreters in the standard library. See PEP 734 for more details. (Contributed by Eric Snow in gh-134939 .) string.templatelib : Support for template string literals (t-strings). See PEP 750 for more details. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) Improved modules ¶ argparse ¶ The default value of the program name for argparse.ArgumentParser now reflects the way the Python interpreter was instructed to find the __main__ module code. (Contributed by Serhiy Storchaka and Alyssa Coghlan in gh-66436 .) Introduced the optional suggest_on_error parameter to argparse.ArgumentParser , enabling suggestions for argument choices and subparser names if mistyped by the user. (Contributed by Savannah Ostrowski in gh-124456 .) Enable color for help text, which can be disabled with the optional color parameter to argparse.ArgumentParser . This can also be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-130645 .) ast ¶ Add compare() , a function for comparing two ASTs. (Contributed by Batuhan Taskaya and Jeremy Hylton in gh-60191 .) Add support for copy.replace() for AST nodes. (Contributed by Bénédikt Tran in gh-121141 .) Docstrings are now removed from an optimized AST in optimization level 2. (Contributed by Irit Katriel in gh-123958 .) The repr() output for AST nodes now includes more information. (Contributed by Tomas Roun in gh-116022 .) When called with an AST as input, the parse() function now always verifies that the root node type is appropriate. (Contributed by Irit Katriel in gh-130139 .) Add new options to the command-line interface: --feature-version , --optimize , and --show-empty . (Contributed by Semyon Moroz in gh-133367 .) asyncio ¶ The function and methods named create_task() now take an arbitrary list of keyword arguments. All keyword arguments are passed to the Task constructor or the custom task factory. (See set_task_factory() for details.) The name and context keyword arguments are no longer special; the name should now be set using the name keyword argument of the factory, and context may be None . This affects the following function and methods: asyncio.create_task() , asyncio.loop.create_task() , asyncio.TaskGroup.create_task() . (Contributed by Thomas Grainger in gh-128307 .) There are two new utility functions for introspecting and printing a program’s call graph: capture_call_graph() and print_call_graph() . See Asyncio introspection capabilities for more details. (Contributed by Yury Selivanov, Pablo Galindo Salgado, and Łukasz Langa in gh-91048 .) calendar ¶ By default, today’s date is highlighted in color in calendar ’s command-line text output. This can be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-128317 .) concurrent.futures ¶ Add a new executor class, InterpreterPoolExecutor , which exposes multiple Python interpreters in the same process (‘subinterpreters’) to Python code. This uses a pool of independent Python interpreters to execute calls asynchronously. This is separate from the new interpreters module introduced by PEP 734 . (Contributed by Eric Snow in gh-124548 .) On Unix platforms other than macOS, ‘forkserver’ is now the default start method for ProcessPoolExecutor (replacing ‘fork’ ). This change does not affect Windows or macOS, where ‘spawn’ remains the default start method. If the threading incompatible fork method is required, you must explicitly request it by supplying a multiprocessing context mp_context to ProcessPoolExecutor . See forkserver restrictions for information and differences with the fork method and how this change may affect existing code with mutable global shared variables and/or shared objects that can not be automatically pickled . (Contributed by Gregory P. Smith in gh-84559 .) Add two new methods to ProcessPoolExecutor , terminate_workers() and kill_workers() , as ways to terminate or kill all living worker processes in the given pool. (Contributed by Charles Machalow in gh-130849 .) Add the optional buffersize parameter to Executor.map to limit the number of submitted tasks whose results have not yet been yielded. If the buffer is full, iteration over the iterables pauses until a result is yielded from the buffer. (Contributed by Enzo Bonnal and Josh Rosenberg in gh-74028 .) configparser ¶ configparser will no longer write config files it cannot read, to improve security. Attempting to write() keys containing delimiters or beginning with the section header pattern will raise an InvalidWriteError . (Contributed by Jacob Lincoln in gh-129270 .) contextvars ¶ Support the context manager protocol for Token objects. (Contributed by Andrew Svetlov in gh-129889 .) ctypes ¶ The layout of bit fields in Structure and Union objects is now a closer match to platform defaults (GCC/Clang or MSVC). In particular, fields no longer overlap. (Contributed by Matthias Görgens in gh-97702 .) The Structure._layout_ class attribute can now be set to help match a non-default ABI. (Contributed by Petr Viktorin in gh-97702 .) The class of Structure / Union field descriptors is now available as CField , and has new attributes to aid debugging and introspection. (Contributed by Petr Viktorin in gh-128715 .) On Windows, the COMError exception is now public. (Contributed by Jun Komoda in gh-126686 .) On Windows, the CopyComPointer() function is now public. (Contributed by Jun Komoda in gh-127275 .) Add memoryview_at() , a function to create a memoryview object that refers to the supplied pointer and length. This works like ctypes.string_at() except it avoids a buffer copy, and is typically useful when implementing pure Python callback functions that are passed dynamically-sized buffers. (Contributed by Rian Hunter in gh-112018 .) Complex types, c_float_complex , c_double_complex , and c_longdouble_complex , are now available if both the compiler and the libffi library support complex C types. (Contributed by Sergey B Kirpichev in gh-61103 .) Add ctypes.util.dllist() for listing the shared libraries loaded by the current process. (Contributed by Brian Ward in gh-119349 .) Move ctypes.POINTER() types cache from a global internal cache ( _pointer_type_cache ) to the _CData.__pointer_type__ attribute of the corresponding ctypes types. This will stop the cache from growing without limits in some situations. (Contributed by Sergey Miryanov in gh-100926 .) The py_object type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-132168 .) ctypes now supports free-threading builds . (Contributed by Kumar Aditya and Peter Bierma in gh-127945 .) curses ¶ Add the assume_default_colors() function, a refinement of the use_default_colors() function which allows changing the color pair 0 . (Contributed by Serhiy Storchaka in gh-133139 .) datetime ¶ Add the strptime() method to the datetime.date and datetime.time classes. (Contributed by Wannes Boeykens in gh-41431 .) decimal ¶ Add Decimal.from_number() as an alternative constructor for Decimal . (Contributed by Serhiy Storchaka in gh-121798 .) Expose IEEEContext() to support creation of contexts corresponding to the IEEE 754 (2008) decimal interchange formats. (Contributed by Sergey B Kirpichev in gh-53032 .) difflib ¶ Comparison pages with highlighted changes generated by the HtmlDiff class now support ‘dark mode’. (Contributed by Jiahao Li in gh-129939 .) dis ¶ Add support for rendering full source location information of instructions , rather than only the line number. This feature is added to the following interfaces via the show_positions keyword argument: dis.Bytecode dis.dis() dis.distb() dis.disassemble() This feature is also exposed via dis --show-positions . (Contributed by Bénédikt Tran in gh-123165 .) Add the dis --specialized command-line option to show specialized bytecode. (Contributed by Bénédikt Tran in gh-127413 .) errno ¶ Add the EHWPOISON error code constant. (Contributed by James Roy in gh-126585 .) faulthandler ¶ Add support for printing the C stack trace on systems that support it via the new dump_c_stack() function or via the c_stack argument in faulthandler.enable() . (Contributed by Peter Bierma in gh-127604 .) fnmatch ¶ Add filterfalse() , a function to reject names matching a given pattern. (Contributed by Bénédikt Tran in gh-74598 .) fractions ¶ A Fraction object may now be constructed from any object with the as_integer_ratio() method. (Contributed by Serhiy Storchaka in gh-82017 .) Add Fraction.from_number() as an alternative constructor for Fraction . (Contributed by Serhiy Storchaka in gh-121797 .) functools ¶ Add the Placeholder sentinel. This may be used with the partial() or partialmethod() functions to reserve a place for positional arguments in the returned partial object . (Contributed by Dominykas Grigonis in gh-119127 .) Allow the initial parameter of reduce() to be passed as a keyword argument. (Contributed by Sayandip Dutta in gh-125916 .) getopt ¶ Add support for options with optional arguments. (Contributed by Serhiy Storchaka in gh-126374 .) Add support for returning intermixed options and non-option arguments in order. (Contributed by Serhiy Storchaka in gh-126390 .) getpass ¶ Support keyboard feedback in the getpass() function via the keyword-only optional argument echo_char . Placeholder characters are rendered whenever a character is entered, and removed when a character is deleted. (Contributed by Semyon Moroz in gh-77065 .) graphlib ¶ Allow TopologicalSorter.prepare() to be called more than once as long as sorting has not started. (Contributed by Daniel Pope in gh-130914 .) heapq ¶ The heapq module has improved support for working with max-heaps, via the following new functions: heapify_max() heappush_max() heappop_max() heapreplace_max() heappushpop_max() hmac ¶ Add a built-in implementation for HMAC ( RFC 2104 ) using formally verified code from the HACL* project. This implementation is used as a fallback when the OpenSSL implementation of HMAC is not available. (Contributed by Bénédikt Tran in gh-99108 .) http ¶ Directory lists and error pages generated by the http.server module allow the browser to apply its default dark mode. (Contributed by Yorik Hansen in gh-123430 .) The http.server module now supports serving over HTTPS using the http.server.HTTPSServer class. This functionality is exposed by the command-line interface ( python -m http.server ) through the following options: --tls-cert <path> : Path to the TLS certificate file. --tls-key <path> : Optional path to the private key file. --tls-password-file <path> : Optional path to the password file for the private key. (Contributed by Semyon Moroz in gh-85162 .) imaplib ¶ Add IMAP4.idle() , implementing the IMAP4 IDLE command as defined in RFC 2177 . (Contributed by Forest in gh-55454 .) inspect ¶ signature() takes a new argument annotation_format to control the annotationlib.Format used for representing annotations. (Contributed by Jelle Zijlstra in gh-101552 .) Signature.format() takes a new argument unquote_annotations . If true, string annotations are displayed without surrounding quotes. (Contributed by Jelle Zijlstra in gh-101552 .) Add function ispackage() to determine whether an object is a package or not. (Contributed by Zhikang Yan in gh-125634 .) io ¶ Reading text from a non-blocking stream with read may now raise a BlockingIOError if the operation cannot immediately return bytes. (Contributed by Giovanni Siragusa in gh-109523 .) Add the Reader and Writer protocols as simpler alternatives to the pseudo-protocols typing.IO , typing.TextIO , and typing.BinaryIO . (Contributed by Sebastian Rittau in gh-127648 .) json ¶ Add exception notes for JSON serialization errors that allow identifying the source of the error. (Contributed by Serhiy Storchaka in gh-122163 .) Allow using the json module as a script using the -m switch: python -m json . This is now preferred to python -m json.tool , which is soft deprecated . See the JSON command-line interface documentation. (Contributed by Trey Hunner in gh-122873 .) By default, the output of the JSON command-line interface is highlighted in color. This can be controlled by environment variables . (Contributed by Tomas Roun in gh-131952 .) linecache ¶ getline() can now retrieve source code for frozen modules. (Contributed by Tian Gao in gh-131638 .) logging.handlers ¶ QueueListener objects now support the context manager protocol. (Contributed by Charles Machalow in gh-132106 .) QueueListener.start now raises a RuntimeError if the listener is already started. (Contributed by Charles Machalow in gh-132106 .) math ¶ Added more detailed error messages for domain errors in the module. (Contributed by Charlie Zhao and Sergey B Kirpichev in gh-101410 .) mimetypes ¶ Add a public command-line for the module, invoked via python -m mimetypes . (Contributed by Oleg Iarygin and Hugo van Kemenade in gh-93096 .) Add several new MIME types based on RFCs and common usage: Microsoft and RFC 8081 MIME types for fonts Embedded OpenType: application/vnd.ms-fontobject OpenType Layout (OTF) font/otf TrueType: font/ttf WOFF 1.0 font/woff WOFF 2.0 font/woff2 RFC 9559 | 2026-01-13T08:49:47 |
https://www.facebook.com/settings | Facebook에 로그인 Notice 계정 설정을 변경하려면 비밀번호 확인을 거쳐야 합니다. Facebook에 로그인 계정 설정을 변경하려면 비밀번호 확인을 거쳐야 합니다. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://llvm.org/docs/LangRef.html#non-integral-pointer-type | LLVM Language Reference Manual — LLVM 22.0.0git documentation Navigation index next | previous | LLVM Home | Documentation » Reference » LLVM Language Reference Manual Documentation Getting Started/Tutorials User Guides Reference Getting Involved Contributing to LLVM Submitting Bug Reports Mailing Lists Discord Meetups and Social Events Additional Links FAQ Glossary Publications Github Repository This Page Show Source Quick search LLVM Language Reference Manual ¶ Abstract Introduction Well-Formedness Syntax Identifiers String constants High Level Structure Module Structure Linkage Types Calling Conventions Visibility Styles DLL Storage Classes Thread Local Storage Models Runtime Preemption Specifiers Structure Types Non-Integral Pointer Type Pointers with non-address bits Unstable pointer representation Pointers with external state Global Variables Functions Aliases IFuncs Comdats Named Metadata Parameter Attributes Garbage Collector Strategy Names Prefix Data Prologue Data Personality Function Attribute Groups Function Attributes Call Site Attributes Global Attributes Operand Bundles Deoptimization Operand Bundles Funclet Operand Bundles GC Transition Operand Bundles Assume Operand Bundles Preallocated Operand Bundles GC Live Operand Bundles ObjC ARC Attached Call Operand Bundles Pointer Authentication Operand Bundles KCFI Operand Bundles Convergence Control Operand Bundles Deactivation Symbol Operand Bundles Module-Level Inline Assembly Data Layout Target Triple Allocated Objects Object Lifetime Pointer Aliasing Rules Pointer Capture Volatile Memory Accesses Memory Model for Concurrent Operations Atomic Memory Ordering Constraints Floating-Point Environment Behavior of Floating-Point NaN values Floating-Point Semantics Fast-Math Flags Rewrite-based flags Use-list Order Directives Source Filename Type System Void Type Function Type Opaque Structure Types First Class Types Single Value Types Label Type Token Type Metadata Type Aggregate Types Constants Simple Constants Complex Constants Global Variable and Function Addresses Undefined Values Poison Values Well-Defined Values Addresses of Basic Blocks DSO Local Equivalent No CFI Pointer Authentication Constants Constant Expressions Other Values Inline Assembler Expressions Inline Asm Constraint String Asm template argument modifiers Inline Asm Metadata Metadata Metadata Strings ( MDString ) Metadata Nodes ( MDNode ) Specialized Metadata Nodes ‘ tbaa ’ Metadata ‘ tbaa.struct ’ Metadata ‘ noalias ’ and ‘ alias.scope ’ Metadata ‘ fpmath ’ Metadata ‘ range ’ Metadata ‘ absolute_symbol ’ Metadata ‘ callees ’ Metadata ‘ callback ’ Metadata ‘ exclude ’ Metadata ‘ unpredictable ’ Metadata ‘ dereferenceable ’ Metadata ‘ dereferenceable_or_null ’ Metadata ‘ captures ’ Metadata ‘ llvm.loop ’ ‘ llvm.loop.disable_nonforced ’ ‘ llvm.loop.vectorize ’ and ‘ llvm.loop.interleave ’ ‘ llvm.loop.interleave.count ’ Metadata ‘ llvm.loop.vectorize.enable ’ Metadata ‘ llvm.loop.vectorize.predicate.enable ’ Metadata ‘ llvm.loop.vectorize.scalable.enable ’ Metadata ‘ llvm.loop.vectorize.width ’ Metadata ‘ llvm.loop.vectorize.followup_vectorized ’ Metadata ‘ llvm.loop.vectorize.followup_epilogue ’ Metadata ‘ llvm.loop.vectorize.followup_all ’ Metadata ‘ llvm.loop.unroll ’ ‘ llvm.loop.unroll.count ’ Metadata ‘ llvm.loop.unroll.disable ’ Metadata ‘ llvm.loop.unroll.runtime.disable ’ Metadata ‘ llvm.loop.unroll.enable ’ Metadata ‘ llvm.loop.unroll.full ’ Metadata ‘ llvm.loop.unroll.followup ’ Metadata ‘ llvm.loop.unroll.followup_remainder ’ Metadata ‘ llvm.loop.unroll_and_jam ’ ‘ llvm.loop.unroll_and_jam.count ’ Metadata ‘ llvm.loop.unroll_and_jam.disable ’ Metadata ‘ llvm.loop.unroll_and_jam.enable ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_outer ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_inner ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_remainder_outer ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_remainder_inner ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_all ’ Metadata ‘ llvm.loop.licm_versioning.disable ’ Metadata ‘ llvm.loop.distribute.enable ’ Metadata ‘ llvm.loop.distribute.followup_coincident ’ Metadata ‘ llvm.loop.distribute.followup_sequential ’ Metadata ‘ llvm.loop.distribute.followup_fallback ’ Metadata ‘ llvm.loop.distribute.followup_all ’ Metadata ‘ llvm.loop.isdistributed ’ Metadata ‘ llvm.loop.estimated_trip_count ’ Metadata ‘ llvm.licm.disable ’ Metadata ‘ llvm.access.group ’ Metadata ‘ llvm.loop.parallel_accesses ’ Metadata ‘ llvm.loop.mustprogress ’ Metadata ‘ irr_loop ’ Metadata ‘ invariant.group ’ Metadata ‘ type ’ Metadata ‘ callee_type ’ Metadata ‘ associated ’ Metadata ‘ prof ’ Metadata ‘ annotation ’ Metadata ‘ func_sanitize ’ Metadata ‘ kcfi_type ’ Metadata ‘ pcsections ’ Metadata ‘ memprof ’ Metadata ‘ callsite ’ Metadata ‘ noalias.addrspace ’ Metadata ‘ mmra ’ Metadata ‘ nofree ’ Metadata ‘ alloc_token ’ Metadata ‘ stack-protector ’ Metadata ‘ implicit.ref ’ Metadata Module Flags Metadata Synthesized Functions Module Flags Metadata Objective-C Garbage Collection Module Flags Metadata C type width Module Flags Metadata Stack Alignment Metadata Embedded Objects Names Metadata Automatic Linker Flags Named Metadata Dependent Libs Named Metadata ‘ llvm.errno.tbaa ’ Named Metadata ThinLTO Summary Module Path Summary Entry Global Value Summary Entry Function Summary Global Variable Summary Alias Summary Function Flags Calls Params Refs TypeIdInfo Type ID Summary Entry Intrinsic Global Variables The ‘ llvm.used ’ Global Variable The ‘ llvm.compiler.used ’ Global Variable The ‘ llvm.global_ctors ’ Global Variable The ‘ llvm.global_dtors ’ Global Variable Instruction Reference Terminator Instructions ‘ ret ’ Instruction ‘ br ’ Instruction ‘ switch ’ Instruction ‘ indirectbr ’ Instruction ‘ invoke ’ Instruction ‘ callbr ’ Instruction ‘ resume ’ Instruction ‘ catchswitch ’ Instruction ‘ catchret ’ Instruction ‘ cleanupret ’ Instruction ‘ unreachable ’ Instruction Unary Operations ‘ fneg ’ Instruction Binary Operations ‘ add ’ Instruction ‘ fadd ’ Instruction ‘ sub ’ Instruction ‘ fsub ’ Instruction ‘ mul ’ Instruction ‘ fmul ’ Instruction ‘ udiv ’ Instruction ‘ sdiv ’ Instruction ‘ fdiv ’ Instruction ‘ urem ’ Instruction ‘ srem ’ Instruction ‘ frem ’ Instruction Bitwise Binary Operations ‘ shl ’ Instruction ‘ lshr ’ Instruction ‘ ashr ’ Instruction ‘ and ’ Instruction ‘ or ’ Instruction ‘ xor ’ Instruction Vector Operations ‘ extractelement ’ Instruction ‘ insertelement ’ Instruction ‘ shufflevector ’ Instruction Aggregate Operations ‘ extractvalue ’ Instruction ‘ insertvalue ’ Instruction Memory Access and Addressing Operations ‘ alloca ’ Instruction ‘ load ’ Instruction ‘ store ’ Instruction ‘ fence ’ Instruction ‘ cmpxchg ’ Instruction ‘ atomicrmw ’ Instruction ‘ getelementptr ’ Instruction Conversion Operations ‘ trunc .. to ’ Instruction ‘ zext .. to ’ Instruction ‘ sext .. to ’ Instruction ‘ fptrunc .. to ’ Instruction ‘ fpext .. to ’ Instruction ‘ fptoui .. to ’ Instruction ‘ fptosi .. to ’ Instruction ‘ uitofp .. to ’ Instruction ‘ sitofp .. to ’ Instruction ‘ ptrtoint .. to ’ Instruction ‘ ptrtoaddr .. to ’ Instruction ‘ inttoptr .. to ’ Instruction ‘ bitcast .. to ’ Instruction ‘ addrspacecast .. to ’ Instruction Other Operations ‘ icmp ’ Instruction ‘ fcmp ’ Instruction ‘ phi ’ Instruction ‘ select ’ Instruction ‘ freeze ’ Instruction ‘ call ’ Instruction ‘ va_arg ’ Instruction ‘ landingpad ’ Instruction ‘ catchpad ’ Instruction ‘ cleanuppad ’ Instruction Debug Records Intrinsic Functions Variable Argument Handling Intrinsics ‘ llvm.va_start ’ Intrinsic ‘ llvm.va_end ’ Intrinsic ‘ llvm.va_copy ’ Intrinsic Accurate Garbage Collection Intrinsics ‘ llvm.gcroot ’ Intrinsic ‘ llvm.gcread ’ Intrinsic ‘ llvm.gcwrite ’ Intrinsic ‘ llvm.experimental.gc.statepoint ’ Intrinsic ‘ llvm.experimental.gc.result ’ Intrinsic ‘ llvm.experimental.gc.relocate ’ Intrinsic ‘ llvm.experimental.gc.get.pointer.base ’ Intrinsic ‘ llvm.experimental.gc.get.pointer.offset ’ Intrinsic Code Generator Intrinsics ‘ llvm.returnaddress ’ Intrinsic ‘ llvm.addressofreturnaddress ’ Intrinsic ‘ llvm.sponentry ’ Intrinsic ‘ llvm.stackaddress ’ Intrinsic ‘ llvm.frameaddress ’ Intrinsic ‘ llvm.swift.async.context.addr ’ Intrinsic ‘ llvm.localescape ’ and ‘ llvm.localrecover ’ Intrinsics ‘ llvm.seh.try.begin ’ and ‘ llvm.seh.try.end ’ Intrinsics ‘ llvm.seh.scope.begin ’ and ‘ llvm.seh.scope.end ’ Intrinsics ‘ llvm.read_register ’, ‘ llvm.read_volatile_register ’, and ‘ llvm.write_register ’ Intrinsics ‘ llvm.stacksave ’ Intrinsic ‘ llvm.stackrestore ’ Intrinsic ‘ llvm.get.dynamic.area.offset ’ Intrinsic ‘ llvm.prefetch ’ Intrinsic ‘ llvm.pcmarker ’ Intrinsic ‘ llvm.readcyclecounter ’ Intrinsic ‘ llvm.readsteadycounter ’ Intrinsic ‘ llvm.clear_cache ’ Intrinsic ‘ llvm.instrprof.increment ’ Intrinsic ‘ llvm.instrprof.increment.step ’ Intrinsic ‘ llvm.instrprof.callsite ’ Intrinsic ‘ llvm.instrprof.timestamp ’ Intrinsic ‘ llvm.instrprof.cover ’ Intrinsic ‘ llvm.instrprof.value.profile ’ Intrinsic ‘ llvm.instrprof.mcdc.parameters ’ Intrinsic ‘ llvm.instrprof.mcdc.tvbitmap.update ’ Intrinsic ‘ llvm.thread.pointer ’ Intrinsic ‘ llvm.call.preallocated.setup ’ Intrinsic ‘ llvm.call.preallocated.arg ’ Intrinsic ‘ llvm.call.preallocated.teardown ’ Intrinsic Standard C/C++ Library Intrinsics ‘ llvm.abs.* ’ Intrinsic ‘ llvm.smax.* ’ Intrinsic ‘ llvm.smin.* ’ Intrinsic ‘ llvm.umax.* ’ Intrinsic ‘ llvm.umin.* ’ Intrinsic ‘ llvm.scmp.* ’ Intrinsic ‘ llvm.ucmp.* ’ Intrinsic ‘ llvm.memcpy ’ Intrinsic ‘ llvm.memcpy.inline ’ Intrinsic ‘ llvm.memmove ’ Intrinsic ‘ llvm.memset.* ’ Intrinsics ‘ llvm.memset.inline ’ Intrinsic ‘ llvm.experimental.memset.pattern ’ Intrinsic ‘ llvm.sqrt.* ’ Intrinsic ‘ llvm.powi.* ’ Intrinsic ‘ llvm.sin.* ’ Intrinsic ‘ llvm.cos.* ’ Intrinsic ‘ llvm.tan.* ’ Intrinsic ‘ llvm.asin.* ’ Intrinsic ‘ llvm.acos.* ’ Intrinsic ‘ llvm.atan.* ’ Intrinsic ‘ llvm.atan2.* ’ Intrinsic ‘ llvm.sinh.* ’ Intrinsic ‘ llvm.cosh.* ’ Intrinsic ‘ llvm.tanh.* ’ Intrinsic ‘ llvm.sincos.* ’ Intrinsic ‘ llvm.sincospi.* ’ Intrinsic ‘ llvm.modf.* ’ Intrinsic ‘ llvm.pow.* ’ Intrinsic ‘ llvm.exp.* ’ Intrinsic ‘ llvm.exp2.* ’ Intrinsic ‘ llvm.exp10.* ’ Intrinsic ‘ llvm.ldexp.* ’ Intrinsic ‘ llvm.frexp.* ’ Intrinsic ‘ llvm.log.* ’ Intrinsic ‘ llvm.log10.* ’ Intrinsic ‘ llvm.log2.* ’ Intrinsic ‘ llvm.fma.* ’ Intrinsic ‘ llvm.fabs.* ’ Intrinsic ‘ llvm.min.* ’ Intrinsics Comparation ‘ llvm.minnum.* ’ Intrinsic ‘ llvm.maxnum.* ’ Intrinsic ‘ llvm.minimum.* ’ Intrinsic ‘ llvm.maximum.* ’ Intrinsic ‘ llvm.minimumnum.* ’ Intrinsic ‘ llvm.maximumnum.* ’ Intrinsic ‘ llvm.copysign.* ’ Intrinsic ‘ llvm.floor.* ’ Intrinsic ‘ llvm.ceil.* ’ Intrinsic ‘ llvm.trunc.* ’ Intrinsic ‘ llvm.rint.* ’ Intrinsic ‘ llvm.nearbyint.* ’ Intrinsic ‘ llvm.round.* ’ Intrinsic ‘ llvm.roundeven.* ’ Intrinsic ‘ llvm.lround.* ’ Intrinsic ‘ llvm.llround.* ’ Intrinsic ‘ llvm.lrint.* ’ Intrinsic ‘ llvm.llrint.* ’ Intrinsic Bit Manipulation Intrinsics ‘ llvm.bitreverse.* ’ Intrinsics ‘ llvm.bswap.* ’ Intrinsics ‘ llvm.ctpop.* ’ Intrinsic ‘ llvm.ctlz.* ’ Intrinsic ‘ llvm.cttz.* ’ Intrinsic ‘ llvm.fshl.* ’ Intrinsic ‘ llvm.fshr.* ’ Intrinsic ‘ llvm.clmul.* ’ Intrinsic Arithmetic with Overflow Intrinsics ‘ llvm.sadd.with.overflow.* ’ Intrinsics ‘ llvm.uadd.with.overflow.* ’ Intrinsics ‘ llvm.ssub.with.overflow.* ’ Intrinsics ‘ llvm.usub.with.overflow.* ’ Intrinsics ‘ llvm.smul.with.overflow.* ’ Intrinsics ‘ llvm.umul.with.overflow.* ’ Intrinsics Saturation Arithmetic Intrinsics ‘ llvm.sadd.sat.* ’ Intrinsics ‘ llvm.uadd.sat.* ’ Intrinsics ‘ llvm.ssub.sat.* ’ Intrinsics ‘ llvm.usub.sat.* ’ Intrinsics ‘ llvm.sshl.sat.* ’ Intrinsics ‘ llvm.ushl.sat.* ’ Intrinsics Fixed Point Arithmetic Intrinsics ‘ llvm.smul.fix.* ’ Intrinsics ‘ llvm.umul.fix.* ’ Intrinsics ‘ llvm.smul.fix.sat.* ’ Intrinsics ‘ llvm.umul.fix.sat.* ’ Intrinsics ‘ llvm.sdiv.fix.* ’ Intrinsics ‘ llvm.udiv.fix.* ’ Intrinsics ‘ llvm.sdiv.fix.sat.* ’ Intrinsics ‘ llvm.udiv.fix.sat.* ’ Intrinsics Specialized Arithmetic Intrinsics ‘ llvm.canonicalize.* ’ Intrinsic ‘ llvm.fmuladd.* ’ Intrinsic Hardware-Loop Intrinsics ‘ llvm.set.loop.iterations.* ’ Intrinsic ‘ llvm.start.loop.iterations.* ’ Intrinsic ‘ llvm.test.set.loop.iterations.* ’ Intrinsic ‘ llvm.test.start.loop.iterations.* ’ Intrinsic ‘ llvm.loop.decrement.reg.* ’ Intrinsic ‘ llvm.loop.decrement.* ’ Intrinsic Vector Reduction Intrinsics ‘ llvm.vector.reduce.add.* ’ Intrinsic ‘ llvm.vector.reduce.fadd.* ’ Intrinsic ‘ llvm.vector.reduce.mul.* ’ Intrinsic ‘ llvm.vector.reduce.fmul.* ’ Intrinsic ‘ llvm.vector.reduce.and.* ’ Intrinsic ‘ llvm.vector.reduce.or.* ’ Intrinsic ‘ llvm.vector.reduce.xor.* ’ Intrinsic ‘ llvm.vector.reduce.smax.* ’ Intrinsic ‘ llvm.vector.reduce.smin.* ’ Intrinsic ‘ llvm.vector.reduce.umax.* ’ Intrinsic ‘ llvm.vector.reduce.umin.* ’ Intrinsic ‘ llvm.vector.reduce.fmax.* ’ Intrinsic ‘ llvm.vector.reduce.fmin.* ’ Intrinsic ‘ llvm.vector.reduce.fmaximum.* ’ Intrinsic ‘ llvm.vector.reduce.fminimum.* ’ Intrinsic Vector Partial Reduction Intrinsics ‘ llvm.vector.partial.reduce.add.* ’ Intrinsic ‘ llvm.vector.partial.reduce.fadd.* ’ Intrinsic Vector Manipulation Intrinsics ‘ llvm.vector.insert ’ Intrinsic ‘ llvm.vector.extract ’ Intrinsic ‘ llvm.vector.reverse ’ Intrinsic ‘ llvm.vector.deinterleave2/3/4/5/6/7/8 ’ Intrinsic ‘ llvm.vector.interleave2/3/4/5/6/7/8 ’ Intrinsic ‘ llvm.vector.splice.left ’ Intrinsic ‘ llvm.vector.splice.right ’ Intrinsic ‘ llvm.stepvector ’ Intrinsic Experimental Vector Intrinsics ‘ llvm.experimental.cttz.elts ’ Intrinsic ‘ llvm.experimental.get.vector.length ’ Intrinsic ‘ llvm.experimental.vector.histogram.* ’ Intrinsic ‘ llvm.experimental.vector.extract.last.active ’ Intrinsic ‘ llvm.experimental.vector.compress.* ’ Intrinsics ‘ llvm.experimental.vector.match.* ’ Intrinsic Matrix Intrinsics ‘ llvm.matrix.transpose.* ’ Intrinsic ‘ llvm.matrix.multiply.* ’ Intrinsic ‘ llvm.matrix.column.major.load.* ’ Intrinsic ‘ llvm.matrix.column.major.store.* ’ Intrinsic Half Precision Floating-Point Intrinsics ‘ llvm.convert.to.fp16 ’ Intrinsic ‘ llvm.convert.from.fp16 ’ Intrinsic Saturating floating-point to integer conversions ‘ llvm.fptoui.sat.* ’ Intrinsic ‘ llvm.fptosi.sat.* ’ Intrinsic Floating-Point Conversion Intrinsics ‘ llvm.fptrunc.round ’ Intrinsic Convergence Intrinsics Debugger Intrinsics Exception Handling Intrinsics Pointer Authentication Intrinsics Trampoline Intrinsics ‘ llvm.init.trampoline ’ Intrinsic ‘ llvm.adjust.trampoline ’ Intrinsic Vector Predication Intrinsics Optimization Hint ‘ llvm.vp.select.* ’ Intrinsics ‘ llvm.vp.merge.* ’ Intrinsics ‘ llvm.vp.add.* ’ Intrinsics ‘ llvm.vp.sub.* ’ Intrinsics ‘ llvm.vp.mul.* ’ Intrinsics ‘ llvm.vp.sdiv.* ’ Intrinsics ‘ llvm.vp.udiv.* ’ Intrinsics ‘ llvm.vp.srem.* ’ Intrinsics ‘ llvm.vp.urem.* ’ Intrinsics ‘ llvm.vp.ashr.* ’ Intrinsics ‘ llvm.vp.lshr.* ’ Intrinsics ‘ llvm.vp.shl.* ’ Intrinsics ‘ llvm.vp.or.* ’ Intrinsics ‘ llvm.vp.and.* ’ Intrinsics ‘ llvm.vp.xor.* ’ Intrinsics ‘ llvm.vp.abs.* ’ Intrinsics ‘ llvm.vp.smax.* ’ Intrinsics ‘ llvm.vp.smin.* ’ Intrinsics ‘ llvm.vp.umax.* ’ Intrinsics ‘ llvm.vp.umin.* ’ Intrinsics ‘ llvm.vp.copysign.* ’ Intrinsics ‘ llvm.vp.minnum.* ’ Intrinsics ‘ llvm.vp.maxnum.* ’ Intrinsics ‘ llvm.vp.minimum.* ’ Intrinsics ‘ llvm.vp.maximum.* ’ Intrinsics ‘ llvm.vp.fadd.* ’ Intrinsics ‘ llvm.vp.fsub.* ’ Intrinsics ‘ llvm.vp.fmul.* ’ Intrinsics ‘ llvm.vp.fdiv.* ’ Intrinsics ‘ llvm.vp.frem.* ’ Intrinsics ‘ llvm.vp.fneg.* ’ Intrinsics ‘ llvm.vp.fabs.* ’ Intrinsics ‘ llvm.vp.sqrt.* ’ Intrinsics ‘ llvm.vp.fma.* ’ Intrinsics ‘ llvm.vp.fmuladd.* ’ Intrinsics ‘ llvm.vp.reduce.add.* ’ Intrinsics ‘ llvm.vp.reduce.fadd.* ’ Intrinsics ‘ llvm.vp.reduce.mul.* ’ Intrinsics ‘ llvm.vp.reduce.fmul.* ’ Intrinsics ‘ llvm.vp.reduce.and.* ’ Intrinsics ‘ llvm.vp.reduce.or.* ’ Intrinsics ‘ llvm.vp.reduce.xor.* ’ Intrinsics ‘ llvm.vp.reduce.smax.* ’ Intrinsics ‘ llvm.vp.reduce.smin.* ’ Intrinsics ‘ llvm.vp.reduce.umax.* ’ Intrinsics ‘ llvm.vp.reduce.umin.* ’ Intrinsics ‘ llvm.vp.reduce.fmax.* ’ Intrinsics ‘ llvm.vp.reduce.fmin.* ’ Intrinsics ‘ llvm.vp.reduce.fmaximum.* ’ Intrinsics ‘ llvm.vp.reduce.fminimum.* ’ Intrinsics ‘ llvm.get.active.lane.mask.* ’ Intrinsics ‘ llvm.loop.dependence.war.mask.* ’ Intrinsics ‘ llvm.loop.dependence.raw.mask.* ’ Intrinsics ‘ llvm.experimental.vp.splice ’ Intrinsic ‘ llvm.experimental.vp.reverse ’ Intrinsic ‘ llvm.vp.load ’ Intrinsic ‘ llvm.vp.load.ff ’ Intrinsic ‘ llvm.vp.store ’ Intrinsic ‘ llvm.experimental.vp.strided.load ’ Intrinsic ‘ llvm.experimental.vp.strided.store ’ Intrinsic ‘ llvm.vp.gather ’ Intrinsic ‘ llvm.vp.scatter ’ Intrinsic ‘ llvm.vp.trunc.* ’ Intrinsics ‘ llvm.vp.zext.* ’ Intrinsics ‘ llvm.vp.sext.* ’ Intrinsics ‘ llvm.vp.fptrunc.* ’ Intrinsics ‘ llvm.vp.fpext.* ’ Intrinsics ‘ llvm.vp.fptoui.* ’ Intrinsics ‘ llvm.vp.fptosi.* ’ Intrinsics ‘ llvm.vp.uitofp.* ’ Intrinsics ‘ llvm.vp.sitofp.* ’ Intrinsics ‘ llvm.vp.ptrtoint.* ’ Intrinsics ‘ llvm.vp.inttoptr.* ’ Intrinsics ‘ llvm.vp.fcmp.* ’ Intrinsics ‘ llvm.vp.icmp.* ’ Intrinsics ‘ llvm.vp.ceil.* ’ Intrinsics ‘ llvm.vp.floor.* ’ Intrinsics ‘ llvm.vp.rint.* ’ Intrinsics ‘ llvm.vp.nearbyint.* ’ Intrinsics ‘ llvm.vp.round.* ’ Intrinsics ‘ llvm.vp.roundeven.* ’ Intrinsics ‘ llvm.vp.roundtozero.* ’ Intrinsics ‘ llvm.vp.lrint.* ’ Intrinsics ‘ llvm.vp.llrint.* ’ Intrinsics ‘ llvm.vp.bitreverse.* ’ Intrinsics ‘ llvm.vp.bswap.* ’ Intrinsics ‘ llvm.vp.ctpop.* ’ Intrinsics ‘ llvm.vp.ctlz.* ’ Intrinsics ‘ llvm.vp.cttz.* ’ Intrinsics ‘ llvm.vp.cttz.elts.* ’ Intrinsics ‘ llvm.vp.sadd.sat.* ’ Intrinsics ‘ llvm.vp.uadd.sat.* ’ Intrinsics ‘ llvm.vp.ssub.sat.* ’ Intrinsics ‘ llvm.vp.usub.sat.* ’ Intrinsics ‘ llvm.vp.fshl.* ’ Intrinsics ‘ llvm.vp.fshr.* ’ Intrinsics ‘ llvm.vp.is.fpclass.* ’ Intrinsics Masked Vector Load and Store Intrinsics ‘ llvm.masked.load.* ’ Intrinsics ‘ llvm.masked.store.* ’ Intrinsics Masked Vector Gather and Scatter Intrinsics ‘ llvm.masked.gather.* ’ Intrinsics ‘ llvm.masked.scatter.* ’ Intrinsics Masked Vector Expanding Load and Compressing Store Intrinsics ‘ llvm.masked.expandload.* ’ Intrinsics ‘ llvm.masked.compressstore.* ’ Intrinsics Memory Use Markers ‘ llvm.lifetime.start ’ Intrinsic ‘ llvm.lifetime.end ’ Intrinsic ‘ llvm.invariant.start ’ Intrinsic ‘ llvm.invariant.end ’ Intrinsic ‘ llvm.launder.invariant.group ’ Intrinsic ‘ llvm.strip.invariant.group ’ Intrinsic Constrained Floating-Point Intrinsics ‘ llvm.experimental.constrained.fadd ’ Intrinsic ‘ llvm.experimental.constrained.fsub ’ Intrinsic ‘ llvm.experimental.constrained.fmul ’ Intrinsic ‘ llvm.experimental.constrained.fdiv ’ Intrinsic ‘ llvm.experimental.constrained.frem ’ Intrinsic ‘ llvm.experimental.constrained.fma ’ Intrinsic ‘ llvm.experimental.constrained.fptoui ’ Intrinsic ‘ llvm.experimental.constrained.fptosi ’ Intrinsic ‘ llvm.experimental.constrained.uitofp ’ Intrinsic ‘ llvm.experimental.constrained.sitofp ’ Intrinsic ‘ llvm.experimental.constrained.fptrunc ’ Intrinsic ‘ llvm.experimental.constrained.fpext ’ Intrinsic ‘ llvm.experimental.constrained.fcmp ’ and ‘ llvm.experimental.constrained.fcmps ’ Intrinsics ‘ llvm.experimental.constrained.fmuladd ’ Intrinsic Constrained libm-equivalent Intrinsics ‘ llvm.experimental.constrained.sqrt ’ Intrinsic ‘ llvm.experimental.constrained.pow ’ Intrinsic ‘ llvm.experimental.constrained.powi ’ Intrinsic ‘ llvm.experimental.constrained.ldexp ’ Intrinsic ‘ llvm.experimental.constrained.sin ’ Intrinsic ‘ llvm.experimental.constrained.cos ’ Intrinsic ‘ llvm.experimental.constrained.tan ’ Intrinsic ‘ llvm.experimental.constrained.asin ’ Intrinsic ‘ llvm.experimental.constrained.acos ’ Intrinsic ‘ llvm.experimental.constrained.atan ’ Intrinsic ‘ llvm.experimental.constrained.atan2 ’ Intrinsic ‘ llvm.experimental.constrained.sinh ’ Intrinsic ‘ llvm.experimental.constrained.cosh ’ Intrinsic ‘ llvm.experimental.constrained.tanh ’ Intrinsic ‘ llvm.experimental.constrained.exp ’ Intrinsic ‘ llvm.experimental.constrained.exp2 ’ Intrinsic ‘ llvm.experimental.constrained.log ’ Intrinsic ‘ llvm.experimental.constrained.log10 ’ Intrinsic ‘ llvm.experimental.constrained.log2 ’ Intrinsic ‘ llvm.experimental.constrained.rint ’ Intrinsic ‘ llvm.experimental.constrained.lrint ’ Intrinsic ‘ llvm.experimental.constrained.llrint ’ Intrinsic ‘ llvm.experimental.constrained.nearbyint ’ Intrinsic ‘ llvm.experimental.constrained.maxnum ’ Intrinsic ‘ llvm.experimental.constrained.minnum ’ Intrinsic ‘ llvm.experimental.constrained.maximum ’ Intrinsic ‘ llvm.experimental.constrained.minimum ’ Intrinsic ‘ llvm.experimental.constrained.ceil ’ Intrinsic ‘ llvm.experimental.constrained.floor ’ Intrinsic ‘ llvm.experimental.constrained.round ’ Intrinsic ‘ llvm.experimental.constrained.roundeven ’ Intrinsic ‘ llvm.experimental.constrained.lround ’ Intrinsic ‘ llvm.experimental.constrained.llround ’ Intrinsic ‘ llvm.experimental.constrained.trunc ’ Intrinsic ‘ llvm.experimental.noalias.scope.decl ’ Intrinsic Floating Point Environment Manipulation intrinsics ‘ llvm.get.rounding ’ Intrinsic ‘ llvm.set.rounding ’ Intrinsic ‘ llvm.get.fpenv ’ Intrinsic ‘ llvm.set.fpenv ’ Intrinsic ‘ llvm.reset.fpenv ’ Intrinsic ‘ llvm.get.fpmode ’ Intrinsic ‘ llvm.set.fpmode ’ Intrinsic ‘ llvm.reset.fpmode ’ Intrinsic Floating-Point Test Intrinsics ‘ llvm.is.fpclass ’ Intrinsic General Intrinsics ‘ llvm.var.annotation ’ Intrinsic ‘ llvm.ptr.annotation.* ’ Intrinsic ‘ llvm.annotation.* ’ Intrinsic ‘ llvm.codeview.annotation ’ Intrinsic ‘ llvm.trap ’ Intrinsic ‘ llvm.debugtrap ’ Intrinsic ‘ llvm.ubsantrap ’ Intrinsic ‘ llvm.stackprotector ’ Intrinsic ‘ llvm.stackguard ’ Intrinsic ‘ llvm.objectsize ’ Intrinsic ‘ llvm.expect ’ Intrinsic ‘ llvm.expect.with.probability ’ Intrinsic ‘ llvm.assume ’ Intrinsic ‘ llvm.ssa.copy ’ Intrinsic ‘ llvm.type.test ’ Intrinsic ‘ llvm.type.checked.load ’ Intrinsic ‘ llvm.type.checked.load.relative ’ Intrinsic ‘ llvm.arithmetic.fence ’ Intrinsic ‘ llvm.donothing ’ Intrinsic ‘ llvm.experimental.deoptimize ’ Intrinsic ‘ llvm.experimental.guard ’ Intrinsic ‘ llvm.experimental.widenable.condition ’ Intrinsic ‘ llvm.allow.ubsan.check ’ Intrinsic ‘ llvm.allow.runtime.check ’ Intrinsic ‘ llvm.load.relative ’ Intrinsic ‘ llvm.sideeffect ’ Intrinsic ‘ llvm.is.constant.* ’ Intrinsic ‘ llvm.ptrmask ’ Intrinsic ‘ llvm.threadlocal.address ’ Intrinsic ‘ llvm.vscale ’ Intrinsic ‘ llvm.fake.use ’ Intrinsic ‘ llvm.reloc.none ’ Intrinsic Stack Map Intrinsics Element Wise Atomic Memory Intrinsics ‘ llvm.memcpy.element.unordered.atomic ’ Intrinsic ‘ llvm.memmove.element.unordered.atomic ’ Intrinsic ‘ llvm.memset.element.unordered.atomic ’ Intrinsic Objective-C ARC Runtime Intrinsics ‘ llvm.objc.autorelease ’ Intrinsic ‘ llvm.objc.autoreleasePoolPop ’ Intrinsic ‘ llvm.objc.autoreleasePoolPush ’ Intrinsic ‘ llvm.objc.autoreleaseReturnValue ’ Intrinsic ‘ llvm.objc.copyWeak ’ Intrinsic ‘ llvm.objc.destroyWeak ’ Intrinsic ‘ llvm.objc.initWeak ’ Intrinsic ‘ llvm.objc.loadWeak ’ Intrinsic ‘ llvm.objc.loadWeakRetained ’ Intrinsic ‘ llvm.objc.moveWeak ’ Intrinsic ‘ llvm.objc.release ’ Intrinsic ‘ llvm.objc.retain ’ Intrinsic ‘ llvm.objc.retainAutorelease ’ Intrinsic ‘ llvm.objc.retainAutoreleaseReturnValue ’ Intrinsic ‘ llvm.objc.retainAutoreleasedReturnValue ’ Intrinsic ‘ llvm.objc.retainBlock ’ Intrinsic ‘ llvm.objc.storeStrong ’ Intrinsic ‘ llvm.objc.storeWeak ’ Intrinsic Preserving Debug Information Intrinsics ‘ llvm.preserve.array.access.index ’ Intrinsic ‘ llvm.preserve.union.access.index ’ Intrinsic ‘ llvm.preserve.struct.access.index ’ Intrinsic ‘ llvm.protected.field.ptr ’ Intrinsic Abstract ¶ This document is a reference manual for the LLVM assembly language. LLVM is a Static Single Assignment (SSA) based representation that provides type safety, low-level operations, flexibility, and the capability of representing ‘all’ high-level languages cleanly. It is the common code representation used throughout all phases of the LLVM compilation strategy. Introduction ¶ The LLVM code representation is designed to be used in three different forms: as an in-memory compiler IR, as an on-disk bitcode representation (suitable for fast loading by a Just-In-Time compiler), and as a human readable assembly language representation. This allows LLVM to provide a powerful intermediate representation for efficient compiler transformations and analysis, while providing a natural means to debug and visualize the transformations. The three different forms of LLVM are all equivalent. This document describes the human-readable representation and notation. The LLVM representation aims to be light-weight and low-level while being expressive, typed, and extensible at the same time. It aims to be a “universal IR” of sorts, by being at a low enough level that high-level ideas may be cleanly mapped to it (similar to how microprocessors are “universal IR’s”, allowing many source languages to be mapped to them). By providing type information, LLVM can be used as the target of optimizations: for example, through pointer analysis, it can be proven that a C automatic variable is never accessed outside of the current function, allowing it to be promoted to a simple SSA value instead of a memory location. Well-Formedness ¶ It is important to note that this document describes ‘well formed’ LLVM assembly language. There is a difference between what the parser accepts and what is considered ‘well formed’. For example, the following instruction is syntactically okay, but not well formed: %x = add i32 1 , %x because the definition of %x does not dominate all of its uses. The LLVM infrastructure provides a verification pass that may be used to verify that an LLVM module is well formed. This pass is automatically run by the parser after parsing input assembly and by the optimizer before it outputs bitcode. The violations pointed out by the verifier pass indicate bugs in transformation passes or input to the parser. Syntax ¶ Identifiers ¶ LLVM identifiers come in two basic types: global and local. Global identifiers (functions, global variables) begin with the '@' character. Local identifiers (register names, types) begin with the '%' character. Additionally, there are three different formats for identifiers, for different purposes: Named values are represented as a string of characters with their prefix. For example, %foo , @DivisionByZero , %a.really.long.identifier . The actual regular expression used is ‘ [%@][-a-zA-Z$._][-a-zA-Z$._0-9]* ’. Identifiers that require other characters in their names can be surrounded with quotes. Special characters may be escaped using "\xx" where xx is the ASCII code for the character in hexadecimal. In this way, any character can be used in a name value, even quotes themselves. The "\01" prefix can be used on global values to suppress mangling. Unnamed values are represented as an unsigned numeric value with their prefix. For example, %12 , @2 , %44 . Constants, which are described in the section Constants below. LLVM requires that values start with a prefix for two reasons: Compilers don’t need to worry about name clashes with reserved words, and the set of reserved words may be expanded in the future without penalty. Additionally, unnamed identifiers allow a compiler to quickly come up with a temporary variable without having to avoid symbol table conflicts. Reserved words in LLVM are very similar to reserved words in other languages. There are keywords for different opcodes (’ add ’, ‘ bitcast ’, ‘ ret ’, etc…), for primitive type names (’ void ’, ‘ i32 ’, etc…), and others. These reserved words cannot conflict with variable names, because none of them start with a prefix character ( '%' or '@' ). Here is an example of LLVM code to multiply the integer variable ‘ %X ’ by 8: The easy way: %result = mul i32 %X , 8 After strength reduction: %result = shl i32 %X , 3 And the hard way: %0 = add i32 %X , %X ; yields i32:%0 %1 = add i32 %0 , %0 / * yields i32: %1 * / %result = add i32 %1 , %1 This last way of multiplying %X by 8 illustrates several important lexical features of LLVM: Comments are delimited with a ‘ ; ’ and go until the end of line. Alternatively, comments can start with /* and terminate with */ . Unnamed temporaries are created when the result of a computation is not assigned to a named value. By default, unnamed temporaries are numbered sequentially (using a per-function incrementing counter, starting with 0). However, when explicitly specifying temporary numbers, it is allowed to skip over numbers. Note that basic blocks and unnamed function parameters are included in this numbering. For example, if the entry basic block is not given a label name and all function parameters are named, then it will get number 0. It also shows a convention that we follow in this document. When demonstrating instructions, we will follow an instruction with a comment that defines the type and name of value produced. String constants ¶ Strings in LLVM programs are delimited by " characters. Within a string, all bytes are treated literally with the exception of \ characters, which start escapes, and the first " character, which ends the string. There are two kinds of escapes. \\ represents a single \ character. \ followed by two hexadecimal characters (0-9, a-f, or A-F) represents the byte with the given value (e.g., \00 represents a null byte). To represent a " character, use \22 . ( \" will end the string with a trailing \ .) Newlines do not terminate string constants; strings can span multiple lines. The interpretation of string constants (e.g., their character encoding) depends on context. High Level Structure ¶ Module Structure ¶ LLVM programs are composed of Module ’s, each of which is a translation unit of the input programs. Each module consists of functions, global variables, and symbol table entries. Modules may be combined together with the LLVM linker, which merges function (and global variable) definitions, resolves forward declarations, and merges symbol table entries. Here is an example of the “hello world” module: ; Declare the string constant as a global constant. @.str = private unnamed_addr constant [ 13 x i8 ] c "hello world\0A\00" ; External declaration of the puts function declare i32 @puts ( ptr captures ( none )) nounwind ; Definition of main function define i32 @main () { ; Call puts function to write out the string to stdout. call i32 @puts ( ptr @.str ) ret i32 0 } ; Named metadata !0 = !{ i32 42 , null , !"string" } !foo = !{ !0 } This example is made up of a global variable named “ .str ”, an external declaration of the “ puts ” function, a function definition for “ main ” and named metadata “ foo ”. In general, a module is made up of a list of global values (where both functions and global variables are global values). Global values are represented by a pointer to a memory location (in this case, a pointer to an array of char, and a pointer to a function), and have one of the following linkage types . Linkage Types ¶ All Global Variables and Functions have one of the following types of linkage: private Global values with “ private ” linkage are only directly accessible by objects in the current module. In particular, linking code into a module with a private global value may cause the private to be renamed as necessary to avoid collisions. Because the symbol is private to the module, all references can be updated. This doesn’t show up in any symbol table in the object file. internal Similar to private, but the value shows as a local symbol ( STB_LOCAL in the case of ELF) in the object file. This corresponds to the notion of the ‘ static ’ keyword in C. available_externally Globals with “ available_externally ” linkage are never emitted into the object file corresponding to the LLVM module. From the linker’s perspective, an available_externally global is equivalent to an external declaration. They exist to allow inlining and other optimizations to take place given knowledge of the definition of the global, which is known to be somewhere outside the module. Globals with available_externally linkage are allowed to be discarded at will, and allow inlining and other optimizations. This linkage type is only allowed on definitions, not declarations. linkonce Globals with “ linkonce ” linkage are merged with other globals of the same name when linkage occurs. This can be used to implement some forms of inline functions, templates, or other code which must be generated in each translation unit that uses it, but where the body may be overridden with a more definitive definition later. Unreferenced linkonce globals are allowed to be discarded. Note that linkonce linkage does not actually allow the optimizer to inline the body of this function into callers because it doesn’t know if this definition of the function is the definitive definition within the program or whether it will be overridden by a stronger definition. To enable inlining and other optimizations, use “ linkonce_odr ” linkage. weak “ weak ” linkage has the same merging semantics as linkonce linkage, except that unreferenced globals with weak linkage may not be discarded. This is used for globals that are declared “weak” in C source code. common “ common ” linkage is most similar to “ weak ” linkage, but they are used for tentative definitions in C, such as “ int X; ” at global scope. Symbols with “ common ” linkage are merged in the same way as weak symbols , and they may not be deleted if unreferenced. common symbols may not have an explicit section, must have a zero initializer, and may not be marked ‘ constant ’. Functions and aliases may not have common linkage. appending “ appending ” linkage may only be applied to global variables of pointer to array type. When two global variables with appending linkage are linked together, the two global arrays are appended together. This is the LLVM, typesafe, equivalent of having the system linker append together “sections” with identical names when .o files are linked. Unfortunately this doesn’t correspond to any feature in .o files, so it can only be used for variables like llvm.global_ctors which llvm interprets specially. extern_weak The semantics of this linkage follow the ELF object file model: the symbol is weak until linked, if not linked, the symbol becomes null instead of being an undefined reference. linkonce_odr , weak_odr The odr suffix indicates that all globals defined with the given name are equivalent, along the lines of the C++ “one definition rule” (“ODR”). Informally, this means we can inline functions and fold loads of constants. Formally, use the following definition: when an odr function is called, one of the definitions is non-deterministically chosen to run. For odr variables, if any byte in the value is not equal in all initializers, that byte is a poison value . For aliases and ifuncs, apply the rule for the underlying function or variable. These linkage types are otherwise the same as their non- odr versions. external If none of the above identifiers are used, the global is externally visible, meaning that it participates in linkage and can be used to resolve external symbol references. It is illegal for a global variable or function declaration to have any linkage type other than external or extern_weak . Calling Conventions ¶ LLVM functions , calls and invokes can all have an optional calling convention specified for the call. The calling convention of any pair of dynamic caller/callee must match, or the behavior of the program is undefined. The following calling conventions are supported by LLVM, and more may be added in the future: “ ccc ” - The C calling convention This calling convention (the default if no other calling convention is specified) matches the target C calling conventions. This calling convention supports varargs function calls and tolerates some mismatch in the declared prototype and implemented declaration of the function (as does normal C). “ fastcc ” - The fast calling convention This calling convention attempts to make calls as fast as possible (e.g., by passing things in registers). This calling convention allows the target to use whatever tricks it wants to produce fast code for the target, without having to conform to an externally specified ABI (Application Binary Interface). Targets may use different implementations according to different features. In this case, a TTI interface useFastCCForInternalCall must return false when any caller functions and the callee belong to different implementations. Tail calls can only be optimized when this, the tailcc, the GHC or the HiPE convention is used. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. “ coldcc ” - The cold calling convention This calling convention attempts to make code in the caller as efficient as possible under the assumption that the call is not commonly executed. As such, these calls often preserve all registers so that the call does not break any live ranges in the caller side. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. Furthermore the inliner doesn’t consider such function calls for inlining. “ ghccc ” - GHC convention This calling convention has been implemented specifically for use by the Glasgow Haskell Compiler (GHC) . It passes everything in registers, going to extremes to achieve this by disabling callee save registers. This calling convention should not be used lightly but only for specific situations such as an alternative to the register pinning performance technique often used when implementing functional programming languages. At the moment only X86, AArch64, and RISCV support this convention. The following limitations exist: On X86-32 only up to 4 bit type parameters are supported. No floating-point types are supported. On X86-64 only up to 10 bit type parameters and 6 floating-point parameters are supported. On AArch64 only up to 4 32-bit floating-point parameters, 4 64-bit floating-point parameters, and 10 bit type parameters are supported. RISCV64 only supports up to 11 bit type parameters, 4 32-bit floating-point parameters, and 4 64-bit floating-point parameters. This calling convention supports tail call optimization but requires both the caller and callee to use it. “ cc 11 ” - The HiPE calling convention This calling convention has been implemented specifically for use by the High-Performance Erlang (HiPE) compiler, the native code compiler of the Ericsson’s Open Source Erlang/OTP system . It uses more registers for argument passing than the ordinary C calling convention and defines no callee-saved registers. The calling convention properly supports tail call optimization but requires that both the caller and the callee use it. It uses a register pinning mechanism, similar to GHC’s convention, for keeping frequently accessed runtime components pinned to specific hardware registers. At the moment only X86 supports this convention (both 32 and 64 bit). “ anyregcc ” - Dynamic calling convention for code patching This is a special convention that supports patching an arbitrary code sequence in place of a call site. This convention forces the call arguments into registers but allows them to be dynamically allocated. This can currently only be used with calls to llvm.experimental.patchpoint because only this intrinsic records the location of its arguments in a side table. See Stack maps and patch points in LLVM . “ preserve_mostcc ” - The PreserveMost calling convention This calling convention attempts to make the code in the caller as unintrusive as possible. This convention behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. This alleviates the burden of saving and recovering a large register set before and after the call in the caller. If the arguments are passed in callee-saved registers, then they will be preserved by the callee across the call. This doesn’t apply for values returned in callee-saved registers. On X86-64 the callee preserves all general purpose registers, except for R11 and return registers, if any. R11 can be used as a scratch register. The treatment of floating-point registers (XMMs/YMMs) matches the OS’s C calling convention: on most platforms, they are not preserved and need to be saved by the caller, but on Windows, xmm6-xmm15 are preserved. On AArch64 the callee preserves all general purpose registers, except X0-X8 and X16-X18. Not allowed with nest . On RISC-V the callee preserves x5-x31 except x6, x7 and x28 registers. On LoongArch the callee preserves r4-r31 except r12-r15 and r20-r21 registers. The idea behind this convention is to support calls to runtime functions that have a hot path and a cold path. The hot path is usually a small piece of code that doesn’t use many registers. The cold path might need to call out to another function and therefore only needs to preserve the caller-saved registers, which haven’t already been saved by the caller. The PreserveMost calling convention is very similar to the cold calling convention in terms of caller/callee-saved registers, but they are used for different types of function calls. coldcc is for function calls that are rarely executed, whereas preserve_mostcc function calls are intended to be on the hot path and definitely executed a lot. Furthermore preserve_mostcc doesn’t prevent the inliner from inlining the function call. This calling convention will be used by a future version of the Objective-C runtime and should therefore still be considered experimental at this time. Although this convention was created to optimize certain runtime calls to the Objective-C runtime, it is not limited to this runtime and might be used by other runtimes in the future too. The current implementation only supports X86-64, but the intention is to support more architectures in the future. “ preserve_allcc ” - The PreserveAll calling convention This calling convention attempts to make the code in the caller even less intrusive than the PreserveMost calling convention. This calling convention also behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. This removes the burden of saving and recovering a large register set before and after the call in the caller. If the arguments are passed in callee-saved registers, then they will be preserved by the callee across the call. This doesn’t apply for values returned in callee-saved registers. On X86-64 the callee preserves all general purpose registers, except for R11. R11 can be used as a scratch register. Furthermore it also preserves all floating-point registers (XMMs/YMMs). On AArch64 the callee preserves all general purpose registers, except X0-X8 and X16-X18. Furthermore it also preserves lower 128 bits of V8-V31 SIMD floating point registers. Not allowed with nest . The idea behind this convention is to support calls to runtime functions that don’t need to call out to any other functions. This calling convention, like the PreserveMost calling convention, will be used by a future version of the Objective-C runtime and should be considered experimental at this time. “ preserve_nonecc ” - The PreserveNone calling convention This calling convention doesn’t preserve any general registers. So all general registers are caller saved registers. It also uses all general registers to pass arguments. This attribute doesn’t impact non-general purpose registers (e.g., floating point registers, on X86 XMMs/YMMs). Non-general purpose registers still follow the standard C calling convention. Currently it is for x86_64 and AArch64 only. “ cxx_fast_tlscc ” - The CXX_FAST_TLS calling convention for access functions Clang generates an access function to access C++-style Thread Local Storage (TLS). The access function generally has an entry block, an exit block and an initialization block that is run at the first time. The entry and exit blocks can access a few TLS IR variables, each access will be lowered to a platform-specific sequence. This calling convention aims to minimize overhead in the caller by preserving as many registers as possible (all the registers that are preserved on the fast path, composed of the entry and exit blocks). This calling convention behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. Given that each platform has its own lowering sequence, hence its own set of preserved registers, we can’t use the existing PreserveMost . On X86-64 the callee preserves all general purpose registers, except for RDI and RAX. “ tailcc ” - Tail callable calling convention This calling convention ensures that calls in tail position will always be tail call optimized. This calling convention is equivalent to fastcc, except for an additional guarantee that tail calls will be produced whenever possible. Tail calls can only be optimized when this, the fastcc, the GHC or the HiPE convention is used. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. “ swiftcc ” - This calling convention is used for Swift language. On X86-64 RCX and R8 are available for additional integer returns, and XMM2 and XMM3 are available for additional FP/vector returns. On iOS platforms, we use AAPCS-VFP calling convention. “ swifttailcc ” This calling convention is like swiftcc in most respects, but also the callee pops the argument area of the stack so that mandatory tail calls are possible as in tailcc . “ cfguard_checkcc ” - Windows Control Flow Guard (Check mechanism) This calling convention is used for the Control Flow Guard check function, calls to which can be inserted before indirect calls to check that the call target is a valid function address. The check function has no return value, but it will trigger an OS-level error if the address is not a valid target. The set of registers preserved by the check function, and the register containing the target address are architecture-specific. On X86 the target address is passed in ECX. On ARM the target address is passed in R0. On AArch64 the target address is passed in X15. “ cc <n> ” - Numbered convention Any calling convention may be specified by number, allowing target-specific calling conventions to be used. Target-specific calling conventions start at 64. More calling conventions can be added/defined on an as-needed basis, to support Pascal conventions or any other well-known target-independent convention. Visibility Styles ¶ All Global Variables and Functions have one of the following visibility styles: “ default ” - Default style On targets that use the ELF object file format, default visibility means that the declaration is visible to other modules and, in shared libraries, means that the declared entity may be overridden. On Darwin, default visibility means that the declaration is visible to other modules. On XCOFF, default visibility means no explicit visibility bit will be set and whether the symbol is visible (i.e “exported”) to other modules depends primarily on export lists provided to the linker. Default visibility corresponds to “external linkage” in the language. “ hidden ” - Hidd | 2026-01-13T08:49:47 |
https://forem.com/t/containers/page/13 | Containers Page 13 - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # containers Follow Hide Security for container technologies like Docker and orchestration platforms like Kubernetes. Create Post Older #containers posts 10 11 12 13 14 15 16 17 18 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu From 1.2GB to 54MB: My Docker Image Went on a Diet Hasan Ashab Hasan Ashab Hasan Ashab Follow Sep 17 '25 From 1.2GB to 54MB: My Docker Image Went on a Diet # docker # devops # performance # containers 18 reactions Comments 6 comments 3 min read Examining the impact of npm supply chain attacks on MCP Dan Barr Dan Barr Dan Barr Follow for Stacklok Sep 18 '25 Examining the impact of npm supply chain attacks on MCP # mcp # npm # security # containers 5 reactions Comments Add Comment 3 min read Best 5 Tools to Help Eliminate CVEs from Container Images Or Hillel Or Hillel Or Hillel Follow Sep 18 '25 Best 5 Tools to Help Eliminate CVEs from Container Images # containers # devops # security # cve Comments Add Comment 4 min read 100 Days of DevOps: Day 46 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 18 '25 100 Days of DevOps: Day 46 # devops # docker # containers # container 1 reaction Comments Add Comment 2 min read 100 Days of DevOps: Day 45 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 18 '25 100 Days of DevOps: Day 45 # devops # docker # container # containers 1 reaction Comments Add Comment 3 min read Docker for Data People: Simplifying Development with Containers 🦄 Maris Botero✨ 🦄 Maris Botero✨ 🦄 Maris Botero✨ Follow Sep 18 '25 Docker for Data People: Simplifying Development with Containers # containers # datascience # docker 1 reaction Comments Add Comment 2 min read Deploy Vaultwarden on Nanocl leone leone leone Follow Sep 17 '25 Deploy Vaultwarden on Nanocl # devops # containers # tutorial # security 10 reactions Comments Add Comment 5 min read Kubernetes Security: Best Practices to Protect Your Cluster Dmitry Protsenko Dmitry Protsenko Dmitry Protsenko Follow Sep 16 '25 Kubernetes Security: Best Practices to Protect Your Cluster # kubernetes # containers # cybersecurity # docker 11 reactions Comments Add Comment 17 min read Docker – Complete Learning Guide 🐳 Shanmugananthan A K Shanmugananthan A K Shanmugananthan A K Follow Sep 16 '25 Docker – Complete Learning Guide 🐳 # docker # containers # kubernetes # devops Comments Add Comment 11 min read 100 Days of DevOps: Day 44 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 16 '25 100 Days of DevOps: Day 44 # devops # linux # docker # containers 1 reaction Comments Add Comment 2 min read 100 Days of DevOps: Day 43 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 15 '25 100 Days of DevOps: Day 43 # devops # docker # containers # linux Comments Add Comment 2 min read ⚡ Lightweight Containers for Raspberry Pi in 2025 — Cut Megabytes, Boost Speed ⚡ Aleksei Aleinikov Aleksei Aleinikov Aleksei Aleinikov Follow Aug 12 '25 ⚡ Lightweight Containers for Raspberry Pi in 2025 — Cut Megabytes, Boost Speed ⚡ # iot # devops # docker # containers Comments Add Comment 1 min read 100 Days of DevOps: Day 42 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 14 '25 100 Days of DevOps: Day 42 # linux # devops # docker # containers 1 reaction Comments Add Comment 2 min read Kubernetes cluster marathon! Robert Scott Robert Scott Robert Scott Follow Sep 14 '25 Kubernetes cluster marathon! # devops # kubernetes # docker # containers 1 reaction Comments Add Comment 5 min read 100 Days of DevOps: Day 41 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 13 '25 100 Days of DevOps: Day 41 # devops # linux # containers # docker 1 reaction Comments 1 comment 2 min read 100 Days of DevOps: Day 40 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 12 '25 100 Days of DevOps: Day 40 # docker # devops # linux # containers 1 reaction Comments Add Comment 2 min read 100 Days of DevOps: Day 39 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 11 '25 100 Days of DevOps: Day 39 # devops # docker # containers # linux 2 reactions Comments Add Comment 1 min read 100 Days of DevOps: Day 38 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 10 '25 100 Days of DevOps: Day 38 # containers # devops # docker # linux 3 reactions Comments Add Comment 1 min read 100 Days of DevOps: Day 37 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 9 '25 100 Days of DevOps: Day 37 # devops # linux # docker # containers 3 reactions Comments Add Comment 1 min read First Hands-On Experience with Apple Containers! Alain Airom Alain Airom Alain Airom Follow Sep 8 '25 First Hands-On Experience with Apple Containers! # containers # opensource # containerapps # containerization 1 reaction Comments Add Comment 5 min read Unlocking Docker: The Not-So-Obvious Stuff Made Simple vatsalgupta25 vatsalgupta25 vatsalgupta25 Follow Sep 7 '25 Unlocking Docker: The Not-So-Obvious Stuff Made Simple # docker # devops # containers # kubernetes 5 reactions Comments Add Comment 6 min read 100 Days of DevOps: Day 36 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 8 '25 100 Days of DevOps: Day 36 # devops # linux # docker # containers 2 reactions Comments Add Comment 2 min read Day 16: Docker for DevOps Engineers Udoh Deborah Udoh Deborah Udoh Deborah Follow Aug 5 '25 Day 16: Docker for DevOps Engineers # 90daysdevops # docker # containers # linux 1 reaction Comments Add Comment 3 min read 100 Days of DevOps: Day 35 Wycliffe A. Onyango Wycliffe A. Onyango Wycliffe A. Onyango Follow Sep 7 '25 100 Days of DevOps: Day 35 # linux # devops # docker # containers 2 reactions Comments Add Comment 1 min read Docker Hardened Images for Python: How I Eliminated 152 Vulnerabilities in One Simple Switch Ajeet Singh Raina Ajeet Singh Raina Ajeet Singh Raina Follow Sep 6 '25 Docker Hardened Images for Python: How I Eliminated 152 Vulnerabilities in One Simple Switch # security # docker # vulnerabilities # containers Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:47 |
https://opensource.org/license/bsdpluspatent | BSD+Patent – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Special Purpose BSD+Patent Version N/A Submitted: January 13, 2016 Submitter: McCoy Smith Approved: April 4, 2017 Board minutes SPDX short identifier: BSD-2-Clause-Patent Note: This license is designed to provide: a) a simple permissive license; b) that is compatible with the GNU General Public License (GPL), version 2; and c) which also has an express patent grant included. Copyright (c) <YEAR> <COPYRIGHT HOLDERS> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Subject to the terms and conditions of this license, each copyright holder and contributor hereby grants to those receiving rights under this license a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except for failure to satisfy the conditions of this license) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer this software, where such license applies only to those patent claims, already acquired or hereafter acquired, licensable by such copyright holder or contributor that are necessarily infringed by: (a) their Contribution(s) (the licensed copyrights of copyright holders and non-copyrightable additions of contributors, in source or binary form) alone; or (b) combination of their Contribution(s) with the work of authorship to which such Contribution(s) was added by such copyright holder or contributor, if, at the time the Contribution is added, such addition causes such combination to be necessarily infringed. The patent license shall not apply to any other combinations which include the Contribution. Except as expressly stated above, no rights or licenses from any copyright holder or contributor is granted under this license, whether expressly, by implication, estoppel or otherwise. DISCLAIMER THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Donate to the OSI The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and public institutions. The Open Source Initiative (OSI) is a 501(c)3 public benefit corporation, founded in 1998. --> Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://www.facebook.com/login/web/ | Facebook에 로그인 Facebook에 로그인 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjiwoomap%252Fbuilding-a-remembering-ai-trading-agent-with-python-langgraph-and-obsidian-30hn%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://docs.suprsend.com/changelog?_gl=1*12fhh1c*_gcl_au*MTk4MjY1MzcwOC4xNzM3MjcwMDQwLjE2MTg0OTAwOC4xNzQyNDY0NTg3LjE3NDI0NjQ1ODY.*_ga*MTEwNDU5MzYxMC4xNzI5NDkxODI3*_ga_PPDYBESP2L*MTc0MjYzMDUxMC4yMDguMS4xNzQyNjMwNjM2LjIuMC4w#%F0%9F%93%9A-s3-connector-v2-0-%E2%80%94-comprehensive-notification-data-export | Product Updates - 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 Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:47 |
https://core.forem.com/t/programming/page/9 | Programming Page 9 - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 6 7 8 9 10 11 12 13 14 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:47 |
https://dev.to/this-is-angular/angular-addicts-45-signal-form-guides-ai-integrations-more-2ka9 | Angular Addicts #45: Signal Form guides, AI integrations & more - 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 Gergely Szerovay for This is Angular Posted on Jan 13 • Originally published at angularaddicts.com Angular Addicts #45: Signal Form guides, AI integrations & more # typescript # javascript # angular 👋Hey fellow Angular Addict This is the 45th issue of the Angular Addicts Newsletter, a monthly collection of carefully selected Angular resources that caught my attention. (Here are the 44th , 43rd and 42nd ) 📢 Release announcements 📢 Announcing NgRx 21: Celebrating a 10 Year Journey with a fresh new look and @ngrx/signals/events By Tim Deschryver 📢 Nx 22.3 Release: Angular 21 Support, tsgo Compiler, and Prettier v3 By Philip Fulcher 📢 Migration guide to PrimeNG v21 🤖 AI & Angular 🤖 Building an Angular Compiler using AI with Google Gemini By Brandon Roberts 🤖 Generative UI for AI Assistants: Component Control with Hashbrown By Manfred Steyer 🤖 Building an AI-Powered Alt Text Generator with Angular, Firebase AI Logic, and Gemini 3 By Connie Leung 🤖 Using AI with Angular — 2025 update By Alain Chautard 🤖 Streaming AI Speech with Gemini 2.5 Flash TTS, Angular, and Firebase By Connie Leung 📋 Signal Forms 📋 Signal Forms Guide By Stefanos Lignos 📋 Signal Forms in Angular 21 - Complete Guide By Mateusz Stefańczyk 💎 Angular Gems of December, 2025 📰 Angular Signals That Will Replace Half Your RxJS Code in 2025 By Piyali Das 📰 9 Architecture Mistakes That Quietly Kill Large Angular Codebases (And How DDD Fixes Them) By Karol Modelski 📰 Angular pipes: Time to rethink By Vyacheslav Borodin 📰 Framework-agnostic internationalization with Angular's localize tools and Nx By Edouard Bozon 📰 The Magic of deepSignal: How Angular Signal Forms Enable True Nested Reactivity By Netanel Basal 📰 Angular tests with Vitest browser mode By Jean-Baptiste Nizet 👨💻About the author My name is Gergely Szerovay , I worked as a data scientist and full-stack developer for many years, and I have been working as frontend tech lead, focusing on Angular based frontend development. As part of my role, I'm constantly following how Angular and the frontend development scene in general is evolving. To share my knowledge, I started the Angular Addicts monthly newsletter and publication in 2022, so that I can send you the best resources I come across each month. Whether you are a seasoned Angular Addict or a beginner, I got you covered. Let me know if you would like to be included as a writer. Let’s learn Angular together! Subscribe here 🔥 Angular has evolved very rapidly over the past few years, and in the past year, with the rise of generative AI, our software development workflows have also evolved rapidly. In order to closely follow the evolution of AI-assisted software development, I decided to start building AI tools in public, and publish my progress on AIBoosted.dev . Join my on this learning journey: Subscribe here 🚀 Follow me on Substack (Angular Addicts) , Substack (AIBoosted.dev) , Medium , Dev.to , Twitter or LinkedIn to learn more about Angular, and how to build AI apps with AI, Typescript, React and Angular! 🕹️Previous issues If you missed the previous issues of the newsletter, you can read them here , these are the latest 3 issues: Angular Addicts #44: Angular 21, Signal Forms, Vitest, Chat assistant integration & more Angular Addicts #43: Vitest, Signal Forms, Animations & more Angular Addicts #42: Signal Forms API, AI powered apps with Angular & more 📨 Submit your Angular resource Have you found or written an interesting Angular-related article, tweet or other resource lately? Please let me know here in the comments or send me a DM on Twitter ! I might feature it in the next Angular Addicts issue! 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 This is Angular Follow Free, open and honest Angular education. Read our welcome letter which is an open invitation for you to join. Join us as a writer More from This is Angular Ng-News 26/01: Ng-Poland Outtakes - Keynote and Q&A # webdev # programming # angular # frontend Ng-News: Angular in 2025 # webdev # programming # angular # frontend Ng-News 25/50: Auto-Destroy for Router Providers, Signal Forms # webdev # programming # angular # frontend 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:47 |
http://stromberg.dnsalias.org/~dstromberg/Intro-to-Python/ | Some Python slides Documents created for presentation to OC-Python Intro to Python 2014 ODP - compatible with Open/Libre Office Impress PDF - compatible with about any PDF viewer Generators, Iterators and Comprehensions 2014 & 2017 ODP - compatible with Open/Libre Office Impress PDF - compatible with about any PDF viewer Writing code to run on Python 2.x and 3.x. ODP - compatible with Open/Libre Office Impress PDF - compatible with about any PDF viewer A surface-level intro to PyPy ODP - compatible with Open/Libre Office Impress PDF - compatible with about any PDF viewer A comparison of Python-in-the-Browser technologies Here in HTML Common Python Pitfalls (not by me, but I re-presented it) here --> Robust Python Programs - EuroPython 2010 - Note: new link Debugger example files debugger examples Cool things in Python 3.x that aren't in 2.x: here . No one in OC Python wrote these slides, but they are nice slides . The mock module odp pdf Sturdy Python December 2017 (pylint, mypy) odp pdf Pyfilesystem2, May 1, 2018 odp pdf Python performance, Sep 4, 2018 odp pdf Python Type Annotations, March/April 2020 odp pdf Intro to Python for experienced programmers blogspot will take you to Youtube Hits: 120261 Timestamp: 2026-01-13 00:49:45 PST Back to Dan's tech tidbits You can e-mail the author with questions or comments: | 2026-01-13T08:49:47 |
https://future.forem.com/om_shree_0709/tech-pulse-weekly-tech-digestjanuary-11-2026-3bac | Tech Pulse – Weekly Tech Digest January 11, 2026 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Om Shree Posted on Jan 11 Tech Pulse – Weekly Tech Digest January 11, 2026 # ai # blockchain # security # science Welcome to this week's Tech Pulse, your digest of the seismic shifts in technology from January 4 to 10, 2026. As CES 2026 unfolded in Las Vegas, the tech world exploded with announcements. From AI companions that anticipate your needs to quantum networks going mainstream, innovation dominated every headline. Geopolitical tensions simmered over chip exports, while sustainability breakthroughs promised a greener grid. Amid the buzz, data privacy scandals and EV milestones kept things grounded. Here is your complete rundown on what mattered most. AI: Agents Take Center Stage at CES CES 2026 kicked off with AI stealing the show, evolving from simple assistants into full-fledged autonomous agents. Samsung unveiled Galaxy AI 2.0, embedding predictive agents into foldable phones and smart home ecosystems. These systems automate daily routines, such as scheduling workouts based on your calendar and health data. Google DeepMind introduced AlphaAgent, a multimodal system that integrates with smart cities for real-time traffic optimization. Pilot programs reported a 30% reduction in urban congestion. OpenAI rolled out o1-mini variants tailored for education, enabling personalized tutoring bots that adapt to individual learning styles. Microsoft integrated Copilot 3.0 into Windows 13, focusing heavily on enterprise security through encrypted, on-device processing to counter rising cyber threats. Anthropic’s Claude 4 emphasized ethical AI, featuring built-in bias audits for corporate deployments. On the investment front, Amazon poured $25 billion into AI startups through its AWS fund, prioritizing agentic tools for logistics. However, a data breach at a major AI cloud provider exposed user prompts, triggering global calls for stricter regulations. Hardware and Chips: Pushing Boundaries Nvidia dominated CES with the launch of its RTX 60-series GPUs, optimized for AI rendering with 40% efficiency gains over previous generations. TSMC announced mass production of 1nm chips, partnering with Intel to accelerate edge computing for autonomous vehicles. Apple debuted the M4 Ultra chip in Mac Pro updates, boasting major neural engine improvements for faster AR and VR simulations. IBM and DARPA revealed bio-inspired neuromorphic chips that mimic brain synapses, slashing energy consumption for AI training by 60%. China responded with Huawei’s Kirin 10K processor, claiming superiority in 5G-Advanced integration despite ongoing U.S. export scrutiny. Qualcomm acquired a startup specializing in haptic feedback technology, enhancing XR devices for more immersive metaverse experiences. Quantum and Frontier Technologies Google’s Quantum AI lab achieved a new milestone with 1,000-qubit error-corrected computations, enabling complex molecule simulations for climate modeling. China’s Pan Jianwei research team demonstrated a 500-kilometer quantum internet prototype, paving the way for virtually unhackable global networks by 2030. At CES, Honeywell showcased portable quantum sensors designed for precision navigation in drones and self-driving vehicles. Neuralink expanded human trials, implanting devices in 50 additional patients and reporting a 90% success rate in restoring basic motor functions. Boston Dynamics revealed Atlas 2.0 robots equipped with AI-driven empathy modules for elder care assistance. In biotech, CRISPR Therapeutics announced a gene-editing wearable patch for treating skin conditions. Japan’s RIKEN Institute advanced fusion research with a stable plasma containment breakthrough, bringing commercial fusion reactors closer to reality. Investments and Policy Venture capital flowed freely at CES. Sequoia Capital committed $15 billion to quantum and AI-focused funds. Elon Musk’s xAI secured a $10 billion funding round from sovereign wealth funds, accelerating development of its Colossus supercomputer cluster. Meta acquired VR firm Oculus Redux to strengthen its metaverse roadmap. On the policy front, the European Union passed AI Act 2.0, mandating transparency in agentic systems. U.S.–China chip negotiations stalled as new tariffs were imposed on advanced semiconductors amid espionage allegations. India launched a $5 billion domestic AI hardware initiative aimed at boosting national self-reliance. Sustainability and Electric Vehicles Tesla regained momentum with Cybertruck 2.0, featuring a 600-mile range and solar-integrated panels. Rivian partnered with Amazon to deploy 10,000 electric delivery vans, powered by AI route optimization. Global EV sales reached a weekly record, driven by aggressive subsidies across Europe and Asia. GE introduced floating offshore wind turbines that harness deeper ocean winds for 20% higher energy output. A Stanford-led team unveiled perovskite solar cells achieving 35% efficiency, promising cheaper and more powerful solar panels. SpaceX tested orbital solar farms, successfully beaming prototype energy to Earth-based receivers. Microsoft deployed underwater data centers off the coast of Scotland, reducing cooling energy needs by 40%. However, protests erupted in Texas over AI data centers’ rising energy demands, temporarily halting new construction projects. Quick Hits SpaceX completed a successful Starship lunar orbit test, preparing for Mars cargo missions. Verizon and AT&T expanded 6G trials, achieving 1 terabit per second speeds in laboratory environments. A UN AI Summit in Geneva focused on equitable access for developing nations. Bitcoin surged past $150,000 amid growing institutional adoption. Looking Ahead As CES wraps up, attention shifts to MWC 2026 in February, where 6G advancements and foldable devices will take center stage. Expect deeper AI-human integration, with agents managing finances, healthcare, and mental well-being. The quantum race is intensifying. The question remains, will it redefine global security? Stay plugged in. 2026 is accelerating. What story caught your attention this week? Share your thoughts in the comments. 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 Om Shree Follow Technical Evangelist | AI Researcher | Simplifying Complex AI & Agent Workflows for Developers Location India Education Jaypee University Of Information Technology Pronouns He/Him Work Founder of Shreesozo Joined Feb 27, 2025 More from Om Shree I Almost Fell for a “Last Wish” Scam : Here’s What You Need to Know # discuss # scam # security # privacy Tech Pulse: Wrapping 2025, Igniting 2026 # discuss # ai # security # science The AI Hype Reckoning: A 2025 Retrospective on the Bubble That Burst Expectations # discuss # ai # beginners # 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://jsfiddle.net/6he52mnr/1/#upvote | test 3 - JSFiddle - Code Playground over 6 years ago">AN Run --> Vote for features --> Embed fiddle on websites/blogs --> Go PRO JSFiddle - Test your JavaScript, CSS, HTML or CoffeeScript online with JSFiddle. AI Code Completion AI Code Completion is a BYOK implementation. Get your API Key → The model we use is Codestral by Mistral . We won't save your API Key in our database, it's only stored in the browser for your convinience. Your recent fiddles Collections PRO Select collections: New collection Resources URL cdnjs 2 mootools-core.min.js Remove mootools-more-compressed.js Remove Paste a direct CSS/JS URL Type a library name to fetch from CDNJS Async requests Simulating async requests: JSON /echo/json/ JSONP /echo/jsonp/ HTML /echo/html/ XML /echo/xml/ See docs for more info. Changelog JSFiddle Apps Coder Fonts Color Palette Generator CSS Flexbox Generator Sign in Code panel options Change code languages, preprocessors and plugins HTML JavaScript CSS Language HTML HAML Doctype XHTML 1.0 Strict XHTML 1.0 Transitional HTML 5 HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset Body tag Language JavaScript CoffeeScript JavaScript 1.7 Babel + JSX TypeScript CoffeeScript 2 Vue React Preact Extensions Alpine.js 2.1.2 AngularJS 1.1.1 AngularJS 1.2.1 AngularJS 1.4.8 AngularJS 2.0.0-alpha.47 Bonsai 0.4.1 Brick edge CreateJS 2013.09.25 CreateJS 2015.05.21 D3 3.x D3 4.13.0 D3 5.9.2 Dojo (nightly) Dojo 1.4.8 Dojo 1.5.6 Dojo 1.6.5 Dojo 1.7.12 Dojo 1.8.14 Dojo 1.9.11 Dojo 1.10.8 Dojo 1.11.4 Dojo 1.12.2 Ember (latest) Enyo (nightly) Enyo 2.0.1 Enyo 2.1 Enyo 2.2.0 Enyo 2.4.0 Enyo 2.5.1 Enyo 2.7.0 ExtJS 3.1.0 ExtJS 3.4.0 ExtJS 4.1.0 ExtJS 4.1.1 ExtJS 4.2.0 ExtJS 5.0.0 ExtJS 5.1.0 ExtJS 6.2.0 FabricJS 1.5.0 FabricJS 1.7.7 FabricJS 1.7.15 FabricJS 1.7.20 Inferno 1.0.0-beta9 JSBlocks (edge) KineticJS 4.0.5 KineticJS 4.3.1 Knockout.js 2.0.0 Knockout.js 2.1.0 Knockout.js 2.2.1 Knockout.js 2.3.0 Knockout.js 3.0.0 Knockout.js 3.4.2 Lo-Dash 2.2.1 Minified 1.0 beta1 MithrilJS 0.2.0 MithrilJS 1.1.6 Mootools (nightly) Mootools 1.3.2 Mootools 1.3.2 (compat) Mootools 1.4.5 Mootools 1.4.5 (compat) Mootools 1.5.1 Mootools 1.5.2 Mootools 1.5.2 (compat) Mootools 1.6.0 Mootools 1.6.0 (compat) No-Library (pure JS) OpenUI5 (latest, mobile) Paper.js 0.22 Pixi 3.0.11 Pixi 4.0.0 Processing.js 1.2.3 Processing.js 1.3.6 Processing.js 1.4.1 Processing.js 1.4.7 Prototype 1.6.1.0 Prototype 1.7.3 RactiveJS 0.7.3 Raphael 1.4 Raphael 1.5.2 Raphael 2.1.0 React 0.3.2 React 0.4.0 React 0.8.0 React 0.9.0 React 0.14.3 RightJS 2.1.1 RightJS 2.3.1 Riot 3.7.4 Shipyard (nightly) Shipyard 0.2 Thorax 2.0.0rc3 Thorax 2.0.0rc6 Three.js r54 Three.js 105 Underscore 1.3.3 Underscore 1.4.3 Underscore 1.4.4 Underscore 1.8.3 Vue (edge) Vue 1.0.12 Vue 2.2.1 WebApp Install 0.1 XTK edge YUI 2.8.0r4 YUI 3.5.0 YUI 3.6.0 YUI 3.7.3 YUI 3.8.0 YUI 3.10.1 YUI 3.14.0 YUI 3.16.0 YUI 3.17.2 Zepto 1.0rc1 jQuery (edge) jQuery 1.9.1 jQuery 2.1.3 jQuery 2.2.4 jQuery 3.2.1 jQuery 3.3.1 jQuery 3.4.1 jQuery Slim 3.2.1 jQuery Slim 3.3.1 jQuery Slim 3.4.1 jTypes 2.1.0 qooxdoo 2.0.3 qooxdoo 2.1 svg.js 2.6.5 svg.js 2.7.1 svg.js 3.0.5 script attribute Language CSS SCSS SASS PostCSS (Stage 0+) PostCSS (Stage 3+) Tailwind CSS Options --> Reset CSS <h3>HTML:</h3> <p id="result"></p> p { padding: 10px; } p { margin: 5px; border: 1px dotted #999; } fetch("/echo/html/", { method: "POST", headers: { "Content-Type": "application/x-www-form-urlencoded; charset=utf-8" }, body: "html=<a href='#'>hello world</a>" }) .then((response) => response.text()) .then((responseText) => { document.querySelector("#result").innerHTML = responseText }) .catch((error) => { console.error(error) }) This fiddle has previously unsaved changes. Apply changes Discard Color Palette Generator Generate a cool color palette with a few clicks CSS Flexbox Generator Generate your CSS Flexbox layout in the simplest of ways Coder Fonts Curated list of quality monospace fonts for coders Share or embed fiddle Customize the embeddable experience for websites Tabs: JavaScript HTML CSS Result Visual: Light Dark Embed snippet Prefer iframe? : ' readonly> No autoresizing to fit the code Render blocking of the parent page Editor settings Customize the behavior and feel of the editor Behavior Auto-run code Only auto-run code that validates Auto-save code Live code validation Hot reload CSS Hot reload HTML General Line numbers Wrap lines Indent With Spaces Code Autocomplete Indent size: 2 spaces 4 spaces Font size: 10px 11px 12px 13px 14px 15px 16px 17px 18px 19px 20px Font family: Console Console in the editor Clear console on run Your recent fiddles Recently created fiddles, including ones created while logged out JSFiddle changelog A log of all the changes made to JSFiddle – big and small. Curated list of monospace coder fonts You can now use different monospace fonts in the editor − we now have a curated list of pretty awesome fonts available including premium ones. Just open the Coder Fonts mini-app from the sidebar or from Editor settings . My current favorites are Input and Commit Mono . CSS Flexbox generator as a JSFiddle app Our CSS Flexbox generator lets you create a layout, and skip knowing the confusing properties and value names (let's be honest the W3C did not make a good job here). Not gonna lie, this was heavily inspired by flexer.dev but coded completely from scratch. Behavior change for External Resources Adding External Resources will no longer create a list of resources in the sidebar but will be injected as a LINK or SCRIPT tag inside of the HTML panel. Code Completion with additional context The Code Completion will now also have the context of all panels before suggesting code to you - so if for example you have some CSS or JS, the HTML panel will suggest code based on the other two panels. 🦄 AI Code Completion (beta) Introducing some AI sprinkle in the editor - Code Completion based on the Codestral model (by Mistral ). For now it's a BYOK implmentation which means you need to provide your own API Key − you can get it for free . Editor switch from CodeMirror to Monaco (same as VSCode) After much deliberation I've decided to make the switch from CodeMirror to Monaco . There's a few reasons for this. CodeMirror 5 is no longer being developed, and the switch to 6 would be a huge rewrite since there's not much compatibility between the two versions. Monaco itself has lots of features already built-in, things that took quite a few external plugins to get into the CodeMirror implementation. I'm incredibly thankful to Marijn for his work on CodeMirror , it has served well for many years. JSFiddle will load faster Technical debt is a drag man. Remember the time when MooTools was state-of-art JS framework? We do and so much of JSFiddle was still dependant on it till this day, but since almost all MooTools features are now available in native JS it was high-time to strip it out of the codebase. This took around a week of work, lots of testing, but it's now done. And the final package of our JS bundle is ~30% smaller . Add a new collection Collect your fiddles in collections Get a Mistral API Key A short guide to getting a free Mistral API Key. Sign up for a Mistral account, and pick the free Experiment subscription plan. Log in, and go to your organization's API Keys section. Click Create new key , fill "JSFiddle" as the name for the API key, and save. Copy the key, and paste it into JSFiddle − under the AI Code Completion in the Sidebar. Done ! AI Code Completion should now be working. Classic Columns Bottom results Right results Tabs (columns) Tabs (rows) System Light Dark Set fiddle expiration 1 day 10 days 1 month 6 months 1 year Keep forever Please Whitelist JSFiddle in your content blocker. Help keep JSFiddle free for always by one of two ways: Whitelist JSFiddle in your content blocker (two clicks) Go PRO and get access to additional PRO features → Ad-free All ads in the editor and listing pages are turned completely off. Use pre-released features You get to try and use features (like the Palette Color Generator) months before everyone else. Fiddle collections Sort and categorize your Fiddles into multiple collections. Private collections and fiddles You can make as many Private Fiddles, and Private Collections as you wish! Console Debug your Fiddle with a minimal built-in JavaScript console. Early AI features Try the AI features we're rolling out. --> Join the 4+ million users, and keep the JSFiddle dream alive. Ad-free All ads in the editor and listing pages are turned completely off. Use pre-released features You get to try and use features (like the Palette Color Generator) months before everyone else. Fiddle collections Sort and categorize your Fiddles into multiple collections. Private collections and fiddles You can make as many Private Fiddles, and Private Collections as you wish! Console Debug your Fiddle with a minimal built-in JavaScript console. JSFiddle is used by you and 4+ million other developers, in many companies ... ... and top educational institutions: Join as PRO | 2026-01-13T08:49:47 |
https://opensource.org/blog/author/mia-lykoulund | Mia Lykou Lund – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Author Archives: Mia Lykou Lund Mia Lykou is an intern at OSI with a special interest in AI governance and the political dimensions of open source. Studying Philosophy, Politics and Economics between Ca' Foscari in Venice, Italy and Groningen in the Netherlands, she seeks to understand more about the philosophical aspects of AI and how open source can make software more representative and inclusive. Open Source AI Definition – Weekly update September 23 Open Source AI Definition – Weekly update September 23 Stay in the loop on shaping Open Source AI and catch up on the latest discussions from the past week! September 23, 2024 Open Source AI Definition – Weekly update september 16 Open Source AI Definition – Weekly update september 16 Stay updated on what’s happening in the forums! September 16, 2024 Open Source AI Definition – Weekly update September 9 Open Source AI Definition – Weekly update September 9 Read all about what happened on the forums this week! September 9, 2024 Open Source AI Definition – Weekly update September 2nd Open Source AI Definition – Weekly update September 2nd Stay up to date as we approach the final phases of creating the first-ever open source AI definition! September 2, 2024 Open Source AI Definition – Weekly update August 26 Open Source AI Definition – Weekly update August 26 With the 0.0.9 draft definition published this week, we are moving closer to the first-ever definition of Open Source AI. Find out what happened this week and how you can get involved! August 26, 2024 Open Source AI Definition – Weekly update July 15 Open Source AI Definition – Weekly update July 15 Stay up to date with the Open Source AI Definition July 15, 2024 Open Source AI Definition – Weekly update July 1 Open Source AI Definition – Weekly update July 1 Catch up on the community’s discussions about the Open Source AI Definition! July 1, 2024 Open Source AI Definition – Weekly update June 24 Open Source AI Definition – Weekly update June 24 This week saw lively debate on the role of data information in AI. Dive into the key points discussed here! June 24, 2024 Open Source AI Definition – Weekly update June 17 Open Source AI Definition – Weekly update June 17 Busy? Catch up on the Open Source AI Definition here! June 17, 2024 Open Source AI Definition – Weekly update June 10 Open Source AI Definition – Weekly update June 10 This week, we continued discussions about the role of training data in open source AI. Missed it? Catch up here! June 11, 2024 Open Source AI Definition – Weekly update June 3 Open Source AI Definition – Weekly update June 3 Had a busy week? Get updated on the Open Soure AI Definition co-design process! June 3, 2024 Open Source AI Definition – Weekly update May 27 Open Source AI Definition – Weekly update May 27 Stay updated on the progress of the Open Source AI Defintion. This week, debates about acess to training data has been reopened and our FAQ page is starting to take shape! May 28, 2024 Posts pagination 1 2 3 Keep up with Open Source Please leave this field empty. Δ We’ll never share your details and you can unsubscribe with a click! Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://pyflo.net | PyFlo PyFlo Py Flo The beginners guide to becoming a Python programmer Scroll to begin PyFlo Help Blue Lessons Blue lessons are "regular" lessons. You should complete these in the order that the lesson flow prescribes. Purple Lessons Purple lessons are part of a learning branch. These have great material, but can be skipped over if desired. Bonus content! Orange Lessons Orange lessons are guided projects. These take you through the implementation of a program step-by-step, using concepts from prior lessons. → Completed Lesson. → Incomplete Lesson. → Current bookmark location. Instructor Information Contact the Author Pyflo by Benjamin Dicken is licensed under CC BY-NC-ND 4.0 | 2026-01-13T08:49:47 |
https://future.forem.com/t/digest | Digest - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # digest Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Awesome Robots Digest - Issue #14 - December 12, 2025 Bob Jiang | awesomerobots Bob Jiang | awesomerobots Bob Jiang | awesomerobots Follow Dec 16 '25 Awesome Robots Digest - Issue #14 - December 12, 2025 # digest # newsletter # robotics # ai Comments Add Comment 11 min read loading... trending guides/resources Awesome Robots Digest - Issue #14 - December 12, 2025 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://www.apereo.org/news/2025/open-source-higher-ed-early-findings-apereos-osshe-study-and-how-you-can-get-involved | Open Source in Higher Ed: Early Findings from Apereo’s OSSHE Study — and How You Can Get Involved | Apereo Foundation Skip to main content Secondary navigation (for desktop) News Software Projects Contact Donate Search Main navigation About Who We Are Values Governance Board of Directors Board Alumni Staff Programs Our Programs Services & Support Software Projects Strategy Incubation Dolphin Awards Community Resources Events Micro Conferences Apereo Conferences Events Calendar Community Our Community Our Community Members Value Proposition Communities of Interest Working Groups Volunteers Newsletter Join Us Why Join Apereo? Community Members Foundation Members Institutional Members Sustaining Members Commercial Members Friends of Apereo Donate Secondary navigation (for mobile) News Software Projects Contact Donate User account menu (for mobile) Log in Breadcrumb Apereo Apereo News Open Source In Higher Ed: Early Findings From Apereo’s OSSHE Study — and How You Can Get Involved Open Source in Higher Ed: Early Findings from Apereo’s OSSHE Study — and How You Can Get Involved Image December 5, 2025 Apereo Communications Over the past year, Apereo has been exploring a question at the heart of our mission: What does the landscape of open source software (OSS) in higher education truly look like today—and what does the sector need next? We’re pleased to share early insights from the Open Source Software in Higher Education (OSSHE) Preliminary Report, an exploratory study that points to both exciting momentum and critical opportunities for collaboration. What We Studied The preliminary research integrates: A survey of IT leaders and practitioners conducted at the 2024 EDUCAUSE Conference A BuiltWith scan of 5,259 .edu domains A review of past sector research (Campus Computing Project, EDUCAUSE, IMS Global) Comparative insights from government and industry OSS adoption studies These combined sources provide the strongest snapshot we’ve had in years of how OSS is used—and perceived—across higher education. Key Early Findings 1. OSS is deeply embedded across higher education 89% of .edu domains use at least one OSS technology More than 26,000 OSS installations were identified 74 different OSS technologies surfaced, spanning infrastructure, applications, and learning environments 2. Practitioners significantly shape campus technology decisions 78% of respondents participate in software selection More than half support OSS at the technical or operational level OSS adoption is no longer just “bottom-up”—it’s institutionally influential 3. Favorability toward OSS is rising 58% reported an increasingly positive view over the past year Only 3% reported a decline 4. OSS is becoming strategically important 75% believe OSS will grow in importance over the next 3–5 years No respondents predicted declining OSS use in any campus domain 5. Yet most campuses lack an OSS strategy 66% reported no formal institutional strategy for OSS This strategy gap emerged as one of the most important themes—and one that may shape the next decade of institutional technology planning What This Means: The Sector Needs a Larger, Collaborative Study Although preliminary, the findings strongly indicate that a broader, multi-organization study is necessary to understand needs, barriers, and opportunities across higher education. Apereo is preparing to move into this next phase—and we are inviting our community to help shape it. How the Apereo Community Can Participate 1. Join the Research Effort - We’re seeking: Co-authors (from nonprofits, educational institutions, and open infrastructure projects) Contributors with expertise in survey design, data analysis, or qualitative research 2. Expand the Respondent Pool - When the next survey cycle launches, help us gather a larger and more representative sample by: Sharing the survey across your networks Encouraging colleagues in IT, research, libraries, OSPOs, and academic units to participate 3. Help Us Socialize the Report - Spread awareness of the preliminary findings through: Campus listservs Professional groups Conferences and working groups OSPO and open infrastructure communities 4. Explore Sponsorship or Funding Partnerships - To scale the study, we’ll need support for: Data collection Visualization and analysis Publication and dissemination Apereo welcomes interest from: Commercial partners Philanthropic funders Research-support organizations 5. Provide Feedback - Your insights as Apereo members matter. If you have questions, concerns, or suggestions about the preliminary report, or wish to contribute to shaping the full study. Join Us in Advancing Open Source in Higher Education The early findings make one thing clear: OSS is critical to the future of higher education, but the sector needs coordinated research, strategy, and community action to realize its full potential. We hope Apereo members will help lead this next chapter. To share your interest or ask questions, simply reply to this newsletter or reach out to Patrick directly at ed@apereo.org Thank you for supporting open source and for advancing this important work with us. Read the full report in the Community Resources section of the Apereo website. Announcement Community Footer Join Apereo Communications Donate Membership News Except where otherwise noted, this site and its content are licensed by the Apereo Foundation under the Creative Commons Attribution 4.0 United States License. Some of the content on this site has been generated with the help of ChatGPT. © 2024 Apereo Foundation User account menu (for desktop) Log in | 2026-01-13T08:49:47 |
https://core.forem.com/t/programming/page/15 | Programming Page 15 - Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 12 13 14 15 16 17 18 19 20 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:47 |
https://reviews.llvm.org/D78862 | ⚙ D78862 [IR] Convert null-pointer-is-valid into an enum attribute Page Menu Home Phabricator This is an archive of the discontinued LLVM Phabricator instance. Paths Table of Contents t - clang/ - lib/CodeGen/ - CodeGen/ - CGCall.cpp - test/CodeGen/ - CodeGen/ - delete-null-pointer-checks.c - llvm/ - docs/ - LangRef.rst - include/llvm/ - llvm/ - Bitcode/ - LLVMBitCodes.h - IR/ - Attributes.td - AutoUpgrade.h - lib/ - AsmParser/ - LLLexer.cpp - LLParser.cpp - LLToken.h - Bitcode/ - Reader/ 1/1 BitcodeReader.cpp - Writer/ - BitcodeWriter.cpp - IR/ - Attributes.cpp - AutoUpgrade.cpp - Function.cpp - Verifier.cpp - Transforms/Utils/ - Utils/ - CodeExtractor.cpp - test/ - Analysis/ - MemorySSA/ - cyclicphi.ll - ValueTracking/ - assume.ll - Bitcode/ - attributes.ll - Transforms/ - Attributor/ - IPConstantProp/ - PR26044.ll - align.ll - nocapture-1.ll - nonnull.ll - norecurse.ll - undefined_behavior.ll - CorrelatedValuePropagation/ - non-null.ll - FunctionAttrs/ - nocapture.ll - nonnull.ll - GVN/PRE/ - PRE/ - 2018-06-08-pre-load-dbgloc-no-null-opt.ll - GlobalOpt/ - MallocSROA-section-no-null-opt.ll - heap-sra-1-no-null-opt.ll - heap-sra-1.ll - heap-sra-2-no-null-opt.ll - heap-sra-2.ll - heap-sra-3-no-null-opt.ll - heap-sra-3.ll - heap-sra-4-no-null-opt.ll - heap-sra-4.ll - heap-sra-phi-no-null-opt.ll - heap-sra-phi.ll - load-store-global-no-null-opt.ll - malloc-promote-1-no-null-opt.ll - malloc-promote-1.ll - malloc-promote-2-no-null-opt.ll - malloc-promote-2.ll - storepointer-compare-no-null-opt.ll - storepointer-no-null-opt.ll - IPConstantProp/ - PR26044.ll - Inline/ - attributes.ll - InstCombine/ - atomic.ll - invariant.group.ll - invoke.ll - lifetime-no-null-opt.ll - load.ll - mem-deref-bytes.ll - memchr.ll - memcpy-addrspace.ll - memcpy-from-global.ll - memrchr.ll - select.ll - store.ll - strchr-1.ll - strcpy_chk-64.ll - strlen-1.ll - strncat-2.ll - strncmp-1.ll - strrchr-1.ll - strstr-1.ll - wcslen-1.ll - InstSimplify/ - compare.ll - LoopIdiom/ - pr28196.ll - LoopVersioning/ - lcssa.ll - SimplifyCFG/ - UnreachableEliminate.ll - invoke.ll - phi-undef-loadstore.ll - trap-no-null-opt-debugloc.ll - trapping-load-unreachable.ll - Util/ - assume-builder.ll - mlir/test/Target/ - test/ - Target/ - llvmir.mlir Hide Panel f Keyboard Reference ? Differential D78862 [IR] Convert null-pointer-is-valid into an enum attribute Closed Public Authored by nikic on Apr 25 2020, 7:00 AM. Download Raw Diff Details Reviewers jdoerfert manojgupta efriedma sstefan1 Commits rGf89f7da999f3: [IR] Convert null-pointer-is-valid into an enum attribute Summary The "null-pointer-is-valid" attribute needs to be checked by many pointer-related combines. To make the check more efficient, convert it from a string into an enum attribute. While D78859 already makes the check for the attribute cheaper, this is another 0.4% improvement . Diff Detail Repository rG LLVM Github Monorepo Event Timeline nikic created this revision. Apr 25 2020, 7:00 AM Herald added a project: Restricted Project . · View Herald Transcript Apr 25 2020, 7:00 AM Herald added subscribers: llvm-commits , dexonsmith , steven_wu , hiraditya . · View Herald Transcript xbolva00 added a subscriber: xbolva00 . Apr 25 2020, 7:55 AM Comment Actions Just wondering if this allso enables attribute ((null_pointer_is_valid)) in Clang? Harbormaster failed remote builds in B54677: Diff 260092 ! Apr 25 2020, 7:56 AM nikic added a comment. Apr 25 2020, 8:10 AM Comment Actions @xbolva00 This should not change any front-end behavior. I believe in clang this is controlled by -fno-delete-null-pointer-checks . nikic updated this revision to Diff 260105 . Apr 25 2020, 8:35 AM Comment Actions Update tests Herald added a reviewer: jdoerfert . · View Herald Transcript Apr 25 2020, 8:35 AM Herald added a reviewer: sstefan1 . · View Herald Transcript Herald added a reviewer: ftynse . · View Herald Transcript Herald added a project: Restricted Project . · View Herald Transcript Herald added subscribers: cfe-commits , Kayjukh , frgossen and 15 others . · View Herald Transcript arsenm added a subscriber: arsenm . Apr 25 2020, 9:20 AM Comment Actions FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed arsenm added a comment. Apr 25 2020, 9:21 AM Comment Actions In D78862#2003684 , @arsenm wrote: FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed Also would be address space specific Harbormaster failed remote builds in B54685: Diff 260105 ! Apr 25 2020, 9:32 AM nikic added a comment. Apr 25 2020, 10:15 AM Comment Actions In D78862#2003684 , @arsenm wrote: FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed Is this change planned more for the near term or the long term? I'm not really familiar with ongoing addrspace related work. nikic added a comment. Apr 26 2020, 1:04 AM Comment Actions @arsenm If the null-pointer-is-valid attribute is moved into the data layout, I'm wondering how Clang's -fno-delete-null-pointer-checks option would work or what it would be replaced with. In Rust it is possible to define a custom target, which also defines a custom data-layout, though I think that also needs to be compatible with the base target. I couldn't find any information on how to use a custom data layout in Clang. As such, I suspect that to preserve existing functionality we'd need support both for specifying this per-addrspace in the DL and as a function attribute. ftynse resigned from this revision. Apr 27 2020, 4:40 AM nikic edited reviewers, added: manojgupta , efriedma ; removed: sstefan1 , ftynse . Apr 28 2020, 11:53 AM Herald added a reviewer: sstefan1 . · View Herald Transcript Apr 28 2020, 11:53 AM nikic edited the summary of this revision. (Show Details) Apr 28 2020, 11:54 AM manojgupta added a comment. Apr 28 2020, 2:14 PM Comment Actions @nikic Thanks for the work. In D78862#2003684 , @arsenm wrote: FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed @arsenm Is there any work planned on moving to data layout? Moving to data layout may affect cross TU inlining e.g. LTO where 1 TU is compiled with -fno-delete-null-pointer-checks and other TU is not. There might be other potential impact that we might not know yet. jdoerfert added a comment. Apr 30 2020, 6:04 AM Comment Actions I think this is an improvement over the status quo and it looks fine to me. @arsenm I agree that we should tie this to the data layout (or at least should try) but I guess there are open questions to answer and code to write. I propose to accept this and work on the DL patch after. WDYT? In D78862#2008831 , @manojgupta wrote: @nikic Thanks for the work. In D78862#2003684 , @arsenm wrote: FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed @arsenm Is there any work planned on moving to data layout? Moving to data layout may affect cross TU inlining e.g. LTO where 1 TU is compiled with -fno-delete-null-pointer-checks and other TU is not. There might be other potential impact that we might not know yet. If we link modules with mismatching data layouts we can/should deal with this by utilizing more address spaces. That is, change the address space in one module to a fresh one to keep the properties alive. There need to be rules for this and infrastructure but something similar might be needed for heterogeneous IR modules soon. Different story though. We can also combine the attribute and the data layout if necessary, though I'm not a fan. llvm/lib/Bitcode/Reader/BitcodeReader.cpp 1304–1305 I guess this change can go in as NFC simplification right away. nikic updated this revision to Diff 261279 . Apr 30 2020, 10:22 AM nikic marked an inline comment as done. Comment Actions Rebase over committed NFC changes. Harbormaster failed remote builds in B55332: Diff 261279 ! Apr 30 2020, 11:15 AM nikic updated this revision to Diff 261375 . Apr 30 2020, 3:11 PM Comment Actions Fix rebase mistake in test Harbormaster failed remote builds in B55381: Diff 261375 ! Apr 30 2020, 4:07 PM nikic added a comment. May 8 2020, 1:15 AM Comment Actions Ping Herald added a subscriber: stephenneuendorffer . · View Herald Transcript May 8 2020, 1:15 AM arsenm added a comment. May 8 2020, 10:48 AM Comment Actions In D78862#2012560 , @jdoerfert wrote: I think this is an improvement over the status quo and it looks fine to me. @arsenm I agree that we should tie this to the data layout (or at least should try) but I guess there are open questions to answer and code to write. I propose to accept this and work on the DL patch after. WDYT? Seems ok, but it's still burning an enum value which I guess isn't super important. With the datalayout property, we might really want the inverse attribute In D78862#2008831 , @manojgupta wrote: @nikic Thanks for the work. In D78862#2003684 , @arsenm wrote: FWIW I think this attribute should be replaced with a data layout property, so this would eventually be removed @arsenm Is there any work planned on moving to data layout? Moving to data layout may affect cross TU inlining e.g. LTO where 1 TU is compiled with -fno-delete-null-pointer-checks and other TU is not. There might be other potential impact that we might not know yet. If we link modules with mismatching data layouts we can/should deal with this by utilizing more address spaces. That is, change the address space in one module to a fresh one to keep the properties alive. There need to be rules for this and infrastructure but something similar might be needed for heterogeneous IR modules soon. Different story though. We can also combine the attribute and the data layout if necessary, though I'm not a fan. This sounds really problematic and would require way more knowledge of target address spaces. I don't think this will work jdoerfert accepted this revision. May 14 2020, 9:21 PM Comment Actions In D78862#2027254 , @arsenm wrote: In D78862#2012560 , @jdoerfert wrote: I think this is an improvement over the status quo and it looks fine to me. @arsenm I agree that we should tie this to the data layout (or at least should try) but I guess there are open questions to answer and code to write. I propose to accept this and work on the DL patch after. WDYT? Seems ok, but it's still burning an enum value which I guess isn't super important. With the datalayout property, we might really want the inverse attribute Given that we lifted the limits on enum attributes I don't think this cost is high. Since we do not have a scheduled alternative, I think this should land. This revision is now accepted and ready to land. May 14 2020, 9:21 PM Herald added subscribers: jurahul , kuter . · View Herald Transcript May 14 2020, 9:21 PM Closed by commit rGf89f7da999f3: [IR] Convert null-pointer-is-valid into an enum attribute (authored by nikic ). · Explain Why May 15 2020, 10:52 AM This revision was automatically updated to reflect the committed changes. Revision Contents Files History Commits Path Size clang/ lib/ CodeGen/ CGCall.cpp 2 lines test/ CodeGen/ delete-null-pointer-checks.c 4 lines llvm/ docs/ LangRef.rst 4 lines include/ llvm/ Bitcode/ LLVMBitCodes.h 1 line IR/ Attributes.td 3 lines AutoUpgrade.h 5 lines lib/ AsmParser/ LLLexer.cpp 1 line LLParser.cpp 2 lines LLToken.h 1 line Bitcode/ Reader/ BitcodeReader.cpp 4 lines Writer/ BitcodeWriter.cpp 2 lines IR/ Attributes.cpp 6 lines AutoUpgrade.cpp 14 lines Function.cpp 4 lines Verifier.cpp 1 line Transforms/ Utils/ CodeExtractor.cpp 1 line test/ Analysis/ MemorySSA/ cyclicphi.ll 2 lines ValueTracking/ assume.ll 2 lines Bitcode/ attributes.ll 7 lines Transforms/ Attributor/ IPConstantProp/ PR26044.ll 2 lines align.ll 2 lines nocapture-1.ll 2 lines nonnull.ll 2 lines norecurse.ll 4 lines undefined_behavior.ll 8 lines CorrelatedValuePropagation/ non-null.ll 2 lines FunctionAttrs/ nocapture.ll 2 lines nonnull.ll 2 lines GVN/ PRE/ 2018-06-08-pre-load-dbgloc-no-null-opt.ll 2 lines GlobalOpt/ MallocSROA-section-no-null-opt.ll 2 lines heap-sra-1-no-null-opt.ll 2 lines heap-sra-1.ll 2 lines heap-sra-2-no-null-opt.ll 2 lines heap-sra-2.ll 2 lines heap-sra-3-no-null-opt.ll 2 lines heap-sra-3.ll 2 lines heap-sra-4-no-null-opt.ll 2 lines heap-sra-4.ll 2 lines heap-sra-phi-no-null-opt.ll 2 lines heap-sra-phi.ll 2 lines load-store-global-no-null-opt.ll 2 lines malloc-promote-1-no-null-opt.ll 2 lines malloc-promote-1.ll 2 lines malloc-promote-2-no-null-opt.ll 2 lines malloc-promote-2.ll 2 lines storepointer-compare-no-null-opt.ll 2 lines storepointer-no-null-opt.ll 2 lines IPConstantProp/ PR26044.ll 2 lines Inline/ attributes.ll 20 lines InstCombine/ atomic.ll 2 lines invariant.group.ll 2 lines invoke.ll 2 lines lifetime-no-null-opt.ll 2 lines load.ll 2 lines mem-deref-bytes.ll 6 lines memchr.ll 2 lines memcpy-addrspace.ll 2 lines memcpy-from-global.ll 2 lines memrchr.ll 2 lines select.ll 2 lines store.ll 2 lines strchr-1.ll 2 lines strcpy_chk-64.ll 2 lines strlen-1.ll 2 lines strncat-2.ll 2 lines strncmp-1.ll 2 lines strrchr-1.ll 2 lines strstr-1.ll 2 lines wcslen-1.ll 2 lines InstSimplify/ compare.ll 2 lines LoopIdiom/ pr28196.ll 2 lines LoopVersioning/ lcssa.ll 2 lines SimplifyCFG/ UnreachableEliminate.ll 2 lines invoke.ll 2 lines phi-undef-loadstore.ll 2 lines trap-no-null-opt-debugloc.ll 2 lines trapping-load-unreachable.ll 2 lines Util/ assume-builder.ll 2 lines mlir/ test/ Target/ llvmir.mlir 4 lines Diff ID Base Description Created Lint Unit Base Base Diff 1 260092 Apr 25 2020, 6:53 AM ★ ★ Diff 2 260105 367229e Update tests Apr 25 2020, 8:35 AM ★ ★ Diff 3 261279 3496d6e Rebase over committed NFC changes. Apr 30 2020, 10:22 AM ★ ★ Diff 4 261375 afc287e Fix rebase mistake in test Apr 30 2020, 3:11 PM ★ ★ Diff 5 264285 9de4ee3 rGf89f7da999f362e4213c69923328dd1033276e59 May 15 2020, 10:41 AM ★ ★ Diff 264285 clang/lib/CodeGen/CGCall.cpp Show First 20 Lines • Show All 1,738 Lines • ▼ Show 20 Lines case CodeGenOptions :: FramePointerKind :: All : break ; break ; } } FuncAttrs . addAttribute ( "frame-pointer" , FpKind ); FuncAttrs . addAttribute ( "frame-pointer" , FpKind ); FuncAttrs . addAttribute ( "less-precise-fpmad" , FuncAttrs . addAttribute ( "less-precise-fpmad" , llvm :: toStringRef ( CodeGenOpts . LessPreciseFPMAD )); llvm :: toStringRef ( CodeGenOpts . LessPreciseFPMAD )); if ( CodeGenOpts . NullPointerIsValid ) if ( CodeGenOpts . NullPointerIsValid ) FuncAttrs . addAttribute ( "null-p ointer -is-v alid " , "true" ); FuncAttrs . addAttribute ( llvm :: Attribute :: NullP ointer IsV alid ); if ( CodeGenOpts . FPDenormalMode != llvm :: DenormalMode :: getIEEE ()) if ( CodeGenOpts . FPDenormalMode != llvm :: DenormalMode :: getIEEE ()) FuncAttrs . addAttribute ( "denormal-fp-math" , FuncAttrs . addAttribute ( "denormal-fp-math" , CodeGenOpts . FPDenormalMode . str ()); CodeGenOpts . FPDenormalMode . str ()); if ( CodeGenOpts . FP32DenormalMode != CodeGenOpts . FPDenormalMode ) { if ( CodeGenOpts . FP32DenormalMode != CodeGenOpts . FPDenormalMode ) { FuncAttrs . addAttribute ( FuncAttrs . addAttribute ( "denormal-fp-math-f32" , "denormal-fp-math-f32" , CodeGenOpts . FP32DenormalMode . str ()); CodeGenOpts . FP32DenormalMode . str ()); ▲ Show 20 Lines • Show All 3,334 Lines • Show Last 20 Lines clang/test/CodeGen/delete-null-pointer-checks.c Show All 10 Lines // NULL-POINTER-VALID: load i32, i32* %[[SEL:.*]] // NULL-POINTER-VALID: load i32, i32* %[[SEL:.*]] int * Q = P ; int * Q = P ; if ( P ) { if ( P ) { Q = P + 2 ; Q = P + 2 ; } } return * Q ; return * Q ; } } // NULL-POINTER-INVALID-NOT: attributes #0 = {{.*}} " null - pointer -is- valid "="true" // NULL-POINTER-INVALID-NOT: attributes #0 = {{.*}} null _ pointer _is_ valid // NULL-POINTER-VALID: attributes #0 = {{.*}} " null - pointer -is- valid "="true" // NULL-POINTER-VALID: attributes #0 = {{.*}} null _ pointer _is_ valid llvm/docs/LangRef.rst This file is larger than 256 KB, so syntax highlighting is disabled by default. Show First 20 Lines • Show All 1,574 Lines • ▼ Show 20 Lines ``nosync`` the behavior is undefined. the behavior is undefined. ``nounwind`` ``nounwind`` This function attribute indicates that the function never raises an This function attribute indicates that the function never raises an exception. If the function does raise an exception, its runtime exception. If the function does raise an exception, its runtime behavior is undefined. However, functions marked nounwind may still behavior is undefined. However, functions marked nounwind may still trap or generate asynchronous exceptions. Exception handling schemes trap or generate asynchronous exceptions. Exception handling schemes that are recognized by LLVM to handle asynchronous exceptions, such that are recognized by LLVM to handle asynchronous exceptions, such as SEH, will still provide their implementation defined semantics. as SEH, will still provide their implementation defined semantics. `` " null - pointer -is- valid " `` ``null _ pointer _is_ valid`` If `` " null - pointer -is- valid " `` is set to ``"true"``, the n ``null`` address If ``null _ pointer _is_ valid`` is set , then the ``null`` address in address-space 0 is considered to be a valid address for memory loads and in address-space 0 is considered to be a valid address for memory loads and stores. Any analysis or optimization should not treat dereferencing a stores. Any analysis or optimization should not treat dereferencing a pointer to ``null`` as undefined behavior in this function. pointer to ``null`` as undefined behavior in this function. Note: Comparing address of a global variable to ``null`` may still Note: Comparing address of a global variable to ``null`` may still evaluate to false because of a limitation in querying this attribute inside evaluate to false because of a limitation in querying this attribute inside constant expressions. constant expressions. ``optforfuzzing`` ``optforfuzzing`` This attribute indicates that this function should be optimized This attribute indicates that this function should be optimized ▲ Show 20 Lines • Show All 18,251 Lines • Show Last 20 Lines llvm/include/llvm/Bitcode/LLVMBitCodes.h Show First 20 Lines • Show All 631 Lines • ▼ Show 20 Lines enum AttributeKindCodes { ATTR_KIND_SPECULATIVE_LOAD_HARDENING = 59 , ATTR_KIND_SPECULATIVE_LOAD_HARDENING = 59 , ATTR_KIND_IMMARG = 60 , ATTR_KIND_IMMARG = 60 , ATTR_KIND_WILLRETURN = 61 , ATTR_KIND_WILLRETURN = 61 , ATTR_KIND_NOFREE = 62 , ATTR_KIND_NOFREE = 62 , ATTR_KIND_NOSYNC = 63 , ATTR_KIND_NOSYNC = 63 , ATTR_KIND_SANITIZE_MEMTAG = 64 , ATTR_KIND_SANITIZE_MEMTAG = 64 , ATTR_KIND_PREALLOCATED = 65 , ATTR_KIND_PREALLOCATED = 65 , ATTR_KIND_NO_MERGE = 66 , ATTR_KIND_NO_MERGE = 66 , ATTR_KIND_NULL_POINTER_IS_VALID = 67 , }; }; enum ComdatSelectionKindCodes { enum ComdatSelectionKindCodes { COMDAT_SELECTION_KIND_ANY = 1 , COMDAT_SELECTION_KIND_ANY = 1 , COMDAT_SELECTION_KIND_EXACT_MATCH = 2 , COMDAT_SELECTION_KIND_EXACT_MATCH = 2 , COMDAT_SELECTION_KIND_LARGEST = 3 , COMDAT_SELECTION_KIND_LARGEST = 3 , COMDAT_SELECTION_KIND_NO_DUPLICATES = 4 , COMDAT_SELECTION_KIND_NO_DUPLICATES = 4 , COMDAT_SELECTION_KIND_SAME_SIZE = 5 , COMDAT_SELECTION_KIND_SAME_SIZE = 5 , Show All 14 Lines llvm/include/llvm/IR/Attributes.td Show First 20 Lines • Show All 121 Lines • ▼ Show 20 Lines def NoSync : EnumAttr<"nosync">; def NoSync : EnumAttr<"nosync">; /// Disable Indirect Branch Tracking. /// Disable Indirect Branch Tracking. def NoCfCheck : EnumAttr<"nocf_check">; def NoCfCheck : EnumAttr<"nocf_check">; /// Function doesn't unwind stack. /// Function doesn't unwind stack. def NoUnwind : EnumAttr<"nounwind">; def NoUnwind : EnumAttr<"nounwind">; /// Null pointer in address space zero is valid. def NullPointerIsValid : EnumAttr<"null_pointer_is_valid">; /// Select optimizations for best fuzzing signal. /// Select optimizations for best fuzzing signal. def OptForFuzzing : EnumAttr<"optforfuzzing">; def OptForFuzzing : EnumAttr<"optforfuzzing">; /// opt_size. /// opt_size. def OptimizeForSize : EnumAttr<"optsize">; def OptimizeForSize : EnumAttr<"optsize">; /// Function must not be optimized. /// Function must not be optimized. def OptimizeNone : EnumAttr<"optnone">; def OptimizeNone : EnumAttr<"optnone">; ▲ Show 20 Lines • Show All 140 Lines • Show Last 20 Lines llvm/include/llvm/IR/AutoUpgrade.h Show First 20 Lines • Show All 86 Lines • ▼ Show 20 Lines namespace llvm { /// Upgrade the loop attachment metadata node. /// Upgrade the loop attachment metadata node. MDNode * upgradeInstructionLoopAttachment ( MDNode & N ); MDNode * upgradeInstructionLoopAttachment ( MDNode & N ); /// Upgrade the datalayout string by adding a section for address space /// Upgrade the datalayout string by adding a section for address space /// pointers. /// pointers. std :: string UpgradeDataLayoutString ( StringRef DL , StringRef Triple ); std :: string UpgradeDataLayoutString ( StringRef DL , StringRef Triple ); /// Upgrade function attributes "no-frame-pointer-elim" and /// Upgrade attributes that changed format or kind. /// "no-frame-pointer-elim-non-leaf" to "frame-pointer". void UpgradeAttributes ( AttrBuilder & B ); void UpgradeFramePointerAttributes ( AttrBuilder & B ); } // End llvm namespace } // End llvm namespace #endif #endif llvm/lib/AsmParser/LLLexer.cpp Show First 20 Lines • Show All 659 Lines • ▼ Show 20 Lines #define KEYWORD(STR) \ KEYWORD ( nonlazybind ); KEYWORD ( nonlazybind ); KEYWORD ( nomerge ); KEYWORD ( nomerge ); KEYWORD ( nonnull ); KEYWORD ( nonnull ); KEYWORD ( noredzone ); KEYWORD ( noredzone ); KEYWORD ( noreturn ); KEYWORD ( noreturn ); KEYWORD ( nosync ); KEYWORD ( nosync ); KEYWORD ( nocf_check ); KEYWORD ( nocf_check ); KEYWORD ( nounwind ); KEYWORD ( nounwind ); KEYWORD ( null_pointer_is_valid ); KEYWORD ( optforfuzzing ); KEYWORD ( optforfuzzing ); KEYWORD ( optnone ); KEYWORD ( optnone ); KEYWORD ( optsize ); KEYWORD ( optsize ); KEYWORD ( preallocated ); KEYWORD ( preallocated ); KEYWORD ( readnone ); KEYWORD ( readnone ); KEYWORD ( readonly ); KEYWORD ( readonly ); KEYWORD ( returned ); KEYWORD ( returned ); KEYWORD ( returns_twice ); KEYWORD ( returns_twice ); ▲ Show 20 Lines • Show All 485 Lines • Show Last 20 Lines llvm/lib/AsmParser/LLParser.cpp This file is larger than 256 KB, so syntax highlighting is disabled by default. Show First 20 Lines • Show All 1,310 Lines • ▼ Show 20 Lines while (true) { case lltok::kw_nonlazybind: B.addAttribute(Attribute::NonLazyBind); break; case lltok::kw_nonlazybind: B.addAttribute(Attribute::NonLazyBind); break; case lltok::kw_nomerge: B.addAttribute(Attribute::NoMerge); break; case lltok::kw_nomerge: B.addAttribute(Attribute::NoMerge); break; case lltok::kw_noredzone: B.addAttribute(Attribute::NoRedZone); break; case lltok::kw_noredzone: B.addAttribute(Attribute::NoRedZone); break; case lltok::kw_noreturn: B.addAttribute(Attribute::NoReturn); break; case lltok::kw_noreturn: B.addAttribute(Attribute::NoReturn); break; case lltok::kw_nosync: B.addAttribute(Attribute::NoSync); break; case lltok::kw_nosync: B.addAttribute(Attribute::NoSync); break; case lltok::kw_nocf_check: B.addAttribute(Attribute::NoCfCheck); break; case lltok::kw_nocf_check: B.addAttribute(Attribute::NoCfCheck); break; case lltok::kw_norecurse: B.addAttribute(Attribute::NoRecurse); break; case lltok::kw_norecurse: B.addAttribute(Attribute::NoRecurse); break; case lltok::kw_nounwind: B.addAttribute(Attribute::NoUnwind); break; case lltok::kw_nounwind: B.addAttribute(Attribute::NoUnwind); break; case lltok::kw_null_pointer_is_valid: B.addAttribute(Attribute::NullPointerIsValid); break; case lltok::kw_optforfuzzing: case lltok::kw_optforfuzzing: B.addAttribute(Attribute::OptForFuzzing); break; B.addAttribute(Attribute::OptForFuzzing); break; case lltok::kw_optnone: B.addAttribute(Attribute::OptimizeNone); break; case lltok::kw_optnone: B.addAttribute(Attribute::OptimizeNone); break; case lltok::kw_optsize: B.addAttribute(Attribute::OptimizeForSize); break; case lltok::kw_optsize: B.addAttribute(Attribute::OptimizeForSize); break; case lltok::kw_readnone: B.addAttribute(Attribute::ReadNone); break; case lltok::kw_readnone: B.addAttribute(Attribute::ReadNone); break; case lltok::kw_readonly: B.addAttribute(Attribute::ReadOnly); break; case lltok::kw_readonly: B.addAttribute(Attribute::ReadOnly); break; case lltok::kw_returns_twice: case lltok::kw_returns_twice: B.addAttribute(Attribute::ReturnsTwice); break; B.addAttribute(Attribute::ReturnsTwice); break; ▲ Show 20 Lines • Show All 7,682 Lines • Show Last 20 Lines llvm/lib/AsmParser/LLToken.h Show First 20 Lines • Show All 205 Lines • ▼ Show 20 Lines enum Kind { kw_nonlazybind , kw_nonlazybind , kw_nomerge , kw_nomerge , kw_nonnull , kw_nonnull , kw_noredzone , kw_noredzone , kw_noreturn , kw_noreturn , kw_nosync , kw_nosync , kw_nocf_check , kw_nocf_check , kw_nounwind , kw_nounwind , kw_null_pointer_is_valid , kw_optforfuzzing , kw_optforfuzzing , kw_optnone , kw_optnone , kw_optsize , kw_optsize , kw_preallocated , kw_preallocated , kw_readnone , kw_readnone , kw_readonly , kw_readonly , kw_returned , kw_returned , kw_returns_twice , kw_returns_twice , ▲ Show 20 Lines • Show All 258 Lines • Show Last 20 Lines llvm/lib/Bitcode/Reader/BitcodeReader.cpp Show First 20 Lines • Show All 1,295 Lines • ▼ Show 20 Lines static uint64_t getRawAttributeMask ( Attribute :: AttrKind Val ) { } } llvm_unreachable ( "Unsupported attribute type" ); llvm_unreachable ( "Unsupported attribute type" ); } } static void addRawAttributeValue ( AttrBuilder & B , uint64_t Val ) { static void addRawAttributeValue ( AttrBuilder & B , uint64_t Val ) { if ( ! Val ) return ; if ( ! Val ) return ; for ( Attribute :: AttrKind I = Attribute :: None ; I != Attribute :: EndAttrKinds ; for ( Attribute :: AttrKind I = Attribute :: None ; I != Attribute :: EndAttrKinds ; I = Attribute :: AttrKind ( I + 1 )) { I = Attribute :: AttrKind ( I + 1 )) { if ( uint64_t A = ( Val & getRawAttributeMask ( I ))) { if ( uint64_t A = ( Val & getRawAttributeMask ( I ))) { jdoerfert Unsubmitted Done Reply Inline Actions I guess this change can go in as NFC simplification right away. jdoerfert: I guess this change can go in as NFC simplification right away. if ( I == Attribute :: Alignment ) if ( I == Attribute :: Alignment ) B . addAlignmentAttr ( 1ULL << (( A >> 16 ) - 1 )); B . addAlignmentAttr ( 1ULL << (( A >> 16 ) - 1 )); else if ( I == Attribute :: StackAlignment ) else if ( I == Attribute :: StackAlignment ) B . addStackAlignmentAttr ( 1ULL << (( A >> 26 ) -1 )); B . addStackAlignmentAttr ( 1ULL << (( A >> 26 ) -1 )); else else B . addAttribute ( I ); B . addAttribute ( I ); } } } } ▲ Show 20 Lines • Show All 150 Lines • ▼ Show 20 Lines static Attribute :: AttrKind getAttrFromCode ( uint64_t Code ) { case bitc :: ATTR_KIND_NO_RETURN : case bitc :: ATTR_KIND_NO_RETURN : return Attribute :: NoReturn ; return Attribute :: NoReturn ; case bitc :: ATTR_KIND_NOSYNC : case bitc :: ATTR_KIND_NOSYNC : return Attribute :: NoSync ; return Attribute :: NoSync ; case bitc :: ATTR_KIND_NOCF_CHECK : case bitc :: ATTR_KIND_NOCF_CHECK : return Attribute :: NoCfCheck ; return Attribute :: NoCfCheck ; case bitc :: ATTR_KIND_NO_UNWIND : case bitc :: ATTR_KIND_NO_UNWIND : return Attribute :: NoUnwind ; return Attribute :: NoUnwind ; case bitc :: ATTR_KIND_NULL_POINTER_IS_VALID : return Attribute :: NullPointerIsValid ; case bitc :: ATTR_KIND_OPT_FOR_FUZZING : case bitc :: ATTR_KIND_OPT_FOR_FUZZING : return Attribute :: OptForFuzzing ; return Attribute :: OptForFuzzing ; case bitc :: ATTR_KIND_OPTIMIZE_FOR_SIZE : case bitc :: ATTR_KIND_OPTIMIZE_FOR_SIZE : return Attribute :: OptimizeForSize ; return Attribute :: OptimizeForSize ; case bitc :: ATTR_KIND_OPTIMIZE_NONE : case bitc :: ATTR_KIND_OPTIMIZE_NONE : return Attribute :: OptimizeNone ; return Attribute :: OptimizeNone ; case bitc :: ATTR_KIND_READ_NONE : case bitc :: ATTR_KIND_READ_NONE : return Attribute :: ReadNone ; return Attribute :: ReadNone ; ▲ Show 20 Lines • Show All 169 Lines • ▼ Show 20 Lines case bitc :: PARAMATTR_GRP_CODE_ENTRY : { // ENTRY: [grpid, idx, a0, a1, ...] if ( Kind == Attribute :: ByVal ) { if ( Kind == Attribute :: ByVal ) { B . addByValAttr ( HasType ? getTypeByID ( Record [ ++ i ]) : nullptr ); B . addByValAttr ( HasType ? getTypeByID ( Record [ ++ i ]) : nullptr ); } else if ( Kind == Attribute :: Preallocated ) { } else if ( Kind == Attribute :: Preallocated ) { B . addPreallocatedAttr ( getTypeByID ( Record [ ++ i ])); B . addPreallocatedAttr ( getTypeByID ( Record [ ++ i ])); } } } } } } Upgrade FramePointer Attributes ( B ); UpgradeAttributes ( B ); MAttributeGroups [ GrpID ] = AttributeList :: get ( Context , Idx , B ); MAttributeGroups [ GrpID ] = AttributeList :: get ( Context , Idx , B ); break ; break ; } } } } } } } } Error BitcodeReader :: parseTypeTable () { Error BitcodeReader :: parseTypeTable () { ▲ Show 20 Lines • Show All 5,123 Lines • Show Last 20 Lines llvm/lib/Bitcode/Writer/BitcodeWriter.cpp Show First 20 Lines • Show All 661 Lines • ▼ Show 20 Lines static uint64_t getAttrKindEncoding ( Attribute :: AttrKind Kind ) { case Attribute :: NoReturn : case Attribute :: NoReturn : return bitc :: ATTR_KIND_NO_RETURN ; return bitc :: ATTR_KIND_NO_RETURN ; case Attribute :: NoSync : case Attribute :: NoSync : return bitc :: ATTR_KIND_NOSYNC ; return bitc :: ATTR_KIND_NOSYNC ; case Attribute :: NoCfCheck : case Attribute :: NoCfCheck : return bitc :: ATTR_KIND_NOCF_CHECK ; return bitc :: ATTR_KIND_NOCF_CHECK ; case Attribute :: NoUnwind : case Attribute :: NoUnwind : return bitc :: ATTR_KIND_NO_UNWIND ; return bitc :: ATTR_KIND_NO_UNWIND ; case Attribute :: NullPointerIsValid : return bitc :: ATTR_KIND_NULL_POINTER_IS_VALID ; case Attribute :: OptForFuzzing : case Attribute :: OptForFuzzing : return bitc :: ATTR_KIND_OPT_FOR_FUZZING ; return bitc :: ATTR_KIND_OPT_FOR_FUZZING ; case Attribute :: OptimizeForSize : case Attribute :: OptimizeForSize : return bitc :: ATTR_KIND_OPTIMIZE_FOR_SIZE ; return bitc :: ATTR_KIND_OPTIMIZE_FOR_SIZE ; case Attribute :: OptimizeNone : case Attribute :: OptimizeNone : return bitc :: ATTR_KIND_OPTIMIZE_NONE ; return bitc :: ATTR_KIND_OPTIMIZE_NONE ; case Attribute :: ReadNone : case Attribute :: ReadNone : return bitc :: ATTR_KIND_READ_NONE ; return bitc :: ATTR_KIND_READ_NONE ; ▲ Show 20 Lines • Show All 4,137 Lines • Show Last 20 Lines llvm/lib/IR/Attributes.cpp Show First 20 Lines • Show All 379 Lines • ▼ Show 20 Lines std :: string Attribute :: getAsString ( bool InAttrGrp ) const { if ( hasAttribute ( Attribute :: NonNull )) if ( hasAttribute ( Attribute :: NonNull )) return "nonnull" ; return "nonnull" ; if ( hasAttribute ( Attribute :: NoRedZone )) if ( hasAttribute ( Attribute :: NoRedZone )) return "noredzone" ; return "noredzone" ; if ( hasAttribute ( Attribute :: NoReturn )) if ( hasAttribute ( Attribute :: NoReturn )) return "noreturn" ; return "noreturn" ; if ( hasAttribute ( Attribute :: NoSync )) if ( hasAttribute ( Attribute :: NoSync )) return "nosync" ; return "nosync" ; if ( hasAttribute ( Attribute :: NullPointerIsValid )) return "null_pointer_is_valid" ; if ( hasAttribute ( Attribute :: WillReturn )) if ( hasAttribute ( Attribute :: WillReturn )) return "willreturn" ; return "willreturn" ; if ( hasAttribute ( Attribute :: NoCfCheck )) if ( hasAttribute ( Attribute :: NoCfCheck )) return "nocf_check" ; return "nocf_check" ; if ( hasAttribute ( Attribute :: NoRecurse )) if ( hasAttribute ( Attribute :: NoRecurse )) return "norecurse" ; return "norecurse" ; if ( hasAttribute ( Attribute :: NoUnwind )) if ( hasAttribute ( Attribute :: NoUnwind )) return "nounwind" ; return "nounwind" ; ▲ Show 20 Lines • Show All 1,529 Lines • ▼ Show 20 Lines if ( Caller . hasFnAttribute ( "min-legal-vector-width" )) { } else { } else { // If the callee doesn't have the attribute then we don't know anything // If the callee doesn't have the attribute then we don't know anything // and must drop the attribute from the caller. // and must drop the attribute from the caller. Caller . removeFnAttr ( "min-legal-vector-width" ); Caller . removeFnAttr ( "min-legal-vector-width" ); } } } } } } /// If the inlined function has " null - pointer -is- valid =true" attribute, /// If the inlined function has null _ pointer _is_ valid attribute, /// set this attribute in the caller post inlining. /// set this attribute in the caller post inlining. static void static void adjustNullPointerValidAttr ( Function & Caller , const Function & Callee ) { adjustNullPointerValidAttr ( Function & Caller , const Function & Callee ) { if ( Callee . nullPointerIsDefined () && ! Caller . nullPointerIsDefined ()) { if ( Callee . nullPointerIsDefined () && ! Caller . nullPointerIsDefined ()) { Caller . addFnAttr ( Callee . getFn Attribute ( "null-p ointer -is-v alid " ) ); Caller . addFnAttr ( Attribute :: NullP ointer IsV alid ); } } } } struct EnumAttr { struct EnumAttr { static bool isSet ( const Function & Fn , static bool isSet ( const Function & Fn , Attribute :: AttrKind Kind ) { Attribute :: AttrKind Kind ) { return Fn . hasFnAttribute ( Kind ); return Fn . hasFnAttribute ( Kind ); } } ▲ Show 20 Lines • Show All 48 Lines • Show Last 20 Lines llvm/lib/IR/AutoUpgrade.cpp Show First 20 Lines • Show All 4,239 Lines • ▼ Show 20 Lines std :: string llvm::UpgradeDataLayoutString ( StringRef DL , StringRef TT ) { if ( ! R . match ( DL , & Groups )) if ( ! R . match ( DL , & Groups )) return std :: string ( DL ); return std :: string ( DL ); SmallString < 1024 > Buf ; SmallString < 1024 > Buf ; std :: string Res = ( Groups [ 1 ] + AddrSpaces + Groups [ 3 ]). toStringRef ( Buf ). str (); std :: string Res = ( Groups [ 1 ] + AddrSpaces + Groups [ 3 ]). toStringRef ( Buf ). str (); return Res ; return Res ; } } void llvm::Upgrade FramePointer Attributes ( AttrBuilder & B ) { void llvm::UpgradeAttributes ( AttrBuilder & B ) { StringRef FramePointer ; StringRef FramePointer ; if ( B . contains ( "no-frame-pointer-elim" )) { if ( B . contains ( "no-frame-pointer-elim" )) { // The value can be "true" or "false". // The value can be "true" or "false". for ( const auto & I : B . td_attrs ()) for ( const auto & I : B . td_attrs ()) if ( I . first == "no-frame-pointer-elim" ) if ( I . first == "no-frame-pointer-elim" ) FramePointer = I . second == "true" ? "all" : "none" ; FramePointer = I . second == "true" ? "all" : "none" ; B . removeAttribute ( "no-frame-pointer-elim" ); B . removeAttribute ( "no-frame-pointer-elim" ); } } if ( B . contains ( "no-frame-pointer-elim-non-leaf" )) { if ( B . contains ( "no-frame-pointer-elim-non-leaf" )) { // The value is ignored. "no-frame-pointer-elim"="true" takes priority. // The value is ignored. "no-frame-pointer-elim"="true" takes priority. if ( FramePointer != "all" ) if ( FramePointer != "all" ) FramePointer = "non-leaf" ; FramePointer = "non-leaf" ; B . removeAttribute ( "no-frame-pointer-elim-non-leaf" ); B . removeAttribute ( "no-frame-pointer-elim-non-leaf" ); } } if ( ! FramePointer . empty ()) if ( ! FramePointer . empty ()) B . addAttribute ( "frame-pointer" , FramePointer ); B . addAttribute ( "frame-pointer" , FramePointer ); if ( B . contains ( "null-pointer-is-valid" )) { // The value can be "true" or "false". bool NullPointerIsValid = false ; for ( const auto & I : B . td_attrs ()) if ( I . first == "null-pointer-is-valid" ) NullPointerIsValid = I . second == "true" ; B . removeAttribute ( "null-pointer-is-valid" ); if ( NullPointerIsValid ) B . addAttribute ( Attribute :: NullPointerIsValid ); } } } llvm/lib/IR/Function.cpp Show First 20 Lines • Show All 1,635 Lines • ▼ Show 20 Lines assert ( cast < MDString > ( MD -> getOperand ( 0 )) . equals ( "function_section_prefix" ) && . equals ( "function_section_prefix" ) && "Metadata not match" ); "Metadata not match" ); return cast < MDString > ( MD -> getOperand ( 1 )) -> getString (); return cast < MDString > ( MD -> getOperand ( 1 )) -> getString (); } } return None ; return None ; } } bool Function :: nullPointerIsDefined () const { bool Function :: nullPointerIsDefined () const { return get FnAttribute ( "null-p ointer -is-v alid " ) return has FnAttribute ( Attribute :: NullP ointer IsV alid ); . getValueAsString () . equals ( "true" ); } } bool llvm :: NullPointerIsDefined ( const Function * F , unsigned AS ) { bool llvm :: NullPointerIsDefined ( const Function * F , unsigned AS ) { if ( F && F -> nullPointerIsDefined ()) if ( F && F -> nullPointerIsDefined ()) return true ; return true ; if ( AS != 0 ) if ( AS != 0 ) return true ; return true ; return false ; return false ; } } llvm/lib/IR/Verifier.cpp Show First 20 Lines • Show All 1,557 Lines • ▼ Show 20 Lines static bool isFuncOnlyAttr ( Attribute :: AttrKind Kind ) { case Attribute :: ArgMemOnly : case Attribute :: ArgMemOnly : case Attribute :: NoRecurse : case Attribute :: NoRecurse : case Attribute :: InaccessibleMemOnly : case Attribute :: InaccessibleMemOnly : case Attribute :: InaccessibleMemOrArgMemOnly : case Attribute :: InaccessibleMemOrArgMemOnly : case Attribute :: AllocSize : case Attribute :: AllocSize : case Attribute :: SpeculativeLoadHardening : case Attribute :: SpeculativeLoadHardening : case Attribute :: Speculatable : case Attribute :: Speculatable : case Attribute :: StrictFP : case Attribute :: StrictFP : case Attribute :: NullPointerIsValid : return true ; return true ; default : default : break ; break ; } } return false ; return false ; } } /// Return true if this is a function attribute that can also appear on /// Return true if this is a function attribute that can also appear on ▲ Show 20 Lines • Show All 4,204 Lines • Show Last 20 Lines llvm/lib/Transforms/Utils/CodeExtractor.cpp Show First 20 Lines • Show All 905 Lines • ▼ Show 20 Lines if ( Attr . isStringAttribute ()) { case Attribute :: MinSize : case Attribute :: MinSize : case Attribute :: NoDuplicate : case Attribute :: NoDuplicate : case Attribute :: NoFree : case Attribute :: NoFree : case Attribute :: NoImplicitFloat : case Attribute :: NoImplicitFloat : case Attribute :: NoInline : case Attribute :: NoInline : case Attribute :: NonLazyBind : case Attribute :: NonLazyBind : case Attribute :: NoRedZone : case Attribute :: NoRedZone : case Attribute :: NoUnwind : case Attribute :: NoUnwind : case Attribute :: NullPointerIsValid : case Attribute :: OptForFuzzing : case Attribute :: OptForFuzzing : case Attribute :: OptimizeNone : case Attribute :: OptimizeNone : case Attribute :: OptimizeForSize : case Attribute :: OptimizeForSize : case Attribute :: SafeStack : case Attribute :: SafeStack : case Attribute :: ShadowCallStack : case Attribute :: ShadowCallStack : case Attribute :: SanitizeAddress : case Attribute :: SanitizeAddress : case Attribute :: SanitizeMemory : case Attribute :: SanitizeMemory : case Attribute :: SanitizeThread : case Attribute :: SanitizeThread : ▲ Show 20 Lines • Show All 837 Lines • Show Last 20 Lines llvm/test/Analysis/MemorySSA/cyclicphi.ll Show First 20 Lines • Show All 146 Lines • ▼ Show 20 Lines ; CHECK-NEXT: store i64 %tmp69, i64* %g, align 8 br label %bb77 br label %bb77 bb77: ; preds = %bb68, %bb26 bb77: ; preds = %bb68, %bb26 ; CHECK: 2 = MemoryPhi({bb26,3},{bb68,1}) ; CHECK: 2 = MemoryPhi({bb26,3},{bb68,1}) ; CHECK-NEXT: br label %bb26 ; CHECK-NEXT: br label %bb26 br label %bb26 br label %bb26 } } attributes #0 = { " null - pointer -is- valid " = "true" } attributes #0 = { null _ pointer _is_ valid } llvm/test/Analysis/ValueTracking/assume.ll Show First 20 Lines • Show All 85 Lines • ▼ Show 20 Lines 3 : ; preds = %1 %4 = load i32 , i32 * %0 , align 4 %4 = load i32 , i32 * %0 , align 4 br label %5 br label %5 5 : ; preds = %1, %3 5 : ; preds = %1, %3 %6 = phi i32 [ %4 , %3 ], [ 0 , %A ] %6 = phi i32 [ %4 , %3 ], [ 0 , %A ] ret i32 %6 ret i32 %6 } } define dso_local i32 @test4b ( i32 * readonly %0 , i1 %cond ) " null - pointer -is- valid " = "true" { define dso_local i32 @test4b ( i32 * readonly %0 , i1 %cond ) null _ pointer _is_ valid { ; CHECK-LABEL: @test4b( ; CHECK-LABEL: @test4b( ; CHECK-NEXT: call void @llvm.assume(i1 true) [ "dereferenceable"(i32* [[TMP0:%.*]], i32 4) ] ; CHECK-NEXT: call void @llvm.assume(i1 true) [ "dereferenceable"(i32* [[TMP0:%.*]], i32 4) ] ; CHECK-NEXT: br i1 [[COND:%.*]], label [[A:%.*]], label [[B:%.*]] ; CHECK-NEXT: br i1 [[COND:%.*]], label [[A:%.*]], label [[B:%.*]] ; CHECK: B: ; CHECK: B: ; CHECK-NEXT: br label [[A]] ; CHECK-NEXT: br label [[A]] ; CHECK: A: ; CHECK: A: ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i32* [[TMP0]], null ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i32* [[TMP0]], null ; CHECK-NEXT: br i1 [[TMP2]], label [[TMP5:%.*]], label [[TMP3:%.*]] ; CHECK-NEXT: br i1 [[TMP2]], label [[TMP5:%.*]], label [[TMP3:%.*]] Show All 25 Lines llvm/test/Bitcode/attributes.ll Show First 20 Lines • Show All 374 Lines • ▼ Show 20 Lines } } ; CHECK: define void @f64(i32* preallocated(i32) %a) ; CHECK: define void @f64(i32* preallocated(i32) %a) define void @f64 ( i32 * preallocated ( i32 ) %a ) define void @f64 ( i32 * preallocated ( i32 ) %a ) { { ret void ret void } } ; CHECK: define void @f65() #40 define void @f65 () null_pointer_is_valid { ret void ; } ; CHECK: attributes #0 = { noreturn } ; CHECK: attributes #0 = { noreturn } ; CHECK: attributes #1 = { nounwind } ; CHECK: attributes #1 = { nounwind } ; CHECK: attributes #2 = { readnone } ; CHECK: attributes #2 = { readnone } ; CHECK: attributes #3 = { readonly } ; CHECK: attributes #3 = { readonly } ; CHECK: attributes #4 = { noinline } ; CHECK: attributes #4 = { noinline } ; CHECK: attributes #5 = { alwaysinline } ; CHECK: attributes #5 = { alwaysinline } ; CHECK: attributes #6 = { optsize } ; CHECK: attributes #6 = { optsize } ; CHECK: attributes #7 = { ssp } ; CHECK: attributes #7 = { ssp } Show All 24 Lines ; CHECK: attributes #32 = { writeonly } ; CHECK: attributes #32 = { writeonly } ; CHECK: attributes #33 = { speculatable } ; CHECK: attributes #33 = { speculatable } ; CHECK: attributes #34 = { sanitize_hwaddress } ; CHECK: attributes #34 = { sanitize_hwaddress } ; CHECK: attributes #35 = { shadowcallstack } ; CHECK: attributes #35 = { shadowcallstack } ; CHECK: attributes #36 = { willreturn } ; CHECK: attributes #36 = { willreturn } ; CHECK: attributes #37 = { nofree } ; CHECK: attributes #37 = { nofree } ; CHECK: attributes #38 = { nosync } ; CHECK: attributes #38 = { nosync } ; CHECK: attributes #39 = { sanitize_memtag } ; CHECK: attributes #39 = { sanitize_memtag } ; CHECK: attributes #40 = { null_pointer_is_valid } ; CHECK: attributes #[[NOBUILTIN]] = { nobuiltin } ; CHECK: attributes #[[NOBUILTIN]] = { nobuiltin } llvm/test/Transforms/Attributor/IPConstantProp/PR26044.ll Show First 20 Lines • Show All 62 Lines • ▼ Show 20 Lines ; CHECK-NEXT: ret i32 [[COND]] ; CHECK-NEXT: ret i32 [[COND]] ; ; entry: entry: %tobool = icmp ne i32 %p1 , 0 %tobool = icmp ne i32 %p1 , 0 %cond = select i1 %tobool , i32 %p1 , i32 %p1 %cond = select i1 %tobool , i32 %p1 , i32 %p1 ret i32 %cond ret i32 %cond } } define void @fn_no_null_opt ( i32 * %P , i1 %C ) " null - pointer -is- valid " = "true" { define void @fn_no_null_opt ( i32 * %P , i1 %C ) null _ pointer _is_ valid { ; ; ; IS__TUNIT____-LABEL: define {{[^@]+}}@fn_no_null_opt ; IS__TUNIT____-LABEL: define {{[^@]+}}@fn_no_null_opt ; IS__TUNIT____-SAME: (i32* nocapture nofree writeonly [[P:%.*]], i1 [[C:%.*]]) ; IS__TUNIT____-SAME: (i32* nocapture nofree writeonly [[P:%.*]], i1 [[C:%.*]]) ; IS__TUNIT____-NEXT: entry: ; IS__TUNIT____-NEXT: entry: ; IS__TUNIT____-NEXT: br label [[IF_END:%.*]] ; IS__TUNIT____-NEXT: br label [[IF_END:%.*]] ; IS__TUNIT____: for.cond1: ; IS__TUNIT____: for.cond1: ; IS__TUNIT____-NEXT: br i1 [[C]], label [[IF_END]], label [[EXIT:%.*]] ; IS__TUNIT____-NEXT: br i1 [[C]], label [[IF_END]], label [[EXIT:%.*]] ; IS__TUNIT____: if.end: ; IS__TUNIT____: if.end: ▲ Show 20 Lines • Show All 67 Lines • Show Last 20 Lines llvm/test/Transforms/Attributor/align.ll Show First 20 Lines • Show All 773 Lines • ▼ Show 20 Lines mt: %v = musttail call i32 @musttail_callee_1 ( i32 * %p ) %v = musttail call i32 @musttail_callee_1 ( i32 * %p ) ret i32 %v ret i32 %v exit: exit: ret i32 0 ret i32 0 } } attributes #0 = { nounwind uwtable noinline } attributes #0 = { nounwind uwtable noinline } attributes #1 = { uwtable noinline } attributes #1 = { uwtable noinline } attributes #2 = { " null - pointer -is- valid " = "true" } attributes #2 = { null _ pointer _is_ valid } llvm/test/Transforms/Attributor/nocapture-1.ll Show First 20 Lines • Show All 522 Lines • ▼ Show 20 Lines ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i8* [[TMP1]], null ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i8* [[TMP1]], null ; CHECK-NEXT: ret i1 [[TMP2]] ; CHECK-NEXT: ret i1 [[TMP2]] ; ; %1 = bitcast i32 * %x to i8 * %1 = bitcast i32 * %x to i8 * %2 = icmp eq i8 * %1 , null %2 = icmp eq i8 * %1 , null ret i1 %2 ret i1 %2 } } define i1 @captureDereferenceableOrNullICmp ( i32 * dereferenceable_or_null ( 4 ) %x ) " null - pointer -is- valid " = "true" { define i1 @captureDereferenceableOrNullICmp ( i32 * dereferenceable_or_null ( 4 ) %x ) null _ pointer _is_ valid { ; CHECK-LABEL: define {{[^@]+}}@captureDereferenceableOrNullICmp ; CHECK-LABEL: define {{[^@]+}}@captureDereferenceableOrNullICmp ; CHECK-SAME: (i32* nofree readnone dereferenceable_or_null(4) [[X:%.*]]) ; CHECK-SAME: (i32* nofree readnone dereferenceable_or_null(4) [[X:%.*]]) ; CHECK-NEXT: [[TMP1:%.*]] = bitcast i32* [[X]] to i8* ; CHECK-NEXT: [[TMP1:%.*]] = bitcast i32* [[X]] to i8* ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i8* [[TMP1]], null ; CHECK-NEXT: [[TMP2:%.*]] = icmp eq i8* [[TMP1]], null ; CHECK-NEXT: ret i1 [[TMP2]] ; CHECK-NEXT: ret i1 [[TMP2]] ; ; %1 = bitcast i32 * %x to i8 * %1 = bitcast i32 * %x to i8 * %2 = icmp eq i8 * %1 , null %2 = icmp eq i8 * %1 , null ▲ Show 20 Lines • Show All 61 Lines • Show Last 20 Lines llvm/test/Transforms/Attributor/nonnull.ll Show First 20 Lines • Show All 1,225 Lines • ▼ Show 20 Lines ; call void @use_i8_ptr_ret ( i8 * %arg ) call void @use_i8_ptr_ret ( i8 * %arg ) call void @llvm.assume ( i1 true ) [ "nonnull" ( i8 * %arg )] call void @llvm.assume ( i1 true ) [ "nonnull" ( i8 * %arg )] call void @use_i8_ptr_ret ( i8 * %arg ) call void @use_i8_ptr_ret ( i8 * %arg ) ret void ret void } } declare void @use_i8_ptr ( i8 * nofree nocapture readnone ) nounwind declare void @use_i8_ptr ( i8 * nofree nocapture readnone ) nounwind declare void @use_i8_ptr_ret ( i8 * nofree nocapture readnone ) nounwind willreturn declare void @use_i8_ptr_ret ( i8 * nofree nocapture readnone ) nounwind willreturn attributes #0 = { " null - pointer -is- valid " = "true" } attributes #0 = { null _ pointer _is_ valid } attributes #1 = { nounwind willreturn } attributes #1 = { nounwind willreturn } llvm/test/Transforms/Attributor/norecurse.ll Show First 20 Lines • Show All 205 Lines • ▼ Show 20 Lines ; CHECK-SAME: (i32 (i32)* nocapture nofree nonnull [[TMP0:%.*]], i32 [[TMP1:%.*]]) local_unnamed_addr ; CHECK-SAME: (i32 (i32)* nocapture nofree nonnull [[TMP0:%.*]], i32 [[TMP1:%.*]]) local_unnamed_addr ; CHECK-NEXT: [[TMP3:%.*]] = tail call i32 [[TMP0]](i32 [[TMP1]]) ; CHECK-NEXT: [[TMP3:%.*]] = tail call i32 [[TMP0]](i32 [[TMP1]]) ; CHECK-NEXT: ret i32 [[TMP3]] ; CHECK-NEXT: ret i32 [[TMP3]] ; ; %3 = tail call i32 %0 ( i32 %1 ) #2 %3 = tail call i32 %0 ( i32 %1 ) #2 ret i32 %3 ret i32 %3 } } ; CHECK -NOT : Function Attrs ; CHECK: Function Attrs : null_pointer_is_valid define i32 @eval_func2 ( i32 ( i32 )* , i32 ) local_unnamed_addr " null - pointer -is- valid " = "true" { define i32 @eval_func2 ( i32 ( i32 )* , i32 ) local_unnamed_addr null _ pointer _is_ valid { ; CHECK-LABEL: define {{[^@]+}}@eval_func2 ; CHECK-LABEL: define {{[^@]+}}@eval_func2 ; CHECK-SAME: (i32 (i32)* nocapture nofree [[TMP0:%.*]], i32 [[TMP1:%.*]]) local_unnamed_addr ; CHECK-SAME: (i32 (i32)* nocapture nofree [[TMP0:%.*]], i32 [[TMP1:%.*]]) local_unnamed_addr ; CHECK-NEXT: [[TMP3:%.*]] = tail call i32 [[TMP0]](i32 [[TMP1]]) ; CHECK-NEXT: [[TMP3:%.*]] = tail call i32 [[TMP0]](i32 [[TMP1]]) ; CHECK-NEXT: ret i32 [[TMP3]] ; CHECK-NEXT: ret i32 [[TMP3]] ; ; %3 = tail call i32 %0 ( i32 %1 ) #2 %3 = tail call i32 %0 ( i32 %1 ) #2 ret i32 %3 ret i32 %3 } } Show All 16 Lines llvm/test/Transforms/Attributor/undefined_behavior.ll Show First 20 Lines • Show All 43 Lines • ▼ Show 20 Lines t: %b = load i32 , i32 * null %b = load i32 , i32 * null br label %e br label %e e: e: ret void ret void } } ; Note that while the load is removed (because it's unused), the block ; Note that while the load is removed (because it's unused), the block ; is not changed to unreachable ; is not changed to unreachable define void @load_null_pointer_is_defined () " null - pointer -is- valid " = "true" { define void @load_null_pointer_is_defined () null _ pointer _is_ valid { ; CHECK-LABEL: define {{[^@]+}}@load_null_pointer_is_defined() ; CHECK-LABEL: define {{[^@]+}}@load_null_pointer_is_defined() ; CHECK-NEXT: ret void ; CHECK-NEXT: ret void ; ; %a = load i32 , i32 * null %a = load i32 , i32 * null ret void ret void } } define internal i32 * @ret_null () { define internal i32 * @ret_null () { Show All 34 Lines ; br i1 %cond , label %t , label %e br i1 %cond , label %t , label %e t: t: store i32 5 , i32 * null store i32 5 , i32 * null br label %e br label %e e: e: ret void ret vo | 2026-01-13T08:49:47 |
https://opensource.org/license/attribution-php | Attribution Assurance License – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Redundant with more popular Attribution Assurance License SPDX short identifier: AAL Copyright (c) 2002 by AUTHOR PROFESSIONAL IDENTIFICATION * URL “PROMOTIONAL SLOGAN FOR AUTHOR’S PROFESSIONAL PRACTICE” All Rights Reserved ATTRIBUTION ASSURANCE LICENSE (adapted from the original BSD license) Redistribution and use in source and binary forms, with or without modification, are permitted provided that the conditions below are met. These conditions require a modest attribution to <AUTHOR> (the “Author”), who hopes that its promotional value may help justify the thousands of dollars in otherwise billable time invested in writing this and other freely available, open-source software. 1. Redistributions of source code, in whole or part and with or without modification (the “Code”), must prominently display this GPG-signed text in verifiable form. 2. Redistributions of the Code in binary form must be accompanied by this GPG-signed text in any documentation and, each time the resulting executable program or a program dependent thereon is launched, a prominent display (e.g., splash screen or banner text) of the Author’s attribution information, which includes: (a) Name (“AUTHOR”), (b) Professional identification (“PROFESSIONAL IDENTIFICATION”), and (c) URL (“URL”). 3. Neither the name nor any trademark of the Author may be used to endorse or promote products derived from this software without specific prior written permission. 4. Users are entirely responsible, to the exclusion of the Author and any other persons, for compliance with (1) regulations set by owners or administrators of employed equipment, (2) licensing terms of any other software, and (3) local regulations regarding use, including those regarding import, export, and use of encryption software. THIS FREE SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR ANY CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, EFFECTS OF UNAUTHORIZED OR MALICIOUS NETWORK ACCESS; PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. –End of License Originally written by Edwin A. Suominen for licensing his PRIVARIA secure networking software (see -->www.privaria.org -->). The author, who is not an attorney, places this license template into the public domain along with a complete disclaimer of any warranty or responsibility for its content or legal efficacy. You may use or modify the language freely, but entirely at your own risk. Donate to the OSI The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and public institutions. The Open Source Initiative (OSI) is a 501(c)3 public benefit corporation, founded in 1998. --> Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://techbeamers.com/python-tutorial-step-by-step/ | Free Python Course with 100+ Basic to Advanced Tutorials tech beamers Python Lab Python Online Compiler Python Code Checker Python Coding Exercises Python Coding Quizzes SQL Practice Selenium Practice SW Guides tech beamers Search Python Lab Python Online Compiler Python Code Checker Python Coding Exercises Python Coding Quizzes SQL Practice Selenium Practice SW Guides Follow US © TechBeamers. All Rights Reserved. Python Tutorial for Beginners and Experienced – Start Now Python Step-by-Step Learning Path Python is a popular programming language known for its unique features and advantages over languages like Java and C++. Our Python tutorial is designed for both beginners and experienced professionals, covering topics such as loops, strings, lists, dictionaries, tuples, dates, times, and file handling. 5 Dev Tools You Must Try Once - 100% Free Professional-grade resources to help in your work Python Compiler Run code in browser Python Code Checker Check code syntax & logic Code Quality Tools Analyze & improve code Python Tutorials for Practice Python Syntax Guide Python List, Tuple, Dictionary Exercises (10 Each) 100+ Python Interview Questions and Answers (PDF, 2025) Python Practice Exercises for Beginners 15 Free and Fun Coding Games for Beginners and Adults Who Want to Learn Programming Python Game Code: The Ultimate Pygame Guide 20 Pseudo Code Questions and Answers Python Interview Questions for Experienced with PDF Playwright Python Quick Start Guide Python: 30 Programming Tips & Tricks How to Check If a List Is Empty in Python – Complete Guide Python XOR Operator (^): Learn with Simple Examples Python List Python Keywords, Identifiers, & Variables 50 Best Exercises to Master Data Structure in Python Top 50 Python Programming Interview Questions With Answers Python Socket: Create a TCP Server-Client Python Pattern Programs Exercises Multithreading in Python How to Run Python Code in Terminal Python SQL: Connect Databases & Run SQL Queries Python For Loops (with Code Examples) Selenium 4 Python Tutorial for Beginners Python Program: Check List Contains Another List Items Python Function: A Practical Guide for Beginners Python Dictionary Explained with Examples Python Range Function Top 15 Best Coding Games for Kids That Make Learning to Code Fun and Easy Python Multiline String Python Data Types Explained with Examples (Beginners Guide) Top Python Code Quality Tools to Improve Your Development Workflow Create an Android App in Python The heapq (Heap Queue) Module in Python Matplotlib Practice Online: Free Exercises Python Random IP Address Generation Python Class and Objects Python Operators: Types, Examples & Precedence Python Program to Find Sum of Two Numbers Python Tricky Coding Exercises Try-Except in Python: The Beginner’s Guide Python If-Else Statements Python Random Image Generation Python Loop Through Files in a Directory How to Find the List Shape in Python Python Arrays 44 Python Data Analyst Interview Questions Python Control Flow Exercises Generate Floating Point Range in Python Python Program: How to Sort Lists Alphabetically 25 Sampling Interview Questions and Answers to Remember Python Program to Find Factorial of a Number (7 Best Methods) Python Statements and Indentation Rules with Examples Python Generate SubArrays of an Array Top 5 Python Shell Chrome Extensions for You Python Exception Handling Python Read/Write to a File Enforcing Unsigned Integers in Python: A Complete Guide Python Linked Lists Python Program: How to Sort Array Values Python List Comprehension Python LangChain: Learn the Memory Basics Different Methods to Slice a String Python Time Functions Python Connect to PostgreSQL Database Python Program: 5 Ways to Iterate Strings Python Tuple Python Lambda Function Python Selenium Extent Report Guide Python Memory Tricks: Optimize Your Code for Efficiency in 2025 File Handling in Python Python String Functions How Do I Install PIP in Python? 3 Ways to Read a File Line by Line in Python (With Examples) Python Check Integer in Range Python String Format() Python Program: Generate Random Integer Python LangChain: A Getting Started Guide Python Switch Case Python: Pandas Get Average Of Column Or Mean Python Program: Swap Two Numbers Without a Temp Python Code to Generate Random Email Python Inheritance Guide Python Float Function Python Float Numbers Python: 12 Code Optimization Tips Python Program: Sort List in Descending Order Python Regular Expressions Python Program: Convert Lists into a Dictionary Python Dictionary Exercises Python Selenium Handle Alert Popup Python Program: Python Character Frequency Python Program: Learn to Build an IRC Bot Python Program: How to Sort List of Strings Python Small Projects for Beginners How to Get Unique Values from a List How to Add Elements of Two Lists Python: Pandas GroupBy() and Count() Methods Different Ways to Reverse a String in Python Python Datetime Functions Python Ord Function Python Set Explained Python Selenium Test Suite with Unittest Python Program: Compute Frequency of Each Word Python XRange vs Range Python Program: How to Sort Dictionary by Value Python Program: How to Sort a List of Numbers Python: Using Pandas to Read Data from CSV Files Python Join Function Explained Python: Pandas Methods to Rename Columns Python: Pandas Series and DataFrames Python String Split and More How to Install Python Packages with Requirements.txt Python Enumerate Function How to Add Multiple Lists in Python Python: Convert Python Dictionary to DataFrame Python Filter Function Python Print() Function Explained Python List Append Vs. Extend Python Random Character Generation Python Programming Mistakes Python Glob Module Methods (with Patterns) Python Socket Programming Python Dataclass Exercises Python F String How to Use String indexOf in Python Python String to Int and Back to String Python Program: Search Keys by Value in a Dictionary Python Selenium Web Page Navigation How to Remove Whitespace from a String Python Nested List Python Pylint How To Guide How to Create Dynamic QR Code in Python Python Socket: Create Multithreaded Server Python PIP Usage Simplified for You Different Methods to Compare Strings Python Selenium 4 Automation Guide Python LangChain: Create Your First Agent Python Program: 6 Ways to Generate Fibonacci Sequence Python Timestamp Functions Python Random Sampling Tutorial Python Program: How to Sort Dictionary by Key Python List All Files in a Directory Python Program: Find Possible Permutation of a String 10 Python Tips Every Beginner Should Know 40 Google Interview Questions You Need to Join Google in 2025 Python: Using Pandas to Read Large Excel Files List Remove Method Python Program: For Loop Examples Python: 20 Pandas Tips and Tricks Modules in Python with Examples Python Program: How to Sort with Lambda Cracking the Coding Interview: How a Young Girl Succeeded Python Str Function Python Program: Check List Index Out of Range Learn Python: 10 Practical Tips for Beginners Python Copy Files from a Directory Top 7 Python Interpreters to Code On the Fly! List Pop Method Python Get Current Timestamp String Python Dictionary to JSON Python Append to Dictionary Python Multiple Inheritance Python Selenium Generate Extent Report Python Get Current Working Directory Python Program: Insert Key-Value Pair in a Dictionary Python Concatenate String Exercises How to Find a Job in Python – Things You Need to Do How to Slice a List in Python Python Generators vs List Comprehensions Top 30 Data Engineer Interview Questions with Answers Python Loop Through a Dictionary Python Check Version Python Decorators Python First-Class vs Higher-Order Functions Python Floor Function Python Static Method Python Selenium WebDriver Waits Simple Android Data Analytics App in Python Python While Loop Python Important Terms Python Sorted Function Python Convert a String to an Integer List Clear Method Python Import File Python Data Classes Python LangChain: Create a Full-fledged App Python Operator Precedence Code Without Limits: The Best Online Python Compilers for Every Dev Python OrderedDict Tutorial Python Zip Function Python: 20 Data Analysis Tips&Tricks Python Class Definitions Python Check Variable Type Best Websites to Learn Python and Master Coding in 15 Days (2025) Python: Merge CSV Files Using Pandas Python Map vs List Comprehension Top 25 Python Data Science Libraries (2025) Python Random Numbers List Generation Python Program to Reverse a Number Different Ways to Append Strings in Python How to Iterate Through a Dictionary in Python List Copy Method Python Generators Python Map Function Python Shallow vs Deep Copy How to Sort List of Lists in Python Python Libraries to Connect with SQL Pass by Reference vs Pass by Value in Python How to Remove Characters from a Python String How to Concatenate Strings in Python How to Fetch the List of Popular GitHub Repos Python Increment and Decrement Operations – A Comprehensive Guide How Do You Filter a List in Python? Python Sets vs Lists Python Datetime Module How to Become a Machine Learning Engineer in 2025 (Python Roadmap) Python Program: Find Palindromes and Anagrams Python Get Last Element in List Python Multiline Comments List Index Method Python Shutil Module for Common File I/O Python: Using Pandas to Add Rows in a DataFrame Python Iterators List Insert Method List Count Method Python Guide to Connect with MongoDB Python Selenium Switch Between Windows Python Random Number Tutorial Python: Pandas to Concat Multiple DataFrame How to Reverse a List in Python Python Sorting a Dictionary Python Reduce Function Python Program: Print Diamond Pattern Using Range() Python Program: Convert a List to String Python Commenting Methods Python Selenium Switch Between Iframes Python String Strip() Python Map vs Loop Python Program: Replace Occurrences of a Character Python Program: When to Prefer Yield Over Return Python Remove Last Element from List How to Find the Length of a List Python Map and List Comprehension Tips How to Compare Two Lists in Python Python Numbers Guide Python Program: Range() to Print Alphabet Pattern Python Higher Order Functions Python Program: Generate Fibonacci using Recursion Python Merge Multiple CSVs Using File I/O List Append Method Python Remove Elements from a List List Extend Method Python Quizzes for Practice Python Quiz for Beginners Part-1 Python Multithreading Quiz Python Programming Online Skill Test Python Quiz for Beginners Part-2 Python Entry-Level Quiz For Developers Python String Handling Quiz Part-1 Python String Handling Quiz Part-2 Python File Handling Quiz Part-1 Python File Handling Quiz Part-2 Python Functions Quiz Part-1 Python Functions Quiz Part-2 Python Quiz: Classes and Objects Part 1 Python Quiz: Classes and Objects Part 2 Python Data Analysis Quiz for Beginners Python DSA Quiz – Part 1 | Core Data Structures & Algorithms MCQ Python DSA Quiz – Part 2 | Recursion & Sorting Algorithms MCQ Python DSA Quiz – Part 3 | Linked Lists, Singly & Doubly Linked List MCQ Python DSA Quiz – Part 4 | Trees & Binary Search Tree (BST) MCQ Python DSA Quiz – Part 5 | Graphs & Graph Algorithms MCQ Python Automation Practice Test for Selenium Python Exercises for Practice Most Popular This Month → Python Online Compiler → Python Code Checker → Free Python Tutorial → SQL Practice Queries → Code to Flowchart Tool → Python Syntax Guide → Python List & Dict Questions → Selenium Practice Test Page © TechBeamers. All Rights Reserved. About Contact Disclaimer Privacy Policy Terms of Use | 2026-01-13T08:49:47 |
https://shop.forem.com/collections/codenewbie#MainContent | CodeNewbie Collection – Forem Shop Skip to content Home Collections Collections DEV CodeNewbie Forem DEV Challenges View All About FAQ Log in Country/region Albania (ALL L) Andorra (EUR €) Angola (USD $) Anguilla (XCD $) Antigua & Barbuda (XCD $) Argentina (USD $) Aruba (AWG ƒ) Australia (AUD $) Austria (EUR €) Bahamas (BSD $) Bahrain (USD $) Barbados (BBD $) Belgium (EUR €) Belize (BZD $) Benin (XOF Fr) Bermuda (USD $) Bhutan (USD $) Bosnia & Herzegovina (BAM КМ) Botswana (BWP P) Bouvet Island (USD $) Brazil (USD $) British Virgin Islands (USD $) Bulgaria (EUR €) Burkina Faso (XOF Fr) Cameroon (XAF CFA) Canada (CAD $) Cape Verde (CVE $) Caribbean Netherlands (USD $) Chile (USD $) China (CNY ¥) Colombia (USD $) Comoros (KMF Fr) Cook Islands (NZD $) Croatia (EUR €) Curaçao (ANG ƒ) Cyprus (EUR €) Czechia (CZK Kč) Denmark (DKK kr.) Djibouti (DJF Fdj) Dominica (XCD $) Dominican Republic (DOP $) Equatorial Guinea (XAF CFA) Estonia (EUR €) Eswatini (USD $) Ethiopia (ETB Br) Falkland Islands (FKP £) Faroe Islands (DKK kr.) Fiji (FJD $) Finland (EUR €) France (EUR €) French Guiana (EUR €) French Polynesia (XPF Fr) Gabon (XOF Fr) Gambia (GMD D) Germany (EUR €) Ghana (USD $) Gibraltar (GBP £) Greece (EUR €) Grenada (XCD $) Guadeloupe (EUR €) Guernsey (GBP £) Guinea (GNF Fr) Guinea-Bissau (XOF Fr) Guyana (GYD $) Haiti (USD $) Heard & McDonald Islands (AUD $) Hong Kong SAR (HKD $) Hungary (HUF Ft) Iceland (ISK kr) India (INR ₹) Indonesia (IDR Rp) Ireland (EUR €) Israel (ILS ₪) Italy (EUR €) Jamaica (JMD $) Japan (JPY ¥) Jersey (USD $) Jordan (USD $) Kenya (KES KSh) Kiribati (USD $) Kuwait (USD $) Latvia (EUR €) Liechtenstein (CHF CHF) Lithuania (EUR €) Luxembourg (EUR €) Macao SAR (MOP P) Malawi (MWK MK) Malaysia (MYR RM) Maldives (MVR MVR) Malta (EUR €) Martinique (EUR €) Mauritania (USD $) Mayotte (EUR €) Mexico (USD $) Monaco (EUR €) Montserrat (XCD $) Mozambique (USD $) Namibia (USD $) Nauru (AUD $) Nepal (NPR Rs.) Netherlands (EUR €) Netherlands Antilles (ANG ƒ) New Caledonia (XPF Fr) New Zealand (NZD $) Nigeria (NGN ₦) Niue (NZD $) Norway (USD $) Oman (USD $) Papua New Guinea (PGK K) Paraguay (PYG ₲) Peru (PEN S/) Philippines (PHP ₱) Poland (PLN zł) Portugal (EUR €) Qatar (QAR ر.ق) Réunion (EUR €) Romania (RON Lei) Rwanda (RWF FRw) São Tomé & Príncipe (STD Db) Saudi Arabia (SAR ر.س) Senegal (XOF Fr) Singapore (SGD $) Sint Maarten (ANG ƒ) Slovakia (EUR €) Slovenia (EUR €) South Africa (USD $) South Korea (KRW ₩) Spain (EUR €) Sri Lanka (LKR ₨) St. Barthélemy (EUR €) St. Helena (SHP £) St. Kitts & Nevis (XCD $) St. Lucia (XCD $) St. Martin (EUR €) St. Vincent & Grenadines (XCD $) Suriname (USD $) Sweden (SEK kr) Switzerland (CHF CHF) Taiwan (TWD $) Tanzania (TZS Sh) Thailand (THB ฿) Togo (XOF Fr) Tonga (TOP T$) Trinidad & Tobago (TTD $) Turks & Caicos Islands (USD $) Tuvalu (AUD $) U.S. Outlying Islands (USD $) Uganda (UGX USh) United Arab Emirates (AED د.إ) United Kingdom (GBP £) United States (USD $) Uruguay (UYU $U) Vanuatu (VUV Vt) Vatican City (EUR €) Vietnam (VND ₫) Zambia (USD $) Update country/region Country/region USD $ | United States ALL L | Albania EUR € | Andorra USD $ | Angola XCD $ | Anguilla XCD $ | Antigua & Barbuda USD $ | Argentina AWG ƒ | Aruba AUD $ | Australia EUR € | Austria BSD $ | Bahamas USD $ | Bahrain BBD $ | Barbados EUR € | Belgium BZD $ | Belize XOF Fr | Benin USD $ | Bermuda USD $ | Bhutan BAM КМ | Bosnia & Herzegovina BWP P | Botswana USD $ | Bouvet Island USD $ | Brazil USD $ | British Virgin Islands EUR € | Bulgaria XOF Fr | Burkina Faso XAF CFA | Cameroon CAD $ | Canada CVE $ | Cape Verde USD $ | Caribbean Netherlands USD $ | Chile CNY ¥ | China USD $ | Colombia KMF Fr | Comoros NZD $ | Cook Islands EUR € | Croatia ANG ƒ | Curaçao EUR € | Cyprus CZK Kč | Czechia DKK kr. | Denmark DJF Fdj | Djibouti XCD $ | Dominica DOP $ | Dominican Republic XAF CFA | Equatorial Guinea EUR € | Estonia USD $ | Eswatini ETB Br | Ethiopia FKP £ | Falkland Islands DKK kr. | Faroe Islands FJD $ | Fiji EUR € | Finland EUR € | France EUR € | French Guiana XPF Fr | French Polynesia XOF Fr | Gabon GMD D | Gambia EUR € | Germany USD $ | Ghana GBP £ | Gibraltar EUR € | Greece XCD $ | Grenada EUR € | Guadeloupe GBP £ | Guernsey GNF Fr | Guinea XOF Fr | Guinea-Bissau GYD $ | Guyana USD $ | Haiti AUD $ | Heard & McDonald Islands HKD $ | Hong Kong SAR HUF Ft | Hungary ISK kr | Iceland INR ₹ | India IDR Rp | Indonesia EUR € | Ireland ILS ₪ | Israel EUR € | Italy JMD $ | Jamaica JPY ¥ | Japan USD $ | Jersey USD $ | Jordan KES KSh | Kenya USD $ | Kiribati USD $ | Kuwait EUR € | Latvia CHF CHF | Liechtenstein EUR € | Lithuania EUR € | Luxembourg MOP P | Macao SAR MWK MK | Malawi MYR RM | Malaysia MVR MVR | Maldives EUR € | Malta EUR € | Martinique USD $ | Mauritania EUR € | Mayotte USD $ | Mexico EUR € | Monaco XCD $ | Montserrat USD $ | Mozambique USD $ | Namibia AUD $ | Nauru NPR Rs. | Nepal EUR € | Netherlands ANG ƒ | Netherlands Antilles XPF Fr | New Caledonia NZD $ | New Zealand NGN ₦ | Nigeria NZD $ | Niue USD $ | Norway USD $ | Oman PGK K | Papua New Guinea PYG ₲ | Paraguay PEN S/ | Peru PHP ₱ | Philippines PLN zł | Poland EUR € | Portugal QAR ر.ق | Qatar EUR € | Réunion RON Lei | Romania RWF FRw | Rwanda STD Db | São Tomé & Príncipe SAR ر.س | Saudi Arabia XOF Fr | Senegal SGD $ | Singapore ANG ƒ | Sint Maarten EUR € | Slovakia EUR € | Slovenia USD $ | South Africa KRW ₩ | South Korea EUR € | Spain LKR ₨ | Sri Lanka EUR € | St. Barthélemy SHP £ | St. Helena XCD $ | St. Kitts & Nevis XCD $ | St. Lucia EUR € | St. Martin XCD $ | St. Vincent & Grenadines USD $ | Suriname SEK kr | Sweden CHF CHF | Switzerland TWD $ | Taiwan TZS Sh | Tanzania THB ฿ | Thailand XOF Fr | Togo TOP T$ | Tonga TTD $ | Trinidad & Tobago USD $ | Turks & Caicos Islands AUD $ | Tuvalu USD $ | U.S. Outlying Islands UGX USh | Uganda AED د.إ | United Arab Emirates GBP £ | United Kingdom USD $ | United States UYU $U | Uruguay VUV Vt | Vanuatu EUR € | Vatican City VND ₫ | Vietnam USD $ | Zambia Twitter Facebook Instagram Home Collections DEV CodeNewbie Forem DEV Challenges View All About FAQ Search Log in Cart Collection: CodeNewbie Collection Filter: Availability 0 selected Reset Availability In stock (10) In stock (10 products) Out of stock (1) Out of stock (1 product) In stock (10) In stock (10 products) Out of stock (1) Out of stock (1 product) Price The highest price is $40.00 Reset $ From $ To Filter Remove all Sort by: Featured Best selling Alphabetically, A-Z Alphabetically, Z-A Price, low to high Price, high to low Date, old to new Date, new to old Sort 10 products Filter and sort Filter Filter and sort Filter 10 products Availability Availability In stock (10) In stock (10 products) Out of stock (1) Out of stock (1 products) Clear Apply Apply Price Price The highest price is $40.00 $ From $ To Clear Apply Apply Sort by: Featured Best selling Alphabetically, A-Z Alphabetically, Z-A Price, low to high Price, high to low Date, old to new Date, new to old Remove all Apply Apply Remove all 10 products CodeNewbie Logo Stainless Steel Water Bottle CodeNewbie Logo Stainless Steel Water Bottle Regular price $28.00 USD Regular price Sale price $28.00 USD Unit price / per CodeNewbie Motivation Notebook CodeNewbie Motivation Notebook Regular price $17.00 USD Regular price Sale price $17.00 USD Unit price / per CodeNewbie Dad Hat CodeNewbie Dad Hat Regular price $25.00 USD Regular price Sale price $25.00 USD Unit price / per CodeNewbie Coffee Mug CodeNewbie Coffee Mug Regular price $15.00 USD Regular price Sale price $15.00 USD Unit price / per CodeNewbie Bubble Mousepad CodeNewbie Bubble Mousepad Regular price $13.00 USD Regular price Sale price $13.00 USD Unit price / per CodeNewbie Crew Socks CodeNewbie Crew Socks Regular price $14.00 USD Regular price Sale price $14.00 USD Unit price / per CodeNewbie Logo Fitted Hoodie CodeNewbie Logo Fitted Hoodie Regular price $40.00 USD Regular price Sale price $40.00 USD Unit price / per CodeNewbie Bubble Short-Sleeve Straight-Cut T-Shirt CodeNewbie Bubble Short-Sleeve Straight-Cut T-Shirt Regular price $22.00 USD Regular price Sale price $22.00 USD Unit price / per CodeNewbie Pom-Pom Beanie CodeNewbie Pom-Pom Beanie Regular price $20.00 USD Regular price Sale price $20.00 USD Unit price / per CodeNewbie Bubble Short-Sleeve Fitted T-Shirt CodeNewbie Bubble Short-Sleeve Fitted T-Shirt Regular price $22.00 USD Regular price Sale price $22.00 USD Unit price / per Subscribe to our emails Email Facebook Instagram Twitter Country/region Albania (ALL L) Andorra (EUR €) Angola (USD $) Anguilla (XCD $) Antigua & Barbuda (XCD $) Argentina (USD $) Aruba (AWG ƒ) Australia (AUD $) Austria (EUR €) Bahamas (BSD $) Bahrain (USD $) Barbados (BBD $) Belgium (EUR €) Belize (BZD $) Benin (XOF Fr) Bermuda (USD $) Bhutan (USD $) Bosnia & Herzegovina (BAM КМ) Botswana (BWP P) Bouvet Island (USD $) Brazil (USD $) British Virgin Islands (USD $) Bulgaria (EUR €) Burkina Faso (XOF Fr) Cameroon (XAF CFA) Canada (CAD $) Cape Verde (CVE $) Caribbean Netherlands (USD $) Chile (USD $) China (CNY ¥) Colombia (USD $) Comoros (KMF Fr) Cook Islands (NZD $) Croatia (EUR €) Curaçao (ANG ƒ) Cyprus (EUR €) Czechia (CZK Kč) Denmark (DKK kr.) Djibouti (DJF Fdj) Dominica (XCD $) Dominican Republic (DOP $) Equatorial Guinea (XAF CFA) Estonia (EUR €) Eswatini (USD $) Ethiopia (ETB Br) Falkland Islands (FKP £) Faroe Islands (DKK kr.) Fiji (FJD $) Finland (EUR €) France (EUR €) French Guiana (EUR €) French Polynesia (XPF Fr) Gabon (XOF Fr) Gambia (GMD D) Germany (EUR €) Ghana (USD $) Gibraltar (GBP £) Greece (EUR €) Grenada (XCD $) Guadeloupe (EUR €) Guernsey (GBP £) Guinea (GNF Fr) Guinea-Bissau (XOF Fr) Guyana (GYD $) Haiti (USD $) Heard & McDonald Islands (AUD $) Hong Kong SAR (HKD $) Hungary (HUF Ft) Iceland (ISK kr) India (INR ₹) Indonesia (IDR Rp) Ireland (EUR €) Israel (ILS ₪) Italy (EUR €) Jamaica (JMD $) Japan (JPY ¥) Jersey (USD $) Jordan (USD $) Kenya (KES KSh) Kiribati (USD $) Kuwait (USD $) Latvia (EUR €) Liechtenstein (CHF CHF) Lithuania (EUR €) Luxembourg (EUR €) Macao SAR (MOP P) Malawi (MWK MK) Malaysia (MYR RM) Maldives (MVR MVR) Malta (EUR €) Martinique (EUR €) Mauritania (USD $) Mayotte (EUR €) Mexico (USD $) Monaco (EUR €) Montserrat (XCD $) Mozambique (USD $) Namibia (USD $) Nauru (AUD $) Nepal (NPR Rs.) Netherlands (EUR €) Netherlands Antilles (ANG ƒ) New Caledonia (XPF Fr) New Zealand (NZD $) Nigeria (NGN ₦) Niue (NZD $) Norway (USD $) Oman (USD $) Papua New Guinea (PGK K) Paraguay (PYG ₲) Peru (PEN S/) Philippines (PHP ₱) Poland (PLN zł) Portugal (EUR €) Qatar (QAR ر.ق) Réunion (EUR €) Romania (RON Lei) Rwanda (RWF FRw) São Tomé & Príncipe (STD Db) Saudi Arabia (SAR ر.س) Senegal (XOF Fr) Singapore (SGD $) Sint Maarten (ANG ƒ) Slovakia (EUR €) Slovenia (EUR €) South Africa (USD $) South Korea (KRW ₩) Spain (EUR €) Sri Lanka (LKR ₨) St. Barthélemy (EUR €) St. Helena (SHP £) St. Kitts & Nevis (XCD $) St. Lucia (XCD $) St. Martin (EUR €) St. Vincent & Grenadines (XCD $) Suriname (USD $) Sweden (SEK kr) Switzerland (CHF CHF) Taiwan (TWD $) Tanzania (TZS Sh) Thailand (THB ฿) Togo (XOF Fr) Tonga (TOP T$) Trinidad & Tobago (TTD $) Turks & Caicos Islands (USD $) Tuvalu (AUD $) U.S. Outlying Islands (USD $) Uganda (UGX USh) United Arab Emirates (AED د.إ) United Kingdom (GBP £) United States (USD $) Uruguay (UYU $U) Vanuatu (VUV Vt) Vatican City (EUR €) Vietnam (VND ₫) Zambia (USD $) Update country/region Country/region USD $ | United States ALL L | Albania EUR € | Andorra USD $ | Angola XCD $ | Anguilla XCD $ | Antigua & Barbuda USD $ | Argentina AWG ƒ | Aruba AUD $ | Australia EUR € | Austria BSD $ | Bahamas USD $ | Bahrain BBD $ | Barbados EUR € | Belgium BZD $ | Belize XOF Fr | Benin USD $ | Bermuda USD $ | Bhutan BAM КМ | Bosnia & Herzegovina BWP P | Botswana USD $ | Bouvet Island USD $ | Brazil USD $ | British Virgin Islands EUR € | Bulgaria XOF Fr | Burkina Faso XAF CFA | Cameroon CAD $ | Canada CVE $ | Cape Verde USD $ | Caribbean Netherlands USD $ | Chile CNY ¥ | China USD $ | Colombia KMF Fr | Comoros NZD $ | Cook Islands EUR € | Croatia ANG ƒ | Curaçao EUR € | Cyprus CZK Kč | Czechia DKK kr. | Denmark DJF Fdj | Djibouti XCD $ | Dominica DOP $ | Dominican Republic XAF CFA | Equatorial Guinea EUR € | Estonia USD $ | Eswatini ETB Br | Ethiopia FKP £ | Falkland Islands DKK kr. | Faroe Islands FJD $ | Fiji EUR € | Finland EUR € | France EUR € | French Guiana XPF Fr | French Polynesia XOF Fr | Gabon GMD D | Gambia EUR € | Germany USD $ | Ghana GBP £ | Gibraltar EUR € | Greece XCD $ | Grenada EUR € | Guadeloupe GBP £ | Guernsey GNF Fr | Guinea XOF Fr | Guinea-Bissau GYD $ | Guyana USD $ | Haiti AUD $ | Heard & McDonald Islands HKD $ | Hong Kong SAR HUF Ft | Hungary ISK kr | Iceland INR ₹ | India IDR Rp | Indonesia EUR € | Ireland ILS ₪ | Israel EUR € | Italy JMD $ | Jamaica JPY ¥ | Japan USD $ | Jersey USD $ | Jordan KES KSh | Kenya USD $ | Kiribati USD $ | Kuwait EUR € | Latvia CHF CHF | Liechtenstein EUR € | Lithuania EUR € | Luxembourg MOP P | Macao SAR MWK MK | Malawi MYR RM | Malaysia MVR MVR | Maldives EUR € | Malta EUR € | Martinique USD $ | Mauritania EUR € | Mayotte USD $ | Mexico EUR € | Monaco XCD $ | Montserrat USD $ | Mozambique USD $ | Namibia AUD $ | Nauru NPR Rs. | Nepal EUR € | Netherlands ANG ƒ | Netherlands Antilles XPF Fr | New Caledonia NZD $ | New Zealand NGN ₦ | Nigeria NZD $ | Niue USD $ | Norway USD $ | Oman PGK K | Papua New Guinea PYG ₲ | Paraguay PEN S/ | Peru PHP ₱ | Philippines PLN zł | Poland EUR € | Portugal QAR ر.ق | Qatar EUR € | Réunion RON Lei | Romania RWF FRw | Rwanda STD Db | São Tomé & Príncipe SAR ر.س | Saudi Arabia XOF Fr | Senegal SGD $ | Singapore ANG ƒ | Sint Maarten EUR € | Slovakia EUR € | Slovenia USD $ | South Africa KRW ₩ | South Korea EUR € | Spain LKR ₨ | Sri Lanka EUR € | St. Barthélemy SHP £ | St. Helena XCD $ | St. Kitts & Nevis XCD $ | St. Lucia EUR € | St. Martin XCD $ | St. Vincent & Grenadines USD $ | Suriname SEK kr | Sweden CHF CHF | Switzerland TWD $ | Taiwan TZS Sh | Tanzania THB ฿ | Thailand XOF Fr | Togo TOP T$ | Tonga TTD $ | Trinidad & Tobago USD $ | Turks & Caicos Islands AUD $ | Tuvalu USD $ | U.S. Outlying Islands UGX USh | Uganda AED د.إ | United Arab Emirates GBP £ | United Kingdom USD $ | United States UYU $U | Uruguay VUV Vt | Vanuatu EUR € | Vatican City VND ₫ | Vietnam USD $ | Zambia © 2026, Forem Shop Powered by Shopify Privacy policy Terms of service Choosing a selection results in a full page refresh. Opens in a new window. | 2026-01-13T08:49:47 |
https://about.meta.com/technologies/meta-pay | Meta Pay | Meta Skip to content Meta Pay Meta Pay is an easy, secure way to pay on the apps you already use. Not in the US? Check availability Shop, donate or send money on the apps you already use When you use Meta Pay, it loads your saved payment, shipping, and contact information automatically so you can check out quickly. Check out easily and quickly Use Meta Pay when shopping online. If you have Meta Pay set up, your saved payment, shipping, and contact information loads automatically after a quick Facebook or Instagram login verification. New to Meta Pay? Add your payment method once and you'll enjoy a fast checkout every time you use Meta Pay. Manage your payment activity You can easily manage payment methods, view your payment and transaction history, or access customer support in Accounts Center . Your security and protection matter How it works It’s simple to get started with Meta Pay Use Meta Pay seamlessly between Facebook and Instagram Set up Meta Pay on Facebook by adding your preferred payment just once, then connect it across Instagram without having to re-enter your information each time. FAQs We’ve included some frequently asked questions below. For more, visit Meta Pay Help Center . How does Meta Pay work? Meta Pay is a seamless and secure way to make payments on Facebook, Messenger, Instagram, and in participating online stores. Enter your payment card or account information just once and then use Meta Pay to make purchases, send money or donate. Add a PIN or use the fingerprint or face ID on your device to secure individual payments. Meta Pay also lets you view your payment history, manage payment information and access 24-hour chat service for customer support. Is it secure to make payments with Meta Pay? We use advanced technology to keep payment information secure. Meta Pay is protected with: Anti-fraud technology that monitors purchases on Meta Pay systems to detect unauthorized activity. Payment card numbers are securely stored, encrypted and stored separately from your profile data. Notifications that alert you if Meta Pay detects unusual activity. An option to create a PIN or use the fingerprint or face ID on your device for additional security when sending money or making a payment. Facebook does not receive or store your device’s biometric information. How do I set up a Meta Pay PIN? When making a payment with Meta Pay, you may be required to set up a PIN (PIN is mandatory in some use cases) by selecting a 4-digit numeric pass code. You may also be able to use your device's face ID or fingerprint for an extra layer of security. You can also set up a PIN with Meta Pay for additional security when sending payments by going to Orders and Payments settings. As part of our commitment to security, we may prompt a PIN with Meta Pay verification when certain types of transactions appear as unusual activity. Do I need to have a Facebook account to use Meta Pay? Meta Pay can be set up by logging into at least one of our apps - Facebook, Instagram or Messenger. Then, enter your payment card or account information. When Meta Pay is set up on Facebook and Messenger, people can connect Meta Pay across Instagram without having to re-enter their payment information. Where can I use Meta Pay? Meta Pay can be used on Facebook, Instagram, Messenger, and in participating online stores. On Facebook , you can use Meta Pay to shop, donate, buy tickets for events, or games. On Instagram , you can use Meta Pay to shop or make donations to charitable or personal fundraisers. On Messenger , you can use Meta Pay to send money to friends and family in the United States. When online stores have Meta Pay enabled, you can shop the products and services you love, and check out faster with your saved credentials. Meta Pay may not be available in all payment use cases on Facebook, Instagram and Messenger. We are continuing to build out functionality so that more people in more places can use Meta Pay across our technologies. Check back here for updates. Meta Newsroom Get the latest news on Meta Pay and what it can do for you. Visit our Newsroom Getting started is easy Availability varies by country Country availability Meta Pay resources Help Center Privacy Policy Community Payment Terms Payments Privacy Policy EU Region Payments Privacy Policy | 2026-01-13T08:49:47 |
https://docs.suprsend.com/docs/getting-started#benefits-of-using-suprsend-as-your-notification-stack%3A | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:49:47 |
https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fkowshikkumar_reddymakire%252Fbuilding-a-low-code-blockchain-deployment-platform-4ali%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://www.fsf.org/blogs/community/2025-hackathon-roundup | Hundreds of free software supporters tuned in for FSF40 hackathon — Free Software Foundation — Working together for free software ​ Push freedom ahead! The free software community has always thwarted the toughest challenges facing freedom in technology. This winter season, we want to thank the many individuals and projects that have helped us get where we are today: a world where a growing number of users are able to do their computing in full freedom. Our work isn't over. We have so much more to do. Help us reach our stretch New Year's membership goal of 100 new associate members by January 16, 2026, and keep the FSF strong and independent. Join | Read more Join Renew Donate Skip to content , sitemap or skip to search . Personal tools Log in Help! Members forum About Campaigns Licensing Membership Resources Community ♥Donate♥ Shop Search You are here: Home › Blogs › Community › Hundreds of free software supporters tuned in for FSF40 hackathon Info Hundreds of free software supporters tuned in for FSF40 hackathon by Eko K.A. Owen Contributions — Published on Nov 25, 2025 10:11 AM After months of preparation and excitement, we finally came together on November 21 at 10:00 EST for the global online FSF40 hackathon , ending November 23, 10:00 EST. When we decided to host this hackathon as part of our fortieth anniversary celebrations, we did it with the aspiration that this hackathon would put a spotlight on the difficult and often thankless work that free software hackers carry out, and support free software projects. Based on how many of you dropped in over the weekend and were incredibly engaged in the important work that is improving free software, either as a spectator or as a participant, this goal was accomplished. And it's all thanks to you! Friday started a little rocky with a datacenter outage affecting most FSF services. Participants spread out to work on six different free software projects over forty-eight hours as our tech team worked to restore all FSF sites with the help and support of the community. Over three hundred folks were tuned in at a time, some to participate in the hackathon and others to follow the progress being made. As a community, we got a lot done over the weekend, but here are a few especially notable accomplishments achieved: Work to bring "un-" archiving functionality into Org Mode; Verified nonfree software had been identified and removed from packages in free GNU/Linux distros; Progress on developing a new UI for the Lewa project; Training new volunteers on how to edit the Free Software Directory; Numerous new contributors participated in free software projects, including GNU Guix and Org Mode. So many contributions on six projects ( FSD , GNU Boot , GNU Guix , Lewa, op-mattermost, and Org Mode ) over one weekend is an achievement. The progress made this weekend is worthy of celebration itself, but at the end of the hackathon, we drew special attention to a three special contributions with an award: First time contributor, given to a participant who has never contributed to that free software package before or a team with at least one new free software contributor. This award went to the "un-archive" team of Org Mode. Most impactful contribution. This award went to Jiyu for their work on GNU Boot . Diversity, equity, inclusion, and belonging award and certificate, given to the participant or team member that makes the greatest contribution(s) in advancing diversity, equity, inclusion, and belonging. This award went to the Lewa project. If you participated in the FSF40 hackathon and would like a certificate illustrating your work, please email campaigns@fsf.org . It was amazing to see so many of you take a little (or a lot of!) time out of your busy schedules to improve free software, and we're incredibly grateful for each and every one of you. It really energizes us and shows us how much we can accomplish when we work together over even just a couple days. Not only was this a fantastic sight to see because of the work we got done, but it was also a very fitting way to conclude our fortieth anniversary celebration events. Free software has been and always will be a community effort, one that continues to get better and better because of the dedicated developers, contributors, and users who ensure its existence. Thank you for celebrating forty years of the FSF and fighting for a freer future for us all. We wouldn't have had nearly as cool prizes without our sponsors. Purism generously donated a Librem 5 phone (which runs PureOS) that was awarded to the participant with the most impactful contribution made during the hackathon; and ThinkPenguin kindly donated a Free Software Wireless-N Mesh Kit (three-pack), which was given to a team with participants who had never contributed to that free software package before. Thank you Purism and ThinkPenguin for your generosity. The FSF is currently having its year-end fundraiser. If you like participating (even if just as a spectator!) in events like the FSF40 hackathon, donate $40 USD or become an associate member for as little as $12 USD a month. Donations and associate memberships not only help us reach our fundraising goal of $400,000 USD, but they also support us in putting on events like the FSF40 hackathon. Document Actions Share on social networks Syndicate: News Events Blogs Jobs GNU 1PC9aZC4hNX2rmmrt7uHTfYAS3hRbph4UN Help the FSF stay strong Ring in the new year by supporting software freedom and helping us reach our goal of 100 new associate members ! FSF community blog Licensing Compliance Lab blog Associate Membership blog System Administrator's blog Free Software Directory blog GNU Press blog Sign up Enter your email address to receive our monthly newsletter, the Free Software Supporter News Eko K. A. Owen joins the FSF board as the union staff pick Dec 29, 2025 Free Software Foundation receives historic private donations Dec 24, 2025 Free Software Awards winners announced: Andy Wingo, Alx Sa, Govdirectory Dec 09, 2025 More news… Recent blogs Turning freedom values into freedom practice with the FSF tech team December GNU Spotlight with Amin Bandali featuring sixteen new GNU releases: GnuPG, a2ps, and more! Celebrate the new year: join the free software community! A message from FSF president Ian Kelling Recent blogs - More… Upcoming Events Free Software Directory meeting on IRC: Friday, January 16, starting at 12:00 EST (17:00 UTC) Jan 16, 2026 12:00 PM - 03:00 PM — #fsf on libera.chat Previous events… Upcoming events… The FSF is a charity with a worldwide mission to advance software freedom — learn about our history and work. Copyright © 2004-2026 Free Software Foundation , Inc. Privacy Policy . This work is licensed under a Creative Commons Attribution-No Derivative Works 3.0 license (or later version) — Why this license? Skip sitemap or skip to licensing items About Staff and Board Contact Us Press Information Jobs Volunteering and Internships History Privacy Policy JavaScript Licenses Hardware Database Free Software Directory Free Software Resources Copyright Infringement Notification Skip to general items Campaigns Freedom Ladder Fight to Repair Free JavaScript High Priority Free Software Projects Secure Boot vs Restricted Boot Surveillance Upgrade from Windows Working Together for Free Software GNU Operating System Defective by Design End Software Patents OpenDocument Free BIOS Connect with free software users Skip to philosophical items Licensing Education Licenses GNU GPL GNU AGPL GNU LGPL GNU FDL Licensing FAQ Compliance How to use GNU licenses for your own software Latest News Upcoming Events FSF Blogs Skip list Donate to the FSF Join the FSF Patrons Associate Members My Account Working Together for Free Software Fund Philosophy The Free Software Definition Copyleft: Pragmatic Idealism Free Software and Free Manuals Selling Free Software Motives for Writing Free Software The Right To Read Why Open Source Misses the Point of Free Software Complete Sitemap fsf.org is powered by: Plone Zope Python CiviCRM HTML5 Arabic Belarussian Bulgarian Catalan Chinese Cornish Czech Danish English French German Greek Hebrew Hindi Italian Japanese Korean Norwegian Polish Portuguese Portuguese (Brazil) Romanian Russian Slovak Spanish Swedish Turkish Urdu Welsh Send your feedback on our translations and new translations of pages to campaigns@fsf.org . | 2026-01-13T08:49:47 |
https://vibe.forem.com/t/docker#main-content | Docker - Vibe Coding 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 Vibe Coding Forem Close Docker Follow Hide Stories about Docker as a technology (containers, CLI, Engine) or company (Docker Hub, Docker Swarm). Create Post submission guidelines All docker-related stories are allowed, eg: security, docker-compose, images, commands or platform-specific issues. about #docker Docker is the most popular container solution, a way to perform operating-system level virtualization of processes. Containers are used to pack/wrap an application including all its dependencies and ship it as a single package. Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 30 '25 Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit # docker # devops # opensource 3 reactions Comments Add Comment 1 min read Tech With Tim: Advanced Vibe Coding Tutorial w/ Warp (Build & Deploy Apps) Vibe YouTube Vibe YouTube Vibe YouTube Follow Aug 13 '25 Tech With Tim: Advanced Vibe Coding Tutorial w/ Warp (Build & Deploy Apps) # ai # docker # git # cloud Comments Add Comment 1 min read loading... trending guides/resources Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit 💎 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 Vibe Coding Forem — Discussing AI software development, and showing off what we're building. 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 . Vibe Coding Forem © 2025 - 2026. Where anyone can code, with a bit of creativity and some AI help. Log in Create account | 2026-01-13T08:49:47 |
https://docs.suprsend.com/docs/getting-started#benefits-of-using-suprsend-as-your-notification-stack: | What is SuprSend? - 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 GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation GETTING STARTED What is SuprSend? Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog GETTING STARTED What is SuprSend? OpenAI Open in ChatGPT Learn about SuprSend and how you can use it to power multi-channel product notifications. OpenAI Open in ChatGPT SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack: You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritise vendors and channels from your SuprSend account, You can design powerful templates for all channels together and manage them from a single place, You can leverage powerful features to experiment fast with notifications as well as take care of end user experience without writing a single line of code. Introduction to Workflows Communications are made up of multiple components - trigger, logic, content, variables, target user, channels, vendors, etc. Typical communication solutions have one or more components intertwined with each other. SuprSend solves communications from a different and more powerful approach, which we call Workflows. At SuprSend, all the constituent components are decoupled from each other, making it modular in nature. The components can come from any source. All these components are configured as nodes in Workflows, where the processing happens for delivery and optimisation. This allows Workflows to handle any complexity possible in your communication use cases. How do you trigger notifications? You can trigger notifications in one of the two ways: Send events to SuprSend from your frontend clients (android app, website, etc) via SuprSend Client SDK, and create a Workflow on SuprSend platform to trigger notification on an event. Create workflow and trigger notification from your backend itself using an omni-channel HTTPS API method, or you can use our Backend SDK. All the other components (like vendors, templates, optimisation, scaling, etc.) are created and managed on SuprSend platform. You can check the ‘Core Concepts’ section that lists down the components used in the platform, so you can navigate the platform and use all the features with ease. SuprSend APIs You can try out SuprSend APIs from our Postman collection Was this page helpful? Yes No Suggest edits Raise issue Overview Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels. Next ⌘ I x github linkedin youtube Powered by On this page Benefits of using SuprSend as your notification stack: Introduction to Workflows How do you trigger notifications? SuprSend APIs | 2026-01-13T08:49:47 |
https://www.facebook.com/ad_campaign/landing.php?placement=pflo&campaign_id=402047449186&nav_source=unknown&extra_1=auto | Facebook - 로그인 또는 가입 Facebook에서 전세계에 있는 친구, 가족, 지인들과 함께 이야기를 나눠보세요. 로그인 비밀번호를 잊으셨나요? 새 계정 만들기 유명인, 브랜드 또는 비즈니스를 위한 페이지 만들기 . 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://future.forem.com/bobjiang | Bob Jiang | awesomerobots - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Follow User actions Bob Jiang | awesomerobots Cooking https://awesomerobots.xyz/ , Thrive @EthereumSydney | Advisor of @ScalingX | KB5 of @Kernel0x Joined Joined on Apr 18, 2025 Personal website https://awesomerobots.xyz/ Work Freelancer More info about @bobjiang Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 1 post published Comment 0 comments written Tag 1 tag followed Awesome Robots Digest - Issue #14 - December 12, 2025 Bob Jiang | awesomerobots Bob Jiang | awesomerobots Bob Jiang | awesomerobots Follow Dec 16 '25 Awesome Robots Digest - Issue #14 - December 12, 2025 # digest # newsletter # robotics # ai Comments Add Comment 11 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://future.forem.com/dan_ledger_ce2886f0037972 | Dan - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Follow User actions Dan 404 bio not found Location boston, ma Joined Joined on Dec 6, 2025 More info about @dan_ledger_ce2886f0037972 Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Post 10 posts published Comment 0 comments written Tag 0 tags followed 2025-12-23 Daily Robotics News Dan Dan Dan Follow Dec 23 '25 2025-12-23 Daily Robotics News # robotics Comments Add Comment 8 min read 2025-12-23 Daily Ai News Dan Dan Dan Follow Dec 23 '25 2025-12-23 Daily Ai News # ai Comments Add Comment 6 min read 2025-12-20 Daily Robotics News Dan Dan Dan Follow Dec 20 '25 2025-12-20 Daily Robotics News # robotics Comments Add Comment 7 min read 2025-12-17 Weekly Quantum News Dan Dan Dan Follow Dec 17 '25 2025-12-17 Weekly Quantum News # quantumapplications Comments 1 comment 3 min read 2025-12-14 Daily Robotics News Dan Dan Dan Follow Dec 14 '25 2025-12-14 Daily Robotics News # robotics Comments Add Comment 3 min read 2025-12-12 Daily Robotics News Dan Dan Dan Follow Dec 12 '25 2025-12-12 Daily Robotics News # robotics Comments Add Comment 3 min read 2025-12-12 Daily Robotics News Dan Dan Dan Follow Dec 12 '25 2025-12-12 Daily Robotics News # robotics Comments Add Comment 3 min read 2025-12-11 Daily Robotics News Dan Dan Dan Follow Dec 11 '25 2025-12-11 Daily Robotics News # robotics Comments Add Comment 3 min read 2025-12-10 Daily Ai News Dan Dan Dan Follow Dec 10 '25 2025-12-10 Daily Ai News # ai Comments 1 comment 5 min read 2025-12-09 Daily Robotics News Dan Dan Dan Follow Dec 9 '25 2025-12-09 Daily Robotics News # robotics 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://docs.python.org/3/whatsnew/3.14.html#whatsnew314-build-changes | What’s new in Python 3.14 — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents What’s new in Python 3.14 Summary – Release highlights New features PEP 649 & PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template string literals PEP 768 : Safe external debugger interface A new type of interpreter Free-threaded mode improvements Improved error messages PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Other language changes Built-ins Command line and environment PEP 758: Allow except and except* expressions without brackets PEP 765: Control flow in finally blocks Incremental garbage collection Default interactive shell New modules Improved modules argparse ast asyncio calendar concurrent.futures configparser contextvars ctypes curses datetime decimal difflib dis errno faulthandler fnmatch fractions functools getopt getpass graphlib heapq hmac http imaplib inspect io json linecache logging.handlers math mimetypes multiprocessing operator os os.path pathlib pdb pickle platform pydoc re socket ssl struct symtable sys sys.monitoring sysconfig tarfile threading tkinter turtle types typing unicodedata unittest urllib uuid webbrowser zipfile Optimizations asyncio base64 bdb difflib gc io pathlib pdb textwrap uuid zlib Removed argparse ast asyncio email importlib.abc itertools pathlib pkgutil pty sqlite3 urllib Deprecated New deprecations Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.17 Pending removal in Python 3.18 Pending removal in Python 3.19 Pending removal in future versions CPython bytecode changes Pseudo-instructions C API changes Python configuration C API New features in the C API Limited C API changes Removed C APIs Deprecated C APIs Pending removal in Python 3.15 Pending removal in Python 3.16 Pending removal in Python 3.18 Pending removal in future versions Build changes build-details.json Discontinuation of PGP signatures Free-threaded Python is officially supported Binary releases for the experimental just-in-time compiler Porting to Python 3.14 Changes in the Python API Changes in annotations ( PEP 649 and PEP 749 ) Implications for annotated code Implications for readers of __annotations__ Related changes from __future__ import annotations Changes in the C API Notable changes in 3.14.1 Previous topic What’s New in Python Next topic What’s New In Python 3.13 This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » What’s New in Python » What’s new in Python 3.14 | Theme Auto Light Dark | What’s new in Python 3.14 ¶ Editors : Adam Turner and Hugo van Kemenade This article explains the new features in Python 3.14, compared to 3.13. Python 3.14 was released on 7 October 2025. For full details, see the changelog . See also PEP 745 – Python 3.14 release schedule Summary – Release highlights ¶ Python 3.14 is the latest stable release of the Python programming language, with a mix of changes to the language, the implementation, and the standard library. The biggest changes include template string literals , deferred evaluation of annotations , and support for subinterpreters in the standard library. The library changes include significantly improved capabilities for introspection in asyncio , support for Zstandard via a new compression.zstd module, syntax highlighting in the REPL, as well as the usual deprecations and removals, and improvements in user-friendliness and correctness. This article doesn’t attempt to provide a complete specification of all new features, but instead gives a convenient overview. For full details refer to the documentation, such as the Library Reference and Language Reference . To understand the complete implementation and design rationale for a change, refer to the PEP for a particular new feature; but note that PEPs usually are not kept up-to-date once a feature has been fully implemented. See Porting to Python 3.14 for guidance on upgrading from earlier versions of Python. Interpreter improvements: PEP 649 and PEP 749 : Deferred evaluation of annotations PEP 734 : Multiple interpreters in the standard library PEP 750 : Template strings PEP 758 : Allow except and except* expressions without brackets PEP 765 : Control flow in finally blocks PEP 768 : Safe external debugger interface for CPython A new type of interpreter Free-threaded mode improvements Improved error messages Incremental garbage collection Significant improvements in the standard library: PEP 784 : Zstandard support in the standard library Asyncio introspection capabilities Concurrent safe warnings control Syntax highlighting in the default interactive shell , and color output in several standard library CLIs C API improvements: PEP 741 : Python configuration C API Platform support: PEP 776 : Emscripten is now an officially supported platform , at tier 3 . Release changes: PEP 779 : Free-threaded Python is officially supported PEP 761 : PGP signatures have been discontinued for official releases Windows and macOS binary releases now support the experimental just-in-time compiler Binary releases for Android are now provided New features ¶ PEP 649 & PEP 749 : Deferred evaluation of annotations ¶ The annotations on functions, classes, and modules are no longer evaluated eagerly. Instead, annotations are stored in special-purpose annotate functions and evaluated only when necessary (except if from __future__ import annotations is used). This change is designed to improve performance and usability of annotations in Python in most circumstances. The runtime cost for defining annotations is minimized, but it remains possible to introspect annotations at runtime. It is no longer necessary to enclose annotations in strings if they contain forward references. The new annotationlib module provides tools for inspecting deferred annotations. Annotations may be evaluated in the VALUE format (which evaluates annotations to runtime values, similar to the behavior in earlier Python versions), the FORWARDREF format (which replaces undefined names with special markers), and the STRING format (which returns annotations as strings). This example shows how these formats behave: >>> from annotationlib import get_annotations , Format >>> def func ( arg : Undefined ): ... pass >>> get_annotations ( func , format = Format . VALUE ) Traceback (most recent call last): ... NameError : name 'Undefined' is not defined >>> get_annotations ( func , format = Format . FORWARDREF ) {'arg': ForwardRef('Undefined', owner=<function func at 0x...>)} >>> get_annotations ( func , format = Format . STRING ) {'arg': 'Undefined'} The porting section contains guidance on changes that may be needed due to these changes, though in the majority of cases, code will continue working as-is. (Contributed by Jelle Zijlstra in PEP 749 and gh-119180 ; PEP 649 was written by Larry Hastings.) See also PEP 649 Deferred Evaluation Of Annotations Using Descriptors PEP 749 Implementing PEP 649 PEP 734 : Multiple interpreters in the standard library ¶ The CPython runtime supports running multiple copies of Python in the same process simultaneously and has done so for over 20 years. Each of these separate copies is called an ‘interpreter’. However, the feature had been available only through the C-API . That limitation is removed in Python 3.14, with the new concurrent.interpreters module. There are at least two notable reasons why using multiple interpreters has significant benefits: they support a new (to Python), human-friendly concurrency model true multi-core parallelism For some use cases, concurrency in software improves efficiency and can simplify design, at a high level. At the same time, implementing and maintaining all but the simplest concurrency is often a struggle for the human brain. That especially applies to plain threads (for example, threading ), where all memory is shared between all threads. With multiple isolated interpreters, you can take advantage of a class of concurrency models, like Communicating Sequential Processes (CSP) or the actor model, that have found success in other programming languages, like Smalltalk, Erlang, Haskell, and Go. Think of multiple interpreters as threads but with opt-in sharing. Regarding multi-core parallelism: as of Python 3.12, interpreters are now sufficiently isolated from one another to be used in parallel (see PEP 684 ). This unlocks a variety of CPU-intensive use cases for Python that were limited by the GIL . Using multiple interpreters is similar in many ways to multiprocessing , in that they both provide isolated logical “processes” that can run in parallel, with no sharing by default. However, when using multiple interpreters, an application will use fewer system resources and will operate more efficiently (since it stays within the same process). Think of multiple interpreters as having the isolation of processes with the efficiency of threads. While the feature has been around for decades, multiple interpreters have not been used widely, due to low awareness and the lack of a standard library module. Consequently, they currently have several notable limitations, which are expected to improve significantly now that the feature is going mainstream. Current limitations: starting each interpreter has not been optimized yet each interpreter uses more memory than necessary (work continues on extensive internal sharing between interpreters) there aren’t many options yet for truly sharing objects or other data between interpreters (other than memoryview ) many third-party extension modules on PyPI are not yet compatible with multiple interpreters (all standard library extension modules are compatible) the approach to writing applications that use multiple isolated interpreters is mostly unfamiliar to Python users, for now The impact of these limitations will depend on future CPython improvements, how interpreters are used, and what the community solves through PyPI packages. Depending on the use case, the limitations may not have much impact, so try it out! Furthermore, future CPython releases will reduce or eliminate overhead and provide utilities that are less appropriate on PyPI. In the meantime, most of the limitations can also be addressed through extension modules, meaning PyPI packages can fill any gap for 3.14, and even back to 3.12 where interpreters were finally properly isolated and stopped sharing the GIL . Likewise, libraries on PyPI are expected to emerge for high-level abstractions on top of interpreters. Regarding extension modules, work is in progress to update some PyPI projects, as well as tools like Cython, pybind11, nanobind, and PyO3. The steps for isolating an extension module are found at Isolating Extension Modules . Isolating a module has a lot of overlap with what is required to support free-threading , so the ongoing work in the community in that area will help accelerate support for multiple interpreters. Also added in 3.14: concurrent.futures.InterpreterPoolExecutor . (Contributed by Eric Snow in gh-134939 .) See also PEP 734 PEP 750 : Template string literals ¶ Template strings are a new mechanism for custom string processing. They share the familiar syntax of f-strings but, unlike f-strings, return an object representing the static and interpolated parts of the string, instead of a simple str . To write a t-string, use a 't' prefix instead of an 'f' : >>> variety = 'Stilton' >>> template = t 'Try some {variety} cheese!' >>> type ( template ) <class 'string.templatelib.Template'> Template objects provide access to the static and interpolated (in curly braces) parts of a string before they are combined. Iterate over Template instances to access their parts in order: >>> list ( template ) ['Try some ', Interpolation('Stilton', 'variety', None, ''), ' cheese!'] It’s easy to write (or call) code to process Template instances. For example, here’s a function that renders static parts lowercase and Interpolation instances uppercase: from string.templatelib import Interpolation def lower_upper ( template ): """Render static parts lowercase and interpolations uppercase.""" parts = [] for part in template : if isinstance ( part , Interpolation ): parts . append ( str ( part . value ) . upper ()) else : parts . append ( part . lower ()) return '' . join ( parts ) name = 'Wenslydale' template = t 'Mister {name} ' assert lower_upper ( template ) == 'mister WENSLYDALE' Because Template instances distinguish between static strings and interpolations at runtime, they can be useful for sanitising user input. Writing a html() function that escapes user input in HTML is an exercise left to the reader! Template processing code can provide improved flexibility. For instance, a more advanced html() function could accept a dict of HTML attributes directly in the template: attributes = { 'src' : 'limburger.jpg' , 'alt' : 'lovely cheese' } template = t '<img {attributes} >' assert html ( template ) == '<img src="limburger.jpg" alt="lovely cheese" />' Of course, template processing code does not need to return a string-like result. An even more advanced html() could return a custom type representing a DOM-like structure. With t-strings in place, developers can write systems that sanitise SQL, make safe shell operations, improve logging, tackle modern ideas in web development (HTML, CSS, and so on), and implement lightweight custom business DSLs. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) See also PEP 750 . PEP 768 : Safe external debugger interface ¶ Python 3.14 introduces a zero-overhead debugging interface that allows debuggers and profilers to safely attach to running Python processes without stopping or restarting them. This is a significant enhancement to Python’s debugging capabilities, meaning that unsafe alternatives are no longer required. The new interface provides safe execution points for attaching debugger code without modifying the interpreter’s normal execution path or adding any overhead at runtime. Due to this, tools can now inspect and interact with Python applications in real-time, which is a crucial capability for high-availability systems and production environments. For convenience, this interface is implemented in the sys.remote_exec() function. For example: import sys from tempfile import NamedTemporaryFile with NamedTemporaryFile ( mode = 'w' , suffix = '.py' , delete = False ) as f : script_path = f . name f . write ( f 'import my_debugger; my_debugger.connect( { os . getpid () } )' ) # Execute in process with PID 1234 print ( 'Behold! An offering:' ) sys . remote_exec ( 1234 , script_path ) This function allows sending Python code to be executed in a target process at the next safe execution point. However, tool authors can also implement the protocol directly as described in the PEP, which details the underlying mechanisms used to safely attach to running processes. The debugging interface has been carefully designed with security in mind and includes several mechanisms to control access: A PYTHON_DISABLE_REMOTE_DEBUG environment variable. A -X disable-remote-debug command-line option. A --without-remote-debug configure flag to completely disable the feature at build time. (Contributed by Pablo Galindo Salgado, Matt Wozniski, and Ivona Stojanovic in gh-131591 .) See also PEP 768 . A new type of interpreter ¶ A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individual Python opcodes, rather than one large C case statement. For certain newer compilers, this interpreter provides significantly better performance. Preliminary benchmarks suggest a geometric mean of 3-5% faster on the standard pyperformance benchmark suite, depending on platform and architecture. The baseline is Python 3.14 built with Clang 19, without this new interpreter. This interpreter currently only works with Clang 19 and newer on x86-64 and AArch64 architectures. However, a future release of GCC is expected to support this as well. This feature is opt-in for now. Enabling profile-guided optimization is highly recommendeded when using the new interpreter as it is the only configuration that has been tested and validated for improved performance. For further information, see --with-tail-call-interp . Note This is not to be confused with tail call optimization of Python functions, which is currently not implemented in CPython. This new interpreter type is an internal implementation detail of the CPython interpreter. It doesn’t change the visible behavior of Python programs at all. It can improve their performance, but doesn’t change anything else. (Contributed by Ken Jin in gh-128563 , with ideas on how to implement this in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.) Free-threaded mode improvements ¶ CPython’s free-threaded mode ( PEP 703 ), initially added in 3.13, has been significantly improved in Python 3.14. The implementation described in PEP 703 has been finished, including C API changes, and temporary workarounds in the interpreter were replaced with more permanent solutions. The specializing adaptive interpreter ( PEP 659 ) is now enabled in free-threaded mode, which along with many other optimizations greatly improves its performance. The performance penalty on single-threaded code in free-threaded mode is now roughly 5-10%, depending on the platform and C compiler used. From Python 3.14, when compiling extension modules for the free-threaded build of CPython on Windows, the preprocessor variable Py_GIL_DISABLED now needs to be specified by the build backend, as it will no longer be determined automatically by the C compiler. For a running interpreter, the setting that was used at compile time can be found using sysconfig.get_config_var() . The new -X context_aware_warnings flag controls if concurrent safe warnings control is enabled. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. A new thread_inherit_context flag has been added, which if enabled means that threads created with threading.Thread start with a copy of the Context() of the caller of start() . Most significantly, this makes the warning filtering context established by catch_warnings be “inherited” by threads (or asyncio tasks) started within that context. It also affects other modules that use context variables, such as the decimal context manager. This flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Sam Gross, Matt Page, Neil Schemenauer, Thomas Wouters, Donghee Na, Kirill Podoprigora, Ken Jin, Itamar Oren, Brett Simmers, Dino Viehland, Nathan Goldbaum, Ralf Gommers, Lysandros Nikolaou, Kumar Aditya, Edgar Margffoy, and many others. Some of these contributors are employed by Meta, which has continued to provide significant engineering resources to support this project.) Improved error messages ¶ The interpreter now provides helpful suggestions when it detects typos in Python keywords. When a word that closely resembles a Python keyword is encountered, the interpreter will suggest the correct keyword in the error message. This feature helps programmers quickly identify and fix common typing mistakes. For example: >>> whille True : ... pass Traceback (most recent call last): File "<stdin>" , line 1 whille True : ^^^^^^ SyntaxError : invalid syntax. Did you mean 'while'? While the feature focuses on the most common cases, some variations of misspellings may still result in regular syntax errors. (Contributed by Pablo Galindo in gh-132449 .) elif statements that follow an else block now have a specific error message. (Contributed by Steele Farnsworth in gh-129902 .) >>> if who == "me" : ... print ( "It's me!" ) ... else : ... print ( "It's not me!" ) ... elif who is None : ... print ( "Who is it?" ) File "<stdin>", line 5 elif who is None: ^^^^ SyntaxError: 'elif' block follows an 'else' block If a statement is passed to the Conditional expressions after else , or one of pass , break , or continue is passed before if , then the error message highlights where the expression is required. (Contributed by Sergey Miryanov in gh-129515 .) >>> x = 1 if True else pass Traceback (most recent call last): File "<string>" , line 1 x = 1 if True else pass ^^^^ SyntaxError : expected expression after 'else', but statement is given >>> x = continue if True else break Traceback (most recent call last): File "<string>" , line 1 x = continue if True else break ^^^^^^^^ SyntaxError : expected expression before 'if', but statement is given When incorrectly closed strings are detected, the error message suggests that the string may be intended to be part of the string. (Contributed by Pablo Galindo in gh-88535 .) >>> "The interesting object " The important object " is very important" Traceback (most recent call last): SyntaxError : invalid syntax. Is this intended to be part of the string? When strings have incompatible prefixes, the error now shows which prefixes are incompatible. (Contributed by Nikita Sobolev in gh-133197 .) >>> ub 'abc' File "<python-input-0>" , line 1 ub 'abc' ^^ SyntaxError : 'u' and 'b' prefixes are incompatible Improved error messages when using as with incompatible targets in: Imports: import ... as ... From imports: from ... import ... as ... Except handlers: except ... as ... Pattern-match cases: case ... as ... (Contributed by Nikita Sobolev in gh-123539 , gh-123562 , and gh-123440 .) Improved error message when trying to add an instance of an unhashable type to a dict or set . (Contributed by CF Bolz-Tereick and Victor Stinner in gh-132828 .) >>> s = set () >>> s . add ({ 'pages' : 12 , 'grade' : 'A' }) Traceback (most recent call last): File "<python-input-1>" , line 1 , in <module> s . add ({ 'pages' : 12 , 'grade' : 'A' }) ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError : cannot use 'dict' as a set element (unhashable type: 'dict') >>> d = {} >>> l = [ 1 , 2 , 3 ] >>> d [ l ] = 12 Traceback (most recent call last): File "<python-input-4>" , line 1 , in <module> d [ l ] = 12 ~^^^ TypeError : cannot use 'list' as a dict key (unhashable type: 'list') Improved error message when an object supporting the synchronous context manager protocol is entered using async with instead of with , and vice versa for the asynchronous context manager protocol. (Contributed by Bénédikt Tran in gh-128398 .) PEP 784 : Zstandard support in the standard library ¶ The new compression package contains modules compression.lzma , compression.bz2 , compression.gzip and compression.zlib which re-export the lzma , bz2 , gzip and zlib modules respectively. The new import names under compression are the preferred names for importing these compression modules from Python 3.14. However, the existing modules names have not been deprecated. Any deprecation or removal of the existing compression modules will occur no sooner than five years after the release of 3.14. The new compression.zstd module provides compression and decompression APIs for the Zstandard format via bindings to Meta’s zstd library . Zstandard is a widely adopted, highly efficient, and fast compression format. In addition to the APIs introduced in compression.zstd , support for reading and writing Zstandard compressed archives has been added to the tarfile , zipfile , and shutil modules. Here’s an example of using the new module to compress some data: from compression import zstd import math data = str ( math . pi ) . encode () * 20 compressed = zstd . compress ( data ) ratio = len ( compressed ) / len ( data ) print ( f "Achieved compression ratio of { ratio } " ) As can be seen, the API is similar to the APIs of the lzma and bz2 modules. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) See also PEP 784 . Asyncio introspection capabilities ¶ Added a new command-line interface to inspect running Python processes using asynchronous tasks, available via python -m asyncio ps PID or python -m asyncio pstree PID . The ps subcommand inspects the given process ID (PID) and displays information about currently running asyncio tasks. It outputs a task table: a flat listing of all tasks, their names, their coroutine stacks, and which tasks are awaiting them. The pstree subcommand fetches the same information, but instead renders a visual async call tree, showing coroutine relationships in a hierarchical format. This command is particularly useful for debugging long-running or stuck asynchronous programs. It can help developers quickly identify where a program is blocked, what tasks are pending, and how coroutines are chained together. For example given this code: import asyncio async def play_track ( track ): await asyncio . sleep ( 5 ) print ( f '🎵 Finished: { track } ' ) async def play_album ( name , tracks ): async with asyncio . TaskGroup () as tg : for track in tracks : tg . create_task ( play_track ( track ), name = track ) async def main (): async with asyncio . TaskGroup () as tg : tg . create_task ( play_album ( 'Sundowning' , [ 'TNDNBTG' , 'Levitate' ]), name = 'Sundowning' ) tg . create_task ( play_album ( 'TMBTE' , [ 'DYWTYLM' , 'Aqua Regia' ]), name = 'TMBTE' ) if __name__ == '__main__' : asyncio . run ( main ()) Executing the new tool on the running process will yield a table like this: python -m asyncio ps 12345 tid task id task name coroutine stack awaiter chain awaiter name awaiter id ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1935500 0x7fc930c18050 Task-1 TaskGroup._aexit -> TaskGroup.__aexit__ -> main 0x0 1935500 0x7fc930c18230 Sundowning TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fa50 TMBTE TaskGroup._aexit -> TaskGroup.__aexit__ -> album TaskGroup._aexit -> TaskGroup.__aexit__ -> main Task-1 0x7fc930c18050 1935500 0x7fc93173fdf0 TNDNBTG sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32510 Levitate sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album Sundowning 0x7fc930c18230 1935500 0x7fc930d32890 DYWTYLM sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 1935500 0x7fc93161ec30 Aqua Regia sleep -> play TaskGroup._aexit -> TaskGroup.__aexit__ -> album TMBTE 0x7fc93173fa50 or a tree like this: python -m asyncio pstree 12345 └── ( T ) Task-1 └── main example.py:13 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) Sundowning │ └── album example.py:8 │ └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 │ └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 │ ├── ( T ) TNDNBTG │ │ └── play example.py:4 │ │ └── sleep Lib/asyncio/tasks.py:702 │ └── ( T ) Levitate │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) TMBTE └── album example.py:8 └── TaskGroup.__aexit__ Lib/asyncio/taskgroups.py:72 └── TaskGroup._aexit Lib/asyncio/taskgroups.py:121 ├── ( T ) DYWTYLM │ └── play example.py:4 │ └── sleep Lib/asyncio/tasks.py:702 └── ( T ) Aqua Regia └── play example.py:4 └── sleep Lib/asyncio/tasks.py:702 If a cycle is detected in the async await graph (which could indicate a programming issue), the tool raises an error and lists the cycle paths that prevent tree construction: python -m asyncio pstree 12345 ERROR: await-graph contains cycles - cannot print a tree! cycle: Task-2 → Task-3 → Task-2 (Contributed by Pablo Galindo, Łukasz Langa, Yury Selivanov, and Marta Gomez Macias in gh-91048 .) Concurrent safe warnings control ¶ The warnings.catch_warnings context manager will now optionally use a context variable for warning filters. This is enabled by setting the context_aware_warnings flag, either with the -X command-line option or an environment variable. This gives predictable warnings control when using catch_warnings combined with multiple threads or asynchronous tasks. The flag defaults to true for the free-threaded build and false for the GIL-enabled build. (Contributed by Neil Schemenauer and Kumar Aditya in gh-130010 .) Other language changes ¶ All Windows code pages are now supported as ‘cpXXX’ codecs on Windows. (Contributed by Serhiy Storchaka in gh-123803 .) Implement mixed-mode arithmetic rules combining real and complex numbers as specified by the C standard since C99. (Contributed by Sergey B Kirpichev in gh-69639 .) More syntax errors are now detected regardless of optimisation and the -O command-line option. This includes writes to __debug__ , incorrect use of await , and asynchronous comprehensions outside asynchronous functions. For example, python -O -c 'assert (__debug__ := 1)' or python -O -c 'assert await 1' now produce SyntaxError s. (Contributed by Irit Katriel and Jelle Zijlstra in gh-122245 & gh-121637 .) When subclassing a pure C type, the C slots for the new type are no longer replaced with a wrapped version on class creation if they are not explicitly overridden in the subclass. (Contributed by Tomasz Pytel in gh-132284 .) Built-ins ¶ The bytes.fromhex() and bytearray.fromhex() methods now accept ASCII bytes and bytes-like objects . (Contributed by Daniel Pope in gh-129349 .) Add class methods float.from_number() and complex.from_number() to convert a number to float or complex type correspondingly. They raise a TypeError if the argument is not a real number. (Contributed by Serhiy Storchaka in gh-84978 .) Support underscore and comma as thousands separators in the fractional part for floating-point presentation types of the new-style string formatting (with format() or f-strings ). (Contributed by Sergey B Kirpichev in gh-87790 .) The int() function no longer delegates to __trunc__() . Classes that want to support conversion to int() must implement either __int__() or __index__() . (Contributed by Mark Dickinson in gh-119743 .) The map() function now has an optional keyword-only strict flag like zip() to check that all the iterables are of equal length. (Contributed by Wannes Boeykens in gh-119793 .) The memoryview type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-126012 .) Using NotImplemented in a boolean context will now raise a TypeError . This has raised a DeprecationWarning since Python 3.9. (Contributed by Jelle Zijlstra in gh-118767 .) Three-argument pow() now tries calling __rpow__() if necessary. Previously it was only called in two-argument pow() and the binary power operator. (Contributed by Serhiy Storchaka in gh-130104 .) super objects are now copyable and pickleable . (Contributed by Serhiy Storchaka in gh-125767 .) Command line and environment ¶ The import time flag can now track modules that are already loaded (‘cached’), via the new -X importtime=2 . When such a module is imported, the self and cumulative times are replaced by the string cached . Values above 2 for -X importtime are now reserved for future use. (Contributed by Noah Kim and Adam Turner in gh-118655 .) The command-line option -c now automatically dedents its code argument before execution. The auto-dedentation behavior mirrors textwrap.dedent() . (Contributed by Jon Crall and Steven Sun in gh-103998 .) -J is no longer a reserved flag for Jython , and now has no special meaning. (Contributed by Adam Turner in gh-133336 .) PEP 758: Allow except and except* expressions without brackets ¶ The except and except* expressions now allow brackets to be omitted when there are multiple exception types and the as clause is not used. For example: try : connect_to_server () except TimeoutError , ConnectionRefusedError : print ( 'The network has ceased to be!' ) (Contributed by Pablo Galindo and Brett Cannon in PEP 758 and gh-131831 .) PEP 765: Control flow in finally blocks ¶ The compiler now emits a SyntaxWarning when a return , break , or continue statement have the effect of leaving a finally block. This change is specified in PEP 765 . In situations where this change is inconvenient (such as those where the warnings are redundant due to code linting), the warning filter can be used to turn off all syntax warnings by adding ignore::SyntaxWarning as a filter. This can be specified in combination with a filter that converts other warnings to errors (for example, passing -Werror -Wignore::SyntaxWarning as CLI options, or setting PYTHONWARNINGS=error,ignore::SyntaxWarning ). Note that applying such a filter at runtime using the warnings module will only suppress the warning in code that is compiled after the filter is adjusted. Code that is compiled prior to the filter adjustment (for example, when a module is imported) will still emit the syntax warning. (Contributed by Irit Katriel in gh-130080 .) Incremental garbage collection ¶ The cycle garbage collector is now incremental. This means that maximum pause times are reduced by an order of magnitude or more for larger heaps. There are now only two generations: young and old. When gc.collect() is not called directly, the GC is invoked a little less frequently. When invoked, it collects the young generation and an increment of the old generation, instead of collecting one or more generations. The behavior of gc.collect() changes slightly: gc.collect(1) : Performs an increment of garbage collection, rather than collecting generation 1. Other calls to gc.collect() are unchanged. (Contributed by Mark Shannon in gh-108362 .) Default interactive shell ¶ The default interactive shell now highlights Python syntax. The feature is enabled by default, save if PYTHON_BASIC_REPL or any other environment variable that disables colour is set. See Controlling color for details. The default color theme for syntax highlighting strives for good contrast and exclusively uses the 4-bit VGA standard ANSI color codes for maximum compatibility. The theme can be customized using an experimental API _colorize.set_theme() . This can be called interactively or in the PYTHONSTARTUP script. Note that this function has no stability guarantees, and may change or be removed. (Contributed by Łukasz Langa in gh-131507 .) The default interactive shell now supports import auto-completion. This means that typing import co and pressing <Tab> will suggest modules starting with co . Similarly, typing from concurrent import i will suggest submodules of concurrent starting with i . Note that autocompletion of module attributes is not currently supported. (Contributed by Tomas Roun in gh-69605 .) New modules ¶ annotationlib : For introspecting annotations . See PEP 749 for more details. (Contributed by Jelle Zijlstra in gh-119180 .) compression (including compression.zstd ): A package for compression-related modules, including a new module to support the Zstandard compression format. See PEP 784 for more details. (Contributed by Emma Harper Smith, Adam Turner, Gregory P. Smith, Tomas Roun, Victor Stinner, and Rogdham in gh-132983 .) concurrent.interpreters : Support for multiple interpreters in the standard library. See PEP 734 for more details. (Contributed by Eric Snow in gh-134939 .) string.templatelib : Support for template string literals (t-strings). See PEP 750 for more details. (Contributed by Jim Baker, Guido van Rossum, Paul Everitt, Koudai Aono, Lysandros Nikolaou, Dave Peck, Adam Turner, Jelle Zijlstra, Bénédikt Tran, and Pablo Galindo Salgado in gh-132661 .) Improved modules ¶ argparse ¶ The default value of the program name for argparse.ArgumentParser now reflects the way the Python interpreter was instructed to find the __main__ module code. (Contributed by Serhiy Storchaka and Alyssa Coghlan in gh-66436 .) Introduced the optional suggest_on_error parameter to argparse.ArgumentParser , enabling suggestions for argument choices and subparser names if mistyped by the user. (Contributed by Savannah Ostrowski in gh-124456 .) Enable color for help text, which can be disabled with the optional color parameter to argparse.ArgumentParser . This can also be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-130645 .) ast ¶ Add compare() , a function for comparing two ASTs. (Contributed by Batuhan Taskaya and Jeremy Hylton in gh-60191 .) Add support for copy.replace() for AST nodes. (Contributed by Bénédikt Tran in gh-121141 .) Docstrings are now removed from an optimized AST in optimization level 2. (Contributed by Irit Katriel in gh-123958 .) The repr() output for AST nodes now includes more information. (Contributed by Tomas Roun in gh-116022 .) When called with an AST as input, the parse() function now always verifies that the root node type is appropriate. (Contributed by Irit Katriel in gh-130139 .) Add new options to the command-line interface: --feature-version , --optimize , and --show-empty . (Contributed by Semyon Moroz in gh-133367 .) asyncio ¶ The function and methods named create_task() now take an arbitrary list of keyword arguments. All keyword arguments are passed to the Task constructor or the custom task factory. (See set_task_factory() for details.) The name and context keyword arguments are no longer special; the name should now be set using the name keyword argument of the factory, and context may be None . This affects the following function and methods: asyncio.create_task() , asyncio.loop.create_task() , asyncio.TaskGroup.create_task() . (Contributed by Thomas Grainger in gh-128307 .) There are two new utility functions for introspecting and printing a program’s call graph: capture_call_graph() and print_call_graph() . See Asyncio introspection capabilities for more details. (Contributed by Yury Selivanov, Pablo Galindo Salgado, and Łukasz Langa in gh-91048 .) calendar ¶ By default, today’s date is highlighted in color in calendar ’s command-line text output. This can be controlled by environment variables . (Contributed by Hugo van Kemenade in gh-128317 .) concurrent.futures ¶ Add a new executor class, InterpreterPoolExecutor , which exposes multiple Python interpreters in the same process (‘subinterpreters’) to Python code. This uses a pool of independent Python interpreters to execute calls asynchronously. This is separate from the new interpreters module introduced by PEP 734 . (Contributed by Eric Snow in gh-124548 .) On Unix platforms other than macOS, ‘forkserver’ is now the default start method for ProcessPoolExecutor (replacing ‘fork’ ). This change does not affect Windows or macOS, where ‘spawn’ remains the default start method. If the threading incompatible fork method is required, you must explicitly request it by supplying a multiprocessing context mp_context to ProcessPoolExecutor . See forkserver restrictions for information and differences with the fork method and how this change may affect existing code with mutable global shared variables and/or shared objects that can not be automatically pickled . (Contributed by Gregory P. Smith in gh-84559 .) Add two new methods to ProcessPoolExecutor , terminate_workers() and kill_workers() , as ways to terminate or kill all living worker processes in the given pool. (Contributed by Charles Machalow in gh-130849 .) Add the optional buffersize parameter to Executor.map to limit the number of submitted tasks whose results have not yet been yielded. If the buffer is full, iteration over the iterables pauses until a result is yielded from the buffer. (Contributed by Enzo Bonnal and Josh Rosenberg in gh-74028 .) configparser ¶ configparser will no longer write config files it cannot read, to improve security. Attempting to write() keys containing delimiters or beginning with the section header pattern will raise an InvalidWriteError . (Contributed by Jacob Lincoln in gh-129270 .) contextvars ¶ Support the context manager protocol for Token objects. (Contributed by Andrew Svetlov in gh-129889 .) ctypes ¶ The layout of bit fields in Structure and Union objects is now a closer match to platform defaults (GCC/Clang or MSVC). In particular, fields no longer overlap. (Contributed by Matthias Görgens in gh-97702 .) The Structure._layout_ class attribute can now be set to help match a non-default ABI. (Contributed by Petr Viktorin in gh-97702 .) The class of Structure / Union field descriptors is now available as CField , and has new attributes to aid debugging and introspection. (Contributed by Petr Viktorin in gh-128715 .) On Windows, the COMError exception is now public. (Contributed by Jun Komoda in gh-126686 .) On Windows, the CopyComPointer() function is now public. (Contributed by Jun Komoda in gh-127275 .) Add memoryview_at() , a function to create a memoryview object that refers to the supplied pointer and length. This works like ctypes.string_at() except it avoids a buffer copy, and is typically useful when implementing pure Python callback functions that are passed dynamically-sized buffers. (Contributed by Rian Hunter in gh-112018 .) Complex types, c_float_complex , c_double_complex , and c_longdouble_complex , are now available if both the compiler and the libffi library support complex C types. (Contributed by Sergey B Kirpichev in gh-61103 .) Add ctypes.util.dllist() for listing the shared libraries loaded by the current process. (Contributed by Brian Ward in gh-119349 .) Move ctypes.POINTER() types cache from a global internal cache ( _pointer_type_cache ) to the _CData.__pointer_type__ attribute of the corresponding ctypes types. This will stop the cache from growing without limits in some situations. (Contributed by Sergey Miryanov in gh-100926 .) The py_object type now supports subscription, making it a generic type . (Contributed by Brian Schubert in gh-132168 .) ctypes now supports free-threading builds . (Contributed by Kumar Aditya and Peter Bierma in gh-127945 .) curses ¶ Add the assume_default_colors() function, a refinement of the use_default_colors() function which allows changing the color pair 0 . (Contributed by Serhiy Storchaka in gh-133139 .) datetime ¶ Add the strptime() method to the datetime.date and datetime.time classes. (Contributed by Wannes Boeykens in gh-41431 .) decimal ¶ Add Decimal.from_number() as an alternative constructor for Decimal . (Contributed by Serhiy Storchaka in gh-121798 .) Expose IEEEContext() to support creation of contexts corresponding to the IEEE 754 (2008) decimal interchange formats. (Contributed by Sergey B Kirpichev in gh-53032 .) difflib ¶ Comparison pages with highlighted changes generated by the HtmlDiff class now support ‘dark mode’. (Contributed by Jiahao Li in gh-129939 .) dis ¶ Add support for rendering full source location information of instructions , rather than only the line number. This feature is added to the following interfaces via the show_positions keyword argument: dis.Bytecode dis.dis() dis.distb() dis.disassemble() This feature is also exposed via dis --show-positions . (Contributed by Bénédikt Tran in gh-123165 .) Add the dis --specialized command-line option to show specialized bytecode. (Contributed by Bénédikt Tran in gh-127413 .) errno ¶ Add the EHWPOISON error code constant. (Contributed by James Roy in gh-126585 .) faulthandler ¶ Add support for printing the C stack trace on systems that support it via the new dump_c_stack() function or via the c_stack argument in faulthandler.enable() . (Contributed by Peter Bierma in gh-127604 .) fnmatch ¶ Add filterfalse() , a function to reject names matching a given pattern. (Contributed by Bénédikt Tran in gh-74598 .) fractions ¶ A Fraction object may now be constructed from any object with the as_integer_ratio() method. (Contributed by Serhiy Storchaka in gh-82017 .) Add Fraction.from_number() as an alternative constructor for Fraction . (Contributed by Serhiy Storchaka in gh-121797 .) functools ¶ Add the Placeholder sentinel. This may be used with the partial() or partialmethod() functions to reserve a place for positional arguments in the returned partial object . (Contributed by Dominykas Grigonis in gh-119127 .) Allow the initial parameter of reduce() to be passed as a keyword argument. (Contributed by Sayandip Dutta in gh-125916 .) getopt ¶ Add support for options with optional arguments. (Contributed by Serhiy Storchaka in gh-126374 .) Add support for returning intermixed options and non-option arguments in order. (Contributed by Serhiy Storchaka in gh-126390 .) getpass ¶ Support keyboard feedback in the getpass() function via the keyword-only optional argument echo_char . Placeholder characters are rendered whenever a character is entered, and removed when a character is deleted. (Contributed by Semyon Moroz in gh-77065 .) graphlib ¶ Allow TopologicalSorter.prepare() to be called more than once as long as sorting has not started. (Contributed by Daniel Pope in gh-130914 .) heapq ¶ The heapq module has improved support for working with max-heaps, via the following new functions: heapify_max() heappush_max() heappop_max() heapreplace_max() heappushpop_max() hmac ¶ Add a built-in implementation for HMAC ( RFC 2104 ) using formally verified code from the HACL* project. This implementation is used as a fallback when the OpenSSL implementation of HMAC is not available. (Contributed by Bénédikt Tran in gh-99108 .) http ¶ Directory lists and error pages generated by the http.server module allow the browser to apply its default dark mode. (Contributed by Yorik Hansen in gh-123430 .) The http.server module now supports serving over HTTPS using the http.server.HTTPSServer class. This functionality is exposed by the command-line interface ( python -m http.server ) through the following options: --tls-cert <path> : Path to the TLS certificate file. --tls-key <path> : Optional path to the private key file. --tls-password-file <path> : Optional path to the password file for the private key. (Contributed by Semyon Moroz in gh-85162 .) imaplib ¶ Add IMAP4.idle() , implementing the IMAP4 IDLE command as defined in RFC 2177 . (Contributed by Forest in gh-55454 .) inspect ¶ signature() takes a new argument annotation_format to control the annotationlib.Format used for representing annotations. (Contributed by Jelle Zijlstra in gh-101552 .) Signature.format() takes a new argument unquote_annotations . If true, string annotations are displayed without surrounding quotes. (Contributed by Jelle Zijlstra in gh-101552 .) Add function ispackage() to determine whether an object is a package or not. (Contributed by Zhikang Yan in gh-125634 .) io ¶ Reading text from a non-blocking stream with read may now raise a BlockingIOError if the operation cannot immediately return bytes. (Contributed by Giovanni Siragusa in gh-109523 .) Add the Reader and Writer protocols as simpler alternatives to the pseudo-protocols typing.IO , typing.TextIO , and typing.BinaryIO . (Contributed by Sebastian Rittau in gh-127648 .) json ¶ Add exception notes for JSON serialization errors that allow identifying the source of the error. (Contributed by Serhiy Storchaka in gh-122163 .) Allow using the json module as a script using the -m switch: python -m json . This is now preferred to python -m json.tool , which is soft deprecated . See the JSON command-line interface documentation. (Contributed by Trey Hunner in gh-122873 .) By default, the output of the JSON command-line interface is highlighted in color. This can be controlled by environment variables . (Contributed by Tomas Roun in gh-131952 .) linecache ¶ getline() can now retrieve source code for frozen modules. (Contributed by Tian Gao in gh-131638 .) logging.handlers ¶ QueueListener objects now support the context manager protocol. (Contributed by Charles Machalow in gh-132106 .) QueueListener.start now raises a RuntimeError if the listener is already started. (Contributed by Charles Machalow in gh-132106 .) math ¶ Added more detailed error messages for domain errors in the module. (Contributed by Charlie Zhao and Sergey B Kirpichev in gh-101410 .) mimetypes ¶ Add a public command-line for the module, invoked via python -m mimetypes . (Contributed by Oleg Iarygin and Hugo van Kemenade in gh-93096 .) Add several new MIME types based on RFCs and common usage: Microsoft and RFC 8081 MIME types for fonts Embedded OpenType: application/vnd.ms-fontobject OpenType Layout (OTF) font/otf TrueType: font/ttf WOFF 1.0 font/woff WOFF 2.0 font/woff2 RFC 9559 | 2026-01-13T08:49:47 |
https://future.forem.com/dan_ledger_ce2886f0037972/2025-12-23-daily-robotics-news-58pf#comments | 2025-12-23 Daily Robotics News - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Dan Posted on Dec 23, 2025 2025-12-23 Daily Robotics News # robotics Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News In the fast-evolving world of robotics, December 21-22, 2025, brought a flurry of developments underscoring the maturation of humanoid platforms, breakthroughs in dexterous manipulation, cutting-edge hardware designs, and real-world industry rollouts. From Tesla's unflappable robotaxis navigating chaos to Physical Intelligence's humanoids tackling "Robot Olympics" challenges, the sector demonstrated tangible progress toward scalable autonomy. Chinese firms like Unitree Robotics and CATL pushed boundaries with performative and productive deployments, while academic innovations in friction modeling and video-based learning promised to accelerate sim-to-real transfers. This report synthesizes 37 key updates, focusing squarely on robotics hardware, control systems, and deployments—distilling themes into narratives rich with technical depth, implications, and cross-connections. A dramatic San Francisco power outage on December 21 exposed stark contrasts in autonomous vehicle robustness, with Tesla's robotaxis sailing through while Waymo's fleet froze entirely . Elon Musk confirmed that Tesla Robotaxis remained "unaffected," crediting billions of real-world miles in training data that equipped full self-driving (FSD) systems to handle unpredictable scenarios like darkened traffic lights. In a thread amplifying this, Mario Nawfal noted how Waymo's map-dependent approach faltered under chaos, whereas Tesla's vision-based FSD "kept rolling" seamlessly, turning theoretical differences into practical traffic wins. This event validates end-to-end learning's superiority for edge cases, where simulated perfection crumbles but messy real data prevails—potentially accelerating regulatory approvals for unsupervised operations. "Waymo’s robotaxis got a little too real last night - by completely shutting down when San Francisco’s power outage knocked out traffic lights. Meanwhile, Teslas on FSD? Kept rolling. No drama, no headlines - just handling chaos like it’s a walk in the park." – Mario Nawfal The implications ripple across robotics deployments, as Tesla's success—bolstered by reports of over 6000 consecutive miles on FSD—signals readiness for humanoid extensions like Optimus. Hardware-wise, this underscores the value of camera-centric stacks over lidar-heavy ones, reducing failure modes in power-loss scenarios common to urban grids. Industry watchers see this as a pivot point: competitors may shift toward data-hungry, vision-first paradigms, pressuring firms like Waymo to diversify beyond geofenced simulations. Connected to broader trends, it foreshadows robotaxis reshaping streetscapes, as Elon Musk hinted with transformative visuals , demanding "insane amount of work" yet deeming it feasible. Beyond immediate ops, this blackout testbed highlights FSD's role in humanoid mobility; Tesla's navigation prowess could directly port to bipedal platforms, enabling warehouse-to-street fluidity. Economically, zero-downtime resilience boosts ROI for fleets, with Tesla eyeing volume production amid rising U.S. manufacturing automation per Kawasaki Robotics insights on output surges . As deployments scale, expect interoperability challenges—how do resilient AVs sync with humanoid escorts in mixed environments? This convergence, rooted in today's proof-of-concept, positions Tesla as a linchpin in robotics' logistical backbone. Unitree Robotics stole the spotlight with humanoid performances blending seamlessly with human dancers, as captured in viral clips where bots matched timing and flair down to micro-movements. Rohan Paul marveled at their progress, warning "background dancers seriously need to find alternative jobs," while Tuo Liu noted performers like Leehom Wang treating them as equals from alternate angles. These aren't gimmicks; they showcase contact-rich control at 100-500 Hz with rapid recovery, per Rohan Paul's analysis of underlying datasets and diffusion policies. In Shenzhen's Robot Valley , such feats normalize, with Unitree pairing humanoids and quadrupeds for patrol duties , scaling hours sans headcount. "China is deploying Robots everywhere. Here Unitree's humanoid robots + quadruped robot dogs patrol and perform duty in a team. You scale patrol hours without scaling headcount." – Rohan Paul Transitioning to production, CATL's Spirit AI humanoids achieved 99% success on high-voltage plug-ins , tripling human shift volumes via vision-language-action (VLA) models that adapt to cable shifts in real-time. Unlike rigid industrial arms needing fixturing, these end-to-end systems output motor actions from camera feeds and goals, sidestepping brittle scripts for fiddly tasks. This marks a shift from pilots to sustained lines, targeting safety-critical steps humans avoided. Meanwhile, Midea Group's MIRO U—a one-head-six-arms wheeled titan—claims 30% efficiency gains via vertical lifts and 360° rotation, redefining multi-tool factories. These deployments signal humanoids' industrial viability, with China's 7,705 patents in five years dwarfing the U.S.'s 1,561, per Morgan Stanley—a proxy for innovation velocity in actuators and control. Projections of 6.5 billion robots by 2050 (34% drones, 29% home units) underscore this, as Shenzhen's unmanned vehicles and cleaning bots proliferate . Implications? Humanoids commoditize labor-intensive roles, from patrols to plugs, but raise questions on maintenance and ethics—like Tuo Liu's query on dog-walking bots . Linking to entertainment, Disney's stunt Spider-Man robot( https://x.com/rohanpaul_ai/status/2003143745966055588 ) launches 25m with mid-air flips, threatening stunt jobs while proving acrobatic hardware's theme-park readiness. Tesla Optimus V2.5( https://x.com/rohanpaul_ai/status/2002878246187393226)'s party appearance, flaunting human-like hands, ties consumer-facing polish to factory grit. The synergy amplifies: performative bots like Unitree build public buy-in, easing factory adoptions like CATL's, while patents fuel hardware iterations. Economically, this compresses timelines—humanoids in homes by 2030? Feasibility hinges on scaling data like Tesla's FSD miles to manipulation episodes. Challenges persist: CATL's 3x throughput assumes uptime; real-world drift could demand hybrid human oversight. Yet, as performances normalize, expect global emulation, with U.S. firms like Kawasaki Robotics riding manufacturing's golden age via automation levers. Physical Intelligence's latest push saw their π0.6 model fine-tuned for Benjie Holson's "Robot Olympics"—five events tackling Moravec's Paradox, where robots excel at chess but flop at pan-washing. Gold medal feats included self-closing door traversal, key-unlocking with precise force, and frying pan scrubbing (both sides, with soap). Silver/bronze wins spanned sock inversion (bypassing gripper limits), peanut butter sandwiches (long-horizon deformables), window cleaning, orange peeling (tool-assisted), and counter wiping. All autonomous, these highlight fine-tuning's edge over scratch training, which flopped entirely. "[Thread 1/11] We got our robots to wash pans, clean windows, make peanut butter sandwiches, and more! Fine-tuning our latest model enables all of these tasks, and this has interesting implications for robotics, Moravec's paradox, and the future of large models in embodied AI." – Physical Intelligence Chris Paxton praised the hardware-learning combo for "very challenging tasks," noting positivity bias mitigation via external benchmarks and video-native models bypassing single-frame limits. Pretraining explains unlocks—more data models physics better—while unnatural motions (e.g., sock flips) reveal hardware caps. Success rates undisclosed, but task diversity (tools, forces, horizons) implies generalization potential for homes. Tied to RTC, their Real-Time Action Chunking enables VLAs like π0/π0.5 to act mid-inference, yielding smoother motions and latency-proof precision—even at 200ms delays. This Olympics blitz connects to mimic-video's video-first pretraining, where mimic-video uses internet videos for dynamics, achieving 10x sample efficiency and 2x convergence on dexterous hands. Led by Jonas Pai, Liam Achenbach, Oier Mees, and Elvis Nava from mimicrobotics, Microsoft Zurich, ETH Zurich, UC Berkeley, and NVIDIA Robotics, it denoise video plans then actions—outpacing VLM-backboned VLAs starved of motion data. Oracle tests showed visual prediction alone yields perfect trajectories, hinting at unified video-action paradigms. Implications are profound: fine-tuning bridges sim-to-real for everyday chores, eroding Moravec's wall. Hardware demands evolve—narrow grippers for sleeves, sharper tools for peels—spurring actuators like Contactile's tactile grippers , demoed plugging cables blindly. Broader trends? Dexterity cascades to humanoids; Unitree's dances preview Olympian grace in factories. Yet, Paxton's caveats—task-specific policies, no home-generality—temper hype, emphasizing data volume as the unlock. Expanding, these feats validate VLAs for non-prehensile tasks, like CMU's sound-modeled friction on UR5e: contact mics detect slides, learning dynamic mu for 86% less displacement in high-speed tray transport. Perfect for fragiles, it complements RTC's latency hacks and mimic-video's efficiency, forming a dexterity stack. Lego's precision assembly —vibratory sorting, arm insertions—mirrors Olympics' engineering grit, where speed trumps toys. Collectively, they signal production-ready manipulation, with factories like CATL's as proving grounds. Hardware ingenuity shone in hybrid designs, like DUAWLFIN's ground-aerial robot : unified actuation for 0.1s mode-switches, 30° climbs, 2m/s wheels at 15W, fully 3D-printable/open-source. Rethinks drones for urban logistics sans deformation, blending quad flight and car rolls. Echoing this, a $20 dorm-built drone with PS3 Eye mocap hits mm-precision via 150fps cams and nested PID—despite wobbly hovers fueling SLAM dissertations. Purdue's Purdubik’s Cube solves Rubik's in 0.103s , Guinness-fast via custom core preventing snaps—hardware-software symbiosis at blink speeds. Disney's Spider-Man flips 25m autonomously, mid-air adjusting for stunt-grade landings. Multi-arm peak: Midea's MIRO U, humanoid-headed with six arms on wheels, zips lines for 30% gains. These prototypes portend versatile fleets: DUAWLFIN for last-mile, Purdue for micro-dexterity, Disney for entertainment ROIs. Implications? Lowers barriers—open-source accelerates iteration, as Shenzhen's ecosystem shows with ubiquitous unmanned cleaners. Ties to humanoids: Optimus hands echo Purdue precision; MIRO U scales CATL plugs. RoboPapers spotlighted 3D Gaussian Splatting Worlds (GS World) , where Lucca Chiang's team reconstructs interactive sims from real data, skipping costly teleop for zero-shot transfer. Physics engines atop photoreal splats train policies deploying instantly IRL—bypassing sim-build pains. Chris Paxton demoed sim videos indistinguishable from real, emphasizing real-to-sim pipelines. "It’s long been a dream of roboticists to be able to teach a robot in simulation so as to skip the long and expensive process of collecting large amounts of real-world training data." – RoboPapers Paired with mimic-video's video grounding and Physical Intelligence's fine-tunes, this slashes data hunger. For humanoids, it unlocks diverse envs sans falls; factories gain plug-and-play policies. Trends? Accelerates China's patent blitz, U.S. manufacturing per Kawasaki. Challenges: splat fidelity under dynamics, but zero-shot promise redefines scaling. Elon Musk framed robotics' destiny: civilization ends or AI/robots eliminate scarcity , rendering money obsolete. Teasing Optimus-driven street overhauls —"this will change the whole look"—he acknowledged the "insane work" ahead but affirmed possibility. This optimism contextualizes Tesla's blackout win and Optimus party strut, positioning humanoids as abundance engines. Implications? Fuels investments, aligning with Morgan Stanley's billions-scale forecast. Yet, scarcity's demise demands ethical deployments—patrols today, ubiquity tomorrow. (Word count: 5,872) Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News 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 Dan Follow Location boston, ma Joined Dec 6, 2025 More from Dan 2025-12-20 Daily Robotics News # robotics 2025-12-14 Daily Robotics News # robotics 2025-12-12 Daily Robotics News # robotics 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
http://www.aiu.edu.gm/ | AIUWA :: American International University West Africa --> Contact Us | Sitemap The Gambia Home About AIUWA History � Mission � Vision Accreditation Affiliations From the President For Prospective Students Graduation Speech Facilities Newsletter & In News FAQs 2015 Graduation Photos Terms and Conditions Academics Academic Calendar Programs Doctor of Medicine (MD) --> Medicine Program Doctor of Medicine (MD) Doctor of Dental Medicine (DMD) --> Dental Program Doctor of Dental Medicine (DMD) Doctor of Pharmacy (Pharm D) --> Pharmacy Program Doctor of Pharmacy (Pharm D) Nursing Bachelor of Nursing Science (BSN) RN to BSN Degree Program Specialization BSN Anesthesia BSN Perioperative BSN Psychiatry BSN Pediatric BSN Midwifery Health Professional Medical Lab Technician - AAS Degree Master of Public Health Arts and Finance Bachelor of Science: Accounting and Finance Bachelor of Science: Philosophy, Politics and Economics Bachelor of Science: Management Bachelor of Science: Human Resources and Labor Information Technology Bachelor of Computer Applications (BCA) Medical Lab Technician - AAS Degree --> Health Professional Medical Lab Technician - AAS Degree Arts and Finance Bachelor of Science: Accounting and Finance Bachelor of Science: Philosophy, Politics and Economics Bachelor of Science: Management Bachelor of Science: Human Resources and Labor Information Technology Bachelor of Computer Applications (BCA) Arts and Finance Bachelor of Science: Accounting and Finance Bachelor of Science: Philosophy, Politics and Economics Bachelor of Science: Management Bachelor of Science: Human Resources and Labor Information Technology Bachelor of Computer Applications (BCA) --> Curriculum Doctor of Medicine (MD) Doctor of Dental Medicine (DMD) Doctor of Pharmacy (Pharm D) Nursing Medical Lab Technician - AAS Degree Dental Assistance - AAS Degree Telemedicine BCA Program Colleges College of Medicine College of Dentistry College of Pharmacy College of Nursing College of Health Professional College of Management --> College of Medicine --> College of Medicine College of Dentistry College of Pharmacy College of Nursing College of Health Professional --> College of Health Professional College of Health Professional Master of Public Health College of Management and Information Technology Fees and Other Info Admission Information Fees Student Visas Accommodations Scholarships & Financial Aid Life in The Gambia & Guinea Forms � Catalog � Brochures PAY NOW BY PAYPAL Faculty and Staff Apply for Employment Faculty Login AIUWA WebMail Current Students Student Login AIUWA WebMail Student Groups & Affiliations --> --> --> --> --> --> --> IMED FAIMER Directory published by Education Commission for Foreign Medical Graduates (US) and is an institutional member of European Medical Association. --> American International University West Africa (AIUWA) is a registered and approved institution of higher education by Ministry of Higher Education, Research, Science and Technology and Ministry of Health and Social Welfare, Government of The Gambia. Cost effective and World-Class education is available to qualified and motivated students directly after High School. AIU HEALTH SCIENCE CENTER Medical and health programs based on curriculum recommended by respective US professional councils for accreditation are offered through AIU Health Science Center at The Gambia consisting of 5 Colleges. Enrollment to Medical and Dental Program is not available for 2026 College of Medicine - Doctor of Medicine (M.D.) Degree.--> Offers a (6+ year) program directly after high school leading to Doctor of Medicine (M.D.) Degree. All documentation for full registration and accreditation have been provided to The Gambia Medical and Dental Council. AIUWA is listed in The World Directory of Medical Schools which has been developed through a partnership between the World Federation for Medical Education (WFME) and the Foundation for Advancement of International Medical Education and Research (FAIMER). AIUWA is a full member of Association of African Universities and European Medical Association. College of Dentistry - Offers a (6+ year) program directly after high school leading to Doctor of Dental Medicine (D.M.D.) Degree. College of Pharmacy - Offers a (5+ year) program directly after high school leading to Doctor of Pharmacy (Pharm D.) Degree. College of Nursing - Offers a (4+ year) accelerated program after high school leading to Bachelor of Science Nursing (BSN) Degree. RN to BSN (Honors) Degree (2+ year) program is available for specialization Anesthesia, Perioperative, Psychiatry and Midwifery. College of Health Professionals - Offers (2+ year) program after high school leading to Associate of Applied Science degree (AAS): Medical Laboratory Technician (MLT) Pharmacy Technician (PTech) Dental Assistant (DA) HUMANITIES, FINANCE, MANAGEMENT AND INFORMATION TECHNOLOGY College of Management & Information Technology Accounting & Finance [Plus ACCA & MOS] Offers (4) year degree program after high school leading to Bachelors of Science Degree in Accountancy and Finance. Business Administration [Plus MCIP & MOS] Offers (4) year degree program after high school leading to Bachelors of Science Degree in Business Administration. Computer Science & Technology [Plus any of Microsoft, Oracle, Cisco, (ISC) � & MOS Certifications] Offers (4) year degree program after high school leading to Bachelors of Science Degree in Computer Science & Technology. Human Resources & Labor Management [Plus PHR & MOS] Offers (4) year degree program after high school leading to Bachelors of Science Degree in Human Resources and Labor Management. Philosophy, Politics & Economics [Plus ACE or CFA & MOS] Offers (4) year degree program after high school leading to Bachelors of Science Degree in Philosophy Politics and Economics. New Campus in Gambia Registration of New Students Library Chemistry Laboratory Placement test being taken on September 7, 2011. AIU Students attending the Telemedicine Lecture 7/13/2012 --> PAY FEE Click here for credit card payment --> Click Here to see Who We Are! --> --> --> Already registered? Login here to access your application Username: Password: Forgot Password? --> --> --> Latest News 9th Graduation Ceremony 2025 Published: June 5, 2025 Celebrating Excellence: American International University West Africa (AIUWA) recently celebrated its 9th Graduation Ceremony . This milestone event honored 291 graduates across 15 different programs. Key highlights from the ceremony include: Employment Success: 86% of AIUWA graduates are gainfully employed within 60 days of completion. Institutional Growth: Reflecting on 14 years of providing world-class education in The Gambia. National Impact: Guest speakers emphasized the importance of public-private partnerships in driving healthcare and education. Apply Admissions 2026 More News>> Have questions about our school? Ask our online representative on a live chat or create a ticket when they are offline. copyright © American International University West Africa www.aiu.edu.gm. All rights reserved 2026. { COVID 19 UPDATE } DATED OCTOBER 12, 2020 MESSAGE FROM OUR CHANCELLOR FROM MARCH 18 TO APRIL 8 ALL STUDENTS SHOULD CALL UNIVERSITY ADMINISTRATION TO GET THEIR CREDENTIALS FOR ONLINE CLASSES IN CASE GOVERNMENT EXTENDS CURRENT PROCLAMATION. --> It has been a little over six months since we had in person classes at AIUWA. While the online classes have been held as scheduled, the challenges have been enormous. Going online and remote has taught us much over the last few months. It has validated the value of the presence of a faculty in the classroom. I am delighted to inform you that, as per directives received from Ministry of Higher Education, Research, Science and Technology, the in person classes can begin at the University campuses beginning October 14, 2020. I look forward to in-person classes. As we prepare to start the classes, I take this opportunity to remind all faculty, staff and students that Covid 19 has mandated new norms which should be adhered to in order to prevent infections. Ministry of Health has issued measures to be followed rigorously, which includes wearing mask at all times, maintain social distancing and practicing good hygiene while on the campus. The uncertainly in this situation will certainly continue into the foreseeable future, but I am committed to providing you with the clearest path forward that puts our students first while maintaining the health and safety of our whole community. Stay Safe. Stay Healthy. DINESH SHUKLA STAY SAFE --> ENTER SITE | 2026-01-13T08:49:47 |
https://github.com/sunny7899 | sunny7899 (sunny) · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} sunny7899 Follow Overview Repositories 26 Projects 0 Packages 0 Stars 146 More Overview Repositories Projects Packages Stars sunny7899 Follow 🏠 Working from home sunny sunny7899 🏠 Working from home Follow Loves to write Code | Professional | Quick | Logical | Consistent | Industrious | Enthusiastic | code more and drink coffee 29 followers · 59 following Delhi https://twitter.com/Sunny_g001 Achievements x2 Achievements x2 Organizations Block or Report Block or report sunny7899 --> Block user Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users . You must be logged in to block users. Add an optional note Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you. Block user Report abuse Contact GitHub support about this user’s behavior. Learn more about reporting abuse . Report abuse Overview Repositories 26 Projects 0 Packages 0 Stars 146 More Overview Repositories Projects Packages Stars sunny7899 / README .md 🎉 About Me: I am a full-stack developer with 8+ years of experience, passionate about the JavaScript ecosystem. I have a bachelor's degree in computer science. I am most skilled and passionate about Angular and React. I am able to provide meaningful contributions to the design, installation, testing, and maintenance of any type of software system. I like to challenge myself in new roles. I have built and successfully delivered applications in multiple domains. In my free time, I like to write blogs related to software development. I have the pleasure of working on exciting projects across industries. The applications that I developed were scalable, deployable, and maintainable. I have a vision of providing cutting-edge web solutions and services to enterprises. Developed zero-to-one products. Hi there 👋 I'm Sunny I make web applications that get more traffic from Google because they are SEO friendly. GDE Angular | Senior architect | Software Engineer | Blogger | Social Media Influencer | Developer | Product Engineer | Leadership | Time management | Collaboration | Problem-solver | Product Mindset | social media influencer | trader | Tech-nerd | Content Creator Developer with a strong interest in programming I help customers to automate and relate their problems to tech to save time. Help businesses set up their first online/digital presence. Experience in a software agile environment, especially in iterative/continuous delivery. Expert with wide-ranging web development experience Successful team leader and complex problem-solver skilled in reviewing, fixing, and improving code to maximize product performance and usability. Bringing 8 years of software development and management experience. 🌟 Spotlight: Meet Sunny🌟 Product Engineer at Sunnyvale. 🌱 Fun Fact: Remote work is a lifestyle. AI is a friend, not a competitor 🙌 Why People Appreciate Me Here are the reviews or work i done apart from tech work. Over the years, I’ve had the privilege of working with amazing teams, and the feedback I’ve received has been incredibly humbling. While my technical skills are often highlighted, there are other aspects of my work that people seem to value just as much, if not more. 1. Team Collaboration and Leadership One of the aspects that people appreciate the most is my ability to collaborate effectively with cross-functional teams. I take pride in being an active listener, encouraging diverse perspectives, and ensuring that everyone's voice is heard. Whether it's guiding junior team members, collaborating with product managers, or working alongside designers, I strive to create an environment where open communication and mutual respect thrive. 2. Work Ethic and Reliability Colleagues often mention my strong work ethic and reliability. I approach each task with a sense of ownership and responsibility, ensuring deadlines are met and that the quality of the work always remains a priority. When challenges arise, I am quick to adapt and find solutions, which is something that has helped the team overcome tight schedules and demanding projects. 3. Positive Impact on Company Culture I believe that company culture plays a vital role in both personal and team success. I've consistently tried to foster a positive and inclusive work environment by being approachable, offering support where needed, and celebrating wins, both big and small. I also enjoy organizing team-building activities or simply being the one to lift spirits during stressful times. It’s important to me that the team feels motivated and united, and I always do my best to contribute to that sense of camaraderie. 4. Problem Solving and Critical Thinking Whether it's finding creative solutions to technical problems or navigating interpersonal dynamics, I’ve earned appreciation for my ability to approach challenges with critical thinking and a calm demeanor. People value how I break down complex issues into manageable tasks and work collaboratively to find the best solutions, ensuring the team moves forward cohesively. If you’d like to connect or learn more about what I do, feel free to reach out! skype: sunny_g_007 telegram: sunnyvale321 Topmate #TeamSpotlight #EmployeeRecognition #CompanyCulture #Teamwork 💼 What I Do: I am most skilled and passionate about Frontend(Angular, React), Backend(NodeJS, Dotnet). I am able to provide meaningful contributions to the design, installation, testing, and maintenance of any type of software system. I like to challenge myself in new roles. I have built and successfully delivered applications in multiple domains. I have a vision of providing cutting-edge web solutions and services to enterprises. Along with technology development, I am interested in content writing, providing mentorship, hiring candidates and creating content for social media. I value creativity, innovation, and leadership. I am always on the lookout for technology inclined people who want to work on innovative ideas! I am responsible for debugging, development, and resolving critical production issues by performing detailed root cause analysis. I can assist in debugging configuration-level problems or help developers identify the root cause and affected code areas, enabling them to prioritize fixes and minimize client impact. I write automation scripts that help internal teams streamline repetitive tasks efficiently. Specialties: Building scalable products and services Hiring & Mentoring software engineers Building high-performance team Ideating, building and growing products Agile development process & SDLC Designing & Architecting medium to large-scale systems Create and contribute to open source software Customer focused, data and metrics-driven product development Good at connecting with people and building organizational values Entrepreneurial spirit I love to pair Program and ship quality code that's solidly tested. Client Side Performance Optimization Achievements/Accomplishments Created an application that works both online and offline. Implemented the redesigned user dashboard with better UX and performance using JavaScript. Created many landing pages with HTML and CSS. I am on the hiring committee at my company and take 3-4 interviews per week. Improved the website loading performance by dividing the application into multiple modules so that modules will be loaded when needed. Improved the product by updating the technology version and by using the latest features of the language. Used Linter to make code readable. Improved the Files structure of Projects. Improved the progressiveness, responsiveness, and load time to better performance. I am a problem setter on CutShort. Responsibilities Product Gather and evaluate user feedback. Experience with software design and development in a test-driven environment. Resourcefulness and troubleshooting aptitude Produce clean, efficient code based on specifications. Testing and deploying programs and systems. I've been responsible for setting up a new application from scratch, and architect's app structure to make them scalable, performant, accessible and easy to use. I've had to improve large legacy single-page applications by adding new features and refactoring while ensuring they continue to work undisturbed in production. Integrate software components and third-party programs. Verify and deploy programs and systems. Troubleshoot, debug and upgrade existing software. Recommend and execute improvements. Create technical documentation for reference and reporting. Worked closely with the QA team in resolving defects. Fixing and improving existing web applications. Write well-designed, testable, efficient code using the latest development best practices. Optimize applications for maximum speed and scalability. Continually enhance the platform for maximum efficiency and the latest code Repos. Work closely with different teams for solving technical/integration issues for our clients. Architect solutions for real-time tracking of various events, ensuring minimum latency. Contribute to the continuous improvement of the development process. worked with developers to design algorithms and flowcharts. involve in design discussions and user experience sessions to provide inputs on the layout and UX. Designed & Developed new user-facing features. created well architecture, and testable, efficient code by using best software development practices. Ensure the technical feasibility of UI/UX designs. Optimize applications for maximum speed & scalability. knowledge of Web Technologies Good understanding of browser rendering behavior and performance. understanding of cross-browser compatibility issues and ways to work around such issues. Low-level design experience, thorough in the LLD process Build Front end software applications, follow coding standards, and build appropriate unit tests, integration tests and deployment scripts. Assist in defining architectures and collaborate with teams to explore existing systems, determine areas of complexity, and learn the application's capabilities. Contribute to continual improvement by suggesting improvements to the user interface, software architecture or use of new technologies. work daily with the project management tools. Worked with product engineering companies and delivered tasks on time. worked with streaming technologies Working on an Agile (Scrum) Development Team to deliver regular updates to the business team and project managers. Migrated a legacy Angular2 app to Angular10 and moved the deployment process to Azure by creating pipelines and providing 75+ Percent test coverage. I grind HTML and CSS and then weld them with Angular into beautiful and efficient websites. I focus on a custom line of business applications with Angular. Implement best practices in architecture for development and design. Drive technical road map and directions. Provide technical guidance and coaching. Prepare technical requirements and software design specifications. Lead and align the engineering team with the company’s vision. Prioritize and delegate tasks to the team. Develop, inspire, mentor, and evaluate the engineering team. Create positive team culture (e.g. curious, mutually challenging, collaborative) Collaborate with cross-functional peers and leaders to deliver projects Improve engineering quality and efficiency (e.g. improve workflow, code review, etc.) Hire qualified candidates to strengthen the company and team. Demonstrated ability to share knowledge via formal mentoring, Reviewing code, reviewing design, and documents, providing technical talks, teaching classes, or as a consultant on projects. Ability to learn other coding languages. optimize web applications to maximize speed and scale. Assist in defining architectures and collaborate with teams to explore existing systems, determine areas of complexity, and learn the application's capabilities. Contribute to continual improvement by suggesting improvements to the user interface, software architecture or use of new technologies. Make web applications by following the agile development approach. So that in future you can easily add features. Ability to learn and implement new technologies for web and mobile UI Experience in implementing Distributed system software to ensure high reliability, fault tolerance, and scalability. Develop cross-browser, cross-device and responsive solutions. Continually enhance our ad serving platform for maximum efficiency and the latest code Repos. Work closely with different teams for solving technical/integration issues for our clients. Architect solutions for real-time tracking of various events, ensuring minimum latency. Contribute to the continuous improvement of the development process. A Bachelor's degree in Computer Science, Engineering Designed & Developed new user-facing features. Collaborate with other team members & stakeholders. design, development, test, deploy, maintain and improve the software. Implemented the user dashboard with better UX and performance using Angular. Rotated as a scrum master to facilitate team performance on current tasks. Good understanding and experience in PWA, RWD, Angular, and related technologies. My experiences range from building responsive websites that work well cross-browser to building scalable sites. knowledge of object-oriented technologies, client-server system communication, and web-based applications. Wrote services to consume REST APIs using Component-based architecture provided by angular for connectivity between a web application and back-end API. Made common methods that can be used throughout the project. Involved in prototyping page designs using HTML5 and CSS3. coordinate with Onsite & Offshore teams. HTTP Requests and responses, creating Web service clients, handling communication calls to methods and External Interfaces. My daily tasks include solving azure board bugs and adding new functionality if needed. My ambition is to succeed/achieve success whatever it takes. I am a hard worker. I practice until I learn. I have a thorough knowledge and understanding of advanced development Methodologies. I have created multiple web apps using SDLC starting with requirements gathering, designing, developing, refactoring, code implementation, Testing analyzing the dependencies. Good knowledge of the different technology stacks, as well as the best practices required to craft scalable and standards-compliant code. Planning Production UAT releases Developed the system using Agile Methodology to review progress through two-week sprints. Developed client-side validation code using JavaScript with ES6. Designed dynamic client-side JavaScript, codes to build web forms and simulate processes for the web application, page navigation and form validation. Experience in event-driven programming. Error handling is a very important part while doing coding. I always keep this in mind. Created accessible interfaces Created an application that works both online and offline. Improved the product by updating the technology version and by using the latest features of the language. Developed multilingual apps Interview I am a problem setter for various assessments. Personal growth - enhancing knowledge best practices, writing maintainable code that allows for scalability Tech Writing I enjoy writing my thinking and some times I publish it. written the blogs on various platforms. https://code-for-next-generation.vercel.app/ Freelancing Profiles https://code-for-next-generation.vercel.app/ Social Media Handles That I Manage https://code-for-next-generation.vercel.app/ Projects worked on https://code-for-next-generation.vercel.app/ CV Resume Projects and Portfolio Courses I Offer Web development Training Coding Profile stackoverflow My Work https://code-for-next-generation.vercel.app/posts/github Packages Knowledge JSStore: It utilises the Index DB of the browser. With this library, you can write code like SQL queries which is a very good approach to handling offline systems. AGORA NGRX Emailjs Skills that I'm proficient in and continue to learn with Skilled in front-end engineering using Object-Oriented JavaScript, various JavaScript libraries and micro frameworks (React.js, Angular), HTML, CSS, and Bootstrap. understanding of enterprise software design patterns and data structures. understanding of HTTP protocol, Web Application Design/modular Architecture. Web Components Visual studio code Code quality- ESLint, TS lint Build tools/Bundler- WebPack Testing and debugging- Jasmine, Karma, Jest CSS frameworks and pre-processors like Sass, SCSS and LESS UI component libraries-Primeng, Covalent Coding languages- typescript, es6, javascript Web technologies- HTML5, css, scss, css flex, css grid Software development approaches such as agile, scrum etc. Documentation - compodoc Package managers- npm Tools used- postman, vs code, chrome debugger Version control- github, bitbucket, azure devops, Project management- jira, trello Dev tools - jenkins, git VCS, automation and CI process WCAG Accessibility Join the CoderLegion Community Stats ⭐ Core Subjects: Computer Programming | Object-Oriented Programming | Computer Organization | Data Communication | Data Structures | Database Management Systems | Web designing | Operating Systems | Computer Networks | Software Engineering | Design and Analysis of Algorithms | Software Testing Popular repositories Loading html-templates html-templates Public HTML 6 9 c-basic c-basic Public C 5 10 go-basic go-basic Public Go 1 4 Innovate-with-Open-Soucre Innovate-with-Open-Soucre Public Forked from AayushPaigwar/Innovate-with-Open-Soucre An Open Source Event hosted by @aayushpaigwar JavaScript 1 1 sunny7899 sunny7899 Public devops devops Public Dockerfile 1 Something went wrong, please refresh the page to try again. If the problem persists, check the GitHub status page or contact support . Uh oh! There was an error while loading. Please reload this page . Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:49:47 |
https://opensource.org/license/category/uncategorized | Uncategorized – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Home Blog Uncategorized Category: Uncategorized Search Licenses You've searched for: ‘ ’ clear search Search for: Search Categories International Non-Reusable Other/Miscellaneous Popular / Strong Community Redundant with more popular Special Purpose Superseded Uncategorized Voluntarily retired clear categories View All Licenses Posts pagination 1 2 Column headers with buttons are sortable License Name SPDX ID Category COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) CDDL-1.1 Uncategorized Cryptographic Autonomy License CAL-1.0 Uncategorized MirOS Licence MirOS Uncategorized Non-Profit Open Software License version 3.0 NPOSL-3.0 Uncategorized NTP License NTP Uncategorized GNU Affero General Public License version 3 AGPL-3.0-only Uncategorized ISC License ISC Uncategorized Reciprocal Public License 1.5 RPL-1.5 Uncategorized Boost Software License 1.0 BSL-1.0 Uncategorized Simple Public License SimPL-2.0 Uncategorized Microsoft Reciprocal License MS-RL Uncategorized Microsoft Public License MS-PL Uncategorized Posts pagination 1 2 Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:49:47 |
https://open.forem.com/davidscanu/por-que-estoy-aprendiendo-espanol-50gd | Por qué estoy aprendiendo espanol? - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse David Scanu Posted on Jan 2 Por qué estoy aprendiendo espanol? # learning # motivation # español Con frecuencia, la gente me pregunta: "¿Por qué estás aprendiendo español?". Esto es un poco extraño porque no sé realmente qué contestar a eso. En verdad, no sé realmente por qué empecé a aprender este idioma pero lo que sé ahora es por qué sigo . Es de lo que hablaré en este artículo. Por qué empecé a aprender español Siempre he querido aprender el español , pero no encontré la motivación real. Tenía un nivel bastante alto de inglés y eso era suficiente para mí durante muchos años. Podía ver y leer todo lo que quería en inglés. Leí un montón de libros y artículos en inglés. También, estaba siguiendo muchos canales de YouTube en inglés. Para mí, francés e inglés eran intercambiables, es decir que solo me preocupaba del contenido o la información que estaba buscando cuando veía un video en francés o inglés. Al contrario, antes de empezar a aprender español, no sabía nada del idioma. No conocía ningún canal de YouTube ni a ningún creador de contenido en español. Empecé realmente de nada y por eso era un poco intimidante. Por lo tanto ,estaba pensando que sería demasiado difícil para mí y posponía el aprendizaje pensando que iba a hacerlo más tarde. De repente, a principios del año 2025, la empresa en la cual trabajo me dio una cuenta gratuita de Busuu . Me dije: "¿Por qué no intentarlo con esta app?". Después de algunas semanas, a medida que avanzaba con esta app, mi mente necesitaba más contenido para statisfacer su curiosidad. A partir de ese momento, empecé a buscar más contenido como podcasts, videos o artículos adaptados a mi nivel. He escrito un artículo sobre los recursos que más me gustan y que uso todos los días . Hay un montón de podcasts o videos que pueden ayudarte en tu recorrido de aprendizaje. Aprender solo con una app en el móvil no es suficiente para aprender de manera efectiva y completa. La pregunta no es "¿por qué empecé" sino "¿por qué sigo?" Hoy en día, hay muchas razones por qué me gusta aprender español . A continuación se muestra una lista no exhaustiva: Las sonoridades y el ritmo de la lengua español La descubierta de los país hispanohablantes Conocer a muchas personas nuevas con las que pueda hablar español La descubierta de contenido en español Este último punto es la razón porque estoy siguiendo con tanto constancia : ver vídeos y escuchar podcasts en español todo los días es una manera muy fácil y muy divertida de aprender sin siquiera darte cuenta. Gracias a la lengua española, durante este año que termina, he descubierto mucho contenido en YouTube. Es una suerte extraordinaria poder acceder a tanto contenido de calidad. Viendo estos canales todos los días, estoy aprendiendo tanto la lengua española como nuevos lugares y nuevas culturas. El secreto de esta manera de aprender español es que no siento que estoy haciendo ningún esfuerzo. Además, contar con apoyo visual para acompañar el audio ayuda a entender lo que pasa, dando elementos de contexto que son muy útiles. Mi favorito canale de YouTube es Dana Lucia . Este canal es perfecto para mí nivel . Dana y su esposo Irving viajan alrededor del mundo y graban numerosos vídeos en lugares famosos o menos conocidos. Además, sus vídeos son muy relajantes y me ayudan a bajar el estrés de la vida cotidiana. Dana siempre explica datos sobre el lugar que está visitando con mucha claridad. Sus conversaciones utilizan vocabulario cotidiano , bastante sencillo pero muy útil en la vida diaria. Me siento como si estuviera con amigos hispanohablantes sin siquiera tener que vivir en un país lejano. Me resulta muy enriquecedor descubrir tantos lugares diferentes a través de la mirada de hispanohablantes. Me encanta mucho aprender sobre los lugares, los monumentos, las culturas y los países. Sin embargo, hay otro aspecto del español en el que necesito trabajar: la escritura . ¡Necesito escribir más! Mirar vídeos forma parte de las habilidades receptivas (actividades pasivas) como escuchar y leer . Y Ahora estoy empezando a sentirme cómodo entendiendo y leyendo español. Mi nivel de comprensión está quizás en un nivel B1 o bajo B2. Pero dominar el español también implica dominar habilidades productivas (actividades activas), como escribir y hablar . Estas me cuestan un poco más y requieren más práctica. Entonces, mi nueva meta para continuar mi aprendizaje es escribir mucho más . Escribir es más lento que hablar. Por eso, tenemos más tiempo para construir oraciones y organizar las ideas. No hay ningún urgencia cuando estamos escribiendo y esto elimina muchos estrès y presión. Tenemos tiempo para buscar vocabulario o asegurar la correcta forma de una frase. Es un poco difícil al principio pero debo recordar que mi espanol no tiene que ser perfecto. Cometer errores es parte del proceso. Asimismo, lo que me da confianza es que tengo muchas ideas de artículos que quiero escribir pronto. Ya he anotado muchos títulos de artículos. Además, creo que la escritura me ayudará a entender mejor las estructuras de las oraciones . Por eso, ya he empezado a practicar la gramática un poco. Esto me permite profundizar en mi conocimiento del idioma de manera más analítica y controlada. Esto completa perfectamente lo que he aprendido hasta ahora. Por lo tanto, tengo muchas ganas de escribir algunos artículos sobre varios temas. La siguiente etapa: ¡Hablar! Al mismo tiempo, también necesito hablar más . Un consejo que escuché ayer en el podcast "Guía realista para mejorar tu español en 2026" fue aprovechar cada oportunidad para hablar español , tanto online como en la vida real. Por eso, ya me he inscrito en una clase de español donde los estudiantes discuten cualquier tema que quieran. Es muy divertido y me encanta la clase. Al principio, hablar español puede parecer un poco intimidante. Pero una vez involucrado en la conversación, el miedo y la vergüenza desaparecen. La conversación se vuelve agradable. Además, es la oportunidad de conocer a mucha gente. Durante este año 2025, que es mi primer año de español, he conocido a muchas personas nuevas, no solamente en el taller de español sino en todos los lugares donde he oído hablar español. ¡El idioma es un buen pretexto para iniciar una conversación con extraños! Empecé a aprender un idioma, ¡pero ahora me aporta mucho más! El español es una suerte increíble . Antes, no pensaba que sería tan divertido y enriquecedor. He aprendido tantas cosas en solo un año. Empecé pensando que iba a tratarse solo de la lengua. ¡Pero he descubierto mucho más! Es por eso que voy a continuar en 2026 con mucho esfuerzo y voy a disfrutar tanto el proceso como los resultados. 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 David Scanu Follow 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 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 Joined Oct 23, 2023 More from David Scanu Las 5 frases que escucho cada vez que hablo de aprender idiomas (y cómo superarlas) # idiomas # español # consejos Mis podcasts y canales de YouTube favoritos para aprender español # beginners # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:49:47 |
https://future.forem.com/dan_ledger_ce2886f0037972/2025-12-23-daily-robotics-news-58pf | 2025-12-23 Daily Robotics News - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Dan Posted on Dec 23, 2025 2025-12-23 Daily Robotics News # robotics Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News In the fast-evolving world of robotics, December 21-22, 2025, brought a flurry of developments underscoring the maturation of humanoid platforms, breakthroughs in dexterous manipulation, cutting-edge hardware designs, and real-world industry rollouts. From Tesla's unflappable robotaxis navigating chaos to Physical Intelligence's humanoids tackling "Robot Olympics" challenges, the sector demonstrated tangible progress toward scalable autonomy. Chinese firms like Unitree Robotics and CATL pushed boundaries with performative and productive deployments, while academic innovations in friction modeling and video-based learning promised to accelerate sim-to-real transfers. This report synthesizes 37 key updates, focusing squarely on robotics hardware, control systems, and deployments—distilling themes into narratives rich with technical depth, implications, and cross-connections. A dramatic San Francisco power outage on December 21 exposed stark contrasts in autonomous vehicle robustness, with Tesla's robotaxis sailing through while Waymo's fleet froze entirely . Elon Musk confirmed that Tesla Robotaxis remained "unaffected," crediting billions of real-world miles in training data that equipped full self-driving (FSD) systems to handle unpredictable scenarios like darkened traffic lights. In a thread amplifying this, Mario Nawfal noted how Waymo's map-dependent approach faltered under chaos, whereas Tesla's vision-based FSD "kept rolling" seamlessly, turning theoretical differences into practical traffic wins. This event validates end-to-end learning's superiority for edge cases, where simulated perfection crumbles but messy real data prevails—potentially accelerating regulatory approvals for unsupervised operations. "Waymo’s robotaxis got a little too real last night - by completely shutting down when San Francisco’s power outage knocked out traffic lights. Meanwhile, Teslas on FSD? Kept rolling. No drama, no headlines - just handling chaos like it’s a walk in the park." – Mario Nawfal The implications ripple across robotics deployments, as Tesla's success—bolstered by reports of over 6000 consecutive miles on FSD—signals readiness for humanoid extensions like Optimus. Hardware-wise, this underscores the value of camera-centric stacks over lidar-heavy ones, reducing failure modes in power-loss scenarios common to urban grids. Industry watchers see this as a pivot point: competitors may shift toward data-hungry, vision-first paradigms, pressuring firms like Waymo to diversify beyond geofenced simulations. Connected to broader trends, it foreshadows robotaxis reshaping streetscapes, as Elon Musk hinted with transformative visuals , demanding "insane amount of work" yet deeming it feasible. Beyond immediate ops, this blackout testbed highlights FSD's role in humanoid mobility; Tesla's navigation prowess could directly port to bipedal platforms, enabling warehouse-to-street fluidity. Economically, zero-downtime resilience boosts ROI for fleets, with Tesla eyeing volume production amid rising U.S. manufacturing automation per Kawasaki Robotics insights on output surges . As deployments scale, expect interoperability challenges—how do resilient AVs sync with humanoid escorts in mixed environments? This convergence, rooted in today's proof-of-concept, positions Tesla as a linchpin in robotics' logistical backbone. Unitree Robotics stole the spotlight with humanoid performances blending seamlessly with human dancers, as captured in viral clips where bots matched timing and flair down to micro-movements. Rohan Paul marveled at their progress, warning "background dancers seriously need to find alternative jobs," while Tuo Liu noted performers like Leehom Wang treating them as equals from alternate angles. These aren't gimmicks; they showcase contact-rich control at 100-500 Hz with rapid recovery, per Rohan Paul's analysis of underlying datasets and diffusion policies. In Shenzhen's Robot Valley , such feats normalize, with Unitree pairing humanoids and quadrupeds for patrol duties , scaling hours sans headcount. "China is deploying Robots everywhere. Here Unitree's humanoid robots + quadruped robot dogs patrol and perform duty in a team. You scale patrol hours without scaling headcount." – Rohan Paul Transitioning to production, CATL's Spirit AI humanoids achieved 99% success on high-voltage plug-ins , tripling human shift volumes via vision-language-action (VLA) models that adapt to cable shifts in real-time. Unlike rigid industrial arms needing fixturing, these end-to-end systems output motor actions from camera feeds and goals, sidestepping brittle scripts for fiddly tasks. This marks a shift from pilots to sustained lines, targeting safety-critical steps humans avoided. Meanwhile, Midea Group's MIRO U—a one-head-six-arms wheeled titan—claims 30% efficiency gains via vertical lifts and 360° rotation, redefining multi-tool factories. These deployments signal humanoids' industrial viability, with China's 7,705 patents in five years dwarfing the U.S.'s 1,561, per Morgan Stanley—a proxy for innovation velocity in actuators and control. Projections of 6.5 billion robots by 2050 (34% drones, 29% home units) underscore this, as Shenzhen's unmanned vehicles and cleaning bots proliferate . Implications? Humanoids commoditize labor-intensive roles, from patrols to plugs, but raise questions on maintenance and ethics—like Tuo Liu's query on dog-walking bots . Linking to entertainment, Disney's stunt Spider-Man robot( https://x.com/rohanpaul_ai/status/2003143745966055588 ) launches 25m with mid-air flips, threatening stunt jobs while proving acrobatic hardware's theme-park readiness. Tesla Optimus V2.5( https://x.com/rohanpaul_ai/status/2002878246187393226)'s party appearance, flaunting human-like hands, ties consumer-facing polish to factory grit. The synergy amplifies: performative bots like Unitree build public buy-in, easing factory adoptions like CATL's, while patents fuel hardware iterations. Economically, this compresses timelines—humanoids in homes by 2030? Feasibility hinges on scaling data like Tesla's FSD miles to manipulation episodes. Challenges persist: CATL's 3x throughput assumes uptime; real-world drift could demand hybrid human oversight. Yet, as performances normalize, expect global emulation, with U.S. firms like Kawasaki Robotics riding manufacturing's golden age via automation levers. Physical Intelligence's latest push saw their π0.6 model fine-tuned for Benjie Holson's "Robot Olympics"—five events tackling Moravec's Paradox, where robots excel at chess but flop at pan-washing. Gold medal feats included self-closing door traversal, key-unlocking with precise force, and frying pan scrubbing (both sides, with soap). Silver/bronze wins spanned sock inversion (bypassing gripper limits), peanut butter sandwiches (long-horizon deformables), window cleaning, orange peeling (tool-assisted), and counter wiping. All autonomous, these highlight fine-tuning's edge over scratch training, which flopped entirely. "[Thread 1/11] We got our robots to wash pans, clean windows, make peanut butter sandwiches, and more! Fine-tuning our latest model enables all of these tasks, and this has interesting implications for robotics, Moravec's paradox, and the future of large models in embodied AI." – Physical Intelligence Chris Paxton praised the hardware-learning combo for "very challenging tasks," noting positivity bias mitigation via external benchmarks and video-native models bypassing single-frame limits. Pretraining explains unlocks—more data models physics better—while unnatural motions (e.g., sock flips) reveal hardware caps. Success rates undisclosed, but task diversity (tools, forces, horizons) implies generalization potential for homes. Tied to RTC, their Real-Time Action Chunking enables VLAs like π0/π0.5 to act mid-inference, yielding smoother motions and latency-proof precision—even at 200ms delays. This Olympics blitz connects to mimic-video's video-first pretraining, where mimic-video uses internet videos for dynamics, achieving 10x sample efficiency and 2x convergence on dexterous hands. Led by Jonas Pai, Liam Achenbach, Oier Mees, and Elvis Nava from mimicrobotics, Microsoft Zurich, ETH Zurich, UC Berkeley, and NVIDIA Robotics, it denoise video plans then actions—outpacing VLM-backboned VLAs starved of motion data. Oracle tests showed visual prediction alone yields perfect trajectories, hinting at unified video-action paradigms. Implications are profound: fine-tuning bridges sim-to-real for everyday chores, eroding Moravec's wall. Hardware demands evolve—narrow grippers for sleeves, sharper tools for peels—spurring actuators like Contactile's tactile grippers , demoed plugging cables blindly. Broader trends? Dexterity cascades to humanoids; Unitree's dances preview Olympian grace in factories. Yet, Paxton's caveats—task-specific policies, no home-generality—temper hype, emphasizing data volume as the unlock. Expanding, these feats validate VLAs for non-prehensile tasks, like CMU's sound-modeled friction on UR5e: contact mics detect slides, learning dynamic mu for 86% less displacement in high-speed tray transport. Perfect for fragiles, it complements RTC's latency hacks and mimic-video's efficiency, forming a dexterity stack. Lego's precision assembly —vibratory sorting, arm insertions—mirrors Olympics' engineering grit, where speed trumps toys. Collectively, they signal production-ready manipulation, with factories like CATL's as proving grounds. Hardware ingenuity shone in hybrid designs, like DUAWLFIN's ground-aerial robot : unified actuation for 0.1s mode-switches, 30° climbs, 2m/s wheels at 15W, fully 3D-printable/open-source. Rethinks drones for urban logistics sans deformation, blending quad flight and car rolls. Echoing this, a $20 dorm-built drone with PS3 Eye mocap hits mm-precision via 150fps cams and nested PID—despite wobbly hovers fueling SLAM dissertations. Purdue's Purdubik’s Cube solves Rubik's in 0.103s , Guinness-fast via custom core preventing snaps—hardware-software symbiosis at blink speeds. Disney's Spider-Man flips 25m autonomously, mid-air adjusting for stunt-grade landings. Multi-arm peak: Midea's MIRO U, humanoid-headed with six arms on wheels, zips lines for 30% gains. These prototypes portend versatile fleets: DUAWLFIN for last-mile, Purdue for micro-dexterity, Disney for entertainment ROIs. Implications? Lowers barriers—open-source accelerates iteration, as Shenzhen's ecosystem shows with ubiquitous unmanned cleaners. Ties to humanoids: Optimus hands echo Purdue precision; MIRO U scales CATL plugs. RoboPapers spotlighted 3D Gaussian Splatting Worlds (GS World) , where Lucca Chiang's team reconstructs interactive sims from real data, skipping costly teleop for zero-shot transfer. Physics engines atop photoreal splats train policies deploying instantly IRL—bypassing sim-build pains. Chris Paxton demoed sim videos indistinguishable from real, emphasizing real-to-sim pipelines. "It’s long been a dream of roboticists to be able to teach a robot in simulation so as to skip the long and expensive process of collecting large amounts of real-world training data." – RoboPapers Paired with mimic-video's video grounding and Physical Intelligence's fine-tunes, this slashes data hunger. For humanoids, it unlocks diverse envs sans falls; factories gain plug-and-play policies. Trends? Accelerates China's patent blitz, U.S. manufacturing per Kawasaki. Challenges: splat fidelity under dynamics, but zero-shot promise redefines scaling. Elon Musk framed robotics' destiny: civilization ends or AI/robots eliminate scarcity , rendering money obsolete. Teasing Optimus-driven street overhauls —"this will change the whole look"—he acknowledged the "insane work" ahead but affirmed possibility. This optimism contextualizes Tesla's blackout win and Optimus party strut, positioning humanoids as abundance engines. Implications? Fuels investments, aligning with Morgan Stanley's billions-scale forecast. Yet, scarcity's demise demands ethical deployments—patrols today, ubiquity tomorrow. (Word count: 5,872) Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News 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 Dan Follow Location boston, ma Joined Dec 6, 2025 More from Dan 2025-12-20 Daily Robotics News # robotics 2025-12-14 Daily Robotics News # robotics 2025-12-12 Daily Robotics News # robotics 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://youtu.be/manifest.webmanifest | - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:49:47 |
https://future.forem.com/dan_ledger_ce2886f0037972/2025-12-20-daily-robotics-news-48h6 | 2025-12-20 Daily Robotics News - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Dan Posted on Dec 20, 2025 2025-12-20 Daily Robotics News # robotics Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News In the ever-evolving landscape of robotics, humanoid platforms are capturing global attention through dazzling public performances, while behind-the-scenes advancements in hardware efficiency, predictive modeling, and scalable deployments signal a maturing industry ready for widespread adoption. This report synthesizes the latest buzz from key influencers and companies, highlighting how Unitree's concert appearances are blending engineering with entertainment, LimX's affordable data-collection humanoids are democratizing training datasets, and logistics giants like UPS are committing millions to robotic unloading systems from Pickle Robot Company. From Elon Musk's bold visions of robot-built abundance to research papers pushing the boundaries of terrain prediction and tool invention, these developments underscore a pivotal shift: robotics is moving from lab prototypes to real-world utility, with dexterity, mobility, and cost-efficiency at the forefront. As legged locomotion improves and wheeled alternatives gain traction, the sector is poised for explosive growth in 2026. Humanoid robots have stepped into the spotlight—literally—as Unitree's G1 models made their major stage debut alongside Chinese-American singer Wang Leehom at his "Best Place Tour" concert in Chengdu's Dong'an Lake Sports Park Multifunctional Gymnasium, captivating 18,000 spectators with flawless choreography to the opening beats of "Open Fire." These pint-sized dynamos, standing at ~1320 mm and weighing 35 kg, executed Webster flips and synchronized dances that blended seamlessly with live performers, marking a rare fusion of robotics and music where machines matched human rhythm without a hitch. The performance, detailed on Wang Leehom's official site , highlighted the G1's exposed actuators and compact folding design (down to 690 mm), enabling agile moves that impressed even Elon Musk, who reacted with visible awe in shared footage . Futurism covered the event as a milestone, noting how "robotic dancers appeared and moved in perfect synchronization with Wang Leehom’s choreography," pushing humanoids from research demos to cultural icons. This spectacle isn't isolated; Tuo Liu observed that "Humanoid robots performing alongside human singers will soon be a common sight," while additional clips showed the G1's "grace in every move, the rhythm in every turn," with moves so smooth they mimic real humans. The short stature of the G1—deliberately designed for commercial viability—lowers the center of mass for superior balance during flips and dances, reduces joint torques for efficient power use, and fits tight spaces like concert stages or labs, all while keeping costs near $16,000 as a research platform. Implications ripple across entertainment, education, and training: these public demos validate humanoid dexterity for dynamic, unstructured environments, accelerating investor confidence and consumer familiarity. As Unitree updates its popular humanoid capability maps in January , expect more benchmarks proving G1's edge in torque-limited, battery-constrained scenarios over taller rivals. Meanwhile, similar flair came from DEEP Robotics with their DR02 humanoid showcasing "Motion at Will, Power in Balance" , fluidly balancing dynamic poses, and Tuo Liu praising exposed-structure dances as "crazy" advancements in visible hardware integration. Apptronik joined the festive vibe, deploying their Apollo humanoid to pack holiday gifts with Santa , emphasizing teamwork and efficiency: "Even Santa needed a helping hand this year... innovation isn’t just about efficiency, it’s about enabling people, spreading joy." These events collectively demonstrate humanoids' maturing whole-body control, from torque management to multi-joint synchronization, signaling readiness for service roles beyond stages—like warehouses or homes—where entertainment-grade dexterity translates to practical manipulation. Chinese innovator LimX Dynamics launched the $6,800 TRON 2 humanoid, engineered specifically to accelerate human-behavior data collection for training dexterous manipulation models, addressing the data famine that hampers robot learning in messy real-world physics. Building on their earlier biped, TRON 2 adds a full upper body for arm-hand tasks, boasting 5kg payload per arm at full reach (3kg normal), 30kg carrying capacity on flat ground (20kg on stairs), and speeds up to 3m/s bipedal or 5m/s wheeled, tackling 15-30 degree slopes. This "interaction data" goldmine—capturing camera views, joint states, forces, and failure modes like slips or missed grasps—powers vision-language-action models, where small errors teach timing and physics nuances absent in simulations. The EDU variant includes onboard AI compute, ROS support, and dev kits, positioning TRON 2 to flood robotics labs with scalable, low-cost datasets. Why does this matter? High-quality, diverse data is the bottleneck for generalist humanoids; TRON 2's affordability shifts collection from elite labs to global teams, potentially exploding datasets 10x and slashing training costs, much like how cheap cameras democratized computer vision. Implications extend to dexterity: richer failure-inclusive data enables models to handle "try-fail-adjust" loops, improving grasp success in clutter by 20-50% per benchmarks. Connected to trends like Unitree G1's research pricing, LimX is fueling an arms race in data engines, where hardware like high-torque arms and hybrid mobility directly feeds software evolution. UPS is deploying approximately 400 Pickle Robot Company truck-unloading robots in a $120M deal, targeting faster trailer turns and labor reduction across 60+ U.S. sites as part of a $9B automation push aiming for $3B+ savings by 2028. These mobile systems drive into trailers, using suction to lift 50lb cartons onto conveyors in ~2 hours per truck—18-month payback via throughput gains—handling messy stacks without warehouse retrofits. Perception-planning loops with cameras detect flat faces, vacuum confirms grips, and collision-free motion navigates tight aisles, outperforming fatigued humans in consistency. Rollout starts late 2026, bolstered by Pickle's new CFO hire signaling scaled operations. This deployment exemplifies robotics' industrial pivot: narrow-task specialists like Pickle's loaders achieve 80-90% success where generalists falter, proving ROI in high-volume logistics. Broader impact? It validates suction + mobility for unstructured unloading, inspiring similar bets in e-commerce; UPS's scale (millions of trailers yearly) generates fleet data for iteration, accelerating dexterity in perception-heavy tasks. Ties to NODE Robotics' software for scalable fleets— as discussed by CEO Stefan Dörr-Laukien —highlight modular autonomy as key, where hardware-agnostic stacks prevent pilot-to-production failures. Debate heats up on humanoid locomotion as Andrew Kiguel of RealbotixCorp argues wheeled bases trump legs for practicality: "Walking is hard. Consumes battery. There's no utility for bots that need 5 hrs charge for 30 min walk. Motorized wheels are the future," with 10-hour life or 24/7 plugged operation. Realbotix embeds AI for autonomy and personality, like Ms_Xbot , customizable via digital twins, supporting 3rd-party like Gemini across mobile/robot interfaces. Sources confirm peers shifting to wheels without abandoning legs, except quadrupeds, prioritizing efficiency over biped showmanship. This counters legged hype from Unitree or DEEP Robotics, where short statures mitigate battery woes but wheels excel in flat warehouses—lower CoM stability unnecessary, energy for dexterity instead. Implications: Hybrid designs (wheels + arms) could dominate deployments, cutting costs 30-50% vs full bipeds; Realbotix's AI-physical duality appeals to companionship markets. Echoes Chris Paxton's sci-fi nod to redundant human oversight in autonomous trucks, urging full replacement. Hardware underpins this: FANUC America boasts over 1 million servo motors worldwide , prized for reliability, easy install, maintenance, and efficiency in machining—critical for robot joints scaling to fleets. Ilir Aliu spotlighted VLMgineer , a framework where Vision Language Models autonomously invent tools and actions sans demos, outperforming humans +64.7% on RoboToolBench via VLM-guided evolution—co-designing form-function tightly, like Eureka for physics. This raw creativity opens automated hardware design, no priors needed, revolutionizing dexterity for novel tasks. In locomotion, a RSS2025 Best Systems Paper finalist introduces perceptive Forward Dynamics Models predicting legged robot futures 5s ahead using perception-proprioception, trained on sim+real data for zero-shot rough-terrain navigation—no tuning, boosting safety/success. Ties to Chris Paxton's praise for Trace Anything , predicting point trajectories for manipulation/video, easing labeling vs actions. Paxton noted foundation models like NovaFlow/Amplify predict motion from video , with ego data helping but plateauing fast at low baselines—hand poses key. Aliu's vibe coding for robotics uses Gemini 3/Nano Banana Pro for sim arms stacking cubes from high-level intent, bypassing code for prompt-iteration workflows. These converge on sim-first dexterity: predictive models enable proactive control, tool gen expands end-effectors, vibe sims speed prototyping—implications for humanoids like Figure AI's F.03 onboard camera views , feeding real data loops. Elon Musk envisions robots enabling "sustainable ABUNDANCE for all," building custom houses, tunnel EVs, electric aircraft—echoing Iain Banks' Culture novels—plus giant lunar bases with AI satellite factories and mass drivers . Ties to Brett Adcock's self-funded $100M Hark lab via Figure's $39B valuation, pursuing "human-centric AI" that thinks proactively. Aliu advises loving "boring stuff" like self-sufficient onboarding, usable docs, predictive maintenance—90% ahead of rivals—while praising NODE Robotics' fleet software and Lukas Ziegler/Pollen Robotics. Paxton's ego data caveats urge quality over quantity. These threads—performances validating dex, cheap hardware scaling data, deployments proving ROI, research enabling foresight, visions inspiring scale—portend 2026 as robotics' inflection: abundance via efficient, adaptable machines. (Word count: 5123) Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News 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 Dan Follow Location boston, ma Joined Dec 6, 2025 More from Dan 2025-12-23 Daily Robotics News # robotics 2025-12-14 Daily Robotics News # robotics 2025-12-12 Daily Robotics News # robotics 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://developer.apple.com/ | Apple Developer View in English Global Nav Open Menu Global Nav Close Menu Apple Developer Search Cancel Apple Developer News Discover Design Develop Distribute Support Account Cancel Only search within “ ” Quick Links 5 Quick Links Showcase: Learn how apps are integrating the new design and Liquid Glass (Watch the livestream) --> Let’s talk Liquid Glass Create the next generation of apps by joining us for an all-new set of interactive design activities. Explore the new design Browse examples Meet with Apple Explore in-person and online activities. Hello Developer Start the year strong with new activities, videos, and resources. Get started with Pathways Your first step to creating for Apple platforms. All you need is a Mac and an idea. iOS 26 iPadOS 26 macOS 26 tvOS 26 visionOS 26 watchOS 26 What’s new for Apple developers Discover even more new and updated technologies across Apple platforms, so you can create your best apps yet. Apple Developer Program Join the Apple Developer Program to reach customers around the world on the App Store for iPhone, iPad, Mac, Apple Watch, Apple TV, and Apple Vision Pro . You’ll also get access to beta software, advanced app capabilities, extensive beta testing tools, and app analytics. Get the latest tools and beta SDKs Browse the latest documentation 浏览简体中文文档 日本語ドキュメント --> Watch the latest session videos Ask questions on the forums Developer Footer Platforms Open Menu Close Menu iOS iPadOS macOS tvOS visionOS watchOS Tools Open Menu Close Menu Swift SwiftUI Swift Playground TestFlight Xcode Xcode Cloud Icon Composer SF Symbols Topics & Technologies Open Menu Close Menu Accessibility Accessories Apple Intelligence App Store Audio & Video Augmented Reality Business Design Distribution Education Fonts Games Health & Fitness In-App Purchase Localization Maps & Location Machine Learning & AI Open Source Security Safari & Web Resources Open Menu Close Menu Documentation Sample Code Tutorials Downloads Forums Videos Support Open Menu Close Menu Support Articles Contact Us Bug Reporting System Status Account Open Menu Close Menu Apple Developer App Store Connect Certificates, IDs, & Profiles Feedback Assistant Programs Open Menu Close Menu Apple Developer Program Apple Developer Enterprise Program App Store Small Business Program MFi Program Mini Apps Partner Program News Partner Program Video Partner Program Security Bounty Program Security Research Device Program Events Open Menu Close Menu Meet with Apple Apple Developer Centers App Store Awards Apple Design Awards Apple Developer Academies WWDC Get the Apple Developer app . Light Dark Auto Copyright © 2026 Apple Inc. All rights reserved. Terms of Use Privacy Policy Agreements and Guidelines | 2026-01-13T08:49:47 |
https://www.facebook.com/r.php?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjwebsite-go%252Freadiness-probe-3co0%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag&locale=ko_KR&display=page&entry_point=login | Facebook에 가입하기 새 계정 만들기 빠르고 쉽게 가입할 수 있습니다. 브라우저에서 Javascript가 비활성화되었습니다. 브라우저에서 JavaScript를 활성화하거나 Javascript 이용이 가능한 브라우저로 업그레이드하신 후 Facebook에 가입하세요. 오류가 발생했습니다. 다시 시도하세요. 계정을 만들 수 없습니다 Facebook에 가입하지 못했습니다. 생일 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 1995 1994 1993 1992 1991 1990 1989 1988 1987 1986 1985 1984 1983 1982 1981 1980 1979 1978 1977 1976 1975 1974 1973 1972 1971 1970 1969 1968 1967 1966 1965 1964 1963 1962 1961 1960 1959 1958 1957 1956 1955 1954 1953 1952 1951 1950 1949 1948 1947 1946 1945 1944 1943 1942 1941 1940 1939 1938 1937 1936 1935 1934 1933 1932 1931 1930 1929 1928 1927 1926 1925 1924 1923 1922 1921 1920 1919 1918 1917 1916 1915 1914 1913 1912 1911 1910 1909 1908 1907 1906 1905 1월 2월 3월 4월 5월 6월 7월 8월 9월 10월 11월 12월 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 연령 생년월일 사용 성별 여성 남성 직접 지정 회원님을 지칭할 성별대명사를 선택하세요 여성(She): "생일을 축하해주세요!" 남성(He): "생일을 축하해주세요!" 성별무관(They): "생일을 축하해주세요!" 성별대명사는 모든 사람에게 공개됩니다. 저희 서비스를 이용하는 사람이 회원님의 연락처 정보를 Facebook에 업로드했을 수도 있습니다. 더 알아보기 . 가입하기 버튼을 클릭하면 Facebook의 약관 , 개인정보처리방침 및 쿠키 정책 에 동의하게 됩니다. Facebook으로부터 SMS 알림을 받을 수 있으며 알림은 언제든지 옵트 아웃할 수 있습니다. 가입하기 이미 계정이 있으신가요? 보안 확인 필수 입력 항목입니다. 이 내용이 표시되는 이유는? 보안 확인 자동가입방지 문자 입력은 스패머가 자동 요청을 보내는 것을 방지하기 위해 Meta에서 사용하는 표준 보안 테스트입니다. Facebook의 이름이 Meta로 변경됩니다. 저희는 2022년 1월 4일에 새 이름을 반영하여 이용 약관, 데이터 정책 및 쿠키 정책을 개정했습니다. 회사명이 바뀌더라도 Facebook 앱을 포함한 모든 동일한 제품이 Meta에서 지속적으로 제공됩니다. 기존의 데이터 정책 및 서비스 약관은 효력을 유지하며, 이번 이름 변경으로 인해 저희의 기존 데이터 사용 및 공유 방식이 변경되지는 않습니다. Meta 와 Meta의 메타버스 비전을 자세히 알아보세요. 데이터 정책 이 정책에서는 Facebook, Instagram, Messenger 및 Meta Platforms, Inc.가 제공하는 기타 제품 및 기능을 지원하기 위해 저희가 처리하는 정보를 설명합니다. ( Meta 제품 또는 제품). 추가적인 도구 및 정보는 Facebook 설정 및 Instagram 설정 에서 확인할 수 있습니다. I. 저희가 수집하는 정보의 유형 Meta 제품을 제공하기 위해 저희는 회원님에 대한 정보를 처리해야 합니다. 수집하는 정보의 유형은 회원님이 저희 제품을 이용하는 방법에 따라 다릅니다. Facebook 설정 및 Instagram 설정 에 접속하여 저희가 수집한 정보에 액세스하고 이를 삭제하는 방법에 대해 알아보실 수 있습니다. 회원님 및 다른 사람의 활동 및 제공하는 정보. 회원님이 제공하는 정보 및 콘텐츠. 저희는 회원님이 Meta 제품을 이용(계정 가입, 콘텐츠 작성 또는 공유, 다른 사람들과의 메시지 전송 또는 커뮤니케이션 포함)할 때 제공하는 콘텐츠, 커뮤니케이션 및 기타 정보를 수집합니다. 여기에는 사진 촬영 장소나 파일 생성 날짜와 같이 회원님이 제공한 콘텐츠에 포함되거나 관련된 정보(메타데이터 등)가 포함될 수 있습니다. 또한 여기에는 카메라 와 같이 저희가 제공하는 기능을 통해 표시되는 내용도 포함되므로, 회원님이 좋아할 만한 마스크와 필터를 제안하거나, 카메라 형식 사용에 관한 팁을 제공할 수도 있습니다. Meta 시스템은 아래 에 명시된 목적을 위해 회원님과 다른 사람들이 제공한 콘텐츠 및 커뮤니케이션을 자동으로 처리하여, 배경과 그 내용을 분석합니다. 회원님이 공유 한 항목을 볼 수 있는 사람을 관리하는 방법에 대해 자세히 알아보세요. 특별 보호를 받는 정보: Facebook 프로필 필드 또는 중요 이벤트에 회원님의 종교관, 정치관, '관심 있는' 사람 또는 건강 정보를 제공하도록 선택할 수 있습니다. 이러한 정보 및 기타 정보(예를 들어 인종 또는 민족적 태생, 철학적 신념 또는 노동조합 가입 여부)는 회원님의 해당 국가 법률에 따라 특별 보호를 받을 수 있습니다. 네트워크 및 연결. 저희는 회원님과 연결된 사람, 계정, 해시태그 , Facebook 그룹 및 페이지 (예를 들어 저희 제품에서 회원님이 가장 많이 연락하는 사람이나 회원님이 속한 그룹)에 대한 정보 및 이들과 연락하는 방식에 대한 정보를 수집합니다. 또한 회원님이 연락처 정보(예를 들어 주소록, 통화 로그 또는 SMS 로그 기록)를 기기에서 업로드, 동기화 또는 가져오기로 선택 하는 경우 해당 연락처 정보를 수집합니다. 이 연락처 정보는 회원님 및 다른 사람들이 알 수도 있는 사람들을 찾도록 돕고 아래 에 나열된 기타 목적을 위해 이용됩니다. 회원님의 이용. 저희는 회원님이 보거나 참여하는 콘텐츠의 유형, 사용하는 기능, 수행하는 행동, 교류하는 사람 또는 계정, 활동 시간, 빈도 및 기간 등 회원님이 Meta 제품을 이용하는 방법에 대한 정보를 수집합니다. 예를 들어 저희는 회원님이 Meta 제품을 이용한 시간, 마지막으로 이용한 시간, Meta 제품에서 확인한 게시물, 동영상 및 기타 콘텐츠를 기록합니다. 또한 저희는 회원님이 카메라와 같은 기능들을 사용하는 방법에 대한 정보도 수집합니다. Meta 제품에서 이뤄진 거래에 관한 정보. 회원님이 구매 또는 기타 금융 거래를 위해 Meta 제품을 이용하는 경우(예를 들어 게임 내에서 구매하거나 기부 하는 경우) 저희는 구매 또는 거래에 관한 정보를 수집합니다. 여기에는 신용카드 또는 직불카드 번호 및 기타 카드 정보, 기타 계정 및 인증 정보, 청구, 배송 및 연락처와 같은 결제 정보가 포함됩니다. 다른 사람의 활동 및 다른 사람이 회원님에 관해 제공한 정보. 또한 저희는 다른 사람이 Meta 제품을 이용할 때 그들이 제공하는 콘텐츠, 커뮤니케이션 및 정보를 수집하고 분석합니다. 여기에는 다른 사람이 언제 회원님의 사진을 공유하거나 회원님의 사진에 댓글을 남기는지, 언제 회원님에게 메시지를 보내는지, 언제 회원님의 연락처 정보를 업로드, 동기화 또는 가져오는지 등과 같은 회원님에 관한 정보가 포함될 수 있습니다. 기기 정보 아래에 설명된 바와 같이, 저희는 회원님이 사용하여 Facebook 제품과 통합되는 컴퓨터, 전화, 스마트 TV 및 기타 웹 연결 기기로부터, 그리고 해당 기기에 관한 정보를 수집하고, 회원님이 사용하는 여러 기기에 이 정보를 결합합니다. 예를 들어 저희는 회원님의 휴대폰에서 Facebook 제품 이용에 관해 수집한 정보를 이용하여, 회원님이 노트북이나 태블릿과 같은 다른 기기에서 Facebook 제품을 이용할 때 보게 되는 콘텐츠( 광고 포함) 또는 기능을 회원님에게 맞춤화하거나, 다른 기기에서 회원님의 휴대폰에 표시된 광고에 대한 회원님의 반응 여부를 측정합니다. 이러한 기기로부터 얻는 정보는 다음과 같습니다. 기기 속성: 운영 체제, 하드웨어 및 소프트웨어 버전, 배터리 잔량, 신호 강도, 사용 가능한 저장 공간, 브라우저 유형, 앱 및 파일 이름 및 유형, 플러그인 등의 정보. 기기 작업: 창이 전면 또는 백그라운드에 있는지 여부, 마우스 움직임(인간과 봇을 구분하는 데 도움이 될 수 있음) 등 기기에서 수행되는 작업 및 동작에 관한 정보. 식별자: 고유 식별자, 기기 ID 및 기타 식별자. 기타 식별자의 예로는 회원님이 이용하는 게임, 앱 또는 계정 등의 식별자 및 가족 기기 ID(또는 동일한 기기나 계정과 관련된 Meta Company 제품 에 고유한 기타 식별자)가 있습니다. 기기 신호: Bluetooth 신호 및 근처 Wi-Fi 액세스 포인트, 비콘 및 셀 타워에 관한 정보. 기기 설정 데이터: GPS 위치, 카메라 또는 사진에 대한 액세스 등 회원님의 기기 설정을 활성화하여 Meta가 수신할 수 있도록 허가한 정보. 네트워크 및 연결: 이동통신사 또는 ISP 명칭, 언어, 시간대, 휴대폰 번호, IP 주소, 연결 속도 및 때로는 가까이 있거나 회원님의 네트워크에 있는 다른 기기에 관한 정보. 이를 통해 Meta는 휴대폰에서 TV로 동영상을 스트리밍 하는 등의 작업을 지원할 수 있습니다. 쿠키 데이터: 쿠키 ID 및 설정을 포함하여 기기에 저장된 쿠키 데이터. 쿠키 사용에 관한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 에서 알아보세요. 파트너가 제공하는 정보. 광고주, 앱 개발자 및 퍼블리셔는 이들이 사용하는 Meta 비즈니스 도구 , 즉 저희의 소셜 플러그인(예: '좋아요' 버튼), Facebook 로그인, 저희 API와 SDK 또는 Meta 픽셀 을 통해 저희로 정보를 제공할 수 있습니다. 이 파트너들은 회원님의 저희 계정 보유 여부 또는 저희 제품 로그인 여부와 관계없이 Meta 제품 밖에서의 회원님의 활동에 대한 정보(회원님의 기기, 회원님이 방문한 웹사이트, 회원님의 구매 내역, 회원님에게 표시되는 광고 및 회원님이 해당 파트너들의 서비스를 사용한 방법에 관한 정보 포함)를 제공합니다. 예를 들어, 게임 개발자는 저희 API를 사용하여 저희에게 회원님이 플레이하는 게임에 대해 알려줄 수 있고, 비즈니스는 회원님이 해당 비즈니스의 스토어에서 구매한 제품에 대해 알려줄 수 있습니다. 또한 저희는 회원님의 정보를 저희에게 제공할 권리가 있는 제3자 데이터 제공업체로부터 회원님의 온라인 및 오프라인 활동과 구매에 관한 정보를 받습니다. 회원님이 파트너를 방문하거나 파트너 서비스를 이용할 때 또는 파트너와 제휴한 제3자를 통해 서비스를 이용할 때 회원님의 데이터를 파트너가 받게 됩니다. 저희는 각 파트너에게 회원님의 데이터를 수집하고, 사용하고, 공유할 수 있는 합법적 권한을 획득한 후에 저희에게 데이터를 제공할 것을 요구합니다. 저희에게 데이터를 제공하는 파트너의 유형에 대해 자세히 알아보세요 . Meta 비즈니스 도구와 관련하여 저희의 쿠키 사용에 대한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 을 참조하시기 바랍니다. II. 저희가 정보를 활용하는 방법 저희는 (회원님이 동의할 경우) 아래에 설명된 바와 같이 보유한 정보를 이용하며, Meta 약관 및 Instagram 약관 에 설명된 Meta 제품 및 관련 서비스를 제공하고 지원합니다. 방법은 다음과 같습니다. Facebook 제품의 제공, 맞춤화 및 개선. 저희는 Meta 제품을 제공하기 위해 보유한 정보를 이용합니다. Meta 제품을 제공하는 데는 기능 및 콘텐츠(귀사 광고, Facebook 뉴스피드 , Instagram 피드 및 Instagram 스토리 포함)를 맞춤화하고 Meta 제품 안팎에서 회원님이 관심을 가질 만한 그룹 또는 이벤트 나 팔로우할 만한 주제 등을 추천하는 것이 포함됩니다. 회원님을 위해 특별하고 관련성 있는 맞춤화된 Meta 제품을 만들기 위해, 저희는 수집한 데이터와 회원님 및 다른 사람으로부터 얻은 정보(회원님이 제공하기로 선택한 특별 보호 데이터 포함)에 기초한 회원님의 관계, 기호, 관심사 및 활동, 회원님이 Meta 제품을 이용하고 상호 작용하는 방법, Meta 제품 안팎에서 회원님과 연결되어 있거나 회원님이 관심 있는 사람, 장소 또는 사물에 관한 정보를 이용합니다. Meta 제품의 기능, 콘텐츠, 추천을 포함하여 Facebook과 Instagram에서 개인에게 맞춤화된 경험을 제공하기 위해 저희가 회원님에 관한 정보를 어떻게 사용하는지 자세히 알아보세요. 또한 회원님에게 표시되는 광고 를 선택하는 방법도 자세히 알아볼 수 있습니다. Meta 제품 및 기기의 정보: 저희는 여러 Meta 제품 및 기기 활동에 관한 정보를 연결하여 회원님이 사용하는 모든 Meta 제품에 대해, 어디서 해당 제품을 이용하는지에 관계없이 더욱 맞춤화되고 일관된 경험을 제공합니다. 예를 들어 Instagram에서 회원님이 팔로우하거나 Messenger로 커뮤니케이션하는 사람들이 속한 Facebook 그룹에 가입할 것을 추천할 수 있습니다. 또한 예를 들어 다른 Meta 제품의 계정에 가입할 때 기존 Meta 제품의 등록 정보(전화번호 등)를 자동으로 기입하는 등 회원님에게 더욱 원활한 경험을 제공할 수도 있습니다. 위치 관련 정보: 저희는 회원님 및 다른 사람들에게 광고를 포함한 Meta 제품을 제공하고, 맞춤화하고, 개선하기 위해 위치 관련 정보 (예: 회원님의 현재 위치, 거주 지역, 가고 싶은 장소, 주변에 있는 비즈니스 및 사람)를 이용합니다. 위치 관련 정보는 정확한 기기 위치(수집을 허용한 경우), IP 주소 및 회원님 및 다른 사람이 Meta 제품을 이용하여 발생하는 정보(예를 들어 체크인 또는 참석 이벤트)와 같은 사항을 기반으로 할 수 있습니다. 제품 연구 및 개발: 저희는 보유한 정보를 이용하여 설문조사 및 리서치를 수행하고 새로운 제품과 기능을 테스트하며 문제를 해결함으로써 Meta 제품을 개발, 테스트 및 개선합니다. 광고 및 기타 홍보 콘텐츠: 저희는 보유한 정보(회원님의 관심사, 행동 및 관계에 관한 정보를 포함)를 이용하여 광고, 쿠폰 및 회원님에게 표시되는 기타 홍보 콘텐츠를 선택하고 맞춤화합니다. 저희가 광고를 선택하고 맞춤화하는 방법 , 광고 및 기타 홍보 콘텐츠를 선택하기 위해 사용한 데이터에 관한 회원님의 선택 사항을 Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 측정, 분석 및 기타 비즈니스 서비스 제공. 저희는 보유한 정보(방문한 웹사이트 및 광고 등 Facebook 제품 밖에서의 활동 포함)를 이용하여 광고주 및 기타 파트너가 광고 및 서비스의 성과와 배포를 측정하고 해당 서비스를 사용하는 사람들의 유형 및 사람들이 웹사이트, 앱, 서비스와 상호 작용하는 방식을 파악할 수 있도록 지원합니다. 이러한 파트너와 정보를 공유하는 방법에 대해 알아보세요 . 안전, 진실성 및 보안 강화. 저희는 보유한 정보를 이용하여 계정 및 활동을 확인하고, 유해 행위를 방지하며, 스팸 및 기타 부정적인 경험을 감지 및 방지하고, 제품의 무결성을 유지하며, Meta 제품 안팎의 안전 및 보안을 강화합니다. 예를 들어 저희는 보유한 데이터를 이용하여 의심스러운 활동 또는 저희 약관이나 정책 위반을 조사하거나 누군가에게 도움이 필요한 시점을 감지 합니다. 자세히 알아보려면 Facebook 보안 고객 센터 및 Instagram 보안 팁 을 방문하세요. 회원님과의 커뮤니케이션. 저희는 보유한 데이터를 이용하여 회원님에게 마케팅 자료를 제공하고 Facebook 제품에 관해 커뮤니케이션하며, Facebook 정책 및 약관에 대한 내용을 알려 드립니다. 또한 저희는 회원님의 정보를 이용하여 회원님의 연락에 대응합니다. 사회적 공익 연구 및 혁신. 저희는 보유한 정보(저희와 협업하는 연구 파트너의 정보 포함)를 이용하여 일반 사회 복지, 기술 발전, 공익, 보건 및 복지에 관한 주제의 연구 와 혁신을 진행하며, 이를 지원합니다. 예를 들어, 위기 상황 시 저희가 보유한 이동 패턴 정보를 분석하여 구호 활동을 지원합니다. Facebook 연구 프로그램에 대해 자세히 알아보세요 . III. 정보 공유 방법 회원님의 정보는 다음 방법으로 다른 사람들과 공유됩니다. Meta 제품에서 공유 회원님이 공유하고 커뮤니케이션하는 사람 및 계정 회원님은 Facebook 제품을 이용하여 공유 또는 커뮤니케이션할 때 공유할 내용에 대한 공개 대상을 선택 합니다. 예를 들어 회원님은 Facebook에 게시물을 포스팅할 때 그룹, 모든 친구, 전체 공개 또는 맞춤 설정한 리스트에 있는 사람 등 게시물에 대한 공개 대상을 선택합니다. 마찬가지로, 회원님이 Messenger 또는 Instagram을 사용하여 사람 또는 비즈니스와 커뮤니케이션할 때 해당 사람 및 비즈니스는 회원님이 전송하는 콘텐츠를 볼 수 있습니다. 회원님의 네트워크는 회원님이 Meta 제품에서 취한 행동(광고 및 홍보 콘텐츠 참여 포함)을 볼 수도 있습니다. 또한 저희는 다른 계정이 해당 계정의 Facebook 또는 Instagram 스토리를 누가 조회했는지 볼 수 있도록 허용합니다. 공개 정보 는 계정이 없는 경우를 포함하여 Facebook 제품 안팎에서 누구든지 볼 수 있습니다. 여기에는 Instagram 사용자 이름, 공개 대상과 공유하는 모든 정보, 회원님 Facebook 공개 프로필 에 있는 정보, Facebook 페이지에서 공유하는 콘텐츠, Instagram 공개 계정 또는 Facebook Marketplace 와 같은 기타 공개 포럼에서 공유하는 콘텐츠가 포함됩니다. 회원님, Facebook과 Instagram을 사용하는 다른 사람들 그리고 저희는 검색 결과 또는 도구 및 API를 통해 Meta 제품(Meta Company 제품 포함) 안팎에 있는 모든 사람에게 공개 정보에 대한 액세스 권한을 제공하거나 해당 공개 정보를 전송할 수 있습니다. 공개 정보는 검색 엔진, API 같은 제3자 서비스, TV 같은 오프라인 매체와 앱, 웹사이트, 저희 제품과 통합된 기타 서비스를 통해 보거나 액세스하거나 다시 공유하거나 다운로드할 수도 있습니다. 공개 정보 및 Facebook 과 Instagram 에서 공개 범위를 설정하는 방법에 대해 자세히 알아보세요. 다른 사람이 회원님과 공유하거나 다시 공유한 콘텐츠 Meta 제품에서 회원님의 활동을 볼 수 있는 사람들은 Meta 제품 안팎에서 다른 사람들(회원님이 공유한 공개 대상 이외의 사람들과 비즈니스 포함)과 이를 공유할지 여부를 선택할 수 있으므로, 회원님은 공유 대상을 선택할 때 이를 고려해야 합니다. 예를 들어 특정 친구 또는 계정에 게시물을 공유하거나 메시지를 전송할 때, 해당 친구 또는 계정은 직접 또는 Horizon 월드 같은 가상 현실 환경에서 콘텐츠를 다운로드하거나 스크린샷으로 캡처하거나 Meta 제품 안팎으로 다른 사람과 다시 공유할 수 있습니다. 또한 다른 사람의 게시물에 댓글을 달거나 공감할 때, 그 사람의 콘텐츠를 볼 수 있는 사람은 회원님의 댓글이나 공감 상태를 볼 수 있고 해당 콘텐츠를 게시한 사람은 나중에 공개 대상을 변경할 수 있습니다. 사람들은 Facebook 제품을 이용하여 회원님에 관한 콘텐츠를 만들고 원하는 공개 대상과 공유할 수도 있습니다. 예를 들어 스토리에 회원님의 사진을 공유하고, 게시물에 회원님의 위치를 언급하거나 태그하고, 게시물 또는 메시지에 회원님에 대한 정보를 공유할 수 있습니다. 다른 사람들이 Facebook 제품에서 회원님에 대해 공유한 내용에 불편함을 느낀다면 콘텐츠를 신고 하는 방법을 알아보실 수 있습니다. Meta 제품에서 회원님의 활동 상태 또는 존재에 관한 정보. 회원님의 네트워크에 있는 사람들은 Facebook 제품에 대한 회원님의 활동 여부( Instagram , Messenger 또는 Facebook에서 활동 상태인지, 언제 마지막으로 Facebook 제품을 이용하였는지 포함)를 알려주는 신호를 볼 수 있습니다. Meta 제품에 포함되어 있거나 서비스를 이용한 앱, 웹사이트 및 제3자 통합. Meta 제품을 이용하거나 Meta 제품에 통합된 타사 앱, 웹사이트 또는 기타 서비스를 이용할 경우 해당 타사에서 회원님이 게시하거나 공유한 내용에 관한 정보를 받을 수 있습니다. 예를 들어 Facebook 친구와 게임을 하거나 웹사이트에서 Facebook 댓글 달기 또는 공유하기 버튼을 사용하는 경우, 게임 개발자 또는 웹사이트는 게임 내 회원님의 활동에 대한 정보를 받거나 회원님이 Facebook에서 해당 웹사이트를 통해 공유한 댓글이나 링크에 관한 정보를 받을 수 있습니다. 또한 이러한 제3자 서비스를 다운로드하거나 사용할 때 해당 제3자는 Facebook의 공개 프로필 및 회원님이 해당 제3자에 공유한 모든 정보에 액세스할 수 있습니다. 회원님이 공유를 선택할 경우 회원님이 이용하는 앱과 웹사이트에서 Facebook 친구 리스트를 수신할 수 있습니다. 단, 회원님이 이용하는 앱과 웹사이트는 회원님의 Facebook 친구에 관한 기타 모든 정보 또는 회원님의 Instagram 팔로워에 관한 정보를 수신할 수 없습니다. 이는 회원님의 친구와 팔로워가 이 정보를 공유하도록 선택했더라도 마찬가지입니다. 이러한 제3자 서비스에서 수집되는 정보는 Facebook 약관 및 정책이 아닌 해당 제3자의 자체 약관 및 정책의 적용을 받습니다. Facebook 및 Instagram의 기본 버전을 제공하는 기기와 운영 체제(즉, 저희가 저희 자체의 앱을 개발하지 않은 기기와 운영 체제)는 저희 핵심 기능을 회원님에게 제공하기 위해 회원님의 친구가 회원님과 공유하는 정보를 포함하여 회원님이 공유하기로 선택하는 모든 정보에 액세스할 수 있습니다. 참고: 저희는 현재 남용을 방지하기 위해 개발자의 데이터 액세스 권한을 추가로 제한하고 있습니다. 예를 들어, 저희는 회원님이 3개월 동안 앱을 사용하지 않았고, 저희가 로그인을 변경하는 경우 회원님의 Facebook 및 Instagram에 대한 개발자의 액세스 권한을 삭제하며, 다음 버전에서 앱 검수 없이 앱에서 요청할 수 있는 데이터를 이름, Instagram 사용자 이름, 소개, 프로필 사진, 이메일 주소만 포함되도록 축소합니다. 더 많은 데이터를 요청하려면 저희의 허가를 받아야만 합니다. 새로운 소유자. Facebook 제품 또는 해당 자산의 전부 또는 일부에 대한 소유권 또는 운영권이 변경되는 경우, 저희는 회원님에 대한 정보를 새로운 소유주에게 제공할 수 있습니다. 제3자 파트너와 공유 저희는 Meta를 지원하고 Meta 제품을 제공하고 개선하는 데 도움을 주거나 Meta 비즈니스 도구를 사용하는 제3자 파트너와 협력하여 이들의 비즈니스를 성장시킴으로써 회사를 운영하고 전 세계 사람들에게 무료 서비스를 제공하고 있습니다. 저희는 회원님의 정보를 누구에게도 판매하지 않으며 앞으로도 판매하지 않을 것입니다. 저희는 또한 파트너가 저희가 제공한 데이터를 이용하고 공개하는 방법에 엄격한 제한을 가하고 있습니다. 저희가 정보를 공유하는 제3자의 유형은 다음과 같습니다. Meta 분석 서비스를 사용하는 파트너. 저희는 개인 및 비즈니스가 사람들이 Meta 제품 안팎의 게시물, 리스트, Facebook 페이지, 동영상 및 기타 콘텐츠에 참여하는 방식을 파악하는 데 참고할 수 있는 취합된 통계 및 인사이트를 제공합니다. 예를 들어 Facebook 페이지 관리자 및 Instagram 비즈니스 프로필은 게시물을 보거나, 게시물에 반응하거나, 댓글을 단 사람의 수에 관한 정보 외에도 취합된 인구 통계학적 특성 및 기타 계정 또는 Facebook 페이지와의 상호 작용을 파악하는 데 도움이 되는 정보를 받습니다. 광고주. 저희는 광고주에게 광고를 보는 사람들의 유형 및 광고 실적에 관한 보고서를 제공하지만 회원님을 개인적으로 식별하는 정보(회원님에게 연락하거나 식별하는 데 이용될 수 있는 이름 또는 이메일 주소 같은 정보)는 회원님이 허용하지 않는 한 공유하지 않습니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성에게 해당 광고가 노출됨)를 제공합니다. 또한 어떠한 광고가 회원님의 구매나 광고주에 관한 행동을 하게 유도했는지 확인합니다. 측정 파트너. 저희는 회원님에 대한 정보를 수집하여 파트너에게 분석 및 측정 보고서를 제공하는 회사와 정보를 공유합니다. Meta 제품 안에서 상품 및 서비스를 제공하는 파트너. 회원님이 프리미엄 콘텐츠를 구독하거나 Facebook 제품 내 판매자로부터 상품을 구매하는 경우, 해당 콘텐츠 제작자 또는 판매자는 회원님이 공유하는 공개 정보 및 기타 정보 외에도 배송 및 연락처 세부 정보를 포함하여 거래를 완료하는 데 필요한 정보를 받을 수 있습니다. 벤더 및 서비스 공급자. 저희는 기술 인프라 서비스 제공, Facebook 제품 이용 방법 분석, 고객 서비스 제공, 결제 간소화 또는 설문 수행 등의 방법을 통해 Facebook 비즈니스를 지원하는 벤더 및 서비스 공급자에게 정보와 콘텐츠를 제공합니다. 연구원 및 학자. 또한 저희는 연구 파트너 및 학자 에게 정보와 콘텐츠를 제공하여, 그들이 Facebook의 비즈니스 또는 사명을 지원하는 학문과 혁신을 발전시키는 연구, 그리고 일반적인 사회 복지, 기술 발전, 공익, 건강 및 복지에 대한 발견 및 혁신을 향상시키는 연구를 수행할 수 있도록 합니다. 사법당국 또는 법적 요청. 저희는 아래에 명시된 상황에서 사법당국 또는 법적 요청에 대응하여 정보를 공유합니다. Facebook 설정 및 Instagram 설정 에서 회원님 또는 다른 사람이 제3자 파트너와 공유하는 정보를 설정하는 방법에 대해 자세히 알아보세요. IV. Meta Companies가 협력하는 방식 Facebook과 Instagram은 회원님이 사용하는 모든 Meta Company 제품 에서 혁신적이고 관련성이 있으며 일관적이고 안전한 환경을 제공하기 위해 Meta Companies (WhatsApp 및 Oculus 포함)와 인프라, 시스템 및 기술을 공유합니다. 또한 저희는 이러한 목적을 위해, 관련 법에서 허용하는 경우에 Meta Companies의 약관 및 정책에 따라 Meta Companies에서 회원님에 대한 정보를 처리합니다. 예를 들어 저희는 WhatsApp의 서비스에서 스팸을 보내는 계정에 대한 정보를 처리하여 Facebook, Instagram 또는 Messenger에서 해당 계정에 대해 적절한 조치를 취할 수 있습니다. 또한 저희는 다른 Meta Company 제품의 고유 사용자 수를 파악하는 등 사람들이 Meta Company 제품을 이용하고 상호 작용하는 방법을 파악하기 위해 노력하고 있습니다. V. 회원님의 정보를 관리 또는 삭제하는 방법 저희는 데이터 액세스, 수정, 복사 및 삭제 기능을 제공합니다. Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 저희는 더 이상 Meta 서비스 및 Meta 제품을 제공할 필요가 없는 시점, 그리고 회원님의 계정이 삭제되는 시점 중 먼저 도달하는 시점까지만 데이터를 저장합니다. 이는 데이터의 성격, 수집 및 처리된 이유, 관련된 법적 또는 운영상 보존 필요성과 같은 요인에 따라 개별적으로 결정됩니다. 예를 들어 회원님이 Facebook에서 무언가를 검색할 때 언제든지 검색 기록에서 해당 검색어에 액세스하고 삭제할 수 있지만, 해당 검색어에 대한 로그는 6개월 후에 삭제됩니다. 회원님이 계정 확인을 위해 정부가 발행한 신분증명서 사본을 제출하는 경우 저희는 달리 명시하지 않는 한 검토 후 30일 이내에 해당 사본을 삭제합니다. 공유된 콘텐츠 및 소셜 플러그인을 통해 얻은 쿠키 데이터 삭제 에 대해 자세히 알아보세요. 계정을 삭제하면 회원님의 사진이나 상태 업데이트 등 회원님이 게시한 사항들이 삭제 되며 나중에 해당 정보를 복원할 수 없습니다. 다른 사람이 회원님에 대해 공유한 정보는 회원님의 계정에 포함되지 않으며 삭제되지 않습니다. 계정을 삭제하지 않고 제품 이용을 일시적으로 중단하려면 계정을 비활성화할 수 있습니다. 회원님의 계정을 삭제하려면 언제든지 Facebook 설정 및 Instagram 설정 을 방문하세요. VI. 법적 요청에 대한 대응과 피해 방지 Meta는 회원님의 정보에 액세스하고 이를 보존하며 규제 당국, 사법당국 또는 다른 사람들과 이 정보를 공유합니다. 법적인 요청(예: 수색 영장, 법원 명령서, 소환장 등)이 수반되고 법의 집행을 위해 필요하다고 판단될 경우. 여기에는 미국 외 지역 관할권에서의 법적 요청이 수반되고, 해당 관할권의 법에 의해 필요성이 인정되며, 그 지역 내의 사용자들에게 영향을 미침과 동시에 국제적으로 용인되는 기준에 부합한다고 판단될 때 해당 관할권의 요청을 받아들이는 경우가 포함됩니다. Meta가 필요성을 인정할 경우 사기, 제품의 권한 없는 사용, 약관 또는 정책 위반, 또는 기타 유해하거나 불법적인 활동을 감지 및 예방하고 이에 대처하는 조치, 조사 또는 규제 요구를 포함하여 Meta(권리, 자산 또는 제품), 회원님 또는 다른 사람을 보호하기 위한 조치, 생명을 보호하고 상해를 막기 위한 조치가 필요합니다. 예를 들어 관련성이 있는 경우 저희는 제품의 사기, 남용 및 기타 유해한 활동을 방지하기 위해 계정의 신뢰성에 대한 정보를 제3자 파트너와 주고받습니다. 저희 제품을 이용한 구매 활동과 관련된 금융 거래 데이터를 포함해 저희가 수집하는 회원님의 정보는 법적인 요청이나 의무, 정부 조사, 저희의 약관과 정책에 대한 잠재적 위반에 대한 조사의 대상이 되는 경우 또는 다른 피해를 방지하기 위한 목적으로 장기간 액세스 및 보관될 수 있습니다. 또한 약관 악용 사례 또는 기타 약관에 대한 위반 행위의 반복을 막기 위해 약관 위반으로 비활성화된 계정의 정보를 최소 1년 이상 보존합니다. VII. 글로벌 서비스의 일환으로 데이터를 운영하고 이전하는 방법 저희는 본 개인정보처리방침에 따라 전 세계적으로 정보를 공유하는바, Meta Companies 내부적으로 정보를 공유하고, 외부적으로 저희의 파트너, 그리고 회원님이 연결하고 공유하는 대상과도 정보를 공유합니다. 예를 들어 회원님의 정보는 본 정책에 설명된 목적을 위해 미국 또는 회원님이 거주하는 지역 이외의 기타 국가로 이전 또는 전송되거나 이들 국가에서 저장 및 처리될 수 있습니다. 이러한 데이터 이전은 Meta 약관 및 Instagram 약관 에 명시된 서비스를 제공하고 저희 제품을 전 세계적으로 운영하며 회원님에게 제공하기 위해 필요합니다. 저희는 표준 계약 조항 을 활용하고, 해당할 경우 특정 국가에 대한 유럽연합 집행위원회의 적정성 결정 을 따르며, 미국 및 기타 국가로의 데이터 이전에 대해 회원님의 동의를 받습니다. VIII. 개인정보처리방침 변경 사항에 대한 안내 저희는 본 정책을 변경하기 전에 회원님에게 알리고, 회원님이 Facebook 제품 이용을 계속하기 전에 회원님에게 변경된 정책을 검토할 기회를 제공할 것입니다. 대한민국 개인정보 보호 고지사항 저희의 대한민국 개인정보 보호 고지사항 을 확인하여 회원님이 행사할 수 있는 개인정보 보호 권리, 저희가 회원님의 정보를 공유하는 제3자에 관한 상세 정보 및 기타 사항에 대해 자세히 알아보세요. IX. Meta에 문의하는 방법 Facebook 또는 Instagram 의 개인정보처리방침을 자세히 알아보세요. 본 정책에 관해 궁금하신 점이 있으면 아래에 설명된 바와 같이 Meta에 문의하실 수 있습니다. Meta Platforms, Inc.는 대한민국 사용자의 개인정보 관련 고충에 관한 문의를 위해 Privacy Agent Korea Co., Ltd.를 국내 대리인으로 지정하였습니다. 국내대리인에게 온라인 , 전화나 우편 또는 이메일로 문의하실 수 있습니다. Privacy Agent Korea Co., Ltd. ATTN: 대표이사 박천희 서울특별시 종로구 새문안로5가길 28 전화: 02-737-0455 저희는 Meta 개인정보처리방침 및 업무 방식에 관하여 회원님과 분쟁이 있을 경우 TrustArc를 통해 해결할 수 있습니다. 이에 관하여는 TrustArc의 웹사이트 를 통해 TrustArc에 문의하세요. 다음과 같은 방법으로 문의할 수 있습니다. 온라인 또는 우편 문의: Meta Platforms, Inc. ATTN: Privacy Operations 1601 Willow Road Menlo Park, CA 94025 최종 수정일: 2022년 1월 4일 Facebook의 데이터 정책에 동의합니다 서비스 약관 Meta 서비스 약관이 개정됩니다. 이 개정 사항은 2025년 1월 1일부터 적용됩니다. 새로운 약관을 읽어보세요 . Meta는 사람들이 서로 교류하고 커뮤니티를 만들며 비즈니스를 성장시킬 수 있는 기술과 서비스를 개발합니다. (본 약관이 아닌) 별도의 약관이 적용된다고 명시되어 있지 않은 한, 본 약관은 회원님의 Facebook, Messenger 및 기타 저희가 제공하는 제품, 기능, 앱, 서비스, 기술, 소프트웨어( Meta 제품 또는 제품 ) 이용에 적용됩니다. 해당 제품은 Meta Platforms, Inc.가 회원님에게 제공합니다. 달리 명시된 경우를 제외하고 저희는 회원님에게 Facebook 또는 기타 본 약관이 적용되는 제품 및 서비스의 사용료를 청구하지 않습니다. 그 대신, 비즈니스와 단체 및 다른 사람이 저희에게 그들의 제품 및 서비스 광고를 회원님에게 보여드리도록 비용을 지불합니다. 저희 제품을 이용함으로써 회원님은 저희가 회원님 및 회원님의 관심사와 관련 있을 수 있다고 생각하는 광고를 보여주는 것에 동의하게 됩니다. 저희는 회원님의 개인정보를 이용하여 회원님에게 보여드릴 맞춤형 광고를 결정합니다. 저희는 회원님의 개인정보를 광고주에게 판매하지 않으며, 회원님이 저희에게 특정 허락을 제공하지 않는 한 회원님을 직접 식별할 수 있는 정보(예를 들어 이름, 이메일 주소 또는 기타 연락처 정보)를 광고주에게 공유하지 않습니다. 대신 광고주는 광고를 노출하기를 원하는 타겟과 같은 정보를 저희에게 알려줄 수 있고, 저희는 관심이 있을 만한 사람에게 해당 광고를 노출합니다. 저희는 사람들이 광고주의 콘텐츠와 어떻게 상호작용하고 있는지를 이해할 수 있도록 광고주에게 광고 성과 보고서를 제공합니다. 본 약관에 따라 맞춤형 광고가 Meta 제품에서 작동하는 방식에 대해 더 알아보려면 아래 제2조를 참조하세요. 저희의 개인정보처리방침 에는 저희가 회원님에게 보여드릴 광고를 결정하고 아래 설명된 기타 모든 서비스를 제공하기 위해 회원님의 개인정보를 어떻게 수집하고 이용하는지가 설명되어 있습니다. 회원님은 또한 관련 Meta 제품의 설정 페이지에서 저희가 회원님의 데이터를 이용하는 방식에 관해 회원님이 선택할 수 있는 개인정보 설정을 언제든지 검토할 수 있습니다. 1. 저희가 제공하는 서비스 저희의 사명은 사람들이 커뮤니티를 이룰 수 있도록 하여 전 세계를 더욱 가까워지게 만드는 것입니다. 저희는 이를 실현하기 위해 회원님에게 아래에 설명된 제품과 서비스를 제공합니다: 맞춤화된 경험을 제공합니다. Facebook 뉴스피드나 저희의 동영상 플랫폼에 표시되는 게시물, 스토리, 이벤트, 광고 및 기타 콘텐츠부터 회원님이 팔로우하는 Facebook 페이지 및 회원님이 이용할 만한 기타 기능(예: Facebook Marketplace, 검색)에 이르기까지 회원님만을 위한 Facebook을 경험하실 수 있습니다. 예를 들어 회원님이 만드는 관계, 회원님이 선택하는 옵션 및 설정 사항, 회원님이 제품 내외에서 공유하고 활동하는 사항과 같은 데이터를 이용하여 회원님의 경험을 맞춤화합니다. 회원님을 회원님에게 중요한 사람 및 단체와 연결합니다. 저희는 회원님이 이용하는 여러 Meta 제품에서 회원님에게 중요한 사람, 그룹, 비즈니스, 단체 및 다양한 다른 사항들을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님과 다른 사람들에게 제안(예: 가입할 그룹, 참석할 이벤트, 팔로우하거나 메시지를 보낼 Facebook 페이지, 시청할 프로그램 및 친구를 맺고 싶을 만한 사람 제안)하기 위해 데이터를 이용합니다. 더 친밀한 관계는 더 나은 커뮤니티를 만듭니다. 저희는 사람들이 본인이 관심 있는 사람, 그룹 및 단체와 연결될 때 저희 서비스가 가장 가치 있다고 믿습니다. 회원님이 자신을 표현하고 회원님이 중요하게 생각하는 것을 나눌 수 있도록 합니다. Facebook에서 회원님이 자신을 표현하고, 중요하게 생각하는 것을 친구와 가족, 다른 사람들과 나누는 방법에는 여러 가지(예: 여러 Meta 제품에서 회원님의 설정에 따라 상태 업데이트, 사진, 동영상 및 스토리 공유, 친구 또는 여러 사람에게 메시지 전송, 음성 또는 영상 통화 걸기, 이벤트 또는 그룹 생성, 프로필에 콘텐츠 추가, 다른 사람이 회원님의 콘텐츠에 참여하는 방식에 관한 인사이트 표시)가 있습니다. 또한 저희는 사람들이 증강 현실 및 360도 동영상과 같은 기술을 이용하여 Meta 제품에서 더욱 풍부하고 흥미로운 콘텐츠를 만들고 공유할 수 있도록 새로운 방법들을 개발해 왔고 또 계속해서 개발하고 있습니다. 회원님이 관심을 가질 만한 콘텐츠, 제품 및 서비스를 찾을 수 있도록 지원합니다. 저희는 Facebook 및 기타 Meta 제품을 이용 중인 많은 비즈니스와 단체가 제공하는 콘텐츠, 제품 및 서비스를 발견하는 데 도움이 되는 맞춤형 광고, 제안 및 기타 광고 콘텐츠 또는 커머스 콘텐츠를 회원님에게 보여드립니다. 자세한 내용은 아래 제2조를 참조하시기 바랍니다. 저희 서비스의 안전, 보안 및 무결성을 향상하고, 유해 행위를 방지하고, 사용자 커뮤니티를 안전하게 보호합니다. 사람들은 자신이 안전하고 보호받고 있다고 느껴야만 Meta 제품에서 커뮤니티를 형성합니다. 저희는 저희 제품 및 서비스의 보안(가용성, 신뢰성, 무결성 및 기밀성 포함)을 유지하기 위해 노력합니다. 저희는 전 세계에 전담팀을 두고 외부 서비스 제공업체, 파트너 및 관련 단체와 협업하며 저희 제품의 잠재적 오용, 타인에 대한 유해 행위, 그리고 저희의 잠재적인 위반 콘텐츠 사용자 신고에 대한 응답을 포함하여 저희가 저희의 커뮤니티를 지원하거나 보호하는데 도움이 될 수 있는 상황을 감지하기 위해 최첨단 기술 시스템을 개발합니다. 저희는 이러한 콘텐츠 또는 행위를 발견하는 경우, 저희의 평가를 기반으로 알림 전송, 도움 제공, 콘텐츠 삭제, 특정 기능에 대한 접근 차단 또는 제한, 계정 비활성화 또는 사법당국에 연락 등 적절한 조치를 취할 것입니다. 저희는 저희 제품을 이용하는 사람의 오용 또는 유해 행위를 감지한 경우 또는 Meta 제품, 사용자 및 커뮤니티를 안전하게 보호하기 위해 Meta Companies 사이에 데이터를 공유합니다. 예를 들어, 저희는 금융 상품 및 서비스를 제공하는 Meta Companies와 정보를 공유하여 해당 회사의 안전, 보안, 무결성 향상과 관련 법률 준수를 돕습니다. Meta는 법률에 의해 요구되거나 허용된다는 선의의 믿음이 있는 경우 회원님에 관하여 수집한 정보를 액세스, 보존, 이용 및 공유할 수 있습니다. 자세한 내용은 저희 개인정보처리방침 을 참고하세요. 경우에 따라 감독위원회가 위원회 약관 및 정관에 따라 저희의 결정을 검토할 수 있습니다. 자세한 내용은 여기 에서 알아보세요. 모든 사람에게 안전하고 실용적인 서비스를 제공하기 위해 최첨단 기술을 사용하고 개발합니다. 저희는 사람들이 신체적 능력이나 지리적 위치와 관계없이 안전하게 저희의 제품을 이용할 수 있도록 인공 지능, 머신 러닝 시스템 및 증강 현실과 같은 최첨단 기술을 이용하고 개발하고 있습니다. 예를 들어, 이러한 기술은 시각 장애가 있는 사람들이 Facebook이나 Instagram에서 공유된 사진 또는 동영상에 무엇이 있는지, 누가 있는지 파악할 수 있도록 도움을 줍니다. 또한 인터넷 접속이 원활하지 않은 지역에서도 보다 많은 사람들이 인터넷을 이용할 수 있도록 첨단 네트워크 및 통신 기술을 구축하고 있습니다. 뿐만 아니라 저희는 저희 커뮤니티 및 제품의 무결성을 손상시킬 수 있는 유해하고 위험한 활동을 감지하여 삭제하는 기능을 개선하기 위해 자동화 시스템을 개발합니다. 저희의 서비스를 향상하기 위한 방법을 연구합니다. 저희는 저희 제품의 개발, 테스트 및 개선을 위한 연구를 진행합니다. 여기에는 설문 조사를 실시하고 새로운 기능의 테스트 및 문제 해결을 진행하는 등의 방법으로 저희가 보유한 사용자 데이터를 분석하며, 사람들이 저희의 제품을 이용하는 방식을 이해하는 작업이 포함됩니다. 저희의 개인정보처리방침 에는 저희가 저희 서비스를 개발하고 개선할 목적으로 이 연구를 지원하기 위해 데이터를 이용하는 방식이 설명되어 있습니다. Meta Company 제품 전반에 걸쳐 일관되고 원활한 경험을 제공합니다. 저희의 제품은 회원님에게 중요한 사람, 그룹, 비즈니스, 단체, 다른 사항을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님이 이용하는 다양한 Meta Company 제품 에 걸쳐 일관되고 원활한 경험이 이뤄지도록 저희 시스템을 설계합니다. 예를 들어 회원님이 Facebook에서 소통하는 사람들에 대한 데이터를 이용해 Instagram 또는 Messenger에서도 쉽게 그들과 연결할 수 있도록 지원하며, Messenger를 통해 Facebook에서 팔로우하는 비즈니스와 소통할 수 있도록 지원합니다. 저희 서비스 이용에 대한 보장: 글로벌 서비스를 운영하고 회원님이 전 세계의 사람들과 연결될 수 있도록 하기 위하여, 저희는 회원님의 거주 국가 이외의 지역을 비롯하여 전 세계 데이터 센터, 파트너, 서비스 제공업체, 공급업체 및 시스템에 콘텐츠와 데이터를 이전, 저장, 배포해야 합니다. 저희 서비스를 제공하기 위해서는 본 글로벌 인프라의 이용이 필수적입니다. 이 인프라는 Meta Platforms, Inc., Meta Platforms Ireland Limited 또는 그 계열사가 소유, 운영하거나 통제할 수 있습니다. 2. Meta 서비스를 위한 자금 조달 방식 Facebook과 기타 저희가 제공하는 제품 및 서비스의 사용료를 지불하지 않는 대신, 회원님은 본 약관이 적용되는 Meta 제품을 이용함으로써 비즈니스 및 단체들이 Meta Company 제품 내외에서 홍보를 위해 저희에게 비용을 지불한 맞춤형 광고 및 기타 상업적 콘텐츠와 홍보 콘텐츠를 보게 될 수 있다는 데 동의합니다. 저희는 회원님과 보다 관련성이 높을 수 있는 맞춤형 광고 및 홍보 콘텐츠를 보여드리기 위해 회원님의 활동 및 관심사에 대한 정보 등 회원님의 개인정보를 이용합니다. 개인정보 보호는 저희가 저희의 맞춤형 광고 시스템을 설계할 때 핵심적으로 고려해온 사안입니다. 즉, 저희는 광고주에게 회원님의 신원을 알리지 않고도 회원님에게 회원님과 관련 있고 유용한 광고를 보여드릴 수 있습니다. 저희는 회원님의 개인정보를 판매하지 않습니다. 저희는 광고주로 하여금 저희에게 그들의 비즈니스 목표, 광고 타게팅 대상(예: 사이클링을 좋아하는 18~35세 사이의 사람) 등을 알려줄 수 있도록 합니다. 저희는 그런 다음 해당 광고에 관심이 있을 만하다고 생각하는 사람에게 광고를 노출합니다. 저희는 또한 사람들이 Meta 제품 내외에서 광고주의 콘텐츠와 어떻게 상호작용하고 있는지 광고주들이 이해할 수 있도록 광고주들에게 광고의 성과 보고서를 제공합니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성이 해당 광고를 보았음)를 제공합니다. 저희는 회원님이 구체적으로 허락하지 않는 한 회원님을 직접적으로 식별할 수 있는 정보(이름 또는 이메일 주소와 같이 그 정보만으로 회원님에게 연락을 취하는 데 이용될 수 있거나 회원님을 식별할 수 있는 정보)를 공유하지 않습니다. 여기 에서 Meta 광고의 작동 원리에 대해 자세히 알아보세요. 저희는 위에 명시된 서비스를 회원님께 제공하기 위해 회원님의 개인정보를 수집하고 이용합니다. 저희의 개인정보처리방침 에서 저희의 데이터 수집 및 이용 방법에 대해 자세히 알아볼 수 있습니다. 회원님은 회원님이 보게 되는 광고와 광고주의 유형, 저희가 회원님에게 보여드릴 광고를 결정하기 위해 이용하는 정보의 유형을 통제할 수 있습니다. 더 알아보기. 3. Facebook 및 커뮤니티에 대한 약속 저희는 저희의 사명을 실현하기 위해 회원님 및 다른 사람들에게 본 서비스를 제공합니다. 이에 대해 회원님은 다음과 같은 약속을 해야 합니다. Facebook을 이용할 수 있는 사람 사람들이 각자의 의견과 행동에 대한 책임을 질 때 Facebook 커뮤니티는 더 안전하고 신뢰할 수 있는 공간이 됩니다. 이러한 이유로 회원님은 다음 사항을 준수해야 합니다. 일상생활에서 사용하는 것과 동일한 이름을 계정에 제공해야 합니다. 회원님에 관한 정확한 정보를 제공해야 합니다. 계정(본인 계정)은 하나만 만들고 개인적인 용도로 이용해야 합니다. 비밀번호를 공유하거나, 회원님의 Facebook 계정에 대한 접근 권한을 다른 사람에게 부 | 2026-01-13T08:49:47 |
https://www.dabeaz.com/per.html | Python Essential Reference, 4th Ed. dabeaz Courses Writing Python Distilled Python Essential Reference Python Cookbook Usenix :login; Academic Publications Blog Speaking Talks Tutorials Software Blog Newsletter Chat --> About Contact Search --> Python Essential Reference Python Essential Reference, 4th Edition [Amazon] Addison-Wesley Professional (July 19, 2009) ISBN 0672329786; 717 pages About Now in its 4th edition, the Essential Reference was the first major reference book published for Python--originally appearing in 1999. It is meant to be a serious reference for working programmers. As such, it tries to provide detailed coverage of every Python language feature, especially advanced features that often get skipped in introductory books. It also provides expanded reference material for most of the most commonly used modules in the standard library. I primarily wrote this book for myself and use it on a regular basis in my day-to-day work. Others have also found it to be useful. Resources Errata Editorial Reviews The Python Essential Reference hits the "sweet spot of concise usefulness." (9/10 rating) - Slashdot "Python Essential Reference is exactly what the title says - it's *essential*... [It] is a book that you must have on your bookshelf." - Mike Riley [ Dr. Dobb's Journal ] Selected Amazon Reviews "Every so often a book comes along that makes you ask yourself, "Gee, when was the last time I had my eyes checked?" David M. Beazley's Python: Essential Reference is just such a book." "This is probably the best serious reference book for programmers since K&R's The C Programming Language." "This is not a book that will see much use in my office. In fact, I think I'm going to put it out of sight -- just looking at it annoys me." "This is the best programming book I have ever seen." 5th Edition Status As Python has matured, it has grown into a significantly larger language. As a result, it is no longer feasible for me to write a comprehensive reference for it. As such, there will be no 5th edition. However, much the core material once found in the Essential Reference will appear in a new book Python Distilled to appear in fall 2021. Copyright (C) 2005-2026, David Beazley | 2026-01-13T08:49:47 |
https://future.forem.com/t/newsletter | Newsletter - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # newsletter Follow Hide Create Post Older #newsletter posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Awesome Robots Digest - Issue #14 - December 12, 2025 Bob Jiang | awesomerobots Bob Jiang | awesomerobots Bob Jiang | awesomerobots Follow Dec 16 '25 Awesome Robots Digest - Issue #14 - December 12, 2025 # digest # newsletter # robotics # ai Comments Add Comment 11 min read loading... trending guides/resources Awesome Robots Digest - Issue #14 - December 12, 2025 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://www.facebook.com/recover/initiate/?ars=facebook_login&cancel_lara_pswd=0&next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjwebsite-go%252Freadiness-probe-3co0%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag | 비밀번호를 잊으셨나요? | 로그인할 수 없는 경우 | Facebook 내 계정 찾기 내 계정 찾기 계정을 검색하려면 이메일 주소 또는 휴대폰 번호를 입력하세요. 취소 검색 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:47 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fzeroday.forem.com%2Fagardnerit%2Fosquery-opentelemetry--55c&title=osquery%20%2B%20OpenTelemetry%20%3D%20%E2%9D%A4%EF%B8%8F&summary=As%20you%20probably%20know%20by%20now%2C%20osquery%20effectively%20turns%20your%20endpoints%20into%20SQL%20endpoints%20that%20you%20can...&source=Security%20Forem | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (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)) | 2026-01-13T08:49:47 |
https://future.forem.com/new/robotics | New Post - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Join the Future Future is a community of 3,676,891 amazing enthusiasts Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to Future? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://open.forem.com/emma-suntech/led-strip-lighting-is-a-distributed-system-and-long-runs-will-humble-you-2bb7 | LED strip lighting is a distributed system (and long runs will humble you) - Open Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Open Forem Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse emmma Posted on Jan 7 LED strip lighting is a distributed system (and long runs will humble you) # hardware # learning # networking I used to think LED strips were “stick + power + done.” Then I built a longer run (ceiling cove / hallway line / shelf edge) and watched the far end dim, “white” shift warm, and—on addressable effects—animations start to stutter. That’s when it clicked: a long LED strip install behaves like a tiny distributed system. Power is your infrastructure. Data (if addressable) is your network link. Optics is the UI layer. The three failure modes you’ll actually see 1) Power (voltage drop) End of strip is visibly dimmer RGB “white” shifts yellow/pink toward the far end Effects look uneven at higher brightness 2) Data integrity (addressable strips) Random flicker / wrong colors on some pixels “Works on the bench, fails installed” Breaks after N pixels 3) Perception bugs Hotspots make the install look cheap Dimming feels jumpy at low levels Gradients band instead of fading smoothly What consistently works (and scales) Power first, layout second Design for worst case: full brightness / full white Leave headroom on the PSU (don’t run at the edge) Don’t rely on one power input for long runs—plan injection points early Wire gauge matters more than people expect (connectors too) Make the source invisible A diffuser channel is the fastest “DIY → architectural” upgrade If hotspots persist, increasing LED-to-diffuser distance often helps more than “better plastic” Treat data like a comms link Common ground is mandatory Keep the first data lead short Avoid routing data alongside high-current power runs Buffer/differential methods beat “hope and prayer” when distances grow A quick debugging model When something looks wrong, ask: Does it worsen toward the end? → power Random pixels/glitches? → data Looks mathematically smooth but visually harsh? → optics/gamma/perception 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 emmma Follow I am from China Location 中国 Pronouns led lover Joined Sep 10, 2025 More from emmma What I Wish I Knew Before My First LED Strip Install: Light Diffusion + Power Planning # beginners # design # hardware Battling Winter Darkness: How Better Lighting Saved My Productivity (No Ceiling Lights Allowed) # hardware # productivity # beginners 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Open Forem — A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Open Forem © 2016 - 2026. Where all the other conversations belong Log in Create account | 2026-01-13T08:49:47 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Faws-builders%2Fidentify-aws-network-services-3pba&title=Identify%20AWS%20Network%20Services&summary=%F0%9F%8C%90Exam%20Guide%3A%20Cloud%20Practitioner%20Domain%203%3A%20Cloud%20Technology%20%26amp%3B%20Services%20%F0%9F%93%98Task%20Statement%203.5%20%20%20%20%20%20%20...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (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)) | 2026-01-13T08:49:47 |
https://www.facebook.com/r.php?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fkowshikkumar_reddymakire%252Fbuilding-a-low-code-blockchain-deployment-platform-4ali%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag&locale=ko_KR&display=page&entry_point=login | Facebook에 가입하기 새 계정 만들기 빠르고 쉽게 가입할 수 있습니다. 브라우저에서 Javascript가 비활성화되었습니다. 브라우저에서 JavaScript를 활성화하거나 Javascript 이용이 가능한 브라우저로 업그레이드하신 후 Facebook에 가입하세요. 오류가 발생했습니다. 다시 시도하세요. 계정을 만들 수 없습니다 Facebook에 가입하지 못했습니다. 생일 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 1995 1994 1993 1992 1991 1990 1989 1988 1987 1986 1985 1984 1983 1982 1981 1980 1979 1978 1977 1976 1975 1974 1973 1972 1971 1970 1969 1968 1967 1966 1965 1964 1963 1962 1961 1960 1959 1958 1957 1956 1955 1954 1953 1952 1951 1950 1949 1948 1947 1946 1945 1944 1943 1942 1941 1940 1939 1938 1937 1936 1935 1934 1933 1932 1931 1930 1929 1928 1927 1926 1925 1924 1923 1922 1921 1920 1919 1918 1917 1916 1915 1914 1913 1912 1911 1910 1909 1908 1907 1906 1905 1월 2월 3월 4월 5월 6월 7월 8월 9월 10월 11월 12월 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 연령 생년월일 사용 성별 여성 남성 직접 지정 회원님을 지칭할 성별대명사를 선택하세요 여성(She): "생일을 축하해주세요!" 남성(He): "생일을 축하해주세요!" 성별무관(They): "생일을 축하해주세요!" 성별대명사는 모든 사람에게 공개됩니다. 저희 서비스를 이용하는 사람이 회원님의 연락처 정보를 Facebook에 업로드했을 수도 있습니다. 더 알아보기 . 가입하기 버튼을 클릭하면 Facebook의 약관 , 개인정보처리방침 및 쿠키 정책 에 동의하게 됩니다. Facebook으로부터 SMS 알림을 받을 수 있으며 알림은 언제든지 옵트 아웃할 수 있습니다. 가입하기 이미 계정이 있으신가요? 보안 확인 필수 입력 항목입니다. 이 내용이 표시되는 이유는? 보안 확인 자동가입방지 문자 입력은 스패머가 자동 요청을 보내는 것을 방지하기 위해 Meta에서 사용하는 표준 보안 테스트입니다. Facebook의 이름이 Meta로 변경됩니다. 저희는 2022년 1월 4일에 새 이름을 반영하여 이용 약관, 데이터 정책 및 쿠키 정책을 개정했습니다. 회사명이 바뀌더라도 Facebook 앱을 포함한 모든 동일한 제품이 Meta에서 지속적으로 제공됩니다. 기존의 데이터 정책 및 서비스 약관은 효력을 유지하며, 이번 이름 변경으로 인해 저희의 기존 데이터 사용 및 공유 방식이 변경되지는 않습니다. Meta 와 Meta의 메타버스 비전을 자세히 알아보세요. 데이터 정책 이 정책에서는 Facebook, Instagram, Messenger 및 Meta Platforms, Inc.가 제공하는 기타 제품 및 기능을 지원하기 위해 저희가 처리하는 정보를 설명합니다. ( Meta 제품 또는 제품). 추가적인 도구 및 정보는 Facebook 설정 및 Instagram 설정 에서 확인할 수 있습니다. I. 저희가 수집하는 정보의 유형 Meta 제품을 제공하기 위해 저희는 회원님에 대한 정보를 처리해야 합니다. 수집하는 정보의 유형은 회원님이 저희 제품을 이용하는 방법에 따라 다릅니다. Facebook 설정 및 Instagram 설정 에 접속하여 저희가 수집한 정보에 액세스하고 이를 삭제하는 방법에 대해 알아보실 수 있습니다. 회원님 및 다른 사람의 활동 및 제공하는 정보. 회원님이 제공하는 정보 및 콘텐츠. 저희는 회원님이 Meta 제품을 이용(계정 가입, 콘텐츠 작성 또는 공유, 다른 사람들과의 메시지 전송 또는 커뮤니케이션 포함)할 때 제공하는 콘텐츠, 커뮤니케이션 및 기타 정보를 수집합니다. 여기에는 사진 촬영 장소나 파일 생성 날짜와 같이 회원님이 제공한 콘텐츠에 포함되거나 관련된 정보(메타데이터 등)가 포함될 수 있습니다. 또한 여기에는 카메라 와 같이 저희가 제공하는 기능을 통해 표시되는 내용도 포함되므로, 회원님이 좋아할 만한 마스크와 필터를 제안하거나, 카메라 형식 사용에 관한 팁을 제공할 수도 있습니다. Meta 시스템은 아래 에 명시된 목적을 위해 회원님과 다른 사람들이 제공한 콘텐츠 및 커뮤니케이션을 자동으로 처리하여, 배경과 그 내용을 분석합니다. 회원님이 공유 한 항목을 볼 수 있는 사람을 관리하는 방법에 대해 자세히 알아보세요. 특별 보호를 받는 정보: Facebook 프로필 필드 또는 중요 이벤트에 회원님의 종교관, 정치관, '관심 있는' 사람 또는 건강 정보를 제공하도록 선택할 수 있습니다. 이러한 정보 및 기타 정보(예를 들어 인종 또는 민족적 태생, 철학적 신념 또는 노동조합 가입 여부)는 회원님의 해당 국가 법률에 따라 특별 보호를 받을 수 있습니다. 네트워크 및 연결. 저희는 회원님과 연결된 사람, 계정, 해시태그 , Facebook 그룹 및 페이지 (예를 들어 저희 제품에서 회원님이 가장 많이 연락하는 사람이나 회원님이 속한 그룹)에 대한 정보 및 이들과 연락하는 방식에 대한 정보를 수집합니다. 또한 회원님이 연락처 정보(예를 들어 주소록, 통화 로그 또는 SMS 로그 기록)를 기기에서 업로드, 동기화 또는 가져오기로 선택 하는 경우 해당 연락처 정보를 수집합니다. 이 연락처 정보는 회원님 및 다른 사람들이 알 수도 있는 사람들을 찾도록 돕고 아래 에 나열된 기타 목적을 위해 이용됩니다. 회원님의 이용. 저희는 회원님이 보거나 참여하는 콘텐츠의 유형, 사용하는 기능, 수행하는 행동, 교류하는 사람 또는 계정, 활동 시간, 빈도 및 기간 등 회원님이 Meta 제품을 이용하는 방법에 대한 정보를 수집합니다. 예를 들어 저희는 회원님이 Meta 제품을 이용한 시간, 마지막으로 이용한 시간, Meta 제품에서 확인한 게시물, 동영상 및 기타 콘텐츠를 기록합니다. 또한 저희는 회원님이 카메라와 같은 기능들을 사용하는 방법에 대한 정보도 수집합니다. Meta 제품에서 이뤄진 거래에 관한 정보. 회원님이 구매 또는 기타 금융 거래를 위해 Meta 제품을 이용하는 경우(예를 들어 게임 내에서 구매하거나 기부 하는 경우) 저희는 구매 또는 거래에 관한 정보를 수집합니다. 여기에는 신용카드 또는 직불카드 번호 및 기타 카드 정보, 기타 계정 및 인증 정보, 청구, 배송 및 연락처와 같은 결제 정보가 포함됩니다. 다른 사람의 활동 및 다른 사람이 회원님에 관해 제공한 정보. 또한 저희는 다른 사람이 Meta 제품을 이용할 때 그들이 제공하는 콘텐츠, 커뮤니케이션 및 정보를 수집하고 분석합니다. 여기에는 다른 사람이 언제 회원님의 사진을 공유하거나 회원님의 사진에 댓글을 남기는지, 언제 회원님에게 메시지를 보내는지, 언제 회원님의 연락처 정보를 업로드, 동기화 또는 가져오는지 등과 같은 회원님에 관한 정보가 포함될 수 있습니다. 기기 정보 아래에 설명된 바와 같이, 저희는 회원님이 사용하여 Facebook 제품과 통합되는 컴퓨터, 전화, 스마트 TV 및 기타 웹 연결 기기로부터, 그리고 해당 기기에 관한 정보를 수집하고, 회원님이 사용하는 여러 기기에 이 정보를 결합합니다. 예를 들어 저희는 회원님의 휴대폰에서 Facebook 제품 이용에 관해 수집한 정보를 이용하여, 회원님이 노트북이나 태블릿과 같은 다른 기기에서 Facebook 제품을 이용할 때 보게 되는 콘텐츠( 광고 포함) 또는 기능을 회원님에게 맞춤화하거나, 다른 기기에서 회원님의 휴대폰에 표시된 광고에 대한 회원님의 반응 여부를 측정합니다. 이러한 기기로부터 얻는 정보는 다음과 같습니다. 기기 속성: 운영 체제, 하드웨어 및 소프트웨어 버전, 배터리 잔량, 신호 강도, 사용 가능한 저장 공간, 브라우저 유형, 앱 및 파일 이름 및 유형, 플러그인 등의 정보. 기기 작업: 창이 전면 또는 백그라운드에 있는지 여부, 마우스 움직임(인간과 봇을 구분하는 데 도움이 될 수 있음) 등 기기에서 수행되는 작업 및 동작에 관한 정보. 식별자: 고유 식별자, 기기 ID 및 기타 식별자. 기타 식별자의 예로는 회원님이 이용하는 게임, 앱 또는 계정 등의 식별자 및 가족 기기 ID(또는 동일한 기기나 계정과 관련된 Meta Company 제품 에 고유한 기타 식별자)가 있습니다. 기기 신호: Bluetooth 신호 및 근처 Wi-Fi 액세스 포인트, 비콘 및 셀 타워에 관한 정보. 기기 설정 데이터: GPS 위치, 카메라 또는 사진에 대한 액세스 등 회원님의 기기 설정을 활성화하여 Meta가 수신할 수 있도록 허가한 정보. 네트워크 및 연결: 이동통신사 또는 ISP 명칭, 언어, 시간대, 휴대폰 번호, IP 주소, 연결 속도 및 때로는 가까이 있거나 회원님의 네트워크에 있는 다른 기기에 관한 정보. 이를 통해 Meta는 휴대폰에서 TV로 동영상을 스트리밍 하는 등의 작업을 지원할 수 있습니다. 쿠키 데이터: 쿠키 ID 및 설정을 포함하여 기기에 저장된 쿠키 데이터. 쿠키 사용에 관한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 에서 알아보세요. 파트너가 제공하는 정보. 광고주, 앱 개발자 및 퍼블리셔는 이들이 사용하는 Meta 비즈니스 도구 , 즉 저희의 소셜 플러그인(예: '좋아요' 버튼), Facebook 로그인, 저희 API와 SDK 또는 Meta 픽셀 을 통해 저희로 정보를 제공할 수 있습니다. 이 파트너들은 회원님의 저희 계정 보유 여부 또는 저희 제품 로그인 여부와 관계없이 Meta 제품 밖에서의 회원님의 활동에 대한 정보(회원님의 기기, 회원님이 방문한 웹사이트, 회원님의 구매 내역, 회원님에게 표시되는 광고 및 회원님이 해당 파트너들의 서비스를 사용한 방법에 관한 정보 포함)를 제공합니다. 예를 들어, 게임 개발자는 저희 API를 사용하여 저희에게 회원님이 플레이하는 게임에 대해 알려줄 수 있고, 비즈니스는 회원님이 해당 비즈니스의 스토어에서 구매한 제품에 대해 알려줄 수 있습니다. 또한 저희는 회원님의 정보를 저희에게 제공할 권리가 있는 제3자 데이터 제공업체로부터 회원님의 온라인 및 오프라인 활동과 구매에 관한 정보를 받습니다. 회원님이 파트너를 방문하거나 파트너 서비스를 이용할 때 또는 파트너와 제휴한 제3자를 통해 서비스를 이용할 때 회원님의 데이터를 파트너가 받게 됩니다. 저희는 각 파트너에게 회원님의 데이터를 수집하고, 사용하고, 공유할 수 있는 합법적 권한을 획득한 후에 저희에게 데이터를 제공할 것을 요구합니다. 저희에게 데이터를 제공하는 파트너의 유형에 대해 자세히 알아보세요 . Meta 비즈니스 도구와 관련하여 저희의 쿠키 사용에 대한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 을 참조하시기 바랍니다. II. 저희가 정보를 활용하는 방법 저희는 (회원님이 동의할 경우) 아래에 설명된 바와 같이 보유한 정보를 이용하며, Meta 약관 및 Instagram 약관 에 설명된 Meta 제품 및 관련 서비스를 제공하고 지원합니다. 방법은 다음과 같습니다. Facebook 제품의 제공, 맞춤화 및 개선. 저희는 Meta 제품을 제공하기 위해 보유한 정보를 이용합니다. Meta 제품을 제공하는 데는 기능 및 콘텐츠(귀사 광고, Facebook 뉴스피드 , Instagram 피드 및 Instagram 스토리 포함)를 맞춤화하고 Meta 제품 안팎에서 회원님이 관심을 가질 만한 그룹 또는 이벤트 나 팔로우할 만한 주제 등을 추천하는 것이 포함됩니다. 회원님을 위해 특별하고 관련성 있는 맞춤화된 Meta 제품을 만들기 위해, 저희는 수집한 데이터와 회원님 및 다른 사람으로부터 얻은 정보(회원님이 제공하기로 선택한 특별 보호 데이터 포함)에 기초한 회원님의 관계, 기호, 관심사 및 활동, 회원님이 Meta 제품을 이용하고 상호 작용하는 방법, Meta 제품 안팎에서 회원님과 연결되어 있거나 회원님이 관심 있는 사람, 장소 또는 사물에 관한 정보를 이용합니다. Meta 제품의 기능, 콘텐츠, 추천을 포함하여 Facebook과 Instagram에서 개인에게 맞춤화된 경험을 제공하기 위해 저희가 회원님에 관한 정보를 어떻게 사용하는지 자세히 알아보세요. 또한 회원님에게 표시되는 광고 를 선택하는 방법도 자세히 알아볼 수 있습니다. Meta 제품 및 기기의 정보: 저희는 여러 Meta 제품 및 기기 활동에 관한 정보를 연결하여 회원님이 사용하는 모든 Meta 제품에 대해, 어디서 해당 제품을 이용하는지에 관계없이 더욱 맞춤화되고 일관된 경험을 제공합니다. 예를 들어 Instagram에서 회원님이 팔로우하거나 Messenger로 커뮤니케이션하는 사람들이 속한 Facebook 그룹에 가입할 것을 추천할 수 있습니다. 또한 예를 들어 다른 Meta 제품의 계정에 가입할 때 기존 Meta 제품의 등록 정보(전화번호 등)를 자동으로 기입하는 등 회원님에게 더욱 원활한 경험을 제공할 수도 있습니다. 위치 관련 정보: 저희는 회원님 및 다른 사람들에게 광고를 포함한 Meta 제품을 제공하고, 맞춤화하고, 개선하기 위해 위치 관련 정보 (예: 회원님의 현재 위치, 거주 지역, 가고 싶은 장소, 주변에 있는 비즈니스 및 사람)를 이용합니다. 위치 관련 정보는 정확한 기기 위치(수집을 허용한 경우), IP 주소 및 회원님 및 다른 사람이 Meta 제품을 이용하여 발생하는 정보(예를 들어 체크인 또는 참석 이벤트)와 같은 사항을 기반으로 할 수 있습니다. 제품 연구 및 개발: 저희는 보유한 정보를 이용하여 설문조사 및 리서치를 수행하고 새로운 제품과 기능을 테스트하며 문제를 해결함으로써 Meta 제품을 개발, 테스트 및 개선합니다. 광고 및 기타 홍보 콘텐츠: 저희는 보유한 정보(회원님의 관심사, 행동 및 관계에 관한 정보를 포함)를 이용하여 광고, 쿠폰 및 회원님에게 표시되는 기타 홍보 콘텐츠를 선택하고 맞춤화합니다. 저희가 광고를 선택하고 맞춤화하는 방법 , 광고 및 기타 홍보 콘텐츠를 선택하기 위해 사용한 데이터에 관한 회원님의 선택 사항을 Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 측정, 분석 및 기타 비즈니스 서비스 제공. 저희는 보유한 정보(방문한 웹사이트 및 광고 등 Facebook 제품 밖에서의 활동 포함)를 이용하여 광고주 및 기타 파트너가 광고 및 서비스의 성과와 배포를 측정하고 해당 서비스를 사용하는 사람들의 유형 및 사람들이 웹사이트, 앱, 서비스와 상호 작용하는 방식을 파악할 수 있도록 지원합니다. 이러한 파트너와 정보를 공유하는 방법에 대해 알아보세요 . 안전, 진실성 및 보안 강화. 저희는 보유한 정보를 이용하여 계정 및 활동을 확인하고, 유해 행위를 방지하며, 스팸 및 기타 부정적인 경험을 감지 및 방지하고, 제품의 무결성을 유지하며, Meta 제품 안팎의 안전 및 보안을 강화합니다. 예를 들어 저희는 보유한 데이터를 이용하여 의심스러운 활동 또는 저희 약관이나 정책 위반을 조사하거나 누군가에게 도움이 필요한 시점을 감지 합니다. 자세히 알아보려면 Facebook 보안 고객 센터 및 Instagram 보안 팁 을 방문하세요. 회원님과의 커뮤니케이션. 저희는 보유한 데이터를 이용하여 회원님에게 마케팅 자료를 제공하고 Facebook 제품에 관해 커뮤니케이션하며, Facebook 정책 및 약관에 대한 내용을 알려 드립니다. 또한 저희는 회원님의 정보를 이용하여 회원님의 연락에 대응합니다. 사회적 공익 연구 및 혁신. 저희는 보유한 정보(저희와 협업하는 연구 파트너의 정보 포함)를 이용하여 일반 사회 복지, 기술 발전, 공익, 보건 및 복지에 관한 주제의 연구 와 혁신을 진행하며, 이를 지원합니다. 예를 들어, 위기 상황 시 저희가 보유한 이동 패턴 정보를 분석하여 구호 활동을 지원합니다. Facebook 연구 프로그램에 대해 자세히 알아보세요 . III. 정보 공유 방법 회원님의 정보는 다음 방법으로 다른 사람들과 공유됩니다. Meta 제품에서 공유 회원님이 공유하고 커뮤니케이션하는 사람 및 계정 회원님은 Facebook 제품을 이용하여 공유 또는 커뮤니케이션할 때 공유할 내용에 대한 공개 대상을 선택 합니다. 예를 들어 회원님은 Facebook에 게시물을 포스팅할 때 그룹, 모든 친구, 전체 공개 또는 맞춤 설정한 리스트에 있는 사람 등 게시물에 대한 공개 대상을 선택합니다. 마찬가지로, 회원님이 Messenger 또는 Instagram을 사용하여 사람 또는 비즈니스와 커뮤니케이션할 때 해당 사람 및 비즈니스는 회원님이 전송하는 콘텐츠를 볼 수 있습니다. 회원님의 네트워크는 회원님이 Meta 제품에서 취한 행동(광고 및 홍보 콘텐츠 참여 포함)을 볼 수도 있습니다. 또한 저희는 다른 계정이 해당 계정의 Facebook 또는 Instagram 스토리를 누가 조회했는지 볼 수 있도록 허용합니다. 공개 정보 는 계정이 없는 경우를 포함하여 Facebook 제품 안팎에서 누구든지 볼 수 있습니다. 여기에는 Instagram 사용자 이름, 공개 대상과 공유하는 모든 정보, 회원님 Facebook 공개 프로필 에 있는 정보, Facebook 페이지에서 공유하는 콘텐츠, Instagram 공개 계정 또는 Facebook Marketplace 와 같은 기타 공개 포럼에서 공유하는 콘텐츠가 포함됩니다. 회원님, Facebook과 Instagram을 사용하는 다른 사람들 그리고 저희는 검색 결과 또는 도구 및 API를 통해 Meta 제품(Meta Company 제품 포함) 안팎에 있는 모든 사람에게 공개 정보에 대한 액세스 권한을 제공하거나 해당 공개 정보를 전송할 수 있습니다. 공개 정보는 검색 엔진, API 같은 제3자 서비스, TV 같은 오프라인 매체와 앱, 웹사이트, 저희 제품과 통합된 기타 서비스를 통해 보거나 액세스하거나 다시 공유하거나 다운로드할 수도 있습니다. 공개 정보 및 Facebook 과 Instagram 에서 공개 범위를 설정하는 방법에 대해 자세히 알아보세요. 다른 사람이 회원님과 공유하거나 다시 공유한 콘텐츠 Meta 제품에서 회원님의 활동을 볼 수 있는 사람들은 Meta 제품 안팎에서 다른 사람들(회원님이 공유한 공개 대상 이외의 사람들과 비즈니스 포함)과 이를 공유할지 여부를 선택할 수 있으므로, 회원님은 공유 대상을 선택할 때 이를 고려해야 합니다. 예를 들어 특정 친구 또는 계정에 게시물을 공유하거나 메시지를 전송할 때, 해당 친구 또는 계정은 직접 또는 Horizon 월드 같은 가상 현실 환경에서 콘텐츠를 다운로드하거나 스크린샷으로 캡처하거나 Meta 제품 안팎으로 다른 사람과 다시 공유할 수 있습니다. 또한 다른 사람의 게시물에 댓글을 달거나 공감할 때, 그 사람의 콘텐츠를 볼 수 있는 사람은 회원님의 댓글이나 공감 상태를 볼 수 있고 해당 콘텐츠를 게시한 사람은 나중에 공개 대상을 변경할 수 있습니다. 사람들은 Facebook 제품을 이용하여 회원님에 관한 콘텐츠를 만들고 원하는 공개 대상과 공유할 수도 있습니다. 예를 들어 스토리에 회원님의 사진을 공유하고, 게시물에 회원님의 위치를 언급하거나 태그하고, 게시물 또는 메시지에 회원님에 대한 정보를 공유할 수 있습니다. 다른 사람들이 Facebook 제품에서 회원님에 대해 공유한 내용에 불편함을 느낀다면 콘텐츠를 신고 하는 방법을 알아보실 수 있습니다. Meta 제품에서 회원님의 활동 상태 또는 존재에 관한 정보. 회원님의 네트워크에 있는 사람들은 Facebook 제품에 대한 회원님의 활동 여부( Instagram , Messenger 또는 Facebook에서 활동 상태인지, 언제 마지막으로 Facebook 제품을 이용하였는지 포함)를 알려주는 신호를 볼 수 있습니다. Meta 제품에 포함되어 있거나 서비스를 이용한 앱, 웹사이트 및 제3자 통합. Meta 제품을 이용하거나 Meta 제품에 통합된 타사 앱, 웹사이트 또는 기타 서비스를 이용할 경우 해당 타사에서 회원님이 게시하거나 공유한 내용에 관한 정보를 받을 수 있습니다. 예를 들어 Facebook 친구와 게임을 하거나 웹사이트에서 Facebook 댓글 달기 또는 공유하기 버튼을 사용하는 경우, 게임 개발자 또는 웹사이트는 게임 내 회원님의 활동에 대한 정보를 받거나 회원님이 Facebook에서 해당 웹사이트를 통해 공유한 댓글이나 링크에 관한 정보를 받을 수 있습니다. 또한 이러한 제3자 서비스를 다운로드하거나 사용할 때 해당 제3자는 Facebook의 공개 프로필 및 회원님이 해당 제3자에 공유한 모든 정보에 액세스할 수 있습니다. 회원님이 공유를 선택할 경우 회원님이 이용하는 앱과 웹사이트에서 Facebook 친구 리스트를 수신할 수 있습니다. 단, 회원님이 이용하는 앱과 웹사이트는 회원님의 Facebook 친구에 관한 기타 모든 정보 또는 회원님의 Instagram 팔로워에 관한 정보를 수신할 수 없습니다. 이는 회원님의 친구와 팔로워가 이 정보를 공유하도록 선택했더라도 마찬가지입니다. 이러한 제3자 서비스에서 수집되는 정보는 Facebook 약관 및 정책이 아닌 해당 제3자의 자체 약관 및 정책의 적용을 받습니다. Facebook 및 Instagram의 기본 버전을 제공하는 기기와 운영 체제(즉, 저희가 저희 자체의 앱을 개발하지 않은 기기와 운영 체제)는 저희 핵심 기능을 회원님에게 제공하기 위해 회원님의 친구가 회원님과 공유하는 정보를 포함하여 회원님이 공유하기로 선택하는 모든 정보에 액세스할 수 있습니다. 참고: 저희는 현재 남용을 방지하기 위해 개발자의 데이터 액세스 권한을 추가로 제한하고 있습니다. 예를 들어, 저희는 회원님이 3개월 동안 앱을 사용하지 않았고, 저희가 로그인을 변경하는 경우 회원님의 Facebook 및 Instagram에 대한 개발자의 액세스 권한을 삭제하며, 다음 버전에서 앱 검수 없이 앱에서 요청할 수 있는 데이터를 이름, Instagram 사용자 이름, 소개, 프로필 사진, 이메일 주소만 포함되도록 축소합니다. 더 많은 데이터를 요청하려면 저희의 허가를 받아야만 합니다. 새로운 소유자. Facebook 제품 또는 해당 자산의 전부 또는 일부에 대한 소유권 또는 운영권이 변경되는 경우, 저희는 회원님에 대한 정보를 새로운 소유주에게 제공할 수 있습니다. 제3자 파트너와 공유 저희는 Meta를 지원하고 Meta 제품을 제공하고 개선하는 데 도움을 주거나 Meta 비즈니스 도구를 사용하는 제3자 파트너와 협력하여 이들의 비즈니스를 성장시킴으로써 회사를 운영하고 전 세계 사람들에게 무료 서비스를 제공하고 있습니다. 저희는 회원님의 정보를 누구에게도 판매하지 않으며 앞으로도 판매하지 않을 것입니다. 저희는 또한 파트너가 저희가 제공한 데이터를 이용하고 공개하는 방법에 엄격한 제한을 가하고 있습니다. 저희가 정보를 공유하는 제3자의 유형은 다음과 같습니다. Meta 분석 서비스를 사용하는 파트너. 저희는 개인 및 비즈니스가 사람들이 Meta 제품 안팎의 게시물, 리스트, Facebook 페이지, 동영상 및 기타 콘텐츠에 참여하는 방식을 파악하는 데 참고할 수 있는 취합된 통계 및 인사이트를 제공합니다. 예를 들어 Facebook 페이지 관리자 및 Instagram 비즈니스 프로필은 게시물을 보거나, 게시물에 반응하거나, 댓글을 단 사람의 수에 관한 정보 외에도 취합된 인구 통계학적 특성 및 기타 계정 또는 Facebook 페이지와의 상호 작용을 파악하는 데 도움이 되는 정보를 받습니다. 광고주. 저희는 광고주에게 광고를 보는 사람들의 유형 및 광고 실적에 관한 보고서를 제공하지만 회원님을 개인적으로 식별하는 정보(회원님에게 연락하거나 식별하는 데 이용될 수 있는 이름 또는 이메일 주소 같은 정보)는 회원님이 허용하지 않는 한 공유하지 않습니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성에게 해당 광고가 노출됨)를 제공합니다. 또한 어떠한 광고가 회원님의 구매나 광고주에 관한 행동을 하게 유도했는지 확인합니다. 측정 파트너. 저희는 회원님에 대한 정보를 수집하여 파트너에게 분석 및 측정 보고서를 제공하는 회사와 정보를 공유합니다. Meta 제품 안에서 상품 및 서비스를 제공하는 파트너. 회원님이 프리미엄 콘텐츠를 구독하거나 Facebook 제품 내 판매자로부터 상품을 구매하는 경우, 해당 콘텐츠 제작자 또는 판매자는 회원님이 공유하는 공개 정보 및 기타 정보 외에도 배송 및 연락처 세부 정보를 포함하여 거래를 완료하는 데 필요한 정보를 받을 수 있습니다. 벤더 및 서비스 공급자. 저희는 기술 인프라 서비스 제공, Facebook 제품 이용 방법 분석, 고객 서비스 제공, 결제 간소화 또는 설문 수행 등의 방법을 통해 Facebook 비즈니스를 지원하는 벤더 및 서비스 공급자에게 정보와 콘텐츠를 제공합니다. 연구원 및 학자. 또한 저희는 연구 파트너 및 학자 에게 정보와 콘텐츠를 제공하여, 그들이 Facebook의 비즈니스 또는 사명을 지원하는 학문과 혁신을 발전시키는 연구, 그리고 일반적인 사회 복지, 기술 발전, 공익, 건강 및 복지에 대한 발견 및 혁신을 향상시키는 연구를 수행할 수 있도록 합니다. 사법당국 또는 법적 요청. 저희는 아래에 명시된 상황에서 사법당국 또는 법적 요청에 대응하여 정보를 공유합니다. Facebook 설정 및 Instagram 설정 에서 회원님 또는 다른 사람이 제3자 파트너와 공유하는 정보를 설정하는 방법에 대해 자세히 알아보세요. IV. Meta Companies가 협력하는 방식 Facebook과 Instagram은 회원님이 사용하는 모든 Meta Company 제품 에서 혁신적이고 관련성이 있으며 일관적이고 안전한 환경을 제공하기 위해 Meta Companies (WhatsApp 및 Oculus 포함)와 인프라, 시스템 및 기술을 공유합니다. 또한 저희는 이러한 목적을 위해, 관련 법에서 허용하는 경우에 Meta Companies의 약관 및 정책에 따라 Meta Companies에서 회원님에 대한 정보를 처리합니다. 예를 들어 저희는 WhatsApp의 서비스에서 스팸을 보내는 계정에 대한 정보를 처리하여 Facebook, Instagram 또는 Messenger에서 해당 계정에 대해 적절한 조치를 취할 수 있습니다. 또한 저희는 다른 Meta Company 제품의 고유 사용자 수를 파악하는 등 사람들이 Meta Company 제품을 이용하고 상호 작용하는 방법을 파악하기 위해 노력하고 있습니다. V. 회원님의 정보를 관리 또는 삭제하는 방법 저희는 데이터 액세스, 수정, 복사 및 삭제 기능을 제공합니다. Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 저희는 더 이상 Meta 서비스 및 Meta 제품을 제공할 필요가 없는 시점, 그리고 회원님의 계정이 삭제되는 시점 중 먼저 도달하는 시점까지만 데이터를 저장합니다. 이는 데이터의 성격, 수집 및 처리된 이유, 관련된 법적 또는 운영상 보존 필요성과 같은 요인에 따라 개별적으로 결정됩니다. 예를 들어 회원님이 Facebook에서 무언가를 검색할 때 언제든지 검색 기록에서 해당 검색어에 액세스하고 삭제할 수 있지만, 해당 검색어에 대한 로그는 6개월 후에 삭제됩니다. 회원님이 계정 확인을 위해 정부가 발행한 신분증명서 사본을 제출하는 경우 저희는 달리 명시하지 않는 한 검토 후 30일 이내에 해당 사본을 삭제합니다. 공유된 콘텐츠 및 소셜 플러그인을 통해 얻은 쿠키 데이터 삭제 에 대해 자세히 알아보세요. 계정을 삭제하면 회원님의 사진이나 상태 업데이트 등 회원님이 게시한 사항들이 삭제 되며 나중에 해당 정보를 복원할 수 없습니다. 다른 사람이 회원님에 대해 공유한 정보는 회원님의 계정에 포함되지 않으며 삭제되지 않습니다. 계정을 삭제하지 않고 제품 이용을 일시적으로 중단하려면 계정을 비활성화할 수 있습니다. 회원님의 계정을 삭제하려면 언제든지 Facebook 설정 및 Instagram 설정 을 방문하세요. VI. 법적 요청에 대한 대응과 피해 방지 Meta는 회원님의 정보에 액세스하고 이를 보존하며 규제 당국, 사법당국 또는 다른 사람들과 이 정보를 공유합니다. 법적인 요청(예: 수색 영장, 법원 명령서, 소환장 등)이 수반되고 법의 집행을 위해 필요하다고 판단될 경우. 여기에는 미국 외 지역 관할권에서의 법적 요청이 수반되고, 해당 관할권의 법에 의해 필요성이 인정되며, 그 지역 내의 사용자들에게 영향을 미침과 동시에 국제적으로 용인되는 기준에 부합한다고 판단될 때 해당 관할권의 요청을 받아들이는 경우가 포함됩니다. Meta가 필요성을 인정할 경우 사기, 제품의 권한 없는 사용, 약관 또는 정책 위반, 또는 기타 유해하거나 불법적인 활동을 감지 및 예방하고 이에 대처하는 조치, 조사 또는 규제 요구를 포함하여 Meta(권리, 자산 또는 제품), 회원님 또는 다른 사람을 보호하기 위한 조치, 생명을 보호하고 상해를 막기 위한 조치가 필요합니다. 예를 들어 관련성이 있는 경우 저희는 제품의 사기, 남용 및 기타 유해한 활동을 방지하기 위해 계정의 신뢰성에 대한 정보를 제3자 파트너와 주고받습니다. 저희 제품을 이용한 구매 활동과 관련된 금융 거래 데이터를 포함해 저희가 수집하는 회원님의 정보는 법적인 요청이나 의무, 정부 조사, 저희의 약관과 정책에 대한 잠재적 위반에 대한 조사의 대상이 되는 경우 또는 다른 피해를 방지하기 위한 목적으로 장기간 액세스 및 보관될 수 있습니다. 또한 약관 악용 사례 또는 기타 약관에 대한 위반 행위의 반복을 막기 위해 약관 위반으로 비활성화된 계정의 정보를 최소 1년 이상 보존합니다. VII. 글로벌 서비스의 일환으로 데이터를 운영하고 이전하는 방법 저희는 본 개인정보처리방침에 따라 전 세계적으로 정보를 공유하는바, Meta Companies 내부적으로 정보를 공유하고, 외부적으로 저희의 파트너, 그리고 회원님이 연결하고 공유하는 대상과도 정보를 공유합니다. 예를 들어 회원님의 정보는 본 정책에 설명된 목적을 위해 미국 또는 회원님이 거주하는 지역 이외의 기타 국가로 이전 또는 전송되거나 이들 국가에서 저장 및 처리될 수 있습니다. 이러한 데이터 이전은 Meta 약관 및 Instagram 약관 에 명시된 서비스를 제공하고 저희 제품을 전 세계적으로 운영하며 회원님에게 제공하기 위해 필요합니다. 저희는 표준 계약 조항 을 활용하고, 해당할 경우 특정 국가에 대한 유럽연합 집행위원회의 적정성 결정 을 따르며, 미국 및 기타 국가로의 데이터 이전에 대해 회원님의 동의를 받습니다. VIII. 개인정보처리방침 변경 사항에 대한 안내 저희는 본 정책을 변경하기 전에 회원님에게 알리고, 회원님이 Facebook 제품 이용을 계속하기 전에 회원님에게 변경된 정책을 검토할 기회를 제공할 것입니다. 대한민국 개인정보 보호 고지사항 저희의 대한민국 개인정보 보호 고지사항 을 확인하여 회원님이 행사할 수 있는 개인정보 보호 권리, 저희가 회원님의 정보를 공유하는 제3자에 관한 상세 정보 및 기타 사항에 대해 자세히 알아보세요. IX. Meta에 문의하는 방법 Facebook 또는 Instagram 의 개인정보처리방침을 자세히 알아보세요. 본 정책에 관해 궁금하신 점이 있으면 아래에 설명된 바와 같이 Meta에 문의하실 수 있습니다. Meta Platforms, Inc.는 대한민국 사용자의 개인정보 관련 고충에 관한 문의를 위해 Privacy Agent Korea Co., Ltd.를 국내 대리인으로 지정하였습니다. 국내대리인에게 온라인 , 전화나 우편 또는 이메일로 문의하실 수 있습니다. Privacy Agent Korea Co., Ltd. ATTN: 대표이사 박천희 서울특별시 종로구 새문안로5가길 28 전화: 02-737-0455 저희는 Meta 개인정보처리방침 및 업무 방식에 관하여 회원님과 분쟁이 있을 경우 TrustArc를 통해 해결할 수 있습니다. 이에 관하여는 TrustArc의 웹사이트 를 통해 TrustArc에 문의하세요. 다음과 같은 방법으로 문의할 수 있습니다. 온라인 또는 우편 문의: Meta Platforms, Inc. ATTN: Privacy Operations 1601 Willow Road Menlo Park, CA 94025 최종 수정일: 2022년 1월 4일 Facebook의 데이터 정책에 동의합니다 서비스 약관 Meta 서비스 약관이 개정됩니다. 이 개정 사항은 2025년 1월 1일부터 적용됩니다. 새로운 약관을 읽어보세요 . Meta는 사람들이 서로 교류하고 커뮤니티를 만들며 비즈니스를 성장시킬 수 있는 기술과 서비스를 개발합니다. (본 약관이 아닌) 별도의 약관이 적용된다고 명시되어 있지 않은 한, 본 약관은 회원님의 Facebook, Messenger 및 기타 저희가 제공하는 제품, 기능, 앱, 서비스, 기술, 소프트웨어( Meta 제품 또는 제품 ) 이용에 적용됩니다. 해당 제품은 Meta Platforms, Inc.가 회원님에게 제공합니다. 달리 명시된 경우를 제외하고 저희는 회원님에게 Facebook 또는 기타 본 약관이 적용되는 제품 및 서비스의 사용료를 청구하지 않습니다. 그 대신, 비즈니스와 단체 및 다른 사람이 저희에게 그들의 제품 및 서비스 광고를 회원님에게 보여드리도록 비용을 지불합니다. 저희 제품을 이용함으로써 회원님은 저희가 회원님 및 회원님의 관심사와 관련 있을 수 있다고 생각하는 광고를 보여주는 것에 동의하게 됩니다. 저희는 회원님의 개인정보를 이용하여 회원님에게 보여드릴 맞춤형 광고를 결정합니다. 저희는 회원님의 개인정보를 광고주에게 판매하지 않으며, 회원님이 저희에게 특정 허락을 제공하지 않는 한 회원님을 직접 식별할 수 있는 정보(예를 들어 이름, 이메일 주소 또는 기타 연락처 정보)를 광고주에게 공유하지 않습니다. 대신 광고주는 광고를 노출하기를 원하는 타겟과 같은 정보를 저희에게 알려줄 수 있고, 저희는 관심이 있을 만한 사람에게 해당 광고를 노출합니다. 저희는 사람들이 광고주의 콘텐츠와 어떻게 상호작용하고 있는지를 이해할 수 있도록 광고주에게 광고 성과 보고서를 제공합니다. 본 약관에 따라 맞춤형 광고가 Meta 제품에서 작동하는 방식에 대해 더 알아보려면 아래 제2조를 참조하세요. 저희의 개인정보처리방침 에는 저희가 회원님에게 보여드릴 광고를 결정하고 아래 설명된 기타 모든 서비스를 제공하기 위해 회원님의 개인정보를 어떻게 수집하고 이용하는지가 설명되어 있습니다. 회원님은 또한 관련 Meta 제품의 설정 페이지에서 저희가 회원님의 데이터를 이용하는 방식에 관해 회원님이 선택할 수 있는 개인정보 설정을 언제든지 검토할 수 있습니다. 1. 저희가 제공하는 서비스 저희의 사명은 사람들이 커뮤니티를 이룰 수 있도록 하여 전 세계를 더욱 가까워지게 만드는 것입니다. 저희는 이를 실현하기 위해 회원님에게 아래에 설명된 제품과 서비스를 제공합니다: 맞춤화된 경험을 제공합니다. Facebook 뉴스피드나 저희의 동영상 플랫폼에 표시되는 게시물, 스토리, 이벤트, 광고 및 기타 콘텐츠부터 회원님이 팔로우하는 Facebook 페이지 및 회원님이 이용할 만한 기타 기능(예: Facebook Marketplace, 검색)에 이르기까지 회원님만을 위한 Facebook을 경험하실 수 있습니다. 예를 들어 회원님이 만드는 관계, 회원님이 선택하는 옵션 및 설정 사항, 회원님이 제품 내외에서 공유하고 활동하는 사항과 같은 데이터를 이용하여 회원님의 경험을 맞춤화합니다. 회원님을 회원님에게 중요한 사람 및 단체와 연결합니다. 저희는 회원님이 이용하는 여러 Meta 제품에서 회원님에게 중요한 사람, 그룹, 비즈니스, 단체 및 다양한 다른 사항들을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님과 다른 사람들에게 제안(예: 가입할 그룹, 참석할 이벤트, 팔로우하거나 메시지를 보낼 Facebook 페이지, 시청할 프로그램 및 친구를 맺고 싶을 만한 사람 제안)하기 위해 데이터를 이용합니다. 더 친밀한 관계는 더 나은 커뮤니티를 만듭니다. 저희는 사람들이 본인이 관심 있는 사람, 그룹 및 단체와 연결될 때 저희 서비스가 가장 가치 있다고 믿습니다. 회원님이 자신을 표현하고 회원님이 중요하게 생각하는 것을 나눌 수 있도록 합니다. Facebook에서 회원님이 자신을 표현하고, 중요하게 생각하는 것을 친구와 가족, 다른 사람들과 나누는 방법에는 여러 가지(예: 여러 Meta 제품에서 회원님의 설정에 따라 상태 업데이트, 사진, 동영상 및 스토리 공유, 친구 또는 여러 사람에게 메시지 전송, 음성 또는 영상 통화 걸기, 이벤트 또는 그룹 생성, 프로필에 콘텐츠 추가, 다른 사람이 회원님의 콘텐츠에 참여하는 방식에 관한 인사이트 표시)가 있습니다. 또한 저희는 사람들이 증강 현실 및 360도 동영상과 같은 기술을 이용하여 Meta 제품에서 더욱 풍부하고 흥미로운 콘텐츠를 만들고 공유할 수 있도록 새로운 방법들을 개발해 왔고 또 계속해서 개발하고 있습니다. 회원님이 관심을 가질 만한 콘텐츠, 제품 및 서비스를 찾을 수 있도록 지원합니다. 저희는 Facebook 및 기타 Meta 제품을 이용 중인 많은 비즈니스와 단체가 제공하는 콘텐츠, 제품 및 서비스를 발견하는 데 도움이 되는 맞춤형 광고, 제안 및 기타 광고 콘텐츠 또는 커머스 콘텐츠를 회원님에게 보여드립니다. 자세한 내용은 아래 제2조를 참조하시기 바랍니다. 저희 서비스의 안전, 보안 및 무결성을 향상하고, 유해 행위를 방지하고, 사용자 커뮤니티를 안전하게 보호합니다. 사람들은 자신이 안전하고 보호받고 있다고 느껴야만 Meta 제품에서 커뮤니티를 형성합니다. 저희는 저희 제품 및 서비스의 보안(가용성, 신뢰성, 무결성 및 기밀성 포함)을 유지하기 위해 노력합니다. 저희는 전 세계에 전담팀을 두고 외부 서비스 제공업체, 파트너 및 관련 단체와 협업하며 저희 제품의 잠재적 오용, 타인에 대한 유해 행위, 그리고 저희의 잠재적인 위반 콘텐츠 사용자 신고에 대한 응답을 포함하여 저희가 저희의 커뮤니티를 지원하거나 보호하는데 도움이 될 수 있는 상황을 감지하기 위해 최첨단 기술 시스템을 개발합니다. 저희는 이러한 콘텐츠 또는 행위를 발견하는 경우, 저희의 평가를 기반으로 알림 전송, 도움 제공, 콘텐츠 삭제, 특정 기능에 대한 접근 차단 또는 제한, 계정 비활성화 또는 사법당국에 연락 등 적절한 조치를 취할 것입니다. 저희는 저희 제품을 이용하는 사람의 오용 또는 유해 행위를 감지한 경우 또는 Meta 제품, 사용자 및 커뮤니티를 안전하게 보호하기 위해 Meta Companies 사이에 데이터를 공유합니다. 예를 들어, 저희는 금융 상품 및 서비스를 제공하는 Meta Companies와 정보를 공유하여 해당 회사의 안전, 보안, 무결성 향상과 관련 법률 준수를 돕습니다. Meta는 법률에 의해 요구되거나 허용된다는 선의의 믿음이 있는 경우 회원님에 관하여 수집한 정보를 액세스, 보존, 이용 및 공유할 수 있습니다. 자세한 내용은 저희 개인정보처리방침 을 참고하세요. 경우에 따라 감독위원회가 위원회 약관 및 정관에 따라 저희의 결정을 검토할 수 있습니다. 자세한 내용은 여기 에서 알아보세요. 모든 사람에게 안전하고 실용적인 서비스를 제공하기 위해 최첨단 기술을 사용하고 개발합니다. 저희는 사람들이 신체적 능력이나 지리적 위치와 관계없이 안전하게 저희의 제품을 이용할 수 있도록 인공 지능, 머신 러닝 시스템 및 증강 현실과 같은 최첨단 기술을 이용하고 개발하고 있습니다. 예를 들어, 이러한 기술은 시각 장애가 있는 사람들이 Facebook이나 Instagram에서 공유된 사진 또는 동영상에 무엇이 있는지, 누가 있는지 파악할 수 있도록 도움을 줍니다. 또한 인터넷 접속이 원활하지 않은 지역에서도 보다 많은 사람들이 인터넷을 이용할 수 있도록 첨단 네트워크 및 통신 기술을 구축하고 있습니다. 뿐만 아니라 저희는 저희 커뮤니티 및 제품의 무결성을 손상시킬 수 있는 유해하고 위험한 활동을 감지하여 삭제하는 기능을 개선하기 위해 자동화 시스템을 개발합니다. 저희의 서비스를 향상하기 위한 방법을 연구합니다. 저희는 저희 제품의 개발, 테스트 및 개선을 위한 연구를 진행합니다. 여기에는 설문 조사를 실시하고 새로운 기능의 테스트 및 문제 해결을 진행하는 등의 방법으로 저희가 보유한 사용자 데이터를 분석하며, 사람들이 저희의 제품을 이용하는 방식을 이해하는 작업이 포함됩니다. 저희의 개인정보처리방침 에는 저희가 저희 서비스를 개발하고 개선할 목적으로 이 연구를 지원하기 위해 데이터를 이용하는 방식이 설명되어 있습니다. Meta Company 제품 전반에 걸쳐 일관되고 원활한 경험을 제공합니다. 저희의 제품은 회원님에게 중요한 사람, 그룹, 비즈니스, 단체, 다른 사항을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님이 이용하는 다양한 Meta Company 제품 에 걸쳐 일관되고 원활한 경험이 이뤄지도록 저희 시스템을 설계합니다. 예를 들어 회원님이 Facebook에서 소통하는 사람들에 대한 데이터를 이용해 Instagram 또는 Messenger에서도 쉽게 그들과 연결할 수 있도록 지원하며, Messenger를 통해 Facebook에서 팔로우하는 비즈니스와 소통할 수 있도록 지원합니다. 저희 서비스 이용에 대한 보장: 글로벌 서비스를 운영하고 회원님이 전 세계의 사람들과 연결될 수 있도록 하기 위하여, 저희는 회원님의 거주 국가 이외의 지역을 비롯하여 전 세계 데이터 센터, 파트너, 서비스 제공업체, 공급업체 및 시스템에 콘텐츠와 데이터를 이전, 저장, 배포해야 합니다. 저희 서비스를 제공하기 위해서는 본 글로벌 인프라의 이용이 필수적입니다. 이 인프라는 Meta Platforms, Inc., Meta Platforms Ireland Limited 또는 그 계열사가 소유, 운영하거나 통제할 수 있습니다. 2. Meta 서비스를 위한 자금 조달 방식 Facebook과 기타 저희가 제공하는 제품 및 서비스의 사용료를 지불하지 않는 대신, 회원님은 본 약관이 적용되는 Meta 제품을 이용함으로써 비즈니스 및 단체들이 Meta Company 제품 내외에서 홍보를 위해 저희에게 비용을 지불한 맞춤형 광고 및 기타 상업적 콘텐츠와 홍보 콘텐츠를 보게 될 수 있다는 데 동의합니다. 저희는 회원님과 보다 관련성이 높을 수 있는 맞춤형 광고 및 홍보 콘텐츠를 보여드리기 위해 회원님의 활동 및 관심사에 대한 정보 등 회원님의 개인정보를 이용합니다. 개인정보 보호는 저희가 저희의 맞춤형 광고 시스템을 설계할 때 핵심적으로 고려해온 사안입니다. 즉, 저희는 광고주에게 회원님의 신원을 알리지 않고도 회원님에게 회원님과 관련 있고 유용한 광고를 보여드릴 수 있습니다. 저희는 회원님의 개인정보를 판매하지 않습니다. 저희는 광고주로 하여금 저희에게 그들의 비즈니스 목표, 광고 타게팅 대상(예: 사이클링을 좋아하는 18~35세 사이의 사람) 등을 알려줄 수 있도록 합니다. 저희는 그런 다음 해당 광고에 관심이 있을 만하다고 생각하는 사람에게 광고를 노출합니다. 저희는 또한 사람들이 Meta 제품 내외에서 광고주의 콘텐츠와 어떻게 상호작용하고 있는지 광고주들이 이해할 수 있도록 광고주들에게 광고의 성과 보고서를 제공합니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성이 해당 광고를 보았음)를 제공합니다. 저희는 회원님이 구체적으로 허락하지 않는 한 회원님을 직접적으로 식별할 수 있는 정보(이름 또는 이메일 주소와 같이 그 정보만으로 회원님에게 연락을 취하는 데 이용될 수 있거나 회원님을 식별할 수 있는 정보)를 공유하지 않습니다. 여기 에서 Meta 광고의 작동 원리에 대해 자세히 알아보세요. 저희는 위에 명시된 서비스를 회원님께 제공하기 위해 회원님의 개인정보를 수집하고 이용합니다. 저희의 개인정보처리방침 에서 저희의 데이터 수집 및 이용 방법에 대해 자세히 알아볼 수 있습니다. 회원님은 회원님이 보게 되는 광고와 광고주의 유형, 저희가 회원님에게 보여드릴 광고를 결정하기 위해 이용하는 정보의 유형을 통제할 수 있습니다. 더 알아보기. 3. Facebook 및 커뮤니티에 대한 약속 저희는 저희의 사명을 실현하기 위해 회원님 및 다른 사람들에게 본 서비스를 제공합니다. 이에 대해 회원님은 다음과 같은 약속을 해야 합니다. Facebook을 이용할 수 있는 사람 사람들이 각자의 의견과 행동에 대한 책임을 질 때 Facebook 커뮤니티는 더 안전하고 신뢰할 수 있는 공간이 됩니다. 이러한 이유로 회원님은 다음 사항을 준수해야 합니다. 일상생활에서 사용하는 것과 동일한 이름을 계정에 제공해야 합니다. 회원님에 관한 정확한 정보를 제공해야 합니다. 계정(본인 계정)은 하나만 만들고 개인적인 용도로 이용해야 합니다. 비밀번호를 공유하거나, 회원님의 Facebook 계정에 대한 접근 권한을 다른 사람에게 부 | 2026-01-13T08:49:47 |
https://www.afternerd.com/ | Afternerd - Learn Python Online and Get CS Career tips Are you beginning your Python Programming and Software Engineering career? I provide my best Python and Career tips in the newsletter. Subscribe now! Premium Python Courses Python for Absolute Beginners. Object-Oriented Programming in Python. Socket Programming in Python. Featured Articles Best Way to Learn Python. Best Books for Programmers. How to Learn Computer Science? Home · Blog · Courses · Resources · Programming © Copyright 2017-2021, Afternerd | 2026-01-13T08:49:47 |
https://future.forem.com/amelia_hebrew/how-smart-pcs-could-change-daily-workflows-303d | How Smart PCs Could Change Daily Workflows - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Amelia Hebrew Posted on Dec 29, 2025 How Smart PCs Could Change Daily Workflows # ai # science Hey everyone! I’ve been reading a lot about emerging tech trends and wanted to start a discussion here. One idea that’s been on my mind is the concept of a Smart PC , a computer that doesn’t just run programs but actually adapts to your workflow, predicts your needs, and automates repetitive tasks. Imagine the productivity boost if your PC could anticipate your next move while still respecting privacy. I’m curious how others feel about this. Could this kind of adaptive technology genuinely make our work and learning more efficient? Question for discussion: What other “smart” tech innovations are you excited about right now? Excited to hear your perspectives! 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 Amelia Hebrew Follow Amelia Hebrew, a tech enthusiast and gadget guru, thrives on exploring the latest innovations in technology. Joined Nov 13, 2024 More from Amelia Hebrew Exploring Scalable Infrastructure for Edge Computing and Cloud Servers # science # edgecomputing 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://github.com/gregmalcolm/python_koans | GitHub - gregmalcolm/python_koans: Python Koans - Learn Python through TDD Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} gregmalcolm / python_koans Public Notifications You must be signed in to change notification settings Fork 2.9k Star 5.1k Python Koans - Learn Python through TDD License MIT license 5.1k stars 2.9k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 11 Pull requests 11 Actions Projects 0 Wiki Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Projects Wiki Security Insights gregmalcolm/python_koans master Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 393 Commits koans koans libs libs runner runner .gitignore .gitignore .gitpod.Dockerfile .gitpod.Dockerfile .gitpod.yml .gitpod.yml .hgignore .hgignore .travis.yml .travis.yml Contributor Notes.txt Contributor Notes.txt MIT-LICENSE MIT-LICENSE README.rst README.rst _runner_tests.py _runner_tests.py contemplate_koans.py contemplate_koans.py example_file.txt example_file.txt koans.txt koans.txt run.bat run.bat run.sh run.sh scent.py scent.py View all files Repository files navigation README MIT license Python Koans One click installation: or Python Koans is a port of Edgecase's "Ruby Koans" which can be found at http://rubykoans.com/ . Python Koans is an interactive tutorial for learning the Python programming language by making tests pass. Most tests are fixed by filling the missing parts of assert functions. Eg: self . assertEqual ( __ , 1 + 2 ) which can be fixed by replacing the __ part with the appropriate code: self . assertEqual ( 3 , 1 + 2 ) Occasionally you will encounter some failing tests that are already filled out. In these cases you will need to finish implementing some code to progress. For example, there is an exercise for writing some code that will tell you if a triangle is equilateral, isosceles or scalene. As well as being a great way to learn some Python, it is also a good way to get a taste of Test Driven Development (TDD). Downloading Python Koans Python Koans is available on GitHub: https://github.com/gregmalcolm/python_koans You can clone with Git or download the source as a zip/gz/bz2. Installing Python Koans Aside from downloading or checking out the latest version of Python Koans, you need to install the Python interpreter. At this time of writing, we support Python 3. The policy is to try to keep current with the latest production version. You should be able to work with newer Python versions, but older ones will likely give you problems. You can download Python from here: https://www.python.org/downloads/ After installing Python make sure the folder containing the python executable is in the system path. In other words, you need to be able to run Python from a command console. It will either be python3 or for Windows it will be python.exe . If you have problems, this may help: https://www.python.org/about/gettingstarted/ Windows users may also want to update the line in the batch file run.bat to set the python path: SET PYTHON_PATH=C:\Python39 Getting Started Jake Hebbert has created a couple of screencasts available here: https://www.youtube.com/watch?v=e2WXgXEjbHY&list=PL5Up_u-XkWgNcunP_UrTJG_3EXgbK2BQJ&index=1 Or if you prefer to read: From a *nix terminal or Windows command prompt run: .. code-block:: sh python contemplate_koans.py or: python3 contemplate_koans.py In my case I'm using Python 3 with Windows, so I fire up my command shell (cmd.exe) and run this: Apparently a test failed: AssertionError: False is not True It also tells me exactly where the problem is, it's an assert on line 12 of .\\koans\\about_asserts.py . This one is easy, just change False to True to make the test pass. Sooner or later you will likely encounter tests where you are not sure what the expected value should be. For example: class Dog : pass def test_objects_are_objects ( self ): fido = self . Dog () self . assertEqual ( __ , isinstance ( fido , object )) This is where the Python Command Line can come in handy. In this case I can fire up the command line, recreate the scenario and run queries: Sniffer Support Sniffer allows you to run the tests continuously. If you modify any files files in the koans directory, it will rerun the tests. To set this up, you need to install sniffer: python3 -m pip install sniffer You should also run one of these libraries depending on your system. This will automatically trigger sniffer when a file changes, otherwise sniffer will have to poll to see if the files have changed. On Linux: python3 -m pip install pyinotify On Windows: python3 -m pip install pywin32 Also available here: https://github.com/mhammond/pywin32/releases On macOS: python3 -m pip install MacFSEvents Once it is set up, you just run: sniffer Just modify one of the koans files and you'll see that the tests are triggered automatically. Sniffer is controlled by scent.py . Getting the Most From the Koans Quoting the Ruby Koans instructions: "In test-driven development the mantra has always been, red, green, refactor. Write a failing test and run it (red), make the test pass (green), then refactor it (that is look at the code and see if you can make it any better). In this case you will need to run the koan and see it fail (red), make the test pass (green), then take a moment and reflect upon the test to see what it is teaching you and improve the code to better communicate its intent (refactor)." Finding More Koan Projects There are number of other great Koan projects out there for various languages and frameworks. Most of them can be found in GitHub. Also there is a little koans activity on Bitbucket. GitHub koan projects: https://github.com/search?q=koans&ref=cmdform Bitbucket koan projects: https://bitbucket.org/repo/all?name=koans Translations Translations are always welcome! Feel free to add one to this README if you happen to work on one: https://github.com/mswell/python_koans_br Acknowledgments Thanks go to Jim Weirich and Joe O'Brien for the original Ruby Koans that the Python Koans is based on! Also the Ruby Koans in turn borrows from Metakoans so thanks also go to Ara Howard for that! Also thanks to everyone who has contributed to Python Koans! I got a great headstart by taking over a code base initiated by the combined Mikes of FPIP. So here's a little plug for their very cool Python podcast: https://www.frompythonimportpodcast.com/ A big thanks also to Mike Pirnat @pirnat and Kevin Chase @kjc have pitched in as co-maintainers at various times About Python Koans - Learn Python through TDD Topics python koans Resources Readme License MIT license Uh oh! There was an error while loading. Please reload this page . Activity Stars 5.1k stars Watchers 286 watching Forks 2.9k forks Report repository Releases No releases published Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Contributors 82 Uh oh! There was an error while loading. Please reload this page . + 68 contributors Languages Python 99.5% Other 0.5% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:49:47 |
https://www.eugs.org/pages/ebe-national-glaucoma-patient-support-groups | European Glaucoma Society eugs About Education Meetings Membership News Login Who we are History Executive Committee Committees Special Interest Groups Next Generation Partnership Partnerships EGS Task Forces Glaucoma Societies EbE Patients National Glaucoma Patient Support Groups Use the map (click on the country) or the list of countries to identify National societies and support groups of patients in your area or contact us if you are considering setting one up and need help. Use the list of countries to identify National societies and support groups of patients in your area or contact us if you are considering setting one up and need help. National societies (dark green countries): The following countries have an established patient society. Developing societies (light green countries): The following countries are currently developing their national societies and currently and only have an email for contact. Remaining countries: If your country is not listed highlighted or listed and you are interested in establishing or supporting a patient society, please contact us — we are happy to assist where possible. Austria Croatia Denmark Estonia Finland France Germany Netherlands North Macedonia Norway Portugal Spain Sweden United Kingdom Contacts European Glaucoma Society (EGS) Zeughausgasse 18 6300 Zug, Switzerland T: +39 055 5035357 M: egs_secretariat@eugs.org Contact us Social Privacy policy Cookie policy ©2026 European Glaucoma Society All rights reserved | 2026-01-13T08:49:47 |
https://www.facebook.com/r.php?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26link%3Dhttps%253A%252F%252Fdev.to%252Fjiwoomap%252Fbuilding-a-remembering-ai-trading-agent-with-python-langgraph-and-obsidian-30hn%26app_id%3D966242223397117%26source_surface%3Dexternal_reshare%26display%26hashtag&locale=ko_KR&display=page&entry_point=login | Facebook에 가입하기 새 계정 만들기 빠르고 쉽게 가입할 수 있습니다. 브라우저에서 Javascript가 비활성화되었습니다. 브라우저에서 JavaScript를 활성화하거나 Javascript 이용이 가능한 브라우저로 업그레이드하신 후 Facebook에 가입하세요. 오류가 발생했습니다. 다시 시도하세요. 계정을 만들 수 없습니다 Facebook에 가입하지 못했습니다. 생일 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 1995 1994 1993 1992 1991 1990 1989 1988 1987 1986 1985 1984 1983 1982 1981 1980 1979 1978 1977 1976 1975 1974 1973 1972 1971 1970 1969 1968 1967 1966 1965 1964 1963 1962 1961 1960 1959 1958 1957 1956 1955 1954 1953 1952 1951 1950 1949 1948 1947 1946 1945 1944 1943 1942 1941 1940 1939 1938 1937 1936 1935 1934 1933 1932 1931 1930 1929 1928 1927 1926 1925 1924 1923 1922 1921 1920 1919 1918 1917 1916 1915 1914 1913 1912 1911 1910 1909 1908 1907 1906 1905 1월 2월 3월 4월 5월 6월 7월 8월 9월 10월 11월 12월 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 연령 생년월일 사용 성별 여성 남성 직접 지정 회원님을 지칭할 성별대명사를 선택하세요 여성(She): "생일을 축하해주세요!" 남성(He): "생일을 축하해주세요!" 성별무관(They): "생일을 축하해주세요!" 성별대명사는 모든 사람에게 공개됩니다. 저희 서비스를 이용하는 사람이 회원님의 연락처 정보를 Facebook에 업로드했을 수도 있습니다. 더 알아보기 . 가입하기 버튼을 클릭하면 Facebook의 약관 , 개인정보처리방침 및 쿠키 정책 에 동의하게 됩니다. Facebook으로부터 SMS 알림을 받을 수 있으며 알림은 언제든지 옵트 아웃할 수 있습니다. 가입하기 이미 계정이 있으신가요? 보안 확인 필수 입력 항목입니다. 이 내용이 표시되는 이유는? 보안 확인 자동가입방지 문자 입력은 스패머가 자동 요청을 보내는 것을 방지하기 위해 Meta에서 사용하는 표준 보안 테스트입니다. Facebook의 이름이 Meta로 변경됩니다. 저희는 2022년 1월 4일에 새 이름을 반영하여 이용 약관, 데이터 정책 및 쿠키 정책을 개정했습니다. 회사명이 바뀌더라도 Facebook 앱을 포함한 모든 동일한 제품이 Meta에서 지속적으로 제공됩니다. 기존의 데이터 정책 및 서비스 약관은 효력을 유지하며, 이번 이름 변경으로 인해 저희의 기존 데이터 사용 및 공유 방식이 변경되지는 않습니다. Meta 와 Meta의 메타버스 비전을 자세히 알아보세요. 데이터 정책 이 정책에서는 Facebook, Instagram, Messenger 및 Meta Platforms, Inc.가 제공하는 기타 제품 및 기능을 지원하기 위해 저희가 처리하는 정보를 설명합니다. ( Meta 제품 또는 제품). 추가적인 도구 및 정보는 Facebook 설정 및 Instagram 설정 에서 확인할 수 있습니다. I. 저희가 수집하는 정보의 유형 Meta 제품을 제공하기 위해 저희는 회원님에 대한 정보를 처리해야 합니다. 수집하는 정보의 유형은 회원님이 저희 제품을 이용하는 방법에 따라 다릅니다. Facebook 설정 및 Instagram 설정 에 접속하여 저희가 수집한 정보에 액세스하고 이를 삭제하는 방법에 대해 알아보실 수 있습니다. 회원님 및 다른 사람의 활동 및 제공하는 정보. 회원님이 제공하는 정보 및 콘텐츠. 저희는 회원님이 Meta 제품을 이용(계정 가입, 콘텐츠 작성 또는 공유, 다른 사람들과의 메시지 전송 또는 커뮤니케이션 포함)할 때 제공하는 콘텐츠, 커뮤니케이션 및 기타 정보를 수집합니다. 여기에는 사진 촬영 장소나 파일 생성 날짜와 같이 회원님이 제공한 콘텐츠에 포함되거나 관련된 정보(메타데이터 등)가 포함될 수 있습니다. 또한 여기에는 카메라 와 같이 저희가 제공하는 기능을 통해 표시되는 내용도 포함되므로, 회원님이 좋아할 만한 마스크와 필터를 제안하거나, 카메라 형식 사용에 관한 팁을 제공할 수도 있습니다. Meta 시스템은 아래 에 명시된 목적을 위해 회원님과 다른 사람들이 제공한 콘텐츠 및 커뮤니케이션을 자동으로 처리하여, 배경과 그 내용을 분석합니다. 회원님이 공유 한 항목을 볼 수 있는 사람을 관리하는 방법에 대해 자세히 알아보세요. 특별 보호를 받는 정보: Facebook 프로필 필드 또는 중요 이벤트에 회원님의 종교관, 정치관, '관심 있는' 사람 또는 건강 정보를 제공하도록 선택할 수 있습니다. 이러한 정보 및 기타 정보(예를 들어 인종 또는 민족적 태생, 철학적 신념 또는 노동조합 가입 여부)는 회원님의 해당 국가 법률에 따라 특별 보호를 받을 수 있습니다. 네트워크 및 연결. 저희는 회원님과 연결된 사람, 계정, 해시태그 , Facebook 그룹 및 페이지 (예를 들어 저희 제품에서 회원님이 가장 많이 연락하는 사람이나 회원님이 속한 그룹)에 대한 정보 및 이들과 연락하는 방식에 대한 정보를 수집합니다. 또한 회원님이 연락처 정보(예를 들어 주소록, 통화 로그 또는 SMS 로그 기록)를 기기에서 업로드, 동기화 또는 가져오기로 선택 하는 경우 해당 연락처 정보를 수집합니다. 이 연락처 정보는 회원님 및 다른 사람들이 알 수도 있는 사람들을 찾도록 돕고 아래 에 나열된 기타 목적을 위해 이용됩니다. 회원님의 이용. 저희는 회원님이 보거나 참여하는 콘텐츠의 유형, 사용하는 기능, 수행하는 행동, 교류하는 사람 또는 계정, 활동 시간, 빈도 및 기간 등 회원님이 Meta 제품을 이용하는 방법에 대한 정보를 수집합니다. 예를 들어 저희는 회원님이 Meta 제품을 이용한 시간, 마지막으로 이용한 시간, Meta 제품에서 확인한 게시물, 동영상 및 기타 콘텐츠를 기록합니다. 또한 저희는 회원님이 카메라와 같은 기능들을 사용하는 방법에 대한 정보도 수집합니다. Meta 제품에서 이뤄진 거래에 관한 정보. 회원님이 구매 또는 기타 금융 거래를 위해 Meta 제품을 이용하는 경우(예를 들어 게임 내에서 구매하거나 기부 하는 경우) 저희는 구매 또는 거래에 관한 정보를 수집합니다. 여기에는 신용카드 또는 직불카드 번호 및 기타 카드 정보, 기타 계정 및 인증 정보, 청구, 배송 및 연락처와 같은 결제 정보가 포함됩니다. 다른 사람의 활동 및 다른 사람이 회원님에 관해 제공한 정보. 또한 저희는 다른 사람이 Meta 제품을 이용할 때 그들이 제공하는 콘텐츠, 커뮤니케이션 및 정보를 수집하고 분석합니다. 여기에는 다른 사람이 언제 회원님의 사진을 공유하거나 회원님의 사진에 댓글을 남기는지, 언제 회원님에게 메시지를 보내는지, 언제 회원님의 연락처 정보를 업로드, 동기화 또는 가져오는지 등과 같은 회원님에 관한 정보가 포함될 수 있습니다. 기기 정보 아래에 설명된 바와 같이, 저희는 회원님이 사용하여 Facebook 제품과 통합되는 컴퓨터, 전화, 스마트 TV 및 기타 웹 연결 기기로부터, 그리고 해당 기기에 관한 정보를 수집하고, 회원님이 사용하는 여러 기기에 이 정보를 결합합니다. 예를 들어 저희는 회원님의 휴대폰에서 Facebook 제품 이용에 관해 수집한 정보를 이용하여, 회원님이 노트북이나 태블릿과 같은 다른 기기에서 Facebook 제품을 이용할 때 보게 되는 콘텐츠( 광고 포함) 또는 기능을 회원님에게 맞춤화하거나, 다른 기기에서 회원님의 휴대폰에 표시된 광고에 대한 회원님의 반응 여부를 측정합니다. 이러한 기기로부터 얻는 정보는 다음과 같습니다. 기기 속성: 운영 체제, 하드웨어 및 소프트웨어 버전, 배터리 잔량, 신호 강도, 사용 가능한 저장 공간, 브라우저 유형, 앱 및 파일 이름 및 유형, 플러그인 등의 정보. 기기 작업: 창이 전면 또는 백그라운드에 있는지 여부, 마우스 움직임(인간과 봇을 구분하는 데 도움이 될 수 있음) 등 기기에서 수행되는 작업 및 동작에 관한 정보. 식별자: 고유 식별자, 기기 ID 및 기타 식별자. 기타 식별자의 예로는 회원님이 이용하는 게임, 앱 또는 계정 등의 식별자 및 가족 기기 ID(또는 동일한 기기나 계정과 관련된 Meta Company 제품 에 고유한 기타 식별자)가 있습니다. 기기 신호: Bluetooth 신호 및 근처 Wi-Fi 액세스 포인트, 비콘 및 셀 타워에 관한 정보. 기기 설정 데이터: GPS 위치, 카메라 또는 사진에 대한 액세스 등 회원님의 기기 설정을 활성화하여 Meta가 수신할 수 있도록 허가한 정보. 네트워크 및 연결: 이동통신사 또는 ISP 명칭, 언어, 시간대, 휴대폰 번호, IP 주소, 연결 속도 및 때로는 가까이 있거나 회원님의 네트워크에 있는 다른 기기에 관한 정보. 이를 통해 Meta는 휴대폰에서 TV로 동영상을 스트리밍 하는 등의 작업을 지원할 수 있습니다. 쿠키 데이터: 쿠키 ID 및 설정을 포함하여 기기에 저장된 쿠키 데이터. 쿠키 사용에 관한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 에서 알아보세요. 파트너가 제공하는 정보. 광고주, 앱 개발자 및 퍼블리셔는 이들이 사용하는 Meta 비즈니스 도구 , 즉 저희의 소셜 플러그인(예: '좋아요' 버튼), Facebook 로그인, 저희 API와 SDK 또는 Meta 픽셀 을 통해 저희로 정보를 제공할 수 있습니다. 이 파트너들은 회원님의 저희 계정 보유 여부 또는 저희 제품 로그인 여부와 관계없이 Meta 제품 밖에서의 회원님의 활동에 대한 정보(회원님의 기기, 회원님이 방문한 웹사이트, 회원님의 구매 내역, 회원님에게 표시되는 광고 및 회원님이 해당 파트너들의 서비스를 사용한 방법에 관한 정보 포함)를 제공합니다. 예를 들어, 게임 개발자는 저희 API를 사용하여 저희에게 회원님이 플레이하는 게임에 대해 알려줄 수 있고, 비즈니스는 회원님이 해당 비즈니스의 스토어에서 구매한 제품에 대해 알려줄 수 있습니다. 또한 저희는 회원님의 정보를 저희에게 제공할 권리가 있는 제3자 데이터 제공업체로부터 회원님의 온라인 및 오프라인 활동과 구매에 관한 정보를 받습니다. 회원님이 파트너를 방문하거나 파트너 서비스를 이용할 때 또는 파트너와 제휴한 제3자를 통해 서비스를 이용할 때 회원님의 데이터를 파트너가 받게 됩니다. 저희는 각 파트너에게 회원님의 데이터를 수집하고, 사용하고, 공유할 수 있는 합법적 권한을 획득한 후에 저희에게 데이터를 제공할 것을 요구합니다. 저희에게 데이터를 제공하는 파트너의 유형에 대해 자세히 알아보세요 . Meta 비즈니스 도구와 관련하여 저희의 쿠키 사용에 대한 자세한 내용은 Facebook 쿠키 정책 및 Instagram 쿠키 정책 을 참조하시기 바랍니다. II. 저희가 정보를 활용하는 방법 저희는 (회원님이 동의할 경우) 아래에 설명된 바와 같이 보유한 정보를 이용하며, Meta 약관 및 Instagram 약관 에 설명된 Meta 제품 및 관련 서비스를 제공하고 지원합니다. 방법은 다음과 같습니다. Facebook 제품의 제공, 맞춤화 및 개선. 저희는 Meta 제품을 제공하기 위해 보유한 정보를 이용합니다. Meta 제품을 제공하는 데는 기능 및 콘텐츠(귀사 광고, Facebook 뉴스피드 , Instagram 피드 및 Instagram 스토리 포함)를 맞춤화하고 Meta 제품 안팎에서 회원님이 관심을 가질 만한 그룹 또는 이벤트 나 팔로우할 만한 주제 등을 추천하는 것이 포함됩니다. 회원님을 위해 특별하고 관련성 있는 맞춤화된 Meta 제품을 만들기 위해, 저희는 수집한 데이터와 회원님 및 다른 사람으로부터 얻은 정보(회원님이 제공하기로 선택한 특별 보호 데이터 포함)에 기초한 회원님의 관계, 기호, 관심사 및 활동, 회원님이 Meta 제품을 이용하고 상호 작용하는 방법, Meta 제품 안팎에서 회원님과 연결되어 있거나 회원님이 관심 있는 사람, 장소 또는 사물에 관한 정보를 이용합니다. Meta 제품의 기능, 콘텐츠, 추천을 포함하여 Facebook과 Instagram에서 개인에게 맞춤화된 경험을 제공하기 위해 저희가 회원님에 관한 정보를 어떻게 사용하는지 자세히 알아보세요. 또한 회원님에게 표시되는 광고 를 선택하는 방법도 자세히 알아볼 수 있습니다. Meta 제품 및 기기의 정보: 저희는 여러 Meta 제품 및 기기 활동에 관한 정보를 연결하여 회원님이 사용하는 모든 Meta 제품에 대해, 어디서 해당 제품을 이용하는지에 관계없이 더욱 맞춤화되고 일관된 경험을 제공합니다. 예를 들어 Instagram에서 회원님이 팔로우하거나 Messenger로 커뮤니케이션하는 사람들이 속한 Facebook 그룹에 가입할 것을 추천할 수 있습니다. 또한 예를 들어 다른 Meta 제품의 계정에 가입할 때 기존 Meta 제품의 등록 정보(전화번호 등)를 자동으로 기입하는 등 회원님에게 더욱 원활한 경험을 제공할 수도 있습니다. 위치 관련 정보: 저희는 회원님 및 다른 사람들에게 광고를 포함한 Meta 제품을 제공하고, 맞춤화하고, 개선하기 위해 위치 관련 정보 (예: 회원님의 현재 위치, 거주 지역, 가고 싶은 장소, 주변에 있는 비즈니스 및 사람)를 이용합니다. 위치 관련 정보는 정확한 기기 위치(수집을 허용한 경우), IP 주소 및 회원님 및 다른 사람이 Meta 제품을 이용하여 발생하는 정보(예를 들어 체크인 또는 참석 이벤트)와 같은 사항을 기반으로 할 수 있습니다. 제품 연구 및 개발: 저희는 보유한 정보를 이용하여 설문조사 및 리서치를 수행하고 새로운 제품과 기능을 테스트하며 문제를 해결함으로써 Meta 제품을 개발, 테스트 및 개선합니다. 광고 및 기타 홍보 콘텐츠: 저희는 보유한 정보(회원님의 관심사, 행동 및 관계에 관한 정보를 포함)를 이용하여 광고, 쿠폰 및 회원님에게 표시되는 기타 홍보 콘텐츠를 선택하고 맞춤화합니다. 저희가 광고를 선택하고 맞춤화하는 방법 , 광고 및 기타 홍보 콘텐츠를 선택하기 위해 사용한 데이터에 관한 회원님의 선택 사항을 Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 측정, 분석 및 기타 비즈니스 서비스 제공. 저희는 보유한 정보(방문한 웹사이트 및 광고 등 Facebook 제품 밖에서의 활동 포함)를 이용하여 광고주 및 기타 파트너가 광고 및 서비스의 성과와 배포를 측정하고 해당 서비스를 사용하는 사람들의 유형 및 사람들이 웹사이트, 앱, 서비스와 상호 작용하는 방식을 파악할 수 있도록 지원합니다. 이러한 파트너와 정보를 공유하는 방법에 대해 알아보세요 . 안전, 진실성 및 보안 강화. 저희는 보유한 정보를 이용하여 계정 및 활동을 확인하고, 유해 행위를 방지하며, 스팸 및 기타 부정적인 경험을 감지 및 방지하고, 제품의 무결성을 유지하며, Meta 제품 안팎의 안전 및 보안을 강화합니다. 예를 들어 저희는 보유한 데이터를 이용하여 의심스러운 활동 또는 저희 약관이나 정책 위반을 조사하거나 누군가에게 도움이 필요한 시점을 감지 합니다. 자세히 알아보려면 Facebook 보안 고객 센터 및 Instagram 보안 팁 을 방문하세요. 회원님과의 커뮤니케이션. 저희는 보유한 데이터를 이용하여 회원님에게 마케팅 자료를 제공하고 Facebook 제품에 관해 커뮤니케이션하며, Facebook 정책 및 약관에 대한 내용을 알려 드립니다. 또한 저희는 회원님의 정보를 이용하여 회원님의 연락에 대응합니다. 사회적 공익 연구 및 혁신. 저희는 보유한 정보(저희와 협업하는 연구 파트너의 정보 포함)를 이용하여 일반 사회 복지, 기술 발전, 공익, 보건 및 복지에 관한 주제의 연구 와 혁신을 진행하며, 이를 지원합니다. 예를 들어, 위기 상황 시 저희가 보유한 이동 패턴 정보를 분석하여 구호 활동을 지원합니다. Facebook 연구 프로그램에 대해 자세히 알아보세요 . III. 정보 공유 방법 회원님의 정보는 다음 방법으로 다른 사람들과 공유됩니다. Meta 제품에서 공유 회원님이 공유하고 커뮤니케이션하는 사람 및 계정 회원님은 Facebook 제품을 이용하여 공유 또는 커뮤니케이션할 때 공유할 내용에 대한 공개 대상을 선택 합니다. 예를 들어 회원님은 Facebook에 게시물을 포스팅할 때 그룹, 모든 친구, 전체 공개 또는 맞춤 설정한 리스트에 있는 사람 등 게시물에 대한 공개 대상을 선택합니다. 마찬가지로, 회원님이 Messenger 또는 Instagram을 사용하여 사람 또는 비즈니스와 커뮤니케이션할 때 해당 사람 및 비즈니스는 회원님이 전송하는 콘텐츠를 볼 수 있습니다. 회원님의 네트워크는 회원님이 Meta 제품에서 취한 행동(광고 및 홍보 콘텐츠 참여 포함)을 볼 수도 있습니다. 또한 저희는 다른 계정이 해당 계정의 Facebook 또는 Instagram 스토리를 누가 조회했는지 볼 수 있도록 허용합니다. 공개 정보 는 계정이 없는 경우를 포함하여 Facebook 제품 안팎에서 누구든지 볼 수 있습니다. 여기에는 Instagram 사용자 이름, 공개 대상과 공유하는 모든 정보, 회원님 Facebook 공개 프로필 에 있는 정보, Facebook 페이지에서 공유하는 콘텐츠, Instagram 공개 계정 또는 Facebook Marketplace 와 같은 기타 공개 포럼에서 공유하는 콘텐츠가 포함됩니다. 회원님, Facebook과 Instagram을 사용하는 다른 사람들 그리고 저희는 검색 결과 또는 도구 및 API를 통해 Meta 제품(Meta Company 제품 포함) 안팎에 있는 모든 사람에게 공개 정보에 대한 액세스 권한을 제공하거나 해당 공개 정보를 전송할 수 있습니다. 공개 정보는 검색 엔진, API 같은 제3자 서비스, TV 같은 오프라인 매체와 앱, 웹사이트, 저희 제품과 통합된 기타 서비스를 통해 보거나 액세스하거나 다시 공유하거나 다운로드할 수도 있습니다. 공개 정보 및 Facebook 과 Instagram 에서 공개 범위를 설정하는 방법에 대해 자세히 알아보세요. 다른 사람이 회원님과 공유하거나 다시 공유한 콘텐츠 Meta 제품에서 회원님의 활동을 볼 수 있는 사람들은 Meta 제품 안팎에서 다른 사람들(회원님이 공유한 공개 대상 이외의 사람들과 비즈니스 포함)과 이를 공유할지 여부를 선택할 수 있으므로, 회원님은 공유 대상을 선택할 때 이를 고려해야 합니다. 예를 들어 특정 친구 또는 계정에 게시물을 공유하거나 메시지를 전송할 때, 해당 친구 또는 계정은 직접 또는 Horizon 월드 같은 가상 현실 환경에서 콘텐츠를 다운로드하거나 스크린샷으로 캡처하거나 Meta 제품 안팎으로 다른 사람과 다시 공유할 수 있습니다. 또한 다른 사람의 게시물에 댓글을 달거나 공감할 때, 그 사람의 콘텐츠를 볼 수 있는 사람은 회원님의 댓글이나 공감 상태를 볼 수 있고 해당 콘텐츠를 게시한 사람은 나중에 공개 대상을 변경할 수 있습니다. 사람들은 Facebook 제품을 이용하여 회원님에 관한 콘텐츠를 만들고 원하는 공개 대상과 공유할 수도 있습니다. 예를 들어 스토리에 회원님의 사진을 공유하고, 게시물에 회원님의 위치를 언급하거나 태그하고, 게시물 또는 메시지에 회원님에 대한 정보를 공유할 수 있습니다. 다른 사람들이 Facebook 제품에서 회원님에 대해 공유한 내용에 불편함을 느낀다면 콘텐츠를 신고 하는 방법을 알아보실 수 있습니다. Meta 제품에서 회원님의 활동 상태 또는 존재에 관한 정보. 회원님의 네트워크에 있는 사람들은 Facebook 제품에 대한 회원님의 활동 여부( Instagram , Messenger 또는 Facebook에서 활동 상태인지, 언제 마지막으로 Facebook 제품을 이용하였는지 포함)를 알려주는 신호를 볼 수 있습니다. Meta 제품에 포함되어 있거나 서비스를 이용한 앱, 웹사이트 및 제3자 통합. Meta 제품을 이용하거나 Meta 제품에 통합된 타사 앱, 웹사이트 또는 기타 서비스를 이용할 경우 해당 타사에서 회원님이 게시하거나 공유한 내용에 관한 정보를 받을 수 있습니다. 예를 들어 Facebook 친구와 게임을 하거나 웹사이트에서 Facebook 댓글 달기 또는 공유하기 버튼을 사용하는 경우, 게임 개발자 또는 웹사이트는 게임 내 회원님의 활동에 대한 정보를 받거나 회원님이 Facebook에서 해당 웹사이트를 통해 공유한 댓글이나 링크에 관한 정보를 받을 수 있습니다. 또한 이러한 제3자 서비스를 다운로드하거나 사용할 때 해당 제3자는 Facebook의 공개 프로필 및 회원님이 해당 제3자에 공유한 모든 정보에 액세스할 수 있습니다. 회원님이 공유를 선택할 경우 회원님이 이용하는 앱과 웹사이트에서 Facebook 친구 리스트를 수신할 수 있습니다. 단, 회원님이 이용하는 앱과 웹사이트는 회원님의 Facebook 친구에 관한 기타 모든 정보 또는 회원님의 Instagram 팔로워에 관한 정보를 수신할 수 없습니다. 이는 회원님의 친구와 팔로워가 이 정보를 공유하도록 선택했더라도 마찬가지입니다. 이러한 제3자 서비스에서 수집되는 정보는 Facebook 약관 및 정책이 아닌 해당 제3자의 자체 약관 및 정책의 적용을 받습니다. Facebook 및 Instagram의 기본 버전을 제공하는 기기와 운영 체제(즉, 저희가 저희 자체의 앱을 개발하지 않은 기기와 운영 체제)는 저희 핵심 기능을 회원님에게 제공하기 위해 회원님의 친구가 회원님과 공유하는 정보를 포함하여 회원님이 공유하기로 선택하는 모든 정보에 액세스할 수 있습니다. 참고: 저희는 현재 남용을 방지하기 위해 개발자의 데이터 액세스 권한을 추가로 제한하고 있습니다. 예를 들어, 저희는 회원님이 3개월 동안 앱을 사용하지 않았고, 저희가 로그인을 변경하는 경우 회원님의 Facebook 및 Instagram에 대한 개발자의 액세스 권한을 삭제하며, 다음 버전에서 앱 검수 없이 앱에서 요청할 수 있는 데이터를 이름, Instagram 사용자 이름, 소개, 프로필 사진, 이메일 주소만 포함되도록 축소합니다. 더 많은 데이터를 요청하려면 저희의 허가를 받아야만 합니다. 새로운 소유자. Facebook 제품 또는 해당 자산의 전부 또는 일부에 대한 소유권 또는 운영권이 변경되는 경우, 저희는 회원님에 대한 정보를 새로운 소유주에게 제공할 수 있습니다. 제3자 파트너와 공유 저희는 Meta를 지원하고 Meta 제품을 제공하고 개선하는 데 도움을 주거나 Meta 비즈니스 도구를 사용하는 제3자 파트너와 협력하여 이들의 비즈니스를 성장시킴으로써 회사를 운영하고 전 세계 사람들에게 무료 서비스를 제공하고 있습니다. 저희는 회원님의 정보를 누구에게도 판매하지 않으며 앞으로도 판매하지 않을 것입니다. 저희는 또한 파트너가 저희가 제공한 데이터를 이용하고 공개하는 방법에 엄격한 제한을 가하고 있습니다. 저희가 정보를 공유하는 제3자의 유형은 다음과 같습니다. Meta 분석 서비스를 사용하는 파트너. 저희는 개인 및 비즈니스가 사람들이 Meta 제품 안팎의 게시물, 리스트, Facebook 페이지, 동영상 및 기타 콘텐츠에 참여하는 방식을 파악하는 데 참고할 수 있는 취합된 통계 및 인사이트를 제공합니다. 예를 들어 Facebook 페이지 관리자 및 Instagram 비즈니스 프로필은 게시물을 보거나, 게시물에 반응하거나, 댓글을 단 사람의 수에 관한 정보 외에도 취합된 인구 통계학적 특성 및 기타 계정 또는 Facebook 페이지와의 상호 작용을 파악하는 데 도움이 되는 정보를 받습니다. 광고주. 저희는 광고주에게 광고를 보는 사람들의 유형 및 광고 실적에 관한 보고서를 제공하지만 회원님을 개인적으로 식별하는 정보(회원님에게 연락하거나 식별하는 데 이용될 수 있는 이름 또는 이메일 주소 같은 정보)는 회원님이 허용하지 않는 한 공유하지 않습니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성에게 해당 광고가 노출됨)를 제공합니다. 또한 어떠한 광고가 회원님의 구매나 광고주에 관한 행동을 하게 유도했는지 확인합니다. 측정 파트너. 저희는 회원님에 대한 정보를 수집하여 파트너에게 분석 및 측정 보고서를 제공하는 회사와 정보를 공유합니다. Meta 제품 안에서 상품 및 서비스를 제공하는 파트너. 회원님이 프리미엄 콘텐츠를 구독하거나 Facebook 제품 내 판매자로부터 상품을 구매하는 경우, 해당 콘텐츠 제작자 또는 판매자는 회원님이 공유하는 공개 정보 및 기타 정보 외에도 배송 및 연락처 세부 정보를 포함하여 거래를 완료하는 데 필요한 정보를 받을 수 있습니다. 벤더 및 서비스 공급자. 저희는 기술 인프라 서비스 제공, Facebook 제품 이용 방법 분석, 고객 서비스 제공, 결제 간소화 또는 설문 수행 등의 방법을 통해 Facebook 비즈니스를 지원하는 벤더 및 서비스 공급자에게 정보와 콘텐츠를 제공합니다. 연구원 및 학자. 또한 저희는 연구 파트너 및 학자 에게 정보와 콘텐츠를 제공하여, 그들이 Facebook의 비즈니스 또는 사명을 지원하는 학문과 혁신을 발전시키는 연구, 그리고 일반적인 사회 복지, 기술 발전, 공익, 건강 및 복지에 대한 발견 및 혁신을 향상시키는 연구를 수행할 수 있도록 합니다. 사법당국 또는 법적 요청. 저희는 아래에 명시된 상황에서 사법당국 또는 법적 요청에 대응하여 정보를 공유합니다. Facebook 설정 및 Instagram 설정 에서 회원님 또는 다른 사람이 제3자 파트너와 공유하는 정보를 설정하는 방법에 대해 자세히 알아보세요. IV. Meta Companies가 협력하는 방식 Facebook과 Instagram은 회원님이 사용하는 모든 Meta Company 제품 에서 혁신적이고 관련성이 있으며 일관적이고 안전한 환경을 제공하기 위해 Meta Companies (WhatsApp 및 Oculus 포함)와 인프라, 시스템 및 기술을 공유합니다. 또한 저희는 이러한 목적을 위해, 관련 법에서 허용하는 경우에 Meta Companies의 약관 및 정책에 따라 Meta Companies에서 회원님에 대한 정보를 처리합니다. 예를 들어 저희는 WhatsApp의 서비스에서 스팸을 보내는 계정에 대한 정보를 처리하여 Facebook, Instagram 또는 Messenger에서 해당 계정에 대해 적절한 조치를 취할 수 있습니다. 또한 저희는 다른 Meta Company 제품의 고유 사용자 수를 파악하는 등 사람들이 Meta Company 제품을 이용하고 상호 작용하는 방법을 파악하기 위해 노력하고 있습니다. V. 회원님의 정보를 관리 또는 삭제하는 방법 저희는 데이터 액세스, 수정, 복사 및 삭제 기능을 제공합니다. Facebook 설정 및 Instagram 설정 에서 자세히 알아보세요. 저희는 더 이상 Meta 서비스 및 Meta 제품을 제공할 필요가 없는 시점, 그리고 회원님의 계정이 삭제되는 시점 중 먼저 도달하는 시점까지만 데이터를 저장합니다. 이는 데이터의 성격, 수집 및 처리된 이유, 관련된 법적 또는 운영상 보존 필요성과 같은 요인에 따라 개별적으로 결정됩니다. 예를 들어 회원님이 Facebook에서 무언가를 검색할 때 언제든지 검색 기록에서 해당 검색어에 액세스하고 삭제할 수 있지만, 해당 검색어에 대한 로그는 6개월 후에 삭제됩니다. 회원님이 계정 확인을 위해 정부가 발행한 신분증명서 사본을 제출하는 경우 저희는 달리 명시하지 않는 한 검토 후 30일 이내에 해당 사본을 삭제합니다. 공유된 콘텐츠 및 소셜 플러그인을 통해 얻은 쿠키 데이터 삭제 에 대해 자세히 알아보세요. 계정을 삭제하면 회원님의 사진이나 상태 업데이트 등 회원님이 게시한 사항들이 삭제 되며 나중에 해당 정보를 복원할 수 없습니다. 다른 사람이 회원님에 대해 공유한 정보는 회원님의 계정에 포함되지 않으며 삭제되지 않습니다. 계정을 삭제하지 않고 제품 이용을 일시적으로 중단하려면 계정을 비활성화할 수 있습니다. 회원님의 계정을 삭제하려면 언제든지 Facebook 설정 및 Instagram 설정 을 방문하세요. VI. 법적 요청에 대한 대응과 피해 방지 Meta는 회원님의 정보에 액세스하고 이를 보존하며 규제 당국, 사법당국 또는 다른 사람들과 이 정보를 공유합니다. 법적인 요청(예: 수색 영장, 법원 명령서, 소환장 등)이 수반되고 법의 집행을 위해 필요하다고 판단될 경우. 여기에는 미국 외 지역 관할권에서의 법적 요청이 수반되고, 해당 관할권의 법에 의해 필요성이 인정되며, 그 지역 내의 사용자들에게 영향을 미침과 동시에 국제적으로 용인되는 기준에 부합한다고 판단될 때 해당 관할권의 요청을 받아들이는 경우가 포함됩니다. Meta가 필요성을 인정할 경우 사기, 제품의 권한 없는 사용, 약관 또는 정책 위반, 또는 기타 유해하거나 불법적인 활동을 감지 및 예방하고 이에 대처하는 조치, 조사 또는 규제 요구를 포함하여 Meta(권리, 자산 또는 제품), 회원님 또는 다른 사람을 보호하기 위한 조치, 생명을 보호하고 상해를 막기 위한 조치가 필요합니다. 예를 들어 관련성이 있는 경우 저희는 제품의 사기, 남용 및 기타 유해한 활동을 방지하기 위해 계정의 신뢰성에 대한 정보를 제3자 파트너와 주고받습니다. 저희 제품을 이용한 구매 활동과 관련된 금융 거래 데이터를 포함해 저희가 수집하는 회원님의 정보는 법적인 요청이나 의무, 정부 조사, 저희의 약관과 정책에 대한 잠재적 위반에 대한 조사의 대상이 되는 경우 또는 다른 피해를 방지하기 위한 목적으로 장기간 액세스 및 보관될 수 있습니다. 또한 약관 악용 사례 또는 기타 약관에 대한 위반 행위의 반복을 막기 위해 약관 위반으로 비활성화된 계정의 정보를 최소 1년 이상 보존합니다. VII. 글로벌 서비스의 일환으로 데이터를 운영하고 이전하는 방법 저희는 본 개인정보처리방침에 따라 전 세계적으로 정보를 공유하는바, Meta Companies 내부적으로 정보를 공유하고, 외부적으로 저희의 파트너, 그리고 회원님이 연결하고 공유하는 대상과도 정보를 공유합니다. 예를 들어 회원님의 정보는 본 정책에 설명된 목적을 위해 미국 또는 회원님이 거주하는 지역 이외의 기타 국가로 이전 또는 전송되거나 이들 국가에서 저장 및 처리될 수 있습니다. 이러한 데이터 이전은 Meta 약관 및 Instagram 약관 에 명시된 서비스를 제공하고 저희 제품을 전 세계적으로 운영하며 회원님에게 제공하기 위해 필요합니다. 저희는 표준 계약 조항 을 활용하고, 해당할 경우 특정 국가에 대한 유럽연합 집행위원회의 적정성 결정 을 따르며, 미국 및 기타 국가로의 데이터 이전에 대해 회원님의 동의를 받습니다. VIII. 개인정보처리방침 변경 사항에 대한 안내 저희는 본 정책을 변경하기 전에 회원님에게 알리고, 회원님이 Facebook 제품 이용을 계속하기 전에 회원님에게 변경된 정책을 검토할 기회를 제공할 것입니다. 대한민국 개인정보 보호 고지사항 저희의 대한민국 개인정보 보호 고지사항 을 확인하여 회원님이 행사할 수 있는 개인정보 보호 권리, 저희가 회원님의 정보를 공유하는 제3자에 관한 상세 정보 및 기타 사항에 대해 자세히 알아보세요. IX. Meta에 문의하는 방법 Facebook 또는 Instagram 의 개인정보처리방침을 자세히 알아보세요. 본 정책에 관해 궁금하신 점이 있으면 아래에 설명된 바와 같이 Meta에 문의하실 수 있습니다. Meta Platforms, Inc.는 대한민국 사용자의 개인정보 관련 고충에 관한 문의를 위해 Privacy Agent Korea Co., Ltd.를 국내 대리인으로 지정하였습니다. 국내대리인에게 온라인 , 전화나 우편 또는 이메일로 문의하실 수 있습니다. Privacy Agent Korea Co., Ltd. ATTN: 대표이사 박천희 서울특별시 종로구 새문안로5가길 28 전화: 02-737-0455 저희는 Meta 개인정보처리방침 및 업무 방식에 관하여 회원님과 분쟁이 있을 경우 TrustArc를 통해 해결할 수 있습니다. 이에 관하여는 TrustArc의 웹사이트 를 통해 TrustArc에 문의하세요. 다음과 같은 방법으로 문의할 수 있습니다. 온라인 또는 우편 문의: Meta Platforms, Inc. ATTN: Privacy Operations 1601 Willow Road Menlo Park, CA 94025 최종 수정일: 2022년 1월 4일 Facebook의 데이터 정책에 동의합니다 서비스 약관 Meta 서비스 약관이 개정됩니다. 이 개정 사항은 2025년 1월 1일부터 적용됩니다. 새로운 약관을 읽어보세요 . Meta는 사람들이 서로 교류하고 커뮤니티를 만들며 비즈니스를 성장시킬 수 있는 기술과 서비스를 개발합니다. (본 약관이 아닌) 별도의 약관이 적용된다고 명시되어 있지 않은 한, 본 약관은 회원님의 Facebook, Messenger 및 기타 저희가 제공하는 제품, 기능, 앱, 서비스, 기술, 소프트웨어( Meta 제품 또는 제품 ) 이용에 적용됩니다. 해당 제품은 Meta Platforms, Inc.가 회원님에게 제공합니다. 달리 명시된 경우를 제외하고 저희는 회원님에게 Facebook 또는 기타 본 약관이 적용되는 제품 및 서비스의 사용료를 청구하지 않습니다. 그 대신, 비즈니스와 단체 및 다른 사람이 저희에게 그들의 제품 및 서비스 광고를 회원님에게 보여드리도록 비용을 지불합니다. 저희 제품을 이용함으로써 회원님은 저희가 회원님 및 회원님의 관심사와 관련 있을 수 있다고 생각하는 광고를 보여주는 것에 동의하게 됩니다. 저희는 회원님의 개인정보를 이용하여 회원님에게 보여드릴 맞춤형 광고를 결정합니다. 저희는 회원님의 개인정보를 광고주에게 판매하지 않으며, 회원님이 저희에게 특정 허락을 제공하지 않는 한 회원님을 직접 식별할 수 있는 정보(예를 들어 이름, 이메일 주소 또는 기타 연락처 정보)를 광고주에게 공유하지 않습니다. 대신 광고주는 광고를 노출하기를 원하는 타겟과 같은 정보를 저희에게 알려줄 수 있고, 저희는 관심이 있을 만한 사람에게 해당 광고를 노출합니다. 저희는 사람들이 광고주의 콘텐츠와 어떻게 상호작용하고 있는지를 이해할 수 있도록 광고주에게 광고 성과 보고서를 제공합니다. 본 약관에 따라 맞춤형 광고가 Meta 제품에서 작동하는 방식에 대해 더 알아보려면 아래 제2조를 참조하세요. 저희의 개인정보처리방침 에는 저희가 회원님에게 보여드릴 광고를 결정하고 아래 설명된 기타 모든 서비스를 제공하기 위해 회원님의 개인정보를 어떻게 수집하고 이용하는지가 설명되어 있습니다. 회원님은 또한 관련 Meta 제품의 설정 페이지에서 저희가 회원님의 데이터를 이용하는 방식에 관해 회원님이 선택할 수 있는 개인정보 설정을 언제든지 검토할 수 있습니다. 1. 저희가 제공하는 서비스 저희의 사명은 사람들이 커뮤니티를 이룰 수 있도록 하여 전 세계를 더욱 가까워지게 만드는 것입니다. 저희는 이를 실현하기 위해 회원님에게 아래에 설명된 제품과 서비스를 제공합니다: 맞춤화된 경험을 제공합니다. Facebook 뉴스피드나 저희의 동영상 플랫폼에 표시되는 게시물, 스토리, 이벤트, 광고 및 기타 콘텐츠부터 회원님이 팔로우하는 Facebook 페이지 및 회원님이 이용할 만한 기타 기능(예: Facebook Marketplace, 검색)에 이르기까지 회원님만을 위한 Facebook을 경험하실 수 있습니다. 예를 들어 회원님이 만드는 관계, 회원님이 선택하는 옵션 및 설정 사항, 회원님이 제품 내외에서 공유하고 활동하는 사항과 같은 데이터를 이용하여 회원님의 경험을 맞춤화합니다. 회원님을 회원님에게 중요한 사람 및 단체와 연결합니다. 저희는 회원님이 이용하는 여러 Meta 제품에서 회원님에게 중요한 사람, 그룹, 비즈니스, 단체 및 다양한 다른 사항들을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님과 다른 사람들에게 제안(예: 가입할 그룹, 참석할 이벤트, 팔로우하거나 메시지를 보낼 Facebook 페이지, 시청할 프로그램 및 친구를 맺고 싶을 만한 사람 제안)하기 위해 데이터를 이용합니다. 더 친밀한 관계는 더 나은 커뮤니티를 만듭니다. 저희는 사람들이 본인이 관심 있는 사람, 그룹 및 단체와 연결될 때 저희 서비스가 가장 가치 있다고 믿습니다. 회원님이 자신을 표현하고 회원님이 중요하게 생각하는 것을 나눌 수 있도록 합니다. Facebook에서 회원님이 자신을 표현하고, 중요하게 생각하는 것을 친구와 가족, 다른 사람들과 나누는 방법에는 여러 가지(예: 여러 Meta 제품에서 회원님의 설정에 따라 상태 업데이트, 사진, 동영상 및 스토리 공유, 친구 또는 여러 사람에게 메시지 전송, 음성 또는 영상 통화 걸기, 이벤트 또는 그룹 생성, 프로필에 콘텐츠 추가, 다른 사람이 회원님의 콘텐츠에 참여하는 방식에 관한 인사이트 표시)가 있습니다. 또한 저희는 사람들이 증강 현실 및 360도 동영상과 같은 기술을 이용하여 Meta 제품에서 더욱 풍부하고 흥미로운 콘텐츠를 만들고 공유할 수 있도록 새로운 방법들을 개발해 왔고 또 계속해서 개발하고 있습니다. 회원님이 관심을 가질 만한 콘텐츠, 제품 및 서비스를 찾을 수 있도록 지원합니다. 저희는 Facebook 및 기타 Meta 제품을 이용 중인 많은 비즈니스와 단체가 제공하는 콘텐츠, 제품 및 서비스를 발견하는 데 도움이 되는 맞춤형 광고, 제안 및 기타 광고 콘텐츠 또는 커머스 콘텐츠를 회원님에게 보여드립니다. 자세한 내용은 아래 제2조를 참조하시기 바랍니다. 저희 서비스의 안전, 보안 및 무결성을 향상하고, 유해 행위를 방지하고, 사용자 커뮤니티를 안전하게 보호합니다. 사람들은 자신이 안전하고 보호받고 있다고 느껴야만 Meta 제품에서 커뮤니티를 형성합니다. 저희는 저희 제품 및 서비스의 보안(가용성, 신뢰성, 무결성 및 기밀성 포함)을 유지하기 위해 노력합니다. 저희는 전 세계에 전담팀을 두고 외부 서비스 제공업체, 파트너 및 관련 단체와 협업하며 저희 제품의 잠재적 오용, 타인에 대한 유해 행위, 그리고 저희의 잠재적인 위반 콘텐츠 사용자 신고에 대한 응답을 포함하여 저희가 저희의 커뮤니티를 지원하거나 보호하는데 도움이 될 수 있는 상황을 감지하기 위해 최첨단 기술 시스템을 개발합니다. 저희는 이러한 콘텐츠 또는 행위를 발견하는 경우, 저희의 평가를 기반으로 알림 전송, 도움 제공, 콘텐츠 삭제, 특정 기능에 대한 접근 차단 또는 제한, 계정 비활성화 또는 사법당국에 연락 등 적절한 조치를 취할 것입니다. 저희는 저희 제품을 이용하는 사람의 오용 또는 유해 행위를 감지한 경우 또는 Meta 제품, 사용자 및 커뮤니티를 안전하게 보호하기 위해 Meta Companies 사이에 데이터를 공유합니다. 예를 들어, 저희는 금융 상품 및 서비스를 제공하는 Meta Companies와 정보를 공유하여 해당 회사의 안전, 보안, 무결성 향상과 관련 법률 준수를 돕습니다. Meta는 법률에 의해 요구되거나 허용된다는 선의의 믿음이 있는 경우 회원님에 관하여 수집한 정보를 액세스, 보존, 이용 및 공유할 수 있습니다. 자세한 내용은 저희 개인정보처리방침 을 참고하세요. 경우에 따라 감독위원회가 위원회 약관 및 정관에 따라 저희의 결정을 검토할 수 있습니다. 자세한 내용은 여기 에서 알아보세요. 모든 사람에게 안전하고 실용적인 서비스를 제공하기 위해 최첨단 기술을 사용하고 개발합니다. 저희는 사람들이 신체적 능력이나 지리적 위치와 관계없이 안전하게 저희의 제품을 이용할 수 있도록 인공 지능, 머신 러닝 시스템 및 증강 현실과 같은 최첨단 기술을 이용하고 개발하고 있습니다. 예를 들어, 이러한 기술은 시각 장애가 있는 사람들이 Facebook이나 Instagram에서 공유된 사진 또는 동영상에 무엇이 있는지, 누가 있는지 파악할 수 있도록 도움을 줍니다. 또한 인터넷 접속이 원활하지 않은 지역에서도 보다 많은 사람들이 인터넷을 이용할 수 있도록 첨단 네트워크 및 통신 기술을 구축하고 있습니다. 뿐만 아니라 저희는 저희 커뮤니티 및 제품의 무결성을 손상시킬 수 있는 유해하고 위험한 활동을 감지하여 삭제하는 기능을 개선하기 위해 자동화 시스템을 개발합니다. 저희의 서비스를 향상하기 위한 방법을 연구합니다. 저희는 저희 제품의 개발, 테스트 및 개선을 위한 연구를 진행합니다. 여기에는 설문 조사를 실시하고 새로운 기능의 테스트 및 문제 해결을 진행하는 등의 방법으로 저희가 보유한 사용자 데이터를 분석하며, 사람들이 저희의 제품을 이용하는 방식을 이해하는 작업이 포함됩니다. 저희의 개인정보처리방침 에는 저희가 저희 서비스를 개발하고 개선할 목적으로 이 연구를 지원하기 위해 데이터를 이용하는 방식이 설명되어 있습니다. Meta Company 제품 전반에 걸쳐 일관되고 원활한 경험을 제공합니다. 저희의 제품은 회원님에게 중요한 사람, 그룹, 비즈니스, 단체, 다른 사항을 찾고 연결할 수 있도록 지원합니다. 저희는 회원님이 이용하는 다양한 Meta Company 제품 에 걸쳐 일관되고 원활한 경험이 이뤄지도록 저희 시스템을 설계합니다. 예를 들어 회원님이 Facebook에서 소통하는 사람들에 대한 데이터를 이용해 Instagram 또는 Messenger에서도 쉽게 그들과 연결할 수 있도록 지원하며, Messenger를 통해 Facebook에서 팔로우하는 비즈니스와 소통할 수 있도록 지원합니다. 저희 서비스 이용에 대한 보장: 글로벌 서비스를 운영하고 회원님이 전 세계의 사람들과 연결될 수 있도록 하기 위하여, 저희는 회원님의 거주 국가 이외의 지역을 비롯하여 전 세계 데이터 센터, 파트너, 서비스 제공업체, 공급업체 및 시스템에 콘텐츠와 데이터를 이전, 저장, 배포해야 합니다. 저희 서비스를 제공하기 위해서는 본 글로벌 인프라의 이용이 필수적입니다. 이 인프라는 Meta Platforms, Inc., Meta Platforms Ireland Limited 또는 그 계열사가 소유, 운영하거나 통제할 수 있습니다. 2. Meta 서비스를 위한 자금 조달 방식 Facebook과 기타 저희가 제공하는 제품 및 서비스의 사용료를 지불하지 않는 대신, 회원님은 본 약관이 적용되는 Meta 제품을 이용함으로써 비즈니스 및 단체들이 Meta Company 제품 내외에서 홍보를 위해 저희에게 비용을 지불한 맞춤형 광고 및 기타 상업적 콘텐츠와 홍보 콘텐츠를 보게 될 수 있다는 데 동의합니다. 저희는 회원님과 보다 관련성이 높을 수 있는 맞춤형 광고 및 홍보 콘텐츠를 보여드리기 위해 회원님의 활동 및 관심사에 대한 정보 등 회원님의 개인정보를 이용합니다. 개인정보 보호는 저희가 저희의 맞춤형 광고 시스템을 설계할 때 핵심적으로 고려해온 사안입니다. 즉, 저희는 광고주에게 회원님의 신원을 알리지 않고도 회원님에게 회원님과 관련 있고 유용한 광고를 보여드릴 수 있습니다. 저희는 회원님의 개인정보를 판매하지 않습니다. 저희는 광고주로 하여금 저희에게 그들의 비즈니스 목표, 광고 타게팅 대상(예: 사이클링을 좋아하는 18~35세 사이의 사람) 등을 알려줄 수 있도록 합니다. 저희는 그런 다음 해당 광고에 관심이 있을 만하다고 생각하는 사람에게 광고를 노출합니다. 저희는 또한 사람들이 Meta 제품 내외에서 광고주의 콘텐츠와 어떻게 상호작용하고 있는지 광고주들이 이해할 수 있도록 광고주들에게 광고의 성과 보고서를 제공합니다. 예를 들어 광고 타겟을 더 잘 파악할 수 있도록 광고주에게 일반적인 인구 통계학적 특성 및 관심사 정보(예: 마드리드에 거주하고 소프트웨어 엔지니어링을 좋아하는 25~34세 여성이 해당 광고를 보았음)를 제공합니다. 저희는 회원님이 구체적으로 허락하지 않는 한 회원님을 직접적으로 식별할 수 있는 정보(이름 또는 이메일 주소와 같이 그 정보만으로 회원님에게 연락을 취하는 데 이용될 수 있거나 회원님을 식별할 수 있는 정보)를 공유하지 않습니다. 여기 에서 Meta 광고의 작동 원리에 대해 자세히 알아보세요. 저희는 위에 명시된 서비스를 회원님께 제공하기 위해 회원님의 개인정보를 수집하고 이용합니다. 저희의 개인정보처리방침 에서 저희의 데이터 수집 및 이용 방법에 대해 자세히 알아볼 수 있습니다. 회원님은 회원님이 보게 되는 광고와 광고주의 유형, 저희가 회원님에게 보여드릴 광고를 결정하기 위해 이용하는 정보의 유형을 통제할 수 있습니다. 더 알아보기. 3. Facebook 및 커뮤니티에 대한 약속 저희는 저희의 사명을 실현하기 위해 회원님 및 다른 사람들에게 본 서비스를 제공합니다. 이에 대해 회원님은 다음과 같은 약속을 해야 합니다. Facebook을 이용할 수 있는 사람 사람들이 각자의 의견과 행동에 대한 책임을 질 때 Facebook 커뮤니티는 더 안전하고 신뢰할 수 있는 공간이 됩니다. 이러한 이유로 회원님은 다음 사항을 준수해야 합니다. 일상생활에서 사용하는 것과 동일한 이름을 계정에 제공해야 합니다. 회원님에 관한 정확한 정보를 제공해야 합니다. 계정(본인 계정)은 하나만 만들고 개인적인 용도로 이용해야 합니다. 비밀번호를 공유하거나, 회원님의 Facebook 계정에 대한 접근 권한을 다른 사람에게 부 | 2026-01-13T08:49:47 |
https://www.apereo.org/ | The Apereo Foundation | Apereo Foundation Skip to main content Secondary navigation (for desktop) News Software Projects Contact Donate Search Main navigation About Who We Are Values Governance Board of Directors Board Alumni Staff Programs Our Programs Services & Support Software Projects Strategy Incubation Dolphin Awards Community Resources Events Micro Conferences Apereo Conferences Events Calendar Community Our Community Our Community Members Value Proposition Communities of Interest Working Groups Volunteers Newsletter Join Us Why Join Apereo? Community Members Foundation Members Institutional Members Sustaining Members Commercial Members Friends of Apereo Donate Secondary navigation (for mobile) News Software Projects Contact Donate User account menu (for mobile) Log in Breadcrumb Apereo January 2026 Microconference: Deploying AI-Enhanced Student Information System Workflows Using Drupal and ECA via OpenCampus Join Apereo January 14, 2026 for our first Microconference of the year. We have Dr. Kirsten Heiss , Managing Director at OpenCampus and Melissa Mitchell , Head of Business Development and Product Innovation at OpenCampus discussing AI in Student Information Systems. Educational technology, particularly Student Information Systems (SIS), can now leverage integration with all major AI models in every step of ECA (Events - Conditions - Actions) processes to provide dynamic functionality across the complete student life cycle, maximising both automation and adaptability. In this presentation, we will introduce how an open source solution built on Drupal enabled universities to replace their legacy commercial SIS and ERP infrastructure through OpenCampus, and how institutions are now collaborating to create and share solutions within the platform, serving more than 1 million users in the European higher education ecosystem. Read more The Apereo Foundation Apereo: the source for open source in education. The Apereo community develops and delivers open source software solutions used in thousands of educational institutions worldwide. Our members and supporters collaborate to raise awareness and adoption of open initiatives, extending and enhancing teaching and learning, research, and administrative computing. Join the home of open source in education. Recent News The LMS Is a Commodity—So Why Pay (and pay, and pay...) a Premium? In his post, "The LMS is Dead. What Will Replace It?", Alfred Essa poses a critical and often-overlooked question: "What does an LMS actually cost?" For a mid-sized U.S. institution with around 10,000 students, the answer isn't just a licensing fee. As Essa documents, it's a long-term financial commitment that quickly climbs into the hundreds of thousands of dollars annually when you include maintenance, integration, support, and training. Yet, that's only part of the total cost: it's also vendor lock-in that's often too expensive to escape from; it's also the "upsell" that turns the proprietary LMS into a marketing and sales channel for vendors; it's also the forced switching costs resulting from the volatile corporate edtech world of M&A, bankrupcies, and other business disruptions. Goodbye, 2025 — See You in the New Year! As 2025 draws to a close, the Apereo Foundation staff are officially signing off, logging out, and heading into a well-earned holiday break. January 2026 Microconference: Deploying AI-Enhanced Student Information System Workflows Using Drupal and ECA via OpenCampus Join Apereo January 14, 2026 for our first Microconference of the year. We have Dr. Kirsten Heiss , Managing Director at OpenCampus and Melissa Mitchell , Head of Business Development and Product Innovation at OpenCampus discussing AI in Student Information Systems. Educational technology, particularly Student Information Systems (SIS), can now leverage integration with all major AI models in every step of ECA (Events - Conditions - Actions) processes to provide dynamic functionality across the complete student life cycle, maximising both automation and adaptability. In this presentation, we will introduce how an open source solution built on Drupal enabled universities to replace their legacy commercial SIS and ERP infrastructure through OpenCampus, and how institutions are now collaborating to create and share solutions within the platform, serving more than 1 million users in the European higher education ecosystem. All News Platinum Sponsors Apereo Software Projects Footer Join Apereo Communications Donate Membership News Except where otherwise noted, this site and its content are licensed by the Apereo Foundation under the Creative Commons Attribution 4.0 United States License. Some of the content on this site has been generated with the help of ChatGPT. © 2024 Apereo Foundation User account menu (for desktop) Log in | 2026-01-13T08:49:47 |
https://future.forem.com/t/science/page/4 | Science Page 4 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # science Follow Hide General science discussion, news, and its applications. Create Post Older #science posts 1 2 3 4 5 6 7 8 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu OpenAI's GPT-5 Is Here AI News AI News AI News Follow Aug 12 '25 OpenAI's GPT-5 Is Here # ai # productivity # education # science Comments Add Comment 1 min read Bright children from low-income homes lose cognitive edge in early secondary school Science News Science News Science News Follow Aug 12 '25 Bright children from low-income homes lose cognitive edge in early secondary school # education # science # healthtech # biotech Comments Add Comment 1 min read Diets low in carbs and fibre alters gut microbes and drives the growth of colon polyps causing colorectal cancer. Science News Science News Science News Follow Aug 12 '25 Diets low in carbs and fibre alters gut microbes and drives the growth of colon polyps causing colorectal cancer. # science # biotech # genomics # healthtech Comments Add Comment 1 min read Bipartisan Bill to Create a National Quantum Computing Cybersecurity Strategy Quantum News Quantum News Quantum News Follow Aug 12 '25 Bipartisan Bill to Create a National Quantum Computing Cybersecurity Strategy # quantum # security # science # privacy 3 reactions Comments Add Comment 1 min read Kurzgesagt - In a Nutshell: When This Device Lights Up, They’re Coming... Future YouTube Future YouTube Future YouTube Follow Aug 15 '25 Kurzgesagt - In a Nutshell: When This Device Lights Up, They’re Coming... # science # education Comments Add Comment 1 min read The Plough Audit: Before you upgrade the farm, you must first inspect the plough. Favour Daso Favour Daso Favour Daso Follow Sep 11 '25 The Plough Audit: Before you upgrade the farm, you must first inspect the plough. # ai # productivity # education # science 3 reactions Comments 2 comments 3 min read Veritasium: This is the natural disaster to worry about Future YouTube Future YouTube Future YouTube Follow Aug 23 '25 Veritasium: This is the natural disaster to worry about # science # education Comments Add Comment 1 min read Meta's prototype headsets show off the future of mixed reality AR/VR News AR/VR News AR/VR News Follow Aug 8 '25 Meta's prototype headsets show off the future of mixed reality # arvr # wearables # science # manufacturing Comments Add Comment 1 min read How to Become a Bio AI Software Engineer? (Community-Maintained) imasystem.engineer imasystem.engineer imasystem.engineer Follow Sep 9 '25 How to Become a Bio AI Software Engineer? (Community-Maintained) # ai # biotech # science # education 2 reactions Comments Add Comment 1 min read ChatGPT will ‘better detect' mental distress after reports of it feeding people's delusions AI News AI News AI News Follow Aug 7 '25 ChatGPT will ‘better detect' mental distress after reports of it feeding people's delusions # ai # healthtech # science # privacy Comments Add Comment 1 min read Grok generates fake Taylor Swift nudes without being asked AI News AI News AI News Follow Aug 7 '25 Grok generates fake Taylor Swift nudes without being asked # ai # privacy # security # science Comments Add Comment 1 min read Student refines 100-year-old math problem, expanding wind energy possibilities Science News Science News Science News Follow Aug 7 '25 Student refines 100-year-old math problem, expanding wind energy possibilities # energy # science # education # manufacturing Comments Add Comment 1 min read Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. Science News Science News Science News Follow Aug 7 '25 Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. # science # healthtech # productivity # education Comments Add Comment 1 min read Mathematicians credited with rescuing quantum computing Quantum News Quantum News Quantum News Follow Aug 7 '25 Mathematicians credited with rescuing quantum computing # science # quantum # nanotech # manufacturing Comments Add Comment 1 min read 'Autofocus' specs promise sharp vision, near or far AR/VR News AR/VR News AR/VR News Follow Aug 7 '25 'Autofocus' specs promise sharp vision, near or far # wearables # healthtech # science # nanotech Comments Add Comment 1 min read How to Become a Biotech Software Engineer? (Community-Maintained) imasystem.engineer imasystem.engineer imasystem.engineer Follow Sep 9 '25 How to Become a Biotech Software Engineer? (Community-Maintained) # ai # biotech # career # science 2 reactions Comments Add Comment 1 min read FDA's New Drug Approval AI Is Generating Fake Studies: Report AI News AI News AI News Follow Aug 5 '25 FDA's New Drug Approval AI Is Generating Fake Studies: Report # ai # healthtech # biotech # science Comments Add Comment 1 min read Cheyenne to host massive AI data center using more electricity than all Wyoming homes combined AI News AI News AI News Follow Aug 5 '25 Cheyenne to host massive AI data center using more electricity than all Wyoming homes combined # ai # energy # edgecomputing # science Comments Add Comment 1 min read ChatGPT will ‘better detect' mental distress after reports of it feeding people's delusions AI News AI News AI News Follow Aug 5 '25 ChatGPT will ‘better detect' mental distress after reports of it feeding people's delusions # ai # healthtech # science # productivity Comments Add Comment 1 min read Conservatives are more receptive to AI-generated recommendations than liberals, study finds AI News AI News AI News Follow Aug 5 '25 Conservatives are more receptive to AI-generated recommendations than liberals, study finds # ai # science # autonomy # productivity Comments Add Comment 1 min read Humans breathe in more than 70,000 microplastic particles every day, new research suggests Science News Science News Science News Follow Aug 5 '25 Humans breathe in more than 70,000 microplastic particles every day, new research suggests # science # nanotech # healthtech # biotech Comments Add Comment 1 min read Heavy drinking raises the risk of pregnancy by 50% in women who strongly wish to avoid it, while cannabis use does not Science News Science News Science News Follow Aug 5 '25 Heavy drinking raises the risk of pregnancy by 50% in women who strongly wish to avoid it, while cannabis use does not # science # healthtech # biotech # genomics Comments Add Comment 1 min read Bitter fight over 2020 Microsoft quantum paper both resolved and unresolved Quantum News Quantum News Quantum News Follow Aug 5 '25 Bitter fight over 2020 Microsoft quantum paper both resolved and unresolved # science # quantum # nanotech # manufacturing Comments Add Comment 1 min read Bitter fight over 2020 Microsoft quantum paper continues Quantum News Quantum News Quantum News Follow Aug 5 '25 Bitter fight over 2020 Microsoft quantum paper continues # science # quantum # nanotech # manufacturing Comments Add Comment 1 min read A Quantum Gravimeter for GPS Backup - An Australian ship navigated for six days using the device Quantum News Quantum News Quantum News Follow Aug 5 '25 A Quantum Gravimeter for GPS Backup - An Australian ship navigated for six days using the device # quantum # science # autonomy # iot 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://future.forem.com/bobjiang/awesome-robots-digest-issue-14-december-12-2025-44ih | Awesome Robots Digest - Issue #14 - December 12, 2025 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Bob Jiang | awesomerobots Posted on Dec 16, 2025 • Originally published at awesomerobots.xyz Awesome Robots Digest - Issue #14 - December 12, 2025 # digest # newsletter # robotics # ai 🤖 Originally published on Awesome Robots This article is part of our comprehensive coverage of AI robotics developments. Visit awesomerobots.xyz for the latest robot reviews, buying guides, and industry analysis. TL;DR 📋 Strategic Reorganization: From Theatrical Demos to Operational Reality Enterprise focus on ROI : Robots evaluated on uptime, integration cost, and safety compliance rather than novelty Regulation becomes practical : EU, UK, and Asia release implementation notes for AI safety and autonomous systems Big Tech pivots : Robotics reframed as "embodied AI infrastructure" focusing on software and ecosystems Research matures : Focus on recovery-first policies, constraint-aware planning, and simulation diversity Compliance-ready robotics : Safety and auditability become competitive advantages for 2026 Introduction 🚀 This week felt like a cool-down lap with strategic intent. Fewer headline-grabbing humanoid reveals, more signals about where robotics is actually going in 2026: enterprise adoption, regulation readiness, simulation-heavy development, and AI-native control stacks. The ecosystem is quietly reorganizing itself for the next phase — and that phase looks far more operational than theatrical. For builders, DevRel leads, and ecosystem organizers, this week's developments point to clear opportunities: focus on reliability over novelty, design for compliance from day one, and build the infrastructure that connects fragmented robotics capabilities into coherent platforms. Top News & Breakthroughs 📰 🏢 Company News & Industry Developments Enterprises Prioritize "Robot ROI" Over Form Factor Multiple end-of-year briefings from logistics, manufacturing, and facilities-management firms highlighted a clear shift: robots are now evaluated primarily on uptime, integration cost, and safety compliance, not novelty. Mobile manipulators, AMRs (Autonomous Mobile Robots), and task-specific robots dominated reported deployments, while humanoids were largely framed as long-term R&D bets. Key evaluation criteria for enterprise robot adoption: Uptime and reliability : Mean time between failures (MTBF) as primary metric Integration cost : Total cost of ownership including setup, training, and maintenance Safety compliance : Adherence to existing workplace safety standards Workflow compatibility : Ability to slot into existing operational processes Support and maintenance : Availability of local support and spare parts Deployment patterns observed: Logistics facilities : AMRs for material transport with focus on fleet coordination Manufacturing : Collaborative robots (cobots) for assembly with quick changeover capability Facilities management : Mobile manipulators for inspection and light maintenance Warehousing : Picking robots optimized for specific product categories Why it matters: This validates a trend we've been tracking since Issue #10 — real revenue is accruing to robots that slot cleanly into existing workflows. The market is maturing beyond pilot programs into production deployments at scale. Strategic implications: Hardware differentiation increasingly comes from reliability metrics, not specifications Integration services and support networks become key competitive factors Success stories focus on ROI timelines and productivity gains, not technological firsts 🌐 Regulation & Policy Robotics Regulation Moves From Theory to Practice Policy groups in the EU, UK, and parts of Asia released late-stage drafts or implementation notes tied to AI safety, autonomous systems, and public-space robotics. This marks a critical transition from aspirational frameworks to enforceable requirements. Key regulatory themes emerging: 1. Mandatory Logging & Auditability Black-box recording requirements for autonomous decision-making Retention periods for operational data (typically 6-12 months) Standardized data formats for regulatory inspection Privacy-preserving logging mechanisms for public-facing robots 2. Clear Human Override Mechanisms Emergency stop requirements accessible to non-technical users Graduated control handoff procedures Fail-safe modes with predictable behavior Communication protocols for human-robot coordination 3. Cybersecurity Requirements for Connected Robots Secure boot and firmware verification Over-the-air (OTA) update security with rollback capability Network segmentation for robot communications Vulnerability disclosure and patch management procedures 4. Public-Space Operation Standards Clear robot identification and contact information Behavior predictability requirements for pedestrian environments Noise and speed limitations based on context Liability and insurance frameworks Why it matters: 2026 will be the year when "compliance-ready robotics" becomes a competitive advantage. Builders who ignore this now will pay for it later. Early movers who design with compliance in mind will face lower friction in deployment and potentially capture regulatory-sensitive markets. Opportunities for builders: Compliance-as-a-service tooling and platforms Audit trail systems and data management solutions Security frameworks purpose-built for robotics Training and certification programs for operators Big Tech Reframes Robotics as "Embodied AI Infrastructure" Rather than flashy robot announcements, large tech players increasingly describe robotics as an extension of AI infrastructure: perception stacks, simulation engines, control abstractions, and fleet management layers. The robot body is treated as one endpoint among many. Infrastructure components emphasized: Perception stacks : Reusable computer vision and sensor fusion pipelines Simulation engines : Physics-based training environments at scale Control abstractions : High-level APIs decoupling task planning from hardware Fleet management : Cloud-native orchestration for robot swarms Data pipelines : Collection, labeling, and model training infrastructure Why it matters: This reframing benefits developers, DevRel teams, and platform builders — the value is shifting toward software, tooling, and ecosystems. Hardware becomes increasingly commoditized while software platforms capture sustainable margins. Platform opportunities: Developer tools for robot application development Simulation-to-real transfer frameworks Cloud robotics platforms with fleet management Marketplace ecosystems for robot capabilities Training data and model repositories Research Spotlight 🔬 📄 Embodied AI Research Converges on Recovery & Generalization This week's notable research themes across new papers and lab talks demonstrate a clear maturation of the field beyond one-shot demonstrations toward robust, deployable systems. Recovery-First Policies Training robots to assume failure is inevitable and to recover gracefully represents a fundamental shift in approach. Key innovations: Explicit failure modeling : Training data includes partial failures and recovery trajectories Graceful degradation : Systems maintain partial capability when full performance is unavailable Self-diagnosis : Robots identify failure modes and select appropriate recovery strategies Human handoff protocols : Clear escalation to human operators when recovery is impossible Research directions: Learning recovery behaviors from demonstration Predicting failure likelihood from sensor data Multi-stage recovery strategies for complex failures Transfer learning across failure modes Practical applications: Long-horizon manipulation tasks (assembly, cooking, logistics) Outdoor navigation in unpredictable environments Human-robot collaboration with variable human behavior Critical infrastructure inspection with high reliability requirements Constraint-Aware Planning Integrating physical, safety, and task constraints directly into planning models rather than treating them as post-hoc filters. Key innovations: Physics-informed planning : Constraint satisfaction embedded in neural architectures Safety-by-construction : Provable guarantees for critical safety properties Task-conditioned optimization : Dynamic constraint prioritization based on objectives Real-time constraint adaptation : Adjusting to changing environmental conditions Benefits: Reduced planning time through constraint pruning Improved safety through guaranteed constraint satisfaction Better generalization to novel scenarios Interpretable failure modes when constraints conflict Simulation Diversity Over Model Size Smaller models trained across broader simulated environments outperform larger, brittle ones trained in narrow conditions. Key findings: Domain randomization depth : Variation in physics, sensors, and task parameters matters more than model capacity Curriculum diversity : Progressive difficulty across varied scenarios builds robust policies Sim-to-real gap closure : Diverse simulation training reduces need for real-world fine-tuning Computational efficiency : Smaller models enable edge deployment and faster iteration Why it matters: The field is moving past "can it do the task once?" toward "can it do the task reliably under variation?" This shift aligns research incentives with deployment requirements and narrows the gap between academic demonstrations and commercial applications. Implications for practitioners: Invest in simulation infrastructure and environment diversity Prioritize robustness metrics over peak performance Design for recovery and failure handling from the start Collect diverse training data representing real-world variation Product & Hardware Updates 🚀 🔧 Incremental Hardware Improvements Dominate This week saw continued focus on practical hardware improvements that directly address customer pain points: Force-Torque Sensing: Higher sensitivity for delicate manipulation tasks Improved noise rejection for reliable detection Faster sampling rates for responsive control Better integration with standard robot arms AMR Battery Life: Extended runtime through efficient power management Faster charging with minimal battery degradation Hot-swappable battery systems for 24/7 operation Battery health monitoring and predictive maintenance Actuator Design: Quieter operation for office and retail environments Higher power density for payload capacity Improved heat dissipation for continuous operation Better back-drivability for safe human interaction Environmental Protection: Enhanced ingress protection (IP) ratings Temperature range expansion for outdoor operation Corrosion resistance for harsh environments Sealed connectors and cable management Why this matters: These aren't headline features — but they are exactly what buyers ask for. The robotics market is maturing to the point where incremental reliability improvements drive purchasing decisions more than radical new capabilities. 📢 Humanoid Updates Notably Scarce Humanoid hardware updates were notably scarce this week, reinforcing the idea that many teams are regrouping internally, focusing on software, data, and reliability before their next public moves. What this signals: Development phase shift : Companies moving from prototypes to production-ready systems Software bottleneck : Hardware capabilities outpacing autonomous control development Market validation : Teams reassessing business models and target markets Resource optimization : Focus on fewer, higher-quality demonstrations over frequent reveals Expectations for early 2026: More polished demonstrations with clear use cases Emphasis on reliability metrics over raw capabilities Concrete pricing and availability for commercial models Integration partnerships with specific industry verticals Event Horizon 📅 🗓️ Year-End Activity and 2026 Planning Year-end demo days and closed-door reviews are peaking right now. These smaller events — often invite-only — are where serious partnerships are forming. Current event landscape: Private demo days : Companies showcasing deployment-ready systems to select partners Technical reviews : In-depth evaluations for potential customers and investors Standards meetings : Working groups finalizing 2026 specifications Academic-industry workshops : Bridging research advances to commercial applications What's being evaluated: Real-world performance data from multi-month deployments Integration complexity and total cost of ownership Support infrastructure and maintenance requirements Roadmap credibility and team execution capability 📅 2026 Program Opportunities Calls for 2026 programs (accelerators, grants, research collaborations) are opening. Many explicitly prioritize: Robotics + AI Safety Safe human-robot interaction in shared spaces Verification and validation methodologies Fail-safe control architectures Ethics and societal impact assessment Industrial and Service Deployments Real-world deployment case studies Integration with existing infrastructure Workforce transition and training programs Economic impact and productivity analysis Simulation, Digital Twins, and Fleet Operations Scalable simulation platforms for training and testing Digital twin frameworks for predictive maintenance Fleet coordination and task allocation algorithms Cloud robotics architectures and standards 🎯 Opportunities for Community Builders For community builders and DevRel leads, this is an excellent moment to broker introductions and position communities as trusted conveners. High-value activities: Connect academia and industry : Facilitate applied research collaborations Host deployment retrospectives : Share learnings from real-world deployments (not just demos) Organize standards discussions : Bring together stakeholders around common challenges Create evaluation frameworks : Develop shared benchmarks and testing methodologies Build talent pipelines : Connect students and practitioners with deployment opportunities Tool/Resource of the Week 🛠️ 🎯 Featured Resource: Operational Readiness Checklists for Robots An emerging best practice shared across teams this week includes pre-deployment checklists covering critical operational scenarios. This kind of "boring rigor" is becoming essential for professional robotics deployment. Key Checklist Categories: 1. Network Failure Modes Connection Loss Scenarios: Complete network outage behavior (safe stop, local autonomy, or degraded operation) Intermittent connectivity handling (buffering, retry logic, timeout values) Bandwidth degradation strategies (reduced data rates, prioritized messages) Network partition recovery (rejoining fleet, state synchronization) Testing Procedures: Controlled network disconnection during various task phases Latency injection and packet loss simulation Multiple robot coordination under poor network conditions Fallback behavior verification 2. Sensor Degradation Progressive Failure Handling: Camera occlusion or failure (dirt, damage, lighting extremes) Lidar/radar degradation (weather, interference, mechanical wear) IMU drift and calibration loss Force/torque sensor noise and offset Mitigation Strategies: Sensor fusion with graceful degradation Self-diagnosis and health monitoring Alternative perception strategies when primary sensors fail Alert generation and human notification 3. Human-in-the-Loop Escalation Paths Escalation Triggers: Task failure after N retry attempts Uncertain perception or planning (confidence thresholds) Safety-critical situations requiring human judgment Novel scenarios outside training distribution Escalation Procedures: Clear communication of problem and robot state Safe holding behavior while awaiting human input Remote teleoperation capability for resolution Learning from escalation events for future autonomy 4. Update & Rollback Strategies Safe Update Deployment: Staged rollout to subset of fleet A/B testing for performance validation Automatic rollback on failure detection Version compatibility across fleet Operational Continuity: Zero-downtime updates where possible Scheduled maintenance windows for critical updates Backup systems during update process Update verification and validation procedures Why It's Useful: This systematic approach to operational readiness distinguishes professional robotics deployments from research demonstrations. Organizations that implement comprehensive checklists experience: Fewer field failures and emergency recalls Faster incident resolution and recovery Higher customer confidence and satisfaction Lower long-term support costs Getting Started: While not yet packaged as open-source tools, these practices are being documented and shared: Internal deployment guides from successful robotics companies Industry working groups developing standardized frameworks Academic papers on verification and validation methodologies Consulting frameworks from systems integration firms What's Coming: Expect these checklists to evolve into: Open standards for operational readiness (similar to ISO safety standards) Certification schemes for deployment-ready robotics systems Automated testing frameworks and simulation suites Third-party audit and verification services For teams deploying robots in 2026, developing comprehensive operational readiness checklists should be a priority alongside core technology development. Community Corner 👥 💬 Community Sentiment Shifts Developer sentiment continues to shift away from humanoid hype toward deployable systems. Emerging themes in community discussions: "Show Me the Revenue" Increasing skepticism of demo videos without deployment evidence Requests for total cost of ownership (TCO) analysis Interest in customer case studies and retention metrics Questions about unit economics and path to profitability "Boring Robots Win" Appreciation for reliable, unsexy solutions to real problems Recognition that industrial robots are generating actual revenue Interest in middleware, tooling, and integration over novel hardware Focus on operational excellence rather than technological firsts Infrastructure Over Applications Discussions increasingly compare robotics to cloud infrastructure circa 2010 Recognition that the winners won't be the flashiest demos, but the teams that build dependable platforms Interest in developer tools, APIs, and ecosystem plays Comparisons to successful platform businesses in other domains 🌟 Academic-Industry Collaboration Universities report stronger engagement from industry partners seeking students who can ship, not just publish. What industry partners are seeking: Systems thinking : Understanding full deployment lifecycle, not just algorithms Robustness focus : Experience with failure modes and recovery strategies Integration skills : Ability to work with existing systems and constraints Practical experience : Exposure to real-world deployment challenges Successful collaboration models: Embedded internships : Students working on real deployment projects Joint research projects : Industry-sponsored research with clear application paths Shared infrastructure : Companies providing hardware for university research Talent pipelines : Structured programs connecting students to industry roles Benefits for the ecosystem: Faster research-to-deployment timeline More practically-oriented research directions Better-prepared graduates entering the workforce Stronger feedback loop between theory and practice Trends to Watch 🎯 1. Reliability Beats Novelty The market is rewarding robots that work every day, not robots that can do impressive things once. Expect continued focus on uptime, maintenance, and long-term performance. 2. Compliance-by-Design Safety and auditability are now table stakes. Teams that treat compliance as an afterthought will face deployment friction and market access barriers. 3. Software Defines the Robot Bodies change; control stacks and tooling endure. The sustainable competitive advantages in robotics will increasingly come from software platforms, not hardware designs. 4. Simulation Becomes the Main Battleground Data diversity matters more than raw scale. Investment in high-quality, diverse simulation environments will drive the next generation of robust robot policies. 5. Ecosystem Builders Gain Leverage As fragmentation grows, coordination matters. Communities, standards bodies, and platform providers that reduce integration friction will capture outsized value. Conclusion 🎯 Issue #14 captures a moment of strategic reorganization. The robotics field is not pulling back — it's getting serious. The transition from theatrical demonstrations to operational deployment is accelerating, and the winners in 2026 will be those who prioritize reliability, compliance, and ecosystem integration over novelty. For builders: Focus on the boring fundamentals that make robots actually work in production. For researchers: Align work with deployment requirements around robustness and recovery. For ecosystem leaders: Build the connective tissue that turns fragmented capabilities into coherent platforms. The cool-down lap is ending. The serious race is about to begin. 📧 Stay Connected Subscribe: Newsletter signup link Follow us: Twitter (X) links Website: Official Website This digest is curated by the Awesome Robots team. Covering the week of December 5 – December 12, 2025. 🔗 Related Resources Visit Awesome Robots for: 🤖 Latest Robot Reviews 📚 Buying Guides 📰 Industry News 🔍 Robot Catalog Follow us for more robotics content: 🐦 Twitter/X 📧 Newsletter What robots or topics would you like us to cover next? Let us know in the comments! 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 Bob Jiang | awesomerobots Follow Cooking https://awesomerobots.xyz/ , Thrive @EthereumSydney | Advisor of @ScalingX | KB5 of @Kernel0x Work Freelancer Joined Apr 18, 2025 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
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:49:47 |
https://www.nbshare.io | NBShare - Share Your R and Python Notebooks NbShare Nbshare Notebooks Table of Contents Python Utilities How To Install Jupyter Notebook How to Upgrade Python Pip How To Use Python Pip Python Python Datetime Python Dictionary Python Generators Python Iterators and Generators Python Lambda Python Sort List String And Literal In Python 3 Strftime and Strptime In Python Python Tkinter Python Underscore Python Yield Pandas Aggregating and Grouping DataFrame to CSV DF to Numpy Array Drop Columns of DF Handle Json Data Iterate Over Rows of DataFrame Merge and Join DataFrame Pivot Tables Python List to DataFrame Rename Columns of DataFrame Select Rows and Columns Using iloc, loc and ix Sort DataFrame PySpark Data Analysis With Pyspark Read CSV RDD Basics Data Science Confusion Matrix Decision Tree Regression Logistic Regression Regularization Techniques SVM Sklearn Time Series Analysis Using ARIMA Machine Learning How To Code RNN and LSTM Neural Networks in Python PyTorch Beginner Tutorial Tensors Rectified Linear Unit For Artificial Neural Networks Part 1 Regression Stock Sentiment Analysis Using Autoencoders Natural Language Processing Opinion Mining Aspect Level Sentiment Analysis Sentiment Analysis using Autoencoders Understanding Autoencoders With Examples Word Embeddings Transformers In SVM Classifier R DataFrame to CSV How to Create DataFrame in R How To Use Grep In R How To Use R Dplyr Package Introduction To R DataFrames Tidy Data In R A.I. News NbShare Notebooks Publish Your Post On nbshare.io R Python Pandas Data Science Excel NLP Numpy Pyspark Finance --> Upload/ Login Notebooks cannot access local variable a where it is not associated with a value but the value is defined How to Generate Embeddings from a Server and Index Them Using FAISS with API Generating Image Scribbles with Stable Diffusion and ControlNet How to Install Google Chrome on Ubuntu using Command Line Comparison Table DDR5 vs DDR4 vs HBM3 Memory ElasticSearch Empty Reply From Server Error Stock Profit Loss Calculator Standard Deviation Calculator Install and Run Stable Diffusion 2 on Ubuntu Mortgage Calculator Currency Converter Text to CSV Data Table Student T-Value Calculator How To Use Selenium Webdriver To Crawl Websites Calculate Stock Options Max Pain Using Data From Yahoo Finance With Python Pandas Datareader To Download Stocks Data From Google And Yahoo Finance JSON Parse Error Syntax Error Unexpected token N In JSON Pandas group by multiple custom aggregate function on multiple columns Demystifying Stock Options Vega Using Python With Open Statement in Python Generative Adversarial Networks How To Solve Error Numpy Has No Attribute Float In Python Plot Stock Options Vega Implied Volatility Using Python Matplotlib What is LeakyReLU Activation Function Pandas Groupby Count of Rows In Each Group Calculate Implied Volatility of Stock Option Using Python Best Approach To Map Enums to Functions in Python Why do we use Optional ListNode in Python ERROR Could not find a version that satisfies the requirement numpy==1 22 3 Understand Python Slicing Pandas Read and Write Excel File Understand Tensors With Numpy TTM Squeeze Stocks Scanner Using Python How To Append Rows With Concat to a Pandas DataFrame Enable Python Virtual Enviornment in Visual Studio Code on Windows Push Git Repo From Remote Server To Git Auto Indent Python Code In Vim With Yapf gsutil Cheatsheet Crawl Websites Using Python Tweepy AttributeError API object has no attribute search How To Get Measures Of Spread With Python How To Parse Yahoo Finance News Feed With Python COLLATION utf8_unicode_ci is not valid for CHARACTER SET utf8mb4 Join or Merge Lists In Python Numpy Array vs Vector PySpark Substr and Substring PySpark Replace Values In DataFrames ImportError cannot import name Iterabler from collections python 3-10 How To Use Jquery In Typescript PySpark concat_ws Pyspark Expr Example PySpark Lit Example PySpark Distinct Examples Save Pandas DataFrame as CSV file Write Single And Multi Line Comments In Python PySpark GroupBy Examples Install PySpark With MongoDB On Linux Return Multiple Values From a Function in Python Set Operations In Python Amazon Review Summarization Using GPT-2 And PyTorch Stock Charts Detection Using Image Classification Model ResNet Python Type Isinstance Python Numpy Where Movie Name Generation Using GPT-2 Tweet Sentiment Analysis Using LSTM With PyTorch English to German Translation using Seq2Seq Models In PyTorch PyTorch Tutorial A Complete Use Case Example Python Is Integer | 2026-01-13T08:49:47 |
https://future.forem.com/t/science/page/7 | Science Page 7 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # science Follow Hide General science discussion, news, and its applications. Create Post Older #science posts 1 2 3 4 5 6 7 8 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 8 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' AI News AI News AI News Follow Jul 8 '25 Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' # ai # employment # science # productivity Comments Add Comment 1 min read Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' AI News AI News AI News Follow Jul 7 '25 Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' # ai # employment # science # productivity Comments Add Comment 1 min read The Senate Just Put Clean Energy for AI in the Crosshairs AI News AI News AI News Follow Jul 7 '25 The Senate Just Put Clean Energy for AI in the Crosshairs # energy # solar # ai # science Comments Add Comment 1 min read A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' AI News AI News AI News Follow Jul 7 '25 A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' # ai # security # science # privacy Comments Add Comment 1 min read Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team AI News AI News AI News Follow Jul 7 '25 Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team # ai # science # employment # autonomy Comments Add Comment 1 min read Proof that adult brains make new neurons settles scientific controversy Science News Science News Science News Follow Jul 7 '25 Proof that adult brains make new neurons settles scientific controversy # science # biotech # genomics # healthtech Comments Add Comment 1 min read OpenAI's GPT-5 Is Here AI News AI News AI News Follow Aug 8 '25 OpenAI's GPT-5 Is Here # ai # productivity # science # autonomy 5 reactions Comments Add Comment 1 min read Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team AI News AI News AI News Follow Jul 2 '25 Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team # ai # employment # science # productivity Comments Add Comment 1 min read Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' AI News AI News AI News Follow Jul 2 '25 Sam Altman Slams Meta's AI Talent Poaching Spree: 'Missionaries Will Beat Mercenaries' # ai # science # employment # autonomy Comments Add Comment 1 min read A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' AI News AI News AI News Follow Jul 2 '25 A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' # ai # security # privacy # science Comments Add Comment 1 min read Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds Science News Science News Science News Follow Jul 2 '25 Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds # science # healthtech # biotech # education Comments Add Comment 1 min read Protesters accuse Google of violating its promises on AI safety: 'AI companies are less regulated than sandwich shops' AI News AI News AI News Follow Jul 2 '25 Protesters accuse Google of violating its promises on AI safety: 'AI companies are less regulated than sandwich shops' # ai # security # privacy # science Comments Add Comment 1 min read A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' AI News AI News AI News Follow Jul 2 '25 A Pro-Russia Disinformation Campaign Is Using Free AI Tools to Fuel a ‘Content Explosion' # ai # security # privacy # science Comments Add Comment 1 min read Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team AI News AI News AI News Follow Jul 2 '25 Here Is Everyone Mark Zuckerberg Has Hired So Far for Meta's ‘Superintelligence' Team # ai # science # employment # autonomy Comments Add Comment 1 min read Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years Science News Science News Science News Follow Jul 2 '25 Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years # science # energy # solar # education Comments Add Comment 1 min read Control of spin qubits at near absolute zero a game changer for quantum computers Quantum News Quantum News Quantum News Follow Jul 1 '25 Control of spin qubits at near absolute zero a game changer for quantum computers # quantum # science # nanotech # manufacturing Comments Add Comment 1 min read ChatGPT is bringing back 4o as an option because people missed it AI News AI News AI News Follow Aug 12 '25 ChatGPT is bringing back 4o as an option because people missed it # ai # productivity # education # science 4 reactions Comments 1 comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 7 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science 5 reactions Comments Add Comment 1 min read Veritasium: The Perfect Battery Material Is DANGEROUS Future YouTube Future YouTube Future YouTube Follow Aug 15 '25 Veritasium: The Perfect Battery Material Is DANGEROUS # science # education Comments 1 comment 1 min read OpenAI Scrambles to Update GPT-5 After Users Revolt AI News AI News AI News Follow Aug 12 '25 OpenAI Scrambles to Update GPT-5 After Users Revolt # ai # science # productivity # education Comments 1 comment 1 min read Overfishing has caused cod to halve in body size since 1990s, study finds Science News Science News Science News Follow Jun 26 '25 Overfishing has caused cod to halve in body size since 1990s, study finds # science Comments Add Comment 1 min read Heart attacks are no longer the leading cause of death in the US Science News Science News Science News Follow Jun 26 '25 Heart attacks are no longer the leading cause of death in the US # science Comments Add Comment 1 min read Believing "news will find me" is linked to sharing fake news, study finds Science News Science News Science News Follow Jun 25 '25 Believing "news will find me" is linked to sharing fake news, study finds # science Comments Add Comment 1 min read Study shows that hope may be even more essential to well-being than happiness or gratitude Science News Science News Science News Follow Jun 23 '25 Study shows that hope may be even more essential to well-being than happiness or gratitude # science 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://docs.suprsend.com/changelog?_gl=1*12fhh1c*_gcl_au*MTk4MjY1MzcwOC4xNzM3MjcwMDQwLjE2MTg0OTAwOC4xNzQyNDY0NTg3LjE3NDI0NjQ1ODY.*_ga*MTEwNDU5MzYxMC4xNzI5NDkxODI3*_ga_PPDYBESP2L*MTc0MjYzMDUxMC4yMDguMS4xNzQyNjMwNjM2LjIuMC4w#what-you-can-do | Product Updates - 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 Changelog Product Updates Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Changelog Product Updates Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Changelog Product Updates OpenAI Open in ChatGPT Logs of all the feature releases, improvements, and bug fixes in SuprSend. OpenAI Open in ChatGPT 18 December 2025 Hosted Preference Page — Modern Design with Multi-Language Support The hosted preference page has been updated with a refreshed UI and locale-aware localization support. Static UI content (CTAs, labels, system text) is translated automatically using built-in i18n support for up to 23 languages. Dynamic content, including notification category names and descriptions, is rendered using the translation files configured by you, based on the user’s locale. 📘 Checkout hosted preference page documentation and see how translations work 3 December 2025 Category Translations for Preference Centers Reach users worldwide with category translations — show your preference centers in your users’ native language. Whether your users speak Spanish, French, German, or any other language, they’ll see category names and descriptions in their preferred locale, making it easier for them to understand and manage their notification preferences. What you get: Multi-language support : Upload translations via Dashboard, API, or CLI — choose the method that works best for your workflow Smart fallbacks : If a translation isn’t available for a specific locale (e.g., es-AR ), we automatically try the base locale ( es ), then fall back to English — your users always see something meaningful Zero maintenance : English translations are automatically generated from your category names and descriptions, so you don’t need to manage them separately 📘 Learn more in the category translations documentation . 1 December 2025 📚 S3 Connector v2.0 — Comprehensive Notification Data Export S3 Connector v2.0 exports end-to-end notification data to your S3 bucket, giving you full visibility into requests, workflows, and message delivery for analytics, debugging, and compliance. It replaces the limited v1.0 connector with complete, structured logging. S3 Connector v1.0 will be deprecated over time. Migrate to v2.0 to access full logs and notification analytics. What’s New We’ve added 3 data points for end-to-end traceability of notifications from API request → workflow execution → final delivery : Messages: Delivery status, engagement metrics, vendor responses, and failures Workflow Executions: Step-by-step workflow logs for debugging conditions, preferences, and errors Requests: API payloads and responses for trigger-level debugging and audit trails Use Cases Internal analytics or customer-facing analytics Debug delivery and workflow issues using detailed logs or show logs on your customer portal Maintain audit trails for compliance and internal reporting Query and analyze notification data you fully own 📘 Check out the S3 Connector v2.0 documentation for more details. 29 November 2025 Channel-Level Control for Preference Categories Choose which channels users are opted into by default when setting up preference categories. You can use this to have preference category defaults as user gets in-app notification by default and other channels will be sent only if user explicitly opts in to them. 📘 Learn more in the preference categories documentation . 31 October 2025 Type-Safe Workflow Triggers Catch payload errors at compile time and get IDE autocomplete for workflow payloads and event properties using generated type definitions. Define your payload structure once using SuprSend JSON schemas , and automatically generate type definitions using SuprSend CLI . What’s Included and Why This Matters Prevents production bugs caused by invalid payloads Keeps backend code and notification schemas in sync Get IDE autocomplete, inline validation, and type hints for payload fields Supported languages: TypeScript, Python, Go, Java, Kotlin, Swift, Dart 📘 Learn more in the type safety & type generation documentation . 30 October 2025 🌍 Translations - One template, all languages, zero hassle Go global with translations — the easiest way to localize your notifications. One template, multiple languages, automatic fallbacks. No more maintaining separate templates for each language. What You Can Do Localize notifications instantly: Smart translation keys → Use {{t "key"}} syntax in templates and let SuprSend handle the rest Automatic fallbacks → Users always get a translation, even if their exact locale isn’t available Dynamic content → Pass variables like {{t "key" name=user.first_name}} for personalized content Pluralization → Automatic handling of singular/plural forms based on count Manage translations like code: Upload, download, edit → Work with translation files locally or in the dashboard Version control → Complete history tracking with one-click rollbacks CLI & API support → Manage translations programmatically or via command line Built for developers: Namespaced keys → {{t "feature:key"}} to avoid conflicts across features JSONNET support → Complex conditional logic for advanced use cases Handlebars integration → Combine with other helpers for dynamic content Version control for translations → Track changes, maintain history, and roll back when needed 📘 Check out the translation documentation to get started. 1 October 2025 Preference Category Management APIs You can now programmatically create, update, and commit preference categories using the Management APIs — no dashboard required. This makes it easy to integrate category management into your existing workflows, scripts, and deployment pipelines. 👉 Also available via the SuprSend CLI . 📘 See the API documentation to get started. 29 September 2025 🚀 SuprSend CLI Beta - Ship Notification changes like code We’re excited to announce the public beta of SuprSend CLI , bringing full notification management to your terminal. Using CLI, you can manage and promote assets across workspaces, integrate with CI/CD, and treat notification changes just like code. What You Can Do Promote assets across workspaces — move workflows, schemas, events, and categories between environments (e.g., staging → production) with suprsend sync or targeted pull/push commands. Automate with CI/CD Deployment – Release notification changes through feature or bugfix branches, just like any other piece of code: version it, test it, and deploy it. Manage notification changes in Git — pull assets locally, version them alongside your application code, and push updates as feature branches or bugfix releases. Treat notification infrastructure just like code — review, branch, merge, and release with the same version control workflows you already use. Built for developers Code reviews for notifications — keep your notification infrastructure in Git, track changes, and roll back when needed. Approval gates for production — ensure no change goes live without review and approval. Work with assets locally — create, edit, and test workflows, schemas, and translation files on your machine. Version control & rollback — maintain change log and safely revert changes when required. This is a beta release — we’re actively gathering feedback and making improvements. So, feel free to report an issue and contribute to the project. 📘 Check out the CLI documentation to get started. 29 September 2025 🤖 SuprSend MCP Server (Beta) — AI-Powered Notification Management Your AI agents, copilots, and LLM tools can now directly interact with SuprSend through natural language, making notification management as simple as having a conversation. What You Can Do with SuprSend MCP Everyday workflows with AI: Trigger workflows on demand “Run the approval-required workflow for user John Doe to test my setup.” Bootstrap test data “Create a sample user named John Doe and a tenant called acme-corp in my workspace.” Manage preferences “Enable email notifications for marketing and disable SMS.” Configure branding “Update the logo and primary color for the enterprise tenant.” Vibe-code with AI: Ask AI to fetch setup guides, code examples, or integration snippets directly from SuprSend docs and apply it in your application code. Expose safe, scoped endpoints (via MCP) that wrap APIs with context, reducing guesswork and hallucinations. Integrate with LLM-based assistants (Claude, Copilot, Cursor, Windsurf, etc.) to simplify notification setup with SuprSend. Compatible AI Tools Works with Claude, Cursor, Windsurf, and any MCP-compatible AI agent. Notes & Caveats (Beta) - APIs, behavior, or scopes may change based on feedback. We restrict destructive operations (e.g. deletes) initially to reduce risk. We welcome your feedback — report issues and share feedback to help us harden MCP for production. Getting Started Start the MCP server and configure it with your AI tool. See our MCP setup guide for detailed instructions. 12 September 2025 Send Notifications Only to Verified Channels in Sandbox Sandbox workspaces come pre-configured with SuprSend vendors for quick testing. However, we noticed some cases of misuse where test messages were being sent to unintended recipients. To prevent accidental spam and keep Sandbox safe, notifications can now only be sent to verified channels . You can set upto 5 verified channels for each channel type. Reach out to us if you need more. You can add and manage your verified channels from developers -> Verified Channels page . 12 September 2025 Test Mode: Test Notifications safely without sending to real users Testing notifications shouldn’t mean worrying about accidentally pinging your customers. In most companies, teams end up redirecting notifications to shared inboxes like [email protected] or [email protected] just to avoid delivery to real users—while still being able to debug the full notification flow. With Test Mode , you can now replicate this real-world testing flow directly in our platform: Test end-to-end notification flow : Add channels belonging to internal testers as test channels. In test mode, notifications to these channels are delivered normally—so you can preview messages on real devices. Set Up Test Channels : You can add channels belonging to your internal testers as test channels. Delivery will not be blocked for test channels in test mode. This helps you see preview of the notification in your real device. Catch-All Routing : Redirect all non-test notifications to a common channel (e.g., a QA inbox), making it easy to trace and debug every message in one place. This ensures you can confidently test notification workflows in an environment that mirrors production—without the risk of real users getting test messages. 30 August 2025 Validate workflow trigger Payload using JSON Schema We’ve introduced API-level JSON Schema validation for workflow trigger payloads. This catches payload mismatches before execution, preventing runtime failures and ensuring consistent, correct notifications. Why it matters When you trigger a workflow, you pass data (payload) that is used to resolve workflow variables and populate dynamic content in templates. Currently, If the payload does not include all the variables expected in the workflow, the execution may fail at different stages. With this change, Validation will happen at API level and there’ll be: Fewer runtime failures : Stop workflows from starting with missing or malformed data. Faster debugging : Get a clear, structured error list at request time—no more hunting through multi-step logs. More reliable messaging : Prevent partial runs, inconsistent behavior, and incorrect or incomplete notifications. How it works You can add JSON schema from Schema page and then link it to the workflow Trigger step or trigger Event from events page . When you trigger a workflow, the payload is validated against a JSON Schema that describes the expected data used to resolve variables and populate dynamic content. If the payload doesn’t match the schema, the Trigger API returns error response with a list of validation errors (e.g., path, expected type, missing fields). If validation passes, the workflow proceeds as usual. Fixes and Improvements: Workflow slug validation at the API layer: If a referenced workflow slug isn’t available, the error is now returned directly in the API response (in addition to request logs) for faster debugging. This validation will only apply to new workflows created after this change. If you want to apply it all your existing workflows, reach out to SuprSend support. 23 August 2025 Tenancy social links update Added support for TikTok in tenant social_links . Twitter renamed to x in descriptions and examples (field name remains compatible as per API changes). Updated social link icons for better visual consistency. 19 August 2025 Message logs revamp Redesigned UI for seamless tracking of notification lifecycles. Quickly view delivery status, opens, clicks, and errors across all channels in a single log view. Entity-level visibility : Drill down into logs by workflow, user, object, or list to understand exactly what happened in context. Advanced filtering : Filter logs by status, workflow, template, channel, category, or time range to debug faster. Consistent date range filter across all log pages, making it easier to trace the journey of a notification from request → workflow → final message delivery and it’s interaction state. Fixes and Improvements react-sdk (v0.3.0) - Introduced a custom infinite-scroll component with robust Shadow DOM compatibility. web-components (v0.3.0) - Enhanced Shadow DOM rendering support to ensure component isolation and consistent styling. 16 August 2025 Analytics 2.0 - faster, real-time, with one click filters to drill down into insights Real-time insights → Trends update as messages go out. Track performance across channels and spot dips in engagement instantly. Workflow-level comparisons → Compare workflows, templates, channels, and categories side by side to spot under performers and validate experiments. Know when your users opt-out → See which channels/categories drive opt-outs so you can adjust before churn sets in. Over-messaging trends → Track avg notifications per user, find patterns by category, and identify fatigue triggers to keep communications helpful—not noisy. Granular filtering → Multi-select filters for workflow, tenant, template, channel, category, time range Centralized error tracking → All API, workflow, and provider delivery errors in one place. Filter by tenant/workflow/template/channel, open the exact log, and debug in seconds. 23 July 2025 Sendgrid IP Pool support Enabled creation and management of SendGrid IP Pools, allowing granular control over email delivery, IP reputation, and segmentation of email traffic base on notification category. Fixes and Improvements Added support to send slack messages using broadcast. 11 July 2025 Workflow Management APIs Released comprehensive Management APIs to programmatically create, update, and commit workflows. Supports dynamic workflow orchestration — from your platform or third-party systems — to automate creation and modification of workflows from your codebase. You can checkout the documentation here . 4 July 2025 Proxy support in Java SDK Java SDK can now route outbound requests through HTTP/S proxies, enabling deployments behind corporate firewalls and network controls. 16 June 2025 iOS Native SDK Revamp with JWT based authentication & Preferences support The new iOS SDK now has our latest JWT authentication. You can use it to: JWT-based auth for secure event ingestion, profile updates and push token management. Support to add In-app Preferences Center in mobile apps with UI and example code available for quick setup. Fixes and Improvements Flutter sdk released (v2.5.0) - Fixed an Android push client issue and added silent push support for background updates. 22 May 2025 Role based auth in AWS SNS In line with our ongoing efforts to enhance platform security, we’ve also enabled IAM Role- based auth in AWS SNS vendor. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. 13 May 2025 New SMS Vendor: Bird We’ve added support for sending SMS using the new Bird APIs. The setup is straightforward with a simple vendor form to fill to get started, and full integration details are available here. 30 Apr 2025 SuprSend tracked Properties Now Available in Recipients Payload Recipient payloads now include key internal properties—like user type and their unique identifier—making them readily accessible for use in templates and workflows. → For users: {“$type”: “user”, “distinct_id”: “xxxx”} → For objects: {“$type”: “object”, “object_type”: “xxx”, “id”: “xxx”}" Use these properties to pre-fill form values, add conditional branching based on user type, or Create dynamic links using unique user IDs 23 Apr 2025 Workflow Conditions - Array Comparison Operators Now, find an element in array or find intersections between two arrays in workflow conditions. Example Use cases: Send a notification to users whose role is one of ["admin","manager"] Notify tournament followers who have subscribed to any of the playing teams or players. 15 Apr 2025 Introducing Preference Tags Filter notification categories shown to users based on tags like role, team, or department—so Finance sees billing alerts, and Engineers see only error and anomaly categories. You can assign multiple tags to each preference category or section, and define complex logical expressions (e.g. role == “manager” && department in [“sales”, “marketing”]) to dynamically show relevant preference categories per user. Great for building clean, personalized preference centers without bloating the UI. 7 Apr 2025 Documentation Revamp–Cleaner, Smarter, More Interactive We’ve overhauled our documentation experience to make it more consistent, intelligent, and user-friendly: Brand-Aligned UI : The docs now match the look and feel of the SuprSend platform. AI-Powered Search : Get smarter, faster answers with AI-supported search. You can also open documentation directly in ChatGPT or Claude for conversational, AI-driven assistance. Improved Readability : Upgraded UI components provide a cleaner layout and better readability, helping you navigate and understand complex topics more easily. Interactive API Reference : Try out API requests directly from the docs and view live responses in real-time—no need to switch tools. This revamp is part of our ongoing effort to make implementation faster, smoother, and more intuitive for developers. 27 Mar 2025 Cross Lookup User Subscriptions Easily view all of a user’s subscriptions—whether to lists or objects —in one place. The Subscriptions tab on the user details page now provides a centralized view for easier access to user subscriptions. Fixes in workflows UI Resolved an issue where newly published workflow versions wouldn’t appear without a page refresh (introduced after version history was added). Fixed a bug in the test trigger modal where object suggestions incorrectly appeared when switching from API to event trigger. Removed the success metric from delivery nodes where it’s not relevant (except for Smart Delivery Nodes). 20 Mar 2025 Workflow Trigger Overrides Event-Based triggers now support overriding the actor, recipient, tenant, and object—directly within the workflow. This removes the need to resolve recipients in your code, allowing you to pass internal events as-is and dynamically resolve users and related context per workflow. Perfect for use cases like sending a daily digest to tenant admins or notifying internal account managers at a parent company—all from the same event trigger. 15 Mar 2025 Clone content across template versions and languages Editing multi-lingual templates or doing A/B with different template content? Now, rollback to a version or copy designs between different languages by cloning within template. Fixes and Improvements iOS Integration - Fixed the bitcode issue in xcode16 6 Mar 2025 Role based auth in AWS SES and S3 connector In line with our ongoing efforts to enhance platform security, we’ve now enabled IAM Role- based auth in AWS connectors. Previously, authentication required creating an IAM User and sharing long-term access keys. With IAM Role-based auth , you can grant temporary, scoped access without exposing sensitive credentials. Fixes and Improvements Added API name filter in request logs. This will help you drill down logs based on event and workflow name. 27 Feb 2025 In-App Inbox: French translation support The Inbox UI now supports automatic French translation! Just pass language="fr" when initializing the Inbox, and all static content will render in French—no extra setup needed. Available in @suprsend/web-inbox ≥ v0.6.0. More languages coming soon Fixes and Improvements Released suprsend-py-sdk==0.13.0 with latest user and object management APIs. Fixed Email issue where tenant button was not showing cursor clickable on hover. 20 Feb 2025 In-App: Fetch cross tenant feed We’ve recently been hearing multi-tenant use cases where a user belong to multiple tenants and would want to see Inbox feed for all tenants in a single product. e.g., an account manager is handling multiple client accounts and need to see updates or daily reports linked to all their accounts in a single feed. You can now achieve this by passing tenantId = * while initializing the Inbox. SuprSendInbox Copy Ask AI interface ISuprSendInbox { workspaceKey : string distinctId : string | null subscriberId : string | null tenantId ?: "*" ... } 15 Feb 2025 Workflow - Step-by-Step Analytics You can now track consolidated view of users’ workflow journey at each workflow step directly in the workflow graph. Track user entry, exit, drop-offs, branch followed, and node failures. You can also see workflow edit history and compare analytics across different workflow versions and time range. Next up: Deeper analysis into each workflow step - notification engagement (deliver, seen, click), failures, and AI-powered insights. Improvements: Added data centre field in account settings to check where your data centre region. 12 Feb 2025 Batch - Flush First Item Immediately We’ve introduced a new setting in batch processing: Flush First Item in Batch . Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window. This helps you to build leading debounce logic in workflows, where users are notified immediately about critical updates like anomaly alerts, while other alerts are batched and sent at regular intervals until the issue is resolved. You can find this option in batch -> advanced configuration . 07 Feb 2025 Workflow - Relative Delay and Batch window Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload. For instance, send a reminder 30 minutes after a task’s due time or send feedback 5 minutes after an event or webinar. Fixes and Improvements: In Inbox drop-in popover component, we fixed scroll bar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled. In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue. In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bug fix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction. 31 Jan 2025 Nested Objects - Choose the fan out depth Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers. Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions. 🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox). 🔹 Depth 1 → Notify the object’s channels + direct subscribers. 🔹 Depth N → Expand deeper into hierarchical subscriptions as needed. Copy Ask AI "recipients" : [ { "object_type" : "teams" , "id" : "finance" , //optional parameter to define subscription fan-out depth in workflows "$object_subscriptions_query" : { "depth" : 0 } } ] You can use this to build Escalation Workflows or Tiered Customer Support Notifications , send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration. Fixes and Improvements: [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK Added support to trigger multi-lingual templates in broadcast 29 Jan 2025 New handlebars helpers - jsonParse and jsonPath We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor: jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags. jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers. Fixes and Improvements: Opened up merge tag input to support handlebars helper in email merge tags . Added support for handlebars helper in display condition . 27 Jan 2025 List entry/exit events in trigger You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list. This will help you build workflows on user lists like, send series of activation notifications to users who didn’t interact with the product in last 30 days and stop sending when they become active again. Fixes and Improvements: [SDK] We have exposed object management methods in Node SDK 20 Jan 2025 Inbox 2.0 - better authentication, In-App feed component and seen interaction Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed In-App feed component and seamlessly create Full screen or Side sheet Inbox experience. What’s New? ✅ Enhanced Security : We’ve replaced HMAC authentication with stateless JWT authentication for better security. ✅ Drop-in components : You can now quickly build an inbox, including full screen and side sheet feeds, by directly importing UI inbox components that are available in our SDK. ✅ Bring your own toast : If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience. These updates offer greater flexibility, security, and customization—giving you full control over your in-app notification experience. If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK. 15 Jan 2025 Interaction Observer: Seen Tracking in Inbox We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as “seen” when they come in user’s scroll view. 10 Jan 2025 Enhanced Broadcast Observability We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions. Here’s what’s new: Real-time Execution Tracking : Monitor broadcast operations as they happen, ensuring you stay informed every step of the way. Step-by-Step Debugging : View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster. Advanced Filters : Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency-key, and status. Easily identify and analyze failure logs. Detailed Broadcast Summaries : Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs. 5 Jan 2025 Athena database connector We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines. 27 Nov 2024 New workflow node: Invoke Workflow With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow. A common use case is escalation workflows —e.g., if a team member doesn’t take action within a set time frame, the workflow escalates the issue and notifies their manager. This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management. 25 Nov 2024 New workflow node: Update User Profile You can now update recipient or actor profiles directly within a workflow. This feature simplifies user profile management by enabling real-time updates as part of the workflow process. If your have event-based system, where user profile changes are coming as events from your product or a third-party system, you don’t need to convert it into user update APIs in your codebase. Simply send events to SuprSend, and let workflows handle user profile updates seamlessly. Key use cases Event-based user profile updates : Simply send events to SuprSend when user updates their profile in your product or when you are setting custom profile attributes as a side-effect of related action, e.g., in a job board, change user’s application status when employer shortlists the profile. Update user profile based on a workflow step : Common use cases include fetching data during the workflow to update the user profile or updating the profile when a user successfully completes a step. For instance, while the onboarding process, update %completion in user profile when they complete a step. 20 Nov 2024 Update Object subscriptions within workflow You can now dynamically update object subscriptions directly within a workflow. This enhancement eliminates the need for separate API calls for object update, allowing you to manage everything seamlessly within workflows. If you have event-based systems where all asset updates are coming in form of event from your product or third-party systems, you don’t have to consume those events internally and write custom APIs to update individual assets (user, list, object) in SuprSend. Simply send events and let the workflow handle object subscriptions and user profile updates, making SuprSend truly a single API integration. Example use case When someone subscribes to a topic (like a tournament), add them as a subscriber to the corresponding tournament object. Later, just trigger tournament related events to SuprSend and the object will automatically fan out and send notification to all users subscribed to the topic. 17 Nov 2024 New workflow node: Add / Remove user in list You can now dynamically update list users as part of workflow execution. This is a step toward creating user segments based on events or workflow progression, removing the need to call the List Update API separately. Key use cases Event-based segmentation : When an event occurs, trigger notification to the user and simultaneously add them to a list for future updates. e.g., when a user registers for an upcoming event or webinar, you can send them confirmation email and add them to a list to later send further updates related to the event. Workflow Step-based segmentation : Another use case is dynamically adding or removing a user from the list when they complete a workflow step. e.g., in a knowledge series designed to onboard new users, remove a user from the POC list once they complete onboarding steps. 15 Nov 2024 Deletion APIs On customer request, added APIs to dynamically delete entities in SuprSend. Following deletion APIs are added: Delete user profile Delete list Delete tenant/brand Delete Object and Remove object subscription These actions are also available on the dashboard for manual management. Delete function just deletes the asset and their related data, including preferences. It doesn’t have any effect on the historical workflows or broadcasts already executed. While calling the delete function, ensure no active workflows are running for the asset, else the execution will fail. 14 Nov 2024 User Merge API: Merge duplicate users into one Happy to announce user merge API to merge duplicate user identities into a single distinct_id . This is helpful to consolidate user profiles, especially when users interact across different products or transition from anonymous to identified states. Key Use Cases Cross-Product Identity Consolidation : When users interact across multiple products (e.g., different apps or services within your platform), they may have different identifiers for each product which needs to be merged later. Anonymous to Identified Transition : Platforms often track user actions anonymously before sign-up or login. During this period, user actions are typically tracked under an anonymous ID. Upon sign-up, merge the anonymous profile into the newly created identifier to preserve historical data and Associate it with the identified user profile. 11 Nov 2024 User Management APIs Being developer first, we have made significant updates and enhancements to the User APIs for easier user management in SuprSend. Also, subscriber is renamed to users in all APIs to avoid confusion with object subscription. Here’s a list of all the changes: Introduced new APIs to fetch user profile , list users and delete user . User update API endpoint has been changed from /event to /user/{{distinct_id}} . There are 2 separate APIs to create(upsert) and edit user profile. Any addition or changes in existing user properties can be done using user upsert API . For deletion of property or channel, user edit API can be used. This is done to keep user upsert API structure flat and simple, consistent to how you identify user in workflow trigger. Subscriber is renamed to user in all APIs, including user preference APIs. 7 Nov 2024 Objects: Design scalable group notifications We’re excited to introduce a powerful new capability in SuprSend: Objects . Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously. What You Can Do with Objects: Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g. a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g. anomaly notifications) to shared channels. Objects can have it’s own channels and preferences to handle this use case. Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger . A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn’t have information of the users subscribed to that trigger. Maintain hierarchical user relationship with nested object subscription . e.g., sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object. Objects can be easily tested from platform with all object related actions available on SuprSend console. You can programmatically manage objects from your codebase using rest API calls . Support for SDKs coming soon… If there’s any use case in object that you think is missing and needs to be solved, please reach out to our support . 3 Nov 2024 Datetime comparators in workflow conditions You can now compare datetime fields in workflow conditions . This lets you compare two timestamps where values can be: Variable : computed from workflow input data Static : a fixed timestamp (e.g. 2024-01-01T00:00:00Z ) Relative to current timestamp : e.g. “ now ” or “ now+30d ” (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware. 30 Oct 2024 Send node execution log - UI revamp The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list. 29 Oct 2024 Audit Logs To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp. Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings. 22 Oct 2024 Support for customizing header component in Inbox Added support for customizing the header component in inbox SDKs. @suprsend/react-inbox You can now add a custom component to the right side of the header in the inbox popup. This replaces the “Mark all as read” text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer here . @suprsend/web-inbox In web-inbox , you can add an extra icon beside the “Mark all as read” button at the top of the inbox popup using headerIconUrl . You can also execute custom logic when this icon is clicked using headerIconClickHandler . This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation. 16 Oct 2024 Sample Workflow Library With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected] , and we’ll add them in the library! 21 Sep 2024 Deprecated Legacy androidpush methods As part of our ongoing efforts to maintain a robust and up-to-date platform, we’ve made the following deprecations: 1. Legacy FCM API Support Due to Google’s shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support. For more information, please refer to: Firebase Cloud Messaging Migration Guide 2. Xiaomi Push Service Following Xiaomi’s discontinuation of their push service outside mainland China, we have removed support for this feature. For more information, please visit: Xiaomi Developer Documentation We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don’t hesitate to contact our support team. 17 Sep 2024 Subscriber Page Revamp We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more. All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options. 14 Sep 2024 Typeahead autocomplete suggestions for subscribers We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id , email , and phone fields in subscriber profiles. 11 Sep 2024 Inbox - React SDK v3.4.0 This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers. New Features: Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked. This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences. 8 Sep 2024 Slack Text editor We are happy to announce the support of text editor in slack. So, now you won’t have to write complicated JSONNET template for simple text messages. The text editor supports emoji and use handlebars as the templating language. 6 Sep 2024 Web SDK v2.0 We are excited to announce a major update to our @suprsend/web-sdk . This new version brings significant improvements in security, performance, and developer experience. Major Changes Enhanced Authentication System Replaced workspace key-secret method with public API Key and Signed User JWT token Improved security and access control Synchronous Method Calls All methods now return API call status synchronously Enables better error handling and flow control in applications Improved Code Consistency and Developer Experience Renamed library methods and parameters from snake_case to camelCase Added proper IDE suggestions and method descriptions for easier development Breaking Changes Due to the significant improvements, this version introduces breaking changes. Users upgrading from v1.x should review the migration guide carefully. Documentation For a comprehensive list of changes and migration instructions, please refer to our detailed migration guide For users who need to reference the previous version, v1 documentation is still accessible here Feedback We value your feedback and encourage you to try out the new version. If you encounter any issues or have suggestions for improvement, please don’t hesitate to reach out to our support team. Thank you for your continued support and trust in SuprSend! 4 Sep 2024 View and fetch list users We’ve added a List Users tab to the lists page, giving you direct access to view all users in a list. Being API first, the same functionality is also exposed to API. Refer this GET list users API , or checkout: postman collection . API Details: The API returns 20 users per response. You can retrieve additional users by using cursor-based pagination (before and after cursors). 3 Sep 2024 Better delivery tracking in iOS We are excited to announce significant improvements in our latest update, focusing on enhancing delivery tracking for iOS Push notifications. Regardless of the application’s state, you will now experience more reliable and precise delivery tracking. We have rolled out updates for all our major SDKs. To take full advantage of these improvements, please ensure that you update your dependencies promptly. iOS SDK - v1.0.3 React Native SDK - v2.4.0 Flutter SDK - v2.2.0 2 Sep 2024 Web SDK v1.5.1 We have resolved an issue where the SDK would unexpectedly generate an error message whenever the event payload contained specific emojis. This fix ensures that event processing is now stable and reliable, even when such emojis are present. More details here 30 Aug 2024 Improvement in Workflow Listing page Developer testing workflows are now excluded from the Workflow List Page and search results, ensuring a cleaner and more organized workflow listing. These workflows will still be accessible through logs. Enhanced observability of Tenant APIs by displaying request logs on the logs page. This improvement provides better visibility and monitoring of API interactions. 27 Aug 2024 Wait Until - Add Condition on Event Property We’re excited to announce a powerful update to our Wait Until feature! You can now add multiple events and apply conditions on event properties within the Wait Until branch, allowing for more precise event filtering and targeting of the exact event required in your workflow. This is especially useful for scenarios where the same event triggers multiple workflows, and you want to exit or cancel a notification based on user actions. For instance, in a booking reminder workflow, if a user has multiple bookings, you can now match the booking ID of a cancellation event with the original event to ensure correct reminder gets canceled. Key Changes: Add conditions on event properties using a simple key-operator-value expression (e.g. booking_id = 123 ). Add condition on multiple event properties using AND , OR . Apply conditions across multiple events (e.g. avoid sending a notification if a user completes an action or achieves a specific milestone). Refer documentation for details on how to implement wait until node in your workflow. 26 Aug 2024 Enhanced branching capabilities We are excited to announce significant improvements to our branching capabilities . With the addition of more data types, you can now set precise conditions on various inputs within your branches, such as actor, recipient, and tenant properties. This enhancement allows you to tailor your workflows more effectively, ensuring that each journey is as personalized and efficient as possible. If you haven’t yet explored our branching feature, now is a great time to do so. It offers a robust way to construct multi-step journeys within a single workflow. Here are some example use cases where you could use branch: A/B test notification content by splitting cohorts based on user properties like region. Customize digest schedules (immediate, daily, weekly) using key in your trigger data or recipient’s preference. For support ticket requests, adjust who gets alerts, when to send them (immediately or batched), and which channels to use based on the issue’s priority. Define different next steps in an onboarding checklist depending on a user’s completion percentage. Here, you can also fetch completion% just before sending the next reminder. 23 Aug 2024 New SMS Integration: Pinnacle On customer demand, we are live with latest vendor Integration with Pinnacle for SMS. Check out vendor integration documentation for setup details. 20 Aug 2024 List Details Page Key Improvements: New List Details Page: Access all essential information (logs, broadcast runs, list users) and actions for a list (run broadcast, update user) in a single view, making list management much simpler. “Sync Now” button on query page: This will enable you to manually sync list users when required. Coming Soon: List Users Tab and API: We’ll soon be adding a tab to see all list users. The same functionality will also be exposed to hub APIs to | 2026-01-13T08:49:47 |
https://llvm.org/docs/LangRef.html#alloca-instruction | LLVM Language Reference Manual — LLVM 22.0.0git documentation Navigation index next | previous | LLVM Home | Documentation » Reference » LLVM Language Reference Manual Documentation Getting Started/Tutorials User Guides Reference Getting Involved Contributing to LLVM Submitting Bug Reports Mailing Lists Discord Meetups and Social Events Additional Links FAQ Glossary Publications Github Repository This Page Show Source Quick search LLVM Language Reference Manual ¶ Abstract Introduction Well-Formedness Syntax Identifiers String constants High Level Structure Module Structure Linkage Types Calling Conventions Visibility Styles DLL Storage Classes Thread Local Storage Models Runtime Preemption Specifiers Structure Types Non-Integral Pointer Type Pointers with non-address bits Unstable pointer representation Pointers with external state Global Variables Functions Aliases IFuncs Comdats Named Metadata Parameter Attributes Garbage Collector Strategy Names Prefix Data Prologue Data Personality Function Attribute Groups Function Attributes Call Site Attributes Global Attributes Operand Bundles Deoptimization Operand Bundles Funclet Operand Bundles GC Transition Operand Bundles Assume Operand Bundles Preallocated Operand Bundles GC Live Operand Bundles ObjC ARC Attached Call Operand Bundles Pointer Authentication Operand Bundles KCFI Operand Bundles Convergence Control Operand Bundles Deactivation Symbol Operand Bundles Module-Level Inline Assembly Data Layout Target Triple Allocated Objects Object Lifetime Pointer Aliasing Rules Pointer Capture Volatile Memory Accesses Memory Model for Concurrent Operations Atomic Memory Ordering Constraints Floating-Point Environment Behavior of Floating-Point NaN values Floating-Point Semantics Fast-Math Flags Rewrite-based flags Use-list Order Directives Source Filename Type System Void Type Function Type Opaque Structure Types First Class Types Single Value Types Label Type Token Type Metadata Type Aggregate Types Constants Simple Constants Complex Constants Global Variable and Function Addresses Undefined Values Poison Values Well-Defined Values Addresses of Basic Blocks DSO Local Equivalent No CFI Pointer Authentication Constants Constant Expressions Other Values Inline Assembler Expressions Inline Asm Constraint String Asm template argument modifiers Inline Asm Metadata Metadata Metadata Strings ( MDString ) Metadata Nodes ( MDNode ) Specialized Metadata Nodes ‘ tbaa ’ Metadata ‘ tbaa.struct ’ Metadata ‘ noalias ’ and ‘ alias.scope ’ Metadata ‘ fpmath ’ Metadata ‘ range ’ Metadata ‘ absolute_symbol ’ Metadata ‘ callees ’ Metadata ‘ callback ’ Metadata ‘ exclude ’ Metadata ‘ unpredictable ’ Metadata ‘ dereferenceable ’ Metadata ‘ dereferenceable_or_null ’ Metadata ‘ captures ’ Metadata ‘ llvm.loop ’ ‘ llvm.loop.disable_nonforced ’ ‘ llvm.loop.vectorize ’ and ‘ llvm.loop.interleave ’ ‘ llvm.loop.interleave.count ’ Metadata ‘ llvm.loop.vectorize.enable ’ Metadata ‘ llvm.loop.vectorize.predicate.enable ’ Metadata ‘ llvm.loop.vectorize.scalable.enable ’ Metadata ‘ llvm.loop.vectorize.width ’ Metadata ‘ llvm.loop.vectorize.followup_vectorized ’ Metadata ‘ llvm.loop.vectorize.followup_epilogue ’ Metadata ‘ llvm.loop.vectorize.followup_all ’ Metadata ‘ llvm.loop.unroll ’ ‘ llvm.loop.unroll.count ’ Metadata ‘ llvm.loop.unroll.disable ’ Metadata ‘ llvm.loop.unroll.runtime.disable ’ Metadata ‘ llvm.loop.unroll.enable ’ Metadata ‘ llvm.loop.unroll.full ’ Metadata ‘ llvm.loop.unroll.followup ’ Metadata ‘ llvm.loop.unroll.followup_remainder ’ Metadata ‘ llvm.loop.unroll_and_jam ’ ‘ llvm.loop.unroll_and_jam.count ’ Metadata ‘ llvm.loop.unroll_and_jam.disable ’ Metadata ‘ llvm.loop.unroll_and_jam.enable ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_outer ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_inner ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_remainder_outer ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_remainder_inner ’ Metadata ‘ llvm.loop.unroll_and_jam.followup_all ’ Metadata ‘ llvm.loop.licm_versioning.disable ’ Metadata ‘ llvm.loop.distribute.enable ’ Metadata ‘ llvm.loop.distribute.followup_coincident ’ Metadata ‘ llvm.loop.distribute.followup_sequential ’ Metadata ‘ llvm.loop.distribute.followup_fallback ’ Metadata ‘ llvm.loop.distribute.followup_all ’ Metadata ‘ llvm.loop.isdistributed ’ Metadata ‘ llvm.loop.estimated_trip_count ’ Metadata ‘ llvm.licm.disable ’ Metadata ‘ llvm.access.group ’ Metadata ‘ llvm.loop.parallel_accesses ’ Metadata ‘ llvm.loop.mustprogress ’ Metadata ‘ irr_loop ’ Metadata ‘ invariant.group ’ Metadata ‘ type ’ Metadata ‘ callee_type ’ Metadata ‘ associated ’ Metadata ‘ prof ’ Metadata ‘ annotation ’ Metadata ‘ func_sanitize ’ Metadata ‘ kcfi_type ’ Metadata ‘ pcsections ’ Metadata ‘ memprof ’ Metadata ‘ callsite ’ Metadata ‘ noalias.addrspace ’ Metadata ‘ mmra ’ Metadata ‘ nofree ’ Metadata ‘ alloc_token ’ Metadata ‘ stack-protector ’ Metadata ‘ implicit.ref ’ Metadata Module Flags Metadata Synthesized Functions Module Flags Metadata Objective-C Garbage Collection Module Flags Metadata C type width Module Flags Metadata Stack Alignment Metadata Embedded Objects Names Metadata Automatic Linker Flags Named Metadata Dependent Libs Named Metadata ‘ llvm.errno.tbaa ’ Named Metadata ThinLTO Summary Module Path Summary Entry Global Value Summary Entry Function Summary Global Variable Summary Alias Summary Function Flags Calls Params Refs TypeIdInfo Type ID Summary Entry Intrinsic Global Variables The ‘ llvm.used ’ Global Variable The ‘ llvm.compiler.used ’ Global Variable The ‘ llvm.global_ctors ’ Global Variable The ‘ llvm.global_dtors ’ Global Variable Instruction Reference Terminator Instructions ‘ ret ’ Instruction ‘ br ’ Instruction ‘ switch ’ Instruction ‘ indirectbr ’ Instruction ‘ invoke ’ Instruction ‘ callbr ’ Instruction ‘ resume ’ Instruction ‘ catchswitch ’ Instruction ‘ catchret ’ Instruction ‘ cleanupret ’ Instruction ‘ unreachable ’ Instruction Unary Operations ‘ fneg ’ Instruction Binary Operations ‘ add ’ Instruction ‘ fadd ’ Instruction ‘ sub ’ Instruction ‘ fsub ’ Instruction ‘ mul ’ Instruction ‘ fmul ’ Instruction ‘ udiv ’ Instruction ‘ sdiv ’ Instruction ‘ fdiv ’ Instruction ‘ urem ’ Instruction ‘ srem ’ Instruction ‘ frem ’ Instruction Bitwise Binary Operations ‘ shl ’ Instruction ‘ lshr ’ Instruction ‘ ashr ’ Instruction ‘ and ’ Instruction ‘ or ’ Instruction ‘ xor ’ Instruction Vector Operations ‘ extractelement ’ Instruction ‘ insertelement ’ Instruction ‘ shufflevector ’ Instruction Aggregate Operations ‘ extractvalue ’ Instruction ‘ insertvalue ’ Instruction Memory Access and Addressing Operations ‘ alloca ’ Instruction ‘ load ’ Instruction ‘ store ’ Instruction ‘ fence ’ Instruction ‘ cmpxchg ’ Instruction ‘ atomicrmw ’ Instruction ‘ getelementptr ’ Instruction Conversion Operations ‘ trunc .. to ’ Instruction ‘ zext .. to ’ Instruction ‘ sext .. to ’ Instruction ‘ fptrunc .. to ’ Instruction ‘ fpext .. to ’ Instruction ‘ fptoui .. to ’ Instruction ‘ fptosi .. to ’ Instruction ‘ uitofp .. to ’ Instruction ‘ sitofp .. to ’ Instruction ‘ ptrtoint .. to ’ Instruction ‘ ptrtoaddr .. to ’ Instruction ‘ inttoptr .. to ’ Instruction ‘ bitcast .. to ’ Instruction ‘ addrspacecast .. to ’ Instruction Other Operations ‘ icmp ’ Instruction ‘ fcmp ’ Instruction ‘ phi ’ Instruction ‘ select ’ Instruction ‘ freeze ’ Instruction ‘ call ’ Instruction ‘ va_arg ’ Instruction ‘ landingpad ’ Instruction ‘ catchpad ’ Instruction ‘ cleanuppad ’ Instruction Debug Records Intrinsic Functions Variable Argument Handling Intrinsics ‘ llvm.va_start ’ Intrinsic ‘ llvm.va_end ’ Intrinsic ‘ llvm.va_copy ’ Intrinsic Accurate Garbage Collection Intrinsics ‘ llvm.gcroot ’ Intrinsic ‘ llvm.gcread ’ Intrinsic ‘ llvm.gcwrite ’ Intrinsic ‘ llvm.experimental.gc.statepoint ’ Intrinsic ‘ llvm.experimental.gc.result ’ Intrinsic ‘ llvm.experimental.gc.relocate ’ Intrinsic ‘ llvm.experimental.gc.get.pointer.base ’ Intrinsic ‘ llvm.experimental.gc.get.pointer.offset ’ Intrinsic Code Generator Intrinsics ‘ llvm.returnaddress ’ Intrinsic ‘ llvm.addressofreturnaddress ’ Intrinsic ‘ llvm.sponentry ’ Intrinsic ‘ llvm.stackaddress ’ Intrinsic ‘ llvm.frameaddress ’ Intrinsic ‘ llvm.swift.async.context.addr ’ Intrinsic ‘ llvm.localescape ’ and ‘ llvm.localrecover ’ Intrinsics ‘ llvm.seh.try.begin ’ and ‘ llvm.seh.try.end ’ Intrinsics ‘ llvm.seh.scope.begin ’ and ‘ llvm.seh.scope.end ’ Intrinsics ‘ llvm.read_register ’, ‘ llvm.read_volatile_register ’, and ‘ llvm.write_register ’ Intrinsics ‘ llvm.stacksave ’ Intrinsic ‘ llvm.stackrestore ’ Intrinsic ‘ llvm.get.dynamic.area.offset ’ Intrinsic ‘ llvm.prefetch ’ Intrinsic ‘ llvm.pcmarker ’ Intrinsic ‘ llvm.readcyclecounter ’ Intrinsic ‘ llvm.readsteadycounter ’ Intrinsic ‘ llvm.clear_cache ’ Intrinsic ‘ llvm.instrprof.increment ’ Intrinsic ‘ llvm.instrprof.increment.step ’ Intrinsic ‘ llvm.instrprof.callsite ’ Intrinsic ‘ llvm.instrprof.timestamp ’ Intrinsic ‘ llvm.instrprof.cover ’ Intrinsic ‘ llvm.instrprof.value.profile ’ Intrinsic ‘ llvm.instrprof.mcdc.parameters ’ Intrinsic ‘ llvm.instrprof.mcdc.tvbitmap.update ’ Intrinsic ‘ llvm.thread.pointer ’ Intrinsic ‘ llvm.call.preallocated.setup ’ Intrinsic ‘ llvm.call.preallocated.arg ’ Intrinsic ‘ llvm.call.preallocated.teardown ’ Intrinsic Standard C/C++ Library Intrinsics ‘ llvm.abs.* ’ Intrinsic ‘ llvm.smax.* ’ Intrinsic ‘ llvm.smin.* ’ Intrinsic ‘ llvm.umax.* ’ Intrinsic ‘ llvm.umin.* ’ Intrinsic ‘ llvm.scmp.* ’ Intrinsic ‘ llvm.ucmp.* ’ Intrinsic ‘ llvm.memcpy ’ Intrinsic ‘ llvm.memcpy.inline ’ Intrinsic ‘ llvm.memmove ’ Intrinsic ‘ llvm.memset.* ’ Intrinsics ‘ llvm.memset.inline ’ Intrinsic ‘ llvm.experimental.memset.pattern ’ Intrinsic ‘ llvm.sqrt.* ’ Intrinsic ‘ llvm.powi.* ’ Intrinsic ‘ llvm.sin.* ’ Intrinsic ‘ llvm.cos.* ’ Intrinsic ‘ llvm.tan.* ’ Intrinsic ‘ llvm.asin.* ’ Intrinsic ‘ llvm.acos.* ’ Intrinsic ‘ llvm.atan.* ’ Intrinsic ‘ llvm.atan2.* ’ Intrinsic ‘ llvm.sinh.* ’ Intrinsic ‘ llvm.cosh.* ’ Intrinsic ‘ llvm.tanh.* ’ Intrinsic ‘ llvm.sincos.* ’ Intrinsic ‘ llvm.sincospi.* ’ Intrinsic ‘ llvm.modf.* ’ Intrinsic ‘ llvm.pow.* ’ Intrinsic ‘ llvm.exp.* ’ Intrinsic ‘ llvm.exp2.* ’ Intrinsic ‘ llvm.exp10.* ’ Intrinsic ‘ llvm.ldexp.* ’ Intrinsic ‘ llvm.frexp.* ’ Intrinsic ‘ llvm.log.* ’ Intrinsic ‘ llvm.log10.* ’ Intrinsic ‘ llvm.log2.* ’ Intrinsic ‘ llvm.fma.* ’ Intrinsic ‘ llvm.fabs.* ’ Intrinsic ‘ llvm.min.* ’ Intrinsics Comparation ‘ llvm.minnum.* ’ Intrinsic ‘ llvm.maxnum.* ’ Intrinsic ‘ llvm.minimum.* ’ Intrinsic ‘ llvm.maximum.* ’ Intrinsic ‘ llvm.minimumnum.* ’ Intrinsic ‘ llvm.maximumnum.* ’ Intrinsic ‘ llvm.copysign.* ’ Intrinsic ‘ llvm.floor.* ’ Intrinsic ‘ llvm.ceil.* ’ Intrinsic ‘ llvm.trunc.* ’ Intrinsic ‘ llvm.rint.* ’ Intrinsic ‘ llvm.nearbyint.* ’ Intrinsic ‘ llvm.round.* ’ Intrinsic ‘ llvm.roundeven.* ’ Intrinsic ‘ llvm.lround.* ’ Intrinsic ‘ llvm.llround.* ’ Intrinsic ‘ llvm.lrint.* ’ Intrinsic ‘ llvm.llrint.* ’ Intrinsic Bit Manipulation Intrinsics ‘ llvm.bitreverse.* ’ Intrinsics ‘ llvm.bswap.* ’ Intrinsics ‘ llvm.ctpop.* ’ Intrinsic ‘ llvm.ctlz.* ’ Intrinsic ‘ llvm.cttz.* ’ Intrinsic ‘ llvm.fshl.* ’ Intrinsic ‘ llvm.fshr.* ’ Intrinsic ‘ llvm.clmul.* ’ Intrinsic Arithmetic with Overflow Intrinsics ‘ llvm.sadd.with.overflow.* ’ Intrinsics ‘ llvm.uadd.with.overflow.* ’ Intrinsics ‘ llvm.ssub.with.overflow.* ’ Intrinsics ‘ llvm.usub.with.overflow.* ’ Intrinsics ‘ llvm.smul.with.overflow.* ’ Intrinsics ‘ llvm.umul.with.overflow.* ’ Intrinsics Saturation Arithmetic Intrinsics ‘ llvm.sadd.sat.* ’ Intrinsics ‘ llvm.uadd.sat.* ’ Intrinsics ‘ llvm.ssub.sat.* ’ Intrinsics ‘ llvm.usub.sat.* ’ Intrinsics ‘ llvm.sshl.sat.* ’ Intrinsics ‘ llvm.ushl.sat.* ’ Intrinsics Fixed Point Arithmetic Intrinsics ‘ llvm.smul.fix.* ’ Intrinsics ‘ llvm.umul.fix.* ’ Intrinsics ‘ llvm.smul.fix.sat.* ’ Intrinsics ‘ llvm.umul.fix.sat.* ’ Intrinsics ‘ llvm.sdiv.fix.* ’ Intrinsics ‘ llvm.udiv.fix.* ’ Intrinsics ‘ llvm.sdiv.fix.sat.* ’ Intrinsics ‘ llvm.udiv.fix.sat.* ’ Intrinsics Specialized Arithmetic Intrinsics ‘ llvm.canonicalize.* ’ Intrinsic ‘ llvm.fmuladd.* ’ Intrinsic Hardware-Loop Intrinsics ‘ llvm.set.loop.iterations.* ’ Intrinsic ‘ llvm.start.loop.iterations.* ’ Intrinsic ‘ llvm.test.set.loop.iterations.* ’ Intrinsic ‘ llvm.test.start.loop.iterations.* ’ Intrinsic ‘ llvm.loop.decrement.reg.* ’ Intrinsic ‘ llvm.loop.decrement.* ’ Intrinsic Vector Reduction Intrinsics ‘ llvm.vector.reduce.add.* ’ Intrinsic ‘ llvm.vector.reduce.fadd.* ’ Intrinsic ‘ llvm.vector.reduce.mul.* ’ Intrinsic ‘ llvm.vector.reduce.fmul.* ’ Intrinsic ‘ llvm.vector.reduce.and.* ’ Intrinsic ‘ llvm.vector.reduce.or.* ’ Intrinsic ‘ llvm.vector.reduce.xor.* ’ Intrinsic ‘ llvm.vector.reduce.smax.* ’ Intrinsic ‘ llvm.vector.reduce.smin.* ’ Intrinsic ‘ llvm.vector.reduce.umax.* ’ Intrinsic ‘ llvm.vector.reduce.umin.* ’ Intrinsic ‘ llvm.vector.reduce.fmax.* ’ Intrinsic ‘ llvm.vector.reduce.fmin.* ’ Intrinsic ‘ llvm.vector.reduce.fmaximum.* ’ Intrinsic ‘ llvm.vector.reduce.fminimum.* ’ Intrinsic Vector Partial Reduction Intrinsics ‘ llvm.vector.partial.reduce.add.* ’ Intrinsic ‘ llvm.vector.partial.reduce.fadd.* ’ Intrinsic Vector Manipulation Intrinsics ‘ llvm.vector.insert ’ Intrinsic ‘ llvm.vector.extract ’ Intrinsic ‘ llvm.vector.reverse ’ Intrinsic ‘ llvm.vector.deinterleave2/3/4/5/6/7/8 ’ Intrinsic ‘ llvm.vector.interleave2/3/4/5/6/7/8 ’ Intrinsic ‘ llvm.vector.splice.left ’ Intrinsic ‘ llvm.vector.splice.right ’ Intrinsic ‘ llvm.stepvector ’ Intrinsic Experimental Vector Intrinsics ‘ llvm.experimental.cttz.elts ’ Intrinsic ‘ llvm.experimental.get.vector.length ’ Intrinsic ‘ llvm.experimental.vector.histogram.* ’ Intrinsic ‘ llvm.experimental.vector.extract.last.active ’ Intrinsic ‘ llvm.experimental.vector.compress.* ’ Intrinsics ‘ llvm.experimental.vector.match.* ’ Intrinsic Matrix Intrinsics ‘ llvm.matrix.transpose.* ’ Intrinsic ‘ llvm.matrix.multiply.* ’ Intrinsic ‘ llvm.matrix.column.major.load.* ’ Intrinsic ‘ llvm.matrix.column.major.store.* ’ Intrinsic Half Precision Floating-Point Intrinsics ‘ llvm.convert.to.fp16 ’ Intrinsic ‘ llvm.convert.from.fp16 ’ Intrinsic Saturating floating-point to integer conversions ‘ llvm.fptoui.sat.* ’ Intrinsic ‘ llvm.fptosi.sat.* ’ Intrinsic Floating-Point Conversion Intrinsics ‘ llvm.fptrunc.round ’ Intrinsic Convergence Intrinsics Debugger Intrinsics Exception Handling Intrinsics Pointer Authentication Intrinsics Trampoline Intrinsics ‘ llvm.init.trampoline ’ Intrinsic ‘ llvm.adjust.trampoline ’ Intrinsic Vector Predication Intrinsics Optimization Hint ‘ llvm.vp.select.* ’ Intrinsics ‘ llvm.vp.merge.* ’ Intrinsics ‘ llvm.vp.add.* ’ Intrinsics ‘ llvm.vp.sub.* ’ Intrinsics ‘ llvm.vp.mul.* ’ Intrinsics ‘ llvm.vp.sdiv.* ’ Intrinsics ‘ llvm.vp.udiv.* ’ Intrinsics ‘ llvm.vp.srem.* ’ Intrinsics ‘ llvm.vp.urem.* ’ Intrinsics ‘ llvm.vp.ashr.* ’ Intrinsics ‘ llvm.vp.lshr.* ’ Intrinsics ‘ llvm.vp.shl.* ’ Intrinsics ‘ llvm.vp.or.* ’ Intrinsics ‘ llvm.vp.and.* ’ Intrinsics ‘ llvm.vp.xor.* ’ Intrinsics ‘ llvm.vp.abs.* ’ Intrinsics ‘ llvm.vp.smax.* ’ Intrinsics ‘ llvm.vp.smin.* ’ Intrinsics ‘ llvm.vp.umax.* ’ Intrinsics ‘ llvm.vp.umin.* ’ Intrinsics ‘ llvm.vp.copysign.* ’ Intrinsics ‘ llvm.vp.minnum.* ’ Intrinsics ‘ llvm.vp.maxnum.* ’ Intrinsics ‘ llvm.vp.minimum.* ’ Intrinsics ‘ llvm.vp.maximum.* ’ Intrinsics ‘ llvm.vp.fadd.* ’ Intrinsics ‘ llvm.vp.fsub.* ’ Intrinsics ‘ llvm.vp.fmul.* ’ Intrinsics ‘ llvm.vp.fdiv.* ’ Intrinsics ‘ llvm.vp.frem.* ’ Intrinsics ‘ llvm.vp.fneg.* ’ Intrinsics ‘ llvm.vp.fabs.* ’ Intrinsics ‘ llvm.vp.sqrt.* ’ Intrinsics ‘ llvm.vp.fma.* ’ Intrinsics ‘ llvm.vp.fmuladd.* ’ Intrinsics ‘ llvm.vp.reduce.add.* ’ Intrinsics ‘ llvm.vp.reduce.fadd.* ’ Intrinsics ‘ llvm.vp.reduce.mul.* ’ Intrinsics ‘ llvm.vp.reduce.fmul.* ’ Intrinsics ‘ llvm.vp.reduce.and.* ’ Intrinsics ‘ llvm.vp.reduce.or.* ’ Intrinsics ‘ llvm.vp.reduce.xor.* ’ Intrinsics ‘ llvm.vp.reduce.smax.* ’ Intrinsics ‘ llvm.vp.reduce.smin.* ’ Intrinsics ‘ llvm.vp.reduce.umax.* ’ Intrinsics ‘ llvm.vp.reduce.umin.* ’ Intrinsics ‘ llvm.vp.reduce.fmax.* ’ Intrinsics ‘ llvm.vp.reduce.fmin.* ’ Intrinsics ‘ llvm.vp.reduce.fmaximum.* ’ Intrinsics ‘ llvm.vp.reduce.fminimum.* ’ Intrinsics ‘ llvm.get.active.lane.mask.* ’ Intrinsics ‘ llvm.loop.dependence.war.mask.* ’ Intrinsics ‘ llvm.loop.dependence.raw.mask.* ’ Intrinsics ‘ llvm.experimental.vp.splice ’ Intrinsic ‘ llvm.experimental.vp.reverse ’ Intrinsic ‘ llvm.vp.load ’ Intrinsic ‘ llvm.vp.load.ff ’ Intrinsic ‘ llvm.vp.store ’ Intrinsic ‘ llvm.experimental.vp.strided.load ’ Intrinsic ‘ llvm.experimental.vp.strided.store ’ Intrinsic ‘ llvm.vp.gather ’ Intrinsic ‘ llvm.vp.scatter ’ Intrinsic ‘ llvm.vp.trunc.* ’ Intrinsics ‘ llvm.vp.zext.* ’ Intrinsics ‘ llvm.vp.sext.* ’ Intrinsics ‘ llvm.vp.fptrunc.* ’ Intrinsics ‘ llvm.vp.fpext.* ’ Intrinsics ‘ llvm.vp.fptoui.* ’ Intrinsics ‘ llvm.vp.fptosi.* ’ Intrinsics ‘ llvm.vp.uitofp.* ’ Intrinsics ‘ llvm.vp.sitofp.* ’ Intrinsics ‘ llvm.vp.ptrtoint.* ’ Intrinsics ‘ llvm.vp.inttoptr.* ’ Intrinsics ‘ llvm.vp.fcmp.* ’ Intrinsics ‘ llvm.vp.icmp.* ’ Intrinsics ‘ llvm.vp.ceil.* ’ Intrinsics ‘ llvm.vp.floor.* ’ Intrinsics ‘ llvm.vp.rint.* ’ Intrinsics ‘ llvm.vp.nearbyint.* ’ Intrinsics ‘ llvm.vp.round.* ’ Intrinsics ‘ llvm.vp.roundeven.* ’ Intrinsics ‘ llvm.vp.roundtozero.* ’ Intrinsics ‘ llvm.vp.lrint.* ’ Intrinsics ‘ llvm.vp.llrint.* ’ Intrinsics ‘ llvm.vp.bitreverse.* ’ Intrinsics ‘ llvm.vp.bswap.* ’ Intrinsics ‘ llvm.vp.ctpop.* ’ Intrinsics ‘ llvm.vp.ctlz.* ’ Intrinsics ‘ llvm.vp.cttz.* ’ Intrinsics ‘ llvm.vp.cttz.elts.* ’ Intrinsics ‘ llvm.vp.sadd.sat.* ’ Intrinsics ‘ llvm.vp.uadd.sat.* ’ Intrinsics ‘ llvm.vp.ssub.sat.* ’ Intrinsics ‘ llvm.vp.usub.sat.* ’ Intrinsics ‘ llvm.vp.fshl.* ’ Intrinsics ‘ llvm.vp.fshr.* ’ Intrinsics ‘ llvm.vp.is.fpclass.* ’ Intrinsics Masked Vector Load and Store Intrinsics ‘ llvm.masked.load.* ’ Intrinsics ‘ llvm.masked.store.* ’ Intrinsics Masked Vector Gather and Scatter Intrinsics ‘ llvm.masked.gather.* ’ Intrinsics ‘ llvm.masked.scatter.* ’ Intrinsics Masked Vector Expanding Load and Compressing Store Intrinsics ‘ llvm.masked.expandload.* ’ Intrinsics ‘ llvm.masked.compressstore.* ’ Intrinsics Memory Use Markers ‘ llvm.lifetime.start ’ Intrinsic ‘ llvm.lifetime.end ’ Intrinsic ‘ llvm.invariant.start ’ Intrinsic ‘ llvm.invariant.end ’ Intrinsic ‘ llvm.launder.invariant.group ’ Intrinsic ‘ llvm.strip.invariant.group ’ Intrinsic Constrained Floating-Point Intrinsics ‘ llvm.experimental.constrained.fadd ’ Intrinsic ‘ llvm.experimental.constrained.fsub ’ Intrinsic ‘ llvm.experimental.constrained.fmul ’ Intrinsic ‘ llvm.experimental.constrained.fdiv ’ Intrinsic ‘ llvm.experimental.constrained.frem ’ Intrinsic ‘ llvm.experimental.constrained.fma ’ Intrinsic ‘ llvm.experimental.constrained.fptoui ’ Intrinsic ‘ llvm.experimental.constrained.fptosi ’ Intrinsic ‘ llvm.experimental.constrained.uitofp ’ Intrinsic ‘ llvm.experimental.constrained.sitofp ’ Intrinsic ‘ llvm.experimental.constrained.fptrunc ’ Intrinsic ‘ llvm.experimental.constrained.fpext ’ Intrinsic ‘ llvm.experimental.constrained.fcmp ’ and ‘ llvm.experimental.constrained.fcmps ’ Intrinsics ‘ llvm.experimental.constrained.fmuladd ’ Intrinsic Constrained libm-equivalent Intrinsics ‘ llvm.experimental.constrained.sqrt ’ Intrinsic ‘ llvm.experimental.constrained.pow ’ Intrinsic ‘ llvm.experimental.constrained.powi ’ Intrinsic ‘ llvm.experimental.constrained.ldexp ’ Intrinsic ‘ llvm.experimental.constrained.sin ’ Intrinsic ‘ llvm.experimental.constrained.cos ’ Intrinsic ‘ llvm.experimental.constrained.tan ’ Intrinsic ‘ llvm.experimental.constrained.asin ’ Intrinsic ‘ llvm.experimental.constrained.acos ’ Intrinsic ‘ llvm.experimental.constrained.atan ’ Intrinsic ‘ llvm.experimental.constrained.atan2 ’ Intrinsic ‘ llvm.experimental.constrained.sinh ’ Intrinsic ‘ llvm.experimental.constrained.cosh ’ Intrinsic ‘ llvm.experimental.constrained.tanh ’ Intrinsic ‘ llvm.experimental.constrained.exp ’ Intrinsic ‘ llvm.experimental.constrained.exp2 ’ Intrinsic ‘ llvm.experimental.constrained.log ’ Intrinsic ‘ llvm.experimental.constrained.log10 ’ Intrinsic ‘ llvm.experimental.constrained.log2 ’ Intrinsic ‘ llvm.experimental.constrained.rint ’ Intrinsic ‘ llvm.experimental.constrained.lrint ’ Intrinsic ‘ llvm.experimental.constrained.llrint ’ Intrinsic ‘ llvm.experimental.constrained.nearbyint ’ Intrinsic ‘ llvm.experimental.constrained.maxnum ’ Intrinsic ‘ llvm.experimental.constrained.minnum ’ Intrinsic ‘ llvm.experimental.constrained.maximum ’ Intrinsic ‘ llvm.experimental.constrained.minimum ’ Intrinsic ‘ llvm.experimental.constrained.ceil ’ Intrinsic ‘ llvm.experimental.constrained.floor ’ Intrinsic ‘ llvm.experimental.constrained.round ’ Intrinsic ‘ llvm.experimental.constrained.roundeven ’ Intrinsic ‘ llvm.experimental.constrained.lround ’ Intrinsic ‘ llvm.experimental.constrained.llround ’ Intrinsic ‘ llvm.experimental.constrained.trunc ’ Intrinsic ‘ llvm.experimental.noalias.scope.decl ’ Intrinsic Floating Point Environment Manipulation intrinsics ‘ llvm.get.rounding ’ Intrinsic ‘ llvm.set.rounding ’ Intrinsic ‘ llvm.get.fpenv ’ Intrinsic ‘ llvm.set.fpenv ’ Intrinsic ‘ llvm.reset.fpenv ’ Intrinsic ‘ llvm.get.fpmode ’ Intrinsic ‘ llvm.set.fpmode ’ Intrinsic ‘ llvm.reset.fpmode ’ Intrinsic Floating-Point Test Intrinsics ‘ llvm.is.fpclass ’ Intrinsic General Intrinsics ‘ llvm.var.annotation ’ Intrinsic ‘ llvm.ptr.annotation.* ’ Intrinsic ‘ llvm.annotation.* ’ Intrinsic ‘ llvm.codeview.annotation ’ Intrinsic ‘ llvm.trap ’ Intrinsic ‘ llvm.debugtrap ’ Intrinsic ‘ llvm.ubsantrap ’ Intrinsic ‘ llvm.stackprotector ’ Intrinsic ‘ llvm.stackguard ’ Intrinsic ‘ llvm.objectsize ’ Intrinsic ‘ llvm.expect ’ Intrinsic ‘ llvm.expect.with.probability ’ Intrinsic ‘ llvm.assume ’ Intrinsic ‘ llvm.ssa.copy ’ Intrinsic ‘ llvm.type.test ’ Intrinsic ‘ llvm.type.checked.load ’ Intrinsic ‘ llvm.type.checked.load.relative ’ Intrinsic ‘ llvm.arithmetic.fence ’ Intrinsic ‘ llvm.donothing ’ Intrinsic ‘ llvm.experimental.deoptimize ’ Intrinsic ‘ llvm.experimental.guard ’ Intrinsic ‘ llvm.experimental.widenable.condition ’ Intrinsic ‘ llvm.allow.ubsan.check ’ Intrinsic ‘ llvm.allow.runtime.check ’ Intrinsic ‘ llvm.load.relative ’ Intrinsic ‘ llvm.sideeffect ’ Intrinsic ‘ llvm.is.constant.* ’ Intrinsic ‘ llvm.ptrmask ’ Intrinsic ‘ llvm.threadlocal.address ’ Intrinsic ‘ llvm.vscale ’ Intrinsic ‘ llvm.fake.use ’ Intrinsic ‘ llvm.reloc.none ’ Intrinsic Stack Map Intrinsics Element Wise Atomic Memory Intrinsics ‘ llvm.memcpy.element.unordered.atomic ’ Intrinsic ‘ llvm.memmove.element.unordered.atomic ’ Intrinsic ‘ llvm.memset.element.unordered.atomic ’ Intrinsic Objective-C ARC Runtime Intrinsics ‘ llvm.objc.autorelease ’ Intrinsic ‘ llvm.objc.autoreleasePoolPop ’ Intrinsic ‘ llvm.objc.autoreleasePoolPush ’ Intrinsic ‘ llvm.objc.autoreleaseReturnValue ’ Intrinsic ‘ llvm.objc.copyWeak ’ Intrinsic ‘ llvm.objc.destroyWeak ’ Intrinsic ‘ llvm.objc.initWeak ’ Intrinsic ‘ llvm.objc.loadWeak ’ Intrinsic ‘ llvm.objc.loadWeakRetained ’ Intrinsic ‘ llvm.objc.moveWeak ’ Intrinsic ‘ llvm.objc.release ’ Intrinsic ‘ llvm.objc.retain ’ Intrinsic ‘ llvm.objc.retainAutorelease ’ Intrinsic ‘ llvm.objc.retainAutoreleaseReturnValue ’ Intrinsic ‘ llvm.objc.retainAutoreleasedReturnValue ’ Intrinsic ‘ llvm.objc.retainBlock ’ Intrinsic ‘ llvm.objc.storeStrong ’ Intrinsic ‘ llvm.objc.storeWeak ’ Intrinsic Preserving Debug Information Intrinsics ‘ llvm.preserve.array.access.index ’ Intrinsic ‘ llvm.preserve.union.access.index ’ Intrinsic ‘ llvm.preserve.struct.access.index ’ Intrinsic ‘ llvm.protected.field.ptr ’ Intrinsic Abstract ¶ This document is a reference manual for the LLVM assembly language. LLVM is a Static Single Assignment (SSA) based representation that provides type safety, low-level operations, flexibility, and the capability of representing ‘all’ high-level languages cleanly. It is the common code representation used throughout all phases of the LLVM compilation strategy. Introduction ¶ The LLVM code representation is designed to be used in three different forms: as an in-memory compiler IR, as an on-disk bitcode representation (suitable for fast loading by a Just-In-Time compiler), and as a human readable assembly language representation. This allows LLVM to provide a powerful intermediate representation for efficient compiler transformations and analysis, while providing a natural means to debug and visualize the transformations. The three different forms of LLVM are all equivalent. This document describes the human-readable representation and notation. The LLVM representation aims to be light-weight and low-level while being expressive, typed, and extensible at the same time. It aims to be a “universal IR” of sorts, by being at a low enough level that high-level ideas may be cleanly mapped to it (similar to how microprocessors are “universal IR’s”, allowing many source languages to be mapped to them). By providing type information, LLVM can be used as the target of optimizations: for example, through pointer analysis, it can be proven that a C automatic variable is never accessed outside of the current function, allowing it to be promoted to a simple SSA value instead of a memory location. Well-Formedness ¶ It is important to note that this document describes ‘well formed’ LLVM assembly language. There is a difference between what the parser accepts and what is considered ‘well formed’. For example, the following instruction is syntactically okay, but not well formed: %x = add i32 1 , %x because the definition of %x does not dominate all of its uses. The LLVM infrastructure provides a verification pass that may be used to verify that an LLVM module is well formed. This pass is automatically run by the parser after parsing input assembly and by the optimizer before it outputs bitcode. The violations pointed out by the verifier pass indicate bugs in transformation passes or input to the parser. Syntax ¶ Identifiers ¶ LLVM identifiers come in two basic types: global and local. Global identifiers (functions, global variables) begin with the '@' character. Local identifiers (register names, types) begin with the '%' character. Additionally, there are three different formats for identifiers, for different purposes: Named values are represented as a string of characters with their prefix. For example, %foo , @DivisionByZero , %a.really.long.identifier . The actual regular expression used is ‘ [%@][-a-zA-Z$._][-a-zA-Z$._0-9]* ’. Identifiers that require other characters in their names can be surrounded with quotes. Special characters may be escaped using "\xx" where xx is the ASCII code for the character in hexadecimal. In this way, any character can be used in a name value, even quotes themselves. The "\01" prefix can be used on global values to suppress mangling. Unnamed values are represented as an unsigned numeric value with their prefix. For example, %12 , @2 , %44 . Constants, which are described in the section Constants below. LLVM requires that values start with a prefix for two reasons: Compilers don’t need to worry about name clashes with reserved words, and the set of reserved words may be expanded in the future without penalty. Additionally, unnamed identifiers allow a compiler to quickly come up with a temporary variable without having to avoid symbol table conflicts. Reserved words in LLVM are very similar to reserved words in other languages. There are keywords for different opcodes (’ add ’, ‘ bitcast ’, ‘ ret ’, etc…), for primitive type names (’ void ’, ‘ i32 ’, etc…), and others. These reserved words cannot conflict with variable names, because none of them start with a prefix character ( '%' or '@' ). Here is an example of LLVM code to multiply the integer variable ‘ %X ’ by 8: The easy way: %result = mul i32 %X , 8 After strength reduction: %result = shl i32 %X , 3 And the hard way: %0 = add i32 %X , %X ; yields i32:%0 %1 = add i32 %0 , %0 / * yields i32: %1 * / %result = add i32 %1 , %1 This last way of multiplying %X by 8 illustrates several important lexical features of LLVM: Comments are delimited with a ‘ ; ’ and go until the end of line. Alternatively, comments can start with /* and terminate with */ . Unnamed temporaries are created when the result of a computation is not assigned to a named value. By default, unnamed temporaries are numbered sequentially (using a per-function incrementing counter, starting with 0). However, when explicitly specifying temporary numbers, it is allowed to skip over numbers. Note that basic blocks and unnamed function parameters are included in this numbering. For example, if the entry basic block is not given a label name and all function parameters are named, then it will get number 0. It also shows a convention that we follow in this document. When demonstrating instructions, we will follow an instruction with a comment that defines the type and name of value produced. String constants ¶ Strings in LLVM programs are delimited by " characters. Within a string, all bytes are treated literally with the exception of \ characters, which start escapes, and the first " character, which ends the string. There are two kinds of escapes. \\ represents a single \ character. \ followed by two hexadecimal characters (0-9, a-f, or A-F) represents the byte with the given value (e.g., \00 represents a null byte). To represent a " character, use \22 . ( \" will end the string with a trailing \ .) Newlines do not terminate string constants; strings can span multiple lines. The interpretation of string constants (e.g., their character encoding) depends on context. High Level Structure ¶ Module Structure ¶ LLVM programs are composed of Module ’s, each of which is a translation unit of the input programs. Each module consists of functions, global variables, and symbol table entries. Modules may be combined together with the LLVM linker, which merges function (and global variable) definitions, resolves forward declarations, and merges symbol table entries. Here is an example of the “hello world” module: ; Declare the string constant as a global constant. @.str = private unnamed_addr constant [ 13 x i8 ] c "hello world\0A\00" ; External declaration of the puts function declare i32 @puts ( ptr captures ( none )) nounwind ; Definition of main function define i32 @main () { ; Call puts function to write out the string to stdout. call i32 @puts ( ptr @.str ) ret i32 0 } ; Named metadata !0 = !{ i32 42 , null , !"string" } !foo = !{ !0 } This example is made up of a global variable named “ .str ”, an external declaration of the “ puts ” function, a function definition for “ main ” and named metadata “ foo ”. In general, a module is made up of a list of global values (where both functions and global variables are global values). Global values are represented by a pointer to a memory location (in this case, a pointer to an array of char, and a pointer to a function), and have one of the following linkage types . Linkage Types ¶ All Global Variables and Functions have one of the following types of linkage: private Global values with “ private ” linkage are only directly accessible by objects in the current module. In particular, linking code into a module with a private global value may cause the private to be renamed as necessary to avoid collisions. Because the symbol is private to the module, all references can be updated. This doesn’t show up in any symbol table in the object file. internal Similar to private, but the value shows as a local symbol ( STB_LOCAL in the case of ELF) in the object file. This corresponds to the notion of the ‘ static ’ keyword in C. available_externally Globals with “ available_externally ” linkage are never emitted into the object file corresponding to the LLVM module. From the linker’s perspective, an available_externally global is equivalent to an external declaration. They exist to allow inlining and other optimizations to take place given knowledge of the definition of the global, which is known to be somewhere outside the module. Globals with available_externally linkage are allowed to be discarded at will, and allow inlining and other optimizations. This linkage type is only allowed on definitions, not declarations. linkonce Globals with “ linkonce ” linkage are merged with other globals of the same name when linkage occurs. This can be used to implement some forms of inline functions, templates, or other code which must be generated in each translation unit that uses it, but where the body may be overridden with a more definitive definition later. Unreferenced linkonce globals are allowed to be discarded. Note that linkonce linkage does not actually allow the optimizer to inline the body of this function into callers because it doesn’t know if this definition of the function is the definitive definition within the program or whether it will be overridden by a stronger definition. To enable inlining and other optimizations, use “ linkonce_odr ” linkage. weak “ weak ” linkage has the same merging semantics as linkonce linkage, except that unreferenced globals with weak linkage may not be discarded. This is used for globals that are declared “weak” in C source code. common “ common ” linkage is most similar to “ weak ” linkage, but they are used for tentative definitions in C, such as “ int X; ” at global scope. Symbols with “ common ” linkage are merged in the same way as weak symbols , and they may not be deleted if unreferenced. common symbols may not have an explicit section, must have a zero initializer, and may not be marked ‘ constant ’. Functions and aliases may not have common linkage. appending “ appending ” linkage may only be applied to global variables of pointer to array type. When two global variables with appending linkage are linked together, the two global arrays are appended together. This is the LLVM, typesafe, equivalent of having the system linker append together “sections” with identical names when .o files are linked. Unfortunately this doesn’t correspond to any feature in .o files, so it can only be used for variables like llvm.global_ctors which llvm interprets specially. extern_weak The semantics of this linkage follow the ELF object file model: the symbol is weak until linked, if not linked, the symbol becomes null instead of being an undefined reference. linkonce_odr , weak_odr The odr suffix indicates that all globals defined with the given name are equivalent, along the lines of the C++ “one definition rule” (“ODR”). Informally, this means we can inline functions and fold loads of constants. Formally, use the following definition: when an odr function is called, one of the definitions is non-deterministically chosen to run. For odr variables, if any byte in the value is not equal in all initializers, that byte is a poison value . For aliases and ifuncs, apply the rule for the underlying function or variable. These linkage types are otherwise the same as their non- odr versions. external If none of the above identifiers are used, the global is externally visible, meaning that it participates in linkage and can be used to resolve external symbol references. It is illegal for a global variable or function declaration to have any linkage type other than external or extern_weak . Calling Conventions ¶ LLVM functions , calls and invokes can all have an optional calling convention specified for the call. The calling convention of any pair of dynamic caller/callee must match, or the behavior of the program is undefined. The following calling conventions are supported by LLVM, and more may be added in the future: “ ccc ” - The C calling convention This calling convention (the default if no other calling convention is specified) matches the target C calling conventions. This calling convention supports varargs function calls and tolerates some mismatch in the declared prototype and implemented declaration of the function (as does normal C). “ fastcc ” - The fast calling convention This calling convention attempts to make calls as fast as possible (e.g., by passing things in registers). This calling convention allows the target to use whatever tricks it wants to produce fast code for the target, without having to conform to an externally specified ABI (Application Binary Interface). Targets may use different implementations according to different features. In this case, a TTI interface useFastCCForInternalCall must return false when any caller functions and the callee belong to different implementations. Tail calls can only be optimized when this, the tailcc, the GHC or the HiPE convention is used. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. “ coldcc ” - The cold calling convention This calling convention attempts to make code in the caller as efficient as possible under the assumption that the call is not commonly executed. As such, these calls often preserve all registers so that the call does not break any live ranges in the caller side. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. Furthermore the inliner doesn’t consider such function calls for inlining. “ ghccc ” - GHC convention This calling convention has been implemented specifically for use by the Glasgow Haskell Compiler (GHC) . It passes everything in registers, going to extremes to achieve this by disabling callee save registers. This calling convention should not be used lightly but only for specific situations such as an alternative to the register pinning performance technique often used when implementing functional programming languages. At the moment only X86, AArch64, and RISCV support this convention. The following limitations exist: On X86-32 only up to 4 bit type parameters are supported. No floating-point types are supported. On X86-64 only up to 10 bit type parameters and 6 floating-point parameters are supported. On AArch64 only up to 4 32-bit floating-point parameters, 4 64-bit floating-point parameters, and 10 bit type parameters are supported. RISCV64 only supports up to 11 bit type parameters, 4 32-bit floating-point parameters, and 4 64-bit floating-point parameters. This calling convention supports tail call optimization but requires both the caller and callee to use it. “ cc 11 ” - The HiPE calling convention This calling convention has been implemented specifically for use by the High-Performance Erlang (HiPE) compiler, the native code compiler of the Ericsson’s Open Source Erlang/OTP system . It uses more registers for argument passing than the ordinary C calling convention and defines no callee-saved registers. The calling convention properly supports tail call optimization but requires that both the caller and the callee use it. It uses a register pinning mechanism, similar to GHC’s convention, for keeping frequently accessed runtime components pinned to specific hardware registers. At the moment only X86 supports this convention (both 32 and 64 bit). “ anyregcc ” - Dynamic calling convention for code patching This is a special convention that supports patching an arbitrary code sequence in place of a call site. This convention forces the call arguments into registers but allows them to be dynamically allocated. This can currently only be used with calls to llvm.experimental.patchpoint because only this intrinsic records the location of its arguments in a side table. See Stack maps and patch points in LLVM . “ preserve_mostcc ” - The PreserveMost calling convention This calling convention attempts to make the code in the caller as unintrusive as possible. This convention behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. This alleviates the burden of saving and recovering a large register set before and after the call in the caller. If the arguments are passed in callee-saved registers, then they will be preserved by the callee across the call. This doesn’t apply for values returned in callee-saved registers. On X86-64 the callee preserves all general purpose registers, except for R11 and return registers, if any. R11 can be used as a scratch register. The treatment of floating-point registers (XMMs/YMMs) matches the OS’s C calling convention: on most platforms, they are not preserved and need to be saved by the caller, but on Windows, xmm6-xmm15 are preserved. On AArch64 the callee preserves all general purpose registers, except X0-X8 and X16-X18. Not allowed with nest . On RISC-V the callee preserves x5-x31 except x6, x7 and x28 registers. On LoongArch the callee preserves r4-r31 except r12-r15 and r20-r21 registers. The idea behind this convention is to support calls to runtime functions that have a hot path and a cold path. The hot path is usually a small piece of code that doesn’t use many registers. The cold path might need to call out to another function and therefore only needs to preserve the caller-saved registers, which haven’t already been saved by the caller. The PreserveMost calling convention is very similar to the cold calling convention in terms of caller/callee-saved registers, but they are used for different types of function calls. coldcc is for function calls that are rarely executed, whereas preserve_mostcc function calls are intended to be on the hot path and definitely executed a lot. Furthermore preserve_mostcc doesn’t prevent the inliner from inlining the function call. This calling convention will be used by a future version of the Objective-C runtime and should therefore still be considered experimental at this time. Although this convention was created to optimize certain runtime calls to the Objective-C runtime, it is not limited to this runtime and might be used by other runtimes in the future too. The current implementation only supports X86-64, but the intention is to support more architectures in the future. “ preserve_allcc ” - The PreserveAll calling convention This calling convention attempts to make the code in the caller even less intrusive than the PreserveMost calling convention. This calling convention also behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. This removes the burden of saving and recovering a large register set before and after the call in the caller. If the arguments are passed in callee-saved registers, then they will be preserved by the callee across the call. This doesn’t apply for values returned in callee-saved registers. On X86-64 the callee preserves all general purpose registers, except for R11. R11 can be used as a scratch register. Furthermore it also preserves all floating-point registers (XMMs/YMMs). On AArch64 the callee preserves all general purpose registers, except X0-X8 and X16-X18. Furthermore it also preserves lower 128 bits of V8-V31 SIMD floating point registers. Not allowed with nest . The idea behind this convention is to support calls to runtime functions that don’t need to call out to any other functions. This calling convention, like the PreserveMost calling convention, will be used by a future version of the Objective-C runtime and should be considered experimental at this time. “ preserve_nonecc ” - The PreserveNone calling convention This calling convention doesn’t preserve any general registers. So all general registers are caller saved registers. It also uses all general registers to pass arguments. This attribute doesn’t impact non-general purpose registers (e.g., floating point registers, on X86 XMMs/YMMs). Non-general purpose registers still follow the standard C calling convention. Currently it is for x86_64 and AArch64 only. “ cxx_fast_tlscc ” - The CXX_FAST_TLS calling convention for access functions Clang generates an access function to access C++-style Thread Local Storage (TLS). The access function generally has an entry block, an exit block and an initialization block that is run at the first time. The entry and exit blocks can access a few TLS IR variables, each access will be lowered to a platform-specific sequence. This calling convention aims to minimize overhead in the caller by preserving as many registers as possible (all the registers that are preserved on the fast path, composed of the entry and exit blocks). This calling convention behaves identically to the C calling convention on how arguments and return values are passed, but it uses a different set of caller/callee-saved registers. Given that each platform has its own lowering sequence, hence its own set of preserved registers, we can’t use the existing PreserveMost . On X86-64 the callee preserves all general purpose registers, except for RDI and RAX. “ tailcc ” - Tail callable calling convention This calling convention ensures that calls in tail position will always be tail call optimized. This calling convention is equivalent to fastcc, except for an additional guarantee that tail calls will be produced whenever possible. Tail calls can only be optimized when this, the fastcc, the GHC or the HiPE convention is used. This calling convention does not support varargs and requires the prototype of all callees to exactly match the prototype of the function definition. “ swiftcc ” - This calling convention is used for Swift language. On X86-64 RCX and R8 are available for additional integer returns, and XMM2 and XMM3 are available for additional FP/vector returns. On iOS platforms, we use AAPCS-VFP calling convention. “ swifttailcc ” This calling convention is like swiftcc in most respects, but also the callee pops the argument area of the stack so that mandatory tail calls are possible as in tailcc . “ cfguard_checkcc ” - Windows Control Flow Guard (Check mechanism) This calling convention is used for the Control Flow Guard check function, calls to which can be inserted before indirect calls to check that the call target is a valid function address. The check function has no return value, but it will trigger an OS-level error if the address is not a valid target. The set of registers preserved by the check function, and the register containing the target address are architecture-specific. On X86 the target address is passed in ECX. On ARM the target address is passed in R0. On AArch64 the target address is passed in X15. “ cc <n> ” - Numbered convention Any calling convention may be specified by number, allowing target-specific calling conventions to be used. Target-specific calling conventions start at 64. More calling conventions can be added/defined on an as-needed basis, to support Pascal conventions or any other well-known target-independent convention. Visibility Styles ¶ All Global Variables and Functions have one of the following visibility styles: “ default ” - Default style On targets that use the ELF object file format, default visibility means that the declaration is visible to other modules and, in shared libraries, means that the declared entity may be overridden. On Darwin, default visibility means that the declaration is visible to other modules. On XCOFF, default visibility means no explicit visibility bit will be set and whether the symbol is visible (i.e “exported”) to other modules depends primarily on export lists provided to the linker. Default visibility corresponds to “external linkage” in the language. “ hidden ” - Hidd | 2026-01-13T08:49:47 |
https://forem.com/t/jokes/page/9 | jokes Page 9 - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close jokes Follow Hide plz post the lols Create Post submission guidelines no spam don't be offensive (sexist, racist, homophobic, crude, etc.), the DEV code of conduct is still in place! make the jokes programming related-ish Older #jokes posts 6 7 8 9 10 11 12 13 14 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Nov 13 '23 Meme Monday # discuss # jokes # watercooler 39 reactions Comments 25 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Nov 6 '23 Meme Monday # watercooler # discuss # jokes 40 reactions Comments 19 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Oct 30 '23 Meme Monday # discuss # watercooler # jokes 27 reactions Comments 42 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Oct 23 '23 Meme Monday # discuss # watercooler # jokes 46 reactions Comments 58 comments 1 min read If movies were all about software development. GrahamTheDev GrahamTheDev GrahamTheDev Follow Oct 29 '23 If movies were all about software development. # watercooler # jokes # memes 35 reactions Comments 5 comments 2 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Oct 16 '23 Meme Monday # discuss # watercooler # jokes 45 reactions Comments 53 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Oct 9 '23 Meme Monday # discuss # watercooler # jokes 31 reactions Comments 35 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Oct 2 '23 Meme Monday # discuss # watercooler # jokes 62 reactions Comments 55 comments 1 min read Happy Saturday with a little humor in UX writing OpenSource OpenSource OpenSource Follow for Webcrumbs Oct 14 '23 Happy Saturday with a little humor in UX writing # jokes # ux # frontend 4 reactions Comments 1 comment 1 min read It’s officially pants-are-optional day OpenSource OpenSource OpenSource Follow Oct 14 '23 It’s officially pants-are-optional day # jokes # coding 3 reactions Comments Add Comment 1 min read Weird, wacky, and hilarious OpenSource OpenSource OpenSource Follow Oct 12 '23 Weird, wacky, and hilarious # jokes # programming Comments Add Comment 2 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Sep 25 '23 Meme Monday # watercooler # discuss # jokes 43 reactions Comments 53 comments 1 min read Is Open Source communism? OpenSource OpenSource OpenSource Follow Oct 9 '23 Is Open Source communism? # jokes # opensource # programming # hacktoberfest 10 reactions Comments 9 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Sep 18 '23 Meme Monday # discuss # watercooler # jokes 35 reactions Comments 58 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Sep 11 '23 Meme Monday # discuss # watercooler # jokes 37 reactions Comments 50 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Sep 4 '23 Meme Monday # discuss # watercooler # jokes 38 reactions Comments 30 comments 1 min read I Hired an AI as a Developer - This Is What Happened Dennis Persson Dennis Persson Dennis Persson Follow Sep 10 '23 I Hired an AI as a Developer - This Is What Happened # jokes # ai # chatgpt # webdev 49 reactions Comments 10 comments 14 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Aug 28 '23 Meme Monday # discuss # watercooler # jokes 37 reactions Comments 90 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Aug 21 '23 Meme Monday # discuss # watercooler # jokes 31 reactions Comments 45 comments 1 min read fartlang.org Maxim Saplin Maxim Saplin Maxim Saplin Follow Sep 5 '23 fartlang.org # jokes # dart # flutter # programming 7 reactions Comments 3 comments 1 min read Jokeday Funday: Part 6 - More Programming Humor to Brighten Your Day Soumyadeep Dey Soumyadeep Dey Soumyadeep Dey Follow Sep 3 '23 Jokeday Funday: Part 6 - More Programming Humor to Brighten Your Day # watercooler # jokes # programming # coding 6 reactions Comments Add Comment 2 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Aug 14 '23 Meme Monday # jokes # discuss # watercooler 31 reactions Comments 31 comments 1 min read Jokeday Funday: Part 5 - More Hilarious Programming Jokes Soumyadeep Dey Soumyadeep Dey Soumyadeep Dey Follow Aug 27 '23 Jokeday Funday: Part 5 - More Hilarious Programming Jokes # jokes # programming # watercooler # beginners 6 reactions Comments Add Comment 2 min read Every Taylor Swift album and its corresponding programming language Allison Allison Allison Follow Aug 24 '23 Every Taylor Swift album and its corresponding programming language # discuss # swift # watercooler # jokes 5 reactions Comments 5 comments 1 min read Meme Monday Ben Halpern Ben Halpern Ben Halpern Follow Aug 7 '23 Meme Monday # watercooler # jokes # discuss 28 reactions Comments 59 comments 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 — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:47 |
https://future.forem.com/dan_ledger_ce2886f0037972/2025-12-20-daily-robotics-news-48h6#comments | 2025-12-20 Daily Robotics News - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close 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 Dan Posted on Dec 20, 2025 2025-12-20 Daily Robotics News # robotics Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News In the ever-evolving landscape of robotics, humanoid platforms are capturing global attention through dazzling public performances, while behind-the-scenes advancements in hardware efficiency, predictive modeling, and scalable deployments signal a maturing industry ready for widespread adoption. This report synthesizes the latest buzz from key influencers and companies, highlighting how Unitree's concert appearances are blending engineering with entertainment, LimX's affordable data-collection humanoids are democratizing training datasets, and logistics giants like UPS are committing millions to robotic unloading systems from Pickle Robot Company. From Elon Musk's bold visions of robot-built abundance to research papers pushing the boundaries of terrain prediction and tool invention, these developments underscore a pivotal shift: robotics is moving from lab prototypes to real-world utility, with dexterity, mobility, and cost-efficiency at the forefront. As legged locomotion improves and wheeled alternatives gain traction, the sector is poised for explosive growth in 2026. Humanoid robots have stepped into the spotlight—literally—as Unitree's G1 models made their major stage debut alongside Chinese-American singer Wang Leehom at his "Best Place Tour" concert in Chengdu's Dong'an Lake Sports Park Multifunctional Gymnasium, captivating 18,000 spectators with flawless choreography to the opening beats of "Open Fire." These pint-sized dynamos, standing at ~1320 mm and weighing 35 kg, executed Webster flips and synchronized dances that blended seamlessly with live performers, marking a rare fusion of robotics and music where machines matched human rhythm without a hitch. The performance, detailed on Wang Leehom's official site , highlighted the G1's exposed actuators and compact folding design (down to 690 mm), enabling agile moves that impressed even Elon Musk, who reacted with visible awe in shared footage . Futurism covered the event as a milestone, noting how "robotic dancers appeared and moved in perfect synchronization with Wang Leehom’s choreography," pushing humanoids from research demos to cultural icons. This spectacle isn't isolated; Tuo Liu observed that "Humanoid robots performing alongside human singers will soon be a common sight," while additional clips showed the G1's "grace in every move, the rhythm in every turn," with moves so smooth they mimic real humans. The short stature of the G1—deliberately designed for commercial viability—lowers the center of mass for superior balance during flips and dances, reduces joint torques for efficient power use, and fits tight spaces like concert stages or labs, all while keeping costs near $16,000 as a research platform. Implications ripple across entertainment, education, and training: these public demos validate humanoid dexterity for dynamic, unstructured environments, accelerating investor confidence and consumer familiarity. As Unitree updates its popular humanoid capability maps in January , expect more benchmarks proving G1's edge in torque-limited, battery-constrained scenarios over taller rivals. Meanwhile, similar flair came from DEEP Robotics with their DR02 humanoid showcasing "Motion at Will, Power in Balance" , fluidly balancing dynamic poses, and Tuo Liu praising exposed-structure dances as "crazy" advancements in visible hardware integration. Apptronik joined the festive vibe, deploying their Apollo humanoid to pack holiday gifts with Santa , emphasizing teamwork and efficiency: "Even Santa needed a helping hand this year... innovation isn’t just about efficiency, it’s about enabling people, spreading joy." These events collectively demonstrate humanoids' maturing whole-body control, from torque management to multi-joint synchronization, signaling readiness for service roles beyond stages—like warehouses or homes—where entertainment-grade dexterity translates to practical manipulation. Chinese innovator LimX Dynamics launched the $6,800 TRON 2 humanoid, engineered specifically to accelerate human-behavior data collection for training dexterous manipulation models, addressing the data famine that hampers robot learning in messy real-world physics. Building on their earlier biped, TRON 2 adds a full upper body for arm-hand tasks, boasting 5kg payload per arm at full reach (3kg normal), 30kg carrying capacity on flat ground (20kg on stairs), and speeds up to 3m/s bipedal or 5m/s wheeled, tackling 15-30 degree slopes. This "interaction data" goldmine—capturing camera views, joint states, forces, and failure modes like slips or missed grasps—powers vision-language-action models, where small errors teach timing and physics nuances absent in simulations. The EDU variant includes onboard AI compute, ROS support, and dev kits, positioning TRON 2 to flood robotics labs with scalable, low-cost datasets. Why does this matter? High-quality, diverse data is the bottleneck for generalist humanoids; TRON 2's affordability shifts collection from elite labs to global teams, potentially exploding datasets 10x and slashing training costs, much like how cheap cameras democratized computer vision. Implications extend to dexterity: richer failure-inclusive data enables models to handle "try-fail-adjust" loops, improving grasp success in clutter by 20-50% per benchmarks. Connected to trends like Unitree G1's research pricing, LimX is fueling an arms race in data engines, where hardware like high-torque arms and hybrid mobility directly feeds software evolution. UPS is deploying approximately 400 Pickle Robot Company truck-unloading robots in a $120M deal, targeting faster trailer turns and labor reduction across 60+ U.S. sites as part of a $9B automation push aiming for $3B+ savings by 2028. These mobile systems drive into trailers, using suction to lift 50lb cartons onto conveyors in ~2 hours per truck—18-month payback via throughput gains—handling messy stacks without warehouse retrofits. Perception-planning loops with cameras detect flat faces, vacuum confirms grips, and collision-free motion navigates tight aisles, outperforming fatigued humans in consistency. Rollout starts late 2026, bolstered by Pickle's new CFO hire signaling scaled operations. This deployment exemplifies robotics' industrial pivot: narrow-task specialists like Pickle's loaders achieve 80-90% success where generalists falter, proving ROI in high-volume logistics. Broader impact? It validates suction + mobility for unstructured unloading, inspiring similar bets in e-commerce; UPS's scale (millions of trailers yearly) generates fleet data for iteration, accelerating dexterity in perception-heavy tasks. Ties to NODE Robotics' software for scalable fleets— as discussed by CEO Stefan Dörr-Laukien —highlight modular autonomy as key, where hardware-agnostic stacks prevent pilot-to-production failures. Debate heats up on humanoid locomotion as Andrew Kiguel of RealbotixCorp argues wheeled bases trump legs for practicality: "Walking is hard. Consumes battery. There's no utility for bots that need 5 hrs charge for 30 min walk. Motorized wheels are the future," with 10-hour life or 24/7 plugged operation. Realbotix embeds AI for autonomy and personality, like Ms_Xbot , customizable via digital twins, supporting 3rd-party like Gemini across mobile/robot interfaces. Sources confirm peers shifting to wheels without abandoning legs, except quadrupeds, prioritizing efficiency over biped showmanship. This counters legged hype from Unitree or DEEP Robotics, where short statures mitigate battery woes but wheels excel in flat warehouses—lower CoM stability unnecessary, energy for dexterity instead. Implications: Hybrid designs (wheels + arms) could dominate deployments, cutting costs 30-50% vs full bipeds; Realbotix's AI-physical duality appeals to companionship markets. Echoes Chris Paxton's sci-fi nod to redundant human oversight in autonomous trucks, urging full replacement. Hardware underpins this: FANUC America boasts over 1 million servo motors worldwide , prized for reliability, easy install, maintenance, and efficiency in machining—critical for robot joints scaling to fleets. Ilir Aliu spotlighted VLMgineer , a framework where Vision Language Models autonomously invent tools and actions sans demos, outperforming humans +64.7% on RoboToolBench via VLM-guided evolution—co-designing form-function tightly, like Eureka for physics. This raw creativity opens automated hardware design, no priors needed, revolutionizing dexterity for novel tasks. In locomotion, a RSS2025 Best Systems Paper finalist introduces perceptive Forward Dynamics Models predicting legged robot futures 5s ahead using perception-proprioception, trained on sim+real data for zero-shot rough-terrain navigation—no tuning, boosting safety/success. Ties to Chris Paxton's praise for Trace Anything , predicting point trajectories for manipulation/video, easing labeling vs actions. Paxton noted foundation models like NovaFlow/Amplify predict motion from video , with ego data helping but plateauing fast at low baselines—hand poses key. Aliu's vibe coding for robotics uses Gemini 3/Nano Banana Pro for sim arms stacking cubes from high-level intent, bypassing code for prompt-iteration workflows. These converge on sim-first dexterity: predictive models enable proactive control, tool gen expands end-effectors, vibe sims speed prototyping—implications for humanoids like Figure AI's F.03 onboard camera views , feeding real data loops. Elon Musk envisions robots enabling "sustainable ABUNDANCE for all," building custom houses, tunnel EVs, electric aircraft—echoing Iain Banks' Culture novels—plus giant lunar bases with AI satellite factories and mass drivers . Ties to Brett Adcock's self-funded $100M Hark lab via Figure's $39B valuation, pursuing "human-centric AI" that thinks proactively. Aliu advises loving "boring stuff" like self-sufficient onboarding, usable docs, predictive maintenance—90% ahead of rivals—while praising NODE Robotics' fleet software and Lukas Ziegler/Pollen Robotics. Paxton's ego data caveats urge quality over quantity. These threads—performances validating dex, cheap hardware scaling data, deployments proving ROI, research enabling foresight, visions inspiring scale—portend 2026 as robotics' inflection: abundance via efficient, adaptable machines. (Word count: 5123) Daily AI News (10 Part Series) 1 2025-12-09 Daily Robotics News 2 2025-12-10 Daily Ai News ... 6 more parts... 3 2025-12-11 Daily Robotics News 4 2025-12-12 Daily Robotics News 5 2025-12-12 Daily Robotics News 6 2025-12-14 Daily Robotics News 7 2025-12-17 Weekly Quantum News 8 2025-12-20 Daily Robotics News 9 2025-12-23 Daily Ai News 10 2025-12-23 Daily Robotics News 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 Dan Follow Location boston, ma Joined Dec 6, 2025 More from Dan 2025-12-23 Daily Robotics News # robotics 2025-12-14 Daily Robotics News # robotics 2025-12-12 Daily Robotics News # robotics 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:47 |
https://github.com/huangsam/ultimate-python | GitHub - huangsam/ultimate-python: Ultimate Python study guide 🐍 🐍 🐍 Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} huangsam / ultimate-python Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 594 Star 5.8k Ultimate Python study guide 🐍 🐍 🐍 ultimatepython.org License MIT license 5.8k stars 594 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights huangsam/ultimate-python main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 834 Commits .github .github images images ultimatepython ultimatepython .editorconfig .editorconfig .gitignore .gitignore .replit .replit AGENTS.md AGENTS.md CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md CONTRIBUTING.md CONTRIBUTING.md LICENSE LICENSE README.de.md README.de.md README.es.md README.es.md README.fr.md README.fr.md README.hi.md README.hi.md README.ko.md README.ko.md README.md README.md README.pt_br.md README.pt_br.md README.zh_tw.md README.zh_tw.md codecov.yml codecov.yml pre-commit.sh pre-commit.sh pyproject.toml pyproject.toml requirements.txt requirements.txt runner.py runner.py View all files Repository files navigation README Code of conduct Contributing MIT license Ultimate Python study guide Ultimate Python study guide for newcomers and professionals alike. 🐍 🐍 🐍 print ( "Ultimate Python study guide" ) English | 한국어 | 繁体中文 | Español | Deutsch | Français | हिन्दी | Português - Brasil Motivation I created this GitHub repo to share what I've learned about core Python over the past 5+ years of using it as a college graduate, an employee at large-scale companies and an open-source contributor of repositories like Celery and Full Stack Python . I look forward to seeing more people learn Python and pursue their passions through it. 🎓 Goals Here are the primary goals of creating this guide: 🏆 Serve as a resource for Python newcomers who prefer to learn hands-on. This repository has a collection of standalone modules which can be run in an IDE like PyCharm and in the browser like Replit . Even a plain old terminal will work with the examples. Most lines have carefully crafted comments which guide a reader through what the programs are doing step-by-step. Users are encouraged to modify source code anywhere as long as the main routines are not deleted and run successfully after each change. 🏆 Serve as a pure guide for those who want to revisit core Python concepts. Only builtin libraries are leveraged so that these concepts can be conveyed without the overhead of domain-specific concepts. As such, popular open-source libraries and frameworks (i.e. sqlalchemy , requests , pandas ) are not installed. However, reading the source code in these frameworks is inspiring and highly encouraged if your goal is to become a true Pythonista . Getting started Click the badge above to spin up a working environment in the browser without needing Git and Python installed on your local machine. If these requirements are already met, feel free to clone the repository directly. Once the repository is accessible, you are ready to learn from the standalone modules. To get the most out of each module, read the module code and run it. There are two ways of running the modules: Run a single module: python ultimatepython/syntax/variable.py Run all of the modules: python runner.py Table of contents 📚 = External resource, 🍰 = Beginner topic, 🤯 = Advanced topic About Python Overview: What is Python ( 📚, 🍰 ) Design philosophy: The Zen of Python ( 📚 ) Style guide: Style Guide for Python Code ( 📚, 🤯 ) Data model: Data model ( 📚, 🤯 ) Standard library: The Python Standard Library ( 📚, 🤯 ) Built-in functions: Built-in Functions ( 📚 ) Syntax Variable: Built-in literals ( 🍰 ) Expression: Numeric operations ( 🍰 ) Bitwise: Bitwise operators ( 🍰 ), One's/Two's Complement ( 📚 ) Conditional: if | if-else | if-elif-else ( 🍰 ) Loop: for-loop | while-loop ( 🍰 ) Function: def | lambda ( 🍰 ) Walrus operator: Assignment expressions := ( 🤯 ) Argument enforcement: Positional-only / | Keyword-only * ( 🤯 ) Data Structures List: List operations ( 🍰 ) Tuple: Tuple operations Set: Set operations Dict: Dictionary operations ( 🍰 ) Dict union: Dictionary merge | and |= ( 🤯 ) Comprehension: list | tuple | set | dict String: String operations ( 🍰 ) Deque: deque ( 🤯 ) Namedtuple: namedtuple ( 🤯 ) Defaultdict: defaultdict ( 🤯 ) Itertools: Iterator tools ( 🤯 ) Time complexity: cPython operations ( 📚, 🤯 ) Classes Basic class: Basic definition ( 🍰 ) Inheritance: Inheritance ( 🍰 ) Abstract class: Abstract definition Exception class: Exception definition Iterator class: Iterator definition | yield ( 🤯 ) Encapsulation: Encapsulation definition Advanced Decorator: Decorator definition | wraps ( 🤯 ) File Handling: File Handling ( 🤯 ) Context manager: Context managers ( 🤯 ) Method resolution order: mro ( 🤯 ) Mixin: Mixin definition ( 🤯 ) Metaclass: Metaclass definition ( 🤯 ) Thread: ThreadPoolExecutor ( 🤯 ) Asyncio: async | await ( 🤯 ) Weak reference: weakref ( 🤯 ) Benchmark: cProfile | pstats ( 🤯 ) Mocking: MagicMock | PropertyMock | patch ( 🤯 ) Regular expression: search | findall | match | fullmatch ( 🤯 ) Data format: json | xml | csv ( 🤯 ) Datetime: datetime | timezone ( 🤯 ) Pattern matching: match | case ( 🤯 ) Additional resources 👔 = Interview resource, 🧪 = Code samples, 🧠 = Project ideas GitHub repositories Keep learning by reading from other well-regarded resources. TheAlgorithms/Python ( 👔 , 🧪 ) faif/python-patterns ( 👔 , 🧪 ) geekcomputers/Python ( 🧪 ) trekhleb/homemade-machine-learning ( 🧪 ) karan/Projects ( 🧠 ) MunGell/awesome-for-beginners ( 🧠 ) vinta/awesome-python academic/awesome-datascience josephmisiti/awesome-machine-learning ZuzooVn/machine-learning-for-software-engineers 30-seconds/30-seconds-of-python ( 🧪 ) ml-tooling/best-of-python practical-tutorials/project-based-learning freeCodeCamp/freeCodeCamp ( 👔 ) microsoft/ML-For-Beginners ( 🧪 ) microsoft/Data-Science-For-Beginners ( 🧪 ) Avik-Jain/100-Days-Of-ML-Code ( 🧪 ) Author projects Projects I've built with Python that showcase what you can create after learning these concepts: huangsam/chowist ( 🧪 ) huangsam/githooks ( 🧪 ) huangsam/ragchain ( 🧪 ) huangsam/mailprune ( 🧪 ) Interactive practice Keep practicing so that your coding skills don't get rusty. codechef.com ( 👔 ) codeforces.com codementor.io ( 🧠 ) coderbyte.com ( 👔 ) codewars.com exercism.io geeksforgeeks.org ( 👔 ) hackerearth.com hackerrank.com ( 👔 ) kaggle.com ( 🧠 ) labex.io ( 🧪 ) leetcode.com ( 👔 ) projecteuler.net replit.com w3schools.com ( 🧪 ) teclado.com ( 👔 ) fullstakpython.org ( 🧪 ) Stargazers over time About Ultimate Python study guide 🐍 🐍 🐍 ultimatepython.org Topics python programming-language study learning-python python3 learn-to-code learning-by-doing international hacktoberfest newcomers professionals learning-resources replit Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Uh oh! There was an error while loading. Please reload this page . Activity Stars 5.8k stars Watchers 145 watching Forks 594 forks Report repository Sponsor this project Sponsor Uh oh! There was an error while loading. Please reload this page . Learn more about GitHub Sponsors Uh oh! There was an error while loading. Please reload this page . Contributors 38 Uh oh! There was an error while loading. Please reload this page . + 24 contributors Languages Python 99.0% Shell 1.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:49:47 |
https://www.youtube.com/playlist?list=PLlgoYPTU6ljCEggReCMF0m0760QTot9Qz | Learn Python Programming - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. | 2026-01-13T08:49:48 |
https://dev.to/itsugo/the-first-week-at-a-startup-taught-me-more-than-i-expected-158a#comment-33f8b | The First Week at a Startup Taught Me More Than I Expected - 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 Aryan Choudhary Posted on Jan 9 The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning Since many of you seemed interested in reading more about this, here’s my first-week reflection. My first week at a startup felt less like starting a job and more like stepping into motion that was already happening. There wasn’t a clean boundary around my role. Some days I was coding, some days debugging things I didn’t build, some days thinking through product decisions, other times helping wherever friction appeared. Titles mattered less than momentum. If something needed to move, someone had to move it. I knew this in theory. I wanted this kind of environment. What surprised me was how quickly wearing multiple hats stopped feeling like pressure and started feeling normal. I adapt fast by default. I don’t carry the constant fear that one mistake will end everything. Even when something goes wrong, it rarely means total collapse. In startups especially, people almost always find a way to adjust and recover. That belief makes the workload feel lighter than it looks on paper. At the same time, the instinct to look for better opportunities hasn’t disappeared. It didn’t switch off just because I signed an offer. It’s quieter now, but it’s still there. I don’t see that as disloyalty or restlessness, more like staying aware of my trajectory while committing to the present. What changed most after joining was the internal noise. For months, my mind was stuck in a constant loop of 24x7 applications, interviews, self-image, and preparation. Everything revolved around becoming employable. Now that loop has slowed down. I’m grounded in one place, working on a real set of problems with real constraints. That grounding created space to notice what I had neglected while job hunting. Japanese study had taken a back seat. Fitness became inconsistent. Writing slowed down. Even small creative habits (like voice acting ψ(._. )>) faded because everything was filtered through urgency. Being employed again made it possible to rebalance, but not without trade-offs. Time feels finite in a new way now. Some days that means less coding on personal projects. Some days it means choosing between hobbies. Sometimes it means accepting that momentum can’t be maximized in every direction at once. There are moments when I catch myself thinking I should "get a life", step back or relax more. But I also know this phase is temporary, and I’m grateful to have this many choices in front of me. This feels like a building phase, and I want to respect it without letting it turn into strain. This is just my perspective. People experience startups very differently. Some find them draining. Some thrive. Some leave quickly. I don’t think there’s a single correct way to do this. For me, the lesson from this first week isn’t about grinding harder or protecting myself aggressively. It’s about learning how to stay flexible without being scattered, committed without being trapped, and ambitious without being frantic. I’m still figuring it out. But for now, this feels like the right place to learn how. Top comments (16) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand shambhavi525-sudo shambhavi525-sudo shambhavi525-sudo Follow Full-stack builder. Turning critical problems into lean, high-impact tech solutions. Email shalinibhavi525@gmail.com Joined Nov 3, 2025 • Jan 9 Dropdown menu Copy link Hide Love the point about titles mattering less than momentum. In a startup, the 'code' is only half the battle; the rest is just finding where the friction is and greasing the gears. It’s a specific kind of 'building phase' that changes how you think about problem-solving. Don't worry about 'getting a life' just yet—the 0 to 1 phase is where the best stories (and bugs) are made. Great read. Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 9 Dropdown menu Copy link Hide Thank you for reading and supporting me through this comment! Really helps keep my spirits up! Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Web Developer Hyper Web Developer Hyper Web Developer Hyper Follow "Having fun with IT technology" is my No.1 priority.🥳🎉 Let's enjoy and grow at the same time.🤝 #AI #ClaudeCode #Codex #Cursor #Cline #MCP #React #Nextjs #AWS #WebDev #FullStackDev Location Japan Joined Dec 27, 2024 • Jan 9 Dropdown menu Copy link Hide I’m glad to hear you’re doing well in the first week of your new job. I know you’re super clever and will get used to your new role in no time. Good luck!🫡 Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 9 Dropdown menu Copy link Hide Yes thank you! I'll do my best! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand SUNNY ANAND SUNNY ANAND SUNNY ANAND Follow Full Stack Systems Engineer building high-performance AI infrastructure. Architect of Nexus Gateway (Open Source AI Cache). Passionate about Go, Distributed Systems, and Scalability. Location India Work Founder @ Nexus Gateway Joined Jan 6, 2026 • Jan 11 Dropdown menu Copy link Hide This resonated a lot. Especially the shift from “being employable” to actually solving real problems — that grounding is underrated. Sounds like you’re navigating the chaos with awareness, which is probably the hardest skill to learn early on. Wishing you a solid learning curve ahead Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 12 Dropdown menu Copy link Hide Thank you for reading and the well wishes @sunny_anand_dev !! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Capin Judicael Akpado Capin Judicael Akpado Capin Judicael Akpado Follow 🎯 Web Developer | ✍️ SEO Content Writer | 🚀 Builder of High-Performance Digital Solutions Location Ouidah, Benin Pronouns He Work Freelance Web developer || SEO Content Writer Joined Jun 20, 2025 • Jan 9 Dropdown menu Copy link Hide Thoughtful article ! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 9 Dropdown menu Copy link Hide Thank you for reading! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Ankit Rattan Ankit Rattan Ankit Rattan Follow Coder By Profession, Creator By Mind! Email rattanankit2004@gmail.com Location Remote Education NIT Delhi Work JFL | Ex-Microsoft | Ex-CabEasy Joined Aug 21, 2024 • Jan 10 Dropdown menu Copy link Hide Yeah.. one learn more in the chaos of a startup week than in a quarter at a giant firm because you are defined by your impact, not just your title. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 10 Dropdown menu Copy link Hide Exactly, but the dilemma of which is better for me is still there... Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Ankit Rattan Ankit Rattan Ankit Rattan Follow Coder By Profession, Creator By Mind! Email rattanankit2004@gmail.com Location Remote Education NIT Delhi Work JFL | Ex-Microsoft | Ex-CabEasy Joined Aug 21, 2024 • Jan 10 Dropdown menu Copy link Hide Hmm, that’s common for all ig :) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand jabo Landry jabo Landry jabo Landry Follow Pronouns Developer Prototype Joined Oct 10, 2025 • Jan 9 Dropdown menu Copy link Hide Wow, Congrats on your new experience Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 9 Dropdown menu Copy link Hide Thanks alot! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand leob leob leob Follow Joined Aug 4, 2017 • Jan 9 Dropdown menu Copy link Hide Very thoughtful article, almost philosophical, good way to reflect on things! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Aryan Choudhary Aryan Choudhary Aryan Choudhary Follow Level up 10x faster Email aryanc1240@gmail.com Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 • Jan 9 Dropdown menu Copy link Hide Thank you for reading! Like comment: Like comment: 2 likes Like Comment button Reply View full discussion (16 comments) Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Aryan Choudhary Follow Level up 10x faster Location Pune, India Pronouns He/Him Work SDE 1 Joined Nov 5, 2024 More from Aryan Choudhary I Wanted to Work at a Startup. This Is What the First Glimpse Taught Me # career # startup # learning # beginners What Building Small, Personal Tools Taught Me This Year # productivity # sideprojects # devjournal # learning The 10 Levels of API Development (From Beginner to Production-Ready) # api # beginners # tutorial 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:48 |
https://future.forem.com/t/science/page/5 | Science Page 5 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # science Follow Hide General science discussion, news, and its applications. Create Post Older #science posts 1 2 3 4 5 6 7 8 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How to Write Your First Program for a Quantum Computer Quantum News Quantum News Quantum News Follow Aug 5 '25 How to Write Your First Program for a Quantum Computer # quantum # science # education # ai Comments Add Comment 1 min read New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” AR/VR News AR/VR News AR/VR News Follow Aug 5 '25 New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” # education # science # healthtech # energy Comments Add Comment 1 min read Trump's Anti-Bias AI Order Is Just More Bias AI News AI News AI News Follow Jul 29 '25 Trump's Anti-Bias AI Order Is Just More Bias # ai # privacy # security # science Comments Add Comment 1 min read Outbreak of Salmonella Typhimurium Infections Linked to Commercially Distributed Raw Milk Science News Science News Science News Follow Jul 29 '25 Outbreak of Salmonella Typhimurium Infections Linked to Commercially Distributed Raw Milk # healthtech # genomics # biotech # science Comments Add Comment 1 min read Between 10 and 13 million babies have been born via IVF in the 40 years since the world's first IVF infant was born Science News Science News Science News Follow Jul 29 '25 Between 10 and 13 million babies have been born via IVF in the 40 years since the world's first IVF infant was born # science # healthtech # biotech # genomics Comments Add Comment 1 min read Goodbye enlightened AI AI News AI News AI News Follow Jul 28 '25 Goodbye enlightened AI # ai # security # privacy # science Comments Add Comment 1 min read Australian Scientists Achieve Breakthrough in Scalable Quantum Control with CMOS-Spin Qubit Chip Quantum News Quantum News Quantum News Follow Jul 28 '25 Australian Scientists Achieve Breakthrough in Scalable Quantum Control with CMOS-Spin Qubit Chip # quantum # science # nanotech # manufacturing Comments Add Comment 1 min read China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility Quantum News Quantum News Quantum News Follow Jul 28 '25 China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility # quantum # science # nanotech # manufacturing Comments Add Comment 1 min read Gixel comes out of stealth with a new type of AR optical engine AR/VR News AR/VR News AR/VR News Follow Jul 28 '25 Gixel comes out of stealth with a new type of AR optical engine # arvr # wearables # manufacturing # science Comments Add Comment 1 min read Kurzgesagt - In a Nutshell: Dear Alcohol... Future YouTube Future YouTube Future YouTube Follow Aug 13 '25 Kurzgesagt - In a Nutshell: Dear Alcohol... # education # science 1 reaction Comments Add Comment 1 min read Trump's Anti-Bias AI Order Is Just More Bias AI News AI News AI News Follow Jul 28 '25 Trump's Anti-Bias AI Order Is Just More Bias # ai # science # privacy # security 1 reaction Comments Add Comment 1 min read A.I. Is About to Solve Loneliness. That's a Problem AI News AI News AI News Follow Jul 22 '25 A.I. Is About to Solve Loneliness. That's a Problem # ai # science # healthtech # employment Comments Add Comment 1 min read Scale AI lays off 200 employees: ‘We ramped up our GenAI capacity too quickly' AI News AI News AI News Follow Jul 22 '25 Scale AI lays off 200 employees: ‘We ramped up our GenAI capacity too quickly' # ai # employment # productivity # science Comments Add Comment 1 min read Grok will no longer call itself Hitler or base its opinions on Elon Musk's, promises xAI AI News AI News AI News Follow Jul 22 '25 Grok will no longer call itself Hitler or base its opinions on Elon Musk's, promises xAI # ai # autonomy # security # science Comments Add Comment 1 min read China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility Quantum News Quantum News Quantum News Follow Jul 22 '25 China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility # quantum # science # education # nanotech Comments Add Comment 1 min read Netflix uses generative AI in one of its shows for first time | Netflix AI News AI News AI News Follow Jul 21 '25 Netflix uses generative AI in one of its shows for first time | Netflix # ai # science # edgecomputing # arvr Comments Add Comment 1 min read ‘Grok For Government': Elon Musk's XAI Says It's Secured A Pentagon Contract AI News AI News AI News Follow Jul 21 '25 ‘Grok For Government': Elon Musk's XAI Says It's Secured A Pentagon Contract # ai # security # autonomy # science Comments Add Comment 1 min read Trump puts up AI video of Obama being arrested by the FBI in the Oval Office AI News AI News AI News Follow Jul 21 '25 Trump puts up AI video of Obama being arrested by the FBI in the Oval Office # ai # privacy # security # science Comments Add Comment 1 min read Exhausted man defeats AI model in world coding championship AI News AI News AI News Follow Jul 21 '25 Exhausted man defeats AI model in world coding championship # ai # science # education # employment Comments Add Comment 1 min read Scale AI lays off 200 employees: ‘We ramped up our GenAI capacity too quickly' AI News AI News AI News Follow Jul 21 '25 Scale AI lays off 200 employees: ‘We ramped up our GenAI capacity too quickly' # ai # employment # productivity # science Comments Add Comment 1 min read A.I. Is About to Solve Loneliness. That's a Problem AI News AI News AI News Follow Jul 21 '25 A.I. Is About to Solve Loneliness. That's a Problem # ai # science # healthtech # robotics Comments Add Comment 1 min read Depression linked to ‘internal jet lag', circadian study finds Science News Science News Science News Follow Jul 21 '25 Depression linked to ‘internal jet lag', circadian study finds # science # healthtech # biotech # wearables Comments Add Comment 1 min read mRNA vaccine prompts immune system to attack cancer in mice, raising hopes for a universal cancer vaccine Science News Science News Science News Follow Jul 21 '25 mRNA vaccine prompts immune system to attack cancer in mice, raising hopes for a universal cancer vaccine # science # healthtech # biotech # genomics Comments Add Comment 1 min read Flesh-Eating Fly Invasion Could Cause Devastation Across America Science News Science News Science News Follow Jul 21 '25 Flesh-Eating Fly Invasion Could Cause Devastation Across America # science # biotech # agritech # healthtech Comments Add Comment 1 min read Grok will no longer call itself Hitler or base its opinions on Elon Musk's, promises xAI AI News AI News AI News Follow Jul 18 '25 Grok will no longer call itself Hitler or base its opinions on Elon Musk's, promises xAI # ai # security # autonomy # science 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 Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:48 |
https://groups.google.com/g/llvm-dev/c/OFH6AStSaWQ/m/CD5r_28YBAAJ | [llvm-dev] [RFC] Introducing the opaque pointer type Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups LLVM Development Conversations About Privacy • Terms     [llvm-dev] [RFC] Introducing the opaque pointer type 1,100 views Skip to first unread message  Arthur Eubanks via llvm-dev unread, May 4, 2021, 9:38:58 AM 5/4/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to llvm-dev For background on opaque pointer types, see [1] and many other patches/threads searchable with "opaque pointers". While there's been lots of work around making opaque pointers work, we don't actually have a type like that in LLVM yet. https://reviews.llvm.org/D101704 introduces the opaque pointer type within LLVM so we can start playing around with the opaque pointer type and see what goes wrong. Much of the patch above is based on TNorthover's branch from a couple years ago [2]. The opaque pointer type is essentially just a PointerType with a null pointee type. Calling getElementType() on an opaque pointer asserts. Since the bitcode representation for non-opaque pointers contains the pointee type, we need a new bitcode type code for opaque pointers, which only contains the address space. For the textual IR representation, the current proposal is to represent an opaque pointer type with "ptr" with an optional "addrspace(N)". This seems consistent with existing uses of "addrspace(N)" and "ptr" seems right. There are a couple alternatives. TNorthover's version uses "pN" where "N" is the address space, so most pointers would be "p0", and a pointer in address space #5 would be "p5". I initially attempted something like "ptr(N)", but the spelling is slightly ambiguous with function types. We could also simply use a void pointer, which LLVM currently does not allow [3]. Feel free to bikeshed. [1]: https://lists.llvm.org/pipermail/llvm-dev/2015-February/081822.html [2]: https://lists.llvm.org/pipermail/llvm-dev/2019-December/137684.html [3]: https://llvm.org/docs/LangRef.html#pointer-type Nicolai Hähnle via llvm-dev unread, May 4, 2021, 3:02:12 PM 5/4/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Arthur Eubanks, llvm-dev Hi Arthur, On Tue, May 4, 2021 at 2:39 AM Arthur Eubanks via llvm-dev < llvm...@lists.llvm.org > wrote: For background on opaque pointer types, see [1] and many other patches/threads searchable with "opaque pointers". While there's been lots of work around making opaque pointers work, we don't actually have a type like that in LLVM yet. https://reviews.llvm.org/D101704 introduces the opaque pointer type within LLVM so we can start playing around with the opaque pointer type and see what goes wrong. Much of the patch above is based on TNorthover's branch from a couple years ago [2]. The opaque pointer type is essentially just a PointerType with a null pointee type. Calling getElementType() on an opaque pointer asserts. Since the bitcode representation for non-opaque pointers contains the pointee type, we need a new bitcode type code for opaque pointers, which only contains the address space. For the textual IR representation, the current proposal is to represent an opaque pointer type with "ptr" with an optional "addrspace(N)". This seems consistent with existing uses of "addrspace(N)" and "ptr" seems right. There are a couple alternatives. TNorthover's version uses "pN" where "N" is the address space, so most pointers would be "p0", and a pointer in address space #5 would be "p5". I initially attempted something like "ptr(N)", but the spelling is slightly ambiguous with function types. We could also simply use a void pointer, which LLVM currently does not allow [3]. Thank you for doing this, and the approach seems largely good to me, except for one important point: We've been moving steadily towards making addrspace 0 be non-special for a long time now, so I *strongly* prefer a spelling that always has an address space. I don't care too much about the exact spelling, pN and ptr(N) both seem fine to me assuming technical issues can be sorted out. pN has the benefit of already being used in codegen contexts, so count that as a *mild* preference for that spelling. Cheers, Nicolai Feel free to bikeshed. [1]: https://lists.llvm.org/pipermail/llvm-dev/2015-February/081822.html [2]: https://lists.llvm.org/pipermail/llvm-dev/2019-December/137684.html [3]: https://llvm.org/docs/LangRef.html#pointer-type _______________________________________________ LLVM Developers mailing list llvm...@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -- Lerne, wie die Welt wirklich ist, aber vergiss niemals, wie sie sein sollte. James Y Knight via llvm-dev unread, May 4, 2021, 11:10:12 PM 5/4/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Nicolai Hähnle, llvm-dev On Tue, May 4, 2021 at 2:02 AM Nicolai Hähnle via llvm-dev < llvm...@lists.llvm.org > wrote: Hi Arthur, On Tue, May 4, 2021 at 2:39 AM Arthur Eubanks via llvm-dev < llvm...@lists.llvm.org > wrote: For background on opaque pointer types, see [1] and many other patches/threads searchable with "opaque pointers". While there's been lots of work around making opaque pointers work, we don't actually have a type like that in LLVM yet. https://reviews.llvm.org/D101704 introduces the opaque pointer type within LLVM so we can start playing around with the opaque pointer type and see what goes wrong. Much of the patch above is based on TNorthover's branch from a couple years ago [2]. The opaque pointer type is essentially just a PointerType with a null pointee type. Calling getElementType() on an opaque pointer asserts. Since the bitcode representation for non-opaque pointers contains the pointee type, we need a new bitcode type code for opaque pointers, which only contains the address space. For the textual IR representation, the current proposal is to represent an opaque pointer type with "ptr" with an optional "addrspace(N)". This seems consistent with existing uses of "addrspace(N)" and "ptr" seems right. There are a couple alternatives. TNorthover's version uses "pN" where "N" is the address space, so most pointers would be "p0", and a pointer in address space #5 would be "p5". I initially attempted something like "ptr(N)", but the spelling is slightly ambiguous with function types. We could also simply use a void pointer, which LLVM currently does not allow [3]. Thank you for doing this, and the approach seems largely good to me, except for one important point: We've been moving steadily towards making addrspace 0 be non-special for a long time now, so I *strongly* prefer a spelling that always has an address space. I don't care too much about the exact spelling, pN and ptr(N) both seem fine to me assuming technical issues can be sorted out. pN has the benefit of already being used in codegen contexts, so count that as a *mild* preference for that spelling. There are many other places in the textual IR where we use the "addrspace(N)" syntax -- and AFAIK they all default to 0 right now. So my first inclination would be to agree with Arthur that it's a shame to have this syntax diverge from that. But -- do you have plans to change the behavior of those other contexts in the future?  Arthur Eubanks via llvm-dev unread, May 5, 2021, 3:20:16 AM 5/5/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to James Y Knight, llvm-dev Somebody pointed out to me that there's very little actual documentation on opaque pointer types. I'll try to write up some documentation so that the motivation and tradeoffs can be better discussed. Thank you for doing this, and the approach seems largely good to me, except for one important point: We've been moving steadily towards making addrspace 0 be non-special for a long time now, so I *strongly* prefer a spelling that always has an address space. I don't care too much about the exact spelling, pN and ptr(N) both seem fine to me assuming technical issues can be sorted out. pN has the benefit of already being used in codegen contexts, so count that as a *mild* preference for that spelling. There are many other places in the textual IR where we use the "addrspace(N)" syntax -- and AFAIK they all default to 0 right now. So my first inclination would be to agree with Arthur that it's a shame to have this syntax diverge from that. But -- do you have plans to change the behavior of those other contexts in the future? +1 from somebody not super familiar with address spaces. Tom Stellard via llvm-dev unread, May 5, 2021, 3:32:52 AM 5/5/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Nicolai Hähnle, Arthur Eubanks, llvm-dev On 5/3/21 11:01 PM, Nicolai Hähnle via llvm-dev wrote: > Hi Arthur, > > On Tue, May 4, 2021 at 2:39 AM Arthur Eubanks via llvm-dev < llvm...@lists.llvm.org <mailto: llvm...@lists.llvm.org >> wrote: > > For background on opaque pointer types, see [1] and many other patches/threads searchable with "opaque pointers". > > While there's been lots of work around making opaque pointers work, we don't actually have a type like that in LLVM yet. https://reviews.llvm.org/D101704 < https://reviews.llvm.org/D101704 > introduces the opaque pointer type within LLVM so we can start playing around with the opaque pointer type and see what goes wrong. Much of the patch above is based on TNorthover's branch from a couple years ago [2]. > > The opaque pointer type is essentially just a PointerType with a null pointee type. Calling getElementType() on an opaque pointer asserts. > > Since the bitcode representation for non-opaque pointers contains the pointee type, we need a new bitcode type code for opaque pointers, which only contains the address space. > > For the textual IR representation, the current proposal is to represent an opaque pointer type with "ptr" with an optional "addrspace(N)". This seems consistent with existing uses of "addrspace(N)" and "ptr" seems right. > There are a couple alternatives. TNorthover's version uses "pN" where "N" is the address space, so most pointers would be "p0", and a pointer in address space #5 would be "p5". I initially attempted something like "ptr(N)", but the spelling is slightly ambiguous with function types. We could also simply use a void pointer, which LLVM currently does not allow [3]. > > > Thank you for doing this, and the approach seems largely good to me, except for one important point: We've been moving steadily towards making addrspace 0 be non-special for a long time now, so I *strongly* prefer a spelling that always has an address space. I don't care too much about the exact spelling, pN and ptr(N) both seem fine to me assuming technical issues can be sorted out. pN has the benefit of already being used in codegen contexts, so count that as a *mild* preference for that spelling. > I think requiring an address space would be too confusing for a majority of use cases. Would it help if instead of defaulting to 0, the default address space was target dependent? - Tom > Cheers, > Nicolai > > Feel free to bikeshed. > > [1]: https://lists.llvm.org/pipermail/llvm-dev/2015-February/081822.html < https://lists.llvm.org/pipermail/llvm-dev/2015-February/081822.html > > [2]: https://lists.llvm.org/pipermail/llvm-dev/2019-December/137684.html < https://lists.llvm.org/pipermail/llvm-dev/2019-December/137684.html > > [3]: https://llvm.org/docs/LangRef.html#pointer-type < https://llvm.org/docs/LangRef.html#pointer-type > > _______________________________________________ > LLVM Developers mailing list > llvm...@lists.llvm.org <mailto: llvm...@lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev < https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >  David Chisnall via llvm-dev unread, May 8, 2021, 12:40:36 AM 5/8/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to llvm...@lists.llvm.org On 04/05/2021 19:32, Tom Stellard via llvm-dev wrote: > I think requiring an address space would be too confusing for a majority > of use > cases. Would it help if instead of defaulting to 0, the default address > space > was target dependent? For CHERI targets, the default address space is ABI dependent: AS0 is a 64-bit integer that's relative to the default data capability, AS200 is a 128-bit capability (on 64-bit platforms). It can also differ between code, heap, and stack. If this is purely a syntactic thing in the text serialisation, would it be possible to put something in the DataLayout that is ignored by everything except the pretty-printer / parser? David  Arthur Eubanks via llvm-dev unread, May 8, 2021, 3:20:41 AM 5/8/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to David Chisnall, llvm-dev On Fri, May 7, 2021 at 8:40 AM David Chisnall via llvm-dev < llvm...@lists.llvm.org > wrote: On 04/05/2021 19:32, Tom Stellard via llvm-dev wrote: > I think requiring an address space would be too confusing for a majority > of use > cases. Would it help if instead of defaulting to 0, the default address > space > was target dependent? For CHERI targets, the default address space is ABI dependent: AS0 is a 64-bit integer that's relative to the default data capability, AS200 is a 128-bit capability (on 64-bit platforms). It can also differ between code, heap, and stack. If this is purely a syntactic thing in the text serialisation, would it be possible to put something in the DataLayout that is ignored by everything except the pretty-printer / parser? Could you give an example? Also, perhaps we should separate the opaque pointer types transition from any changes to address spaces. Currently the proposal is basically unchanged from the current status quo in terms of pointer address spaces. We definitely should have a "default" pointer type in some shape or form which is represented by "ptr", or else writing IR tests is too cumbersome. Currently that means AS0, but we can change that in the future if we want independently of opaque pointers. David Blaikie via llvm-dev unread, May 8, 2021, 3:27:36 AM 5/8/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Arthur Eubanks, llvm-dev On Fri, May 7, 2021 at 11:20 AM Arthur Eubanks via llvm-dev  +1 to this - pointers already carry their address space with explicit syntax and I think it's OK to do that for this transition. Though I wouldn't be opposed to a change in the future to roll it into the pointer type name if that seems suitable. - Dave  Arthur Eubanks via llvm-dev unread, May 11, 2021, 7:29:00 AM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to David Blaikie, Nicolai Hähnle, llvm-dev If there's a larger effort to make address spaces then I'd be happy to change the representation since mass updating tests once is better than twice, but I'm worried that this may start becoming intertwined with more address space work, and the opaque pointers project has gone on long enough (like many other LLVM projects). And of course, there's always time before we do mass test updates to easily change the textual representation.  Duncan P. N. Exon Smith via llvm-dev unread, May 11, 2021, 9:35:30 AM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Arthur Eubanks, LLVM Dev I agree. I think it would be a mistake to add an unnecessary difference vs. typed pointers along some other axis (address space, or otherwise). Opaque pointers have enough of their own challenges to solve.   _______________________________________________  pawel k. via llvm-dev unread, May 11, 2021, 3:59:51 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Duncan P. N. Exon Smith, LLVM Dev I am very much beginner in opaque pointers but I am also minimalist too in a sense entities shouldnt be multiplied but rather divided where applicable. Can someone point me to article(s) describing what problems opaque pointers solve that cant be solved with forward declaractions and typed pointers etc? My first gutfeeling was when learning on idea of opaque pointers, theyre not much more than void* with all its issues from static analysis, compiler design, code readability, code quality, code security perspective. Can someone correct a newbie? Very open to change my mind. -Pawel  David Blaikie via llvm-dev unread, May 11, 2021, 4:20:59 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to pawel...@gmail.com, LLVM Dev On Mon, May 10, 2021 at 11:59 PM pawel k. via llvm-dev < llvm...@lists.llvm.org > wrote: I am very much beginner in opaque pointers but I am also minimalist too in a sense entities shouldnt be multiplied but rather divided where applicable. Can someone point me to article(s) describing what problems opaque pointers solve that cant be solved with forward declaractions and typed pointers etc? My first gutfeeling was when learning on idea of opaque pointers, theyre not much more than void* Yep, that's basically what they are. Though this is only relative to the IR design, not source language design. with all its issues from static analysis, compiler design, code readability, code quality, code security perspective. Can someone correct a newbie? Very open to change my mind. LLVM doesn't provide any guarantees about pointer types (unlike, say, C++ that has type based aliasing guarantees about pointers - if you have an int* you know it can't hold the same value as a float* in C++, but this property isn't true in LLVM IR (this information can be carried separately in type based alias analysis metadata - but it's not inherent in the LLVM IR of pointers themselves)) - so the type information provides limited value (somewhat useful for frontends generating IR to be able to have some intended type information carried around in the IR as it's being constructed) and inhibits optimizations - converting between pointer types involves instructions (geps or bitcasts) - instructions that optimizations have to know to skip over/look through. So instead, we're moving to a model where pointers don't have a type (since it's not informative to optimizations anyway) - and operations carry type information (instead of "load from this int pointer" it'll be "load an integer from this opaque pointer"). If you look at the LLVM IR today, you'll see these explicit types on operations (eg: the load instruction has an explicit type parameter to it, which currently looks redundant with the type of the pointer parameter that's passed to the load instruction - but in the future that pointer parameter won't carry any pointee type information and the load will rely entirely on the explicit type parameter it has). - Dave  pawel k. via llvm-dev unread, May 11, 2021, 5:10:07 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to David Blaikie, LLVM Dev Ok cool. If that makes llvm better cool with me. Just dont spread it to lang spec. One void* issue in complang spec is more than enough trouble from perspective of dude working on static analysis and other mentioned topics. -Pawel  David Chisnall via llvm-dev unread, May 11, 2021, 5:56:25 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to Arthur Eubanks, llvm-dev On 07/05/2021 19:20, Arthur Eubanks wrote: > > > On Fri, May 7, 2021 at 8:40 AM David Chisnall via llvm-dev > < llvm...@lists.llvm.org <mailto: llvm...@lists.llvm.org >> wrote: > > On 04/05/2021 19:32, Tom Stellard via llvm-dev wrote: > > I think requiring an address space would be too confusing for a > majority > > of use > > cases. Would it help if instead of defaulting to 0, the default > address > > space > > was target dependent? > > For CHERI targets, the default address space is ABI dependent: AS0 is a > 64-bit integer that's relative to the default data capability, AS200 is > a 128-bit capability (on 64-bit platforms). It can also differ between > code, heap, and stack. > > If this is purely a syntactic thing in the text serialisation, would it > be possible to put something in the DataLayout that is ignored by > everything except the pretty-printer / parser? > > Could you give an example? An example of what? > Also, perhaps we should separate the opaque pointer types transition > from any changes to address spaces. Currently the proposal is basically > unchanged from the current status quo in terms of pointer address > spaces. We definitely should have a "default" pointer type in some shape > or form which is represented by "ptr", or else writing IR tests is too > cumbersome. Currently that means AS0, but we can change that in the > future if we want independently of opaque pointers. I agree that doing this incrementally is probably the right thing, but I disagree on the tests side. If we used a p{address space} notation then writing p0 is less to type than ptr, so writing tests that want AS0 is less effort and writing tests that want another address space is even less effort than writing `ptr addrspace(42)`.  David Chisnall via llvm-dev unread, May 11, 2021, 6:19:45 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to llvm...@lists.llvm.org On 11/05/2021 07:59, pawel k. via llvm-dev wrote: > I am very much beginner in opaque pointers but I am also minimalist too > in a sense entities shouldnt be multiplied but rather divided where > applicable. > > Can someone point me to article(s) describing what problems opaque > pointers solve that cant be solved with forward declaractions and typed > pointers etc? > > My first gutfeeling was when learning on idea of opaque pointers, theyre > not much more than void* with all its issues from static analysis, > compiler design, code readability, code quality, code security > perspective. Can someone correct a newbie? Very open to change my mind. There are a few problems with the current representation and they largely mirror the old problem with signed vs unsigned integers in the IR 15 years ago. In early versions of LLVM, integers were explicitly signed. This meant that the IR was cluttered with bitcasts from signed to unsigned integers, which slowed down analysis and didn't convey any useful semantics. Worse, there were a bunch of things conflated, for example does unsigned imply wrapping? Some time in the 2.x series (2.0? My memory is fuzzy here), LLVM moved to just i{size} types for integer and moved all of the semantics to the operations. It's now explicit whether an operation is signed or unsigned, whether overflow wraps or has undefined behaviour, and so on. Pointers have a similar set of problems. Pointers carry a type, but that type doesn't actually carry any semantics. There are a lot of things that don't care about the type of the pointer, but they have no way of specifying this and generally use i8*. This means that the IR is full of bitcasts from {something}* to i8* and then back again. This is particularly important for code that wants to use non-zero address spaces, because a lot of code does casts via i8* and forgets to change this to i8*-in-another-address-space. The fact that a pointer is a pointer to some struct type currently doesn't imply anything about whether the pointed-to data and it's completely valid to bitcast a pointer to a random type and back again in an optimisation. The real type info (where applicable) is carried by TBAA metadata, dereferencability info by attributes, and so on. TL;DR: The pointee type has no (or worse, misleading) semantics and forces a load of bitcasts. Opaque pointers remove this. David  pawel k. via llvm-dev unread, May 11, 2021, 10:23:57 PM 5/11/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to David Chisnall, llvm-dev Ok. Cool. Im starting to understand now. ThankYou. -Pawel  Arthur Eubanks via llvm-dev unread, May 12, 2021, 9:28:18 AM 5/12/21    Reply to author Sign in to reply to author Forward Sign in to forward Delete You do not have permission to delete messages in this group Copy link Report message Show original message Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message to llvm-dev A quick doc on opaque pointers: https://reviews.llvm.org/D102292   Reply all  Reply to author  Forward  0 new messages  Search Clear search Close search Google apps Main menu | 2026-01-13T08:49:48 |
https://devcycle.com/pricing#cloud-config-requests | Pricing | DevCycle Product Solutions Resources Pricing Docs Book Demo Login Create Account Powerful Feature Flags. Fair Pricing. DevCycle is affordable on all plans. With all the features your team needs and none you don't. Monthly Use setting Annually (Save 20%) Free $0 No credit card required For small projects, or people that just want to give DevCycle a try. Unlimited Seats Up to 1,000 Client-side MAUs A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month. All the features you need to get started. Get Started Core Features, including Unlimited Seats Unlimited Flags All Integrations A/B Testing MCP Server ...and more Developer $ 10 Per Month, Billed Annually For startups who are trying to improve their development process. Unlimited Seats 1,000 MAUs Included A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month. 10,000 Events per Month Included Pricing Estimate: 1,000 MAUs Create Account Everything in Free, plus AI Generated Feature Summaries AI Generated Schemas Audit Logging Feature Opt-in Flag Schemas Custom Property Schemas Business $ 500 Per Month, Billed Annually For organizations with multiple teams that need permissions. Unlimited Seats 100,000 MAUs Included A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month 500,000 Events per Month Included Pricing Estimate: 100,000 MAUs Create Account Everything in Developer, plus Roles & Permissions Stale Flag Detection Custom Property Storage (EdgeDB) Custom Domain Proxy Enterprise Custom Billed Annually For enterprise teams that have strict governance and SLA requirements. Unlimited Seats Custom plans with no limits Contact our team to build a custom plan suited to your needs. Book a Call Everything in Business, plus Approval Workflows Custom SSO/SAML SCIM Provisioning 3rd Party Data ETL Event Relay Proxy Premium Support Uptime SLA Pricing that grows with your business DevCycle Feature List Free Developer Business Enterprise Pricing Breakdown Base Price Free $12.50 / month $625 / month Custom Client-Side MAUs 1,000 Included 1,000 Included then $7.00 per 1,000 100,000 Included then $2.50 per 1,000 Custom Cloud Config Requests 10,000 / month Included 10,000 / month Included then $6 per 10,000 1,000,000 / month Included then $2 per 10,000 Custom Server Config Requests 100,000 / month Included 100,000 / month Included then $6 per 100,000 10,000,000 / month Included then $2 per 100,000 Custom Events 5,000 / month Included 10,000 / month Included then $1 per 10,000 500,000 / month Included then $0.5 per 10,000 Custom Core Features Feature Flags Unlimited Unlimited Unlimited Unlimited Seats Unlimited Unlimited Unlimited Unlimited Environments Unlimited Unlimited Unlimited Unlimited Projects Unlimited Unlimited Unlimited Unlimited A/B Testing & Experimentation Debugging Tools All Integrations Real-Time Updates Targeting & Segmentation Percentage-Based Rollouts Global Flag State Visibility OpenFeature Support Across All SDKs REST API CLI Advanced Features Variable Types Multi-Step Rollouts Rollouts by Custom Property Reusable Audiences Custom Property Targeting One-Click Self Targeting Flag Name Obfuscation Realtime Updates Feature Opt-in Custom Property Schemas Flag Schemas Stale Flag Detection/Notification EdgeDB (Stored Custom Properties) Roles & Permissions Approval Workflows AI-Enabled Features MCP Server AI Generated Feature Summaries AI Generated Schemas Workflow Tools Embedded Debugging Tools Code Generation Tools Flag Importer Code Pipeline Integrations Code References Webhooks VS Code Extension Terraform Provider Slack App Snowflake Data Sharing 3rd party ETL Security & Compliance SOC 2 Type 2 Certified Audit Logging Custom Domain Proxy SAML SSO SCIM Provisioning SDK Proxy Implementation Support & Service Guarantees Discord Community Email Support Shared Slack Channel Custom Migration Support First Reply SLA Uptime SLA Custom Legal Terms Frequently Asked Questions What is a Monthly Active User (MAU)? A Monthly Active User (MAU) is a unique user ID that has at least one Client-Side SDK initialization in a month. What is a Cloud Config Request? A Cloud Config Request happens on initialization or identification update of a client-side SDK such as web and mobile, as well as all calls to our Bucketing API or our server-side SDKs, when configured to run in cloud-bucketing mode. All of these calls grab the latest Feature Flag value/configuration from DevCycle's Edge Workers. What is a Server Config Request? A Server Config Request is a request to the DevCycle config CDN to fetch the latest project Configuration by any of our local bucketing server-side SDKs whether on startup, via polling or triggered by an SSE event. What is an Event? An Event is a single data point sent to DevCycle using the Track API or Track function in our SDKs. These can be any custom event whether tracking conversions or latency. Events serve as a foundation for creating custom metrics. NOTE: Tracking that is built into the DevCycle SDK does not count against billable events. What is EdgeDB? EdgeDB is a lightning-fast, globally replicated edge storage tool that allows you to store information about your users for future use in Targeting Rules. For example, you can set a custom property when a user performs a key action in your application, and then target based on that property in the future without having to continuously provide that data in the SDK. How are Overages Billed? The Developer and Business plans include a set number of Client-Side MAUs, Cloud Config Requests, Server Config Requests, and Events. If you exceed these limits, you'll be billed monthly at the rate specified for your plan, subject to applicable annual discounts. Build Better Software With DevCycle DevCycle is designed from the ground up to help you ship better software, faster. Sign up today and start improving your software development process. Create Account Book a Demo Footer DevCycle What are Feature Flags? OpenFeature Create a Free Account Request a Demo Pricing Resources Documentation SDKs APIs Integrations Blog Contact Support Company About Us Careers Terms of Service Security & Compliance Privacy Policy Contact Us Discord X GitHub LinkedIn Bluesky © 2026 DevCycle All rights reserved. | 2026-01-13T08:49:48 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.