OK... Now imagine your ISP had the cap and Amazon did not pay your ISP anything extra, and your ISP is not a related entity to Amazon, so they have no financial incentive to favor Amazon, and your ISP decided to waive the cap for Amazon prime educational videos.

That's more like the Wikipedia situation.

Maybe the description "Network Neutrality" is not even the goal we should want it's really Non-interference; as in, no use of network traffic management to promote a commercial service sold by yourself or a related entity by delivering better network performance or by waiving network access fees or discounting overage, and no accepting financial compensation in exchange for providing Non-equal access by doing the same.

However: it is acceptable to waive data usage counting or caps, or allow a 3rd party to pay customers' bill, for access to an application or website as a community service. To qualify as a community service, the purpose of the resource must be non-profit, and there can be no charge or display of advertising while using the resource provided for free as a community service.

I always thought 'sextuplets' were what you called nymphomaniac twin sisters!

Twin is two. Sex is 6.

A sextuplet is a tight-nit group of 6; typically used to refer to the birth of 6 kids together.

In the case of primes; it is 6 primes found sequentially which are very close to each other, where the largest prime is within 16 units distance of the smallest of the 6 primes.

Outsource their Advertising business to a subsidiary that has no control of what search results appear on the page.

Let that subsidiary do all business in Europe; let the search company not do any business in Europe.

And then the search company can simply ignore all requests to control search results as out of jurisdiction.

Sure Microsoft; after you sign this memorandum where you enter into binding agreement to fork over payment for all costs associated with the audit, plus an additional non-refundable fee of 6139000¥ plus a 31390¥ retainer.

Costs to Include payment for some additional vacation time for management and senior staff and the cost of purchasing additional computers, server equipment, software, and gov't employees, labor, overtime hours desired to assist with the audit, and other ordinary expenses.

Fuck, I barely speak English, I don't want to learn a new language.

English is fine. PHP on the other hand, is not.

You seem to be suggesting a solution in which someone will both cooperatively pass laws spanning multiple nations,

Actually.. I guess I would rather not. Another alternative that would not require it would be to require providers impose a $1 to $5 per call termination fee for any oversea telemarketing call, regardless of whether a product successfully sold or not, and at least 25% of any extra fee collected needs to be paid to the person who was called.

I would like to add a "Telemarketing call reporting" function, where the person who receives the call will enter a code such as "#", during the call, then if the other parties disconnects the call within 5 seconds, or the person presses "#" two more times; the call will automatically be reported as a telemarketing call requiring charging for the service.

In this case, no extra international cooperation is required, since the person making the call terminates the call in the country they are calling, they are automatically subject to any and all fees which may be imposed for the call, and, there are already laws that will cause the originating telecom provider to pay for any and all fees that are due and not paid by the caller.

Telemarketers targeting the US will have their operations calling from Canada or elsewhere, and in Canada they'll be calling from the US or elsewhere.

What we need is a law prohibiting telemarketing from an overseas operation to be passed in both countries, and a cooperative agreement to enforce the other country's law locally.

And a regulation that companies which provide termination for overseas calls either refuse any call, or ensure through their contractual agreements and technology on their network that caller id will always be present and reflects a valid telephone number for the actual country of origin unique and persistent to the calling party.

Hello USA , Hello UK, Hello any of the usual suspects.

Hello any country with resources that wants to make one of the above countries look bad by framing them and then "discovering" new malware in the wild.

This is what their reaction used to be when we talked about switching Windows servers' operating system to Linux. "Linux? No! Wtf is Linux?"

I'm only half-kidding. over the past year or two, there's been a nifty cottage industry of small storefronts that perform screen replacements on cell phones. If that number gets cut in half, things are going to get interesting for these store owners.

Firstly; I think the old phones will still be widely used for a few more years, as long as the price of a screen replacement is low comparable to the cost of a new phone, I think they will be okay for at least another year, they were always a market of limited duration meeting a temporary need.

Otterbox and other impact resistant cases. Not only would this impact Otter Products, but also many retailers, since cases tend to be a high-margin upsell, so their profits would slip.

I suspect their margin may need to become thinner, but this is less likely. It's easy to see how fewer broken screens will affect sales of screen replacement service, however, the sales of impact-resistant cases are going to be primarily linked to customer perception of risk. The new screens don't make the phone waterproof, and then there are is that iPhone 6+ bending issue, which may very well have increased sales of cases.

Next, people view their cases or phone skins as a fashion statement, and I don't see that going away .

