What's missing in Talkyard
Here are things relatively many ask about, and that have not yet been implemented:
Custom groups— now available, June 2019. You can add people to a group, and configure security permision and notification settings for everyone in the group at once. Maybe some other features people will want are missing — will impement, during the nearest weeks and months.
- Mobile app notifications and desktop notifications. (Currently, you get notified via email instead.)
- Business login: LDAP / ActiveDirectory login, SAML, Okta etc. — Nowadays (year 2020), there's Vouch-Proxy, what do you think about it? Seems it'd work with LDAP, Okta, OpenID Connect and many others. Here's a blog post by Okta about Vouch-Proxy.
There's social login already: Gmail, Facebook, Twitter, Github. And Single Sign-On via API.
So now you know.
- 14 replies
There are 14 replies. Estimated reading time: 14 minutes
- SSteve Lee @stevelee2019-09-27 21:10:13.543Z
The admin pages do not show the number of likes.
- KajMagnus @KajMagnus2019-09-29 17:38:53.005Z
Hmm can you please explain a bit more? Do you mean ... Maybe the Review tab in the admin area, where one sees other people's posts and can review them? And that there're no Like votes shown there? — If so, showing Like votes there, and Disagree votes etc, seems like possibly a good idea. Can be helpful, when reviewing, is that what you had in mind?
Or you want a summary of all likes everywhere? And a graph: Num like votes, plotted against time?
Sorry I meant the review tab - the pages that show my comments - at least on the top level one. It would be useful to see the number of likes. So I likes total.
But now I think of it the like is per page not comment so may not fit with those review pages?
- KajMagnus @KajMagnus2019-10-04 16:10:31.337Z
I'll show Like etc vote counts, in the next version. (Just fixed.)
- In reply tostevelee⬆:KajMagnus @KajMagnus2019-10-04 15:33:15.594Z
Thanks for explaining. I agree with you; it'd be nice to see Like and Disagree votes etc on the review tab. (Likes are per post / comment, not per page.)
- BPeter It-Leo @brainbug2019-10-28 11:26:24.776Z
Sub Topics would be nice. They would give a look and feel like a common forum and a better handling of bigger communities. Or at least topic grouping as a "headline" which can be collapsed and minimized.
- KajMagnus @KajMagnus2019-10-28 14:38:03.278Z
This sounds interesting — and I'm a bit unsure what you have in mind? Maybe you could share a link to some website that has sub topics implemented? You didn't mean sub categories?
Would there be different section inside one discussion topic (like, this page), with their own headlines?
And one could collapse the sub topics — then, only the headlines would be shown?
Or is this about the forum topic list page? I.e. pages like: https://www.talkyard.io/forum/
There is probably more than one way to reach the goal.
I was thinking about: how to find a topic within talkyard, especially if you have about 30 "main" static topics with lot of sub topics as you might have in a forum (here they are categories).
So i like the non static way of talkyard but see some issues finding a topic when you have 2000 or more topics. If you organize topics with categories only, you will have a lot of categories and sub-categories. But it could be a smart way also... don't know that. So let me try to explain with an example:
You have a community which is sharing a lot of information for cars:
Car Models (Headline - static / topics - collapsing)
- Audi (Sub Topic, has new threads)
- BMW (Sub Topic)
- Chrysler (Sub Topic)
- Ford (Sub Topic)
... 15 more "Topics"
- Ford (Sub Topic)
Repairing (Headline - static / topic - collapsing)
At this point it would be nice to create static headline and pre defined topics (like a forum).
Or another way as you mentioned before with categories and subcategories. In the example the topic "Audi" has the category "car" and will automcatically put under the static headline "car" in the main view. So it would be easier to find a topic. But if you have a great forum and about 20 headlines and 100-200 categories, it would be painfull to select a category (overwhelming the user to find the right categorie and scrolling through dozens of entries while creating a new topic). So i think pre defined topics would be much better with some categories (which would be maybe the headline? Like category: car, repairing... - these are automatically the static and collapsable headlines....). I have something like this in mind.
That would keep the "dynamic" i love in talkyard with the alternative use as forum (which i am looking for). But it might be not the intension of talkyard, i know that (but would be a nice optional feature). But i see your point about sub categories.
That is why i think categories should not the main way to organize the "main menu" and more for detailing the topic. The level 1 (main) and level 2 (sub) topics for the main menu and after that new topics (level 3) will be created from user.
Maybe it's possible to create "non choosable main categories" which are the main menu. Then you have categorie "audi" which has been defined as a subcategorie for cars (which the user does not see) from the admin, Creating a new topic with this categorie will automatically put under the main "headline" cars. That would a first step for organizing large communites with lot of topics.
It's just about having like 2000 topics within thousands of answeres. But probably talkyard is not made to handle that this way and showing answeres.
Maybe a solution would be like this: https://community.nodebb.org/
There are main categories with sub categories located all at main site. So you can jump directly to the sub category. In these sub categories you can create a new topic and does not have to choose from a large categorie list. This should be an alternative feature to organize the topics/categories in talkyard. For small communities you can use the existing type. For large communities you can organize as mentioned in this paragraph. Then talkyard would be a nice, modern and attractive alternative to current forum software.
- KajMagnus @KajMagnus2020-02-09 10:18:07.836Z
(sorry for the late reply ... I started writing, and then I was going to proofread this later and ... a bit forgot, until some weeks later. .... Then I re-read what you wrote, and, felt uncertain if I understood everything correctly, ... worked with other things ... and ... didn't reply until now. — I wrote the reply below some months ago, and ... not sure if it makes much sense.)
This sounds to me like a forum homepage "menu builder" or "categories and topics index builder"? Maybe one could drag & drop top level categories, and also topics, to create a level 1 menu. Categories would list their sub categories, like the NodeBB example you linked, does. And one could also somehow insert "featured topics" as level 2 sub items, as children of the categories, and in that way list not only sub categories, but also the most important topics in those categories?
Something like this? (Where
[t]are some icons showing if the "thing" is a Category or a Topic)
Forum Name ============ [t] Welcome Topic Name [t] Get-help chat channel link [c] Category Name [c] Sub Category [c] Another Sub Category [c] Third Sub Cat [t] Featured Topic Name [t] Other Featured Topic Name [c] Another Category [c] Some Sub Category [c] Yet Another Sub Category [t] A recently popular Topic [t] The 2nd most "hot" topic in this category [t] Top level featured topic [t] Another featured topic
So one could insert topics and categories in whichever way one wants.
One could maybe choose to show the most popular topics, in a category,
and also manually mark certain topics as "Featured", and then they'll appear next to the categories and the "Popular" topics?
And, by default, only categories would be shown, like in your NodeBB example?
- Leon Stafford @leonstafford2019-11-27 04:07:25.891Z
May just be me missing where to find the docs:
- API calls (only see the upsert one in e2e specs)
- webhooks: would like to be able to not login to Talkyard (or any other tool) unless absolutely necessary. With so many things used, webhooks allow centralizing it in a way that makes sense to me (with more usable data than email notifications)
- KajMagnus @KajMagnus2019-11-27 07:06:51.386Z
Agreed that docs are missing :- P
What webhooks do you want / need?
There's an RSS / Atom feed. Example (for this site): https://www.talkyard.io/-/v0/feed — can be combined with Zapier
Currently there's Single Sign-On, and Upsert-Categories, and (implementing right now) Upsert-Pages.
- Leon Stafford @leonstafford2019-11-27 09:51:35.134Z
Couldn't see if there was pagination option in feeds (hardcoded limit to 25 most recent?)
Thinking out loud, I'd like to be able to pull KPIs, like:
- number posts
- number posts with replies
- number posts answered
- number users
And have event triggered webhooks, like when a user signs up and when a post/comment is made, I can attribute that to the user, based on their email.
This helps with a centralized customer area I'm working on, where, for example a customer support request comes in, I can quickly see all activity from this person across forum, payment, email.
Also enjoying the ReTool app as a centralized admin UI. With something like this, I can have a singular admin UI for most daily tasks and not need to login to each system, with it's own login, UI, etc. (Replying by email doesn't work for all software/SaaS)
- KajMagnus @KajMagnus2019-12-03 21:58:58.838Z
Number of topics with replies, you mean?
Maybe I can change
limit = 25to a value taken from the URL param? Like,
limit=44&olderThanMs=<unix timestamp in milliseconds>, how would that work? (
&offset=...could be problematic if a new post appears, in between the API requests — then a post could get accidentally excluded when paginating the feed. But
olderThanMs=...doesn't have this problem)
event triggered webhooks— maybe you could reply with some JSON describing the data you'd like to receive, when a reply gets posted?
centralized customer area I'm working on— ok, good use case. ReTool looks nice, hmm I'm wondering, maybe something I could use too.
Sorry for the late reply.