Data can be retrieved even after owners perform a factory reset, researcher says.

Devices will stop working for users who don't want to pay the new monthly fee.

The hacker had access to personal information, the ability to change passwords and two-factor authentication, and could steal valuable in-game items from some of the 'richest' players in the game

Michelle Chen

The post Will the Pandemic Lead to Better Treatment for Drug Users? appeared first on The Nation.

The future royal wore a trouser suit for her first official evening engagement with Prince Harry, ushering in a new kind of sartorial diplomacy

Last night, for her first official evening engagement with Prince Harry, Meghan Markle wore an Alexander McQueen trouser suit. It was slim-fitting, with cropped cigarette trousers, worn with very high stiletto heels and a cream dishabille blouse. The outfit was many things: very Saint Laurent’s Le Smoking, a bit Princess Diana, with a soupçon of Marlene Dietrich, even a hint of Carine Roitfeld (although Roitfeld probably wouldn’t have worn a blouse underneath the tux). What it was not was a Sandringham-appropriate boxy Catherine Walker skirt suit. It was notable because it didn’t feel like standard royal family dressing at all.

The royal family wrote the rule book on sartorial diplomacy. Usually, their approach is unambiguous. It is a gown embroidered with 2,091 shamrocks in Ireland; a Chanel tweed coat in Paris in the middle of Brexit; a dress by Polish designer Gosia Baczyńska at a garden party in Warsaw. It is the opposite of wearing a cult band T-shirt that only fellow devotees will recognise. The clothes are designed to speak of decency and propriety; the visual messages are clear enough to charm heads of state and reach the rest of us in the cheap seats as well.

Alberta's use of a smartphone app to help slow the spread of the coronavirus may provide other provinces with insight on what to do — and what to avoid — as Canada begins easing restrictions, heightening the need for effective contact tracing.

WeChat is one of the world’s most popular apps, but researchers at the University of Toronto caution it is surveilling international users and using their information to broaden censorship on the app in China.

'I truly do wonder what's going on inside of her brain,' one outraged tweeter wrote

The meal delivery service and dating platform have joined forces to encourage the new era of dating

Researchers found a security flaw in Zoom's "Waiting Room" feature that could have allowed users to access a video meeting even if they were not approved to join a call. Zoom said Wednesday it had fixed the issue.

The anticipated proliferation of devices demands an innovative approach to managing, securing and delivering these endpoints and the applications that will run on them.

Keep on reading: Why End-User Computing Needs a Refresh

Lowe’s, a national hardware store chain, has agreed to settle the Justice Department’s claims alleging that the company violated the Uniform Services Employment and Reemployment Rights Act (USERRA) when it terminated the employment of Matthew King, a U.S. Army Guard member and Iraq War veteran, without just cause.

The Justice Department filed a lawsuit against United Airlines Inc., alleging violations of the Uniformed Services Employment and Reemployment Rights Act of 1994 (USERRA).

The Department of Justice filed a civil antitrust lawsuit today challenging Anheuser-Busch InBev’s (ABI) proposed acquisition of total ownership and control of Grupo Modelo.

The Department of Justice announced today that it has reached a settlement with Anheuser-Busch InBev SA/NV (ABI) and Grupo Modelo S.A.B. de C.V. that requires the companies to divest Modelo’s entire U.S. business to Constellation Brands Inc., in order to go forward with their merger.

The organic snack bar company has created the first geo-location Twitter campaign to promote its trail mix bar.

The CATable will keep the cat off the keyboard.

The rollout starts in Seattle, then more broadly.

The overhaul now includes the Voyager feature for deep exploration, not just satellite views.

This little solar powered device can take the guesswork out of SODIS water treatment, showing when the resulting water is safe to drink.

They'll also be investing in alternative powertrains and other ways to directly reduce emissions.

Made with a patented energy- and wood-saving technique, this Corelam collection is perfect for those who move a lot.

The smart thermostat will help people save even more money and help utilities curb peak demand loads.

A new study suggests Zipcar users are less inclined to look after vehicles, and don't trust their fellow users. What does that mean for collaborative consumption?

Google Reader is gone on July 1, but our RSS feed isn't going anywhere.

Kerry Washington PSA

Nuelle™ Chief Commercial Officer Lesa Musatto briefly shares why Fiera® was created, its benefits and how it works.

