Threads and the fediverse, again. By Uriel Fanelli
Cerca risultati per: fediverse
As a systems architect, I am compelled to always consider two things among many: system capacity and costs. This translates into two questions: “how does it scale in capacity?” and “how much does it cost, and who pays?” These are two questions that few are asking when they place their trust in federated systems like …
There is a certain buzz in the Fediverse (or “Mastodon” for cephalopods) due to the news that “Threads” has an ActivityPub interface, making it capable of federating with the Fediverse, i.e., anything else that speaks ActivityPub. There are already petitions from sysadmins who categorically refuse to federate, which, in my opinion, is a waste of …
I’ve reiterated several times on the point that ActivityPub is a terrible protocol (which is easy to agree), what I didn’t mentioned so far is how bad is the implementation of most used instances. Under the architect point of view, it looks to me like developers are trying to write a “single user instance (which …
I am not sure I can say that an instance with 7 users like mine (including my cousin: don’t tell me I hate women) is not a personal instance. However, the fediverse has a number of instances with less than ten users and a lot with “just” one user. This situation is definitely the fediverse’s …
So far I have written a couple of posts concerning the stagnation of the fediverse, and I must say that the resonance has surprised me. It is clear that the fediverse matters, but it is also clear that it repels the opensource community. Issues I raised are: The reason is, precisely, that unlike other standards …