Language Selection

English French German Italian Portuguese Spanish

Apple Threats

Filed under
Mac
  • Apple threatens leakers with criminal action in leaked memo – report

     

    The memo about leaking, which was leaked to Bloomberg and published on Friday, threatened employees with criminal consequences and shines a harsh light on the Silicon Valley company’s aggressive surveillance of its own employees and intensive investigative efforts to catch and punish leakers.  

  • In a Leaked Memo, Apple Warns Employees to Stop Leaking Information

     

    The Cupertino, California-based company said in a lengthy memo posted to its internal blog that it "caught 29 leakers," last year and noted that 12 of those were arrested. "These people not only lose their jobs, they can face extreme difficulty finding employment elsewhere," Apple added. The company declined to comment on Friday.

  • Apple's memo warning employees about leaking information is predictably leaked

    An internal memo warning Apple employees that leaking information could result in legal action and criminal charges has, rather predictably, been leaked.

  • Apple Sued an Independent iPhone Repair Shop Owner and Lost

    Last year, Apple’s lawyers sent Henrik Huseby, the owner of a small electronics repair shop in Norway, a letter demanding that he immediately stop using aftermarket iPhone screens at his repair business and that he pay the company a settlement.

    Norway’s customs officials had seized a shipment of 63 iPhone 6 and 6S replacement screens on their way to Henrik’s shop from Asia and alerted Apple; the company said they were counterfeit.

    In order to avoid being sued, Apple asked Huseby for “copies of invoices, product lists, order forms, payment information, prints from the internet and other relevant material regarding the purchase [of screens], including copies of any correspondence with the supplier … we reserve the right to request further documentation at a later date.”

More in Tux Machines

KDE is adding Matrix to its instant messaging infrastructure

KDE has been looking for a better way of chatting and live-sharing information for several years now. IRC has been a good solution for a long time, but it has centralized servers KDE cannot control. It is also insecure and lacks features users have come to expect from more modern IM services. Other alternatives, such as Telegram, Slack and Discord, although feature-rich, are centralized and built around closed-source technologies and offer even less control than IRC. This flies in the face of KDE's principles that require we use and support technologies based on Free software. However, our search for a better solution has finally come to an end: as of today we are officially using Matrix for collaboration within KDE! Matrix is an open protocol and network for decentralised communication, backed by an open standard and open source reference implementations for servers, clients, client SDKs, bridges, bots and more. It provides all the features you’d expect from a modern chat system: infinite scrollback, file transfer, typing notifications, read receipts, presence, search, push notifications, stickers, VoIP calling and conferencing, etc. It even provides end-to-end encryption (based on Signal’s double ratchet algorithm) for when you want some privacy. Read more Also: KDE To Support Matrix Decentralized Instant Messaging

Android Leftovers

Canonical Is Planning Some Awesome New Content For The Snap Store

There I was, thoughtfully drafting an article titled "3 Things Canonical Can Do To Improve The Snap Ecosystem," when I jumped on the phone with Evan Dandrea, an Engineering Manager who just so happens to be responsible for the Snapcraft ecosystem at Canonical. As it turns out, that headline will need a slight edit. One less number. That's because I've just learned Canonical has some ambitious plans for the future of the Snap Store. Read more

Extensive Benchmarks Looking At AMD Znver1 GCC 9 Performance, EPYC Compiler Tuning

With the GCC 9 compiler due to be officially released as stable in the next month or two, we've been running benchmarks of this near-final state to the GNU Compiler Collection on a diverse range of processors. In recent weeks that has included extensive compiler benchmarks on a dozen x86_64 systems, POWER9 compiler testing on the Talos II, and also the AArch64 compiler performance on recent releases of GCC and LLVM Clang. In this latest installment of our GCC 9 compiler benchmarking is an extensive look at the AMD EPYC Znver1 performance on various releases of the GCC compiler as well as looking at various optimization levels under this new compiler on the Znver1 processor. Read more