|
This site [help.openstreetmap.org] keeps suggesting to visit community.openstreetmap.org as well. When I try to look at that, "discourse" only keeps griping about my browser [which is recent and there's little or nothing wrong with it] and I can't see any way to either search or log in over there. In the browser error console, it throws some garbage like
which should not be a show-stopping error. Jeez, c'mon. Generic Firefox on Linux, figure it out already. So, two questions: What is the RIGHT place to ask questions these days? Here or "community" ? Why did OSM pick such a crippled platform to base "community" around, where it's evidently so picky about exact user-agent headers that it refuses to gracefully fall back to a working configuration and deliver basic functionality? _H*
showing 5 of 7
show 2 more comments
|
|
Quoting from here - "(Discourse's) official browser support policy is the latest version of Firefox, Chrome, Safari and Edge". You would therefore appear to be out of luck. If you want to use Discourse, I would suggest that you either (a) upgrade or (b) persuade Discourse (not OSM) to change that policy. ** FWIW I'm also running "generic Firefox on Linux" and this Browser says it's currently 115.0.2. ** OSM has taken the entirely sensible approach to not change the Discourse implementation at c.osm.org from the standard where it can be avoided. |
What version of Firefox is it?
FF 91 ESR, fairly recent which works with everything else I throw it at and should be supported for a long time to come. My useragent header may be slightly different from stock, but that should never matter to a correctly designed site.
Did Discourse do something screwy with javascript like what broke iD a while back? Or are they being deliberately obstructionist?
Do other Discourse sites such as https://meta.discourse.org/ work? If not, it sounds like something you'd want to report upstream.
Same results, but then I changed my useragent to fake "firefox 99" and then it looked more normal. That's pretty short-sighted on their part, but I'll try to poke their support if they even have any.
I can't understand why OSM is even suggesting that people use that mess, let alone migrate to that if that's the intent of the red message bar at the top of this help site. What's wrong with this mechanism right here? There are WAY too many different places to attempt to get help with OSM, it's confusing AF, and adding yet another one just makes things worse.
Given what I've seen I'd frankly rather not use Discourse, because this help forum seems to have been perfectly adequate for a long time and there's no reason to move to a broken platform because someone thinks it's all new and shiny. C'mon, people. Think bigger please. By splitting a help forum into two or three different and mutually exclusive pieces, you're losing audience and confusing those who have no idea all these different things exist.
[I say "two or three" because it's not just this and Discourse, I had to go all the way to Github to get my last problem actually noticed and fixed. Super-frustrating.]
That's OK; it's not compulsory! That said, OSQA (which is the software that this forum uses) is unsupported and has to be dragged kicking and screaming onto new platforms as OSM upgrades servers. The long-term plan is for c.osm.org to replace this site, but it's not at feature parity yet.
FYI Firefox 91 ESR has been unsupported for nearly a year (source).
On debian "oldstable" (with security updates) I get FF 102 ESR, which works with Discourse.