Seems to be working out pretty good so far over at https://social.coop/ tho this kind of thing lends itself better toward digital services due to it being easier to bootstrap bits vs IRL operations.
Woke up with a thought. In light of the news of Microsoft thinking about buying github combined with the ever increasing trend of creating locked down computers: phones, ChromeOS, MS Always Connected, it occurs to me that the next steps will be to require permission not just to distribute software (app stores), but to also be a developer. Access to the tools will increasingly be through the cloud mediated through these locked devices. Permission to develop could be revoked at any time.
@sim @mayuutann @sukinosenze It's not about owning up to mistakes. We all make mistakes, and we're grownups about it, but I was having a conversation with a friend the other day and got confused by something he typed, and then seconds later it "self-corrected" and I just felt wow, that's really nice, because it reduced the risk of meta-messages and the conversation could stay on topic. It's just a signal-vs-noise ratio thing. Especially if I look back at the conversation a day later and only want to know the stuff we talked about in a nice edited view.
Also, any edited messages are clearly marked as edited and the history is there.
I just read Mastodon's #256 earlier today and I'm not really upset, but mostly just disappointed that people would trash a genuinely useful feature that is even in the standard, because they believe it would just be abused and that the UI question is insurmountable, even though github, Facebook and other places have perfectly reasonable UIs for edited messages.