Sounds like opinions are pretty mixed. Maybe we should put it to a vote.

But then how do we decide if that vote should be public or not…

I was clearly being sarcastic.

There’s no real evidence that Meta was intentionally hiding anything, nor is Pixelfed even close to resembling a threat to Instagram.

So a few comments were hidden, no one seems to be able to reproduce it, and it appears to just be a glitch.

Why would Meta do this???

Sure, that’s great while it’s still just “instances that do federate with threads” and “instances that don’t federate with threads”.

I really don’t think that’s a meaningful comparison.

Federation relies on unity – fragmentation ruins that.

If you see massive fragmentation as a feature then I really don’t know what to tell you.

I guess enjoy?

Yup, thus fragmenting the crap out of the fediverse (the last E)

We’re here

Are we though? Because it looks like you’re on kbin and I’m on slrpnk.

If either one of our instances decides to implement proprietary features that Threads creates (the second E in EEE) and the other one doesn’t, that could break the experience of us being “here” together.

But then if other instances don’t want those features

In other words, if other instances don’t want to have compatibility with the popular instances – hence the issue.

It was for a good few weeks

deleted by creator

What makes you think he’s sweating it? He simply mentioned it…