Facebook Messenger Adds Group Video Chat

Facebook Messenger is on a roll, pushing out new features in rapid succession as 2016 comes to a close.

A week after releasing a new, Snapchat-style camera, the wildly popular messaging app is introducing group video chat, its most requested feature. Group video chat on Messenger will be available globally, both on iOS and Android, and will start rolling out Monday.

Messenger&;s impressive run of new feature releases (it&039;s also experimenting with AI-powered contextual suggestions) is evidence Facebook is unwilling to simply let it ride the coattails of the 1.79 billion user core app it&039;s inherently tied to. Instead, as Messenger ships fun new features, Facebook is proving the wisdom of spinning out the app in 2014, a move initially met with user backlash.

Group video chat on Messenger will support up to six videos at a time, but up to 50 people can watch and, if they so choose, join via voice, stickers and the like. A video icon will now appear at the top right of group conversations, and tapping on it will alert group members and give them the choice to join.

Group video chat is having a bit of a moment right now. Houseparty, a group video chat app by the creators of Meerkat, just raised $50 billion. And Fam, an iMessage group video app, seems to be taking off as well.

One big question about Messenger remains: how will it make money? At this point, the app is very popular — claiming over 1 billion users — but it&039;s not contributing meaningfully to Facebook&039;s bottom line. Facebook is anticipating a slowdown in ad load growth, so it may soon need to make a revenue push inside Messenger, something that lead to even more changes. But in the meantime, enjoy your video chats.

Quelle: <a href="Facebook Messenger Adds Group Video Chat“>BuzzFeed

Facebook Messenger Adds Group Video Chat

Facebook Messenger is on a roll, pushing out new features in rapid succession as 2016 comes to a close.

A week after releasing a new, Snapchat-style camera, the wildly popular messaging app is introducing group video chat, its most requested feature. Group video chat on Messenger will be available globally, both on iOS and Android, and will start rolling out Monday.

Messenger&;s impressive run of new feature releases (it&039;s also experimenting with AI-powered contextual suggestions) is evidence Facebook is unwilling to simply let it ride the coattails of the 1.79 billion user core app it&039;s inherently tied to. Instead, as Messenger ships fun new features, Facebook is proving the wisdom of spinning out the app in 2014, a move initially met with user backlash.

Group video chat on Messenger will support up to six videos at a time, but up to 50 people can watch and, if they so choose, join via voice, stickers and the like. A video icon will now appear at the top right of group conversations, and tapping on it will alert group members and give them the choice to join.

Group video chat is having a bit of a moment right now. Houseparty, a group video chat app by the creators of Meerkat, just raised $50 billion. And Fam, an iMessage group video app, seems to be taking off as well.

One big question about Messenger remains: how will it make money? At this point, the app is very popular — claiming over 1 billion users — but it&039;s not contributing meaningfully to Facebook&039;s bottom line. Facebook is anticipating a slowdown in ad load growth, so it may soon need to make a revenue push inside Messenger, something that lead to even more changes. But in the meantime, enjoy your video chats.

Quelle: <a href="Facebook Messenger Adds Group Video Chat“>BuzzFeed

Announcing Exclude Disk Support for Hyper-V VMs with ASR

A key ask that Azure Site Recovery (ASR) customers often have is the ability to exclude disks from replication, either to optimize the replication bandwidth consumed or to optimize the target-side resources utilized by such disks. ASR&;s VMware to Azure scenario has had this capability since earlier this year. Today, we are announcing the availability of this feature for ASR&039;s Hyper-V to Azure scenario as well.

Why do customers exclude disks from replication?

Excluding disks from replication is often necessary because:

The data churned on the excluded disk is not important or doesn’t need to be replicated (or / and)
Storage and network resources can be saved by not replicating this churn

Let&039;s elaborate on what data isn&039;t “important”? The importance of replicated data is determined by its usefulness at the time of Failover. Data that is not replicated must also not be needed at the time of failover. The absence of this data should not impact the Recovery Point Objective (RPO) in any way.

What are the typical scenarios?

There are some specific examples of data churn that can be easily identified and are great candidates for exclusion – for example any page file writes, Microsoft SQL server tempdb writes etc. Depending on the workload and the storage subsystem, the page file can register a significant amount churn. However, replicating this data from the primary site to Azure would be resource intensive and completely worthless. Thus the replication of a VM with a single virtual disk having both the OS and the page file can be optimized by:

