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

151–160 of 213 posts

Re: Wiki.js

#151

Post by stevenicr »

fastball wrote: post #137
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,…

I like the points you mention here - I took a look at your site and glad to see pricing is easy to find. I myself want to self host, as I don't trust the cloud - but if I was to try your version of this thing, I would lean into the $300 one time payment, as the free tier would be worth the time (20 notes) - and I hate monthly payments and non-owned code.

I did scan of the faq and ended up up on the docs and searched for export. I was pleasantly impressed with the entry which showed an export option along with text and videos showing how to do this.

For me, I probably won't be spending 300 on this when I can wiki or wordpress for free... but if I was not so jaded about saas and cloud, I would be persuaded to check out your thing if you had on the front page like "export, backup" and bonus if it was 'import/export markdown or similar files'

I'd feel less worried about vendor lockin, holding data hostage, what happens when you go bankrupt, etc

the heading fonts on your privacy page are a little wonky in my browser (firefox) - being that you are uk and sharing data with EU and outside the EU - I'd only save info if it was encrypted.. not sure if that is a thing, if so I would make 'privacy built in' a big thing on the front page.

my cents in trying to help, I'm sure 98% of those who may use your service are not as sensitive to the same things I am - so this is not a critique saying it's bad, just offering some random thoughts as I took a look.

Re: Wiki.js

#153

Post by unicornporn »

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 almost went with MediaWiki, but ended up with DokuWiki. The fresh install of MediaWiki is 154 MB (!) and it's not exactly lightweight. DokuWiki is 10.9 MB and all content is saved in plain text files. Very attractive.

However, backlinks are not possible without hacks. A wiki without backlinks is kind of lame and I could very well use my good old plain text files.

Have you run in to trouble when updating MediaWiki, or is it smooth sailing? SQLite is not mentioned here: https://www.mediawiki.org/wiki/Download

Re: Wiki.js

#154

Post by fungos »

hundchenkatze wrote: post #135
fungos wrote: post #123

Earlier quoted context omitted.

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.

If they are the sole copyright owners (no external contribution) or have SLAs, they can for any future version of the software. It is not uncommon, it is just hard as most doesn't have SLA to do this.

Re: Wiki.js

#155

Post by httgp »

tommoor wrote: post #147
Keyframe wrote: post #21

I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?

Outline ( https://www.getoutline.com ) supports this functionality.

Oh wow, this looks great! I was pleasantly surprised that this is open-source and can be swift-hosted too.

Re: Wiki.js

#156

Post by fastball »

stevenicr wrote: post #151
fastball wrote: post #137

Earlier quoted context omitted.

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,…

I like the points you mention here - I took a look at your site and glad to see pricing is easy to find. I myself want to self host, as I don't trust the cloud - but if I was to try your version of this thing, I would lean into the $300 one time payment, as the free tier would be worth the time (20 notes) - and I hate monthly payments and non-owned code. I did scan of the faq and ended up up on the docs and searched…

Thanks for taking the time to write down your thoughts!

Data ownership is pretty important to us, even though we are only offering a hosted solution, which is why we explicitly say as much in our T&Cs[1]. But yep, we want to make export / backup of your data as easy as humanly possible. The hard part generally is that there are a number of features that exist on Supernotes which just don't exist elsewhere, so even when you use the export feature it is hard to guarantee we can export it in a format that is useful to you.

That is part of the reason we are doing our best to openly document our API[2] so that you can interact with your own content in whatever way you wish (including importing content from wherever or exporting to wherever). Obviously this requires some coding, but we're hoping the community[3] will share any tools they build on top of the API with each other.

Unfortunately E2EE is not quite there yet, as it makes it much more difficult to facilitate sharing when you have E2EE, as well it being a bit of a problem when it comes to a knowledge base if a user loses their private keys and you have to tell them "sorry we can't get your content back – it's all gone". But this is definitely something we are working towards – just takes some time to nail the UX. Since we are definitely never going to sell your data or anything (as per T&Cs), it's better for us if it's E2EE as then it's just one less liability for us from a data protection perspective.

[1] https://supernotes.app/terms/

[2] https://api.supernotes.app/docs/

[3] https://community.supernotes.app/

Re: Wiki.js

#157

Post by cxr »

VexorLoophole wrote: post #120
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…

Also wanted to get into creating a local 'wiki' or knowledge base. Sadly I didn't hit the sweet spot till now. My requirements are: - future proof (at least not only a one man project) - Fast search over all informations - Fast creation of quick notes (inbox) - Mobile iOS client Currently I am stuck with Notion, which has a great 'database' concept. Which is fun to use. Sadly it's too slow. If I want to take a quick…

MediaWiki is certainly future proof and has lots of inertia, including a large API surface area, a large ecosystem, and the backing of a deep-pocketed benefactor. An extremely underrated/largely unknown project is Miraheze[0] which is a non-profit that provides free MediaWiki instances to people.

I wish proper wikis hadn't gone by the wayside. (I think it has a lot to do with MediaWiki's default skin being out of style, and people not realizing they can change it.) Most of all, I wish open source projects would stop dumping a bunch of Markdown in a repo somewhere and calling it a "wiki". They're not even close to comparable.

My two biggest complaints about MediawWiki are 1. PHP, and 2. no well-supported way to opt-in to a different syntax like Markdown or AsciiDoc or pretty much anything that isn't MediaWiki-flavored wikitext.

0. https://miraheze.org/

Re: Wiki.js

#158

Post by kmill »

heresie-dabord wrote: post #143
john-shaffer wrote: post #131

Earlier quoted context omitted.

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 everyt…

> The language and ecosystem are so full of footguns "footgun" is an excellent term. Here's an earlier use on HN, 2010: https://news.ycombinator.com/item?id=1904960

I've wondered whether the term directly evolved from this sort of joke list that was popular to pass around on the early internet: http://www.personal.psu.edu/sxt104/program1.html

Re: Wiki.js

#159

Post by winton »

Keyframe wrote: post #21

I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?

Though its more of a building block, Editor.js supports this: https://editorjs.io

Re: Wiki.js

#160

Post by as1mov »

bovermyer wrote: post #77
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 use Zim for this, backed by Dropbox. It's just text files, and Zim is just an editor, not a server or anything like that. If I ever tire of keeping a personal wiki for whatever reason, all of the content I've built up in it will remain organized as files within directories.

+1 for Zim+Syncthing, been using it for almost 2 years now. The only gripe I might have is against the near useless search and proper support for code blocks.
Post reply on HN