WebOS Devlog 4 ✨

Debugging My WebOS Project

• Today I continued working on my WebOS project and focused mainly on debugging and identifying issues in the current build.

Work Done:

• Tested the project to understand which features were working and which ones were causing problems.
• Started using browser developer tools to inspect the project and look for possible errors.
• Checked the HTML, CSS, and JavaScript structure since the entire project is currently contained in a single file.
• Investigated issues with app interactions and screens not opening as expected.
• Began tracing possible JavaScript problems related to buttons, events, and element connections.

Challenges:

• Some features are still not responding correctly, and I am still working to locate the exact cause.
• Debugging a large single-file project makes it harder to locate specific issues quickly.
• Understanding browser console errors and developer tools is taking time, but it is helping narrow down the problems.

Next Steps:

• Continue analyzing JavaScript errors and fixing broken interactions.
• Test each application and feature separately.
  Improve the project structure to make future debugging easier.

The project is still under development, but each debugging session is helping me understand the system better and move closer to a stable version.

WebOS Devlog 4 ✨

Debugging My WebOS Project

• Today I continued working on my WebOS project and focused mainly on debugging and identifying issues in the current build.

Work Done:

• Tested the project to understand which features were working and which ones were causing problems.
• Started using browser developer tools to inspect the project and look for possible errors.
• Checked the HTML, CSS, and JavaScript structure since the entire project is currently contained in a single file.
• Investigated issues with app interactions and screens not opening as expected.
• Began tracing possible JavaScript problems related to buttons, events, and element connections.

Challenges:

• Some features are still not responding correctly, and I am still working to locate the exact cause.
• Debugging a large single-file project makes it harder to locate specific issues quickly.
• Understanding browser console errors and developer tools is taking time, but it is helping narrow down the problems.

Next Steps:

• Continue analyzing JavaScript errors and fixing broken interactions.
• Test each application and feature separately.
  Improve the project structure to make future debugging easier.

The project is still under development, but each debugging session is helping me understand the system better and move closer to a stable version.

Cosmos Devlog 8 🪐✨– Silly Stuff Page

What I worked on:

• Added a simple Silly Stuff page to the website.
• Filled it with a handful of basic, intentionally lame jokes to make the site feel a little more personal and less serious.
• Kept the design minimal so it fits with the rest of the website without taking attention away from the main content.

Challenges:

Nothing major here—this page was meant to be lighthearted, so I focused on keeping it simple instead of overcomplicating it.

Progress:

• The page is complete for now. It’s just a fun little corner of the website, and I might add more random jokes or goofy content in future updates.

Gonna reship the project soon! 🫶🏻

Cosmos Devlog 8 🪐✨– Silly Stuff Page

What I worked on:

• Added a simple Silly Stuff page to the website.
• Filled it with a handful of basic, intentionally lame jokes to make the site feel a little more personal and less serious.
• Kept the design minimal so it fits with the rest of the website without taking attention away from the main content.

Challenges:

Nothing major here—this page was meant to be lighthearted, so I focused on keeping it simple instead of overcomplicating it.

Progress:

• The page is complete for now. It’s just a fun little corner of the website, and I might add more random jokes or goofy content in future updates.

Gonna reship the project soon! 🫶🏻

Cosmos Devlog 7 🪐✨- Home Page Refresh

What I Worked On:

• I revisited the home page to refine the overall experience instead of adding more features. 
• I reorganized a few sections, adjusted the layout, and made small design changes that helped the page feel more balanced and intentional. 
• I also planned out a new “Silly Stuff” section that will feature a collection of wonderfully terrible space jokes.

Challenges:

Most of the challenge came from deciding what to change rather than how to change it. Even minor layout tweaks affected spacing and alignment, so it took a fair bit of trial and error to make everything feel cohesive while leaving room for future additions.

Progress:

• The home page now has a cleaner flow and feels much closer to the vision I had for The Cosmos. 
• With the foundation in place, the next step is bringing the Silly Stuff page to life—because every journey through the universe deserves a few astronomically bad jokes along the way. 🫶🏻😄

Cosmos Devlog 7 🪐✨- Home Page Refresh

What I Worked On:

• I revisited the home page to refine the overall experience instead of adding more features. 
• I reorganized a few sections, adjusted the layout, and made small design changes that helped the page feel more balanced and intentional. 
• I also planned out a new “Silly Stuff” section that will feature a collection of wonderfully terrible space jokes.

