Displaying 10 most recent entries of 10 freshness feeds
Created and Directed by: Charlie Todd
Executive Producers: Alan Aisenberg, Justin Ayers, Juan Cocuy, Andrew Soltys, and Charlie Todd
Co-Producers: Aleks Arcabascio, Isabel Lopez
Associate Producer: Michelle F. Thomas
Production Coordinator: Dave Szarejko
Production Assistants: Jonathan Portee, Alex Augustyniak, Jamel Francis, Dave Greenberg, Chris Kelly, Adam Manison, Alexis Trevizo
Director of Photography: Justin Ayers
Camera Operators: Alex Crowe, Mike Doyle, Chloe Smolkin, Spencer Thielmann
Hidden Camera Technicians: Marius Becker, Ryan Hamelin
1st Camera Assistants: Erin Trout, Katie Voss
2nd Camera Assistants: Goran Mrvic, Kelli Wilcoxen
Still Photography: Arin Sang-urai
Gaffer: Ted Maroney
Key Grip: Cory Beisser
Best Electric: Seth Margolies
Best Grip: Andrew Naugle
G&E Swing: Eric Ambrosino
Production Designer: Anthony Henderson
Art Director: Sydney Bowers
Production Sound Mixer: Alan Kudan
A2: Artur Szerejko
Sound Intern: Lucas Kadar
Editor: Matt Braunsdorf
Assistant Editor: Ryan Connors
Post-Production Sound Mixer: Arjun Sheth
Coloring Facility: Irving Harvey
Music by: Tyler Walker
Trivia Consultants:Ross White and Mackensie Pless
Special Thanks: One Star Bar (Joe DiPietro, Joe Cordi), Tony Hightower
Host: Yoni Lotan
None of Your Quizness: Lou Gonzalez, Chrissie Gruebel, Brian Urreta
For our latest mission, we surprised random trivia teams by turning a regular bar trivia night into a high stakes game show.
This project was a collaboration with the new movie Game Night. Our first task was to find the perfect bar. We needed a space that had a back room where we could build our set, and a basement where we could set up our control room. “one star” bar in Chelsea ended up being perfect.
Installing a truss for our lights in the back room.
Building the set.
The control room in the basement.
For the “returning champions” None of Your Quizness, we cast our improviser friends Lou Gonzalez, Chrissie Gruebel, and Brian Urreta from the great improv team The Mannequin Room. They were secretly given all of the answers in advance, allowing us to make sure the real people we were surprising always won.
All of the teams we surprised were real, existing trivia teams. We worked with TriviaNYC to find the best teams. TriviaNYC actually runs trivia games at “one star” bar already, but we specifically asked them to help us find teams that had never played at “one star.” This way they wouldn’t know the bar had a back room, and they would be less likely to spot our hidden cameras in the front. We invited the teams to come at different times throughout the night, so we could surprise them one by one. They thought they were coming to a normal bar trivia event.
The reactions when the teams walked through the curtain were so much fun. On one side of the curtain was a normal bar, and on the other there was a full game show set with lights, theme music, a cheering studio audience, and an announcer introducing their actual team name and telling them to “come on down.”
Our friend Yoni Lotan played both the bartender and the host of the game show.
Yoni, as “Alex Martindale,” announces that the winner will receive a $1,000 prize.
The trivia consisted of 10 main round questions and then one final question. The final question was “final Jeopardy” style where the teams could wager as many of their points as they liked. (The video cuts this aspect out for simplicity.) We arranged it so the “returning champions” would always wage 100% of their points and get the answer wrong, ensuring that our challengers would always win.
Celebrating a correct answer.
Realizing they won the game!
Our confetti cannon was probably a little too big for the room. It was ridiculously powerful and over-the-top.
Our “stage manager” Dave Szarejko brings out the $1,000 prize. We really did give each team $1,000.
TAGS: featured, missions
In "The House that Spied on Me," Kashmir Hill outfits her home to be as "smart" as possible and writes about the results.
TAGS: encryption, internetofthings, privacy, spyware, surveillance
Not to be one-upped by the likes of Google, Amazon, or Apple, Samsung introduced its own virtual assistant service called “Bixby” ahead of the release of the Samsung Galaxy S8/S8+. At launch, Bixby was rather incomplete especially since the voice command feature took several weeks to roll out, but Samsung is continuing work on Bixby with a promise of greater functionality, availability, and openness. While we have seen hints at how Samsung might further integrate Bixby with its Samsung Experience UX in the upcoming Galaxy S9, we have recently learned of a totally unintended, yet hilarious, “feature” in Bixby: interfering with an obscure baseball card tracking app.
The open source application, called “Baseball Card Tracker,” is available for free from the Google Play Store. It’s a fairly simple app for a pretty niche audience of users. It doesn’t have a beautiful Material Design interface, but it doesn’t really need to because it gets the job done for its users.
The developer of the application recently upgraded his smartphone to the Samsung Galaxy S8, but was perplexed when he discovered that his simple application would not install on his new phone. Now, a regular user might fire off an angry email at a developer, but a developer would connect to their phone via ADB and collect a logcat to diagnose the problem. So what did he discover?
His Baseball Card Tracker app fails to install on his new Galaxy S8 because it is trying to declare a permission, called
bbct.android.lite.permission.READ, which is already owned by a package called
com.samsung.android.bixby.agent (also known as Bixby Voice). Let’s break this down some more.
Every Android application has what is called a “Manifest” which is an XML file that contains a list of activities, receivers, services, and a list of permissions that the app can declare. What we’re concerned with are the permissions defined in the Manifest. An application can either declare which permissions they would like to use (
<uses-permission> tag) or they can define their own custom permissions (
<permission> tag) that other apps must declare before they can call that app.
For example, if an application wants to read the contacts on your device, the app must declare the
android.permission.READ_CONTACTS permission in its Manifest.
By declaring this permission, an application can then read your device’s contacts database. Note that since this is considered a “dangerous” permission, starting in Android Marshmallow the developer has to request this permission be granted at runtime rather than at installation.
Now consider the case where an application developer might want to implement a custom permission. The popular automation app called Tasker implements a permission called
net.dinglisch.android.tasker.PERMISSION_RUN_TASK which other apps must declare in their Manifest before they are allowed to directly run Tasker’s tasks or actions.
<permission android:description="@string/permission_descr_run_tasks" android:label="@string/permission_label_run_task" android:name="net.dinglisch.android.tasker.PERMISSION_RUN_TASKS" android:protectionLevel="normal"/>
The Baseball Card Tracker app in question also implements a custom permission which is named
bbct.android.lite.permission.READ. This is done so another app of theirs can declare this permission and then read the card tracking database of the user.
The same permission cannot be declared by two different apps. For whatever reason, Samsung’s Bixby Voice application is declaring the same permission that the Baseball Card Tracker app is attempting to declare for itself. However, since Bixby Voice is already pre-installed on the Galaxy S8, this means that the Baseball Card Tracker app cannot be installed as it uses the same permission name.
Line 9: <permission android:name="com.samsung.android.bixby.agent.permission.READ_LANGUAGE" android:protectionLevel="signatureOrSystem"/> Line 10: <permission android:name="com.samsung.android.bixby.agent.permission.WRITE_LANGUAGE" android:protectionLevel="signatureOrSystem"/> Line 11: <permission android:name="com.samsung.android.bixby.agent.permission.ACCESS_SETTING" android:protectionLevel="signatureOrSystem"/> Line 12: <permission android:name="com.samsung.android.bixby.agent.permission.BIXBY_SERVICE_AVAILABLE_CHANGE" android:protectionLevel="signatureOrSystem"/> Line 13: <permission android:name="com.samsung.android.bixby.agent.permission.GET_SERVICE_ID" android:protectionLevel="signatureOrSystem"/> Line 14: <permission android:name="com.samsung.android.bixby.apphome.permission.CONTENT_SYNC" android:protectionLevel="signatureOrSystem"/> Line 15: <permission android:name="com.samsung.android.bixby.apphome.READ_PERMISSION" android:protectionLevel="signatureOrSystem"/> Line 16: <permission android:name="com.samsung.android.bixby.apphome.WRITE_PERMISSION" android:protectionLevel="signatureOrSystem"/> Line 17: <permission android:name="com.samsung.android.bixby.apphome.permission.VIEW" android:protectionLevel="signatureOrSystem"/> Line 82: <permission android:name="com.samsung.android.bixby.permission.WAKEUP_LAUNCH_BIXBY" android:protectionLevel="signatureOrSystem"/> Line 83: <permission android:name="com.samsung.android.bixby.ACCESS_SERVICE" android:protectionLevel="signatureOrSystem"/> Line 84: <permission android:name="com.samsung.android.bixby.agent.permission.RECEIVE_BIXBY_VIEW_STATE" android:protectionLevel="signatureOrSystem"/> Line 85: <permission android:name="com.samsung.android.bixby.agent.permission.READ_LEARNING" android:protectionLevel="signatureOrSystem"/> Line 86: <permission android:name="com.samsung.android.bixby.agent.permission.WRITE_LEARNING" android:protectionLevel="signatureOrSystem"/> Line 87: <permission android:name="bbct.android.lite.permission.READ"/> Line 88: <permission android:name="com.samsung.android.bixby.agent.permission.TEXT_TEST" android:protectionLevel="signatureOrSystem"/> Line 89: <permission android:name="com.samsung.android.bixby.agent.permission.LAUNCH_BIXBY_VOICE" android:protectionLevel="signatureOrSystem"/> Line 90: <permission android:name="com.samsung.android.bixby.agent.permission.BIXBY_SIMULATOR" android:protectionLevel="signatureOrSystem"/> Line 91: <permission android:name="com.samsung.android.bixby.permission.BIXBY_DICTATION" android:protectionLevel="signatureOrSystem"/> Line 92: <permission android:name="com.samsung.android.bixby.agent.permission.BIXBY_ALARM" android:protectionLevel="signatureOrSystem"/> Line 93: <permission android:name="com.samsung.android.bixby.agent.permission.READ_APPCHOOSER" android:protectionLevel="signatureOrSystem"/> Line 94: <permission android:name="com.samsung.android.bixby.agent.permission.WRITE_APPCHOOSER" android:protectionLevel="signatureOrSystem"/> Line 95: <permission android:name="com.samsung.android.bixby.permission.WAKEUP_SUGGEST_SENSITIVE" android:protectionLevel="signatureOrSystem"/> Line 96: <permission android:name="com.samsung.android.bixby.agent.permission.BIND_AGENT"/> Line 97: <permission android:name="com.samsung.android.bixby.agent.permission.READ_PERMISSION"/> Line 131: <permission android:name="com.samsung.android.bixby.bridge.provision.READ_PERMISSION" android:protectionLevel="signatureOrSystem"/> Line 132: <permission android:name="com.samsung.android.bixby.bridge.provision.WRITE_PERMISSION" android:protectionLevel="signatureOrSystem"/> Line 160: <permission android:description="@string/permission_description_em" android:label="Bixby Agent Service Access Permission" android:name="com.samsung.android.bixby.agent.permission.BIXBY_AGENT" android:protectionLevel="signatureOrSystem"/> Line 161: <permission android:description="@string/permission_description_es" android:label="@string/permission_label_es" android:name="com.samsung.android.bixby.agent.permission.APP_SERVICE" android:protectionLevel="normal"/>
What makes this all the more confusing is why the Bixby app is declaring this permission at all! If you decompile the app and take a look at all of the custom permissions that Bixby declares, all of them except for one follow the “
com.samsung.android.bixby” naming convention. That exception is of course the permission found in the poor developer’s Baseball card app.
Commonsware (who first pointed out this hilarious mishap) seems to think the cause is that some developers at Samsung copied code snippets from Stack Overflow. The developer of the app in question posted snippets of his code back in 2013, but has since edited it to genericize the post. We’re unlikely to find out an exact reason why this interference happened, however. It’s possible, but highly unlikely, that it was a total coincidence.
This ultimately has absolutely no effect on any average user. Sure, it might affect the few users of the app who own a Samsung Galaxy S8, S8+, Note8, or who wish to own the upcoming Galaxy S9/S9+, but the fix is relatively simple. For the developer, he would need to rename the permission in his Manifest (or get rid of it entirely) so his app no longer “interferes” with Samsung Bixby. Of course, it isn’t his fault that this is happening in the first place, but he has little recourse in the matter.
Commonsware argues that this little mishap is a great example for why developers need to check their Manifest before shipping an app. I recommend you read his blog post for more details on that, but I just wanted to share this ultimately inconsequential story because of its absurdity. The poor developer!
TAGS: developments, featured, full xda, news, xda feature, samsung bixby, samsung galaxy note 8, samsung galaxy s8, samsung galaxy s8 plus
Wow. Word traveled fast about my knee injury.
As I mentioned on Friday, I’m in a lot of pain. After several days of being unable to walk, though, I am happy to report that I’m slowly on the mend. Thank you to everyone who sent kind messages. It really meant a lot as I was stuck in bed. Thank you even more for your long, thoughtful comments below Friday’s com—
What’s that? As of the... [read more]
Just four days left to submit your proposal for BAHFest London!
TAGS: diy, drones, video
An industry survey has revealed that almost half of prospective buyers believe it will take them seven years or more to raise the deposit they need to purchase a season ticket allowing them to travel to work by train.
‘In the current economic climate, how anyone can expect me to raise £4,360 to travel into London for the year is beyond me,’ said Sally Dyson of Stevenage. ‘I got a mortgage for my home but no one seems prepared to lend me the money I need to get to work. Until the banks start lending again people like me can’t even hope to get on the season ticket ladder.’
Those that have managed to secure loans for season tickets say it was a rigorous process. ‘It took a long time to persuade a bank that lending me the money to get from Orpington to London Victoria was a wise investment,’ said Darren Tulley. ‘They did a full credit check and wanted to see a year’s worth of payslips and bank statements. In the end they only agreed when I put my house up as collateral.’
But for many moving from renting a monthly return to owning an annual season ticket remains only a dream. ‘My dad left me his old season ticket to use as equity, but it was on the market for nine months and I didn’t even have one viewer,’ complained Mark Costa of Colchester in Essex. ‘In the end I had to walk to work. I set off first thing Monday and got to London by Wednesday morning, but by the time I’d opened a few emails it was time to leave again for the weekend. Luckily now it’s a much shorter commute to the Jobcentre.’
While season ticket price increases have been limited this year, rail companies insist that train tickets remain a sound investment. ‘It’s still a buyer’s market,’ said Michael Roberts, chief executive of the Association of Train Operating Companies. ‘Just look at the off-peak returns we sold in 2011 – if we were selling them today they’d fetch at least 20% more.’
TAGS: from the archives, 30-12-12, comedy, commuters, estate agent, house buyers, parody, property market, rail fares, rail travel, satire, season ticket, spoof news, trains