Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Ninja edits. A grace period where you can edit your comment without it showing it was edited. This is usually for typos and formatting mistakes that you notice right after posting your comment. A minute will do.
If anything, I'd love a diff of each edit vs the ability to ninja edit
rather than allowing edits for invisible edits for X minutes, couldn't your client just delay actually sending it for X minutes allowing to cancel or edit freely until that point?
Gmail allows a similar feature and it seems safer in a distributed system than relying on everyone else to respect what happens after you send a raw message and an edit right after
Implementing this like Gmail would mean doing it server-side. Handling it in the client would be more error-prone, since your device would have to have a good connection in the future, and if it doesn't, handle retries and make sure never to double-post.
There's a last-edited time, which I think should provide a superset of that information.
considers
Maybe have clients/Web UI more-clearly highlight if a response predated the last parent edit, which is I think the case where that really becomes an issue.
Honestly, I haven't actually seen anyone involved in bad-faith edits in conversations here. I've even seen people regularly thank people who provide corrections before correcting their post to credit the correction. Obviously, that doesn't mean that it's true everywhere or will last, but from a community standpoint, that's one area where I've been pretty happy with people here.