Cancelo

cancelo

MariaDB 11.4 introduced many advanced features. One that grabbed my attention is the general support of packages for stored routines. Although this was previously available by activating the Oracle compatibility mode, now, the feature is available generally out-of-the-box. This will help you to significantly enhance the organization of database development within a MariaDB environment. Packages provide a modular approach to managing database logic. This addition aligns MariaDB more closely with other advanced database systems that have long utilized packages, such as Oracle, and sets it apart in that regard from other open-source relational databases that don't support packages. Packages in MariaDB allow you to group related stored procedures, functions, variables, and other elements together into a single unit. This structure provides several benefits, including improved code organization, enhanced reusability, and simplified maintenance. Prior to this update, each stored procedure and function in MariaDB existed independently, which could lead to a cluttered schema and more complicated management of complex business logic when implemented in the database. Packages address this issue by providing a way to logically group related routines. Again, the primary advantage of using packages is the encapsulation of related routines. For example, in an e-commerce application, operations related to order processing can be grouped into a single package called OrderProcessing. This package might include procedures like PlaceOrder, CancelOrder, and UpdateOrderStatus, as well as functions such as GetOrderDetails. This logical grouping makes the database schema more organized and the codebase easier to navigate and hence to maintain. Creating Packages Creating and using packages in MariaDB 11.4 and later is straightforward. Simply use the CREATE PACKAGE statement to define a package and the CREATE PACKAGE BODY statement to implement the package’s routines. Here is a simplified example without the actual business logic implementation: DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; In this example, the OrderProcessing package is defined with two procedures and one function. The package body provides the implementation for these routines, encapsulating the logic related to order processing within a single package. Calling Packaged Stored Routines To call a procedure or function that was defined in a package, you use the "dot notation." Here's an example of how to call the CancelOrder procedure in the OrderProcessing package: CALL OrderProcessing.CancelOrder(7); The same applies to functions in packages: SELECT OrderProcessing.GetOrderDetails(7); You can also define package-level variables and constants, which are accessible to all routines within the package. This way, you can share common data without relying on global variables or passing around parameters between routines. By centrally managing shared data within the package, you reduce code duplication and minimize the risk of errors. The following is an example (don't take the variable names too seriously in this snippet of code): DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; Other Benefits of Packages The introduction of packages in MariaDB 11.4 also brings the possibility of better version control and modularization of code. You can now manage stored routines more effectively, making it easier to track changes and updates. This modularization is particularly beneficial in large projects, where multiple developers might be working on different parts of the database logic simultaneously. By isolating different functionalities into packages, conflicts, and overlaps can be minimized, leading to a smoother development process. Moreover, packages support forward declarations, which means that the routines can be defined before their actual implementation. This feature allows for a more flexible and structured approach to coding, where developers can outline the package interface first and then fill in the details. This separation of interface and implementation can lead to cleaner, more understandable code, facilitating collaboration, and reducing the learning curve for new developers joining a project. For developers accustomed to working with Oracle databases, the inclusion of packages in MariaDB 11.4 will feel familiar and welcome. It bridges a functional gap between MariaDB and Oracle, making it easier to transition between these platforms. Packages vs Multiple Schemas It's important to note the distinction between packages and merely using multiple database schemas. While multiple schemas can help segregate different parts of a database, they do not offer the same level of organization and encapsulation as packages. Schemas are useful for dividing distinct areas of data and logic, but they do not inherently group related procedures and functions together in a way that enhances modularity and maintainability. Packages, on the other hand, allow for a more granular and cohesive approach, grouping related logic together within the same schema. This not only simplifies the management of routines but also improves the clarity and maintainability of the code. Try It Out As always, MariaDB continues to evolve. Try it out today by downloading the latest version of MariaDB, or if you have Docker running: docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword" MariaDB 11.4 introduced many advanced features . One that grabbed my attention is the general support of packages for stored routines. Although this was previously available by activating the Oracle compatibility mode , now, the feature is available generally out-of-the-box. This will help you to significantly enhance the organization of database development within a MariaDB environment. MariaDB 11.4 advanced features Oracle compatibility mode Packages provide a modular approach to managing database logic. This addition aligns MariaDB more closely with other advanced database systems that have long utilized packages, such as Oracle, and sets it apart in that regard from other open-source relational databases that don't support packages. Packages in MariaDB allow you to group related stored procedures, functions, variables, and other elements together into a single unit. This structure provides several benefits, including improved code organization, enhanced reusability, and simplified maintenance. Prior to this update, each stored procedure and function in MariaDB existed independently, which could lead to a cluttered schema and more complicated management of complex business logic when implemented in the database . implemented in the database Packages address this issue by providing a way to logically group related routines. Again, the primary advantage of using packages is the encapsulation of related routines. For example, in an e-commerce application, operations related to order processing can be grouped into a single package called OrderProcessing . This package might include procedures like PlaceOrder , CancelOrder , and UpdateOrderStatus , as well as functions such as GetOrderDetails . OrderProcessing PlaceOrder CancelOrder UpdateOrderStatus GetOrderDetails This logical grouping makes the database schema more organized and the codebase easier to navigate and hence to maintain. Creating Packages Creating and using packages in MariaDB 11.4 and later is straightforward. Simply use the CREATE PACKAGE statement to define a package and the CREATE PACKAGE BODY statement to implement the package’s routines. Here is a simplified example without the actual business logic implementation: CREATE PACKAGE CREATE PACKAGE BODY DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT);
  PROCEDURE CancelOrder(order_id INT);
  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON;
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  PROCEDURE PlaceOrder(customer_id INT, product_id INT, quantity INT)
  BEGIN
    -- Implementation code here
  END;

  PROCEDURE CancelOrder(order_id INT)
  BEGIN
    -- Implementation code here
  END;

  FUNCTION GetOrderDetails(order_id INT) RETURNS JSON
  BEGIN
    -- Implementation code here
  END;
END;

$$
DELIMITER ; In this example, the OrderProcessing package is defined with two procedures and one function. The package body provides the implementation for these routines, encapsulating the logic related to order processing within a single package. OrderProcessing Calling Packaged Stored Routines To call a procedure or function that was defined in a package, you use the "dot notation." Here's an example of how to call the CancelOrder procedure in the OrderProcessing package: CancelOrder OrderProcessing CALL OrderProcessing.CancelOrder(7); CALL OrderProcessing.CancelOrder(7); The same applies to functions in packages: SELECT OrderProcessing.GetOrderDetails(7); SELECT OrderProcessing.GetOrderDetails(7); You can also define package-level variables and constants, which are accessible to all routines within the package. This way, you can share common data without relying on global variables or passing around parameters between routines. By centrally managing shared data within the package, you reduce code duplication and minimize the risk of errors. The following is an example (don't take the variable names too seriously in this snippet of code): DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; DELIMITER $$

CREATE OR REPLACE PACKAGE OrderProcessing
  -- procedure list (see previous example)
END;

CREATE OR REPLACE PACKAGE BODY OrderProcessing
  -- variable declarations
  DECLARE some_count INT DEFAULT 1;
  DECLARE some_total INT DEFAULT 0;

  -- procedure definitions (see previous example)
END;

$$
DELIMITER ; Other Benefits of Packages The introduction of packages in MariaDB 11.4 also brings the possibility of better version control and modularization of code. You can now manage stored routines more effectively, making it easier to track changes and updates. This modularization is particularly beneficial in large projects, where multiple developers might be working on different parts of the database logic simultaneously. By isolating different functionalities into packages, conflicts, and overlaps can be minimized, leading to a smoother development process. Moreover, packages support forward declarations, which means that the routines can be defined before their actual implementation. This feature allows for a more flexible and structured approach to coding, where developers can outline the package interface first and then fill in the details. This separation of interface and implementation can lead to cleaner, more understandable code, facilitating collaboration, and reducing the learning curve for new developers joining a project. For developers accustomed to working with Oracle databases, the inclusion of packages in MariaDB 11.4 will feel familiar and welcome. It bridges a functional gap between MariaDB and Oracle, making it easier to transition between these platforms. Packages vs Multiple Schemas It's important to note the distinction between packages and merely using multiple database schemas. While multiple schemas can help segregate different parts of a database, they do not offer the same level of organization and encapsulation as packages. Schemas are useful for dividing distinct areas of data and logic, but they do not inherently group related procedures and functions together in a way that enhances modularity and maintainability. Packages, on the other hand, allow for a more granular and cohesive approach, grouping related logic together within the same schema. This not only simplifies the management of routines but also improves the clarity and maintainability of the code. Try It Out As always, MariaDB continues to evolve . Try it out today by downloading the latest version of MariaDB, or if you have Docker running: MariaDB continues to evolve downloading docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword" docker run --name mariadb-11.4 -e MARIADB_ROOT_PASSWORD=my-secret-pw -e MARIADB_DATABASE=mydb -e MARIADB_USER=myuser -e MARIADB_PASSWORD=mypassword -d mariadb:11.4

docker exec -it mariadb-11.4 mariadb -p"mypassword"

Packages for Store Routines in MariaDB 11.4: What You Need to Know

Startups of The Year 2023 Winners: North America 

Creating and Releasing an App with Flutter: Part II

