- always upvote questions you care about, to increase the probability that they will get answered
- never upvote other people's answers unless you might gain from it somehow, otherwise you are just giving other high reputation users more reputation relative to you
- only mark something to close or as a duplicate if it will bring you some advantage, because closing things creates enemies, especially if the OP has a high profileOne example advantage is if you have already answered the question (and the duplicate as well in case of duplicates), because this will prevent competitors from adding new better answers to overtake you.
- protect questions you've answered whenever someone with less than 10 reputation answers it with a bad answer, to prevent other good contributors from coming along and beating you
- when you find a duplicate pool answer every question with similar answers.Alter each answer slightly to avoid the idiotic duplicate answer detector.If one of the question closes, it is not too bad, as it continues netting you to upvotes, and prevents new answers from coming in.
- follow on Twitter/RSS someone who comments on the top features of new software releases. E.g. for Git, follow GitHub on Twitter, C++ on Reddit. Then run back to any question which has a new answer.
- always upvote the question when you answer it:
- the more upvotes, more likely people are to click it.
- the OP is more likely to see your answer and feel good and upvote you
- if a niche question only has few answers and you come with a good one, upvote the existing ones by other high profile users.This may lead to them upvoting or liking you.
- always upvote comments that favor you:
- "I like this answer!" on your answers
- "also look at that question" when you have answered that question
- if you answer a question by newbie without 15 reputation, find their other questions if any and upvote them, so that the OP can upvote your answer in addition to just accepting
- if a question has 50 million answers and you answer it (often due to a new feature), make a comment on the question pointing to your answer
- if you get a downvote, always leave a comment asking why. It is not because you care about their useless opinion, but because other readers might see the comment, feel sorry for you, and upvote.
- ask any questions under a separate anonymous accounts. Because:
- intelligent people are born knowing, and don't ever ask any questions, so that would hurt your reputation
- downvoting questions does not take 1 reputation away from the downvoter, and so it greatly opens the door for your opponents to downvote you without any cost.
Stack overflow allows deleting content/making it visible only to 10k rep users.
Ciro Santilli is strictly against this, and this is an intended core policy of OurBigBook.com.
If you delete people's content randomly, they will be much less likely to write anything.
Getting downvoted to oblivion is one thing, but data loss? Unacceptable.
Only illegal content must ever be deleted. Or extremely obvious spam. But anything in a gray area should never be removed.
Deletion can be done by either:
- votes of high reputation users
- moderators
- or worse of all, which happens often on the smaller websites: auto-deletion because come content has not received enough views/votes above some treshold! stackoverflow.com/help/auto-deleted-questions. The most illogical thing of all is that the question is not even permanently removed from the system, only hidden from other/low reputation users! So it does not save any disk space at all! Mind blowing!
- archive.org/post/1055220/how-to-query-for-all-the-websites-that-end-in-combr
- archive.org/details/WebArchiveDomainFiles only a random list with per-ccTLDs upon request of (paid presumably) partners. As of 2023 only contains the Netherlands: archive.org/details/Dotnl-2016-present-domains-in-wayback-domainyear-of-last-capture
This is Ciro Santilli's name for the idea that we should not have structured degrees at university that require entry exams, only tests that anybondy could take, likely for free, and then they would just have proof that they know the stuff for e.g. teachers that care about a subject while selecting students to work with them in research.
We just need control rooms where someone can watch students for cheating. Multiple different exams can be taken in the same room of course, students just have to sign up in advance. The exams should happen regularly depending on demand. E.g. extremelly common subjects should happen every month, and highly specialized ones every 6 months or 1 year.
Questions should be always taken from an open question pool which also contains answers, thus allowing anyone to effectively study for it.
We then make an API available, so that students can grant access to specific results to anyone they choose, or even make the results public for anyone to see. This way the people that care about the exams can just machine learn what exams correlate with their desired performance.
Bibliography:
This is the most extreme and final form of peer tutoring, it's natural final consequence given the Internet Age.
Sample usage by Andy Matuschak (possible coiner): notes.andymatuschak.org/About_these_notes
x.com/Birdyword/status/1777591446612193667Singaporean taxi drivers are the cutest.
A while ago a Singaporean taxi driver asked me what a UK hawker centre lunch might cost. I explained that there aren't any. He asked what office workers ate, and I explained the concept of Meal deals. And he looked at me with such a powerful combination of pity and revulsion.
Pinned article: 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!
Intro to OurBigBook
. Source. We have two killer features:
- 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-calculusArticles 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/derivativeVideo 2. OurBigBook Web topics demo. Source. - 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.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 3. Visual Studio Code extension installation.
Figure 4. Visual Studio Code extension tree navigation.
Figure 5. Web editor. 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.Video 4. OurBigBook Visual Studio Code extension editing and navigation demo. Source. 
- Infinitely deep tables of contents:
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