It’s time for a slightly overdue summary of the changes introduced to Vernissage in July. The work was primarily focused on enabling the editing of statuses after they have been submitted to the server.

Status Updates

Updating the content of statuses is a relatively complex process, as it requires taking into account:

• the ability to edit a status on the web interface,
• sending information about the status update to other instances via ActivityPub,
• receiving information about status updates made in other instances via ActivityPub,
• creating entries that track the edit history of each status.

This is not a trivial task, and I wanted the feature to be presented to users in the most user-friendly way possible. For this reason, editing a status works exactly the same as creating a new one, so users shouldn’t feel confused or disoriented. Additionally, I wanted the display of edit history to be just as intuitive. When a status has a history of edits, a list of all previous versions is shown, and users can switch between the current and earlier versions. I hope this is a simple and intuitive solution.

Work on this functionality is still ongoing. Sending and receiving status changes from Pixelfed is already working. While receiving updates from Mastodon functions correctly, there is still an issue with sending updates to Mastodon. I hope to resolve this problem in the coming days so that everything will function as intended.

Minor Fixes and Changes

• Added new sorting options to the user list (available to moderators), such as by account creation date, last login, number of statuses, etc.
• Implemented email notifications to inform users whether their registration request has been accepted or rejected.
• Improved logging of deleted old statuses.
• Finalized the articles feature - it’s now possible to add photos to articles directly from the web interface.
• Improved the error message shown when a user enters an incorrect captcha code, making it clearer what went wrong.
• Added small loading indicators to show that an action on a status is being processed after it is clicked.
• Fixed a bug that in some cases prevented settings-related numerical values from being saved.
• Replaced the plain text input field for editing photo dates with a date-time picker.

As you can see, quite a few changes were introduced. Once the status editing functionality is finalized, the next step will be to add features that give users more control over blocking domains, users, hashtags, etc. I also plan to implement the ability to report to other instances and receive reports from them. In the meantime, I will continue to fix any newly discovered bugs. Step by step, we keep moving forward.