You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On most instances hitting the edit button leads to a ban info page, which may initially throw some users into confusion. I understand that hiding the edition capabilities completely is not that much of a good idea either, as not every instance is banned.
One solution I can think of is to make the server check for a ban status once, possibly also scraping the ban expiration date, then save that in a file or other form of a metadata it could announce to federated servers* to find those which are not banned, then redirect the user (with a confirmation page, of course). As a result the users willing to make edits to articles censored in their countries can still do that without manually trying to find an instance which does not ban edits.
* e.g. using ActivityPub
The text was updated successfully, but these errors were encountered:
On most instances hitting the edit button leads to a ban info page, which may initially throw some users into confusion. I understand that hiding the edition capabilities completely is not that much of a good idea either, as not every instance is banned.
One solution I can think of is to make the server check for a ban status once, possibly also scraping the ban expiration date, then save that in a file or other form of a metadata it could announce to federated servers* to find those which are not banned, then redirect the user (with a confirmation page, of course). As a result the users willing to make edits to articles censored in their countries can still do that without manually trying to find an instance which does not ban edits.
* e.g. using ActivityPub
The text was updated successfully, but these errors were encountered: