fix: update mowojang API base URL

[Piorunx22]

Description

https://mowojang.matdoes.dev/ returns HTTP 301 redirect to https://mowojang.seraph.si/

Fixed the 3D skin viewer by updating the texture fetch to the new host.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🎨 Style/UI changes
• ♻️ Code refactoring (no functional changes, no api changes)
• ⚡ Performance improvements
• 🧪 Adding or updating tests
• 🔧 Build/CI changes
• 🧹 Chore (maintenance, dependencies, etc.)

Testing

• I have tested these changes locally
• I have added tests that prove my changes work as expected (if appropriate)

Checklist

• My code follows the project's style guidelines
• I have used conventional commits for all commit messages
• I have added necessary documentation (if appropriate)
• I have added tests that prove my changes work as expected (if appropriate)
• I have added changesets if my changes should be reflected in the changelog

Code Quality Checks

• pnpm lint passes without errors
• pnpm format has been run (or no formatting issues exist)
• pnpm build completes successfully

[changeset-bot]

⚠️ No Changeset found

Latest commit: a260947

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[DuckySoLucky]

@DarthGigi +1

[DarthGigi]

Thanks!

[Kathund]

Even though this was merged I just want to point out something interesting that I found

I'm going to refer to the two instances of mowojang as matjang and seraphjang. Matjang will refer to https://mowojang.matdoes.dev and seraphjang will refer to https://mowojang.seraph.si

matjang seams to be having issues and sometimes returning 500 with the text Internal server error

And other times just fully resolving. Other times it just redirects to seraphjang with 301

seraphjang seams to be a proxy of some sorts of matjang as it says in the description of base page (/home - https://mowojang.seraph.si/)

My personal suggestion would be to try matjang and if it fails fall back to serahjang
There could be more that I am missing but this is just some interesting things that I found

[DuckySoLucky]

Even though this was merged I just want to point out something interesting that I found

I'm going to refer to the two instances of mowojang as matjang and seraphjang. Matjang will refer to https://mowojang.matdoes.dev and seraphjang will refer to https://mowojang.seraph.si

matjang seams to be having issues and sometimes returning 500 with the text Internal server error And other times just fully resolving. Other times it just redirects to seraphjang with 301

seraphjang seams to be a proxy of some sorts of matjang as it says in the description of base page (/home - https://mowojang.seraph.si/)

My personal suggestion would be to try matjang and if it fails fall back to serahjang There could be more that I am missing but this is just some interesting things that I found

At backend I'm using official mojang's API as fallback in case this one fails, so I guess we could do that on the frontend as well?

[Clemintina]

Hello, as the co-owner of the Seraph project. The proxy was a fork of mat's code, we then rewrote it with multiple instances to reduce the error rate his proxy has. As such, he was credited in the official documentation. Our proxy should have no errors, and follows proper conventions unless you hit our original Rust based proxy which is still running his code which uses html errors.

[DarthGigi]

Thanks for your input @Clemintina

After talking to mat on discord, I've decided to completely switch from his (and seraph's) mowojang instance to just using the mojang api directly. As he told me that mojang's api added IP ratelimits.

Since our calls to mowojang are mostly done on the frontend/client side, that means that every call has the user's IP and not ours or mat's/seraph's mowojang instance(s), essentially fixing the rate limit issue as well as taking off some load on you.

[Clemintina]

Thanks for your input @Clemintina

After talking to mat on discord, I've decided to completely switch from his (and seraph's) mowojang instance to just using the mojang api directly. As he told me that mojang's api added IP ratelimits.

Since our calls to mowojang are mostly done on the frontend/client side, that means that every call has the user's IP and not ours or mat's/seraph's mowojang instance(s), essentially fixing the rate limit issue as well as taking off some load on you.

No worries, feel free to use ours if this solution doesn't work well. It adds virtually no load on our servers.

[DarthGigi]

Nevermind I guess