You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hydrus Network has a special file format, that describes information about a website/API. It is used to get all the images from a supported website. These files are also able to be user generated.
If NekoFans were able to read these files, then we could very easily add support for a lot of new websites/API by importing the already made Presets.
Here is a full list of websites/APIs that Nekofans could add if it could read the file format.
These 'downloaders' also provide additional metadata about the images that could be displayed by nekofans. A lot of data would also need to be ignored.
Help with this is appretiated, a simple proof of concept or a way to convert these parser .png files into a usable format would be great. Nekofans could include these .png files in the build of Nekofans and parse them dynamically at runtime. Or we somehow convert them ahead of time into and save it in a simplified form
The text was updated successfully, but these errors were encountered:
The Hydrus Network has a special file format, that describes information about a website/API. It is used to get all the images from a supported website. These files are also able to be user generated.
If NekoFans were able to read these files, then we could very easily add support for a lot of new websites/API by importing the already made Presets.
Here is a full list of websites/APIs that Nekofans could add if it could read the file format.
These 'downloaders' also provide additional metadata about the images that could be displayed by nekofans. A lot of data would also need to be ignored.
Additional info can be found on the Hydrus Wiki
Help with this is appretiated, a simple proof of concept or a way to convert these parser .png files into a usable format would be great. Nekofans could include these .png files in the build of Nekofans and parse them dynamically at runtime. Or we somehow convert them ahead of time into and save it in a simplified form
The text was updated successfully, but these errors were encountered: