@Makura feditext supports this! i know this as someone who wrote a PR for iceshrimp.js that added support for it
nerd shit: it's possible your instance lacks the source.follow_requests_count value in its /api/v1/verify_credentials response. this is part of the core mastodon API, and required by feditext to even show the follow requests list, but for some reason, still missing from a couple servers.
anyways iceshrimp.js (and possibly other misskey forks) uses ratelimiter which stores state in redis. if you've been rate-limited, check if your instance uses a redis instance and look for keys under <INSTANCE-HOST>:limit:<USER_ID>. you can DEL them or even ZRANGE <KEY> 0 -1 to view the logs the rate limiter is running with
@ielenia i've always just imported my old follows manually- this is the first time i've ever done an official migration
i had completely forgotten that instances will generally try to rebuild social graph by sending new follow requests from all the previous account's followers.
i only did this officially so that people would stop getting my accounts confused- hell, my first account on wet-dry world only redirects; even that's not quite "migrated"
oh god oh fucking hell okay so it turns out when you migrate a fedi account it tells all of the instances with accounts following you that they should issue new follow requests to that account good fucking grief
shoutout fedi admins who have to rebuild their own instance to hack in a patch to a broken feature in order to avoid delving into the horrendous spaghetti code that surrounds it
@ari@arimelody.space