IanColdwater/twittermute.txt

liamengland1 · 2020-01-24T23:33:10Z

In case anyone wants to fully automate entering these in. I took @j6k4m8's snippet and expanded on it.

Doesn't work on old twitter design, sadly

shstkvch · 2020-01-25T00:01:03Z

@jakebellacera Thank you so much for doing this, so useful. What's the advantage of using Object.getOwnPropertyDescriptor over just setting the value of the field with document.querySelectorAll("[name='keyword']")[0].value = keyword; as in @j6k4m8's snippet ?

freedmand · 2020-01-25T00:15:14Z

Expanded on @jakebellacera's script to make it work for my browser. Visit https://twitter.com/settings/add_muted_keyword, open your browser's javascript console, and paste the following script in:

const delayMs = 1000; // change this if you feel like its running too fast

const keywords = `ActivityTweet
generic_activity_highlights
generic_activity_momentsbreaking
RankedOrganicTweet
suggest_activity
suggest_activity_feed
suggest_activity_highlights
suggest_activity_tweet
suggest_grouped_tweet_hashtag
suggest_pyle_tweet
suggest_ranked_organic_tweet
suggest_ranked_timeline_tweet
suggest_recap
suggest_recycled_tweet
suggest_recycled_tweet_inline
suggest_sc_tweet
suggest_timeline_tweet
suggest_who_to_follow
suggestactivitytweet
suggestpyletweet
suggestrecycledtweet_inline`.split(/\W+/);

const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, "value").set;

const addMutedKeyword = keyword => {
  const input = document.querySelector("[name='keyword']");
  nativeInputValueSetter.call(input, keyword);
  input.dispatchEvent(new Event('input', { bubbles: true }));
  document.querySelector("[data-testid='settingsDetailSave']").click();
}

const delay = () => {
  return new Promise(res => setTimeout(res, delayMs));
};

keywords.reduce(async (prev, keyword) => {
  await prev;
  addMutedKeyword(keyword);
  await delay();
  document.querySelector('[aria-label="Add muted word or phrase"]').click();
  return delay();
}, Promise.resolve());

j6k4m8 · 2020-01-25T00:39:37Z

You beautiful, wonderful people. Confirmed @jakebellacera's code works for me, latest firefox on 'vanilla' twitter.com. Glad my lines of code found a good home :)

jakebellacera · 2020-01-25T00:46:32Z

@shstkvch glad it was useful to someone. 🙂 The main reason why is because Twitter uses React, and the input is a controlled field, so merely mutating the value on the HTML field does nothing because the application state isn’t aware that the input changed (and therefore you cannot submit the form on the page).

Think4866 · 2020-01-25T00:58:28Z

Thanks for sharing, awesome

vabruce · 2020-01-25T00:58:33Z

Well done, thank you for sharing!

catarino · 2020-01-25T01:19:01Z

In case anyone wants to fully automate entering these in. I took @j6k4m8's snippet and expanded on it.

Visit https://twitter.com/settings/muted_keywords
Open your browser's dev tools (note: this does work in Chrome)
Paste the following code in:

const delayMs = 500; // change this if you feel like its running too fast

const keywords = `ActivityTweet
generic_activity_highlights
generic_activity_momentsbreaking
RankedOrganicTweet
suggest_activity
suggest_activity_feed
suggest_activity_highlights
suggest_activity_tweet
suggest_grouped_tweet_hashtag
suggest_pyle_tweet
suggest_ranked_organic_tweet
suggest_ranked_timeline_tweet
suggest_recap
suggest_recycled_tweet
suggest_recycled_tweet_inline
suggest_sc_tweet
suggest_timeline_tweet
suggest_who_to_follow
suggestactivitytweet
suggestpyletweet
suggestrecycledtweet_inline`.split(/\W+/);

const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, "value").set;

const addMutedKeyword = keyword => {
  const input = document.querySelector("[name='keyword']");
  nativeInputValueSetter.call(input, keyword);
  input.dispatchEvent(new Event('input', { bubbles: true }));
  document.querySelector("[data-testid='settingsDetailSave']").click();
}

const delay = () => {
  return new Promise(res => setTimeout(res, delayMs));
};

keywords.reduce(async (prev, keyword) => {
  await prev;
  document.querySelector("a[href='/settings/add_muted_keyword']").click();
  await delay();
  addMutedKeyword(keyword);
  return delay();
}, Promise.resolve());

also works on Safari.

thx for this
@freedmand :)

apervola · 2020-01-25T01:46:55Z

great work, much appreciated !

superherointj · 2020-01-25T06:05:31Z

Thanks!

vish0l · 2020-01-25T06:57:35Z

thanks

digisavvy · 2020-01-25T07:28:56Z

@freedmand's code worked in my case. +1 would buy again! Where can I send a few bucks for you to get a beverage?

doctoraw · 2020-01-25T08:32:25Z

Thanks ! 🌈

evandrix · 2020-01-25T09:47:08Z

👍

