It absolutely is.
It's possibly also how they'll get broken up by the DoJ.
I'd email it as an attachment.
In Australia the local post office has fax facilities.
My semi-immutable OS is based around a Debian installation where every application is installed in a separate Docker container.
When you launch the application, it volume mounts an appropriate directory that contains only the data related to that application.
Chrome for example launches with a single subdirectory inside ~/Downloads, so each instance can only see its own directory.
I can also test compilation of random repositories inside a container, without affecting the underlying OS.
The OS itself has only got a minimal Debian and Docker installed.
Been using it for several years. I can't recall when I last rebooted it.
You mean, a messaging app offered by Meta isn't secure? I'm shocked, I say, shocked!
Anyway..
Manufacturer warranty?
Yeah. I can just picture it. Survivalists doing an appendectomy in their barn using a pocket knife and some whisky..
Seriously, if the shit properly hits the fan, there's no "survival" scenario, it's extinction and homo-erectus goes the way of the dinosaurs.
Anything less than that means the rich get richer and the poor die.
Why?
It's a serious question. What features are you missing, what do you dislike, etc.
Otherwise the answer might easily be: search for "NFC payment" in Google Play and that's not helpful.
Uh, the text goes on to say:
"including its immediate and permanent removal, without prejudice to law enforcement and user appeals requirements"
In other words, if law enforcement asks you to take it down, you will. That does not appear to have occurred here.
Nom Nom Nom?
In reality this happens all the time. When you develop a codebase it's based on your understanding of the problem. Over time you gain new insights into the environment in which that problem exists and you reach a point where you are bending over backwards to implement a fix when you decide to start again.
It's tricky because if you start too early with the rewrite, you don't have a full understanding, start too late and you don't have enough arms and legs to satisfy the customers who are wanting bugs fixed in the current system while you are building the next one.
.. or you hire a new person who knows everything and wants to rewrite it all in BASIC, or some other random language ..
vk6flab
joined 9 months ago
Perl is the only language that looks just as incomprehensible before and after a rot13 transformation.
Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.
And lisp is hard to say if you have one.
Edit: aa -> after a