Social media offers many people a level of anonymity that would be hard to achieve outside of online life. This is sometimes used by individuals to share negative or harmful messages, while avoiding repercussions that may affect their ‘offline life’. But is this really the case, and can so-called ‘trolls’ really hide behind a screen?
The recent case of Colliers & Others v Bennett  EWHC 1884 seems to say no.
The case relates to an anonymous Twitter account named Harry Tuttle (@arrytuttle) that engaged in heated online arguments about anti-semitism with the claimants, including Rachel Riley of Countdown fame and blogger David Collier. It is alleged that the @arrytuttle account posted defamatory tweets and harassed the claimants – but how do you sue an anonymous account?
In July 2019, Daniel Bennett – a former barrister – was outed by another Twitter user as a possible owner of the @arrytuttle account. Immediately following this, the account and all its tweets were deleted. Daniel Bennent subsequently apologised to some users for some tweets from the @arrytuttle account.
The claimants wanted to obtain proof as to who tweeted from @arrytuttle, and to obtain copies of the offending tweets. They applied for both pre action disclosure and a Norwich Pharmacal order, which is an order which requires disclosure of documents to show the identity of a wrongdoer.
After hard fought argument, the court ordered in favour of two of the claimants and Daniel Bennett was ordered to identify who used and had access to the @arrytuttle twitter account between March 2018 and 9 July 2019.
He was also ordered to disclose a narrow category of tweets that could be defamatory about the two successful Claimants (including Rachel Riley). The tweets metadata and analytics are also to be disclosed.
It will be interesting to see whether this results in further action being taken and the impact this has on the behaviour of anonymous accounts online.
|__hssrc||session||This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.|
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|__cf_bm||30 minutes||This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.|
|__hssc||30 minutes||HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.|
|ss||session||This cookie is set by the provider Eventbrite. This cookie is used for the functionality of website chat-box function.|
|TawkConnectionTime||session||Tawk.to, a live chat functionality, sets this cookie. For improved service, this cookie helps remember users so that previous chats can be linked together.|
|__hstc||1 year 24 days||This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_162540320_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|hubspotutk||1 year 24 days||This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts.|
|_fbp||3 months||This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.|
|fr||3 months||Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|