Presumptive Democratic presidential candidate Joe Biden strongly denies claims by Tara Reade that he sexually assaulted her in 1993, when he was a senator.

Streaming services have reported huge spikes in subscribers during the crisis as stay-at-home orders have forced more people to stay inside.

Shares of Pinterest fell as much as 9% in after-hours trading on Tuesday after the company reported its first quarter results.

Chinese internet giant Tencent has been surveilling content posted by foreign users on its wildly popular messaging service WeChat in order to help it refine censorship on its platform at home, according to a new report.

The woman who accused Joe Biden of sexually assaulting her in 1993 called on him to drop out of the US presidential race, saying Thursday she'd take a polygraph about the alleged encounter if he would.

Huzzah! It's the moment we've all been waiting for -- Cheezburger's classic LOLCats! 

Your ultimate source for the newest, and cutest, cat memes! All of which are created by our very own users! If you want to check out more cat memes that we know will make you laugh, check out Lolcat. If you have some funny ideas and would like to submit them, take a look at our Meme Builder. 

We love our user's original cat memes! 

Biden has repeatedly denied Reade's allegation.

At React Conf 2019 we announced an experimental release of React that supports Concurrent Mode and Suspense. In this post we’ll introduce best practices for using them that we’ve identified through the process of building the new facebook.com.

This post will be most relevant to people working on data fetching libraries for React.

It shows how to best integrate them with Concurrent Mode and Suspense. The patterns introduced here are based on Relay — our library for building data-driven UIs with GraphQL. However, the ideas in this post apply to other GraphQL clients as well as libraries using REST or other approaches.

This post is aimed at library authors. If you’re primarily an application developer, you might still find some interesting ideas here, but don’t feel like you have to read it in its entirety.

Talk Videos

If you prefer to watch videos, some of the ideas from this blog post have been referenced in several React Conf 2019 presentations:

• Data Fetching with Suspense in Relay by Joe Savona
• Building the New Facebook with React and Relay by Ashley Watkins
• React Conf Keynote by Yuzhi Zheng

This post presents a deeper dive on implementing a data fetching library with Suspense.

Putting User Experience First

The React team and community has long placed a deserved emphasis on developer experience: ensuring that React has good error messages, focusing on components as a way to reason locally about app behavior, crafting APIs that are predictable and encourage correct usage by design, etc. But we haven’t provided enough guidance on the best ways to achieve a great user experience in large apps.

For example, the React team has focused on framework performance and providing tools for developers to debug and tune application performance (e.g. React.memo). But we haven’t been as opinionated about the high-level patterns that make the difference between fast, fluid apps and slow, janky ones. We always want to ensure that React remains approachable to new users and supports a variety of use-cases — not every app has to be “blazing” fast. But as a community we can and should aim high. We should make it as easy as possible to build apps that start fast and stay fast, even as they grow in complexity, for users on varying devices and networks around the world.

Concurrent Mode and Suspense are experimental features that can help developers achieve this goal. We first introduced them at JSConf Iceland in 2018, intentionally sharing details very early to give the community time to digest the new concepts and to set the stage for subsequent changes. Since then we’ve completed related work, such as the new Context API and the introduction of Hooks, which are designed in part to help developers naturally write code that is more compatible with Concurrent Mode. But we didn’t want to implement these features and release them without validating that they work. So over the past year, the React, Relay, web infrastructure, and product teams at Facebook have all collaborated closely to build a new version of facebook.com that deeply integrates Concurrent Mode and Suspense to create an experience with a more fluid and app-like feel.

Thanks to this project, we’re more confident than ever that Concurrent Mode and Suspense can make it easier to deliver great, fast user experiences. But doing so requires rethinking how we approach loading code and data for our apps. Effectively all of the data-fetching on the new facebook.com is powered by Relay Hooks — new Hooks-based Relay APIs that integrate with Concurrent Mode and Suspense out of the box.

Relay Hooks — and GraphQL — won’t be for everyone, and that’s ok! Through our work on these APIs we’ve identified a set of more general patterns for using Suspense. Even if Relay isn’t the right fit for you, we think the key patterns we’ve introduced with Relay Hooks can be adapted to other frameworks.

Best Practices for Suspense

