• 1 Post
  • 31 Comments
Joined 3 months ago
cake
Cake day: July 3rd, 2025

help-circle
  • After decades I am still uncertain of some grammatical rules and word choices. I still struggle with spelling often, and once in a while I find a word that I have been pronouncing wrong my whole life.

    Get more contact with native speakers. No shade but half of them don’t even know the rules

    I know how you feel, I also feel that. I am not always sure how to navigate cultural connotations of words, sometimes a native surprises me by using a phrase, that I have known before, in a way that I knew is the proper use but would have never come up with that myself. Yet, since I started spending more personal time with native speakers, I would often be asked to take a look at a draft of their message. Or they ask me how would I word something. Because “you are better with words” ¯\(ツ)/¯ The difference is, you and I pay attention to what/how we say it. Native speakers often just say it as it comes

    Granted, as we already established, I am not a native speaker but by looking at your posts I would not say you are struggling with English






  • But is that a limitation of AP?

    As far as I understand one could split a fediverse instance into three parts: data, backend and UI. The data is not shared 1to1 - each instance gets a copy of the activity and from that creates it’s own copy. Hence the same post on different instances will have different id The problem we are speaking about is the capability of the backend to process incoming copies. Meaning, I also understand that the part that serves the local data to UI should not be the problem

    What if there was a queue at the front and from the backend a scalable ingestion worker would be split off? Those would only do the putting the actions onto the data. Probably with per community(?) FIFO topics/partitions, so we can process data in parallel and not worry about an updoot for a post that does not exist yet

    Those would still be fairly easy to deploy and be vertically scalable, right? Or is there some bottleneck in the protocol itself?


  • ActivityPub works fine now because the community is fairly small, but it will reach its limits as it is currently designed. Its basically an event driven model vs a push and pull model. Sure a docker image can more or less jusy be deployed, but that simplicity is a ticking time bomb.

    You mean that when there’s more traffic, the instances will start to DDOS each other?