OpenStreetMap

Community.osm.org - how's it going?

Posted by SomeoneElse on 25 March 2023 in English. Last updated on 28 March 2023.

The new forum “community.osm.org” has been going for a while now, so maybe it’s useful to have a look at how things are going.

There’s obviously lots that goes into creating that forum as a site where people can share ideas - there’s the forum software itself, and the people looking after the technical administration of the site, the migration of the old forum (which has just happened) and the help site (planned for later), the various implementation decisions that got us to here, and also the people looking after content moderation (which is more actively managed than before). Of all of these, this diary entry is really only about the Discourse software itself.

I’ll not comment here about the future migration of https://help.openstreetmap.org/ to Discourse and the work required within Discourse to support that, since it would be unfair to judge something that has not happened yet.

Full disclosure - I’m one of the moderators of a couple of categories in the forum, but this is very much a personal view.

What’s good:

The software is actively maintained, unlike the old FluxBB forum software, or OSQA, which is used for the help site.

It’s working! Some communities that might have been a bit quiet or spread over private forums are now able to talk together much easier than before.

Searching works, with some caveats around the UI (see below for that). This may sound obvious, but mailing lists search at for example talk-gb can be a bit of a pain to use - a page such as this only shows the subject and the name of the poster, not the date of the message.

You can avoid “me too” answers (but see “reaction icons” below).

There’s a translate button on every post that supports the most common languages. This reduces the “echo chamber” effect that some forums had previously (and some other OSM channels still do now).

For browsing and reading, most things work on mobile. Initial login is slow, but it works (usually, eventually). It’s certainly better than OSQA which is not at all easy to use on mobile and needs a lot of zooming in and zooming out.

The barrier to entry is much lower than e.g. Telegram. If you have an OSM account, you can log in. You don’t need to e.g. provide a mobile phone number to a third party that you do not necessarily trust.

You can do most things by email (with caveats). See here and here. Email threading was nonexistent in received emails before a recent Discourse upgrade, but this has now been fixed.

You can automatically upload pictures without needing a separate hosting site (unlike, say, mailing lists).

You can use tags as “virtual categories” and post using them. It’s a bit complicated, and new users are never going to figure it out on their own, but it does have the potential to be a useful feature. This is a virtual “United Kingdom” category below “general” and this is a virtual Garmin one.

What’s bad:

The Site layout is poor. https://community.openstreetmap.org/ shows a couple of massive icons, some verbiage and half a dozen links (three on mobile). The remaining 40-odd forums (where most people hang out) are “below the fold” and in no particular order. See also here for more about that.

The forum structure is quite limited, although this may be an implementation decision. Replying by email can cause issues with quoting - depending on the email client, sometimes all of the previous messages is quoted again.

Composing messages on mobile (Firefox) is challenging.

The moderation approach is somewhat restricted by the tools available. When something is reported various messages and numbers are shown but it is not at all clear (except from experience) what applies to the person doing the reporting and what to the person reported. Also, some moderators have complained that they can’t do what they expect to be able to (i.e. not what they were able to do on the old forum).

I know that computer systems tend not to be, but it does seem to be random in places. What one user sees does not match what another user sees.

Pages are slow to load. A 4-second load time (even on a mobile phone) over a fast Internet connection in 2023 is simply ridiculous. See here for more.

It sounds basic, but it’s not possible to see who a reply was to. This is particularly a problem by email, where persons A, B and C reply. If C replies to B there’s nothing (even on the web UI) to indicate that. If B’s reply to A wasn’t visible by email (perhaps because of a local email filter) then it looks like C is replying to A. I mostly work around this by, where relevant, always quoting a bit of message to reply to - that way it’s obvious. See also here and here.

Although searching mostly works, the UI around searching is pretty “user hostile”. To see this, go here and press ^f (normally an in-page browser search) and that keypress is intercepted by Discourse and you are shown “find in topic” instead, which “simply doesn’t find” lots of text. Try searching for “persistent and stable” and it’ll say “no results found” Then browse to here and scroll up a bit, and you can see that that text exists. You can click on it to see the posts, but you can’t search for it. You can press ^F twice and search within page, but because Discourse doesn’t send the whole page to the browser, that search does not work from the top of the page - it’s well into “chocolate teapot” territory. See also here.

The back button does not work.

Users find minimum post length annoying.