The online marketing industry is broken, its reputation is bad and getting worse. Our industry is full of marketers, entrepreneurs and developers with , relying on extracting user data to fuel their unethical models. questionable styles, tactics and ethics driven by numbers business Growth hacks at cost of everything else Built with the purpose of taking attention away and making the users addicted to the products Built with the purpose being to collect data, sell that data and sell advertising Featuring dark patterns with design choices that to take actions that benefit the platform rather than themselves manipulate the users Tens if not hundreds of external, third-party scripts tracking every move Intentional in order to make it more difficult for users to quit, cancel, edit settings friction within design Buying, selling and scraping of user data such as email addresses with the intention of sending unsolicited mass sales mailers The most celebrated companies are the worst offenders Some of the most celebrated companies and people working within them are the worst offenders. Google has turned away from its “ ” motto and philosophy. don’t be evil You’ve already heard everything you need to know about how Facebook abuses your trust. The list is too long to include here. From the book Chaos Monkeys by , a former product manager at the company, you have a good insight into how a typical marketer thinks these days: Antonio García Martínez For my entire career at Facebook, I was embroiled in a rolling debate with the Facebook privacy and legal teams about what we could and couldn’t get away with, chiseling away at their legal trepidation, and trying to find some legal rubric that would forgive (or at least defensibly excuse) our next depredation with user data. Here’s a very current example of a dark pattern Facebook introduced in their design. The focus is on the fake new notification and message buttons on the top even though there actually are no new messages. The idea is to get more people to rush in and accept their invasive terms without a second thought. GDPR is just another obstacle for their growth team and something that can be hacked in order to manipulate more users to say yes to something they may not want. Despite what Mark Zuckerberg wants you or the senators to believe. Unilever is one of the largest advertisers online and this is : how they think Prowling his London office in jeans, Keith Weed, who oversees marketing and Unilever, one of the world’s largest advertisers, described how mobile phones have elevated data as a marketing tool. “Now with the good old mobile, I have individualized data on people. You don’t need to know their names . . . You know their telephone number. You know where they live, because it’s the same location as their PC.” Weed knows what times of the day you usually browse, watch videos, answer e-mail, travel to the office — and what travel routes you take. “From your mobile, I know whether you stay in four-star or two-star hotels, whether you go to train stations or airports. I use these insights along with what you’re browsing on your PC. I know whether you’re interested in horses or holidays in the Caribbean. The core values most big businesses (and those who are trying to become big) hold and stand for are the financial growth and monetary success. This growth matters the most and we use whatever tactic or strategy that leads us to it. This has attracted financially motivated people. And it’s difficult for these people to sacrifice short-term growth or financial success in exchange for user privacy, respect and strong ethics. ” It is difficult to get a man to understand something, when his salary depends upon his not understanding it.” This is the environment we’re working in. Discipline and patience are not tolerated. All the good values have costs, are viewed as barriers and are seen as a , at least in the short-term. competitive disadvantage GDPR has made advertising more complicated But the world we live and operate in is slowly changing. Social media and website advertising has gotten a lot more complicated since the General Data Protection Regulation (GDPR) has gone into effect. You now need permission from users in order to collect and use their personal data. All the GDPR notices on the different websites have really opened our eyes to how many third-party trackers are collecting our data. Compare and . The first is a typical website that you are used to these days. https://www.usatoday.com/ https://eu.usatoday.com/ It includes banners, intrusive advertising, it’s slow to load and uses a lot of your data. Behind the scenes it loads many external tracking scripts that are there to monitor your every move (on site and off site too), learn more about you so they can interrupt you to sell you more stuff you don’t need. More than 5MB of junk in total is loaded. The second version is the EU version which is compatible with the GDPR law. It’s pleasing to the eye, it’s quick to load, it doesn’t use much of your data, it doesn’t push intrusive ads you don’t want to see and it doesn’t load any tracking scripts in the background. The total size of the GDPR-friendly version is 500KB. It’s refreshing to visit, has a great user experience and is something that pretty much the whole web used to be before the big digital advertising revolution. With new ideas and better business models, I hope we can return to this type of ethical websites that are good for users but also companies running them. A growing number of marketers and companies with integrity Luckily there are a growing numbers of marketers and companies (and politicians with that support users) who share a wish to make the world of online a better place. even more regulations marketing . People with integrity. Something more people and companies should aspire to themselves. They hold admirable traits, qualities and a fresh, less intrusive view on how marketing should be done of recently voiced his opinion on this: Amir Salihefendic Doist of Farnam Street has recently updated his ethics and privacy policy plus removed all the Facebook tracking pixels: Shane Parrish , director of marketing at , : Kevan Lee Buffer is in on it too Good marketing requires empathy. Be genuine. Help people. Provide value first. Don’t persuade. Don’t sell someone something they don’t need. Enrich people’s lives. When they need you, be ready. Listen. Communicate clearly. Give freely. Advertise minimally. Seek permission and celebrate intent. Always speak the truth. Dream big. Deliver high quality. When in doubt, be a magnet not a hammer. Here’s an example of how things can be done from the book by , founder of Moz: Lost and Founder Rand Fishkin “You think we should make it harder to cancel?” I replied. “If you change the cancellation process to a phone call,” Rob explained, “I’m willing to bet that friction alone will improve your monthly churn rate. Plus, you can then talk to folks as they’re canceling and get a much better understanding of who they are and why they’re leaving. You could probably save a good number of them, too, or get them back as customers again in the future. Maybe switch some to a cheaper plan or convince them to buy a different product from you.” I’d seen some stats that backed up Rob’s guess and told him so. “You’re right. Making the subscription cancelable only by phone can have a real impact on churn rate. But we all hate services that require a phone call to cancel after a purely online signup. They’re intentionally making it difficult. It’s not empathetic, and that means it’s not TAGFEE.” “Fair enough,” Rob replied, “but you’re leaving a lot of money on the table.” “Well,” I answered, “we always say: they’re not core values if you’re willing to sacrifice them in exchange for money.” At Moz, we have six core values, represented by the acronym TAGFEE — Transparency, Authenticity, Generosity, Fun, Empathy, and the Exception. These are the beliefs we prioritize above the success or growth of the business. TAGFEE acts as a litmus test for whether we should or shouldn’t take an action, hire or let someone go from the team, or create a process or policy. We use it in everyday discussion about the content we put on our website, the ways we engage with our community, the products we build, and the internal actions we take. Rand seems to be taking this approach to his new startup too: Growth hacks are inferior to creating real value to people It’s up to us creators, developers, marketers, designers, and entrepreneurs. We can bring the user-friendly web back and we can . reintroduce some of these great principles and values All the growth hacks and tricks are inferior to . creating real value to people the audience you are trying to target Respect about what you’re doing Be upfront and honest to the people you are targeting Provide real value to people and make those options clear Give options of those that are interested to learn more Ask for permission of those that are not interested Ask for nothing in return to cheat people into accepting something they don’t want to Don’t use dark pattern design , persuade and lie to people Don’t manipulate , salesy and don’t sell things people don’t need Don’t be pushy It’s not easy to make these big changes. You will make mistakes, you will be disappointed, you will encounter resistance. Any small step you take can lead to an important change in the long run. And you will be happier and more fulfilled too. Some user-friendly steps I have taken on my blog One step I took on my blog recently was to . reduce the number of external scripts One quick win was to remove the default social sharing buttons and use a plugin that displays them without having any calls to the servers of Facebook et al. Except for when I embed content from other sites, my last remaining external script is Google Analytics. I’ve turned off every advanced tracking option that Google allows you to. I’ve also anonymized the IP addresses of my visitors in Google Analytics by adding (piece of code): this little trick ga(‘set’, ‘anonymizeIp’, true); By doing this, you only lose some accuracy in the city data. Everything else is fine. Still, Google collects a lot more data than I ever need but there is a lack of decent alternatives. and Paul Jarvis are working on a more simple and trustworthy solution (Fathom) that I am eager to replace GA with . Danny van Kooten when it’s ready YouTube also supports no-cookie embedding so I use that when embedding videos. Plus I have lazy loading on videos which means that they do not load anything (including external scripts) unless you scroll down to those areas. This . makes the blog faster too Within my content, I fully focus on providing the value without any empty promises, without intrusive advertising, without pushy, sleazy sales tactics to get people to buy secrets that would make them rich overnight. The web is full of these. I don’t use any of the intrusive pop-ups, pop-overs and such (looking at you too ). All my content is totally free. There are no email captures either. Medium These are some of the small steps I have taken and I will take these further as I discover new ideas and alternatives to the default way the things are done today. Data collection should not drive you at the expense of everything else All this doesn’t mean that you’re not ambitious. That your companies will never grow. That you will never achieve the goals that you want to achieve. It doesn’t mean that you have to totally ignore marketing, tactics and data either. Data is useful and can help you understand your audience better and help you create a better product. These things can be useful and valuable but they should not drive you and your business at the expense of everything else. Or in the words of : Derek Sivers Really, “marketing” just means being considerate. Marketing means making it easy for people to notice you, relate to you, remember you, and tell their friends about you. Marketing means listening for what people need, and creating something surprisingly tailored for them. Marketing means getting to know people, making a deeper connection, and keeping in touch. All of these are just considerate — looking at things from the other person’s point of view, and doing what’s best for them. Originally published at howtomakemyblog.com on May 31, 2018.