Challenges:

Most of the challenge came from deciding what to change rather than how to change it. Even minor layout tweaks affected spacing and alignment, so it took a fair bit of trial and error to make everything feel cohesive while leaving room for future additions.

Progress:

• The home page now has a cleaner flow and feels much closer to the vision I had for The Cosmos. 
• With the foundation in place, the next step is bringing the Silly Stuff page to life—because every journey through the universe deserves a few astronomically bad jokes along the way. 🫶🏻😄

Cosmos Devlog 6 🪐✨ - Designing the home page

What I worked on today:

• Enhanced the homepage by designing an immersive hero section, adding floating animations, and a featured quote section. 
• Refined the layout and visual hierarchy to create a more engaging, cohesive, and space-inspired landing experience.

Challenges:

• Resolved layout issues caused by fixed navigation and page scrolling.
• Fixed CSS syntax errors affecting animations and shadows.

Progress:

• Designed the homepage hero section.
• Added some animation.
• Integrated a quote card to reinforce the site’s theme.
• Improved overall layout, spacing, and visual consistency.

Also, I feel so glad to let y’all know that my project is now complete and ready to be shipped. I feel so excited! And thank you all for supporting me! 🫶🏻😄

Cosmos Devlog 6 🪐✨ - Designing the home page

What I worked on today:

• Enhanced the homepage by designing an immersive hero section, adding floating animations, and a featured quote section. 
• Refined the layout and visual hierarchy to create a more engaging, cohesive, and space-inspired landing experience.

Challenges:

• Resolved layout issues caused by fixed navigation and page scrolling.
• Fixed CSS syntax errors affecting animations and shadows.

Progress:

• Designed the homepage hero section.
• Added some animation.
• Integrated a quote card to reinforce the site’s theme.
• Improved overall layout, spacing, and visual consistency.

Also, I feel so glad to let y’all know that my project is now complete and ready to be shipped. I feel so excited! And thank you all for supporting me! 🫶🏻😄

Cosmos Devlog 5 🪐✨ - Building the Planetary projects page

What I worked on:

• Created a dedicated Planetary Projects page.
• Added project titles, descriptions, and mission status indicators for each project.
• Included links to live demos and repositories, allowing visitors to explore the projects directly.

Challenges:

• Deciding how to present projects in a way that was both visually engaging and easy to navigate.
• Keeping the page responsive and visually balanced as the number of showcased projects increases.

Progress:

• Planetary Projects page completed. 🫶🏻

Cosmos Devlog 5 🪐✨ - Building the Planetary projects page

What I worked on:

• Created a dedicated Planetary Projects page.
• Added project titles, descriptions, and mission status indicators for each project.
• Included links to live demos and repositories, allowing visitors to explore the projects directly.

Challenges:

• Deciding how to present projects in a way that was both visually engaging and easy to navigate.
• Keeping the page responsive and visually balanced as the number of showcased projects increases.

Progress:

• Planetary Projects page completed. 🫶🏻

Cosmos Devlog 4 🪐✨- Building the Mission Dossier

What I worked on:

• Created a dedicated Mission Dossier page instead of a generic About Me section.
• Designed a glassmorphism-inspired interface to complement the space theme.
• Organized personal information into a structured dossier format with labels such as Explorer, Mission Objective, and Current Status.
• Added visual hierarchy through custom typography, spacing, and glowing accents to reinforce the sci-fi aesthetic.

Challenges:

• Finding the right balance between visual style and readability. While the goal was to create an immersive interface, it was equally important to ensure the information remained clear and easy to navigate.
• Iterated through several layout concepts before settling on a design that felt more like a spacecraft database than a traditional profile page.

Progress:

• Mission Dossier page completed.

• Consistent design language established for future pages across the portfolio.

Cosmos Devlog 4 🪐✨- Building the Mission Dossier

What I worked on:

• Created a dedicated Mission Dossier page instead of a generic About Me section.
• Designed a glassmorphism-inspired interface to complement the space theme.
• Organized personal information into a structured dossier format with labels such as Explorer, Mission Objective, and Current Status.
• Added visual hierarchy through custom typography, spacing, and glowing accents to reinforce the sci-fi aesthetic.

Challenges:

