Lunar VS caniuse

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.

We do have a great tool such as CanIUse and of course, BaseLine is not going to replace it.

Can I use...

Lots of parts to WebRTC ( https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API ) but none that I know that can knock out something outside of your browser. It could maybe overload RAM and get killed.

Try using the offending website on a browser/OS that _doesn't_ have WebRTC such as https://caniuse.com/?search=webrtc. Or try with WebRTC disabled.

Possible you're getting throttled by your router or ISP when certain connections are made.

And there's this https://browserleaks.com/webrtc

A11ySupport.io: The caniuse of accessibility. Lists compatibility of various browser accessibility features for different screen reader and browser combinations.

Ah yep! I just didn't wait long enough. Very cool. Seems like it took a lot of work. And it seems better than other browser-based video editors I've seen in the past, so kudos.

TIL about the webcodecs API to get frames of video and chunks of audio: https://caniuse.com/?search=webcodecs

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme.

https://caniuse.com/?search=css3

For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com

If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?

It’s a glorified feature matrix, and usually a project of a passionate community. I approve, even if some of the memes are a bit dank.

https://caniuse.com/ is a popular tool to check what web features are working across different browsers - "can you use this and assume that it will work for others".

The article uses custom css @properties which are awesome and have 88% browser support [1].

One thing to watch out for is differences in how browsers handle setting the fallback initial-value. Chrome will use initial-value if CSS variable is undefined OR set to an invalid value. Firefox will only use initial-value if the variable is undefined. For most projects, this won't be an issue, but for a recent project, I ended up needing to use javascript to set default values in Firefox to iron out the inconsistency between browser implementations.

[1] https://caniuse.com/?search=%40property

Safari is the only browser that doesn't support extending HTML element

https://caniuse.com/?search=Custom%20Elements

You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed!

https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...

https://caniuse.com/?search=webworkers