That doesn't rule out "dark matter having other interactions which do not interfere with our detectors" Dark sector theories which include other dark particles or new particle interactions are not controversial amongst cosmologists in this space. For example there's a whole area of study around "dark photons" which would mix with our photons and interact with dark matter.
> If someone offered a whole team of devs in India for an unknown number of months basically for free, one would be a fool to turn that down even knowing it wouldn't last forever. Claude etc feels like the same kinda deal.
I've made a lot of money fixing software where people paid for those offshore teams and they would have been better off having not done that and writing maintainable software from the start. They were fools paying for it and they still would have been fools if it had been free.
Sure, I've been part of "in-sourcing" failing projects too, but it was always a sign of management incompetence rather than anything else. It's easy to shift the blame to an outsourcer when it's been GIGO; constantly changing requirements, feature creep, no budget for maintenance, the usual stuff that kills codebases.
The paper claims directly "the rate of degradation over time remains unsatisfactorily unpredictable" but you are claiming the authors do not understand or are unaware of the point you are making?
I think what I explained is known by anyone in solar physics. I cannot believe they would not have discussed it. It's absence in the paper is weird. But I think unpredictable refers more to LEO in the context of the paper where things are indeed more dynamic that just the 11 year periodicity of cosmic rays from solar activity causing scattering in the heliosphere.
> The GPL doesn’t require them to provide the sources to the world;
I don't see how this is relevant. The people making the request are within those boundaries. The rest is moot. The spirit of the GPL is that graphene is entitled to the GPLd source in some way and google must reasonably comply.
There might be some legal nuance here. What binaries does Google distribute and does Google provide sources of those? (I assume pixel updates count, is that pure AOSP?) Does grapheneOS request sources for beta tags that are not distributed yet in binary form?
Don't get me wrong, I still think this is shitty behavior from Google.
Chromium being open source is not a mistake. Letting google be the sole driver and not forking it has been. People who want control over their browsers have options. It's a fight because most people don't care about these things.
They have control over what they distribute. Chromium and Firefox are both open source and people can (and should) use derivatives they find acceptable.
reply