Strict Standards: Redefining already defined constructor for class wpdb in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/wp-db.php on line 52

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/cache.php on line 389

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 537

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 556

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 653

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 678

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/theme.php on line 508

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/disclose-secret.php on line 102

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 44

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 58

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 59

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/manager.php on line 60

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/cache.php on line 28

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/cache.php on line 37

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/option.php on line 156

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/option.php on line 403

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 24

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 27

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 30

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator.php on line 33

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/migrator_post_levels.php on line 117

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/disclose-secret/config_ui.php on line 71

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method JAWPopularPostsWidget::load() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Ajax_Comment_Preview::init() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGenerator::Enable() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_query_vars() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 137

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 114

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14

Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/classes.php on line 212

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_where() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_where() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_join() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_join() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_groupby() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_tag_templates() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 160

Warning: Cannot modify header information - headers already sent by (output started at /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/wp-db.php:52) in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/feed-rss2.php on line 2
Bank 2.0 » Second Life http://www.bank-zweinull.de IT-Trends und Innovationen für Banken
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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 137

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Mon, 28 Jul 2014 17:10:49 +0000
http://wordpress.org/?v=2.2.3 en © Martina.Goehring@centrestage.de () Martina.Goehring@centrestage.de IT-Trends und Innovationen fuuml;r Banken Martina.Goehring@centrestage.de No no http://www.centrestage.de/banking/wp-content/plugins/podpress/images/powered_by_podpress.jpg Bank 2.0 http://www.bank-zweinull.de 144 144
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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
<br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Nun auch die Sparkassen in Second Life!
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/11/07/nun-auch-die-sparkassen-in-second-life/
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/11/07/nun-auch-die-sparkassen-in-second-life/#comments

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Wed, 07 Nov 2007 10:22:32 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
Second LifeSparkassen http://www.bank-zweinull.de/2007/11/07/nun-auch-die-sparkassen-in-second-life/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 134

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 135

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line 74

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Sparkassen in Second LifeDie vituelle Welt sollen jetzt auch die Sparkassen betreten. Nach der Deutschen Bank mit Q110 ist nun der Ostdeutsche Sparkassenverlag in Second Life eingezogen. Am 2. November 2007 auf der Herbsttagung für Sparkassenvorstände an der Ostdeutschen Sparkassenakademie wurde die eigene Insel “S-Island” vorgestellt. Mit dieser steht für Sparkassen ein Experimentierraum im Internet der Zukunft zur Verfügung mit

  • Konferenzraum
  • Beratungsraum und Filiale
  • Gutschein-Cashy

Die Zielsetzungen sind (siehe auch beigefügte Präsentation):

  • sich mit Second Life in einer gesicherten Umgebung vertraut machen,
  • gemeinsamer Platz zum Bauen, Entwickeln und Programmieren von Objekten,
  • Erproben von Geschäftsmodellen und Marketing im Second Life,
  • Anbieten von Seminaren und Workshops für Startups und
  • Förderung von Kunst.

Das ganze wurde zusammen mit ITM Gesellschaft für IT Management und der TwentyOne GmbH aus Dresden realisiert. Begleitend dazu gibt es weitere Informationen im Blog.

]]>

Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/11/07/nun-auch-die-sparkassen-in-second-life/feed/
00:01:01 br / bStrict Standards/b: 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 ge br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp Leitartikel,,Second,Life Martina.Goehring@centrestage.de no No

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
<br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Web 2.0 und virtuelle Welten
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/10/26/web-20-und-virtuelle-welten/
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/10/26/web-20-und-virtuelle-welten/#comments

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Fri, 26 Oct 2007 11:45:55 +0000
Martin Engstler
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
Bank+ZukunftQ110Second Life http://www.bank-zweinull.de/2007/10/26/web-20-und-virtuelle-welten/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 134

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 135

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line 74

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Auf dem Innovationsforum “Bank&Zukunft” des Fraunhofer-Instituts für Arbeitswirtschaft und Organisation (IAO) stellte heute Rainer Welsch von der IBM Deutschland GmbH die Q110 Second Life Filiale der Deutschen Bank vor.

