Locking for rule 5.

Locking for rule 5.

Locking for rule 5.

aight

Thanks for the clear response. So it is safe to assume that federated remote communities get permanently saved to the instance?

Gone. The instance owner no longer hosts the instance.

OP, I’ll be locking your post as it violates rule 5.

OP, I’ll be locking this post as it violates rule 5.

OP, please mark this post as NSFW.

No problem. Though I’ll be locking this post. It really generated lots of reports and drama in the comments section.

Your post is locked for rule 5, OP.

Just as a side note: Accounts not on the instance of the community (in this case lemmy.world) will have problems receiving and resolving reports.

This is a known issue and will be supposedly fixed in Lemmy v0.20.0

That’s a problem with your network or phone’s.

99.9% / 0% / 0.1%

Using ASCII in URLs is simple and is less error prone than “supporting” unicode via percent encoding. It is also just a convention to use ASCII for usernames in many platforms. ASCII is also supported out of the box in major OSes while some unicode characters might not. What about impersonation? And what about people trying to type in the username of someone that uses unicode? It is not logical to use unicode in this case.

Canta uses Shizuku to delete user and systen apps. There is also a few categories like Recommended, Advanced, Unsafe, etc. Most of the apps also have comments on it by the dev (I suppose).

Which most likely is written in much more detail than you ever could do.

Because URLs are usually in ASCII. That was a standard. Check RFC 1738 and 3986. Now, you can use percent encoding, but why use that. It just complicates things.