Shared posts

13 Jan 21:53

Duo video calls can now reach users without the app

by Nick Sarafolean

Over the past two years, Google introduced two messaging services that serve as replacements or accompaniments to Hangouts, which no longer serves as Google’s messaging hub. The first of these new services is Google Duo, a simple app that allows users to make video calls to other individual users. The hindrance of the service has been that many users don’t have Duo installed. That’s now changing, as Duo video calls can now be made to users without the app.

The feature, powered by Google Play’s App Preview Messaging, will allow non-Duo users to see the video call much the same as if they were using the Duo app, including a preview of what the caller’s camera is displaying. Once a call is ended, non-Duo users will see a notification prompt inviting them to download Duo for future use as well as a small notification that will allow users to block the caller from making future calls. The feature only works with Android devices and, for now, seems limited in which devices can receive calls. Phone contacts that can receive Duo calls will now appear in your Duo contacts list without an invite symbol next to them.

Alongside the change to Duo, Google is improving Allo, its messaging app. Google has used App Preview Messaging since its inception to send messages to non-Allo users. The messaging pop-ups were unsightly, but that has been refined in the latest version, which changes the pop-ups to resemble the Allo app, though many of Allo’s key features are unavailable.

With improvements to its messaging services, Google is clearly hoping to drive an uptick in adoption. In a saturated messenger market, however, that could prove to be a tough battle.

Do you use Allo or Duo? If so, leave a comment below letting us know what you think of these changes!

13 Jan 02:44

instagram / facebook

13 Jan 02:43

instagram / facebook

13 Jan 02:43

FREE games from the Humble Trove! Starting now, we’re...



FREE games from the Humble Trove! 

Starting now, we’re giving everyone access to six DRM-free Humble Original games. They’ll only be publicly available until February 2, so get them now!

Want more? Active Humble Monthly subscribers can access the full Humble Trove of more than forty DRM-free titles, including our Humble Originals. Just added: Torchlight and Torchlight II!

12 Jan 16:13

Sleepover

Sleepover Alfred is the coolest 'dad' ever!









See more: Sleepover
12 Jan 12:53

Wanna See a Neat Trick?

by alex

Wanna See a Neat Trick?

11 Jan 19:32

Photo









11 Jan 19:32

Nerdy Relationships: Movies vs Real Life

Nerdy Relationships: Movies vs Real Life

 

JHallComics made this funny web comic for Dorkly and pretty much nailed what nerdy relationships are like in movies vs. real life...

Nerdy Relationships: Movies vs Real Life

Nerdy Relationships: Movies vs Real Life

Nerdy Relationships: Movies vs Real Life

Nerdy Relationships: Movies vs Real Life

Nerdy Relationships: Movies vs Real Life

Artist: JHallComics for Dorkly

Follow us on:
 

January 11 2018
11 Jan 12:48

Me Time.

by Chris Grabowski
This was pretty much me last night. It's kinda embarrassing that if I stay awake past 9 I'm pretty much wrecked the next day...

Love,
   Chris.
Facebook.com/PoorlyDrawnThoughts
Instagram.com/PoorlyDrawnThoughts
Twitter.com/PoorlyDrawnGuy
11 Jan 12:48

#1663 – Just stress

by Chris

#1663 – Just stress

11 Jan 12:48

HTML 5.2 is Done, HTML 5.3 is Coming

by Geoff Graham

The W3C has completed its second round of HTML5 recommendations for implementation. The entire announcement is worth a read because there are interesting tidbits that provide more context and personnel changes within W3C, but the highlights of this recommendation are nicely summed up:

Many of the features added integrate other work done in W3C. The Payment Request API promises to make commerce on the Web far easier, reducing the risks of making a mistake or being caught by an unscrupulous operator. New security features such as Content Security Policy protect users more effectively, while new work incorporated from ARIA helps developers offer people with disabilities a good user experience of their applications.

There are also semantic changes to HTMl elements that are worth noting:

Clarifications and bug fixes bring the HTML Recommendation closer to what has been deployed recently. The definition for the main element has been updated to support modern responsive design patterns, the style element can be used inside the body element. Numerous constraints on code have been loosened, while where necessary for interoperability or security a few have been carefully reinforced.

And, spoiler alert! HTML 5.3 is officially in its first public working draft.

Direct Link to ArticlePermalink

HTML 5.2 is Done, HTML 5.3 is Coming is a post from CSS-Tricks

11 Jan 12:48

Giving hope to orphans with our new game bundle: Hope is on the...



Giving hope to orphans with our new game bundle:

Hope is on the way with Tripwire and friends! You’ll get awesome games like Rising Storm 2: Vietnam, Killing Floor 2, BLACKHOLE, and more. Plus, your purchase will support support Change30, a charity providing critical resources to orphans in need.