Rainer Welsch IBM

Interessant waren seine Ausführungen, was von den Kunden in der Second Life Filiale genutzt wird:

  • Grosses Interesse finden alles, was mit Spaß und “Gaming” zu tun hat, z.B. die Basketballsimulation auf den Zwillingstürmen der Deutschen Bank oder der Geldautomat, der wenn man rechtzeitig reagiert, Lindendollars ausgibt.
  • Die Simulation der unterschiedlichen Lebenssituationen in Themenwelten wie „Hochzeit“, „Zukunftsplanung“ und „Immobilienkauf“ mit ihren finanziellen Auswirkungen wird auch häufig genutzt.
  • Produktinformationen werden auch in der virtuellen Welt abgerufen.
]]>

Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/10/26/web-20-und-virtuelle-welten/feed/
00:01:01 br / bStrict Standards/b: 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 ge br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp Second,Life,,Vertrieb,,Innovation Martina.Goehring@centrestage.de no No

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
<br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Die Deutsche Bank in Second Life
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/08/14/die-deutsche-bank-in-second-life/
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/08/14/die-deutsche-bank-in-second-life/#comments

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Tue, 14 Aug 2007 15:46:08 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
Bank+ZukunftBankingQ110Second LifeWeb 2.0 http://www.bank-zweinull.de/2007/08/14/die-deutsche-bank-in-second-life/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 134

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 135

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line 74

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Bank2.0_LogoVon Juli bis Dezember 2007 ist in Second Life auch Q110, die Berliner Filiale der Zukunft der Deutschen Bank, vertreten und macht damit die Welt der Wünsche buchstäblich erlebbar. Dabei wird das Zusammenspiel von realen und virtuellen Möglichkeiten erprobt.

Drei Stationen geben Einblick in die Wunschwelten der Menschen: Hochzeit, Zukunftsplanung und Immobilienkauf. Ein Hochzeitspaar kann virtuell eine Hochzeit erleben und erhält gleichzeitig einen Kostenvoranschlag für die real geplante Hochzeit. Q110 betreibt eine eigene „Community“, wo man sich als Mitglied zum Beispiel mit anderen Heiratswilligen oder angehenden Häuslesbauern treffen kann.

brightcove Direktvideo link


Die ersten Erfahrungen im Umgang mit den Nutzern in Second Life liegen ebenfalls vor. So hat das Kölner Institut psychonomics sowohl positive als auch negative Faktoren herausgefunden:

Positiv:
Die virtuelle Filiale wurde von den Nutzern überwiegend als innovative Idee gelobt.
Der Bank wurde ein dadurch entstehender Imagegewinn attestiert.
Besonders die Möglichkeit, den vor Ort vertretenen „Q110“-Mitarbeitern bzw. Avataren Fragen stellen zu können, wurde als Pluspunkt bewertet.

Negativ:
Kritik gab es an der ungenügenden Information und fehlenden persönlichen Beratung vor Ort.
Der Bestand an Angeboten, Produktinformationen und Möglichkeiten, sich damit auseinanderzusetzen, sei ungenügend.
Es fehlen innovative Ideen, um das bestehende Interesse der Nutzer dauerhaft für sich zu nutzen.

Die virtuelle Bank der Zukunft befindet sich auf der SL-Insel von IBM, die auch zur Umsetzung des Q110 Konzepts beigetragen hat. Zu Q110 in Second Life kommen Sie am einfachsten, wenn Sie in die SL-Suchmaske den Begriff „Q110“ eingeben.

]]>

Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/08/14/die-deutsche-bank-in-second-life/feed/
00:01:01 br / bStrict Standards/b: 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 ge br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php/b on line b188/bbr / br / bStrict Standards/b: 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 'CEST/2.0/DST' instead in b/homepages/3/d24003326/htdocs/bank-zweinull/wp Leitartikel,,Second,Life Martina.Goehring@centrestage.de no No

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28
<br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> <br /> <b>Strict Standards</b>: 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 'CEST/2.0/DST' instead in <b>/homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/wp-feedstats/wp-feedstats.php</b> on line <b>188</b><br /> Banken in Second Life
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/03/29/banken-in-second-life/
Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/03/29/banken-in-second-life/#comments

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 23

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 25

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 27

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 28

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/functions.php on line 14
Thu, 29 Mar 2007 19:53:36 +0000
Martina Goehring
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_tags_to_rss() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57
BankingCommunity BankingQ110Second Life http://www.bank-zweinull.de/2007/03/29/banken-in-second-life/ Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 134

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/coolplayer/coolplayer.php on line 135

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/formatting.php on line 74

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/plugin.php on line 57

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 669

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/3/d24003326/htdocs/bank-zweinull/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 670

