My API does ALOT of things. The main things it handles are:
- My random profile picture
- The spin counter when you click my pfp
- Modifying my Lanyard data
- My socials
- The weekly video section of my site (No link for this one, its a websocket thing)
This list is WAY more than it should be, or I want it to be though! So I have a couple plans for what to do when it comes to splitting these chunks apart.
1. PFPizer
I've been (VERY SLUGGISHLY) working on a program dedicated to hosting random pfps. Whether it will have a UI dashboard is still up in the air because I LOVE dashboards yet HATE making dashboards, but the idea is that it'll be a fairly accessible way for anyone to host something somewhere, with tons of API endpoints, and very configurable options.
This would be great because, honestly, the API pfps are somewhat limiting and very hardcoded. And, as it stands, there's no way to credit the original artist's work for the images, which is something I hope to do with PFPizer. Plus, it just feels filthy having to commit other artist's works to my git repos, so it'll stop that as well.
2. Lanyard fork
Originally, the API proxied the Lanyard websocket, as well as changing some of its data. This was because I was using the lanyard websocket at lanyard.rest, and I didn't wanna connect to it with tons of websockets, and just so I could have parity between services. But, now that I'm hosting lanyard on my own, proxying it is meaningless! Instead, I wish to fork Lanyard, and host that fork instead, with my own modifications.
3. Clipdump
I have ALSO been (SUPER DUPER EXTRA SLUGGISHLY) working on a program dedicated to hosting my clips. Mainly for the sake of getting around Discord's 10mb file limit without paying for disgusting Nitro or Nitro Classic, but also so that I can automatically put clips on my website!
The socials and spincount will be kept to the API. Hopefully, I'll be able to get all this done uh. One day! Yay!