Re: The problem with nuclear summed up in one throwaway phrase .....
If the Cro-Magnons had built nuclear power stations
then 12,000 years of technological evolution would have solved this a LONG time ago...
10282 publicly visible posts • joined 1 May 2015
I would not call that a LOW bar. Ask an average 15 year old educated in California to express his current physical or emotional state using a simile or a metaphor, and the LACK of response might surprise you.
Or not.
What we would call "basic language skills" seem to be LACKING. Schools used to teach people to express themselves in writing. I'm not sure WHAT they teach in these schools, these days...
I guess that wraps back to the "mime-like warning signs" "picture only instructions" and use of emoticons by physicians instead of the usual "show me where it hurts" or "let's have a look at it, then".
"My Brain Hurts"
or as a simile "It's like someone inside is jack-hammering his way out through my skull"
or as a metaphor "It's PURE HELL in my HEAD"
(where's the "My Brain Hurts" emoticon? It probably looks like Michael Palin)
Japan switched to using phonetic alphabets long ago, yet kept a subset of the Chinese characters (kanji) because they have a LOT of homonyms in the language and chinese characters probably disambiguate things well enough to keep using them (either that or tradition). But it DOES take a good part of Japanese and Chinese schooling JUST to learn to read and write. And everyone I've ever seen reading any significant amount Chinese writing (like a book) has to carry a dictionary and refer to it often.
This is why nearly EVERY language uses a phonetic alphabet. It just makes more sense. Humans generally communicate vocally. And our writing reflects that.
(and emoticons are NOT CUTE - they are MOSTLY NAUSEATING unless explicitly used for humor)
Icon, because there's not actually a VOMIT icon.
Without having REAL daily enemies to slay, just to stay alive, it seems that an IDIOCRACY filled with compliant sheeple of lower average intelligence (and tyrannical "leaders" of even LOWER intelligence) may be INEVITABLE... (no need to be smart and/or clever just to survive)
If I must use an emoticon, see icon (that, or the middle finger)
I suppose it is to be expected if you want to use a BLOB/TEXT column to store JSON, or maybe XML, or any other "does not really require a schema" thing. OK I've seen schemas for XML but just about every time I use XML data it's treated as free-form.
(I would have chosen XML though, as I do not like parsing nor creating JSON and for various reasons [such as 'embedded'] I usually end up rolling my own)
In any case they SHOULD support as many formats as possible, especially for extended properties for things inside the table.
/me wonders if the SQL can select on it directly - all records without a "fubar" property or "where 'foo'='bar'" [and those things are stored within the BLOB/TEXT as JSON or XML or something] or maybe you need their special tools to assist...
i should create a special e-mail address just for them...
"Up.Yours.Porker at example.com" (whatever my domain is subbed in for 'example.com') although the DMV already _does_ have my regular e-mail address from when I renewed driver's license and car registration online...
claim "4th ammendment" and "5th ammendment" to the rest of 'em.
(YMMV in the UK or elsewhere in the world)
here's some snark to go with that
* you apply for a job requiring high intelligence and technical skills HR has no clue about
* your application/CV/resume is scanned and filtered by AVERAGE intelligence (I am being kind) individuals with NO knowledge of the job or its REAL requirements
* hiring manager gets list of resumes with irrelevant experience, recent graduation from college, and "bolloxed up with BS" buzzword lists at the top of the page
And you're not "on the list". So to get through you do what recruiters do, find the hiring manager's name and sneak your custom-written CV/resume in directly to that manager, by snail mail. Still far from 100% but it has a MUCH better chance of working than going through H.R.
This whole scenario reminds me too much of the infamous drowned rat experiments from the 1950s.
* rats were drowned in buckets of water. Wild rats did not live long, several tame/domesticated ones lasted for quite a while
* At the point of dying, in a subsequent experiment, several wild rats were rescued, allowed to rest, got dried off, etc. and were THEN put back.
* The rescued rats lasted WAY longer (a separate source suggested DAYS vs MINUTES)
(I'll leave any conclusions open-ended)
Samantha could have been someone eventually.
How about the basis of AI for actual robots? 'Nandroids' perhaps?
"Sorry, not in MY sandbox" they say - and why is that exactly (when you dig deep down enough)?
"THAT toy MUST be played with the way I tell you or I'm taking it away" - another possible snarky comment to illustrate a point...
without freedom, there is no more innovation.
if Linux is (or can be) affected, are there MORE DETAILS on this?
I am mostly curious how it got there, but I suspect that my Fail2Ban logs would indicate a likely source.
(since 4:00 AM this morning, i.e. about 5 hours, there were 11 attempts on ssh blocked by Fail2Ban)
I will gladly forward this information someplace if it will help stop it. Unfortunately sending complaints takes time. if I could (easiiy) automate the complaint process I'd probably do that, too. I bet that most of the victims' IP addresses are infected Linux machines trying to crack in via ssh.
(my 'root' mail gets re-directed to an IMAP directory that I can view and clean up whenever i want/need, so it might be trivial to write a Perl script to deconstruct the reports and figure out who to complain and forward info to; however de-ciphering the correct complaint mail address could be tricky)
Specifically, a SQL server database is permanently locked by the server so how would thieves encrypt it without bringing the server down immediately.
It could be done by first dumping all of the data into an encrypted file, THEN issuing "DROP TABLE" and other commands on the actual database. Restoring would do "CREATE TABLE" and "INSERT" commands (hopefully along with indexes and stored procedures and so forth)
accountants probably edit (or at least copy to) files on a share. Then, malware ANYWHERE on the network that has write access to that share can pooch it.
A Linux server could make and store backups of the share using a cron job and store them where windows machines cannot (easily, or even remotely easily) access it. THEN, you restore the latest backup after you clean the malware off of the various computers, and go from there.
And proper directory-level and file-level security would help to keep EVERY windows computer from having write access to those shares.
it is naive to believe Linux makes you safe.
When you apply the correct security-related thinking to setting up a Linux server, it's pretty frickin' solid as far as security goes.
SO yes, and no. YES it is naive, so you need to hire a Linux admin (or consultant) who knows what he's doing, and then you should be as prepared as you can be for any kind of malware storm
Uber-security might involve putting the server and data into a VM, and then have the host machine buttoned up tighter than a bullfrog's behind (and host the recent backups, with offsite storage for the older ones).
There are a LOT of things you can do with Linux (security-wise) that aren't so easy in the windows world, and they are VERY effective. But yeah, it cannot be set up by an IDIOT or you'll be pretty bad off when the storm hits.
By adopting Linux across the company.
At least some of us agree with you in principle, and enough evidence exists that the changeover WOULD save you money. Convincing every employee in a large company to switch to Linux desktops might be difficult.
HOWEVER, on the server end you'll have better luck. You could, for example, do automatic daily (compressed tarball) backups of a data share, with weeks' of history and frequent-enough offsite mirroring (so you can go back > a year if you have to) and at least protect important data assets THAT way. And unless the Linux machines were set up by an IDIOT, the likelihood that a windows malware application COULD affect the servers (aside from pooching data on shares) is SMALL.
(important note, non-SMB-shared directories will effectively be shielded against malware attacks from windows systems, assuming an IDIOT did not set up the servers)
Unfortunately someone may some day figure out how to crack Linux security, and the "inside job" is ALSO not protected against, at least not completely.
But with a good BOFH and properly configured LINUX or BSD servers, you'd have a MUCH better chance of weathering a malware storm. In My Bombastic Opinion of course.
You made me read that article.
In reference to various security concerns, It DID say this: Two months later, in June, it pulled the whole thing: the LSE software is no longer included in new laptops.
just thought I'd point that out. So unsurprisingly, Superfish AND this LSE thing suggest Lenovo has TRIED the potential backdoor thing before, got caught, and reversed their policies.
So is there any proof they're doing it AGAIN, NOW?
proof please. "sauce" please.
If UEFI has spyware in it, prove it please. I'm not saying you're wrong, I'm saying that you need to prove things of this nature if you are going to make a claim like this, Because if the allegations ARE true, it has wide sweeping implications.
not saying CCP does not WANT this. But other stories about China manufacturing and malware-on-board have been made before WITHOUT any conclusive substantiating evidence, right Bloomberg? Still waiting for the proof... (and their credibility has been damaged)
I did a rebase once. It was stressful. I think I triple-checked every command. Had no choice. I was working on an automated e-mailer shell script [sends analysis files from an SQL database within a zip file attached to an automated e-mail to several people via a crontab entry using shell and Perl] and forgot to sanitize the script first. Ooops. The script, I must say, is brilliant. My mistake unfortunately ruined my moment of triumph.
As many of us probably already know, ALL git history is available for anyone with access to the repo. So if you accidentally commit something you should not, a key, a token, a pass phrase, peoples e-mail addresses, whatever it might be, if you do NOT rebase to a point before that commit, it will be visible FOREVER, even if you do a subsequent edit to remove it.
(So at least the option to do a 'rebase' was there to fix it)
what makes git tricky to understand is its choice of nomenclature
true. I had to re-train my thinking a bit to familiarize myself with that the @#$% they actually MEANT by "that" (whatever 'that' is for the current context). It did not take long before I "got it".
I've used P4, cvs, svn, and git. I prefer svn for my own things, but git's ok for public and work-related projects. I've also (*cough*) experienced "Source Safe" back in the day and I *ahem* "perceive myself to have been involuntarily violated and become dirty" because of it...
the git command-line interface is... not exactly easy to learn.
I dispute the accuracy of your opinion. example follows...
From the article: you should never ever use the github interfaces to merge anything
When I read that part, I knew EXACTLY why Linus would say this. For a raw pull request (i.e. submitting your dev branch's differences from the official repo) the github inteface works very well. For actual editing and stuff, no.
Therefore you should just do all of your merges and any additional edits using a decent local merge tool (maybe 'meld'?) between your local working copy and the dev branch on github, after you do a 'git pull' on your local copy of the dev branch so you know that what you're comparing to for your merge is at least CLOSE to what you'll be doing the pull request for (assuming that no major edits in the official branch affect the pull request).
Then use 'git commit' followed by 'git push' to your dev branch, and then do the pull request.
You really only need to memorize and master a few git commands:
git status
git pull
git push
git commit
git add
git rm
the rest of the commands can be looked up in the docs "whenever", as needed.
NOT that hard. seriously NOT. But yeah you need a token. And I solved that.
If you search for it on github, I wrote a simple program that lets you use a pass phrase to decrypt an encrypted file and put its contents in the clipboard (for X11 systems though). In short, you would encrypt the github issued 'password' token in a file, and then run the utility from a command shell (say 'bash') and enter your pass phrase, and the github token will be on the clipboard. Then, when you do 'git push' and git prompts for user/pass, you type in the user and paste the token when it prompts for password. This is due to github's recent policy change regarding pass phrases and git command line, and the method I use can be put on computers you do not own (like customer machines) as needed to access github repos without revealing your token.
sounds like time for upgraded silicon. whoever makes the thing should probably design MAC randomization in and get it to market so that manufacturers will start using it. Ideally it would have the same footprint on the circuit board. They could even charge more money for it, calling it "security enhanced" or something.
(additional features might include lower quiescent operating current or better power-save)
if I operate a device (digital or otherwise) and it creates "an invention" (let's say a superior type of widget) I can still patent the invention, and I am its inventor. The device that made the invention is not the inventor. But the device's operator IS.
Basically, the AI guy screwed up the patent application by self-promoting his AI as "an inventor", probably to glean royalties from any 3rd party that uses it to invent things, later.
And, yes, space aliens WOULD easily qualify as 'Natural Persons'.
icon, because, facepalm for the AI guy that listed his AI as "an inventor"
You're lucky I'm not the President, because I would have the IRS take your taxes apart line by line
Do you REALLY want some government entity or individual to have the *KIND* of power that allows for CAPRICIOUS TYRANNY in the form of "weaponizing" a TAX AUTHORITY?
This does NOT pass the "shoe on the other foot" test, by a LONG margin.
Nope, it's a Democrat inquiry called by Pelosi to distract from her own failings
I'm not saying you're ENTIRELY wrong because we know that politicians do things _LIKE_ this a _LOT_ because they're politicians. However, I think the inquiry might actually be a GOOD thing, once the truth comes out.
A bunch of people allegedly trespassed and broke public property. They were "less than peaceful" which is NOT what Trump wanted to happen when he held his rally. It scared a bunch of politicians for a number of reasons, and they're busy hyping it all up for their own personal gain. This is what politicians _DO_ way too often. And, of course, their echo chamber media pals are enabling them because, if it bleeds, it leads.
So the REAL problem is the politicians. The people who trespassed and broke property need to be prosecuted accordingly. The only way to GET RID of evil politicians is to REPLACE them with DIFFERENT (hopefully not evil) politicians.
which COULD maybe be one of US, you know...
They have asked some companies to preserve records
Right. this is not the same as demanding the records and THEN "going fishing" to "find something". Subpoenas and warrants must be relevant AND specific to avoid violating things like the U.S. Constitution's 4th amendment.
(I do not like the way this is being treated BUT they [congress] haven't violated the law; however SOME people on Jan 6 WERE allegedly trespassing and damaging public property, so they SHOULD be brought to justice, within the confines of the law and constitutional rights)
U.S. Congress subpoena power is still "due process" and of course if there is overreach (like violating the 4th amendment to the U.S. Constitution) then a federal judge can intervene for any objections to discovery that is deemed a violation or simply "too broad". So it's still "due process" and not tyranny so long as you have the ability to object and the congressional investigation is overseen by the courts.
It becomes tyranny when due process no longer exists.
(IANAL so my legal advice/opinion is worth what you paid for it)
Yet, I think there is STILL value to leaving your phone off (with no battery) at times...
The questions that no one has asked those leaders are "who are they protecting?" and "why are they fighting this?"
I would like to see SIMILAR QUESTIONS asked about what happened in Milwaukee, Portland, Seattle, and other places from organizations like B.L.M. and ANTIFA. And I think the death toll from all of THAT was a *LOT* higher.
The laws were broken, and justice MUST be applied EQUALLY to ALL.
(and what happened on January 6 was a clear violation of the law, too)
Actually, "they" should know better than to anger programmers, many of whom are white-hat hackers, with a few grey hats as well. Github was (more or less) originally a place where people were FREE to put open source projects. Commercial-use support came afterwards, and I use it so it's a good thing.
HOWEVER, "angering the customer base" is a BAD thing. If I am right, and the people who originally *MADE* Github so popular are "Freedom Loving" hacker-types that *CRINGE* at even the *IDEA* of nanny-bots built into the service (and getting in the way of their FREEDOM), I think the results will be predictable.
from the article: The software also won't make suggestions if the user's code contains any of the stored slurs.
So that could be a back-door way of implementing an OFF switch, right? I'm assuming that would be in a context of a "you must use this" directive from a clueless boss.
I don't like "features" of this nature anyway. I type fast and don't need something correcting me while I type, nor GENERATING BAD CODE *FOR* me. I haven't used Copilot yet and so it may not be as IRRITATING as other "autocomplete" or so-called "intelligent" features of an IDE. Still, from the descriptions (and apparent history of generating INSECURE code according to the article) it's probably NOT something I'd use without coercion.
I'll just have to make sure to include a harmless (yet 'banned' word) in the header comments of each file. heh.
/* The liberal use of code comments by maintainers is encouraged */
your example is CLEARLY a reason why "profanity nanny" global "one size fits all" filters need to have LOCAL SETTINGS MANAGEMENT (including an "off" switch).
And maybe certain programmers should REALLY just become more tolerant and/or get a sense of humor. There are CERTAINLY more important things in the world of software development than ROBOT WORD POLICE. One of them was pointed out in the article, something about Copilot generating INSECURE CODE...
actually I would hope that during the negotiations they are GIVING a LOT of intelligence TO the police
(I would be MORE interested in NAILING THE PERPS than getting my data back, as anything truly important is being regularly backed up)
back in the early days of teh intarwebs only a relative handful of people, the vast majority of whom were NOT potential miscreants, could access other computers on teh intarwebs. So the *pressing* need for security was a *bit* less than it is now. (A *bit* being more like the comparison between dust and boulders, knowing that you really do not want dust to accumulate either).
Currently, only a relative handful of people have access to satellites via radio. Obvious comparison follows.