surprised pikachu

that really shouldn’t be an ongoing issue, I’ll try to find some time this weekend to see if I can identify it.

it shouldn’t have much direct impact as lemmy doesn’t care about it being federated much currently but it might become more relevant with future updates.

i just tried subscribing to a random lemmy.world community and that worked without a problem, took less than a minute and it was updated to say joined.

would you mind sharing some of the communities you experience this with? feel free to pm me if you don’t want to share that publicly.

https://gui.fediseer.com/instances/detail/feddit.org#censures-given alle blockierten instanzen sollten hier aufgelistet sein

@abos@feddit.org @abos@discuss.tchncs.de fyi

no specific timeline currently unfortunately, it depends on when we have spare time to progress with this

hello,

we’re currently working on migrating to new infrastructure (same hardware, new deployment setup) that will allow us to separate IP blocks for feddit.org from those used by the rest of the fediverse foundation.

we currently have certain bad reputation and some asian networks blocked due to a large amount of malicious traffic, which is a major problem for other fediverse foundation services, partially resulting in service outages before these blocks were implemented.

unfortunately this will still take some time for the migration to be completed.

if you are being blocked while using a residential or mobile internet connection outside of asia or a static non-VPN IP please let us know your IP and we will review your individual case. you can send us an email to admin @ domain of this instance or send a lemmy pm to @BurningTurtle@feddit.org or me and we’ll forward this internally.

i just checked and it is indeed using the same rate limit for settings exports.

this was likely an issue with lemmy’s rate limits.

there is a dedicated rate limit for importing settings, which is currently set to 1 attempt per 24h. unfortunately this setting is not exposed in the web interface, which is likely why we didn’t originally adjust this to a higher number.

i’ll have have a look at raising that.