Moving the forum to a different provider?

This community is tiny. Judging based on views and replies in Discourse, this community would be lucky to break 10,000 subs with its own subreddit at this moment. This thread has 44 comments, and most are replies, not top-level. Unless this community is filled with people who would downvote me only because they disagree, then my comments would show up just fine and you wouldn't have to scroll any further than you do on Discourse.

Reddit is a no-go for me. So, if we moved to reddit, I would definitely not be contributing to any discussions anymore. I mentioned that before. I'm not saying that I should be the reason for not moving, but I am pretty sure that others dislike Reddit as much as I do.

9 Likes

Yep, hate Reddit though I won't go as far as to say I'd leave this community of it came to that. Discord on the other hand, I'm probably giving away my age here but I just don't get that at all.

Just give me good old forum software, if need be even a free ad supported platform such as Proboards would be preferred over those.

I just can't imagine a cheap dedicated server can't handle a forum like this... Have a look at Hetzner or even OneProvider for some great offers and unlimited bandwidth.

3 Likes

This doesn't solve the problem forever (or maybe even for now), but it looks like Discourse is 50% off hosting for Open Source projects, so the Business Class would seem to be $150 vs $300.

(found here: https://free.discourse.group)

It also seems like they might help with moving to a VPS

If you exceed our bandwidth limit (for several consecutive months) you have two options:
We’ll help you move to self-hosting, either on your own server or any Docker compatible cloud (a $20/month Digital Ocean droplet should suffice).
Upgrade to our Standard hosting plan at 50% off.

(found here: Free Hosting for Open Source v2 | Blog)


I am for sticking with Discourse if possible since there is a lot of history here. One thing I would like to figure out is an easier way to make "wiki" pages that answer common / evergreen questions. I know that discourse calls one page type a wiki, but it looks like a normal post and doesnt have any sort of hierarchy so I never bother. Maybe if we moved more of this content to structured pages, the page views to the forum itself would decrease?

5 Likes

I said I won't be posting anymore. I will not abandon Joplin nor the community. You just won't read any comments on reddit from me. That's all.

e.g. I'm also not too happy with stackoverflow anymore. Often a solution is picked that is actually wrong. If you are blunt like me, you are always downvoted, even though you speak the truth (without name calling or personally offending someone). They rather care about sugar coating, diplomacy, and sucking up to others, than facts. Unless you are moderator. In which case you can even be openly unfriendly to people. I can't deal with this bigotry.
Actually, you don't even have to be blunt, you only have to point out that an answer is factually wrong with providing proof... and it can end up with you being banned.

5 Likes

Do mean some kind of hierarchical menu? Because it can be done using a special tag, as was done for example for the GSoC blog last year.

If there's enough interest in it I guess we could have a main community wiki post that would link to other wiki pages. And we could pin this main wiki post so that's it's always easily accessible. I think that would make sense because there's indeed quite a bit of content on the forum that's not part of the official doc, but that can be very useful anyway.

1 Like

I've also created a few tags like #how-to and #tips-and-tricks to make certain posts easier to find.

P.S. We can create more tags. I removed the possibility to create tags for users with lower trust levels, because a lot of people added weird, undescriptive, useless tags which only messed up the tag system.

1 Like

a web-version of joplin would work very well as a community wiki

1 Like

Perhaps some ever-green information could also be transferred into a community run documentation/FAQ (done in Discourse but Git Book or something would be even better).
That would be a great starting point for new users, but also quite some work to maintain it.

(Sorry for the Off topic)

I think we should stick with discourse. There is too much history here to switch to something else. Amanda also showed that it doesn’t seem to be to difficult/expensive.

I will start using tags as @tessus mentioned, I think that will be a good way to pay attention to what content is evergreen / FAQ.

As for the idea of a wiki, I realized that I am should probably just look to move things to help instead of creating a new place. I know that it is built from Github somehow. but not sure what the tech is. Would be cool if that was editable on the page itself / easier to see how to add new pages, but that might not be worth investing any time into.

1 Like

That was my thought. I'm wondering if you thought it needed to be a wiki so anyone could edit, or whether you were just meaning help articles. I would think that allowing a few volunteers to edit help articles, possibly with a comment section so people could suggest additions. The scope is rather limited and allowing anyone to edit might not be worth the trouble. On the other hand, it would be good if new folks could easily be given permission to edit help articles. Sometimes new people are well positioned to write up documentation since they are seeing things with fresh eyes.

Maybe Joplin is still too dynamic, but I think having well written documentation is far superior to expecting new people to search the forum and post questions to get problems solved. Of course the forum is essential. But it's not the best first stop for new folks.

1 Like

In general I think official documentation should go under /help, but there are also more general topics that are more suitable for a community wiki. For example, how to setup WebDAV with a particular provider, how to import notes from CherryTree, how to customise the app CSS, etc. I wouldn't necessarily want to have this in the doc because it's a bit too specialised, however that would be good topics for a community wiki, which could be updated by anyone over time.

I agree that the pull request system is not well suited for this but creating wiki posts on Discourse maybe indeed combined with tags might work.

1 Like

I hadn't paid attention to this before, but I don't actually see a way to create a wiki post. Perhaps my trust level isn't high enough?

On another forum I use (that uses discourse) there is a wiki category. I'd say that a specific category for documentation wikis makes much more sense than tags, although tags could be used to organize the category. I actually think that the GSOC would be better as tags rather than categories, but that's a different issue.

It needs level 3 trust, which all regular users should have. You need to create a post first, and then turn it into a wiki as described there: How to create a Wiki Post - faq - Discourse Meta

Interesting! Looks like the other forum I'm on has set the category to be wiki posts, as the instructions explain at the end. Thanks!

1 Like

Yes, you can create a category where topics are automatically created as wiki pages.

1 Like

I like reddit and get a lot out of it as a community, but it's certainly not perfect (what is?). OTOH, I don't feel that it would be the right platform for the kind of discussion that I find here. In theory StackOverflow could be better, but I despise it and the "holier than thou" attitude of too many of the participants. If the forums moved there I'd ignore them and lose a lot from this community. But, I don't feel that the kinds of discussion Stackoverflow has is suitable for this environment either.

Discourse does what it says on the tin, and that's important. It supports free-flowing conversations in a way that a lot of other platforms do not. I understand that costs are important for Open Source projects with a small user base, and I don't really have enough experience in the discussion forums area to come up with a solution, sorry. I do hope that the quality of discussions isn't compromised by the eventual choice of platform.

1 Like

I think the discussion area in the Joplin github repository should be activated. There are a lot of ideas for new features or plugins discussion launched here on Discourse which I really think belong in the github discussion. I looked at the powershell repository on github which uses the discussion area and found that suggestions and ideas for features and the discussion around those should be close to the source of the app. Now, what is left for Discourse then? Support? maybe. General talk about working with Joplin? Maybe. I guess the experience between mobile and desktop devices will differ enough for some things to stay here. But in the end I think that opening up the discussion area on github is independent of what other tools the community uses.
Instant chat could be done on gitter.im and turns out to be a good feature in many other projects.

This is probably the best option if that day ever comes, take my name down as I'd be willing to assist.

We are already spread out too much. Discord, web, forum, github (and there are some unofficial channels).

I don't think it makes sense to open yet another place to discuss things.

4 Likes