@vie I mean, some of "us" have been for a long time - the Palantir employees among us, for example - and I think it's mostly people who previously had those tendencies but lacked the access or funds to capitalize on them that are showing their true colors now.

@packetcat This is a very very good post.

@ricci @jdp23 That's the part I mean - as far as I know, nobody's funding work on the portable identity FEPs.

@jdp23 I shan't beat this drum at you too much, but, they did have $30 million to do that with. I suspect things would be a lot better here if we had that kind of cash.

Hell, if I could go full time developing fedi software, I absolutely would.

@jdp23 I hadn't seen this, but it's not hard to believe.

@jdp23 Yeah, I believe it is mostly or entirely from-scratch.

@jdp23 Yeah, I'm not sure why (or if) Blacksky isn't using the Bluesky mute functionality, but Rudy says they're doing it differently somehow.

I agree that local only posts should not migrate between AppViews, but shouldn't they migrate between PDSes? I guess it doesn't matter so much, but it seems odd.

When people said that Bluesky's federation wasn't complicated only because it wasn't real, this is what they meant.

Now that there is more than one AppView, more than one centralized repository of interconnected social data, we start to see the cracks. That's where they show up in ActivityPub too.

#atproto

Because the protocol doesn't support private data, Blacksky is launching a bunch of features in a centralized (Blacksky-only) way, including mutes and private posts.

These are good features, and it's great that they're building them, but it frustrates me that Blacksky is constrained by the protocol from making them participate in any of the benefits of the ATProto system such as account portability.

#atproto #blacksky

@afewbugs @Nickiquote do it if you want your posts to go away after a while, don't if you don't. For text posts, at least, the storage and processing are negligible.