Home Blog Page 3

Tim Cook dinner selected poorly | Cell Dev Memo by Eric Seufert


Yesterday, Decide Yvonne Gonzalez Rogers, who has presided over the Epic Video games v. Apple case because it was introduced by Epic in 2020, dominated that Apple violated an injunction issued in 2021 that compelled Apple to permit builders to hyperlink to exterior account administration techniques, together with for funds. From the WSJ (emphasis mine):

A federal choose hammered Apple for violating an antitrust ruling associated to App Retailer restrictions and took the extraordinary step of referring the matter to federal prosecutors for a legal contempt investigation … The order is the newest twist in a long-running authorized dispute between Apple and Epic Video games, developer of the favored videogame “Fortnite.” It accused Apple of monopolistic habits in a 2021 case associated to the tight controls it imposes over app makers … Rogers largely dominated in Apple’s favor within the 2021 case however required the iPhone maker to permit builders to supply customers different strategies for paying for companies and subscriptions exterior the App RetailerApple mentioned it might adjust to the order. The corporate disagrees with the court docket’s choice and can enchantment, a spokeswoman mentioned.

Apple had appealed the unique ruling, which was upheld roughly two years in the past, in April 2023. In my protection on the time, in a chunk titled The Epic v. Apple enchantment choice will change little or no, I argued that forcing Apple to permit link-out and different types of different funds would have little affect on the app economic system as long as Apple continued to pressure builders to pay fee charges on these transactions. From that piece:

And Apple and Google have each dug their heels in on amassing a platform payment on different funds. Apple launched entitlements associated to each in-app and out-of-app different funds as a way to acquire a 27% payment on IAPs in courting apps within the Netherlands, the place the home competitors authority dominated that different funds (completely in courting apps) have to be supported. And Google and Apple each extract a 26% payment on different funds processed in South Korea, the place a regulation was handed in 2021 to claim the identical. And Google introduced final week that it’ll permit different funds in Google Play within the UK following an investigation by the UK’s competitors authority, however that it’ll extract a 27% payment on these funds … If these charges are extracted on different funds, given the conversion friction inherent in monetizing customers exterior of native fee mechanisms, the economics of “by-the-book” different IAPs for cell sport builders will merely break.

I’ve chronicled Apple’s makes an attempt to keep up its fee on out-of-store transactions in my Apple to builders: Heads I win, tails you lose collection (see elements one, two, three, and 4). My argument all alongside has been that, if Apple is allowed to use its vital fee on transactions that happen out of the App Retailer, the economics of fee options are merely unworkable. This ruling modifications that, nevertheless: in a withering 80-page choice, Decide Rogers determines that Apple not solely violated the injunction but additionally that an Apple government lied beneath oath through the trial. And with this choice, with which the corporate should comply instantly, Apple’s ironclad grip on out-of-store funds has been damaged. Whereas different developments on this case have largely been insignificant, this one isn’t: it’s really a watershed second for the app economic system (noting that Apple plans to enchantment).

From the choice (emphasis mine):

Apple’s response to the Injunction strains credulity. After two units of evidentiary hearings, the reality emerged. Apple, regardless of realizing its obligations thereunder, thwarted the Injunction’s targets, and continued its anticompetitive conduct solely to keep up its income stream. Remarkably, Apple believed that this Court docket wouldn’t see by its apparent cover-up (the 2024 evidentiary listening to) … In stark distinction to Apple’s preliminary in-court testimony, contemporaneous enterprise paperwork reveal that Apple knew precisely what it was doing and at each flip selected probably the most anticompetitive choice. To cover the reality, Vice-President of Finance, Alex Roman, outright lied beneath oath. Internally, Phillip Schiller had advocated that Apple adjust to the Injunction, however Tim Cook dinner ignored Schiller and as an alternative allowed Chief Monetary Officer Luca Maestri and his finance crew to persuade him in any other case. Cook dinner selected poorly … That is an injunction, not a negotiation. There are not any do-overs as soon as a celebration willfully disregards a court docket order. Time is of the essence. The Court docket won’t tolerate additional delays. As beforehand ordered, Apple won’t impede competitors. The Court docket enjoins Apple from implementing its new anticompetitive acts to keep away from compliance with the Injunction. Efficient instantly Apple will not impede builders’ means to speak with customers nor will they levy or impose a brand new fee on off-app purchases.

And time really is of the essence: in the present day, Stripe launched an extension of its off-platform app funds choice that enables for native, in-app checkout on iOS (see this video to know how seamless the method is). Clearly, Stripe anticipated this final result as an eventuality. And I’m sure that each app developer is presently investigating how they’ll launch off-platform funds.