It’s tempting to focus only on the total startup time for an app — but it turns out that users’ perception of performance is determined by more than the absolute loading time. For example, when comparing two apps with the same absolute startup time, our research shows that users will generally perceive the one with fewer intermediate loading states and fewer layout changes as having loaded faster. Suspense is a powerful tool for carefully orchestrating an elegant loading sequence with a few, well-defined states that progressively reveal content. But improving perceived performance only goes so far — our apps still shouldn’t take forever to fetch all of their code, data, images, and other assets.

The traditional approach to loading data in React apps involves what we refer to as “fetch-on-render”. First we render a component with a spinner, then fetch data on mount (componentDidMount or useEffect), and finally update to render the resulting data. It’s certainly possible to use this pattern with Suspense: instead of initially rendering a placeholder itself, a component can “suspend” — indicate to React that it isn’t ready yet. This will tell React to find the nearest ancestor <Suspense fallback={<Placeholder/>}>, and render its fallback instead. If you watched earlier Suspense demos this example may feel familiar — it’s how we originally imagined using Suspense for data-fetching.

It turns out that this approach has some limitations. Consider a page that shows a social media post by a user, along with comments on that post. That might be structured as a <Post> component that renders both the post body and a <CommentList> to show the comments. Using the fetch-on-render approach described above to implement this could cause sequential round trips (sometimes referred to as a “waterfall”). First the data for the <Post> component would be fetched and then the data for <CommentList> would be fetched, increasing the time it takes to show the full page.

There’s also another often-overlooked downside to this approach. If <Post> eagerly requires (or imports) the <CommentList> component, our app will have to wait to show the post body while the code for the comments is downloading. We could lazily load <CommentList>, but then that would delay fetching comments data and increase the time to show the full page. How do we resolve this problem without compromising on the user experience?

Render As You Fetch

The fetch-on-render approach is widely used by React apps today and can certainly be used to create great apps. But can we do even better? Let’s step back and consider our goal.

In the above <Post> example, we’d ideally show the more important content — the post body — as early as possible, without negatively impacting the time to show the full page (including comments). Let’s consider the key constraints on any solution and look at how we can achieve them:

• Showing the more important content (the post body) as early as possible means that we need to load the code and data for the view incrementally. We don’t want to block showing the post body on the code for <CommentList> being downloaded, for example.
• At the same time we don’t want to increase the time to show the full page including comments. So we need to start loading the code and data for the comments as soon as possible, ideally in parallel with loading the post body.

This might sound difficult to achieve — but these constraints are actually incredibly helpful. They rule out a large number of approaches and spell out a solution for us. This brings us to the key patterns we’ve implemented in Relay Hooks, and that can be adapted to other data-fetching libraries. We’ll look at each one in turn and then see how they add up to achieve our goal of fast, delightful loading experiences:

1. Parallel data and view trees
2. Fetch in event handlers
3. Load data incrementally
4. Treat code like data

Parallel Data and View Trees

One of the most appealing things about the fetch-on-render pattern is that it colocates what data a component needs with how to render that data. This colocation is great — an example of how it makes sense to group code by concerns and not by technologies. All the issues we saw above were due to when we fetch data in this approach: upon rendering. We need to be able to fetch data before we’ve rendered the component. The only way to achieve that is by extracting the data dependencies into parallel data and view trees.

Here’s how that works in Relay Hooks. Continuing our example of a social media post with body and comments, here’s how we might define it with Relay Hooks:

// Post.js
function Post(props) {
  // Given a reference to some post - `props.post` - *what* data
  // do we need about that post?
  const postData = useFragment(graphql`
    fragment PostData on Post @refetchable(queryName: "PostQuery") {
      author
      title
      # ...  more fields ...
    }
  `, props.post);

  // Now that we have the data, how do we render it?
  return (
    <div>
      <h1>{postData.title}</h1>
      <h2>by {postData.author}</h2>
      {/* more fields  */}
    </div>
  );
}

Although the GraphQL is written within the component, Relay has a build step (Relay Compiler) that extracts these data-dependencies into separate files and aggregates the GraphQL for each view into a single query. So we get the benefit of colocating concerns, while at runtime having parallel data and view trees. Other frameworks could achieve a similar effect by allowing developers to define data-fetching logic in a sibling file (maybe Post.data.js), or perhaps integrate with a bundler to allow defining data dependencies with UI code and automatically extracting it, similar to Relay Compiler.