madaboutcode · 2020-01-25T11:37:09Z

The fixed delay in the code was not working all the time for me. So I added a wait until the add page returns before clicking on the add button again.

(function(){
  const delayMs = 500; 

  const keywords = `ActivityTweet
  generic_activity_highlights
  generic_activity_momentsbreaking
  RankedOrganicTweet
  suggest_activity
  suggest_activity_feed
  suggest_activity_highlights
  suggest_activity_tweet
  suggest_grouped_tweet_hashtag
  suggest_pyle_tweet
  suggest_ranked_organic_tweet
  suggest_ranked_timeline_tweet
  suggest_recap
  suggest_recycled_tweet
  suggest_recycled_tweet_inline
  suggest_sc_tweet
  suggest_timeline_tweet
  suggest_who_to_follow
  suggestactivitytweet
  suggestpyletweet
  suggestrecycledtweet_inline`.split(/\W+/);

  const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, "value").set;

  const addMutedKeyword = keyword => {
    const input = document.querySelector("[name='keyword']");
    nativeInputValueSetter.call(input, keyword);
    input.dispatchEvent(new Event('input', { bubbles: true }));
    document.querySelector("[data-testid='settingsDetailSave']").click();
  }

  const delay = () => {
    return new Promise(res => setTimeout(res, delayMs));
  };

  keywords.reduce(async (prev, keyword) => {
    await prev;
    
    // wait till the browser returns to the initial screen before clicking the add button again. 
    while(window.location.href !== 'https://twitter.com/settings/muted_keywords'){
      await delay();
    }
    document.querySelector("a[href='/settings/add_muted_keyword']").click();
    await delay();
    addMutedKeyword(keyword);
    return delay();
  }, Promise.resolve());
            
})()

julianwieg · 2020-01-25T11:48:48Z

thank you!

paaandy · 2020-01-25T12:05:52Z

YES thank you so much, always thought it an assault to force my eyes to read that stuff

mjy · 2020-01-25T17:17:35Z

@TylerBussel - I think you're right, this does nothing, maybe @IanColdwater can edit this gist so this is not burried.

I had been playing with uBlockOrigin settings at the same time as I was playing with these, and going back and replicating, even taking some time to see if things took a while to take effect- I can't see any effect/replicate what I initially saw. And there is this:

https://twitter.com/TwitterSupport/status/1220872428605317122

Though if you read carefully there is wiggle room- they may have some other effect, but that seems to be grasping at straws.

But, until we get proof (screenshots(?)), this is bogus.

joshdance · 2020-01-25T19:34:40Z

I doubt this does anything.

Direct quote from Twitter "Hi Ian, muting these keywords won't actually change the number of suggested Tweets in your timeline. We are exploring ways to improve suggestions to allow you to further customize your timeline. More to come!" source - https://twitter.com/TwitterSupport/status/1220872428605317122

Reason is none of these words actually appear in the tweet body. It is not 'mute meta data about tweets' it is 'mute words' which presumably only are in the tweet body.

Nerjuz · 2020-01-27T06:35:13Z

❤️

GuillaumeRossolini · 2020-01-27T07:18:58Z

To the people for whom this didn't work: try switching your timeline back to chronological (instead of popular, or however it is called).
@TylerBussel @ronaldKM98 @mjy @joshdance

heygambo · 2020-01-27T09:39:19Z

This seems interesting but I'm not 100% sure what it does 😅

horvaro · 2020-01-27T11:55:10Z

❤️

The fixed delay in the code was not working all the time for me. So I added a wait until the add page returns before clicking on the add button again.

(function(){
  const delayMs = 500; 

  const keywords = `ActivityTweet
  generic_activity_highlights
  generic_activity_momentsbreaking
  RankedOrganicTweet
  suggest_activity
  suggest_activity_feed
  suggest_activity_highlights
  suggest_activity_tweet
  suggest_grouped_tweet_hashtag
  suggest_pyle_tweet
  suggest_ranked_organic_tweet
  suggest_ranked_timeline_tweet
  suggest_recap
  suggest_recycled_tweet
  suggest_recycled_tweet_inline
  suggest_sc_tweet
  suggest_timeline_tweet
  suggest_who_to_follow
  suggestactivitytweet
  suggestpyletweet
  suggestrecycledtweet_inline`.split(/\W+/);

  const nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLInputElement.prototype, "value").set;

  const addMutedKeyword = keyword => {
    const input = document.querySelector("[name='keyword']");
    nativeInputValueSetter.call(input, keyword);
    input.dispatchEvent(new Event('input', { bubbles: true }));
    document.querySelector("[data-testid='settingsDetailSave']").click();
  }

  const delay = () => {
    return new Promise(res => setTimeout(res, delayMs));
  };

  keywords.reduce(async (prev, keyword) => {
    await prev;
    
    // wait till the browser returns to the initial screen before clicking the add button again. 
    while(window.location.href !== 'https://twitter.com/settings/muted_keywords'){
      await delay();
    }
    document.querySelector("a[href='/settings/add_muted_keyword']").click();
    await delay();
    addMutedKeyword(keyword);
    return delay();
  }, Promise.resolve());
            
})()

