If they do it better without contributing the improvements back to the standard then that's something to complain about. Because then all they're doing is a different, better, proprietary standard and they never really had any intention of embracing an open source project.
That's exactly it and there's no reason to pretend otherwise. Meta is a financial instrument to turn money into more money. The only reason Meta would engage with any third party is to make their commercial products more attractive to advertisers. Play with Meta and before you know if they'll be writing all the rules about how you're allowed to run your instance.
"and is actually good" it won't be actually good because with Meta the users are always going to be the product. What you are thinking is exactly what they want to do. Build the best looking app first so everybody installs it, then they're in a position to start making the calls about the future of the fediverse.
Exactly, off the record means the expectation is Meta will be given free expertise to gain an edge on their competitors. Don't give diddly squat to actors who want to commercialize your content. It will never end well for you, only Meta.
Seriously, if you want to see them squirm, hit them with a wall of silence. They clearly feel they need something and, for Meta, negative feedback is better than no feedback at all.
FB: We're confused why someone would sign up for a social media site set up by somebody in their dorm room, tell us how to be more like you.
Looking at you oceanbreeze.earth, your instance is worth defending from bots
Since we're only talking about a week timeline here, would it be possible to update the sync app with a list of popular Lemmy instances and a way to view your favorite one from a web view within the app? That way people could still use sync in the meantime while native features gradually get rolled out.
I want this too, sort of like multireddits but spanning the entire fediverse.
One thing I've seen get in the way is everyone wants their own instance rather than to setup just one community on an existing instance.
Your first mistake is setting a minimum expectation for a Meta product. They've not promised it will do any of that and they already have you thinking it will based on nothing but rumor.