Restructuring fediverse apps and activitypub development lists

Social affiliations šŸ’ƒšŸ•ŗ Delightful commons
, ,
#1

Introduction

The wiki below is used to brainstorm a better taxonomy for the fediverse-related delightful lists.

Objective of the 4 fediverse-related delightful lists - which originated from wiki pages of the Fediverse Party project - was to inform people in the technology ecosystem on ANY existing ActivityPub-related social web development projects. The ecosystem was very small, and even an intent - e.g. in the form of an open issue - to implement AP support was enough reason for inclusion. Also unmaintained projects were still included with the thought that the code might still inspire people, or lead to contributions and/or forks.

Dilligent curation efforts over time has made the lists grow very large. They are popular resources for folks to ā€˜grazeā€™ the ActivityPub protocol family ecosystem. Yet the usefulness of the lists is reduced by a taxonomy that no longer covers the entries in each list category appropriately.

The wiki below is where new taxonomy will be elaborated, and can be edited by anyone.

Objectives

  1. Find a comprehensive, more detailed list taxonomy.
  2. Separate foundational technology from app-specific projects
  3. Highlight innovation areas of the AS/AP fediverse.

Current taxonomy

delightful-fediverse-apps

delightful-activitypub-development

1 Like
#2

This is a wiki post that anyone can edit.

General thoughts

  • MUST align to Social coding commons and SX ubiquitous language.
  • SHOULD be in service of envisioning a peopleverse (focus on evolution / innovation).
  • SHOULD emphasize social networking as: ā€œany direct or indirect human interaction between peopleā€.
  • SHOULD align with Social coding commons:
    • Fediverse is evolved by Social experience design.
    • Fediverse SX is service oriented and follows a paradigm of app-free computing.
    • Fediverse offers services, handles service composition, orchestration, and choreography.
    • Fediverse is a heterogeneous mix of both traditional apps and services.
    • Fediverse has hybrid decentralization, supports both federated and p2p networking.
    • Fediverse cocreation involves countless people in creator and client stakeholder roles.
    • Fediverse 3-stage standardization process is driven by commons-based peer production.
  • SHOULD have taxonomy such that entries are only listed once, not in multiple categories.

Improving delightful-fediverse-apps

:point_right: Rename list to delightful-fediverse-experience.

The interoperable fediverse provides access to an online social fabric of interwoven social experiences. A social experience is a social web solution that serve a particular need in a particular domain, and is delivered in the form of applications and services, plus tools and integrations.

The new name highlights that being part of the fediverse (belonging) in itself is a delightful experience. The taxonomy should outline the ā€˜treasure mapā€™ of the social fabric that can be navigated, from the perspective of the client stakeholder (i.e. end-users).

:point_right: Favor innovation, de-emphasize well-adopted business domains.

Some areas on the fediverse have good adoption, get all the attention, while other more innovative areas are hard to discover. Create top-level list categories where ā€œAlternative social mediaā€ is ranked lower / lowest, and use it to list most current apps that are decentralized copies of corporate social media platforms.

:point_right: Gather app-specific client facing resources together.

If delightful-activitypub-development contains entries that e.g enrich the UI of an app, then the project serves client stakeholders and should be moved to the fediverse experience list.

:gem: delightful-fediverse-experience

Contents

Improving delightful-activitypub-development

:point_right: Rename list to delightful-fediverse-development.

The development ecosystem is scoped to the concept of an ActivityPub protocol family.

For the second stage of the curated list overhaul this list will be purged from all entries that are not directly developer related. Any UI and app extension, plugins and non-developer tools and utilities will be moved to delightful-fediverse-experience, expanding the taxonomy further. See issue:

#4