openbenches.org VS REST-API-Node

Very nice! Reminds me of OpenBenches: https://openbenches.org/

You've missed one 'airports' in the footer: 'This page lists pianos that have been confirmed to be in airports around the world.'

Thought about branching out into train station organs? https://en.wikipedia.org/wiki/London_Bridge_station_organ?us...

There's some recent good news about this in a GitHub issue: https://github.com/openbenches/openbenches.org/issues/232

I love going on https://openbenches.org It is a map you can zoom in on that shows you memorial benches in the UK in their location and what’s written on the plaque.

You should upload that to http://openbenches.org

I’m more amazed that their source OpenBenches exists.

> OpenStreetMap has a list of (nearly) every bench in the world – but they don’t record whether there is an inscription on it. We tried to send a Freedom of Information request to Westminster Council for a list of their benches – but they don’t keep that information. […] So now it is time to crowd-source the data!

https://openbenches.org/

Wait till you see https://openbenches.org/

This one goes without saying. However, many repositories did have steps to running locally, and a list of the requirements. For example, this repository lists the environments to run the application locally.

I'm not sure what happened here with this repository at all. I understand sometimes it's difficult to maintain a repository, and I'm alright with that, but please do not merge PRs without testing the implementation or noting that full implementation of the issue was not done.

At first, I was assigned to the issue where I need to check the user authentication before allowing them to create a comment. However when I started working on it, I realized that this issue is related to an unsolved issue. As a result, I decided to communicate with the maintainer and move to another issue in the project.