The key is that regardless of the technology we’re using to load our data — GraphQL, REST, etc — we can separate what data to load from how and when to actually load it. But once we do that, how and when do we fetch our data?

Fetch in Event Handlers

Imagine that we’re about to navigate from a list of a user’s posts to the page for a specific post. We’ll need to download the code for that page — Post.js — and also fetch its data.

Waiting until we render the component has problems as we saw above. The key is to start fetching code and data for a new view in the same event handler that triggers showing that view. We can either fetch the data within our router — if our router supports preloading data for routes — or in the click event on the link that triggered the navigation. It turns out that the React Router folks are already hard at work on building APIs to support preloading data for routes. But other routing frameworks can implement this idea too.

Conceptually, we want every route definition to include two things: what component to render and what data to preload, as a function of the route/url params. Here’s what such a route definition might look like. This example is loosely inspired by React Router’s route definitions and is primarily intended to demonstrate the concept, not a specific API:

// PostRoute.js (GraphQL version)

// Relay generated query for loading Post data
import PostQuery from './__generated__/PostQuery.graphql';

const PostRoute = {
  // a matching expression for which paths to handle
  path: '/post/:id',

  // what component to render for this route
  component: React.lazy(() => import('./Post')),

  // data to load for this route, as function of the route
  // parameters
  prepare: routeParams => {
    // Relay extracts queries from components, allowing us to reference
    // the data dependencies -- data tree -- from outside.
    const postData = preloadQuery(PostQuery, {
      postId: routeParams.id,
    });

    return { postData };
  },
};

export default PostRoute;

Given such a definition, a router can:

• Match a URL to a route definition.
• Call the prepare() function to start loading that route’s data. Note that prepare() is synchronous — we don’t wait for the data to be ready, since we want to start rendering more important parts of the view (like the post body) as quickly as possible.
• Pass the preloaded data to the component. If the component is ready — the React.lazy dynamic import has completed — the component will render and try to access its data. If not, React.lazy will suspend until the code is ready.

This approach can be generalized to other data-fetching solutions. An app that uses REST might define a route like this:

// PostRoute.js (REST version)

// Manually written logic for loading the data for the component
import PostData from './Post.data';

const PostRoute = {
  // a matching expression for which paths to handle
  path: '/post/:id',

  // what component to render for this route
  component: React.lazy(() => import('./Post')),

  // data to load for this route, as function of the route
  // parameters
  prepare: routeParams => {
    const postData = preloadRestEndpoint(
      PostData.endpointUrl, 
      {
        postId: routeParams.id,
      },
    );
    return { postData };
  },
};

export default PostRoute;

This same approach can be employed not just for routing, but in other places where we show content lazily or based on user interaction. For example, a tab component could eagerly load the first tab’s code and data, and then use the same pattern as above to load the code and data for other tabs in the tab-change event handler. A component that displays a modal could preload the code and data for the modal in the click handler that triggers opening the modal, and so on.

Once we’ve implemented the ability to start loading code and data for a view independently, we have the option to go one step further. Consider a <Link to={path} /> component that links to a route. If the user hovers over that link, there’s a reasonable chance they’ll click it. And if they press the mouse down, there’s an even better chance that they’ll complete the click. If we can load code and data for a view after the user clicks, we can also start that work before they click, getting a head start on preparing the view.

Best of all, we can centralize that logic in a few key places — a router or core UI components — and get any performance benefits automatically throughout our app. Of course preloading isn’t always beneficial. It’s something an application would tune based on the user’s device or network speed to avoid eating up user’s data plans. But the pattern here makes it easier to centralize the implementation of preloading and the decision of whether to enable it or not.

Load Data Incrementally

The above patterns — parallel data/view trees and fetching in event handlers — let us start loading all the data for a view earlier. But we still want to be able to show more important parts of the view without waiting for all of our data. At Facebook we’ve implemented support for this in GraphQL and Relay in the form of some new GraphQL directives (annotations that affect how/when data is delivered, but not what data). These new directives, called @defer and @stream, allow us to retrieve data incrementally. For example, consider our <Post> component from above. We want to show the body without waiting for the comments to be ready. We can achieve this with @defer and <Suspense>:

