EReriknstr·Jul 13, 2017
Off topic but the hash shown piqued my interest.
The source is linked from the page - https://github.com/btrask/stronglink
> A searchable, syncable, content-addressable notetaking system
In ProcOS: scheduling atop Unikernelsbtrask
stronglink
C2015–2017
btrask / stronglink
stronglink
A searchable, syncable, content-addressable notetaking system
6Distinct people
10Mentions
0Explicit recommenders
1KGitHub stars
What to know before exploring
What it is
A searchable, syncable, content-addressable notetaking system
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month10 dated mentions
Observed mentions: 2015-09-02 01:56:03 UTC to 2017-07-13 09:47:33 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Sep 2015 | 2015-09-01 00:00:00 UTC | 2015-10-01 00:00:00 UTC | 1 | 1 | 0 |
| Oct 2015 | 2015-10-01 00:00:00 UTC | 2015-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2015 | 2015-11-01 00:00:00 UTC | 2015-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2015 | 2015-12-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2016 | 2016-01-01 00:00:00 UTC | 2016-02-01 00:00:00 UTC | 2 | 0 | 2 |
| Feb 2016 | 2016-02-01 00:00:00 UTC | 2016-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2016 | 2016-03-01 00:00:00 UTC | 2016-04-01 00:00:00 UTC | 1 | 1 | 0 |
| Apr 2016 | 2016-04-01 00:00:00 UTC | 2016-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2016 | 2016-05-01 00:00:00 UTC | 2016-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2016 | 2016-06-01 00:00:00 UTC | 2016-07-01 00:00:00 UTC | 2 | 1 | 1 |
| Jul 2016 | 2016-07-01 00:00:00 UTC | 2016-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2016 | 2016-08-01 00:00:00 UTC | 2016-09-01 00:00:00 UTC | 1 | 0 | 1 |
| Sep 2016 | 2016-09-01 00:00:00 UTC | 2016-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2016 | 2016-10-01 00:00:00 UTC | 2016-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2016 | 2016-11-01 00:00:00 UTC | 2016-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2016 | 2016-12-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2017 | 2017-01-01 00:00:00 UTC | 2017-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2017 | 2017-02-01 00:00:00 UTC | 2017-03-01 00:00:00 UTC | 1 | 0 | 1 |
| Mar 2017 | 2017-03-01 00:00:00 UTC | 2017-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2017 | 2017-04-01 00:00:00 UTC | 2017-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2017 | 2017-05-01 00:00:00 UTC | 2017-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2017 | 2017-06-01 00:00:00 UTC | 2017-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2017 | 2017-07-01 00:00:00 UTC | 2017-08-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
10 sourcesWhy not use Markdown instead of MediaWiki syntax?
About URLs, you can take a look at StrongLink: https://github.com/btrask/stronglink
Your JSON subset is very interesting too: https://github.com/seagreen/Son
In Watching Wikipedia's extinction event from a distanceI wrote such a library in C[1] and in practice it's been no problem. Most libraries that do IO provide hooks (for example I made SQLite fully async[2], with no changes to their code). For cases where that isn't possible (or desirable), there's also an easy way to temporarily move the entire fiber to a thread pool.[3] That's actually much faster than moving back and forth for every call (which is what AIO emulation normally entails).
[1] https://github.com/btrask/libasync
[2] https://github.com/btrask/stronglink/blob/master/res/async_s...
[3] https://github.com/btrask/libasync/blob/master/src/async.h#L...
Disclaimer: not production ready, for most values of "production"
Edit: stacks don't grow dynamically, of course. But that's also a problem in Go if you want to efficiently call C libraries. If you really need efficiency, you can use raw
Read the rest
callbacks for that particular section.
I developed a "general purpose" JSON-based CRDT[1] as a part of my content addressing system project. The idea was to have an "append-only tree", where subtrees could be used by individual applications for different purposes, for example as counters or mutable sets.
In retrospect, it didn't need to support recursion. A single-level append-only set is enough to be fully general and easier to perform indexing on. Using JSON was also overkill, since too much flexibility is bad for content-addressing.
[1] https://github.com/btrask/stronglink/blob/master/client/READ...
In A Conflict-Free Replicated JSON DatatypeStrongLink – a searchable, syncable, content-addressable notetaking system
2 points · Open discussionThe author's other project, https://github.com/btrask/stronglink looks fairly interesting too - 'A searchable, syncable, content-addressable notetaking system'.
In Show HN: Hash Archive helps you verify the hashes of insecure downloadsStrongLink: Content-Addressable Notetaking System with “hash://” URI
4 points · Open discussionI recently wrote a similar article ("C Programming Substance Guide")[1] which made the rounds here[2]. I've updated and improved it quite a bit since then too. It seems like we agree on the major points but it might be a good second opinion.
[1] https://github.com/btrask/stronglink/blob/master/SUBSTANCE.m...
[2] https://news.ycombinator.com/item?id=10157018
In How to C in 2016Adding layers of indirection isn't going to give us a permanent addressing system. This service just adds new points of failure: the service itself, or the creator of an identifier who fails to update it or changes it maliciously.
The real solution is some form of content addressing. Whichever one you want: URNs, magnet links, the "ni:" RFC[1], IPFS paths[2], or my own hash link system[3].
[1] http://tools.ietf.org/html/rfc6920
[2] https://ipfs.io/
[3] https://github.com/btrask/stronglink/
In Permanent Identifiers for the Web