pull down to refresh
271 sats \ 7 replies \ @ek 12 Feb \ parent \ on: Stacker News For Writers BooksAndArticles
Unfortunately, I am not. At least no new ideas.
Imo, the UI should include a changelog for every edit (after the timer) but if the changelog should be similar to Github is not clear yet.
But in general, a lot on SN related to writing is inspired by Github.
For example, this is how it looks on Github:
https://m.stacker.news/15996https://m.stacker.news/15997
Yeah, I don't really think that would be useful. You would want the edited post NOT to appear to be edited. Obviously you want the change record in github, but I don't think you need it for a post.
reply
You would want the edited post NOT to appear to be edited.
Mhh, why not?
Maybe I'm too worried about abuse, but I think commitment to your text within the current edit timer also has benefits.
With no changelog, there would also be no more edit timer.
The changelog doesn't have to be obvious but I think edits should be transparent 🤔
As far as I can tell, you want edits to work like currently just with no timer, right? For everything or just for posts?
reply
Let me explain what I see as a use case. For what we think of now as a regular post, I think things are fine as they are. What I am looking for would be a static page, either like @grayruby 's idea of an expanded territory description, or a different type of post, that would be freely updatable and editable with the purpose of keeping items current, like an online bulletin board, index, etc. I think that's what @DarthCoin is looking for too, but I could be wrong. The purpose would be to update information without having to delete the old post and make a new one.
reply
reply
Let's say I have a post with linked posts contained within it, like an index. Then let's say the stacker deletes that post and I want to replace it with a different link. It would be cluttered and pointless to have change logs visible if these updates are made frequently.
reply
It would be cluttered and pointless to have change logs visible if these updates are made frequently.
Yeah, I agree. But that's what I am trying to figure out: how to make it not cluttered and not pointless in general. I imagine "infinite edits" could generally be useful. We usually don't build something for, let's say, a very specific use case.
But maybe we can just implement this with no changelog (would also make it easier) and then iterate from there.
reply
That's a good idea, and I don't want to complicate your life, but you are right about the importance of change logs if we're going to have limitless edits. I also worry it could fuck up discussions if the op is editing on the fly while people are responding to the original text. The current limit is a nice compromise. I'm really talking about a different type of post, not one that is necessarily meant to invite discussion. It is probably too much to ask.
reply