Linux also shows up more in CVE databases etc because many distributions also assign their own CVEs for the same bugs.

I thought Lepton was being built on top of Waydroid? So technically you can already use the core feature of Lepton today.

Effluently shining!

Totally - it got us discussing! And if we didn’t, that daemon wouldn’t have been flagged.

Cheers for the thought provocation.

I’m not a Mac lover, it’s just the term; Spyware is data gathering in secret without the user’s knowledge. Apple seems to have it all documented and controllable vs say Windows where you can’t turn off telemetry gathering, just set it to “Basic/required”.

More a semantics thing. I assumed you meant there was something you can’t turn off in Apple shit and it’s done secretly (another commenter has highlighted a daemon that’s doing exactly that!).

I wasn’t part of the downvote brigade either. I don’t get why people downvote stuff that’s more a point of discussion. You didn’t say anything shocking nor blatantly incorrect.

Honest question; in what way is it spyware and do you have references?

From everything I’ve ever seen, macOS is more transparent and controllable than Windows or Android.

I’d still recommend Linux but if I were forced to use a mainstream commercial OS (e.g. for work), I’d pick macOS over anything else except FOSS.

You had McDonalds? That was just a farm in my day. Eee-eye-eee-eye-oh!

They’re raising it because of RAM needs of browsers and GNOME.

If you’re a shell nerd like me, you’ll still be fine running it on a potato.

Macrohard Window

Most corporate owned devices are managed with some kind of tool (for restricting what users can do, pushing out software and updates, etc). These tools are called Mobile Device Management (MDM).

The developer is detecting the presence of MDM tools and using that to present a splash page to the user about the licensing requirements etc.

Some educational institutes use MDM to manage students, even so far as to require it be installed on personal owned devices. The developer has been working with edu users to except them.

Bad for Meta. They wasted a lot of time, money, manpower etc.

Edit: I’m just answering the person’s question. I hate Meta - I don’t have Facebook and I don’t have a Quest.

Pretty sure it’s My Name Is All En.

Dr En En En.

Mozilla are still using Phabricator?! That stopped being maintained in 2021…

Apple’s entire history as an org has been as a fast follower, not a first mover.

The Apple Newton is a great example of why they avoid being a first mover.

I’m always confused why the energy isn’t just put on pressuring Firefox publicly rather than just sitting in comments being negative and suggesting forks that critically depend on Firefox and can no way continue development without upstream.

CVEs don’t get issued “resolved” statuses… They are either reserved, published, or rejected (technically NVD have a few extra for published). That’s just junk data in that tool you’re using. Use authoritative sources like cve.org or nvd.nist.gov.

You can see the CPEs on NVD and they’re old versions of Plex (and were old when the vulns were published).

You’re aware those CVEs are only relevant for ancient versions of Plex and were fixed long ago?

You’re going to need to back up your claim otherwise you might as well be lying as there’s no CVE like this I can find nor any public disclosure.

Plex have a bug bounty program and a responsive security team too.

Post your security report.

Both faster_log and async_println were purely malicious packages (not taken over and turned malicious).

I know faster_log is typosquatting / luring fast_log users but I’m not sure about about async_println (which was a clone of the malicious faster_log).

async_std::print is a thing so I guess trying to lure users who search crates before docs :shrug:

Both were impersonating fast_log.