winsrewu

The author reports on ongoing software development work, focusing on two main areas. For a Fabric mod, the FMJ v2 component is nearly complete and awaits testing. Concurrently, they are engaged in full-stack development, having switched the ORM for better JSON support. Efforts to enhance the authentication system and UI are partially done, with an email system implemented and return values standardized, but error handling remains non-functional.

I figured the April Fool's version wasn't that fun either.

After heading to the Fabric Discord to chat a bit following #2, the only thing missing for the Fabric Mod JSON v2 now is some testing. So, I have another chance to ramble, though I’ll have to wait for them to wake up for a response.

The rest of the time, I’ve been working on full-stack development. Originally, I planned to improve the UI, but then I realized the authentication system needed to log some IP information. To do this, I’d have to set up keys on both the frontend and backend, and also add email

winsrewu

In a brief blog post, the author reflects on a rejected pull request for Fabric loader due to its aggressive approach and subpar quality, noting plans to collaborate on a similar feature. They also describe creating two tools: one for managing server.properties with a formatting error, and another for video clipping via image recognition, which functions despite performance issues.

The page refreshed and the content is gone. I don’t feel like writing anymore, so I’ll keep it short.

The other day, without much thought and without fully understanding the situation, I submitted a pull request to the Fabric loader.
The functionality was okay, but the approach was a bit too aggressive, and the quality wasn’t great, so it didn’t get merged.
Someone else is working on the same thing, but progress is a bit slow. I plan to communicate with them and implement some features first, ensuring forward compatibility.
Fabric loader PR #1024.

Aside from that, I wrote two small tools.

winsrewu

This blog post details the technical challenges and solutions for a custom music streaming website. The author explains how a recent browser update broke the old audio streaming logic, necessitating a new approach using Media Source Extensions and mp4-box.js to handle Bilibili's m4a format. The post also covers the motivations for building a custom platform, including resource integration and playback control, and mentions its Next.js and Vercel-based architecture.

I think I'm using this bbs as a blog, lol.

Anyway, first of all (ignore my broken English)

Well, it really is too broken, needs fixing