I’ve persistently maintained that Apple has the appropriate to cost no matter payment it chooses for App Retailer funds — see Three arguments in opposition to Apple anti-trust accusations for my arguments. I don’t begrudge Apple’s declare on App Retailer commissions, given the central function it performs in facilitating them. However Apple’s efforts to impede off-platform funds have been past the pale, as I’ve detailed over the previous few years within the Heads I win, Tails you lose collection. This improvement is simply and overdue.



JetBrains open sources its code completion LLM, Mellum


JetBrains has introduced that its code completion LLM, Mellum, is now out there on Hugging Face as an open supply mannequin.

In line with the corporate, Mellum is a “focal mannequin,” that means that it was constructed purposely for a selected process, moderately than attempting to be good at the whole lot. “It’s designed to do one factor rather well: code completion,” Anton Semenkin, senior product supervisor at JetBrains, and Michelle Frost, AI advocate at JetBrains, wrote in a weblog publish

Focal fashions are usually cheaper to run than basic bigger fashions, which makes them extra accessible to groups that don’t have the sources to be operating massive fashions. 

“Consider it like T-shaped abilities – an idea the place an individual has a broad understanding throughout many subjects (the horizontal high bar or their breadth of data), however deep experience in a single particular space (the vertical stem or depth). Focal fashions comply with this similar concept: they aren’t constructed to deal with the whole lot. As a substitute, they specialize and excel at a single process the place depth actually delivers worth,” the authors wrote. 

Mellum at the moment helps code completion for a number of well-liked languages: Java, Kotlin, Python, Go, PHP, C, C++, C#, JavaScript, TypeScript, CSS, HTML, Rust, Ruby.

There are plans to develop Mellum right into a household of various focal fashions supreme for different particular coding duties, reminiscent of diff prediction. 

The present model of Mellum is most supreme for both AI/ML researchers exploring AI’s position in software program improvement, or AI/ML engineers or educators as a basis for studying the right way to construct, fine-tune, and adapt domain-specific language fashions. 

“Mellum isn’t a plug-and-play answer. By releasing it on Hugging Face, we’re providing researchers, educators, and superior groups the chance to discover how a purpose-built mannequin works underneath the hood,” the authors wrote. 

5 the explanation why you need to be part of Robotiq at Automate 2025 in Detroit


Let’s be trustworthy, automation can really feel overwhelming. With all the thrill about AI, cobots, and Business 4.0, it’s arduous to know what truly works on the manufacturing facility ground. That’s why Automate 2025 in Detroit isn’t simply one other commerce present. It’s your alternative to get hands-on with actual options that remedy actual manufacturing issues.

And nobody brings that practicality and affect higher than Robotiq.

reactjs – React Native iOS Construct Failed: fmt/src/format.cc compilation error after downloading Pod file


I’m engaged on a React Native mission, and after efficiently downloading the Pod file, I’m going through a construct failure when working the app on iOS. Right here’s what occurs:

  1. I run the next command to start out the app:

  2. rm -rf ios/Pods
    rm -rf ios/DerivedData
    rm -rf ~/Library/Developer/Xcode/DerivedData
    cd ios && pod set up --repo-update && cd ..se64
    
  3. "ios:dev": "npx react-native run-ios --scheme 'VeeraHealthPcosDev' --configuration Debug --simulator="iPhone 13"" 
    
  4. The construct fails, and I get this error message:

    ** BUILD FAILED **
    
    
    The next construct instructions failed:
            CompileC /Customers/rac/Library/Developer/Xcode/DerivedData/veerahealthpcos-fjsocvigquxpakdaumsxcfhhcmhw/Construct/Intermediates.noindex/Pods.construct/Debug-iphonesimulator/fmt.construct/Objects-normal/x86_64/format.o /Customers/rac/Desktop/working/rn-veera-health-pcos/ios/Pods/fmt/src/format.cc regular x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in goal 'fmt' from mission 'Pods')
            Constructing workspace veerahealthpcos with scheme VeeraHealthPcosDev and configuration Debug
    (2 failures)
    
    data Run CLI with --verbose flag for extra particulars.
    

Atmosphere:

I can’t replace to the most recent model of React Native, as my mission is dependent upon older package deal variations that aren’t appropriate with the most recent React Native model. I’ve tried cleansing the construct folder, reinstalling the dependencies, and even updating the Pods, however the difficulty persists.

I believe the issue could also be associated to the file ios/Pods/fmt/src/format.cc, however I’m unsure the way to resolve it. Has anybody else encountered this difficulty or have any strategies for an answer?

Contained in the post_install do |installer| block, I added the next to change the construct settings:

