AkkomaGang/akkoma

Fork 92

Ability to disable editing posts. #247

New issue

Closed

opened 2022-10-31 01:46:06 +00:00 by foxing · 6 comments

foxing commented

2022-10-31 01:46:06 +00:00

Contributor

I am requesting the ability to disable post editing for all users on an instance, it introduces too many problems and solves none that delete and redraft doesn't already.

I am unable to find an option to do this within admin fe and there doesn't appear to be any documentation, but if someone can point me the right direction should it already exist then please do.

I am requesting the ability to disable post editing for all users on an instance, it introduces too many problems and solves none that delete and redraft doesn't already. I am unable to find an option to do this within admin fe and there doesn't appear to be any documentation, but if someone can point me the right direction should it already exist then please do.

spla commented

2022-10-31 06:38:59 +00:00

Out of curiosity, what problems?

Edit posts is working like a charm in my Akkoma instance and is way better than delete & redraft because allows to edit a post without breaking any interaction of the former one.

Out of curiosity, what problems? Edit posts is working like a charm in my Akkoma instance and is way better than delete & redraft because allows to edit a post without breaking any interaction of the former one.

foxing commented

2022-10-31 13:19:54 +00:00

Author

Contributor

Out of curiosity, what problems?

Edit posts is working like a charm in my Akkoma instance and is way better than delete & redraft because allows to edit a post without breaking any interaction of the former one.

I have observed for years people explain why twitter shouldn't and will not have an edit function, yes akkoma having an edit history partially solves some of the problems but it still does not solve others.
I don't really care to go into deep detail but I am of the opinion that typos don't matter and don't need to be fixed given microblogging's inherantly casual atmosphere, important corrections to posts should trigger notifications hence a reply would serve that better.
And of course an individual problem relating to the fediverse not having widespread edit compatibility, and I would not wish my users to use it (even with the warning) to add important stuff to their posts thinking that it can be seen by most of the fediverse.

I have moved my instance to akkoma and this has caused a divide already on opinion of the edit function, it would be easier to just give an option, I am also not very happy about the removal of pleroma chats for a similar reason, because of that having a more widespead fediverse compatibility, it wouldn't be unexpected to think that people will be missing messages because of it. It would have achieved the same stance against it to just default it to switched off.
I saw it in another issue post on here but I agree that akkoma does not have the user base to actually be able to set new standards, and it will not for a long time if ever.

The best solution I would argue for the delete and redraft issue would instead be notifiying people they are replying to a post that is now deleted, and additionally if/when they are deleting a post with replies to it.

> Out of curiosity, what problems? > > Edit posts is working like a charm in my Akkoma instance and is way better than delete & redraft because allows to edit a post without breaking any interaction of the former one. I have observed for years people explain why twitter shouldn't and will not have an edit function, yes akkoma having an edit history partially solves some of the problems but it still does not solve others. I don't really care to go into deep detail but I am of the opinion that typos don't matter and don't need to be fixed given microblogging's inherantly casual atmosphere, important corrections to posts should trigger notifications hence a reply would serve that better. And of course an individual problem relating to the fediverse not having widespread edit compatibility, and I would not wish my users to use it (even with the warning) to add important stuff to their posts thinking that it can be seen by most of the fediverse. I have moved my instance to akkoma and this has caused a divide already on opinion of the edit function, it would be easier to just give an option, I am also not very happy about the removal of pleroma chats for a similar reason, because of that having a more widespead fediverse compatibility, it wouldn't be unexpected to think that people will be missing messages because of it. It would have achieved the same stance against it to just default it to switched off. I saw it in another issue post on here but I agree that akkoma does not have the user base to actually be able to set new standards, and it will not for a long time if ever. The best solution I would argue for the delete and redraft issue would instead be notifiying people they are replying to a post that is now deleted, and additionally if/when they are deleting a post with replies to it.

floatingghost commented

2022-11-11 10:33:12 +00:00

Owner

i am not going to make every piece of functionality optional, this would compound complexity with every feature it was applied to

chats were removed because they were only compatible with pleroma and they were near-unused

edits are compatible with everyone major (not misskey yet)

edit remain

i am not going to make every piece of functionality optional, this would compound complexity with every feature it was applied to chats were removed because they were _only_ compatible with pleroma and they were near-unused edits are compatible with everyone major (not misskey yet) edit remain

👍 1

floatingghost closed this issue

2022-11-11 10:33:12 +00:00

foxing commented

2022-11-12 02:23:24 +00:00

Author

Contributor

I have already forked your software to re introduce pleroma chats, and obviously I will now have to integrate the removal of the edit function too. Thanks for forcing people's hand. From the appearance of your code, the edit function is already partially optional in the front end, you clearly intended for it at some point.

Please understand that the less features you make optional, the less people willing to accept akkoma as the standard software, including a higher amount of people who are going to seriously dislike you. I have already witnessed many people talk negatively about your unwillingness to give people options with their own instances such as keeping chats, which is essentially forcing people to choose between custom emoji reacts and quotes or pleroma chats. I have already forked your software to re introduce pleroma chats, and obviously I will now have to integrate the removal of the edit function too. Thanks for forcing people's hand. From the appearance of your code, the edit function is already partially optional in the front end, you clearly intended for it at some point.

floatingghost commented

2022-11-12 02:28:44 +00:00

Owner

go for it! akkoma never aimed to be a default, standard software - it's explicitly for my area of fedi, and if others like that, then great! if they don't, ah well

the joys of free software is that you can change anything as you see fit, and I nor anyone else can stop you

go for it! akkoma never aimed to be a default, standard software - it's explicitly for my area of fedi, and if others like that, then great! if they don't, ah well the joys of free software is that you can change anything as you see fit, and I nor anyone else can stop you

❤️ 1

floatingghost commented

2022-11-12 02:29:46 +00:00

Owner

(also edits were cherry-picked from tusooa, it's not actually my code, just for the record)