@Setok With regard to this, realize that a lot of the problems come out of engineering decisions made long ago that would be very difficult to change course on at this point.

It's not merely a matter of throwing programmer time to tweak some UI functionality.

It's more akin to deciding to build a car and later on complaining that really you wanted to fly but this vehicle doesn't do that.

It's pretty hard to change course at this point without starting over.

@lari @petri

@volkris @lari @petri that’s a fair point of course. But doesn’t change the reality that we risk falling behind here.

@Setok so I lost track of that thread, and then I found it again and realized I hadn't finished it.

I see that the thread really went on to focus on developer attention and funding, but now let me emphasize that I'm saying there are core problems to ActivityPub that can't be fixed with just some more developer focus or funding.

AP was to its core built around instances, not users, and so many complaints that people have come directly from that design decision. It's not like a developer can just change that. To make AP center on users would make it an entirely different protocol.

At that point you might as well just use one of the alternatives that's already doing that.

This is the model that the entire system is built on. No interface changes are really going to fix it.

And this isn't even getting into the major efficiency problems with the model, this is just what is conceptually required.

@lari @petri