The reaction icons are very limited - high on emotion, low on feedback. There is no “vote down” option, which will be essential for “help” migration. There is also no “that’s a really useful comment but I don’t agree with all of it”.

What’s just ugly:

The documentation is piss-poor. See also here for another example of functionality that appears to have been designed under the influence of recreational pharmaceuticals. There’s an about link (which says who the admins and moderators are) and an FAQ (which seems primarily concerned with etiquette guidelines). There is Discourse’s searchable “meta” site (which is good, but you are only going to look for it if you know that such a thing is likely to exist).

The best documentation we have seems to be this which is an introduction to Discourse for OSMers by OSMers. It’s written in German, but you can translate it using Discourse’s built-in translation button..

The upstream release process is a mess. Normally new versions of computer software are “released”. In mid-January a more appropriate zoo analogy would be to say that Version 3 of Discourse “escaped”.

Edit: Link to here removed as that issue is now fixed.

Edit 2: A couple of extra “good” points added - picture hosting and virtual categories.

Location: Lunyo Estate, Katabi, Virus, Entebbe City, Central Region, Uganda

Discussion

Comment from SK53 on 28 March 2023 at 14:52

I think the big advantage of the Community site is that there is more awareness of things happening in other communities and consequently better knowledge that many mapping issues are more general. Some of this is purely down to some of the poor UI/UX aspects you describe!

Comment from Firefishy on 29 March 2023 at 17:57

I completed big tidy of some of the old forum imported categories today. Tagged the topics as relevant and then merged them into existing categories eg: Category: General Tag: Garmin.

Comment from Firefishy on 29 March 2023 at 17:59

The 4 second page load time is a difficult one. I cannot replicate it. Google report Good “Core web vitals” for 99%+ of the site for both Mobile and Desktop. There might be some edge case, but I am not seeing it.

Comment from SomeoneElse on 31 March 2023 at 00:04

@Firefishy - Re “virtual categories” I added them into the “good” part of the list just before your comment, but as an example, “Garmin” is still a bit hidden. Search for the text on https://community.openstreetmap.org/ and you won’t find it. Typing it into the search box finds 6 items - one is a tag (but it does not say that it is a tag) and 5 are users (but it does not say that they are users).

Of course, the decision not to have a Garmin category (just a tag) is a local deployment decision, and I’ve steered clear of talking about those above to avoid muddying the waters between “Discourse the software” and “how we have deployed it”.

Comment from SomeoneElse on 31 March 2023 at 00:21

@Firefishy - Re the speed issue, I suspect that this is mostly due to just how bloated the site is. I’ve just tried a couple of times, each time in a new Firefox private window on a mobile phone.

On a Nokia 6.1, Android 9 on 3 (4G with 31 Mbps down) I got a 5 second delay before the front page https://community.osm.org loaded.

On a Nokia X10, Android 13 on O2 (4G with 26 Mbps down) I got a 3 second delay before the front page https://community.osm.org loaded.

On a PC, Windows 10 / Chrome Incognito (FTTC “broadband” with 16 Mbps down), the delay was about 2 seconds.

If there’s anything I can do to test this locally, let me know. I’ve also got a chromebook and a couple of old laptops here that might show the same issue and show what is “eating all the pies” in the site itself.

Comment from InsertUser on 2 April 2023 at 17:23

I think the “OSM-Forum auf Discourse - Tipps und Tricks für neue User” thread would benefit from being copied into the wiki somewhere where we can take advantage of a permanent machine translation in the usual (wiki) fashion rather than a translation that’s on the fly and might hit a rate limit.

Comment from Firefishy on 2 April 2023 at 19:48

I keep a close eye on the translation feature of community.osm.org. It is an important feature for our community and am happy to adjust any rate limits if they are causing any problems. I would prefer if the Tips remained where they are.

Comment from RobJN on 2 April 2023 at 21:53

Like SK53 wrote, I find that reading more about other communities (i.e. non-UK for me) are doing, is the biggest benefit of the new forum.

And a few of the negatives don’t affect me. Firstly, despite using firefox on mobile, I don’t have the issue noted here. Loading times don’t bother me, and I find the interface intuitive enough that I haven’t needed documentation. I don’t recall ever noting anything wrong with the back button either and the “below the fold” point has never bothered me. In fact I wonder how important it is these days given that scrolling on a mobile is common on pretty much everything.

