pull down to refresh

Yes, I would like that to happen. For long posts, tutorials or even @Rexdentron lists are useful to update. I myself I found that some of my guides are obsolete and needs to be updated. This is what I am doing now, reviewing my guides (on github) and update some and also translating in 8 languages. It's amazing to see how fast things are changing...
Indeed endless editable posts could also end up in scams. For that I will propose a fee for edit a post older than x days. MAKE THEM PAY.
on github
This is the right way of managing your content.
Changes are tracked in a central location and you can copy/paste from there to SN.
What goes on SN needs to remain immutable like transactions on the chain.
reply
I am going to create a dedicated section only for the guides I post on SN. I have some that are posted only on SN and not on Github.
reply
0 sats \ 4 replies \ @ek 21h
I think a history of edits is enough to protect against abuse.
What kind of scams are you imagining perpetual edits would allow?
reply
What kind of scams are you imagining perpetual edits would allow?
oh boy... options are endless. SN it just started... lots of scammers will join when they see that there's a cow to milk with gullible readers.
History of edits could help yes, but also "pay to edit". When they have to pay is hard to scam.
reply
0 sats \ 2 replies \ @ek 21h
You said 'options are endless' but didn’t mention a single option that is not already possible without perpetual edits
reply
53 sats \ 1 reply \ @DarthCoin 21h
If they already change their bio from a shitcoiner to pretend to be a bitcoiner, imagine what is going to do with posts. I am already tired of making screenshots.
reply
21 sats \ 0 replies \ @ek 21h
Ah, mhh, ok
reply