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).
forgejo: https://codeberg.org/asudox
matrix: https://matrix.to/#/@asudox:matrix.org
aspe:keyoxide.org:D63IYCGSU4XXB5JSCBBHXXFEHQ
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).
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.
You won’t get non latin usernames anytime soon. But you can change the display name using non latin charactets
You can delete or disable the service that creates those stories. Download Shizuku and activate it, then use Canta to delete it.
I said:
I couldn’t care less as long as the language is good.
Why wouldn’t I care if the language is bad in my opinion?
Sure. It is open source, but the development is done by Apple engineers. I also would like to state that Go has trackers in it. I also don’t really care what the creator of a language is. Homophobe, sexist, racist or other similar stuff, I couldn’t care less as long as the language is good.
Welp, I haven’t seen anyone learn Swift other than for Apple stuff these days. So I wonder how many can actually contribute to the code. It’s also made by Apple, so yeah. It would have been more performant and secure (both of which are pretty important in a browser) if it was written in a more low level language. For example Rust.
It’s nice and all but usage of Swift is kind of not great.
Surprised that happened. Very rare to see that these days.
Not sure if that is effective at all. Why would a crawler check the robots.txt if it’s programmed to ignore it anyways?
Block? Nope, robots.txt does not block the bots. It’s just a text file that says: “Hey robot X, please do not crawl my website. Thanks :>”
Shouldn’t have shared your face online publicly I guess.
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.