When you follow someone, you can mute just boosts from them if you like.
Other than that, all of these things are things people can build using the API. I agree they're needed, and I think enough others do that things will get built.
I certainly want to build my own algorithmic feed, because reverse chronology is already a nuisance to me.
huh. ability to mute someone's reposts in your own timeline won't do much for purposes of browsing through that particular person's tweets though. it's not about 'how someone's tweets appear in your timeline', but 'browsing someone's tweets'. to be fair, twitter doesn't let you just filter out reblogs from someone's profile timeline either (though one could just do a search like 'from:username'), but with visible likes, this sort of 'personal curation' separates itself into 'profile tweets' and 'likes', with retweets getting used more sparingly.
I also don't like that difference in separation w/less visible likes/favourites.
Other than that I think what you're describing might well be a good feature for one of the frontends to support. Incidentally, since all of the profile info is available without auth, it's also possible to build an entirely separate profile browser that could offer that filtering for any profile.
EDIT: Mastodon in fact includes a profile browser for remote profiles; it's just that when logged out it will redirect to the remote profile instead of show the "local view" of it. So if someone wants to build a profile browser like that, all the necessary code for a good starting point is there in Mastodon already. Thought it might well be easier just to do it from scratch.
Other than that, all of these things are things people can build using the API. I agree they're needed, and I think enough others do that things will get built.
I certainly want to build my own algorithmic feed, because reverse chronology is already a nuisance to me.