TTN Mapper - time to shut down?

jezd
Sun, 04 Jan 2026 13:28:23 +0000

Given the slightly defensive tone at times towards people who seem keen to look at taking this on, I am not sure how productive this thread is becoming.

On the one hand, this started out as a simple check on demand for TTN Mapper, yes or no, and that feels largely answered. What seems a little odd is questioning people’s reasons for using it. If someone says it is important to them, that is probably best taken at face value.

It also appears that the thread is now being used to gauge who might be willing to take on the role of owner, maintainer, and bill payer. That is understandable, but it would help if that was made a bit clearer.

For anyone genuinely considering stepping in, it would be really helpful to have a clear overview of what sits behind TTN Mapper. A straightforward backend diagram showing the services and hardware currently used, along with an outline of the monthly running costs, would give people a realistic sense of the scale involved. If the thread is also being used to help assess who might be considered worthy of taking on stewardship, then having that information available feels entirely reasonable.

Finally, it is worth remembering that most people here are technical. People will hit hurdles, just as the original authors did, but they will learn and find solutions. It is 2026, and the world has moved on quite a bit in the last twelve years — a solution today may well look very different to that from a decade ago.

I’ll be honest, I have seen a number of people more than capable and just as keen to take it on, but if there are things we are not seeing, then I say just close it down — let another solution rise from the ashes.