• Finding the right balance between visual style and readability. While the goal was to create an immersive interface, it was equally important to ensure the information remained clear and easy to navigate.
• Iterated through several layout concepts before settling on a design that felt more like a spacecraft database than a traditional profile page.

Progress:

• Mission Dossier page completed.

• Consistent design language established for future pages across the portfolio.

DEVLOG #5 (might be the last devlog) Hey! It’s been 11 days since the last devlog. DOSEFIELD wasn’t abandoned—I was just busy building instead of writing.This update was really about two things: making the code cleaner and making the site feel like it belongs in a space mission.The first issue was hidden in the background. The NASA validation numbers on the website were calculated separately from the ones used in my research. The math was identical, but it existed in multiple places. That meant one future change could easily make the numbers disagree.So I refactored everything to use a single source of truth. Now every result comes from the same function, making the site much easier to maintain and much harder to break.Then I focused on the design. The old version worked, but it didn’t feel like DOSEFIELD. I redesigned the interface with a mission-control style, added a cleaner layout, and simplified the visuals. I also removed a lot of unnecessary effects—less glow, fewer gradients, and a more purposeful look.After all those changes, I reran every test. All 107 tests still pass, and the stopping-power calculations remain within 1.55% of NIST reference data, exactly as before.There’s still one limitation: my model predicts about 67% of the radiation dose measured by NASA during the trip to Mars. That’s because it doesn’t yet simulate secondary particle production inside spacecraft shielding. It’s an important limitation, and it’s clearly explained on the website rather than hidden.The biggest lesson from this update wasn’t about physics—it was about revisiting old work. Good code doesn’t duplicate logic, and good design doesn’t rely on effects to look impressive. Sometimes the best improvement is simply cleaning up what you already built.

Devlog #08

Hello everyone(˶ᵔᗜᵔ˶)ﾉﾞ,

Welcome to Devlog #08 of AniSuffle.

Hope you all are doing great.

Okay, now let me explain quickly of my recent changes or update on the site.

I am not sure but maybe this will be abit shorter devlog, maybeeee(ᵕ—ᴗ—)…. since most of the work is about backend (so nothing flashy to explain) also I will try to not bore anyone reading this.[also i try keeping the devlogs raw and unfiltered]

Okay now lemme explain.

Save Button & Auth Feature

Sooo, the feature I have recently added to my site, actually not added, am still working on it is the save button and also adding a auth feature (the login and signup feature to be more simple =)).

Its not complete though.

And one more thing, you definitely dont need to login or signup to use any of the features and tools I have made so far beacuse I understand that signing up is such a pain, I mean at least to me it isss.

But there is one feature I want to add, and for this I think the signup is necessary.

Now let me expalin how the save feature is going to work.

It might be abit different as I am still working on it, I will just tell what I am planning to do.

** Why am I writing this devlog now?**

And before that If you ask why am I writing a devlog if I have not done the job, then ummm…∘ ∘ ∘ ( °ヮ° )

Actually I am working on the backend and I am scared I might mess anything up, as I am not too confident on backend and storing user data safely is my top priority( ◡̀_◡́)ᕤ whenever I am dealing with the backend and while doing this I didnt realize that I have already 5 or maybe 6 hours I am not sure but maybe its around 6 hours of time logged already so I thought of updating the devlog, even though I am in the middle of the function (I mean the development process(ᵕ ó ᴗ ò)).

I feel like I sound abit unclear (ó﹏ò｡)ummm, lemme just explain properly how the save feature is going to (or supposed to) work.

So there are two scenerios.

** When not signed in**

When you are not signed it, you will still be able to access all the feature of the site, even the save button.

But there is a catch.

All your saved animes/mangas will be stored on the localstorage.

Just a small explaination just in case you have no idea of what localstorage is, ummm…

In simple terms you can think it as the browser’s storage area, its typically around 4 MB or 5 MB i assume, but they should be more than enough to us as we are just storing the anime/manga url, source, id and stuff.. lets not go too deep into itദ്ദി(˵ •̀ ᴗ - ˵ ) ✧.

So you will still be able to save animes/mangas but you would need to be on the same browser with same browser profile to access those info.

When signed in

When you are signed in, your saved infos will be stored on the database of the server and you will be able to access them from any device and any browser. and This is the reason I am adding the Singup feature

Oh…

The devlog doesnt seems small any more. I’m i’m i’m sorry for that(ㅅ •᷄ ₃•᷅ )