The Guiding Principles Of An Ethical Digital Marketer

FTC v. Amazon Court Filing, retrieved on Sep 26, 2023, is part of . You can jump to any part in this filing . This part is 13 of 20. HackerNoon’s Legal PDF Series here COUNT IV - Violation of ROSCA—Failure To Provide Simple Cancellation Mechanism 264. In numerous instances, in connection with charging consumers for goods or services sold in transactions effected on the Internet through a negative option feature, as described in Paragraphs 2 through 224 above, Defendant fails to provide simple mechanisms for a consumer to stop recurring charges for the good or service to the consumer’s credit card, debit card, bank account, or other financial account. 265. Defendant’s practices as set forth in Paragraph 264 are violations of Section 4 of ROSCA, 15 U.S.C. § 8403(3), and are therefore violations of a rule promulgated under Section 18 of the FTC Act, 15 U.S.C. § 57a, 15 U.S.C. § 8404(a), and therefore constitute an unfair or deceptive act or practice in violation of Section 5(a) of the FTC Act, 15 U.S.C. § 45(a). 266. Defendant committed the violations set forth in Paragraph 264 with the knowledge required by Section 5(m)(1)(A) of the FTC Act, 15 U.S.C. § 45(m)(1)(A). Continue Reading . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case 2:23-cv-00932 retrieved on September 28, 2023, from is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. ftc.gov

Amazon Accused of Failing To Provide Simple Cancellation Mechanism, Violating ROSCA