Finally, there are people who buy the cases because they need or want a blackberry-style holster, and again, even with impact-resistant glass, the concern of damage to the phone, scratching, or wear from routine daily use remains, and there will be many people who won't perceive the improved glass as a subsitute for a ogod case.

It depends on whether you consider the gorilla glass version previously used by iPhones as a competitor or not. Generally the reading "competitive cover glass now in the market" would be a comparison against only glass made by OTHER COMPANIES', not previous versions of your own product which are now deprecated.

It is all in the design and implementation. Binary formats and protocols generally have field and record delimiters, as well as error detection and correcting features like checksums.

In my experience, bespoke file formats do not have any of these things, or they are not reliable at all. Of course Mission-critical filesystems such as Ext4, and Enterprise-application DBMs such as PostgreSQL, Oracle, or even MySQL (as long as you use InnoDB and not MyISAM) have many hundreds of thousands of man-hours in developing their binary file formats and tools to help repair them.

But systemd is new. The new logging format has none of that level of engineering and effort behind it, therefore; there is absolutely no reason to believe that systemd's journal is meeting a level of real-world production-usable robustness comparable to the Ext filesystem or comparable to PostgreSQL, which have been used by hundreds of thousands of large enterprises over 15 years of production experience.

There is no "mostly ACID"--a database is or isn't, and the human-readability of a file has no bearing on how corruptable it is. Things like underlying file system and implementation have more to do with it.

Incorrect. Corruption can occur on both binary and human-readable files. The impact of corruption on a binary file is much more severe. The corruption of a human-readable file can generally be resolved by humans. Humans can't read the binary file in the first place, and in general, the computer can't resolve the binary file corruption, and generally, the only way it can be resolved is for the programmer who designed the proprietary binary file format to analyze the file, or for specialized tools such as E2fsck to be developed which discard rather than attempting to recover bits from apparently corrupted data.

The point is the term "ACID" is not really applicable to a text-based log in the first place; it's an inappropriate use of the term. ACID refers to a standard of transactional integrity of a relational database. Text-base syslog files never update a previous entry, and every record only has one column, so it DOESNT MAKE SENSE to speak of the relational integrity of a text syslog file. You could say the text logfile is fully ACID compliant, except, in some cases, the Log rotation operation is often not ACID compliant, since it may be performed by a script without the proper care.

Failed transactions roll back cleanly and single byte errors most certainly do NOT render all data theteafter inaccessible! Despite that you have binary formatted data, even if it is all VARCHAR fields.

In my experience... PostgreSQL will shutdown and refuse to start back up. You will then be in for a lengthy restore from backup followed by point in time recovery efforts by replaying transaction logs, or a very lengthy repair process. MySQL has similar issues.

I'm not saying this is bad for pgSQL or MySQL, as there are definitely efficiency requirements that drive the design, but the fact is that they cannot cope with corruption so well; they can do fairly well with some common problems, such as a pull of the plug, that is: assuming the SYNC command really does guarantee written data is committed to stable media before returning execution.

It left China with either letting go of censorship, or breaking significant chunks of the Internet for their population.

DMCA-style takedown or GEO-Lockdown of CDN content upon an e-mail request of the Chinese government.

Apply what ever laws for DSL to have dry loop DSL to Coax so that you have dry loop COAX.

The problem with this idea is that a Dry Loop is an actual thing; it's a physical connection, and it's a good match for the technology. Your dry loop is a dedicated electrical circuit.

A cable distribution network works differently. There is no dedicated circuit from the cable company to each customer; everything connects back to a headend..

And it's a ginormous broadcast network.

There's no cable running back to the cable company labelled "John Doe's line"

Customers don't have dedicated wiring back to the headend, therefore; it is impossible to create a dedicated electrical circuit.

Furthermore..... spectrum on the cable lines are limited and have to be shared with video. The cable company has to choose how they want to carve up their spectrum and ultimately which frequency ranges their headend will allow for broadband channels.

Finally, all the bandwidth on the headend is shared among customers in a neighborhood or general area, and this is one of the bottlenecks that prevents "unlimited" service.

It's essentially as if there is an Ethernet network with all customers plugged into the same switch, and some additional security measures on the endpoint devices to prevent sniffing.

However, it's kind of like an old style thicknet, in that there is not a dedicated homerun for each customer back to the central point.

It is inherently shared; every device transmitting inherently consumes the cable company's property, so there's really no room for a true "Dry Loop".