Bank2.0_Logo„Die Menschen sind bereit, in virtuellen Welten Geld auszugeben. Heute ist der Markt etwa 15 Millionen Dollar groß. In fünf Jahren wird der Markt zwischen 500 Millionen und einer Milliarde Dollar schwer sein“, sagte Oliver Samwer der faz.net. Gemeinsam mit seinen Brüdern Alexander und Marc Samwer hat er Alando und Jamba gegründet und verkauft, hat in StudiVZ und LinkedIn investiert und nun beteiligen sie sich über ihre Beteiligungsgesellschaft European Founders mit 10 Prozent an den Anshe Chung Studios, dem Unternehmen der ersten Second Life Dollar-Millionärin Ailin Gräf.

Laut secondlifeinsider.com gibt es 10 Banken in Second Life, davon sind sechs aus der realen Welt, die anderen gibt es nur virtuell. Welche das sind, wird in diesem Post zwar nicht erwähnt. Dafür wird aber erklärt, warum sich Banking in Second Life ziemlich vom Banking in der realen Welt unterscheidet.

Laut Jim Bruene von netbanker.com gibt es folgende 6 Banken aus der realen Welt in Second Life:

“Sep. 2005: Wells Fargo is the first real-world bank with a presence in Second Life.
Dec. 2005: Wells Fargo leaves SL, moving its Stagecoach Island to a new platform.
7 Dec 2006: ABN AMRO becomes first European bank in SL.
7 Jan 2007: BNP Paribas opens a small test area.
7 Feb 2007: Swiss bank BCV opens its doors in SL.
21 Feb 2007: ING Bank launches website and blog to get users involved in building what it calls Our Virtual Holland.
2 Mar 2007: Danish Saxo Bank announces plans to create trading platform in SL.”

Wells Fargo, USA

Die Gründe von Wells Fargo, sich bei Second Life zu engagieren, sind laut News.com und netbanker.com:

„Apparently, the first real-world bank with a truly virtual presence in Second Life is none other than Wells Fargo Bank. They launched a pilot of an online multiplayer video game built entirely inside Second Life, accessible only to Wells Fargo customers who received an invite from the bank. The pilot project, known as “Stagecoach Island”, is a digital environment intended to help young people learn financial responsibility. However, after a few months the site was moved to a standalone site with no connection to Second Life stagecoachisland.com.”

[update 22.06.2007] Wells Fargo gilt als die derzeit innovativste Bank im Bereich online Services. Sie haben es exzellent verstanden, Innovation-Kundenerlebnis-Web 2.0 zusammenzuführen. Eine sehr gute und umfassende Zusammenstellung aller Services dazu liefert Visible Banking.

ABN AMRO, Niederlande

Laut Pressemiteilung eröffnete ABN AMRO, die größte Niederländische Bank, eine Niederlassung in Second Life mit folgenden Zielen: „The virtual branch

  • will be very similar to the ABN AMRO Financial Centres,
  • will offer information and create a platform where (potential) customers of the bank can meet each other,
  • will offering financial advice,
  • will be organising seminars on Second Life for specific target groups, such as business starters or new graduates (Young Professionals) and Preferred Banking clients,
  • will also use the virtual world of Second Life to recruit new staff.”

Zunächst soll Kommunikation im Vordergrund stehen. Bankendienstleistungen sind aber in der Zukunft durchaus denkbar. Wietze Reehoorn, a member of ABN’s executive board, said in a statement: “Communicating with customers via the Internet can become more personal and more direct. Competition between Dutch banks will be determined to a significant degree by finding the best way to establish personal contact with customers.”

