Language Selection

English French German Italian Portuguese Spanish

Adobe Inadvertently Makes the Case for Free/Libre Software

Filed under
Software
  • Adobe Warns Users Someone Else Might Sue Them For Using Old Versions Of Photoshop

    For years we've noted repeatedly how in the modern era you no longer truly own the things you buy. From game consoles that magically lose important functionality post purchase, to digital purchases that just up and disappear, we now live in an era where a quick firmware update can erode functionality and overlong EULAs can strip away all of your rights in an instant, leaving you with a hole in your pocket and a glorified paperweight.

    The latest case in point: Adobe this week began warning users of its Creative Cloud software applications that they are no longer authorized to use older versions of the company's software platforms (Lightroom Classic, Photoshop, Premiere, Animate, and Media Director). In the letter, Adobe rather cryptically implied that users could risk copyright infringement claims by mysterious third parties if they continued using older versions of these platforms and refused to update them. E

  • Adobe Tells Users They Can Get Sued for Using Old Versions of Photoshop

    Adobe is warning some owners of its Creative Cloud software applications that they’re no longer allowed to use older versions of the software. It’s yet another example of how in the modern era, you increasingly don’t actually own the things you’ve spent your hard-earned money on.

    Adobe this week began sending some users of its Lightroom Classic, Photoshop, Premiere, Animate, and Media Director programs a letter warning them that they were no longer legally authorized to use the software they may have thought they owned.

    “We have recently discontinued certain older versions of Creative Cloud applications and and a result, under the terms of our agreement, you are no longer licensed to use them,” Adobe said in the email. “Please be aware that should you continue to use the discontinued version(s), you may be at risk of potential claims of infringement by third parties.”

Adobe warning of legal problems

  • Adobe warning of legal problems if subscribers keep using old versions of Creative Cloud apps [u]

    "Adobe recently discontinued certain older versions of Creative Cloud applications. Customers using those versions have been notified that they are no longer licensed to use them and were provided guidance on how to upgrade to the latest authorized versions," said Adobe in a statement to AppleInsider.

    "Unfortunately, customers who continue to use or deploy older, unauthorized versions of Creative Cloud may face potential claims of infringement by third parties. We cannot comment on claims of third-party infringement, as it concerns ongoing litigation."

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's howtos

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights