On my keyboard, 1 is upper case &, and 4 is upper case apostrophe, while $ is lower case £ and ! is lower case §... (But it also has a dedicated key for a letter that is used in only one word... ù, used only in où.)
And there's no dead-char for acute accent, caps-lock does a shift-lock on Windows (but an actual caps-lock on most Linux) (the combination of these two problems means you need alt-codes to type the letter É), and most unforgivable of all†, full-stop is shift-semicolon. Because people clearly use semicolons more often than they do sentences without one. Clearly.
†according to a friend who'll recognize himself, but I agree with him.
It's debatable. Both square bracket sides, both brace sides, the backslash, the pipe, and the # character require AltGr instead of being plain or shifted. When programming in C and C++ (and any other brace-block language), that's an annoyance.
And the shift-lock versus caps-lock thing is the same on FreeBSD/Xorg as it is on Linux/Xorg, and complicated by the fact that on keyboards that have words or word fragments on these keys, the key is, indeed, Caps Lock, "Verr Maj" ("Verr" from verrouiller, to lock, and "Maj" from majuscules, capital letters). But then again, the key marked "Shift" on QWERTY keyboards is marked "Maj" = Caps on AZERTY ones, so it's really Shift Lock.
Whoever was responsible for this needs to be ... chastised. I recommend strapping him to that rather battered wall over there, and I'll turn on this switch. Oh, that thing with the tubes? Don't worry, it won't hurt for very long...
@anotherusername Actually depends on the definition of look. I prefer the overall looks of Windows 8/10 to Windows 7. Start menu/screen is a pile of shit, though, both for looks and usability. And FastBoot can go jump off a cliff for being a massive waste only designed to make Windows look better in startup times by being filled with fakery and badness.
@hungrier I've only ever purchased 3ds games legitimately, though I do have a Supercard that can be used to play my old DS games and emulate SNES, and that thing has worked for years - which is a must have if you haven't played Ouendan 2
Then again, I might still be experiencing the glow of nostalgia that can only happen after consuming two bottles of 45 year old wine with good friends.
Edit: is this archaeological evidence for early forms of Linux hardware?
You see, the Unix was designed to run within the VHF to UHF spectra (much like a radio), which is all well and good until you consider that modern computers run in the microwave range, at which regular radio reception starts to have serious issues. If one were to use a UHF receiver to tune in to a quad-phased broadcast in the Microwave spectra, one would fail miserably.
I would wager a bet that Ed Bott's computing apparatus was a more contemporary design utilizing a 3GHz central processor unit (or CPU). Under such frequencies, the linux would literally tear itself apart, its code lacking the internal cohesion to sustain this extreme environment. The Microsoft by comparison, is streamlined and engineered to withstand this Microwave environment, thanks no doubt to the forethought of its designers.
And of this there is ample evidence, which one can easily do an msn-search for and witness first hand. All of this evidence is on the public record, and cannot be denied.
So I wonder if this is related. Slightly obfuscated headers:
Received: by 10.237.35.134 with SMTP id j6csp298537qtc;
Fri, 10 Mar 2017 19:15:49 -0800 (PST)
X-Received: by 10.36.116.71 with SMTP id o68mr2186451itc.60.1489202149379;
Fri, 10 Mar 2017 19:15:49 -0800 (PST)
Received: from o3.email.fitbit.com (o3.email.fitbit.com. [220.127.116.11])
by mx.google.com with ESMTPS id n17si4881489ioo.93.2017.03.10.19.15.49
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 10 Mar 2017 19:15:49 -0800 (PST)
Received-SPF: pass (google.com: domain of firstname.lastname@example.org designates 18.104.22.168 as permitted sender) client-ip=22.214.171.124;
spf=pass (google.com: domain of email@example.com designates 126.96.36.199 as permitted sender) firstname.lastname@example.org;
dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=fitbit.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=email.fitbit.com; h=content-type:from:mime-version:subject:to; s=smtpapi; bh=JZGDDEO/Undb5/+1j5ZTxZXsZkg=; b=Z6k7W8mQTezxozuHMn 8XIfOMFaAX8HPSgeCBXKU4WSKMBot18KtEUQ600luP+9l9z7HpzjjhNXnfFqK8E4 zJl7kQONpR60iyWDb93EB22ScW6Hod6+cHLktLPmu22SUknz6siTSNJZ/g39yjJ0 koW8jflRl2l6qhkiSZbDPCV+U=
Received: by filter0095p1las1.sendgrid.net with SMTP id filter0095p1las1-28240-58C36BE4-2B
2017-03-11 03:15:48.697038119 +0000 UTC
Received: from MzA5ODM (a9.fe.a86c.ip4.static.sl-reverse.com [188.8.131.52]) by ismtpd0003p1sjc2.sendgrid.net (SG) with HTTP id kvQoaZxqSwa3J4Nfkszj1A for <email@example.com>; Sat, 11 Mar 2017 03:15:48.614 +0000 (UTC)
Content-Type: multipart/alternative; boundary=df361e6fe995c360110e912270822f72ec03d6ad5daef043ada01bc7a5dc
Date: Sat, 11 Mar 2017 03:15:48 +0000
From: "http://rayban.ddnsking.com/" <firstname.lastname@example.org>
Subject: [Fitbit] http://rayban.ddnsking.com/ vous a invité(e) à rejoindre le groupe · sur Fitbit
X-SG-EID: KZiMIh2ZtZI8pNnCAUheF4ufE1zf707K3b/RphfOAOnAwYs3W/gTu+RQPROGneL50+BhMEopS2REbm 2/bF+Nf9PvQMoiu9MbboqrGqK6/AosANoXFlYWdftB9GEEYaeP/a2W7KyP614A7SYK1S/XekecRE+g 84tZ7bq0K0RyPEY9qMoPHt3WbgBectVPPnfs8JE4FOkxaCCzMDyeDZVf5zdpBbqCg0oNMqRbHO+xoB BkE5TOXAjMUW/I7B0EZpDR
Looks like their api key to sendgrid got leaked maybe?
This is not just regular spam. All the security checks passed and it went straight into my gmail inbox.
Also I guess they got my gearbest email somewhere.... Maybe gearbest was breached too?
Attach a mechanical device on your limbs that generated energy by movement (and making movement slighty harder, but that's what you get). It seems too simple to be true. I'd like to know if there's any reason why we don't do that? (other than "people don't like exercise")
There's a kickstarter for it. I found it while looking at wind-up battery chargers (inspired by this conversation). I think I prefer the wind-up idea, personally.
Whether the data breach qualified for requiring notification is a question for the lawyers to debate, but on its face I don't think so.
The passwords were not encrypted; they were hashed, and the law doesn't cover hashed data. What's more, encrypted data is only included under the scope when there is reason to suspect that the encryption key might have also been stolen. Since there is no key for hashed data, it can't meet this condition.
The personal information definition requires that both a username and a secret verification factor -- password, security question and answer -- must be stolen, which, together, are sufficient to grant a malicious actor access to the user's account. The data that was stolen consisted of user names in the clear, but the passwords were hashed, and using a presumably secure method.
The only plausible reason that it might have required notification was after they'd been informed that many of the accounts had insecure passwords which could be easily cracked from the hashes in the leaked databases. At that point they had reasonable evidence that both usernames and passwords to at least some of the accounts were available to malicious actors. But the law doesn't appear to require them to automatically assume that securely-hashed passwords would be cracked if they're part of the data leak.
The results presented so far on SHA-1 do not call its security into question.
However, due to advances in technology, NIST plans to phase out of SHA-1 in favor of
the larger and stronger hash functions (SHA-224, SHA-256, SHA-384 and SHA-512) by
I don't know if it was an "official deprecation" but planning to phase it out counts as one to me.
@RaceProUK My money is on really crappy 2.4 GHz radio hardware. I had this exact issue with one of my thumb-sized bluetooth headsets. Worked great, so long as the phone was on the same side of the body it was in, but lose (effectively) lone of sight, and let the connectivity issues begin!
hmm.... i'm no physicist, but looking at the limitations of the controller it looks like..... yeah i think that's just bluetooth with a different hat on technology.
that means a total range of ~4-10 meters depending on whether the joycons are class 2 or 3. That frequency range has okay penetration of things like walls, but is significantly worse at penetrating water, of which we are largely comprised. Thus i can infer that the joycons need an indirect path from the controller to the device when occluded by the body, if this bounce path is longer than the effective range (which is probably about 10 meters, assuming they are a class 2 bluetooth-esque device) you'll have issues with connection.
If this is the case smaller rooms will have less issues with the controller desync than larger rooms as the smaller room minimizes the bounce path length when the controller can't use the direct link. Also trying to avoid occluding the controller with your body would be a good thing.
If nintendo put a class 3 chip in there instead of a class 2 chip they might be able to fix the issue with a firmware update to increase the transmit power of the joycons. That will of course reduce the battery life, but the tradeoff may be worth it if the wireless communications chip is capable of actually controlling the output wattage in firmware (changing from 1mW class 3 output to class two 2.5mW output), though the odds of that are..... maybe 30%. If they can't do that the only way to fix the issue would be a hardware update to increase the available transmit power.
Nota Bene: this is all conjecture based on the publically available specs for the Nintendo Switch and the observed behavior in the handful of videos describing the issue i watched. I am not a lawyer. I am not a rocket scientist. I am not associated with Nintendo in any way. I do not own a Switch. I don't plan on purchasing one until later in the lifecycle when another round of games come out (if i even do purchase) all rights reserved. this post is offered without warranty, and is not indicated as being fit for any purpose. Use at your own Discretion. Exercise caution. Your Mileage May Vary.
some kind of sanity check for a tab's memory usage
By far the easiest way to do this is using processes. Tracking memory allocated to a tab (or, more generally, any complex task) when you've potentially got multiple threads working within the tab is distinctly difficult, especially if you don't want to add vast amounts of management metadata overhead.
This. Except, a smartphone can't control the AC or measure the wheel pressure or have access to a dedicated GPS antenna on the roof*. But car makers could provide access to all that to your phone with an USB connector and a standard protocol.
I was once working on a project that communicated through an OBDII adapter for that, actually. Except I never got very far due to lack of hardware that the car manufacturer wouldn't ever attempt to hook into my system to let it work.