MoeraOrg / MoeraOrg/moera-issues

Visibility/commenting to a limited circle of friends

Open
#263 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

client how? milestone feature new service node
Dominant language
No language data
Stars
20
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Make possible to limit visibility or commenting (separately) to friends of friends or friends of friends of friends. Checking may be performed through a third-party service that everyone trusts the friendship information. Or the node itself may scan friend lists periodically (but this creates more traffic and not every node may keep its friendship information open even to friends).

Some friends known that they are public persons and it is too easy to become their friends, may be excluded from scanning. Their friends are not permitted, unless they are friends of someone else that is trusted. The third-party service mentioned above may keep a shared list of such public persons (but every node may override the data fetched from the list in their own settings).

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.

Research direction

No files, tests, or entry points are named. Start by clarifying the visibility and commenting rules for friends-of-friends, trusted services, and public-person exclusions, then identify the affected access-control components and define how each setting should be validated.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.