FTC v. Amazon Court Filing, retrieved on Sep 26, 2023, is part of . You can jump to any part in this filing . This part is 6 of 30. HackerNoon’s Legal PDF Series here Prime’s Four-Page, Six-Click, Fifteen-Option Iliad Cancellation Process 113. Under substantial pressure from the Commission, Amazon changed its Iliad cancellation process in or about April 2023, shortly before the filing of this Complaint. Prior to that point, there were only two ways to cancel a Prime subscription through Amazon: a) through the online labyrinthine cancellation flow known as the “Iliad Flow” on desktop and mobile devices; or b) by contacting customer service. 114. The Iliad Flow required consumers intending to cancel to navigate a four-page, six-click, fifteen-option cancellation process. In contrast, customers could enroll in Prime with one or two clicks. 115. Although consumers may have enrolled in Prime through devices other than computers and smartphones, such as through the Prime Video application on the Amazon FireStick and Fire TV, they could not cancel via these same technologies. Instead, they had to use the Iliad Flow or call customer service. 116. Amazon launched the Iliad Flow in 2016, and did not substantially change it in the United States until in or about April 2023. 117. To cancel via the Iliad Flow, a consumer had to first locate it, which Amazon made difficult. Consumers could access the Iliad Flow from Amazon.com by navigating to the Prime Central page, which consumers could reach by selecting the “Account & Lists” dropdown menu, reviewing the third column of dropdown links Amazon presented, and selecting the eleventh option in the third column (“Prime Membership”). This took the consumer to the Prime Central Page. 118. Once the consumer reached Prime Central, the consumer had to click on the “Manage Membership” button to access the dropdown menu. That revealed three options. The first two were “Share your benefits” (to add household members to Prime) and “Remind me before renewing” (Amazon then sent the consumer an email reminder before the next charge). See Attachment Q, at 1-2. 119. The last option was “End Membership.” The “End Membership” button did not end membership. Rather, it took the consumer to the Iliad Flow. See Attachment Q, at 2-3. It was impossible to reach the Iliad Flow from Amazon.com in fewer than two clicks. 120. Consumers could also reach the Iliad Flow by contacting customer service, asking to cancel, (Redacted) 121. Consumers could also reach the Iliad Flow from Amazon.com by typing “cancel membership” in the search bar. This produced an “Alexa” answer that included an “End Your Amazon Prime Membership” link. See Attachment T, at 2. 122. Clicking the link did not end Prime membership. Instead, it took the consumer to 7 another page with a heading that read: “End Your Amazon Prime Membership.” The page 8 contained a button labelled “End Your Prime Membership.” Pressing the button did not end 9 Prime Membership. Instead, it took the consumer to the Iliad Flow. See Attachment T, at 3-4. The search bar pathway to the Iliad Flow varied somewhat depending on what 0 search the consumer ran. For instance, searching “how to turn off Prime,” or “cancel prime” 1 (rather than “how to cancel Prime”) took the consumer to a page with a link to Prime Central, 2 from which the consumer had to then locate the path to the Iliad Flow. Searching “End Membership” took the consumer to a page with three blue links under the heading “Closing your Amazon account,” and a subheading “Get information on how to close your Amazon account.” The middle link was “cancel membership.” Clicking “cancel membership” did not cancel membership. Instead, it took the consumer to the Iliad Flow. 124. Typing “cancel membership” in the search bar on a mobile device brought the consumer to the Iliad Flow through similar steps. See Attachment S. 125. Thus, to reach the Iliad Flow, consumers had to do one of the following: 1) contact customer service and inform a customer service agent that they wanted to cancel (Redacted); 2) navigate from Amazon.com to the Prime account management page (Prime Central), locate the “manage membership” dropdown, and press a button labelled “End Membership”; or 3) search “How to cancel membership” in the Amazon search bar, then move through subsequent steps to reach the Iliad Flow—frequently, selecting a link reading “End Your Amazon Prime Membership” and then pressing a button reading “End Your Prime Membership.” 126. Once consumers reached the Iliad Flow, they had to proceed through its entirety—spanning three pages, each of which presented consumers several options, beyond the Prime Central page—to cancel Prime. See Attachment Q. 127. On the first page of the Iliad Flow, Amazon forced consumers to “[t]ake a look back at [their] journey with Prime” and presented them with a summary showing the Prime services they used. Amazon also displayed marketing material on Prime services, such as Prime Delivery, Prime Video, and Amazon Music Prime. Amazon placed a link for each service and encouraged consumers to access them immediately, i.e., “Start shopping today’s deals!”, “You can start watching videos by clicking here!”, and “Start listening now!” See Attachment Q, at 3. Clicking on any of these options took the consumer out of the Iliad Flow. 128. Also, on page one of the Iliad Flow, Amazon presented consumers with three buttons at the bottom. “Remind Me Later,” the button on the left, sent the consumer a reminder three days before their Prime membership renews (an option Amazon had already presented the consumer once before, in the “Manage Membership” pull-down menu through which the consumer entered the Iliad Flow). The “Remind Me Later” button took the consumer out of the Iliad Flow without cancelling Prime. “Keep My Benefits,” on the right, also took the consumer out of the Iliad Flow without cancelling Prime. Finally, “Continue to Cancel,” in the middle, also did not cancel Prime but instead proceeded to the second page of the Iliad Flow. See Attachment Q, at 3. Therefore, consumers could not cancel their Prime subscription on the first page of the Iliad Flow. 129. On the second page of the Iliad Flow, Amazon presented consumers with alternative or discounted pricing, such as the option to switch from monthly to annual payments (and vice-versa), student discounts, and discounts for individuals with EBT cards or who receive government assistance. Amazon emphasized the option to switch from monthly to annual payments by stating the amount a consumer would save at the top of this page in bold. Clicking the orange button (“Switch to annual payments”) or the links beneath took the consumer out of the Iliad Flow without cancelling. See Attachment Q, at 4. 130. Right above these alternatives, Amazon stated “Items tied to your Prime membership will be affected if you cancel your membership,” positioned next to a warning icon. See Attachment Q, at 4. 131. Amazon also warned consumers that “[b]y cancelling, you will no longer be eligible for your unclaimed Prime exclusive offers,” and hyperlinked to the Prime exclusive offers. See Attachment Q, at 4. Clicking this link took the consumer out of the Iliad Flow without cancelling. 132. Finally, at the bottom of Iliad Flow page two, Amazon presented consumers with buttons offering the same three options as the first page: “Remind Me Later,” “Continue to Cancel,” and “Keep My Membership” (labelled “Keep My Benefits” on the first page). See Attachment Q, at 4. Once again, consumers could not cancel their Prime subscription on the second page of the Iliad Flow. Choosing either “Remind Me Later” or “Keep My Membership” took the consumer out of the Iliad Flow without cancelling. Consumers had to click “Continue to Cancel” to access the third page of the Iliad Flow. 133. On the third page of the Iliad Flow, Amazon showed consumers five different options, only one of which, “End Now”—presented last, at the bottom of the page— immediately cancelled a consumer’s Prime membership. See Attachment Q. Pressing any of the first four buttons took the consumer out of the Iliad Flow without immediately cancelling. 134. On the third page of the Iliad Flow, the first and second options—“Remind Me Later” and “Keep My Membership”—were substantially identical to the buttons on the Iliad Flow’s first two pages. Therefore, Amazon forced consumers who reach the Iliad Flow’s last page to view the “Remind Me Later” option four times (including once to enter the Iliad Flow) and the “Keep My Membership” option three times. See Attachment Q, at 5. 135. The third option, “Pause on [date],” would “pause” or put on hold—but not cancel—a consumer’s Prime membership. Amazon did not charge “paused” members for Prime but made it simple for “paused” members to re-join Prime through a single “quick-resume” click. Amazon presented the “pause” option adjacent to a warning icon and text stating that, “[b]y pausing, [consumers] will no longer be eligible for [their] unclaimed Prime exclusive offers,” and provided links to “Prime exclusive offers” (which if clicked exit the Iliad Flow without canceling). See Attachment Q, at 5. Redacted 137. Above the fourth and fifth options—the “End on [date]” and “End Now” options—Amazon also added a warning icon and text that states “[b]y cancelling, [consumers] will no longer be eligible for [their] unclaimed Prime exclusive offers.” See Attachment Q, at 5. 138. The fourth option, “End on [date],” turned off Prime’s auto-renew feature. It did not immediately cancel the consumer’s membership. Instead, the membership would end when the current billing cycle concluded, and the consumer would not receive a refund. See Attachment Q, at 5. 140. Therefore, to complete the Iliad Flow and cancel a Prime membership, the consumer needed to click a minimum of six times from Amazon.com: Prime Central  “Manage Membership”  “End Membership” → “Continue to Cancel” → “Continue to Cancel” → “End Now.” See Attachment Q. 141. Amazon limited refunds available through the Iliad Flow to one monthly charge, although Amazon did not disclose this to subscribers entering the flow. Consequently, a Nonconsensual Enrollee who discovered Prime charges after a few months could not obtain a full refund online. (Redacted) 142. The Iliad Flow was also accessible through a mobile device. Similar to the Iliad Flow on desktop, the Iliad Flow on mobile was also difficult for consumers to locate and presented a complex array of options across multiple pages. Cancelling via the Iliad Flow on a mobile device was an eight-page, eight-click minimum process. 143. On a mobile device, a consumer entered the Iliad Flow by 1) tapping on “My Account,” 2) selecting “Manage Prime Membership” from a dropdown menu on the second page, 3) selecting “Manage membership” on the third page, 4) selecting “Manage membership” on the fourth page, and 5) selecting “End my Membership” on the fifth page. See Attachment R, at 1-5. 144. On the sixth page, the consumer seeking to cancel began the mobile equivalent of the Iliad Flow. Specifically, on this page, Amazon presented benefits information similar to the desktop Iliad Flow, and stated at the top of the page “[Name], thank you for being a member with us. Take a look back at your journey with Prime.” See Attachment R, at 6. Amazon included the same three options—“Keep My Benefits,” “Continue to Cancel,” and “Remind Me Later”—although consumers had to scroll down to view them. None of these options ended the Prime membership. Consumers who selected “Continue to Cancel” proceeded to a seventh page. See Attachment R, at 6. 145. On the seventh page, Amazon presented alternate payment options similar to those in the desktop Iliad Flow: Amazon placed the three options at the bottom of the page in the same order. See Attachment R, at 7. Pressing “Continue to Cancel” did not end the membership. It took the consumer to an eighth and final page. See Attachment R, at 7. 146. On the eighth and final page, Amazon presented five buttons. The first three were “Pause on [date],” “Keep My Membership,” and “Remind Me Later.” The consumer had to scroll down to view the fourth and fifth. The fourth (“End on [date]”) turned off auto-renew, but did not immediately cancel, and consumers who chose this option did not receive a refund. Only the fifth and final button (“End Now”) immediately cancelled the membership. Amazon refunded consumers who pressed this button a pro-rated amount for the balance of the monthly billing cycle. See Attachment R, at 8. 147. Amazon designed the Iliad Flow (both desktop and mobile) to inform consumers about a) Prime benefits they would lose by cancelling Prime, and b) alternative payment methods available to them to keep Prime. 148. Amazon did not design the Iliad Flow to be simple or easy for consumers. The Iliad Flow inhibits or prevents many consumers who intend to cancel from cancelling their membership. Redacted Continue Reading . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case 2:23-cv-00932 retrieved on September 28, 2023, from is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction. ftc.gov

