Earlier quoted context omitted.
> Running on the blazing fast Node.js engine Is Node.js that blazing-fast ?
Surprisingly yes. It has billions of dollars or optimizations and research in it over the years and can really fly. Of course you can write slow node code just like you can in any language, but a single well-written node instance can handle a lot of traffic.
Wiki.js
201–210 of 213 posts
Re: Wiki.js
#202Earlier quoted context omitted.
Try rewriting history if you want, but the thread goes off-topic as soon as mekster suggests the project change the license, and your reply there only feeds into it. And it still doesn't explain how you can claim that your comment was meant to "agree" with gary-kim's. > My reply is in this context, not in the parent's parent The parent's parent at that point is... your comment, "For future versions, not past versions…
> mekster suggests the project change the license When have I suggested the project change the license??? I only said it is possible.
Re: Wiki.js
#203Earlier quoted context omitted.
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…
>"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." The take away is clearly "things that work in the small often don't work in the large. If you're taking life advice, take it from someone…
Re: Wiki.js
#204Earlier quoted context omitted.
> They can change the license to a closed one from a certain version in the future. You're right if and only if by "they" you mean every copyright holder whose contributions would exist in the future version (including, say, the contributions of the very person you're responding to). But if by "they" you mean the project leaders acting without the cooperation of everyone who holds copyright, then that's a no.
It was easy to tell it's almost one man's job if you look at the level of integrity the software has. https://github.com/Requarks/wiki/graphs/contributors Main guy commiting 600k lines and the second most committed guy 450 lines. So yeah, it wouldn't take him a whole lot of time if he really wanted to change the license by removing all the others' commits and rewriting it by himself. Also, what does AGPL has anything…
> So yeah, it wouldn't take him a whole lot of time if he really wanted to change the license by removing all the others' commits and rewriting it by himself.
Good point. I may try to get involved in its development as well to spread that out a little more.
> Also, what does AGPL has anything to do with keeping the license open sourced?
The AGPL requires that any code linked to it also be distributed with an AGPL license (the difference from the GPL being that hosting over a network counts as distribution). Every part of the project is technically linked to itself so if someone makes a change, no one else can use that change in the project under a different license.
Re: Wiki.js
#205Re: Wiki.js
#206I 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?
Re: Wiki.js
#207Earlier quoted context omitted.
I've been using Obsidian for note taking recently, and as much as I really enjoy it - having hypermedia would be quite useful too. I can paste images in Obsidian, but it tends to put the pasted image in the root folder, and I can't display it inline with my notes. EDIT: VisualEditor, the de facto standard for pasting things like screenshots into your articles seems to be a pain to install. Got my local env up and run…
I may have misunderstood, but I'm using images in Obsidian without any trouble. Create a folder inside Obsidian, right click it, choose "Use as attachment folder" and then drag and drop / paste images into your documents however you like. It saves to this folder and automatically generates the markup when you put an image in.
Given the complexity of setting up WikiMedia properly, I think I'm going to keep using Obsidian.
Re: Wiki.js
#208Slightly 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've been using Obsidian for note taking recently, and as much as I really enjoy it - having hypermedia would be quite useful too. I can paste images in Obsidian, but it tends to put the pasted image in the root folder, and I can't display it inline with my notes. EDIT: VisualEditor, the de facto standard for pasting things like screenshots into your articles seems to be a pain to install. Got my local env up and run…
Re: Wiki.js
#209Re: Wiki.js
#210Earlier quoted context omitted.
You seem to be assuming that you are the only person who will ever contribute meaningfully to the software. But if, as you probably also hope, the software is widespead and successful, there will most probably arise at least one popular third-party extension/modification. And you will not be able to incorporate this addition into the product which you distribute to your b2b customers; this will make your version of t…
The other option is that could simply pay community members some fair portion of the b2b revenue in exchange for signing the CLA. If you're the primary contributor, it's fair to take most of the revenue for yourself, but revenue sharing with major contributors from the community is also fair. Could be difficult tax-wise though? IDK.