AnswerOverflow VS stringref

> TOO many bots log entire channels out to public html sites. This is prevalent in everything like discord etc but the degree to it in IRC is just ridiculous god knows what any of those 1500 bots in a channel are doing.

These sorts of bots are quite rare on Discord, you usually have to make an account to be able to see anything. There have been attempts at standardizing this (like https://www.answeroverflow.com/) but they haven't taken off. Public logs are much more common on IRC than on Discord.

Related: AnswerOverflow makes Discord messages searchable on Google/ other search engines. It’s open source.

https://www.answeroverflow.com/

I agree that the discord centralization for Q&A is becoming problematic, it makes it less discoverable and searchable (Had this problem a lot with Svelte).

That said, I have had success so far using https://www.answeroverflow.com/ to search discord for questions. It sucks we have to use such tools, but given the current situation, it's also better to adapt.

We've started mirroring our Discord to the web using https://www.answeroverflow.com/

You could roll your own equivalent but AnswerFlow has some nice features and handles issues around consent nicely.

If you're starting a Discord then I'd strongly recommend stating upfront that you might mirror content to another location even if you're not doing it now - it makes it a lot easier than doing so further down the line.

A better solution would be to not use Discord but friction, push-back from my colleagues on alternatives and a fear of fragmenting the community made this the best option for us.

The idea of Wasm as a universal plugin system is very promising. But string passing is maybe not the best example to highlight, considering that Wasm is introducing stringref to enable zero-copy string sharing between the Wasm runtime and host language.

https://github.com/WebAssembly/stringref/blob/main/proposals...

> dcodeIO (from the AssemblyScript community) was definitely not behaving in good faith

I certainly disagree with that take. I only see one person being frustrated because his concerns were being thrown under the rug as "non important", I would recommend you to read on dcode's blog to learn more about how the timeline happened [1]. There are always things to improve regarding how we communicate, of course, but those should not be used as a weapon to attack or dismiss someone but as means to improve.

It's also important to note that a few months after, the Wasm committee realized of the mistake and actually tried to solve it with the Wasm Stringref proposal [2].

The issue is not about if using UTF-8 or UTF-16 is the way to go, but how disagreement is being handled in what's supposed to be an open community

[1] https://dcode.io/#webassembly

[2] https://github.com/WebAssembly/stringref