Wow I must have seriously messed up. Not only did I manage to make duplicates of my current article, but also somehow got my home webpage to crash. I surely am a bad user! At least I got my local file uploaded, not in the way I wanted though (inheritance is not working as expected from the file structure. But that probably is my fault).
Also maybe some things to check (not that they are 100% bugs): 1) When viewing parent/children articles sometimes the dropdown menu doesn't work when clicked (the upside down triangle). 2) Why not just delete articles instead of unlisting them? Isn't it bad for the server's storage?
I feel kind of bad for all the requests that I am making, I should preview my stuff before committing it.
My new article seemed awesome when I previewed it via the index.html file but when I uploaded it (with --web) the inheritance was broken. Maybe that's because the article already existed and I tried to push it again! Yes, that makes sense.
Yes, give it a try and let me know if you face any issues. I want both to be amazing, but perhaps cli is a bit better now for those who can use it. Give the Visual Code Extension a try.
Thanks for all the tips. I will start using the cli version, it seems much more comfortable, at least for me
Oh that was really fast. I checked a few minutes ago and I though I was crazy. Nice work
Thank you so much for reporting this.
Dollar signs: by default dollar signs are for mathematics as in:
I like $\sqrt{1+1}$ as a number.
which renders as:
I like as a number.
To have a literal dollar you have to escape it with a backslash as in:
I have \$10 for lunch.
which renders as:
I have $10 for lunch.
The equals sign space: = would generate a header, but you can't create headers directly on the web editor. You should instead create new sections by just creating new articles with the New button. Then you set the parent to the other article as shown at: www.youtube.com/watch?v=yQRjLyqILl0 Note that the UI changed slightly from that older video, the parent selection is now under the "metadata" tab in the editor.
If you find any other issues or have any doubts do let me know and I'll try to fix/reply ASAP. This serious editor bug was there because I use mostly local editing, but I want the editor to work perfectly as well.
I think their focus moved more and more to automatic data collection as opposed to UGC.
Golden was of interest, thanks for mentioning it. It also had much less strict notability guidelines than wikipedia which is another serious issue with the platform. Unfortunately they shutdown signup got merged into another financial intellicence thing: Section "Golden (wiki, 2019)".
It's almost certain that there are remaining XSSes though given I wrote the markup from scratch. But you'll have to work harder than that.
This page is not the top Google hit for "bawuzzzz". I love it so much.
blanket#1#1 by liga (@liga, 0) on 2024-05-02
<script>alert("This doesn't work right?")</script>
And yes, academia is broken beyond belief, like the rest of education.
But a PhD with the intention of doing something cool next not necessarily in academia like working in a research department or trying to create a startup is not so bad I'd say. But you have to find a good one of course.
I agree you should do something because it is cool. It's just that to me something can only be cool if "it is fucking revolutionary". Though perhaps OurBigBook is a notable counter example lol
And glad to hear that my posts helped :-)

Pinned article: ourbigbook/introduction-to-the-ourbigbook-project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact