• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: August 19th, 2023

help-circle




  • Adobe used to house all the licensing mechanisms in a single file named amtlib.dll. The people who cracked it just nulled out the function. And since it was the same for every piece of software, just repeat the null process for each one. Bam, the entire suite for free.

    When Adobe switched from CS to CC subscription, it was cracked in 24 hours. Largely because they didn’t change much.

    Adobe then axed the crippling DLL file and baked the mechanism right into the executable. A patcher tool was released that could crack each one. The upside is you could install and keep them updated from the CC Desktop and just run the patcher each time. Sometimes you had to wait for an update to the patcher. So before you clicked “update” you had to double check to make sure it worked.

    To stop the free trial abuse (which is how people installed anyway) Adobe started requiring billing information during setup before you even get to downloads.

    Later on, Adobe prevented users from updating apps if there wasn’t an active subscription.

    The patcher eventually stopped working because it was abandoned (this around 2019 when I gave up using it because Resolve and Affinity were more affordable and met my needs.) Months later someone else picked up the patcher development. There’s also pre-cracked versions you can download and install.

    I’ve not touched Adobe since and find Resolve to be significantly more stable and at $300, much more affordable. The Affinity Photo and Designer apps are great and affordable too at $170 for the bundle.







  • It’s always been bad practice to just blindly update software. That’s why we have different distros.

    Ubuntu and Mint hold your hand and make it easy for newcomers. Great way to dive into Linux. I completely agree these are great for “it just works” and no fuss. I’ve not had one break on me.

    Arch and Gentoo expect you to have experience and know what you’re doing. You build it up how you want it. That’s what makes these so great. But you need the experience and knowledge.

    I’ve personally tried openSUSE and in my opinion it feels like a good middle ground between both ends. In the past I’ve recommended Mint to get started, openSUSE once you’ve got experience, and then Arch for when you want total control.









  • Arch is not meant to be a daily driver if you’re expecting “shit just works” stability long term when you just blindly run updates. You have to understand what you’re updating and sometimes why.

    It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems.

    If you want to use Arch, you need to invest in snapshots using rsync or dd. Given how it’s a rolling release, you should do this weekly. If something fucks up, grab all your logs and put them somewhere safe. Roll back and look at your logs to see what broke. Then apply updates as needed. You can ignore packages for quite a while. If you’re not smart enough to understand it now, you may in the future. It takes time and practice.

    Debian based is only “out of date” feature wise because they do a package freeze. They ensure stability before release. Updates are largely security related.


  • Your entire statement here stems from not knowing what you’re talking about. That’s OK. I’ll provide some insight.

    Secure Boot is a security feature of UEFI that only allows trusted, cryptographically signed operating systems to boot. The nature of this prevents rootkits. Software that runs before the OS and injects itself. BIOS has many hard limitations and disadvantages over the modern standard that is UEFI. Your comparison going from 32 to 64 bit architecture is quite fitting. It’s not that different. There are many hard limitations and disadvantages to 32 bit. It’s unfit for today’s standards due to lack of features and security. All aspects of technology have to move forward.