So all in all, a really good new addition. I now go here as my first place and check the other forums (e.g. talk-gb’s online achieve) second / less often.

Comment from drolbr on 3 April 2023 at 07:51

It is seven seconds here, on a Gigaset GS5 mobile phone with Android 11 on Firefox in a private tab.

It is slow.

Comment from Mateusz Konieczny on 3 April 2023 at 11:54

Sometimes it takes multiple seconds to load page of text on modern laptop with 16GB RAM.

Discourse is simply incredibly slow, bloated and poorly optimized like large part of software nowadays.

Comment from Matija Nalis on 3 April 2023 at 15:25

Regarding performance problems, it might be network and/or device speed related.

If there’s anything I can do to test this locally, let me know. I’ve also got a chromebook and a couple of old laptops here that might show the same issue and show what is “eating all the pies” in the site itself.

@SomeOneElse you can press “F12” in your desktop browser and choose “Lighthouse” (for Chrome/Chromium) or “Performance/Web Developer” (for Firefox), and look (or share) the results. “First Contentful Paint” and “Time to Interactive” are good general metrics to look at. (There are lots of details to see where the problem if those are too big.)

@Firefishy: there are also web-based tools to analyze where is slowdown, e.g. https://pagespeed.web.dev/analysis/https-community-openstreetmap-org-t-performance-issues-with-discourse-3-0-8182-11/llr6v442j1?form_factor=mobile

on 3G mobile network, it says 4.5s for First Contentful Paint. There are other detailed tools like https://gtmetrix.com/ or (now requiring login, grrr - I’ve quite like it before, though) webpagetest.org

How much of that is fixable by non-discourse developers is questionable, though. But one might check if there are any low-hanging fruits.

Comment from SomeoneElse on 10 April 2023 at 09:36

I’ve saved a recording from the “performance” tab of firefox on a Chromebook to https://map.atownsend.org.uk/tmp/c.osm.org.profile.json . From me pressing return in the address bar to the page appearing took about 8 seconds.

Comment from westnordost on 11 April 2023 at 23:39

Regarding the page load times…. could it also be specific to Firefox on mobile?

I have now for some months noticed that Firefox on my mobile seems to get stuck loading a page sometimes and/or it takes really long to show. Even (I think) quite basic sites and with wifi internet connection.

When I tried the same page in Chrome, it loaded immediately. Something is wrong with my phone or something is wrong with Firefox on mobile (or maybe a plugin I am using - ublock?)

Comment from SomeoneElse on 12 April 2023 at 01:13

I’ve just tried the Nokia 6.1 with an incognito Chrome tab - 4 seconds. The Nokia X10 with Chrome, about 3 seconds. Maybe it’s slightly faster than Firefox, but 4 seconds to do anything in 2023 is just too slow. An iPhone 8 Plus of about the same vintage as the Nokia 6.1 (but obviously much more expensive new) is about 2.5 seconds.

Comment from drolbr on 12 April 2023 at 11:00

No, it is about the same on both browsers (Chrome, Firefox) on mobile as well as on the desktop (Chromium, Firefox).

BTW, in both cases the development consoles say that 1.7 MB have actually been transferred, out of a total of 7 MB. This is what kills the performance.

Comment from westnordost on 12 April 2023 at 11:13

7MB? Hm. Did anything change with the last update? Related topic in which I also measured how much is transferred on page load:

https://community.openstreetmap.org/t/performance-issues-with-discourse-3-0/8182

Comment from SomeoneElse on 21 May 2023 at 11:03

With regard to translation - pages now seem compatible with Google Translate, so for example https://translate.google.ca/?sl=en&tl=de&text=https%3A%2F%2Fcommunity.openstreetmap.org%2Ft%2Ftagging-help-for-osmose-error-untagged-named-object%2F99233%2F11&op=translate now works as is. Obviously that’s just an anonymous view of the page, so you can’t reply from there, but it’s much less clumsy to use than Discourse’s built in one-post-at-a-time-but-not-the-thread titles translation.

I’ve no idea whether this was a change at Discourse or at Google, or when (it might have been working for ages and I haven’t tried it).

Comment from SomeoneElse on 20 August 2023 at 15:00

I won’t attempt to re-edit the original diary post after so many months, but it’s worth mentioning that some of these issues have now been addressed, for example voting up and down.

Log in to leave a comment