You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Logseq https://github.com/logseq/logseq no web interface/centralized server?
81
+
* Zim https://zim-wiki.org/ Local only. <WYSIWYG>.
82
+
* https://itsfoss.com/obsidian-markdown-editor[]. <Closed source>. They have an OK static website publication mechanism: https://publish.obsidian.md/ram-rachum-research/Public/Agents+aren't+objective+entities%2C+they're+a+model but leaf node view only for now, no cross source page render. They are committed to having plaintext source which is cool: https://twitter.com/kepano/status/1675626836821409792
83
+
* <Notion (productivity software)>[].
84
+
85
+
But no upvotes/topics. Favorites could be used as upvotes, but it does not seem like you can favorite other people's work. It's just not their focus, will never be.
86
+
87
+
They have an education push: https://www.notion.so/product/notion-for-education but it's likely hopeless.
88
+
Major downsides that most of those personal knowledge databases have:
89
+
* very little/no focus on public publishing, which is the primary focus of OurBigBook.com
90
+
* either limited or no multiuser features, e.g. edit protection and cross user topics
91
+
* graph based instead of tree based. For books we need a single clear ordering of a tree. Graph should come as a secondary thing through tags.
92
+
93
+
= Foam
94
+
{c}
95
+
{disambiguate=personal knowledge base}
96
+
{parent=List of personal knowledge base software}
97
+
98
+
https://github.com/foambubble/foam impressive.
99
+
100
+
<Open source> <Roam Research> clone.
101
+
102
+
Markdown based, <Visual Studio Code> based. Template project: https://github.com/foambubble/foam-template[]. Publishing possible but not mandatory focus, main focus is self notes. TODO possible or not? https://jackiexiao.github.io/foam/reference/publishing-pages/[] and if yes how. They seem to use graphs more than trees which will complicate publication. IDs seem to be correct, unscoped from files. IDs might be correctly implemented but need to confirm. A CLI tool at: https://github.com/foambubble/foam-cli[]
This is the project with the closest philosophy to <OurBigBook> that <Ciro Santilli> has ever found. It just tends to be even more idealistic than, <OurBigBook> in general, which is insane!
113
+
114
+
Source code: https://sr.ht/~jonsterling/forester[]. Not on <GitHub>, too much idealism.
Author's main social media account seems to be: https://mathstodon.xyz/@jonmsterling e.g. https://mathstodon.xyz/@jonmsterling/111359099228291730
119
+
120
+
They have `\Include` like <OurBigBook>, nice: https://www.jonmsterling.com/jms-007L.xml[], but OMG that name `\transclude{xxx-NNNN}`!!
121
+
122
+
Headers have open/close:
123
+
``
124
+
\subtree[jms-00YG]{}
125
+
``
126
+
<OurBigBook> considered this, but went with `parent=` instead finally.
127
+
128
+
Does not encourage human readable IDs, uses stuff like `jms-00YG`.
129
+
130
+
The markup doesn't seem to have any insane constructs, you have to type out open paragraphs everywhere?! OMG, too idealistic, not enough pragmatism.
131
+
132
+
Jon has some very good theory of <personal knowledge base>, rationalizing several points that <Ciro Santilli> had in his mind but hadn't fully put into words, which is quite cool.
* https://help.obsidian.md/Getting+started/Sync+your+notes+across+devices they do have a device sync mechanism
90
160
161
+
= Project Xanadu
162
+
{c}
163
+
{parent=List of personal knowledge base software}
164
+
{wiki}
165
+
166
+
Crazy overlaps with <Ciro Santilli>'s <OurBigBook Project>, Wikipedia states:
167
+
\Q[Administrators of Project Xanadu have declared it superior to the World Wide Web, with the mission statement: "Today's popular software simulates paper. The World Wide Web (another imitation of paper) trivialises our original hypertext model with one-way ever-breaking links and no management of version or contents.]
<Closed source>, no local editing? <PDF> annotation focus.
97
178
179
+
Seems like a "organize ideas for my private academic research" use case.
180
+
98
181
Co-founded by this dude: https://x.com/iamdrbenmiles
99
182
100
183
= Quartz
@@ -118,16 +201,12 @@ Everything is forcibly is scoped to files https://quartz.jzhao.xyz/features/wiki
118
201
119
202
Global table of contents based of in-disk file structure: https://quartz.jzhao.xyz/features/explorer with customizable sorting/filtering.
120
203
121
-
= Project Xanadu
204
+
= Roam Research
122
205
{c}
123
206
{parent=List of personal knowledge base software}
124
-
{wiki}
207
+
{tag=Closed source software}
125
208
126
-
Crazy overlaps with <Ciro Santilli>'s <OurBigBook Project>, Wikipedia states:
127
-
\Q[Administrators of Project Xanadu have declared it superior to the World Wide Web, with the mission statement: "Today's popular software simulates paper. The World Wide Web (another imitation of paper) trivialises our original hypertext model with one-way ever-breaking links and no management of version or contents.]
Copy file name to clipboardExpand all lines: ciro-santilli-s-hardware/bicycle.bigb
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ Log:
45
45
* https://www.trekbikes.com/gb/en_GB/equipment/cycling-components/bike-tyres/hybrid-bike-tyres/bontrager-h2-hard-case-ultimate-reflective-hybrid-tyre/p/31553 seems Schwalbe like, but will it fit?
46
46
They had a Schwalbe Marathon Plus 700x35c (non-Tour, as that one didn't fit as per previous experiment) on the shop and I went for it. They said 35c was the maximum recommended for that mudgard which is a bit of a shame, but good to know. Also getting one from Amazon to match on front as shop only had one.
47
47
48
-
2024-04: micropuncture on front tube? Could not identify during ride, refilled and was OK to get homw. Almost no pressure in middle of ride. Passed through some deep water which may have made things worse? Had a small pice of glass-like material stuck in tyre, but didn't seem to penetrate? One day and a half later, was full empty again after full fill without riding, so confirming micropuncture theory. Buying 2x Conti Tube Cross 28 (700C) presta inner tubes.
48
+
2024-04: micropuncture on front tube? Could not identify during ride, refilled and was OK to get home. Almost no pressure in middle of ride. Passed through some deep water which may have made things worse? Had a small pice of glass-like material stuck in tyre, but didn't seem to penetrate? One day and a half later, was full empty again after full fill without riding, so confirming micropuncture theory. Buying 2x Conti Tube Cross 28 (700C) presta inner tubes.
49
49
50
50
Tried to put a spare Schwalbe Men's Marathon Plus Tour 700x40C on the bike to get better stability. It seemed to fit the wheel quite well, but unfortunately failed to go well in the fork because it was too tall and hit the mudgard. Without mudgard it might work. Measured height was 6cm for Schwalbe vs 5.3cm for the stock one.
Copy file name to clipboardExpand all lines: cool-data-embedded-in-the-bitcoin-blockchain.bigb
+40-5Lines changed: 40 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,10 @@ There are a few dozen </ASCII arts> in the blockchain.
54
54
55
55
Almost all of them are copy pastes of stuff present elsewhere, or boring high resolution ones auto-generated from images. But hey, it's still fun to see.
56
56
57
+
* https://www.blockchain.com/explorer/blocks/btc/229417[block 229417] (2013-04-03) has a cute one liner sword <miner message> by <HHTT>:
* 5acc5293506c65d346d6ca171d8e8b73b39b3f99fb16a98cc7f3ce9dbe27a87c (https://www.blockchain.com/explorer/transactions/btc/5acc5293506c65d346d6ca171d8e8b73b39b3f99fb16a98cc7f3ce9dbe27a87c[2014-03-10]) goes straight to the point:
58
62
``
59
63
+----+
@@ -642,6 +646,26 @@ Almost all of them are copy pastes of stuff present elsewhere, or boring high re
* https://github.com/cirosantilli/bitcoin-inscription-indexer/blob/master/data/out/0517.txt#L202[tx fd739c26276ea81fea8210939d527fccd7c9622f93aa17d18ee0bd5321387fde], block 517406 (https://www.blockchain.com/explorer/transactions/btc/fd739c26276ea81fea8210939d527fccd7c9622f93aa17d18ee0bd5321387fde[2018-04-09]) contains the first line of an ad from American stockbroker company https://en.wikipedia.org/wiki/TD_Ameritrade[TD Ameritrade]. It is encoded one line per transaction with <OP_RETURN>, but the ordering is completely scrambled. A link is given: https://TDAmeritrade.com/Blockchain[] but it is 404 as of January 2024 of course, companies can't keep their pages up for more than 3 seconds, but there is an archive which decodes the indented picture for us, including the corresponding tx hashes for each line https://web.archive.org/web/20180902001329/https://www.tdameritrade.com/landing-pages/offer/blockchain/index.html?cid=TVTDACDDRTVJ64[], here is a copy from the website because we were lazy to double check each line:
646
670
``
647
671
.............See the full picture at TDAmeritrade.com/Blockchain................
@@ -3586,11 +3610,6 @@ Many of their messages also mention `SockThing`, which was part of their mining
3586
3610
* http://hhtt.1209k.com/sockthing.php
3587
3611
* https://github.com/fireduck64/SockThing
3588
3612
3589
-
https://www.blockchain.com/explorer/blocks/btc/229417[block 229417] (2013-04-03) has a cute sword <ASCII art>:
Starting from their very first ASCII transaction on https://www.blockchain.com/explorer/blocks/btc/197602[block 197602] (2012-09-07), there is what seems to be a poem spread across several transactions. Some of the lines are repeated, presumably because they didn't update the current line to a new line and so mined the same thing multiple times:
3595
3614
\Q[
3596
3615
I am a pretty princess\br
@@ -4111,6 +4130,15 @@ Some of the very first <ASCII art> present in the blockchain besides <BitLen> is
4111
4130
``
4112
4131
Reproduced e.g. at: https://www.textartcopy.com/ascii-middle-finger.html
4113
4132
* tx 0aab36554c2ac5ec23747e7f21f75dbe3f16739134cf44953ad7ac98927146d6 (https://www.blockchain.com/explorer/transactions/btc/0aab36554c2ac5ec23747e7f21f75dbe3f16739134cf44953ad7ac98927146d6[2014-09-28]) via <cryptograffiti.info>: naked <woman> laying on her side showing her <vagina> from under her legs, signed `fsc`. TODO full author name?
4133
+
* https://www.blockchain.com/explorer/transactions/btc/66826fccef3e3ebb34abce25bfeff8f9dcaaf88e4707a5576c494d8a1cf1681a[tx 66826fccef3e3ebb34abce25bfeff8f9dcaaf88e4707a5576c494d8a1cf1681a] (2015-12-16) has a one liner <penis> and <breasts>:
4134
+
``
4135
+
jEW B====D ( . Y . )
4136
+
``
4137
+
soon followed by more breasts at https://www.blockchain.com/explorer/transactions/btc/37c1e90c6ce3e648c51bfa38cbb43e996cd46e038517596d4c90ca2a6425a701[37c1e90c6ce3e648c51bfa38cbb43e996cd46e038517596d4c90ca2a6425a701]:
4138
+
``
4139
+
jEW ( . Y . )TIDDIES( . Y . )
4140
+
``
4141
+
Found by <Messages from the mines>.
4114
4142
4115
4143
= Mt. Gox' shutdown
4116
4144
{parent=Themes}
@@ -4315,6 +4343,8 @@ Analysis of some of them follows.
4315
4343
= Bibliography
4316
4344
{parent=Cool data embedded in the Bitcoin blockchain}
4317
4345
4346
+
Other Bitcon analysis:
4347
+
4318
4348
Analyses in other blockchains:
4319
4349
* <Ethereum>
4320
4350
* https://reidjs.medium.com/top-6-weird-innovative-and-hilarious-findings-in-the-ethereum-blockchain-83dbbca461ca Top 6 Weird, Innovative, and Hilarious findings in the Ethereum Blockchain by Reid Sherman (2018)
@@ -4366,6 +4396,11 @@ Claims 1600 files found.
4366
4396
4367
4397
Mentions some upload mechanisms, notably <AtomSea & EMBII> and <Satoshi uploader>.
4368
4398
4399
+
= Messages from the mines
4400
+
{parent=Bibliography}
4401
+
4402
+
https://messagesfromthemines.brangerbriz.com
4403
+
4369
4404
= Other blockchains
4370
4405
{parent=Cool data embedded in the Bitcoin blockchain}
* Logseq https://github.com/logseq/logseq no web interface/centralized server?
339
-
* Zim https://zim-wiki.org/ Local only. <WYSIWYG>.
340
-
* https://itsfoss.com/obsidian-markdown-editor[]. <Closed source>. They have an OK static website publication mechanism: https://publish.obsidian.md/ram-rachum-research/Public/Agents+aren't+objective+entities%2C+they're+a+model but leaf node view only for now, no cross source page render. They are committed to having plaintext source which is cool: https://twitter.com/kepano/status/1675626836821409792
341
-
* <Notion (productivity software)>[].
342
-
343
-
But no upvotes/topics. Favorites could be used as upvotes, but it does not seem like you can favorite other people's work. It's just not their focus, will never be.
344
-
345
-
They have an education push: https://www.notion.so/product/notion-for-education but it's likely hopeless.
346
-
Major downsides that most of those personal knowledge databases have:
347
-
* very little/no focus on public publishing, which is the primary focus of OurBigBook.com
348
-
* either limited or no multiuser features, e.g. edit protection and cross user topics
349
-
* graph based instead of tree based. For books we need a single clear ordering of a tree. Graph should come as a secondary thing through tags.
321
+
A list of reviews of such systems is maintained at:
322
+
* <Personal knowledge base software>{full}
323
+
* <Markdown editor>{full}
324
+
325
+
This is the class of existing software the perhaps comes the closest to <OurBigBook>, in particular systems such as:
326
+
* <Roam Research> and its <open source> clone <Foam (personal knowledge base)>
327
+
* <Forester>
328
+
329
+
While we believe that <OurBigBook> can hold its own against most of them as a <personal knowledge base>, there is one feature which we believe truly distinguishes OurBigBook from all others in a big way: trustless mind meld with the <OurBigBook topic feature>, which no other system seems to have.
330
+
331
+
Many such systems are also no publishing focused enough, and are more focused only in maintaining people's private knowledge bases. Some of them don't even have publishing at all, or its complicated. While publishing is optional in OurBigBook, it is a crucial feature and extremely well supported.
0 commit comments