installer.pods_project.targets.every do |goal|
  goal.build_configurations.every do |config|
    # Enable arm64 (take away earlier exclusion of arm64):
    config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'x86_64'
    config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES'
  finish
finish

installer.pods_project.targets.every do |goal|
  if goal.title == 'fmt'
    goal.build_configurations.every do |config|
      # Pressure C++17 (required by trendy fmt) and libc++  
      config.build_settings['CLANG_CXX_LANGUAGE_STANDARD'] = 'c++17'  
      config.build_settings['CLANG_CXX_LIBRARY'] = 'libc++'  
      # Disable Clang modules (can keep away from module import points)
      config.build_settings['CLANG_ENABLE_MODULES'] = 'NO'  
      config.build_settings['CLANG_MODULES_AUTOLINK'] = 'NO'  
      # (Non-obligatory) Add any wanted defines, e.g. for compatibility
      config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
    finish
  finish
finish

installer.pods_project.targets.every do |goal|
  if goal.title == 'OneSignalNotificationServiceExtension'
    goal.build_configurations.every do |config|
      # Exclude x86_64 on simulator so we solely construct arm64
      config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'x86_64'
      # Solely construct the energetic arch in debug
      config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES'
    finish
  finish
finish

After working the app, I anticipated the construct to succeed, however as an alternative, I acquired the next error:

The next construct instructions failed:
        SwiftEmitModule regular x86_64 Emitting module for OneSignalNotificationServiceExtension (in goal 'OneSignalNotificationServiceExtension' from mission 'xyz')
        SwiftCompile regular x86_64 /Customers/rac/Desktop/working/rn-veera-health-pcos/ios/OneSignalNotificationServiceExtension/NotificationService.swift (in goal 'OneSignalNotificationServiceExtension' from mission 'xyz')
        Constructing workspace xyz with scheme VeeraHealthPcosDev and configuration Debug
(3 failures)

It seems to be a problem associated to the OneSignalNotificationServiceExtension. Any strategies on the way to resolve this or repair the construct failure could be appreciated.

Embracing a Passwordless Future: Cisco’s Journey to Seamless Authentication with Duo Passwordless


ndly means that may permit its 130,000 customers to securely work anyplace, from any gadget, with out friction. By leveraging its personal Duo Passwordless, the crew was capable of eradicate phishable multi-factor authentication elements, enhance usability and productiveness, scale back authentication actions by 93%, and safe its workforce from anyplace. 

At Cisco, securing our office for the longer term means constantly adapting to technological developments and staying forward of the menace panorama. Leveraging our personal suite of safety merchandise, together with Duo, has been key in serving to us do this.  

When most of our workforce labored remotely in the course of the pandemic, we applied Duo Past and moved from a standard network-based perimeter and VPN mannequin to a zero-trust framework in order that customers may securely work anyplace, from any gadget, with out friction. 

At this time, our zero-trust journey continues as we try to fulfill the safety wants of as we speak whereas adapting for what’s subsequent with Duo Passwordless. Id is now the perimeter— the primary line of protection in opposition to cyber threats. With most knowledge breaches coming from weak or stolen credentials, it’s clear that the longer term requires passwordless authentication. 

The issue with passwords

To place it merely, passwords are a straightforward goal for hackers. As soon as the gold commonplace for safeguarding delicate data, passwords at the moment are outdated and weak within the ever-evolving menace panorama. They’re extremely inclined to phishing assaults, may be simply forgotten, and infrequently result in person frustration that brings an inflow of password-related assist desk tickets to IT groups.  

When affected by password fatigue, customers are inclined to make use of weak, reused, or solely barely modified passwords throughout completely different accounts. Good password administration is tough and troublesome to implement, and previous to utilizing Duo Passwordless, Cisco IT struggled to handle these challenges throughout an enormous workforce spanning greater than 130,000 customers.  

As a big firm and a pacesetter in know-how, a compromise in our safety can have a significant affect on our enterprise and our innovation. If attackers acquire delicate data resembling supply code, inside system particulars, buyer knowledge, or mental property, it not solely places our enterprise and staff in danger, however the prospects who depend on our know-how. We wanted to adapt our strategy to authentication to mitigate the password associated safety dangers to our enterprise and challenges confronted by our staff and assist groups.

Conventional multi-factor authentication (MFA) is now not adequate

Authentication has advanced as cybercrime has develop into an increasing number of subtle. We began with “one thing ,” or a username and password. We added MFA, which mixes “one thing ” with “one thing you’ve” or “are” like a tool or fingerprint. Whereas stronger than a username and password alone, the “one thing ” issue of a password remained inclined to vulnerabilities.  

