Forced cloud: Difference between revisions

(One intermediate revision by one other user not shown)

Line 1:

'''Forced [[Cloud (service)|cloud]]''', '''forced internet''', '''forced remote connection''', etc... is a practice in which software or hardware requires a continuous/constant (or, at least, regular) device connection to remote servers owned by the company who made said software/hardware, even when the features technically don't require network connections.

'''Forced [[Cloud (service)|cloud]]''', '''forced internet''', '''forced remote connection''', etc... is a practice in which software or hardware requires a continuous/constant (or, at least, regular) device connection to remote servers owned by the company who made said software/hardware (or a partner of said company), even when the features technically don't require network connections.

Because forced cloud generally means locality is technically possible, entities that engage in this practice have little reason to do so outside of personal gain. They may find it favorable for several reasons, including:

Line 18:

The user is "chained" to the cloud provider. The provider typically has no incentives to support interoperability, making it harder for the user to migrate.

===Limited or non-existent offline functionality===

Products or services that depend of cloud services might work partially or might not work at all, making the product or service very limited or unusable if there's not any network connection.

==Examples==

@@ Line 1: / Line 1: @@
 {{StubNotice}}
-'''Forced [[Cloud (service)|cloud]]''', '''forced internet''', '''forced remote connection''', etc... is a practice in which software or hardware requires a continuous/constant (or, at least, regular) device connection to remote servers owned by the company who made said software/hardware, even when the features technically don't require network connections.
+'''Forced [[Cloud (service)|cloud]]''', '''forced internet''', '''forced remote connection''', etc... is a practice in which software or hardware requires a continuous/constant (or, at least, regular) device connection to remote servers owned by the company who made said software/hardware (or a partner of said company), even when the features technically don't require network connections.
 Because forced cloud generally means locality is technically possible, entities that engage in this practice have little reason to do so outside of personal gain. They may find it favorable for several reasons, including:
@@ Line 18: / Line 18: @@
 {{See also|Data lock-in}}
 The user is "chained" to the cloud provider. The provider typically has no incentives to support interoperability, making it harder for the user to migrate.
+===Limited or non-existent offline functionality===
+Products or services that depend of cloud services might work partially or might not work at all, making the product or service very limited or unusable if there's not any network connection.
 ==Examples==