Want to Cancel Amazon Prime? Forget about it! 

¿Quieres cancelar Amazon Prime? ¡Olvídalo!

Vous souhaitez annuler Amazon Prime ? Oublie ça!

अमेज़न प्राइम रद्द करना चाहते हैं? इसके बारे में भूल जाओ!

Amazonプライムをキャンセルしたいですか?気にしないで！

Quer cancelar o Amazon Prime? Esqueça isso!

Bạn muốn hủy Amazon Prime? Quên nó đi!

想要取消亚马逊 Prime 服务吗？忘掉它！

Greetings from the land of sleep-deprived partners! As I sit here at my desk, yawning like a baby hippo and trying to keep my eyelids from turning into curtains, I can't help but wonder: Is there anything your genius mind can't do? I come to you today with a simple plea, a request that could reform the way we sleep and potentially save countless relationships from the clutches of nocturnal cacophony. My appeal though simple is significant: can you please, pretty please, create a noise-cancelling device specifically designed for snoring partners? You see, , I am not just an average human; I am a sleep-deprived hero trying to navigate the treacherous waters of slumber next to a snoring partner. The nightly struggle is real, and it's time we address it with your ingenious touch. Mr. Musk Imagine this Musk: a cozy bedroom, dimly lit, the scent of lavender wafting through the air, and two souls lying side by side, ready to embrace the sweet caress of dreams. But as soon as the lights go out, a racket of cosmic proportions erupts. No, it's not the sound of a rocket leaving the launchpad at SpaceX station; it's the snoring symphony composed by my significant other. Now, don't get me wrong. I love my partner to the moon and back (pun intended), but when it comes to their snoring, even the most patient among us can feel like they're orbiting the brink of insanity. I've tried earplugs, noise-cancellation headphones, and even blasting heavy metal into my eardrums (which only led to some groovy, headbanging dreams). But alas, none of these solutions are as elegant and effective as what your genius mind could concoct. Picture this device, dear Master of Innovation: sleek, comfortable, and designed to fit snugly around the ears. As soon as it detects the seismic rumblings of snoring, it springs into action. Advanced algorithms analyze the snore frequency, amplitude, and duration, while microphones pick up other environmental sounds. Then, like magic, the device generates an anti-snore sound wave, perfectly out of phase with the original snore, effectively canceling it out. Here’s a potential for marital bliss! The tranquillity of uninterrupted sleep! Partners across the globe would celebrate the advent of such a device. Countless couples would be saved from sleeping in separate rooms, escaping the tragic fate of drifting apart due to incompatible nighttime noise levels. Of course, there may be some comical mishaps along the way. But imagine the marketing possibilities, Elon! You could call it "SnoreX" or "SleepX," and it would fly off the shelves faster than your Roadster. I can already see the testimonials pouring in, praising you as the saviour of sleep-deprived relationships everywhere. I must admit, Mr. Musk, I've had my fair share of waggish encounters with snoring partners. From recording their snorts and playing them back in the morning, only to be met with disbelieving stares, to waking them up accidentally while trying to stifle their snores – it's been quite the adventure. Now, I know you're a busy man, Elon, juggling more projects than I have fingers to count them on, but I genuinely believe this snore-cancelling device could be a game-changer. It might not be as awe-inspiring as relocating humanity to Mars or exploring the cosmos, but it would be an everyday marvel, silently mending relationships and spreading happiness, one night of peaceful sleep at a time. So, dear , if you're reading this, take a moment to ponder the plight of snoring partners worldwide. Let your imagination run wild, unleash your creative brilliance, and gift us with the ultimate solution to noise pollution. Together, we can make bedtime great again! Elon With hope, humour, and a dash of sleep deprivation, A fervent supporter in need of quiet nights.

Dear Elon Musk, Can You Create a Noise-Cancelling Device for Snoring Partners?

Hey Hackers! On April 6th, the Australian Securities & Investments Commission (ASIC) announced, via , the cancelation of the “Australian financial services (AFS) licence held by Oztures Trading Pty Ltd, trading as Binance Australia Derivatives (Binance)”. media release ASIC revealed that they have been conducting a “targeted review” of Binance’s business services in Australia regarding the crypto company’s reportedly irregular classification of retail investors as wholesale clients. Last week, ASIC issued a hearing notice, under the to determine whether to cancel or suspend Binance’s AFS license. Corporations Act 2001, It appears that Binance did not want to wait for that decision and actually requested a cancelation of their license the day before the hearing. “Following recent engagement with ASIC, Binance has chosen to pursue a more focused approach in Australia by winding down the Binance Australia Derivatives business. This does not affect Binance’s continued commitment to the development of the local blockchain and digital assets industry and Australians can continue to enjoy the use of our spot exchange product.” - Binance Spokesperson Due to the cancelation of the Financial Services License, clients cannot increase derivatives positions or open new positions with Binance, and all positions will be closed on April 21st. ASIC states that this cancelation does not excuse Binance from their responsibility to serve as a member of Australian Financial Complaints Authority until the end of April 2024. “It is critically important that AFS licensees classify retail and wholesale clients in accordance with the law. Retail clients trading in crypto derivatives are afforded important rights and consumer protections under financial services laws in Australia, including access to external dispute resolution through the Australian Financial Complaints Authority. Our targeted review of these matters is ongoing, including focus on the extent of consumer harms. ASIC supports a regulatory framework for crypto with a focus on consumer protection and market integrity. The final decision as to the regulatory settings is one for Government.” - , ASIC Chair Joe Longo Binance is dealing with a bunch regulatory investigations and lawsuits, so it may not be a bad idea for them to just give up and cancel their license to focus their efforts where they are more needed; like in the United States against the SEC and CFTC. What are your thoughts on this news? Do you think this might affect Binance’s overall business in Australia? Enter my on Publish0x to win yourself some free Crypto! Monthly Giveaway Check out my Socials: https://linktr.ee/zerorequiem0x See ya! :) Also published here

Australia Cancels Binance's Derivatives Business License: Here's Why

This is by (source: ). Levelsio is an indiepreneur. Twitter thread Levelsio @levelsio 02-22-2023 https://twitter.com/levelsio/status/1628340962136305664?s=46&t=cmto90R-A_PbWAD033otpg&embedable=true&thread=true Feature image generated via prompt of ‘A monster stopping you from leaving’ HackerNoon Stable Diffusion

How Difficult Is It to Cancel a Subscription From The Economist?

If you’ve ever used JavaScript API to enhance a form submission, there’s a good chance you’ve accidentally introduced a duplicate-request/race-condition bug. Today, I’ll walk you through the issue and my recommendations to avoid it. fetch (Video at the end if you prefer that) Let’s consider a very basic with a single input and a submit button. HTML form <form method="post">
  <label for="name">Name</label>
  <input id="name" name="name" />
  <button>Submit</button>
</form> When we hit the submit button, the browser will do a whole page refresh. Notice how the browser reloads after the submit button is clicked. The page refresh isn’t always the experience we want to offer our users, so a common alternative is to use to add an event listener to the form’s “submit” event, prevent the default behavior, and submit the form data using the API. JavaScript fetch A simplistic approach might look like the example below. After the page (or component) mounts, we grab the form DOM node, add an event listener that constructs a request using the form , , and , and at the end of the handler, we call the event’s method. fetch action method data preventDefault() const form = document.querySelector('form');
form.addEventListener('submit', handleSubmit);

function handleSubmit(event) {
  const form = event.currentTarget;
  fetch(form.action, {
    method: form.method,
    body: new FormData(form)
  });

  event.preventDefault();
} Now, before any JavaScript hotshots start tweeting at me about GET vs. POST and request body and and whatever else, let me just say, I know. I’m keeping the request deliberately simple because that’s not the main focus. Content-Type fetch The key issue here is the . This method prevents the browser from performing the default behavior of loading the new page and submitting the form. event.preventDefault() Now, if we look at the screen and hit submit, we can see that the page doesn’t reload, but we do see the HTTP request in our network tab. Notice the browser does not do a full page reload. Unfortunately, by using JavaScript to prevent the default behavior, we’ve actually introduced a bug that the default browser behavior does not have. When we use plain and you smash the submit button a bunch of times really quickly, you’ll notice that all the network requests except the most recent one turn red. This indicates that they were canceled, and only the most recent request is honored. HTML If we compare that to the JavaScript example, we will see that all of the requests are sent, and all of them are complete without any being canceled. This may be an issue because although each request may take a different amount of time, they could resolve in a different order than they were initiated. This means if we add functionality to the resolution of those requests, we might have some unexpected behavior. As an example, we could create a variable to increment for each request (“ “). Every time we run the function, we can increment the total count as well as capture the current number to track the current request (“ “). totalRequestCount handleSubmit thisRequestNumber When a request resolves, we can log its corresponding number to the console. fetch const form = document.querySelector('form');
form.addEventListener('submit', handleSubmit);

