Serving the interwebz since Warning! If you can see this text, your browser is too old to load some of the CSS styles.
News
Roadmap for
Fuze Mediaboard will remain the priority until the end of the year. FuzeVD version 3, which has started development but is currently on hold, will be the focus in the early weeks/months of . An initial release in is the target.
Please be aware that FuzeVD 2 will likely stop working before that point due to YouTube's hostile changes. The updater in FuzeVD 2 is not built to handle the newest version of yt-dlp because that library depends on a javascript runtime, which FuzeVD Updater cannot download automatically. Do not use 'External update yt-dlp'; downloader will cease to function - unless you install a javascript runtime such as Deno in the same folder as the yt-dlp executable.
100% human
No AI is used to create any Fuze.page software or media.
Open-source contributions found to have been AI-generated/assisted will be rejected.
FuzeVD is now open source
View the source code on the Github repository. Please note that the yt-dlp and ffmpeg EXE files are not bundled in the source code - you will need to add them to the "Video Downloader" folder yourself.
Fuze Mediaboard version 0.0.0 has been released, succeeding Fuze Game as the flagship Fuze.page software. This is a messageboard that can be deployed on a web server to host a community.
Software proposal: Fuze Imageboard
There exist a number of imageboard programs today including Vichan, JSchan, and Yotsuba. Each one is fraught with its own problems: Vichan is inefficient; JSchan is limited; Yotsuba, well, that's a long story.
The end goal is to write an imageboard that is:
Efficient. The fact that Yotsuba runs so much more efficiently than Vichan, despite the former running an ancient version of PHP (as of the Great Cuckset), indicates that efficiency varies wildly between imageboards and that there are greater gains to be made.
Minimalist. Generally the more dependencies there are, the more vulnerable the software stack becomes to glitches, slowdowns, and security holes. This is especially the case when the stack is not constantly maintained and kept up to date. Features get added and deprecated over time whilst some software gets abandoned entirely, making proper maintenance headache-inducing - Better to avoid unnecessary dependencies which are not already mature and well-established. This rule should not override rule 1.
Modern. Since the early days of the internet, there have been many advances in web technologies. One such advancement is websockets. In classic imageboards the client either needs to refresh to check for new posts in a thread, or turn on an auto-update which sends requests to the server with an interval; this is wasteful and archaic. With websockets, the server can send an update to connected clients the moment a post is received. This rule should not override rules 1 and 2.
This proposal may or may not be implemented, in part or in full.
This release contains major bug fixes and a few additions.
The previously selected format and quality will now load on application startup.
Removed "notify on download complete" and added options to split the download into chapters, include the video ID (which is now excluded by default), and to disable AV1 encoding.
