bool to handle potential future osm api behavior

This commit is contained in:
stopflock committed 2026-10-04 20:05:33 -05:00
1 parent 1d6cfd775f
commit a627deab51
2 files changed
+52 -19

No files matched your search

+10
View File
@@ -49,6 +49,16 @@ double topPositionWithSafeArea(double baseTop, EdgeInsets safeArea) {
return baseTop + safeArea.top;
}
// Whether to proactively check blocks/active *before* attempting to fetch
// the username during login. Current OSM behavior: user/details returns 403
// for blocked accounts, so we check blocks/active first (it's documented as
// accessible even while blocked) to detect this reliably instead of getting
// an unexplained 403. Flip to false once OSM allows user/details to succeed
// for blocked accounts too, so login can complete normally and rely on the
// regular checkActiveBlock() triggers (launch/resume/queue/test connection)
// to surface the block warning instead.
const bool kCheckBlockBeforeUsernameFetch = true;
// Client name for OSM uploads ("created_by" tag)
const String kClientName = 'DeFlock';
// Note: Version is now dynamically retrieved from VersionService