Conversation

Notices

1. MMN-o ✅⃠ (mmn)'s status on Wednesday, 19-Apr-2017 03:55:37 EDT MMN-o ✅⃠

   • ostatus
   • GNU Social
   • maloki
   @maloki No it wouldn't cause a lot of Federation issues necessarily. It could perhaps cause duplicates, but since #Atom has the "atom:updated" element then - just as with any feed reader - !OStatus implementations can see that it is updated.
   
   However, it should only be possible to update atom:content and not mentions. Categories etc. is debatable.
   
   Why we haven't implemented updates in !GNUsocial is mainly because we solve it the social way, by just saying "oops, made an error" or accept that we are not all perfect and thus can live with spelling errors etc. If it's something really, really bad we just delete the post.
   
   Also, updates are not implemented because I work too much and if I did implement it, I'd want it to have a complete revision history - which would probably be cause enough for people who want to edit their post to choose "delete" instead anyway. ;)
   • MMN-o ✅⃠ (mmn)'s status on Wednesday, 19-Apr-2017 03:57:21 EDT MMN-o ✅⃠

     in reply to

     • GNU Social
     • maloki
     @maloki In the current state of code, !GNUsocial at least wouldn't accept the update (no duplicates) because the post would still, if I read the Atom spec correctly, have the same URI.
   • MMN-o ✅⃠ (mmn)'s status on Wednesday, 19-Apr-2017 04:10:18 EDT MMN-o ✅⃠

     • maloki
     @maloki Sorry, don't take my long post as some kind of rant against you (that's how I interpret the "dude").
     
     I just explain my perspective of it after a couple of years in this environment ;) And I can't do it on the #GitHub issues because, y'know, I don't like being a customer with proprietary services etc.