Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wiki.js

wiki.js.org

Post reply on HN
Print view View original

131–140 of 213 posts

Re: Wiki.js

#131

Post by john-shaffer »

ArtDev wrote: post #116
heresie-dabord wrote: post #114

I used a Wiki for a long time. But I try to minimise maintenance ("foist it upon others"). I also try to resist the enthusiasm for Rube Goldberg machines and for installing bad tooling (such as PHP). Now that git has become ubiquitous, I prefer git with a self-hosted git-daemon instance. git , grep , awk , and sqlite make a strong set of tools for knowledge curation. edit: minor grammar fix

Unnecessarily bashing PHP is soo 2005. Like javascript, it can be written poorly due to its loose roots. Also just like javascript, it is a very different language now. That said, DocuWiki is pretty decent to get up and running quickly.

I use PHP in my day job. It is by far the worst language I've ever used. Nothing else even comes close. The language and ecosystem are so full of footguns that you are bound to shoot yourself eventually. The OpenSSL implementation will silently truncate the key [1][2] without even giving a warning. The cURL lib, in 2020, still hasn't implemented a get_curl_opt function. Sure you could wrap it if you're writing everything, but the reality is I have to work in this nightmare ecosystem that just uses raw curl. Every == comparison is still a potential security hole due to PHP's insane (and inconsistent) typecasting behaviors. Sometimes a number gets cast to a string, but a string gets cast to a number if you use it as an array key. WTF? Do I have to wait another 15 years for PHP to become a halfway decent language?

[1] https://github.com/WP2Static/wp2static/pull/506

[2] https://stackoverflow.com/questions/55062897/decrypt-aes256-...

Re: Wiki.js

#132

Post by [deleted] »

hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

[deleted]

Re: Wiki.js

#133

Post by Geezus_42 »

zeta0134 wrote: post #106
keithnz wrote: post #65

Earlier quoted context omitted.

I did start similar things over 10 years ago. Where I am at these days is just text files ( markdown ) nested into folder structures. I've found this the most sustainable for quite a few years and it's been super useful. Main thing is, do whatever, as long as you find it easy to sustain.

This is what finally replaced Google Keep for my shopping list and then eventually everything else. I use Markor and Syncthing on my phone, and a standard text editor on my various computers. It is super nice especially to be able to organize the directory using standard file management tools, search using grep and friends, etc. There is something to be said for simplicity.

+1 for Markor, also available on fdroid

Re: Wiki.js

#134

Post by Geezus_42 »

keithnz wrote: post #65
hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

I did start similar things over 10 years ago. Where I am at these days is just text files ( markdown ) nested into folder structures. I've found this the most sustainable for quite a few years and it's been super useful. Main thing is, do whatever, as long as you find it easy to sustain.

If you use vscode you should look into the dendron add-on.

Re: Wiki.js

#135

Post by hundchenkatze »

fungos wrote: post #123
mekster wrote: post #104

Earlier quoted context omitted.

> It's a guarantee that the project will remain open source What are you talking about? They can change the license to a closed one from a certain version in the future.

For future versions, not past versions.

I don't think any of the mainstream open-source licenses allow you to retroactively revoke or change the license.

Re: Wiki.js

#136

Post by ttsda »

hombre_fatal wrote: post #72
hn_check wrote: post #67

Earlier quoted context omitted.

This is the problem with a good percentage of advice and life/career hacks on HN -- they're always spoken of in the early, idealist stage. Before the reality has set in. Before the downsides have made their presence known. I've been in a number of firms with wiki knowledge systems. In 100% of the cases it was a wasteland of derelict knowledge that had been abandoned and was usually much more destructive than benefici…

I don't really understand your take-away except for a cynical "bah, nothing ever works so don't try." Or maybe it annoys you that you didn't see some trite platitudinal disclaimer in my post about how how life is all about trade-offs and what works for Bob might work for Alice. It's like you're about to tell me that exercising doesn't pay off because it's hard to stick with a strategy. "Heh, let's see if he's still d…

The skepticism is not unwarranted. Borrowing your exercise example, it would be like saying you do X pushups every day and it changed your life, and then saying you've been doing that for a couple days. Wikis are infamous for not working out on the long term.

Re: Wiki.js

#137

Post by fastball »

hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

Just to throw my hat in the ring here:

My co-founder and I have been building a hosted version of this[1] for the last two years, because we recognized that while self-hosted wikis work great for techie people, there are a lot of other people who that label doesn't fit.

So we've been working to create a collaborative knowledge-base platform built around some key concepts:

1. Built around cards rather than documents, which allows for a lot of interesting and flexible features. Such as...

2. Granular sharing – on Supernotes, you can share an entire collection of cards, or you can share one card at a time. We also have recently introduced[2] a "friends" features that allows you to quickly drag-and-drop cards onto your friends to share with them.

3. Multi-parent nesting – there is no folder-style filesystem on Supernotes, we allow you to nest cards inside of each other. On top of this, we allow for this nesting to be multi-parent, so different users can fit the same cards into their own unique structure (effectively a collaborative / personalized version of symbolic links).

4. Public vs. private tags – cards can be tagged with public tags that everyone sees, but can also be tagged privately with only tags that you can see. This same idea is reflected across the platform, where we want the underlying content to be the same for everyone but want to allow users to personalize the metadata/structure to suit their own workflow.

5. Focus on speed – we have spent a lot of time making Supernotes speedy quick, and try to make it faster every time we release a new feature.

Anyway that is the rough idea. The goal of Supernotes is to be a sort of data-layer where you can keep all these compartmentalized pieces of content (as cards) and then mix-and-match at will to create very simple or very complex stores of knowledge. We also want you to be able to embed these pieces of content elsewhere (say in a Notion document or on your blog) with as little effort as possible (not quite there yet, but will be soon).

[1] https://supernotes.app/

[2] https://supernotes.app/changelog

Re: Wiki.js

#138

Post by iamacyborg »

hadrien01 wrote: post #88
iamacyborg wrote: post #66

Earlier quoted context omitted.

Gamepedia was bought by Fandom too, FYI.

They're apparently working hard to upgrade and merge their diverging MediaWiki codebases; some details on this very interesting blogpost: https://community.fandom.com/wiki/User_blog:MisterWoodhouse/...

Neat, I actually sold a wiki to Curse pre-Gamepedia and worked there for a short while. Not very happy to see a single company gobble up so much of the online gaming community.

Re: Wiki.js

#140

Post by heresie-dabord »

ArtDev wrote: post #116
heresie-dabord wrote: post #114

I used a Wiki for a long time. But I try to minimise maintenance ("foist it upon others"). I also try to resist the enthusiasm for Rube Goldberg machines and for installing bad tooling (such as PHP). Now that git has become ubiquitous, I prefer git with a self-hosted git-daemon instance. git , grep , awk , and sqlite make a strong set of tools for knowledge curation. edit: minor grammar fix

Unnecessarily bashing PHP is soo 2005. Like javascript, it can be written poorly due to its loose roots. Also just like javascript, it is a very different language now. That said, DocuWiki is pretty decent to get up and running quickly.

> Like javascript, it can be written poorly due to its loose roots.

I understand that bad code can be expressed in every language. But there is bad tooling too.

PHP clearly has a lucrative place in the world. But it remains a significant threat vector.

Yes, even in 202x. I leave others to discuss why this is the case. I won't install PHP on a workstation just to run a Wiki. ^_^

Post reply on HN