Auto-approve followbacks (frontend part) #365

Merged
floatingghost merged 1 commit from Oneric/akkoma-fe:followbacks-fe into develop 2024-02-20 16:24:37 +00:00
Member

Depends on the backend patches from AkkomaGang/akkoma#674 to actually take effect. See backend PR for further details.

Depends on the backend patches from https://akkoma.dev/AkkomaGang/akkoma/pulls/674 to actually take effect. See backend PR for further details.
katafrakt reviewed 2024-02-03 11:21:45 +00:00
src/i18n/en.json Outdated
@ -600,6 +600,7 @@
"list_aliases_error": "Error fetching aliases: {error}",
"list_backups_error": "Error fetching backup list: {error}",
"lock_account_description": "Restrict your account to approved followers only",
"permit_followback_description": "Always approve follow requests from followed users",
First-time contributor

This is a nitpick, but I wonder if the message here is clear enough. Perhaps something like this would be more precise:

Automatically approve follow requests from users you already follow

?

This is a nitpick, but I wonder if the message here is clear enough. Perhaps something like this would be more precise: > Automatically approve follow requests from users you already follow ?
Author
Member

Thanks for the suggestions, this is probably a bit easier to read, yeah

However, with “Automatically” the description gets longer than any other description currently on this page leading to linebreaks at widths which (at least in English) previously didn’t need any.
Just swapping “Automatically” for “Always” gets the text a bit below the current longest again though; for now I pushed this. Does this seem good or was “Automatically”-“Always” part of the confusing bit?

Alternatively the "follow request" part could be implied and “Automatically approve requests from already followed users” will also be short enough. Or maybe I’m just worrying too much about the linebreak and we should just use your original suggestion

Thanks for the suggestions, this is probably a bit easier to read, yeah However, with “Automatically” the description gets longer than any other description currently on this page leading to linebreaks at widths which (at least in English) previously didn’t need any. Just swapping “Automatically” for “Always” gets the text a bit below the current longest again though; for now I pushed this. Does this seem good or was “Automatically”-“Always” part of the confusing bit? Alternatively the "*follow* request" part could be implied and *“Automatically approve requests from already followed users”* will also be short enough. Or maybe I’m just worrying too much about the linebreak and we should just use your original suggestion
First-time contributor

I think it's actually "Automatic" vs "Always" that makes it a bit unclear. Not sure if the line length is that important here. "Automatically approve requests from already followed users" sounds good IMO.

I think it's actually "Automatic" vs "Always" that makes it a bit unclear. Not sure if the line length is that important here. "Automatically approve requests from already followed users" sounds good IMO.
Author
Member

oki, changed it to the latter

(as for line length: on a typical desktop all of the discussed options are equally fine, but on tablets or phones using the mobile interface it might become relevant)

oki, changed it to the latter (as for line length: on a typical desktop all of the discussed options are equally fine, but on tablets or phones using the mobile interface it might become relevant)
Oneric marked this conversation as resolved
Oneric force-pushed followbacks-fe from 67bbf6971c to c065a46694 2024-02-03 15:14:48 +00:00 Compare
Oneric force-pushed followbacks-fe from c065a46694 to a77a9e04d9 2024-02-04 21:19:23 +00:00 Compare

:nodders: functionality all works

thankieos

:nodders: functionality all works thankieos
floatingghost merged commit ed0b403c33 into develop 2024-02-20 16:24:37 +00:00
floatingghost deleted branch followbacks-fe 2024-02-20 16:24:37 +00:00
mel referenced this pull request from a commit 2024-05-15 22:36:01 +00:00
Sign in to join this conversation.
No description provided.