Veritula – Meta
Discuss Veritula itself. For feedback and suggestions.
Log in or sign up to participate in this discussion.
With an account, you can revise, criticize, and comment on ideas, and submit new ideas.When all I change during a revision is the criticism flag, the activity log just says ‘no changes’.
As of 9702c05, a revision activity now says that the idea was either marked or unmarked as a criticism.
Hi all! This platform looks like such an awesome idea!
This discussion says, "Discuss Veritula itself. For feedback and suggestions."
I wanted to ask about how many members are here. And whether it's encouraged to invite more people, in order to add more and more conversations.
Should probably show the explanation in a revision, when given. In the activity feed, that is.
Should I give the icons in the activity feed colors?
The activity feed just shows top-level criticisms as regular ideas. They should be shown as criticisms just like when they are child ideas.
When a comment is a criticism on another criticism, the activity should say ‘So and so addressed criticism #…’
In activity feed, behind timestamp (‘… hours ago’), link to corresponding discussion.
There should be user profiles.
Since the diff processes the text as a single line, the hunk header is always going to say either @@ -0,0 +1 @@ (for the first version) or @@ -1 +1 @@ (for every subsequent version). Meaning the header provides no real information. So I might as well remove it.
Done as of 8d3eed0, see eg the version history of #414.
There’s a bug where hovering over a link in the markdown preview removes the form and all typed text. Hovering over a link should have no effect on the form.
Now that there are user profiles (#408), the search page can have an option to filter ideas by user. That way, we can see that user’s uncontroversial ideas, meaning ideas of his that he can rationally hold, and controversial ones, meaning ideas of his that he cannot rationally hold.
Then people could occasionally check the search page for ideas they think they can rationally hold but actually can’t. And then they can work on addressing criticisms. A kind of ‘mental housekeeping’ to ensure they never accidentally accept problematic ideas as true.
Diffs should omit unchanged lines. Maybe just leave up to three lines around changed content for context – that’s how git does it.
Done as of cc8e3e9. It now says ‘x unchanged lines collapsed’. See eg this activity.
Now that diffs are formatted, they don’t omit unchanged lines anymore.
Fixed as of 76299a2, see eg https://veritula.com/ideas/3951-done-as-of-cc1ab95-ruby-example-ruby-def/revisions/2. (Click on “Expand unchanged parts”.)
Would be neat linking to a specific activity.
Each activity should have a distinct HTML title. The browser history and search results in search engines all look the same…
There’s a bug where right-clicking in a form to paste text doesn’t result in the preview updating.
Dirk Meulenbelt says the concept of revising someone else’s idea is not intuitive.
The following commits should address this:
3af3966Clarify in title that someone revised an idea (rather than originated idea)The HTML title now says ‘Idea x revised by…’
6c70ceaUnderneath idea, indicate that someone revised an idea (rather than submitted it)It says ‘Dennis Hackethal, 1 day ago’ for new ideas, ‘Dennis Hackethal revised 1 day ago’ for revisions
d20d386Explain that users can revise each others’ ideasAs part of the alert on the revision page, when the user is about to revise someone else’s idea.
c5748e3Turn ‘revise’ link into ‘revise their idea’ when it’s someone else’s ideaUnderneath each idea.
e0fbd41List user under each revision in version historySo that each version is clearly attributed to the corresponding user.
06d3241List contributors at top of version historyComma-separated list to see all contributors at a glance. Eg see here
Tom Nassis asks (#448):
I wanted to ask about how many members are here.
Currently 7.
And whether it's encouraged to invite more people, in order to add more and more conversations.
Yes.
The more ideas there are in a discussion, the further the form for top-level ideas is pushed down. Then people don’t know how to submit a new idea and comment on an existing one instead, even if it’s unrelated, as happened with #448. So I need to make this clearer.
Done as of 4922b8c. The form now sticks to the bottom of the discussion page.
The way IG solves this is by rendering the form in a fixed position. It’s still on the bottom but always remains visible.
Reddit is a bit different because they have multiple subreddits/communities, but each community has top-level posts which people can then comment on. They have a completely separate page/UI for top-level posts. And then directly underneath a top-level post, there’s a textarea saying “Join the conversation”.
Any progress on this? Scrolling to the bottom to submit new ideas is annoying.
Yes, see here: https://veritula.com/discussions/veritula-meta
Give it a shot.
Sorry, I was debugging something and temporarily disabled this feature. Should be back up.
It might make sense to have the new top-level idea form at the top, in the meantime. Compared to the current design, this would invite the creation of more top-level ideas.
There could be a floating button on the side that takes you to the bottom of the page.
There could be a side pane that stays visible while scrolling content.
Now that there are notifications, people should be able to @mention each other.
Mostly done, apart from some polishing, as of 5f5c545. Eg @dennis-hackethal*.
If it’s mostly done, what’s missing?
The feature wasn’t quite polished. For example, arrow navigation through the dropdown menu was missing. And there were some bugs. But it’s polished now and the bugs should be fixed as of 4ced719.
I'm still getting a feel for this platform. I'm wondering whether it would help promote wider and deeper engagement if Veritula was organized in terms of problems and their solutions. So instead of discussions, discussion trees, and broad topics such as 'Abortion', users would articulate problems and their solutions. Of course, the problem itself could be criticized as well as its proposed solutions. This approach might also make Veritula even more Popperian. All life is problem solving as Popper says.
As I recall, previous iterations of Veritula had explicit designations such as ‘problem’ and ‘solution’ but I decided against continuing those designations. It’s been years but I think it was too rigid and felt too much like ‘red tape’. It’s easier when the only check box in this regard is a boolean for ‘criticism’.
Can’t discussions already map onto the structure you suggest?
Discussion title: problem
Top-level ideas in the discussion: proposed solutions
Nested ideas: criticisms, counter-criticisms, and further solutions
Note also that revisions act as solutions to problems. So do counter-criticisms, in a way.
So I think people can already use Veritula in the way you suggest.
They can also use it like this:
Discussion title: some topic (such as ‘abortion’)
Top-level ideas: problems
Nested ideas: solutions, criticisms and so on
Makes sense to me.
'Discussions' is a much broader term than 'problems and their solutions.'
So I can see how that would allow for greater freedom.
I can also imagine some of the challenges presented in prior iterations of Veritula, if it had more of a 'problems and their solutions' structure.
Perhaps some of this theory of problem-solving just shared can make it into 'How Does Veritula Work?'
Yes, I do think discussions can map onto the structure I suggest.
So, no worries. I was wondering whether the 'Discussion Titles' can draw in current and future users in a more frictionless manner with problem statements.
But if it was tried before, why try it again? Thanks.
You marked this as a criticism but it sounds like you’re agreeing with me.
Perhaps some of this theory of problem-solving just shared can make it into 'How Does Veritula Work?'
Done, see #510.
I was wondering whether the 'Discussion Titles' can draw in current and future users in a more frictionless manner with problem statements.
I think you’re right, that would be best.
You suggest replacing discussion trees:
[I]nstead of […] discussion trees […] users would articulate problems and their solutions.
But then you also write:
Of course, the problem itself could be criticized as well as its proposed solutions.
Which means you’d still have trees regardless. So that sounds like a contradiction.
To be clear, I'm not opposed to 'trees' in general.
I was wondering whether 'discussion trees' can be replaced with 'problems-and-their-solutions trees' (for lack of a better phrasing).
Veritula should have a section with a list of all its current members.
For now, people just have profiles.
But having a list of members would build a sense of rapport between the participants.
And would promote a greater flow of communication.
[H]aving a list of members would build a sense of rapport between the participants.
Just so you know, although I’ve implemented the list of members, I do want to be clear that Veritula is not meant for socializing.
I know what you mean, but Veritula unavoidably facilitates public (i.e. social) interactions, no? Of a certain kind, to be clear. Ideas, ideas, ideas.
Well, discussions are necessarily a ‘social’ activity in that they involve at least two people, yes. I just don’t want Veritula to be yet another social network.
In a mixed society, people can prioritize truth seeking or fitting in but not both.
Workaround: have users email me for password reset for now. Re-evaluate when I have enough users to merit additional infrastructure for sending emails.
I should revisit this now that I have email infrastructure in place.
See #595. The form for new ideas is pushed to the very bottom of the discussion page. For long discussion, that means users won’t know where to submit new ideas.
Newly added comments keep animating when hidden and then unhidden.
All emails have unsubscribe links, but people shouldn’t be able to unsubscribe from system emails like password resets.
Friendly IDs for discussions would be nice. With automatic redirects for numeric ID from legacy links.
Include (preview of) content in idea URLs: '/ideas/123-first-30-or-so-chars-of-idea-here'.
That would make idea URLs more meaningful, but there’s something simple and beautiful about the shorter URLs that only have the numeric ID.
Could have backwards compatibility for the short version and continue using the hashtag in the UI. Best of both worlds?
That would mean fetching an idea to compute the path for each hashtag. Overhead?
Seems like minor overhead. It’s not like there are tons of user-generated hashtags everywhere.
This actually helps to prevent rendering links with IDs that don’t point to any existing idea.
Fetching the idea is not necessary if the feature is backwards compatible. Can still just use /ideas/123.
As noted in #1777, fetching the idea actually helps. Well worth the overhead.
Having features to both collapse an idea and hide all its comments seems like an opportunity for unification. Why not just go with collapsing and remove the ability to hide all comments?
Because that would mean hiding each comment individually if you ever do want to hide all comments of an idea.
Sometimes you just want to hide the comments without collapsing the parent idea.
Cycling through the revisions of a leaf reveals its gutter, which should be hidden since it’s a leaf.
Make sure cycling between a leaf revision with children and a leaf revision without children properly toggles the gutter.
Feature to collapse all criticized ideas of a discussion? Useful for todo lists.
Or each discussion could have a search/filter form to filter ideas not just by criticized or not but also content and potentially other attributes.
Or the existing search page could be filtered by discussion. For example, I could link to that page with an additional query param discussion_id=1 or something like that.
When you revise an idea to address a criticism, its author should get a notification so they get a chance to verify that the revision really does address the criticism.
For example, I had to manually notify Edwin in #1811 of a revision I had made to address a criticism of his. Without this notification, he might miss the revision. If he disagrees that the revision addresses his criticism, that’s a potential error that might not get corrected.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G/|\P1 P2 P3\|/I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show. That page should also scroll the target idea into view in case its preceded by too much context that would otherwise push it below the viewport.
This feature would also allow me to remove the buggy ‘context’ feature.
The red ‘Criticized’ label shows how many pending criticisms an idea has. For example ‘Criticized (5)’ means the idea has five pending criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify pending criticisms.
There should be an easy way to filter comments of a given idea down to only pending criticisms.
As of 8e0a6e1, comments on each idea are shown in the following order: criticisms first, regular comments last. Within each category, uncontroversial comments are shown first. Lastly, comments are sorted by creation date (ascending).
Once this idea is implemented, the ‘Show activity’ button on bounties#show can link to the implementation.
Could simply sort comments by pending criticism first, creation date second. (Variation of #4274.)
The red ‘Criticized’ label could be a link leading to a filtered version of ideas#show.
The red ‘Criticized’ label could be clickable and filter the displayed comments ‘in place’.
That would probably be stretching the capabilities of Stimulus…
There could be a separate button to filter comments down.
Should I be showing the comment form by default on ideas#show?
To avoid scrolling past content, I could remove the autofocus on the textarea unless a certain query parameter is given.
Having implemented this, a problem has surfaced: when linking to an old version of an idea, the alert “You’re about to comment on an old version of this idea. Are you sure …” shows. That’s jarring if you didn’t want to comment but merely look at the idea.
The ‘Revise…’ button is hidden when the comment form is open. It makes sense to hide it because it doesn’t belong in that context. But once hidden, the user has no quick way to revise an idea. Maybe the first thing they want to do after opening ideas#show is not comment but revise.
As of acb14e3, the revision button is an icon button that lives next to the collapse icon button.
Therefore, the button doesn’t need to be hidden anymore.
That would mean the revise button would be at the top of the idea. But presumably, people would typically want to revise an idea after they finish reading it. Meaning after they reach the bottom.
It could go both ways. Someone may have already read an idea and just wants to revise it, in which case having to scroll to the bottom is cumbersome.
Add hover effects to schemed buttons so there’s consistency with the existing hover effects for links.
https://veritula.com/activities/1808
Since the discussions starts with an idea, there should be a reply button.
Bug: when clicking the link to the activity in #1953, the idea is replaced with “Content missing”.
The displayed criticism count for a filtered parent can differ from the number of displayed criticisms.
For all ideas, the total number of pending criticisms (if any) should always be shown, even if they are not all being rendered. For filtered parents, I could put an asterisk behind the count. On hover, explain that some pending criticisms may be hidden due to filtering.
Any filtered idea should always display only the count of shown criticisms.
As with #2098, implementing an accurate count of the number of shown criticisms gets very tricky once the user starts submitting new criticisms on filtered parents.
That could mislead people into thinking a revision has no pending criticisms, which would be bad for error correction.
The instructions at the top of the page are clear that not all ideas are being rendered.
People could easily miss or forget that.
For filtered parents, I could put an asterisk behind the count. On hover, explain that the total number of pending criticisms may be greater on the unfiltered view.
Any filtered ideas should show a criticism label displaying n / m for the count, where n is the number of rendered criticisms and m is the number of total criticisms.
An explanation could accompany the n / m display, like a title on hover.
That way, there should never be any confusion as to a mismatch between the total vs rendered number of pending criticisms.
In addition, when looking at a deeply nested idea on ideas#show and submitting a criticism on a parent, I need to make sure the updated badges take into account that newly submitted criticism, even though the new criticism would not show after refreshing the page.
I have this working to the point that it shows n / m, but getting the counter to update properly when new criticisms are posted on filtered parents is surprisingly difficult – so difficult the juice may not be worth the squeeze.
For any filtered parent, the criticism badge could be shown without a count.
I could get rid of the count everywhere, even on unfiltered views. That would have the added benefit that users wouldn’t prefer one problematic idea over another just because it has fewer pending criticisms.
Still, the count is valuable in that it shows how many criticisms need to be addressed to restore an idea.
By the time someone receives an email notification, they will probably have forgotten whatever they wrote originally that prompted someone to reply to them.
Fixed as of recently. Emails now quote the parent idea.
Veritula should have some way to acknowledge an idea, including a way to show that a thread is resolved, at least for the time being, without having to comment.
Emoji reactions (#2159) are implemented as of ea482fb.
How about emoji reactions?
People could wrongly think they have epistemological relevance. For example, they might adopt an idea that has pending criticism just because it got positive reactions.
The red “Criticized” label is far more prominent than reactions would be.
In a way, reactions might have epistemological relevance.
If an idea has pending criticisms, it can still have parts worth saving in a revision. Reactions based on paragraphs (#2458) could point out those parts.
Reactions could be limited to the recipient of a comment.
That limits the scope of the problem but doesn’t eliminate it. A single recipient could still react in a distracting way.
There’s value in others being able to react as well. Maybe an idea affects them in some way or they want to voice support.
There could be an explanation somewhere stating that emoji reactions do not have epistemological relevance.
Hardly anyone reads those, and many of those who do forget.
Reactions can be ambiguous. It wouldn’t always be clear which part of an idea someone is reacting to.
I can speculate ahead of time, but I might implement reactions and find that this is not an issue after all. And if it is, I can either retire the feature or improve it.
That only happens if people submit bulk ideas, and people shouldn’t do that anyway.
But not everyone will always use the platform in an ideal way, and I don’t want to make it easier for issues to compound.
I could implement reactions on a per-paragraph basis.
Then what does somebody do who wants to react to an idea as a whole? Do they react to the last paragraph?
The way I picture it, as you hover over different paragraphs, a reaction button appears and moves between paragraphs. So it would always be clear that reactions are on specific paragraphs. The user would pick whatever paragraph they most wish to react to.
But this doesn’t address the scenario where someone wants to react to no particular paragraph but the idea as a whole.
Too complicated/ambitious for a first implementation. Start piecemeal. But could be a promising approach if reactions to ideas as a whole end up being ambiguous (#2166).
It isn’t clear what would happen during a revision. A paragraph might be changed or deleted. Too complicated.
But presumably, the same is true for reactions to ideas as a whole. Reactions would have to be removed for revisions.
For reactions to paragraphs, at least you could tell if the content someone reacted to has changed, and only then remove the reaction.
Why should reacts persist through revisions?
Those run the risk of turning Veritula into yet another social network like Reddit or messenger like Telegram.
This is speculation, see #4106. If it really becomes an issue, I can retire the feature or improve it.
Not if I do reactions on a per-paragraph basis. I think that’s a new feature none of those sites have.
I plan to go piecemeal by starting with reactions to ideas as a whole, then maybe to paragraphs/block-level elements down the line.
The purpose of the reaction would be to record a kind of agreement or acknowledgment.
That way, Veritula could show unacknowledged criticisms to users. So in addition to revising or counter-criticizing, they get a chance to acknowledge a criticism without having to comment.
Posting arbitrary emojis doesn’t achieve that purpose.
Posting arbitrary emojis doesn’t achieve that purpose.
Maybe it does. Any kind of reaction is a response that turns a criticism from unacknowledged to acknowledged.
I like the acknowledged/unacknowledged idea.
Doesn’t need to be arbitrary emojis, it could just be a handful that you choose, each being a different flavour of acknowledgement.
Thumbs up,
Thinking emoji,
Mind-blown emoji,
Etc.
Edit: X spaces are an example of a limited set of emojis working well.
I think the reason the limited set works well in X spaces is that there’s no text input. So there’s no way to sidestep the restriction.
For Veritula, it would be more like an emoji restriction on tweets. That wouldn’t work because you couldn’t stop people from posting arbitrary emojis in tweets by just typing them with their keyboards.
Edit: …
Pointing out changes is discouraged. Version history and diffing take care of that for you.
This is a good idea.
I often receive criticisms that I have no counter-criticisms for, and it would be nice to be able to acknowledge those, both as a way to display gratitude, and as a way to indicate that I think something is tentatively settled.
The Effective Altruism forum has an interesting way to react to posts.
There’s an ‘Agree’ button and a ‘Disagree’ button. Those are apparently anonymous. Then separately, there’s a button to ‘Add a reaction’ of either ‘Heart’, ‘Helpful’, ‘Insightful’, ‘Changed my mind’, or ‘Made me laugh’. And those are apparently not anonymous.
I wonder why they chose to make some reactions anonymous but not others. I don’t think I’d want a ‘Heart’ or ‘Made me laugh’ button, they seem too social-network-y. Also, ‘Heart’ seems like a duplicate of ‘Agree’. But ‘Insightful’ and ‘Changed my mind’ seem epistemologically relevant. Maybe ‘Helpful’, too.
If I did decide to go with ‘Agree’ and ‘Disagree’ buttons, I wouldn’t make them anonymous, though.
This seems both complicated and restrictive. People could easily sidestep the restriction anyway: nothing stops someone from leaving a comment with only a single emoji in it.
Revisions are complicated. Too many options (superseding a previous version, ‘Is criticism?’, unchecking comments). It might help to have a more guided processes over multiple screens.
Done as of 90bfadf1. The revision process is now divided over four guided steps with explanations.
I started a discussion earlier, and what I wrote in the “about” section of the discussion was not written well. I would like to revise it. Is this possible? If not, is there an intention to make this possible eventually?
I went ahead and implemented this feature since it was a good suggestion.
You can edit your discussion here.
When I revise a criticism, I can’t see what it criticises. The edit screen should show the parent idea, similar to when I write a new criticism.
Valid. As of c310cbb, the most recent parent is shown above the idea you’re editing.
Feature idea: pay people to criticize an idea.
You start a ‘bounty’ of an arbitrary amount (min. USD 5), which is prorated among eligible critics after some deadline.
There could then be a page for bounties at /bounties. And a page listing a user’s bounties at /:username/bounties.
When starting a bounty, the user writes terms for the kinds of criticism they want. This way, they avoid having to pay people pointing out typos or other unwanted criticisms.
Anyone can start a bounty on any idea. There can only be one bounty per idea at a time.
To ensure a criticism is worthy of the bounty, the initiator gets a grace period of 24 hours at the end to review pending criticisms. Inaction automatically awards the bounty to all pending criticisms at the end of the grace period.
This has been implemented, sans page at /:username/bounties, which seems unnecessary.
Need to address the risk of the initiator himself being a bad actor who rejects pending criticisms for arbitrary reasons just to avoid paying.
There could be an additional grace period for admins to review the initiator’s selections.
People who feel cheated can reach out to admins to report bad bounty initiators. Admins can then prevent such initiators from starting more bounties in the future.
A modification of #2513 could work. Say you start a bounty. Your card is authorized for twice the ceiling. If you’re a good citizen, you’ll be charged the ceiling, at most. But if you’re found to submit arbitrary criticisms to avoid paying, your card is charged the full authorization. Admins can even decide to stop the bounty early if they detect abuse before the grace period beings.
I can roll out the feature to a few trusted users. Then I can reevaluate later with more experience to judge actual risks rather than speculate ahead of time.
Need to address the risk of people submitting arbitrary counter-criticisms just before the deadline to exclude competing criticisms from the bounty.
The grace period for the initiator unfortunately does not address this risk since he may decide not to review problematic criticisms.
See #3452. Other critics have an incentive to report abuse. People found to abuse deadlines could become ineligible for payouts and excluded from participating in future bounties.
Been trying a slight modification of bounties in prod for a couple of weeks or so. Working well so far.
@dirk-meulenbelt recently offered to chip in for a bounty I want to run. That got me thinking: multiple people should be able to fund bounties.
This is now a feature, see the ‘Funding’ section of a bounty.
Need ‘standing’ bounties: they don’t expire. I keep finding myself wanting a standing bounty for #3069 so I don’t have to re-run expiring bounties.
Done, mostly as of 346fb25, then polished in 6dbf721, 5381525, 9f0f936, and 91e6f27.
Could this feature be unified with #2669 somehow?
Feature idea: private discussions only the creator and invited people can see. This could be a paid feature; $2 per discussion, say.
What happens if you add a user to a private discussion, they submit a bunch of ideas, and then you remove them?
There could be hard cutoff: they lose access to everything, including their own ideas in that discussion.
But that sucks. Maybe someone works hard and submits a bunch of ideas only to lose access to them all.
This functionality is pretty standard across apps. You can be removed from Discord servers, Telegram channels, etc without warning or reason at any time. People generally know and accept this. If they still put in effort, that’s on them.
But then invitees might not put as much effort into those discussions.
That depends on a bunch of factors, including their relationship with the discussion owner, into which Veritula has no visibility.
What if they still have subscriptions or bookmarks in that discussion?
If the discussion owner accidentally removes someone and then adds them back right away, it sucks if all the associated records are still gone.
In later implementations, I could maybe implement a ‘soft’ delete or grace period. Or I could keep the associated records and rely on authorization rules to prevent access. But as of right now, that’s a premature consideration.
They could keep access to their own ideas but not see others’.
There’d probably be a bunch of edge cases with this approach. For example, others would still be able to comment on those ideas, and the comments would have to be hidden from OPs. Which begs the question of how that impacts the displayed criticism count… And so on.
They could keep read-only access to the discussion but can’t add new ideas or change existing ideas.
Maybe you remove them because you don’t even want them to be able to see anything.
Permanent access: once added, you can’t remove them.
If you later realize that adding someone was a mistake, you should be able to correct that mistake.
How would you notify participants of changes to the privacy setting?
The activity feed already shows updates to discussions. Could just include changes to the privacy setting there. And, whenever the privacy setting does change, notify participants of the change.
This is done as of 9b5788c but it’s still free for now. Will make it a paid feature after some more testing and polishing.
Feature idea: selecting some text, then hitting ‘Comment’, automatically pastes a quote of the selected text into the textarea, Telegram style, with the proper Markdown formatting.
Bug: tooltips sometimes don’t disappear. They should disappear when the user stops hovering over the element that triggered the tooltip.
I can still reproduce the issue by clicking on the button to collapse/expand an idea.
Discussions are getting slower to render as they grow. It’s a rendering issue (not a db issue).
I could use ActionController::Live to stream top-level ideas to the page one by one. Instant page load.
Including that module significantly slows down hot reloads on all pages. I need a tight feedback loop in dev.
Replacing a raw SQL query in Idea.tree with a standard ActiveRecord query solves this issue.
Fast UX is more important than fast developer experience.
A slow developer experience will slow down all further development, including bug fixes and feature rollouts, which hurts UX as well.
After resetting my working directory and beginning to implement streams a second time, I can no longer reproduce this issue, despite reasonable attempts to reproduce it.
I’ve since been able to reproduce the issue after all. Running a raw SQL query in Idea.tree in combination with the inclusion of the Live module seems to mess with Rails’s reloader.
Incompatible with Devise authentication: https://github.com/heartcombo/devise/issues/2332
I could extract discussions#show into a new, separate StreamController or something like it. That controller would not use Devise.
The thread suggests a workaround: use authenticated do … blocks in routes.rb instead of before_action :authenticate_user! in controllers.
It’s probably a good idea to do this anyway to avoid divulging the existence of routes that unauthenticated users don’t need to know exist. (They will get a 404 instead of a 401.)
Then again, I’d want to redirect users to the sign-in page (and then ideally back to where they were trying to go).
I could override authenticate_user! in the DiscussionsController.
That means duplicate functionality; anytime I customize Devise in the future, I’ll have to remember to adjust this one method as well.
JS modules are always deferred and unusable until the page is fully loaded. As a result, comment buttons and gutters won’t work while ideas are still streaming onto the page.
I now purposely prevent interactions with buttons and gutters, and gray them out, until the page is fully loaded. So instead of broken hover effects and interactions, the user gets intentionally disabled elements, and this intentionality is communicated to them.
Once the page is fully loaded, buttons and gutters are enabled and visually restored.
Since the browser’s loading indicator remains visible until then, this behavior shouldn’t violate user expectation.
Now that parts of the page are purposely and visually disabled (see #2694), users may not expect everything to be working 100% during a loading state.
This problem will surface rarely – users would have to hit cmd + f immediately upon opening the page. For most users, by the time they start typing, the page is already fully loaded. So this seems like a small price to pay in exchange for discussion pages that always render faster.
This page used to take ~3.5 seconds to load. Now it renders within 600ms :)
I could cache ideas so deeply nested trees can be rendered at once.
Cache invalidation for user-based caching sounds like a nightmare.
A single new idea somewhere down the tree could invalidate the cache and slow things down again.
I could lazy load ideas: only load the parts of the page that would be visible on the current viewport. Then load more parts as the user scrolls.
Complex, requires non-trivial scroll listeners correlated to deeply nested ideas.
On initial page load, I could just load the first ten or so top-level ideas and their immediate children, just to reduce wait times and populate the page. Then load the rest asynchronously.
I could have a separate route at /ideas/:id/isolated which renders only the idea without any parents or children. And then a discussion could render a bunch of deeply nested turbo frames loading that route.
For large discussions, wouldn’t that flood the server with requests?
The top level ideas could be rendered as turbo frames of ideas#show.
Too many requests when there are enough top-level ideas.
I just tried this. Seemed promising at first but sometimes ideas load out of order. Looks horrible.
I could render the first ~10 top-level ideas immediately and only render the rest as turbo frames off screen. By the time the user scrolls down, they should all be loaded.
Automatically generated ideas are polluting the search page.
As of 2d3d38f, system-generated ideas are excluded from search results. They can be included again by checking a new checkmark in the form.
Would be nice highlighting strings matching the query in search results.
Feature idea: page at /ideas/:id/guide which shows you an idea and helps you address all pending criticisms one by one, if any. At the end, it shows a message ‘You’re all set!’ or something like that.
Done, live now. Every idea with pending criticisms has “Rehabilitate” under it, which opens that idea’s guide, and “Guide” in the navbar goes through all of yours, starting with the ideas closest to being adoptable. Either way, it’s one pending criticism at a time: you can criticize it, revise the idea, move on, or skip. Moving on is the abandoning from #4089: it sets the idea aside for you alone, and the idea comes back if it gets new criticisms.
Maybe there could be some type of guide for a user’s ideas generally. It takes him through all of his controversial ideas and let’s him either counter-criticize pending criticisms or revise his ideas, one at a time. And maybe the user could also choose to ‘abandon’ a controversial idea, in which case the guide would not show the idea again (unless maybe there was some new activity on the idea?).
On the search page, there should be a button to clear the query input.
Changing the query on the search page moves the cursor to the start of the query input. It should move to the end or, ideally, keep its position.
In Brave for iPad, the footer doesn’t extend all the way to the bottom of the page. As a result, in dark mode, there’s a black gap underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear; seems to be a Brave quirk.
This UI bug essentially exacerbates a wider issue: that the footer color does not match the background color of the html element, which becomes apparent with scroll inertia on the bottom of the page.
6623c22 implements #2802 and there is no difference in background between footer and page body anymore.
Maybe I’ll figure out the Brave quirk more generally someday, but it’s not noticeably anymore.
I could simply give the footer the same background color as the rest of the page. There’s a discrepancy between light and dark mode anyway. And on horizontal overscroll, the difference in background is painful.
That wouldn’t remove the gap.
I could prevent vertical overscroll.
When copying a box quote from Veritula, the box quote formatting (>) is lost.
When you copy text for an inline quote, you wouldn’t want the box-quote formatting.
There’s a way to get what you want: if you select some text in an idea before hitting its criticize or comment button, the selected text should always be inserted as a box quote.
Archiving this criticism for now, but if you’re still seeing any issues, let me know and I’ll take another look.
To be clear, if you copy the entire box quote and paste it into a textarea, it will start with the > sign. I just double checked.
You’re saying you’d still want the > if you only copy/pasted part of the box quote, right?
To be clear, if you copy the entire box quote and paste it into a textarea, it will start with the > sign. I just double checked.
This doesn't work for me the way it does for you. I tried copying the entire quote, and also in a separate attempt, copying extra stuff above and below the box quote, and neither gave me the > sign.
I have tried on my windows computer and my iPad.
… copying extra stuff above and below the box quote, and neither gave me the > sign.
Cannot reproduce, neither on iPad nor macOS.
I tried copying the entire quote…
Cannot reproduce. If I triple-click a word in a box quote, then copy/paste, I get the > sign.
Ah, but I can reproduce when I manually make the selection by clicking and dragging to cover the entire quote (and only the quote, nothing above or below).
‘Veritula’ is a difficult name, people don’t know how to spell or pronounce it. They can’t easily remember it.
'Veritula' is not a difficult name as compared to other highly successful explanatory enterprises, like 'Veritasium.'
See also: "Kurzgesagt – In a Nutshell", the highly successful educational YT channel. I know people who are big fans, and yet can't pronounce the name correctly.
There's something to be said for a degree of complexity and novelty to a name. It lends air of thoughtfulness, and could spark curiosity in potential new users.
Idea: ‘The Second Renaissance’, ‘2nd Renaissance’, ‘2R’ for short.
‘Renaissance’ isn’t exactly easy to spell either.
Easier than ‘Veritula’, though. At least it’s a known word.
Idea: ‘Return to Reason’, ‘RR’
Idea: ‘Reason Arena’, ‘RA’
I like something with ‘Arena’ because it would imply action, some ideas winning out over others, and has a Darwinian aspect to it. Our best ideas are the tentative champions in the arena of ideas, waiting for the next challenger.
I have largely inexplicit criticisms of the word ‘arena’ in this context, but one that bubbled up to the explicit level is that the word reminds me of Pokemon for some reason 😅
Doesn’t sound as serious/legitimate as I’d like in this context.
Feature idea: pay people to address criticisms (either revise an idea and check off criticisms or counter-criticize).
Yes, people could just start bounties on criticisms.
Old ideas can pollute discussions. Like in this meta thread.
Proposed solution: allow people to archive ideas. Maybe only their own.
Proposed solution: ideas with pending criticisms could be archived automatically if they haven’t had any activity in the past 30 days, say.
Proposed solution: edit a discussion to hide top-level ideas. That way, discussion owners can hide ideas they no longer deem relevant.
For example, completed tasks in discussions used as issue trackers, like this Meta thread, could be hidden so they don’t pollute the thread.
There could be a button for users to reveal hidden ideas so nothing is lost or hidden dishonestly. And direct links to hidden ideas would continue to work.
This requires manual action. Could mean a lot of work depending on the discussion.
There could be periodic reminders and a review board to make it easier.
That could just annoy people and cause them to unsubscribe from emails.
Autofocus should put the cursor at the end of an input, not the beginning.
Done for the search input as of 765ba05. It makes sense for that input because the user expects to be able to keep typing after submitting the form. For other inputs, the user will expect whatever default their browser implements.
Search page is getting slower the more ideas there are in the db.
https://veritula.com/ideas?q=&nature=uncontroversial is down from 2988ms to 476. Growing db should now have marginal effect, if any.
Idea: Activity feed should track when you last visited it, take you there when you open it. Currently, someone like me who likes to see everything happening on Veritula needs to go back through pages to find the last thing they saw.
That’s what notifications are for. You’d want to hit the bell icon for each discussion and at the top of the page listing all discussions. Then you’ll be notified of every activity on existing discussions, and of new discussions. The notification page keeps track of read vs unread notifications.
As the site grows and there is more activity, there would be too much going on for any user to be interested in all the activity on the site, so it would eventually become irrelevant
The site isn’t at all big enough for this to matter yet.
It would be a waste of time to add features that don’t scale well.
This would work fine for discussion-specific or idea-specific activity feeds, even at scale.
Done as of a12ffb3, see eg https://veritula.com/discussions/veritula-meta/activities and the new link to ‘Activity’ at the top of each discussion.
Idea: Veritula Articles
Currently, Veritula is a discussion website. I believe it could one day do what Wikipedia and Grokipedia do, but better.
A step towards that would be enabling users to produce ‘articles’ or something similar.
An ‘Articles’ tab would be distinct from the ‘Discussions’ tab, featuring explanatory documents similar to encyclopedia entries, and perhaps also blogpost-like content.
Articles focus on distilling the good ideas created/discovered in the discussions that occur on Veritula.
‘Articles’ are functionally no different than top-level ideas in a discussion thread.
Top-level ideas in a discussion thread are not standalone pages.
One thing that Wikipedia does well is having a structured, high level page for each idea/subject. This enables readers to get a good sense of an idea quickly.
Right now, to get a good sense of an idea on Veritula, a user often has to study a branching discussion, which can take a lot of work depending on how the discussion played out. A discussion also emphasises things that were relevant to the disagreements that took place in the discussion, rather than distilling the most important elements of an idea into a hierarchy, regardless of disagreements that took place in getting to it (like an encyclopedia entry does).
Top-level ideas in a discussion thread are not standalone pages.
Every idea (including every top-level one) has a separate, linkable page. You can reach it by clicking the link starting with the # sign.
These are not standalone pages in the sense that a Wikipedia page is a standalone page.
Articles would have the same ‘page’ status as the discussion pages that currently exist. (Forgive my lack of technical vocabulary.)
A possible counter-factual that may or may not be relevant to the goals of Veritula: An article with title metadata ‘Boron’ would presumably be much more search engine-friendly than a top-level ideas for Boron where the metadata title is ‘#[ID]’ and the actual desired title is merely included as the first line of the body text, while it is effectively a subpage of a discussion of another name.
As far as search engines are concerned, every idea page is already a standalone page. Not an SEO expert but I cannot imagine search engines penalize URLs containing an ID.
‘page’ status
What is a page status? How did you determine that an idea’s page status is not the same as a Wikipedia article’s?
Right now, to get a good sense of an idea on Veritula, a user often has to study a branching discussion, which can take a lot of work depending on how the discussion played out.
While this is true for most existing discussions, it’s not a fundamental limitation of discussions in general. For example, ‘How Does Veritula Work?’ has several long-form posts without much discussion. It just depends on what kinds of posts people want to submit.
See #2777.
While it is true that discussions don’t restrict people from posting long-form content like what is on the ‘How Does Veritula Work?’ discussion, that is not the intuitive function of a discussion thread. I believe the long-form content in that discussion is much more natural to an article format.
I think it is worth noting that I am much more excited to publish standalone articles than to drop top-level ideas into discussion topics.
I am not marking this as a criticism, as my personal desires in this respect may be irrelevant to the goals of Veritula.
How I find myself using Veritula at the moment is looking at the latest developing threads. Catching up on the context of that thread through clicking “Activity” is not time-effective; it reminds me of trying to catch up with a group chat full of messages. Threads naturally become messy, and not all points serve to advance the problem (some can be misunderstandings or micro-corrections). For this reason, there should be some summary that considers the following as context:
- The thread problem + metadata
- The discussion points under that thread (considering different branches) that relate to the problem.
- A prompt that aims at addressing “messiness” minimisation.
The summary should preserve substantive developments, competing answers and unresolved criticisms, while compressing resolved misunderstandings and linking back to the relevant posts.
If such a setup, including the summary, prompt and rules for what gets included, were kept open and criticiazable, we should arrive at a good system (so there should be a thread where we can iterate on ideas).
Top-level ideas need to be published to a specific discussion, which will cause some amount of silo-ing or similar dynamics.
See #2765. People can make discussions as general as they want. So there need not be any silo-ing.
Didn’t you want competing articles on some topic? In which case the same criticism applies to articles as well, unless I’m missing something.
I used to think that articles would need to be grouped in some way, but I no longer think so. Articles will often compete, even if they aren’t about the same or even similar topic.
E.g. an article ‘Easy-to-Vary Explanations’ would compete with an article ‘The Simulation Hypothesis’
Users would be able to point out and connect conflicting articles, but that wouldn’t cause them to be connected by topic, but rather by conflict.
Users may wish to publish articles that don’t neatly fit into a discussion topic.
They can start a new discussion with as wide a topic as they want.
I think so. If Veritula did implement articles, the first thing I’d want is the ability to criticize them; to submit deeply nested counter-criticisms; and to render a label showing how many pending criticisms an article has, calculated based on criticism chains. Which is just what Veritula has already.
If Veritula did implement articles, the first thing I’d want is the ability to criticize them; to submit deeply nested counter-criticisms; and to render a label showing how many pending criticisms an article has, calculated based on criticism chains.
I agree, and I think here you have inadvertently pointed at a key difference between discussions and articles. In terms of implementation, articles would be a near clone of discussions, except that the articles themselves can be criticised by users, including all the functionality that articles being criticisable may one day come with, like entire articles going dormant if they don’t answer criticisms within a certain period.
A couple of examples: If I wanted to keep and share information on Karl Popper, it would be a lot more intuitive to produce an article on him in encyclopedia style—where I can present information in a hierarchy, rather than creating a discussion and then making each detail about him a top-level idea, which is more chaotic. The same would be true if I wanted to make articles on CR terms—this doesn’t seem very natural to do in a Veritula discussion, but would be very natural in a series of Veritula articles, one for each term.
It also favours this articles idea that implementing it would be fairly straightforward, due to how much could be carried over from the discussions implementation. It makes it low cost to try.
If I wanted to keep and share information on Karl Popper, it would be a lot more intuitive to produce an article on him in encyclopedia style—where I can present information in a hierarchy, rather than creating a discussion and then making each detail about him a top-level idea, which is more chaotic.
You already don’t have to do divvy it up like that. Nothing is stopping you from creating a discussion called ‘Karl Popper’ and then posting a single, long-form, top-level idea where you present information in a hierarchy.
Since discussions themselves are criticisable, is there anything wrong with just titling a discussion 'Karl Popper' and then putting the equivalent of an encyclopedia article in the about section? That is functionally identical to what an article would be, but I am interested if you would prefer discussions not be used that way.
Since discussions themselves are criticisable…
They’re not, see #2871.
… is there anything wrong with just titling a discussion 'Karl Popper' and then putting the equivalent of an encyclopedia article in the about section?
Yes. About sections can’t be part of criticism chains.
… is there anything wrong with just titling a discussion 'Karl Popper' and then putting the equivalent of an encyclopedia article in the about section?
About sections are for context or background info, not content.
Given #2877, will this still be the case?
#2877 doesn’t mean you should put entire articles in the about section. (That’s still what top-level ideas are for.) It means that, if you’re willing to use the about section for that, then by your own logic there’s no need for this new feature.
Note: Discussions with outstanding top-level criticisms do not render a 'criticised' pill like ideas with outstanding criticisms do.
Continuing on from #2882, would it make sense to enable users to criticise the discussion/entry/topic, such that it would render a criticism pill?
If I wanted to keep and share information on Karl Popper, it would be a lot more intuitive to produce an article on him in encyclopedia style—where I can present information in a hierarchy, rather than creating a discussion and then making each detail about him a top-level idea, which is more chaotic. The same would be true if I wanted to make articles on CR terms—this doesn’t seem very natural to do in a Veritula discussion, but would be very natural in a series of Veritula articles, one for each term.
Just because something feels unintuitive or unnatural to you doesn’t mean it isn’t the right way for it to be done in the grand scheme of things.
If a goal of Veritula is for it to eventually be widely used, it should cater to at least some of what people are used to. The articles and encyclopedia formats are the most standard way for high-level information to be presented in written form, and internet users expect different kinds of content in articles vs discussions.
I just realised that it is possible to publish a top-level idea as a 'criticism' in a discussion, in the way I have advocated an article would be criticisable. I am struggling to understand what it means to criticise a discussion. @dennis-hackethal* may you please explain this?
I am struggling to understand what it means to criticise a discussion.
Top-level criticisms don’t criticize the discussion as a whole. They’re just criticisms of something. Anything. It depends on context.
For example, top-level criticisms in the Veritula – Meta discussion are often bug reports. So they’re criticisms of Veritula.
If ‘discussions’ take on a broader form, like we have discussed up to #2880, would this change? What if a user wishes to express that they take issue with something written in the entry/topic body text? I suppose they would quote it in their top-level criticism.
If ‘discussions’ take on a broader form, like we have discussed up to #2880, would this change?
Maybe. It could depend on which term Veritula adopts.
What if a user wishes to express that they take issue with something written in the entry/topic body text? I suppose they would quote it in their top-level criticism.
Yes.
Maybe about sections should themselves be criticizable… In which case they’re just regular top-level ideas. So maybe I could just remove about sections for future discussions. I’ll mull it over.
You wrote in #2856:
… is there anything wrong with just titling a discussion 'Karl Popper' and then putting the equivalent of an encyclopedia article in the about section?
If you are willing to do that, I don’t see the need for this new feature.
What you said you were after, posting ideas without starting a discussion (#2813), is possible now: you can post on your profile (#4399). And as of f27080b9, the activity feed has a Profiles tab for browsing those posts.
Archiving #2753 for now, since #2751 and #2877 still stand. If profile posts fall short of what you had in mind, leave a criticism and I’ll take a look.
Forget the term ‘article’ for a second. It sounds like you want the ability to post ideas without having to associate them with a discussion, is that right?
What if somebody wanted to post something related that isn’t a comment or criticism? Where/how would they do that?
The user could publish it as a separate independent idea, including a link to the idea they want to relate/refer to.
This is how relating discussions works currently. For instance, if I start a discussion on Bitcoin, I might want to connect it to the existing discussion on Zcash. At present, the only way to achieve this is by adding a link to the Zcash discussion within my new Bitcoin discussion.
I suspect you would agree with me that this approach to how discussions interact isn’t really an issue. I also think it wouldn’t be an issue for independently published ideas, for the same reasons.
Note: This has led me to the idea that links within Veritula could be bidirectional. Each idea could have an option to display all other ideas that refer to it. I will submit this as a top-level idea in this thread.
The user could publish it as a separate independent idea, including a link to the idea they want to relate/refer to.
Posting a sibling on an existing discussion is far easier.
I still think that Veritula already offers what you want – posting a single, top-level idea that is structured any way you like, to a new discussion whose title can be as open-ended as you like – but I’m sympathetic to your motivation.
Not every user is always interested in starting a discussion. Maybe they just want to put some information out there. And although others should still be able to discuss that information, criticism chains and all, that may not always be their primary motivation for posting the information in the first place.
So I’m open to replacing the word ‘discussion’ with a more general word. It should still communicate a sort of ‘grouping’ of ideas but need not be as narrow as ‘discussion’. Would that help?
ChatGPT suggestions:
Topic, thread, subject, space, entry, note / post / piece, context, cluster.
It’s also worth considering what each word would sound like in terms of UI elements. For example, ‘Start a new topic’, ‘Share a space’, etc.
So I’m open to replacing the word ‘discussion’ with a more general word. It should still communicate a sort of ‘grouping’ of ideas but need not be as narrow as ‘discussion’. Would that help?
Certainly. I think this makes a lot sense.
I think ‘entry’ is my favourite of the ones you mentioned (and of some others I explored with Gemini). ‘Topic’ is also alright, but seems more leading than ‘entry’. I like ‘entry’ because it seems the most agnostic to user intent, while also working fine with UI elements.
Interview published today, with one of the founders of Wikipedia:

He argues, like I do, that Wikipedia should allow multiple competing articles on each topic.
I partly agree with him on other problems he identifies, but unfortunately he doesn’t come at it from a Popperian angle.
Another idea: letting users post ideas to their own profile. Such ideas wouldn’t be part of a discussion.
Implemented as of ecc72ff. Check your profile.
Idea: Links within Veritula could be made bidirectional. While viewing an idea, users could see all the ideas that refer to it. This could be displayed as a list of backlinks at the bottom of the idea’s page.
Done as of 14003625. Each idea now has a separate page listing all the ideas that link to it. For example: https://veritula.com/ideas/5546-how-does-veritula-work-veritula-latin-for/links
The page features a ring with discussions and profiles grouping the referring ideas:

The page as a whole looks like this, listing the ideas in text form as well:

Last but not least, an idea with referring links gets a new pill badge:

Let me know if this is along the lines of what you had in mind.
One thing I haven’t decided yet: each circle in the graphic links to its idea, but it could instead link to its own page of incoming links.
This could lead to a cool knowledge graph feature down the line, where users could see how ideas might relate across discussions, and which ideas are referred to the most.
I noticed that the idea count of some discussions in the Discussions page seem to be inaccurate. In the Keeping Tidy discussion, I count 13 ideas, including revisions, while the listing for it on Discussions says it contains 17.
You forgot to count comments on older versions of ideas.
Since users are able to revise other users’ ideas, why is it standard practice on Veritula to submit trivial improvements to ideas (such as correction of typos, poor grammar and redundancies) as criticisms, rather than directly revising the idea itself? Example: #2865
Perhaps I have misunderstood the intention of enabling users to revise other people’s ideas.
There are a few reasons people might send criticisms instead of revising an idea themselves:
- You get a chance to disagree.
- Submitting a criticism is easier.
- A criticism is a written record explaining why a revision is necessary.
Because of the third reason, you may see people post a criticism and then immediately revise your idea to address it.
Maybe I’m wrong but I’m sensing a bit of frustration between the lines. Please note that Veritula pursues a higher standard of error correction than other platforms. Some criticisms may be unexpected; discussions could go in a direction you did not anticipate. You may receive criticisms that would be deemed nitpicky on other platforms, but they’re not meant to be. They may go beyond what’s strictly socially acceptable. I intend criticism to be a gift to you. For ‘small’ criticisms, it’s usually best to revise accordingly and not counter-criticize.
Your idea reads more like a question than a criticism. But since I’ve (hopefully) answered it, I’m marking this response a criticism to neutralize it.
Thank you for clarifying this. The idea of submitting a criticism and also immediately revising makes sense.
The criticisms you shared today (that inspired me to post #2884) are valid. This question came out of confusion as to how Veritula is intended to be used, rather than frustration directed at you.
I am currently unable to zoom out to the full width when accessing Veritula on mobile.
Give this another shot. Should be fixed as of 6c7e74b.
For very deeply nested discussions, you may still need to scroll sideways to see some ideas. But you should now be able to zoom out far enough to always fit any idea into the viewport.
This change is on purpose. The zoom feature was buggy. After zooming out far enough, the navbar and footer got cut off on the right. So I replaced it with proper scrolling.
Would you say zooming was indispensable or just nice to have?
It means that I have to scroll sideways to see the end of each line in a paragraph, which makes it more difficult to read ideas. It feels quite bad to use, compared to using Veritula on my computer, where the entire width of a paragraph is visible at all times.
A solution might be to adjust the mobile site dynamically to fit the user’s phone width.
‘Discussions’ are too narrow a term for a collection of ideas. See #2878.
While ideas should always be ‘discussable’, that doesn’t mean everyone who wants to share an idea always wants to start a discussion. Maybe they just want to put some information out there.
The word ‘discussion’ sets the right expectation. Veritula is built on the idea that anything you post can be criticized. ‘Entry’, ‘post’, ‘note’, etc suggest a place to put information out unchallenged. Someone who only wants to share information can already do that with a single top-level idea.
Chronicles depend on the word ‘discussion’. They retell discussions, like the one between Newton’s and Einstein’s theories.
Renaming costs a lot. URLs like /discussions/… would need redirects, and the MCP tools and the code all say ‘discussion’.
Since people can now post on their profiles, there’s arguably no need for something other than ‘discussions’ outside of profiles anymore.
Tyler recently wrote to me, in the context of a question he wanted to figure out, “would be good to Veritula this.” Cool seeing ‘Veritula’ used as a verb.
Why is similarity a bad thing in and of itself? It can be reminiscent of discussions as long as it’s less narrow.
Similarity is fine if it is less narrow, but ‘thread’ doesn’t seem any less narrow than ‘discussion’ to me. A ‘thread’ usually means a reply chain.
I have found myself using this term naturally, as in ‘starting a thread on Veritula’. I believe I’ve heard others say this, too.
I have an inexplicit criticism of this relating to “school subject”.
I can’t decide if this communicates a grouping of ideas. Seems borderline.
“Go check out the Karl Popper context on Veritula” would only make sense if you are already a Veritula user who is accustomed to using this terminology.
This actually seems anti-discussion. Sounds like a grouping of ideas that are only related by conceptual proximity, rather than building on each other.
Bug: as you cycle through a parent’s versions on ideas#show, the children are suddenly not being filtered anymore, and the highlighted idea suddenly has siblings.
Please add a ‘first, previous, next, last’ navigation thing to the top of the activity feed page and similar pages. Currently I need to scroll to the bottom to go to a different page.
Good call. I made the pagination ‘sticky’ as of 1e7a85d. Archiving this but let me know if something isn’t working right.
Need a search form per discussion.
Done as of 19009b2. Discussions now have a link to search ideas, which points to the search page with that discussion already preselected in a new discussion dropdown.
Preview links of discussions should show the name of the discussion being linked.
See eg https://x.com/agentofapollo/status/1991252721618547023
I implemented this a while back.
X caches link previews, so old previews remain the same. But new previews feature the discussion title, see eg https://www.opengraph.xyz/url/https%3A%2F%2Fveritula.com%2Fdiscussions%2Fcriticisms-of-zcash.
@dennis-hackethal* see the revision chain on #3164. Revision 5 improved the content but I accidentally removed valuable comments. Revision 6 (a revision of revision 4) brought back the comments but I failed to include the content improvement in revision 5. I then made revision 7 to have both the comments and the improved content.
Maybe it should be possible to amend which comments apply to an idea without needing to make a whole new revision. This could behave weirdly in some edge cases, but it’s food for thought. If you think the way it currently works is going to be best, that seems fine to me.
As of 212b357f, revising goes in steps, and a reply only stays behind if you mark it, with a button that says what that means (“Answered by this revision” or “No longer applies”). That should prevent what happened with #3164.
Changing which replies apply without a new revision would rewrite a version’s history, which the timeline relies on. If replies still get lost, I’d rather let a new revision bring back the ones an earlier version left out.
Archiving #3166 for now. If it happens again, leave a comment and I’ll take a look.
Obsidian autopairs markdown syntax and brackets. I like it a lot and would like Veritula to have something similar!
I haven’t used Obsidian, so I don’t understand what you are requesting. Is it that, whenever you open a bracket, you want the closing bracket to appear automatically?
I’ve asked Gemini to explain it:
1. Auto-Closure (Insertion State)
When the user inputs an opening delimiter, the system immediately injects the corresponding closing delimiter and places the caret (cursor) between them.
Input: (
Buffer State: (|)
Logic: insert(opening_char) + insert(closing_char) + move_caret(-1)
2. Type-Through (Escape State)
If the caret is positioned immediately before a closing delimiter that was autopaired, and the user types that specific closing delimiter, the system suppresses the character insertion and instead advances the caret.
Context: [text|]
Input: ]
Buffer State: [text]| (Not [text]])
Logic: if (next_char == input_char) { move_caret(+1); prevent_default(); }
3. Atomic Deletion (Regression State)
If the caret is between an empty pair of delimiters, a backspace event deletes both the opening and closing characters simultaneously, returning the buffer to the pre-insertion state.
Context: (|)
Input: Backspace
Buffer State: |
Logic: if (prev_char == open && next_char == close) { delete_range(caret-1, caret+1); }
4. Selection Wrapping (Transformation State)
If a text range is selected (highlighted) and an opening delimiter is typed, the system wraps the selection rather than replacing it.
Context: |selected_text|
Input: [[
Buffer State: [[selected_text]]
Logic: surround_selection(input_pair)
5. Markdown-Specific Heuristics
Obsidian applies context-aware logic for Markdown syntax (e.g., * or _). It often checks word boundaries to determine if the user intends to bold/italicize or use a bullet point.
Context (Start of line): | + * + Space -> Bullet list (autopair disabled/consumed by formatting).
Context (Middle of line): word | + * -> word *|* (autopair enabled for italics).
I have implemented 1-4. Give it a try. I think 5 is out of scope for now but I may revisit it at some point. If auto-closing asterisks are a problem at the start of a line (when making lists), use a hyphen instead.
I can take this opportunity to replace manual markdown with a proper text editor. Then there’s no need for autopaired brackets.
The editor will need to support:
- Automatic links to ideas like #123
- Links to @mentions like @dennis-hackethal*
- Safe link formatting
- Disabling of turbo links
- Namespaced footnotes
- Custom blockquote format
- Protection against XSS
- Retention of formatting when pasting
On second thought, implementing a proper text editor would take more work than I initially realized, and is far beyond the scope of what Benjamin is requesting anyway. I can revisit this idea later.
It would be nice if I could collapse the 'submit top-level idea' form. It currently takes up a third of my screen when I scroll on PC.
As of 9087189, the footer automatically hides and shows based on scrolling behavior.
Try it out and let me know if this doesn’t help.
Benjamin suggests making it clearer that you can use Veritula by yourself.
There’s an encoding bug affecting title previews.
Idea: voice spaces, like Twitter spaces, except an AI generates a transcript and automatically turns it into a discussion tree, with criticism chains and all.
This seems overkill for now. If people want to do this off-platform and then feed it into Veritula, they can do that.
@tyler-mills says:
I keep coming back to a graph-based presentation. Every comment a node, edges red if ending in criticisms. I crave a way to see structurally how many red criticism threads and grey comment threads are stemming from a given idea. The red ones could be bold and bright if they lead to an uncriticized idea, else dim and thin. Then we can see at a glance which ideas are sources of more criticisms, and/or hold greater opportunities for further criticism — can see which ideas are “deeper” niches, one might say (..!). Have greater evolvability…
Basically not doable for the user with the current bubble+hashtag method. But again it could just be an optional view. I think I mentioned I find that Kialo does a cool job with their sun dial diagrams (which are optional).
How would you preview text in nodes?
Tyler says:
No preview necessarily, or the first sentence upon mouse-over could work. I’m imagining a structural view independent of the main view. (Though still suggest looking at columns for each idea in the main view).
@tyler-mills says:
… I’m finding the threads a bit cumbersome to keep track of. Would love an option to have each top level idea in a column, and horizontal scrolling would be fine with me if there are many of them.
Not sure this is a good idea. You say you wouldn’t mind horizontal scrolling, but users generally dislike horizontal scroll.
Could be optional, as I said. Rearrange top-level ideas as toggled. Maybe not worth the trouble. Just spitballing. See #4825.
I agree this feature should be optional and toggleable but that doesn’t address its (potential) shortcomings. It just kinda hides them.
Not understanding this criticism. Maybe my idea is unclear. I'm picturing the existing "column" of a discussion, repeated column-wise for each top-level idea. Current discussion content takes up only the left ~third of my screen, while the right two thirds of my screen is totally unused. The cost of using that real estate is more content (clutter) on screen, the benefit is less time scrolling up and down in one dimension, looking for given ideas and getting bearings, which I sometimes find tiring. A second dimension helps get bearings (e.g. "Oh yeah, this relates to that one over here near the middle of the third column." Rather than: "That one was ... 77% of the way down the page, hmm, what were some words from it that I can use to ctrl+f, grrrrr.").
I’m saying it’s not clear to be how deeply nested comments would be shown.
If I’m understanding you correctly, you dislike having to scroll up and down in a discussion. You see empty space on the right and you think it should be filled. Hence your suggestion to put top-level ideas next to each other rather than on top of each other.
But then where do comments on each top-level idea go? Do they still go underneath? Nesting needs indentation. So that means deep nesting gets lots of indentation. So there’ll still be plenty of empty space.
Those are the kinds of things we’d need to figure out to have a mature design proposal ready for implementation.
Code blocks need syntax highlighting.
Veritula used to have this feature but I removed it when diffing changed.
Done as of 65dba4b.
Ruby example:
def criticized? ideapending_criticisms(idea).any?enddef pending_criticisms ideacriticisms(idea).filter { |c| pending_criticisms(c).none? }enddef criticisms ideachildren(idea).filter(&:criticism?)end
JS example (h/t ChatGPT):
function criticized(idea) {return pendingCriticisms(idea).length > 0;}function pendingCriticisms(idea) {return criticisms(idea).filter(c => pendingCriticisms(c).length === 0);}function criticisms(idea) {return children(idea).filter(c => c.isCriticism);}
When an idea has nothing but a code block, there’s too much of a margin at the bottom, between the block and the border of the highlight.
There’s a small issue related to previewing changes in code blocks: even when there are no changes yet, if the code overflows horizontally, the scroll shadow is shown through DOM manipulation, which in turn triggers the diffing library into thinking the user made a change.
So then the same code block is shown without any changes, under the ‘Changes’ tab, which is confusing. It should still just say ‘No changes’.
There’s an issue with horizontal scroll for overflowing code blocks in the activity feed on mobile. Can’t scroll all the way to the right.
Would be nice if the copy button was sticky-top so that it scrolled with the user.
A sticky button can't work here: the main content area has to be a horizontal scroll container so deeply nested trees can grow sideways, and that stops position: sticky from sticking. The workarounds (reworking the global layout, or JavaScript positioning that jitters on mobile) are too risky for such a small benefit.
I spoke to soon. Rolling this back for now. Too jittery when scrolling on mobile. Non-trivial to implement. Need to see how other sites do it.
The diff view can’t handle the removal/replacement of entire code blocks yet. The removed block looks broken, the new block doesn’t show at all. See activity 3207 in dev.
On mobile, there needs to be more of a padding on the right, inside the code block.
When the code overflows horizontally, a subtle inset shadow on the side shows that you can scroll:
const posts = [{id: 1, title: "Understanding JavaScript Closures in Depth", url: "https://example.com/articles/javascript-closures-deep-dive"},{id: 2, title: "A Complete Guide to Modern Web Development Practices", url: "https://example.com/articles/modern-web-dev-guide"},{id: 3, title: "Exploring the Node.js Event Loop and Async Patterns", url: "https://example.com/articles/nodejs-event-loop"}];function formatPost(post) {return `${post.id}: ${post.title} -> ${post.url}`;}function prettyPrint(posts) {return posts.map(formatPost).join(" | ");}console.log(prettyPrint(posts));
Bounties should be clear about what currency they are being paid out in.
Valid. As of 7af3c7b, the site uses ‘USD’ throughout.
Need the ability to exclude archived ideas from search results.
Composing a top-level idea on mobile is atrocious. Need to scroll all the way down to see the form, the form keeps hiding itself, etc.
Should comments be sorted by controversial/uncontroversial first, date second?
Idea: embedded discussions on third-party websites.
Option 2: an embed code is shown on your profile, with a page-url attribute you fill in. That’s the page where you place the code. The first time someone posts a comment, the associated discussion is created. Instead of a title, the discussion gets assigned the URL. That way, people seeing the discussion on V can open the URL for context.
Extend the existing Discussion model to have a nullable embed_url. An embedded discussion would not have a title.
Option 1: when you create a discussion, an embed code is shown, which you can paste anywhere.
That would mean people couldn’t programmatically use embed codes, like on their blogs. They would always have to manually go into V and create a discussion first.
Create an EmbeddedDiscussion model, separate from Discussion.
That would prevent existing discussions from being embedded on other sites. But why prevent that?
To keep things simple. This is just an MVP.
But having a separate model isn’t exactly keeping things simple either.
Veritula should have a 'Posts' tab next to the 'Discussions' tab, where people can browse the things people post on their profiles.
Done as of f27080b9, as tabs on the activity feed rather than a separate Posts tab: All, Discussions, and Profiles.
Doesn’t the ‘Search’ tab offer what you want? I could rename it to ‘Posts’. Maybe ‘Ideas’.
Search is site-wide. I have in mind a feed of what people are writing, that isn't in discussions.
I understand this might be too social-media-y for your taste, but I think it would be good to have. It doesn't need to be prominent. Discussions can remain the main focus.
I first want to see some more people posting to their profiles so there’ll be enough ideas to show in that tab.
There are more profile posts now, and f27080b9 makes it a tab instead of its own page, so fewer posts aren’t as big a deal anyway.
Also, did you know you can follow people? Click the bell icon when you visit someone’s profile.
I would like to follow you but I don't want my notifications full of bug fix stuff 😅
If there was more granularity to the follow function I would use it a lot I think.
If I mute a discussion, does that stop me from getting notifications from the people I follow, when they interact with that discussion?
If I mute a discussion, does that stop me from getting notifications from the people I follow, when they interact with that discussion?
Yes.
As a rule of thumb, specificity beats generality. For example, if you follow someone but mute a discussion, you won’t be notified of their posts in that discussion. But if you then subscribe to a specific thread in that muted discussion, you will get notifications for that thread.
There are exceptions. If you mute someone, you’ll never be notified of their actions, no matter how specific.
Bug: When I try to type a top level idea into a discussion on my phone, the text is covered by the keyboard.
Should be fixed as of 9ea99f9 but let me know if you’re still having issues.
When a reader comes to a Veritula post via a link, the site should let them know if there is a superseding revised version of it, and if they would like to see that version instead. When I share things with my friends, I want them to see the most current version, not the version that corresponds to the link they have been given at some point in the past.
Right now it depends on the user seeing that it is not the most recent revision on their own.
…the site should let [visitors] know if there is a superseding revised version of [an idea].
There are arrow buttons linking to the previous and next version, and the UI says which version you’re currently looking at.
But there’s no indication that the current version has been superseded.
I would prefer to find out I was reading an outdated version of something before I started reading it, not at the end, and not in the comments.
Outdated is different from superseded. The versions show at the top of the idea. That signals at least potential ‘supersession’ before you start reading.
A ‘supersession’ isn’t some special flag in the system – it’s just another criticism that can be countercriticized. So I hesitate to implement special functionality for ‘special’ criticisms.
Try appending /latest to the link. I still need to expose this feature somehow, but you can use that in the meantime.
Example: https://veritula.com/ideas/4421-5-minute-creativity-tl-dr-when-making-a/latest
When I go on a profile, the posts are lost amongst the other user activity.
Posts should have an exclusive place on the profile, as well as featuring in the user activity.
Done as of af4e814. There’s now a default wall tab and an activity tab. The wall only shows posts made specifically to the profile. That means posts by the user and others to that profile, and the user’s reposts from anywhere. Version chains are collapsed into the most recent version.
… the posts are lost amongst the other user activity.
To be clear, when you say “posts”, you mean specifically ideas the user posted only to their profile, outside of discussions?
What about reposts from discussions?
I think users will expect reposts to appear on their profile alongside their posts on the wall. That seems natural.
Suggestion: Allow reacts to be used in the activity feed.
That way I can quickly add colour to whatever has been happening recently on the site.
Done as of 6d4f4a70. You can now also reply to ideas directly from the activity feed.
Suggestion: Make italicised text the same colour as regular text.
Bold text is good in red. Italicised text is less legible, and the red compounds that.
This would also create more of a differentiation of emphasis between bold and italicised text.
Idea: ability to lock an idea to prevent edits. If you submit the first version, you get to lock the idea. Useful especially on your own profile that you might use as more of a blog and don’t necessarily want others changing your ideas.
Locking isn’t needed. Ideas are already immutable: other people can only add versions. The real problem was which version your profile shows. As of e3507e6f, the wall shows each post as its author last revised it, so other people’s revisions no longer speak for you there, and nobody has to be stopped from improving your ideas.
This criticism applies to #4520 as well.
Alternatively, you could make an option "allow revisions by other users" in the new idea form that is off by default.
Need rate limiting for new users to prevent excessive posting.
Someone who recently joined made a bunch of low-quality posts in a short amount of time.
The UI needs to be more minimalistic. Too many buttons to click on. Needs clear primary action on every screen.
As of today’s deploy, ideas show far fewer buttons. The edit, repost, react, subscribe and menu buttons in an idea’s header stay hidden until you hover over the idea. The same goes for the React button in the activity feed and on profiles. Comment and Criticize are plain text rather than gray boxes. So while you read, those two are the only actions you see. Whether an idea is a criticism now shows in its header, not in a pill under the text.
A discussion needs to be more skimmable via one or both of these:
1. hide long posts behind "read more" button
2. collapse critique chains/threads behind a "reply more" button
Both done, as of 3945f28a and 82b641de. Long ideas now show cut short, with a Read more button that expands them in place. Discussions open with settled branches collapsed: the replies to comments and to addressed criticisms sit behind a plus on their gutter line. Pending criticisms, which decide whether an idea can be adopted, stay open. In most browsers, Cmd+F still finds text in collapsed branches and opens them.
It would be nice to have a changelog as i cannot see the commit history (ex. of one of an app i built https://understandtutor.com/changelog)
https://veritula.com/discussions/veritula-meta/activities
It’s not quite the same but should give you an idea.
Need time indicators again, for when an idea was posted, like we used to have. But shorter: something like ‘1h’
Thoughts on an optional "implies" relation for ideas? I find myself commenting on one idea something which it implies, then criticizing that, but the original idea is not marked criticized. Being able to chain or bundle ideas avoids the bookkeeping issue of having to make new criticisms for each step in the chain, if one is criticized.
An ‘implies’ relation would build the implication into the site’s structure, where nobody could criticize it. But whether A implies B should be open to criticism like any other claim. Instead, criticize A directly: ‘A implies B, and C refutes B.’ That criticism stays pending until someone disputes the implication or answers C.
When it’s your own idea, I recommend adding implications to the idea itself, as part of a revision. That way, criticism chains stay intact.
Related to this or not, it could be useful to be able to set a bounty on a set of ideas, rather than just one. "Criticize any of these ideas for n$".
You can already fund a bounty on each idea, and a bounty covering several would mean reworking how bounties are paid, shown and won.
I’m archiving #4824 for now, but if you have a case where separate bounties fall short, feel free to reply with a criticism and it’ll be unarchived automatically.
Reiterating/refining #3904: There should be a graphical indication for pending criticisms. The dropdown line should be red if the comment it leads to is a pending criticism. The yellow pills can be turned gray to be easier on the eyes.
The quote
indentation bar
is red, which would cause visual confusion.
It should be made not red. Gray. Arguable even without the red criticism line idea above, since it already conflicts with the "red = criticism" motif.
Currently, a single gray "thread" comes off an idea, and splits off into sub-ideas. A single criticism in the above scheme would turn the whole thread red, which is ambiguous.
The main thread is ambiguous currently, by that reasoning: it's always gray. Having the whole thing red to indicate one or more pending criticisms below seems useful, and cool. And the offshoots from the main thread (the little curly part leading to each sub-idea) can have the new colors.
E.g.: User scrolls down the main bright red thread, past gray comment offshoots and dim red refuted criticism offshoots, until reaching the bright red pending criticisms offshoot that is the cause of the main thread being bright red. (!)
Bounties could pay out multiplicatively, up to a limit (e.g. 10$ per criticism, up to 3). This would preserve the incentive for bounty hunting after one criticism has already been posted.
Maybe I’m misunderstanding you, but that’s how standing bounties work already.
When you fund a standing bounty, you set the number of criticisms you’re willing to pay for, and the amount for each.
If that’s something you want to do for your current bounty, you still can, before current funding runs out.
See also “How Do Bounties Work?”
Yeah, I'm not sure why I wrote this... I remember the option for number of criticisms now. I guess it slipped my mind.
The "Battle tested" badge should have a hyphen!
https://www.merriam-webster.com/dictionary/battle-tested
This may be too subjective, but I've always really disliked end-of-line hyphenation, of the kind currently used here. I find it pretty disruptive to the flow of reading, AND a source of visual clutter. That's a heavy cost for the supposed benefit of a justified margin, but we don't seem to be getting that benefit here either; the margin still appears jagged. A justified margin itself is unnecessary, if you ask me, but it can in any case be accomplished the other way, where small spaces are distributed between words in each line as needed. To me the latter method of the two is better for readability, no contest. I would advocate for the third/default method, here (jagged margin, no funny business), since justified margins seems needlessly formal.
My profile shows my revision to #5126 under Wall and under Activity, but not the post itself under the Wall. The revision is a jumble of red and green highlighted text (in this case, because the revision was significant), hard to read. Wall should only show latest versions of posts, not edits to them. Edits should go under Activity. And/or have the previous post versions viewable with the little arrows, as usual (and as done in the idea-focused view, after you click on the idea itself). Always show latest versions of ideas on the Wall so it's clear and easy to read.
Fixed as of 1a588356. Check your profile:
No way to delete posts. Posted same thing twice by mistake (unexpected Chrome behavior). Choices are to leave the duplicate, which seems inelegant, or to revise it into another whole post, which I did, but that contributed to the issue in #5143 (creates an unclear green and red update post).
Deleting posts can really mess up the continuity of discussions, and allow for dishonesty.
Okay to allow for posts that have no comments or criticisms? Or only for posts on one's profile (perhaps also meeting that criterion)?
It can still mess up the continuity of discussions when the post to be deleted has parents.
Another choice: criticize one for being a duplicate. In the criticism, link to the original and instruct people to ignore the duplicate.
Another problem with letting people delete posts is that others may have written a comment in the meantime, which they then can’t submit.
I’m open to letting people contact me for serious cases (like accidentally posting their password or credit-card details). And then I can delete that content manually in the database.
Aside from that, we’d need to identify a case where simply criticizing a post isn’t enough. The criticism can state the reasons one would otherwise have for deleting a post.
Discussions have an ‘Archive’ button for top-level posts. It looks like a box you’d put on a shelf in an archive.
Top-level profile posts could have such a button, too. And I could add an ‘Archived’ tab.
Would that help you achieve what you’re looking for?
I don't think so; just having a Wall of posts on my profile is fine, no funny business. Here I was only hoping to delete an accidental mis-post. Maybe allowing deletion of exact duplicates with no parents is reasonable? But this is just a cleanliness/organizational thing, and kind of a fluke, probably not an issue worth spending much time on. (But I stand by #5143, and regardless of the size of the revision. Seems cleaner to me to only show the latest version, no diff.)
Maybe allowing deletion of exact duplicates with no parents is reasonable?
Too niche/specific for an extra feature tbh. If accidental duplicates happened often, then maybe.
I question whether previous versions of a criticism should contribute to the battle-tested count, as they do currently. Someone can make a spelling correction to the criticism, which creates the "supersedes" criticism of that previous version of the criticism, and that then contributes to the battle-tested count. This seems wrong, since that counter-criticism is not substantive, and even if it were, OP only generally responds to the latest version of a criticism (may not even have known about previous versions; all of this happened in: https://veritula.com/ideas/5089-knowledge-growth-such-as-in-genes-in-the-biospher).
But sometimes revisions can be substantive, and OP could defend against one version, and in that case it should count toward the battle-tested badge!
Yep. Was going to say this, too. The system has no semantic way to check the content of a criticism. So it has to assume that every unaddressed criticism is substantive.
But the system does have a way to identify automatically generated criticisms.
It does, but it has no universal way to semantically check why a criticism was generated this way. All it knows is that the criticism was generated as part of a superseding revision, but it doesn’t know the meaning of the contents of that revision.
… OP only generally responds to the latest version of a criticism …
I’m not sure that’s generally true. But regardless, OP should address all pending versions of a criticism.
Ben found a UI bug:

The text shouldn’t wrap after “trust”.
I’ve experimentally turned off pretty text wrapping in paragraphs. I’ll give it some time to see how ideas look around the site now. If they look worse on the whole (orphans etc), I can always undo fd699cd.
It’s because of text-wrap: pretty;
Chromium renders it properly. Desktop and mobile Safari doesn’t.
Idea: showing the quickest way to rehabilitate an idea.
Could be a visual feature showing something like the shortest path down a discussion tree where a criticism needs to be addressed.
Or all such branches.
Such a thing has probably been done in graph theory before, could look for existing algorithms.
Each reply answers one idea, so addressing an idea’s pending criticisms directly is always the quickest way to rehabilitate it: one new criticism for each. Going further down the tree never takes fewer, so there’s no shorter path to show. What helps is going through them one at a time, which the guide now does (#2628).
Offer easy way to link to latest version of an idea. The ability already exists – an idea link + /latest will always go to the latest version – but isn’t directly exposed in the form of a link or button yet.
Tyler suggested (#3904) we use the chart type from Kialo:

Could be a useful visualization in addition to trees.
Each top-level idea would be the center node, with its replies in segments around it. They’d be colored like the visual tree’s discs: the idea blue, criticisms red, and comments gray, solid if rationally adoptable and hollow if not.
Unlike Kialo, though, segments with the same parent would all be the same size: they’d split their parent’s arc equally between them.
#6063 doesn’t say what the chart would show that the visual tree doesn’t. Since #3904, the tree has come to do what Tyler asked for there: every reply is a node, criticisms are red, and edges to pending criticisms light up, so you can see at a glance which threads are still open. Without a problem the tree leaves unsolved, there’s no way to tell whether the chart is worth building or how it should look.
@tyler-mills I’ll leave it to you to see if this chart type would give V anything the tree doesn’t. Archiving this idea for now.