Assets for Press and Partners

07 Jan 19:40

hide

by Lunarbaboon
07 Jan 04:41

Star Wars Sarlacc Baby Lounger

by erin@dudeiwantthat.com (Erin Carstens)
07 Jan 00:32

Christmas Present Mix-up

by CommitStrip

07 Jan 00:32

Unihertz Jelly Phone Pro review

by Dima Aryeh

The Unihertz Jelly Phone Pro is a unique phone. The company has packed a full Android experience in a package that is 92.3mm x 43mm x 13.3mm. The device features a 2.45-inch 240×432 display, a quad core 1.1GHz processor, 2GB of RAM, 16GB of storage with a microSD card, dual SIM slots, an 8MP autofocus rear camera, a 2MP front-facing camera, and a 950mAh battery. It even has GPS and LTE as well as the mythical headphone jack. Yep, it’s already better than many flagships.

This device isn’t really meant to replace your main phone, according to Unihertz. It’s more of a backup and travel phone. With dual SIM operation and all the features you would expect from a phone, it technically can replace your phone. But there are a few obvious drawbacks to using it.

Jelly-Phone-Pro-6

First up, let’s talk about form factor. The phone is minuscule; it’s made just small enough to fit into the coin pocket on your jeans. It’s round and slippery but fits into your hand surprisingly well. The 2.45-inch display can be a bit small if you have big thumbs but it’s surprisingly usable. Typing is another issue, but carefully pecking out letters is not nearly as bad as you’d think. You also get a removable battery and the three card trays underneath.

Jelly-Phone-Pro-

The display itself doesn’t look great but it’s not terrible. There’s a bit of light bleeding up top and the colors are pretty washed out and warm. It’s one of those displays that looks inset, from the days before Samsung’s SAMOLED displays popularized the thin glass and slim digitizer approach. Nonetheless, it’s a decent resolution and doesn’t look bad at all. There is no oleophobic coating on the display.

Below the screen you get three buttons: back, home, and recent tasks. This is the same layout we’re all used to, and having physical keys definitely helps when you’ve got such a tiny display (although you can disable them and use an on-screen nav bar if you’d like). The home button doubles as an RGB notification light and it’s ridiculously bright. Probably too bright, actually, but the colors are very pretty and vivid. Above the display is the earpiece which is surprisingly quiet. Phone calls are hard to hear, so using some headphones with the Jelly Pro is a good idea.

Jelly-Phone-Pro-2

On the back, behind the glossy fingerprint magnet plastic, you’ll find a single speaker. It’s a bit tinny and not very loud, but it’s decent.

Overall the build quality is quite good. The rear is flexy but there aren’t creaks or bends that indicate a poorly built phone. Even flexing it JerryRigEverything-style causes no issues.

Jelly-Phone-Pro-5

Software-wise, you’re getting nearly stock Android 7.0 Nougat. It’s great to see an unadulterated build of Android on this device, especially where every bit of performance matters. The launcher is a bit different and there are a few features like the ability to disable the status bar, a battery saving mode, “DuraSpeed” for maintaining current app performance, and a few other settings tweaks. One shocking feature that’s present is split screen; yes, it’s part of stock Android, but I can’t believe it was kept in. Otherwise, it’s the AOSP we know and love, complete with Play Store access.

Being AOSP, it’s shockingly smooth! Animations are generally fluid and pretty. This comes as a huge surprise considering the budget hardware. It’s not fast, but it’s relatively smooth.

App loading times are pretty slow, often taking over a second or more. Performance in apps is a bit stuttery but decent. Using one app at a time is a good experience but loading multiple running apps quickly slows things down. Nonetheless, it remains surprisingly usable for the price and size.

Jelly-Phone-Pro-3

You expect the camera to be terrible, don’t you? I can’t believe I’m saying this, but it isn’t terrible. In fact, it’s downright decent when there is plenty of light outside. The plastic lens distorts a bit, but landscape shots look very decent. There is detail, a surprising amount of sharpness, and bright (but inaccurate) colors.

Once things get dark, the photos become terrible. They’re underexposed, blurry, and grainy.

Jelly Phone Pro sample photos

The battery life is a serious weak point of the device. You’re unlikely to get to the end of the day with the standard battery mode. The optional battery saving modes do help quite a bit, but I still found myself charging the device once or twice a day with light to normal use. Again, it’s not meant to be your daily phone. Its tiny battery will be easily charged by a battery bank, though.

The Unihertz Jelly Phone Pro is not a daily driver. Yet I can’t help but love it. It’s tiny yet fully functional; it should be terrible for the price, but it really isn’t. It even produces decent photos in good light! It’s hard not to pick one up as a backup phone.

07 Jan 00:31

Photo



07 Jan 00:31

Meltdown and Spectre