The transfer to passwordless: specializing in safety and person expertise

We started working carefully with the Duo product crew to take a user-friendly, zero belief strategy that not solely enhanced safety but in addition improved the person expertise. To do that, we applied Duo Passwordless. It wasn’t nearly enhancing safety, however on the identical time cultivating a seamless expertise that may higher serve our prospects and staff each now and into the longer term.

While Duo Passwordless remains to be MFA, it takes it a step additional and combines the expertise into one step, making for a smoother person expertise. It depends on cryptographic public-private key pairs, using biometrics (resembling fingerprint or facial recognition) or safety keys like YubiKeys to authenticate customers with out the necessity for passwords.

Enhancing Duo as buyer zero

As “buyer zero” for Duo Passwordless, we had the flexibility to check and enhance the know-how by way of early pilot packages earlier than launch. Utilizing a multi-phased strategy, we began with a small group of IT and safety workers, enhancing efficiency and performance by way of suggestions earlier than progressively increasing to the complete workforce over 10 months. The data gained from preliminary pilot teams and insights into how completely different customers could be impacted helped form our strategy to speaking the adjustments with our workforce. 

By means of cautious collaboration between groups throughout our group, Cisco IT Safety and the Safety and Belief Group (S&TO) started driving the path of our passwordless future. My crew inside IT Safety served as the principle drivers behind this effort, with S&TO offering change administration assist, and IT UX, IT Comms, and IT Analysis & Analytics supporting as wanted. Assist@Cisco additionally performed a task as soon as we shifted to necessary passwordless just for key apps, managing the assist course of for our inside customers so service groups may give attention to the operation and enchancment of the product.  

Challenges and classes discovered

Whereas the complete rollout has seen excessive ranges of natural workforce enrollment with restricted promotion, there have been some challenges with adoption. Many customers reported preliminary considerations with using biometrics. For instance, Home windows Good day customers who didn’t log in with biometrics by default, merely didn’t know to set it up. Except particularly instructed, customers on this state of affairs didn’t notice biometrics have been an possibility for them.  

To treatment, we targeted on worker schooling round how biometrics are used, the place they’re saved, in addition to the worth of shifting to passwordless authentication. As well as, we offered options to biometrics. For instance, on Home windows, customers can use a PIN. In the event that they don’t like platform-based authenticators, they will use a YubiKey with a PIN or setup a passkey on a cellular gadget. 

Additionally essential to notice, we didn’t initially mandate the transfer to passwordless. Our strategy to encouraging worker adoption and alter was formed by our dedication to delivering one of the best person expertise. We wished to ship providers and know-how that acted as a magnet for adoption fairly than a mandate.  

Now that we’re additional into our journey, now we have began Passwordless Solely enforcement on sure apps. The slower, however at-will transition allowed natural adoption and helped get individuals comfy with the brand new know-how prior to creating the follow necessary. 

 The affect: A safer and productive workforce

Because the passwordless answer was made obtainable to the whole workforce, we’ve seen substantial advantages together with:  

  • Zero password-related safety incidents 
  • A frictionless expertise for over 130,000 staff with zero belief safe entry 
  • Improved usability and productiveness, decreasing authentication actions by 93% 
  • Enhanced safety by eliminating phishable MFA elements 
  • Substantial discount in IT time and prices resulting from fewer password-related points

The long run: Continued innovation and growth

Whereas there’s a lengthy highway forward of a full trade shift away from passwords completely, this has primarily been about altering the expertise for our workforce as we speak and mitigating potential future threats for our enterprise. Getting ready for a totally passwordless future is a journey that we proceed to construct and enhance on, together with: 

  •  Enhancing safety and usefulness for our workforce: Our journey started with our implementation of Duo Past and continues with Duo Passwordless, underpinning our present transition to Cisco Safe Entry inside Cisco IT (extra to return!). Id safety is a basis for zero belief entry, and Duo is far more than simply MFA.  
  • Strengthening and evolving our zero-trust structure: The profitable rollouts of our Duo options mixed with the newest rollout of Cisco Safe Entry unlocks even stronger zero belief outcomes with an identify-first SSE.  

Study extra about Duo Passwordless Authentication, our journey, and the highly effective mixture of Cisco Safe Entry and Duo. For Cisco staff, learn to arrange passwordless in your Cisco gadget right here.

 

 

Extra Assets:

 

PS:  Attending Cisco Stay in San Diego this June? 

You’ll have a particular alternative to speak reside with Cisco IT consultants to dive into these success tales and different deployments! Look for Cisco on Cisco in every of the showcases and you should definitely search Cisco on Cisco within the session catalog to add our classes to your schedule!

Share: