How about creating...a type of stacker.news post that can be updated? \ stacker news ~meta

pull down to refresh

How about creating...a type of stacker.news post that can be updated?

41 sats \ 11 comments \ @Signal312 2 Oct 2024 meta

Why can't posts be updated? I can see that in many situations, you'd want the post to remain the same.

However, I see a lot of use cases for posts that can be updated, that are not static. Maybe that you can pay more for?

I've been thinking about this a while, and especially since following this post - Easily attach wallet to SEND & RECEIVE sats from SN with Coinos.io and HODL. There are some great, detailed instructions in it, but they were (partially) out of date quickly. The post was made Sept. 21, and just a few days later it was already out of date, because of changes to the CoinOS app.

Somebody trying to follow the instructions from the above post now would either be unsuccessful, or have to painstakingly tease out the updates from comments. Not impossible, but it would be a lot easier if you could just update the original.

So, I can really see the use case for editable posts.

Also...just for making things easier to understand. For instance, the author of a "how to" post would be able to clarify things that readers are having trouble with, add or subtract steps, update screenshots, etc.

@k00b, @ek, @supratic

view all related items

44 sats \ 7 replies \ @k00b 2 Oct 2024

We have an issue for it: https://github.com/stackernews/stacker.news/issues/1049

10 sats \ 4 replies \ @Signal312 OP 2 Oct 2024

Got it, thank you. I thought I've seen discussion of this before, but then couldn't find anything searching on stacker news. Should have checked the feature requests!

Looks like on Reddit, they do allow edits (with some restrictions).

0 sats \ 0 replies \ @deSign_r 8 Oct 2024

0 sats \ 2 replies \ @Signal312 OP 2 Oct 2024

Something like this might be relatively straightforward:

Have an ItemEditHistory table. Perhaps only these fields: id originalItemID createdAt title text editReason ?
Add field to Item table nEdits (sum of related rows in ItemEditHistory)
When an edit occurs: -- Insert new record (with old text and title values, and current datetime for createdAt field) from item to the ItemEditHistory -- In the original Item record, update the text and title fields with the updated values, and update nEdits with the total of related records from ItemEditHistory table
The post could have a little button on it, indicating (if edited) the number of edits. Then just don't show that button if it hasn't been edited, to avoid clutter.
It should be straightforward to show a history of edits.

Mentioning @elvismercury because he wrote some posts on this as well.

0 sats \ 1 reply \ @k00b 2 Oct 2024

I wrote hypothetical implementation details here: #492677

0 sats \ 0 replies \ @Signal312 OP 3 Oct 2024

Oh, I see, got it. I guess my proposal is very similar to what you have here: #492722

11 sats \ 1 reply \ @Coinsreporter 2 Oct 2024

The con mentioned over there says

Degradation of post quality (why would i thoroughly craft my post if i can edit it later on?)

I completely agree. Also, I think the uneditable posts ensure the accountability of stackers. If you just wanna do it for directory type of posts, it's just fine but for every post, it'll definitely degrade quality of a post.

0 sats \ 0 replies \ @Signal312 OP 2 Oct 2024

I'm not saying the standard post should be editable. But there's a type of post that would definitely benefit a lot from being editable.

34 sats \ 0 replies \ @Thereal 2 Oct 2024

Great ideas generated by Bitcoin minds are benefits from Bitcoin itself. This is nice

34 sats \ 0 replies \ @supratic 2 Oct 2024

Thanks for the mention! This feature has been requested multiple times. Technically, will be maybe a mess to orchestrate... and also confusing for readers.

I agree it will be useful, in my case I could potentially just delete the old one, and rewrite an updated version, so there's less confusion.

0 sats \ 0 replies \ @Coinsreporter 2 Oct 2024

There are some great, detailed instructions in it, but they were (partially) out of date quickly.

There's always an option to create a new post for the update. You just need to put the link of previous (outdated) post in the updated one. Also, if someone updates something in an old post, there are many things which needs to be considered beforehand. The biggest one is to get that post in the 'Hot' zone. What's the utility of updating if stackers don't view the update?