New zero-day vulnerability: In addition to rowhammer, it turns out lots of servers are vulnerable to regular hammers, too.
07 Jan 00:31

Notice Me Senpai

Notice Me Senpai Cute.



See more: Notice Me Senpai
07 Jan 00:31

Scary Movie

by The Awkward Yeti

121617_ScaryMovie

07 Jan 00:31

There’s a problem with the code

by CommitStrip

07 Jan 00:31

Answering your questions about “Meltdown” and “Spectre”

by Matt Linton

This week, security vulnerabilities dubbed “Spectre” and “Meltdown” made news headlines. On Wednesday, we explained what these vulnerabilities are and how we're protecting you against them.

Since then, there's been considerable discussion about what this means for Google Cloud and the industry at large. Today, we’d like to clear up some confusion and highlight several key considerations for our customers.

What are “Spectre” and “Meltdown”?


Last year, Google’s Project Zero team discovered serious security flaws caused by “speculative execution,” a technique used by most modern processors (CPUs) to optimize performance.

Independent researchers separately discovered and named these vulnerabilities “Spectre” and “Meltdown.” 

Project Zero described three variants of this new class of speculative execution attack. Variant 1 and Variant 2 have been referred to as “Spectre.” Variant 3 has been referred to as “Meltdown.” Most vendors are referring to them by Common Vulnerabilities and Exposures aka “CVE” labels, which are an industry standard way of identifying vulnerabilities.

security-1

There's no single fix for all three attack variants; each requires protection individually.

Here's an overview of each variant:

  • Variant 1 (CVE-2017-5753), “bounds check bypass.” This vulnerability affects specific sequences within compiled applications, which must be addressed on a per-binary basis. This variant is currently the basis for concern around browser attacks, Javascript exploitation and vulnerabilities within individual binaries.

  • Variant 2 (CVE-2017-5715), “branch target injection.” This variant may either be fixed by a CPU microcode update from the CPU vendor, or by applying a software protection called “Retpoline” to binaries where concern about information leakage is present. This variant is currently the basis for concern around Cloud Virtualization and “Hypervisor Bypass” concerns that affect entire systems.

  • Variant 3 (CVE-2017-5754), “rogue data cache load.”  This variant is the basis behind the discussion around “KPTI,” or “Kernel Page Table Isolation.” When an attacker already has the ability to run code on a system, they can access memory which they do not have permission to access.

For more information on these variants, please read this week’s Google Security post.

Am I protected from Spectre and Meltdown?  


Google’s engineering teams began working to protect our customers from these vulnerabilities upon our learning of them in June 2017. We applied solutions across the entire suite of Google products, and we collaborated with the industry at large to help protect users across the web.

G Suite and Google Cloud Platform (GCP) are updated to protect against all known attack vectors. Some customers may worry that they have not been protected since they were not asked to reboot their instance. Google Cloud is architected in a manner that enables us to update the environment while providing operational continuity for our customers. Via live migration we can patch our infrastructure without requiring customers to reboot their instances.

Customers who use their own operating systems with Google Cloud services should continue to follow security best practices and apply security updates to their images just as they would for any other operating system vulnerability. We're providing an up-to-date reference on the availability of vendor patches for common operating systems on our GCE Security Bulletin page.


I’ve heard that Spectre is nearly impossible to protect against. Is this true?


There has been significant concern in particular about “Spectre.” The use of the name “Spectre” to refer to both Variants 1 and 2 has caused some confusion over whether it's “fixed” or not.

Google Cloud instances are protected against all known inter-VM attacks, regardless of the patch status of the guest environments, and attackers do not have access to any customers’ data as a result of these vulnerabilities. Google Cloud and other public clouds use virtualization technology to isolate neighboring customer workloads. A virtualization component known as a hypervisor connects the physical machine to virtual machines. This hypervisor can be updated to address Variant 2 threats. Google Cloud has updated its hypervisor using “Retpoline,” which addresses all currently known Variant 2 attack methods.

Variant 1 is the basis behind claims that Spectre is nearly impossible to protect against. The difficulty is that Variant 1 affects individual software binaries, so it must be handled by discovering and addressing exploits within each binary.

Risks that Variant 1 would pose to the infrastructure underpinning Google Cloud are addressed by the multiple security controls that make up our layered “defense in depth” security posture. Because Google is in full control of our infrastructure from the hardware up to our secure software development practices, our infrastructure is protected against Variant 1. You can read more about the security foundations of our infrastructure in our whitepaper.

We work continuously to stay ahead of the constantly-evolving threat landscape and will continue to roll out additional protections to address potential risks.

As a user of the public cloud, am I more vulnerable to Spectre and Meltdown than others?

