Activity feed
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.
A discussion aiming to identify and develop Critical Rationalist terminology
Dennis suggested I create this discussion and tag @dirk-meulenbelt and @darren-wiebe.
Logan Chipkin has also suggested I get in contact with @darren-wiebe in regards to putting together a CR encyclopedia or something of the sort.
I could simply give the footer the same background color as the rest of the page.
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.
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.
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.
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.
#2793·Dennis HackethalOP, about 20 hours agoI could simply give the footer the same background color as the rest of the page.
That wouldn’t remove the gap.
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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
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.
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.
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.
#2791·Dennis HackethalOP revised about 20 hours agoIn 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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
This UI bug essentially exacerbates a wider issue: that the footer color does not match the background color of the
htmlelement, which becomes apparent with scroll inertia on the bottom of the page.
I could prevent vertical overscroll.
#2791·Dennis HackethalOP revised about 20 hours agoIn 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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
This UI bug essentially exacerbates a wider issue: that the footer color does not match the background color of the
htmlelement, which becomes apparent with scroll inertia on the bottom of the page.
I could simply give the footer the same background color as the rest of the page.
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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
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.
On 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 bar underneath the gray footer.
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 bar underneath the gray footer. I cannot reproduce the issue in Safari. The cause is unclear.
On iPad, the footer doesn’t extend all the way to the bottom of the page.
On 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 bar underneath the gray footer.
#2700·Dennis HackethalOP, 5 days agoI can still reproduce the issue by clicking on the button to collapse/expand an idea.
Fixed as of 0178828.
#2626·Dennis HackethalOP, 10 days agoChanging 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.
Done as of 765ba05.
typo
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 fist line of the body text, while it is effectively a subpage of a discussion of another name.
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.
#2768·Dennis HackethalOP, 1 day agoRight 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.
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.
#2766·Dennis HackethalOP, 1 day agoTop-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 fist line of the body text, while it is effectively a subpage of a discussion of another name.
See #2777.
While it is true that discussions don’t restrict people from posting long-form content that 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.
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.
#2768·Dennis HackethalOP, 1 day agoRight 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 that 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.