Splitting the single virtual disk into two virtual disks – one with the OS and one with the page file
Excluding the page file disk from replication

Similarly, for Microsoft SQL Server with tempdb and system database file on the same disk can be optimized by:

Keeping the system database and tempdb on two different disks
Excluding the tempdb disk from replication.

How to Exclude disk from replication?

Follow the normal Enable replication workflow to protect a VM from ASR portal. In the 4th step of Enable replication there is a new column named DISK TO REPLICATE to exclude disk from the replication. By default all the disks are selected for the replication. Unselect the VHD that you want to exclude from replication and complete the steps to enable the replication. Learn more about it in the Hyper-V to Azure(with VMM) or Hyper-V to Azure(no VMM) documentation. You can also view this video to see the feature in action.

Excluding the SQL Server tempdb disk

Let&039;s consider the Hyper-V to Azure scenario for a SQL Server virtual machine that has a tempdb which can be excluded.

Name of the Hyper-V VM: SalesDB

Disks on the source Hyper-V VM:

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1
Disk1
D:
SQL system database and User Database1

DB-Disk2 (Excluded the disk from the protection)
Disk2
E:
Temp files

DB-Disk3 (Excluded the disk from the protection)
Disk3
F:
SQL tempdb database (folder path(F:MSSQLData) –> note down the folder path before failover

DB-Disk4
Disk4
G:
User Database2

Since data churn on two disks of the VM are temporary in nature, while protecting SalesDB VM, exclude Disk2 and Disk3 from the replication. ASR will not replicate those disks and on failover those disks will not be present on the failover VM on Azure

Disks on the Azure VM after failover:

Guest OS disk#
Drive letter
Data type on the disk

DISK0
C:
OS disk

Disk1
E:
Temporary storage [Azure adds this disk and assigns the first available drive letter]

Disk2
D:
SQL system database and User Database1 

Disk3
G:
User Database2

Since Disk2 and Disk3 were excluded from SalesDB VM, E: is the first drive letter from the available list. Azure assigns E: to temporary storage volume. For all the replicated disks, drive letter remains the same.

Disk3 which was SQL tempdb disk (tempdb folder path F:MSSQLData) and excluded from replication, the disk is not available on the failover VM. As a result, the SQL service is in stopped state and it needs the F:MSSQLData path.

There are two ways in which you can create this path.

Add a new disk and assign tempdb folder path or
Use existing temporary storage disk for tempdb folder path

Add a new disk:

Note down the SQL tempdb.mdf and tempdb.ldf path before failover.
From the Azure portal, add a new disk to the failover VM with the same or more size as that of source SQL tempdb disk (Disk3).
Login to the Azure VM. From the disk management(diskmgmt.msc) console initialize and format the newly added disk.
Assign the same drive letter that was used by SQL tempdb disk (F:).
Create tempdb folder on F: volume (F:MSSQLData).
Start SQL service from service console.

Use existing temporary storage disk for SQL tempdb folder path:

      1.    Open a command line console

      2.    Run SQL server in recovery mode from command line console

Net start MSSQLSERVER /f / T3608

       3.   Run the following sqlcmd to change the tempdb path to new path

sqlcmd -A -S <SQL server instance name>

sqlcmd -A -S SalesDB

USE master;

GO

ALTER DATABASE tempdb

MODIFY FILE (NAME = tempdev, FILENAME = &039;E:MSSQLtempdatatempdb.mdf&039;);

GO

ALTER DATABASE tempdb

MODIFY FILE (NAME = templog, FILENAME = &039;E:MSSQLtempdatatemplog.ldf&039;);

GO

      4.   Stop Microsoft SQL server service.

Net stop MSSQLSERVER

       5.   Start Microsoft SQL server service.

Net start SSQLSERVER

Refer to the following Azure guideline for temporary storage disk

Using SSDs in Azure VMs to store SQL Server TempDB and Buffer Pool Extensions
Performance best practices for SQL Server in Azure Virtual Machines

Failback (from Azure to on-premises)

Now let&039;s understand what all disks will be replicated when you do failover from Azure to your on-premises Hyper-V host. Disks that you create manually in Azure will be not be replicated. For example, if you fail over three disks and create two directly in Azure VM, only three disks which were failed over will be failed back. You can&039;t include disks created manually in failback or in re-protect from on-premises to Azure. It also does not replicate temporary storage disk to on-premises.

Failback to OLR

When failback is done to the original location, failback VM disk configuration remains the same as that of original VM disk configuration. That means the disks which were excluded from Hyper-V site to Azure, will be available on the failback VM.

In the above example, Azure VM disk configuration:

Guest OS disk#
Drive letter
Data type on the disk

DISK0
C:
OS disk

Disk1
E:
Temporary storage [Azure adds this disk and assigns the first available drive letter]

Disk2
D:
SQL system database and User Database1

Disk3
G:
User Database2

After planned failover from Azure to on-premises Hyper-V, disks on the Hyper-V VM(Original Location Replication):

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1
Disk1
D:
SQL system database and User Database1

DB-Disk2 (Excluded disk)
Disk2
E:
Temp files

DB-Disk3
(Excluded disk)
Disk3
F:
SQL tempdb database (folder path(F:MSSQLData)

DB-Disk4
Disk4
G:
User Database2

Exclude Paging file disk

Let&039;s consider the Hyper-V to Azure scenario for a virtual machine which has a pagefile disk that can be excluded.

There are two cases:

Case1: Pagefile is configured on the D: drive

Hyper-V VM disk configuration:

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1
(Excluded the disk from the protection)
Disk1
D:
pagefile.sys

DB-Disk2
Disk2
E:
User data 1

DB-Disk3
Disk3
F:
User data 2

Pagefile settings on the Hyper-V VM:

After you failover the VM from Hyper-V to Azure, disks on Azure VM:

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1
Disk1
D:
Temporary storage –> pagefile.sys

DB-Disk2
Disk2
E:
User data 1

DB-Disk3
Disk3
F:
User data 2

Since Disk1 (D:) was excluded, D: is the first drive letter from the available list, Azure assigns D: letter to temporary storage volume.  Since D: is available on the Azure VM, pagefile setting of the VM remains the same.

Pagefile settings on Azure VM:

 

Case2: Pagefile file is configured on any other drive(other than D: drive)

Hyper-V VM disk configuration:

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1 (Excluded the disk from the protection)
Disk1
G:
pagefile.sys

DB-Disk2
Disk2
E:
User data 1

DB-Disk3
Disk3
F:
User data 2

Pagefile settings on the Hyper-V VM:

After you failover the VM from Hyper-V to Azure, disks on Azure VM:

VHD name
Guest OS disk#
Drive letter
Data type on the disk

DB-Disk0-OS
DISK0
C:
OS disk

DB-Disk1
Disk1
D:
Temporary storage –> pagefile.sys

DB-Disk2
Disk2
E:
User data 1

DB-Disk3
Disk3
F:
User data 2

Since D: is the first drive letter available from the list, Azure assigns D: to temporary storage volume. For all the replicated disks, drive letter remains the same. Since G: disk is not available system will use C: drive for pagefile.

Pagefile settings on Azure VM:

You can check out additional product information, and start replicating your workloads to Microsoft Azure using Azure Site Recovery today. You can use the powerful replication capabilities of Site Recovery for 31 days at no charge for every new physical server or virtual machine that you replicate. Visit the Azure Site Recovery forum on MSDN for additional information and to engage with other customers, or use the ASR User Voice to let us know what features you want us to enable next.

Azure Site Recovery, as part of Microsoft Operations Management Suite, enables you to gain control and manage your workloads no matter where they run (Azure, AWS, Windows Server, Linux, VMware or OpenStack) with a cost-effective, all-in-one cloud IT management solution. Existing System Center customers can take advantage of the Microsoft Operations Management Suite add-on, empowering them to do more by leveraging their current investments. Get access to all the new services that OMS offers, with a convenient step-up price for all existing System Center customers. You can also access only the IT management services that you need, enabling you to on-board quickly and have immediate value, paying only for the features that you use.

Pagefile is configured on D: drive
Pagefile file is configured on any other drive(other than D: drive)

Quelle: Azure

Google Says It Would Not Help Build A Muslim Registry, If Asked

Drew Angerer / Getty Images

In response to questions from BuzzFeed News, Google clarified its position on President-elect Donald Trump&;s proposed Muslim registry. “In relation to the hypothetical of whether we would ever help build a &039;muslim registry&039; – we haven&039;t been asked, of course we wouldn&039;t do this and we are glad – from all that we&039;ve read – that the proposal doesn&039;t seem to be on the table,” a spokesperson for the company told BuzzFeed News.

Uber said “No,” in response to the same questions, clarifying that it would not help build or provide data for a Muslim registry. Oracle declined to respond to the same questions about a Muslim registry. The company also declined to say whether the National Security Agency was still an Oracle customer. Oracle&039;s refusal to comment comes one day after CEO Safra Catz announced that she would join the transition team for President Elect Donald Trump, while remaining at Oracle.

Alphabet CEO Larry Page and Catz both attended a high profile tech summit hosted at Trump Tower on Tuesday. They were joined by Facebook COO Sheryl Sandberg, Microsoft CEO Satya Nadella, Palantir CEO Alex Karp and Eric Schmidt, the chairman of Google&039;s parent Alphabet, among others. BuzzFeed News has reached out to other attendees to find out whether they would help build or provide data for a Muslim registry. Facebook and Microsoft both said that they would not help build a registry, after initially declining to comment on the record.

In 2013, Edward Snowden leaked leaked documents that described how tech companies like Google, Apple, Microsoft, and Yahoo worked with US intelligence services as part of a top secret surveillance and spying program called PRISM.

Catz went into the summit to discuss ways that Trump could better support the tech industry, Reuters reported. Her list included reducing regulations, reforming the tax code, negotiating better trade deals. Hours before the summit, Trump announced a forum of business advisors, including Uber CEO Travis Kalanick and SpaceX and Tesla CEO Elon Musk, who would meet regularly to directly advise the President. Catz&039;s name was not on the list.

During the summit, Catz brought up the subject of the cloud. According to a detailed report in Recode, Catz “characterized [the cloud] a little hyped (not a surprise from a database company)” while Page wanted to talk about infrastructure spending.

More than 1300 employees from major tech companies signed a pledge earlier this week to never help build a Muslim registry. The list of signatories includes one employee from Oracle and dozens of employees from Google.

Quelle: <a href="Google Says It Would Not Help Build A Muslim Registry, If Asked“>BuzzFeed

The Unbelievable Story Behind The Strangest Fake News Empire On The Web

BuzzFeed News; Getty

In early July, a website made to look like a real news organization published what would prove to be one of the biggest fake news hits of the US election.

WTOE5News.com was barely two weeks old when it published the hoax story, “Pope Francis Shocks World, Endorses Donald Trump for President, Releases Statement.

It improbably quoted the pope as saying that the FBI’s inability to prosecute Hillary Clinton for her emails led him to endorse Trump. The story also falsely declared that “news outlets around the world” were reporting the endorsement.

To date, the hoax has registered over 100,000 comments, shares, and reactions on Facebook, according to data from BuzzSumo. But the hoax did even better on Facebook when, in late September, the website Ending the Fed published a fake story with the exact same headline. That post has earned close to 1 million Facebook engagements and was the single biggest fake news hit of the election, according to a previous analysis by BuzzFeed News.

Ending the Fed’s copycat hoax has gone on to capture additional attention as concerns about fake news during the election have intensified. That hoax has been pointed to again and again. Yet little has been said — and is known — about the site that originated this massive fake news hit.

WTOE 5 News is no longer online, and its owner has never been identified. It has largely been overlooked as a player in the world of fake news, a flash in the ersatz pan. But a BuzzFeed News investigation has found that the site is part of one of the world’s most unique and ambitious fake news operations — a network of at least 43 websites that together have published more than 750 fake news articles.

Many of the fake stories identified by BuzzFeed News followed the exact same pattern: They falsely reported that a big celebrity was moving to a specific town or community.

None of the sites list an owner or company, and all of their domain registration records are private. Not surprisingly, the person behind one of the biggest fake news scams of all time prefers to remain hidden. To try and identify the owner, BuzzFeed News followed a trail from the fake sites to a group of now-defunct websites about topics including nurses and photos of Jennifer Love Hewitt, and eventually to a house in the small city of Atascadero, California, where a man named Justin Smithson resides.

This is the story of one of the world’s largest and most unique fake news empires, and how it gave birth to what became the iconic hoax of the 2016 election.

Steve Arrison thought his job was about get a lot easier.

Arrison is CEO of the Hot Springs Convention & Visitors Bureau for the town of Hot Springs, Arkansas. Just under 40,000 people live there, but it welcomes an estimated 3 million tourists a year. Arrison’s job is to bring in as many of those visitors as possible. In early March, a news story had the town thinking they’d landed a major VIP and tourist draw.

“Clint Eastwood is Moving to Hot Springs, Arkansas” read the headline. It was being shared like crazy by locals. Even state media was starting to call about it. But as soon as Arrison clicked the link and started reading, he realized something was off.

“I went to the web and saw that same site said Katy Perry was moving to some place in Texas, so immediately a red flag went up,” Arrison told BuzzFeed News. “A lot of people wasted a lot of time on something that was blatantly false. Information moves so quickly it takes a while for the truth to catch up to the falsehoods.”

Beginning in late February, there was a sudden onslaught of news stories on Facebook that all claimed one celebrity after another was moving to an unexpected place. The stories had headlines such as “Johnny Depp Explains Why He’s Moving to Pittsburgh, Pennsylvania,” “Matthew McConaughey Explains Why He’s Moving to Greenville, South Carolina,” and “Demi Lovato Moving to Perris, California.” The list of celebrities in the hoaxes began to expand and soon Eminem, Ryan Gosling, Rihanna, Jim Carrey, Samuel L. Jackson, Justin Bieber, and Brad Pitt were moving. As the days and weeks went on, the locations also began to move farther away on the map: Vin Diesel was moving to Saskatoon, Saskatchewan. Leonardo DiCaprio was moving to Guidford, Surrey, UK.

These stories appeared on sites with legitimate-sounding news domains such as kspm33.com, mckenziepost.com, ky6news.com, and km8news.com. The design of each site was strikingly similar — often just the colors and the name were changed. The text, too, was a simple copy-and-paste effort; just the celebrity’s name and location were changed from one story to the next. It quickly proved to be an effective strategy as the stories began to spread across the internet.

One morning in early March, a staffer for venerable rumor-checking website Snopes logged on to the site’s main email account to read the tips and questions that had flowed in overnight. She saw something unusual: Roughly 25 emails that all asked about reports of different celebrities moving to different towns. The same rumor was being repeated again and again — but with different celebrities and different locations.

Kim LaCapria, a writer for Snopes, told BuzzFeed News they were initially puzzled at how “scattered” the rumors were.

“That spate of rumors was scattered across locations and individuals and basically was diffused to the point where the average social media user would be less apt to ‘see’ the rumor,” she said. “Particularly because they’re seeing it from their vantage point, and likely to think, ‘Well, who’s going to take the time to lie or make up a hoax about my tiny neighborhood?’”

The local focus ensured the hoaxes spread in targeted clusters, and meant someone in, say, Saskatoon had no idea that the same trick was being played on people in Pittsburgh.

Snopes eventually wrote a single post to warn people that no, that big celebrity was almost certainly not moving to their town. One simple clue was that the about page for each site had the exact same disclosure telling people that they were reading a “a fantasy news site.” But the stories kept coming and people kept getting fooled.

LaCapria said in an email that “the rumor was so atypically benign (clearly not a potential lie to advance any agenda or belief) that it again just sort of managed to infest tons of local areas.”

BuzzFeed News identified 342 celebrity-moving hoaxes spread across multiple, connected sites. As the scam scaled and hit more communities, local news websites began publishing debunkings to keep locals from falling for the hoaxes. News outlets in Texas, Maine, Illinois, South Carolina, British Columbia, and many other places tried to stop the stories from spreading.

Meanwhile, the growing network of fake sites began pumping out new variations. Male celebrities suddenly had very complimentary things to say about the women in specific towns. Celebrities began getting flat tires in obscure places, naming somewhat obscure locales as their favorite vacation spots, and buying homes in unexpected communities. One of the strangest variations was a series of at least 11 hoax stories claiming that Justin Bieber was building megachurches in places such as Spokane, Washington.

Another variation moved away from specific celebrities and instead falsely claimed that big film sequels were being shot in different locations: Father of the Bride III, a Harry Potter spinoff, a new Star Wars Film, a new Pretty Woman. They were all suddenly in production and coming to your town. BuzzFeed News identified 152 fake news articles claiming that major film sequels were being filmed in different locations.

The hoaxes combine two important elements that help them spread: location and name recognition. Many people saw a story about their town that also included a celebrity or major film and couldn’t help but share the link on Facebook, thereby driving traffic to sites littered with ads.

An analysis of the sites&; content, done using the BuzzSumo, found that while these hoaxes never went hugely viral, they managed to consistently generate tens of thousands of shares, comments, and reactions on Facebook, which likely led to strong traffic and revenue.

BuzzFed News began internally calling this the “local viral scam” because the fake stories went viral on a local basis but never bubbled up higher than that.

LaCapria of Snopes admitted she has grudging respect for the way this approach combined someone or something famous with different locations to spark social shares.

“It’s a very unique thing, the execution was so different,” she said. “It only works if you plug in a relevant celebrity to the area. It was really well targeted.”

It was also proving lucrative enough to keep expanding. BuzzFeed News was only able to identify the existence of one site, McenziePost.com, in February. But at the end of April there were more than 20 nearly identical fake news sites. By June at least 27 were in operation. That was also the month WTOE 5 News was registered. A few weeks later, in a departure from the template of previous fake news articles, that site published the pope endorsing Trump story. It earned over 100,000 shares, comments, and reactions on Facebook, making it the network’s fourth biggest hit on the platform, according to an analysis done using BuzzSumo.

Not long after, on July 19, yet another newly registered site published the exact same story with a twist: This time the pope endorsed Hillary Clinton. (The site that hosted it, KYPO6, it is no longer online but used the same template and language as other sites in the network.)

That story performed even better, generating over 200,000 shares, comments, and reactions on Facebook, according to BuzzSumo. (Both stories were published before the party conventions.)

A few other websites picked up the fake papal story fake story in July, but none saw significant engagement. The Clinton story, in spite of being a bigger hit on Facebook, did not inspire copycats. For the most part, those two hoaxes came and went, and the network of fake sites went back to their core focus of churning out local viral stories.

Then, as the election kicked into high gear in September, Ending the Fed published a hoax story with the exact same headline and scored a massive hit. (Ending the Fed is an anonymously run website that previously attracted attention when Facebook promoted one of its false stories as a trending topic.)

Perhaps inspired by the success of that copycat story, the papal hoax story made yet another appearance on one of the local viral fake sites, Channel16News.com, in mid-October. But it failed to gain much traction on Facebook.

Since then, the network of fake sites has continued to grow, reaching at least 44 sites. The most recently registered domain identified by BuzzFeed News, DailyNews5.com, was bought on Nov. 3. That’s a few days prior to the US election — and before alarm bells about fake news began going off in the media and among political leaders.

But rather than completely shut down the operation and move on in order to avoid attention, the sites continue to push out new hoaxes. A fake story about a new Star Wars film being shot in Roswell, New Mexico, went online just this week, according to data in BuzzSumo. Whoever is running the sites appears to be unconcerned by the outrage over fake news. Or perhaps the sites were too lucrative to shut down? We wanted answers. So BuzzFeed News decided to follow the money.

Though some are now offline, nearly all of the sites in this fake news network contained the same Google AdSense ID in their source code. This means the money earned each month from ads placed on the sites is going into a single account. That ID has also appeared on other websites over the years, from TehYouTube.com and NursingJobResources.com to JenniferLoveHewittPics.com and KimKardashianPics.com. Google does not publicly list the owners of AdSense IDs, but the aforementioned sites were publicly registered by the same person: Justin Smithson, who lived in Missouri at the time, according to historical registration data from Whoisology and DomainTools. The Justin Smithson who resided at that Missouri address now lives in Atascadero, California, according to records obtained in a LexisNexis search. (Go here to view a collection of documents linking Smithson and the network of fake sites to the AdSense ID.)

On the left is a list of some of the websites connected via a single AdSense ID. On the right is a public domain registration record for JenniferLoveHewittPics.com and other sites registered by the same Justin Smithson.

CuteStat / DomainTools / Google

Smithson is a pilot in his thirties who works for a charter airline in San Luis Obispo. Over the years he has registered and launched many websites. At some point, it appears that Smithson signed up for Google AdSense in order to place ads on his websites. As he launched new sites, Smithson continued to use that same AdSense code, leaving a trail that eventually connected him to the network of fake news sites. (There is of course a chance that Smithson registered those sites on behalf of someone else, who then added AdSense and went on to later launch the network of fake sites. Or that Smithson handed over his AdSense account to someone else.)

In addition to being an experienced webmaster, public Facebook comments from Smithson also indicate he has above-average knowledge of computers and the internet. These two public Facebook comments (which were later deleted) show him sharing details about his personal computer’s processing power, as well as information about the fast internet connection he has at home:

Facebook

Domain registration records also show that Smithson continues to register new domains using the same email address he used for JenniferLoveHewittPics.com and others. At the end of November, for example, he registered FoxBusiness.xyz. In September he bought AlexJones.xyz. As with the fake news sites, those domains now have their ownership information hidden.

In early October, BuzzFeed News contacted Smithson by email to request an interview about his fake news websites. “I&039;m guessing this is some kind of spam/scam but if not… You&039;ve got the wrong person,” he replied.

Smithson did not reply to subsequent emails, including one on Oct. 5 requesting a meeting at noon. On Oct. 6, BuzzFeed News visited his place of work and his Atascadero home, where we found him on the front porch with another man. When they men saw us approaching with a camera in hand, they went inside.

We called out to say we wanted to talk to Justin, and one of the men yelled from a window that there wasn’t anyone there by that name. He threatened to break our camera, so we left.

Smithson did not reply to four subsequent emails, texts, and phone calls. Nor did he reply this week when BuzzFeed News sent him detailed questions and shared the evidence that points to him as the owner of perhaps the world’s biggest fake news operation. (Aside from any state-sponsored efforts, that is.)

As of this writing, at least 20 of these websites are still online. Their stories are still being shared, and they still publish new fake news stories that fool people and earn money for that same AdSense account. LaCapria of Snopes says she still sees new variations of the local viral scam from time to time.

“It still seems to be living on — but most people have gotten past asking us if it’s true that a celebrity is moving to their town,” she said.

Quelle: <a href="The Unbelievable Story Behind The Strangest Fake News Empire On The Web“>BuzzFeed

Federal Law Now Guarantees Your Right To Leave A Bad Yelp Review

AP/Richard Vogel

Federal law now guarantees the right to leave a bad Yelp review, after President Obama signed the Consumer Review Fairness Act on Wednesday.

The law, which passed the Senate in November with bipartisan support, comes after years of legal efforts to overturn so-called “gag clauses” in contracts, which consumer advocates say are used by businesses to stifle free speech. The clauses, which have been included in the fine print of sign-up forms and purchase agreements, forbid public criticism of companies by their customers.

Such clauses are banned under the new law, which also prohibits businesses from imposing a penalty or fee on a client if they write a bad review. Consumer advocacy groups and other supporters of the law are celebrating its passing.

Yelp, whose users have been sued by companies over negative reviews, said the Act “gives Americans nationwide new guaranteed legal protections when it comes to sharing these honest, first-hand experiences.”

Paul Levy, an attorney with Public Citizen who has represented a number of consumers who have been sued over gag clauses, said businesses have used the legal fine print to “suppress truthful criticism and skew the marketplace of ideas by allowing only positive reviews and suppressing negative ones.”

“Non-disparagement clauses not only prevent consumers from expressing themselves but also deprive prospective customers of balanced and truthful information on which they can base their decisions about where to do business,” he said. “What’s worse, most consumers are unaware when they have agreed to a non-disparagement clause curtailing their First Amendment rights.”

Levy represented one of the first consumers to be sued by a company over a negative review. A company called KlearGear claimed a couple in Utah owed a debt for violating its terms of service by writing the review. The couple sued KlearGear in 2012 arguing they didn&;t owe any debt to the company and received a default judgement including over $300,000 in damages when the company never appeared in court.

In another case in 2014, a Wisconsin woman filed a lawsuit against Accessory Outlet, an online mobile retailer, after they demanded she pay $250 for violating its terms of sale. The company never appeared in court to defend its claims and the court granted the woman a default judgment in 2015, including triple the damages and attorneys fees.

California made gag clauses in contracts illegal in in 2015. Any business that violates the law will be fined up to $2,500 on its first violation and $5,000 for following violations. Consumers can receive up to $10,000 if they can prove the business acted recklessly in violating the law.

LINK: Yelp’s Warning: This Dentist Might Sue You For Posting A Negative Review

LINK: Someone Is Filing Wild Lawsuits Aimed At Negative Online Comments

LINK: Gag Clause 2.0: Companies Tell Customers To Keep Quiet If They Want To Cancel

LINK: Court Upholds The Right To Leave A Bad Yelp Review

Quelle: <a href="Federal Law Now Guarantees Your Right To Leave A Bad Yelp Review“>BuzzFeed