But it would be pretty well in line with the "I trust my contact with this communication, but only if they're not systematically misled to copy it to readily exploitable insecure storage" line of thinking.
Since the purposes of the program are pretty heavy on private communication, I'm inclined to think that takes precedence here, especially considering the consequences for dropping default message previews versus adding default reveal of supposedly private information.
They may be vastly overestimating how much military power lets them do whatever they want, but it's plenty for throwing one hideous narcissist vengeance tantrum when the frustration hits.
Most of the smashing up and disfiguration of a perfectly good interface, uglification, waste and breakage of both data and compatibility were introduced in a rewrite 2023 ostensibly aiming for "fresh" design and user interface work.
I'd heed the call for donation simply for returning to pre-2023 design with up-to-date security patches. As it is, maybe it's merciful if development just comes to a standstill. Almost every visible step lately seems to move in the wrong direction.
Booking a flight is the kind of thing I'd really want to avoid doing myself nowadays if possible though. Surveying the offers is usually such a snake pit of deceptive marketing and incomplete service conditions that I feel somewhat nauseous just at the prospect of having to look at it.
I wouldn't remotely trust a software assistant to deal with all that misdirection autonomously, but I guess I'd be prepared to give it a chance collating options with tolerable time and cost, attempting to make the price include the stuff that has to be added to preserve health, sanity and a modicum of human dignity.
Asking it to find the best deal? Sure, I could totally see that. But I want to double check that myself and actually buy it in order to make sure my flight to Denver from Portland doesn't have a layover in Anchorage or something.
> If I were to run this on a Mac SSD, 24/7 for heavy usage such as Openclaw, that is going to significantly reduce the lifetime of the SSD.
How sure are you about that? I've never looked closer at how a large LLM with mixture of experts architecture switches between expert modules, but staying on roughly the same topic for the use (as it often would when editing the same codebase), I wouldn't be surprised to see the switches of composition are fairly rare, fairly small, and to the extent it happens it's repeated reads from the flash disk rather than writes it tends to cause.
Afaik the experts are not usually very interpretable, and generally would be surprised if at least one does not change every token. I don't know what happens in practice, but I know at least during training, nothing is done to minimize the number of expert switches between tokens.
I'd have thought at least a tiny explicit penalty term for switching, to discourage messing around with the composition without any expected gains from it.
If one is to use these on hardware that can't keep everything loaded I guess someone should examine how it works out in practice. Interpretability may be be a too much to ask, but I can't spontaneously see any reason why the experts can't at least be pushed to incorporate what's needed to remain the good choice for a longer segment.
The switching is done by layer, not just per token. Every layer is loading completely different parameters, you don't really benefit from continuity. You're generally better off shifting this work to the CPU, since CPU RAM is more abundant than the GPU's VRAM hence it matters less that so much of it is "wasted" on inactive expert layers. Disk storage is even more relatively abundant, so offloading experts to disk if you can't keep them in RAM (as OP does) is the next step.
I just also want to toss in that (at least for Element in particular) the continuing lack of long-form composition or history navigation appears to be a liability with some contacts.
At this point it's probably fine for chat format one-liners in the moment, but for the communications that have historically been going over e-mail as opposed to IRC it's something of a pain to use.
Basically a good point.
Merely never ending up in situations where it's a struggle to make ends meet has a huge impact on stress though.
You often don't even have to use the wealth in order to benefit with respect to stress.
That only really holds if reporting on the manipulation bets is not turned into effective propaganda for skewing events towards the manipulation outcome.
So the main argument of the article holds IMO.
Edited to add: I'd like to rephrase that a bit actually. It doesn't even have to help bring about the particular outcome being bet on. It's enough that it can be used to shift public opinion in some way that's worth the cost to the manipulator.
Sure, but events where that kind of "skew" is effective are going to be quite rare. And even then, the incentive is just for everyone to try and "skew" the event as early as possible, where factors other than monetary cost or reward then become dominant. No different from what usually happens with no prediction market at all.
> It's enough that it can be used to shift public opinion in some way that's worth the cost to the manipulator.
This has been tried in the real world and is just not very effective. It's just too hard to move the price in ways that will shift public opinion when literally anyone else has a huge incentive to bet against you.
Since the purposes of the program are pretty heavy on private communication, I'm inclined to think that takes precedence here, especially considering the consequences for dropping default message previews versus adding default reveal of supposedly private information.
reply