memory-control VS AnswerOverflow

Indeed, webassembly is moving extremely slowly. I started a project years ago expecting https://github.com/WebAssembly/memory-control/blob/main/prop... and https://github.com/WebAssembly/memory64 to be fixed at some point. Neither are yet, and the project still suffers from it to this day.

I think wasm is still great without these fixes, but I have lost confidence in the idea that wasm will reach its full potential any time soon.

Additionally, googlers are championing memory control https://github.com/WebAssembly/memory-control/blob/main/prop..., which provides memory protection.

But researching it a bit I found this issue, so it clearly seems to be a problem for a bunch of people out there. And apparently both V8 and Spidermonkey have already addressed this quite recently, see this issue.

FWIW there is a proposal in the works to add page-based protection, which will allow unmapping the 0 page, restoring the trap-on-null-deref behavior that is important for many languages with safety checks.

https://github.com/WebAssembly/memory-control

> 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.