by @JoBrodie – who hopes you’ll tell her about other alternatives you know of 🙂

This post is a work in progress as I am currently trying out the different tools available.

Storify is closing its doors on 16 May 2018 and all content will become unavailable. Any time before that point you can download your own (and other people’s stories). To avoid having to keep writing Storify stories I’m just going to call them Stories for now.

Table of contents

Capturing Storify stories (aka Stories)

… your own

… or anyone else’s

Other capturing options

Re-publishing your Stories

Alternative tools for future use

The search continues…

1. Capturing Stories

Storify‘s cheerily named ‘End of Life’ FAQ can be found here: https://storify.com/faq-eol – follow the instructions in the section called “How do I export content from Storify?”

1.1 Capturing your own Stories

You can save your Stories as .XML, .HTML or .JSON files. When I tried with the HTML I was expecting a page of code but ended up with something that wasn’t quite that, and which I couldn’t embed into a new post. However you can still use the Save As option to save it as a web page (or as a PDF). You’d need to do this for each of your Stories.

You can also save as a web page by sticking .html at the end of any Story URL, then saving the resulting page.

Wakelet, a free tool, will very helpfully let you export all of your published Stories to its platform and it will automatically publish them for you once done. This works very well. I had 43 published Stories and I set it running last night and woke up to all of them being migrated (I think it probably didn’t take the whole of the night to happen!). So far it has the Jo seal of approval*.

To use it you need to sign up (free, I logged in through Google). You’ll be given a bit of text to add to your Storify profile (a sort of handshake) then you can start the process and select the published Stories you want to import.

You need to insert the bit of text in Step ‘1’ into your Storify bio then complete Step ‘2’ and let it get on with it. There’s also an explanatory video.

For unpublished / draft Stories you can either publish them and do the above, or just get the draft on-screen and save it as a web page.

Sutori, also a free tool, that lets you export your Stories to them too. Here’s their blog post responding to the news of Storify closing. Once you’ve registered you can create a new Story and one of the options is to import from Storify.

Click the ‘Create story’ button on the left, then choose ‘Import from Storify’ that pops up.

Comparison
Here’s the same content, imported from Storify, on Wakelet and Sutori. I think Wakelet wins this particular test because it shows the text of a deleted tweet. I created the Storify in 2011, included in it a tweet that I later deleted to see what happened (the tweet persisted) Storify original | Wakelet import | Sutori import

1.2 Capturing someone else’s Story

Sticking .html at the end of any Story URL, then saving the resulting page. I don’t think you can use Wakelet to capture other people’s Stories, but you can with Sutori (however if they receive a ‘please remove’ request from the person who originally wrote it they will delete it).

1.3 Other capturing options

With short Stories you could copy the link for each ‘atom’ that makes up your Story (tweets, YouTube video links etc) and insert them individually into a WordPress dot com blog, but this would be ridiculously labour-intensive for larger Stories. Screenshotting / screencapturing is also an option, or using tools like Freezepage etc.

2. Re-publishing your Stories

Wakelet will automatically take care of that, your Stories now have a new web address (which brings its own annoyance but at least they’re published).

For Stories saved as web pages (or as text, then perhaps as a PDF) you could either upload the PDF to your website (eg a free WordPress dot com blog, like this one) or put the file in something like free Dropbox and share the link wherever you like.

3. Alternative tools for future use

Wakelet – this seems to be the most similar to Storify so far (I have not tested it for creation of new Wakelets, only for importing old Stories)

Sutori – (how to create a Sutori story guide) I have created an example Sutori with four of my tweets. I think it looks nice but seems to be too labour-intensive for collecting larger volumes of tweets. Possibly I need to spend a bit more time with it.

Shorthand Social – I’ve not tried this yet but clearly it lets you embed tweets. I don’t know if it lets you add them at the same volume that Storify did though (several hundred at a time). Here’s their ‘guide to Shorthand Social‘ post.

Participate – I have not tested this but it a colleague mentioned that it can save old Storify posts.

Twitter threading – if you’re just interested in collecting together a bunch of tweets then create a thread, encouraging people to reply to that (you can use the Unroll tool to get all the participating tweets in one collection). Admittedly this doesn’t work as well if you have a bunch of conversations going on based around a hashtag.

Twitter Moments – I think this only works for tweets, don’t think you can add in YouTube links (but I haven’t tried so maybe you can).

WordPress dot com blogs – many things will embed into WordPress blogs. I use the free .com version so am a bit more restricted than the .org versions (where you have to download software and you’d have your own server) but you can easily add a tweet’s link and it will autoembed as the full tweet (it will remain if deleted too).

4. The search continues…

I wanted to find out what people on Twitter were recommending as an alternative and searching there for Storify alternatives brought up Wakelet as the clear winner, in part because they have been very proactive in contacting people tweeting that they’re seeking alternatives – a sensible use of targeted marketing! There are also lots of people recommending it.

To find additional options I ran the same search but added -wakelet to remove tweets mentioning that to let me see the other options more clearly, that highlighted Sutori and Shorthand Social. Chatting on Twitter let me hear about Participate.

*Re: Wakelet importing
Obviously some things are lost in the transfer – eg the view count, the date of publication and any embedded Stories within a Story will eventually be lost. I tried and failed to add a link to the Wakelet version of one of mine. The Wakelet URL for an imported story is alphanumeric rather than following the pattern of Storify which has its domain / the user name / the name of the Story – that would have been helpful but fairly minor compared to losing all the Stories and the effort involved in capturing them!

Twitter seems to be fiddling about while Rome burns. Its latest daftness is to double everyone’s character limit, from 140 to 280. Of course plenty of tweets are still nowhere near the new character limit but too many of those that are can make scrolling on a phone a bit disheartening. To be honest I thought the rot set in when Twitter made images automatically appear (rather than clicking to view) 😉 I’m sure we’ll all get used to this and in a few months Twitter will give us something new to bleat about.

If you’re on Firefox there are at least two addons that have been created in the last couple of days. I tried out the one called proper length tweetsand it’s working fine for me. There’s also one called Tweet Truncatorwhich I’ve not tried.

You can also use Dabr which is a simplified browser-based version of Twitter which won’t let you write more than 140 and truncates longer tweets. No addons needed, just authorise it to interact with your Twitter account and away you go.

Similarly Tweetbot apparently lets you play with regular expressions to prune out any tweet that’s longer than 140 – though I think this would actually remove it from your timeline, rather than showing a truncated version which I’d prefer.

As far as I can tell if you’re blocked you can no longer directly reply to a tweet sent by an account that’s blocked you. However you can send them a new at-message tweet (they probably won’t see it given that they’ve blocked you) and you can still contribute to their conversation thread by replying to an intermediary tweet (ie by sending a reply to someone who has (a) already replied to the tweet and (b) hasn’t blocked you). But do be polite or your account may be suspended 🙂

I’ve tested direct replies to an account thats blocked me using the following apps / platforms and received an error message on each – cannot send a direct reply from any of them. If you know of one that works please let me know.

Twitter on desktop and for iPhone

Tweetdeck

Echofon (iPhone)

Dabr.co.uk

Janetter (iPhone)

Twitter would do better to stop people from being able to send tweets to the at-name of anyone that’s blocked them, as this current loophole-closure doesn’t stop replies-to-replies or new conversations.

It does make it a bit harder for me to correct the misleading tweets that homeopathy supporters send out – a few of them have blocked me, and other “anti-homeopathy skeptics”, for pointing out that homeopathy is not valid medicine.

Updated 22 Aug 2018 – I search periodically for this post on Twitter because people often share it, then reply to themselves with some other useful thing they’ve found and that’s why this post keeps getting longer! Also check the comments for additional suggestions.

Let’s get rid of other people’s likes on Twitter!

Options known about so far… the first six involve using website Twitter, the sixth is info sent to me about a phone app. Numbers 2-5 involve workarounds to improve the experience on Twitter.com

2. AdBlock Plus with Element Hiding Helper (Firefox)
It’s the Element Hiding Helper that does the heavy lifting here, although AdBlock Plus by itself gets rid of the sponsored tweets. Generally I don’t really mind sponsored tweets (I’m happy for Twitter to advertise to me) but I’m not interested in who to follow or trends and the additional bolt-on lets me get rid of that.

When you see a tweet that’s been inserted into your timeline because someone’s liked it call up the Element Hiding Helper. It lets you select an area containing the offending tweet (be careful not to select too much, or too little) and remove it from view. It might take a few attempts to catch all the slightly different variants (oh there are variants!) but I’ve found it to be very successful. You can also wipe out Moments, Trends, Who To Follow panels from around the main timeline and you can eliminate things inside the timeline too.

