D G

Stop spinning the bottle like a caveman. QR Cups’ 18 oz. red cups put a modern spin to the party game with the help of a companion app. Each of the 25 cups has a QR code that reveals a risque question or activity when scanned.

You can order the QR Cups: Truth or Dare Edition from Amazon for $10 (USD). The company is also working on bro code and movie trivia variants.

[via DudeIWantThat]

A company called Znaps has a Kickstarter campaign underway to turn your smartphone's charging port and cable into a magnetic charger charger.

It's similar to Apple's MagSafe power connector, which allows you to easily plug and unplug the power connector to your laptop with a satisfying magnetic snap.

Most importantly, it also detaches if and when someone trips on the power cord, which could break the cord and send your laptop hurtling towards a faceoff with the floor. And the floor always wins that fight. But MagSafe isn't available for the iPhone.

Here's what Apple's MagSafe connector looks like.

For the Znaps, a tiny magnetic adapter fits into your device's charging port (Lightning for iOS devices, microUSB for Android) and a separate magnetic adapter fits over your cable's connector. And the rest is pretty self explanatory. 

It means you could simply place your phone's charging port close to the charging cable, and it'll snap in with the power of magnets.

And it'll disconnect without causing any damage if you pull on your phone when it's still charging.

And there's even a little status light, just like you'd find on a MacBook's MagSafe charging connector.

The campaign is barely a quarter of the way through with 24 days remaining, and Znaps has already amassed $437,295 of its $94,221 goal. That's 464% of Znap's goal, so saying there's some interest is an understatement. 

Watch the rest of Znaps' Kickstarter campaign video here:

SEE ALSO: A secret option in your Android phone can help make it work faster

Join the conversation about this story »

NOW WATCH: How to make your iPhone louder using just household items

As part of the 2015 "PLAY" sale, Journey is going to be re-released on the PlayStation 4 tomorrow for $14.99 ($11.99 for Plus members). For the most part this is the same exact game most of you have already played, but with enhanced visuals, which you can view in the gameplay video above. Just like fl0w and Flower for PS4, Journey is also Cross-Buy.

Everyone has already talked ad nauseum about the game for years, but having played through it again on PS4, my opinion remains relatively unchanged. It's an incredible looking adventure, and is still one of the strongest arguments for games as art, but the existential narrative is a bit overrated, and the platforming and puzzle solving, still too simplistic.

Lobster & Bacon Corn Fritters with Jalapeno-Honey Aioli. Limited on Filler and Jam Packed with Phenomenal Flavor, You Need These Crispy Fritters in Your Life! {recipe}

craving more? check out TasteSpotting

Spicy meatballs with ghost chilli oil — spicy, delicious & easy dinner that can be prepared ahead {recipe}

craving more? check out TasteSpotting

This is amazing.

Using simple imagery and Google’s layered artificial neural network, the deep stereo technology can create some relatively fluid footage of a scene using two or more pictures of the location and then “creating” what is missing in between to make everything look like it was actually filmed. Just look at the video and be amazed.

[John Flynn]

The post Deep Stereo Technology Takes Static Pictures and “Animates” Them [Video] appeared first on Geeks are Sexy Technology News.

submitted by WLH7M [link] [185 comments]

submitted by faizdar [link] [747 comments]

submitted by dirtydayboy [link] [1208 comments]

submitted by Vmoney1337 [link] [603 comments]

submitted by Vmoney1337 [link] [894 comments]

submitted by mshelbz [link] [991 comments]

submitted by Brian_Sun_ [link] [282 comments]

via

Good luck with that!

The post How do I convert to… appeared first on Bits and Pieces.

submitted by mormotomyia [link] [159 comments]

submitted by micsnasty34 [link] [145 comments]

submitted by austapasta
[link] [868 comments]

You know you’re in some deep sludge of brown goo when a bike race starts and pretty much everyone around you immediately loses control and crashes. That’s what happens when you ride a bike downhill on a glacier. That’s what happens when you ride the Megavalanche race.

Read more...

I’m starting to feel a little dizzy.

Read more...

Google’s self-driving prototypes have been tooling around on real roads for some time now, and like cars that are driven by people, they’ve had a few bumps and traffic incidents, but no one has gotten hurt. That’s all changed now, as the company reports one of its driverless vehicles has been involved in an accident that involved injuries for the first time.

The collision happened near Google’s home in Mountain View, CA, where 20 of its self-driving prototypes have been cruising around recently. In this case, the company’s Lexus SUV bearing sensors and cameras was hit from the back, Chris Urmson, head of Google’s self-driving car program, wrote in a blog post on Thursday, and three Google employees riding inside to monitor the test car complained of minor whiplash as a result.

They were checked out at a hospital and later cleared to go back to work after the July 1 collision, Google says, while the driver of the other car also complained of neck and back pain.

Because these cars are just prototypes and can’t drive around without a human behind the wheel just yet, a Google employee is required to be behind the wheel. Then there’s usually someone in the front passenger seat to take notes and in this case, there was another Googler in the back seat along for the ride.

According to an accident report that Google filed with the California Department of Motor Vehicles about the July 1 crash, the driverless SUV was going about 15 mph in self-driving mode behind two other cars, as they all approached an intersection with a green light. When the first car slowed to a stop so it wouldn’t block the intersection, the other car and Google’s vehicle also stopped.

About a second later, a fourth vehicle hit Google’s car from the back at about 17 mph, with the driverless car’s on-board sensors showing the other car did not brake.

Though police responded, they didn’t file an accident report. This is a good thing, says Google’s Urmson.

“We’re seeing first-hand the true measure of how distraction is impacting driving,” he told USA Today. “None of our accidents rise to the level of police reports. So what we are experiencing is what the road is really like.”

The company started issuing monthly reports about the collisions and accidents in June (including a list of all the accidents before then), noting that the company’s cars hadn’t been the cause of any of the previous collisions.

Out of a total of 14 accidents in the last six years and 1.9 million miles of testing, the company says 11 of those involved Google cars getting rear-ended.

Urmson adds in his post that the SUVs “are being hit surprisingly often” by distracted drivers, who could be looking at their phones.

“The clear theme is human error and inattention,” Urmson wrote. “We’ll take all this as a signal that we’re starting to compare favorably with human drivers.”