You should petition your admins to defederate or move to an instance that does so.

Lemm.ee basically doesn't defederate anything. You should probably go to an instance that defederates those instances.

Keep in mind that user-level instance blocks are not the same as instance-level defederations. AFAIK, it only blocks the communities. You'll still see comments and posts from that instance in other communities and that instance will still influence your feed with their votes.

It is better to go to an instance that defederates or to convince your current admin to defederate.

Punycode is not solving the same problem. Punycode solves Unicode in domain names. Percent encoding is for Unicode in URL paths. Lemmy only needs to worry about the paths, Punycode should be "supported" out of the box without any special handling

At least use TOML if you like ini, there is no ini spec but TOML can look quite similar.

It is also just a convention to use ASCII for usernames in many platforms.

That's only true for platforms that only caters to the English speaking world. The fediverse should be and is much broader than that.

ASCII is also supported out of the box in major OSes while some unicode characters might not.

What? There is no major OS that does not support Unicode out of the box.

Percent encoding is perfectly fine and users won't even see it.

Also please stop down voting twice with your alt accounts, that's not cool.

It's a major downside to my own users though. I wish I could disable uploads for everyone else :P

There is a standard way to encode Unicode into URLs, it definitely doesn't have to be ascii. Percent encoding is used all over the place.

EDIT: I don't mind a down vote but double down voting me from your alt @Asudox@lemmy.world is not cool. That's sockpuppetry/vote manipulation.

Yes, storage costs matters. I think it's honestly crazy that Lemmy caches images as much as it does. It would be great to be able to just disable it completely, but alas you can't do that without disabling uploads for your own users either (at least I don't know how).

Yes, but honestly unless you're very big, federation queries are the bulk of the processing and stuff from your own instance doesn't matter that much. I mean think about it, do you think the 100 active users on your own instance is what costs or the 10000 users posting all over the fediverse is what matters? Obviously the latter. So again, local user count is not that impactful.

ActivityPub users need to be identified by some identifier in the URL, and Lemmy chose the user name to be that identifier. As a result, non-Latin usernames become… complicated.

Sorry but this is just false. URIs can easily encode UTF-8 characters and it's perfectly standard to do so via percent-encoding. Example: https://en.wikipedia.org/wiki/😂. Your browser will even automatically convert that 😂 into the appropriate percent-encoding and will even display the emoji in the address bar, even if that is not the "true" URI.

This is, if you ask me, an unnecessary limitation in Lemmy.

No thanks, I’ll be staying with datastruct.nextState() rather than const nextState = prevState.nextState()

You can easily do the first option in Rust, you just use the mut keyword. That's it, nothing more than that. And you'll find that you quite rarely have to do that, and when you do it, it's actually quite a useful signal to be aware of, since mutability sometimes means a bit more surprising data changes.