This collection of things built with CollectionBuilder (CB) might also be interesting, both for seeing how this works and practice and for finding interesting collections built with this: https://collectionbuilder.github.io/cb-examples/
So basically a multi-person Zettelkasten? The idea with a Zettelkasten (zk for short) is that each note is a singular idea, concept, or argument that is all linked together. Arguments can link to their evidence, concepts can link to other related concepts, and so on.
This additionally reminds me of a Bullet Journal; for me, a Bullet Journal fulfills the role of the author's sketchbook; the creator, Ryder Carroll, brands it as a planner, diary, sketchbook, calendar, and a 'catch-all for life': https://en.wikipedia.org/wiki/Bullet_journal
Wikidata editor here. On some of the older Wikimedia projects (and English Wikipedia/enwiki especially), adminship comes with a large amount of extra baggage and is viewed as a somewhat prestigious position (but I have only seen this on enwiki, not Wikidata or other projects. On Wikidata, adminship is mostly a formality for established editors.)
Keep in mind that enwiki has the largest amount of history and bureaucracy out of all of the Wikimedia projects, due to being the first in a long line.
I'm not the person you replied to, but I'll answer anyway :)
IPNS is essentially DNS over the IPFS network. IPNS domains point to a specific IPFS file (or a set of files, like we see here). IPNS domains are signed with a private key; when you want to update your IPNS entry, you add your new content to a new IPFS file
and then you update the IPNS entry by signing it with a public key.
There's also the various https://diybookscanner.org variants. Not the quickest imaginable system, but it's much better than going <i>snap snap snap</i> with a cellphone.
In certain circles, there's always a risk of swatting[1].
If you're anonymous online and your physical address is leaked, that could lead to doxxing[2] that could eventually lead to the aforementioned swatting.
"Lawson’s case hinged on whether he was a contractor in his brief four month stint delivering food for Grubhub, or an employee—entitled to minimum wage, overtime, and other benefits. An initial 2018 ruling sided with the company, and denied Lawson employee status. But after an appeal to the Ninth Circuit and a remand back down to the same district court, Judge Jacqueline Scott Corley has now ruled that, under California laws, Lawson was legally a Grubhub employee.
"'Mr. Lawson is properly classified as an employee, not an independent contractor, for purposes of his minimum wage and overtime claims,' wrote Judge Corley..."
I love using Wormhole (https://wormhole.app/) for this purpose. The UI and the downloads are extremely snappy, and for large files it uses peer-to-peer technology to speed up downloads. Download links can also expire, which is a nice bonus.
(N.b. Not associated with Wormhole or the developers; I'm just a satisfied user.)
> You first need to compile/install a bunch of things in order to make Lua useful.
How is this any different from pretty much any language out there? From a quick eyeball of RustPython's Cargo.toml[1], there are about 70 different dependencies which all need to be compiled. I haven't worked too much with Autoconf, but I am pretty sure CPython has quite a few dependencies.
> The second part is that the Lua constructs for programming in the large are very weak.
This is deliberate because it forces you to use the tools you are given instead of reimplementing features that can already be implemented by using other primitives in Lua.
> I believe that Adobe had a postmortem about this (Lightroom, I think?)
I can't find this article. Has anyone else had any luck?
GitHub: https://github.com/tomodachi94
Blog and bio: https://tomodachi94.github.io/?utm_medium=social&utm_source=hn&utm_campaign=hn_profile