Deprecated: Creation of dynamic property ACF::$fields is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/fields.php on line 136 Deprecated: Creation of dynamic property acf_loop::$loops is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 26 Deprecated: Creation of dynamic property ACF::$loop is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/loop.php on line 270 Deprecated: Creation of dynamic property ACF::$revisions is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/revisions.php on line 413 Deprecated: Creation of dynamic property acf_validation::$errors is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 26 Deprecated: Creation of dynamic property ACF::$validation is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/validation.php on line 212 Deprecated: Creation of dynamic property acf_form_customizer::$preview_values is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 26 Deprecated: Creation of dynamic property acf_form_customizer::$preview_fields is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 27 Deprecated: Creation of dynamic property acf_form_customizer::$preview_errors is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-customizer.php on line 28 Deprecated: Creation of dynamic property ACF::$form_front is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-front.php on line 603 Deprecated: Creation of dynamic property acf_form_widget::$preview_values is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 34 Deprecated: Creation of dynamic property acf_form_widget::$preview_reference is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 35 Deprecated: Creation of dynamic property acf_form_widget::$preview_errors is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/forms/form-widget.php on line 36 Deprecated: ElementorDeps\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/functions.php on line 32 Deprecated: ElementorDeps\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/functions.php on line 44 Deprecated: ElementorDeps\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/ContainerBuilder.php on line 231 Deprecated: ElementorDeps\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Source/ReflectionBasedAutowiring.php on line 17 Deprecated: ElementorDeps\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Source/Autowiring.php on line 21 Deprecated: ElementorDeps\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Source/DefinitionFile.php on line 25 Deprecated: ElementorDeps\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Source/DefinitionArray.php on line 33 Deprecated: ElementorDeps\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php on line 42 Deprecated: ElementorDeps\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Proxy/ProxyFactory.php on line 38 Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Container.php on line 87 Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Container.php on line 87 Deprecated: ElementorDeps\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Container.php on line 87 Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the events-manager domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/.sites/685/site2987125/web/vivid/wp-includes/functions.php on line 6114 Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/base/controls-stack.php on line 353 Deprecated: Elementor\Controls_Stack::get_active_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/base/controls-stack.php on line 353 Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $controls as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/base/controls-stack.php on line 800 Deprecated: Elementor\Controls_Stack::get_style_controls(): Implicitly marking parameter $settings as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/base/controls-stack.php on line 800 Deprecated: Elementor\Elements_Manager::create_element_instance(): Implicitly marking parameter $element_type as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/managers/elements.php on line 70 Deprecated: Elementor\Element_Base::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/base/element-base.php on line 1573 Deprecated: Elementor\Repeater::__construct(): Implicitly marking parameter $args as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/includes/elements/repeater.php on line 48 Deprecated: Elementor\Core\Utils\Collection::filter(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/core/utils/collection.php on line 51 Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/ObjectDefinition.php on line 62 Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/ObjectDefinition.php on line 75 Deprecated: ElementorDeps\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/ObjectDefinition.php on line 158 Deprecated: ElementorDeps\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Resolver/ObjectCreator.php on line 158 Deprecated: ElementorDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34 Deprecated: ElementorDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/elementor/vendor_prefixed/dependency-injection/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34 Deprecated: Creation of dynamic property acf_field_oembed::$width is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-oembed.php on line 31 Deprecated: Creation of dynamic property acf_field_oembed::$height is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-oembed.php on line 32 Deprecated: Creation of dynamic property acf_field_google_map::$default_values is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-google-map.php on line 33 Deprecated: Creation of dynamic property acf_field__group::$have_rows is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/includes/fields/class-acf-field-group.php on line 31 Deprecated: Creation of dynamic property acf_field_clone::$cloning is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-clone.php on line 34 Deprecated: Creation of dynamic property acf_field_clone::$have_rows is deprecated in /home/.sites/685/site2987125/web/vivid/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-clone.php on line 35 Klage gegen Social Media wegen Suchtgefährdung - VIVID - Fachstelle für Suchtprävention
x
VIVID INSIDE

Klage gegen Soziale Medien wegen Suchtgefährdung

Soziale Medien können süchtig machen oder Sucht verstärken. In den USA wurde nun die weltweit erste Klage dazu zugelassen.

800 Klagen in 42 US-Bundesstaaten

Wenn jemand abhängig nach Sozialen Medien wie etwa Instagram, Tiktok oder Snapchat wird, können dann die betreffenden Unternehmen rechtlich dafür belangt werden? Wenn jemand – auch durch Soziale Medien verstärkt – ein unrealistisches Körperbild entwickelt, darf dann das Social Media-Unternehmen geklagt werden? Mit anderen Worten: Darf der Zusammenhang von Sucht und Sozialen Medien überhaupt vor Gericht kommen? Ja, entschieden zwei US-amerikanische Gerichte. Eine Klage an die Betreiber Sozialer Medien ist zulässig.

Unternehmen wollten Klagen verhindern

Große Anbieter von Diensten im Internet wollten die Klage verhindern. Sie hatten sich darauf berufen, dass die Sucht durch die Handlung Dritter zustande komme. Sie selbst seien nur die Plattformen. Die schädigenden und süchtig machenden Inhalte kämen jedoch von Anderen.

Sie beriefen sich dabei auf den berüchtigten Paragraph 230 des „Communications Decency Act“. Demnach können Internet-Dienstleister für die Handlungen Dritter nicht verantwortlich gemacht werden, sie sind dagegen immun.

Die eingebrachte Klage jedoch betrifft nicht nur Inhalte Dritter, entschieden Ende 2023 zwei Gerichte in zwei US-Bundesstaaten, eines in Oakland und eines in Los Angeles. Daher haben die Tech-Unternehmen nicht generell Immunität gegenüber Klagen.

Hunderte Klagen in den USA

Das Gericht entschied damit gegen Alphabet (GOOGL.O), das Google und YouTube betreibt, Meta Platforms (META.O), das Facebook und Instagram betreibt, ByteDance, das TikTok betreibt, und Snap (SNAP.N), das Snapchat betreibt. Das berichtet die Agentur Reuters.

In den USA wurde 2023 eine landesweite Klage gegen Social-Media-Unternehmen eingereicht. Rund 800 einzelne Klagen aus 140 Schulbezirken und 42 Bundesstaaten werden darin vertreten. Diese hunderten Klagen wurden im Namen einzelner junger Menschen eingereicht, die durch Soziale Medien negative Auswirkungen hatten, etwa Erfahrungen mit Gewalt, Mobbing oder Sucht machten. Einzelne Klagen umfassen auch ein unrealistisches Körperbild, das von sozialen Medien ausgehen und eine Essstörung verstärken kann.

Konten löschen und Filter wegschalten

In den Klagen wird behauptet, dass Social-Media-Websites durch bestimmte Funktionen und Algorithmen junge Menschen anlocken. Bei Kindern und Jugendlichen, in deren Namen die Klagen eingereicht wurden, hätten sie Sucht oder andere psychische Probleme verursacht. So werden unter anderem die unzureichende Altersüberprüfung und die fehlende Beschränkung der Nutzungshäufigkeit und Nutzungsdauer bemängelt.

Die Klage beinhaltet auch, dass es schwierig ist, Konten zu löschen und Filter zur Bearbeitung von Inhalten wegzuschalten. Gefordert werden Schadensersatz und die Unterlassung der angeblich rechtswidrigen Praktiken.

Weltweit wurde mit Spannung erwartet, ob die Klagen vor dem US-Gericht zugelassen werden oder ob den Tech-Unternehmen von vornherein die Verantwortung für Internet-Sucht abgesprochen wird. Diese Entscheidung hat weitreichende Auswirklungen auch auf andere Länder.

Mehr dazu: