Ciro thinks this is idiotic, and that Wizards should sell all cards individually with unlimited supply and all with the same prices, especially online where there are no printing costs. But because Wizards made the silly promise never to reprint certain cards with the reserved list in 1994, they can't even correct this mistake legally! (TODO maybe, see further discussion at: www.mtggoldfish.com/articles/contract-from-below-promissory-estoppel-and-the-reserved-list). There is however one simple solution: create and promote a new no reserve list format, and let reserve list formats rot away:One interesting outcome of this would be to have card cost limited formats. Penny Dreadful puts a super low limit, on individual cards, but it would be cool to have a max cost per deck version of it.
- www.youtube.com/watch?v=wIq0NWSLAJA Magic TV - A Look at Non Reserve List Legacy by ChannelFireball (2015). Notably, they suggest the workaround of printing very slightly differently functional reprints, e.g. "Snow covered duals". Genius.
- www.reddit.com/r/magicTCG/comments/8gtoj4/no_reserve_list_legacy/
A cool thing is when they printed Garth One-Eye, which allows you to make imaginary copies of some of those restricted list cards during play. This is the type of "flirting with the rules", that Ciro Santilli admires. The introduction of online-only cards such as XXX has pushed that even further as of 2021.
This was especially insane when Ciro was young and the Internet was not very widely available in Brazil yet, and Ciro did not know how to check the values of cards on online markets, and would trade cards with older much more knowledgable teenagers, based solely on his appraisal of a card's strength! Can you imagine how many young Timmys got ripped off in this manner, trading useless one million mana spells for ultra expensive black lotuses?
Another option we could pursue would be to make governments consider TCG pack opening a form of gambling, which it obviously is:
There is however one good solution to Magic's insane cost: watch people who have nothing better to do in their lives play on YouTube.
And as Internet formats dominate more and more, if they have any brains at will they will migrate to a subscription model where you pay to play for a given period of time, and have immediate access to all cards. It could even be a tiered access, with older formats being more expensive (more bugs to fix on different cards), but you must get access to all cards of a format at once.
In order to solve conflicts, you just have to understand what commit you are trying to move where.
E.g. if from:we do:what happens step by step is first 6 is moved on top of 5:and then 7 is moved on top of the new 6:
5 master
|
4 7 my-feature HEAD
| |
3 6
|/
2
|
1git rebase master6on5 HEAD
|
5 master
|
4 7 my-feature
| |
3 6
| |
2-----------------+
|
17on5 HEAD
|
6on5
|
5 master
|
4 7 my-feature
| |
3 6
| |
2-----------------+
|
17on5 my-feature HEAD
|
6on5
|
5 master
|
4
|
3
|
2
|
1
This dude is mind blowing. Big respect.
Some of the most impressive videos are the ones in which he goes and extracts metals from minerals himself all the way.
Shame the academic system wasn't compatible with him: www.reddit.com/r/codyslab/comments/f5531p/codys_qualifications/ Maybe there were safety issues involved though.
Advanced. Not beginner friendly, very clunky.
dumps.wikimedia.org/enwiki/latest/enwiki-latest-category.sql.gz contains a list of categories. It only contains the categories and some counts, but it doesn't contain the subcategories and pages under each category, so it is a bit pointless.
The schema is listed at: www.mediawiki.org/wiki/Manual:Category_table
The SQL first defines the table:followed by a few humongous inserts:which we can see at: en.wikipedia.org/wiki/Category:Computer_storage_devices
CREATE TABLE `category` (
`cat_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`cat_title` varbinary(255) NOT NULL DEFAULT '',
`cat_pages` int(11) NOT NULL DEFAULT 0,
`cat_subcats` int(11) NOT NULL DEFAULT 0,
`cat_files` int(11) NOT NULL DEFAULT 0,
PRIMARY KEY (`cat_id`),
UNIQUE KEY `cat_title` (`cat_title`),
KEY `cat_pages` (`cat_pages`)
) ENGINE=InnoDB AUTO_INCREMENT=249228235 DEFAULT CHARSET=binary ROW_FORMAT=COMPRESSED;INSERT INTO `category` VALUES (2,'Unprintworthy_redirects',1597224,20,0),(3,'Computer_storage_devices',88,11,0)Se see that en.wikipedia.org/wiki/Category:Computer_storage_devices_by_companyso it contains only categories.
- en.wikipedia.org/wiki/Category:Computer_storage_devices is a subcategory of that category and it appears in that file.
- en.wikipedia.org/wiki/Acronis_Secure_Zone is a page of the category, and it does not appear
We can check this with:and it shows:There doesn't seem to be any interlink between the categories, only page and subcategory counts therefore.
sed -s 's/),/\n/g' enwiki-latest-category.sql | grep Computer_storage_devices(3,'Computer_storage_devices',88,11,0
(521773,'Computer_storage_devices_by_company',6,6,0 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 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.
Figure 3. Visual Studio Code extension installation.
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. 
- 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