I think the “difficulty” people experience with Discourse mostly comes from the fact that it actually has structure. There are topics, categories, and optional tags — and users feel they must pick the “right” one. Then they’re asked for system, version, OS, and other details that help others give accurate answers.
On Facebook, they don’t have to relate to anything except the exact thing they want to ask. There’s no “new topic” button, no categories, no tags, no version fields. You just write on the wall, and everyone else has to adapt to whatever you posted — not the other way around.
A structured system will never feel as easy as a structureless one when the user’s only goal is to write anything, whether it’s “help with Gramps” or “look at this cute kitten”. Facebook removes all friction by removing all structure, while Discourse asks the user to place their question in a context so the answers can be better, more accurate, and easier to find later.
This is a well‑known UX pattern: the less structure a platform has, the easier it feels for infrequent users — even if it makes the content harder to organize, search, and solve afterwards.
You see the same pattern in notebook‑style tools like OneNote, Notion, or Evernote. They feel simple and flexible precisely because they let users write completely unstructured text, with only lightweight markers like “@” or “#” for navigation. That illusion of simplicity is why so many people choose them: they can avoid making decisions about structure, categories, metadata, or relationships.
Obsidian is a different case entirely. Even though it also uses plain text, it demands far more intentional structure from the user to unlock its full potential — a potential that surpasses most family‑tree software by a wide margin. But because it falls outside what people perceive as “the standard”, many avoid it anyway. It triggers the same “this is new and I have to relate to more than just names and dates” reflex you see everywhere — a kind of structural aversion that makes users default to whatever feels simplest, even when the more powerful option is right in front of them.
We see the same pattern in Gramps: users frequently ask for simplified ways to enter data, precisely because they don’t want to actively decide what the information is or how it should be classified. The less they have to relate to structure, the more comfortable they feel, even if it means losing context, accuracy, or long‑term usability.
So the only realistic way to get users to move over to Discourse is for “superusers” to stop answering technical questions on Facebook and other places where the structureless approach dominates. As long as people get instant help in the unstructured environment, they have no incentive to use the structured one.
This lack of structure is also why so many people prefer Facebook in general. You see the same pattern in research tools: people gravitate toward OneNote, Notion, or Evernote instead of more structured systems like Zotero, simply because they don’t have to deal with metadata or categorization. And in genealogy software, many choose programs because they’re seen as “the standard”, even if 60% of their information disappears the moment they try to export it.
It’s a paradox: you can often get more long‑term value from a notebook‑style system like Obsidian than from rigid genealogy programs like RootsMagic, Gramps, or Legacy. But people still choose the systems with the fewest visible requirements, because they don’t want to deal with structure — even when structure is what actually preserves their data.
Digression: You can see this paradox here on Gramps Discourse as well.
The moment someone posts a longer, evidence‑based reply that questions the established “gold standard” and asks people to think before answering, the discussion often slows down or stops entirely.
It suddenly demands more cognitive effort than a quick, reactive comment: readers have to pause, actually read, process the argument, and respond with something more than a one‑line opinion.
That alone is often enough to break the flow in what many experience as a casual, low‑effort space.
It is the same pattern again: when a conversation demands more than surface‑level engagement, many people instinctively pull back.
We can see a similar pattern in the growing use of AI as a “research tool”.
A lot of people want to type a question and receive a finished product in return, without having to deal with sources, context, or internal consistency.
The result may have little or no connection to historical fact, but it feels good because it looks complete and costs almost no effort.
This is not even new: long before AI, people were already “buying” the simplest possible path to a prestigious ancestor – a Viking king, a French noble, or whatever sounded impressive – without doing the structured research needed to support it.
AI just automates the same temptation: it produces a plausible story without forcing anyone to build a structured method.
The keyword here – and it always will be – is what you might call structure‑phobia: the tendency to avoid anything that forces us to think about context, categories, or relationships before we can move on.
And if anyone has made it this far into the text, here is the metadata:
Methodological Note: The initial draft of this text was written in Norwegian. Microsoft Copilot was used to assist with translation into English and to refine structure, readability, and argument flow. All factual claims, interpretations, and conclusions were reviewed and validated by the author. AI assistance was used strictly as a linguistic and editorial tool.
Which, of course, is yet another example of the very paradox described above: choosing the path of least resistance to reach a finished result. I openly admit that I used a tool I don’t particularly enjoy using, simply because I did not want to sit with dictionaries and translate everything manually from Norwegian to English. In that sense, structure‑phobia strikes again – even for someone who spends a lot of time arguing against it.
And I can probably bet that this very text will end up proving its own point: most readers will drop off long before the end. The moment something becomes long, structured, and demands sustained attention, the audience collapses. Which, ironically, is the clearest possible demonstration of everything described above.