Here’s what my page looks like. I’ve got rid of Moments and the Analytics panel. On other pages you’d see the lack of Trends and Who to follow…

Here’s a clip of what I see on my mentions (for privacy I’ve not shown any tweets as some are from locked accounts). There’s a white panel containing tweets in the middle and two lovely clear grey panels on either side, with nothing in them at all 🙂

NOTE that doing this may cut out other tweets from your timeline. I’ve found that if I have this switched on I may miss replies, and some of my own tweets (particularly those with images) are hidden, so it’s worth toggling between pruned and unpruned timelines periodically to check. It’s not perfect.

3. UBlock Origin filter

Thanks to an update from gorhill in the comments below it looks likely that if this tweet doesn’t render correctly on your screen you’ll see mangled instructions. I’ve added a screenshot of the same tweet below the embed (some browsers will show both correctly)

Annoyed at other peoples' likes showing up in your twitter feed? Do you use UBlock Origin? Add this to your filters: https://t.co/XPHZ0wOwyW##[data-suggestion-json*=ActivityTweet]

3a. Chrome Extension: Make Twitter Great Again
“Hide liked tweets by others in timeline, hide Live Video, promoted tweets and others improvements for Twitter” (link) – apparently Opera can also use the same apps as Chrome.

3b. Chrome Extension: Get rid of trending topics
Andy (@digitonal) also shared a tip for getting rid of trending topics on Chrome using the Stylish extension to run a custom rule for Twitter.

.Trends {
display: none;
}

3c. Chrome Developer tools: Block all RTs (except manual or quote RTs)
Nick Douglas has written a helpful post on Lifehacker with instructions on how to do this for Chrome browser users: How to disable all retweets on Twitter (6 March 2018)

4. User styles – Twitter: Hide likes in timeline feed with Stylish
Note – read Kyle‘s comment below (jump to the comment) for info on privacy concerns with Stylish, and an alternative that works with Chrome.

I have to admit I’m not entirely sure what this is. It’s some sort of CSS style that you can apply but I’m afraid I wouldn’t know how or for which browser (perhaps all browsers). I’m unlikely to investigate further as my solution (option 2) works fine but here’s the link and how I heard about it.

5. Dismiss every liked tweet with ‘I don’t like this tweet’
Every tweet has a small arrow to the top right with options in (highlighted in blue below). For these liked tweets one of the options is ‘I don’t like this tweet’ or ‘show me less of this’ (not seen in the example below because it’s a different type of tweet) – select that and after a few times apparently the annoyance will go away.

I don’t use this method myself in case it causes problems for the person who’s tweet has been liked but it seems to work, though takes longer (and one advantage is that it does actually tell Twitter you don’t like it whereas my preferred method gives no feedback).

Picture below is illustrative. Because it wasn’t promoted to me as a ‘someone liked this’ the “I don’t like this” option isn’t available from the drop-down menu, but that’s where you’d find it if you had one of these tweets in your timeline.

6. Use a list of people you follow as main timeline

George in the comments below suggested this one and it’s got potential! Create a list (give it a nice name so no-one will be annoyed when they find they’ve been added) add the people whose tweets you would like to see and then view that list instead of your main timeline. You’ll see only the tweets of the people you’ve added and you won’t see any additionally inserted tweets that Twitter wants you to know about. Thanks George!

BackgroundI follow over 2,000 people on Twitter so obviously I don’t see every one of their tweets, but I can live with that. If I need to catch up with someone’s tweets I can look at their profile. Twitter went through a phase of showing me ‘things you’ve missed’ while I’d been away, which was annoying. There’s also an option where you can be shown the ‘best’ tweets rather than the straightforward reverse-order chronological timeline. Fiddling about unnecessarily.

More recently Twitter’s started sharing, in your main timeline, tweets that other people have liked. Ironically I don’t think anyone likes this, I hate it. Even though some of the tweets are pretty good it really annoys me. Liking or favouriting on Twitter has usually been a semi-public act, in that you can go and look at someone’s likes if you wish, but otherwise they’re not ‘surfaced’ to your timeline, and now they are. I vaguely remember Twitter having an Activity tab where it showed what your friends were liking but it was short-lived.

No-one’s found an option that lets you switch this off (which is odd given that you can select options for almost everything else that Twitter displays) but here [above] are a few suggestions.

This bit moved to the end for clarity after I spotted this tweet. Good point well made, I am quite chatty. See it’s 4 paragraphs now 😉

Some people are suing President Trump because he’s blocked them on Twitter. They argue that doing this stops them from reading or replying to his tweets and, by extension, means that their opinion cannot be made available to others who are reading the thread.

This is not true.

While I am not a supporter of President Trump this lawsuit appears to be based on a misunderstanding of what Twitter’s block actually means (to be fair this misunderstanding is very widespread). Perhaps if I were a lawyer I’d see some merit in the lawsuit but it currently eludes me, it seems to me to be daft, incoherent and wrong.

A block from an otherwise unlocked / public account wouldn’t stop anyone from reading the tweets or even replying to them (though locking the account certainly would).

Reading tweets from someone who’s blocked you, while logged in
If a user has blocked you simply search for their tweets (eg from:realdonaldtrump). I’ve tested this using a work account that blocked my personal account and it works on desktop Twitter, Tweetdeck, several iPhone apps, Dabr.co.uk and probably most Twitter platforms and apps.

Enthusiasts could set up an account with IFTTT and have any public account’s tweets emailed to them, or they could use another account to create a website widget which relays the tweets there.

Replying to tweets from someone who’s blocked you, while logged in
On desktop Twitter you need to click on the speech bubble icon to bring up the reply window (see the pics below). If you click on the tweet itself you’ll be taken to the ‘you are blocked’ page. On all the other platforms I’ve tested, including Tweetdeck, you can click on the tweet and reply to it.

Everyone else clicking on the tweet you’re replying to can see your reply*.

Viewing a “this tweet is unavailable” tweet that’s quote-RTed by someone else
In this scenario I’d simply right-click, open in private browsing window where you can view the tweet while not logged in. You can reply to the person who quoted the tweet while logged in to the regular browser window.

If an account blocks you can they see your tweets? Yes they can, though as your tweets aren’t delivered to them they won’t see them unless they want to. So, practically speaking, this might be ‘no’.

If anyone wishes to ‘not see tweets from someone’ while ‘avoiding being sued for blocking them’ then I strongly suggest MUTE as the better choice. If you are not following an account then MUTING them stops any tweets they send you from arriving. They don’t know they’re muted and can read and reply to your tweets (which others can see, but you won’t).

On desktop and iPhone Twitter (I’ve not tested other apps) you can arrange your settings to that you’ll only see tweets from accounts that you follow, which is basically the equivalent of muting everyone except accounts you follow. Again, no-one else knows.

*Twitter doesn’t show all replies
I don’t know how Twitter determines which tweets it will or won’t show, it may be algorithmic or it may be based on other users flagging up tweets as offensive. Occasionally in a thread I see ‘view more tweets, including those that may contain offensive content’ and they’re rarely all that offensive. Even if Mr Trump hadn’t blocked your account your replies to him might not be shown to him.

Worked example, with pictures
I’ve just blocked myself (@jobrodie) using one of my old work accounts @chi_med. The pictures below show me what I see / don’t see, and how I can reply to the tweet of an account that’s blocked me.

Fig 1. @chi_med has blocked @jobrodie. When I’m logged in as @jobrodie I see a ‘you are blocked’ page if I try and look at @chi_med’s profile

Fig 2. While logged in as @jobrodie I’ve searched for tweets from @chi_med by typing from:chi_med into the search bar, the results are clearly visible. Note the small speech bubble at the bottom left of every tweet – that will let me reply to the tweet.

Fig 3. This is what I see if I click on one of the tweets (instead of the speech bubble to reply) – I’m taken back to the ‘you are blocked’ page from Fig 1, this is its URL.

Fig 4. Clicking the speech bubble brings up a reply window.

Fig 5. I’m not logged in, but the tweet from @chi_med now displays my reply – visible to all.Fig 6. How the tweet looks when I’m logged in as @chi_med. I can see that there has been a reply (see the little ‘1’ next to the speech bubble) but I can’t see what the tweet says because I’ve blocked the account that sent it. Others would see the tweet though.

How to open up a tweet or conversation thread to your public timeline without quote-tweeting it (which breaks any threading as that creates a new tweet).

