create 0016-internal-like-system

[RubenSmn]

ADR on an Intern Like system

Did some brainstorming with @dadiorchen about the current way of giving a like, resulting in this document

Shortcut to goto the markdown page: https://github.com/RubenSmn/treetracker-decisions/blob/main/0016-intern-like-system.md

[dadiorchen]

Some background, on the web map we are going to add a like button on trees, currently, we are using FB like button, but it has some limitation, and we don't have the data of that, for example: top liked tree on treetracker.
So another idea is to build our own like button. and also to consider if a generic like button is also useful for admin panel, and android/ios treetracker app?
Please give some input @sebastiangaertner @nmcharlton @Elforama

[nmcharlton]

Should be "internal" rather than "intern".

[nmcharlton]

If we don't link "likes" to a user account, the user experience may be confusing. A user returning to a previously "liked" tree may see no record that they liked it, causing them to do so again.

[dadiorchen]

I'm also worried about this, but there might be some trade-off way to identify the user, by collecting some fingerprint based on browser agent or so? or use cookie, locale storage

[nmcharlton]

Option #2 – Internal Like system linked with Keycloak user authentication system

[nmcharlton]

The need to log in before liking/saving an entity is a very common pattern, so would be expected by most users. The "like" button is a great way to ease users into creating an account/wallet with Greenstand.

We can show the like button, then prompt to log in when the user clicks it.

[dadiorchen]

I also prefer the keycloak/SSO solution

[dadiorchen]

@RubenSmn should we change the status of this PR to something indicating that we have made the decision? I think now we all agree with option 2, right?

Status: proposed
Input: Welcome from anyone!
Deciders: {list everyone involved in the decision using github handle}
Date: 2022-09-09

[sebastiangaertner]

Agree