Big if true.
@lemmy.ca
You've got the right idea with the permission change... the key is that you can have code executing on the remote side with different permissions. So the writer process has permission to write in one directory, and the turnsyle procees (often the root super-user) rotates the files or directories at a different time (or on a signal, sometimes).
So, like... a week ago? https://seekingalpha.com/...
Neat, but sounds like bad legal advice. Last time I looked it up, it said something like "possessing a firearm on or about one's person"... so it doesn't matter if it's attached to your dog or pulled behind you on a skateboard or held in mid-air using some kind of hovering drone... if it is near you and under your control, you have it.
IMO, the interesting case would be if the weapon is stored in your home (where nobody questions it may be), and you can summon it.
I seem to recall reading that, but I think you have the wrong impression. I'm pretty sure it's just there build system. They have always had two (one private for the paid stuff), and now they are just building everything "in private" not removing any source.
There are many projects that do not have open build systems, and I can understand them eanting to cut costs and simplify infrastructure.
e.g. just because redhat has a private build system and tries to restrict access to their binaries, that does not make them closed-source.
thanks for using Leebra!
go to feed...