source namespace: what service should be used for Fediverse platform accounts?

Open
#9 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

No file, test, or implementation entry point is named. First resolve whether the service identifies the platform, the specific server, or the generic Fediverse naming scheme, including whether the server may be omitted from the handle. Done means reaching an agreed namespace representation suitable for the package.

Written by the indexing model from the issue text.

Description

Fediverse platforms all use the same form to identify users (@username@server). Should the service in this case identify the platform (e.g. Mastodon vs Pleroma vs Akkoma vs PixelFed or whatever), the specific server (e.g. mas.to vs pixelfed.social or whatever, in which case the username/handle could omit the server part), or something else that identifies the generic naming scheme?

Dominant language
JavaScript
Stars
104
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/reallysimple

All issues in scripting/reallysimple

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.