Lemme wrap up quick umm but wait I will drop the screenshot of the site by pointing at the save button.

Currently its with no css, but dont worry I will update that ugly default button design (and maybe position as well) as soon as i finish my backed(・–・;)ゞ

I guess thats it for this devlog , If I forget to mention anything , I will surely update it in the next devlog.

If you didnt understand any of the point , please do comment and I will try to explain you there ദ്ദി◝ ⩊ ◜.ᐟ

Thank You all so much for reading.

Have a nice day =)

Hey everyone!Here’s a quick update on VeritasCore.If you haven’t seen it before, VeritasCore is an AI auditing tool. Instead of building another language model, it evaluates existing ones. You point it at a deployed AI model, it automatically launches red-team attacks looking for jailbreaks, bias, prompt injection vulnerabilities, and behavioral drift, then produces a cryptographically signed compliance certificate using Ed25519 so the results can be independently verified.The MVP already works. My goal for this hackathon is something different: making the entire pipeline run on AMD’s AI ecosystem using ROCm 7.2, PyTorch 2.9, and vLLM 0.16.0.Before writing a single line of integration code, I wanted to answer one question:Will this actually run on ROCm?A surprising number of AI projects quietly depend on NVIDIA-only libraries. Things like FlashAttention, xFormers, bitsandbytes, custom CUDA kernels, or even hardcoded cuda:0 references can completely derail a port.So my first task wasn’t coding—it was detective work.I went through the repository dependency by dependency, expecting to uncover compatibility problems.Instead, I found… almost nothing.The reason is surprisingly simple: VeritasCore doesn’t perform inference itself. It’s a black-box auditor that communicates with models over HTTP. The GPU only matters for the model being audited—not for the auditor.That completely changed the migration strategy.Instead of trying to rewrite the auditor, I can simply replace the scripted demo endpoint with a real open-source model served through vLLM on AMD hardware.To prepare for that, I built a small smoke test that will:verify PyTorch is using the HIP/ROCm build,confirm the AMD GPU is visible,and send a real inference request through the smallest practical model before scaling up.So far, I haven’t used a single second of GPU time. Every test has run entirely on CPU while preparing the environment.The next milestone is the exciting one: launching the first inference on the AMD notebook and seeing what actually breaks.That’s usually where the real engineering begins.

Cosmos Devlog 3 🪐✨ - Custom Cursor

Today’s focus was adding a custom cursor to the website.

What I worked on:

• Implemented a custom cursor to better match the space theme.
• Fixed issues where the cursor reverted to the default pointer when hovering over links.
• Learned how CSS cursor properties behave across different elements and how to override them consistently.

Challenges:

• The implementation took longer than expected due to multiple styling conflicts.
• As I’m still new to web development, debugging the issue required a lot of trial and error and reading documentation.

Progress:

• Custom cursor is fully functional.
• No major visual updates today, but I built a stronger understanding of CSS and debugging.

Credits:

• Cursor asset sourced from Cursors-4U and integrated into the project to fit the space-themed aesthetic.

Next steps:

• Design and implement the landing sequence.
• Continue building the homepage and navigation.
  Stay tuned! 🫶🏻

Cosmos Devlog 3 🪐✨ - Custom Cursor

Today’s focus was adding a custom cursor to the website.

What I worked on:

• Implemented a custom cursor to better match the space theme.
• Fixed issues where the cursor reverted to the default pointer when hovering over links.
• Learned how CSS cursor properties behave across different elements and how to override them consistently.

Challenges:

• The implementation took longer than expected due to multiple styling conflicts.
• As I’m still new to web development, debugging the issue required a lot of trial and error and reading documentation.

Progress:

• Custom cursor is fully functional.
• No major visual updates today, but I built a stronger understanding of CSS and debugging.

Credits:

• Cursor asset sourced from Cursors-4U and integrated into the project to fit the space-themed aesthetic.

Next steps:

• Design and implement the landing sequence.
• Continue building the homepage and navigation.
  Stay tuned! 🫶🏻

Cosmos Devlog 2 🪐✨ - What I would be doing today:

• Make the site more creative.

• Add some space facts.

• Try to finish the first page of the website.

• Maybe add some images.

Note: I am so sorry but I have been staying a little busy lately because of school work so I will try my best to complete making the site as fast as I can! 🫶🏻