What is triald and why is it taking so much disk space?
eclecticlight.co
eclecticlight.co
- I find it so odd, Apple users fascination of their own operating system, this sort of voyeur or wildlife documentarian attitude. It’s your machine, but the inner workings are this ineffable mystery.
>I’m not aware of any control over or opt-out from Trial, although it could be covered in Apple’s general request to share data including panic logs, if you can remember where to control that.
>I first noticed Trial when studying Visual Look Up in the log. At the start of each Look Up, the subsystem com.apple.trial enters the following into the log:
>Initializing TRIClient. Trial version: TrialXP-292.18
>_PASEntitlement: Entitlement "com.apple.private.security.storage.triald" is not present.
>Found entitlement: "com.apple.trial.client" --> <private>
><private> 0x12d9547e0 (no container): using Trial root dir <private> >This suggests that Trial is recording information about Visual Look Up, although nothing more explicit appears in subsequent log entries.
- Apple can double speak all they want about digital privacy, but their actions tell the truth. As a paying Apple customer, you’re not deemed worthy enough to even understand how your own machines work, less even to “tamper” with their working, and who knows what data is actually being shared?
- Personally, I say no thank you. I’ve been on Debian or a variant for almost 10 years now, and haven’t looked back. It’s only gotten easier, as software generally moves more and more to SaaS web apps and the intrinsic cross-platform nature of the browser.
Fortunately, I can buy my personal hardware from whomever I wish, and it certainly will not be Lenovo.
That has _very_ much not been my and some colleagues' experience.
Are you really that careless with your privacy and your basic freedoms to the point that you make your choices based on the ~battery life~ of your computing device?
Sorry to pick on you, but whenever I hear these sorts of questions I realize how shallow people can be, even those who are (supposedly) informed and smart enough to know better.
To be worried about the inconvenience of ~shorter battery life~ over fundamental freedoms is like failing the marshmallow test for tech people.
Not OP, but yes. In a laptop, battery life is the number one thing I'm looking for. That being said, Linux does fine when it comes to battery life in my experience.
2. Many of us simply do not agree that the use of an Apple computing device impinges on either our privacy or basic freedoms, or (more nuanced) that the marginal risk is so small that it’s not worth the moderately large inconvenience of shorter battery life.
2. There is no argument here: if you can not control what and how your device operates, your freedom is being taken. You can argue that you don't value this freedom over the convenience it brings you, but this is at best an admission of you being on (1).
Can you explain to me what the long term gain I could expect, exactly, by foregoing a MacOS laptop?
I have lots of computing devices; many are Linux, a couple are Windows, and I have an Apple laptop.
This follows two attempts at a Linux laptop, with crummier hardware in many ways, and many inconveniences from Linux-on-the-desktop sucking. It just works, and I have lots of battery life.
> 2. There is no argument here: if you can not control what and how your device operates, your freedom is being taken.
Am I supposed to be a free software zealot? If my computer sucks, that also impinges on my freedom.
Yes, there may be some hypothetical ability to clone lots and lots of repos and do a lot of troubleshooting and cure one source of suck-- and then argue with upstream maintainers and kowtow until eventually my fix is accepted. When the sources of suck on Linux outnumber the sources of suck on MacOS by a reasonably high multiple, I'd rather keep the MacOS device in my bag than the other machines I have that run Linux.
If you're going to argue about some kind of collective loss by many people making the same choice as me-- that we all lose freedom, etc-- spare me. Tragedy of the commons, etc: not enough people are going to make the choice you're posing to have any significant effect.
You would not be contributing to an ecosystem controlled by a single entity who is increasingly abusing their dominance to extract more rent from consumers and other developers.
c.f.
> > If you're going to argue about some kind of collective loss by many people making the same choice as me-- that we all lose freedom, etc-- spare me. Tragedy of the commons, etc: not enough people are going to make the choice you're posing to have any significant effect.
So, I'd be using my market power to advocate for things that are disproportionately important to you at my own expense. That doesn't seem like "freedom".
I've been a Linux user and developer forever. For awhile, I was a kernel subsystem maintainer. I've walked the walk about making free software available and useful.
I also believe having a Mac laptop benefits me, and is worth the money, and that it is not morally corrosive. Can you please spare me the judgment that I'm "weak-willed" or stupid for my choice?
A billion flies can not be wrong...
I am not personally affected by what you choose to use. I could give two shits about it and go on with my day.
It's you who stands to gain or lose - along with all those that make a similar choice.
> That doesn't seem like "freedom".
You are also free to stuff yourself with sugar, drugs, play russian roulette, sleep around with any willing consenting adult.
But no, being free to do X does not mean that X is morally virtuous. And you don't get to say "spare me of your judgement" and you shouldn't be expecting any sympathy if you have to face any consequences when things blow up on your face.
This willfully pretends not to understand the argument (I hope). My use of MacOS is not likely to make a big difference in the adoption of MacOS, and therefore ascribing all of the massive network effect of usage to me is a tad unfair.
> I am not personally affected by what you choose to use. I could give two shits about it and go on with my day.
OK. Personally, I'm doing quite fine with MacOS for my laptop. Thanks for your concern, but you don't need to call names and judge me over it. If you really don't care so much, you can spare us all the invective.
> You are also free to stuff yourself with sugar, drugs, play russian roulette
All of these things have likely and measurable short term harms to the individual doing them. Using Apple carries some risk of individual and systemic negative effects, but also some benefits (both individually and communally).
Note, this is true of all things. I just drove to school to teach some classes to kids. I could have died on the way. There are possibly even better moral choices of where I could spend my time that are given up (opportunity costs). But, I judged this is what I wanted to do and the benefits outweighed the risks.
> But no, being free to do X does not mean that X is morally virtuous.
I'm pretty sure that I've done way more to make open systems possible on the desktop than you. The fact that one thing I'm doing isn't moving the needle that direction (but isn't hurting it, either) should be OK. Otherwise, you should immediately stop all activity which isn't helping the cause of open-systems-on-desktop to avoid accusations of hypocrisy.
> you shouldn't be expecting any sympathy if you have to face any consequences when things blow up on your face.
Anyone deserves sympathy when things blow up in their face.
It's not all to you. But you are contributing to it, and you shouldn't be excusing yourself on the basis of "look at everyone else doing it".
> I'm pretty sure that I've done way more to make open systems possible on the desktop than you.
This is not a competition to see who is more virtuous or less of a sinner. It is just me arguing that using Apple products is a moral failing.
> you should immediately stop all activity which isn't helping the cause of open-systems-on-desktop to avoid accusations of hypocrisy.
I am not perfect and I am not free of sin. But at least I am willing to call a failing as such. The first step to redemption is to accept your own faults.
I think there's room in the world for closed offerings and open offerings, and that they each have their own advantages and contributions to the world (and their own risks).
> The first step to redemption is to accept your own faults.
P'raps calling most of the world "weak-willed" (which I notice you've stealth-edited your prior comment to soften) and implying they may not be "smart" is going a bit beyond accepting your own faults and instead exposing others to harsh judgment for not valuing the things that you do.
You frame it that way -- most people don't.
I like having a MacOS computer. Lots of daily things work better. Including battery life.
Linux still exists and I still use it elsewhere. If Apple turns evil, I can move to having a Linux laptop again and just be slightly more miserable.
It is not a matter of "turning evil". They are already do "evil" things. It's just that you don't care because it doesn't affect you personally or the things that you consume from them.
I disagree. I think Apple has been a pretty good steward as a commercial vendor, with a few missteps. I have a pretty high degree of trust in them-- though my eyes are always open for any substantive problems emerging.
To illustrate something by exaggerating (one of) the numbers to make it crystal clear what I'm getting at:
A Mac that I don't fully control but has 12 hour battery life feels more free in practice than a fully-open platform with a 1-hour battery life. The latter leaves me less able to use the device for things I want to, and takes up more of my time hunting for wall outlets or just having a dead machine when I need one that's working. Time spent keeping my devices working does not feel like freedom, since I could have used that time for other things.
There's hypothetical freedom to do stuff I don't really care to do (audit or fiddle with my OS), then there's the actual range of liberty-of-action for stuff that I do care to do. Personally, I tend to favor the latter, strongly. The former's just a nice-to-have.
"Inconvenience caused by a shorter-battery life" vs "patronizing a company that is systematically abusing its power to take away freedom from everyone" is not such a case that requires any type of trade-off to be made.
The biggest issue is getting all the hardware supported out of the box. For example, there is a certain amount of mucking about you have to do to get any off the shelf laptop running Linux. On rare occasion system updates change something that the laptop doesn't like, hunting down that change can become tedious.
I've owned Samsung laptops, HP laptops, Thinkpads. I've built my own work desktops. I've never had any issues, as long as the hardware is ~6 months out on the market.
That's about the time it takes for linux devs to catch up with companies that focus on windows drivers.
The rule still is to get either a Linux-supported or at least a Linux-popular laptop, even if it's more expensive or doesn't match all your features/requirements. Then it doesn't matter whether it's 6 years old or brand new. It will work.
i.e. it's more important for it to be Lenovo and the correct line than the age. But not all Lenovo are equal. T/P stuff is likely supported out of the box even if brand new. X depends on popularity of the model. Tablets/IdeaPad stuff.... look elsewhere. (Lenovo is just an example, leaving other brands for the reader).
Even on very cheap HP laptops, following this rule has worked for me flawlessly so far. Between telling people "you should spend more money on X just to be sure" and "Y is cheaper and it is very likely that it will work", I'd 100% recommend them trying the cheaper option first. Even if it turns out to not work, they can always return it and go to the more expensive alternative later.
And not only I have _never_ bought a new laptop ( always used/refurbished/thrift) , but for the past 12 years I have been submitting patches to Linux to support the laptops I get. Once you get outside of the popular lines, there is very few people doing that. It will not happen in 6 months or 6 years unless you do it. Typing this from an HP laptop which even 6 years after release did not have all WMI hotkeys mapped.
I have 5 laptops on linux at home, all but one being from a "pro" line (ie Lenovo thinkpad, HP elitebook, Dell latitude, all have a working webcam. I'd say with the exception of fingerprint readers which I never cared to test all the functionnalities have been working from day 1.
I think anyone is safe provided you buy profesionnal models, don't buy the latest and newest tech and avoid nvidia GPUs.
The IPU3 (Kaby Lake era!) is the only one generation that has been upstreamed, and as of today it only supports 2 types of sensors that were used in a couple Lenovo Miix models. Nothing else! There are some patches floating around for the Surface devices of the era [1], but nothing upstreamed. And of course any newer IPU is out of the question (Intel is now at IPU6).
And it happens that all of these IPU3 webcams that work with upstream kernel are mostly because of the effort of just ONE guy, who is not employed by Intel, and who did not even know C a couple years ago (if you happen to be reading this, kudos to you!).
[1] https://github.com/linux-surface/linux-surface/blob/master/p...
You have an even older model, I guess. Before SP4 webcams were USB.
Honestly, I don't.
I think all my laptops had only iGPUs. I always treated my laptops as secondary workstations for the times I was away from my main desktop.
Or don't out Linux on Windows hardware. System integration teams are a thing, and one person without access to documentation is going to do it poorly.
Instead, buy Linux in Linux hardware.
For reference, Windows on the same laptop gets about 6 hours while just sitting there.
I've literally never needed to search my disk for a file (using the Windows search interface), and if I ever do, I'd rather wait a few more seconds that one time for my search to complete, rather than have the indexer consume my CPU at all times.
This set of problems may be obviated by actually getting Manjaro to cooperate. It's on the todo list.
I have been using Rawhide (+ mainline, non rc or git, kernel) on my work machine for the past 6 months without issue.
If you have to compile a lot of kmods it can be a pain as everything is transitioning to GCC12 but the kernels are still built with GCC11. A container can take care of that though.
yum is still aliased on most fedora / rhel systems so you can put Fedora 35 on a drive and run yum update -y and it'll kick off the associated dnf process.
I assume that got better, though. I hope it did.
And yes DNF is much faster.
That does speak to the remarkable efficiency of Voidtools Everything, as I understand it they don't use Window's filesystem stack but parse the NTFS partition directly. And I get that the Windows indexer is technically more powerful because it indexes file metadata like author etc. I still don't get what makes Windows search this slow.
It the same for transferring the folder/files to other location. a single 1GB file will take 5 second to transfer to external hard drive. A 1GB non-zipped folder (consists of thousands of thousand file from 1KB to 1MB each) will take half hour or more to transfer to external drive. I have a 150GB folder that contains over 500k of files, averaging 120KB to 4 MB, will take 3 hours to transfer to the external drive. I have another 120GB folder that are consist of videos, averaging 300MB to 10GB, took 20 minutes to completely transfer to external drive. This transfer through NVMe ---> spinning rust external drive through USB 3.1.
If you are pulling a large repo that have thousands of files in it will take a while for Spotlight to index each file. That is not the fault of Spotlight, that is just the way it is because it have to scan individually each file to index.
Also to completely disable it, you needs to disable the service and remove the entry from schedule tasks. It keep coming back because of the service and scheduled tasks are not disabled. This is how Google Chrome keep starting up their updater and bypassing my disabled startup entries for Chrome. Because of scheduled tasks is not removed, Chrome uses that to reactivate their updater and recreate a startup entry. Managed to completely neutered Chrome updater through Sysinternals AutoRuns.
At some point, every machine's software becomes an ineffable mystery. Do you know what is going on in all your 3rd-party Linux drivers, say, from NVIDIA?
The replies to my original post seem to me to be arguing for 100% transparency from the keyboard to the atoms on the finfets. I don't think I'm strawmanning that (maybe hyperbolizing a little, but with RISC-V proponents, maybe not!)
That sounds like a noble goal, like world peace, ending starvation, and curing all modern ails. However, the extent to which tribalism and out-grouping emerges from people who don't use the "superior, pure" solution is nonsense: just look at the tone of the first post, snidely declaring that this is proof apple is again such a bad solution. That's not helpful, and after hearing similar tech arguments for nearly 35 years online, it is tiresome (ironic). On top of that, the dream of transparency seems unlikely because every open source hardware project I've ever seen has failed [1], there is zero motivation for it.
Again, not to say it isn't a noble goal, but don't fetishize it to the point of outgrouping others.
[1] This is a broad statement, as there is plenty of gadgetry that is open source hardware. I mean: open source hardware for Linux laptops. Or at least hardware that has open source drivers but doesn't have an "Appendix H".
Since I can't meaningfully audit kernel level stuff anyway (not my area) I mostly care whether it works for me (or for the production purpose the customer needs or etc.) and that's not an ideal world but I choose to prioritise open source userspace contributions and running code.
I also run windows 10 on a Thinkpad Helix 2 for my personal machine - with WSL to provide me an X11 environment that I use to ssh to the debian/freebsd/<whatever the customer runs> machines I'm actually doing development work on. I like writing server side code (and tolerate writing browser side code) so being a linux desktop admin would involve a whole extra field of expertise that wouldn't gain me anything, and I'd rather spend the required learning time on writing and publishing more code instead.
Other people are entirely welcome to choose entirely different trade-offs, of course, but this particular attitude works for me.
Edit: Ironically, my one foray into OS X ended because Aqua insisted on reaching into my X11 instance and controlling focus, which completely trashed my fvwm2 FocusFollowsMouse setup in terms of usability for me, so I decided the Microsoft black box was a better trade-off than an Apple black box even though in those days I had to have cygwin for my X11 + ssh setup.
I hate using Linux on the actual laptop. The touchpad is always a trainwreck. Sensitivity and scroll speed/acceleration is infuriating (too much Xorg config hassle). Trying to get "middle click" working -always- has issues. Power buttons never work properly, same with LidClose actions (i've read many knowledge bases and stackoverflow posts, none seem to work for my particular hardware, as is always the case). It is frustrating as hell to get it to act like a well-behaved "normal" laptop. Don't get me started on suspend/hibernate issues, or the flaky bluetooth drivers that always need system ctl restart command line help.
Now that I've made the tradeoff to not use Linux as anything but a remote server via VNC, my choices are Windows or Mac for a primary computer. I don't like ads showing up in start menu, or idiotic MFA and login requirements, so I'm left with Mac.
But I don't get on with touchpads (the apple ones are absolutely superior to anybody else's but it's just not my thing) and my wrists -really- don't get on with mice these days, so a trackpoint is pretty essential to my comfort.
Happily, I see the start menu sufficiently rarely that any presence of ads doesn't even register to me, and the login stuff is basically "meh" since it's (so far) stayed out of my way sufficiently for me not to care.
But that's my choice of trade-offs - may you have great joy out of yours :D
If people wanted to fight for it, stop using NVIDIA products, but do you see that happening? Not bloody likely.
This isn't so much whataboutism as it is about trying to coerce an ecosystem of hundreds of vendors to listen to a small cadre of open source proponents.
If the Linux kernel forces AMD to improve UAI and make it look like LAM, I'd consider that a victory. Let's see what happens.
Nouveau will get there, one hopes...
i.e. the ability to examine and understand something weird that’s going on and that may be a potential problem.
This ideal falls short in the hardware realm, where we have to contend with the Intel Management Engine and the like.
Nevertheless, the modern Linux world is vastly more open and accessible than the closed-by-design Apple world. Even if I had to use Nvidia drivers, that would be one binary blob in a sea of open source, whereas the Apple ecosystem is opaque binary blobs as far as the eye can see, without even the courtesy of documentation. It makes a difference.
Here's the practical upshot - once, many moons ago, I forwarded port 22 to my home desktop machine so I could access it remotely. I had fail2ban running and regularly checked the logs, so I wasn't worried. What I didn't realize was that maybe 6 months prior I'd made a test account for some purpose, with 'test' as the username and password. Inevitably, some worm managed to guess this combo in less than the 6 tries before fail2ban kicked in. The kicker, though? I was sitting at the machine when it happened, and I could tell immediately. The HDD light was flashing, and I knew it shouldn't be. There was load on the CPU, and I knew there shouldn't be. Checked 'top', spotted the weird process immediately, killed it, locked the account (it never escaped the test account so no harm done) and went on with my day.
Can you imagine that story on Windows? "My hard drive light is blinking and I don't know why" - yep, that's daily life. "There's a weird process in the list" - yep, there's lots of those, good luck tracking down which company is responsible.
Why would I ever buy Nvidia? Asking as a non-AI developer who doesn’t play PC-games.
I’m perfectly happy with Intel graphics. I hear it has good, open-source drivers too.
Exactly what am I missing?
I don't use Nvidia because of this, and I'm not alone. If you ask "what is the best graphics card for linux" on a linux forum you will invariably get a chorus of "not Nvidia".
Similarly, all fruits have fat content. Just off the top of my head:
1. avocados (a whopping 15% fat content!)
2. there is no legal requirement for me to list another fruit here
I’d certainly like to.
There's also a large difference between a closed driver or firmware blob, where the function is known but the workings are not, and large portions of the userspace, including system services and applications, that are entirely opaque.
It really is nice to have, when you want to look it up. Userspace daemons and their behavior should not be a mystery.
At an extreme minimum, most daemons on macOS have at least a man page describing their high level function.
man triald will report no manual entry, though.
Sadly not because, like OSX, that software is proprietary and us filthy peasants are denied the honour of gazing upon the holy source code crafted by the holiest engineers, anointed by Huang himself.
Of course, that's assuming you don't download the Nvidia leak and gaze upon the source code within. That would be bad, you're bad for thinking it, don't do that. Only bad people would do that. May Huang have mercy on your soul.
This appears to be downloading and executing new code, and potentially returning results back to the mothership.
That there is no explicit opt-in, or even much information about WHAT this is doing, is sadly what I've come to expect from Apple.
> - Personally, I say no thank you. I’ve been on Debian or a variant for almost 10 years now, and haven’t looked back. It’s only gotten easier, as software generally moves more and more to SaaS web apps and the intrinsic cross-platform nature of the browser.
Personally, all the paying Apple customers in my family have been able to understand how the systems works to make video calls and talk to their grandchildren.
10years ago we tried installing Linux on an HP laptop we paid for and could barely get a picture opened up because... (do I really need to spell this out?) of unreliable display drivers means that the screen blacks out on whim.
I find it so odd, Linux users overlooking the fact that people who don't tinker with computers all their life do not have the time to get Linux up & running.
Linux, and its various distros, are an ever-evolving tech. Linux 10 years ago was so much less capable than Linux in 2022. Just because it didn't work then, definitely doesn't mean it won't work now.
Seriously, swear to fucking god, every time someone says “oh Linux just works”, the next comment is “oh? I tried that distro on the recommended hardware and had trouble with…”
Next response is ALWAYS: “Oh yeah that’s broken but I don’t use that feature.” Usually about hibernate. As in, apparently everyone using a laptop plugged into a wall and never closes the lid. Or uses a desktop. I don’t even know, it doesn’t make any goddamn sense.
I just don’t believe you guys any more. Everyone who says Linux just works has adapted their workflows to be hyper specific to the things they do, and have just decided that basic-ass features present and working on mainstream OSes are just gimmicks that the rest of us should forgo out of moral purity.
Also with this “try again” noise. Good lord, happy y’all are blessed with the patience to try again until you find the right Goldilocks set of hardware and tweaks that doesn’t give you a migraine but there exists a large contingency of the population that doesn’t spend every waking moment staring at glowing rectangles. Spare us a fucking thought, and spare a thought for our relatives who took years to learn how to double click.
If anyone knows how to get XUbuntu 18.04 LTS to not shut down with the lid closed and power on, please let me know. I have a subnotebook that sits in a cabinet to run something, and since a recent "upgrade", it won't stay alive. Looking with Google produces at least five articles on this, all contradictory and none of which work. There's a GUI for setting this, it's set appropriately, and that doesn't work. There's a relevant configuration file where the "close lid" option can be set, and that doesn't affect this problem.
I don't think you can expect deep empathy and a strong desire to simplify things down to the grandparent level if much of the reason for using the system is for geek cred and a landscape for such endless tuning/tweaking.
I'd even put myself in the latter camp, I like tuning things!
Certainly Linux on the desktop has gotten dramatically better over the last few years, but I don't see it ever getting to appliance level without really cutting out what we typically associate with the flexibility of Linux (more like Android or a set top box)
I just used an outrageously complex espresso machine to make myself some coffee. For most, that would be purely an inferior choice when compared to a drip machine. I think a lot of it depends on how much you want that last few %. I think a lot of people simply aren't interested in the investment required to get a little more out of their computers.
And as a computer guy, of course that makes no sense to me :)
Statement is a bit out of date, apart from a good PC, most Linux users don't even know they are using it.
I find it crazy people have apps running on their Macs and windows desktops that they can't even find out what it is doing, let alone how it works.
Thankfully we have a choice, each to their own.
Have you looked at a Linux syslog lately? This is 20.04 LTS on desktop. It does a lot on its own. Probably too much.
Mar 31 00:33:18 Nagle-LTS whoopsie[1278]: [00:33:17] Cannot reach: https://daisy.ubuntu.com
Mar 31 02:17:42 Nagle-LTS snapd[503370]: storehelpers.go:721: cannot refresh: snap has no updates available: "bare", "blender", "brackets", "chromium", "core", "core18", "core20", "demo-curl", "gnome-3-26-1604", "gnome-3-28-1804", "gnome-3-34-1804", "gnome-3-38-2004", "gnome-system-monitor", "gtk-common-themes", "gtk2-common-themes", "inkscape", "remarkable", "snap-store"
Mar 31 02:17:42 Nagle-LTS snapd[503370]: autorefresh.go:536: auto-refresh: all snaps are up-to-date
Mar 31 02:30:09 Nagle-LTS systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs...
Mar 31 02:30:11 Nagle-LTS systemd[1]: ua-timer.service: Succeeded.
Mar 31 02:30:11 Nagle-LTS systemd[1]: Finished Ubuntu Advantage Timer for running repeated jobs.
Mar 31 03:05:03 Nagle-LTS systemd[1]: Starting Firmware update daemon...
Mar 31 03:05:04 Nagle-LTS systemd[1]: Started Firmware update daemon.
Mar 31 03:05:05 Nagle-LTS fwupd[1434387]: 10:05:05:0005 FuPluginPciMei ME family not supported for 0:9.0.1.1333
Mar 31 03:05:05 Nagle-LTS fwupd[1434387]: 10:05:05:0007 FuEngine failed to record HSI attributes: failed to get historical attr: json-glib version too old
Mar 31 03:05:05 Nagle-LTS systemd[1]: fwupd-refresh.service: Succeeded.
Mar 31 03:05:05 Nagle-LTS systemd[1]: Finished Refresh fwupd metadata and update motd.
The Ubuntu "snap" system is busy, although it didn't update anything today. Two independent systems seem to be updating "snaps", which are part of Ubuntu's container system for remotely updated applications.
Mar 31 06:36:49 Nagle-LTS systemd[1]: Starting Daily apt upgrade and clean activities...
Mar 31 06:37:11 Nagle-LTS dbus-daemon[936]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.11660' (uid=0 pid=1437238 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
Mar 31 06:37:11 Nagle-LTS systemd[1]: Starting PackageKit Daemon...
Mar 31 06:37:11 Nagle-LTS PackageKit: daemon start
Mar 31 06:37:11 Nagle-LTS dbus-daemon[936]: [system] Successfully activated service 'org.freedesktop.PackageKit'
....
Mar 31 06:38:52 Nagle-LTS systemd[1]: apt-daily-upgrade.service: Succeeded.
Mar 31 06:38:52 Nagle-LTS systemd[1]: Finished Daily apt upgrade and clean activities.
Mar 31 06:43:56 Nagle-LTS PackageKit: daemon quit
Mar 31 06:43:56 Nagle-LTS systemd[1]: packagekit.service: Succeeded.
No, one doesn't wonder. one googles that, then there's an answer. That's exactly the root's point here.
Personally I disable snap but I know what it does and why it is useful.
One thing I did do while I was building that first linux pc, and for every computer I've bought or built since then, was a tiny bit of research on driver compatibility. Just something as simple as typing '<laptop model> linux compatability' into google. Or, if while configuring a new system there is a choice of wifi cards or hard drives or whatever, I just look each one up and check before I buy. It is a minor hassle compared to the on-going benefits I derive from a linux system.
Sure, in a perfect world all manufacturers would produce high quality open source drivers for all systems, but we are just not that well coordinated. It is getting better, though.
And that's the reason you don't have problems - you're going for hardware/laptops that are well supported in Linux.
Do you expect mom and pop to do the same? Versus buying something off-the-shelf with Windows, or MacOS and it just working, without needing to undertake that step?
And is your dad a Truck person? He may have enjoyed the research process (heck, I enjoy researching tech purchases).
I try Linux again every couple years, and have every time been quickly reminded why I stopped using it (on the desktop, anyway).
I used to dual boot windows for games. But now I can play games on Linux too.
> while I was building that first linux pc
> for every computer I've bought or built since then
> bit of research on driver compatibility
This is pretty self explanatory. Your expectation of what basic computer skills should be is way too high.
Computers are general purpose tools, the ability to reconfigure them to accomplish different tasks is the core feature that makes them useful.
Not being able to pick out software and hardware that work together is like not knowing how to drive. If you can't do this then you are just a passenger.
Willfully avoiding learning basic programming concepts is like refusing to learn how to change a flat tire. I guess nowadays if your car is always connected to a cell tower and you have a comfortable income you might be able to drive your whole life without ever needing this skill but they were still teaching us how to do it back when I took driver's ed.
What is the difference between not knowing what the software on your system is doing and not knowing what any of your software is doing and it is not running on your system?
`~/Library/Trial/Treatments/SIRI_DIALOG_ASSETS/factorPacks/6242008c0f185b3e2ef6bf8e/assets/com.apple.siri.dialog.socialconversationfl#d5b431b/dialog/SocialConversation.catfamily/dalWhoIsYourValentine.cat/en.cat.bin`
the file is gzip compressed and the decompressed data reveals some strings that are probably related to the question asked in the `cat` file:
tag:valentine";Only localize if Valentine's Day is relevant to your localeJ2�SS[If I could have a Valentine, it would be all 7.5 billion people on Earth. That is<sub alias=",">…</sub> a lot of heart-shaped lollipops.]:�SS[If I could have a Valentine, it would be all 7.5 billion people on Earth. That is<sub alias=",">…</sub> a lot of heart-shaped lollipops.]
So this isn't just about a/b testing but also about feeding current data into Siri to allow some local processing of timely events.
Do note though, that I have Siri disabled on my Mac, so this is of questionable value
Maybe you should check that Siri is still disabled on your Mac?
Would be much nicer if they stated the purpose and allowed for some configuration, though. And verification by third parties is obviously still important.
It's even better in Russian: доверяй, но проверяй, doveryay no proveryay
It's better because it displays both words are semantically related. In fact, "verify" is cognate with their root, vera/veryat', probably a common Indoeuropean root but I'm too lazy to verify (pun intended).
The latest desktop and mobile OSes are quietly shipping code to enable this, despite the uproar that happened when Apple announced it. They let people believe they were stopping the project, but it nonetheless proceeds quietly.
Apple is not trustworthy.
https://en.m.wikipedia.org/wiki/MacOS_Monterey
(Edit for clarity: enable above is used in the "to support" sense. I do not know if such clientside scanning is enabled (in the activated sense) yet, only that Apple has explicitly stated at least twice that it will be. It appears imminent. Some or all of the code has already shipped and is on your machine(s).)
Why should I trust your declarations?
(linked from the above-linked wikipedia article as citation for the clientside scanning feature documentation on wikipedia)
https://web.archive.org/web/20210903214920/https://www.apple...
Apple said they were doing it.
Apple never subsequently said they were not doing it. (They did say some things that implied that they MIGHT not do it, designed to make you stop being mad at them ("Based on feedback from customers, advocacy groups, researchers, and others, we have decided to take additional time over the coming months to collect input and make improvements before releasing these critically important child safety features.").)
They did, however, reiterate that this was going to be released.
What more evidence do you want than the vendor's direct affirmative statements?
When people plainly tell you who they are: believe them.
If you don’t have the signature, it won’t do anything.
I’m a privacy advocate, and this approach actually increased my trust as it was a more palatable option than allowing unfettered server side access in response to LEO requests (which happens in extreme cases, but not on a routine basis.)
Privacy includes privacy to break the law until and unless specific probable cause is established in a court. Companies have no moral or legal obligation to get involved in mass scanning to enable proactive law enforcement. "But the children!" does not make this not a privacy violation. Signatures don't make this not a privacy violation.
The system is also ripe for abuse. What happens when the legislature mandates a regulatory body be able to set policy to amend the signature list?
You do not want to live in the world this creates.
This is not about child safety. Think more along the lines of Tiananmen Tank Man.
The topic is local scanning on an end user device without the consent of the device owner.
Clientside scanning of files given over to the cloud is nonsensical. Apple already scans serverside.
No evidence at all.
So I reiterate: Why should I believe you?
Please don’t reiterate obtuse questions when reasonable answers were delivered on a silver platter.
I'm not moving the goal posts. I'm asking him if he has any evidence that this app is for CSAM detection. So far, I've yet to see any.
Apple is within their rights to scan files on their servers. They already do this now, as you note. This thread is about something else: Apple OS bundled malware that scans files on non-Apple-owned machines without consent, even files that have not left the user's own device. This turns your own local hardware into a snitch against your will. What it scans for is also not within your control.
They do not do this today, but they have stated at least twice that they intend to begin.
It's completely relevant to my point because it's unlikely they'd be doing this without the pressure from US politicians.
There's also a lot of speculation that it's happening device side so that E2E encryption can be enabled for uploads.
E2E encryption that leaks information to the middle device about what data is being encrypted is not E2E encrypted.
It's backdoored.
Any system that can't be used safely by child pornographers for safety from government surveillance cannot be used safely by other groups that the government does not wish to operate. Those groups will (without any convictions) be labeled "violent domestic terrorists" by Apple and the FBI when their in-group memes are added to the clientside scanning signature list.
This is the bright line. It's your computer and data, not theirs.
Companies need to comply with the law. This is not law! Backroom pressure to deny millions due process is not reasonable, democratic, or conducive to preserving human rights. It has no basis in law, it is how dictators operate.
If Apple is breaking current law, charge them. If they are not, stop pressuring them, or maybe try to pass a law to alter their behavior (with associated public debate), like civilized adults do.
"Beautiful company you have there, Tim Apple. Shame if something were to happen to it if you don't help us spy on your billions of users." is about as undemocratic and authoritarian as you can get.
Apple trying to sugarcoat the anti-customer malware they're potentially getting strongarmed into rolling out is just as morally repugnant.
When a judge issues a search warrant, the accused has legal rights that dictate what is and is not probable cause. No such due process will exist with what is or is not added to the content detection signature list, everyone on the platform is deemed worthy of suspicion and is searched. The ML algorithm will declare you guilty based on a list of hashes, the inputs for which you are not allowed to possess or see (but somehow NCMEC is). There is no additional step before guys with machine guns raid your house and steal every phone and computer in it.
This is an end run around human rights to due process.
Not OP, but I'll throw my two cents in. While some people on HN were hyperventilating about the CSAM thing, I was digging into the docs to see what was actually happening. In every instance, I found myself a bit more impressed with how much engineering the folks at Apple clearly put into making it work without compromising privacy. Contrary to what people kept saying here on HN. It made me a lot more suspicious of randos on HN and a bit more willing to give Apple the benefit of the doubt.
I'm always amenable to more actual evidence, but as of yet that seems completely lacking. If I were more conspiracy minded I'd wonder if there was an orchestrated effort.
This is an authoritarian, tyrannical end run around basic human rights to due process, and if indeed it is an essential prerequisite (per the government) to Apple deploying e2e crypto, then we don't actually have freedom of expression (as Apple would presumably be punished by the federal government for publishing software that supports e2e encryption WITHOUT such literal spyware).
The fact that this is even being discussed is a giant blinking red warning light about the lack of freedom in our society. Both for millions like us, who want the availability of quality tools that don't work against our personal interests and human rights, as well as Apple, who appears to not be allowed to publish software unless it contains backdoors for the cops.
https://www.reuters.com/article/us-apple-fbi-icloud-exclusiv...
That should worry you a lot.
PS: Any clientside scanning whatsoever that the user did not consent to, that reports its results to a remote party (even if only positives) is a privacy violation. You cannot scan local files in any way whatsoever (for a purpose that is explicitly against the user, that is, reporting on suspected illegal activity) without compromising privacy, even if Apple's system works perfectly as described. Clientside nonconsensual scanning is inherently a privacy violation.
$ file /path/to/msg-bigG.squeezed_quantized_acceptor.fst
/path/to/msg-bigG.squeezed_quantized_acceptor.fst: OpenFst binary FST data, fst type: squeezed_quantized_acceptor, arc type: standard, version: 3, num states: 1237632, num arcs: 7376910
That's my best guess. Since Siri and Photos now processes more locally (especially on M1's dedicated ML cores), all the training improvements and testing probably happen locally as well.
It makes sense it would regularly download updates for ML models. I'm more curious about what data gets uploaded back to Apple...
The privacy implications of this are dubious. There is as-yet no good research showing how these finetuned models can be used to reveal exactly what photos you have in your photo library, but many experts believe that won't be the case for long.
Really? Apple can essentially be asked by Law Enforcement for answers to questions like "Give me all the IMEIs of people in location X, radius 10 miles, that appear to have pictures of cats"
But experts believe that techniques might be developed in the future to figure out based on the numbers what data must have been in the training set (and hence your photos). Nobodies managed to do that yet.
If you train a model A) cats, one for B) dogs and one for C) dogs and cats. Is there any research which asks if you can do a network subtraction C-B = D, and get a sensible network D than can loosely do what A does?
IMO this is the kind of statement that should have something to back it up.
My guess is dictation.
My Trial folder is about 500MB. I've never enabled Siri on my computers declining the option during the setup at first boot. But I do use dictation quite a bit.
If 500MB is the cost of having dictation work solely on my laptop without hitting the internet, I'm OK with it.
The problem is that people love to invent conspiracy theories about Apple because they have an axe to grind.
They get opportunities to do so because of two things: Many of Apple's daemons and other services are not publicly documented. And because it's running a flavor of Unix, it is a lot easier for amateur computer sleuths to poke about and discover what's running that people outside of Apple don't know about.
Operating systems of the past were more opaque, so we just had to blindly trust the manufacturer. But people can see things better now. It would help rebuild trust if Apple would have a standard reference online explaining all of its OS bits.
> du -hs ~/Library/Trial
2.6M /Users/___/Library/Trial
> find ~/Library/Trial | wc -l
160for folks with siri on and extra bloat, i'd guess they could reduce it some by turning off "Show Siri Suggestions in App" and "Learn from this App" for each app in the "Siri Suggestions & Privacy" section of siri's system prefs (for the apps they don't care about having siri integration).
So many (consumer-focused) FOSS products have huge, obtuse quirks in them that prevent their widespread adoption, and uber-tech-literate people tend to overlook this because they really want to believe that FOSS can succeed.
In reality, a lot of these quirks come about because of the non-commercial nature of the projects[1]. When a business produces software, the aim is to get as many people as possible to use it. This means a smooth (enough) user experience or death.
For software written by volunteers, the aim is to (generally) satisfy the intellectual curiosity of the people writing it. This means huge issues for users, and QA in basically all forms, are overlooked in favour of working on cool/interesting things for developers.
[1] Yes, I know commercial FOSS exists. I run a reasonably large commercial FOSS project myself. However, the overwhelming majority of FOSS projects out there are volunteer-led and run.
Also, terrible obtuse quirks are certainly not unique to FOSS products. Go ask someone who deals with, I don't know, the software used to run hospitals and healthcare systems (electronic health records, or EHR's) as but one example.
You can do stupid things in Linux, but if you stay on the rails (I only upgraded to Ubuntu 20.04 last week) you're fine. Windows will just mess your system up every so often without you even doing anything except installing the updates it tells you to.
https://www.debian.org/doc/manuals/apt-guide/ch2.en.html
What guesswork is needed?
I think that's fair.
If you say yes, it is not an accident but 1. your own decision 2. it is easily reversible.
On the other hand all my blackhat friends have a really bad time with closed source software. This is the primary reason black box security testing is dying.
The number of people who can properly analyse complex software to uncover what it actually does is a line asymptotically approaching zero. While OpenSSL is an overused example, it still remains a good one.
Besides, you’ll never know if the code you’re looking at abuses some compiler quirk without studying the binary.
- a modern OS has anywhere upwards of 50 million lines of code (Linux kernel alone is ~30 million lines of code) [1]
- a modern browser is anywhere upwards of 30 million lines of code [2]
- there are over 3.5 million individual packages available for the various Linuxes [3]
And so on. The pretence that there are people and resources readily available to analyse those sources, and understand them well enough to uncover complex vulnerabilities is just that: a pretence, a myth. As evidenced by high-profile bugs that existed in popular codebases for years.
Does the availability of source code make analysis somewhat easier? Yes. There's a difference though between reviewing left-pad on GitHub and auditing OpenSSL, for example. There are thousands of people who can do the former, and perhaps 5 who can do the latter.
That is why "the number of people who can properly analyse complex software to uncover what it actually does is a line asymptotically approaching zero".
[1] https://www.linux.com/news/linux-in-2020-27-8-million-lines-...
[2] https://www.openhub.net/p/chrome/analyses/latest/languages_s...
I doubt that. And even the people who are good at analyzing binaries probably prefer to have the source code available to save a lot of time.
Maybe some user can be unaware of what is happening with OSS, but the community as a whole will always have accurate information of what is what (unlike this case where everyone is guessing).
OpenSSL audit would like to have a word with this mythical community. log4j vulnerability, too.
For starters, the obvious implied suggestion is that these types of vulnerabilities don't exist in commonly used closed-source systems. That's been proven hilariously false time and again.
Secondly, commercial vendors have seen fit to adopt opensource where it suits them in order to take advantage of (and offload responsibility for) what these components do. You're effectively saying "Open Source community doesn't have accurate information because look at X and Y" and ignoring that "X and Y" were also not discovered to have problems by any closed-source using dependent commercial entities.
I never implied that, obviously or not.
> Secondly, commercial vendors have seen fit to adopt opensource where it suits them in order to take advantage of
Commercial vendors adopted opensource due to lower cost of ownership, not due to perceived lack of problems or because "community knows exactly what is what"
But how do I know the source code I check is the binary my machine runs? Even if I build from source I could have a malicious gcc that takes clean source and outputs a malicious binary.
Unless you are running jit or something you can't really know what your computer is running even if you use open source.
It is certainly a trade off, and everyone will have their own reasoning. There is no objectively correct answer.
That depends on your definition of nefarious.
~/Library/Trial/Treatments/<NUMBER>/factorPacks/<OTHER_NUMBER>/assets/com.apple.siri.asr.dictation.*/etiquette.json
These files do contain an impressive amount of swear words, some of which I had never heard.
But probably needed for Siri to process speech locally, as they'd likely want to filter out those words.
However, linux is alive and well, despite some flavours attempting to force autoupdating snap stores and the like onto users.
For example, Fedora build is ruled by these principles: https://pagure.io/fesco/issue/1518, while the Mozilla build is not.
You need your tools goals to be aligned with your own, and reject any that aren't, not cater to them.
Working around the FF package by installing from elsewhere is no answer.
Otherwise be careful with Manjaro; it is a noble project with great goals and some great implementations (and a stellar community!), but they tend to go a bit overboard on customization for customization's sake which has introduced breakage in the past. Nothing that isn't fixed within a day in my experience, but stable it most certainly is not.
There's also Mint for a more traditional and conservative take on Ubuntu's method, as well as MX Linux which shows off how good Debian can be in the right hands.
Or go crazy like me and start using OpenBSD as your main workstation provided your workflow can adapt to it; I'm on 7.0 on this machine with Firefox 95 and literally everything I need is here.
This is my daily driver for both home and work. I've completely ditched Windows and other versions of Linux. Steam runs fine, and with Proton, I have compatibility good enough not to miss Windows at all. Some games (Dark Messiah is one) that won't even run in Windows anymore run great in Proton.
The company I work for does a lot of container-based work, and aside from a couple tweaks to apt sources that naively assume release names, everything "just works".
So, in conclusion, it shouldn't matter one bit how canonical decides to distribute firefox, if you can just use the debian based apt, or flatpak.
I hope canonical goes away from the snap model, because I've had nothing but issues with it, until I got fed up enough to remove it, and then everything was great again. Issues were mostly related to read-only mounted file system, and otherwise the mess it produces. However, even if I had experienced none of those, the whole automatic updates whether-you-like-it-or-not... is one of the reasons why I'm not using windows or macOS.
The biggest pay-off for OpenSnitch is if you're going to be installing and using third-party programs like VSCode and Unity, who love to talk to analytics providers.
Isn't that enough?
If you found that your next door neighbor was sneaking into your house while you're away, and he said "oh I have an option not to do that. Just ask me not to any more." Would that be good enough? You say "ok I would like to invoke that option" and that's it, you happily go away on a month long vacation without installing any cameras or anything because they guy said he won't do that now.
That's a single package, whose setting affects no other apps, and you have to trust that the app even really does what it says, which makes no sense when the topic is apps that may be doing unwanted things behind your back.
Taking that further, you can ditch your Mac and switch to Linux or BSD if you're concerned about the article subject. In other words, you can sell your house and move if you don't like the direction the neighborhood is going with all the peeping toms about, but there's extra work involved in that solution so you have to decide if you can afford such a change for more privacy. So, you can sell your Mac and move your workflow to a less invasive OS on hardware you choose, but depending on how deep your workflow is intertwined with and relies upon the macOS ecosystem, that can be a ton of work as well.
The ideal solution seems to be to VPN off my home internet connection, but that just feels so broken...
I've thankfully only lost VPN access a handful of times since installing it because our internet is relatively stable.
Not sure why are a singling out Apple here. Windows is worse as are many (most?) hardware vendors; there is a reason everyone REALLY should fresh install vanilla Windows over the vendors OEM version.
There are about 30 Apple processes to which you need to deny all network access. Then a Mac is relatively quiet. (By default Apple stuff is whitelisted in Little Snitch, you have to go and manually uncheck built-in allow rules.)
Apple built something called the ContentFilterExclusionList that bypassed Little Snitch and VPNs for Apple apps, which was thankfully disabled rapidly (and without an announcement) after a big backlash. Hopefully it will not resurface.
If it does it will still be possible to alter the system boot security level setting and tamper with the signed system volume (and modify the exclusion plist) and the system will still work (and so will the firewall), but it will take some hacking. This (and the work by marcan and the Asahi team) is the sole reason why I just dropped eight large on that chonky mac mini with the twenty cores.
The escape hatch remains. For now. (You still can't buy them anonymously.)
.single .entry-content:before { pointer-events: none; }
edit: I see that you are probably referring to the z-index of the ::before element overlapping the text, preventing selection.
~/Library/Trial/v6/AssetStore/assets/82/623873afd8fba430d4f4a45e/content/dialog/SocialConversation.catfamily/dalAprilFoolsSiri.cat
category: Social
description: For when users say 'April fools' to Siri without any other words.
listenafterspeaking: false
readyforloc: true
subcategory: Daily Rituals
It's April 2nd. April Fools! <break time="300ms"/> If you want to play some tricks of your own, say, 'Tell me an April Fools prank.'Who does this computer belong to, the author or Apple, Inc. Let me guess, Apple controls the SSV and decides what files it contains. Removing crapware becomes exceedingly difficult. Brilliant.
The App Store is a joke.
All that said, it’s still currently way better than other big tech - but I am not blindly accepting their behaviour, for now its good enough for me but that can change in the future
From what we can tell, This here is not a trial connected to revenue. It’s connected to Siri and other ML-frameworks, but not to, say, the Apple Store or Music applications.
Mark my words in two or three years Apple will ban developers from using third party A/B testing frameworks and require them to use the Apple-provided solution based on triald.
The alternative to A/B testing in UX design is not some more rigorous trial with fully-informed consent. Instead, it‘s the older and still predominant mechanism of “let’s just change it”.
Consent in medical tests is important because it involves a ‘B’ that is a substance or procedure that has not (yet) been shown to be safe & effective. The trial is less restrictive than the alternative scenario, where it would be illegal to just treat you with ‘B’.
None of that applies: both the A and B in A/B tests are software versions, for which there are zero legal requirements. Neither version will have an impact on your health or kill you, which cannot always be said for untested pharmaceuticals. A tailor is absolutely free to suggest dark navy to one customer and anthracite to the next, even if they flip a coin to decide and/or mentally take note of what customers like.
The possible harm from A/B testing is the maximum of the harms of A and B. If you wouldn’t complain about either alternative, there is no legitimate reason to complain about the combined A/B harm.
> None of that applies: both the A and B in A/B tests are software versions, for which there are zero legal requirements.
There should be, that is my point.
All that A/B testing and the constant other changes even in minor patch versions only lead to update hesitancy in people, which in turn leads to security issues because people don't update their software because they don't want to be disrupted in their workflows.
Not to mention that most A/B testing is essentially pseudoscience at best if not outright fraud that's being peddled by people wanting to sell A/B testing "solutions", or the implications on user privacy because of the mandatory phone-home.
FWIW this is what made Microsoft so big in the corporate world: for decades you could expect that nothing major would change, you would not need to re-train your employees or buy new software. That changed with Windows XP (although it was easy to roll back at least the optical changes) and got exponentially worse with the utter crap that is Windows 11.
If I pay for a product, I expect to be treated with respect. Being turned into a guinea pig to save on feedback cost isn't being respectful. Doing so without notice or consent is even worse.
There's no law against it, of course, but that doesn't mean it's good or even okay.
If it in anyway restricts bandwidth or causes other harms, eg uses up the last of your HDD space causing an issue, then that's an additional crime according to UK law.
These laws shouldn't just be applied to individuals.
Users, particularly those who paid thousands of dollars for the hardware, are not guinea pigs.
Citation needed, Apple have an advertising identifier built into the os to help advertisers track you, they share analytics about how you use their os by default, they analyse the data you store with them in iCloud.
I know Google, Microsoft, Amazon they all do these anti-user things thats not my point, my point is that Apple say they have a strong track record of standing up for their users and their users believe them regardless of their track record.
And some of the differentiation that IS being done is not A/B testing in the usual sense of the word. i.e. if one particular hardware model needs a different version of an asset, those models can be assigned to a separate set, but that does not really make it an A/B test.
Ok, seriously, y’all need to tone it down with the speculation. Spotting the word “trial” and immediately jumping to the worst conclusion is dumb and how misinformation spreads. As some commenters have mentioned below, triald manages CloudKit asset packs for Siri to allow it to change its local behavior independent of an OS update. That’s all it is. I don’t really have a problem with “oh let’s poke into this thing on my computer and figure out what it does” but I am kind of sick of just looking at log entries and coming to a misleading conclusion without really understanding what’s going on behind the hood. Yeah, it uses space on your disk and Apple could describe what it is better, but it’s not secret spyware or a plot to fill up your disk for no reason.
(Fun fact: a lot of the assets in the ~/Library/Trial directory are transparently compressed at the filesystem level using a new “LZBITMAP” compressor type in macOS Monterey. Without this it would take more space, so they are definitely aware of the disk usage at Apple.)
Right now, anything that can affect running systems from the outside has to be viewed as an attack vector. It would be a good idea for anyone running anything critical or semi-critical to turn off all remote updates for a few months.