Warning: Creating default object from empty value in /homepages/23/d183491407/htdocs/sushiunity2/shared/class/class.fa_pass.php on line 170

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/eilt.php on line 5

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 70

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 254

Deprecated: Function ereg_replace() is deprecated in /homepages/23/d183491407/htdocs/news/lesen.php on line 360

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 555

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 556

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 4

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 14

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 15

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 16

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 17

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 18

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 19

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 39

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/letzter_artikel.php on line 40

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 946

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 947

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 948

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 949

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 950

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 977

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 978

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 983

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/news/lesen.php on line 984
Facebook kauft WhatsApp | Kuvi
 Sonntag, 29.Januar l 10:54 Uhr

Warning: file(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 6

Warning: file(http://rss.wunderground.com/auto/rss_full/global/stations/10406.xml): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 6

Warning: implode(): Invalid arguments passed in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 6

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 16

Strict Standards: date_sunrise(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 16

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 17

Strict Standards: date_sunset(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/wetter_header.php on line 17
Borken l Klar l 0,0 °C
Letzten News: 00:10 Uhr
06:58 Uhr  | New York, Menlo Park

Facebook kauft WhatsApp

New York, Menlo Park. Facebook plant die teuerste Übernahme in seiner Unternehmensgeschichte. Als Kaufpreis seien insgesamt knapp 14 Milliarden Euro vereinbart worden, teilte «Facebook»-Chef Zuckerberg mit. Zusätzlich werden drei Milliarden bezahlt, die Summe soll später in Form von Aktien an die Gründer und Mitarbeiter fließen.

Facebook kauft WhatsApp
[Foto: Thomas Neutzler] 

Das Online-Netzwerk Facebook übernimmt den Kurzmitteilungsdienst WhatsApp. Facebook-Chef Zuckenberg teilte mit, als Kaufpreis seien insgesamt 18 Milliarden Dollar vereinbart worden.


Die beiden befreundeten Firmenchefs Zuckerberg und Koum haben den Deal, eigenen Angaben zufolge, in den vergangenen zwei Wochen ausgehandelt, eine eher kurze Zeitspanne für eine Übernahme in dieser Größenordnung. WhatsApp ist ein Programm für Smartphones, mit dem Kurznachrichten, Fotos und Audiodateien verschickt werden können. Der Dienst hat derzeit etwa 450 Millionen Nutzer. Jeden Tag kommen im Schnitt eine Million neue Kunden hinzu. Mit WhatsApp können Besitzer von Smartphones kostengünstig Kurznachrichten, Fotos und Videos verschicken.


Die Nutzung eines Online-Netzwerks wie Facebook verbraucht im Alltag der Bundesbürger schon so viel Zeit wie Mittag- und Abendessen zusammen. Durchschnittlich verbringen die Nutzer eines Sozialen Netzwerks 54 Minuten am Tag in ihrer Community, wie die im August 2012 vorgelegte neue ARD/ZDF-Onlinestudie ergab.
Bereitwillig breiten viele Nutzer auf Faceboojk ihr Privatleben aus. Sobald Urlaubs- und Partyfotos hochgeladen sind, gehören sie Facebook und werden über WhatsUpp verschickt. Nicht selten verwandelt sich dieses Netztwerk in einen Albtraum, denn der vermeintliche Spaß führt weit häufiger als gedacht zu Missbrauch: Accounts werden gehackt, Jugendliche gemobbt, öffentlich an den Pranger gestellt, sexuell belästigt oder, sie verbringen ihre Freizeit stundenlang online.

Außerdem greifen immer mehr Arbveitnehmer auf diese Daten zurück. Zuletzt hatten US-Unternehmen von ihren Bewerbern die Zugangsdaten zu deren Facebook-Accounts verlangt. So hofften sie an Informationen über den Lebenswandel der Bewerber zu kommen. Facebook, WhatsUpp, Google und andere Dienste betreiben eine flächendeckende Datensammlung. Jeder Klick hinterlässt seine Spuren im Netz.

Zum Thema Facebook: Polizei warnt vor Betrugsmasche

Polizeidienststellen aus veschiedenen Bundesländern warnen vor einer Betrugsmasche, die auf Facebook um sich geht. Die Täter nehmen dabei die Identität anderer Facebook-Nutzer an und bringen deren Freunde um ihr Geld.

Zum Thema: Polizei warnt vor Betrugsmasche

Ob man ein lustiges Video via Facebook teilt oder ein politisches Statement über WhatsUpp, oder auf Twitter postet: es kann Menschen in Schwierigkeiten bringen.
Hei

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/sushi3/variables.php on line 8

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/box.php on line 4

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/23/d183491407/htdocs/kuku2/module/box.php on line 5
Zum Thema:
22:40 |  | Arnheim
ArnheimGericht verhängt Höchststrafe im Facebook-Mordfall

Im Fall des sogenannten «Facebook-Mords» hat das Bezirksgericht im niederländischen Arnheim den 15-jährigen Täter am Montag zur Jugendhöchststrafe von einem Jahr Haft verurteilt. Zudem ordnete das Gericht eine dreijährige psychiatrische Behandlung des Jungens an.

Magazin
ANZEIGE:
20:14 |  | Berlin
BerlinFacebook schon wieder abgemahnt

Der Bundesverband der Verbraucherschützer wirft dem sozialen Netzwerk Facebook erneut einen Verstoß gegen den Datenschutz vor und hat das Unternehmen deswegen abgemahnt.

ANZEIGE:
Kreditkate ohne Schufa - ohne versteckte Kosten!
Meistgelesen Facebook
03:45 |  | Hückelhoven
HückelhovenVerbot von Facebook-Party

In Hückelhoven sorgt die Einladung zu einer großen Facebook-Party für Aufregung. Ein Unbekannter hat für das zweite Augustwochenende dazu an den Adolfosee eingeladen, und über 1.800 Menschen haben zugesagt. Die Stadt Hückelhoven und der Kreis Heinsberg haben die Party verboten, weil der See in einem Landschaftsschutzgebiet liegt.