Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
Fediverse Party
Fediverse Party
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Feneas
  • Fediverse PartyFediverse Party
  • Issues
  • #28

Closed
Open
Opened Jul 19, 2020 by Arnold Schrijver@aschrijverDeveloper
  • Report abuse
  • New issue
Report abuse New issue

Fediverse Party for end-users AND researchers & developers?

This is just an idea that popped up, and I'd like to do some brainstorming.

TL;DR

The complexity and fragmented knowledge needed to develop new groundbreaking fediverse apps is the weak spot hampering the speed of Fediverse evolution.

Fediverse Party is excellent for end-users, and has the best SEO. It should also be the first entrypoint those developing the Fediverse and researching new specifications & use cases.

Background

So we have a lot of discussion on how the structure of the wiki, what info should be where, how many entries should be on a page, etc. The main purpose of the wiki is as a place of research and curation of stuff before it is added to fediverse.party.

I love the look&feel of fediverse.party and how it makes the Fediverse accessible for normal users, not just the technical/geeky types like us ;) The Fediverse itself is evolving fast, as the number of additions to the watchlists make very clear. But in this evolution - the development of new fediverse applications - is also where the biggest challenge still is. E.g. it is a PITA to gather all the knowledge for a codebase that federates with Mastodon. Things are harder still if you want to tread new grounds that go beyond microblogging. It is really hard to find developments/research for AP vNext. Things are so fragmented. It is a weakness that slows the evolution. And it is an opportunity for fediverse.party to jump into this spot.

The wiki for me, and I imagine any other fediverse-interested techie, is the most interesting. But whereas fediverse.party has excellent SEO (ranked first on DDG and Google for 'fediverse' search term), the wiki is basically unfindable. I've shared the link to the AP watchlist numerous times, to the delight of people not knowing about it.

Idea: Fediverse Party R&D section based on Wiki pages

The current site has a 'Knowledge' section, which is underused and frankly not clear on what knowledge it should hold. This section could be converted into a top-level 'R&D' section for those developing the Fediverse.

Gitlab's wiki features are only so-so, but at least the wiki is a git repo in itself. What we could do is to auto-publish the wiki pages to the R&D section.

This way:

  • Findability of research is as good as fediverse.party site.
  • Content is nicely formatted and ordered the way we want (based on front matter).
  • The existing wiki links stay intact so there's no link rot.
  • There can be as many wiki pages as we want. Need not worry about wiki structure.

WDYT?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
idea needs feedback
Assign labels
  • View project labels
Reference: feneas/fediverse#28