How would I Ctrl+F a video or watch it on a severely slow and/or capped Internet connection? And how would I watch without audio on my computer or with a hearing disability? Its captions have errors, such as a complete lack of punctuation and goofs like "until seventh generation core i7" when "Intel" was meant, due to having been automatically generated. Pending answers to these, I prefer text over video.
If the CSS loads all the desktop-version images, it's badly coded and/or the browser doesn't use the CSS properly.
What's the proper way using HTML and CSS to specify a separate image for desktop or mobile? Internet Explorer fails to support the srcset property of the img element at all, and srcset in Edge has severe distortion issues.
Then what's the "proper" way to accommodate the fat fingers of users of touch screen devices without needing excessive scrolling for users with more precise pointing devices? Adding padding around links improves usability on touch screens but increases the scrolling for mouse or trackpad users. And controlling the padding with a CSS media query breakpoint based on viewport width doesn't help because a touch-operated iPad held in landscape orientation has more pixels than a trackpad-operated netbook.
Which Wonka? There are two Wonka organizations: the Dahl estate and Nestlé.
(In-universe, they'd be seen as Wonka's biographer and the company that bought the company that bought the candy company from the Buckets, respectively.)
The FSF considers the javascript required to access github "non-free" but that is not the same as proprietary I think. It's not closed source
Then where's the source code? The script file that GitHub serves is minified, and minified JavaScript is not "the preferred form of the work for making modifications to it", which is how both GPLv2 and GPLv3 define a work's "source code".
In addition, the requirement to run non-free JavaScript is not the only thing that prevents a manufacturer of networked appliances from just starting its own dynamic DNS service for use by its appliances' firmware. I have read reports that the people who handle PSL pull requests are backlogged, which could delay a product launch by months.
Let's Encrypt requires a fully qualified domain name (FQDN) under a well-known top-level domain (TLD), not an IP address in RFC 1918 space or a name under a made-up TLD such as.local or.internal. So do all other CAs whose root certificates are included in Mozilla NSS, as a FQDN is one of the Baseline Requirements adopted by the CA/Browser Forum.
Domains are cheap.
Cheap enough for every head of household to buy and to continue to renew in perpetuity? Because buying a domain is the only way to get a certificate for hosts on your LAN that visitors' devices will trust, and a certificate is the only way you're going to satisfy the "Secure Contexts" requirement for recently introduced JavaScript APIs.
Even apart from the Chrome for Android 7 issue, it might not be so trivial to install your home NAS's private root certificate on laptops, tablets, and smartphones carried by friends and family visiting your LAN.
How so? Microsoft bans anything remotely similar to Visual Studio on Windows 10 S. "Prepare to package an app (Desktop Bridge)" lists the following as an issue that must be addressed before packaging an app:
Your app generates code. Your app can generate code that it consumes in memory, but avoid writing generated code to disk because the Windows App Certification process can't validate that code prior to app submission. Also, apps that write code to disk won’t run properly on systems running Windows 10 S.
Drivers for Windows 10 S must meet these requirements. I imagine that participants in a public driver beta test would use Windows 10 Pro instead of Windows 10 S.
I don't know that many people who habe domains just for their own devices at home...
The manufacturer of such a device is expected to follow the following steps:
1. Register a domain for devices to use. 2. Submit this domain to Mozilla's Public Suffix List so that cookies and certificates from one device don't leak to others. 3. Issue a subdomain of this domain to each device. 4. Operate a dynamic DNS service so that devices can set their AAAA and TXT records.
The cost of steps 1 and 4 would be rolled into the price of each device.
Sure, it's technically possible, but it's also possible for the user to operate their own CA
It may not be possible for the user to configure a particular device to trust his own CA's root certificate. For example, under Android 7 "Nougat", an application will not trust user-added root certificates unless the application's developer has opted in, and there's no rule that all web browser developers must opt in. See "Changes to Trusted Certificate Authorities in Android Nougat" by Chad Brubaker
Other than DRM there is no point in the encryption with localhost communication for a video player app.
The other point is to satisfy the mixed active content blocking policy of major web browsers. If the outer page is HTTPS, all requests it makes must also be HTTPS. Or do you consider the mixed active content blocking policy itself pointless?
The installer for the application would install the corresponding root certificate into the root certificate store of all major web browsers currently installed on the same machine.
But this wouldn't work so well for allowing access by other machines on the same LAN. This requires operating a dynamic DNS server that issues subdomains of a domain on the Public Suffix List and then obtaining a certificate from Let's Encrypt through the DNS challenge.
there's the additional problem of the HTTPS server not being reachable from the outside at all.
ACME as implemented by Let's Encrypt supports a cleartext HTTP challenge and a DNS challenge. A user obtaining a certificate can use either of these to prove domain control. Only the cleartext HTTP challenge requires the server to be "reachable from the outside". The DNS challenge requires that the device requesting the certificate have control over TXT records associated with the requested hostname, which is true of any dynamic DNS implementation.
If they want an HTTPS website to be able to access a local service I've installed via WebSocket, then what other option is there?
Have the local HTTPS server generate its own private key and then send a certificate signing request (CSR) with the public key and hostname to a certificate authority (CA).
But this in turn raises two questions: which CA, and which hostname? Let's Encrypt is limited to 20 certificates per registrable domain per week, and if all devices are on the same domain, it'll hit that rate limit fairly quickly. Is every end user supposed to pay for his own domain and pay to keep it renewed? Or is the manufacturer supposed to register a domain, run its own dynamic DNS server, give each end user a subdomain, and submit it to Mozilla's Public Suffix List (PSL) so that subdomains are considered registrable? Last I heard, the PSL had such a backlog that adding a domain took months.
Also, this only theoretically allows an attacker to steal cookies if they're based off the company's root domain.
Then the domain used for the dynamic DNS service should differ from the domain used for the company's customer service web application. It's why Google serves works uploaded by users from the domain googleusercontent.com.
So...will a rapper try to trademark the word n-igg-er
Not exactly a rapper, but when Flex started singing, his stage name was derived from the N word. Damon Wayans attempted to start a clothing line named after the N word.
The Secure Model of Computation would be defined over a less flexible subset of a Turing machine that deliberately avoids the properties on which the proof of the halting problem's undecidability rests.
"(c) Residents of jurisdictions that do not recognize disclaimers of implied warranty or mandatory arbitration are not eligible to license this software or purchase this device."
Slashdot Mirror
Watch the video
How would I Ctrl+F a video or watch it on a severely slow and/or capped Internet connection? And how would I watch without audio on my computer or with a hearing disability? Its captions have errors, such as a complete lack of punctuation and goofs like "until seventh generation core i7" when "Intel" was meant, due to having been automatically generated. Pending answers to these, I prefer text over video.
If the CSS loads all the desktop-version images, it's badly coded and/or the browser doesn't use the CSS properly.
What's the proper way using HTML and CSS to specify a separate image for desktop or mobile? Internet Explorer fails to support the srcset property of the img element at all, and srcset in Edge has severe distortion issues.
Seven CSS declarations improve its readability.
designing their pages properly
Then what's the "proper" way to accommodate the fat fingers of users of touch screen devices without needing excessive scrolling for users with more precise pointing devices? Adding padding around links improves usability on touch screens but increases the scrolling for mouse or trackpad users. And controlling the padding with a CSS media query breakpoint based on viewport width doesn't help because a touch-operated iPad held in landscape orientation has more pixels than a trackpad-operated netbook.
Which Wonka? There are two Wonka organizations: the Dahl estate and Nestlé.
(In-universe, they'd be seen as Wonka's biographer and the company that bought the company that bought the candy company from the Buckets, respectively.)
The FSF considers the javascript required to access github "non-free" but that is not the same as proprietary I think. It's not closed source
Then where's the source code? The script file that GitHub serves is minified, and minified JavaScript is not "the preferred form of the work for making modifications to it", which is how both GPLv2 and GPLv3 define a work's "source code".
In addition, the requirement to run non-free JavaScript is not the only thing that prevents a manufacturer of networked appliances from just starting its own dynamic DNS service for use by its appliances' firmware. I have read reports that the people who handle PSL pull requests are backlogged, which could delay a product launch by months.
Gosh, 250m views for YouTube Read series... that's actually much less than I expected.
YouTube Red is currently limited to the United States and four other countries.
SSL is now completely free via let's encrypt.
Let's Encrypt requires a fully qualified domain name (FQDN) under a well-known top-level domain (TLD), not an IP address in RFC 1918 space or a name under a made-up TLD such as .local or .internal. So do all other CAs whose root certificates are included in Mozilla NSS, as a FQDN is one of the Baseline Requirements adopted by the CA/Browser Forum.
Domains are cheap.
Cheap enough for every head of household to buy and to continue to renew in perpetuity? Because buying a domain is the only way to get a certificate for hosts on your LAN that visitors' devices will trust, and a certificate is the only way you're going to satisfy the "Secure Contexts" requirement for recently introduced JavaScript APIs.
Free ones are available.
Namely?
If you're referring to subdomains offered by dynamic DNS providers, these providers have to be on Mozilla's Public Suffix List (PSL). If a domain isn't already on the PSL, and 20 other users of subdomains under the same domain have obtained certificates in the past week, Let's Encrypt will deny you a certificate, citing its rate limit policy. If a domain is on the PSL, each subdomain gets its own separate rate limiting bucket of 20 certificates per subdomain per week. In addition, submissions to the PSL must be made by the dynamic DNS provider as a pull request through GitHub.com, and use of GitHub.com requires running proprietary software written in JavaScript on your computer.
Every browser allows self-signed certificates.
I was under the impression that the developer of an application for Android 7 had to explicitly opt in to trusting user-installed root certificates. Does Chrome for Android 7 opt in?
What's the problem?
Even apart from the Chrome for Android 7 issue, it might not be so trivial to install your home NAS's private root certificate on laptops, tablets, and smartphones carried by friends and family visiting your LAN.
ONLY apps can app apps!
How so? Microsoft bans anything remotely similar to Visual Studio on Windows 10 S. "Prepare to package an app (Desktop Bridge)" lists the following as an issue that must be addressed before packaging an app:
Drivers for Windows 10 S must meet these requirements. I imagine that participants in a public driver beta test would use Windows 10 Pro instead of Windows 10 S.
I don't know that many people who habe domains just for their own devices at home ...
The manufacturer of such a device is expected to follow the following steps:
1. Register a domain for devices to use.
2. Submit this domain to Mozilla's Public Suffix List so that cookies and certificates from one device don't leak to others.
3. Issue a subdomain of this domain to each device.
4. Operate a dynamic DNS service so that devices can set their AAAA and TXT records.
The cost of steps 1 and 4 would be rolled into the price of each device.
Sure, it's technically possible, but it's also possible for the user to operate their own CA
It may not be possible for the user to configure a particular device to trust his own CA's root certificate. For example, under Android 7 "Nougat", an application will not trust user-added root certificates unless the application's developer has opted in, and there's no rule that all web browser developers must opt in. See "Changes to Trusted Certificate Authorities in Android Nougat" by Chad Brubaker
Other than DRM there is no point in the encryption with localhost communication for a video player app.
The other point is to satisfy the mixed active content blocking policy of major web browsers. If the outer page is HTTPS, all requests it makes must also be HTTPS. Or do you consider the mixed active content blocking policy itself pointless?
What steps should be taken to field customer support requests related to these?
A. Browsers other than the pack-in, Chrome, or Firefox
B. Browsers installed after the certificate was installed
"It takes a few weeks to process requests" according to Rate Limits. So I don't see how it'd necessarily be faster than a PSL addition.
When the majority of the world concludes it too expensive to do business in the European Union, it becomes the European Union's loss.
or use localhost as the domain and install the certificate into the trusted keystore
"the trusted keystore" of which browsers on which devices?
The installer for the application would install the corresponding root certificate into the root certificate store of all major web browsers currently installed on the same machine.
But this wouldn't work so well for allowing access by other machines on the same LAN. This requires operating a dynamic DNS server that issues subdomains of a domain on the Public Suffix List and then obtaining a certificate from Let's Encrypt through the DNS challenge.
there's the additional problem of the HTTPS server not being reachable from the outside at all.
ACME as implemented by Let's Encrypt supports a cleartext HTTP challenge and a DNS challenge. A user obtaining a certificate can use either of these to prove domain control. Only the cleartext HTTP challenge requires the server to be "reachable from the outside". The DNS challenge requires that the device requesting the certificate have control over TXT records associated with the requested hostname, which is true of any dynamic DNS implementation.
If they want an HTTPS website to be able to access a local service I've installed via WebSocket, then what other option is there?
Have the local HTTPS server generate its own private key and then send a certificate signing request (CSR) with the public key and hostname to a certificate authority (CA).
But this in turn raises two questions: which CA, and which hostname? Let's Encrypt is limited to 20 certificates per registrable domain per week, and if all devices are on the same domain, it'll hit that rate limit fairly quickly. Is every end user supposed to pay for his own domain and pay to keep it renewed? Or is the manufacturer supposed to register a domain, run its own dynamic DNS server, give each end user a subdomain, and submit it to Mozilla's Public Suffix List (PSL) so that subdomains are considered registrable? Last I heard, the PSL had such a backlog that adding a domain took months.
Also, this only theoretically allows an attacker to steal cookies if they're based off the company's root domain.
Then the domain used for the dynamic DNS service should differ from the domain used for the company's customer service web application. It's why Google serves works uploaded by users from the domain googleusercontent.com.
So...will a rapper try to trademark the word n-igg-er
Not exactly a rapper, but when Flex started singing, his stage name was derived from the N word. Damon Wayans attempted to start a clothing line named after the N word.
Again, the laws of your country still need to allow this.
The seller would be based in a country that allows disclaiming implied warranties and not ship to countries that do not. A seller from one of the countries that does not may consider bringing $100,000 or more of investment to a country that does on an E2 visa.
The Secure Model of Computation would be defined over a less flexible subset of a Turing machine that deliberately avoids the properties on which the proof of the halting problem's undecidability rests.
"(c) Residents of jurisdictions that do not recognize disclaimers of implied warranty or mandatory arbitration are not eligible to license this software or purchase this device."
You could try Fantasy Flight Games' adaptation of Doom to see what's possible.