In many respects, public cloud users are better-protected from security vulnerabilities than are users of traditional datacenter-hosted applications. Security best practices rely on discovering vulnerabilities early, and patching them promptly and completely. Each of these activities is aided by the scale and automation that top public cloud providers can offer — for example, few companies maintain a several-hundred-person security research team to find vulnerabilities and patch them before they're discovered by others or disclosed. Having the ability to update millions of servers in days, without causing user disruption or requiring maintenance windows, is difficult technology to develop but it allows patches and updates to be deployed quickly after they become available, and without user disruption that can damage productivity.

Spectre and Meltdown are new and troubling vulnerabilities, but it’s important to remember that there are many different types of threats that Google (and other cloud providers) protect against every single day. Google’s cloud infrastructure doesn’t rely on any single technology to make it secure. Our stack builds security through progressive layers that deliver defense in depth. From the physical premises to the purpose-built servers, networking equipment, and custom security chips to the low-level software stack running on every machine, our entire hardware infrastructure is Google-controlled, -secured, -built and -hardened.

Is performance impacted?

On most of Google’s workloads, including our cloud infrastructure, we've seen negligible impact on performance after applying remediations. This was explained further in our follow-up Security blog post on January 4.

There are many conflicting reports about patch impacts being publicly discussed. In some cases, people have published results of tests that focus solely on making API calls to the operating system, which does not represent the real-world scenario that customer software will encounter. There's no substitute for testing to determine for yourself what performance you can expect in your actual situation. We believe solutions exist that introduce minimal performance impact, and expect such techniques will be adopted by software vendors over time. We designed and tested our mitigations for this issue to have minimal performance impact, and the rollout has been uneventful.

Where can I get additional information?

  • Our Support page offers a list of affected Google products and will be updated with their current status of mitigation against these risks

  • Our GCP Security Bulletins page will provide notifications as other operating system maintainers publish patches for this vulnerability and as Compute Engine releases updated OS images

07 Jan 00:31

Photo















07 Jan 00:31

Comic for 2018.01.06

07 Jan 00:31

When Dad Buys Toys - Comic

When Dad Buys Toys - Comic

 

LOL! Messy Cow drew this cute comic about what happens when Dads buy toys for the kids...

When Dad Buys Toys - Comic
When Dad Buys Toys - Comic
When Dad Buys Toys - Comic
When Dad Buys Toys - Comic

Artist: Messy Cow

Follow us on:
 

January 06 2018
05 Jan 14:44

The Verge: ‘Chrome Is Turning Into the New Internet Explorer 6’

by John Gruber

Tom Warren, writing for The Verge:

Whether you blame Google or the often slow moving World Wide Web Consortium (W3C), the results have been particularly evident throughout 2017. Google has been at the center of a lot of “works best with Chrome” messages we’re starting to see appear on the web. Google Meet, Allo, YouTube TV, Google Earth, and YouTube Studio Beta all block Windows 10’s default browser, Microsoft Edge, from accessing them and they all point users to download Chrome instead. Some also block Firefox with messages to download Chrome.

Good story, but I think it’s a little weird to tell the history of Chrome without mentioning WebKit until late in the story.

05 Jan 13:04

Custom minifigs of Star Trek: The Next Generation characters

by Jason Kottke

Star Trek Minifigs

Oh these are cool: custom-made minifigs of all your favorite Star Trek:TNG characters. The Wesley Crusher one is kinda funny, but Wil Wheaton makes a good case as to why it’s unfair to the character. And it turns out, you can get custom minifigs for just about everything, from LeBron James to Game of Thrones to yourself. (via io9)

Tags: Legos   Star Trek   TV
03 Jan 16:00

LG and Samsung don’t slow down your old phones due to aging batteries

by Dima Aryeh

After Apple admitted to slowing down iPhones with older batteries, a lot of people worried that this was an industry standard process. Fortunately, we have learned that this is not the case. HTC and Motorola both stated that neither of them does this.

Today, LG and Samsung has made similar statements. Here is LG’s statement:

Never have, never will! We care what our customers think.

And Samsung’s:

Product quality has been and will always be Samsung Mobile’s top priority. We ensure extended battery life of Samsung mobile devices through multi-layer safety measures, which include software algorithms that govern the battery charging current and charging duration. We do not reduce CPU performance through software updates over the lifecycles of the phone.

Four of the major smartphone manufacturers have now said that they will not slow down your phone if your battery isn’t performing like new. This leaves a few more like Google, Nokia, and Blackberry, but it’s unlikely that any of them do this.

Let’s hope such anti-consumer behavior sticks with Apple, unlike the death of the headphone jack (although Motorola really started that one).

02 Jan 19:45

Positivity

by Brian Russell

Be the change you want to see in the world…but sudden changes to your personality can be jarring and terrifying for others.

The post Positivity appeared first on Underfold Comics.

30 Dec 19:07

Photo