[insin]

Author here, this the website where you go to get customer support from Google, right? /s

Was everyone who reviews extensions at Google part of the cohort who were suddenly given a cardboard box and shown the door recently? The extension has been blowing up in Japan over the weekend (user numbers more than doubled from 29,000 to 68,000 over the last few days) so I internationalized it to add a Japanese locale (and incidentally accidentally used "en" for the default locale rather than "en_US" which everyone seems to default to, for which the Edge Extension Dashboard completely wiped my store listing in their interface - cheers).

New versions on Chrome Web Store are usually approved first within in a few hours, but it's been sitting for more than 24 hours now and their contact form suggests you only bother them after 3 weeks! It doesn't help that the version I submitted has invalid locale strings for Chrome (which worked fine in Firefox, the default browser launched by the web-ext extension development tool - thanks) and you can't back a known-bad version out of review.

Yes, I too have read all the rants about being beholden to Big Extension Store and have nobody to blame but myself :)

Also, happy to answer any questions you have about writing extensions on top of React Native for Web apps - New Twitter was a fix it or quit it situation for me, and I ended up getting lots of practice at the former when it's looking like I probably should have just done the latter.

[abdullahkhalids]

Here are some crazy features I really want. I doubt you can implement, but a man can dream.

1. For some accounts, I don't see what they tweet, but want to continue seeing their retweets.

2. For some accounts, I only want to see tweets that are replies to my other followers. Otherwise, I don't want to see their tweets on my timeline.

3. Some "famous" people will retweet every praise they get from someone. You know "I totally loved @famousperson's new book". I would love to just block any retweets by them that has their own username in it. And keep everything else.

4. Chronological timeline, but only show maximum of N tweets from a particular account.

5. Craziest feature. Flip the timeline around, so scrolling downwards shows me newer tweets. And at the start of the session, move me to the last tweet I viewed.

Effective use of twitter is about removing as much of the noise as possible from your timeline, so as to increase the signal-to-noise ratio.

[insin]

Those are all very doable except for 5, but they're so (relatively) niche I think they'd belong together in a separate extension dedicated to selectively trimming down your timeline.

Personally, after I moved Retweets to their own tab, I found I just never missed them or looked at them again, and if I put them back in it just seems like random noise now.

> And at the start of the session, move me to the last tweet I viewed

This one I would like to do, but... Twitter has at least some built-in ability to do this (if you scroll your timeline a few screens worth, navigate away from the home timeline then eventually navigate back, it can restore your previous position), but I haven't found a way to make use of it for this feature - I _suspect_ they're caching the current state of whatever way they do their windowing of timeline tweets, then restoring that later, which means it's probably not possible to leverage it to jump to a particular tweet from a cold start.

Automatically scrolling through tweets until you hit a particular last-seen one isn't great alternative either, as it's pretty slow and the timeline currently seems to end after about a day and a half.

[abdullahkhalids]

Thanks for the detailed answer.

> Personally, after I moved Retweets to their own tab, I found I just never missed them or looked at them again, and if I put them back in it just seems like random noise now.

Depends on who you follow. I follow a limited set of intellectual minded people who themselves follow a lot of people and retweet the good stuff. So, I would quite like to continue reading them.

[dom96]

Another annoyance of the Chrome Web Store: you cannot publish a new version if another version is still pending publication. Ran into that once which meant an even greater time stuck waiting for the latest version to be published...

[scotcha1]

my experience with shipping updates to the google chrome store is that you typically are waiting days if not weeks, depending on the time of year. 24 hours seems incredibly fast! hopefully it will get approved soon, good luck!