Veritula – Meta
Discussion started by Dennis Hackethal
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.Discuss Veritula itself. For feedback and suggestions.
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.
Highlight current nav item.
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), each profile can have a tab for unproblematic ideas. Among all the ideas a user has submitted, those are the ones he can rationally hold. And another tab for problematic ideas, ie ideas he has submitted that he cannot rationally hold.
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.
Would be neat linking to a specific activity.
Done as of a02e6c4, see eg this 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 (rathen 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.
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”.
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.
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.
Good idea. I’ve added this to my list of features to implement.
Done as of 6251b6a, see veritula.com/members.
[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.
Veritula deserves to scale to the size of Wikipedia.
But it never will, unless its users innovate.
How can the global success of Wikipedia inspire Veritula?
I agree that Veritula deserves to scale to something huge.
Looking through the history of Wikipedia, I see that its core concept is that of “compiling the world's knowledge in a single location […]”. To be clear, I think the core concept of Veritula is to be a programmatic implementation of Popper’s rational discussion methodology; it then becomes a dictionary for ideas as a result. It’s also less about listing facts and more about listing ideas and their logical relationship (though criticisms do provide built-in fact-checking mechanisms). That said, with enough users, Veritula could become a place with a lot of knowledge.
The linked site traces some of the success of Wikipedia to volunteers: “The use of volunteers was integral in making and maintaining Wikipedia.” So early adopters such as yourself are crucial.
In addition, 9/11 apparently played a role in making Wikipedia famous:
The September 11 attacks spurred the appearance of breaking news stories on the homepage, as well as information boxes linking related articles. At the time, approximately 100 articles related to 9/11 had been created. After the September 11 attacks, a link to the Wikipedia article on the attacks appeared on Yahoo!'s home page, resulting in a spike in traffic.
Veritula could be a place where people break news stories and others can quickly fact-check and improve upon reports by revising them. An urgent story would draw a lot of users to the site, too.
Something like Wikipedia’s arbitration process could be interesting, too.
Something similar to Wikipedia’s page-protection feature to combat “edit warring” and “prevent vandalism” could address the issue of people posting criticisms in rapid succession to protect their pet ideas.
Your suggestion to look to Wikipedia for inspiration is spot on. Thanks.
To prevent edit warring and vandalism, maybe Veritula could have a reputation system similar to that of Stack Overflow, where you need to earn enough reputation before you can edit someone else’s post, say.
Password reset is broken
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.
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?
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 outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
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…
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.
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.
Done as of b423e18.
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.
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”.
Bug: when cycling through ‘filtered’ revisions (meaning there are more revisions that don’t lead to the highlighted idea), the criticism badge can change count for the same revision.
Any filtered idea should always display only the count of shown criticisms.
For all ideas, the total number of pending criticisms (if any) should always be shown, even if they are not all being rendered.
If no criticisms are being displayed, yet the label says an idea has n pending criticisms, that might confuse people. More generally, any mismatch between rendered vs counted criticisms could confuse people.
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.