// Post.js
function Post(props) {
  const postData = useFragment(graphql`
    fragment PostData on Post {
      author
      title

      # fetch data for the comments, but don't block on it being ready
      ...CommentList @defer
    }
  `, props.post);

  return (
    <div>
      <h1>{postData.title}</h1>
      <h2>by {postData.author}</h2>
      {/* @defer pairs naturally with <Suspense> to make the UI non-blocking too */}
      <Suspense fallback={<Spinner/>}>
        <CommentList post={postData} />
      </Suspense>
    </div>
  );
}

Here, our GraphQL server will stream back the results, first returning the author and title fields and then returning the comment data when it’s ready. We wrap <CommentList> in a <Suspense> boundary so that we can render the post body before <CommentList> and its data are ready. This same pattern can be applied to other frameworks as well. For example, apps that call a REST API might make parallel requests to fetch the body and comments data for a post to avoid blocking on all the data being ready.

Treat Code Like Data

But there’s one thing that’s still missing. We’ve shown how to preload data for a route — but what about code? The example above cheated a bit and used React.lazy. However, React.lazy is, as the name implies, lazy. It won’t start downloading code until the lazy component is actually rendered — it’s “fetch-on-render” for code!

To solve this, the React team is considering APIs that would allow bundle splitting and eager preloading for code as well. That would allow a user to pass some form of lazy component to a router, and for the router to trigger loading the code alongside its data as early as possible.

Putting It All Together

To recap, achieving a great loading experience means that we need to start loading code and data as early as possible, but without waiting for all of it to be ready. Parallel data and view trees allow us to load the data for a view in parallel with loading the view (code) itself. Fetching in an event handler means we can start loading data as early as possible, and even optimistically preload a view when we have enough confidence that a user will navigate to it. Loading data incrementally allows us to load important data earlier without delaying the fetching of less important data. And treating code as data — and preloading it with similar APIs — allows us to load it earlier too.

Using These Patterns

These patterns aren’t just ideas — we’ve implemented them in Relay Hooks and are using them in production throughout the new facebook.com (which is currently in beta testing). If you’re interested in using or learning more about these patterns, here are some resources:

• The React Concurrent docs explore how to use Concurrent Mode and Suspense and go into more detail about many of these patterns. It’s a great resource to learn more about the APIs and use-cases they support.
• The experimental release of Relay Hooks implements the patterns described here.

• We’ve implemented two similar example apps that demonstrate these concepts:

  • The Relay Hooks example app uses GitHub’s public GraphQL API to implement a simple issue tracker app. It includes nested route support with code and data preloading. The code is fully commented — we encourage cloning the repo, running the app locally, and exploring how it works.
  • We also have a non-GraphQL version of the app that demonstrates how these concepts can be applied to other data-fetching libraries.

While the APIs around Concurrent Mode and Suspense are still experimental, we’re confident that the ideas in this post are proven by practice. However, we understand that Relay and GraphQL aren’t the right fit for everyone. That’s ok! We’re actively exploring how to generalize these patterns to approaches such as REST, and are exploring ideas for a more generic (ie non-GraphQL) API for composing a tree of data dependencies. In the meantime, we’re excited to see what new libraries will emerge that implement the patterns described in this post to make it easier to build great, fast user experiences.

Popular instant messaging platform, WhatsApp, has rolled out a new feature that allows users to view content from Facebook and Instagram within the app. The update is expected to increase user engagement in the messaging platform.

The latest update has been rolled out for select iOs users. WhatsApp support will allow users to play Instagram and Facebook videos within the app, without exiting the chat. Presently, a user who receives videos or images from Facebook, Instagram or any such app would be redirected to these apps to view the content. However, this is set to change with the new update, reports The Verge.

The latest update also introduced the ability to add and revoke admin privileges from users in a group chat. It empowers admins to edit the subject, description, and icon of a chat that is already underway. In November 2017, WhatsApp rolled out an update through which one can view YouTube videos directly inside the messaging app, in picture-in-picture mode.

If a YouTube link has been sent on a conversation, then users can directly view the video through the link on WhatsApp itself, as it will no longer be re-directed to YouTube. Instead, the YouTube clip will appear within a small floating window on your screen, thus implying that you can watch YouTube videos and message at the same time.

On a related note, the update is also expected to be rolled out to Android users in the coming weeks.

(Edited by mid-day online desk, with inputs from ANI)

