6,694 karma · joined November 6, 2020
> Full coverage for deposits for payment and settlement purposes, bearing no interest, being redeemable on demand, and providing normally required payment and settlement services
IIRC, bunq in the Netherlands issues Mastercard "credit cards" (with no "debit" annotation as on true Mastercard debit cards). They're treated as credit cards for Mastercard purposes but are backed by deposits.
For "bytes" as the term-of-art itself? Probably not. For "codes" or "words"? 5 bits are the standard in Baudot transmission (in teletype though). 6- and 7-bit words were the standards of the day for very old computers (ASCII is in itself a 7-bit code), especially on DEC-produced ones (https://rabbit.eng.miami.edu/info/decchars.html).
I'm pretty sure this is actually Google's fault (even Sony televisions suffer from this bullcrap). Unlike phone Android, Google TV (yes, that's the official name now) enforces certain "standards", one of them is this bullcrap.
> I wonder how much polarization affects things; I was once told that terrestrial FM Radio is transmitted with vertical polarization to reduce interference from tall objects between you and the transmitter.
> Terrestrial TV (some of which used bands that overlap FM radio) uses horizontal polarization.
This is only true in the US (and probably areas influenced by US standards). In Europe, FM radio transmissions (and digital television nowadays) tend to be mixed-polarization (circular polarization), except if there are known interference (usually border areas) that would preclude mixed-polarization.
Analog television meanwhile significantly differs depending on your area, which required you to either test which tower and polarity is the best (note that all broadcasts are transmitted at a single tower, unlike in the US), or just... request a map with that data.
Just verify modern OSes now, they definitely do mediate via systemd-resolver (including in server OSes).
[1] Not IPv6 on mobile devices but a fully-owned IPv6 range that is supposed to be the address for a device regardless of where it is, see RFC 3775
This is technically incorrect, because Windows now includes SSH too!
Messing with what is supposed to be a carrier standard, as I already think what is happening, puts Google to (in my opinion) a legally unreasonable position in some countries, and I won't be shocked it it will be treated as a carrier with licenses et al. (or rather, lack of licenses, which is just plain bad for Google). I won't be surprised if it turned out that many Googlers already knew that this is a bad idea legal-wise, but the higher-ups have approved this shoehorning.
Outside of China, it is de facto a Google thing due to Jibe not really in mood to interconnect with others, plus the fact that Google actually shoehorns RCS in countries where they think they can get away with it. Your statement "iPhone depends on the provider so has less coverage" basically bares this one. Two example:
1. Japan has already a different provider-supported thing +Message, (RCS-based but a different flavor because RCS is complicated), but Google is trying to win to them (and if I remember correctly, au actually jumped ship to Jibe recently-ish).
2. African carriers were confused because of RCS shoehorning without the carrier's consent: SMS reliably actually decreased because Google assumes that once you got an Android phone, surely you won't temporarily use that SIM on a "basic" phone for just an hour or two, right? Google just assumes that's offline, but for people still using their Android devices to reach their family on a farm who temporarily switched to a basic phone for its reliability and reach, their messages will still be send solely via RCS (which predictably won't reach the intended recipient because, of course, it does not have RCS).
Apple of course has its incentive to keep its users on iMessage, but it now accepts RCS (whether Jibe or not) and being "patchy" means that there are many, many carriers which did not implement RCS on their volition. I just imagine how would Google handle an oppressive government's request for interception on Jibe after carriers demonstrably shown that RCS was implemented without their consent, with fines and possibly prison sentences for illegally operating a carrier service to boot.
(Yes, there are other recursive resolver implementations, but they look at BIND as the reference implementation and absent any contravention to the RFC or intentional design-level decisions, they would follow BIND's mechanism.)
I would hazard a guess that their test environment have both the systemd variant and the Unbound variants (Unbound technically does not arrange them, but instead reconstructs it according to RFC "CNAME restart" logic because it is a recursive resolver in itself), but not just plain directly-piped resolv.conf (Presumably because who would run that in this day and age. This is sadly just a half-joke, because only a few people would fall on this category.)
1) How to secure routing information: some says RPKI, some argues that's not enough and are experimenting with something like SCION (https://docs.scion.org/en/latest/)
2) Principal-Agent problem: jabber.ru's hijack relied on (presumably) Hetzner being forced to do it by German law agents based on the powers provided under the German Telecommunications Act (TKG)
GDK is open-source (https://github.com/microsoft/gdk), but to be fair there is a possibility that there are some parts under NDA.
Honestly, the weird 16-239 (on 8-bit) color range and 60000/1001 fps limitations stem from the original NTSC standard, which considering both the Japanese NTSC adaptation and European standards do not have is rather frustating nowadays. Both the HDVS and HD-MAC standards define it in precise ways (exactly 60 fps for HDVS and 0-255 color range for HD-MAC*) but America being America...
* I know that HD-MAC is analog(ue), but it has an explicit digital step for transmission and it uses the whole 8 bits for the conversion!
... okay, technically PAL and SECAM too, but only in audio (analogue Zweikanalton versus digital NICAM), bandwidth placement (channel plan and relative placement of audio and video signals, and, uhm, teletext) and, uhm, teletext standard (French Antiope versus Britain's Teletext and Fastext).
It is necessary that it was precisely defined because of the requirements of backwards-compatible color transmission (YIQ is the common abbreviation for the NTSC color space, I being ~reddish and Q being ~blueish), basically they treated B&W (technically monochrome) pictures like how B&W film and videotubes treated them: great in green, average in red, and poorly in blue.
A bit unrelated: pre-color transition, the makeups used are actually slightly greenish too (which appears nicely in monochrome).
It doesn't really matter that a single person has found a loophole because many, many other people don't have such a luxury, and that's what the lawmakers are aiming for.
To be really fair, on Windows:
- H.264 is the only guaranteed (modern-ish) video codec (HEVC, VP9, AV1 is not built-in unless the device manufacturer bothered to do it)
- JPEG, GIF, and PNG are the only guaranteed (widely-used) image codecs (HEIF, AVIF, and JXL is also not built-in)
- MP3 and AAC are the only guaranteed (modern-ish) audio codecs (Opus is another module)
... and all of them are widely used when Windows 7 was released (before the modern codecs) so probably modules are now the modern Windows Method™ for codecs.
Note on pre-8 HEVC support: the codec (when not on VLC or other software bundling their own codecs) is often on that CyberLink Bluray player, not a built-in one.
The correct answer here, rather disappointingly, is that they were never neutral. Google Videos (the one that Google actually launched) arguably is a neutral service, but YouTube was always designed to be a social media (even if that term is not as well-known at the time as it is now). It even had five star ratings, which as the style for its time. It is always closer to Instagram rather than Dropbox (although that's an anachronistic comparison since that YouTube was the first of the three).
For those who does not handle these things: I am not sure on what processor Network Time Foundation is using, but Stripe's $15 fee is actually on the low side of chargebacks (some processors even use the fixed fee + percentage model). Worse, this is unconditional: if you somehow won this, you won't get the chargeback fee.