Post #1616270

2026-02-06 23:58 UTC

@BalooUriza or it will lead to the rejection of OSM. Yes, the developer is at fault, but we are not even giving them time to correct it. This has already happened when OSMF banned the default user agent flutter_map. OSMF did not promise to distribute tiles for free (especially to corporations), but sometimes this affects small tile users who do not cause a heavy load. It is understandable that when an application overloads the OSMF servers, it must be restricted immediately.

Replies (3)

@foxy@en.osm.town 2026-02-06 23:58

@BalooUriza But why not have a more softer mechanism? Imagine that if someone violates OSMF tile attribution, you could not just write an email, but show the seriousness of your intentions by blocking some tiles. Most likely, users will still be able to use the application, but the developer will fix the violation much faster.

Open ##1616271
@BalooUriza@social.tulsa.ok.us 2026-02-07 00:13

@foxy That *is* the softer mechanism. Effectively, your answer was in place before the server upgrade and it just meant OSM was straight unavailable for everyone much of the day.

Open ##1616280
@pnorman@en.osm.town 2026-02-07 01:47

@foxy We tried notifying them and giving them time to correct it. The email listed on their app store page bounced and told us to download their India-only app and submit feedback through it. We also gave months notice on flutter_map's default UA. We first blocked in September then reversed it to give apps time to change. If we have some way to contact a user we almost always will before blocking and we can work with their schedule. We just have no way to contact most problem users.

Open ##1616283