Catch up on all the latest Mumbai news, crime news, current affairs, and also a complete guide on Mumbai from food to things to do and events across the city here. Also download the new mid-day Android and iOS apps to get latest updates

Representational picture

San Francisco: A data set of over 3 million Facebook users collected via a personality app was available to download freely for anyone for almost four years, New Scientist reported. The data set was collected via the personality quiz app "myPersonality" by academics at the University of Cambridge.

"The data was highly sensitive, revealing personal details of Facebook users, such as the results of psychological tests.

"It was meant to be stored and shared anonymously, however such poor precautions were taken that deanonymising would not be hard," the report said.

The data sets were controlled by David Stillwell and Michal Kosinski at the University of Cambridge.

"More than 6 million people completed the tests on the myPersonality app and nearly half agreed to share data from their Facebook profiles with the project," said the report.

Alexandr Kogan, at the centre of the British political consultancy firm Cambridge Analytica scandal, was previously part of the project.

"Cambridge Analytica had approached the myPersonality app team in 2013 to get access to the data, but was turned down because of its political ambitions," the report said.

Facebook last month suspended "myPersonality" from its platform, saying the app may have violated its policies.

The social media giant on Monday said that is auditing each and every app that has access to the data of its users and has already suspended 200 apps which failed to comply with its policies.

The company CEO Mark Zuckerberg had promised a thorough investigation and audit into apps that had access to information before Facebook changed its platform policies in 2014 -- significantly reducing the data apps could access.

"To date, thousands of apps have been investigated and around 200 have been suspended -- pending a thorough investigation into whether they did in fact misuse any data," Facebook said.

If Facebook finds evidence that these or other apps did misuse data, it will ban them and notify users via Help Centre on its website.

Appearing before the US Congress in April, Zuckerberg told lawmakers that his own personal data was part of 87 million Facebook users that was improperly shared with Cambridge Analytica.

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

Representational picture

A recent study conducted by a popular dating website on over 5,000 smartphone users above the age of 18 has some interesting findings regarding their dating behaviour. According to the results, Android users are apparently judged 21 times more negatively by iPhone users for using a smartphone running an Android OS.

On the other hand, Android users are likely to judge an iPhone user 15 times more negatively.

The study found that one major reason for this is the possibility of an iPhone user belonging to a higher income strata than an Android user. 40 per cent more than the median Android users earn lesser money than an iPhone user per year, which would a deciding factor, when it comes to going on a date.

Additionally, the study found that 15 per cent of adults, who are currently dating would think twice before dating someone with a cracked smartphone screen. This is regardless of whether the person is a iPhone or Android user. Other aspects like bad grammar, bad fashion sense, crooked or discoloured teeth also played a role in their decision making.

India's star footballer Sunil Chhetri has gone out of his way in order to help a fan who approached him online in order to get a free Netflix account.

Not only did Sunil Chhetri give the fan a Netflix subscription but also handed him a personally signed jersey.. This was after this fan had asked Sunil Chhetri to share his Netflix ID and password during coronavirus pandemic. The fan also stated that the football captain could change the password after the lockdown is done.

Taking to Twitter, Sunil Chhetri posted a screenshot of a message he received on Facebook and wrote: "Jersey X Autograph on a picture X Reply to the post X Video wishing the neighbour's son's pet dog X. Here's someone who has priorities straight and it's really making me want to consider the demand."

Netflix India's Twitter handle took note of this message from Chhetri and went on to reply: "While we on that topic, could we also get your autograph on a picture?"

In the true spirit of a barter, how about you guys hand the kid a two-month subscription and I'll send a signed shirt and a picture your way? Do we have a deal? https://t.co/Ub0WaMcutg

— Sunil Chhetri (@chetrisunil11) May 3, 2020

Sunil Chhetri then proposed a 'barter' deal and asked for a two-month free subscription for the fan in return for an autographed jersey from him.

He wrote: "In the true spirit of a barter, how about you guys hand the kid a two-month subscription and I will send a signed shirt and a picture your way? Do we have a deal?"

In reply, Netflix India's Twitter handle posted: "How about we send him both the jersey and a subscription card? Let's make his day."

To this, Chhetri replied: "Sounds great guys, now that we've got this figured out. Subscription for the kid, Shirt for the kid, Shirt for you guys."

