Lunar VS RatPoison

It’s done in a similar way on macOS: a dylib is added to the bundle and an LC_LOAD command is added to the app binary. The dylib is the first thing that runs because of using the constructor attribute, like this: https://notes.alinpanaitiu.com/Injecting%20a%20DYLIB%20into%...

The nice thing is that a signed app will refuse to load a dylib that does not have the same signature. So crackers will be forced to change the whole app signature which can be easily detected in app code.

I have that kind of protection in Lunar (https://lunar.fyi/) and Clop (https://lowtechguys.com/clop) and it seems to be good enough as they have no recent cracks.

Pretty sure Lunar [0] can do this for you, and you can buy a lifetime license.

[0]: https://lunar.fyi/

I've had good luck with the Lunar app - it manages my Dell and LG monitors on an M2. (No affiliation) https://lunar.fyi

Wild! I am working on exactly the same thing now for Lunar (https://lunar.fyi), and I'm also calling it Night Mode ^_^ what a coincidence

I've been trying to make "white regions in dark backgrounds" less painful for months, but doing that at the system level on macOS is incredibly hard. I see you're doing it with CSS filters, which make sense in the limited scope of an article. But applying something like that on the whole macOS UI would cause confusion.

I already use something similar on the iPhone: I read on the Kindle app which has white text on black background, then I have a full red Color Tint filter on the Triple Back Tap shortcut which I use before reading. Very similar effect to your solution, although I don't have images in my books.

I was comparing anti-piracy measures with DRM, I don't have actual DRM in my app. I can't block users that really bought the app from using it (which is what DRM is notorious for).

But I do have a license verification for the Pro features (https://lunar.fyi/#pro), and that is what people are cracking in the app. I only added more protection around this verification.

Lunar

There's no Reduce White Point on Mac as far as I am aware. However, you can use the fantastic Lunar [0] app to achieve this, as it supports "Sub-Zero Dimming".

To use it, I think you just need to start Lunar, and then press the Reduce Brightness button on your keyboard until it goes below the minimum Mac allows.

[0] https://lunar.fyi

As the dev of a macOS app that breaks all the time because of external hardware, the tone of the article hits close to home. (I’m talking about https://lunar.fyi/ whose brightness control commands can be blocked by USB-C hubs, “smart” monitors, too long cables etc.)

I had to disable public GitHub issues on the app repo [1] because people seemed to fuel each other with spiteful comments and “why can’t you just!!” sentences.

The contact form still attracts many such “entitled” people and it hurts to wake up to such messages, but at least I can choose to ignore those if I can’t bring anything to the discussion. There’s no peer pressure.

These people are expecting too much from a handful of developers who are sharing a lot of free work and time that could have been spent better than hunting new IDs in URLs and updating regular expressions.

[1] https://github.com/alin23/Lunar

Last year I bought a second computer for my music studio. I wanted to use the same set of 2 monitors and wired keyboard + trackpad on both machines.

I wrote simple scripts to switch my monitor inputs with keyboard shortcuts (even simpler with Lunar, amazing new Mac app — https://lunar.fyi), which saved me from having to press annoying input-source buttons.

But I couldn't for the life of me find a simple, suitable software controllable KVM switch. That still requires the hardware button to be controlled, so frustrating.

Some people like the process of writing code, more than the end result. I had a few months of that feeling, but nowadays it’s rarely about writing for me.

Just the other day I used Copilot to explain the disassembly of macOS KeyboardBacklight code, so that I can turn off the keyboard lights when using Lunar’s Blackout (https://lunar.fyi/#blackout)

It even helped me generate the ObjC function signatures from assembly and use the right calling convention in Swift afterwards. It really feels like magic.

I would have no joy in writing that code, it’s mostly bridging and translation anyway. I just need it to do this thing so that people can take advantage of it.

Nah, since 8th June when I could prove it was indeed RatPoison we pinged everybody with additional info. Status on GitHub was a pull request, not even by a developer.

if you have your own paste, just do this without the me.dead stuff

Is it detected now? · Issue #782 · RatPoison-dev/RatPoison · GitHub

#1: crip shit out here nigga #2: they fell for it #3: In case any of you want to know what really led to all this detection drama. | 0 comments

[COMMUNITY WARNING] RatPoison detection + Valve Anti-Cheat methods update. It appears Valve has recently updated their anti-cheat system (Valve Anti Cheat). This first section will describe my findings with the new modules and various information you may find interesting. The second section will have some news about RatPoison. Let's get started with the VAC update. First of all, we received 2 new modules in the last ~240MB update. Module 1 consists of a Process Memory handle listener and will flag all calls to ReadProcessMemory/WriteProcessMemory, rendering externals that aren't utilizing thread hijacking detected. The second module is an integrity check that utilizes a variety of assorted hashing algorithms implemented in C++. Notable mentions are: SHA-384, FNV and a XOR cipher with base64 underlying bind. This module runs a full S&I check on the currently running game platform (source.exe, hl2.exe, csgo.exe). To prevent false positives, it runs the checks on the modules loaded as well (they should not be tampered with in normal circumstances). Unfortunately, due to these events our cheat RatPoison has been detected. The majority of persons that have used the cheat in the last 2-3 months will most likely be banned soon. RatPoison Project will be shutting down soon. The repository will be archived at https://github.com/RatPoison-dev/RatPoison. A note from the developers follows this decision (quote): --------------- Hello to the CS:GO cheating community. In light of recent events, we have decided to shut down the RatPoison project. Reasons include: social issues, developer complications, and problems with how hard it would be to continue the development process. --------------- (end quote) Please do not message the RatPoison team. This decision is irreversible. P.S. If you have played with ratpoison I would recommend transferring all your skins to another account since some bans will be delayed.

Unfortunately, due to these events our cheat RatPoison has been detected. The majority of persons that have used the cheat in the last 2-3 months will most likely be banned soon. RatPoison Project will be shutting down soon. The repository will be archived at https://github.com/RatPoison-dev/RatPoison. A note from the developers follows this decision (quote):