let totalRequestCount = 0

function handleSubmit(event) {
  totalRequestCount += 1
  const thisRequestNumber = totalRequestCount 
  const form = event.currentTarget;
  fetch(form.action, {
    method: form.method,
    body: new FormData(form)
  }).then(() => {
    console.log(thisRequestNumber)
  })
  event.preventDefault();
} Now, if we smash that submit button a bunch of times, we might see different numbers printed to the console out of order: 2, 3, 1, 4, 5. It depends on the network speed, but I think we can all agree that this is not ideal. Consider a scenario where a user triggers several requests in close succession, and upon completion, your application updates the page with their changes. The user could ultimately see inaccurate information due to requests resolving out of order. fetch This is a non-issue in the non-JavaScript world because the browser cancels any previous request and loads the page after the most recent request completes, loading the most up-to-date version. But page refreshes are not as sexy. The good news for JavaScript lovers is that we can have both a AND a consistent UI! sexy user experience We just need to do a bit more legwork. If you look at the API documentation, you’ll see that it’s possible to abort a fetch using an and the property of the options. It looks something like this: fetch AbortController signal fetch const controller = new AbortController();
fetch(url, { signal: controller.signal }); By providing the ‘s signal to the request, we can cancel the request any time the ‘s method is triggered. AbortContoller fetch AbortContoller abort You can see a clearer example in the JavaScript console. Try creating an , initiating the request, then immediately executing the method. AbortController fetch abort const controller = new AbortController();
fetch('', { signal: controller.signal });
controller.abort() You should immediately see an exception printed to the console. In Chromium browsers, it should say, “Uncaught (in promise) DOMException: The user aborted a request.” And if you explore the Network tab, you should see a failed request with the Status Text “(canceled).” With that in mind, we can add an to our form’s submit handler. The logic will be as follows: AbortController First, check for an for any previous requests. If one exists, abort it. AbortController Next, create an for the current request that can be aborted on subsequent requests. AbortController Finally, when a request resolves, remove its corresponding . AbortController There are several ways to do this, but I’ll use a to store relationships between each submitted DOM node and its respective . When a form is submitted, we can check and update the accordingly. WeakMap <form> AbortController WeakMap const pendingForms = new WeakMap();

function handleSubmit(event) {
  const form = event.currentTarget;
  const previousController = pendingForms.get(form);

  if (previousController) {
    previousController.abort();
  }
    
  const controller = new AbortController();
  pendingForms.set(form, controller);

  fetch(form.action, {
    method: form.method,
    body: new FormData(form),
    signal: controller.signal,
  }).then(() => {
    pendingForms.delete(form);
  });
  event.preventDefault();
}

const forms = document.querySelectorAll('form');
for (const form of forms) {
  form.addEventListener('submit', handleSubmit);
} The key thing is being able to associate an abort controller with its corresponding form. Using the form’s DOM node as the ‘s key is a convenient way to do that. WeakMap With that in place, we can add the ‘s signal to the request, abort any previous controllers, add new ones, and delete them upon completion. AbortController fetch Hopefully, that all makes sense. Now, if we smash that form’s submit button a bunch of times, we can see that all of the API requests except the most recent one get canceled. This means any function responding to that HTTP response will behave more as you would expect. Now, if we use that same counting and logging logic we have above, we can smash the submit button seven times and would see six exceptions (due to the ) and one log of “7” in the console. AbortController If we submit again and allow enough time for the request to resolve, we’d see “8” in the console. And if we smash the submit button a bunch of times, again, we’ll continue to see the exceptions and final request count in the right order. If you want to add some more logic to avoid seeing DOMExceptions in the console when a request is aborted, you can add a block after your request and check if the error’s name matches “ “: .catch() fetch AbortError fetch(url, {
  signal: controller.signal,
}).catch((error) => {
  // If the request was aborted, do nothing
  if (error.name === 'AbortError') return;
  // Otherwise, handle the error here or throw it back to the console
  throw error
}); Closing This whole post was focused on JavaScript-enhanced forms, but it’s probably a good idea to include an any time you create a request. It’s really too bad it’s not built into the API already. But hopefully, this shows you a good method for including it. AbortController fetch It’s also worth mentioning that this approach does not prevent the user from spamming the submit button a bunch of times. The button is still clickable, and the request still fires off, it just provides a more consistent way of dealing with responses. Unfortunately, if a user spam a submit button, those requests would still go to your backend and could use consume a bunch of unnecessary resources. does Some naive solutions may be disabling the submit button, using a , or only creating new requests after previous ones resolve. I don’t like these options because they rely on slowing down the user’s experience and only work on the client side. debounce They don’t address abuse via scripted requests. To address abuse from too many requests to your server, you would probably want to set up some . That goes beyond the scope of this post, but it was worth mentioning. rate limiting It’s also worth mentioning that rate limiting doesn’t solve the original problem of duplicate requests, race conditions, and inconsistent UI updates. Ideally, we should use both to cover both ends. Anyway, that’s all I’ve got for today. If you want to watch a video that covers this same subject, watch this. https://www.youtube.com/watch?v=w8ZIoLnh1Dc&embedable=true Thank you so much for reading. If you liked this article, please . It's one of the best ways to support me. You can also or if you want to know when new articles are published. share it sign up for my newsletter follow me on Twitter Originally published on . austingil.com

Stories, News & Mentions about CANCELO

Cancelo’s Stories on HackerNoon