• 0 Posts
  • 12 Comments
Joined 10 months ago
cake
Cake day: September 9th, 2023

help-circle




  • a “tl,dr” bot would probably not even need high end hardware, because it does not matter if it takes ten minutes for a summary.

    True, that’s a good take. Tl;dr for the masses! Do you think an internal or external tl;dr bot would be embraced by the Paperless community?

    It could either process the (entire or selected) collection, adding the new tl;dr entries to the files “behind the scenes”, just based on some general settings/prompt to optimize for the desired output – or it could do the work on-demand on a per-document basis, either based on the general settings or custom settings, though this could be a flow-breaking bottleneck in situations where the hardware isn’t powerful enough to keep up with you. However, that only seems like a temporary problem to me, since hardware, LLMs etc. will keep advancing and getting more powerful/efficient/cheap/noice.

    a chat bot do not belong into paperless

    Right – but, opposingly to that, Paperless definitely do belong into some chatbots!


  • I’m not interest in sending my documents to open AI.

    You wouldn’t have to. There are plenty of well-performing open-source models that work with an API similar to the Open AI standard, with which you can simply substitute OpenAI models by using a different URL and API-key.

    You can run these models in the cloud, either selfhosted or “as a service”.

    Or you can run them locally on high-end consumer-grade hardware, some even on smartphones, and the models are only getting smaller and more performant with very frequent advancements regarding training, tuning and prompting. Some of these open-source models are already claiming to be outperforming GPT-4 in some regards, so this solution seems viable too.

    Hell, you can even build and automate your own specialized agents in collaborating “crews” using frameworks, and so much more…

    Though, I’m unsure if the LLM functionality should be integrated into Paperless, or rather implemented by calling the Paperless API from the LLM agent. I see how both ways could fit some specific uses.







  • When I cast from the Jellyfin app on my phone (or the webapp) (to either the Jellyfin app on my Android TV box) or to Kodi (through Jellycon/Jellyfin addon or DLNA), the content is playing independently of my phone. This means that if I disconnect from the device I’m casting to in the Jellyfin app, the content will keep playing. It’s not streaming through my phone, but I can reconnect to regain remote control. I guess it’s the same case for Linux clients. If not, you can use Kodi with Jellycon addon (and not the Jellyfin addon, since that will sync the library to Kodi, which is unnecessary here). You will need a screen to set it up, but once that’s done + auto-launch Kodi at boot if you wish to, it will work headlessly if necessary as a client to cast to. Another reason to use Kodi is the very wide variety of formats it supports.