Login
You're viewing the techdon.dev public feed.
  • Nov 13, 2026, 12:14 AM
    @phnt @silverpill

    > Because if you write your views in a way that they fetch Create activities from the DB and preload the Object, you then have to make a list of things to exclude, because not all Objects that Create works with are what you want.

    Yeah, I don't think the way Pleroma does it is optimal, but I think there'd be less DB contention if they were fetched separately, even client-side. (Individual request throughput suffers sometimes but for multiple users, you have fewer cases where someone decides to click on the hellthread and then 25s later the three-way join that includes the two biggest tables in the DB and with the visibility index and ?with_muted accounted for times out. The thing that may be faster is often trading throughput for individual reqs for more frequently releasing your req's lock on the bottlenecked resource.)

    > If you have CreateAnswer, CreateNote, CreateDocument, your ingestion is more complicated and your builder is more complicated, but rendering timelines and stuff is simpler, because you can restrict by the ActivityType.

    This would hose the only good thing ActivityPub has going for it if you mean in the protocol. If you structure your DB like that then you want to make your DB account for it: move the object type up into a column or index in the table holding the Activity instead of CreateNote->Note'ing the protocol. Pleroma doesn't *have* to put all of the objects into an objects table or all of the activities into an activities table; you could make a CreateNote table that holds the Create-Notes and split that off. "This query in this type of DB using the structure this application uses" is not something that should drive the protocol. I mean, if you want a stream of Note objects and screw whatever other objects get Create'd (and other ways to interact with objects), maybe you should walk the Notes in the objects table instead of the Create activities and then filter the ones that aren't Notes.

    Especially in this case, like, CreateNote->Answer. "You can't do that!" but someone *will*. Look at how fucked Lemmy is on follower addresses and they essentially broke "follow a board (group)" that way (and then for some reason didn't wanna fix it, or at least that is how I understand it to be). You see anything because someone will send a message to your /inbox that has that thing. There was that, I forget what it was called, "kroeg"? Active development and C# and then it went away, so the source is no longer available and there are no live servers and the kid doing it had sent a lot of activities to FSE that had weird breakages so when I imported all of them into Revolver, I kept having to stop and fix pieces: "Here's an array, why's it an array? It's not an array in any activity except *one*." (And, you know, you have to account for this kind of thing even if it's one activity because you don't want to fall over instead of just rejecting it. Like the PleromaFE crashes that happened because a timestamp was in a format that the backend didn't mind but the frontend hated. Anyway, I've been running FSE with this split-inbox where activities get POST'd to both Pleroma and Revolver and Revolver currently ignores non-public activities for obvious reasons so you see very few Create->Answers.)
    💬 0🔄 0⭐ 0