3 ms·
Unfortunately we need this for Discord a lot more. Really should be a default thing instead of extra steps and on by default with the possibility to export to s
by anonzzzies 2y ago
Unfortunately we need this for Discord a lot more. Really should be a default thing instead of extra steps and on by default with the possibility to export to something else (static html with some search engine) so it doesn't depend on the discord server running.
- creesch 2y agoDiscord community servers can already be searched and discovered. Which is effectively what this is about. I suspect you are more talking about the conversation on discord? I don't think the actual chat conversations need to be indexed, in fact as a platform for chat I appreciate discord for what it is. though irc also worked fine for me back in the day. What annoys me more is the fact that discord these days is also used as a substitute for forums and such. There is so much information just hidden on discord you will only find when you know to join specific servers because there is no way to search for that information from the outside. For some topics and subjects that is fine. But for support for software (even open source) I feel that it is a loss and actually has contributed to a decline of information availability on the internet.
- squigz 2y ago> What annoys me more is the fact that discord these days is also used as a substitute for forums and such. There is so much information just hidden on discord you will only find when you know to join specific servers because there is no way to search for that information from the outside. Which would, of course, be solved by having those conversations indexed and searchable on the web.
- lxgr 2y ago> Discord community servers can already be searched and discovered. By those that have an account and that know on which "servers" to find the content they're looking for. > What annoys me more is the fact that discord these days is also used as a substitute for forums and such. There is so much information just hidden on discord you will only find when you know to join specific servers because there is no way to search for that information from the outside. And that's exactly the problem. Discord is a great Teamspeak successor (I suppose; I've never used that). It's a horrible substitute for a bug tracker, development roadmap, forum, release announcement feed etc.
- mdaniel 2y agoThat's why I loathe any project that picks Discord (or worse, fucking Slack) when Zulip exists, is open source, offers hosting for open source projects, and ships with "publish these channels to the web": https://zulip.com/help/public-access-option#enabling-web-public-channels-in-your-organization https://zulip.com/help/public-access-option#enabling-web-pub... To see it in action, feel free to open this in an incognito window, it won't prompt you for credentials https://leanprover.zulipchat.com/ https://leanprover.zulipchat.com/
- progval 2y agoZulip seems to rely too heavily on Javascript to be indexable by search engines. I copy-pasted some sentences from month-old posts on https://leanprover.zulipchat.com/ https://leanprover.zulipchat.com/ into Google and Bing, and neither could find the posts.
- tabbott 2y agoSearch engines are great at rendering content using JavaScript, they're just not able to explore the Zulip web application's URL structure, so they tend to index one page per Zulip installation. The current solution is that projects that want their publicly available content to be search engine indexed set up https://github.com/zulip/zulip-archive https://github.com/zulip/zulip-archive, which usually involves hooking a GitHub action up to GitHub Pages for a 0-infrastructure deployment. Ultimately, that's the same model as an IRC indexing project like this one: a separate tool from the chat server is responsible for search engine indexing. Lean runs one here: https://leanprover-community.github.io/archive/ https://leanprover-community.github.io/archive/, but it looks like it hasn't updated in a year, so likely whoever in the Lean community needs to investigate why it isn't updating. https://github.com/zulip/zulip/issues/21881 https://github.com/zulip/zulip/issues/21881 tracks our goal of making the server natively offer search engine indexing. The current separate archive tool model has some advantages (search engine load can't break the server, for example), but I think it'll be worth doing the native version when we can find the resources for it. Source: I lead the Zulip project.