> The simple fact is: Adding another node to the Fediverse is harmful to the health of the network.
@helge you are very far from that being "a fact". Personally I doubt you could bring any arguments to make it even in the realm of "non-controversial".
@steve I don't really understand what @silverpill wants to underscore with that FEP.
In my software I am using something like his core types for actual data types, but the differences are mostly in behaviour a server/client has in relation to them. Ie, what can one "do" when encountering such an object, and that's better guided by looking at their data "shapes". The properties common to the Object type can be used for "object things": display name, content, use URL, etc. The extra properties for Actor, can be used for actor things: addressing. The properties for Collections: for retrieval, etc.
@silverpill I think Actor should be considered a core type (for the purposes of ActivityPub) just because the whole of the ActivityPub specification is based on it and its structure.
@silverpill which works for maybe 1% of people that create content professionally. How are we to dar say that the fediverse needs to accessible to everyone if we put crypto-currency obstacles in front of people.
In my humble opinion, any monetization option that only deals with cryptocurrency is useless in making the fediverse a valid alternative to whale content creators that might want to migrate from traditional social media.
@benpate are there any useful things built on top of them, or are they just crypto currency adjacent? Regular artists, I bet, would prefer to be paid in actual currency, not make belief money.
@catileptic wouldn't offering options to the users be a better compromise than full "removal".
I feel like users are still capable, or at least should be capable, of agency in deciding what's better for them, even if the final result is consuming more garbage.
Mostly a programmer.Implementing #ActivityPub in the #Go programming language.Current projects: * #GoActivityPub - a library to use ActivityPub in Go. * #FedBOX - a generic ActivityPub service supporting the client to server API. * #brutalinks - a link aggregator inspired by (old) reddit, hacker news and lobste.rs built on top of FedBOX. * #oni - a single user ActivityPub server with minimal fuss.My posts are mostly related to ActivityPub and web development.