Updated – whether or not your mobile phone app can or can’t do the .@ may depend on the version of your software (eg iOS) or whether or not you’ve updated the app.

Mobile phone users
Carry on as you were by clicking the start of the reply to position the cursor there and typing the . as normal (tested on Twitter for iPhone, Echofon for iPhone and Twitter for Android – I’m assuming other apps behave similarly but please let me know if not).

@Flatsquid tells me that he can’t do this on his version of Twitter for iPhone (whereas I can) so this may be a version issue. I don’t have an option to update my version so can’t confirm, though I am using an older iOS.

Tablet usersTwitter for iPad can’t do .@
Twitter on Safari doesn’t work either but it seems that using Dabr on a browser does (thanks @medtek for checking). Open browser app, go to http://dabr.co.uk/ and log in by authorising with Twitter credentials. Click reply and place the . at the front. Possibly Echofon for iPad would work too.

Web usersTwitter dot com and Tweetdeck can’t do .@
1a. On Twitter dot com or Tweetdeck reply within the confines of the new system
1b. Then retweet your own tweet – this makes it available to all your followers and maintains the thread so people can click and see the conversation.

OR

2. Dabr: Go to http://dabr.co.uk/ and log in by authorising with Twitter. Click reply and place the . at the front.

What’s this all about?
Twitter’s latest improvement meddling has removed the capacity to insert a . before the username of the person you’re replying to on the desktop / web browser version of Twitter (eg Twitter.com or Tweetdeck). The simple addition of the . before the @ did two things (a) it converted a reply (which has a more limited distribution to those involved in the conversation and people following both them and you) to a broadcast tweet (visible to anyone following you) so that more could see it while (b) maintaining the threading, letting people click and see the expanded tweet in context. [Note that any tweet sent is visible on your public timeline unless sent as a DM or you’ve locked your account.]

In the new format Twitter has removed the usernames from the text of the tweet (giving us more characters, a potential plus I suppose) but making all replies replies and not easily ‘surfaced’ to more people.

I think this ONLY affects people tweeting from Twitter dot com and Tweetdeck, phone apps appear to be unaffected (may depend on OS version or app version).

I have no idea why Twitter has done this. I’m assuming they want to make desktop Twitter as difficult as possible to use to force everyone onto mobile apps, though that doesn’t make sense since there are so many things you can’t do (in terms of settings) on mobile apps. People have suggested that it reduces the risk of people piling on in response to a more publicised tweet – that would only be true if .@ was also removed from mobile apps or you couldn’t retweet your own tweet (which serves the same purpose, but perhaps doesn’t cue people in the same way that seeing .@ does). Possibly this will change in future.

Removing / adding people in the conversation
The other annoyance with Twitter’s new replies is that it adds an extra hassle barrier in untagging people from the conversation. They have now added a ‘remove everyone other than the person I’m replying to from this conversation’ one-click option.

Clicking ‘reply’ has always meant ‘reply all’ but the previous system made it easy to select the usernames as a chunk of text and delete, now you have to go and look for them. To do this click reply, then click on the line above saying ‘Replying to @name, @name etc’ and choose the options to delete people. You can write the names of new additions within the tweet – so there’s one way to remove people but a different way to add them, which seems confusing.

Edit 8 September 2017 – it looks like Twitter’s finally fixed this loophole. More testing needed but it appears that you can no longer reply to an account that has blocked you. This is a big improvement at first glance (although I can no longer correct nonsense spouted by homeopaths who’ve blocked me). You can send them new tweets but cannot use the loopholes below to reply to a tweet, so no more contributing to threads. Unless you reply to another reply, in which case you can.

Added 5 June 2017 – it seems that you no longer need to use third party apps when using Twitter / Tweetdeck on a desktop computer with a browser. You can see the tweets of people who’ve blocked you appearing in search results and you can reply by clicking directly on the reply icon (you can’t click on the tweet on Twitter though, though can on Tweetdeck). Or at least I can.

If you’re replying to someone who’s blocked you please try and be polite – your tweets are still subject to Twitter’s community rules and terms of service. Also, remember that the person who’s blocked you won’t actually see your replies (unless they want to), but everyone else can.

Here’s the original post…

tl;dr– use these third party apps – Dabr (desktop) or Echofon or Janetter on iPhone.

Remember that people you've blocked can still (a) see and (b) reply to your tweets. Think most ppl know (a), not so sure they know (b).

This post serves two purposes – mainly to let more people know that if you’ve blocked someone they can still reply to your tweets (and that other people can see and interact with those replies) and to highlight to skeptical or political activists that it’s still possible to correct misinformation tweeted by “the other side” (which of course works both ways!).

Over the years I’ve been blocked by lots of alternative medicine providers and supporters, particularly homeopaths and people flogging live blood analysis. Some of them are pretty harmless but a handful persist in tweeting misleading and occasionally dangerous health information. In those cases I think it’s worth replying to those tweets so that whenever anyone else clicks on them they might see the threaded replies with more correct info.

I think most people now know that if you block someone they can still see your tweets.

Generally this is wrongly believed to involve a bit of effort (in that they’d have to log out and search for your tweets, or log into a different account etc). However if the blockee is using one of the third party apps mentioned below then it involves precisely zero effort – it’s easy to see the tweets and reply to them, particularly if watching a conversation unfold via a hashtag. Most third party apps will now no longer let you view the profile of someone that’s blocked you – but if you’re reading and contributing to a hashtag you’d probably not even notice.

I think fewer people know that blocked people can also reply to your tweets, or retweet them [see note at end], while logged in as themselves rather than some spare account. Remember that if someone’s blocked you the chances are high that they won’t see your reply, but others may well do.

Here’s how they (you / I / we) can do that.

Desktop Twitter

Log into Dabr(http://dabr.co.uk/) by authorising it to interact with your Twitter account, search for a hashtag or the name of someone who’s blocked you – find a tweet, click reply.

Neither twitter.com nor Tweetdeck (now owned by Twitter I believe, so should be considered as an official Twitter app) will let you see tweets from those who’ve blocked you. (Updated 5 June 2017 – I discovered today that this is no longer the case and it’s possible to both view, and reply to, these tweets through web Twitter or Tweetdeck – this may change back to how it previously was of course!).

iPhone

*Note* I do not automatically update my apps, or my iOS version (it all works fine as it is so no particular pressure to do so). This may mean that my version is working while your updated one doesn’t – obviously I can’t really test this, so be aware of that if it doesn’t work for you.

Echofon and Janetter Download the app (I think free / ad-supported versions are available), log in, search for hashtags or names and click on a tweet to reply. You won’t be able to view their profile (but can see their tweets fine in hashtag- or name-search results though).

Neither the official Twitter for iPhone app nor Osfoorafor iPhone will let you reply to the tweets. You can see them on Osfoora but not Twitter for iPhone. I’ve not tried any other iPhone apps. Mobile Twitter (viewing mobile.twitter.com on Safari on iPhone) blocks the tweets entirely too, no viewing (and obviously no replying).

Google, Android or other phones I don’t know about

At this stage I don’t know. It used to be Fenix for Android which let people see tweets from those who’d blocked them but I believe that’s no longer possible so I’m not sure which apps would do this, if any. I’m hoping that someone reading this might let us know and I’ll update the post.

Supplemental:
probably more than you wanted to read about Retweeting

There are a few ways to retweet someone’s tweet – 1 and 2 won’t be available if you’ve been blocked though, but 3 and 4 are

‘Native’ RTing – on desktop Twitter you would click on the retweet button, it asks you to confirm and if you say yes the RT button goes green and this adds ‘1’ to the tweets RT count

Quote RT – on desktop Twitter this is identical to (1) but this time you add a comment and the green button stays grey and the counter doesn’t increase

Retweet with Comment – on Echofon for iPhone this manually pastes the text into the tweet and lets you edit it and add your own comment

Retweet as Quote – on Echofon for iPhone this manually pastes the tweet’s URL / link into the tweet and lets you add a comment.

I’m sure other variants are available but I’ve not tried it on Janetter or Dabr

Both 3 and 4 work if you’re blocked.

Watch out with 4 though as the tweet would normally show up as an embedded tweet but if you’re blocked it will instead show up as ‘This tweet is unavailable’. On seeing that message many of your followers might reasonably assume that the tweet has been deleted or that the user has blocked them. They might not realise that they’ll be able to see the tweet fine if they click on it, and it’s only you who has been blocked – so be aware that (4) may be a bit confusing and (3) may be better.