Drawbacks & ToDo

File handling

Of course there are some drawbacks to this system and I will most likely edit the N8N workflow to include a bunch of additional measures to make the flow much easier and more broad in scope.

Ideally, I'd like to copy a picture URL and be able to also submit it to Zipline to archive images too. Sure I can just download them to my device or simply copy-paste them, but again this project is about keeping memes and other content saved and archived for use later. Its more about preserving memes and meme culture.

It shouldn't be too difficult to create some additional switches within N8N to handle specific types of URL's etc... or have additional settings. Regardless of implementation, having a more broad solution is ideal.

Opening Files

One of the things n8n has to do to upload something to Zipline (from what I can tell) is to READ the file completely in N8N. This means that entire file must fit into RAM. This is a problem.

In order to be more reliable, I had to move the Zipline / N8N stack over to my Unraid server from my Raspberry Pi, as I attempted to upload a 8GB file to Zipline and it fully crashed the Raspberry Pi because of its limited RAM.

There may be another way to do this sort of thing (maybe through a custom shell command run in N8N), but for now, its a big limitation and that CAN crash the system. I should honestly report this to N8N as an issue so it can be limited by system memory and throw an error rather than crashing the entire system.

Regardless, my Unraid server has a shit load of RAM and it can handle very large files with ease.