The boy had earlier sent a Twitter post to Sunil Chhetri. Take a look at the shared post by the footballer.

Jersey ❌
Autograph on a picture ❌
Reply to the post ❌
Video wishing the neighbour's son's pet dog ❌

Here's someone who has priorities straight and it's really making me want to consider the demand. 😂 pic.twitter.com/OdBGrS7g5v

— Sunil Chhetri (@chetrisunil11) May 2, 2020

Earlier, in a series of tweets, Chhetri had announced that the members of the Indian team had come together and 'put on table a sum that has been sent to the PM-Cares Fund' to help in the fight against coronavirus.

Inputs from IANS

Catch up on all the latest sports news and updates here. Also download the new mid-day Android and iOS apps to get latest updates.

Mid-Day is now on Telegram. Click here to join our channel (@middayinfomedialtd) and stay updated with the latest news

This story has been sourced from a third party syndicated feed, agencies. Mid-day accepts no responsibility or liability for its dependability, trustworthiness, reliability and data of the text. Mid-day management/mid-day.com reserves the sole right to alter, delete or remove (without notice) the content in its absolute discretion for any reason whatsoever

Representational Image

It may sound audacious to some but Facebook thinks that sharing with a trained employee of the company the intimate images that you fear might go viral in the social networking platforms can help it stop their spread, thereby protecting your privacy.

The social networking giant on Tuesday said it was testing a reporting tool so that people who worry that someone might want to harm them by sharing an intimate image can proactively upload it, which will eventually help Facebook to block anyone else from sharing it on Facebook, Instagram, or Messenger.

Facebook said it entered into partnership with safety organisations on a way for people to securely submit photos they fear will be shared without their consent -- images that are also referred to as "revenge porn" or "non-consensual pornography".

"This pilot programme, starting in Australia, Canada, the UK and US, expands on existing tools for people to report this content to us if it's already been shared," Antigone Davis, Facebook's Global Head of Safety, wrote in a Facebook post.

From anxiety and depression to the loss of a personal relationship or a job, the result of having most intimate moments shared without permission can be devastating for a person.

And while these images harm people of all genders, ages and sexual-orientations, women are nearly twice as likely as men to be targeted, Davis said.

"This week, Facebook is testing a proactive reporting tool in partnership with an international working group of safety organisations, survivors and victim advocates, including the Australian Office of the eSafety Commissioner, the Cyber Civil Rights Initiative and The National Network to End Domestic Violence in the US, the UK Revenge Porn Helpline and YWCA Canada," Davis added.

As part of this initiative, anyone who fears an intimate image of them will be shared can contact one of Facebook's partners to submit a form.

After submitting the form, the victim receives an email containing a secure, one-time upload link. The victim can use the link to upload images they fear will be shared.

Thereafter, one of a handful of specifically trained members of Facebook's Community Operations Safety Team will review the report and create a unique fingerprint, or hash, that allows the social network to identify future uploads of the images without keeping copies of them on its servers.

Facebook said once it creates these hashes, it will notify the victim via email and delete the images from its servers within seven days.

"We store the hashes so any time someone tries to upload an image with the same fingerprint, we can block it from appearing on Facebook, Instagram or Messenger," Davis added.

Catch up on all the latest Crime, National, International and Hatke news here. Also download the new mid-day Android and iOS apps to get latest updates

Facebook had announced a redesign of its desktop version in the F8 conference this year. Now, it is officially available for all users around the globe.

Jio has also announced new add-on data packs under work from home theme

Learning to deliver on their promise in Africa

In a fresh bid to empower its over 300 million users, the micro-blogging website Twitter on Wednesday made it easier for them to report cyberbullying.

Giving more power to its 1.2 billion daily users, Facebookwill now allow them to automatically launch its crisis response tool "Safety Check" in case of an earthquake, terror attack, tsunami and so on.

Virginia-based security firm Kryptowire recently reported that there are few Android devices from a Chinese company that are infected with software that collects users’ personal information and conversation made through text messages and calls.

Giving more power to its 1.2 billion daily users, Facebookwill now allow them to automatically launch its crisis response tool "Safety Check" in case of an earthquake, terror attack, tsunami and so on.

As website owners, we are continuously trying to rework on the existing design, to upgrade it to something more contemporary and user centric. As the online visitors instill...

Full Article