Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request : Perpetual Edit #1049

Open
Radentor opened this issue Apr 9, 2024 · 2 comments
Open

Feature Request : Perpetual Edit #1049

Radentor opened this issue Apr 9, 2024 · 2 comments
Labels
difficulty:hard feature new product features that weren't there before

Comments

@Radentor
Copy link

Radentor commented Apr 9, 2024

 Issue : 1049
 Title : Perpetual Edit
 Author : Radentor
 Status : Proposed
 Type : Feature
 Created : 2024-04-09

Abstract

This issue describes the proposal of granting author with ability to perpetually edit his/her SN post.

Motivation

Certain type of SN post (such as directory & statistic report) requires constant update to avoid possible misinformation. Even regular post could slightly benefited from this feature in case the author forget to include certain detail after 10 minute time window has passed.

Consideration

  • Alternatives :
    a. Reposting with update
    b. Delete older post & reposting with update
    c. Invent new type of post with perpetual update

  • Cost :
    a. 100% original cost (infinitely free editable post)
    b. 100% original cost with cooldown (cost-limited editable post)
    c. Increased (150% or 200% of original cost per edit, with cooldown)

  • Moderation :
    a. Total control to author
    b. Moderated by territory founder

  • Timestamping (if edit history is implemented) :
    a. Regular SN numbering
    b. Timestamped with Bitcoin block

  • Transparency :
    a. Edit history toggle-able by author
    b. Edit history always visible to reader
    c. No edit history at all

Pros & Cons

  • Pros :
  1. Easier navigation (bookmarking once is enough)
  2. Better UX (it's awkward to publish new post just to add "small update")
  3. Decluttering (single maintained post > multiple post on every update)
  • Cons :
  1. Degradation of post quality (why would i thoroughly craft my post if i can edit it later on?)

Earlier Mentions

@Radentor Radentor added the feature new product features that weren't there before label Apr 9, 2024
@huumn
Copy link
Member

huumn commented Apr 9, 2024

I discuss design goal here and I think we want to use the history table pattern.

@Radentor
Copy link
Author

Radentor commented Apr 9, 2024

I discuss design goal here and I think we want to use the history table pattern.

Looking forward to it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty:hard feature new product features that weren't there before
Projects
None yet
Development

No branches or pull requests

2 participants