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.
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.
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.
I think we'll continue to see social media fracture and federate as time goes on, and this will turn out to be a net benefit for society. For now, my mental health is definitely better.
What about same question posed to yourself (and myself), but for this website (Hacker News) instead of Twitter? :)
One of my favorite features is the built-in code highlighting.
Using plain pleroma right now, I want to try standing up misskey maybe on a weekend.
If someone reposts a poll into my timeline, the poll shows as having 0 answers, or 1 answer if I answer it.
If someone posts a reply that's visible in my timeline, the post they're replying to isn't reliably visible.
If I'm on someone's (remote) profile on my (local) server, there isn't a giant obvious link for "go to the real profile so I can view all their posts". I have to manually construct the URL for their profile.
Conversely, if I'm on someone's profile on their server, I have to copy-paste their URL into my instance's search bar before I can follow them; that should be one click, which could be done with some browser integration.
I myself developed an extension for integrating Mastodon with Twitter recently[0]. It's a great way to get exposure to Mastodon without leaving the familiar Twitter UI.
You can't win with a platform on the platform's turf.
The only winning move is not to play the game. Or play a game that you can own.
* I'm not the OP, but I made a similar extension.
They've handily left a bunch of data-testid attributes on some of the major elements you need to identify, like the primary column.
Since it's a React app, manually removing stuff from the DOM will either have your changes get blown away the on the next render, or cause issues on the next render. A good trick is to add your own descriptive classes to <body> for the current screen so you can limit the scope of some of the incredibly gnarly CSS selectors you'll need to use to hide things.
Your response instead attacked another poster, which did not contribute to the discussion at all.
