i think a general criticism of fedi i have is that it’s still very services-based and assumes that you have some kind of all-powerful Server that “implements” various features, rather than just being able to do something on your website
-
i think a general criticism of fedi i have is that it’s still very services-based and assumes that you have some kind of all-powerful Server that “implements” various features, rather than just being able to do something on your website
like how feps can have an “implementations” section that lists various softwares, but completely fails to account for cases where a human being wrote some text into a static file and served it with any generic http server. or like an nginx config or whatever.
-
i think a general criticism of fedi i have is that it’s still very services-based and assumes that you have some kind of all-powerful Server that “implements” various features, rather than just being able to do something on your website
like how feps can have an “implementations” section that lists various softwares, but completely fails to account for cases where a human being wrote some text into a static file and served it with any generic http server. or like an nginx config or whatever.
really the problem is that building the concept of the all-powerful Service into your core worldview means you are quite possibly overcomplicating it from the start
