Please add OctoPrint Support to EasyPrint on Printables.  

RE: Please add OctoPrint Support to EasyPrint on Printables.

This may be difficult, but probably not impossible. The EasyPrint feature does its slicing on a server that Pruas either owns, or more likely rents time on. That puts the slicer on the open internet. Most OctoPrint installs are on personal LANs so aren't (or shouldn't be) findable on the open internet for security reasons. (I know that I don't want my RPi that runs my OctoPrint to unwittingly become part of a bot farm, malicious or not.) So, once the server based slicer finishes and creates the print file (gcode or bgcode), how is it able to put the print file onto an OctoPrint that it can't find?

Now, EasyPrint does have an "offline printer" option that may be how you can download the print file to your device and then upload it to your OctoPrint yourself.

RE:

PrusaLink runs in a such way that it sends POST messages to PrusaConnect t lemetry endpoint, and can in response body additional commands such as gcode  (move print head for example) or other ( download gcode and start printing).

Thus the plugin to OctoPrint would have to simulate that it is a printer and send telemetry and process such commands.

I do not know how OctoPrint works but it would have to be able to interwine gcode/bgcode file load with incoming commands form PrusaConnect.

The problem may be when the printer registers to the PrusaConnects, because it sends model and serial number which are AFAIR verified. I remember that for certian models there is a trick to send 'generic serial number' but it means you may be using OctoPrint with Prusa XL but in PrusaConnect it registers as generic ancient i3 model, which may result in suboptimal gcode generated or the number of commands it supports. But that is just a theory, not sure about actual implementation details.

So it should be doable but probably reality will provide much less features than people would expect.