Custom server & API

sotn3m

Hi,

Diarium has a lot of things done right 🙂 One of the unique features is the ability to download additional data when opening a note. I believe this is a big strength of Diarium.
It is no surprise to me that there is a limit on how many integrations can be supported - vide Garmin thread.

Can I propose to add single integration aimed a little bit more at developers? What would happen if users/developers could implement a server according to the standards defined in Diarium?
The idea is that it is up to the user to host the server (cloud, raspberry pi etc) and/or implement it.

I am guessing a contract can be relatively straightforward (for illustration purposes mostly).
Single controller/query:

GET /data_for_diarium/2021/06/15

with return similar to:

[
   {
      "type": "event",
      "icon": "uri...",
      "color": "red",
      "text": "Balance: $50k"
   },
   {
      "type": "event",
      "icon": "uri...",
      "color": "blue",
      "text": "mail from X"
   },
   {
      "type": "event",
      "icon": "uri...",
      "color": "blue",
      "text": "Readwise highlight"
   },
   {
      "type": "photo",
      "thumbnail": "uri...",
      "full": "uri..."
   },
   {
      "type": "photo",
      "thumbnail": "uri...",
      "full": "uri..."
   },
   {
      "type": "photo",
      "thumbnail": "uri...",
      "full": "uri..."
   }
]

Please treat this as an example only - not a proposed solution 🙂

The benefits I see:

should be relatively cheap to implement on Diarium side
allows to show more "private data" unavailable in the internet, but sometimes relevant to diaries
opens Diarium to many more sources - ie. Garmin or whatever single person might need

My situation: having lots of photos on NAS not necessarily shot by mobile. I understand Google Photos might be implemented, but there is so many ways to store photos... And photos are so relevant to memories 😉

Diarium version: 2.17.2.0
OS + version: Windows 21H1

timo

That's a very interesting idea I have not thought about before.
Currently I however think that there would be too little users for this quite advanced feature. One would need to have the necessary development skills to set up a endpoint to feed data into Diarium. For the next updates, I am aiming to add features that are of use for a broader userbase.

RobertSpencer

timo Can I respectfully disagree with you re "Currently I however think that there would be too little users for this quite advanced feature.". I regularly see posts asking for help importing content from other services, and you rightly point out that you can't support all of them.

Having an accessible API means that third party tools can be written to do that work. Initially it will require development skills, but once it's done it can be made available to others without those skills.

If you want examples of what can potentially be done please let me know?

Bjoern

Hi Timo

I also think, that there are far more people which have the skills to integrate a REST API as you may think. Besides of that, people like us can make YouTube Tutorials which others, not so tech-savvy people can use as inspiration.

There are low code plattforms like IFTT, Zapier or N8N. If you offer a possibility that we can host a Diarium Instance with a REST Endpoint, we could make templates for integrations like Diarium to Evernote or lastfm to Diarium and share these with the community.

Regards,
Björn

timo

@Bjoern Diarium doesn't have a server-side component and doesn't run a webserver, how exactly should it offer a REST endpoint?

Bjoern

Hi timo. Thanks for your fast reply. I know that Diarium doesn't have a server component, but as the original poster wrote: "What would happen if users/developers could implement a server according to the standards defined in Diarium?

The idea is that it is up to the user to host the server (cloud, raspberry pi etc) and/or implement it."

Markafly

Where did this conversation go?