The funds will help students achieve their personal and professional goals.

UGA raises almost $10 million for graduate and professional student support - UGA Today

Live coverage of campus protests in metro Atlanta and Georgia from The Atlanta Journal-Constitution

Georgia campus protests over war in Gaza - Live updates

The University of Georgia in Athens has released a statement regarding the arrest of protesters on its campus on Monday.

UGA says 16 arrested at Monday's protest; group knew the rules, school says

Jump To Top of Page MGOLF: UGA assigned to NCAA Austin Regional The University of Georgia men’s golf team will ... read article

Daily Dawg Thread: May 02, 2024 – Bulldawg Illustrated

UGASports examines some of the remaining defensive line battles for Georgia in the 2025 class.

What's Next For UGA's D-line After Stephon Shivers' Commitment? - UGASports

Dawg Post insider Matt DeBary gives the latest on Georgia&#x27;s newest commitment.

BREAKING: Kirby Smart, UGA Football Land Massive DL Commitment | Dawg Post

ATHENS-----Georgia plays host to No. 8 Alabama starting Friday in the SEC home opener at Foley Field. The game times are 6 p.m. Friday, Noon on Saturday and ...

Bulldogs Battle Alabama In SEC Home Opener - University of Georgia Athletics

Oscar Delp is taking the role of elder statesman in the tight end room.

UGASports - Oscar Delp dons the cape for UGA

UGA students are being hailed as heroes for saving their life-saving action.

UGA freshmen hailed heroes for saving children’s lives following rollover crash

Five University of Georgia sorority sisters are being called heroes by the Burke County Sheriff&#x27;s Office for saving a woman and her children after a car crash left them submerged in water.

UGA students describe saving family from car that crashed into creek

UGLA

ugla

UGLA ERP was founded in 2022 in Kyiv with the goal of facilitating business process management, increasing productivity, and enhancing the competitiveness of enterprises. Ukrainian ERP offers an intuitive and powerful toolkit for business process automation, as well as data analysis and visualization to help companies make more informed decisions. StartUps2023 Runner-up Tell us how your startup is changing the world. ERP systems have been an undeniable trend in recent years despite "black swans" such as pandemics and wars. Every year, ERP demonstrates steady growth. Today, even large companies offer their employees hybrid or fully online work formats - after the global pandemic of recent years, working from home or from anywhere in the world has become a daily norm. In Ukraine, the impact of the pandemic in 2022 was amplified by the war-forced migration within the country and externally became a significant factor in cementing remote work formats. Some large companies, especially those without a physical production cycle, may not have a single office or even coworking space, so all collaboration takes place online. This should also be taken into account when building business processes. Therefore, cloud solutions are becoming a cornerstone for most companies already. In addition to the almost traditional cloud solutions, their mobile versions are also gaining momentum - in today's fast-paced world, more and more people are doing their work on the go or simultaneously from multiple devices. Thus, UGLA ERP is changing the world precisely because it is accessible from anywhere, allowing you to provide your employees with the flexibility to work whenever and wherever they want. Not to mention that cloud solutions are generally more accessible than local systems. What sets you apart from the competition? UGLA ERP is a next-generation system that combines all the tools for managing and planning business processes. We developed our program in collaboration with advisors from various industries, focusing on business needs and user convenience for all employees. Additionally, UGLA ERP has a workflow feature that allows you to customize the business processes you need. By choosing UGLA ERP, you get all the necessary tools right away, with no additional costs. The cost of our software is affordable for any business. What do you love about your team, and why are you the ones to solve this problem? First of all, our team consists of very brave guys and girls, as we constantly work in Kyiv during the war. We have a great combination of experience and creativity, which is why we manage to implement what sometimes seems impossible. That's why I think we're the ones to solve the problem of business process planning because we've managed to combine experience, intelligence, and creativity. And, of course, we're 100% fearless. If you weren’t building your startup, what would you be doing? I think we would create something else but 100% Ukrainian)) At the moment, how do you measure success? What are your core metrics? Of course, the number of satisfied clients is essential to us. But it's also important for us to receive feedback and understand that our partners confirm that the main goal of UGLA ERP is being achieved. It involves saving time for employees and management for strategic tasks, personal development, and time with family and friends. As for success metrics, we use standard business metrics such as CAC (Customer Acquisition Cost), MRR (Monthly Recurring Revenue), ARR (Annual Recurring Revenue), LTV (Customer Lifetime Value), ARPU (Average Revenue Per User), Revenue, and others. What goals are you looking forward to accomplishing in 2024? Firstly, to create solutions for other industries such as pharmaceuticals, retail, manufacturing, etc. Secondly, we have specific plans to enter new markets, namely the USA, UK, and some European countries. Of course, there are plans regarding the number of our partners. Which trend(s) are you most excited about in 2024? Share your reasons. I believe that the biggest trends will be associated with even greater integration of ERP into all business processes and planning. Undoubtedly, the application of AI, IoT, and GenAI. Of course, data security will also be crucial. 2023 had been another crazy year, especially in tech, with layoffs and the Generative AI takeover! Which trend are you most concerned about? Be as brief or as detailed as you like. The development of AI, ML, and GenAI. Share your biggest success so far and/or your biggest failure so far. Oh, I'm sure our biggest success is that we continue to work despite all the obstacles. Overall, we had a successful year; we participated in international conferences such as WEB SUMMIT and Viva Tech, where we were able to represent Ukraine and our software. We would love your feedback on HackerNoon as a tech publication! How has your experience been with us? We're just starting our journey with you, but we're already in love! There's so much interesting information, so many opportunities for startups, convenience, and creativity. Any words of wisdom you’d like to share with us? Perhaps "be brave no matter what". Startups of The Year is HackerNoon’s Flagship community-driven event celebrating startups that survived and thrived in 2023. 30,000 startups across 4200+ cities and six continents participated this year to be crowned the best startup in their city. See our global winners announcement . here Companies that blog more get 67% more leads - Jumpstart your company’s blogging journey by purchasing our . Business Blogging Package The 2023 Startups Of The Year is sponsored by: . . The winners will get a free .Tech Domain, a HackerNoon NFT, and a Tech Company News Page. TECH Domains

Meet UGLA ERP, Runner-up of the Startups of the Year in Kyiv.

Pretty Slow / Ugly Fast: How to Optimize your Code in 19 Different Ways

In this article, I'll cover three approaches to implementing short HTTP polling, using client-side JavaScript (TypeScript). Short polling involves making repeated, separate requests to check the status of a resource. Imagine we have an API with two endpoints: postTask and getTask. After posting a task (using the postTask endpoint), we need to continuously poll the getTask endpoint until it returns a status of either DONE or FAILED. We'll start by exploring the Ugly approach. The Ugly The first thing that comes into mind is a recursive setTimeout: function handlePolling(
  taskId: string,
  done: (result: string) => void,
  failed: (err: string) => void,
): void {
  API.getTask(taskId).then(response => {
    switch (response.status) {
      case 'IN_PROGRESS':
        setTimeout(() => handlePolling(taskId, done, failed), 1000);
        break;
      case 'DONE':
        return done(response.result);
      case 'FAILED':
        return failed('polling failed');
      default:
        return failed(`unexpected status = ${response.status}`);
    }
  }).catch(err => {
    failed(`getTask failed - ${err}`);
  });
} This approach is quite straightforward but comes with a couple of notable flaws: Callbacks: done & failed.
While this is largely a matter of preference, using callbacks can start to resemble the infamous "callback hell" from early Node.js days. If we tried to return a Promise, we'd encounter a branching structure since each Promise could either resolve or reject. As a result, we're forced to stick with callbacks for simplicity.


Recursion
The bigger issue is that recursion can make debugging more difficult. Each recursive call adds complexity, making it harder to track the flow and pinpoint where things go wrong. The (Not-So) Bad Let’s rewrite it in a more linear fashion with async & await: const sleep = (timeout: number) => new Promise((resolve) => setTimeout(resolve, timeout));