jimaldon · 2020-01-27T16:44:47Z

Does this also work on the twitter android client?

TylerBussell · 2020-01-27T19:30:14Z

@TylerBussel - I think you're right, this does nothing, maybe @IanColdwater can edit this gist so this is not burried.

I had been playing with uBlockOrigin settings at the same time as I was playing with these, and going back and replicating, even taking some time to see if things took a while to take effect- I can't see any effect/replicate what I initially saw. And there is this:

https://twitter.com/TwitterSupport/status/1220872428605317122

Though if you read carefully there is wiggle room- they may have some other effect, but that seems to be grasping at straws.

But, until we get proof (screenshots(?)), this is bogus.

This has come up several times in the past. We made some changes to the timeline settings + someone released a JS plugin that did some blocking, so it caused some confusion and people thought muting via keyword mute did something.

am1983 · 2020-01-27T20:59:36Z

Not all heroes where capes.

stevetemp7 · 2020-01-27T21:01:23Z

Worked for me. Made twitter usable. Thanks.

davidawad · 2020-01-30T20:34:50Z

@madaboutcode's thing worked for me. Thanks!

maxclark · 2020-02-01T02:08:03Z

👏

heygambo · 2020-02-11T19:21:02Z

What does this do exactly?

IanColdwater/twittermute.txt

liamengland1 commented Jan 24, 2020

shstkvch commented Jan 25, 2020 •

edited

Loading

freedmand commented Jan 25, 2020

j6k4m8 commented Jan 25, 2020

jakebellacera commented Jan 25, 2020

Think4866 commented Jan 25, 2020

vabruce commented Jan 25, 2020

catarino commented Jan 25, 2020

apervola commented Jan 25, 2020

superherointj commented Jan 25, 2020

vish0l commented Jan 25, 2020

digisavvy commented Jan 25, 2020

doctoraw commented Jan 25, 2020

evandrix commented Jan 25, 2020

madaboutcode commented Jan 25, 2020 •

edited

Loading

julianwieg commented Jan 25, 2020

paaandy commented Jan 25, 2020

mjy commented Jan 25, 2020

joshdance commented Jan 25, 2020

Nerjuz commented Jan 27, 2020

GuillaumeRossolini commented Jan 27, 2020

heygambo commented Jan 27, 2020

horvaro commented Jan 27, 2020

jimaldon commented Jan 27, 2020

TylerBussell commented Jan 27, 2020

am1983 commented Jan 27, 2020

stevetemp7 commented Jan 27, 2020

davidawad commented Jan 30, 2020

maxclark commented Feb 1, 2020

heygambo commented Feb 11, 2020

	Mute these words in your settings here: https://twitter.com/settings/muted_keywords

	ActivityTweet
	generic_activity_highlights
	generic_activity_momentsbreaking
	RankedOrganicTweet
	suggest_activity
	suggest_activity_feed
	suggest_activity_highlights
	suggest_activity_tweet
	suggest_grouped_tweet_hashtag
	suggest_pyle_tweet
	suggest_ranked_organic_tweet
	suggest_ranked_timeline_tweet
	suggest_recap
	suggest_recycled_tweet
	suggest_recycled_tweet_inline
	suggest_sc_tweet
	suggest_timeline_tweet
	suggest_who_to_follow
	suggestactivitytweet
	suggestpyletweet
	suggestrecycledtweet_inline

IanColdwater/twittermute.txt

liamengland1 commented Jan 24, 2020

shstkvch commented Jan 25, 2020 • edited Loading

freedmand commented Jan 25, 2020

j6k4m8 commented Jan 25, 2020

jakebellacera commented Jan 25, 2020

Think4866 commented Jan 25, 2020

vabruce commented Jan 25, 2020

catarino commented Jan 25, 2020

apervola commented Jan 25, 2020

superherointj commented Jan 25, 2020

vish0l commented Jan 25, 2020

digisavvy commented Jan 25, 2020

doctoraw commented Jan 25, 2020

evandrix commented Jan 25, 2020

madaboutcode commented Jan 25, 2020 • edited Loading

julianwieg commented Jan 25, 2020

paaandy commented Jan 25, 2020

mjy commented Jan 25, 2020

joshdance commented Jan 25, 2020

Nerjuz commented Jan 27, 2020

❤️

GuillaumeRossolini commented Jan 27, 2020

heygambo commented Jan 27, 2020

horvaro commented Jan 27, 2020

jimaldon commented Jan 27, 2020

TylerBussell commented Jan 27, 2020

am1983 commented Jan 27, 2020

stevetemp7 commented Jan 27, 2020

davidawad commented Jan 30, 2020

maxclark commented Feb 1, 2020

heygambo commented Feb 11, 2020

shstkvch commented Jan 25, 2020 •

edited

Loading

madaboutcode commented Jan 25, 2020 •

edited

Loading