Oh yeah that’s my mistake, it was a plugin for WordPress, not ownership. It looks like it was co-authored by someone as part of W3C to be an internet standard, but I don’t know if that changes much.
It’s mostly that if something somewhere can be bought, Meta will try to. I don’t see any reason to extend any open arms. Just because something is open source doesn’t mean that ownership won’t change or changes can’t be implemented or influenced.
That aside though I also feel that any integration is just asking for an invitation to reckless abandon. I think I mentioned in the previous comment, what happens as Meta begins making contributions to the open source protocol? As people looking to run their own instances come across a Meta build due to SEO? Maybe Meta money starts getting thrown at W3C and the co-author - who knows man. At that point, are we just going to use whatever forks that get Meta’s stuff stripped out from it?
Why risk 100m Facebook and Instagram users for the “potential growth of Masto-lemmy” when it seems like the very obvious reality is that Threads would just leech users from here after some integration then “oops Threads doesn’t support ActivityPub instances all your communities are with us now sorry!”. Not to mention the imposed tracking, dark patterns and monetization - which from my understanding instances can set fetch authorization, alongside defederating it would mostly prevent the data scraping? However I’m not entirely clear on all that.
Anyway, not trying to claim that I’m extremely well versed in the subject or the specific logistics of how it works, I just don’t see a single reason to trust Meta or why there would be any reason to federate with them.
I also personally have no issue having separate spaces for separate things, so to me the integration just seems a bit much. Some people have told me that’s a positive for them, and that’s cool. If I could functionally have one and actually interact in full I’d probably just use one account too. I occasionally view microblogs on Kbin alongside my subscriptions, I browse through here (Beehaw), both slrpnks lemmy and Mastodon instances, all different accounts. If I were interested in the content I’d have made a threads account (but the posts I get shown from Instagram don’t really pull any interest).
If someone is interested in using Threads, why not just use it there? I don’t entirely understand the reason we would need Threads to be seen in the same space as Twitter posts and Reddit threads all alongside our microblogs and posts (if say, Reddit and Twitter were also to federate). It just seems so much more centralized compared to the nature of the decentralized instances, I could see Meta’s interest here being to make their version of WeChat. A space where you have Microblogs, Forums, Marketplace, and games all in one spot no need to ever use anything else.
I dunno, I just feel like the desire to consolidate everything into a single bitty package is asking for a disaster. And to an extent, I genuinely can see this being the start of that path.
Anyway, sorry to get so long winded. Maybe I can take advantage of this idea and develop an app to centralize your Fediverse, Reddit, Twitter, Discord, GameFAQs and any account you can think of all in one spot. Then you can just interact from all of them as a single master user posting from each individual account as you come across the content. Support for all that will probably get pricey so I’ll just charge for extended account integration, maybe I can make my own subscription based off this to cover the cost (/s but feel free to use it!)