BNP Paribas, Frankreich

“The financial group BNP Paribas arrives in Second Life by the means of the Workshop.”

BCV, Schweiz

BCV ist die erste Schweizerbank, die sich nach eigenen Aussagen mit einer Präsenz in Second Life bereits heute auf das Web 3.0 (!) Paradigma vorbereitet und verfolgt des weiteren folgende Ziele:

  • „As part of its innovative communications strategy, BCV will use its island on Second Life as a showcase for its products and services.
  • The building, designed by Lausanne-based artist Ronald Juliet, will also host regular exhibitions of works from BCV’s art collection.
  • In addition, BCV is making land available to local businesses and associations in the hope that its island will become a virtual home for Switzerland’s French-speaking community on Second Life.
  • BCV continues to innovate by establishing a presence on Second Life, putting it at the center of what promises to be a major source of new ideas going forward.
  • With its Second Life initiative, BCV can now extend this approach to the virtual world of social computing as the internet moves toward the more fully interactive “Web 3.0” paradigm.”

ING Bank, Niederlande

ING is taking the virtual-world phenomenon seriously and expects that it will become part of its future internet activities. (…) ING seeks to gain a better understanding of improvements it can make to products and services by assessing valuable feedback from inhabitants who will experience ING in Second Life.”

Ein Post von ING Asia/Pacific Blog dazu: “At ING we also tested and discussed Second Life … we decided to move ahead … we will invite other companies and institutions … to be active, hold office, start a business, and participate in art contests …”

Saxo Bank, Dänemark

Die dänische online investment Bank Saxo aus Kopenhagen hat ein Büro in Second Life eröffnet mit den Zielen:

  • „to offer Second Life residents the ability to manage their real-life financial portfolios from within the virtual world, and may eventually create a market to trade the Linden dollar against real-world currencies.
  • Saxo hopes to add a new platform for Second Life residents called VirtualTrader to its existing platforms by the third quarter of the year, said Stephan Martinussen (Stephan Canto in Second Life), the bank’s co-head of sales trading.
  • So far, Saxo’s virtual office has a meeting space with links to the bank’s website, a live trading game for visitors and an auditorium that will be used for symposia and training modules.”

Weitere virtuelle Banken in Second Life

Meta Bank: Das Interview mit dem Präsident der Meta Bank liefert Informationen über das Banksystem in Second Life und die Funktionsweise des Linden Dollar. „That is why I started Meta Bank, because I wanted to create a capital base that would grow in-world businesses.”

GinkoTec Financial is a Second Life Savings Bank.

TSM Bank auf Germania Farrago bietet den Tausch von Linden Dollar in Euro an.

[update 25.5.2007] Als erster deutscher Finanzdienstleister eröffnete nun die Wirecard Bank AG in Second Life eine virtuelle Filiale, in der sich Kunden über Produkte und Dienstleistungen beraten lassen oder direkt auf die Bezahldienste zugreifen können. Die Bankavatare sind speziell geschulte Servicemitarbeiter.

[update 19.07.2007] Die Deutsche Bank ist mit ihrer mehrfach ausgezeichneten Filiale Q110 seit Anfang Juli nun auch in Second Life vertreten. Bis Dezember sollen in der virtuellen Welt die Themenwelten „Hochzeit“, „Zukunftsplanung“ und „Immobilienkauf“ erlebt werden können, mit Anregungen, Informationen und Hinweisen zu Finanzlösungen sowie dem Austausch mit Gleichgesinnten in Communities. Wer die Avatare in der realen Welt kennenlernen möchte bzw. weiteren Gesprächsbedarf hat, begibt sich in die Filiale Q110 in der Friedrichstraße in Berlin.

]]>

Strict Standards: strtotime(): 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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 75

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 'CEST/2.0/DST' instead in /homepages/3/d24003326/htdocs/bank-zweinull/wp-includes/link-template.php on line 89
http://www.bank-zweinull.de/2007/03/29/banken-in-second-life/feed/