Still I can't help but to wonder whether those notifications are needed or not. Except for instant messaging, I generally don't want notifications. Like I don't need to be told that a new podcast is available, I'll see it next time I open the app.
I would like to at least have the choice to use RSS instead of having to go through a complicated federated system.
Even if I'm using someone else's system, I just don't like the idea of giving them a reason/need to manage all that for me. RSS works fine 99% of the time.
Ideally the push-based parts would be optional for both ends so you could host a static feed and still have people see those updates in their fancy fediverse apps, just not immediately when you post them.
Instead we have a completely different standard without a simple core that you can easily implement if you don't need all the bells and whistles.
Federation comes in mainly because push based systems require a server managing who follows who, what is posted, and who to notify of updates. That's a lot of information for one central service to be responsible for, leading some to think its better to federate and trust a bunch of servers to host copies of some or all of that same data.