…just this guy, you know.
there was a mental word search, glitch in the matrix moment right at that point - read into that what you will, cuz these days all options are valid.
“insinuate” is absolutely the very best word, but publicly one has to walk the fine line between complicity and hair-on-fire alarm, and so “initiate” came out of her mouth.
for the record, I think we are past the face-melting stage.
from the video…
I think we need to be very cautious with the AI narrative where we are being lead to confuse mass surveillance with intelligence and by doing so initiate these corporate technologies into the core of our social and governmental institutions.
so voice typing, huh? not really sure it matters at this point. I use an open source keyboard, but my inputs go right into the OS of the worlds largest spy organization.
on the other hand… this is a great opportunity to hone your handwriting and memory skills.
termux is absolutely fantastic. if you like a nice, clean CLI then run (don’t walk) to f-droid and install.
understood. tinycore is a live installable distro, so you can still test it on bare metal.
pick the GUI flavor and kick the tires for a while.
the repos are browsable inside the package manager - I would imagine they are browsable outside as well, but I have never had cause to do so.
honestly, give tinycore a shot. fire it up in a VM and take a look around - it really is an amazingly useful distro.
if the install had finished and the installer was simply reading the flash drive to clean itself up, unmount filesystems and reboot, then chances are you are fine. However, as a personal rule I never allow an installation to go into production if there were any unexpected anomalies during installation. its just not worth the risk.
agreed on the batterygate thing. ars did a pretty decent writeup on the reasons behind the CPU throttling.
my issue with Apple has always been their… “its magic!” bullshit. that marketing leads to more and more e-waste as other manufacturers follow the sucessful Apple marketing trend, because, you know… its NOT actually magic and batteries are consumable items.
“Ford, how am I supposed to operate my [insanely expensive] digital watch now [that the battery is broken]?” guess i’ll just get another one!
The only way to circumvent this problem is to invent a battery that doesn’t age. The person who does that is going to be a _very _ rich dude.
or how about easily replacable batteries. yes, they can be designed in a sleek, apple-y ergonomic way. but its much easier and more profitable to make battery replacements a phone killing endeavour. this applies to other manufacturers as well.
and I realised I was seeing lemmy literally come alive!
thats a rather soul stirring realization put to words. :-)
pretty sure thats a goat. rugged, contrary and independent. one might even say… the Greatest Of All Time.
indeed! had I not posted this, I would be asking the same question!
so, its quite a bit more mundane than you might have hoped for.
a mix of…
the most recent page I opened was an archive.org page on TI-84 firmware disassembly.
I make heavy use of Firefox containers for separation. honestly, Firefox is an absolute workhorse for me. if the Firefox ecosystem were to fall into the void, I would be dead in the water.
frantic ignoring reddit sounds
dishing out the tools to help users take back control of their lIves. hero quality.
61 Firefox windows and 427 tabs (don’t judge, I know I have a problem) and I have no performance complaints - admittedly, not all of them are active/rendering simultaniously, but still…
Firefox (and its forks) have been my go-to for 15 years.
noscript is your web condom. I will not touch a page without it.
I am shocked there is even a single downvote on this comment. parent is 110% right. a kernel level compromise in the vast majority of exfiltration events its just needless (but nifty) icecream on top of the pain pie being served to the user.
well, I mean… anything can leak memory. but yeah, enterprise/carrier grade devices are designed to be in continuous use for years and they generally do that pretty well.
we are not talking about backend systems here.
we are talking about user devices in the wild, likely in an unknown state, with highly variable usage patterns by the user. someone with experience can usually determine how deeply to poke based on 30 seconds of questioning the user.
“reboot” is absolutely valid when the issue is trivial, non-recurring and the equipment is not sensitive. if a reboot destroys logs then the device was not important to you to begin with.
indeed, but your SSH ports should not be hanging out in the wind for any old IP to hit.