I’ve started thinking recently about what it would look like to federate preprint servers. Federation involves a common language between servers to better enable communication and interoperability across multiple servers/services/clients, as opposed to centralization where all of the user connections and interactions occur on the servers of one operator. In social media, Twitter would be an example of a centralized service, where all Twitter users must have accounts with Twitter in order to interact with each other on that platform. Compare this with Mastodon, which provides a Twitter-like experience, but users are not required to have an account from any one provider in order to interact with users on the network, or Fediverse. In this way, users can identify with (create an account on) the server of the community that they feel the most connected to, but regardless of which community they choose they can still interact with users of every other community.

I’ve been thinking lately about what federation might look like in academic publishing. Publishing of academic research is currently a rather archaic system that serves to exploit the labor of researchers and academics, primarily for the financial gain of a few very large publishers. There have been some efforts to retake the publishing infrastructure and create scholar owned systems with varying degrees of success. Would the fediverse enable greater success in such an initiative or would it not make sense in this context?

  • smallcirclesM
    1•3 years ago

    This would definitely work, and in fact there’s ongoing projects going in this direction. Most notably there’s OLKI:

    Bringing research papers, datasets and peer reviews to a larger network of federated social platforms, with no vendor lock-in and on a platform you can host and control.

    • Federated peer reviews
    • Federated document annotation
    • Federated scientific interaction
    • Federated scientific watch

    Another project, that - while not directly providing this use case - goes in the right direction is SkoHub, that allows you to “extend the scope of Knowledge Organization Systems (KOS) to also act as communication hubs for publishers and information seekers”.

    (Both the SkoHub and OLKI project teams are members of SocialHub, and - not sure - SkoHub may be presenting on the 2nd webinar of the ActivityPub for EU Administrations event that we are organizing)

    The nice thing is that ActivityPub - while being a very basic standard in itself, layered on top of ActivityStreams (basic social primitives) - is a Linked Data standard. You can extend with vocabularies towards any business or application domain, and describe not only the messaging / federation concepts, but also the information model of your app.

    And preferably advocate to standardize on the vocabulary extension, so that other apps independently created to yours, can still seamlessly interoperate. Right now most fediverse applications are modeled around a Microblogging domain, which gives most people the impression that this is what ActivityPub’s primary use case is. But it goes way further than that.

    Also note that “being part of the fediverse” need not be central to your adoption of ActivityPub. Federating between your own app instances, or exclusively to apps within a particular domain is also a valid use case. I wrote something about that on the SocialHub forum: Positioning ActivityPub: De-Emphasize “Being Part of the Fediverse” as primary USP.

    (PS: I co-maintain AP watchlists that give an overview of all stuff that is under development. See AP Apps Watchlist and AP Developer Resources Watchlist. On the latter you find e.g. libraries like Go-Fed that allow you to generate code from your Linked Data vocabulary, to ease app development)

    • @drbOP
      2•3 years ago

      Thank you for the links and further considerations. The OLKI platform looks particularly interesting. Another direction that would be interesting to look into would be if these features could be added to existing platforms such as Open Preprint Systems and it’s journal variant, Open Journal Systems. OPS is relatively new, but it is based on OJS, which I believe is the most widely used journal software.

      • smallcirclesM
        1•3 years ago

        Great links. I added them as candidates to a delightful list I co-maintain: the curated delightful-open-science. (I set up the delightful project as alternative to Awesome on Github, just for FOSS, Open Science and Open Data resources where sublists can be in any code forge).

        What I think is important for any federated future of these kinds of apps, is that some kind of standardization or agreement is formed as to the Linked Data vocabularies that are used to describe both data formats as well as federation message types.

        I am just an advocate to bring fedi to higher levels, and not deeply involved in this field, but I’ll leave reference to this discussion on socialhub.

        • @drbOP
          2•3 years ago

          I linked this in a top-level comment, but I was also pointed to COAR Notify, which is being built on Linked Data Notifications and is basically intending to do what I was proposing in my post.