async function handlePolling(taskId: string): Promise<string> {
  while (true) {
    try {
      await sleep(1000);
      response = await API.getTask(taskId);

      switch (response.status) {
        case 'IN_PROGRESS':
          continue;
        case 'DONE':
          return response.result;
        case 'FAILED':
          return Promise.reject('polling failed');
        default:
          return Promise.reject(`unexpected status = ${response.status}`);
      }
    } catch (err) {
      return Promise.reject(`getTask failed - ${err}`);
    }
  }
} This approach is much cleaner. We've encapsulated setTimeout within a sleep function, and we now return a Promise that can be awaited. The code is more readable and easier to maintain. The only detail that stands out is the while(true) loop. This can be improved by using while(status === 'IN_PROGRESS'), which makes the intent clearer. Additionally, it's a good idea to implement a safety mechanism to limit the number of getTask requests. This helps protect against the rare case where the API might get stuck in an infinite loop or experience an unexpected delay. The Good The approach I prefer the most is using RxJS — a library specifically designed for handling event streams. You can think of it as “lodash for Promises.” RxJS provides a powerful and flexible way to manage asynchronous events like HTTP polling, making it easier to handle complex workflows in a more declarative manner, e.g.: function handlePolling(taskId: string) {
  return new Promise<string>((resolve, reject) => {
    interval(1000).pipe(
      switchMap(() => API.getTask(taskId)), // runs the request each time the interval emits
      takeWhile(response => response.status === 'IN_PROGRESS', true),
      filter(response => response.status !== 'IN_PROGRESS'),
    ).subscribe({
      next: response => {
        switch (response.status) {
          case 'DONE':
            return response.result;
          case 'FAILED':
            return Promise.reject('polling failed');
          default:
            return Promise.reject(`unexpected status = ${response.status}`);
        }
      },
      error: err => reject(`getTask failed - ${err}`),
    });
} What I love about RxJS is how straightforward it makes the code. With the takeWhile operator, we clearly define when to stop the loop, and by using the filter operator, we can skip handling any responses where the status is still IN_PROGRESS. This creates a clean, declarative flow that's easy to read and maintain. Conclusion Both the "Good" and the "Not-So-Bad" approaches are viable ways to handle HTTP polling. However, if your project involves a significant amount of asynchronous logic — such as polling, interdependent async tasks, background loading or complex calculations — then it’s worth considering adopting RxJS. Its powerful tools for managing streams of asynchronous events can greatly simplify your code and make it more maintainable in the long run. In this article, I'll cover three approaches to implementing short HTTP polling, using client-side JavaScript (TypeScript). Short polling involves making repeated, separate requests to check the status of a resource. short Imagine we have an API with two endpoints: postTask and getTask . After posting a task (using the postTask endpoint), we need to continuously poll the getTask endpoint until it returns a status of either DONE or FAILED . postTask getTask postTask getTask DONE FAILED We'll start by exploring the Ugly approach. Ugly The Ugly The first thing that comes into mind is a recursive setTimeout : setTimeout function handlePolling(
  taskId: string,
  done: (result: string) => void,
  failed: (err: string) => void,
): void {
  API.getTask(taskId).then(response => {
    switch (response.status) {
      case 'IN_PROGRESS':
        setTimeout(() => handlePolling(taskId, done, failed), 1000);
        break;
      case 'DONE':
        return done(response.result);
      case 'FAILED':
        return failed('polling failed');
      default:
        return failed(`unexpected status = ${response.status}`);
    }
  }).catch(err => {
    failed(`getTask failed - ${err}`);
  });
} function handlePolling(
  taskId: string,
  done: (result: string) => void,
  failed: (err: string) => void,
): void {
  API.getTask(taskId).then(response => {
    switch (response.status) {
      case 'IN_PROGRESS':
        setTimeout(() => handlePolling(taskId, done, failed), 1000);
        break;
      case 'DONE':
        return done(response.result);
      case 'FAILED':
        return failed('polling failed');
      default:
        return failed(`unexpected status = ${response.status}`);
    }
  }).catch(err => {
    failed(`getTask failed - ${err}`);
  });
} This approach is quite straightforward but comes with a couple of notable flaws: Callbacks: done & failed.
While this is largely a matter of preference, using callbacks can start to resemble the infamous "callback hell" from early Node.js days. If we tried to return a Promise, we'd encounter a branching structure since each Promise could either resolve or reject. As a result, we're forced to stick with callbacks for simplicity. Recursion
The bigger issue is that recursion can make debugging more difficult. Each recursive call adds complexity, making it harder to track the flow and pinpoint where things go wrong. Callbacks: done & failed. While this is largely a matter of preference, using callbacks can start to resemble the infamous "callback hell" from early Node.js days. If we tried to return a Promise, we'd encounter a branching structure since each Promise could either resolve or reject. As a result, we're forced to stick with callbacks for simplicity. Callbacks : done & failed . Callbacks done failed While this is largely a matter of preference, using callbacks can start to resemble the infamous "callback hell" from early Node.js days. If we tried to return a Promise, we'd encounter a branching structure since each Promise could either resolve or reject. As a result, we're forced to stick with callbacks for simplicity. Recursion The bigger issue is that recursion can make debugging more difficult. Each recursive call adds complexity, making it harder to track the flow and pinpoint where things go wrong. Recursion Recursion The bigger issue is that recursion can make debugging more difficult. Each recursive call adds complexity, making it harder to track the flow and pinpoint where things go wrong. The (Not-So) Bad Let’s rewrite it in a more linear fashion with async & await : async await const sleep = (timeout: number) => new Promise((resolve) => setTimeout(resolve, timeout));

async function handlePolling(taskId: string): Promise<string> {
  while (true) {
    try {
      await sleep(1000);
      response = await API.getTask(taskId);

      switch (response.status) {
        case 'IN_PROGRESS':
          continue;
        case 'DONE':
          return response.result;
        case 'FAILED':
          return Promise.reject('polling failed');
        default:
          return Promise.reject(`unexpected status = ${response.status}`);
      }
    } catch (err) {
      return Promise.reject(`getTask failed - ${err}`);
    }
  }
} const sleep = (timeout: number) => new Promise((resolve) => setTimeout(resolve, timeout));

async function handlePolling(taskId: string): Promise<string> {
  while (true) {
    try {
      await sleep(1000);
      response = await API.getTask(taskId);

      switch (response.status) {
        case 'IN_PROGRESS':
          continue;
        case 'DONE':
          return response.result;
        case 'FAILED':
          return Promise.reject('polling failed');
        default:
          return Promise.reject(`unexpected status = ${response.status}`);
      }
    } catch (err) {
      return Promise.reject(`getTask failed - ${err}`);
    }
  }
} This approach is much cleaner. We've encapsulated setTimeout within a sleep function, and we now return a Promise that can be awaited. The code is more readable and easier to maintain. setTimeout sleep The only detail that stands out is the while(true) loop. This can be improved by using while(status === 'IN_PROGRESS') , which makes the intent clearer. Additionally, it's a good idea to implement a safety mechanism to limit the number of getTask requests. This helps protect against the rare case where the API might get stuck in an infinite loop or experience an unexpected delay. while(true) while(status === 'IN_PROGRESS') getTask The Good The approach I prefer the most is using RxJS — a library specifically designed for handling event streams. You can think of it as “lodash for Promises.” RxJS provides a powerful and flexible way to manage asynchronous events like HTTP polling, making it easier to handle complex workflows in a more declarative manner, e.g.: function handlePolling(taskId: string) {
  return new Promise<string>((resolve, reject) => {
    interval(1000).pipe(
      switchMap(() => API.getTask(taskId)), // runs the request each time the interval emits
      takeWhile(response => response.status === 'IN_PROGRESS', true),
      filter(response => response.status !== 'IN_PROGRESS'),
    ).subscribe({
      next: response => {
        switch (response.status) {
          case 'DONE':
            return response.result;
          case 'FAILED':
            return Promise.reject('polling failed');
          default:
            return Promise.reject(`unexpected status = ${response.status}`);
        }
      },
      error: err => reject(`getTask failed - ${err}`),
    });
} function handlePolling(taskId: string) {
  return new Promise<string>((resolve, reject) => {
    interval(1000).pipe(
      switchMap(() => API.getTask(taskId)), // runs the request each time the interval emits
      takeWhile(response => response.status === 'IN_PROGRESS', true),
      filter(response => response.status !== 'IN_PROGRESS'),
    ).subscribe({
      next: response => {
        switch (response.status) {
          case 'DONE':
            return response.result;
          case 'FAILED':
            return Promise.reject('polling failed');
          default:
            return Promise.reject(`unexpected status = ${response.status}`);
        }
      },
      error: err => reject(`getTask failed - ${err}`),
    });
} What I love about RxJS is how straightforward it makes the code. With the takeWhile operator, we clearly define when to stop the loop, and by using the filter operator, we can skip handling any responses where the status is still IN_PROGRESS . This creates a clean, declarative flow that's easy to read and maintain. takeWhile filter IN_PROGRESS Conclusion Both the "Good" and the "Not-So-Bad" approaches are viable ways to handle HTTP polling. However, if your project involves a significant amount of asynchronous logic — such as polling, interdependent async tasks, background loading or complex calculations — then it’s worth considering adopting RxJS. Its powerful tools for managing streams of asynchronous events can greatly simplify your code and make it more maintainable in the long run.

HTTP Polling - the Good, the Bad and the Ugly

In Web3 space, where blockchain technology promises to revolutionize everything from finance to entertainment, a common complaint is that Web3 marketing teams lack the expertise to execute effective Web2 marketing campaigns. This often results in an inability to reach and onboard the masses into the Web3 ecosystem. However, one company is breaking that mold and showing the industry how it's done. Cracking the Code: Upland's Success on TikTok Upland, a Web3-based virtual property trading game, has successfully bridged the gap between the traditional Web2 audience and the burgeoning Web3 space. Their secret? A cleverly implemented marketing plan that leverages TikTok, one of the most powerful social media platforms of Web2. Recognizing TikTok's immense potential for reaching and engaging a broad audience, Upland launched a targeted campaign that caught the attention of both TikTok users and gamers alike. In fact, Upland was featured by TikTok for Business as a success story, demonstrating how a Web3 company can effectively utilize Web2 tools to achieve impressive results. Upland's campaign was nothing short of strategic brilliance. They wisely identified TikTok as a crucial platform for attracting long-term players and launched a U.S. campaign focused on Mobile App Installs and App Event Optimization. But Upland didn't stop there; they took it a step further by pivoting their content strategy towards user-generated content (UGC). This move significantly boosted engagement, allowing users to become part of the Upland narrative and creating a sense of community and ownership often missing in traditional marketing efforts. The results were truly remarkable. After expanding their campaign to Brazil and other Spanish-speaking Latin American countries through the TikTok Creative Exchange, Upland saw a staggering increase in user flow—more than 45 times higher than before. The campaign demonstrated that a well-executed Web2 marketing strategy can yield significant results for Web3 companies, with a 23% increase in registration volume and improved cost metrics. A Blueprint for Web3 Success Upland's success on TikTok serves as a blueprint for other Web3 companies looking to scale and onboard new users. It highlights the importance of understanding the dynamics of Web2 platforms and leveraging them to engage with potential users in a way that feels organic and authentic. The lesson here is clear: to succeed in the Web3 world, you need to master the art of Web2 marketing. While debates continue on X (formerly Twitter) about the effectiveness of Web3 marketing teams, Upland's success story on TikTok stands as a testament to what can be achieved when traditional marketing techniques are adapted and implemented in a new environment. The integration of user-generated content, targeted campaigns, and platform-specific strategies has not only resulted in significant growth for Upland but has also set a new standard for how Web3 companies can—and should—approach marketing. Upland's strategy provides a shining example of how to do it right. Upland is more than just a game; it's a masterclass in modern marketing, meeting users where they are and creating impactful campaigns on a platform as significant as TikTok. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. In Web3 space, where blockchain technology promises to revolutionize everything from finance to entertainment, a common complaint is that Web3 marketing teams lack the expertise to execute effective Web2 marketing campaigns. This often results in an inability to reach and onboard the masses into the Web3 ecosystem. However, one company is breaking that mold and showing the industry how it's done. Cracking the Code: Upland's Success on TikTok Upland , a Web3-based virtual property trading game, has successfully bridged the gap between the traditional Web2 audience and the burgeoning Web3 space. Their secret? A cleverly implemented marketing plan that leverages TikTok, one of the most powerful social media platforms of Web2. Upland Recognizing TikTok's immense potential for reaching and engaging a broad audience, Upland launched a targeted campaign that caught the attention of both TikTok users and gamers alike. In fact, Upland was featured by TikTok for Business as a success story, demonstrating how a Web3 company can effectively utilize Web2 tools to achieve impressive results. Upland's campaign was nothing short of strategic brilliance. They wisely identified TikTok as a crucial platform for attracting long-term players and launched a U.S. campaign focused on Mobile App Installs and App Event Optimization. But Upland didn't stop there; they took it a step further by pivoting their content strategy towards user-generated content (UGC). This move significantly boosted engagement, allowing users to become part of the Upland narrative and creating a sense of community and ownership often missing in traditional marketing efforts. The results were truly remarkable. After expanding their campaign to Brazil and other Spanish-speaking Latin American countries through the TikTok Creative Exchange, Upland saw a staggering increase in user flow—more than 45 times higher than before. The campaign demonstrated that a well-executed Web2 marketing strategy can yield significant results for Web3 companies, with a 23% increase in registration volume and improved cost metrics. A Blueprint for Web3 Success Upland's success on TikTok serves as a blueprint for other Web3 companies looking to scale and onboard new users. It highlights the importance of understanding the dynamics of Web2 platforms and leveraging them to engage with potential users in a way that feels organic and authentic. The lesson here is clear: to succeed in the Web3 world, you need to master the art of Web2 marketing. While debates continue on X (formerly Twitter) about the effectiveness of Web3 marketing teams, Upland's success story on TikTok stands as a testament to what can be achieved when traditional marketing techniques are adapted and implemented in a new environment. The integration of user-generated content, targeted campaigns, and platform-specific strategies has not only resulted in significant growth for Upland but has also set a new standard for how Web3 companies can—and should—approach marketing. Upland's strategy provides a shining example of how to do it right. Upland is more than just a game; it's a masterclass in modern marketing, meeting users where they are and creating impactful campaigns on a platform as significant as TikTok. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

Upland's Marketing Strategy Takes TikTok by Storm

Upland এর বিপণন কৌশল ঝড় দ্বারা TikTok নেয়

Uplands Marketingstrategie erobert TikTok im Sturm

La estrategia de marketing de Upland arrasa en TikTok

La stratégie marketing d'Upland prend d'assaut TikTok

अपलैंड की मार्केटिंग रणनीति ने टिकटॉक को तूफान में धकेल दिया

アップランドのマーケティング戦略がTikTokを席巻

Upland의 마케팅 전략이 TikTok을 폭풍으로 몰아넣었습니다.

A estratégia de marketing da Upland conquista o TikTok como uma tempestade

Маркетинговая стратегия Upland покорила TikTok

Upland'ın Pazarlama Stratejisi TikTok'u Storm'dan Alıyor

Chiến lược tiếp thị của Upland đánh bại TikTok

Upland 的营销策略让 TikTok 大获成功

Tiktok Inc., and ByteDance LTD., v. Merrick B. Garland Update Court Filing, retrieved on May 7, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 3 of 11. B. The Government Previously Made Unlawful Attempts to Ban TikTok. 18. Petitioners’ efforts to address the U.S. government’s asserted concerns regarding the TikTok platform date back to 2019. At that time, Petitioners began engaging with CFIUS, which had initiated a review of ByteDance Ltd.’s 2017 acquisition of Musical.ly, another Internet-based video-sharing platform. 19. Petitioners were in the early stages of engaging with CFIUS on a voluntary basis to address the government’s concerns, when on August 6, 2020, President Trump abruptly issued an executive order purporting to ban TikTok under the International Emergency Economic Powers Act (“IEEPA”), 50 U.S.C. §§ 1701–08. See 85 Fed. Reg. 48,637 (the “Ban Order”). Two separate district courts preliminarily enjoined the Ban Order, concluding (among other things) that it exceeded the President’s IEEPA authority. TikTok Inc. v. Trump, 490 F. Supp. 3d 73, 83 (D.D.C. 2020); TikTok Inc. v. Trump, 507 F. Supp. 3d 92, 112 (D.D.C. 2020); Marland v. Trump, 498 F. Supp. 3d 624, 641 (E.D. Pa. 2020). 20. Specifically, as these courts correctly recognized, the President’s IEEPA authority “to deal with any unusual and extraordinary threat” to the nation “does not include the authority to regulate or prohibit, directly or indirectly . . . [any] personal communication” or the importation or exportation “of any information or informational materials.” 50 U.S.C. § 1702(b)(1), (3). These restrictions on the President’s IEEPA authority — which Congress expanded through multiple amendments to the statute — were designed “to prevent the statute from running afoul of the First Amendment.” United States v. Amirnazmi, 645 F.3d 564, 585 (3d Cir. 2011) (quotation marks omitted); see also Kalantari v. NITV, Inc., 352 F.3d 1202, 1205 (9th Cir. 2003) (IEEPA’s limitations necessary “to prevent the executive branch from restricting the international flow of materials protected by the First Amendment”); Marland, 498 F. Supp. 3d at 629 (same). 21. Looking to the foundational First Amendment principles codified in IEEPA’s text and legislative history, these courts concluded that President Trump’s efforts to ban TikTok violated the statute and raised “serious” constitutional questions (which were unnecessary to decide under the doctrine of constitutional avoidance). TikTok Inc., 507 F. Supp. 3d at 112 n.6; TikTok Inc., 490 F. Supp. 3d at 83 n.3. The courts granted the government’s motions to voluntarily dismiss its appeals after President Biden withdrew the Ban Order. See TikTok Inc. v. Biden, No. 20-5302, 2021 WL 3713550 (D.C. Cir. July 20, 2021); TikTok Inc. v. Biden, No. 20-5381, 2021 WL 3082803 (D.C. Cir. July 14, 2021); Marland v. Trump, No. 20-3322, 2021 WL 5346749 (3d Cir. July 14, 2021). 22. Separately, acting on a CFIUS referral, President Trump on August 14, 2020 issued an order under Section 721 of the Defense Production Act, 50 U.S.C. § 4565, purporting to direct ByteDance to divest from TikTok’s U.S. business and U.S. user data. 85 Fed. Reg. 51,297 (the “Divestment Order”). On November 10, 2020, Petitioners petitioned this Court for review of the Divestment Order and underlying CFIUS actions, arguing, among other things, that the government lacked jurisdiction under the statute. See Petition for Review, TikTok Inc. v. CFIUS, No. 20-1444 (D.C. Cir. Nov. 10, 2020). That petition was held in abeyance in February 2021 on the parties’ joint motion to allow the parties to negotiate a resolution. The government has filed status reports every 60 days since then, most recently on April 22, 2024. Those status reports have consistently reported that “[t]he parties continue to be involved in ongoing negotiations” and “[a]beyance continues to be appropriate.” See, e.g., Status Report, TikTok Inc. v. CFIUS, No. 20-1444 (D.C. Cir. Apr. 22, 2024). 23. Between January 2021 and August 2022, Petitioners and CFIUS engaged in an intensive, fact-based process to develop a National Security Agreement that would resolve the U.S. government’s concerns about whether Chinese authorities might be able to access U.S. user data or manipulate content on TikTok, as well as resolve the pending CFIUS dispute. During that time, Petitioners and government officials communicated regularly, often several times a week — including several in-person meetings — about the government’s concerns and potential solutions. The result was an approximately 90-page draft National Security Agreement with detailed annexes embodying a comprehensive solution addressing the government’s national security concerns. Notably, the draft National Security Agreement provided that all protected U.S. user data (as defined in the agreement) would be stored in the cloud environment of a U.S.-government-approved partner, Oracle Corporation, which would also review and vet the TikTok source code. 24. From Petitioners’ perspective, all indications were that they were nearing a final agreement. After August 2022, however, CFIUS without explanation stopped engaging with Petitioners in meaningful discussions about the National Security Agreement. Petitioners repeatedly asked why discussions had ended and how they might be restarted, but they did not receive a substantive response. In March 2023, without providing any justification for why the draft National Security Agreement was inadequate, CFIUS insisted that ByteDance would be required to divest the U.S. TikTok business. 25. Since March 2023, Petitioners have explained to CFIUS, in multiple written communications and in-person meetings, that a divestiture of the U.S. TikTok business from the rest of the integrated global TikTok platform and business of the sort now required by the Act is not feasible. CFIUS has never articulated any basis for disagreeing with that assessment, offering instead only a conclusory assertion that the reason ByteDance was not divesting was because it was simply unwilling to do so. The Act nonetheless incorporates precisely such an infeasible divestiture standard. 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 retrieved on May 7, 2024, from sf16-va.tiktokcdn.com 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. Tiktok Inc., and ByteDance LTD., v. Merrick B. Garland Update Court Filing, retrieved on May 7, 2024, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This part is 3 of 11. Tiktok Inc., and ByteDance LTD., v. Merrick B. Garland Update Court Filing, retrieved on May 7, 2024, is part of HackerNoon’s Legal PDF Series . You can jump to any part in this filing here . This part is 3 of 11. HackerNoon’s Legal PDF Series here B. The Government Previously Made Unlawful Attempts to Ban TikTok. 18. Petitioners’ efforts to address the U.S. government’s asserted concerns regarding the TikTok platform date back to 2019. At that time, Petitioners began engaging with CFIUS, which had initiated a review of ByteDance Ltd.’s 2017 acquisition of Musical.ly, another Internet-based video-sharing platform. 19. Petitioners were in the early stages of engaging with CFIUS on a voluntary basis to address the government’s concerns, when on August 6, 2020, President Trump abruptly issued an executive order purporting to ban TikTok under the International Emergency Economic Powers Act (“IEEPA”), 50 U.S.C. §§ 1701–08. See 85 Fed. Reg. 48,637 (the “Ban Order”). Two separate district courts preliminarily enjoined the Ban Order, concluding (among other things) that it exceeded the President’s IEEPA authority. TikTok Inc. v. Trump, 490 F. Supp. 3d 73, 83 (D.D.C. 2020); TikTok Inc. v. Trump, 507 F. Supp. 3d 92, 112 (D.D.C. 2020); Marland v. Trump, 498 F. Supp. 3d 624, 641 (E.D. Pa. 2020). 20. Specifically, as these courts correctly recognized, the President’s IEEPA authority “to deal with any unusual and extraordinary threat” to the nation “does not include the authority to regulate or prohibit, directly or indirectly . . . [any] personal communication” or the importation or exportation “of any information or informational materials.” 50 U.S.C. § 1702(b)(1), (3). These restrictions on the President’s IEEPA authority — which Congress expanded through multiple amendments to the statute — were designed “to prevent the statute from running afoul of the First Amendment.” United States v. Amirnazmi, 645 F.3d 564, 585 (3d Cir. 2011) (quotation marks omitted); see also Kalantari v. NITV, Inc., 352 F.3d 1202, 1205 (9th Cir. 2003) (IEEPA’s limitations necessary “to prevent the executive branch from restricting the international flow of materials protected by the First Amendment”); Marland, 498 F. Supp. 3d at 629 (same). 21. Looking to the foundational First Amendment principles codified in IEEPA’s text and legislative history, these courts concluded that President Trump’s efforts to ban TikTok violated the statute and raised “serious” constitutional questions (which were unnecessary to decide under the doctrine of constitutional avoidance). TikTok Inc., 507 F. Supp. 3d at 112 n.6; TikTok Inc., 490 F. Supp. 3d at 83 n.3. The courts granted the government’s motions to voluntarily dismiss its appeals after President Biden withdrew the Ban Order. See TikTok Inc. v. Biden, No. 20-5302, 2021 WL 3713550 (D.C. Cir. July 20, 2021); TikTok Inc. v. Biden, No. 20-5381, 2021 WL 3082803 (D.C. Cir. July 14, 2021); Marland v. Trump, No. 20-3322, 2021 WL 5346749 (3d Cir. July 14, 2021). 22. Separately, acting on a CFIUS referral, President Trump on August 14, 2020 issued an order under Section 721 of the Defense Production Act, 50 U.S.C. § 4565, purporting to direct ByteDance to divest from TikTok’s U.S. business and U.S. user data. 85 Fed. Reg. 51,297 (the “Divestment Order”). On November 10, 2020, Petitioners petitioned this Court for review of the Divestment Order and underlying CFIUS actions, arguing, among other things, that the government lacked jurisdiction under the statute. See Petition for Review, TikTok Inc. v. CFIUS, No. 20-1444 (D.C. Cir. Nov. 10, 2020). That petition was held in abeyance in February 2021 on the parties’ joint motion to allow the parties to negotiate a resolution. The government has filed status reports every 60 days since then, most recently on April 22, 2024. Those status reports have consistently reported that “[t]he parties continue to be involved in ongoing negotiations” and “[a]beyance continues to be appropriate.” See, e.g., Status Report, TikTok Inc. v. CFIUS, No. 20-1444 (D.C. Cir. Apr. 22, 2024). 23. Between January 2021 and August 2022, Petitioners and CFIUS engaged in an intensive, fact-based process to develop a National Security Agreement that would resolve the U.S. government’s concerns about whether Chinese authorities might be able to access U.S. user data or manipulate content on TikTok, as well as resolve the pending CFIUS dispute. During that time, Petitioners and government officials communicated regularly, often several times a week — including several in-person meetings — about the government’s concerns and potential solutions. The result was an approximately 90-page draft National Security Agreement with detailed annexes embodying a comprehensive solution addressing the government’s national security concerns. Notably, the draft National Security Agreement provided that all protected U.S. user data (as defined in the agreement) would be stored in the cloud environment of a U.S.-government-approved partner, Oracle Corporation, which would also review and vet the TikTok source code. 24. From Petitioners’ perspective, all indications were that they were nearing a final agreement. After August 2022, however, CFIUS without explanation stopped engaging with Petitioners in meaningful discussions about the National Security Agreement. Petitioners repeatedly asked why discussions had ended and how they might be restarted, but they did not receive a substantive response. In March 2023, without providing any justification for why the draft National Security Agreement was inadequate, CFIUS insisted that ByteDance would be required to divest the U.S. TikTok business. 25. Since March 2023, Petitioners have explained to CFIUS, in multiple written communications and in-person meetings, that a divestiture of the U.S. TikTok business from the rest of the integrated global TikTok platform and business of the sort now required by the Act is not feasible. CFIUS has never articulated any basis for disagreeing with that assessment, offering instead only a conclusory assertion that the reason ByteDance was not divesting was because it was simply unwilling to do so. The Act nonetheless incorporates precisely such an infeasible divestiture standard. Continue Reading Here. Continue Reading Here . Here About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on May 7, 2024, from sf16-va.tiktokcdn.com 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. About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on May 7, 2024, from sf16-va.tiktokcdn.com 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. sf16-va.tiktokcdn.com

TikTok Calls Ban Attempts by U.S. Government Unlawful 

This year's Upland’s Genesis Hackathon intends to set new standards in the Web3 and blockchain gaming sectors. Upland is organising the Upland’s Genesis Week event, which will shift away from its conventional methodology in favour of a more idea-centric competition. In an exciting change, the 2024 iteration will no longer need participants to present a functional prototype, allowing for a greater emphasis on developing company ideas and planning methods. Main Features of the Hackathon Upland is introducing SPARKLET, a solution designed to facilitate the integration of blockchain applications with blockchain technology. This new information comes at a time when the Web3 domain is seeing resuscitation, with blockchain gaming at the forefront of this trend. The Genesis Hackathon aims to capitalise on these successes by providing participants with a platform that allows them to establish and enhance the capabilities of their own digital communities. The hackathon challenges participants to use the Upland platform and its developer tools to build a new service, game, or experience. Participants will have ten days to prepare a business strategy that defines their aims and techniques. Because they are focused on clarity, originality, and practicality, these plans are critical in determining which teams will advance to the final round. Entries must be submitted by May 10th, 9 AM PT, with finalists notified by May 13th, 2024. Those who make it to the final round will submit detailed presentations, aiming for a spot to pitch live at the Genesis Week event. Form Submission for Hackathon. Prizes and Incentives The hackathon offers substantial incentives, with prizes structured across multiple phases: Phase

Award Type

Details



1

Kickoff Grant

$2,500



2

MVP Deployment Bonus

$15,000 upon successful integration



3

Sparklet Grant Program

Opportunity to pitch for additional support Finalists will compete for these prizes during the Upland Awards Show on June 7th, where the top projects will be showcased. Logistics and Additional Benefits Finalists will travel to Las Vegas, with Upland covering hotel expenses and providing travel stipends of up to $500 for domestic and $1,000 for international flights. This arrangement not only alleviates financial burdens but also enhances the overall experience, allowing participants to focus fully on their presentations. The Genesis 2024 Hackathon is a launchpad for tomorrow's innovators in the Web3 space. With significant prizes, strategic opportunities, and the chance to influence the burgeoning blockchain gaming market, this event is a cornerstone for technological advancement. Don’t miss out—mark your calendar, prepare your submission, and take part in shaping the future of the digital world. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. This year's Upland’s Genesis Hackathon intends to set new standards in the Web3 and blockchain gaming sectors. Upland is organising the Upland’s Genesis Week event, which will shift away from its conventional methodology in favour of a more idea-centric competition. In an exciting change, the 2024 iteration will no longer need participants to present a functional prototype, allowing for a greater emphasis on developing company ideas and planning methods. Main Features of the Hackathon Main Features of the Hackathon Upland is introducing SPARKLET, a solution designed to facilitate the integration of blockchain applications with blockchain technology. This new information comes at a time when the Web3 domain is seeing resuscitation, with blockchain gaming at the forefront of this trend. The Genesis Hackathon aims to capitalise on these successes by providing participants with a platform that allows them to establish and enhance the capabilities of their own digital communities. The hackathon challenges participants to use the Upland platform and its developer tools to build a new service, game, or experience. Participants will have ten days to prepare a business strategy that defines their aims and techniques. Because they are focused on clarity, originality, and practicality, these plans are critical in determining which teams will advance to the final round. Entries must be submitted by May 10th, 9 AM PT, with finalists notified by May 13th, 2024. Those who make it to the final round will submit detailed presentations, aiming for a spot to pitch live at the Genesis Week event. submitted Form Submission for Hackathon. Form Submission Prizes and Incentives Prizes and Incentives The hackathon offers substantial incentives, with prizes structured across multiple phases: Phase

Award Type

Details



1

Kickoff Grant

$2,500



2

MVP Deployment Bonus

$15,000 upon successful integration



3

Sparklet Grant Program

Opportunity to pitch for additional support Phase

Award Type

Details 1

Kickoff Grant

$2,500 2

MVP Deployment Bonus

$15,000 upon successful integration 3

Sparklet Grant Program

Opportunity to pitch for additional support Phase Award Type Details Phase Phase Award Type Award Type Details Details 1 Kickoff Grant $2,500 1 1 Kickoff Grant Kickoff Grant $2,500 $2,500 2 MVP Deployment Bonus $15,000 upon successful integration 2 2 MVP Deployment Bonus MVP Deployment Bonus $15,000 upon successful integration $15,000 upon successful integration 3 Sparklet Grant Program Opportunity to pitch for additional support 3 3 Sparklet Grant Program Sparklet Grant Program Opportunity to pitch for additional support Opportunity to pitch for additional support Finalists will compete for these prizes during the Upland Awards Show on June 7th, where the top projects will be showcased. Logistics and Additional Benefits Logistics and Additional Benefits Finalists will travel to Las Vegas, with Upland covering hotel expenses and providing travel stipends of up to $500 for domestic and $1,000 for international flights. This arrangement not only alleviates financial burdens but also enhances the overall experience, allowing participants to focus fully on their presentations. The Genesis 2024 Hackathon is a launchpad for tomorrow's innovators in the Web3 space. With significant prizes, strategic opportunities, and the chance to influence the burgeoning blockchain gaming market, this event is a cornerstone for technological advancement. Don’t miss out—mark your calendar, prepare your submission, and take part in shaping the future of the digital world. Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

Unlock $15,000 for Your Web3 Project: Compete in Upland's 2024 Genesis Hackathon

আপনার ওয়েব3 প্রকল্পের জন্য $15,000 আনলক করুন: আপল্যান্ডের 2024 জেনেসিস হ্যাকাথনে প্রতিযোগিতা করুন

Sichern Sie sich 15.000 $ für Ihr Web3-Projekt: Nehmen Sie am Genesis Hackathon 2024 von Upland teil.

Desbloquee $ 15,000 para su proyecto Web3: compita en el Hackathon Genesis 2024 de Upland

Débloquez 15 000 $ pour votre projet Web3 : participez au hackathon Genesis 2024 d'Upland

अपने वेब3 प्रोजेक्ट के लिए $15,000 अनलॉक करें: अपलैंड के 2024 जेनेसिस हैकाथॉन में प्रतिस्पर्धा करें

Web3 プロジェクトで 15,000 ドルを獲得: Upland の 2024 Genesis Hackathon に参加しましょう

Web3 프로젝트를 위해 $15,000 잠금 해제: Upland의 2024 Genesis Hackathon에서 경쟁하세요

Desbloqueie US$ 15.000 para seu projeto Web3: compita no Genesis Hackathon 2024 da Upland

Разблокируйте 15 000 долларов для своего проекта Web3: примите участие в хакатоне Genesis 2024 Upland

Web3 Projeniz için 15.000 Doların Kilidini Açın: Upland'in 2024 Genesis Hackathon'unda yarışın

Mở khóa 15.000 đô la cho Dự án Web3 của bạn: Cạnh tranh trong Genesis Hackathon 2024 của Upland

为您的 Web3 项目解锁 15,000 美元：参加 Upland 的 2024 年 Genesis Hackathon

TLDR: Effective code comments serve to elucidate the reasoning behind code design choices, rather than merely describing its functionality while avoiding redundancy and confusion. They should be concise yet informative, providing clarity for non-obvious code segments and explanations for unconventional approaches. Following established rules such as avoiding code duplication and ensuring comments do not obscure unclear code is essential. This text is a resume of the Clean Code Chapter 4 - Comments, with some insights from me and other articles. The Uncle Bob book helps you question your comments to understand if the comment is good or bad, and here you can find these questions more easily. After some time reflecting on the comments, these questions become obvious practices that we internalize, becoming something natural. This kind of knowledge and evolution marks a significant milestone in a developer's growth, demonstrating more maturity and mastery over what they're doing. Uncle Bob has a more purist view and describes comments as failures most of the time because they represent a failure on the part of the developer to create code that doesn't need explanation. I don't believe comments are failures, but rather a tool that, when misused, can hinder more than help. As we'll see, some comments are extremely useful. However, to better understand what constitutes good comments, let's first look at what to avoid when we're creating comments. Bad Explaining the Code Itself When you need to create a comment to explain what the code is doing, your comment is useless because anyone reading your code can already understand what it does. If your code is bad, and you need to explain, you should check the names of variables, functions, and the organization of the code itself. When the code uses variables and functions with explanatory names, following an organized structure, it is easy to understand what is being done. TODO Comments as "notes" of what needs to be done are comments that can be useful but should be avoided. You need to verify if this type of note is something that needs to be explicitly stated in the code if it is something that anyone will understand the need, and if you should not do this or if you cannot do it in this delivery One way to avoid the existence of TODO is to create an ESLint Rule. Mumbling Worse than an unnecessary comment is a comment that only makes sense to the author. You can understand what is commented on, but it makes no sense to anyone other than the author. The comment needs to be easily understandable for other people. Misleading When you make a comment that contradicts your code, for example, when a function should return a boolean false, but in your comment, you say that the function returns a boolean true, or that the variables used are different from the ones that are truly used. This usually occurs when you try to explain the code that shouldn't need an explanation of what it does. Mandated and Noise When your comment has no value but is made out of a "need" to organize something that should not be described through the code. These are comments that only create noise and their existence makes no difference. Comments that can be ignored; their existence can only cause some misunderstanding or error because to understand what the code does its existence is not necessary. Journal, Atrributions and Bylines The Developer should not describe how they reached the final product of their code, informing the journey they followed to reach that code is irrelevant to the code. Another problem is the comment made to inform who made this addition, something that is extremely unnecessary since we have version control tools that make it clear who modified where the code. Position Markers Some developers like to divide a file with one line per comment, just to separate what is being done. This goes against the organization and clarity of the code, bringing only more pollution. If new features need to be created in the code, this comment will confuse instead of guiding other developers on the organization of the code. Too Much Information If there is too much information that should be described in the created code, this should be in the PR, not in the code. Including too much information, with all certainty, will add irrelevant information, the comment should be made with the necessary information, nothing more. Good This is a bit about comments that should be avoided, but now, we enter those that should be questioned to see if the comment is necessary. Informative Comments that provide necessary information that cannot be demonstrated through the code itself, such as the type of time formatting that is used. Although the code explains what it does, the comment that shows time formatting is useful. Clarification When the code, even if well done, is still a bit obscure, or returns something that is too large or easily confused, it is also useful to create a comment that clarifies what the code does. Warning of Consequences It is also useful a comment that warns other developers of the consequences of that code, the problems it can generate, or that the change in it can generate changes in other parts of the code that are not evident in the code itself. Amplifications When you need to amplify the importance of something that is done by the code since the code itself cannot explain what is most important in it. Using these tips to write code comments creates more readable and maintainable code. Helpful comments in your code enable other developers to more quickly understand the design of your codebase.

Comments: The Good, the Bad and the Ugly

United States v. Apple INC Court Filing, retrieved on March 21, 2024 is part of . You can jump to any part in this filing . This part is 25 of 25. HackerNoon’s Legal PDF Series here X. Request for Relief 232. To remedy these illegal acts, Plaintiffs request that the Court: Adjudge and decree that Apple has acted unlawfully to monopolize, or, in the alternative, attempt to monopolize, the smartphone market in the United States in violation of Section 2 of the Sherman Act, 15 U.S.C. § 2; Adjudge and decree that Apple has acted unlawfully to monopolize, or, in the alternative, attempt to monopolize, the performance smartphone market in the United States in violation of Section 2 of the Sherman Act, 15 U.S.C. § 2, the New Jersey Antitrust Act, N.J.S.A. 56:9-1 to -19, Wisconsin’s Antitrust Act, Wis. Stat. Ch. § 133.03 et seq.; Enter relief as needed to cure any anticompetitive harm; Enjoin Apple from continuing to engage in the anticompetitive practices described herein and from engaging in any other practices with same purpose or effect as the challenged practices, including but not limited to: a. preventing Apple from using its control of app distribution to undermine cross-platform technologies such as super apps and cloud streaming apps, among others; b. preventing Apple from using private APIs to undermine cross platform technologies like messaging, smartwatches, and digital wallets, among others; and c. preventing Apple from using the terms and conditions of its contracts with developers, accessory makers, consumers, or others to obtain, maintain, extend, or entrench a monopoly. 5. Enter any other preliminary or permanent relief necessary and appropriate to restore competitive conditions in the markets affected by Apple’s unlawful conduct; 6. Enter any additional relief the Court finds just and proper; and 7. Award each Plaintiff, as applicable, an amount equal to its costs, including reasonable attorneys’ fees, incurred in bringing this action. Dated: March 21, 2024 Respectfully, FOR PLAINTIFF UNITED STATES OF AMERICA: FOR PLAINTIFF STATE OF NEW JERSEY: FOR PLAINTIFF STATE OF ARIZONA: FOR PLAINTIFF STATE OF CALIFORNIA: FOR PLAINTIFF STATE THE DISTRICT OF COLUMBIA: FOR PLAINTIFF STATE THE DISTRICT OF CONNECTICUT: FOR PLAINTIFF STATE OF MAINE: FOR PLAINTIFF PEOPLE OF THE STATE OF MICHIGAN: FOR PLAINTIFF OF STATE OF MINNESOTA: FOR PLAINTIFF STATE OF NEW HAMPSHIRE: FOR PLAINTIFF STATE OF NEW YORK: FOR PLAINTIFF STATE OF NORTH DAKOTA: FOR PLAINTIFF STATE OF OKLAHOMA: FOR PLAINTIFF STATE OF OREGON: FOR PLAINTIFF STATE OF TENNESSEE: FOR PLAINTIFF STATE OF WISCONSIN: FOR PLAINTIFF STATE OF VERMONT: About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings. This court case retrieved on March 21, 2024, 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. justice.gov

Plaintiffs Call for Remedies Against Apple's Unlawful Monopolization in Smartphone Market

How to analyze comment sentiment and react automatically using AI Today, we're digging into a crucial topic for anyone who’s creating content for YouTube: How to analyze and respond to video comments quickly, using the sentiment in those comments. This tutorial is also handy for anyone who's running a YouTube channel and wants to grow engagement. Who cares about comments? We all know that the comments section on YouTube is where real magic happens. That’s where you have a chance to engage with your audience, hear their honest opinions, and build loyalty over time. Yes, nice comments are awesome. But the not-so-nice comments are important, too. they’re the ones you need to respond to the fastest. And An ideal system would work something like the one below. If you’re serious about growing your channel, you’ll want a deeper understanding of your audience. Analyzing comment sentiment gives a good gauge of the overall mood of your viewers—which helps you tailor your content. Truly, this could be a game-changer. Let's jump right in. Part 1: The tools for the job For this project, we’re using a platform called MindsDB—the platform for building custom AI. It basically connects real-time data—like tons of YouTube comments— to . It lets companies prototype and deploy AI-powered enterprise solutions quickly and at scale. AI models In this case, it acts as an orchestration layer where we bring everything together, using AI to analyze the sentiment in the comments. Today, we’ll be using models from OpenAI, which makes ChatGPT. Then we’ll set up some MindsDB automation and alerts—those will come from Slack—to help with instant responses. Here's what the workflow will look like in the end. Part 2: How to get everything set up Step 1. Connect YouTube to MindsDB To connect your YouTube account to MindsDB and be able to set up a chatbot, you need to first generate OAuth2 credentials in the Google Cloud Console and use it to connect YouTube to MindsDB. Find detailed instructions in our documentation . here Let’s name the connection mindsdb_youtube_oauth, which is referred to in the following tutorial. CREATE DATABASE mindsdb_youtube_oauth
WITH ENGINE = 'youtube',
PARAMETERS = {
    "credentials_file": "/path-to-creds-file/credentials.json"
    -- alternatively, use the credentials_url parameter
}; Once you connect YouTube to MindsDB successfully using the above statement, the mindsdb_youtube_oauth connection comes with the following tables: The comments table stores all data related to the comments left by the viewers, including when the comment was added, who added the comment, and the comment’s content. The videos table stores all data related to the videos, including title, description, and transcript. Next, we'll use OpenAI models to analyze the sentiment of the comments and generate replies. Step 2. Use an OpenAI model to analyze the sentiment of YouTube comments Before you can deploy OpenAI models in MindsDB, you should create an engine, providing an OpenAI API key as below. CREATE ML_ENGINE openai_engine
FROM openai
USING
    api_key = 'sk-xxx'; Now you can plug in any of OpenAI’s models into MindsDB using the CREATE MODEL statement and this engine. Let’s create a model that analyzes the sentiment of the comments. CREATE MODEL yt_sentiment_classifier
PREDICT sentiment
USING
    engine = 'openai_engine',
    model_name = 'gpt-4',
    prompt_template = 'describe the sentiment of the comments
                        strictly as "positive", "spam", or "negative".
                        "I love this video":positive
                        "It is not a helpful content":negative
                        "{{comment}}.":'; This model takes the {{comment}} value (from the comments table provided by the mindsdb_youtube_oauth connection created in Step 1) as input and gives the sentiment value as output. Join the comments table (from mindsdb_youtube_oauth) with the model to analyze the sentiment of the comments. Provide the channel_id value in the WHERE clause. SELECT c.comment, m.sentiment
FROM mindsdb_youtube_oauth.comments AS c
JOIN yt_sentiment_classifier AS m
WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"; Here is sample output: comment sentiment This video explains the subject so well. positive Subscribe to this channel asap. spam It didn’t help me understand the subject. negative Step 3. Use an OpenAI model to generate replies to YouTube comments Create a model to generate replies to comments. Here the model will utilize the comment content (from the comments table) and transcript of the video (from the videos table) to come up with a reply. CREATE MODEL yt_reply_model
PREDICT reply
USING
    engine = 'openai_engine',
    model_name = 'gpt-4',
    prompt_template = 'briefly respond to the youtube comment "{{comment}}";
                       as a context, use the video transcript "{{transcript}}"'; This model takes the {{comment}} value (from the comments table) and the {{transcript}} value (from the videos table) as input and gives the reply value as output. Join the comments and videos tables on their common column being the video_id column. Then, join it with the sentiment classifier model and the reply generator model. This is how you can accomplish the chaining of models in MindsDB. (Before executing the below command, add at least one new comment to the channel, so that it can fulfill the LAST keyword condition.) SELECT c.comment AS comment,
       m1.sentiment AS sentiment,
       m2.reply AS reply
FROM mindsdb_youtube_oauth.comments c
LEFT JOIN mindsdb_youtube_oauth.videos v
ON c.video_id = v.video_id
JOIN yt_sentiment_classifier AS m1
JOIN yt_reply_model AS m2
WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
AND c.published_at > LAST; Please note that for long videos the transcript will be long and that may result in the OpenAI token limit being exceeded. Alternatively, to pass long transcript values in the prompt to the model, you can use the feature of MindsDB. RAG Here is a sample output: comment sentiment reply This video explains the subject so well. positive Thank you for your comment. We’re glad you enjoyed the video. It didn’t help me understand the subject. negative Thank you for your comment. Please let us know your feedback on what could be improved. The above query joins the comments and videos tables on their common column, which is the video_id column. The reason for joining these tables is to provide input to both the models—the sentiment classifier model requires the comment column from the comments table, and the reply generator model requires the transcript column from the videos table. Next, the two models are joined using the custom JOIN statement that does not require any ON clause condition because each model is provided with the required input from the data tables. You can select the predictions made by the models as shown in the SELECT clause. Finally, we define the channel_id value in the WHERE clause. The condition that uses the LAST keyword on the published_at column enables you to fetch only the recently added comments. Now that the sentiment of comments is analyzed and replies are generated, let’s add some automation. Step 4. Post replies to positive comments This is the first component of the job that we’ll create in Step 7. Here is how you can insert replies to recent comments whose sentiment has been classified as positive: (Before executing the below command, add at least one new (positive) comment to the channel, so that it can fulfill the LAST keyword condition.) INSERT INTO mindsdb_youtube_oauth.comments (comment_id, reply)
  SELECT c.comment_id AS comment_id,
         m2.reply AS reply
  FROM mindsdb_youtube_oauth.comments c
  LEFT JOIN mindsdb_youtube_oauth.videos v
  ON c.video_id = v.video_id
  JOIN yt_sentiment_classifier AS m1
  JOIN yt_reply_model AS m2
  WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
  AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
  AND c.published_at > LAST
  AND m1.sentiment = 'positive'; The LAST keyword ensures that only the newly added comments are returned by the query. Step 5. Notify about spam comments This is the second component of the job that we’ll create in Step 7. Let’s automate notifications to Slack about spam comments. A notification will include all details about the comment, its sentiment (predicted by the model in Step 2), and a sample reply (generated by the model in Step 3). Set up your Slack channel and connect it to MindsDB following . this instruction CREATE DATABASE yt_slack
WITH
  ENGINE = 'slack',
  PARAMETERS = {
      "token": "xoxb-xxx"
    }; Test the connection by inserting a message into the Slack channel. INSERT INTO yt_slack.channels (channel, text)
VALUES("channel-name", "Test message."); Here is how you can send notifications to Slack about recent comments whose sentiment has been classified as spam: (Before executing the below command, add at least one new (spam) comment to the channel, so that it can fulfill the LAST keyword condition.) INSERT INTO yt_slack.channels (channel, text)
    SELECT "channel-name" AS channel,
           concat('Video: https://www.youtube.com/watch?v=', c.video_id, chr(10),
                  'Spam Comment: https://www.youtube.com/watch?v=', c.video_id, 
                        '&lc=', c.comment_id, chr(10),
                  'Author: ', c.display_name, chr(10),
                  'Comment: ', c.comment) AS text
    FROM mindsdb_youtube_oauth.comments c
    LEFT JOIN mindsdb_youtube_oauth.videos v
    ON c.video_id = v.video_id
    JOIN yt_sentiment_classifier AS m
    WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND c.published_at > LAST
    AND m.sentiment = 'spam'; The LAST keyword ensures that only the newly added comments are returned by the query. Step 6. Notify about negative comments This is the third component of the job that we’ll create in Step 7. Now, what about comments with negative sentiment? As these require analysis and thoughtful answers, let’s automate notifications to Slack about negative comments. A notification will include all details about the comment, its sentiment (predicted by the model in Step 2), and a sample reply (generated by the model in Step 3). Set up your Slack channel and connect it to MindsDB following . this instruction CREATE DATABASE yt_slack
WITH
  ENGINE = 'slack',
  PARAMETERS = {
      "token": "xoxb-xxx"
    }; Test the connection by inserting a message into the Slack channel. INSERT INTO yt_slack.channels (channel, text)

VALUES("channel-name", "Test message."); Here is how you can send notifications to Slack about recent comments whose sentiment has been classified as negative: (Before executing the below command, add at least one new (negative) comment to the channel, so that it can fulfill the LAST keyword condition.) INSERT INTO yt_slack.channels (channel, text)
    SELECT "channel-name" AS channel,
           concat('Video: https://www.youtube.com/watch?v=', c.video_id, chr(10),
                  'Negative Comment: https://www.youtube.com/watch?v=', c.video_id, 
                        '&lc=', c.comment_id, chr(10),
                  'Author: ', c.display_name, chr(10),
                  'Comment: ', c.comment, chr(10),
                  'Sample reply: ', m2.reply) AS text
    FROM mindsdb_youtube_oauth.comments c
    LEFT JOIN mindsdb_youtube_oauth.videos v
    ON c.video_id = v.video_id
    JOIN yt_sentiment_classifier AS m
    JOIN yt_reply_model AS m2
    WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND c.published_at > LAST
    AND m.sentiment = 'negative'; The LAST keyword ensures that only the newly added comments are returned by the query. Step 7. Automate replies to positive comments and notifications about negative and spam comments Let’s create a job that will reply to recent positive comments, send notifications about recent negative comments with draft responses, and send notifications about recent spam comments. To do that, we need to connect a database to MindsDB in order to save the recent comments into a table. (The reason for doing so is that every run of a query that includes the condition with the LAST keyword returns only the newly added comments, which haven’t been returned in the previous run of such a query. To be able to do different actions for positive and negative comments, we need to save the output of the query with LAST. To save a batch of recently added comments returned by the query with LAST, we need a database table. Learn more about the .) LAST keyword here You can connect a database to MindsDB using the CREATE DATABASE statement and providing specific parameters. Choose one of the on how to connect it to MindsDB. supported databases and follow the instructions Here, we connect a PostgreSQL database as below: CREATE DATABASE psql_datasource
WITH ENGINE = 'postgres',
PARAMETERS = {
    "host": "host-name-or-ip-address",
    "port": 5432,
    "database": "database_name",
    "schema": "schema_name",
    "user": "postgres",
    "password": "password"
}; To create a table and insert into it the output of the query with LAST, use this command: CREATE OR REPLACE TABLE psql_datasource.recent_comments (
      SELECT *
      FROM mindsdb_youtube_oauth.comments c
      LEFT JOIN mindsdb_youtube_oauth.videos v
      ON c.video_id = v.video_id
      WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
      AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
      AND c.published_at > LAST
); Now, it’s time to create a job that automates steps 4, 5, and 6. CREATE JOB youtube_chatbot (

  -- save the recently added comments into a table

  CREATE OR REPLACE TABLE psql_datasource.recent_comments (
    SELECT *
    FROM mindsdb_youtube_oauth.comments c
    LEFT JOIN mindsdb_youtube_oauth.videos v
    ON c.video_id = v.video_id
    WHERE c.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND v.channel_id="UC5_wBOLCWath6q1iTgPPD5A"
    AND c.published_at > LAST
  );

  -- automate replies for positive comments (from Step 4)

  INSERT INTO mindsdb_youtube_oauth.comments (comment_id, reply)
    SELECT c.comment_id AS comment_id,
           m2.reply AS reply
    FROM psql_datasource.recent_comments AS c
    JOIN yt_sentiment_classifier AS m
    JOIN yt_reply_model AS m2
    WHERE m.sentiment = 'positive';

   -- automate notifications about spam comments (from Step 5)

   INSERT INTO yt_slack.channels (channel, text)
     SELECT "channel-name" AS channel,
            concat('Video: https://www.youtube.com/watch?v=', c.video_id, chr(10),
                   'Spam Comment: https://www.youtube.com/watch?v=', c.video_id, 
                         '&lc=', c.comment_id, chr(10),
                   'Author: ', c.display_name, chr(10),
                   'Comment: ', c.comment) AS text
     FROM psql_datasource.recent_comments AS c
     JOIN yt_sentiment_classifier AS m
     WHERE m.sentiment = 'spam';

  -- automate notifications about negative comments (from Step 6)

  INSERT INTO yt_slack.channels (channel, text)
    SELECT "channel-name" AS channel,
           concat('Video: https://www.youtube.com/watch?v=', c.video_id, chr(10),
                  'Negative Comment: https://www.youtube.com/watch?v=', c.video_id, 
                        '&lc=', c.comment_id, chr(10),
                  'Author: ', c.display_name, chr(10),
                  'Comment: ', c.comment, chr(10),
                  'Sample reply: ', m2.reply) AS text
    FROM psql_datasource.recent_comments AS c
    JOIN yt_sentiment_classifier AS m
    JOIN yt_reply_model AS m2
    WHERE m.sentiment = 'negative';
)
EVERY 10 minutes; This job (re)creates the recent_comments table and stores only the recently added comments in it. This table is joined with the models to reply to only positive comments. Next, this table is joined with the sentiment classifier model to send notifications about spam comments. And finally, this table is again joined with both models to send notifications about negative comments with draft responses. Please note that for large workloads of comments data, it may be required to increase the . YouTube quota What a custom YouTube chatbot means With the above steps, you can connect YouTube to MindsDB to access your channel’s comments, analyze them with the help of AI, and automate replies to the recently added comments (or send notifications about the recently added comments). In this tutorial, we've shown how to set up a chatbot for a YouTube channel defined in the WHERE clause while querying the comments and videos table. You can customize this chatbot to your use case, utilizing other integrations and features provided by MindsDB. Why analyzing sentiment is so important Analyzing to determine whether it’s positive or negative is gold when it comes to understanding your audience's emotions. language in comments Believe it or not—negative comments, while not fun, are not the enemy. They're an opportunity. They give you valuable feedback that helps you grow as a creator or as a brand. Some of the most dedicated viewers start as critics. When you respond quickly and gracefully to their nastiest comments (which shows that you value their feedback), you really can turn critics into loyal fans. Remember, it's not about proving anyone wrong; it's about responding fast (in real-time, which is possible with MindsDB) and building a connection. Also published . here

AI-Driven YouTube Comment Management: The Good, Bad, and Ugly

USA v. Samuel Bankman-Fried Court Filing, retrieved on March 15, 2024 is part of . You can jump to any part in this filing . This part is 6 of 33. HackerNoon’s Legal PDF Series here II. The Defendant’s Scheme to Make Unlawful Political Contributions In addition to the offenses of conviction, Bankman-Fried was charged with conspiring to violate the Federal Election Campaign Act and defraud the Federal Election Commission. While Bankman-Fried consented to extradition on that count, the government of The Bahamas informed the United States after the extradition that Bankman-Fried had not been extradited on the campaign finance count. (Dkt. 181). For that reason alone, the Government was unable to proceed to trial on what was Count Eight of the original Indictment. Nonetheless, the Court ruled that the Government could present evidence of the campaign finance scheme as direct evidence of the other charged crimes, including to show motive and the relationship between co-conspirators. (Dkt. 289 at 3). At trial, the Government proved Bankman-Fried’s involvement in a conspiracy to make over $100 million in political donations to federal and state officials from both parties, as well as political action committees, all funded with funds from Alameda (and ultimately customers). As the trial evidence established, the defendant passed these donations through accounts belonging to Ryan Salame and Singh (both of whom pled guilty to conspiracy to violate the campaign finance laws). (GX-1088, 1089, 1090). All of the contributions that were funded by Alameda or the defendant, but reported in the names of Salame or Singh, violated the campaign finance laws. Likewise, all of the contributions that were funded by Alameda, a corporation, and made to individual candidates violated the prohibition on corporate contributions to candidates. The defendant’s scheme spanned several years and was plainly designed to permit the defendant to amass power and influence. Beginning in or around 2020, Bankman-Fried began donating large sums of funds to political candidates, at least in part to improve his personal standing in Washington, D.C., increase FTX’s profile, and curry favor with candidates that could help pass legislation favorable to FTX or Bankman-Fried’s personal agenda, including legislation concerning regulatory oversight over FTX and its industry. To accomplish these goals, BankmanFried caused substantial contributions to be made in support of candidates of both major political parties and across the political spectrum. Bankman-Fried, however, did not want to be known as a left-leaning partisan, or to have his name publicly attached to Republican candidates. (GX-477). In order to obscure his association with certain contributions, Bankman-Fried conspired with others including Salame and Singh, to make some of the contributions in the names of Salame and Singh, instead of in the names Bankman-Fried or Alameda. (Tr. 1420-23; 1427-36). As Salame explained in a private message to a confidant, the purpose of these bipartisan donations would be “to weed out anti crypto dems for pro crypto dems and anti crypto repubs for pro crypto repubs,” and that donations would likely be routed through Salame “to weed out that republican side.” (GX505). Between in or about the fall of 2021 and the November 2022 election, Salame, BankmanFried, and Singh collectively made tens of millions of dollars in contributions, including in “hard money” contributions to federal candidates from both major political parties. (GX-28). The money used to make these political donations or to compensate for donations made by credit card originated from Alameda or FTX bank accounts and included funds that had been deposited by FTX customers. (GX-1088, 1089, 1090). Notwithstanding his awareness of the campaign finance laws, in order to conceal the true source of the funds, Bankman-Fried agreed with others that funds for contributions would be transferred from Alameda’s bank accounts to bank accounts in the name of the political donors, and then quickly transferred from those individuals’ bank accounts to political campaigns. To further conceal the scheme, Bankman-Fried and his co-conspirators recorded the outgoing wire transfers from Alameda to individuals’ bank accounts for purposes of making contributions as Alameda “loans” or “expenses.” (GX-480A; Tr. 1458-61). But unlike other loans that were made to FTX executives, most of these outgoing wire payments were not documented in agreements or on term sheets, and there were no set interest rates, no interest payments, no collateral, and no evidence of repayment. In total, Bankman-Fried and his co-conspirators made over 300 political contributions, totaling tens of millions of dollars, that were unlawful because they were made in the name of a straw donor or paid for with corporate funds. The proposed preliminary order of forfeiture lists the contributions identified by the Government. In dozens of instances, use of straw donors allowed Bankman-Fried to evade contribution limits on individual donations to candidates to whom Bankman-Fried had already donated. As a result of this fraudulent conduct, Bankman-Fried and his co-conspirators caused false information to be reported by campaigns and PACs to the FEC, which had the result of impairing and impeding the FEC’s reporting and enforcement functions. The defendant argues that the Court should not consider the defendant’s unlawful political contributions for two reasons. (Def. Mem. at 27). First, he argues that the Government did not prove this conduct by a preponderance of the evidence at trial. But at trial Singh testified that funds were transferred from Alameda to his bank account and then Salame, as part of the conspiracy with the defendant, would transfer those funds to political campaigns as if those were donations from Singh. (Tr. 1420-38). The Government also introduced documentary evidence at trial of this scheme. Government Exhibit 475, the “Donation Processing” Signal chat, provides evidence that Bankman-Fried coordinated sending Alameda funds through the accounts of Singh, Salame, and Bankman-Fried. Government Exhibit 477, a Signal chat between Singh and another person working for the defendant, also shows that certain donations would be made in Singh’s name instead of the defendant’s name. Government Exhibit 28 is a spreadsheet that was maintained by the defendant to track contributions being made in his name, Singh’s name, and Salame’s name. The Government also traced funds from Alameda through bank accounts in the names of Singh, Salame, and Bankman-Fried, on to the accounts of political campaigns. Those tracing charts were admitted into evidence as Government Exhibits 1088, 1089, and 1090. Based on all of that evidence, there is sufficient proof for the Court to conclude by a preponderance of the evidence that the defendant committed violations of the campaign finance laws. To the extent the defendant’s willfulness is at issue, it was established by the inherent aspects of concealment involved in the crime, and the fact that, as several witnesses discussed, the defendant was sophisticated when it came to politics. Additionally, while it is not necessary here, the Court is not constrained by the trial record and may consider additional evidence in connection with sentencing, or hold a hearing, at which the Government would establish that the defendant acted willfully. Second, the defendant complains that he was not permitted to call Bradley Smith as an expert witness at trial. But the testimony for which he was noticed is irrelevant for this proceeding. The defendant says that “Professor Smith would have offered expert testimony concerning ‘[c]ommon, established, and well-known practices for large-scale political giving campaigns,’ as well as testimony ‘to rebut evidence which may be offered by the Government concerning issues of campaign finance and political donations.’” (Def. Mem. at 28 (quoting Def.’s Expert Notice)). But such general testimony would not undermine the clear evidence that money was being laundered through straw donors’ accounts to make illegal contributions. And under the Rules of Evidence, Professor Smith would not be permitted to testify about the defendant’s mental state, Fed. R. Evid. 704(b), so it is not clear how his noticed testimony would have been probative of any of the sentencing issues. If it were, the defendant would have presumably offered some of Professor Smith’s opinions as part of his sentencing submission. 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 retrieved on March 15, 2024, 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. storage.courtlistener

Stories, News & Mentions about UGLA

Ugla’s Stories on HackerNoon

Ugla's News & Mentions