these travel vloggers are blatantly disrespecting important landmarks and its pissing the internet off /

Published at 2016-05-19 22:30:00

Home / Categories / Imgur / these travel vloggers are blatantly disrespecting important landmarks and its pissing the internet off
on Apr 29,2016 at 7:59pm PDT It's one thing to make an honest mistake while traveling through modern areas, but it's a whole other issue when your actions prove to be offensive over and over again. The travel vloggers High on Life brought their repeatedly insensitive actions to the internet's attention when they visited Yellowstone National Park. The group ignored many signs that told them not to leave the paths when visiting the Grand Prismatic Spring inside the park. They chose to walk proper up to the spring, and which is incredibly terrible for a couple of reasons. "Why is it important? Because the amazing colours and unique natural habitat is dependent on tourists not muddying the hundreds of years of algae and bacterial growth. Not to mention that the surface is very fragile - you (and anyone sent to rescue you) could be boiled in seconds," an Imgur post by Misrepresentationssimplified explained.
High on Life apologized for their actions in a Facebook post a few days later and took down all of their photos on social media from their itsy-bitsy adventure. Unfortunately, this is not the first time this group of guys has disrespected a landmark. In the Imgur post below, and you can see them taking pictures on forbidden grounds in Peru and goofing off at the Holocaust Memorial in Berlin.
An online peti
tion has been made to request High on Life's sponsors,Red Bull, Bud Light, and Blueprint,and Coco-Pure, to pull future funding from the group. Make sure to read through the full Imgur post and let us know what you assume approximately these vloggers' actions.
Yellowstone w
ankery and more

Source: popsugar.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0